Windows 2008 Server internal-error

[rubylaser]

Hello, I have just setup a new Proxmox 3.0 server.

pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
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-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

I am trying to restore a backup from our old Proxmox 2.3 Server of a Windows 2008 Server. When I start it up I get internal-error as the status. I have checked the syslog and this is the extent of the info in there.

Jul 19 07:49:47 proxmox pvedaemon[634715]: start VM 111: UPID:proxmox:0009AF5B:005B2660:51E927DB:qmstart:111:root@pam:
Jul 19 07:49:47 proxmox pvedaemon[625801]: <root@pam> starting task UPID:proxmox:0009AF5B:005B2660:51E927DB:qmstart:111:root@pam:
Jul 19 07:49:48 proxmox kernel: device tap111i0 entered promiscuous mode
Jul 19 07:49:48 proxmox kernel: vmbr0: port 7(tap111i0) entering forwarding state
Jul 19 07:49:48 proxmox pvedaemon[625801]: <root@pam> end task UPID:proxmox:0009AF5B:005B2660:51E927DB:qmstart:111:root@pam: OK
Jul 19 07:49:51 proxmox pvedaemon[634810]: starting vnc proxy UPID:proxmox:0009AFBA:005B27AB:51E927DF:vncproxy:111:root@pam:
Jul 19 07:49:51 proxmox pvedaemon[607414]: <root@pam> starting task UPID:proxmox:0009AFBA:005B27AB:51E927DF:vncproxy:111:root@pam:
Jul 19 07:49:51 proxmox ntpd[2257]: Listen normally on 21 tap111i0 fe80::7098:f1ff:fe21:c4af UDP 123
Jul 19 07:49:58 proxmox kernel: tap111i0: no IPv6 routers present
Jul 19 07:50:01 proxmox pvedaemon[634810]: command '/bin/nc -l -p 5902 -w 10 -c '/usr/sbin/qm vncproxy 111 2>/dev/null'' failed: exit code 1
Jul 19 07:50:01 proxmox pvedaemon[607414]: <root@pam> end task UPID:proxmox:0009AFBA:005B27AB:51E927DF:vncproxy:111:root@pam: command '/bin/nc -l -p 5902 -w 10 -c '/usr/sbin/qm vncproxy 111 2>/dev/null'' failed: exit code 1

This shows up in the Proxmox Server Syslog page.

Jul 19 08:17:31 proxmox pvedaemon[658153]: start VM 111: UPID:proxmox:000A0AE9:005DB04C:51E92E5B:qmstart:111:root@pam:
Jul  19 08:17:31 proxmox pvedaemon[654652]: <root@pam> starting task  UPID:proxmox:000A0AE9:005DB04C:51E92E5B:qmstart:111:root@pam:
Jul 19 08:17:32 proxmox kernel: device tap111i0 entered promiscuous mode
Jul 19 08:17:32 proxmox kernel: vmbr0: port 7(tap111i0) entering forwarding state
Jul  19 08:17:32 proxmox pvedaemon[654652]: <root@pam> end task  UPID:proxmox:000A0AE9:005DB04C:51E92E5B:qmstart:111:root@pam: OK
Jul 19 08:17:34 proxmox ntpd[2257]: Listen normally on 22 tap111i0 fe80::acfe:22ff:fe51:a1e9 UDP 123
Jul 19 08:17:34 proxmox ntpd[2257]: peers refreshed
Jul 19 08:17:42 proxmox kernel: tap111i0: no IPv6 routers present

Here is my conf file for the vm.

#172.16.190.153
boot: dcn
bootdisk: ide0
cores: 1
ide0: local:111/vm-111-disk-1.raw,format=raw,size=52G
ide2: none,media=cdrom
memory: 2304
name: windows2008
net0: e1000=72:20:AC:08:F5:F1,bridge=vmbr0
onboot: 1
ostype: w2k8
sockets: 2

Any help is greatly appreciated. Thank you.

 

[rubylaser]

I just tried to do a fresh Windows 7 64bit SP1 install to test the box. The install went well and was working for a while. I did the Windows updates, and went to restart, and now I have the same internal-error message in Proxmox. Afterwards, I just updated to the latest updates, but I'm still having the same problems. It appears to be an issue only with Windows VMs? Any ideas? I've used Proxmox literally for years, and have never seen an issue like this.

root@proxmox:~# pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
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-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
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

 

[tom]

Your configs looks ok so far. I am not aware of such an issue. Can you test on another server hardware?

 

[rubylaser]

Thanks for the reply. My Proxmox cluster at the datacenter is all in production, so I don't want to upgrade that until I rule out any potential issue, but I do have a few Q9550 boxes at home that I can try it out on. I'm installing Windows 7 right now on one of them. I'll try to recreate the issue.