jkami

Sure, here they are kaminski-server-diagnostics-20241019-2250.zip

Diffent amounts on the different VMs, but even the one with the most amount of memory, 50gb of root storage and 4gb of RAM, is not able to boot with a share attached EDIT: And the host has 16gb of RAM

Hi Simon, thanks for the quick reply. I did select virtio-net for all the VMs. Just to make sure, I tried the inverse as well and selected virtio on the newly created VM with the old image, with the same result.

Hi everyone, I tried adding a unriad user share to existing VMs to put backups there. However, no matter the mode (9p or virtiofs) or share location, both VMs i tried crash to the UEFI shell on startup and show a 'mapping table' message. Once I remove the share share, everything boots fine again. Both VMs are running Ubuntu one 20.x.x LTS, the other 22.x.x LTS. However I have a third VM running Ubuntu 22.x.x LTS as well, where I use a user share which I added when setting up the VM in the first place, running fine and booting fine when restarting. What might be the issue here? I added the VMs log, in hope there might be something in there. EDIT: Ok it gets weirder. I thought I might be able to fix this by creating a new VM and use the old drive image. Now the system is booting with the share attached and I can mount it, but it won't connect to br0. Once I remove the share from the new VM it connects to br0 again! Thanks for any help! log.txt