Re: [Qemu-block] [Qemu-devel] [SPDK] qemu process hung at boot-up, no explicit errors or warnings

[Bob Chen]

2018-04-21 1:34 GMT+08:00 John Snow <address@hidden>:

On 04/20/2018 07:13 AM, Bob Chen wrote:
> 2.11.1 could work, qemu is no longer occupying 100% CPU. That's
> interesting...
>

Does 2.12 use 100% even at the firmware menu? Maybe we're not giving
this VM long enough to hit the spot that causes it to use 100%.

> Now I can see the starting screen via vnc, says that not a bootable disk.
>

If it's stopping at the firmware I think the guest is not being taken
into account, and the firmware is either trying to boot the wrong disk
or your disk is corrupted. (Or it can't see your disk at all -- I'm
personally not very familiar with using SPDK.) 

Can you share your command line with us?

I opened another thread to discuss this issue, looks like there's something wrong with the spdk official doc.

However, 2.12 is still very likely to be buggy. I'm sure I waited long enough but the CPU never dropped below 100%. The vnc screen stopped at "Loading SeaBIOS ..."

Again, 2.10 and 2.11 are fine. Though "No bootable device" but CPU dropped anyway.

 

>
> Is that because the guest OS's virtio vhost driver is not up to date enough?
> ​
>
> Thanks,
> Bob
>

On the QEMU-devel list and many other technical lists, can you please
reply in-line instead of replying above? ("top posting")

Thank you,
--John

> 2018-04-20 1:17 GMT+08:00 John Snow <address@hidden
> <mailto:address@hidden>>:

>
>     Forwarding to qemu-block.
>
>     On 04/19/2018 06:13 AM, Bob Chen wrote:
>     > Hi,
>     >
>     > I was trying to run qemu with spdk, referring to
>     > http://www.spdk.io/doc/vhost.html#vhost_qemu_config
>     <http://www.spdk.io/doc/vhost.html#vhost_qemu_config>
>     >
>     > Everything went well since I had already set up hugepages, vfio, vhost
>     > targets, vhost-scsi device(vhost-block was also tested), etc, without
>     > errors or warnings reported.
>     >
>     > But at the last step to run qemu, the process would somehow hang. And its
>     > cpu busy remained 100%.
>     >
>     > I used `perf top -p` to monitor the process activity,
>     >   18.28%  [kernel]                      [k] vmx_vcpu_run
>     >    3.06%  [kernel]                      [k] vcpu_enter_guest
>     >    3.05%  [kernel]                      [k] system_call_after_swapgs
>     >
>     > Do you have any ideas about what happened here?
>     >
>     > Test environment: latest CentOS 7 kernel, nvme ssd, spdk v18.01.x,
>     > dpdk 17.11.1, qemu 2.12.0-rc2. Detail log is attached within this mail.
>     >
>
>     Have you tried any other versions? (2.11.1, or 2.12-rc4?)
>
>     >
>     >
>     > Thanks,
>     > Bob
>     >
>
>