From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MrCBc-0007RQ-48 for qemu-devel@nongnu.org; Fri, 25 Sep 2009 10:54:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MrCBX-0007P3-Cl for qemu-devel@nongnu.org; Fri, 25 Sep 2009 10:54:15 -0400 Received: from [199.232.76.173] (port=56450 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MrCBX-0007Ox-9l for qemu-devel@nongnu.org; Fri, 25 Sep 2009 10:54:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45427) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MrCBW-0006Z9-Le for qemu-devel@nongnu.org; Fri, 25 Sep 2009 10:54:10 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8PEs9mj016638 for ; Fri, 25 Sep 2009 10:54:09 -0400 Message-ID: <4ABCD98F.9040006@redhat.com> Date: Fri, 25 Sep 2009 16:54:07 +0200 From: Gerd Hoffmann MIME-Version: 1.0 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> In-Reply-To: <87iqf72mqm.fsf@pike.pond.sub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org Hi, >> To extend that question: While playing with that I've noticed linux >> does not automagically find the a scsi disk hot-plugged in. After >> reboot (and the scsi bus rescan triggered by that) it finds the >> disk. Reloading the driver module probably would have worked too. We >> don't signal the guest in any way it got a new disk, so this isn't >> exactly surprising. Is this just a emulation limitation? Or a >> limitation of the emulated scsi host adapters? > > What appens when you hotplug or just switch on a real SCSI device? Does > Linux pick it up automatically? Long ago when I last tried that, I > think I had to do a magic write to sysfs to make it look for the device. Old, classic, parallel scsi (with the 50wire cable) works that way. But IIRC there are also more modern variants which can handle hotplug. Dunno how that works though and whenever we could do that with the lsi adapter we are emulating ... cheers, Gerd