search for: 166500

...80] css_evaluate_known_subchannel at 4d2cc0 #35 [163f7be0] slow_eval_known_fn at 4d3cea #36 [163f7c10] bus_for_each_dev at 45ea56 #37 [163f7c50] for_each_subchannel_staged at 4d337e #38 [163f7c98] css_slow_path_func at 4d3450 #39 [163f7cc0] process_one_work at 164ff4 #40 [163f7d60] worker_thread at 166500 #41 [163f7da8] kthread at 16e67c #42 [163f7eb0] kernel_thread_starter at 6b0a5e Removing a disk while writing to it now ends up mostly with errors (which is new behavior and good). However, the detached device is still listed under /dev, and a subsequent umount ends up in a hang. Latter also occu...

...80] css_evaluate_known_subchannel at 4d2cc0 #35 [163f7be0] slow_eval_known_fn at 4d3cea #36 [163f7c10] bus_for_each_dev at 45ea56 #37 [163f7c50] for_each_subchannel_staged at 4d337e #38 [163f7c98] css_slow_path_func at 4d3450 #39 [163f7cc0] process_one_work at 164ff4 #40 [163f7d60] worker_thread at 166500 #41 [163f7da8] kthread at 16e67c #42 [163f7eb0] kernel_thread_starter at 6b0a5e Removing a disk while writing to it now ends up mostly with errors (which is new behavior and good). However, the detached device is still listed under /dev, and a subsequent umount ends up in a hang. Latter also occu...

Noniko, I saw your posting titled "SUSE10.1 has a nice Xen package again" and I was wondering if you had found any documentation on how to run Fedora Core 5 on top of SUSE10.1. Did you build the Fedora environment on a separate Fedora machine and then brought it over to the SUSE machine or did you find the Fedora tools (Yum/Anaconda) on SUSE? Many thanks in advance. Jose Betancourt

...nel at 4d2cc0 > #35 [163f7be0] slow_eval_known_fn at 4d3cea > #36 [163f7c10] bus_for_each_dev at 45ea56 > #37 [163f7c50] for_each_subchannel_staged at 4d337e > #38 [163f7c98] css_slow_path_func at 4d3450 > #39 [163f7cc0] process_one_work at 164ff4 > #40 [163f7d60] worker_thread at 166500 > #41 [163f7da8] kthread at 16e67c > #42 [163f7eb0] kernel_thread_starter at 6b0a5e > > Removing a disk while writing to it now ends up mostly > with errors (which is new behavior and good). > However, the detached device is still listed under /dev, and a > subsequent umount e...

...35 [163f7be0] slow_eval_known_fn at 4d3cea >> #36 [163f7c10] bus_for_each_dev at 45ea56 >> #37 [163f7c50] for_each_subchannel_staged at 4d337e >> #38 [163f7c98] css_slow_path_func at 4d3450 >> #39 [163f7cc0] process_one_work at 164ff4 >> #40 [163f7d60] worker_thread at 166500 >> #41 [163f7da8] kthread at 16e67c >> #42 [163f7eb0] kernel_thread_starter at 6b0a5e >> >> Removing a disk while writing to it now ends up mostly >> with errors (which is new behavior and good). >> However, the detached device is still listed under /dev, and a &...

...35 [163f7be0] slow_eval_known_fn at 4d3cea >> #36 [163f7c10] bus_for_each_dev at 45ea56 >> #37 [163f7c50] for_each_subchannel_staged at 4d337e >> #38 [163f7c98] css_slow_path_func at 4d3450 >> #39 [163f7cc0] process_one_work at 164ff4 >> #40 [163f7d60] worker_thread at 166500 >> #41 [163f7da8] kthread at 16e67c >> #42 [163f7eb0] kernel_thread_starter at 6b0a5e >> >> Removing a disk while writing to it now ends up mostly >> with errors (which is new behavior and good). >> However, the detached device is still listed under /dev, and a &...

Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, 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. Additionally a potential

Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, 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. Additionally a potential