Running Virtual PC on an ESX host?

I'm running ESX virtual machines and installed Virtual Server 2005 R1 onto it no problem. I imported vms and vhd images but cannot start the virtual machines. I think it might have something to do with running a virtual machine within a virtual machine but don't know yet.

The error I get is: Could not be started because of a disk related error AND "The parent virtual hard disk PATH for the differencing virtual hard disk PATH does not exist. Please recconnect the differncing virtual hard disk to the correct parent virtual hard disk.
snyderkvAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vnekicCommented:
Before you deal with this in any other way.  Run a test and create a NEW VIRTUAL from scratch.  Perhaps install XP or something small and see how it runs.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
snyderkvAuthor Commented:
I tried what you suggested but for some reason the system is not seeing the ISO. The error is "The iso image actual file size does not match the size in the ISO volume discripter"

Anyways, to get back to the original issue, I think I know what the issue is. It's looking for a base image "base08A.vhd" in some path that doesn't exist. See I copied these images from the MOC courses. I have all VMC and VHDs but I don't know why it's looking for the parent base image base08A.vhd when I don't have it.

Could someone help out. I'm borrowing these from an MCT btw while he's on vacation so I can get a head start on training.
0
vnekicCommented:
well, just a small note.  If you create a NEW virtual and point it to the VHD, it will use that drive to START your OS.  Try that instead of using the existing config files.  Thats the easy way.  

But, you can always do some coding and open your config files in notepad which is not fun.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

snyderkvAuthor Commented:
I created a new VM and pointed to both virtuals. It actually runs now but doesn't boot up. Does the default behavior as if it wasn't their. Had no problems adding the vhd though.

Anyways it's my first time with VHD so I'm a little slow.
0
vnekicCommented:
Just make sure that the DEFAULT boot VHD is the one with the OS.  If need be.. find the virtual... rename/delete the VHD it created when you created the NEW VM ... and replace it with the BOOT VHD.  Make sure it's named the same as the original.

Now, something that can cause problems is that the controller (hard drive) needs to be configured as when it was orgianlly created.  Hopefully it was standard setup and no something special like a SCSI.

That's when you want to crack open the original config file and see what controller it was set up as.

So, if you created a NEW VM and then added a second drive that points to tour BOOT OS.. that won't work for yah unless you go into the VIRTUAL BIOS and set the drive.

Or just replace the BLANK drive with the VHD you know has the OS.
0
snyderkvAuthor Commented:
Thanks good points.

I tried creating a new VM without creating the disk and simply adding the available boot disks. It says that the disk could not be created and that an unkown error occurred while attempting to access the disk. The D drives of all the disks work.

I added the D drive and renamed the actual C drive to match the D drive kinda like you suggested. Still no luck.

How do you get into the bios on this thing? I opened the VMRC and quickly pressed F2 but no luck. I'm thinking I have issues with VPC within ESX so what I will do is try and boot to BIOS and get the stupid media to boot and do a fresh install.
0
snyderkvAuthor Commented:
Ok I was able to boot to a Dell Open Manage CD. So I guess that part is working
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
(if this question has not been abandoned!)

Most likely that nested Hypervisors are not supported.

Why would you want to run a hypervisor inside ESX, convert the virtual machines on virtual server to ESX using VMware Convertor Standalone.

See here

Download VMware vCenter Converter here

http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vcenter_converter_standalone/4_0

VMware vCenter Converter Standalone 4.x Documentation

http://www.vmware.com/support/pubs/converter_pubs.html

VMware vCenter Converter Standalone 4.3 User Guide

http://www.vmware.com/pdf/convsa_43_guide.pdf

For the conversion steps, read fellow Expert Bestway's article.

http://www.experts-exchange.com/Software/VMWare/A_3639-VMware-vConverter-P2V-for-Windows-Servers.html

Best Practice Video Guide here

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004588
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.