search for: inclomplete

...n't affect the remove callback. The weird situation, however, is solved by the new notify callback. Doing it in blk_cleanup_queue() (also triggered from virtblk_remove()) is too late for this scenario of a lost device. One wouldn't see any errors, but experience a 'hang' due to inclomplete I/O. The invocation of virtblk_request() indirectly caused by del_gendisk() would accept requests, the subsequent host notification, however, would fail. (This is probably another 'window' that should be closed.) > > >> Heinz Graalfs (3): >> virtio: add notify() cal...

...n't affect the remove callback. The weird situation, however, is solved by the new notify callback. Doing it in blk_cleanup_queue() (also triggered from virtblk_remove()) is too late for this scenario of a lost device. One wouldn't see any errors, but experience a 'hang' due to inclomplete I/O. The invocation of virtblk_request() indirectly caused by del_gendisk() would accept requests, the subsequent host notification, however, would fail. (This is probably another 'window' that should be closed.) > > >> Heinz Graalfs (3): >> virtio: add notify() cal...

...emove callback. The weird situation, > however, is solved by the new notify callback. > Doing it in blk_cleanup_queue() (also triggered from > virtblk_remove()) is too late for this scenario of a lost device. > One wouldn't see any errors, but experience a 'hang' due to > inclomplete I/O. The invocation of virtblk_request() indirectly > caused by del_gendisk() would accept requests, the subsequent host > notification, however, would fail. (This is probably another > 'window' that should be closed.) I see. All this makes sense. So it's really important tha...

Hi all, I compiled and installed Xen 3.2 source on FC8. Compilation and installation completed with no errors. However when I try to load Xen I get an error: Kernel panic - Attempted to kill init !!! This is my grub configuration: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means

Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z there exists no handshake mechanism between host and guest when a device

Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z there exists no handshake mechanism between host and guest when a device