You mix old an new syntax. Correct way (new) is:
Code:
drive file=/dev/sdc,index=0,media=disk,cyls=c,heads=h,secs=s,trans=nonemigrating from VMware using raw block device?
- Thread starter mangoo
- Start date
You mix old an new syntax. Correct way (new) is:
No, it must be something else.
Qemu's "BIOS" shows the devices with their sizes correctly even if I use "drive" option.
I mixed it to use -hda /dev/sdc with -hdachs 8192,16,32,none, then many tests...
So I'm a bit closer now.
The system does NOT boot using:
-drive file=/dev/sdc,index=0,media=disk
The system boots, but bluescreens later in a boot process saying it can't find a boot device when I use:
-drive file=/dev/sdc,index=0,media=disk,cyls=8192,heads=16,secs=32,trans=none
The system DOES boot when I add another drive:
-drive file=/dev/sdc,index=0,media=disk,cyls=8192,heads=16,secs=32,trans=none -drive file=/dev/sdc,index=2,media=disk
But it's not optimal - Windows sees one 8 GB drive (correct size) and one 2 GB drive.
When I boot Linux off a live CD, it sees both drives with 8 GB size.
The system does NOT boot if I use additional options for both drives (bluescreen):
-drive file=/dev/sdc,index=0,media=disk,cyls=8192,heads=16,secs=32,trans=none -drive file=/dev/sdc,index=2,media=disk,cyls=8192,heads=16,secs=32,trans=none
or if I use one drive with index=2 (does not past BIOS):
-drive file=/dev/sdc,index=2,media=disk
In the config file, it will boot with:
ide0: /dev/sdc,media=disk,cyls=8192,heads=16,secs=32,trans=none
ide2: /dev/sdc
It will NOT boot with (i.e., when boot=on is added by qm for a given device):
bootdisk: ide0
ide0: /dev/sdc,media=disk,cyls=8192,heads=16,secs=32,trans=none
ide2: /dev/sdc
It's still a bit strange why I have to supply "two disks"; perhaps I have to reinstall, which is not that pleasant.
ide0: /dev/sdc,media=disk,cyls=8192,heads=16,secs=32,trans=none
ide2: /dev/sdc
It will NOT boot with (i.e., when boot=on is added by qm for a given device):
bootdisk: ide0
ide0: /dev/sdc,media=disk,cyls=8192,heads=16,secs=32,trans=none
ide2: /dev/sdc
It's still a bit strange why I have to supply "two disks"; perhaps I have to reinstall, which is not that pleasant.
I want to help but I still miss info.
Pls describe it that I can setup the same here in the lab. You have a VMware (which vmware version?) guest, windows 2003, using direct device mappings (/dev/s...).
Now, how do you "migrate" this to Proxmox VE? If you install Proxmox VE, disks are formatted so you do something different. what?
Pls describe it that I can setup the same here in the lab. You have a VMware (which vmware version?) guest, windows 2003, using direct device mappings (/dev/s...).
Now, how do you "migrate" this to Proxmox VE? If you install Proxmox VE, disks are formatted so you do something different. what?
It is VMware 1.0.3 (so perhaps any 1.0.x version should do).
Windows 2003 is installed on a "raw device" (i.e., /dev/sdh).
"Migration" is pretty simple:
- create a new virtual machine in Proxmox VE
- edit /etc/qemu-server/<new-VM>.conf, replace the HDD (pointing to a file) with a raw device (i.e., /dev/sdj). This should be the same device (or a copy) which was used by VMware. Or, just dd if=/dev/disk/used/by/vmware of=bigfile, and try to start off the "bigfile".
Try to start the virtual machine - it will fail at the very beginning, as I explained earlier.
Let me know what more information you need.
another possible way: convert the existing vmware via vmware converter to a vmware single disk file guest and follow then this howto.
not tried yet, but I will test this.