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" or unknown-block(98,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(98,0)
<6>SysRq : Show Regs
EIP: 0073:[<a01ebba1>] CPU: 0 Not tainted ESP: 007b:b7ffefb0 EFLAGS:
00000286
Not tainted
EAX: 00000000 EBX: 00002150 ECX: 00000013 EDX: 00002150
ESI: 00000000 EDI: 00000000 EBP: b7ffefbc DS: 007b ES: 007b
Call Trace: [<a0163a05>] [<a001dc5b>] [<a004782d>] [<a003907b>]
[<a0003049>]
[<a00032e9>] [<a000f5f0>] [<a000333d>] [<a0002616>] [<a000f5f0>]
[<a0024270>]
[<a000f5f0>] [<a0024270>] [<a000f61d>] [<a01eb840>] [<a000f5f0>]
[<a0017e19>]
[<a000f5f0>] [<a0024270>] [<a0017dfe>] [<a001ad72>] [<a0035247>]
[<a000f5f0>]
[<a0024270>] [<a002431e>] [<a000f5f0>] [<a01ebaf8>] [<a0024270>]
[<a002438d>]
[<a020286d>]
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? Thanks.
geoffrey
--
As democracy is perfected, the office represents, more and more closely,
the inner soul of the people. We move toward a lofty ideal. On some
great and glorious day the plain folks of the land will reach their
heart's desire at last, and the White House will be adorned by a
downright moron.
H. L. Mencken
The Baltimore Sun, 26 July 1920
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
