[PVE-User] Backup WIN7 VM on Proxmox 2.2, restore on Proxmox 4.4 results in "Boot failed: not a bootable disk

[Eneko Lacunza]

Seems strange. Have you tried to boot to a windows 7 installation ISO 
and inspect the virtual disk from within? Maybe try also "repair boot"?

El 30/06/17 a las 09:39, Carsten Bleek escribió:
> Hi Eneko,
>
> VM starts, but windows does not boot.
>
> There is something stange with the raw image. On Proxmox 2.2 Windows 
> is booting. But I can't get any partition informations
>
> Using parted:
>
> parted /var/lib/vz/images/303/vm-303-disk-1.raw
> GNU Parted 2.3
> Using /var/lib/vz/images/303/vm-303-disk-1.raw
> Welcome to GNU Parted! Type 'help' to view a list of commands.
> (parted) p
> Error: /var/lib/vz/images/303/vm-303-disk-1.raw: unrecognised disk label
>
> Using: fdisk
>
> root at cross-prox:~# fdisk /var/lib/vz/images/303/vm-303-disk-1.raw
> Device contains neither a valid DOS partition table, nor Sun, SGI or 
> OSF disklabel
> Building a new DOS disklabel with disk identifier 0xe6aadbb7.
> Changes will remain in memory only, until you decide to write them.
> After that, of course, the previous content won't be recoverable.
>
> Warning: invalid flag 0x0000 of partition table 4 will be corrected by 
> w(rite)
> You must set cylinders.
> You can do this from the extra functions menu.
>
> WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
>          switch off the mode (command 'c') and change display units to
>          sectors (command 'u').
>
> Command (m for help): p
>
> Disk /var/lib/vz/images/303/vm-303-disk-1.raw: 0 MB, 0 bytes
> 255 heads, 63 sectors/track, 0 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0xe6aadbb7
>
>                                    Device Boot      Start End Blocks   
> Id  System
>
> Command (m for help): q
>
> Regards,
>
> Carsten
>
> Am 30.06.2017 um 09:30 schrieb Eneko Lacunza:
>> Hi Carsten,
>>
>> VM doesn't start, or Windows doesn't boot?
>>
>> If VM doesn't start please send error log.
>>
>> El 30/06/17 a las 09:04, Carsten Bleek escribió:
>>> Hi,
>>>
>>> I'm trying to move a KVM Win7 VM from an 2.2 to a 4.4 Proxmox using 
>>> ZFS. I've done it using the normal backup/restore feature of the 
>>> Proxmox GUI. In addition, I've tried to bypass Backup/Restore as 
>>> descibed in 
>>> https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0#Bypassing_Backup_and_Restore 
>>> (same result).
>>>
>>> Regards,
>>>
>>> Carsten
>>>
>>>
>>>
>>> On 4.4 KVM runs as (VM is not not booting):
>>>
>>> /usr/bin/kvm -id 303 -chardev 
>>> socket,id=qmp,path=/var/run/qemu-server/303.qmp,server,nowait -mon 
>>> chardev=qmp,mode=control -pidfile /var/run/qemu-server/303.pid 
>>> -daemonize -name Win7 -smp 4,sockets=2,cores=2,maxcpus=4 -nodefaults 
>>> -boot 
>>> menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg 
>>> -vga std -vnc unix:/var/run/qemu-server/303.vnc,x509,password 
>>> -no-hpet -cpu 
>>> kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce 
>>> -m 4096 -k de -device 
>>> pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device 
>>> pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device 
>>> piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device 
>>> usb-tablet,id=tablet,bus=uhci.0,port=1 -device 
>>> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi 
>>> initiator-name=iqn.1993-08.org.debian:01:7a05c3c8a25 -drive 
>>> file=/var/lib/vz/images/303/vm-303-disk-1.raw,if=none,id=drive-ide0,cache=writethrough,format=raw,aio=threads,detect-zeroes=on 
>>> -device 
>>> ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100 
>>> -drive if=none,id=drive-ide2,media=cdrom,aio=threads -device 
>>> ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 
>>> -netdev 
>>> type=tap,id=net0,ifname=tap303i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown 
>>> -device 
>>> e1000,mac=08:00:27:8C:BA:31,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 
>>> -rtc driftfix=slew,base=localtime -global 
>>> kvm-pit.lost_tick_policy=discard
>>>
>>> On 2.2 KVM runs as and the VM ist booting.
>>>
>>> usr/bin/kvm -id 303 -chardev 
>>> socket,id=monitor,path=/var/run/qemu-server/303.mon,server,nowait 
>>> -mon chardev=monitor,mode=readline -vnc 
>>> unix:/var/run/qemu-server/303.vnc,x509,password -pidfile 
>>> /var/run/qemu-server/303.pid -daemonize -usbdevice tablet -name Win7 
>>> -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga std -localtime 
>>> -rtc-td-hack -no-kvm-pit-reinjection -no-hpet -k de -drive 
>>> file=/dev/cdrom2,if=none,id=drive-ide2,media=cdrom,aio=native 
>>> -device 
>>> ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 
>>> -drive 
>>> file=/var/lib/vz/images/303/vm-303-disk-1.raw,if=none,id=drive-ide0,cache=directsync,aio=native 
>>> -device 
>>> ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100 -m 
>>> 4096 -netdev 
>>> type=tap,id=net0,ifname=tap303i0,script=/var/lib/qemu-server/pve-bridge 
>>> -device 
>>> e1000,mac=08:00:27:8C:BA:31,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 
>>> -cpuunits 1000
>>>
>>
>
>

-- 
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943493611
       943324914
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
www.binovo.es