Windows boot issues

T

TB12

New Member
Aug 2, 2011
10
0
1
Hey guys,


I'm having some problems getting Windows to work with KVM.


When I try to boot from the DVD to install any Windows OS, the virtual monitor screen simply freezes on "Booting from DVD/CD... 2857MB medium detected".


The virtual CPU also seems to hover around 96% usage. I'm completely stumped as to why it's doing this. It's a fresh install of Debian/Proxmox with updated packages. There are no errors from what I can see.


root@ns61535:~# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1dso1


As I've said, any Windows DVD I try does this. I pulled the Windows Server 2008 R2 Trial DVD directly from Microsoft and that gave the exact same problem so I know it's not the ISO that's the issue. All ISO's also work just fine when booted locally.


Any ideas?
 
You installation seems to be incomplete (package pve-qemu-kvm is missing).

We have a 'virtual' package which depends on all needed packages, so
the following should fix your issues:


# aptitude update
# aptitude safe-upgrade
# aptitude install proxmox-ve-2.6.32

(see http://pve.proxmox.com/wiki/Proxmox_VE_Kernel)

Does that help?
 
Hm, doesn't seem to have resolved it.

root@ns61535:~# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1dso1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

Any other ideas?
 
I actually wasn't even able to upload through the gui, never really looked into that one.

Basically my DVD images were getting corrupt during transfer between servers (both using FTP and SFTP/ssh). No idea why, but after comparing identical md5's, everything seems to be working fine now.

Moral of the story, do an md5 or similar.
 
You must log in or register to reply here.
Top Bottom