-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimeoutStartUSec too low, or MicroVMs taking a little while be to start #317
Comments
It seems to me the machines are probably quite close to having come up, their consoles say things like 'Reached target Multi-User System'. Another thing which is suspicious is that the amount of CPU time consumed is very low, only 8 seconds during the 1m30
I do also see a suspicious message about flushing journal persistant storage, and some time spent waiting in systemd:
The machines are configured so hat their journals are written onto the host's storage and can be observed from there. I'm wondering if there is something wrong with this:
|
One more observation on this particular machine: I looked at the systemd message timings inside one of the microvms, and noticed the "Switch Root" taking ~21s: An additional piece of meta-information: This server is not of the most recent build (Xeon E3-1245 V2 @ 3.40GHz) and (currently) uses btrfs on cryptsetup on two disks of spinning rust for the journals and data. |
The timeout could be turned into an option in the host module. I am just lucky to not have run into this yet. 55 MicroVMs on our 2013 hardware start within 90s. |
I have a machine with (less than 10) microvms on it. When the machine is rebooted daily, the log looks like:
My first read of what appears to be happening is that the machines take a fair amount of CPU time before they are considered 'up' to systemd, and if they don't become up within the default time limit of 1m30s, they are terminated and restarted. Eventually this process settles down.
What doesn't quite add up for me is that I think there should be enough CPU available for this to all happen.
Some questions:
The text was updated successfully, but these errors were encountered: