cybrnook

Love your plugin, thank you. Just wanted to see if you put anymore though into updating the styling now that 7 is at beta 4? Trivial for sure, but a small continual annoyance. Assuming it maybe fell off the radar.

Quick google looks like it may be complaining about the mei_me module, and you could potentially blacklist it. https://askubuntu.com/questions/419853/mei-me-unexpected-reset Unraid used to have the ability to append entries to the kernel boot parameters and you could do something like a modprobe.blacklist=mei_me (Please fact check all this). Blacklisting might be more graceful these days. Looks like it's the Intel Management Engine Interface. Perhaps even something you might be able to disable in the BIOS (or even upgrade to latest version via a BIOS update)?

Thanks for trying at least. Was trying to noodle a quicker way forward.

@SimonF I'm sure you already saw/know, but here is the MESA docu: https://docs.mesa3d.org/install.html You think this is something that could fit in a plugin?

Changed Status to Solved

I'm gonna mark this as "solved" at least for the time being with the virtio 2d work around. It's not perfect, but it keeps my Ubuntu systems up and that's the most important part. Thanks for staying on top of it @SimonF . Looking forward now to the acceleration.

Damn, that would be icing on the cake. As of now, almost 3 days uptime with virtio....

@SimonF VM still up and running, though I think I need to give it a little more time. With that said, the performance is really not that great, similar to Cirrus in that it seems like it's running 1 FPS. Is there a way we can test the virtio driver but also enable acceleration?

@SimonF testing now, will update. Fingers crossed. EDIT: So far both VM's are up and running with the edit. Now will let it bake a few days.

@SimonF VM crashed again with the increased vgamem. Not sure if this log from the VM is relevant, but it's all that's there. I am open to just chocking this up to a Ubuntu issue and try and pivot to another flavor to develop on (not preferred, but not outside the realm of possibility): 2024-10-05 06:57:17.755+0000: starting up libvirt version: 10.7.0, qemu version: 9.1.0, kernel: 6.6.52-Unraid, hostname: TheArk LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-2-OpenWrt Development' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-2-OpenWrt Development/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-2-OpenWrt Development/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-2-OpenWrt Development/.config' \ /usr/local/sbin/qemu \ -name 'guest=OpenWrt Development,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-OpenWrt Development/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/677144ea-83d5-f533-6b41-bb2ff7bf4fa2_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ -machine pc-i440fx-9.0,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,topoext=on,host-cache-info=on,l3-cache=off \ -m size=16777216k \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":17179869184}' \ -overcommit mem-lock=off \ -smp 4,sockets=1,dies=1,clusters=1,cores=2,threads=2 \ -uuid 677144ea-83d5-f533-6b41-bb2ff7bf4fa2 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=39,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-shutdown \ -boot strict=on \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pci.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pci.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pci.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pci.0","addr":"0x7.0x2"}' \ -device '{"driver":"ahci","id":"sata0","bus":"pci.0","addr":"0x3"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x4"}' \ -blockdev '{"driver":"file","filename":"/mnt/cache/isos/linuxmint-22-cinnamon-64bit.iso","node-name":"libvirt-2-storage","read-only":true}' \ -device '{"driver":"ide-cd","bus":"sata0.0","drive":"libvirt-2-storage","id":"sata0-0-0","bootindex":2}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/OpenWrt Development/vdisk1.qcow2","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap","cache":{"direct":false,"no-flush":false}}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":true,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/OpenWrt Development/vdisk1.S20241001195039qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap","cache":{"direct":false,"no-flush":false}}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}' \ -device '{"driver":"ide-hd","bus":"sata0.2","drive":"libvirt-1-format","id":"sata0-0-2","bootindex":1,"rotation_rate":1,"write-cache":"on","serial":"vdisk1"}' \ -netdev '{"type":"tap","fd":"40","id":"hostnet0"}' \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:20:a5:b4","bus":"pci.0","addr":"0x2"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=38,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":"spice"}' \ -spice port=5901,addr=0.0.0.0,disable-ticketing=on,seamless-migration=on \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x1e"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x5"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2024-10-05 06:57:17.755+0000: Domain id=2 is tainted: high-privileges char device redirected to /dev/pts/1 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2024-10-05T14:55:59.633591Z qemu-system-x86_64: warning: Spice: reds.cpp:2039:reds_handle_ticket: failed to decrypt RSA encrypted password 2024-10-05T14:55:59.633631Z qemu-system-x86_64: warning: Spice: error:02000084:rsa routines::data too large for modulus

ROFL, and so you did. I see that now 🙂 Obviously you're well aware then.

@SimonF for the clipboard error, yes agreed and I think I got an error/warning similar to that when I tried to make my first snap on a VM where I had clipboard functionality enabled (as I normally had done in the past, so didn't think much of it). The head scratcher I had was trying to decipher what the warning/error was telling me and equating it to having to disable the clipboard. That's where google came in handy. I didn't realize that warning was put in by you and not just a generic one being provided from the subsystem. This is that link I found that pointed me to the clipboard. Seems it was a known issue, but perhaps abandoned for a fix? https://gitlab.com/qemu-project/qemu/-/issues/1380 For the spacing, would be greatly appreciated at least for verbose folks like myself who run in debug mode 🙂

Side note, I modified manually the snapshots.db file for my EnGenius Fitcon VM as an example and removed the parenthesis as well as minimized my spacing to a single space in the "desc": and that brought the formatting back in. (Browser is Edge Chromium): Maybe something as simple as wrapping in ' ' instead of " " ? 🤷‍♂️

@SimonF In poking around with the crashing VM issue, I deleted a few VM's and made some new ones. I am on a full ZFS system, and all VM's have/had snapshots taken. 2 x VM's that I deleted and removed still have remnants in /etc/libvirt/qemu/snapshotdb: Is this expected and is it safe to manually delete them? Two of those folders no longer exist as a VM (so I assume the snap shots must be gone as well, right?). Another thing, I noticed weird spacing issues on the VM snapshot names. I used regular spaces and parenthesis and got lots of white space it looks like. And finally, while I have you 🙂 I'm sure you're already aware, but the ability to snapshot breaks if you enable clipboard functionality. I had previously found a bug report online for it somewhere, seems like someone picked it up and then it went silent.

Latest 6.6? We are on 6.8.12 now, are we moving back?