gentoo shutdowns instead of rebooting?
–
Oct 15 14:30:09 ln shutdown[17350]: shutting down for system reboot
–
6 Replies
If you don't want to wait for Lassie, you can initiate the reboot from the Linode Manager or within a Lish session.
newark18 - works as expected
newark35, newark65 - doesn't start after reboot.
The same Gentoo image. So I guess it has smth to do with newer server configs.
Will be getting to lish later.
The last message I see before screen terminates is that the system will be rebooted.
'reboot' and such in Linux will communicate to the kernel that a warm reboot is to be attempted. In our environment, there's no such thing. When you issue 'reboot', your guest domain goes away, and Lassie will jump in and issue a boot job to your Linode.
It's all the same to our system. Your domU was there, and then it wasn't. I don't think we know if you issued a 'reboot' from your Linode, because it probably tries to fire ACPI commands for a warm reset…which Xen might completely ignore.
These are all guesses, but educated ones. My suspicion is that 'reboot' is blindly saying "warm reset, please", Xen is ignoring it, and destroying the domain. This is probably why when you issue a reboot to your Linode from the Linode Manager, you get a "shutdown" job and a "boot" job.
(Aside: Higher host numbers aren't necessarily indicative of newer software. In this particular case, newark18 actually has "newer" software than newark35. We probably rebooted it at some point. Edit: Yep