Hi Russel, this bug has been migrated to the new GitLab issue tracker;
can you provide me with some extra information over on the new tracker,
please?
(I am *very* likely to miss updates here.)
1. What is your QEMU command line? (A full, working command-line, but the
smallest one you can reprodu
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/320
** Changed in: qemu
Status: Confirmed => Expired
** Bug
** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1921061
Title:
Corsair iCUE Install Fails, qemu VM Reboots
Status in QEMU:
Confirmed
Bug
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
FYI, to provide an update - I found a workaround! It's related to the
CPU selection. I can't seem to pass through my host CPU, even with
v6.0.0 of qemu. Rather, I have to use the qemu64 CPU.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to Q
Hi,
Slight update - as I decided to passthru my NIC as well => driver
install there also causes a VM (Windows 10) reboot. Seems all driver
installs fail?
Running on the latest master, QEMU emulator version 5.2.93 (v6.0.0-rc3).
Thanks!
--
You received this bug notification because you are a mem
