status: internal-error on every windows 2008r2 install

[bleomycin]

Hello,

I'm running the latest stable release and cannot get windows 2008r2 64bit to work at all on proxmox. The installer runs fine, but after the first reboot, or maybe even several reboots later the VM will refuse to boot again, throwing "status: internel error" in proxmox. I've tried virtio HD + networking and regular IDE + e1000, makes no difference. The only "non-standard" thing i'm doing on this machine is passing through 1 NIC and 1 sata controller to 2 other VM's (1 linux 1 bsd). Hardware is E5530 xeon + supermicro X8DTL motherboard. Nothing shows up in syslog or apache error.log. Please let me know if there is any more information i can provide!

pveversion -v
pve-manager: 2.2-26 (pve-manager/2.2/c1614c8c)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-80
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-80
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-1
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-28
qemu-server: 2.0-64
pve-firmware: 1.0-21
libpve-common-perl: 1.0-37
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-34
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1

 

[dietmar]

The only "non-standard" thing i'm doing on this machine is passing through 1 NIC and 1 sata controller to 2 other VM's

How do you do that? Please can you port your VM config?

 

[bleomycin]

How do you do that? Please can you port your VM config?

Sure, this is my config to pass 1 nic to pfsense 32bit

bootdisk: ide0
cores: 1
hostpci0: 07:00.0
ide0: local:110/vm-110-disk-1.raw,size=5G
ide2: local:iso/pfSense_386.iso,media=cdrom,size=113124K
memory: 512
name: PfSense386
net0: e1000=2E:51:34:ED:E5:27,bridge=vmbr0
onboot: 1
ostype: other
sockets: 1

and to pass sata to ubuntu 12.04 64bit

bootdisk: virtio0
cores: 2
hostpci0: 00:1f.2
ide2: none,media=cdrom
memory: 4000
name: zfsbuntu
net0: virtio=96:71:24:8E:66:9E,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: local:101/zfsbuntu.qcow2

With the previous release i attempted to pass through more than 2 device, but that ended up with system crashes, i have not tried again on current release for fear of the same.

 

[udo]

Sure, this is my config to pass 1 nic to pfsense 32bit

bootdisk: ide0
cores: 1
hostpci0: 07:00.0
ide0: local:110/vm-110-disk-1.raw,size=5G
ide2: local:iso/pfSense_386.iso,media=cdrom,size=113124K
memory: 512
name: PfSense386
net0: e1000=2E:51:34:ED:E5:27,bridge=vmbr0
onboot: 1
ostype: other
sockets: 1

and to pass sata to ubuntu 12.04 64bit

bootdisk: virtio0
cores: 2
hostpci0: 00:1f.2
ide2: none,media=cdrom
memory: 4000
name: zfsbuntu
net0: virtio=96:71:24:8E:66:9E,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: local:101/zfsbuntu.qcow2

With the previous release i attempted to pass through more than 2 device, but that ended up with system crashes, i have not tried again on current release for fear of the same.

Hi,
and the "pass through" devices aren't in use by the host (e.g. no driver loaded)?

Udo

 

[bleomycin]

Hi,
and the "pass through" devices aren't in use by the host (e.g. no driver loaded)?

Udo

Well, I'm passing through 1 of two onboard intel nic's so the e1000e driver is loaded in the host. The other device is the onboard sata controller (ich10), i do not see that being loaded.

