Windows 2008 R2 VM migrated from ESXi 5.1 just will not boot!

[effgee]

Hi there, having a huge issue with 2008 R2 server.
Migrating from ESXi, exactly the same hardware.
I'm just moving the disk image into a new Proxmox VM and trying to get into windows to redetect hardware.

To start with, anytime I put a 64 bit cpu, it bluescreens before getting to desktop with an 0x0000005D error.
I managed to get around that by putting either kvm32, or qemu32 for the processor, but after "Windows is loading files.. " but before it gets to desktop, it reboots itself and goes back to bios.


Things I've tried

• Changing the cpu from any of the 64 bit capable definitions to the two availiable 32 bit definitions, (*Ninja edit: and disabling KVM hardware virtualization) this stops the 0x0000005D error but does not allow me to get into the desktop. (Boot loop) I find this strange since 2008 R2 requires a 64 bit capable processor. \
• Also, the "host" definition for cpu is missing in PVE3.
• Changed the storage adapter, I have tried virtio, scsi and ide.
• Installed all updates from pve-test as of tonight and tried as many settings to see if I could get the right combo. No luck.
• Downloaded and booted from this http://www.microsoft.com/en-us/download/details.aspx?id=38435 to see if the recent MS updates are what was causing the issue. Strangely enough to get this iso to boot I had to reconfigure the cpu to a 64 capable one. Had no effect.

Since I have tested so many things the vm config doesn't really reflect current settings, but at this point I've pretty much tried everything

Any help is appreciated.

Machine Config

bootdisk: scsi0
cores: 2
cpu: kvm32
ide2: local:iso/KB2840165-Win7-RTM-SP1-X86.iso,media=cdrom,size=225766K
kvm: 0
memory: 2048
name: toad
net0: e1000=0A:C7:0D:06:8C:0B,bridge=vmbr0
ostype: win7
scsi0: local:103/vm-103-disk-1.qcow2,format=qcow2,cache=writeback,size=41G
sockets: 1
vga: std

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-22-pve: 2.6.32-107
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-25
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-9
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

root@proxmox:/etc/pve/qemu-server# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core  CPU      E6700  @ 3.20GHz
stepping        : 10
cpu MHz         : 3205.412
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
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 lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl                                                                                                                          vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dts tpr_shadow vnmi flexpriority
bogomips        : 6410.82
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:


processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core  CPU      E6700  @ 3.20GHz
stepping        : 10
cpu MHz         : 3205.412
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
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 lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl                                                                                                                          vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dts tpr_shadow vnmi flexpriority
bogomips        : 6410.82
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

 

[m.ardito]

Hi there, having a huge issue with 2008 R2 server.
...
I've pretty much tried everything

maybe you just skipped the most useful resource... searching forums?

http://forum.proxmox.com/threads/14727-Blu-screen-installing-windows-server-2008?highlight=sep



Marco

 

[effgee]

Hi,

I've actually gone through every thread, tip and trick already.
Nothing has worked, at the moment I'm inclined to think it has to do with the disk image being a dynamic partion and / or corruption.

maybe you just skipped the most useful resource... searching forums?

http://forum.proxmox.com/threads/14727-Blu-screen-installing-windows-server-2008?highlight=sep



Marco

 

[snowman66]

Also, the "host" definition for cpu is missing in PVE3.

This is strange. What if you create completely new VM and check if "host" option is available?

or directly edit VM config file:
/etc/pve/qemu-server/VMID.conf.

cpu: host

 

[m.ardito]

so, the

"args: -cpu kvm64,+sep" trick didn't work?

Marco

 

[effgee]

Done that, get an error about not a valid cpu definition.

This is strange. What if you create completely new VM and check if "host" option is available?

or directly edit VM config file:
/etc/pve/qemu-server/VMID.conf.

cpu: host

 

[effgee]

Nope, after a few minutes staring at a black screen I get internal-error on the status window.
I can start the install process from iso with those settings, but am trying to access my already configured server environment.
No idea whats happening.

I would even do a in place upgrade except I have to be able to boot into windows to do that. Who from MS thought that was a good idea.

 

[effgee]

SOLVED

After adding another disk to the system, installing a side copy of Windows Server 2008 R2 and adding boot entries for both disks, I finally was able to see a bit more of what was going on..
Installing the second windows allowed me to press F8 during bootup so I could actually see why the damn thing was rebooting. I was getting a Stop 0x0000007B error. A little google fu later, and discovered this thread.

http://social.technet.microsoft.com...8-r2-bare-metal-restore-0x0000007b-stop-error

I used the last technique and it seems to have worked perfectly.

If in doubt, turn on all possible required services e.g. set both intelide = 0/pciide = 0 and msahci = 0, or set all of these to 0 and it will still boot with the correct driver/s:
aliide, amdide, atapi, cmdide, iastorv, intelide, msahci, pciide, viaide and LSI_SAS.

Hope this helps someone.