Skip to main content

Posts

Showing posts with the label VirtualBox

Error opening directory '/media/sf_C_DRIVE': Permission denied

I tried to share a folder from Windows 10 host to Kali 2020.1 Linux guest using VirtualBox but I am getting the following error message: Error opening directory '/media/sf_C_DRIVE': Permission denied To fix, do: $: sudo adduser $USER vboxsf Then log-off then log back in. If this does not work, reboot the VM Getting similar issue using Fedora 33 on VirtualBox 7.0.12, below is the error message This location could not be displayed You do not have the permissions necessary to view the contents of "sf_D_DRIVE" To fix do the following and reboot the VM. $: sudo usermod -a -G vboxsf $USER Refs: https://stackoverflow.com/questions/26740113/virtualbox-shared-folder-permissions

Install VirtualBox 7.0.4 on Linux Mint 21.1 Vera

Install VirtualBox 7.0.4 on Linux Mint 21.1 Vera ▣ Download VirtualBox 7.0.4 from www.virtualbox.org , select Ubuntu 22.04. ▣ Once download is complete, open a terminal and run the following: $: cd Downloads/ $: sudo dpkg -i virtualbox-7.0_7.0.4-154605~Ubuntu~jammy_amd64.deb $: sudo apt -f install $: sudo usermod -a -G vboxusers timus Replace timus with the current user

How to expand Ubuntu VM root partition

How to expand Ubuntu VM root partition In this post I have expanded the virtual disk of a Ubuntu VM via VirtualBox Media Manager. The OS inside the VM will not automatically use the additional space. In this post I will show how to expand the root partition to make use of the additional space. There are multiple ways to expand a partition in Linux, in this post I will document how to do it using GParted.  Change the VM configuration to boot using Ubuntu installer.  Boot the VM using the Ubuntu ISO installer Run GParted - in the warning dialog that says not all space is used, hit on the Fix button Select the partition to resize and click Resize/Move partition button Expand the partition to the desired size The hit on Apply All Operations Shutdown the VM, remove/detach ISO, then reboot the computer   .end.

How to expand virtual hard disk in VirtualBox

How to expand virtual hard disk in VirtualBox To expand a virtual disk in VirtualBox open Oracle VM Virtual Manager then do File | Virtual Media Manager... (Ctrl+D) menu option. Then select the disk you wanted to expand. Note that VirtualBox does not support expanding a snapshot - you can expand but it will not work. You either have to delete all the snapshots or create a full clone of the snapshot. In the screen capture below I have created a full clone of Ubu2110 to Ubu2110-C1 and adjusted the size from 10GB to 12GB. In the next post , we will explore how to expand storage of a Ubuntu VM to make use of the additional space. Keywords: VirtualBox Ubuntu Expand

Mouse cursor disappers inside the VirtualBox VM when installing CentOS 7

Tried to create a VM using CentOS 7 ISO on VirtualBox 6. The VM booted fine and showed WELCOME TO CENTOS 7 screen, the issue is that clicking inside the VM would cause the mouse cursor to disapper. The VM is still usable but you have to use the keyboard to navigate the OS. To workaround the issue, shutdown the VM and change the settings System | Pointing Device to USB Tablet .

CentOS 7 networking not working on VirtualBox

It seems like this is by design (for security?) that CentOS 7 does not have networking working by default. Anyway, to fix this on VM running VirtualBox, edit /etc/sysconfig/network-scripts/ifcfg-enp0s3 and change the line that says ONBOOT=no to ONBOOT=yes and then reboot the machine. Refs: https://superuser.com/questions/915536/centos-7-virtualbox-no-internet-access

Copy/paste text from Ubuntu 18.10 (Cosmic Cuttlefish) VM from/to Windows host using VirtualBox

Tested on: Host: Windows 10 Enterprise (1803) with VirtualBox 5.2.20 Guest: Ubuntu 18.10 (Cosmic Cuttlefish) Goal : Copy/paste text from/to Ubuntu 18.10 from/to Windows host Solution: This is not absolutely necessary but it is a good practice to update Ubuntu 18.10 to the latest using a terminal, like: $ sudo apt update $ sudo apt upgrade $ sudo apt autoremove I would advice to reboot the machine at this point so that we will be running the latest kernel. The next command may also pick the wrong version of the kernel headers if the machine(VM) is running the older version of the kernel. Now, install dkms so that VirtualBox guest additions can be compiled as part of the kernel, like: $ sudo apt install dkms Now mount VirtualBox guest additions, this will be done from the external/host UI of the VirtualBox guest VM. For example, click on Devices | Insert Guest Additions CD Image... Now head into the VM and do: $ cd /media/<username>/VBox_GAs_5.2.20 $ sudo

Copy/paste text from Kali Linux (VM) to Windows host using VirtualBox

