problem after update - pvestatd look for control socket

[fandert]

Maybe using rdp, or ssh?

Network isn't responding to ping/rdp/ssh etc.

 

[dietmar]

OK, will try to find a fix.

 

[fandert]

OK, will try to find a fix.

anything i can do to help?

i know, this won't help, but it's a bit urgent

 

[tom]

kill the KVM process from this VM?

 

[fandert]

kill the KVM process from this VM?

tried that, too, still the same.

Aug 16 15:33:42 imp02 pvedaemon[40998]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 15:33:43 imp02 pvedaemon[48551]: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 2
Aug 16 15:33:43 imp02 pvedaemon[40924]: <root@pam> end task UPID:imp02:0000BDA7:001E52D9:502CF6B6:vncproxy:101:root@pam: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 2

 

[tom]

if you killed the VM, you cannot connect anymore. are you sure the kill was successful? if the VM is down, you should be able to start it again - what so you get if you type 'qm start 101'?

 

[fandert]

if you killed the VM, you cannot connect anymore. are you sure the kill was successful? if the VM is down, you should be able to start it again - what so you get if you type 'qm start 101'?

root@imp02 ~ # qm start 101
VM 101 already running

root@imp02 ~ # qm stop 101
unable to connect to VM 101 socket - Resource temporarily unavailable
VM quit/powerdown failed - terminating now with SIGTERM

root@imp02 ~ # qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
101 mx02 stopped 4096 0.00 0

root@imp02 ~ # qm start 101
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name mx02.fandert-eservices.de -smp 'sockets=2,cores=2' -nodefaults -boot 'menu=on' -vga std -rtc-td-hack -no-kvm-pit-reinjection -no-hpet -localtime -k de -drive 'file=/var/lib/vz/images/images/101/vm-101-disk-2.raw,if=none,id=drive-ide1,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1' -drive 'file=/var/lib/vz/images/images/101/vm-101-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=201' -drive 'if=none,id=drive-ide3,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=1,drive=drive-ide3,id=ide3,bootindex=100' -drive 'file=/var/lib/vz/images/images/101/vm-101-disk-4.raw,if=none,id=drive-ide2,aio=native,cache=none' -device 'ide-hd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2' -m 4096 -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:0E:9F:B7:4A:64,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -cpuunits 1000 -no-hpet -no-kvm-pit-reinjection' failed: got timeout

 

[tom]

root@imp02 ~ # qm start 101
VM 101 already running

so the 'kill' was not successful. are you familiar with kill?

you need to find the PID (process ID) with ps, then enter:

> kill -9 PID

 

[fandert]

so the 'kill' was not successful. are you familiar with kill?

you need to find the PID (process ID) with ps, then enter:

> kill -9 PID

i am familiar with the kill-command. i killed the vm with this command, but it's still the same error(s).

 

[tom]

If you kill a VM KVM process successfully you cannot get "already running" if you start it again, this is impossible.

 

[fandert]

If you kill a VM KVM process successfully you cannot get "already running" if you start it again, this is impossible.

ok, i killed the process with kill -9 PID, then started the VM again and then copied the text above, but i still have the same issues with these two Windows-VMs.

 

[dietmar]

ok, i killed the process with kill -9 PID, then started the VM again and then copied the text above, but i still have the same issues with these two Windows-VMs.

Please can you post your vm config (that looks like a different issue now)

Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.

 

[fandert]

Please can you post your vm config (that looks like a different issue now)

Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.

args: -no-hpet -no-kvm-pit-reinjection
boot: dcn
bootdisk: ide0
cores: 2
ide0: images:101/vm-101-disk-1.raw
ide1: images:101/vm-101-disk-2.raw
ide2: images:101/vm-101-disk-4.raw
ide3: none,media=cdrom
localtime: 1
memory: 4096
name: mx02
net0: rtl8139=C6:0E:9F:B7:4A:64,bridge=vmbr0
onboot: 1
ostype: win7
sockets: 2

i updated on monday and rebooted this morning after a change of the keyboard-map to german, between the update and this morning it was ok.

 

[fandert]

OMG, it was the no-kvm-pit-reinjection argument. i removed it and now the server is booting.

Thank you for this thought!!

 

[___jul]

OMG, it was the no-kvm-pit-reinjection argument. i removed it and now the server is booting.

Thank you for this thought!!

Hello,

Sorry but what is the no-kvm-pit-reinjection argument ?

I have the same problem after last upgrade 2 days ago

pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-73
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-14-pve: 2.6.32-73
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-30
vncterm: 1.0-2
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

Just stop the Windows, reboot and pray ?

 

[tom]

post your VMID.conf.

 

[___jul]

post your VMID.conf.

I got 2

Aug 19 09:00:10 xxx pvestatd[1007940]: WARNING: unable to connect to VM 106 socket - No such file or directory
Aug 19 09:00:10 xxx pvestatd[1007940]: WARNING: unable to connect to VM 105 socket - No such file or directory
Aug 19 09:00:20 xxx pvestatd[1007940]: WARNING: unable to connect to VM 106 socket - No such file or directory
Aug 19 09:00:20 xxx pvestatd[1007940]: WARNING: unable to connect to VM 105 socket - No such file or directory



xxx:/etc/pve/qemu-server# cat 105.conf
bootdisk: ide0
cores: 1
ide0: local:105/vm-105-disk-1.raw
ide1: local:105/vm-105-disk-2.raw
ide2: cdrom,media=cdrom
memory: 4048
name: NewXP
net0: rtl8139=E2:0B:13:61:0B:00,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
xxx:/etc/pve/qemu-server# cat 106.conf
bootdisk: ide0
cores: 1
ide0: local:106/vm-106-disk-1.qcow2
ide1: local:106/vm-106-disk-2.raw
ide2: local:iso/Hiren's.BootCD.15.1.iso,media=cdrom
lock: backup
memory: 4096
name: Win2003-Clone
net0: rtl8139=DA8:10:C9:C9:B0,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 2

thank you

 

[dietmar]

thank you

First, pleas update to latest available packages. After that, you need to shutdown, then restart those VMs.

 

[___jul]

First, pleas update to latest available packages. After that, you need to shutdown, then restart those VMs.

Ok I've updated everything, shutdown each VM and reboot the server.
Everything seems good now.
Thank you.