lsmodModule                  Size  Used by
vzethdev                8189  0 
vznetdev               19302  0 
pio_nfs                17467  0 
pio_direct             26583  0 
pfmt_raw                3152  0 
pfmt_ploop1             6003  0 
ploop                 114467  4 pio_nfs,pio_direct,pfmt_raw,pfmt_ploop1
simfs                   4480  0 
vzrst                 186395  0 
nf_nat                 23213  1 vzrst
nf_conntrack_ipv4       9978  2 nf_nat
nf_defrag_ipv4          1531  1 nf_conntrack_ipv4
vzcpt                 142405  1 vzrst
nfs                   414919  2 vzrst,vzcpt
lockd                  78223  2 vzrst,nfs
fscache                46811  1 nfs
nfs_acl                 2695  1 nfs
auth_rpcgss            44941  1 nfs
sunrpc                268688  6 pio_nfs,nfs,lockd,nfs_acl,auth_rpcgss
nf_conntrack           80698  4 vzrst,nf_nat,nf_conntrack_ipv4,vzcpt
vzdquota               55883  0 [permanent]
vzmon                  24553  3 vznetdev,vzrst,vzcpt
vzdev                   2765  4 vzethdev,vznetdev,vzdquota,vzmon
ip6t_REJECT             4743  0 
ip6table_mangle         3669  0 
ip6table_filter         3033  0 
ip6_tables             19746  2 ip6table_mangle,ip6table_filter
xt_length               1338  0 
xt_hl                   1547  0 
xt_tcpmss               1623  0 
xt_TCPMSS               3525  0 
iptable_mangle          3493  0 
iptable_filter          2937  0 
xt_multiport            2812  0 
xt_limit                2230  0 
xt_dscp                 2073  0 
ipt_REJECT              2399  0 
ip_tables              18183  2 iptable_mangle,iptable_filter
vhost_net              31368  2 
macvtap                 9964  1 vhost_net
macvlan                10260  1 macvtap
tun                    19189  7 vhost_net
kvm_intel              52954  15 
kvm                   318658  1 kvm_intel
vzevent                 2179  1 
ib_iser                31732  0 
rdma_cm                35285  1 ib_iser
ib_cm                  37046  1 rdma_cm
iw_cm                   8755  1 rdma_cm
ib_sa                  23110  2 rdma_cm,ib_cm
ib_mad                 40565  2 ib_cm,ib_sa
ib_core                74455  6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
ib_addr                 6139  1 rdma_cm
ipv6                  328547  172 vzrst,ip6t_REJECT,ip6table_mangle,ib_addr
iscsi_tcp              10263  0 
libiscsi_tcp           16972  1 iscsi_tcp
libiscsi               47665  3 ib_iser,iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi    53095  4 ib_iser,iscsi_tcp,libiscsi
fuse                   84682  3 
coretemp                7619  0 
snd_pcsp                8733  0 
snd_pcm                86292  1 snd_pcsp
snd_timer              23265  1 snd_pcm
i7core_edac            18168  0 
i2c_i801               11247  0 
ioatdma                58493  56 
i2c_core               31269  1 i2c_i801
snd                    71915  3 snd_pcsp,snd_pcm,snd_timer
tpm_tis                12257  0 
shpchp                 33498  0 
edac_core              46853  1 i7core_edac
dca                     7197  1 ioatdma
soundcore               8182  1 snd
tpm                    16486  1 tpm_tis
snd_page_alloc          8614  1 snd_pcm
serio_raw               4898  0 
tpm_bios                6375  1 tpm
ext3                  244847  3 
jbd                    81188  1 ext3
mbcache                 8160  1 ext3
usb_storage            49428  0 
ahci                   40865  0 
sata_sil                8939  2 
e1000e                261460  0

lsmod | grep ata
sata_sil                8939  2

lspci00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 22)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22)
00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22)
00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 22)
00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
08:01.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
08:04.0 RAID bus controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)

The two devices i am passing through have been rock solid for months on this machine, although it wouldn't surprise me at all if i'm doing something wrong unintentionally, i'm far from an expert on this

 

[bleomycin]

*bump*

Sorry to bump this, but has no one else encountered this? Google brings up a few other posts over the years on this board with others having the exact same problem but no resolution. It would appear this is an old problem that consistently fades into obscurity with people moving on to alternatives?

 

[bleomycin]

*bump*

Sorry to bump this, but has no one else encountered this? Google brings up a few other posts over the years on this board with others having the exact same problem but no resolution. It would appear this is an old problem that consistently fades into obscurity with people moving on to alternatives?

 

[marioh]

Hi, I had the same "internal-error" with the Win2k8R2 using proxmox 2.
I would like to point out that:
- Win2k8R2 installation ended with error: "Windows could not complete the installation. To install Windows on this computer, restart the installation" when Win2k8R2 installation is showing "Setup is preparing your computer for first use".
- Then, you reboot the guest and it does not boot again, even with CD/DVD.
I have tried with different types of virtual hard disk, 1 and 2 Gb RAM, but the result is the same.

 

[bleomycin]

Hi, I had the same "internal-error" with the Win2k8R2 using proxmox 2.
I would like to point out that:
- Win2k8R2 installation ended with error: "Windows could not complete the installation. To install Windows on this computer, restart the installation" when Win2k8R2 installation is showing "Setup is preparing your computer for first use".
- Then, you reboot the guest and it does not boot again, even with CD/DVD.
I have tried with different types of virtual hard disk, 1 and 2 Gb RAM, but the result is the same.

It seems like proxmox isn't ready for production when windows anything is involved. Stick with vmware.

 

[tom]

It seems like proxmox isn't ready for production when windows anything is involved. Stick with vmware.

no, windows should run without problem on KVM. we test all windows version in our test lab and it works great - i personally run and administer a lot of production servers on KVM. if there is a problem, something must be different on your side - hardware, settings or configuration.

 

[ejc317]

