Michael S. Tsirkin wrote: > This will be 2.6.18 material, right? I want to get some wider testing of the patch before pushing upstream, but I consider this a bug fix that we should try to push into 2.6.18. - Sean