Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #965502 > unrolled thread

Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys

Started by"Dr. Oliver Muth" <Dr.O.Muth@habmalnefrage.de>
First post2019-07-20 17:00 +0200
Last post2019-08-13 16:30 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys "Dr. Oliver Muth" <Dr.O.Muth@habmalnefrage.de> - 2019-07-20 17:00 +0200
    Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys Michael Tokarev <mjt@tls.msk.ru> - 2019-07-23 16:50 +0200
      Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys "Dr. Oliver Muth" <Dr.O.Muth@habmalnefrage.de> - 2019-07-25 16:50 +0200
    Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys Bernhard Übelacker <bernhardu@mailbox.org> - 2019-08-07 20:00 +0200
      Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys MAG4 Piemonte <mag4@aruba.it> - 2019-08-13 16:30 +0200

#965502 — Bug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys

From"Dr. Oliver Muth" <Dr.O.Muth@habmalnefrage.de>
Date2019-07-20 17:00 +0200
SubjectBug#932550: qemu-system-x86: WinXP no longer boots with --enable-kvm, stops at \Windows\System32\Drivers\Mup.sys
Message-ID<ylZ05-69q-9@gated-at.bofh.it>
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 Windows rescue screen shows that the VM boots until to the line
multi(0)disk(0)rdisk(0)partition(1)\Windows\System32\Drivers\Mup.sys
and then reboots into the Windows rescue screen.

It still boots successfully when qemu is called without --enable-kvm.
Assuming that the properties of the virtual CPU had changed I tried -cpu host|max|kvm64|qemu64|athlon|phenom but it made no difference.
Assuming that the image was damaged I tried different images from backups of the last 5 years. They all used to work and no longer do.
I also tried to boot the VM from a Windows XP pro CD in order to repair the Windows installation if necessary. But the CD does not boot either (reboots after "Setup is starting Windows").
Note that only XP is affected. All other VMs I use work fine with --enable-kvm.

My CPU:

$ lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       48 bits physical, 48 bits virtual
CPU(s):              3
On-line CPU(s) list: 0-2
Thread(s) per core:  1
Core(s) per socket:  3
Socket(s):           1
NUMA node(s):        1
Vendor ID:           AuthenticAMD
CPU family:          16
Model:               4
Model name:          AMD Phenom(tm) II X3 720 Processor
Stepping:            2
CPU MHz:             800.000
CPU max MHz:         2800,0000
CPU min MHz:         800,0000
BogoMIPS:            5587.84
Virtualization:      AMD-V
L1d cache:           64K
L1i cache:           64K
L2 cache:            512K
L3 cache:            6144K
NUMA node0 CPU(s):   0-2
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save

$ lsmod | grep kvm
kvm_amd               106496  0
ccp                    98304  1 kvm_amd
kvm                   724992  1 kvm_amd
irqbypass              16384  1 kvm


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/3 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu             1.0.0+git-20190125.36a4c85-1
ii  libaio1               0.3.112-3
ii  libasound2            1.1.8-1
ii  libbluetooth3         5.50-1
ii  libbrlapi0.6          5.6-10
ii  libc6                 2.28-10
ii  libcacard0            1:2.6.1-1
ii  libcapstone3          4.0.1+really+3.0.5-1
ii  libepoxy0             1.5.3-0.1
ii  libfdt1               1.4.7-3
ii  libgbm1               18.3.6-2
ii  libgcc1               1:8.3.0-6
ii  libglib2.0-0          2.58.3-2
ii  libgnutls30           3.6.7-4
ii  libibverbs1           22.1-1
ii  libjpeg62-turbo       1:1.5.2-2+b1
ii  libncursesw6          6.1+20181013-2
ii  libnettle6            3.4.1-1
ii  libnuma1              2.0.12-1
ii  libpixman-1-0         0.36.0-1
ii  libpng16-16           1.6.36-6
ii  librdmacm1            22.1-1
ii  libsasl2-2            2.1.27+dfsg-1
ii  libseccomp2           2.3.3-4
ii  libspice-server1      0.14.0-1.3
ii  libtinfo6             6.1+20181013-2
ii  libusb-1.0-0          2:1.0.22-2
ii  libusbredirparser1    0.8.0-1
ii  libvdeplug2           2.3.2+r586-2.2
ii  libvirglrenderer0     0.7.0-2
ii  libxendevicemodel1    4.11.1+92-g6c33308a8d-2
ii  libxenevtchn1         4.11.1+92-g6c33308a8d-2
ii  libxenforeignmemory1  4.11.1+92-g6c33308a8d-2
ii  libxengnttab1         4.11.1+92-g6c33308a8d-2
ii  libxenmisc4.11        4.11.1+92-g6c33308a8d-2
ii  libxenstore3.0        4.11.1+92-g6c33308a8d-2
ii  libxentoolcore1       4.11.1+92-g6c33308a8d-2
ii  qemu-system-common    1:3.1+dfsg-8~deb10u1
ii  qemu-system-data      1:3.1+dfsg-8~deb10u1
ii  seabios               1.12.0-1
ii  zlib1g                1:1.2.11.dfsg-1

