This bug seems to be fixed by moving the kernel and the ramdisk for domUs up to 2.6.24-17. Can anyone else verify this?
This bug seems to be fixed by moving the kernel and the ramdisk for domUs up to 2.6.24-17. Can anyone else verify this?