From: Paul Durrant <Paul.Durrant@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, George Dunlap <dunlapg@umich.edu>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: missing unplug of SCSI devices in HVM guest
Date: Wed, 7 Sep 2016 10:53:22 +0000 [thread overview]
Message-ID: <9f963c8dc93548efb1fb1b8a9334e372@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <F2A0E290-0EC7-4587-A7E3-F97BE4510174@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: 07 September 2016 11:49
> To: Paul Durrant <Paul.Durrant@citrix.com>; George Dunlap
> <dunlapg@umich.edu>
> Cc: xen-devel@lists.xen.org
> Subject: RE: [Xen-devel] missing unplug of SCSI devices in HVM guest
>
> Am 7. September 2016 12:38:09 MESZ, schrieb Paul Durrant
> <Paul.Durrant@citrix.com>:
>
> >I would have thought option #1 is the most logical and desirable in the
> >long run, but #2 could perhaps be used (by means of a configuration
> >option to qemu) in the meantime. In practice I doubt there is anything
> >out there that would use emulated SCSI as well as PV storage.
>
> The qemu changes I sent earlier this month implement #2. And my testing
> shows there will be no loss.
>
Ok. I guess #1 could be implemented later if it proves necessary in some circumstances.
Paul
> Emulated SCSI has the benefit that loading kernel+initrd is faster.
>
With seabios I'd certainly believe it. The IDE emulation is PIO only (unless you hack the config ... which I tend to do).
Paul
> Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-09-07 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 9:24 missing unplug of SCSI devices in HVM guest Olaf Hering
2016-09-06 16:42 ` George Dunlap
2016-09-07 10:38 ` Paul Durrant
2016-09-07 10:48 ` Olaf Hering
2016-09-07 10:53 ` Paul Durrant [this message]
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=9f963c8dc93548efb1fb1b8a9334e372@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=dunlapg@umich.edu \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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).