All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Li Feng <fengli@smartx.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	vkuznets@redhat.com, "Philippe Mathieu-Daudé" <philmd@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 16:31:29 +0100	[thread overview]
Message-ID: <20200514153129.GP2787@work-vm> (raw)
In-Reply-To: <CAHckoCxc2XTA3ckU0sq-BmbZZFtfAY_GaEOW46XFzfZ2qXjeMQ@mail.gmail.com>

* Li Feng (fengli@smartx.com) wrote:
> Dr. David Alan Gilbert <dgilbert@redhat.com> 于2020年5月14日周四 下午11:16写道:
> >
> > * Li Feng (fengli@smartx.com) wrote:
> > > EXSi CPU is : Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
> > > This is my vm, I run qemu in it.
> >
> > Do you know what the real hardware is?
> What information do you need? I could send it out.
> The EXSi version: VMware ESXi, 6.5.0, 5969303

VMWare is saying to the guest it's an E5-2640 v3; is that what
your real CPU is?

Dave

> >
> > Dave
> >
> > > (base) 20-05-14 15:32:50 root@31_216:~  lscpu
> > > Architecture:          x86_64
> > > CPU op-mode(s):        32-bit, 64-bit
> > > Byte Order:            Little Endian
> > > CPU(s):                16
> > > On-line CPU(s) list:   0-15
> > > Thread(s) per core:    1
> > > Core(s) per socket:    1
> > > Socket(s):             16
> > > NUMA node(s):          1
> > > Vendor ID:             GenuineIntel
> > > CPU family:            6
> > > Model:                 63
> > > Model name:            Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
> > > Stepping:              2
> > > CPU MHz:               2599.998
> > > BogoMIPS:              5199.99
> > > Virtualization:        VT-x
> > > Hypervisor vendor:     VMware
> > > Virtualization type:   full
> > > L1d cache:             32K
> > > L1i cache:             32K
> > > L2 cache:              256K
> > > L3 cache:              20480K
> > > NUMA node0 CPU(s):     0-15
> > > Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep
> > > mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall
> > > nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology
> > > tsc_reliable nonstop_tsc cpuid pni pclmulqdq vmx ssse3 fma cx16 pcid
> > > sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx
> > > f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single
> > > tpr_shadow vnmi ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2
> > > invpcid xsaveopt arat
> > >
> > > Thanks,
> > >
> > > Feng Li
> > >
> > > Dr. David Alan Gilbert <dgilbert@redhat.com> 于2020年5月14日周四 下午8:52写道:
> > > >
> > > > * 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.
> > > >
> > > > > > 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.
> > > >
> > > > What's your host CPU?
> > > >
> > > > Dave
> > > >
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Feng Li
> > > > > >
> > > > >
> > > > --
> > > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > > >
> > >
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2020-05-14 15:33 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
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 [this message]
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=20200514153129.GP2787@work-vm \
    --to=dgilbert@redhat.com \
    --cc=fengli@smartx.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vkuznets@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.