This is really wierd, I'm having an issue creating a windows machine.
I have a bunch of old ProxMox servers (1.8) running, and a few of the newer machines running (2.0).
I created a windows machine on the 1.8 server, it worked fine. Migrated it to one of our production (2.0) machines and it didn't work at all, bios comes up and then when it goes to boot from the hard drive it just hangs.
So I tried creating a windows machine on one of our development (2.0) boxes, it worked fine. Migrated it to our production (2.0) machines and the same thing happened, bios comes up, goes to boot from hard drive and just hangs... forever..
So just for grins, I tried creating a windows machine ON our production machine (thinking it may be something with migration), and I get the same thing... Bios, hang...
Oh, and by the way, when I say BIOS and then HANG... I mean, I've actually completed the installation of windows, it reboots, boots into windows to do it's configuration thing, reboots, and then hangs... So it is actually booting off the hard drive at one point, it's just that after it "configures your desktop environment" or whatever, it never boots again. And this seems to only affect our production machines, but I'm not sure why...
Has anyone ever seen this before? Any ideas where to even start?
svr01:~# pveversion -v
pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1
I have a bunch of old ProxMox servers (1.8) running, and a few of the newer machines running (2.0).
I created a windows machine on the 1.8 server, it worked fine. Migrated it to one of our production (2.0) machines and it didn't work at all, bios comes up and then when it goes to boot from the hard drive it just hangs.
So I tried creating a windows machine on one of our development (2.0) boxes, it worked fine. Migrated it to our production (2.0) machines and the same thing happened, bios comes up, goes to boot from hard drive and just hangs... forever..
So just for grins, I tried creating a windows machine ON our production machine (thinking it may be something with migration), and I get the same thing... Bios, hang...
Oh, and by the way, when I say BIOS and then HANG... I mean, I've actually completed the installation of windows, it reboots, boots into windows to do it's configuration thing, reboots, and then hangs... So it is actually booting off the hard drive at one point, it's just that after it "configures your desktop environment" or whatever, it never boots again. And this seems to only affect our production machines, but I'm not sure why...
Has anyone ever seen this before? Any ideas where to even start?
svr01:~# pveversion -v
pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1
Last edited: