bclinton Posted January 19, 2022 Share Posted January 19, 2022 Hi friends. I had 2 existing VM's Windows 10 and Macinabox that were working fine. I haven't used them for months. I recently was trying to install an Ubuntu server VM which I have done so in the past with no issues. No matter what settings I used it would not work, so I tried to run my windows 10 and Macinbox VM's and they too would not work. Looking at the log files for all 3 VM's they end with the same entry that the log below has (qxl_send_events: spice-server bug: guest stopped, ignoring). I have updated to 6.10RC2 since the last time I used VM's...not sure if that is related. I am now unable to add any VM's as I continue to get the same error in the log file. Just looking for something to try. I have rebooted the server and deleted the libvert.img file which deleted my 2 existing VM's. LOG -smp 2,sockets=1,dies=1,cores=1,threads=2 \ -uuid f8fe7cd9-363a-83bb-5c25-481cd180cd51 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Ubuntu/vdisk1.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device virtio-blk-pci,bus=pci.3,addr=0x0,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/ubuntu-20.04.3-live-server-amd64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,drive=libvirt-1-format,id=sata0-0-0,bootindex=2 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:87:42:04,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev id=audio1,driver=none \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring Quote Link to comment
Squid Posted January 19, 2022 Share Posted January 19, 2022 Post the diagnostics after trying to start the various VMs 1 Quote Link to comment
bclinton Posted January 19, 2022 Author Share Posted January 19, 2022 30 minutes ago, Squid said: Post the diagnostics after trying to start the various VMs Thanks for helping me. Here is the log. unraid-syslog-20220119-2246.zip Quote Link to comment
Squid Posted January 19, 2022 Share Posted January 19, 2022 Post the entire zip file 1 Quote Link to comment
bclinton Posted January 19, 2022 Author Share Posted January 19, 2022 3 minutes ago, Squid said: Post the entire zip file unraid-diagnostics-20220119-1656.zip Quote Link to comment
bclinton Posted January 20, 2022 Author Share Posted January 20, 2022 21 hours ago, Squid said: Post the entire zip file Update. This morning I did a shutdown on the server rather than a reboot. Figured I would try the VM setup again. This time it started normal. Not sure what or why I was having problems before, but my guess is the shutdown seems to have resolved it. Before I would simply restart the server. Thanks again for helping with this. It is much appreciated. Quote Link to comment
ALERT Posted January 23, 2022 Share Posted January 23, 2022 i have the same issue trying to create Ubuntu Desktop LTS on Unraid 6.10.0-rc3i alert-server-diagnostics-20220123-1248.zip Quote Link to comment
Squid Posted January 23, 2022 Share Posted January 23, 2022 9 minutes ago, ALERT said: 6.10.0-rc3i Number one, you shouldn't be running private internal test releases, and what does "same issue" actually mean? What are you seeing when trying to create a VM? Quote Link to comment
ALERT Posted January 23, 2022 Share Posted January 23, 2022 Yeah, it seems version switch jumped from Next to Test, and I just clicked update on the popped up top OS Update notification. My log has the same last two lines. I found this topic via google using the last line. VNC doesn't connect, nothing happens next. VM cannot be shut down, only forced to shut down. HOME=/var/lib/libvirt/qemu/domain-3-Ubuntu \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-Ubuntu/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-Ubuntu/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-Ubuntu/.config \ /usr/local/sbin/qemu \ -name guest=Ubuntu,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Ubuntu/master-key.aes"}' \ -machine pc-q35-6.2,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 10,sockets=1,dies=1,cores=5,threads=2 \ -uuid d6b4463d-9f37-edb9-3ef8-8d809654e776 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=38,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ -device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ -device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Ubuntu/vdisk1.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-2-format","id":"virtio-disk2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/ubuntu-20.04.3-desktop-amd64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":2}' \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/ubuntu/ \ -device '{"driver":"virtio-9p-pci","id":"fs0","fsdev":"fsdev-fs0","mount_tag":"unraid","bus":"pci.1","addr":"0x0"}' \ -netdev tap,fd=40,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:4f:ed:9f","bus":"pci.2","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0"}' \ -chardev socket,id=charchannel0,fd=41,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:1,websocket=5701,password=on,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"max_outputs":1,"bus":"pcie.0","addr":"0x1"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.5","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/1 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring Quote Link to comment
Squid Posted January 23, 2022 Share Posted January 23, 2022 The spice server thing seems to be harmless (happens also on my VMs). Once you force stop the vm and try to restart it does any error pop up? Do all the paths (to the vdisks, etc) all exist? Quote Link to comment
ALERT Posted January 23, 2022 Share Posted January 23, 2022 Once I force stop the vm and start it again — it starts successfuly, but the log is the same, no errors on UI, and nothing happens after the log. Tried waiting for an hour. All the paths exist. ISO exists, vdisk is present and was created by the VM. Tried deleting the VM and starting anew. Tried shutting down the server and starting it again. No results. Quote Link to comment
ALERT Posted February 1, 2022 Share Posted February 1, 2022 I might have found the cause! So my Unraid is with HTTPS turned OFF. But my Nginx Proxy Manager has a subdomain with letsncrypt dns challenge for my duckdns that redirects https://unraid.mydoimain.duckdns.org to the HTTP port of my Unraid. Aaaand... VNC doesn't work if I use the local non-secure Unraid URL, but it connects successfuly if I use the secure duckdns subdomain over NPM to the HTTP Unraid port. This doesn't work: http://192.168.1.3/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=192.168.1.3&port=&path=/wsproxy/5701/ This works: https://unraid.mydomain.duckdns.org/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=unraid.mydomain.duckdns.org&port=&path=/wsproxy/5701/ (the link is not real) I have deleted the OS image again and the Ubuntu is loading! Quote Link to comment
flying Posted February 21, 2023 Share Posted February 21, 2023 On 2/1/2022 at 10:40 PM, ALERT said: 我可能找到了原因! 所以我的Unraid关闭了HTTPS。但是我的 Nginx 代理管理器有一个子域,其中包含我的 duckdns 的 letsncrypt dns 挑战,它将 https://unraid.mydoimain.duckdns.org 重定向到我的 Unraid 的 HTTP 端口。 啊...如果我使用本地非安全的 Unraid URL,VNC 不起作用,但如果我通过 NPM 使用安全的 duckdns 子域到 HTTP Unraid 端口,它会成功连接。 这不起作用: http://192.168.1.3/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=192.168.1.3&port=&path=/wsproxy/5701/ 这有效:https://unraid.mydomain.duckdns.org/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=unraid.mydomain.duckdns.org&port=&path=/wsproxy/5701/(链接不是真实的) 我再次删除了操作系统映像,并且 Ubuntu 是装载! Have you solved the problem? How can I use the Nginx Proxy Manager proxy, http://192.168.1.3/ **Can also work Quote Link to comment
ALERT Posted February 21, 2023 Share Posted February 21, 2023 3 hours ago, flying said: Have you solved the problem? How can I use the Nginx Proxy Manager proxy, http://192.168.1.3/ **Can also work I did not do anything specific. I used my duckdns URL to connect to VNC. But now it seems that it just works normally with the local IP connection. You can always put a custom VNC port to the VM settings and connect using a VNC client using the Unraid IP and this port. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.