Tested on: Host: Windows 10 Enterprise (1803) with VirtualBox 5.2.18 Guest: Kali Linux 2018.3a Goal: Copy/paste text from Kali Linux from/to Windows host Solution: This is not absolutely necessary but is a good practice, update Kali to latest version using a terminal, like: :/# apt update :/# apt upgrade :/# apt autoremove Sometimes this is not enough to bring Kali to the latest and greatest, you may have to also upgrade it, like: :/# apt full-upgrade I would advice to reboot the machine at this point so that we will be running the latest kernel. The next command may also pick the wrong version of the kernel headers if the machine(VM) is running the older version of the kernel. Now, install dkms so that VirtualBox guest additions can be compiled as part of the kernel, like: :/# apt install dkms Now mount VirtualBox guest additions, this will be done from the external/host UI of the VirtualBox guest VM. For example, click on Devices | Insert Guest Additions CD

VirtualBox Shared Clipboard not working on Ubuntu Budgie 18.04 VM guest

VirtualBox Guest Additions are installed and Shared Clipboard (Bidirectional) option selected. Even tried to reboot still not working. Any hints how to fix is appreciated. Note that Ubuntu 18.04 (Gnome) and Ubuntu 18.10 LXQt is working the same Windows 10 host. [6/18/2018] Most be getting old. I assumed VirtualBox guest additions was installed as the VM window can be resized. Anyway, installed guest additions and copy/paste worked like a charm. Also reported in Discource https://discourse.ubuntubudgie.org/t/virtualbox-shared-clipboard-not-working-on-budgie-18-04/646

Unable to mount VirtualBox shared drive using 4.3.10

When mounting a shared drive in VirtualBox 4.3.10, got he following error in Linux box: sudo mount -t vboxsf E_DRIVE vbox mount: wrong fs type, bad option, bad superblock on E_DRIVE,        missing codepage or helper program, or other error        (for several filesystems (e.g. nfs, cifs) you might        need a /sbin/mount.<type> helper program)        In some cases useful info is found in syslog - try        dmesg | tail  or so This is caused by wrong symbolic link, to fix it do: ~$ sudo ln -sf /usr/lib/i386-linux-gnu/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf References: http://superuser.com/questions/736024/cannot-share-host-directory-with-virtualbox-guest-mint-16-64-bit

Starting Virtualbox guest shows VERR_SSM_LOAD_CONFIG_MISMATCH

The host machine experienced a power failure, when a guest machine was started up it failed with error message below. Failed to open a session for the virtual machine MACHINENAME. ahci#0: The target VM is missing a device on port 0. Please make sure the source and target VMs have compatible storage configurations [ver=6 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH). It seems like Virtualbox virtual machine configuration was corrupted. Looking at the virtual machine settings noticed that the virtual HD attached to the SATA port was gone. To workaround this case, re-attached the latest snapshot to the VM. Use Virtual Media Manager to determine the correct UUID.

Windows 8.1 Pro RTM auto-resize guest display not working in VirtualBox 4.2.18

Microsoft changed course and released Windows 8.1 to MSDN and TechNet users earlier than planned. It was made available last Sept 8, 2013 . This got me excited to play with this latest version. Downloading the ISO was quite frustrating as I can't use Firefox Download Them All plugin, just does not work. Downloading via IE10 was also painful but there is a workaround. VirtualBox also released 4.2.18 last Sept 6, 2013. This must be good, two good products released in the past few days. Upgrading of VirtualBox didn't work the first time. I have to do a repair to get it to work. So essentially, I have to install it twice. Installing of Windows 8.1 into VirtualBox was nonevent. But getting guest additions was challenging. I had to read lots of blogs including VirtualBox 4.2.18 release forum discussion topic . So, how did I get guest addition auto-resize to work? I have to install guest additions *twice*! This is what was working for me: Install guest additions... then re

VirtualBox paravirtualized network adapter driver

From VirtualBox manual, paravirtualized network adapter provides the best performance. To get this interface from working within VirtualBox, you need to download the drivers separately/manually. Note that Windows driver online update utility does not have it as well. Since driver is open source it can be found in few locations. A good source is from Red Hat, download it from this location  http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ . Download virtio-win*.iso, mount it and install driver for your OS.

Check version of VirtualBox guest additions installed

$: locate vboxguest If this returns nothing either you don't have VirtualBox guest additions installed or you need to update the database used by locate . If you suspect that the database may need a refresh, you can do sudo updatedb . Alternatively, you can check contents of /opt . If you have the additions installed, it should have an entry like VBoxGuestAdditions*.

Cannot install VirtualBox Guest Additions in Windows 8.1 Preview

When installing Windows 8.1 Preview from ISO, I am unable to install Guest Additions. Below is the error message. The search is on how to fix or find a workaround for this issue. Update(s): - Even running in compatibility mode is not working - This is now working on VirtualBox 4.2.16 (Type=Microsoft Windows, Version = Windows 8.1) References: https://forums.virtualbox.org/viewtopic.php?f=8&t=55260