virtualbox.org

I recently found that my Win7Pro VM had quit working following an upgrade of my Linux Kernel from 4.15.0-70 to 5.3.0-22. I was able to get everything working again by dropping back to kernal 5.3.0-19 and installing VB 6.0.14 along with the accompanying Extension Pack and Guest additions.

My question is, now that I have installed VB 6.0.14 can I safely update my Linux Kernel within the 5.3.X series without losing the use of my VM's. My use of Linux has grown to such a degree that I have learned not to fear updating my kernel, and that new kernels often remedy problems or provide greater functionality. Consequently I like to keep my kernal current within a given series (5.3.X in my case).

Thanks in advance,

Robert Brown

rpbrown wrote:can I safely update my Linux Kernel within the 5.3.X series without losing the use of my VM's.

Being a Windows guy, I wouldn't know Linux-wise what's safe and what's not. But I know backup-wise that anything is safe if you have a good restorable backup or three.

Make and know how to restore multiple multi-format backups, have another drive you can clone to, etc. Then paint the town vermilion. Anything goes wrong, restore.

@'rpbrown'
First of all, I edited your post to replace all "Kernal" instances to "Kernel". Call it <something> syndrome, I simply couldn't stand looking at that typo, it was driving me nuts...

Second, I'm moving the thread from "Using VirtualBox" to "Linux Hosts". Your question is not a generic one, but a really specific Host question.

Third:

rpbrown wrote:can I safely update my Linux Kernel within the 5.3.X series without losing the use of my VM's

Your Host's kernel version has nothing to do with your VMs, same as your LibreOffice version has nothing to do with your spreadsheets.

If you upgrade your kernel, VirtualBox shouldn't stop working, I do it all the time. I don't know what failed in your case, because you didn't tell us a single thing about it, and I really hate guessing...

But, as a general rule of thumb, if you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. Download the latest VirtualBox. If that doesn't work you should try the latest test builds. If in doubt, always ask around before performing the upgrade...

scottgus1 wrote:Being a Windows guy, I wouldn't know Linux-wise what's safe and what's not.

Being an OSX/Windows and a Linux guy lately, I can tell you that I've never hesitated, or even thought about doing an upgrade on Linux/OSX. I've never, ever had anything break. Not the case with Windows updates...

scottgus1 wrote:Make and know how to restore multiple multi-format backups, have another drive you can clone to, etc.

Hallelujah!!! I don't know what Linux Host the OP is using, but on my Mint 19 Linux Host, there are a couple of built-in, failsafe mechanisms:

• At boot time I can boot into a previous kernel.
• They have introduced a "Snapshot" mechanism for the OS, something similar to what Windows has, but much more smoother and faster under the hood.

So, if things go haywire, I can always save the day really quickly...

socratis wrote:I've never, ever had anything break. Not the case with Windows updates...

True. Oh, how painfully true...

Oops, I apologize for the misspelling of kernel!

It's true that I did not think to include the text of the error message that appeared when trying to start my Win7Pro VM. It mentioned several files as being either missing or not able to be located. I assumed that the problem was related to the kernel upgrade since that was the only thing I had changed before things stopped working.

I find the clarity of hindsight absolutely amazing! When it all hit the fan, I actually gave up after several hours of tinkering and just created a new VM from scratch. Once created, I exported the VM twice; once with nothing extra installed, just a complete working installation of Windows 7, and then again with the two apps I need to run installed and working.

So you think that the kernel version should not affect the operation of my VM? That makes sense. I suppose the cure I was able to effect had to do with the update to VB 6.0.14.

Now that I have copies of everything stored, I'll try the next maintenance upgrade to my present kernel and see what happens.

Thanks for the advice and input.

rpbrown wrote:It mentioned several files as being either missing or not able to be located

This is definitely not a kernel problem. Unless those files were located in a non-standard location that required some special filesystem driver.

rpbrown wrote:I assumed that the problem was related to the kernel upgrade since that was the only thing I had changed before things stopped working.

I think it was a coincidence. But without the error, having me guessing is rather moot at this point...

Marking as [WorksForMe].

5.3.11 works for me

5.4.0-rc7+ as well once I built the headers

MasterCATZ wrote:once I built the headers

Built the headers? How does one exactly build the headers?