|
Moey posted:Edit: Actually the Unity VM had a corrupted VMDK, so I had to do a database backup/restore to get that piece of poo poo moved. This seems to be par for the course with CUCM virtual appliances. If the guest doesn't shutdown cleanly then it's probably going to be cactus when you turn it back on. Pile Of Garbage fucked around with this message at 15:06 on May 5, 2017 |
#
?
May 5, 2017 12:51
|
|
|
|
| # ? Apr 25, 2024 08:23 |
|
|
Moey posted:I randomly use this to check, my coworker is a monster. anthonypants posted:Here's some backstory on that host: evil_bunnY fucked around with this message at 13:53 on May 5, 2017 |
|
#
?
May 5, 2017 13:51
|
|
|
evil_bunnY posted:You're sending resumes around yeah?
|
|
#
?
May 5, 2017 17:23
|
|
|
evil_bunnY posted:I've removed snap privileges from one of my (now former) coworkers for precisely this reason. He got the loving alarms too. You are doing the Lord's work.
|
|
#
?
May 6, 2017 01:49
|
|
|
So I want to make my old PC into a VM host, but ESXi doesn't seem to like the Realtek NIC, is there some easy way to bypass this?
|
|
#
?
May 7, 2017 20:11
|
|
|
Short answer: get an intel nic, the realtek nics are not great. Long answer: You can find howtos on how to embed drivers for realtek nics online, but really - just get an intel nic. Dual ports are nice.
|
|
#
?
May 7, 2017 20:13
|
|
|
SEKCobra posted:So I want to make my old PC into a VM host, but ESXi doesn't seem to like the Realtek NIC, is there some easy way to bypass this?
|
|
#
?
May 7, 2017 20:14
|
|
|
Wibla posted:Short answer: get an intel nic, the realtek nics are not great. All those guides don't seem to apply to 6.5 and none of the tools seem to work on Windows 10 anthonypants posted:Can you define what "doesn't seem to like" means It says it doesn't like it.
|
|
#
?
May 7, 2017 20:25
|
|
|
SEKCobra posted:It says it doesn't like it. Realtek nics are designed to be as cheap as possible and rely on the OS driver doing stuff that any real NIC should be doing on-board. They're basically winmodems for Ethernet. Attempting to make a realtek driver for ESXi is a recipe for disaster and pink screens of death.
|
|
#
?
May 7, 2017 20:36
|
|
|
Get yourself VMWare workstation instead
|
|
|
#
?
May 7, 2017 21:02
|
|
|
Or, y'know, hyper-v. Or ovirt. Workstation is not comparable
|
|
#
?
May 8, 2017 02:15
|
|
|
If you're just trying to host a few VMs on an old non-server with Windows already on it and you're having NIC troubles I don't see the point of installing a full on hypervisor. I don't think ovirt is going to help with that and Hyper-V sucks donkey rear end for Linux distros compared to Workstation.
|
|
|
#
?
May 8, 2017 02:50
|
|
|
milk milk lemonade posted:If you're just trying to host a few VMs on an old non-server with Windows already on it and you're having NIC troubles I don't see the point of installing a full on hypervisor. I don't think ovirt is going to help with that and Hyper-V sucks donkey rear end for Linux distros compared to Workstation. Well, if he's installing ESXi, so Windows doesn't matter much there. For bare metal, oVirt basically gets support for every NIC Linux supports, so crappy realteks are fine. Hyper-V is also totally fine. The loss is in same page sharing, and the console isn't great, but let's assume these are server VMs given the lack of evidence to the contrary, since that's the norm. "Free bare metal hypervisor which works with realtek nic" is not the same as "vmware workstation", which only really has a win here if you need/want and accelerated console or specifically want ESXi (to virtualize it on workstation with your crappy realtek running on Windows/Linux on the host)
|
|
#
?
May 8, 2017 06:16
|
|
|
Run ESXi in workstation.  ESXi will like the virtual intel nic.
|
|
#
?
May 8, 2017 06:31
|
|
|
I want to put on a selection of WIndows and Linux servers and I want to manage it remotely, other than that I'm open to trying just about anything.
|
|
#
?
May 8, 2017 08:54
|
|
evol262 posted:Well, if he's installing ESXi, so Windows doesn't matter much there. Uh he already said he's having problems getting the NIC working. That's why I said ovirt won't make much a difference. Hyper-V requires either a server license or a Pro license. It is also awful for a bunch of things, not least of which is getting a range of Linux distros working. Running it with a GUI is a waste too. From what I gather from person whose posts I'm responding to they already have a Windows OS to use. So workstation is a fine, easy shortcut that will get around the NIC issues. Thanks for the lesson though?
|
|
|
#
?
May 8, 2017 11:17
|
|
|
milk milk lemonade posted:Uh he already said he's having problems getting the NIC working. That's why I said ovirt won't make much a difference. Bare metal Hyper-V Server is free. https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016
|
|
#
?
May 8, 2017 11:28
|
|
|
milk milk lemonade posted:Uh he already said he's having problems getting the NIC working. That's why I said ovirt won't make much a difference. You know it's rude to talk about a person like they aren't in the room, right? 
|
|
#
?
May 8, 2017 12:36
|
|
|
milk milk lemonade posted:Uh he already said he's having problems getting the NIC working. That's why I said ovirt won't make much a difference. Look, there's no reason to be rude as gently caress. Having problems getting the NIC working with ESXi has absolutely no bearing on oVirt. If he's having problems with the NIC in general, just get an Intel NIC, install ESXi, and be done with it. If it's just with ESXi, oVirt does solve this problem. Workstation is also awful at a lot of things. It's easy to make unsubstantiated claims when you don't provide any details. Hyper-V is fine for Linux. The only real outstanding issue is that Hyper-V 2 has problems worth SuSE and secureboot. I've used it very heavily for Linux. Virtualbox is also a free option if it's not bare metal. SEK: Intel NIC and ESXi, or use oVirt. If remote management is important. Hyper-V may have a free remote management tool now, but if there is one, I don't know it. Someone will correct me, though.
|
|
#
?
May 8, 2017 12:58
|
|
|
I'll have to find my Intel NICs when I am at my parents place the next time, might try ovirt in the meantime.
|
|
#
?
May 8, 2017 13:05
|
|
|
Grab the proper drivers for your Realtek card from https://vibsdepot.v-front.de/wiki/index.php/List_of_currently_available_ESXi_packages and build a custom ISO with them. They will still work on 6.5.
|
|
#
?
May 8, 2017 16:52
|
|
|
big money big clit posted:Grab the proper drivers for your Realtek card from https://vibsdepot.v-front.de/wiki/index.php/List_of_currently_available_ESXi_packages and build a custom ISO with them. They will still work on 6.5. The tool for making the iso apparently doesn't work on WIndows 10.
|
|
#
?
May 8, 2017 18:27
|
|
|
You could always virtualize windows 7 with vbox just to make the ISO or something
|
|
#
?
May 8, 2017 18:40
|
|
|
SEKCobra posted:The tool for making the iso apparently doesn't work on WIndows 10. What is the tool? I have been using this. https://www.v-front.de/p/esxi-customizer-ps.html
|
|
#
?
May 11, 2017 04:13
|
|
|
Not sure if this is the right thread for Horizon stuff, but is anyone else running into this issue with Horizon View 7.1 dedicated linked-clones with persistent disks and Windows 10 v1607? There is a bug where the start menu just doesn't work, most likely due to some file(s) that is being redirected to the persistent disk. VMware acknowledges the bug in this release but the tech I talked to said he isn't privy to any info regarding a patch coming down the line aside from a release date of 'this year'.
|
|
#
?
May 11, 2017 14:54
|
|
|
Aw gently caress, PowerCLI 6.5.1 came out a month ago and no one told me.
|
|
#
?
May 19, 2017 23:04
|
|
|
I have a few hundred VM Templates, that I need to spin up to apply updates, and then convert back to templates. Everyone in the company does it manually, taking the sweet time of converting template to VM, turning the VM on, logging in, applying updates, shutting down, and then converting back to template. Can someone throw me a bone on how to make this a little less manually? In my mind, a script would go like: quote:for-each VM template{ I'm relatively comfortable in Powershell and PowerCLI, but my experience with coming up with a script from zero is not one of my strong areas. Down the road, I'd love to explore and compare scripts that do this one at a time, versus as many as possible in parallel (can't really convert all templates to VM at the same time, as there's not enough resources for that)... I'd like to start by scripting the current workflow, and from there move on to optimizations.
|
|
#
?
May 25, 2017 19:26
|
|
|
I seriously question why you have a few hundred VM Templates. That being said, I thought VMware Update Manager could handle this, but maybe not. If not, this link seems to be a good start - https://communities.vmware.com/thread/500805
|
|
#
?
May 25, 2017 20:59
|
|
|
Such a good contention point you bring up, and one that I've shared upstream inside my Org. The response I get is that these are our "goldens" to deliver pre-configured servers, but the reality is that they're not even half-baked, so I don't really know. Not really my fight (for now). Anyway... That link is a good start, thank you for that. I'll hack my way forward now.
|
|
#
?
May 25, 2017 21:27
|
|
|
Alfajor posted:Such a good contention point you bring up, and one that I've shared upstream inside my Org. The response I get is that these are our "goldens" to deliver pre-configured servers, but the reality is that they're not even half-baked, so I don't really know. Not really my fight (for now). The problem here is that your company is trying to use VMware templates to do configuration management, and that's not what they are for, so any solution to this will be lovely. You should have a relatively limited set of templates and then configuration management will push applications and configuration information based on the personality that server should have. Internet Explorer posted:I seriously question why you have a few hundred VM Templates. That being said, I thought VMware Update Manager could handle this, but maybe not. If not, this link seems to be a good start - https://communities.vmware.com/thread/500805 UM doesn't really deal with guests, aside from updating VMware tools. It's for host patching and upgrades predominantly.
|
|
#
?
May 25, 2017 22:42
|
|
|
big money big clit posted:UM doesn't really deal with guests, aside from updating VMware tools. It's for host patching and upgrades predominantly. I've never used it for that purpose (or really any other) but this seems to imply it used to and I'm not going completely crazy. http://www.vmwareinfo.com/2011/09/no-more-windows-patching-via-vmware.html
|
|
#
?
May 25, 2017 23:32
|
|
|
Update manager used to be able to do all kinds of guest patching stuff. I don't know if it still can.
|
|
#
?
May 26, 2017 00:33
|
|
|
adorai posted:Update manager used to be able to do all kinds of guest patching stuff. I don't know if it still can. It cannot.
|
|
#
?
May 26, 2017 01:22
|
|
|
I preface this by saying I have never tried this on the combination of Windows guests and VMware hosts, so it may not work for poo poo. I am a Linux guy these days. With that ringing endorsement out of the way, have you looked at using Packer to build and provision your templates? It at least claims to support Windows guests and building the VM on ESXi. The idea is to have it boot a VM, install the base OS, run whatever arbitrary provisioning commands you want (install Foo, run Windows Update, create C:\NotPorn\ etc), then save the resulting image. All with one command powered by configs and scripts you can stick in version control and automate like it's 2017. This is what we do in our Linux/XenServer world, and it owns. Whether it is fully baked on the Windows/VMware side of things, I don't know.
|
|
#
?
May 26, 2017 02:05
|
|
|
If the templates are domain joined and connected to WSUS you should be able to query that for patch status. Toss them in their own OU with aggressive autoupdate settings, I'd probably try to avoid running it as a single long running script and instead make it 2 scripts, one to thaw all the VMs and a second to freeze them once it detects WSUS is up to date. Set them to run after your WSUS admin approves updates (every Monday after patch Tuesday or whenever). 1st script runs at 8am to to kick the process off then run the second every hour after that.
|
|
#
?
May 26, 2017 13:04
|
|
|
Docjowles posted:This is what we do in our Linux/XenServer world, and it owns. Whether it is fully baked on the Windows/VMware side of things, I don't know.
|
|
#
?
May 26, 2017 16:35
|
|
|
Docjowles posted:I preface this by saying I have never tried this on the combination of Windows guests and VMware hosts, so it may not work for poo poo. I am a Linux guy these days. why this over puppet?
|
|
#
?
May 26, 2017 17:36
|
|
|
Roargasm posted:why this over puppet? It's not adverse to puppet, it could easily be in addition to puppet. Packer has a puppet provider built in. Anyway, to answer the question you maybe were asking, packer is good at one thing - building images. Puppet isn't so good at building images, it's good at setting desired state. Which means you're still making some glue around puppet (like say jenkins, or whatever) to launch the VM, run puppet, and then make an image. Packer can do all of this, it's the obvious tool for making images (hence, packing them!)
|
|
#
?
May 26, 2017 21:45
|
|
|
Roargasm posted:why this over puppet? It's a level above puppet. Packer boots the actual VM from nothing. Then you tell it to use puppet or whatever tool you want (for us it happens to be Chef) to configure the VM. Then packer shuts it down and exports it to its final destination. Also I happen to think Puppet is bad but that is neither here nor there. If you are using some config management at all that is 95% of the battle. Docjowles fucked around with this message at 21:51 on May 26, 2017 |
|
#
?
May 26, 2017 21:48
|
|
|
|
| # ? Apr 25, 2024 08:23 |
|
|
Or you could just keep a few very basic and bare bones templates and use puppet to configure them on creation for their intended role, rather than keeping a hundred special snowflake images that all need to be converted to VM and turned on and updated and turned off and converted back to templates.
|
|
#
?
May 27, 2017 00:16
|
|