Migrate VM (Windows 8.1) KVM from Proxmox 2.3 to 3.0 - BSOD - can not boot

S

sabinemayr5

New Member
Aug 24, 2014
5
0
1
Hello!

I have a straingh problem. Every VM can migrate without problmens (e.g. dd oder copy raw file). But with this Windows Guest i always get the microsoft recovery console. Windows is fixing some problmes and auto reboot. After that the recovery starts again ...

other guests are centos, debian and ubuntu -> no problmes here

any hints?

Greetz,

Sabine
 
sabinemayr5 said:
Hello!

I have a straingh problem. Every VM can migrate without problmens (e.g. dd oder copy raw file). But with this Windows Guest i always get the microsoft recovery console. Windows is fixing some problmes and auto reboot. After that the recovery starts again ...

other guests are centos, debian and ubuntu -> no problmes here

any hints?

Greetz,

Sabine
Click to expand...
Hi,
and which cpu-type do you use inside the VM? Can you post the VM-config?

Udo
 
old server:

processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
stepping : 9
cpu MHz : 3392.371
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips : 6784.74
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:



new server:

processor : 11
vendor_id : GenuineIntel
cpu family : 6
model : 62
model name : Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
stepping : 4
cpu MHz : 2600.092
cache size : 15360 KB
physical id : 0
siblings : 12
core id : 5
cpu cores : 6
apicid : 11
initial apicid : 11
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips : 5200.18
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:


vm config:

boot: cd
bootdisk: ide0
cores: 2
ide0: storage2:vm-114-disk-1,size=64G
ide1: none,media=cdrom
ide2: none,media=cdrom
keyboard: de
memory: 4096
name: win8
net0: virtio=XXXXXXXXXXXXX,bridge=vmbr0
ostype: win8
sockets: 1


i tried also virtio (virtio was the normal mode for the guest)
cloning with fsarchiver

thanks :-)
 
sabinemayr5 said:
old server:

processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
stepping : 9
cpu MHz : 3392.371
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips : 6784.74
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:



new server:

processor : 11
vendor_id : GenuineIntel
cpu family : 6
model : 62
model name : Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
stepping : 4
cpu MHz : 2600.092
cache size : 15360 KB
physical id : 0
siblings : 12
core id : 5
cpu cores : 6
apicid : 11
initial apicid : 11
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips : 5200.18
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:


vm config:

boot: cd
bootdisk: ide0
cores: 2
ide0: storage2:vm-114-disk-1,size=64G
ide1: none,media=cdrom
ide2: none,media=cdrom
keyboard: de
memory: 4096
name: win8
net0: virtio=XXXXXXXXXXXXX,bridge=vmbr0
ostype: win8
sockets: 1


i tried also virtio (virtio was the normal mode for the guest)
cloning with fsarchiver

thanks :-)
Click to expand...
Hi,
you pve 3.0 system is outdated, you should update! (some peaple have kernel panics with kernel > 2.6.32-27- perhaps update and also intall the -27 kernel for booting in case of trouble).
It's not an gurantee that you VM run's after that, but Proxmox VE 3.1 has cpu-flag optimations ( see http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.1 ).

You wrote your old system was an pve 2.3?! The roadmap say that since version the cpu is KVM64 as default CPU type (previously qemu64) .
Perhaps you should test the old one?!

Udo
 
ok i will try this tomorrow


udo said:
Hi,
you pve 3.0 system is outdated, you should update! (some peaple have kernel panics with kernel > 2.6.32-27- perhaps update and also intall the -27 kernel for booting in case of trouble).
It's not an gurantee that you VM run's after that, but Proxmox VE 3.1 has cpu-flag optimations ( see http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.1 ).

You wrote your old system was an pve 2.3?! The roadmap say that since version the cpu is KVM64 as default CPU type (previously qemu64) .
Perhaps you should test the old one?!

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