KVM restart problem

[Stephane]

Hi,

I meet a problem on my server, after a reboot, my KVM machine wan't no more boot.

I check the log and the error I see is:

pvedaemon[20239]: starting VM 104 on node 0 (localhost)
Jan 24 18:11:49 xxxxxx qm[20240]: VM 104 start
Jan 24 18:11:49 xxxxxx kernel: device vmtab104i0 entered promiscuous mode
Jan 24 18:11:49 xxxxxx kernel: audit(1232817109.292:8): dev=vmtab104i0 prom=256 old_prom=0 auid=4294967295
Jan 24 18:11:49 xxxxxx kernel: vmbr0: port 1(vmtab104i0) entering learning state
Jan 24 18:11:49 xxxxxx qm[20240]: VM 104 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/104.mon,server,nowait -vnc unix:/var/run/qemu-server/104.vnc,password -pidfile /var/run/qemu-server/104.pid -daemonize -usbdevice tablet -name Solipsis -smp 1 -id 104 -cpuunits 1000 -boot cd -vga cirrus -tdf -localtime -k fr -drive file=/var/lib/vz/images/104/vm-104-disk.qcow2,if=ide,index=0,boot=on -drive file=/var/lib/vz/template/iso/fr_Windows_Server_2003_Enterprise.iso,if=ide,index=2,media=cdrom -m 1536 -net tap,vlan=0,ifname=vmtab104i0,script=/var/lib/qemu-server/bridge-vlan0 -net nic,vlan=0,model=rtl8139,macaddr=8E:BD:72:6E:76:14' failed with exit code 1 at /usr/share/perl5/PVE/QemuServer.pm line 295.
Jan 24 18:11:49 xxxxxx pvedaemon[20239]: VM 104 start failed -
Jan 24 18:11:49 xxxxxx kernel: vmbr0: port 1(vmtab104i0) entering disabled state
Jan 24 18:11:49 xxxxxx kernel: vmbr0: port 1(vmtab104i0) entering disabled state

pveversion
pve-manager/1.1/3675

Nothing more, very strange...

Linux xxxxxx 2.6.24-proxmox #1 SMP Mon Sep 8 12:08:54 CEST 2008 x86_64 GNU/Linux

Thank you.

 

[tom]

Linux xxxxxx  2.6.24-proxmox #1 SMP Mon Sep 8 12:08:54 CEST 2008 x86_64 GNU/Linux

This is not a Proxmox VE Kernel - where do you get this? OVH? if yes, ask them for help - looks their customization is not compatible.?

the latest Proxmox VE Kernel:

uname -a

2.6.24-2-pve #1 SMP PREEMPT Wed Jan 14 11:32:49 CET 2009 x86_64 GNU/Linux

If you run 'pveversion -v' you should get:

pve-manager: 1.1-2 (pve-manager/1.1/3675)
qemu-server: 1.0-7
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

 

[Stephane]

pveversion -v
pve-manager: 1.1-2 (pve-manager/1.1/3675)
qemu-server: 1.0-7
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

Hi and thank you for your answer.

In fact, early, I install the Proxmox-OVH release but I would not wait anymore a hypothetical update so I upgrade my system from your repositery instead of OVH's one.

All work right after few reboot but not in this case.

So, OVH support can't help me...

 

[tom]

pveversion -v
pve-manager: 1.1-2 (pve-manager/1.1/3675)
qemu-server: 1.0-7
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

Hi and thank you for your answer.

In fact, early, I install the Proxmox-OVH release but I would not wait anymore a hypothetical update so I upgrade my system from your repositery instead of OVH's one.

All work right after few reboot but not in this case.

So, OVH support can't help me...

So now you got all packages including Kernel from the Promox VE repo?
Pls post again what the problem is, include logs and error messages based on these updated system.

 

[Stephane]

The informations I gave you are the update ones because I do this update sinces the 1.0 release and the only ekementzs I didn't change is the kernel.

So, there is nothing more I can give you.

 

[dietmar]

So you have the wrong kernel.

 

[Stephane]

How I managed to restart many times without encountering any problems?

Thank you anyway.

Regards,

 

[dietmar]

I am confused. You wrote that your are not using the latest kernel:

the only ekementzs I didn't change is the kernel.

We can only support things we know. Obviously you are using a custom kernel?

- Dietmar