Problem during Debian upgrade

mel128

Member
May 9, 2011
77
0
6
Hello,

I'm facing a weird problem.

We have some Proxmox VE servers but not in any cluster.

Today, I did a Debian upgrade. Only Debian packages, we have already the 2.3.13 everywhere.

One the first server, I closed each VM ( only KVM ), did the Debian upgrade ( aptitude full-upgrade ) and reboot the physical server. I started each VM without issue.

On the second one physical server, I did the same ... but I'm unable to launch any VM ! On the left side of the web interface, I see the VM as launched, on the task windows, I've a timeout error and the SSH service of the physical server is down but ping is up. Of course, the VM did not reply on the network.

Where can I look to have more information to solve that issue without reinstalling the physical server ?

Hopefully, VM run on another physical server right now :)

Thank for your help.

Michel
 
The full error message is :

TASK ERROR: start failed: command '/usr/bin/kvm -id 155 -chardev 'socket,id=qmp,path=/var/run/qemu-server/155.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/155.vnc,x509,password -pidfile /var/run/qemu-server/155.pid -daemonize -name NAME_OF_THE_VM -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -k en-us -m 1024 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/155/vm-155-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100'' failed: got timeout


NAME_OF_THE_VM is, of course, the real name of the VM :D
 
post the output of:

Code:
pveversion -v

qm config 155
 
Hello Tom, thank for your reply.

Here are the outputs

# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-19-pve: 2.6.32-96
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-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1

# qm config 155
bootdisk: ide0
cores: 1
ide0: local:155/vm-155-disk-1.raw,size=32G
ide2: none,media=cdrom,size=673068K
memory: 1024
name: NAME_OF_THE_VM
net0: rtl8139=BE:9C:FC:E6:9A:4F,bridge=vmbr1
net1: rtl8139=8A:12:FD:45:37:5C,bridge=vmbr1
ostype: l26
sockets: 1

Of course, NAME_OF_THE_VM replaces the real name of the VM. ;)

Michel
 
The full error message is :

TASK ERROR: start failed: command '/usr/bin/kvm -id 155 -chardev 'socket,id=qmp,path=/var/run/qemu-server/155.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/155.vnc,x509,password -pidfile /var/run/qemu-server/155.pid -daemonize -name NAME_OF_THE_VM -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -k en-us -m 1024 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/155/vm-155-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100'' failed: got timeout


NAME_OF_THE_VM is, of course, the real name of the VM :D

Maybe can you try to execute the full command line manually, sometime you can have more informations. (just strip the ' characters)
 
Hello sprit,

Maybe can you try to execute the full command line manually, sometime you can have more informations. (just strip the ' characters)

I've almost the same message !

# qm start 155
start failed: command '/usr/bin/kvm -id 155 -chardev 'socket,id=qmp,path=/var/run/qemu-server/155.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/155.vnc,x509,password -pidfile /var/run/qemu-server/155.pid -daemonize -name NAME_OF_THE_VM -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -k en-us -m 1024 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/155/vm-155-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap155i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=BE:9C:FC:E6:9A:4F,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=tap,id=net1,ifname=tap155i1,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=8A:12:FD:45:37:5C,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301'' failed: got timeout



Michel
 
Last edited:
Hello everybody,

We've reinstalled the physical server. All is fine after that.

Thank for your help.

Michel
 

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!

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!