Migrated Windows VM via qemu-nbd and selfimage, no boot

O

obrienmd

Member
Oct 14, 2009
109
0
16
Proxmox 1.5 w/ latest updates, 2.6.32.

Used the following guide: http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE, section "Physical server to Proxmox VE using SelfImage". However, when I try to boot the server, the SeaBIOS comes up, says booting from hard drive, then just sits there.

The transfer went fine, I can mount both logical volumes (qemu-nbd targets) in linux (just mount as normal ntfs drives). However, when I run fdisk -l, some very funky information comes up:

Code: 
Disk /dev/dm-6: 644.2 GB, 644245094400 bytes
255 heads, 63 sectors/track, 78325 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x69205244
This doesn't look like a partition table
Probably you selected the wrong device.
     Device Boot      Start         End      Blocks   Id  System
/dev/dm-6p1   ?       13578      119522   850995205   72  Unknown
Partition 1 does not end on cylinder boundary.
/dev/dm-6p2   ?       45382       79243   271987362   74  Unknown
Partition 2 does not end on cylinder boundary.
/dev/dm-6p3   ?       10499       10499           0   65  Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/dm-6p4          167628      167631       25817+   0  Empty
Partition 4 does not end on cylinder boundary.

All qemu-nbd target lvs look very similar to this. Any ideas?
 
obrienmd said:
Proxmox 1.5 w/ latest updates, 2.6.32.

Used the following guide: http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE, section "Physical server to Proxmox VE using SelfImage". However, when I try to boot the server, the SeaBIOS comes up, says booting from hard drive, then just sits there.

The transfer went fine, I can mount both logical volumes (qemu-nbd targets) in linux (just mount as normal ntfs drives). However, when I run fdisk -l, some very funky information comes up:

Code: 
Disk /dev/dm-6: 644.2 GB, 644245094400 bytes
255 heads, 63 sectors/track, 78325 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x69205244
This doesn't look like a partition table
Probably you selected the wrong device.
     Device Boot      Start         End      Blocks   Id  System
/dev/dm-6p1   ?       13578      119522   850995205   72  Unknown
Partition 1 does not end on cylinder boundary.
/dev/dm-6p2   ?       45382       79243   271987362   74  Unknown
Partition 2 does not end on cylinder boundary.
/dev/dm-6p3   ?       10499       10499           0   65  Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/dm-6p4          167628      167631       25817+   0  Empty
Partition 4 does not end on cylinder boundary.
All qemu-nbd target lvs look very similar to this. Any ideas?
Click to expand...

Hi,
it's the same result if you use the qcow2-file as drive instead the convertet raw-device on lvm?
Your disk-file should have a valid disk-partition. Perhaps you don't have selectet in SelfImage the whole disk (default is only partition 1 if i remember right).

Udo
 
Hrm, so I imaged the whole disk this time. However, now when I boot I get a BSOD and it reboots every time (about 3 seconds into loading Windows). I loaded the IDE drivers as displayed in the wiki!?
 
obrienmd said:
Hrm, so I imaged the whole disk this time. However, now when I boot I get a BSOD and it reboots every time (about 3 seconds into loading Windows). I loaded the IDE drivers as displayed in the wiki!?
Click to expand...
Hi,
that can happens. I have made three different experiences:
1. windows boot without trouble (only filesystem check).
2. It's nessessary to run a repair-install over the windows. After that all runs fine.
3. The repair-install don't help - in this case i do a fresh install... perhaps some else has a better hint.

Udo
 
You must log in or register to reply here.
Top Bottom