[EMAIL PROTECTED] said:
> How do I handle the "mtime mismatch (1079561920 vs 1102205165) of COW
> header vs backing file" issue? Should I "touch" the two files involved
> to match up mtimes? Ideas?
That's a sanity check to make sure that you don't try to put a COW file over
a backing file which ha
More info on the guest system kernel panics ... here is some relevant
dmesg output:
Using anticipatory io scheduler
mtime mismatch (1079561920 vs 1102205165) of COW header vs backing file
/dev/ubd/disc1: unknown partition table
Initializing stdio console driver
VFS: Cannot open root device "98:0"
