> On the apparmor issue, is this the "right" fix? I modified 
> /etc/apparmor.d/abstractions/libvirt-qemu, adding,
> /usr/local/bin/qemu-system-x86_64 rmix,
> /usr/local/share/qemu/** r,
>
> Or is there a "better" (correct) way?

Doing the same in /etc/apparmor.d/local/abstractions/libvirt-qemu is
better to now get conflicts on upgrades.

> As for Windows/Linux vs. macOS guests, I don't think they are usign the same 
> UEFI (are they?).
> I did reboot the Windows guest, and it looks to be a different "BIOS", agreed?
> Checking the xml configuration files, they are a bit different (macOS copied 
> below, Windows does not include this). So is it (specifically?) UEFI vs. QEMU 
> (i.e. that is the issue)?
> <loader readonly="yes" type="pflash">OVMF_CODE.fd</loader>
> <nvram>OVMF_VARS.fd</nvram>

The above section belongs to using OVMF and if the windows guest
didn't have that it probably runs on seabios or some other non UEFI
path.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906155

Title:
  USB Passthrough Fails on Start, Needs domain Reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to