Using QEMU version 3.1.50 (v3.1.0-2338-g1ba530a4ec-dirty), after the
commit 35921860156e39f17ffd7e18d0f84d2396a6e8f4
kbd-state: don't block auto-repeat events
It was noticed that keys can get stuck on an Intel GVT-g (iGVT-g)
Windows 10 guest. For example, pressing "e" will result on
"e
I noticed that the key inputs are no longer repeating when using default
setting on QEMU. For example, if I press "a" and keep it pressed it will
print only one "a" instead of repeating them. Another example is when
deleting text: instead of holding backspace pressed and the text is
deleted, it's n
Thank you for testing this, the last update greatly improved the
situation. libspice-server1 updated, so I rebuilt QEMU. The
libspice-server1 0.14.0-1ubuntu2.4 change log is:
* SECURITY UPDATE: off-by-one error in memslot_get_virt
- debian/patches/CVE-2019-3813.patch: fix checks in server/me
Mageia 7 guest is crashing too. The command line:
qemu-system-x86_64 \
-name "Mageia 7" -k pt-br -nodefaults -accel kvm -cpu host -smp
cores=2,threads=1 -m 1G \
-device qxl-vga,xres=1366,yres=768 \
-device qemu-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 \
-device usb-tablet,id=usbt
I can confirm this, KDE Neon using the command line similar to yours
crashes QEMU to me too. I will test with Mageia 7 later to see if it
behaves differently.
But this is a completely different crash. This crash is happening
earlier, what I reported first is a crash when the login screen should
lo
libspice-server1 on host: 0.14.0-1ubuntu2.2
spice-vdagent (the only package) on guest: 0.17.0-1ubuntu2
Guest kernel version: 4.15.0-44-generic
>
> OK, great; can can you confirm the version of the spice packages
> on both the guest and host, and the kernel on the guest.
>
> Dave
>
> --
> Dr. D
Here is the backtrace with the debug symbols added:
(gdb) bt
#0 0x70373e97 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1 0x70375801 in __GI_abort () at abort.c:79
#2 0x71171cc9 in spice_logv (log_domain=0x711dc9f5 "Spice",
args=0x7fff360
With QEMU version 3.1.50 (v3.1.0-1218-gad7a21e812-dirty) (commit
ad7a21e81231ae64540310384fb0f87ac8758b02) on Xubuntu 18.04 host, a KDE
Neon guest is crashing on boot. The QEMU command line is:
gdb -q -ex "set pagination off" -ex "set print thread-events off" -ex
"handle SIGUSR1 nostop nopass nopr
nd causing failures on guests too, with openSUSE still being the
biggest victim.
Regarding this specific usb-audio crash problem, QEMU from
sirius/usb-audio-crash seems to be fixed.
Às 10:56 de 10/12/2018, kra...@redhat.com escreveu:
> On Mon, Dec 10, 2018 at 12:11:09PM +0000, Leonardo Soares
Hi, I did not save that Mageia 7 data as I was unaware I could do this.
The data below is from another crash with openSUSE Leap, this time I
saved this backtrace with generate-core-file.
QEMU command line:
env QEMU_AUDIO_ADC_VOICES=0 QEMU_AUDIO_DRV=pa \
QEMU_AUDIO_DAC_FIXED_FREQ=96000 \
QEMU_AUDI
Linux guests are crashing on startup, this crash happens rarely and,
after boot, it is even rarer but happened at least once with an Ubuntu
18.04 guest.
The host OS is Xubuntu 18.04, happens with multiple kernel versions,
current is 4.20.0-rc5-drm-tip-d63c50f2b014037b43c1c0f108c61e0a31ede3c1+
QEM
11 matches
Mail list logo