Looking at the comments here, I assume this has been a bug in the
kernel, not in QEMU, so I'm closing this one now. If you still think
this is something that needs fixing in QEMU, please open a new ticket in
the new bug tracker at https://gitlab.com/qemu-project/qemu/-/issues
instead.
** Changed i
The QEMU project is currently moving 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 the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
Ran into the same issue on Proxmox 6.3-3
Setting `bcdedit /set xsavedisable 1` and using cpu=host works for me
Without I get bootloops and other options that luqmana posted, Hyper-V fails to
start
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
Oh, and I guess I misinterpreted what -mpx was for. To be clear, I was
running into 2 issues:
1. Hyper-V fails to initialize.
"Fixed" by one of:
a) using named cpu model
b) cpu=host and running `bcdedit /set xsavedisable 1` in Windows before
enabling Hyper-V
c) cpu=host,-mpx
It's more likely to be a bug in KVM.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in QEMU:
New
Status in qemu-kvm p
I haven't tried 5.9, just:
- 5.4.0-58 Works
- 5.8.0-33 (20.04 HWE Edge)Bootloop
- 5.10.1-051001Works
If I have time later I can try narrowing down which kernel causes the
issue.
But is the BNDCFGS MSR issue considered a bug in qemu or what?
--
You receive
If you can bisect between 5.9 (I understand it's bad?) and 5.10 we could
propose it for stable kernels.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu hos
Adding -mpx doesn't seem to help on 5.8, the guest still bootloops.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in Q
Aha! The final boot loop issue is resolved if I either upgrade to 5.10
or downgrade to 5.4 from 5.8.
So the main issue then seems to be the missing control bits.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.
Try instead disabling MPX with "-cpu host,-mpx".
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in QEMU:
New
Status i
** Bug watch added: bugs.centos.org/ #17788
https://bugs.centos.org/view.php?id=17788
** Also affects: qemu-kvm (CentOS) via
https://bugs.centos.org/view.php?id=17788
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of qemu-
devel
Ok, so I narrowed done one possible issue: the BNDCFGS bits in the vm
entry/exit control MSRs are not set but HyperV expects them to be set if
xsave is supported. This quick patch actually lets Hyper-V initialize
and continue booting:
https://gist.github.com/552baa8be026e67bef2d223076b81636
An alt
Ok, after bisect between stable-4.1 and stable-4.2 I did confirm that
https://github.com/qemu/qemu/commit/20a78b02d31534ae478779c2f2816c273601e869
is the first bad commit.
The full qemu command line is:
qemu-system-x86_64 \
-name guest=test,debug-threads=on \
-serial none \
-enable-kv
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/qemu/+bug/1908489/+attachment/556/+files/cpuinfo.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/1908489
Title:
qemu 4.2 boot
** Attachment added: "vmxcap"
https://bugs.launchpad.net/qemu/+bug/1908489/+attachment/555/+files/vmxcap.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/1908489
Title:
qemu 4.2 bootloops
15 matches
Mail list logo
