I recently upgraded my F11 machine to the latest F13 and now found that booting UML machines takes much longer than before. I use the VNUML¹ script and it only works if I increase the boot timeout to about 100 seconds.
I took the latest F11 kernel (22.214.171.124-105.2.23.fc11.i586) and manually installed it on the system. It does not load X11 (incompatibility with the intel driver maybe?) but running UML machines from the console works fine and is fast.
I then tried the latest F12 kernel, it boots into X11 but it has the same problem as the current F13 kernel.
I wonder what changed between kernel 2.6.30 and 2.6.32 which could cause this?
You could try an older F-12 2.6.31 kernel to further narrow down the problem.
Thanks for the hint. Using kernel-126.96.36.199-174.fc12 (latest .31 I could find), it still seems to work fine!
Small update: a collegue is using sabayon linux with kernel 2.6.33 and UML works fine for him. So either sabayon has this already patched, some fedora specific patch causes the problem in the first place or there is some bad fedora kernel <-> userland interaction going one here...
In order to give some numbers how bad this is, I did a minimal test (booting and shutting down a single VM) with the linux-188.8.131.52-bb2-xt-4m UML kernel and root_fs_tutorial-0.5.2 from :
Created attachment 410034 [details]
Log of first run (fast)
Created attachment 410035 [details]
Log of second run (slooooow)
If you run a diff, there are no additional error messages or anything like that in the slow log.
Please tell me if I can provide any more information.
Update regarding comment 3: it does *not* work fine on Sabayon using its .33 kernel. It's much slower there, too (but it was not as obvious as the hardware is much faster on this box).
So, this is very likely a bug in the upstream kernel after all.
Another update: looks like the disastrous performance with 184.108.40.206-24.fc13.i686 was mainly caused by kernel debugging being active. The current F13 kernel performs better, while the debug build performs similar to 220.127.116.11-24.fc13.i686:
18.104.22.168-85.fc13.i686 - 1:12.05
22.214.171.124-85.fc13.i686.debug - 2:38.96
This also shows that 126.96.36.199-85.fc13.i686 is still about 3 times slower than 2.6.31.*
A few more numbers (running the same simple test):
188.8.131.52-174.2.22.fc12.i686 - 0:23.40 // last .31 kernel for F12
184.108.40.206-13.fc12.i686 - 1:11.56 //first .32 kernel for F12
220.127.116.11-115.fc12.i686 - 1:10.72 // last .32 kernel for F12
I can reproduce this all the time, so the regression has to be somewhere between 18.104.22.168 and 22.214.171.124, most likely just 2.6.31->2.6.32
126.96.36.199-112.fc13.i686 - 0:50.64
So, latest F13 kernel seems to be ~20 seconds faster, meaning it now "only" takes about twice the time to complete the test. No idea what change caused the improvement.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I'm wondering if this is related to the utrace patch we carry.
Is it still occuring with the 188.8.131.52 updates ?