[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 10/13] Implement scsi device destruction
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] [PATCH 10/13] Implement scsi device destruction |
Date: |
Fri, 25 Sep 2009 18:31:06 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) |
Artyom Tarasenko <address@hidden> writes:
> 2009/9/25 Markus Armbruster <address@hidden>:
>> Gerd Hoffmann <address@hidden> writes:
[...]
>>> 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.
>
> 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 ;)
- [Qemu-devel] [PATCH 01/13] allow qdev busses allocations be inplace, (continued)
[Qemu-devel] [PATCH 12/13] pci: move unregister from PCIDevice to PCIDeviceInfo, Gerd Hoffmann, 2009/09/22
[Qemu-devel] [PATCH 09/13] Add exit callback to DeviceInfo., Gerd Hoffmann, 2009/09/22