2.11.1 could work, qemu is no longer occupying 100% CPU. That's interesting...
Now I can see the starting screen via vnc, says that not a bootable disk. Is that because the guest OS's virtio vhost driver is not up to date enough? Thanks, Bob 2018-04-20 1:17 GMT+08:00 John Snow <js...@redhat.com>: > 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 > > > > 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 > > > >
