I though, that disabling HIGHMEM and running <256MB ram guests helped. But that was yesterday. Today I had to 20x start/kill the guest before he went up (2.6.15-rc7 skas0).
But YES, you can call it a "better result" because I didn`t give up until it started :-) I don`t understand it at all :-/ How much memory is recomended for a guest? And why has the maschine been running with 2.6.11.12 6 months fine, until this christmas when some guy (me) had the crazy idea of a new kernel :-) Am Montag, den 26.12.2005, 19:15 +0100 schrieb Blaisorblade: > On Sunday 25 December 2005 21:33, Juraj Holtak wrote: > > Hello, > > > > it looks like i`ve found a workaround good enough for me. > > > > I discovered, that the problem is only present, when I boot a guest with > > more than 256MB of ram enabled. I spread my services to more guests (7 > > instead of 5) with <256MB ram. I tested all the kernels I have compiled > > before and had no problems at all. Even the newest 2.6.15-rc7 does the > > job fine in skas0 mode. > > Can you verify if disabling CONFIG_HIGHMEM in the kernel configuration and > recompiling the kernel yields a better result, even with big amounts of RAM? > > In this case, it's in the class of "don't do this" bugs, even if it's not at > all documented clearly enough. > > [42949387.540000] a18c378c: [<a0076dde>] kunmap_high+0x1e/0xb0 > [42949387.540000] a18c379c: [<a002686c>] maybe_map+0x9c/0xc0 > [42949387.540000] a18c37ac: [<a003ca47>] kunmap+0x47/0x80 > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
