** 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
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
Public bug reported:
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 re
OK, found my issue! :-). Still a bit odd, but virt-manager complaints about the
custom QEMU executable => but virsh still works. So I did get the VM running,
with,
QEMU emulator version 5.1.93 (v5.2.0-rc3)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
But it still perfo
My apologies, but I'm somewhat stuck here :-(. Trying to run the latest
(upstream) version of QEMU, but no luck getting it to execute. I even tried
setting securit_driver = "none", as captured here,
https://gitlab.com/apparmor/apparmor/-/wikis/Libvirt
But no luck. Open to any suggestions.
Thank
Sorry for the delay on updating this - but pulling my hair out (and I'm
short enough of that already ... LOL). I can't get Ubuntu to let me run
the custom qemu executable. Really is looking like apparmor. Fighting
with that, but struggling to have it let me run it :-(.
Thanks.
--
You received th
That makes sense, no issue at all. So I cloned from git (v5.2.0-rc3),
built, installed. All good so far :-). But then I tried to modify the
"emulator" in virt-manager, point to this build => I get the error,
Error changing VM configuration: internal error: Failed to start QEMU
binary /usr/local/bi
Sure, will do (upstream version). Is there a preferred way to do it?
Meaning ... build locally, or install from some repository?
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1906156
Title:
Public bug reported:
Hi,
Finding this one a bit odd, but I am loading a driver (kext) in a macOS
guest ... and it works, on the first VM (domain) startup after a full /
clean host OS boot (or reboot). However, if I even reboot the guest OS,
then the driver load fails => can be "corrected" by a fu
Public bug reported:
Hi,
I am seeing (consistently = always), USB Passthrough for my Logitech
Keyboard and Mouse ... they don't work / no response on domain (VM)
startup. After a reset of the VM they then work - but why are they
"dead" on initial startup of the VM? Is this a known issue?
Running
Hi,
Seeing this same thing! And I'm on Ubuntu 20.10, so pretty current :-).
vt82c686b-usb-uhci doesn't seem to be accessible any more, but trying
qemu-xhci => no joy, still have to reset the VM after each startup, to
get the keyboard and mouse working.
Is this expected?
Thanks!
--
You received
Hi,
I built against the latest library I could (Windows Insider Preview,
SDK) - same failure.
Thoughts?
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821595
Title:
Failed to emulate MMI
Should say - I rebuilt (today). Still no joy.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821595
Title:
Failed to emulate MMIO access with EmulatorReturnStatus: 2
Status in QEMU:
New
Bug des
Sorry, not quite following your comment - but it's likely me :-(.
I assume you mean QEMU - but build against what upstream library? I ask
because for QEMU to build, only the three header files from Windows are
copied over, and then it calls / uses the dll's (libraries) in Windows
itself ... right?
Folks seem to think this is the fix,
https://stackoverflow.com/questions/55197032/android-emulator-whpx-failed-to-emulate-mmio-access-exit-code-3
But it's not working for me ... does it help you?
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
And here,
https://www.reddit.com/r/androiddev/comments/c7u6h2/android_virtual_device_on_ryzen/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821595
Title:
Failed to emulate MMIO access with Emulat
Hi,
I tried backing up ... nothing but startup and UEFI (i.e. no OS, just
get to the EFI Shell). Can't even get there ... does that make sense?
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/
NP, will do. Thanks again for the help!
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1871250
Title:
Failed to create HAX VM
Status in QEMU
That makes sense, thanks!
Do we leave this open until that "hits" (gets pulled in), or close it
out? I'm fine with either, whatever you prefer.
Appreciate all the help!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
Awesome - thanks! I admit, not sure how you see the queue, but if you
say it's there, I trust you :-).
Any sort of LE?
Thanks again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1871250
Title:
F
No worries! And my apologies for some confusion too - I was trying
v4.2.0 from the official (recent) downloads, and I think something
wasn't quite right ... so I went back, manually built a clean v4.2.0. It
worked, as you suspected.
Good news is - seems we know the fix. Fast, and quite minor ... d
Hi,
I received an email yesterday (content below) - and it worked! Not sure
why it's not here also (and why only via email), but let me share, hope
this helps! And BTW, when I say worked ... I applied this to the latest
master (locally), addreses the issue. So add this in to the master
(formally)?
BTW, it does make the guest unusable ... can't even enter a password (if
I could get that far, having issues even running setup).
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1871267
Title:
Public bug reported:
Hi,
I am finding this issue with v4.2.0, or the latest master - on a Windows
host, with macOS guest. It happens using gtk (SPICE?) or VNC. When I get
to a place to enter a keystroke, I quite reliably get multiple of the
same key (i.e. press A, get ).
Thinking there may b
Public bug reported:
Hi,
I'm running the latest (master) of QEMU, though the version doesn't seem
to matter - I also checked back to v4.2.0, exactly the same issue. And
this isn't about the VM (guest), if I even just try to run,
> "c:\Program Files\qemu\qemu-system-x86_64.exe" -accel hax
Basica
FYI, I was curious if this was a Ryzen issue or not (which I am running), so I
tried another machine - here are the two combos I tried,
1) Ryzen 5 2600X, Windows 19041.172
2) Core i5-6600K, Windows 18363.720
Same issue on both.
Thanks!
--
You received this bug notification because you are a me
Hi,
Having a similar issue here, running "QEMU emulator version 4.2.91
(v5.0.0-rc1-31-g146aa0f104-dirty)"
Configuration / build command line,
./configure --cross-prefix=x86_64-w64-mingw32- --target-list=x86_64-softmmu
--enable-whpx --enable-fdt --enable-gtk --enable-vnc --disable-pie
--enable-o
Thanks for the pointer! Yep, same here - if I --disable-pie, rebuild and
try again => now no crash, at least checking --version ;-).
Will continue testing here, report back if I see any other oddities.
Thanks again.
--
You received this bug notification because you are a member of qemu-
devel-m
Public bug reported:
Hi,
I an having no issues up to (and including) v5.0.0-rc0, but when I move
to rc1 ... it won't even execute in Windows. If I just try to, for
example, run
qemu-system-x86_64.exe --version
No output, it just exits. This seems to be new with this version.
Thanks!
** Affect
Hi,
Thanks for the pointer! I tried this, but I get an error message, as follows ...
chardev: opening backent "stdio" failed
qemu: could not open serial device 'stdio': Inappropriate ioctl for device.
Thoughts?
Thanks again!
On Thu, Nov 11, 2010 11:22 AM, "David S. Ahern" wrote:
Hi,
Yes, I am in runlevel 5. I have to admit, I did check /etc/inittab, but I'm not
sure what I'm looking for ... :-(. A bit lost here as to what you're saying,
sorry! Can you clarify a bit?
Yes, VNC works - I was trying to say that, just not very clearly. What I'm
after though is to hav
32 matches
Mail list logo
