qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Li Feng <fengli@smartx.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
Date: Thu, 14 May 2020 15:15:22 +0200	[thread overview]
Message-ID: <87r1vmwtcl.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20200514125220.GJ2787@work-vm>

"Dr. David Alan Gilbert" <dgilbert@redhat.com> writes:

> * Philippe Mathieu-Daudé (philmd@redhat.com) wrote:
>> Cc'ing David/Paolo in case they have a clue...
>> 
>> On 5/14/20 1:27 PM, Li Feng wrote:
>> > Dear all,
>> > 
>> > I have encountered a weird crash.
>> > I remember before a few days it works well and I rebase my code from upstream.
>> > 
>> > This is the command:
>> > /root/qemu-master/x86_64-softmmu/qemu-system-x86_64 -enable-kvm
>> > -device virtio-balloon -cpu host -smp 4 -m 2G -drive
>> > file=/root/html/fedora-10g.img,format=raw,cache=none,aio=native,if=none,id=drive-virtio-disk1
>> > -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1
>> > -device virtio-net,netdev=nw1,mac=00:11:22:EE:EE:10 -netdev
>> > tap,id=nw1,script=no,downscript=no,ifname=tap0 -serial mon:stdio
>> > -nographic -object
>> > memory-backend-file,id=mem0,size=2G,mem-path=/dev/hugepages,share=on
>> > -numa node,memdev=mem0 -vnc 0.0.0.0:100 -machine usb=on,nvdimm -device
>> > usb-tablet -monitor unix:///tmp/a.socket,server,nowait -device
>> > virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev
>> > socket,id=channel1,path=/tmp/helloworld1,server,nowait -device
>> > virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1
>> > -qmp tcp:0.0.0.0:2234,server,nowait
>> > qemu-system-x86_64: error: failed to set MSR 0x48f to 0x7fefff00036dfb
>> > qemu-system-x86_64: /root/qemu-master/target/i386/kvm.c:2695:
>> > kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
>
> 48f is MSR_IA32_VMX_TRUE_EXIT_CTLS
> I've not got a note of seeing that one before.
>

If you're not intended to run nested VMs (which would make it 3-level
nesting btw) you can try:

'-cpu host,-vmx'

The strange part is that we don't seem to mangle
MSR_IA32_VMX_TRUE_EXIT_CTLS in QEMU. I bet it has something to do with
VM_EXIT_ALWAYSON_WITHOUT_TRUE_MSR in KVM.

>> > This is the commit record:
>> > *   c88f1ffc19 - (origin/master, origin/HEAD) Merge remote-tracking
>> > branch 'remotes/kevin/tags/for-upstream' into staging (3 days ago)
>> > <Peter Maydell>
>> > |\
>> > | * 47e0b38a13 - block: Drop unused .bdrv_has_zero_init_truncate (3
>> > days ago) <Eric Blake>
>> > | * dbc636e791 - vhdx: Rework truncation logic (3 days ago) <Eric Blake>
>> > | * bda4cdcbb9 - parallels: Rework truncation logic (3 days ago) <Eric Blake>
>> > | * be9c9404db - ssh: Support BDRV_REQ_ZERO_WRITE for truncate (3 days
>> > ago) <Eric Blake>
>> > | * fec00559e7 - sheepdog: Support BDRV_REQ_ZERO_WRITE for truncate (3
>> > days ago) <Eric Blake>
>> > | * 2f98910d5b - rbd: Support BDRV_REQ_ZERO_WRITE for truncate (3 days
>> > ago) <Eric Blake>
>> > 
>> > I run this qemu in a VM base on EXSi.
>> > 
>> > Does anyone have the same issue?
>
> cc'ing in Vitaly since he knows VMWare stuff.

I wish it was true :-)

>
> What's your host CPU?
>

And what's your L1 kernel?

-- 
Vitaly



  reply	other threads:[~2020-05-14 13:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHckoCymFfuVd=tKV-hk+PHn2fk6ydWjSxwKVorj9Qe5KV6nGQ@mail.gmail.com>
2020-05-14 11:27 ` kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed Li Feng
2020-05-14 12:09   ` Philippe Mathieu-Daudé
2020-05-14 12:52     ` Dr. David Alan Gilbert
2020-05-14 13:15       ` Vitaly Kuznetsov [this message]
2020-05-14 15:10       ` Li Feng
2020-05-14 15:12         ` Li Feng
2020-05-14 15:16         ` Dr. David Alan Gilbert
2020-05-14 15:19           ` Li Feng
2020-05-14 15:31             ` Dr. David Alan Gilbert
2020-05-14 15:49               ` Li Feng
2020-05-20  3:50                 ` Li Feng
2020-05-20  7:28                   ` Paolo Bonzini
2020-05-20  8:22                     ` Li Feng
2020-05-20  8:32                       ` Paolo Bonzini
2020-05-20  8:55                         ` Li Feng
2020-05-20  9:34                           ` Paolo Bonzini
2020-05-20  9:36                             ` Li Feng
2020-05-20 10:10                               ` Paolo Bonzini
2020-05-20 10:15                                 ` Li Feng
2020-05-20 10:26                                   ` Paolo Bonzini
2020-05-21  8:10                                     ` Li Feng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1vmwtcl.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=fengli@smartx.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).