>From the dmesg above:
[ 573.935889] Oops: [#1] PREEMPT SMP PTI
[ 573.935892] CPU: 0 PID: 7 Comm: kworker/u2:0 Not tainted 5.11.11-arch1-1 #1
[ 573.935896] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
ArchLinux 1.14.0-1 04/01/2014
[ 573.935899] Workqueue: events_unbound co
-cpu host -smp 4 makes the hang/freeze go away.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924914
Title:
Running sway in a QEMU VM results in a GPU hang of the guest (virtio-
gpu driver)
Sta
I can't reproduce it with weston.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924914
Title:
Running sway in a QEMU VM results in a GPU hang of the guest (virtio-
gpu driver)
Status in QEMU:
I can't get it to happen with -vga qxl.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924914
Title:
Running sway in a QEMU VM results in a GPU hang of the guest (virtio-
gpu driver)
Status in Q
Public bug reported:
System is Arch Linux (guest and host OS).
Problem:
Basically, when using sway on a guest and running certain applications
via Xwayland (on the guest), the GUI will freeze and won't be usable
anymore, I can still ssh to the guest and run commands.
This is the command I use t
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.1 no longer says anything about inaccessible devices
Status in QEMU:
I no longer need this (it's no longer an issue for me), feel free to
reopen if this issue affects you.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bu
On Sat, Dec 12, 2020 at 1:28 PM Diego Viola wrote:
>
> Hi,
>
> I'm experiencing a lot of choppiness in the video output when I pass
> through my USB webcam to the guest using qemu-xhci as follows:
>
> qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -vga vir
On Sun, Dec 13, 2020 at 4:30 PM Diego Viola wrote:
>
> Not sure it's related but I'm seeing this on the guest now when I use
> mpv --vo=drm on a tty:
mpv --vo=drm /dev/video0
trb-start 00012a8c7d70 trb-end 00012a8c7d70
seg-start 00012a8c7000 seg-end 00012a8c7ff0
Video is then a bit smoother.
Diego
On Sat, Dec 12, 2020 at 1:28 PM Diego Viola wrote:
>
> Hi,
>
> I'm experiencing a lot of choppiness in the video output when I pass
> through my USB
Hi,
I'm experiencing a lot of choppiness in the video output when I pass
through my USB webcam to the guest using qemu-xhci as follows:
qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -vga virtio
-device qemu-xhci,id=xhci -device
usb-host,bus=xhci.0,hostdevice=/dev/bus/usb/002/004
My w
This bug is now fixed with Linux 5.9-rc5, thank you.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Status in QEMU:
ndeed, thanks Gerd!
Tested-by: Diego Viola
>
> HTH,
> Gerd
>
Diego
Hi,
I'm trying to use the new usb-host hostdevice property that was added here:
https://git.qemu.org/?p=qemu.git;a=commit;h=9f815e83e983d247a3cd67579d2d9c1765adc644
This is the command line that I am using:
qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -device
qemu-xhci,id=xhci -dev
that.
v2: use drm_atomic_crtc_needs_modeset() (Daniel).
Cc: 1882...@bugs.launchpad.net
Fixes: 3954ff10e06e ("drm/virtio: skip set_scanout if framebuffer didn't
change")
Signed-off-by: Gerd Hoffmann
Tested-by: Jiri Slaby
Tested-by: Diego Viola
---
drivers/gpu/drm/virtio/virtgpu_display.c
I was changing the /dev file permissions based on the output from above,
that's why I decided to submit this bug report.
Either way, the output from lsusb works too.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
Not sure this is a bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.1 no longer says anything about inaccessible devices
Status in QEMU:
New
Bug description:
Previousl
The previous commit is fine, it displays the USB errors:
libusb: error [_get_usbfs_fd] libusb couldn't open USB device
/dev/bus/usb/002/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.
libusb: error [_get_usbfs_fd] libusb couldn't open USB dev
My system is Arch Linux.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.1 no longer says anything about inaccessible devices
Status in QEMU:
New
Bug description:
Previous
** Attachment added: "bisect-log.txt"
https://bugs.launchpad.net/qemu/+bug/1892581/+attachment/5403655/+files/bisect-log.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.
Public bug reported:
Previously, with QEMU 5.0.0 running a VM with the following command:
$ qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -device usb-
ehci,id=ehci -device usb-
host,bus=ehci.0,vendorid=0x04f2,productid=0xb449 -device intel-hda
-device hda-duplex -vga virtio
Would dis
Will the patch make it for 5.8?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Status in QEMU:
New
Bug description
Yeah, I can reproduce the same exact behavior outside of QEMU with sway
and it's consistent to what I observed in QEMU.
> Hmm, happens with xorg only.
I think you were right all along about this, sorry.
Thanks for fixing this bug, feel free to close this bug as fixed.
--
You received this bug
It looks like sway requires swayidle to wake up from sleep[1].
This works:
swayidle timeout 2 'swaymsg "output * dpms off"' resume 'swaymsg "output
* dpms on"'
1. https://github.com/swaywm/sway/issues/2914
** Bug watch added: github.com/swaywm/sway/issues #2914
https://github.com/swaywm/sway
Sway log after the crash.
** Attachment added: "swaylog.txt"
https://bugs.launchpad.net/qemu/+bug/1882851/+attachment/5383276/+files/swaylog.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882
Gerd, thanks. I can confirm your patch fixes the problem with X, but
Wayland (sway) is still affected.
I tested X and wayland, and while the "Guest disabled display" no longer
hangs on X, it still does hangs under wayland.
Should I bisect again?
--
You received this bug notification because you
I just sanity checked, and can confirm the bad commit causes it, and
going back one commit makes it work.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest
** Attachment added: "bisectlog.txt"
https://bugs.launchpad.net/qemu/+bug/1882851/+attachment/5383160/+files/bisectlog.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU vide
OK, I was able to bisect, here is the result:
[diego@arch-zoom linux]$ git bisect bad
3954ff10e06e4fbc548fc02ff1fcaaac3228fed5 is the first bad commit
commit 3954ff10e06e4fbc548fc02ff1fcaaac3228fed5
Author: Gerd Hoffmann
Date: Thu Dec 12 13:53:44 2019 +0100
drm/virtio: skip set_scanout if
I can reproduce it with current linux git master[1].
1. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video fre
Gerd: I tried the LTS kernel on Arch Linux (5.4.46-1-lts) and I can't
reproduce the bug with this kernel.
It works as expected: `xset dpms force off' triggers the "Guest disabled
display" and it disappears after moving the mouse.
Could it be a regression in virtio_gpu?
I guess I'll try the lates
> Hmm, happens with xorg only.
Nope, I can reproduce it with sway as well (which is another Wayland
compositor).
To reproduce it with sway, just do: swaymsg "output * dpms off" and then
should you see "Guest disabled display", at that point I'm unable to get
back image.
I tried the sendkey ctrl-
I can't wake up the screen after hitting keys or moving the mouse after
turning off the screen with sway.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest
`xset dpms force off' on the guest is a good way to reproduce it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Stat
My bad, the workaround works, it's just a bit tricky.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Status in QEMU:
Strange, that workaround doesn't work anymore.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Status in QEMU:
New
OK, I found a workaround: sendkey ctrl-alt-f1 from the QEMU console
(ctrl alt 2) then I can switch back to X and continue from where I left
off.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Public bug reported:
I am using Arch Linux as my Guest and Host OS, after starting qemu with
the following command:
$ qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -vga
virtio
and waiting for a screen blank, I get this message:
Guest disabled display
And nothing happens after t
Switching the resolution with -vga std was working fine before, I'm not
sure on which version it started having this issue, but it should be on
a recent version.
I use the intel i915 drivers on the host OS.
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Public bug reported:
I am currently using QEMU on a Arch Linux host, the guest OS is also
Arch Linux.
The QEMU version is currently 2.12.0-2 packaged by Arch Linux, the
command line I'm using to fire an Arch VM is:
$ qemu-system-x86_64 -enable-kvm -hda archlinux.qcow2 -m 4G -smp 4
The problem I
Hi Francisco, thanks for your quick reply.
I've tried `xrandr --output Virtual-1 --mode 1360x768' with -vga std and
I also get a corrupted image.
I'm attaching a screenshot of what the screen corruption looks like
after changing the resolution.
Thanks.
** Attachment added: "qemu.png"
https:
41 matches
Mail list logo
