dynamik wrote: » Awesome. I'm glad I'm not the only one that's going to get sued
tiersten wrote: » You're worried about getting sued when you're going to be drugged and tattooed when in Chicago? Priorities man!
tiersten wrote: » Oh and Gojamba needs to learn to crop or resize screenshots...
Gomjaba wrote: » "only" limitation : You cannot power-on a virtual machine inside the virtual ESX Cluster - which is I suppose fair enough considering (see the error)
astorrs wrote: » My god you people sure ignore NDAs when they're not related to cert exams.
dynamik wrote: » Are you kidding!? I'm looking forward to it
dynamik wrote: » He just likes to show off his resolution. I bet he's really on like a 12" display and has to paste four screenshots together in Photoshop to come up with that
JDMurray wrote: » I was starting to get a "barber shop mirror" headache about the existential possibilities until I read this limitation.
tiersten wrote: » Yup. Bit strange IMO.
Gomjaba wrote: » Installing VMware Workstation inside of a ESX based virtual machine - Chris Nackers Blog Haven't tried it yet though (bottom of the article)
darkerosxx wrote: » Spare astorrs, he comes from the land of Canada and I'm sure he gets "you people" a lot more than we do. Plus, I'm guessing he actually IS Canadian, so he can't help it.
bertieb wrote: » What do YOU mean YOU people?*Sorry, had to get a Tropic Thunder quote in there somewhere after reading Claymoore posting elsewhere about going full retard
JDMurray wrote: » However, when I tried to start the VM, I received the expected, "You may not power on a virtual machine in a virtual machine" message.
astorrs wrote: » What kind of CPU are you using and do you have VT and NX enabled in the BIOS?
JDMurray wrote: » VT and NX enabled in VMWare Workstation's BIOS? I didn't think to check that. Heck, if VMWare doesn't want VM-in-VM action in its products all it needs do is not support virtualization in its own VM BIOS. But that would mean Windows 7's virtual XP compatibility feature wouldn't work when Windows 7 was running in Workstation either.
JDMurray wrote: » OK, I followed the instructions in this blog article for installing VMWare Workstation in a guest OS running in ESXi. My host was ESXi 3.5.0 U4 and my guest OS was Windows Vista Ultimate SP2. I was able to install VMWare in the guest OS, create a VM, and edit the .vmx file as required. However, when I tried to start the VM, I received the expected, "You may not power on a virtual machine in a virtual machine" message. I looked in the VM's log files but didn't see anything that indicated a specific problem. My conclusion is that the instructions in the blog article are insufficient to achieve the article's claim. If anyone else wants to duplicate my experiment, here are some clarifications on the blog article's instructions that you'll need:Orca is an editor for Microsoft Installer (.msi) files. Orca is only distributed with the Windows Installer 4.5 SDK or the Microsoft Windows Software Development Kit (SDK). If you install the Windows SDK, you only need to select the Windows Installer SDK for installation and not all SDKs in the package. I recommend downloading the Windows Installer 4.5 SDK because it is the latest release. Once the Installer SDK is installed, you'll need to run the oraca.msi package to actually install Orca. This will be either C:\Program Files\Windows Installer 4.5 SDK\TOOLS\orca.msi or C:\Program Files\Microsoft Platform SDK\Bin\Orca.msi depending which SDK you installed. Only after Orca is installed will you see the "Edit with Orca" menu item when you right-click a .msi file. In addition to the .msi file, be sure to transfer all of the subfolders over to the guest OS too. Run the .msi file to install VMWare Workstation on the guest OS. After installing and rebooting, create a new VM using the "I will install the operating system later" option. Also, don't select the "Power on this virtual machine after creation" option. The values of the monitor_control settings in the .vmx file require double quotes ("TRUE") like all the other values in the file. If you have not already entered a valid license key into VMWare Workstation, you will be required to do so before the VM may be powered-on.
astorrs wrote: » LOL no I meant on the physical PC. VM-in-a-VM only works with very specific CPUs.
cnackers wrote: » However, your probably gonna need some very specific hardware and probably need to change a few more settings or play around with various CPU settings. You also probably need to play around with various templates as well, since i've seen several recommendations to start with a Red Hat Linux template as opposed to an Windows template. (Whether it's creating a ESX test environment or attempting VMware workstation inside ESX)
JDMurray wrote: » My physical PC is already running ESXi 3.5.0, so it's a foregone conclusion that my hardware supports virt. Do you know which CPUs support it?
Hunterprime wrote: » Acutally only the AMD Athalon 64 X2 AM2/Phenom and above have across the board support for hardware Virtualization. Intel has not been consistent on which of their CPU's support it.How many Intel CPUs will fail the XP Mode test in Windows 7? | Ed Bott’s Microsoft Report | ZDNet.com has a list of Intel Desktop CPU that support it. Also most Motherboards and systems out of the box do not have the tech turned on in the BIOS. Funny that this was the thing to cause me to stop lurking and post.
Hunterprime wrote: » Acutally only the AMD Athalon 64 X2 AM2/Phenom and above have across the board support for hardware Virtualization. Intel has not been consistent on which of their CPU's support it.
