Thanks for testing James. But that's different from what I'm seeing.
True full reproducer for me:
Host: Fedora 35
git clone https://github.com/virt-manager/virt-manager
cd virt-manager
wget
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-disk-kvm.img
# change image roo
The reporter of the virt-install bug also found this expired focal
cloud-images bug which sounds like the same root issue:
https://bugs.launchpad.net/cloud-images/+bug/1940791
If someone with more launchpad knowledge can route this report to the
correct place, please do. Would be nice to get this
If you are using latest pygobject, like 3.13.4 or later, you are
probably hitting this:
https://bugzilla.gnome.org/show_bug.cgi?id=735090
https://bugzilla.redhat.com/show_bug.cgi?id=1130758
** Bug watch added: GNOME Bug Tracker #735090
https://bugzilla.gnome.org/show_bug.cgi?id=735090
** Bug
Anthony, upstream virt-manager doesn't change the cache default, though
we do in RHEL.
Wasn't the idea of having an adaptive cache default for qemu given the
okay on qemu-devel, particularly for cache=none for block devs? or am I
imagining things (could be the case since I can't seem to find the
t
I filed an upstream libvirt bug for the dd block size issue:
https://bugzilla.redhat.com/show_bug.cgi?id=599091
** Bug watch added: Red Hat Bugzilla #599091
https://bugzilla.redhat.com/show_bug.cgi?id=599091
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this
