On Mon, Dec 3, 2012 at 10:37 AM, Yeela Kaplan wrote:
Glad to hear it worked out.
When oVirt started the vm it mounted the corrupt disk image that seemed fine,
but it couldn't find the OS because of the corrupted fs,
and the error caused it to pause the guest.
But if this is the case, I think this should be considered as a bug, correct?
The VM should start and give an error itself, such as stopping at
grub, error on pivot_root, panic, ecc...
without impact on its ability to power on itself...
or not?