XenServer 6.2 to Proxmox migration -- windows, black screen

O

Offf256

Renowned Member
Feb 18, 2014
20
7
68
So, i have the latest Proxmox 3.1-21
I'm trying to migrate some Windows boxes fromXenserver 6.2 to Proxmox
Following the wiki and some other sources
If I use xe-export I end up with unreadable image
If I use ovf export I can convert vhd images to qcow2 or raw
those images are mountable and I can see files on them
If I attach them to VM and try to start VM I get black screen (sometimes w. non blinking cursor)
I installed VmWare Converter exported VMWare machine
this machine starts and boots fine on VMware WS
Convert slices to one big vmdk (-t 2) - this image also boots fine on VmWare WS
I can convert this image to qcow2
When I try to boot -- blank screen w. cursor
Boot from Win7 CD -- it finds the harddisk and says that boot needs to repair. Ok, repair.
Boot from hard disk -- still blank screen.
Boot again from CD -- now it does not complain about any errors any more.
I found some "black screen w. cursor" threads but those are about contianers.
So, what I am missing here? Any help is greatly appreciated.

A.
 
Some additional information
I checked and re-checekd the images (md5sum, mount)
I tried different display and cpu settings. No luck.
 
Offf256 said:
So, i have the latest Proxmox 3.1-21
Click to expand...
this is not latest... but could work to start

Offf256 said:
If I use ovf export I can convert vhd images to qcow2 or raw
Click to expand...
http://docs.openstack.org/image-guide/content/ch_converting.html

Offf256 said:
If I attach them to VM and try to start VM I get black screen (sometimes w. non blinking cursor)
Click to expand...
to be sure, boot the pve vm with a livecd and check the vm is seeing good disks...
[/QUOTE]

sorry for the rest, never used xen...

Marco
 
OK, already done that. I finally found some pieces of information by searching "internal error".
But these threads contain no answers also :(
When I disable "KVM hardware emulation" windows starts, but crashes soon afterwards w. BSOD 0x0000000005D -- unsupported processor.
I also tried to repair MBR (so the Windows should not be activated at the moment) but no good.
 
Code: 
egrep '(vmx|svm)' /proc/cpuinfo
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 lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow
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 lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow

Just in case rebooted the system and checked BIOS settings. Virtualization Technology was "enabled"
 
Last edited:
Installed from Proxmox ISO
Code: 
root@kvmhost01:~# uname -a
Linux kvmhost01 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux

Also kvm_intel module is loaded according to lsmod
Yes, the test machine is quite old core2duo 6600, but according to documentation it is supported.
 
Last edited:
Offf256 said:
Code: 
egrep '(vmx|svm)' /proc/cpuinfo
Just in case rebooted the system and checked BIOS settings. Virtualization Technology was "enabled"[/QUOTE]

then, try also to shutdown, remove power cord, wait 30 sec and then plug it back. It happened to me once, believe it or not.
this is really weird. 

which motherboard/cpu is pve running on?

Marco
Click to expand...
 
Just the same problem and options. Only diff in that when i disable KVM support - the machine boots well (but very slowly). I am trying my best magic with google for several hours and still have no decision.

I see the problem starts after the SeaBios POST - while trying to access HDD, - i see the F12 offer and then recieve internal error and blank black screen. I am wondering how i installed the W2008 with such problems? Because the problem appeared after the first Windows reboot.
I tried to boot up with IDE or VirtIO (separate installations) - but had no luck..


Also my CPU config:

root@server/ # egrep '(vmx|svm)' /proc/cpuinfo
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid


And the KVM:
/ # cat /etc/pve/local/qemu-server/107.conf
balloon: 8096
boot: cdn
bootdisk: virtio0
cores: 2
freeze: 1
ide2: local:iso/w2008x32.iso,media=cdrom,size=2884354K
keyboard: en-us
memory: 12288
name: W2008
net0: virtio=52:03:A9:0A:70:17,bridge=vmbr0
onboot: 1
ostype: win7
scsihw: virtio-scsi-pci
sockets: 2
tablet: 0
vga: std
virtio0: local:107/vm-107-disk-2.raw,format=raw,size=200G

Playing with CPU or ACPI or converting raw to qcow2 made no luck too

UPDATE:

I have found the reason of the problem. I used a pre-activated ISO that messed up with boot sector making ProxMox KVM confused. Fresh MSDN ISO install solved the problem - but it's rather strange that KVM cannot read boot sector correctly.
 
Last edited:
You must log in or register to reply here.
Top Bottom