Looks like this should have been fixed here:
https://gitlab.com/qemu-project/qemu/-/commit/118f2aadbc66aaae4e8d52
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Looking through old bug tickets ... Did you ever send your patch to the
qemu-devel mailing list? See
https://wiki.qemu.org/Contribute/SubmitAPatch for more information
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
According to the response here: https://www.mail-archive.com/qemu-
de...@nongnu.org/msg572220.html
...the call to xgetbv should be guarded against processors that don't
support the instruction. The attached patch seems to work for me but
must admit I am way out of my depth here (I understand nothi
On 7 November 2018 at 17:15, Nathan Wallace <1758...@bugs.launchpad.net> wrote:
> I am also able to reproduce this bug. The problem is that when hvf is
> enabled, qemu will attempt to execute the xgetbv instruction, which
> isn't supported on my processor (Intel Xeon X5670).
>
> Here is a stack tra
I am also able to reproduce this bug. The problem is that when hvf is
enabled, qemu will attempt to execute the xgetbv instruction, which
isn't supported on my processor (Intel Xeon X5670).
Here is a stack trace from lldb; the behavior is 100% reproducible for
me.
nathan@Nathans-Mac-Pro:~/src/qem
Disregard the above log; that was from a September 2017 build.
On RC1:
Process: qemu-system-x86_64 [6567]
Path: /usr/local/bin/qemu-system-x86_64
Identifier:qemu-system-x86_64
Version: 0
Code Type: X86-64 (Native)
Parent Process
Process: qemu-system-x86_64 [6330]
Path: /Users/USER/*/qemu-system-x86_64
Identifier:qemu-system-x86_64
Version: 0
Code Type: X86-64 (Native)
Parent Process:bash [1558]
Responsible: qemu-system-x86_64 [6330]
User
