search for: 53c895a

Hi all, trying to edit a domain xml to enable an LSI SCSI controller I get the following error: error: unsupported configuration: This QEMU doesn't support the LSI 53C895A SCSI controller It is my understanding that the error is raised due to RedHat disabling this controller in its own qemu-kvm builds. This seems an unfortunate decision, as it makes harder to migrate from VMWare (which uses LSI SCSI and SAS adapters) to RH+KVM. Can anyone elaborate on this decis...

On Sat, 2018-09-29 at 15:02 +0200, Gionatan Danti wrote: > Hi all, > trying to edit a domain xml to enable an LSI SCSI controller I get the > following error: > > error: unsupported configuration: This QEMU doesn't support the LSI > 53C895A SCSI controller > > It is my understanding that the error is raised due to RedHat disabling > this controller in its own qemu-kvm builds. This seems an unfortunate > decision, as it makes harder to migrate from VMWare (which uses LSI SCSI > and SAS adapters) to RH+KVM. > >...

On 02/10/2018 09:19, Andrea Bolognani wrote: > Your assessment looks correct, and the controller is indeed compiled > out downstream. Filing a BZ sounds like a reasonable next step, but > you might also want to investigate virt-v2v, which I believe will > take care of switching to the more performant virtio-scsi (including > installing the necessary drivers) for you when moving

...chas in this configuration that could prevent the > > virtualized guest to power on and boot up? > > > > > When I configure like this, from a linux guest point of view I get this > Symbios Logic SCSI Controller: > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a > > But htis is true only if you add the SCSI controller too, not only the disk > definition. > In my case > > <controller type='scsi' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' &g...

...; > > Do you see any gotchas in this configuration that could prevent the > virtualized guest to power on and boot up? > > When I configure like this, from a linux guest point of view I get this Symbios Logic SCSI Controller: 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a But htis is true only if you add the SCSI controller too, not only the disk definition. In my case <controller type='scsi' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </...

...> > > virtualized guest to power on and boot up? >> > > >> > > >> > When I configure like this, from a linux guest point of view I get this >> > Symbios Logic SCSI Controller: >> > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a >> > >> > But htis is true only if you add the SCSI controller too, not only the >> disk >> > definition. >> > In my case >> > >> > <controller type='scsi' index='0'> >> > <address type='pci&...

...t could prevent the > > > virtualized guest to power on and boot up? > > > > > > > > When I configure like this, from a linux guest point of view I get this > > Symbios Logic SCSI Controller: > > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a > > > > But htis is true only if you add the SCSI controller too, not only the > disk > > definition. > > In my case > > > > <controller type='scsi' index='0'> > > <address type='pci' domain='0x0000' bus...

...t could prevent the > > > virtualized guest to power on and boot up? > > > > > > > > When I configure like this, from a linux guest point of view I get this > > Symbios Logic SCSI Controller: > > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a > > > > But htis is true only if you add the SCSI controller too, not only the > disk > > definition. > > In my case > > > > <controller type='scsi' index='0'> > > <address type='pci' domain='0x0000' bus...

...chas in this configuration that could prevent the > > virtualized guest to power on and boot up? > > > > > When I configure like this, from a linux guest point of view I get this > Symbios Logic SCSI Controller: > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a > > But htis is true only if you add the SCSI controller too, not only the disk > definition. > In my case > > <controller type='scsi' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' >...

...> > > virtualized guest to power on and boot up? >> > > >> > > >> > When I configure like this, from a linux guest point of view I get this >> > Symbios Logic SCSI Controller: >> > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a >> > >> > But htis is true only if you add the SCSI controller too, not only the >> disk >> > definition. >> > In my case >> > >> > <controller type='scsi' index='0'> >> > <address type='pci&...

When user hot-unplug a disk which is busy serving I/O, __blk_run_queue might be unable to drain all the requests. As a result, the blk_drain_queue() would loop forever and blk_cleanup_queue would not return. So hot-unplug will fail. This patch adds a callback in blk_drain_queue() for low lever driver to abort requests. Currently, this is useful for virtio-blk to do cleanup in hot-unplug. Cc:

When user hot-unplug a disk which is busy serving I/O, __blk_run_queue might be unable to drain all the requests. As a result, the blk_drain_queue() would loop forever and blk_cleanup_queue would not return. So hot-unplug will fail. This patch adds a callback in blk_drain_queue() for low lever driver to abort requests. Currently, this is useful for virtio-blk to do cleanup in hot-unplug. Cc:

...>>>> > > >>>> > > >>>> > When I configure like this, from a linux guest point of view I get >>>> this >>>> > Symbios Logic SCSI Controller: >>>> > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a >>>> > >>>> > But htis is true only if you add the SCSI controller too, not only >>>> the disk >>>> > definition. >>>> > In my case >>>> > >>>> > <controller type='scsi' index='0...