virtio-fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, fam@euphon.net, berrange@redhat.com,
	f4bug@amsat.org, aurelien@aurel32.net, pbonzini@redhat.com,
	stefanha@redhat.com, crosa@redhat.com,
	"Raphael Norwitz" <raphael.norwitz@nutanix.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Mathieu Poirier" <mathieu.poirier@linaro.org>,
	"open list:Block layer core" <qemu-block@nongnu.org>,
	"open list:virtiofs" <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start
Date: Wed, 23 Nov 2022 07:27:40 +0100	[thread overview]
Message-ID: <7599e943-d7b2-df26-6827-9e25102dd39b@linux.ibm.com> (raw)
In-Reply-To: <20221121173656-mutt-send-email-mst@kernel.org>

Am 21.11.22 um 23:37 schrieb Michael S. Tsirkin:
[...]
>> qemu-system-x86_64: ../hw/virtio/vhost-vsock-common.c:203: vhost_vsock_common_pre_save: Assertion `!vhost_dev_is_started(&vvc->vhost_dev)' failed.
>> 2022-11-15 16:38:46.096+0000: shutting down, reason=crashed
> 
> Alex were you able to replicate? Just curious.

Ping?


  reply	other threads:[~2022-11-23  6:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221108092308.1717426-1-alex.bennee@linaro.org>
2022-11-08  9:23 ` [Virtio-fs] [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start Alex Bennée
2022-11-08  9:32   ` Michael S. Tsirkin
2022-11-08 10:23     ` Alex Bennée
2022-11-08 10:26       ` Michael S. Tsirkin
2022-11-08 11:21         ` Alex Bennée
2022-11-08 15:24           ` Michael S. Tsirkin
2022-11-08 16:41             ` Alex Bennée
2022-11-08  9:33   ` Michael S. Tsirkin
2022-11-14 16:18   ` Christian Borntraeger
2022-11-14 16:37     ` Michael S. Tsirkin
2022-11-14 16:55       ` Christian Borntraeger
2022-11-14 17:10         ` Michael S. Tsirkin
2022-11-14 17:15           ` Christian Borntraeger
2022-11-14 17:20             ` Michael S. Tsirkin
2022-11-15  7:44               ` Christian Borntraeger
2022-11-15  8:18               ` Christian Borntraeger
2022-11-15  9:05                 ` Michael S. Tsirkin
2022-11-15 11:25                 ` Michael S. Tsirkin
2022-11-15 13:25                   ` Christian Borntraeger
2022-11-15 14:31               ` Alex Bennée
2022-11-15 15:09                 ` Christian Borntraeger
2022-11-15 16:05                   ` Alex Bennée
2022-11-15 16:40                     ` Christian Borntraeger
2022-11-15 16:46                       ` Christian Borntraeger
2022-11-21 22:37                         ` Michael S. Tsirkin
2022-11-23  6:27                           ` Christian Borntraeger [this message]
2022-11-14 16:43     ` Alex Bennée

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=7599e943-d7b2-df26-6827-9e25102dd39b@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael.norwitz@nutanix.com \
    --cc=stefanha@redhat.com \
    --cc=viresh.kumar@linaro.org \
    --cc=virtio-fs@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).