Status: internal-error ?

C

chrbar

Guest
Hello,

I'm a newcomer with Proxmox.

I've installed "Proxmox VE 2 64 bits" on a "Debian Squeeze 64 bits" server.
I create different VM, and when I start them, I obtain "internal-error" as "Status"!
Do you think that is a hardware problem ou another problem (as Proxmox installation or settings)?

I've tried with different types of hardware settings (among the CPU, disk and network choices offer by the VM), I've tried different guest OS too.

If I create a CT with the Template "debian-6.0-standard_6.0-4_i386.tar.gz", this CT runs correctly.

Could you help me :)

Thanks a lot,
Chris
 
and post your 'pveversion -v'
 
Thanks for your help :)

Here my 'pveversion -v':
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-10-pve: 2.6.32-63
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.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1

I've checked and saw nothing special inside the logs (but I'm not a linux expert!).

I copie below the logs which appears in "/var/log/syslog" when I start a VM (and stop it 1 ou 2 mn after the "internal-error" appears):
Sep 8 19:14:54 xx-00000 pvedaemon[6853]: <root@pam> successful auth for user 'root@pam'
Sep 8 19:15:21 xx-00000 pvedaemon[6853]: <root@pam> starting task UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam:
Sep 8 19:15:21 xx-00000 pvedaemon[18173]: start VM 100: UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam:
Sep 8 19:15:21 xx-00000 pvedaemon[6853]: <root@pam> end task UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam: OK
Sep 8 19:17:01 xx-00000 /USR/SBIN/CRON[18212]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 8 19:17:59 xx-00000 pvedaemon[6387]: <root@pam> starting task UPID:sd-27060:00004734:0065368B:504B7DC7:qmstop:100:root@pam:
Sep 8 19:17:59 xx-00000 pvedaemon[18228]: stop VM 100: UPID:sd-27060:00004734:0065368B:504B7DC7:qmstop:100:root@pam:
Sep 8 19:18:00 xx-00000 pvedaemon[6387]: <root@pam> end task UPID:sd-27060:00004734:0065368B:504B7DC7:qmstop:100:root@pam: OK
Sep 8 19:18:47 xx-00000 pvedaemon[1422]: worker 6387 finished
Sep 8 19:18:47 xx-00000 pvedaemon[1422]: starting 1 worker(s)
Sep 8 19:18:47 xx-00000 pvedaemon[1422]: worker 18246 started

Same with logs from "/var/log/apache2/error.log":
[Sat Sep 08 19:14:47 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:14:48 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:14:48 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:14:48 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:06 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:32 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:32 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:37 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:42 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:48 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:15:49 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:17:43 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:17:45 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:21:29 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:21:30 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico
[Sat Sep 08 19:21:30 2012] [error] [client xx.xx.xx.xx] File does not exist: /usr/share/pve-manager/images/favicon.ico

I would be surprised that the problem comes from the "favicon.ico" file?

I've posted some printscreens from my VM, if you want to check it:
https://picasaweb.google.com/lh/sre...1121&authkey=Gv1sRgCLWNsqLptPOL-wE&feat=email

Thanks a lot for your help :)
 
Hi dietmar... I've sent log informations below, by replying to tom.
Thanks :)
 
Last edited by a moderator:
Oupsss I thought my Reply (to tom) need to be validated by Moderator, but I saw that this reply was posted directly... it's possible that I've canceled my reply to tom instead of send it :(
I'll rewrite my reply to tom soon...
 
Hello,

Someone told me that the problem comes from IP Failover: there is not IP Failover set to virtual MAC address?
I didn't set any IP Failover for my VM.
Does VM need an IP Failover to be able to run?

I though IP Failover was needed if you want to run your server directly on the Web.
But I thought we don't need IP Failover settings if you just want to run VM via the Proxmox console.

Could you confirm to me I need to set an IP Failover to be able to run a VM?

Thanks for your help,
Chris
 
chrbar said:
...

I've checked and saw nothing special inside the logs (but I'm not a linux expert!).

I copie below the logs which appears in "/var/log/syslog" when I start a VM (and stop it 1 ou 2 mn after the "internal-error" appears):
Sep 8 19:14:54 xx-00000 pvedaemon[6853]: <root@pam> successful auth for user 'root@pam'
Sep 8 19:15:21 xx-00000 pvedaemon[6853]: <root@pam> starting task UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam:
Sep 8 19:15:21 xx-00000 pvedaemon[18173]: start VM 100: UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam:
Sep 8 19:15:21 xx-00000 pvedaemon[6853]: <root@pam> end task UPID:sd-27060:000046FD:0064F8B8:504B7D29:qmstart:100:root@pam: OK
...
Click to expand...
Hi,
any error if you start the VM on the console with
Code: 
qm start 100
Udo
 
Was this ever resolved? I have the same "internal-error"

/var/log/syslog
Code: 
Mar 17 10:54:45 proxmox pvedaemon[2787]: <root@pam> starting task UPID:proxmox:00000B6B:0004CE1F:5145D935:qmstart:101:root@pam:
Mar 17 10:54:45 proxmox kernel: device tap101i0 entered promiscuous mode
Mar 17 10:54:45 proxmox kernel: vmbr0: port 4(tap101i0) entering forwarding state
Mar 17 10:54:46 proxmox pvedaemon[2787]: <root@pam> end task UPID:proxmox:00000B6B:0004CE1F:5145D935:qmstart:101:root@pam: OK
Mar 17 10:54:48 proxmox pvedaemon[2805]: <root@pam> successful auth for user 'root@pam'
Mar 17 10:54:48 proxmox pvedaemon[2944]: starting vnc proxy UPID:proxmox:00000B80:0004CF3A:5145D938:vncproxy:101:root@pam:
Mar 17 10:54:48 proxmox pvedaemon[2775]: <root@pam> starting task UPID:proxmox:00000B80:0004CF3A:5145D938:vncproxy:101:root@pam:
Mar 17 10:54:55 proxmox pvedaemon[2805]: <root@pam> successful auth for user 'root@pam'
Mar 17 10:54:56 proxmox kernel: tap101i0: no IPv6 routers present

Code: 
root@proxmox:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1

root@proxmox:~# cat /etc/pve/qemu-server/101.conf
Code: 
boot: dcn
bootdisk: sata0
cores: 2
ide2: local:iso/Hiren's.BootCD.15.2.iso,media=cdrom,size=609268K
memory: 1024
name: Windows7
net0: e1000=06:DA:A2:DF:E1:82,bridge=vmbr0
ostype: win7
sata0: local:101/vm-101-disk-1.raw,size=16G
sockets: 1

I'm starting the machine from Hiren's BootCD, and selecting the "Mini Windows XP option". As soon as I do that, the state changes from "running" to "internal-error" as below screenshots.

2013-03-17--1363532108_1050x179_scrot.png
2013-03-17--1363532124_1054x176_scrot.png

Curious about 'boot: dcn'? What is that?
 
Were any of these resolved? I'm getting the exact same issue with ubuntu 13 server and desktop
 
I am having similar problems with new Ubuntu and Windows 2012 R2 too. What I actually do is to change the Video to Standard VGA, this helps a little. But not for mavarics, after 2nd reboot i get the Kernel backtrace. I think there is some issue with the emulated BIOS..
 
I had same problem and my solution of fixing it was to disable KVM hardware virtualization. (Options > KVM hardware virtualization > No)
Hope it will be helpful.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back