From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: missing unplug of SCSI devices in HVM guest Date: Wed, 24 Aug 2016 11:24:25 +0200 Message-ID: <20160824092425.GA23354@aepfle.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7400600373661959662==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============7400600373661959662== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Does anyone remember why the the vbd frontend drivers also claim the SCSI disks, but the vbd backend in qemu has no unplug support for SCSI? The current situation for qemu-xen and qemu-xen-traditional is that both will create an emulated LSI controller with disk=[vdev=sda]. The xenlinux and pvops frontend drivers will claim the disk, but the sym53c8xx will see and claim it as well. As a result each disk is visible twice. One has to blacklist the sym53c8xx driver to avoid that. What should be done to fix this? #1 new unplug protocol for SCSI, but old guests dont know about it #2 reuse IDE flag to also unplug SCSI. This would cover pvops and guests where xenlinux based xen-platform-pci.ko is loaded before sym53c8xx.ko. It would break guests with frontend drivers that do not claim SCSI disks, the SCSI disk would disappear (if such frontends really exist). #3 do not provide SCSI if guest has PV drivers Olaf --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAle9Z8MACgkQXUKg+qaYNn6csACgi2PDcLaKiT+iWBUdJ7ijtqIE tJ4AoLKOIDyuB4f2NYX616QMwXkMie/7 =SdL3 -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- --===============7400600373661959662== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============7400600373661959662==--