I am almost certain you cannot convert a virtual SCSI HD to a virtual IDE HD. I think that you will ahve to recreate the VM's. Possibly somebody might tell you a way to clone a the VM and change the disk type but I doubt it. For all Linux VM the default (and recommended ) harddrive type is SCSI. Sorry.
Martin Felker wrote: I am almost certain you cannot convert a virtual SCSI HD to a virtual IDE HD.
First of all the OP wants to go from IDE to SCS not SCSI to IDE and secondly either or can be changed into the other simply by modifying the corresponding meta-data in both the .vmx configuration file and the Disk DescriptorFile of the .vmdk. This of course has to be done manually and should only be done by Users that understand what they're doing and know how to do it and should not be done without first backing up the corresponding files.
Sounds good. Sorry for the inadvertent interchange of HD type but it doesn't matter much if what you say will work without data loss. Since I may want to do this someday I wouldn't mind it you posted the exact changes to the .vmx file. For example could I just change ide to scsi in these lines.
ide0:0.present = "TRUE"
ide0:0.fileName = "Windows XP Professional.vmdk"
Or if SCSI replace with IDE? I don't think so but naturally I could be wrong. I could make a clone of this VM and try that out but I guess you must have so I don't have to .
It is not just the .vmx configuration file that has to be changed but also and more importantly the Disk DescriptorFile of the .vmdk.
Changes for a 40 GB virtual hard disk IDE vs. SCSI in both the .vmx configuration file and the DDB (Disk Data Base) section of the Disk DescriptorFile of the .vmdk. These are meant to be an example only and the actual geometry needs to be calculated on a case by case basis although these are the stock difference in the values of a 40 GB disk. Also keep in mind that in addition to modifying these values the drivers in the OS will need to be changed and in some cases this too will need to be done manually in order for all of this to work. Also the information below is not necessarily complete as there are other parameters/values that can come into play and why I previously stated "should only be done by Users that understand what they're doing and know how to do it".
Never modify a .vmdk without a full backup of the virtual hard disk!
ide0:0.present = "TRUE" ide0:0.fileName = "Windows XP Professional.vmdk"
ddb.geometry.cylinders = "16383" ddb.geometry.heads = "16" ddb.geometry.sectors = "63" ddb.adapterType = "ide"
scsi0.present = "TRUE" scsi0:0.present = "TRUE" scsi0:0.fileName = "Windows XP Professional.vmdk"
ddb.geometry.cylinders = "5874" ddb.geometry.heads = "255" ddb.geometry.sectors = "56" ddb.adapterType = "buslogic"
Well it looks like you''ve done it in the past!!. Myself I'd find it easier to make a new VM but everyone does not know all the advanced stuff you do I believe there may be some problems if you change the disk typle for an XP VM HD to SCSI since IDE is since IDE is recommened but I'm sure you are right and give the better advice !
I would like to thank everyone for the helpful advice. The solution is a little more advanced than I wish to take on but It is something to Practice and learn!!!
Again thanks everyone for your time!!!!!!!!
Martin Felker wrote: I believe there may be some problems if you change the disk typle for an XP VM HD to SCSI since IDE is since IDE is recommened but I'm sure you are right and give the better advice !
There is absolutely nothing wrong whatsoever with running Windows XP on a SCSI Virtual Hard Disk and it is the default adapter type when installing Windows XP using Easy Install. The issue with selecting SCSI when manually installing Windows XP is you need to manually supply the SCSI Driver at the appropriate time during the Windows Setup, otherwise Windows will not see the SCSI vHDD and with Easy Install the SCSI Driver is automatically supplied during the Windows Setup. That said back to the IDE2SCSI and as previously mentioned it is not just properly calculating the geometry difference and modifying the .vmdk and also the .vmx files along with adding the drivers to the filesystem it is also injecting the appropriate information into the Windows Registry when changing out the type of disk from under itself. I think it's actually easier to do with some Linux Distros then with Windows. The bottom line is even though it is technically possible to do these things, it is not necessarily practical for the average user and as you can see the OP has opted out. While for the advanced user it is faster to do this nonetheless for the average user one should use other methods to achieve the goal even though it takes longer. That's about all I have to say on this issue as I have no extra time right now.
I'm glad you outlined this tour de force. Since I am but a humble and often misinformed user going back to VMware 1.0 in 1999 I guess I'll just have to stick to the basics
Maybe I'll get a chance to play with these (viruatl) disk parameters after I get back from holiday. I'm going off the grid for two weeks.
i had more need to get familiar with these things in the the long, long time ago times when there where ESDI drives. FreeBSD works with this stuff also in partitioning.
I have many other computing interests than VMware. Not only VirtualBox but I just made my first QEM/KVM machine using AQEMU GUI. It looks very promising indeed! Nex up will be Xen.
As openSUSE says
'Have a lot of fun"
I actually need to the opposite for a small Non profit.
I used VMWare Converter to do a P2V from an old DELL T410 that had LSI SAS, into a VMWare SCSI Boot. Any other pathways I tried Disk2VHD, SCVMM Eval, Acronis would give me 0x7B BSODs.
Is there anyway I can convert this to an IDE booting Disk (as I need to put it on small Hyper V box)? I am trying to use Starwinds V2V to do VMDK to VHD, but not sure how to make SCSI 0 boot turn to IDE Primary 0?
Can VMWare Converter to a direct P2V from SCSI to IDE?
Can someone please guide as Im not getting a clear/ related answer/ discussion anywhere?
VMware Converter uses SCSI - to get an IDE-system you need to patch it manually.
What guestOS are talking about ?
P2V - SBS 2008 / Windows Server 2008.
What do you mean patch it manually? Is there a How To? Please guide. Thanks.
There is no howto that I am aware of - but it is not to tricky.
Install a Win 2008 to a a VM with IDE - then create a patch using the info you can find in registry.
With 2008 you basically need to activate the correct services listed in HKLM/system/controlset001/services