[opensuse] Can an hibernated system be started (thawed) using a different kernel.
Hi, Say I hibernate Leap (it is a multiboot machine). Say on restore I boot 13.1, which as it shares the same swap, would see there is an hibernated image in swap and try it. But... would it be restored properly, or would something terrible happen? Obviously, I don't want to try it on real hardware. Perhaps on a virtual one. But perhaps this is known to work, or to not work :-? -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/07/2015 07:54 PM, Carlos E. R. wrote:
Hi,
Say I hibernate Leap (it is a multiboot machine). Say on restore I boot 13.1, which as it shares the same swap, would see there is an hibernated image in swap and try it. But... would it be restored properly, or would something terrible happen?
Obviously, I don't want to try it on real hardware. Perhaps on a virtual one. But perhaps this is known to work, or to not work :-?
I have not tried this on purpose either, but I think it has happened to me a couple times and the system detected that the image in swap was not valid for the system being booted. It simply reverts to a fresh boot, which will destroy (overwrite) your swap image, an you loose any work in progress in the swap image. I don't know what constitutes the signature of that suspend file in swap. See this page: http://unix.stackexchange.com/questions/123547/can-swap-be-shared-safely-whi... -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-11-08 07:07, John Andersen wrote:
On 11/07/2015 07:54 PM, Carlos E. R. wrote:
I have not tried this on purpose either, but I think it has happened to me a couple times and the system detected that the image in swap was not valid for the system being booted.
Ah! So there is a signature. Yes, make sense. I think I remember reading about it.
It simply reverts to a fresh boot, which will destroy (overwrite) your swap image, an you loose any work in progress in the swap image.
Ugh. It should revert to "abort", or "ask".
I don't know what constitutes the signature of that suspend file in swap.
See this page: http://unix.stackexchange.com/questions/123547/can-swap-be-shared-safely-whi...
Yes, a different swap would work (partially), except that it is not my workcase :-) (partially, because I would probably mount partitions that are already opened, and dirty, on the "other" boot, so they would be fsck-ed. And when later starting the hibernated partition, this would try to use the sleeping partitions, with files in opened state, but which was fsck-ed... The result is horrible corruption, I can tell you. It happened to me, quite some years ago.) My use case is that I simply have a multiboot machine, and one of the boots is the default, but that one may not be the one I last used and which I want again. I can not use hibernate on the other boots unless I remember to select it the next time. Which I probably will not :-} -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
08.11.2015 13:00, Carlos E. R. пишет:
My use case is that I simply have a multiboot machine, and one of the boots is the default, but that one may not be the one I last used and which I want again.
I can not use hibernate on the other boots unless I remember to select it the next time. Which I probably will not :-}
If you use openSUSE bootloader to control multiboot, it is expected to store current boot choice as one time next boot selection. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2015 05:23 PM, Andrei Borzenkov wrote:
If you use openSUSE bootloader to control multiboot, it is expected to store current boot choice as one time next boot selection.
I am not using it. But what is it? My boot sequence is MBR -> Grub 1 in extended (13.1) -> grub 2 in logical (42.1). -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
09.11.2015 02:14, Carlos E. R. пишет:
On 11/08/2015 05:23 PM, Andrei Borzenkov wrote:
If you use openSUSE bootloader to control multiboot, it is expected to store current boot choice as one time next boot selection.
I am not using it. But what is it?
My boot sequence is MBR -> Grub 1 in extended (13.1) -> grub 2 in logical (42.1).
Then yes, second level bootloader is probably unaware of choices in first level. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-11-09 04:20, Andrei Borzenkov wrote:
Then yes, second level bootloader is probably unaware of choices in first level.
Aha. Then it is what I thought, yes. You thought that I was booting the other system from the same master grub. With a single grub there would be no problem, it would be automatic. Understood. I thought you were referring to some other method of booting that I was unaware of. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
John Andersen