From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: "Xulei (Stone)" <stone.xulei@huawei.com>,
"seabios@seabios.org" <seabios@seabios.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
mst <mst@redhat.com>, jasowang <jasowang@redhat.com>,
xiaoguangrong <xiaoguangrong@tencent.com>,
Kevin O'Connor <kevin@koconnor.net>, kraxel <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [Qemu-devel] [Question] Seabios HANGs when mmio wirte in a nested vmware host wtih virito-scsi controller
Date: Mon, 17 Jul 2017 15:48:27 +0800 [thread overview]
Message-ID: <36075496-773e-e412-6e19-f332d158be53@gmail.com> (raw)
In-Reply-To: <8E78D212B8C25246BE4CE7EA0E645FE501067051@dggemi503-mbs.china.huawei.com>
On 07/17/2017 03:34 PM, Xulei (Stone) wrote:
>
> On 07/17/2017 11:13 AM, Xulei (Stone) wrote:
>
> >> |--virtio_queue_empty
> >>
> >> Then, kmod falls in infinite loop in handle EPT_MISCONFIG.
> >> As far as i know, when kvm enters guest after handling EPT_MISCONFIG, seabios should return
> >> from mmio write and wait for virtio backend(qemu) to handle this mmio writing.
> >> What puzzles me:
> >> 1) i can not understand why kvm runs in infinite loop and seabios does not return from writew.
>
> >From the trace in L1 guest, it did not hang in KVM, as it went into guest mode normally.
>
> >> 2) kvm nested kvm is ok. But vmware nested kvm is not ok. This problem has anything related
> >> with vmware?
> >>
>
> > It is the issue in vmware, i guess the RIP register is not handled correctly.
> > BTW, does kvm unit tests run well on nested vmware?
>
> Sadly, kvm unit tests run fail on nested vmware and make the CentOS 7.3(with kmod 4.4.11) crashed...
>
Well, so that should be reported to vmware. :-)
prev parent reply other threads:[~2017-07-17 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 3:13 [Qemu-devel] [Question] Seabios HANGs when mmio wirte in a nested vmware host wtih virito-scsi controller Xulei (Stone)
2017-07-17 6:49 ` Xiao Guangrong
2017-07-17 7:34 ` Xulei (Stone)
2017-07-17 7:48 ` Xiao Guangrong [this message]
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=36075496-773e-e412-6e19-f332d158be53@gmail.com \
--to=guangrong.xiao@gmail.com \
--cc=jasowang@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=stone.xulei@huawei.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=xiaoguangrong@tencent.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 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).