Versions of packages qemu-system-x86 recommends:
pn  ovmf             <none>
ii  qemu-system-gui  1:3.1+dfsg-8~deb10u1
ii  qemu-utils       1:3.1+dfsg-8~deb10u1

Versions of packages qemu-system-x86 suggests:
pn  qemu-block-extra  <none>
ii  samba             2:4.9.5+dfsg-5
ii  sgabios           0.0~svn8-4
ii  vde2              2.3.2+r586-2.2

-- no debconf information

[toc] | [next] | [standalone]

#966050

FromMichael Tokarev <mjt@tls.msk.ru>
Date2019-07-23 16:50 +0200
Message-ID<yn4h3-5Wr-7@gated-at.bofh.it>
In reply to#965502
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 "qemu-system-x86_64 --enable-kvm ...".
> Trying "safe mode" on the Windows rescue screen shows that the VM boots until to the line
> multi(0)disk(0)rdisk(0)partition(1)\Windows\System32\Drivers\Mup.sys
> and then reboots into the Windows rescue screen.

Hmm. I can't confirm this, here winXP boots fine with kvm mode, either
from the installation CD or from a few of my (old) hdd images.

Maybe this is specific to AMD CPU? I don't have AMD CPU available for
testing.

Thanks,

/mjt

[toc] | [prev] | [next] | [standalone]

#966416

From"Dr. Oliver Muth" <Dr.O.Muth@habmalnefrage.de>
Date2019-07-25 16:50 +0200
Message-ID<ynNea-CH-17@gated-at.bofh.it>
In reply to#966050
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 though). I don't
have any Intel CPU.

Kind regards

Oliver

$lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       48 bits physical, 48 bits virtual
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):           1
NUMA node(s):        1
Vendor ID:           AuthenticAMD
CPU family:          21
Model:               19
Model name:          AMD A10-5750M APU with Radeon(tm) HD Graphics
Stepping:            1
CPU MHz:             1408.675
CPU max MHz:         2500.0000
CPU min MHz:         1400.0000
BogoMIPS:            4990.81
Virtualization:      AMD-V
L1d cache:           16K
L1i cache:           64K
L2 cache:            2048K
NUMA node0 CPU(s):   0-3
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid
extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1
sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt
lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb
hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale
vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

[toc] | [prev] | [next] | [standalone]

#968542

FromBernhard Übelacker <bernhardu@mailbox.org>
Date2019-08-07 20:00 +0200
Message-ID<ysyoa-2xo-3@gated-at.bofh.it>
In reply to#965502
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 the VM fail the same way.

So I guessed it might be a kernel or firmware issue (firmware
got updated in between).

Then I found following:
    https://lkml.org/lkml/2019/5/4/113

So maybe 4.19.28+2 (4.19.0-4) does not yet contain the first [1] change,
or a kernel >= 4.19.40 may contain the fix [2] already.
In the regular tree this first change appeared
with v5.1-rc3, and the fix in v5.1.

Kind regards,
Bernhard


[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=b9733a74350d6ab2e1a36bface0e3b36866945de
    -> Maybe the introducing change, first in Linux 4.19.33 (2019-04-03)

[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=499bbe739d5aeb1bb775fed5523902f840cbe67b
    -> Maybe fix contained in Linux 4.19.40 (2019-05-05)

[toc] | [prev] | [next] | [standalone]

#969607

FromMAG4 Piemonte <mag4@aruba.it>
Date2019-08-13 16:30 +0200
Message-ID<yuFYd-33c-3@gated-at.bofh.it>
In reply to#968542
Hi, we can confirm that using kernel 4.19.28+2 (4.19.0-4) workaround the 
problem.
Kind regards!

Guido

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web