Hi,
This is actually a follow-up email as I was suggested to post the query on the mailing
list.
So, we are running into an issue while setting up SPDK vhost.
Our guest OS does not seem to boot-up after it looks like Qemu has setup communication
with the vhost app.
We first faced the problem with guest running Scientific Linux 6.1, kernel version
2.6.32-696.1.1.el6.
On James Harris’ recommendation, we tried running guest with CentOS 7, kernel version
3.10.0-514.el7.x86_64. But we see the same issue.
I have attached 2 different config files. One with the vhost setting and one without.
centos7.1.xml : This does not have any vhost related command line arguments while
launching the VM
Status: The VM launches just fine and we are able to login to the VM
vcentos7.1.xml: This one has the vhost setting appended
Status: The vhost-target output seems to show that the vhost-client (qemu) has been setup
properly (vhost_logs.txt) but we can’t login to the VM.
Follwing is the arp output
# arp -an
centos7.1 -->? (192.168.122.24) at 52:54:00:47:0c:3d [ether] on virbr0
vcentos7.1 -->? (192.168.122.204) at <incomplete> on virbr0
Also the console does not show any boot messages or login prompt.
# virsh ttyconsole vcentos7.1
/dev/pts/0
#virsh console vcentos7.1
Connected to domain vcentos7.1
Escape character is ^]
The qemu build used is the spdk branch with the latest commit ID being
6eed2b580b6d5bc853b8efc15931eaf0c0de68a2
Thanks/Regards
-a
Show replies by date
Hello Abhik,
From the SPDK vhost log it seems like VM stops interaction during the BIOS to OS
transition. It is possible that the VM tries to boot from vhost-user-scsi-pci device
instead of the CentOS image.
Could you please try adding boot order parameter to the disk image segment like so:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/home/qemu/qcows/centos7.1.qcow2'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05' function='0x0'/>
</disk>
Regards,
Tomek
From: SPDK [mailto:spdk-bounces@lists.01.org] On Behalf Of Abhik Sarkar
Sent: Friday, May 26, 2017 3:24 AM
To: spdk(a)lists.01.org
Subject: [SPDK] VM not booting up with SPDK vhost
Hi,
This is actually a follow-up email as I was suggested to post the query on the mailing
list.
So, we are running into an issue while setting up SPDK vhost.
Our guest OS does not seem to boot-up after it looks like Qemu has setup communication
with the vhost app.
We first faced the problem with guest running Scientific Linux 6.1, kernel version
2.6.32-696.1.1.el6.
On James Harris’ recommendation, we tried running guest with CentOS 7, kernel version
3.10.0-514.el7.x86_64. But we see the same issue.
I have attached 2 different config files. One with the vhost setting and one without.
centos7.1.xml : This does not have any vhost related command line arguments while
launching the VM
Status: The VM launches just fine and we are able to login to the VM
vcentos7.1.xml: This one has the vhost setting appended
Status: The vhost-target output seems to show that the vhost-client (qemu) has been setup
properly (vhost_logs.txt) but we can’t login to the VM.
Follwing is the arp output
# arp -an
centos7.1 -->? (192.168.122.24) at 52:54:00:47:0c:3d [ether] on virbr0
vcentos7.1 -->? (192.168.122.204) at <incomplete> on virbr0
Also the console does not show any boot messages or login prompt.
# virsh ttyconsole vcentos7.1
/dev/pts/0
#virsh console vcentos7.1
Connected to domain vcentos7.1
Escape character is ^]
The qemu build used is the spdk branch with the latest commit ID being
6eed2b580b6d5bc853b8efc15931eaf0c0de68a2
Thanks/Regards
-a
--------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy
Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000
PLN.
Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze
zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o
powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the
intended recipient(s). If you are not the intended recipient, please contact the sender
and delete all copies; any review or distribution by
others is strictly prohibited.