Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MrDus-0002xc-6k for qemu-devel@nongnu.org; Fri, 25 Sep 2009 12:45:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MrDun-0002sS-8J for qemu-devel@nongnu.org; Fri, 25 Sep 2009 12:45:05 -0400 Received: from [199.232.76.173] (port=56354 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MrDum-0002sE-U9 for qemu-devel@nongnu.org; Fri, 25 Sep 2009 12:45:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54591) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MrDhP-0005mA-9s for qemu-devel@nongnu.org; Fri, 25 Sep 2009 12:31:11 -0400 Subject: Re: [Qemu-devel] [PATCH 10/13] Implement scsi device destruction References: <1253611767-6483-1-git-send-email-kraxel@redhat.com> <1253611767-6483-11-git-send-email-kraxel@redhat.com> <8763b8b1dh.fsf@pike.pond.sub.org> <4ABC7503.70200@redhat.com> <87iqf72mqm.fsf@pike.pond.sub.org> From: Markus Armbruster Date: Fri, 25 Sep 2009 18:31:06 +0200 In-Reply-To: (Artyom Tarasenko's message of "Fri\, 25 Sep 2009 17\:59\:55 +0200") Message-ID: <87iqf7q94l.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: Gerd Hoffmann , qemu-devel@nongnu.org Artyom Tarasenko writes: > 2009/9/25 Markus Armbruster : >> Gerd Hoffmann writes: [...] >>> To extend that question: =C2=A0While playing with that I've noticed lin= ux >>> does not automagically find the a scsi disk hot-plugged in. =C2=A0After >>> reboot (and the scsi bus rescan triggered by that) it finds the >>> disk. Reloading the driver module probably would have worked too. =C2= =A0We >>> don't signal the guest in any way it got a new disk, so this isn't >>> exactly surprising. =C2=A0Is this just a emulation limitation? =C2=A0Or= a >>> limitation of the emulated scsi host adapters? >> >> What appens when you hotplug or just switch on a real SCSI device? =C2= =A0Does >> Linux pick it up automatically? =C2=A0Long ago when I last tried that, I >> think I had to do a magic write to sysfs to make it look for the device. > > I guess it wasn't magic, but an official way of doing it. At least > SCSI-2 controllers didn't get any notification signal on a hot-plug. > I used to do it with > echo "scsi add-single-device 0 0 3 0" > /proc/scsi/scsi Call it "official magic" then ;)