Hi, we can confirm that upgrading to kernel 4.19.67-2 (4.19.0-6) solve the
problem.
Kind regards!
Guido
fixed 932550 4.19.67-1
Control: reassign -1 src:linux 4.19.37-5
Control: affects -1 qemu-system-x86
Control: fixed -1 4.19.37-4
Hello Guido,
thanks for the confirmation.
So I try to reassign this bug to the kernel package.
Kind regards,
Bernhard
Hi, we can confirm that using kernel 4.19.28+2 (4.19.0-4) workaround the
problem.
Kind regards!
Guido
Dear Maintainer,
I found that I could also reproduce this issue on my AMD Ryzen 7.
Based on the modification date of my VM it was working
with Buster/testing at least at 2018-08-24 at this hardware.
I tested the binaries qemu-system-x86_64 down to 2.12+dfsg-2 and
also current qemu git, all show
Hi Michael,
> Maybe this is specific to AMD CPU? I don't have AMD CPU available for
> testing.
Very well possible. Meanwhile I have made some tests with my laptop.
Not with the same VM but one from the same "master".
Same issue there.
Unfortunately it has also an AMD CPU (different model
20.07.2019 17:53, Dr. Oliver Muth wrote:
> Package: qemu-system-x86
> Version: 1:3.1+dfsg-8~deb10u1
> Severity: normal
>
> Dear Maintainer,
>
> I have an old Win XP Pro SP3 VM that used to work with kvm in stretch and
> earlier. Since the upgrade to buster the VM no longer boots with
>
Package: qemu-system-x86
Version: 1:3.1+dfsg-8~deb10u1
Severity: normal
Dear Maintainer,
I have an old Win XP Pro SP3 VM that used to work with kvm in stretch and
earlier. Since the upgrade to buster the VM no longer boots with
"qemu-system-x86_64 --enable-kvm ...".
Trying "safe mode" on the
8 matches
Mail list logo