[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1843151
Title:
Regression:
Has this ever been fixed on the QEMU or Spice side?
Anyway, the QEMU project is currently considering to move 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 older bugs to "Incomplete" now.
If you stil
Hi James,
The change in QEMU in 4.1 is that it's using a newer spice interface; Freddy
is on our spice team and we chatted about whether to change QEMU but they
thought it best to fix Spice to be more tolerant; so I'm happy to go with that
recommendation.
--
You received this bug notificati
Yes, I first replicated the issue by removing "max_outputs=1", then
patched spice server, and the issue no longer happens.
QEMU 4.1.0 still changed something. If I understand correctly, it's now
in some circumstances saying there are 0 monitors, even though there's a
graphic card?
Fixing this in
James: Freedy proposed a fix for the bug I was looking at with a spice fix:
https://lists.freedesktop.org/archives/spice-devel/2019-September/050859.html
That's in the spice-server package.
If you can check that it also fixes your bug that would be great.
--
You received this bug notificatio
Sorry, my #8 was really long. All builds I've done were in clean
chroots, so starting from scratch with just git source, with no
interference from other builds. Also later in #8, I show that
--disable-glusterfs doesn't work because some part of the build looks
for the .so that was never built.
L
hmm, disable-glusterfs *should* work around that; sometimes it's worth
nuking the build directory and trying a fresh configure with these
things.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1843151
Bisection is not going well at all with this code base!
Before your last reply, I started, and the first between 4.0.0 and 4.1.0
is aae6500972 which fails compilation:
==
...
CC stubs/pci-host-piix.o
CC stubs/ram-block.o
CC stubs/ramfb.o
CC stubs/fw_cfg.o
CC
P.S. Looks like I can use --disable-docs to hopefully get around the
json parsing error, but that still doesn't help with the gluster error
or that something is still looking the .so given --disable-glusterfs.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
OK that's interesting - I've got another bug I've been following that's
also fixed by (b).
A bisect would still be interesting; but one place to start might be to try
before and after commit
be812c0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subs
a) spice 0.14.2. Also spice-gtk 0.37, and spice-protocol 0.14.0.
b) Swapping with "-device qxl-vga,max_outputs=1" does fix the problem.
Swapping with "-device qxl-vga" still has the bug.
c) Knowing b, would the bisect still help? If needed, sure, I will.
--
You received this bug notification
Hi James,
OK, thanks - some questions:
a) What version of spice-server have you got on your host?
b) Does swapping the '-vga qxl' for '-device qxl-vga,max_outputs=1' help?
(try with and without the max_outputs=1)
c) Are you able to do bisect builds to try and track down which commit
Sorry, in comment #2 for the native graphics window command line, I
copied from the wrong trial. The argument for QXL should have been
included, because that works with a native graphics window:
(...bootindex=0) \
-vga qxl
--
You received this bug notification because you are a member of
Finding a minimal case did shed some light on this.
Using QEMU's native graphics window, this works fine:
$ /usr/bin/qemu-system-x86_64 \
-m 1G \
-blockdev
raw,node-name=install_iso,read-only=on,file.driver=file,file.filename=/mnt/losable/ISOs/archlinux-2019.09.01-x86_64.iso
\
-device
Comparing the spice debug logs, where I see this with QEMU 4.0.0 without
the bug:
(remote-viewer:19270): GSpice-DEBUG: 00:05:21.201: channel-display.c:1979
display-2:0: received new monitors config from guest: n: 1/4
(remote-viewer:19270): GSpice-DEBUG: 00:05:21.201: channel-display.c:1997
displ
Hi,
Can you give the full qemu commandline you're using on 4.1.0 please?
(If you're starting it using libvirt/virsh then please include the xml
description file for the VM).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
** Description changed:
- Host is Arch Linux. linux 5.2.13, qemu 4.1.0.
+ Host is Arch Linux. linux 5.2.13, qemu 4.1.0. virt-viewer 8.0.
Guest is Arch Linux Sept 2019 ISO. linux 5.2.11.
Have replicated this both on a system using amdgpu and one using
integrated ASPEED graphics.
17 matches
Mail list logo
