From: Stefan Hajnoczi <stefanha@gmail.com>
To: 皮智 <pizhi0616@gmail.com>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com
Subject: Re: [Qemu-devel] ask a question
Date: Wed, 16 Aug 2017 09:59:21 +0100 [thread overview]
Message-ID: <20170816085921.GD3180@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAC0nwAR8tCfVU518a3p8Qmd8Y84mLeb6j2yTrErnnK8_AUnpWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4129 bytes --]
On Wed, Aug 16, 2017 at 02:25:19PM +0800, 皮智 wrote:
> Hi，I meet a problem with vm, my environment is qemu-kvm-2.3,
> virtio-win-0.1.126, host(centos7.2), guest(windows10).
>
> libvirt xml has four virtio-serial channel as follows:
CCing the libvirt mailing list. This may be a libvirt issue.
> <channel type='spicevmc'>
> <target type='virtio' name='com.redhat.spice.0' state='connected'/>
> <alias name='channel0'/>
> <address type='virtio-serial' controller='0' bus='0' port='1'/>
> </channel>
> <channel type='unix'>
> <source mode='bind'
> path='/var/lib/libvirt/qemu/e597eab9-95db-46e9-96f0-12a84c692569'/>
> <target type='virtio' name='pv-mon' state='connected'/>
> <alias name='channel1'/>
> <address type='virtio-serial' controller='0' bus='0' port='2'/>
> </channel>
> <channel type='unix'>
> <source mode='bind'
> path='/var/lib/libvirt/qemu/e597eab9-95db-46e9-96f0-12a84c692569-qga'/>
> <target type='virtio' name='org.qemu.guest_agent.0'
> state='connected'/>
> <alias name='channel2'/>
> <address type='virtio-serial' controller='0' bus='0' port='3'/>
> </channel>
> <channel type='unix'>
> <source mode='bind'
> path='/var/lib/libvirt/qemu/e597eab9-95db-46e9-96f0-12a84c692569-report'/>
> <target type='virtio' name='qga-active-report' state='connected'/>
> <alias name='channel3'/>
> <address type='virtio-serial' controller='0' bus='0' port='4'/>
> </channel>
>
> If I hard reboot the vm, it may happen as follows:
>
> 2017-08-14T07:51:18.401008Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:51:18.956482Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:51:29.176795Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:51:34.454819Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 2042451128 for device virtio-serial0.0
> 2017-08-14T07:51:44.655068Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:51:49.764201Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:51:59.969836Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:52:21.564461Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:52:47.059452Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:53:22.710677Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:53:32.781204Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T07:53:48.040513Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 3179968584 for device virtio-serial0.0
> 2017-08-14T07:54:23.547393Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:55:54.350754Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:56:09.393056Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:57:39.670850Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T07:58:09.867650Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1185792 for device virtio-serial0.0
> 2017-08-14T07:59:10.053208Z qemu-kvm: virtio-serial-bus: Unexpected port id
> 1122983520 for device virtio-serial0.0
> 2017-08-14T08:00:20.235162Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
> 2017-08-14T08:01:20.394196Z qemu-kvm: virtio-serial-bus: Guest failure in
> adding device virtio-serial0.0
>
> So, the virtio-serial port will not be available, it cause my program
> doesn't start in guest(windows10).
> Can you give me some advices ?
>
> Looking forward to your reply.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-08-16 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 6:25 [Qemu-devel] ask a question 皮智
2017-08-16 8:59 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-18 7:39 皮智
2017-07-21 12:54 ` Stefan Hajnoczi
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=20170816085921.GD3180@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=libvir-list@redhat.com \
--cc=pizhi0616@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).