no, windows should run without problem on KVM. we test all windows version in our test lab and it works great - i personally run and administer a lot of production servers on KVM. if there is a problem, something must be different on your side - hardware, settings or configuration.

To the op - what are you storing it on? I can create a .raw image for you (blank .raw image with windows installed) and let you wget it off our server and you can see if you can mount it? One thing we ran into was corrupted windows .iso. They basically were not fully uploaded to Proxmox and will not install right. So we got 1 install right and just created an image.

We got that internal error every time as well running a busted iso. We downloaded the .iso off the Microsoft SPLA website and now all is good. We have 16 windows VMs running on virtio (we actually DD this image onto our SAN volumes and then change IPs) so we know it works. It's our way of "templating".

If you're interested we can give that a go - or happy to help you live if you need. I am not too familiar with your network setup though

 

[hotwired007]

It seems like proxmox isn't ready for production when windows anything is involved. Stick with vmware.

We're using Windows XP, 7, 2003, 2003 R2, 2008 and 2008 R2 and have been running windows 8 without any major issues with for over a year and a half (most issues are caused by the C2K interface and are resolved with a quick kick) - AFAIC Proxmox is production ready - so long as you set up your equipment correctly and test before making any changes.

I dont want to get into the VMWare vs Proxmox argument but - In my opinion comparing Proxmox over VMware the Pros for Proxmox far outway the cons.

 

[marioh]

Thank you tom, ejc317, and hotwired007 for your posts. We are running Proxomox 1.8 and 2.2-26 for production and it works very well (except W2k8R2 over Proxmox 2.2-26/c1614c8c).
If you could, please point us some hints, books, wikis, manuals and/or whaterver you may consider in order to achieve those (correct) "hardware, settings or configuration" (tom) and "set up your equipment correctly and test" (hotwired007). Thank you in advance.

 

[VitaminJ]

Hi, I had the same "internal-error" with the Win2k8R2 using proxmox 2.
I would like to point out that:
- Win2k8R2 installation ended with error: "Windows could not complete the installation. To install Windows on this computer, restart the installation" when Win2k8R2 installation is showing "Setup is preparing your computer for first use".
- Then, you reboot the guest and it does not boot again, even with CD/DVD.
I have tried with different types of virtual hard disk, 1 and 2 Gb RAM, but the result is the same.

Yes, I've experienced this same thing with restoring images to RAW virtual disks using Acronis, Symantec System Recovery, regardless of restore success or failure, I get the no boot thing even with .iso first in boot order. Will not boot until I disconnect the RAW disk or use dd to overwrite the first section of the disk (MBR, etc). The SeaBIOS seems to be ignoring boot order and inspecting the disk's MBR and getting hung on this even when the disk is second in boot order. This occured under PVE 2.2, unfortunately I never thought to look under the Status area in the web UI to see if it said "internal-error". I've since moved to PVE 2.3, unsure if the problem persists.

 

[bmontell]

Yes, I've experienced this same thing with restoring images to RAW virtual disks using Acronis, Symantec System Recovery, regardless of restore success or failure, I get the no boot thing even with .iso first in boot order. Will not boot until I disconnect the RAW disk or use dd to overwrite the first section of the disk (MBR, etc). The SeaBIOS seems to be ignoring boot order and inspecting the disk's MBR and getting hung on this even when the disk is second in boot order. This occured under PVE 2.2, unfortunately I never thought to look under the Status area in the web UI to see if it said "internal-error". I've since moved to PVE 2.3, unsure if the problem persists.

Currently I have the same problem, I tried 2.26 and 2.3 and persists, like a boot order problem such as comets which the problem is how to set the issue?

 

[Rushit]

Same thing happens here. I did a backup of a VM, recovered it on a different server, and I get the "internal-error" on the status display.

 

[stephenvr]

Just got this "internal-error" now on a Windows 2008 R2 VM. It's a test machine so isn't running all the time. I started it up, rebooted it and got this issue.


Here is my pveversion info.

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
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
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-7
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
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
root@proxmox:~#

 

[bmontell]

What I have noticed is that this error happens if I try to apply some windows activator, it messes with the system operating system boot and that is where it stops working virtual machine

 

[cosmos]

What I have noticed is that this error happens if I try to apply some windows activator, it messes with the system operating system boot and that is where it stops working virtual machine

On spot, I had this test machine running Windows 7 32-bit, on a latest proxmox. The host hardware is nothing special, I was mainly evaluating proxmox usage. Everything was fine, till the moment I tried to use a windows activator on the VM. Bang, that was it.

Any idea on how to recover it? I can install a true license, I'd like to avoid the burden to reinstall from scratch.

Plus, shouldn't proxmox be transparent to any activation bypassing technology?