[libvirt] [PATCH 3/3] qemu: Auto-generate controller for hotplugged hostdev

2013-11-20 Thread Eric Farman
If a SCSI hostdev is included in an initial domain XML, without a corresponding controller statement, one is created silently when the guest is booted. When hotplugging a SCSI hostdev, a presumption is that the controller is already present in the domain either from the original XML, or via an ear

[libvirt] [PATCH 3/3] qemu: Auto-generate controller for hotplugged hostdev

2013-11-12 Thread Eric Farman
If a SCSI hostdev is included in an initial domain XML, without a corresponding controller statement, one is created silently when the guest is booted. When hotplugging a SCSI hostdev, a presumption is that the controller is already present in the domain either from the original XML, or via an ear

Re: [libvirt] [PATCH 3/3] qemu: Auto-generate controller for hotplugged hostdev

2013-11-11 Thread Ján Tomko
On 10/08/2013 02:45 PM, Eric Farman wrote: > If a SCSI hostdev is included in an initial domain XML, without a > corresponding controller statement, one is created silently when the > guest is booted. > > When hotplugging a SCSI hostdev, a presumption is that the controller > is already present in

[libvirt] [PATCH 3/3] qemu: Auto-generate controller for hotplugged hostdev

2013-10-08 Thread Eric Farman
If a SCSI hostdev is included in an initial domain XML, without a corresponding controller statement, one is created silently when the guest is booted. When hotplugging a SCSI hostdev, a presumption is that the controller is already present in the domain either from the original XML, or via an ear

[libvirt] [PATCH 3/3] qemu: Auto-generate controller for hotplugged hostdev

2013-09-26 Thread Eric Farman
If a SCSI hostdev is included in an initial domain XML, without a corresponding controller statement, one is created silently when the guest is booted. When hotplugging a SCSI hostdev, a presumption is that the controller is already present in the domain either from the original XML, or via an ear