All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: qemu assert in staging during HVM live migration
Date: Tue, 11 Dec 2018 16:07:35 +0100	[thread overview]
Message-ID: <20181211160735.4e583d6e.olaf@aepfle.de> (raw)
In-Reply-To: <20181123155449.GB6902@perard.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]

Am Fri, 23 Nov 2018 15:54:49 +0000
schrieb Anthony PERARD <anthony.perard@citrix.com>:

> On Thu, Nov 22, 2018 at 11:03:45AM +0100, Olaf Hering wrote:
> > qemu-system-i386: block/block-backend.c:903: blk_get_attached_dev_id: Assertion `!blk->legacy_dev' failed.
> xen-disk (qdisk) is currently using legacy stuff in QEMU, and this
> legacy stuff is going to disappear. Paul have a patch series to
> modernise it:

This assert triggers also without migration.

Do we want to get this fixed for qemu-3.1.0 and perhaps qemu-3.0.1, or shall we declare both broken until the mentioned series is eventually applied?

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-12-11 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 10:03 qemu assert in staging during HVM live migration Olaf Hering
2018-11-23 15:54 ` Anthony PERARD
2018-11-23 15:57   ` Olaf Hering
2018-11-26 14:32     ` Anthony PERARD
2018-11-26 15:16       ` Olaf Hering
2018-12-11 15:07   ` Olaf Hering [this message]
2018-12-11 16:03     ` Paul Durrant

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=20181211160735.4e583d6e.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=anthony.perard@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.