Cairxoxo Posted March 11, 2019 Share Posted March 11, 2019 (edited) Hi everyone, I can no longer start any VMs at all, they state "Execution Error: internal error: qemu unexpectedly closed the monitor: qemu: qemu_thread_create: Resource temporarily unavailable" when trying to start them. The VM service says it's running in the unRAID GUI, but the LibVirt log shows:: 2019-03-11 02:35:56.032+0000: 9697: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer 2019-03-11 02:35:56.032+0000: 9697: error : qemuProcessReportLogError:1928 : internal error: qemu unexpectedly closed the monitor: qemu: qemu_thread_create: Resource temporarily unavailable The VM itself that won't start has this in the log: 2019-03-11 02:35:55.841+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Hass.io,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-Hass.io/master-key.aes -machine pc-q35-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/5b510e31-5996-7354-07db-bd67fcb0c307_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=off -smp 24,sockets=1,cores=12,threads=2 -uuid 5b510e31-5996-7354-07db-bd67fcb0c307 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=25,server,nowait -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=0io-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -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.3,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-03-11 02:35:55.841+0000: Domain id=3 is tainted: high-privileges 2019-03-11 02:35:55.841+0000: Domain id=3 is tainted: host-cpu 2019-03-11T02:35:55.945615Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) qemu: qemu_thread_create: Resource temporarily unavailable 2019-03-11 02:35:56.033+0000: shutting down, reason=failed I've tried rebooting multiple times, each time the VM will come up just fine with the service, then both will crash and stay that way after a period of time. Edited June 28, 2020 by Cairxoxo Quote Link to comment
Cairxoxo Posted March 11, 2019 Author Share Posted March 11, 2019 Diagnostics here tower-diagnostics-20190311-1354.zip Quote Link to comment
bennymundz Posted March 11, 2019 Share Posted March 11, 2019 I had a similar issue. It looks that some dockers were causing a headache for me. If you want to give it a try, I'd recommend deleting all your docker and associated configs then trying to run your VM's and see how it goes. Be sure to make any necessary config backups of your docker, before you delete them and their configs. 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.