[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Remaining problem could be with SeaBIOS. Copying here my question to
OFTC #virt
Doing some GRUB bios-mode boot testing with qemu/x86_64. Attached 2 IDE
devices, a small HDD (file with mbr and 2 partitions) and a CDROM (iso
file). If SeaBIOS boots the CD GRUB can see both devices ("(cd) (hd0)")
After reserching the NFS lock issue it seems I found the solution on the
Debian 11 Bullseye server:
$ sudo systemctl enable rpc-statd
Created symlink /etc/systemd/system/nfs-server.service.wants/rpc-statd.service
→ /lib/systemd/system/rpc-statd.service.
$ sudo systemctl start rpc-statd
Now, the
One issue is that when the libvirt cache mode is set to "none" what is
passed to qemu is "write-cache=on". If I set libvirt cache mode to
"writethrough" qemu gets "write-cache=off" !
The remaining problem is solving the lock issue on NFS. Came back to
this issue again today and its again blocked
Hi TJ,
> Ubuntu 20.04 amd64. Originally thought this was virt-manager but tested via
> virsh and found it
> appears to be caused by libvirt.
Yes this issue isn't a virt-manager issue, but libvirt (or qemu) should
be right.
All the "Failed to lock byte" issues go back to 2017.
There qemu
** Attachment added: "Screenshot from virt-manager"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+attachment/5535410/+files/Screenshot_2021-10-23_11-17-02.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
