On 2017-07-09 23:57, David C. Rankin wrote:
On 07/08/2017 11:25 AM, Carlos E. R. wrote:
When you hibernate a machine you can not mount the partitions it had opened in any other operating system, nor in another instance of the same operating system. You need to awake the hibernated system, then
I'm glad Carlos snapped to what was going on... I was still scratching my head wondering what the heck Sudhir was talking about. I dual-boot (just because I happen to have 2 separate drives in the laptop and left the Win10 SSD alone when I installed Leap).
I would NEVER, not in a MILLION YEARS, have considered trying to dual-boot when one OS was hibernated. That is just such a bizarre thought in my world it never occurred to me what Sudhir was actually talking about.
Why bizarre? It seems a very normal thing to want to do and I have done it. One is working on one system, now wants to do something else on the other system, so hibernate the current system because it preserves the status, and boot to the other. I have done it. It is nice. Grub/lilo will not allow it, but there are tricks to let it allow the thing. The problem is trying to use hibernated filesystem on the other system. The corruption that results is horrible (specially if both are Linux). The system that boots sees the filesystem as not closed properly, so runs fsck on it. When you restore the hibernated filesystem, it expects the filesystem as it left it, and has a memory image of open files that are now closed, and writes things as if it was still holding the previous state. Horrible. The result is horrible. Better format and restore from backup. The good news is that it is possible to know that NTFS is in hibernated state, and Linux knows it and refuses to mount that disk, so it is not corrupted. But not such a thing with Linux filesystems.
I don't know why, but it just seems like common-sense that you fully shutdown one OS before trying to boot another -- maybe that's just me... (and a one reason I will not allow grub to touch the win10 drive, relying on 'Select Boot Device' from the BIOS to chose which drive to boot)
To me it seems reasonable to expect that technology would know how to do it :-) (no, I know that this is not possible and why)
Virtualbox of KVM is the way to go to virtualize windows within Leap. You want to run windows? just start it like another application. You can even create a .desktop file that launches the vboxmanage commandline. I've even got to where I virtualize windows on my server and give it 2-cores and 4GB of ram. I access it via rdesktop -- even over wifi it is fine (not snappy, but fine).
Good for you. My Windows laptop has only 4 GiB, so I can at most give 2 GiB to the other system, making the current one run slow. And running the other system in a window, which is what I prefer to do, gives it too little screen space in a laptop. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)