mintupdate 5.1.0.5
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
mintupdate 5.1.0.5
The changelog for this update is one line: "* Packaging: Break virtualbox-guest pkgs". I need some details.
I've had no problems without this update, so I have to ask the questions:
Is this update meant to "break" virtualbox-guest packages? -- whatever that means to the maintainer.
Or does this update fix/prevent virtualbox-guest packages breaking? -- whatever that means to the maintainer.
I need some explanation before I accept this update, and I need some motivation before I do it.
Thanks for whatever info you can provide.
I've had no problems without this update, so I have to ask the questions:
Is this update meant to "break" virtualbox-guest packages? -- whatever that means to the maintainer.
Or does this update fix/prevent virtualbox-guest packages breaking? -- whatever that means to the maintainer.
I need some explanation before I accept this update, and I need some motivation before I do it.
Thanks for whatever info you can provide.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: mintupdate 5.1.0.5
It will remove those problematic guest packages whose updates caused many systems to break last week. So I think in this case break should be read remove.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Hi Marziano. Thanks for helping.
Oh dear. Great timing. I just had to go from Win7 (on dead computer) to Win10 (on new computer). I finally get Win10 working and get VB working and now this.
Until I read something definitive, I'm not updating anything. Thanks for the heads-up.
PS: Before posting this reply, I did read some of the previous postings that seemed to be related, but I failed to mention that. But the postings I read were vague/cryptic/non-Cinnamon, so I'm in the dark.
What problematic guest packages? Do you have links to discussions of this?
Which updates?... whose updates ...
REMOVE ! ? ! ?...caused many systems to break last week. So I think in this case break should be read remove.
Oh dear. Great timing. I just had to go from Win7 (on dead computer) to Win10 (on new computer). I finally get Win10 working and get VB working and now this.
Until I read something definitive, I'm not updating anything. Thanks for the heads-up.
PS: Before posting this reply, I did read some of the previous postings that seemed to be related, but I failed to mention that. But the postings I read were vague/cryptic/non-Cinnamon, so I'm in the dark.
Last edited by markfilipak on Tue Apr 03, 2018 2:13 pm, edited 1 time in total.
Re: mintupdate 5.1.0.5
Here you go, this is just one of the threads:
viewtopic.php?f=47&t=266431
Here is what xenopeek wrote about it:
viewtopic.php?f=90&t=266478
viewtopic.php?f=47&t=266431
Here is what xenopeek wrote about it:
viewtopic.php?f=90&t=266478
Last edited by Sir Charles on Tue Apr 03, 2018 2:16 pm, edited 1 time in total.
Re: mintupdate 5.1.0.5
Surely not a very fortunate wording.
Regarding the motivation: I give you 3 reasons:
1. This update shall prevent your system to break. Isn't this motivation enough?
2. There get packages removed, which should never had been installed on first hand, they do and cannot do any good (from a few exceptions).
3. As long as you do not apply this update, you will never get any others. This is so, because an open update for the update manager disables all other updates from display; this is done by design.
Regarding the motivation: I give you 3 reasons:
1. This update shall prevent your system to break. Isn't this motivation enough?
2. There get packages removed, which should never had been installed on first hand, they do and cannot do any good (from a few exceptions).
3. As long as you do not apply this update, you will never get any others. This is so, because an open update for the update manager disables all other updates from display; this is done by design.
Re: mintupdate 5.1.0.5
@markfilipak
I am sorry for not having wrapped it up more nicely. I am a man of coarse words
But my account of the havoc that was wreaking last week is accurate, however you want to put it.
I am sorry for not having wrapped it up more nicely. I am a man of coarse words
But my account of the havoc that was wreaking last week is accurate, however you want to put it.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Thanks all, but I'm still unsure/confused...
As my sig-line says: "Windows 10 {VirtualBox {Linux Mint 18 {Cinnamon Desktop} } }".
From the reports, I can't tell whether the Mint systems affected are running Mint as stand-alone, as a VirtualBox host, or as a VirtualBox guest.
In my case, I'm running Mint as a guest.
'inxi -Fxz' reports (in part):
The 'Machine' stuff above makes no sense to me. Here's what VirtualBox says:
Is there any definitive info on systems running Mint as a VirtualBox guest?
Is it safe for me to upgrade to 'Linux Mint 18.3 Sylvia'?
Is it safe for me to whitelist 'mintupdate'?
Sorry about my ignorance. It's no excuse. I'm still so unsure about Mint. All I know for sure is that Global Warming is real. Everything else is Internet-knowledge.
As my sig-line says: "Windows 10 {VirtualBox {Linux Mint 18 {Cinnamon Desktop} } }".
From the reports, I can't tell whether the Mint systems affected are running Mint as stand-alone, as a VirtualBox host, or as a VirtualBox guest.
In my case, I'm running Mint as a guest.
'inxi -Fxz' reports (in part):
Code: Select all
System > Host: mark-VirtualBox Kernel: 4.4.0-21-generic x86_64 (64 bit gcc: 5.3.1)
System > Desktop: Cinnamon 3.0.7 (Gtk 3.18.9-1ubuntu3.3)
System > Distro: Linux Mint 18 Sarah
Machine > System: innotek (portable) product: VirtualBox v: 1.2
Machine > Mobo: Oracle model: VirtualBox v: 1.2
Machine > Bios: innotek v: VirtualBox date: 12/01/2006
Code: Select all
Version 5.2.6 r120293 (Qt5.6.2)
Is it safe for me to upgrade to 'Linux Mint 18.3 Sylvia'?
Is it safe for me to whitelist 'mintupdate'?
Sorry about my ignorance. It's no excuse. I'm still so unsure about Mint. All I know for sure is that Global Warming is real. Everything else is Internet-knowledge.
Re: mintupdate 5.1.0.5
Not quite sure, which info you mean. Anyway: press in the running VM host-n, this will give you the information about the guest.markfilipak wrote: ⤴Tue Apr 03, 2018 3:12 pm Is there any definitive info on systems running Mint as a VirtualBox guest?
In principle it is. But as long as Mint Update is not current, it is not safe. Mint Update has to be - without any if and when - to be current.markfilipak wrote: ⤴Tue Apr 03, 2018 3:12 pm Is it safe for me to upgrade to 'Linux Mint 18.3 Sylvia'?
Definitely yes.
To show you why: The guest additions are a kind of driver for the virtualized hardware, which VB provides for the guest systems. To make those drivers work fully and correctly, the version of VB and of the guest additions have to match. And here is already the point, why the previous decision for the pre-installed guest-additions in Mint (up until 18.2) was a terrible design mistake. I cannot count the cases, where I had to help users because of problems just because of this mistake. With the removal of the pre-installed guest additions this mistake gets finally corrected. After you have done this in your guest you have at first to reboot the guest. Than install the guest additions from the devices menu of the running guest. VB brings always the matching guest additions with each new version. After having the correct guest additions installed you have to reboot the guest once more. Done.
Now something special for your case: You use VB 5.2.6. Not only is this not the latest version (this would be 5.2.. The guest additions for 5.2.6 have a bug, which specifically affected Linux guests. To solve this problem Oracle had offered a corrected version of the guest additions, which hd to get separately downloaded. But as 5.2.8 is now available you should at first update your VB, then you can forget this special problem with 5.2.6.
So the steps to proceed are in this order:
Update VB
Update in the guest mintupdate and proceed as I explained above.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Hi Cosmo. Thank you for all the help you give to me and other folks!
Okay, first, to clear the air. I always install the guest additions from the host via the VM's menu 'Devices' > 'Insert Guest Additions CD Image...'. I never install the guest additions from the Linux distro. I assume that's what you imply below, but I just want you to be sure I know what I'm doing. Installing from the host (as above) has never failed. I assume that all your cautionary notes apply only to the Linux distro, right?
Okay, first, to clear the air. I always install the guest additions from the host via the VM's menu 'Devices' > 'Insert Guest Additions CD Image...'. I never install the guest additions from the Linux distro. I assume that's what you imply below, but I just want you to be sure I know what I'm doing. Installing from the host (as above) has never failed. I assume that all your cautionary notes apply only to the Linux distro, right?
I'm just trying to be careful here. I have done quite a bit of reading and it's not clear whether the folks who have had this problem are running, case 1: a stand-alone Mint, or case 2: Mint as the host, or case 3: Mint as a guest. Of course, the only time Linux guest additions are needed/wanted/useful is case 3, and installing guest additions for cases 1 & 2 is bad. If Mint Update is installing VBox guest additions even when people ARE NOT running Mint as a VBox guest, then of course that's wrong. Is that the problem? Is Mint Update doing THAT?Cosmo. wrote: ⤴Tue Apr 03, 2018 3:39 pmNot quite sure, which info you mean. Anyway: press in the running VM host-n, this will give you the information about the guest.markfilipak wrote: ⤴Tue Apr 03, 2018 3:12 pm Is there any definitive info on systems running Mint as a VirtualBox guest?
Understood. Thank you.In principle it is. But as long as Mint Update is not current, it is not safe. Mint Update has to be - without any if and when - to be current.markfilipak wrote: ⤴Tue Apr 03, 2018 3:12 pm Is it safe for me to upgrade to 'Linux Mint 18.3 Sylvia'?
Just exercising abundant caution, you mean the VBox guest additions from the Linux distro (via Mint Update), correct? In other words, you don't mean installing guest additions directly from the host's VBox, correct? This seems to be causing quite a bit of confusion because, in reality, there are 2 different VBox guest additions: one from the VBox host (via the VM's menu, as I describe in the first paragraph), and one from the Linux distro (via Mint Update). I only use the first, never the second. Do you concur?Definitely yes.
To show you why: The guest additions are a kind of driver for the virtualized hardware, which VB provides for the guest systems. To make those drivers work fully and correctly, the version of VB and of the guest additions have to match. And here is already the point, why the previous decision for the pre-installed guest-additions in Mint (up until 18.2) was a terrible design mistake.
See, here is where I get confused. What do you mean by "pre-installed"? I used to run Mint 17 in a virtual machine and I don't remember the guest additions ever being "pre-installed".I cannot count the cases, where I had to help users because of problems just because of this mistake. With the removal of the pre-installed guest additions this mistake gets finally corrected.
Ah! Now you seem to be confirming what I know: Install guest additions through the Virtual Machine's 'Devices' menu, not through some Mint update. Agreed.After you have done this in your guest you have at first to reboot the guest. Than install the guest additions from the devices menu of the running guest. VB brings always the matching guest additions with each new version. After having the correct guest additions installed you have to reboot the guest once more. Done.
Yes, I was aware of 5.2.8, but I've just gotten my new computer running and haven't updated yet because I needed to get on-line first to download the new version. You see, the reason I run a Mint VM is to get on-line -- I don't trust Windows on-line and I use the Windows firewall to block it. I "wire" the VBox bridge adapter directly to the hardware (which bypasses Windows and the Windows firewall).Now something special for your case: You use VB 5.2.6. Not only is this not the latest version (this would be 5.2.. The guest additions for 5.2.6 have a bug, which specifically affected Linux guests. To solve this problem Oracle had offered a corrected version of the guest additions, which hd to get separately downloaded. But as 5.2.8 is now available you should at first update your VB, then you can forget this special problem with 5.2.6.
Understood. Thank you so much (and I hope your hair grows back soon!).So the steps to proceed are in this order:
Update VB
Update in the guest mintupdate and proceed as I explained above.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Help!
I did as Cosmo recommended.
1 - I upgraded to 'VBox Version 5.2.8 r121009 (Qt5.6.2)' (and I installed 'Oracle_VM_VirtualBox_Extension_Pack-5.2.8.vbox-extpack' while I was at it).
2 - Then I mounted 'VBoxGuestAdditions.iso' -- gratefully, mounting was automatic -- and ran the '/media/mark/VBox_GAs_5.2.8/autorun.sh' script ...
... All went well.
3 - Then I rebooted the Mint VM and took 'mintupdate' out of 'mintupdate's blacklist.
'mintupdate' still wants to remove the VBox guest additions, specifically: 'virtualbox-guest-dkms' & 'virtualbox-guest-utils' & 'virtualbox-guest-x11'.
Synaptic reports:
virtualbox-guest-dkms == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 4498 kB
virtualbox-guest-utils == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 2230 kB
virtualbox-guest-x11 == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 6374 kB
The installed files for 'virtualbox-guest-dkms' are:
The installed files for 'virtualbox-guest-utils' are:
The installed files for 'virtualbox-guest-x11' are:
I'm terrified by this.
Now that I have 'mintupdate' whitelisted, I'm going to try to upgrade from Mint 18.2 to Mint 18.3. Then, if 'mintupdate' still wants to remove the VBox guest additions... well... I don't know what I'll do.
I did as Cosmo recommended.
1 - I upgraded to 'VBox Version 5.2.8 r121009 (Qt5.6.2)' (and I installed 'Oracle_VM_VirtualBox_Extension_Pack-5.2.8.vbox-extpack' while I was at it).
2 - Then I mounted 'VBoxGuestAdditions.iso' -- gratefully, mounting was automatic -- and ran the '/media/mark/VBox_GAs_5.2.8/autorun.sh' script ...
... All went well.
3 - Then I rebooted the Mint VM and took 'mintupdate' out of 'mintupdate's blacklist.
'mintupdate' still wants to remove the VBox guest additions, specifically: 'virtualbox-guest-dkms' & 'virtualbox-guest-utils' & 'virtualbox-guest-x11'.
Synaptic reports:
virtualbox-guest-dkms == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 4498 kB
virtualbox-guest-utils == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 2230 kB
virtualbox-guest-x11 == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 6374 kB
The installed files for 'virtualbox-guest-dkms' are:
Code: Select all
/.
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/60-virtualbox-guest-dkms.rules
/usr
/usr/share
/usr/share/apport
/usr/share/apport/package-hooks
/usr/share/apport/package-hooks/virtualbox-guest-dkms.py
/usr/share/doc
/usr/share/doc/virtualbox-guest-dkms
/usr/share/doc/virtualbox-guest-dkms/README.Debian
/usr/share/doc/virtualbox-guest-dkms/changelog.Debian.gz
/usr/share/doc/virtualbox-guest-dkms/copyright
/usr/src
/usr/src/virtualbox-guest-5.0.40
/usr/src/virtualbox-guest-5.0.40/Makefile
/usr/src/virtualbox-guest-5.0.40/dkms.conf
/usr/src/virtualbox-guest-5.0.40/include
/usr/src/virtualbox-guest-5.0.40/include/VBox
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI/HGSMI.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI/HGSMIChSetup.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI/HGSMIChannels.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI/HGSMIDefs.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/HGSMI/HGSMIMemAlloc.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/Hardware
/usr/src/virtualbox-guest-5.0.40/include/VBox/Hardware/VBoxVideoVBE.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxGuest.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxGuest2.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxGuestLib.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxGuestLibSharedFolders.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxGuestMangling.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxVideo.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VBoxVideoGuest.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VMMDev.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/VMMDev2.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/cdefs.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/err.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/hgcmsvc.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/log.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/ostypes.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/param.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/shflsvc.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/types.h
/usr/src/virtualbox-guest-5.0.40/include/VBox/version.h
/usr/src/virtualbox-guest-5.0.40/include/internal
/usr/src/virtualbox-guest-5.0.40/include/internal/assert.h
/usr/src/virtualbox-guest-5.0.40/include/internal/initterm.h
/usr/src/virtualbox-guest-5.0.40/include/internal/iprt.h
/usr/src/virtualbox-guest-5.0.40/include/internal/lockvalidator.h
/usr/src/virtualbox-guest-5.0.40/include/internal/magics.h
/usr/src/virtualbox-guest-5.0.40/include/internal/memobj.h
/usr/src/virtualbox-guest-5.0.40/include/internal/process.h
/usr/src/virtualbox-guest-5.0.40/include/internal/sched.h
/usr/src/virtualbox-guest-5.0.40/include/internal/string.h
/usr/src/virtualbox-guest-5.0.40/include/internal/thread.h
/usr/src/virtualbox-guest-5.0.40/include/internal/time.h
/usr/src/virtualbox-guest-5.0.40/include/iprt
/usr/src/virtualbox-guest-5.0.40/include/iprt/alloc.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/alloca.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/asm-amd64-x86.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/asm-math.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/asm.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/assert.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/avl.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/cdefs.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/cpuset.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/ctype.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/err.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/errno.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/fs.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/heap.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/initterm.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/latin1.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/list.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/lockvalidator.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/log.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/mangling.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/mem.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/memobj.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/mp.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/net.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/nocrt
/usr/src/virtualbox-guest-5.0.40/include/iprt/nocrt/limits.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/param.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/path.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/power.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/process.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/semaphore.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/spinlock.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/stdarg.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/stdint.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/string.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/thread.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/time.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/timer.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/types.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/uni.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/utf16.h
/usr/src/virtualbox-guest-5.0.40/include/iprt/x86.h
/usr/src/virtualbox-guest-5.0.40/include/the-linux-kernel.h
/usr/src/virtualbox-guest-5.0.40/r0drv
/usr/src/virtualbox-guest-5.0.40/r0drv/alloc-r0drv.c
/usr/src/virtualbox-guest-5.0.40/r0drv/alloc-r0drv.h
/usr/src/virtualbox-guest-5.0.40/r0drv/generic
/usr/src/virtualbox-guest-5.0.40/r0drv/generic/semspinmutex-r0drv-generic.c
/usr/src/virtualbox-guest-5.0.40/r0drv/initterm-r0drv.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/RTLogWriteDebugger-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/alloc-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/assert-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/initterm-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/memobj-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/memuserkernel-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/mp-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/mpnotification-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/process-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/semevent-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/semeventmulti-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/semfastmutex-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/semmutex-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/spinlock-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/string.h
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/the-linux-kernel.h
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/thread-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/thread2-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/time-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/timer-r0drv-linux.c
/usr/src/virtualbox-guest-5.0.40/r0drv/linux/waitqueue-r0drv-linux.h
/usr/src/virtualbox-guest-5.0.40/r0drv/memobj-r0drv.c
/usr/src/virtualbox-guest-5.0.40/r0drv/mp-r0drv.h
/usr/src/virtualbox-guest-5.0.40/r0drv/mpnotification-r0drv.c
/usr/src/virtualbox-guest-5.0.40/r0drv/power-r0drv.h
/usr/src/virtualbox-guest-5.0.40/r0drv/powernotification-r0drv.c
/usr/src/virtualbox-guest-5.0.40/vboxguest
/usr/src/virtualbox-guest-5.0.40/vboxguest/GenericRequest.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/HGCMInternal.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/Init.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/Makefile
/usr/src/virtualbox-guest-5.0.40/vboxguest/Makefile.include.footer
/usr/src/virtualbox-guest-5.0.40/vboxguest/Makefile.include.header
/usr/src/virtualbox-guest-5.0.40/vboxguest/PhysHeap.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/SysHlp.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/SysHlp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBGLInternal.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBox
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBox/log-vbox.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBox/logbackdoor.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBoxGuest-linux.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBoxGuest.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBoxGuestIDC-unix.c.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBoxGuestInternal.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/VBoxGuestLog.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/VMMDev.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/alloc
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/alloc/alloc.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/alloc/heapsimple.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/err
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/err/RTErrConvertFromErrno.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/err/RTErrConvertToErrno.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/log.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/logcom.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/logellipsis.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/logformat.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/logrel.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/log/logrelellipsis.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/divdi3.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/moddi3.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/qdivrem.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/quad.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/udivdi3.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/math/gcc/umoddi3.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg1Weak.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2Add.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2AddWeak.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2AddWeakV.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2Weak.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/RTAssertMsg2WeakV.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/assert.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/misc/thread.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/RTStrCopy.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/RTStrCopyEx.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/RTStrCopyP.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/strformat.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/strformatrt.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/strformattype.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/strprintf.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/string/strtonum.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_Base.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_Destroy.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_DoWithAll.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_Get.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_GetBestFit.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avl_RemoveBestFit.cpp.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/table/avlpv.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/time
/usr/src/virtualbox-guest-5.0.40/vboxguest/common/time/time.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/do_Module.symvers
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTAssertShouldPanic-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTLogWriteStdErr-stub-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTLogWriteStdOut-stub-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTMpGetCoreCount-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTSemEventMultiWait-2-ex-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTSemEventMultiWaitNoResume-2-ex-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTSemEventWait-2-ex-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/RTSemEventWaitNoResume-2-ex-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/errvars-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/mppresent-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/generic/rtStrFormatKernelAddress-generic.c
/usr/src/virtualbox-guest-5.0.40/vboxguest/include
/usr/src/virtualbox-guest-5.0.40/vboxguest/product-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/r0drv
/usr/src/virtualbox-guest-5.0.40/vboxguest/revision-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxguest/version-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxsf
/usr/src/virtualbox-guest-5.0.40/vboxsf/GenericRequest.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/HGCM.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/Init.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/Makefile
/usr/src/virtualbox-guest-5.0.40/vboxsf/Makefile.include.footer
/usr/src/virtualbox-guest-5.0.40/vboxsf/Makefile.include.header
/usr/src/virtualbox-guest-5.0.40/vboxsf/PhysHeap.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/SysHlp.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/SysHlp.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/VBGLInternal.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/VBoxGuestLog.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/VBoxGuestR0LibSharedFolders.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/VMMDev.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/VbglR0CanUsePhysPageList.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/dirops.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/divdi3.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/do_Module.symvers
/usr/src/virtualbox-guest-5.0.40/vboxsf/include
/usr/src/virtualbox-guest-5.0.40/vboxsf/lnkops.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/moddi3.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/product-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/qdivrem.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/quad.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/r0drv
/usr/src/virtualbox-guest-5.0.40/vboxsf/regops.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/revision-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/udivdi3.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/umoddi3.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/utils.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/vbsfmount.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/version-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxsf/vfsmod.c
/usr/src/virtualbox-guest-5.0.40/vboxsf/vfsmod.h
/usr/src/virtualbox-guest-5.0.40/vboxvideo
/usr/src/virtualbox-guest-5.0.40/vboxvideo/HGSMIBase.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/HGSMICommon.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/HGSMIMemAlloc.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/Makefile
/usr/src/virtualbox-guest-5.0.40/vboxvideo/Makefile.include.footer
/usr/src/virtualbox-guest-5.0.40/vboxvideo/Makefile.include.header
/usr/src/virtualbox-guest-5.0.40/vboxvideo/Modesetting.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/VBVABase.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/do_Module.symvers
/usr/src/virtualbox-guest-5.0.40/vboxvideo/heapoffset.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/include
/usr/src/virtualbox-guest-5.0.40/vboxvideo/product-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxvideo/r0drv
/usr/src/virtualbox-guest-5.0.40/vboxvideo/revision-generated.h
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_drv.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_drv.h
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_dummy.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_fb.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_irq.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_main.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_mode.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/vbox_ttm.c
/usr/src/virtualbox-guest-5.0.40/vboxvideo/version-generated.h
Code: Select all
/.
/etc
/etc/init.d
/etc/init.d/virtualbox-guest-utils
/lib
/lib/security
/lib/security/pam_vbox.so
/sbin
/sbin/mount.vboxsf
/usr
/usr/sbin
/usr/sbin/VBoxControl
/usr/sbin/VBoxService
/usr/share
/usr/share/doc
/usr/share/doc/virtualbox-guest-utils
/usr/share/doc/virtualbox-guest-utils/changelog.Debian.gz
/usr/share/doc/virtualbox-guest-utils/copyright
/usr/share/man
/usr/share/man/man8
/usr/share/man/man8/VBoxControl.8.gz
/usr/share/man/man8/VBoxService.8.gz
/usr/share/man/man8/mount.vboxsf.8.gz
Code: Select all
/.
/etc
/etc/X11
/etc/X11/Xsession.d
/etc/X11/Xsession.d/98vboxadd-xclient
/usr
/usr/bin
/usr/bin/VBoxClient
/usr/lib
/usr/lib/VBoxEGL.so
/usr/lib/VBoxOGL.so
/usr/lib/VBoxOGLarrayspu.so
/usr/lib/VBoxOGLcrutil.so
/usr/lib/VBoxOGLerrorspu.so
/usr/lib/VBoxOGLfeedbackspu.so
/usr/lib/VBoxOGLpackspu.so
/usr/lib/VBoxOGLpassthroughspu.so
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/dri
/usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
/usr/lib/xorg
/usr/lib/xorg/modules
/usr/lib/xorg/modules/drivers
/usr/lib/xorg/modules/drivers/vboxvideo_drv.so
/usr/share
/usr/share/doc
/usr/share/doc/virtualbox-guest-x11
/usr/share/doc/virtualbox-guest-x11/changelog.Debian.gz
/usr/share/doc/virtualbox-guest-x11/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/virtualbox-guest-x11
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/VBoxClient.1.gz
/usr/share/virtualbox
/usr/share/virtualbox/x11config.pl
Now that I have 'mintupdate' whitelisted, I'm going to try to upgrade from Mint 18.2 to Mint 18.3. Then, if 'mintupdate' still wants to remove the VBox guest additions... well... I don't know what I'll do.
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Update.
I just watched the "Release Notes for Linux Mint 18.3 Cinnamon" videos. I am NEVER going to upgrade to Mint 18.3 because it involves (or may involve) screwing around with 'grub'. I have trashed more disks with 'grub' than you can shake a stick at. That's really funny because I have edited partitions in binary. But 'grub' completely mystifies me.
So, here's my status:
1 - 'mintupgrade' is whitelisted, but I will not upgrade it because it wants to remove VBox guest additions.
2 - I will not upgrade to Mint 18.3 because it involves (or may involve) screwing around with 'grub'.
So it looks like I'm dead in the water.
I just watched the "Release Notes for Linux Mint 18.3 Cinnamon" videos. I am NEVER going to upgrade to Mint 18.3 because it involves (or may involve) screwing around with 'grub'. I have trashed more disks with 'grub' than you can shake a stick at. That's really funny because I have edited partitions in binary. But 'grub' completely mystifies me.
So, here's my status:
1 - 'mintupgrade' is whitelisted, but I will not upgrade it because it wants to remove VBox guest additions.
2 - I will not upgrade to Mint 18.3 because it involves (or may involve) screwing around with 'grub'.
So it looks like I'm dead in the water.
- smurphos
- Level 18
- Posts: 8501
- Joined: Fri Sep 05, 2014 12:18 am
- Location: Irish Brit in Portugal
- Contact:
Re: mintupdate 5.1.0.5
Just let mintupdate remove the virtualbox-guest* packages. They are not in use in your guest system - you have installed the correct 5.2.8 version guest additions directly from virtualbox. Mintupdate will not touch them.
If you are concerned make a clone of your virtual machine first and then try the process in the clone to check that it all goes well.
viewtopic.php?p=1449369#p1449369
Re your concerns re upgrading to Mint 18.3 - those videos are in regards to undertaking a fresh installation from scratch and mitigating issues with some GPU's during the installation process. They are not relevant to upgrading in place.
Upgrading in place is a straightforward process - see https://blog.linuxmint.com/?p=3462
If you are concerned make a clone of your virtual machine first and then try the process in the clone to check that it all goes well.
viewtopic.php?p=1449369#p1449369
Re your concerns re upgrading to Mint 18.3 - those videos are in regards to undertaking a fresh installation from scratch and mitigating issues with some GPU's during the installation process. They are not relevant to upgrading in place.
Upgrading in place is a straightforward process - see https://blog.linuxmint.com/?p=3462
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
Re: mintupdate 5.1.0.5
The problem with the pre-installed guest additions does only exist for Mint. But the advice to install them only from the devices menu of the running guest and not from the distro's repository is true for every Linux distro.markfilipak wrote: ⤴Tue Apr 03, 2018 7:06 pm I assume that all your cautionary notes apply only to the Linux distro, right?
No, Mint Update does not install the guest additions. Mint Update in general does never install anything, what does not already exist on the system. (Exception are some dependencies in rare cases, usually libraries, which an updated package needs; but if this happens, you get a notification about that.)markfilipak wrote: ⤴Tue Apr 03, 2018 7:06 pm If Mint Update is installing VBox guest additions even when people ARE NOT running Mint as a VBox guest, then of course that's wrong. Is that the problem? Is Mint Update doing THAT?
Those guest-additions get already installed by the Mint installer (except a fresh install of LM 18.3). Following that the updater offers an update for them, if they are available (as it is the case since a short time). Whereas the old guest additions did not give a problem, the new guest additions do. As a consequence Clem did an update for the Mint Updater, which removes the existing guest packages; consequently the updated guest packages do no longer get offered.
Note, that the Updater does only remove the guest packages, which com from the repository. The updater does not touch the guest additions, which have already been installed from the VB devices menu! (And if the updater would do this, they could easily get installed anew, but that is purely theory.) I have tested this with all versions of Mint 17.x and 18.x.
Fully.
Your remembrance is fooling you. You can even launch any Mint live system (except 18.3) and search in synaptic formarkfilipak wrote: ⤴Tue Apr 03, 2018 7:06 pm I used to run Mint 17 in a virtual machine and I don't remember the guest additions ever being "pre-installed".
virtualbox
and you will see 3 guest packages installed. They will also get installed, when you install Mint from this live system.I do not get the point. VB in your Windows host did not get fro nowhere. As you have obviously downloaded VB 5.2.6, why do you bother to download VB 5.2.8?markfilipak wrote: ⤴Tue Apr 03, 2018 7:06 pm Yes, I was aware of 5.2.8, but I've just gotten my new computer running and haven't updated yet because I needed to get on-line first to download the new version. You see, the reason I run a Mint VM is to get on-line -- I don't trust Windows on-line and I use the Windows firewall to block it.
Re: mintupdate 5.1.0.5
No need to be terrified. Those guest packages came with the Mint installer and as long as they are installed, the new - bad - packages would get installed by updating them. You don't need those packages; the do not even match with your version of VB. s I already wrote above: The Mint updater does not touch the guest additions, which you install from the devices menu.markfilipak wrote: ⤴Wed Apr 04, 2018 12:53 am Synaptic reports:
virtualbox-guest-dkms == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 4498 kB
virtualbox-guest-utils == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 2230 kB
virtualbox-guest-x11 == 5.0.40-dfsg-0ubuntu1.16.04.2 -- 6374 kB
I'm terrified by this.
Now that I have 'mintupdate' whitelisted, I'm going to try to upgrade from Mint 18.2 to Mint 18.3. Then, if 'mintupdate' still wants to remove the VBox guest additions... well... I don't know what I'll do.
If you would upgrade to Mint 18.3, those packages will not get removed. The upgrade mechanism of the Mint updater does never remove any existing package, except it would conflict with the upgrade. So upgrading does not change anything regarding the guest package situation.
What you can also do, to be really sure. You can create in VB a snapshot for the current state of the virtual machine. In case there should be a unsolvable problem, you can easily revert to the VB snapshot and this will be, as if all and really every change, which you did after the snapshot would never had been done. Creating a snapshot is anyway a good idea to prevent against unfortunate changes.
Re: mintupdate 5.1.0.5
Why? You assume problems, where they do not exist.markfilipak wrote: ⤴Wed Apr 04, 2018 1:11 am So, here's my status:
1 - 'mintupgrade' is whitelisted, but I will not upgrade it because it wants to remove VBox guest additions.
So it looks like I'm dead in the water.
Once again: You have to apply the update for mint-update, otherwise your system will never get any update for anything at all!
This is solely your decision, but I cannot follow. Usually virtual systems are not dual booted. You will usually not even see the grub menu in a virtual machine. I don't see, which problems you expect.markfilipak wrote: 2 - I will not upgrade to Mint 18.3 because it involves (or may involve) screwing around with 'grub'.
But even in this case: If you have a VB snapshot created before the upgrade and if you don't like the result, you can with one click revert to the snapshot state and it will be, as if you would not have done anything at all. It is a kind of time machine. You can even create a second snapshot after the change and can now switch between both snapshots - forward and backward.
-
- Level 6
- Posts: 1138
- Joined: Thu May 03, 2012 3:54 am
- Location: Israel
- Contact:
Re: mintupdate 5.1.0.5
Finally they removed the Vbox guest additions!
To the OP:
If you install Linux Mint on bare metal, that is directly on the PC and NOT in a virtual machine, you don't need the Vbox guest additions. They are useless!
If you install Linux Mint in a VirtualBox virtual machine, you should get and install the Vbox guest additions that match your Vbox version in the host. If you install the wrong guest additions version, the VM might not work or problems may occur.
I guess the Linux Mint developers wanted to make it easy to install Linux Mint in a Vbox VM, and didn't foresee the issues caused by mismatch of Vbox version on the host and the guest additions in the VM.
Hope this is clear now.
To the OP:
If you install Linux Mint on bare metal, that is directly on the PC and NOT in a virtual machine, you don't need the Vbox guest additions. They are useless!
If you install Linux Mint in a VirtualBox virtual machine, you should get and install the Vbox guest additions that match your Vbox version in the host. If you install the wrong guest additions version, the VM might not work or problems may occur.
I guess the Linux Mint developers wanted to make it easy to install Linux Mint in a Vbox VM, and didn't foresee the issues caused by mismatch of Vbox version on the host and the guest additions in the VM.
Hope this is clear now.
Subjects of interest: Linux, vfio passthrough virtualization, photography
See my blog on virtualization, including tutorials: https://www.heiko-sieger.info/category/ ... alization/
See my blog on virtualization, including tutorials: https://www.heiko-sieger.info/category/ ... alization/
-
- Level 6
- Posts: 1173
- Joined: Sun Mar 10, 2013 8:08 pm
- Location: Mansfield, Ohio
Re: mintupdate 5.1.0.5
Yes, it's clear. Thank you.powerhouse wrote: ⤴Wed Apr 18, 2018 3:53 am Finally they removed the Vbox guest additions!
To the OP:
...
Hope this is clear now.