Node shows no vm's, but vm's are running.
- Thread starter europrox
- Start date
I've seen something like this in the firefox browser - refreshing the browser shows the VMs.
The VMs show if you go to the node and run "qm list" ?
The VMs show if you go to the node and run "qm list" ?
Never seen that. How do you know they are running, can you see them running with "ps" or "ps -ef | grep qemu" or are you still using them?
Hi,
I know it still runs because I can connec tot the missing vm's with rdp or ssh.
result from ps-ef grep qemu
root 32060 1 15 2017 ? 10-09:18:19 /usr/bin/kvm -id 100 -chardev socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait -mon chardev=qmp,mode=control -pidfile /var/run/qemu-server/100.pid -daemonize -smbios type=1,uuid=19cc54e0-567c-46c5-8d83-a045764bbdc9 -name DC01 -smp 2,sockets=2,cores=1,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -vga std -vnc unix:/var/run/qemu-server/100.vnc,x509,password -no-hpet -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce -m 4096 -k en-us -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -chardev socket,path=/var/run/qemu-server/100.qga,server,nowait,id=qga0 -device virtio-serial,id=qga0,bus=pci.0,addr=0x8 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:316f3a90dea1 -drive file=/var/lib/vz/template/iso/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_English_-3_MLF_X21-30350.ISO,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.126.iso,if=none,id=drive-ide3,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=1,drive=drive-ide3,id=ide3,bootindex=201 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/dev/pve/vm-100-disk-1,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=BE:BC:87:0B:68:09,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discard
root 32154 19636 0 12:13 pts/0 00:00:00 grep qemu
"Different broswers has no result" vs "Switching from Firefox to Chrome did the trick"
Do the PVE developers only use chrome?
Do the PVE developers only use chrome?
i think those two users have/had two completely different problems (as europrox said also qm list was empty)
no we test also with firefox (esr & current) and edge on windows 10
I (quite frequently) have to refresh firefox because it has lost details in the "summary" or "hardware" of VMs. Just today, firefox lost a migrated container and thought it was on the old host and could not see it in its new place until refreshed.
It is probably due to running firefox through VNC or a slow home drive but refresh usually fixes it first try.
It is probably due to running firefox through VNC or a slow home drive but refresh usually fixes it first try.