[Solved] VBOX OK on Desktop - Fails on Laptop

Discussions related to using VirtualBox on Linux hosts.
Post Reply
MikeGreen9
Posts: 22
Joined: 9. Mar 2023, 22:20
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Windows 10
Location: Ontario, Canada

[Solved] VBOX OK on Desktop - Fails on Laptop

Post by MikeGreen9 »

Hi.

I am unable to run VirtualBox VM 6.1.50 Windows 10 on my ubuntu 22.04 ASUS laptop.

On my ubuntu 22.04 Desktop, I have the Virtual Box files (VBox WIN10.vbox, VBox WIN10.vdi, etc.) on a separate ntsf partition. Virtual Box WIN10 runs perfectly on my Desktop.

I have built an ESATA that is an exact copy of my ubuntu 22.04 Desktop, including the Virtual Box partition.

I boot the ESATA on my Desktop with all other drives BIOS disabled, mount the Virtual Box partition, and Virtual Box runs like a charm.

I have an ASUS Expertbook laptop which is a dual boot WIN11/ubuntu system. The ubuntu part (the good part) is an RSYNC'd copy of my ubuntu Desktop, and performs identically.

All good up to here

I plug the ESATA copy of my Desktop into my ASUS laptop via an ESATA to USBC cable.
I boot the ASUS and mount the Virtual Box ESATA partition. When I attempt to run Virtual Box it fails. The log file says:
"Oracle VM VirtualBox Extension Pack (Version: 7.0.6 r155176; VRDE Module: VBoxVRDP unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x50000 got 0x30000'')"

It states there is a 'version mismatch' which makes no sense to me. The same version of ubuntu and Virtual Box works on my Desktop, but not on my ASUS ??

The log also says that 3 of the Virtual Box File system are unknown (yet they are known on my Desktop).
"00:00:00.677477 File system of '/media/mg/Virtual Box WIN7/VBox7 WIN10/VBox WIN10/Snapshots' (snapshots) is unknown
00:00:00.677485 File system of '/media/mg/Virtual Box WIN7/VBox7 WIN10/VBox WIN10/VBox WIN10.vdi' is unknown
00:00:00.681065 File system of '/usr/share/virtualbox/Windows 10 Version 1909 untouched ISO [TheWindowsForum].iso'
"

For the record, I executed the following commands on the ASUS:
sudo apt update
sudo apt install --reinstall virtualbox-dkms
sudo modprobe vboxdrv

This made no difference.

Any ideas ?

Thanks,
M....
Last edited by MikeGreen9 on 13. Jan 2025, 23:32, edited 2 times in total.
multiOS
Volunteer
Posts: 1305
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux, BSD
Location: United Kingdom

Re: VBOX OK on Desktop - Fails on Laptop

Post by multiOS »

VirtualBox Host installation and Extension Pack versions must match so, if you have an old (and unsupported) VirtualBox 6.1.50 version installed on your Ubuntu Laptop, then it's naturally going to experience compatibility issues if you present it with a VM that was built to be compatible with a PC which has a later. and significantly different, VirtualBox 7.0.6 installation and Extension Pack version. That is what the error message is telling you.

The other 'errors' relate to file path differences between the two systems that work against direct VM portability, i.e. you need to ensure that the file paths used on both systems are consistent (match exactly).
Last edited by multiOS on 8. Jan 2025, 00:43, edited 4 times in total.
granada29
Volunteer
Posts: 815
Joined: 3. Mar 2015, 07:27
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: Linux, macOS, Windows

Re: VBOX OK on Desktop - Fails on Laptop

Post by granada29 »

Probably out of my depth here - but does your laptop have NTFS drivers installed? i.e. will the host system have read/write access to the file system containing your VM?
MikeGreen9
Posts: 22
Joined: 9. Mar 2023, 22:20
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Windows 10
Location: Ontario, Canada

Re: VBOX OK on Desktop - Fails on Laptop

Post by MikeGreen9 »

Hi and thanks for the prompt responses.

Yes the ASUS supports NTFS.

The paths are identical as far as I can see. The ESATA VBox partition is an exact image of the Desktop VBox partition, label and all.

