Ok, so it seems rpc-statd [1] allows the locks to happen. The other problem you describe seems unrelated to NFS and just a guest boot question right? I have not heard about the "only seeing HD" problem and therefore have no immediate "this is it", but to poke on this a bit cdroms (virtuals as well) can be in ejected and active state, could it be that if not booting of it that it starts inactive waiting for the OS to ask spinning it up?
Things to try could be: 1. try specifying the cdrom as fallback boot, you can list multiple => https://libvirt.org/formatdomain.html#bios-bootloader 2. Force it to be perma-present like try=closed removable=false or so virsh change-media came to mind, but I do not see where it could be useful here Was there a reply from #virt since your question there that would indicate something deeper in seabios? [1]: https://linux.die.net/man/8/rpc.statd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948525 Title: Alters Performance options > Cache mode causing start failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
