From: Russell Morris <1921061@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1921061] Re: Corsair iCUE Install Fails, qemu VM Reboots
Date: Wed, 05 May 2021 23:54:30 -0000 [thread overview]
Message-ID: <162025887104.6829.16291903507440576488.malone@wampee.canonical.com> (raw)
In-Reply-To: 161654808841.23607.13822796780403513821.malonedeb@chaenomeles.canonical.com
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 QEMU.
https://bugs.launchpad.net/bugs/1921061
Title:
Corsair iCUE Install Fails, qemu VM Reboots
Status in QEMU:
New
Bug description:
Hi,
I had this working before, but in the latest version of QEMU (built
from master), when I try to install Corsair iCUE, and it gets to the
driver install point => my Windows 10 VM just reboots! I would be
happy to capture logs, but ... what logs exist for an uncontrolled
reboot? Thinking they are lost in the reboot :-(.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1921061/+subscriptions
next prev parent reply other threads:[~2021-05-06 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 1:08 [Bug 1921061] [NEW] Corsair iCUE Install Fails, qemu VM Reboots Russell Morris
2021-04-18 22:16 ` [Bug 1921061] " Russell Morris
2021-05-05 23:54 ` Russell Morris [this message]
2021-05-14 19:13 ` Thomas Huth
2021-05-14 21:26 ` Russell Morris
2021-05-15 14:05 ` Thomas Huth
2021-06-09 18:53 ` John Snow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162025887104.6829.16291903507440576488.malone@wampee.canonical.com \
--to=1921061@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.