So to continue with the ongoing saga -
I booted the Desktop. I plunked the ESATA back into the Desktop. I mount the VBox partition on the ESATA, and started VBoxWIN10 . Worked like a charm.

So 2 identical ubuntus, and the same identical exact VBox partition, runs just fine on my Desktop, but fails on the ASUS.
The only difference is the hardware and the BIOS. How does this explain the error messages that I am getting?

Thanks,
M....
MikeGreen9
Posts: 22
Joined: 9. Mar 2023, 22:20
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Windows 10
Location: Ontario, Canada

Re: VBOX OK on Desktop - Fails on Laptop

Post by MikeGreen9 »

Hi Again.

I have found a subtle difference.

I have gparted running on both my Desktop & the ASUS.

The VM paths are identical except the ASUS has 'msftdata' under 'Flags' - my Desktop has the 'Flags' field blank. Both are ntfs.

Maybe this is the "File System Unknown' message in the log ??

I will delete/reallocate the laptop VM partition, and copy the VM onto it from my Dekstop. 50gb onto a USB will take a while.

I will keep you posted.

Thanks,
M...
BeckettRivera
Posts: 4
Joined: 10. Oct 2024, 13:33

Re: VBOX OK on Desktop - Fails on Laptop

Post by BeckettRivera »

The error occurs due to a mismatch between VirtualBox (6.1.50) and the Extension Pack (7.0.6) on your ASUS laptop. Update VirtualBox to version 7.0.6 from the official site for compatibility. Also, ensure consistent file paths between desktop and laptop to resolve "unknown file system" errors for seamless VM portability. Using Academized https://academized.com was one of the best decisions I made during a stressful semester. They helped me complete a challenging term paper, and the results were incredible. The writer demonstrated expertise in my field and included well-researched arguments and citations. The process was seamless, from placing the order to receiving the final draft. I highly recommend Academized to any student seeking high-quality and reliable academic writing services!
Last edited by BeckettRivera on 21. Jan 2025, 08:30, edited 1 time in total.
MikeGreen9
Posts: 22
Joined: 9. Mar 2023, 22:20
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Windows 10
Location: Ontario, Canada

Re: VBOX OK on Desktop - Fails on Laptop

Post by MikeGreen9 »

Hi.

I upgraded VirtualBox to 7.1.4 on both machines. I immediately noticed that this time, VirtualBox got a lot farther than on the old rev. WIN10 actually came up and started to display the WIN10 Desktop and it's icons - and then aborted. Comparing VirtualBox logs from both machines, seems to indicate that video may be a part of the problem.

On the ASUS:
Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007e68b0000000 w=1280 h=720 bpp=32 cbLine=0x1400 flags=0x1 origin=0,0

and that's the last line in the log file - it aborts at this point.

I previously stated that the only difference between the machines is Hardware.
The ASUS has a 4K screen, with a 1920 X1080 resolution, and 16gb memory.
The Desktop is not a 4K screen, with a 1360 X 768 resolution, and 32gb memory.

So I made some changes to the ASUS
I changed the ASUS resolution to 1360 X 768, and in VirtualBox, the graphics controller to VBoxSVGA (from VBoxVGA).

AND

I also changed the ASUS VirtualBox Base memory to 8k (down from 16k).

AND it works !! I'm not sure which of the changes did it, but right now I don't care. I've been at this for several days, and I'm just so pleased.



I do have one question - I noticed that on BOTH machines, if I attempt to move the WIN10 desktop screen, the WIN10 desktop starts to flicker and SHRINK continually. (Video memory is at max for both machines.) Any ideas what is causing this ?

Thanks for listening,
M....
MikeGreen9
Posts: 22
Joined: 9. Mar 2023, 22:20
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Windows 10
Location: Ontario, Canada

Re: VBOX OK on Desktop - Fails on Laptop

Post by MikeGreen9 »

I guess no one is listening.

Anyways, for the record, I fixed the shrinking screen in Virtual Box Settings - User Interface - and set 'Visual State' to Scaled.

I will attempt to mark this Post as solved.

Thanks,
M...
Post Reply