What are /r/virtualbox's favorite Products & Services?

From 3.5 billion Reddit comments

Here is where you get it. https://www.virtualbox.org/

There's no viruses, it's oracle.

Once you have virtualbox installed, then you make a new machine and you install an OS (called a guest OS) on it. ISO's are the best way to install a new OS in virtualbox. Just pretend it's like a new machine. And if you screw it up, delete it and start again.

There are a ton of different Linux OSes that you can install to get your feet wet. Look at Ubuntu, Mint, Kubuntu are all popular options. All of those can be downloaded from their respective websites.

Once again, there is no risk downloading it from the virtualbox website. It's a free product.

Increasing a dynamically allocated disk just increases the free space available on said disk. However, you still have to expand the partitions / filesystem within the VM to occupy said free space if you want to take advantage of it.

See - https://dev.to/rishiabee/how-to-expand-a-linux-partition-using-gparted-31c3

If you want to be sure it will work, then I wouldn't try it until there's a version released that lists "11.0 (Big Sur)" here: https://www.virtualbox.org/manual/ch01.html#hostossupport

Because Virtual Box's EFI implementation is experimental and not complete, as indicated by the Virtual Box manual, it may not function for all OS's / configurations? -

https://www.virtualbox.org/manual/UserManual.html#efi

Unless it is required for the OS boot, you should leave it off for your Guests.

Good question, I've not used VB extensively on the command line. If that version of Arch has SSH enabled by default you could probably SSH in.

I would read chapter 8 of the VB manual if I were you: https://www.virtualbox.org/manual/ch08.html

It's probably in there somewhere. VirtualBox is mostly designed to be used in GUI mode. You might want to try qemu or even something like docker depending on what you are trying to do.

Although you have provided the minimum information to post here, you have not provided enough information for anyone to really troubleshoot your issue or offer you possible suggestions / fixes. I suggest you provide your vbox logs, and the startup logs for your Linux Guest. Absent additional information, all I can suggest is that you review the Virtual Box manual - https://www.virtualbox.org/manual/

It's called passthrough https://www.virtualbox.org/manual/ch09.html#pcipassthrough. Most people use KVM/QEMU afaik. Take a look at /r/VFIO.

So I ran into this yesterday - turns out they broke something in the guest additions for 5.2.22. https://www.virtualbox.org/ticket/18093

The solution is to grab the test build of the guest additions from https://www.virtualbox.org/wiki/Testbuilds and install those. Worked for me, anyway.

That said, I'm still having problems with Centos 7 even after reverting to 5.2.18 that are mouse related, similar to what you describe - I can't figure out what might have changed recently to break it yet but it seems like something is funky.

>I need this guest VM to have network access but only to the VM host for a network share but do not want it to have internet access or access to other devices on the LAN.

If all you want to do is share a directory that exists on your Host, with your Guest, you don't need any virtual networking per se. Install Guest Additions on your Windows 7 Guest, and use the "Shared Folders" feature. The directory, which exists natively on your Host, will appear to your Guest as a smb network share.

https://www.virtualbox.org/manual/ch04.html#sharedfolders

>Hello there, I’ve been trying to use my Linux VM but whenever I switch back to my host OS, which is windows 10, anything on virtual box is no longer in focus. I’ve been trying to get some work done but whenever I go back to my main OS it detects as if I left the webpage since it thinks the page lost focus.

Install Guest Additions on your Linux Guest, as it adds mouse pointer integration.

See - https://www.virtualbox.org/manual/ch04.html#guestadd-intro

> i don't know wich version of virtualbox i'm using i downloaded it today and it said it was the most recent.

So, why not take a few minutes and find out what version you are running, and post said information here? It's just a "help" -> "about" menu option away, once you open Oracle VM Virtual Box Manager.

Alternatively, use the command line interface to create the VM, bypassing the Oracle VM Virtual Box Manager entirely. See the Virtual Box manual linked below for syntax -

https://www.virtualbox.org/manual/ch08.html#vboxmanage-createvm

Well if you've found a solution already, good on you. That being said "Host" refers to the OS you are running on your physical hardware, while "Guest" refers to the OS you are running in a virtual machine. However, the fact that you don't know what a "Host" or "Guest" OS is suggests that you are not familiar with virtualization in general, or the attendant terminology. I'd suggest you review the Virtual Box Manual if you intend to do more than just dabble with it.

https://www.virtualbox.org/manual/

Perhaps, take a look at the Virtual Box Manual section pertaining to RDP authentication?

https://www.virtualbox.org/manual/ch07.html#vbox-auth

You can't pass your GPU directly to any Guest running on Virtual Box 6.1.x at this time. Said feature was only implemented with Virtual Box 6, on Linux Hosts. It was removed back in December 2019.

"Linux host: Drop PCI passthrough, the current code is too incomplete (cannot handle PCIe devices at all), i.e. not useful enough"

See - https://www.virtualbox.org/wiki/Changelog

To remove shared folders from a Guest see -

https://www.virtualbox.org/manual/UserManual.html#vboxmanage-sharedfolder

​

>Also do i need other stuff to be disabled?

Malware questions are no longer permitted in this subreddit. You are on your own.

You may want to post this to the official bug tracker, as opposed to this unofficial subreddit -

https://www.virtualbox.org/ticket/19674

For example...

This is just a friendly reminder in case you missed it. Your post must include: * The version of VirtualBox you are using * The host and guest OSes * Whether you have enabled VT-x/AMD-V (applicable to all hosts running 6.1 and above) and disabled HyperV (applicable to Windows 10 Hosts) * Whether you have installed Guest Additions and/or Host Extensions (this solves 90% of the problems we see)

PLUS a detailed description of the problem, what research you have done, and the steps you have taken to fix it. Please check Google and the VirtualBox Manual before asking simple questions. Please also check our FAQ and if you find your question is answered there, PLEASE remove your post or at least change the flair to Solved.
If you have met these requirements, you can ignore this post. Thanks for taking the time to help us help you! Also, PLEASE remember to change the flair of your post to Solved after you have been helped!

I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/virtualbox) if you have any questions or concerns.

This is just a friendly reminder in case you missed it. Your post must include: * The version of VirtualBox you are using * The host and guest OSes * Whether you have enabled VT-x/AMD-V (applicable to all hosts running 6.1 and above) and disabled HyperV (applicable to Windows 10 Hosts) * Whether you have installed Guest Additions and/or Host Extensions (this solves 90% of the problems we see)

PLUS a detailed description of the problem, what research you have done, and the steps you have taken to fix it. Please check Google and the VirtualBox Manual before asking simple questions. Please also check our FAQ and if you find your question is answered there, PLEASE remove your post or at least change the flair to Solved.
If you have met these requirements, you can ignore this post. Thanks for taking the time to help us help you! Also, PLEASE remember to change the flair of your post to Solved after you have been helped!

I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/virtualbox) if you have any questions or concerns.

This is just a reminder in case you missed it. Your post MUST include: * The version of VirtualBox you are using * The host and guest OSes * Whether you have enabled VT-x/AMD-V (applicable to all hosts running 6.1 and above) and disabled HyperV (applicable to Windows 10 Hosts) * Whether you have installed Guest Additions and/or Host Extensions (this solves 90% of the problems we see)

PLUS a detailed description of the problem, what research you have done, and the steps you have taken to fix it. Please check Google and the VirtualBox Manual before asking simple questions. If you have met these requirements, you can ignore this post. Thanks for taking the time to help us help you! Also, PLEASE remember to change the flair of your post to Solved after you have been helped!

I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/virtualbox) if you have any questions or concerns.

As you have not posted the specifics of your setup, all I can offer is what you want to do is indeed possible. I suggest you review the Virtual Box manual regarding network configuration for your Guests on Virtual Box. https://www.virtualbox.org/manual/ch06.html

As for setting up access to a VPN, there is no special sauce for Virtual Box. You would configure the Guest just as you would configure it if it were running on real hardware. I suggest you speak with your company's IT as their requirements for connecting to their VPN.

Well, given your last error msg, I'd make sure I/O APIC is enabled for your Guest (Virtual Box VM Manager - System Pane) for any 64 bit Linux Guests you are trying to run. As per the manual -

"Warning - Be sure to enable I/O APIC for virtual machines that you intend to use in 64-bit mode."

https://www.virtualbox.org/manual/ch03.html#intro-64bitguests

Also, I'd make sure the Paravirtualization Interface for any Linux Guest is set to KVM.

Because they maybe using older versions of Virtualbox (pre 6.X), or are using Guests created on on older versions of Virtualbox.

If you really want to, you can run "vboxmanage modifyvm" command with the "-accelerate2dvideo on" flag to set said 2D acceleration flag for your Guests even if there is not a GUI option to do so. See - https://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm

However, this flag is ignored when running said Guests under the latest builds of Virtualbox.

Well, that's what I was thinking, too. I guess I was hoping the bios delay might also be applied to the EFI logo. I checked here: https://www.virtualbox.org/manual/ch08.html

From what I can tell, there is no real equivalence to --bioslogodisplaytime for EFI. This might just be a fundamental limitation of VirtualBox, unfortunately. I know EFI is only somewhat supported.

It should have asked you what type of operating system you'll be running inside the VM when you created it. You should've selected "Windows 10 64-bit."

I suggest reading chapter 1.7 of the VirtualBox manual if you have any further troubles creating a virtual machine.

Hello,

Please see a description of the network modes

Basically, bridged mode is having your VM obtain an IP from your router and act as another physical computer on your network. Because of that, the packets being transferred for the VM will not be captured by the host machine and thus will not be sent through the VPN.

You either will need to install the VPN software on the VM, or switch to NAT networking so everything goes through your host. (I would still check to make sure it is going to the VPN, though). If you need to be able to access your VM from the host as if it were a server you can also set up a second host-only network adaptor on the VM to allow you to do that.

Then you can set the IPs through the GUI, using ifconfig (which I think is depracted in favour of ip now) etc. Google is your friend there

With regards to which adapter type, take a look at the link below, near the top you'll find a table which tells you how each networking mode talks to another machine. If all you want is the VMs talking to each other you'll probably want internal, if you want them to talk to the host as well you'll need host-only and if they need Internet access it'll probably be bridged or NAT. But the table does a better job of describing this so have a quick read of 6.2 in that link

https://www.virtualbox.org/manual/ch06.html

Hello,

Please see:

https://www.virtualbox.org/manual/ch01.html#intro-removing for moving a VM, and

https://www.virtualbox.org/manual/ch05.html#vdis

For more info on only moving the disk image attached to the VM.

(For VirtualBox versions 6.*)

When the guest OS is loaded and you're logged in, you should be able to go to Devices > Insert Guest Additions CD. In the guest OS, you should be able to use the script or installer executable and reboot the machine. Depending on the OS (ie, Windows), it'll sometimes require you to boot into safe mode to install the Guest Additions for GPU related drivers.

See: https://www.virtualbox.org/manual/ch04.html

I will say, if you're attempting to access a dedicated GPU directly, that would require something called GPU pass-through, which is not widely supported in VirtualBox.

https://www.virtualbox.org/wiki/Downloads

Look under “VirtualBox 5.2.14 Oracle VM VirtualBox Extension Pack”

Guest OS refers to the virtualized system you’re using, in your case Linux. Host OS is the system running virtualbox, in your case, MacOS.

I know there are guest additions available for MacOS because I literally just set it up a few hours ago for a friend.

Yes, it's possible.

You can create a device filter which instructs the host to automatically pass the usb device to the guest instead of trying to mount it.

Check the manual for more information.

I used VMWare for a long time, but I'm totally in love with virtualbox now. And it's free. Crazy. Update: From this page: https://www.virtualbox.org/wiki/Downloads it says for technical reasons the windows version will be available later.

If you go to this link: https://www.virtualbox.org/wiki/Download_Old_Builds_5_2 There is a 5.2 build that you can download, that will be, for all intents and purposes, just as good.

chapter 6. Even i was stuck when i started.
Look at the table for better understanding.
If you still have questions PM me I'll be happy to solve, if possible.

Starting with version 3.2, VirtualBox has <strong>experimental</strong> support for Mac OS X guests.

Basically, OS X guests might work on OS X hosts. As for no 64-bit options for any guest OSs that's usually down to BIOS settings/hardware virtualization support. Your host OS has to be 64 bit.

But other than selecting 32/64 bit, choosing the OS type for the VM helps you with some defaults. But nothing is stopping you from selecting windows 8.1 then installing linux.

Sorry, my post was confusing because of the typo. I mentioned PIIX4 initially, but that was a typo and I edited the post to mention PIIX3, the northbridge.

In VirtualBox you can set the northbridge as either PIIX3 or ICH9. Only the latter supports 36 NICs. Here's some commands to show the chipset and available NICs:

(vega:21:00:PST)% VBoxManage showvminfo voyager|grep -i chipset Chipset: piix3 (vega:21:01:PST)% VBoxManage showvminfo cumulus|grep -i chipset
Chipset: ich9 (vega:21:01:PST)% VBoxManage showvminfo voyager|grep NIC|wc -l 8 (vega:21:01:PST)% VBoxManage showvminfo cumulus|grep NIC|wc -l
36

The voyager VM is limited to 8 NICs and the cumulus one is limited to 36.

To set it to ICH9, run this:

VBoxManage modifyvm vmname --chipset ich9

You'll get a warning indicating that IOAPIC is being turned on as well. Afterwards, you should be able to configure up to 36 NICs.

Here's some more info. about the ICH9 requirement: https://www.virtualbox.org/ticket/8805

Hope it helps!

So essentially you're trying to run nested virtualization? I don't think that's possible with Virtualbox at the root (see: https://www.virtualbox.org/ticket/4032) but it may be possible with Hyper-V on intel chips.

If it were me personally, and I could afford the down time. I'd shut it down and use the export functionality. Then try the import before decommissioning the old host. If you have any snapshots, you may want to consolidate them before all of this.

You may also wish to look in to teleporting. I've never tried it but if you can't afford down time this is probably your only option.

He is welcome to review the source code in the Subversion Repository and compile it himself. He's free to do the same with Firefox. Though I suspect you wouldn't be able to convince him of anything until you determine why he believes it is a virus and can then discredit those thoughts.

Firstly, you can't run a Windows executable in macOS (this is what the error dialog is telling you.)

Secondly the VirtualBox documentation is quite good.

Chapter 14.2. Known Issues https://www.virtualbox.org/manual/ch14.html

• Mac OS X guests:

• VirtualBox does not provide Guest Additions for Mac OS X at this time.

• The graphics resolution currently defaults to 1024x768 as Mac OS X falls back to the built-in EFI display support. See Section 3.13.1, “Video modes in EFI” for more information on how to change EFI video modes.

&nbsp;

Chapter 3.13.1 Video modes in EFI https://www.virtualbox.org/manual/ch03.html#efividmode

EFI provides two distinct video interfaces: GOP (Graphics Output Protocol) and UGA (Universal Graphics Adapter). Mac OS X uses GOP, while Linux tends to use UGA. VirtualBox provides a configuration option to control the framebuffer size for both interfaces.

To control GOP, use the following VBoxManage command:

VBoxManage setextradata "VM name" VBoxInternal2/EfiGopMode N

Where N can be one of 0,1,2,3,4,5 referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.

What version of virtualbox? WinXP is not supported by the latest version. You need to find an older version that supports installation on XP.

https://www.virtualbox.org/manual/ch01.html#hostossupport

You'll need to use the VirtualBox CLI (vboxmanage) to convert the virtual hard drive to VHD. Create a new VM in Hyper-V and attach the converted VHD.

"c:\program files\oracle\virtualbox\vboxmanage.exe" clonemedium disk --format vhd sourceDisk.vdi convertedDisk.vhd

Change sourceDisk and convertedDisk to your needs, possibly including full path in quotes.

https://www.virtualbox.org/manual/ch08.html#vboxmanage-clonevdi

Exact same problem here.

Maybe you'd like to include your debugging logs at this VirtualBox ticket:

https://www.virtualbox.org/ticket/16051

and at this Windows 10 Feedback Hub report:

feedback-hub:?contextid=531&feedbackid=b5d68a20-3388-46af-89f9-b77b6ea466f8&form=1&src=2

To my understanding, you just want to make sure your networking mode is set to NAT, which is the default. This puts the guest on a different IP network from the host but still allows the guest to access the internet. If the guest doesn't need internet access, then disable its network adapter altogether. Remember, there's no guarantee that a virtual machine configuration can be considered perfectly safe (e.g. there could be as-yet unknown exploits in the VirtualBox network stack), but malware researchers are using this type of setup all the time without problems.

Of course, don't enable host/guest clipboard sharing, drag-and-drop, or shared folders.

Shared Folder is what you are looking for.

First, install Guest Additions for Windows. Then in VM's settings, find the Shared Folder tab. Add a folder and make sure Auto-Mount is selected.

When you launch the VM, you should see your shared folder as a network device in Windows.

No come back here! The good redditors below (u/cmotdibbler and u/Vogtinator ) saved the day. What you need is the test builds that have the fix for new Win10 builds.

From u/cmotdibbler https://www.virtualbox.org/wiki/Testbuilds

I am having problems with my new laptop and usb3 passthrough. I have a Windows 8 host, and have now built a couple of different vm's. They all work fine, except for the USB as my new laptop has only usb3 ports. Scary part is I see two year old messages on virtualbox.org like this one. Note that it seems like someone posted a solution towards the bottom. Now whether it works for either of us is another story.

You are going to have to provide more detail, if you want folks to try figure out what you did.

Kali offers a number of ways to be run as a Guest VM in Virtual Box. These methods include -

1. Using one of the pre-built Guest VMs which you can import.
2. Running a Live version of it, with no persistence (i.e. no retention of any saved files or config changes on reboot).
3. Installation of Kali to the Guest, just as you would if you were installing any other Linux distro to real hardware.

Again, the behavior you describe is exactly what I'd expect to see if you did item No. 2. Also, if you imported a Guest VM (item No. 1) that was pre-built by another source, then you'd inherit what ever install options that were selected by the original creator of said VM (including no persistence if so configured by the creator).

I don't use Kali personally, but if the goal is to have control / customization over the Kali install to the Guest, I'd personally opt for option No. 3, and follow the instructions to do that here - https://www.kali.org/docs/installation/kali-linux-hard-disk-install/

I'm not going to argue with you about violating EULA but this site should be helpful. Virtual box runs your new os inside a window while windows is still running. It is not a dual boot method.

http://www.macbreaker.com/2015/01/virtualbox-yosemite-zone.html?m=1

As a side note. Your friends are jerks. It is not a just do x situation lol.

You can't just install VirtualBox on the external drive; it creates registry entries (on Windows at least) and is basically installed to that computer - virtual network cards and such. I've seen a few attempts to make a portable version, however have no experience with those. Here is an example. (I cannot vouch for it, again I've never used it before!)

Under normal circumstances VirtualBox has to be installed on each computer in order for what you want to work. There is a way to boot a direct OS in virtualbox off of USB but it is not recommended except when absolutely necessary. And even then you'd still need to install VirtualBox on the host first, create a new VM and have it boot off the USB drive.

My advice - use the live USB/SD card/SSD with linux installed.

Basically anything you can do through the GUI can be done through the API/CLI utilities. I suggest reviewing the entire manual for more details but here is the section you want.

So yes you can absolutely script things.

This is not an official VirtualBox subreddit but you can ask here as well and see if anyone can help you.

For official support, there is a forum, mailing list, IRC channel, and bug tracker: https://www.virtualbox.org/wiki/Community

Perhaps I've misunderstood you but it sounds like you want the VM to believe it has a wireless card and that is it's source of internet? If this is the case I don't believe you can do this currently. (with any hypervisor that I'm aware of) To do that you'd probably need this

However if you just want "internet" in the VM the host's NIC type wired/wireless doesn't matter. Like any hypervisor, VirtualBox does not passthrough your NIC, instead it gives the VM an emulated one. So the VM will see the one you selected in the settings (they are all wired devices).

Let me know if I've misunderstood the end goal here...

The VMs on your NAT Network can reach the internet. When using NAT Network, you can tell Virtual Box to enable a dhcp server for said NAT Network. You don't need a separate dhcp VM.

https://www.nakivo.com/blog/virtualbox-network-setting-guide/

https://www.nakivo.com/blog/virtualbox-network-setting-guide/

Depends on what you want to do with the VM.

A Host-Only Ethernet Adapter allows communication between the VM and the computer it's running on. For example, you can setup shared folders or run a web services on the VM and access it from the host. However it doesn't allow the VM to access anything else in your network, not even the internet.

This is not a Virtual Box issue. You basically did the equivalent of moving an existing file system to a new, larger drive. However, the file system was only setup to use the space available on the smaller, original drive. Accordingly, you must also expand the file system on said partitions to fill the newly created free space. You can use gparted (https://gparted.org/index.php), to do this.

Again, by default Virtual Box does not create or store data in any "new" partitions. The only time Virtual Box would use separate partitions would be if you setup your Guests to use Raw Disk access -- this is something you would have certainly remembered doing if you configured your Guests this way, as it would require some custom configuration. The partition you see in disk manager are likely recovery partitions, setup by your computer's manufacturer, and tied to backup features of your current Windows install (i.e. allows you to reinstall a fresh copy of Windows 10, or to roll back to prior version of the OS). Deleting them may result in your system not booting. Accordingly, I would not delete said partitions unless you know exactly what they are for, and what you are doing.

If you are confident that such partitions are not necessary anymore, then go ahead and download GPARTED (https://gparted.org/liveusb.php) and use it to create a bootable usb drive. Then use said usb drive to boot into the gparted utility, delete the partitions you don't want, and resize your existing C:\ to fill the rest of the space. If you manage do this successfully, you may need to repair the bootsector on the drive to get the system to boot. Of course, any resize operation may fail, and result in data loss.

My problem was/is when running homestead/vagrant, which uses VirtualBox. I was able to find a temporary solution, to this specific problem. I have tried it and it works. Check it out:

https://laracasts.com/discuss/channels/general-discussion/windows-10-vagrant-virtualbox-homestead?page=1#reply-85139

Specifically:

Install Virtualbox 5 and Vagrant 1.7.4

Comment line 17: config.vm.network :private_network, ip: settings["ip"] ||= "192.168.10.10" in homestead.rb

Comment line 64: b.use ClearNetworkInterfaces in action.rb (path ~\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox\action.rb)

Homestead init and/or up

Homestead halt

In Virtualbox preferences -> network -> host-only networks edit existing Host-Only adapter and add 192.168.10.10 as IP address

Select homestead box in Virtualbox and go to settings -> network -> adapter 2 and select Host-only network (the one edited in step above)

Homestead up, provision

Hope it helps!

I solved it by disabling the option [System] >> [Acceleration] >> "Enable VT-x / AMD-V". The rationale being that with this disabled the Win95 guest should never notice the modern host-CPU, only virtual CPU.

Tested with VirtualBox 6.0, software-based virtualization appears to have been removed/dropped from 6.1.0 (https://www.virtualbox.org/wiki/Changelog-6.1).

https://www.virtualbox.org/manual/ch04.html

> For any serious and interactive use, the Oracle VM VirtualBox Guest Additions will make your life much easier by providing closer integration between host and guest and improving the interactive performance of guest systems.

Really, you should ask Oracle. But I doubt it -

"VirtualBox is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use" (emphasis added)

See - https://www.virtualbox.org/wiki/VirtualBox

If that is what you want, it seem to me this is more what you are after -

https://www.virtualbox.org/manual/ch12.html#collect-debug-info

I can't speak for other hypervisors, as I don't have experience with them.

I don't use packer, but according to the Virtual Box manual -

"Before you can attach a VM to a host-only network you have to create at least one host-only interface. You can use the VirtualBox Manager for this. Choose File, Preferences, Network, Host-Only Network, (+)Add Host-Only Network.

Alternatively, you can use the command line:

VBoxManage hostonlyif create

See Section 8.35, “VBoxManage hostonlyif”.

For host-only networking, as with internal networking, you may find the DHCP server useful that is built into Oracle VM VirtualBox. This can be enabled to then manage the IP addresses in the host-only network since otherwise you would need to configure all IP addresses statically.

In the Oracle VM VirtualBox graphical user interface, you can configure all these items in the global settings by choosing File, Preferences, Network. This lists all host-only networks which are presently in use. Click on the network name and then on Edit. You can then modify the adapter and DHCP settings.

Alternatively, you can use VBoxManage dhcpserver on the command line. See Section 8.42, “VBoxManage dhcpserver”.

See - https://www.virtualbox.org/manual/ch06.html#network_hostonly

>As it installs in the VM, after some time I get an error saying that my disk drive is full.

Where is the error showing up? On your Host or your Guest / VM? If it is on your Host, then I'd simply opt to create the Virtual Hard Disk file (*.vdi) on another drive using the Virtual Media Manager.

https://www.virtualbox.org/manual/ch05.html#vdis

That being said, you may want to leave the *.vdi file on your SSD, and clear out some space. The Guest / VM will be markedly slower if you put the *.vdi on a spinning hard disk or drive.

How are you trying to install Virtual Box? I'd suggest you try the official, Oracle provided binaries as opposed to the ones maintained by Canonical.

https://www.virtualbox.org/wiki/Linux_Downloads

Note 1 - Oracle maintains its own repo for these binaries as well.

Note 2 - If you decide to make the switch, be sure to uninstall all the components of the Ubuntu provided binaries. These packages include the pre-built guest additions / host extensions modules. If you leave them installed, they can cause problems, especially since they may conflict with the Oracle provided binaries.

Host Extensions or Virtual Box Host Extensions provide USB passthrough support for your Guest, VRDP access mainly. You get them here - https://www.virtualbox.org/wiki/Downloads

Note - You build number / version of the Host Extensions must match the build / version number of the Virtual Box revision you are runing.

Guest Additions provide accelerated graphics support, improved mouse / keyboard integration, and shared folders for certain Guests. You usually get an ISO with them when you install Virtual Box.

You need to zero the virtual machine bit on the guest CPU (see VirtualBox CPUID documentation) and set lots of hardware parameters to values that appear genuine (see OpenCore PlatformInfo documentation

Because you have transparencies on in your Windows 10 Guest. Turn them off. Alternatively, disable 3D acceleration for your Windows 10 Guest. Your choice.

See - https://www.virtualbox.org/ticket/19365

>Not using any extensions/additions

If you want better display performance out of your Guest, I suggest you install Virtual Box Guest Additions on the Guest OS. Anyway, the refresh rate of your Guest is irrelevant, as the actual refresh rate of your monitor will be controlled / set by your Host. The refresh rate being reported by your Guest is just a placeholder.

See the discussion here - https://www.virtualbox.org/ticket/16101#:~:text=Windows%20guest%20desktop%20refresh%20rate%20is%20assumed%20to%20be%2060Hz,-Reported%20by%3A&amp;text=The%20host%20desktop%20vertical%20refresh,vertical%20refresh%20rate%20is%2060Hz.

Virtualbox can be set to offset guest time from the bios using --biossystemtimeoffset. Perhaps it would help? Change done with vboxmanage.

I wonder if virtualbox guest daemon is not resetting your time.

"Processor(s): Sets the number of virtual CPU cores the guest OSes can see. Oracle VM VirtualBox supports symmetrical multiprocessing (SMP) and can present up to 32 virtual CPU cores to each virtual machine.You should not configure virtual machines to use more CPU cores than are available physically. This includes real cores, with no hyperthreads."

https://www.virtualbox.org/manual/ch03.html#settings-processor

> Having discard enabled allows the VM to actually execute TRIM properly

OK, so this confirms what I've found.

> I doubt you're doing anything hard enough on it to prematurely age it.

Actually I do stuff that prematurely ages it, that's the reason for this post.

> I would enable Host Extensions, may as well, and that may have an effect on the ability of the VM to do TRIM properly (but I'd have to look that up).

I have not found anything about it that would help. The manual also does not list anything that seem relevant.

Just export the VM using Virtual Box -

https://www.virtualbox.org/manual/ch01.html#ovf-export-appliance

Use a CD imaging tool of your choice to create an ISO with said exported appliance (*.ova file).

First and foremost, you need understand that VirtualBox is not designed for gaming. The "3D Acceleration" feature is really just meant to allow simple hardware-accelerated animations and display effects to work better (like the "Aero" features introduced in Vista). Anything that relies heavily on video memory or high 3D frame rates will not perform well.

You should install guest additions. As long as you're running a supported guest operating system, don't expect anything to be stable until you have guest additions installed.

Another thing is holy crap you gave Windows Vista eight gigabytes of memory? Scale that back to like 2-4 GB, and make sure it has at least two CPU cores, maybe even four, since it looks like you may be CPU bound.

It might help to tell us what game you're running in case there are any specific requirements or anomalies that might affect the performance for better or worse.

If you are trying to take advantage of the automatic mounting, you need to make sure "Auto-mount" is enabled in the Shared Folders setting for the Guest under the Oracle VM Manager. You can specify the mount point there as well, though the default location would be in /media.

Otherwise, you can mount it manually -

In a Linux guest, use the following command:

mount -t vboxsf [-o OPTIONS] sharename mountpoint

To mount a shared folder during boot, add the following entry to /etc/fstab:

sharename mountpoint vboxsf defaults 0 0"

See - https://www.virtualbox.org/manual/ch04.html#sf_mount_manual

See this bug report, and the solutions described therein. If the *.cfg files are in a different directory from the one reported in the error message, then the solutions provided (assuming you take into account the directory said *.cfg files are in), will solve it.

That being said, when seeking help in this subreddit going forward, I suggest you indicate what OS your are running on your Host going forward. From the directory structure presented in your OP, I'm assuming its a form of Linux / Unix, and hence said bug report is applicable too.

https://www.virtualbox.org/ticket/17335

>Do you guys reckon what am I doing wrong?

I don't think you are in the right menu. In the Virtual Box VM Manager, select your Guest and open up the Settings > Network Menu. For Adapter 1, enable the Network Adapter, and in the "Attached to" field, select "Host Only".

In addition to this, you need to also configure Virtual Box to establish a Host only Network -

"Before you can attach a VM to a host-only network you have to create at least one host-only interface. You can use the VirtualBox Manager for this. Choose File, Preferences, Network, Host-Only Network, (+)Add Host-Only Network.

Alternatively, you can use the command line:

VBoxManage hostonlyif create

See Section 8.35, “VBoxManage hostonlyif”.

For host-only networking, as with internal networking, you may find the DHCP server useful that is built into Oracle VM VirtualBox. This can be enabled to then manage the IP addresses in the host-only network since otherwise you would need to configure all IP addresses statically.

In the Oracle VM VirtualBox graphical user interface, you can configure all these items in the global settings by choosing File, Preferences, Network. This lists all host-only networks which are presently in use. Click on the network name and then on Edit. You can then modify the adapter and DHCP settings.

Alternatively, you can use VBoxManage dhcpserver on the command line. See Section 8.42, “VBoxManage dhcpserver”."

See - https://www.virtualbox.org/manual/ch06.html#network_hostonly

>I managed to install a virtual floppy disk drive on the VM but it doesn’t see that a DVD-rom is inside the floppy disk so I guess they’re not “connected”.

The reason its not working is because your configuration is not supported. You cannot load the contents of a dvd, directly, through a virtual floppy disk. You need to convert the contents of the dvd to a RAW image file, then mount said image file in the virtual floppy drive. You can use dd to do this on Linux. See -

" Virtual floppy drives . . . can be connected to either a host floppy drive, if you have one, or a disk image, which in this case must be in RAW format."

https://www.virtualbox.org/manual/UserManual.html#settings-storage

>I'm using a kali linux vm and I insert the GA CD and I've gone into the folder for the GA and ran the executable and it errs out. "No matching drivers found in INF. No drivers installed...."

This error msg makes no sense. *.inf files are only used package drivers for Windows, not Linux. Accordingly, you could not have gotten said error message, as Guest Additions are to be installed within your Kali Linux Guest, not your Windows 10 Host. Linux by default would not be able run *.exe files, or use *.inf files.

I suggest you review the instructions from the Virtual Box Manual regarding installing Giest Additions on a Linux Guest.

https://www.virtualbox.org/manual/ch04.html#additions-linux

Note you can grab the latest Virtual Box Builds from Oracle's website, or alternatively, just add Oracle's repo to your Host's sources list.

https://www.virtualbox.org/wiki/Linux_Downloads

Sorry, misread your original post. Nonetheless the problem, and solution remains similar. As you can see in the Changelog, it was not until Virtual Box Build 6.0.16 that Guest Additions supported Linux Guests running Linux kernel version 5.4.

https://www.virtualbox.org/wiki/Changelog-6.0

Accordingly, the version of Virtual Box you are using (i.e. 6.0.14) will run fine on your Ubuntu 18.04 Host with a 4.15 kernel. But Guest Additions for that build will not work on your Guest (Ubuntu 20.04 with a 5.4 linux kernel). You still need to upgrade Virtual Box to resolve this, or down grade the kernel in your Guest.

Don't install guest additions via the package manager within the Linux Guest.

Follow the procedure provided in the Virtual Box Manual -

https://www.virtualbox.org/manual/ch04.html#additions-linux

Short answer -- you can't.

Longer answer -- said feature was on only available for Linux Hosts, running older versions of Virtual Box. It was removed from Virtual Box 6.1.0, in part because it did not really work. The Windows builds for Virtual Box never had this feature.

"Linux host: Drop PCI passthrough, the current code is too incomplete (cannot handle PCIe devices at all), i.e. not useful enough."

https://www.virtualbox.org/wiki/Changelog

>Any ideas why they did this?

Because it did not work. From the changelog -

"Linux host: Drop PCI passthrough, the current code is too incomplete (cannot handle PCIe devices at all), i.e. not useful enough"

https://www.virtualbox.org/wiki/Changelog

I've since installed the latest "developer" build from https://www.virtualbox.org/download/testcase/VirtualBox-6.1.97-140861-OSX.dmg

Note that in this case, the kexts aren't signed, so I had to boot to recovery and disable SIP and then I re-enabled it using `csrutil --without kext`.

So far, I'm not seeing random panics or segfaults, but vagrant keeps picking up the wrong port, trying to use the guest port of 22 instead of the host port of 2222 for SSH. So, I've not left VMs booted long enough to truly know that's fixed.

Okay, I have been experimenting. It looks like the 5.2 branch should still work. It just has a really terrible update process in Win10. I just upgraded to 5.2.44 (latest) and sure enough, I got errors:

VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT

https://www.virtualbox.org/ticket/16318

It seems to be a failure to replace a component or driver with a new version. I Installed, rebooted, reinstalled, rebooted again, repaired/reinstalled again (immediately at boot) and rebooted, then tried it. After the third reinstall it finally took, and the error cleared. This was also the first time that it gave me a warning with a process ID - which was for my gaming keyboard software. The third repair also only installed USB drivers rather than the other networking components that typically pop up for approval. That suggests to me that the other vbox drivers were already in place, and my gaming keyboard was somehow locking the USB drivers while running, so that they wouldn't install properly. VirtualBox just wasn't smart enough to report this on the first install attempt. I've had this keyboard for a long time (Corsair), so that could explain why my previous attempts to upgrade 5.2 failed.

Moral of the story: If you have a mechanical keyboard, shut off your Logitech/Corsair/Razer mouse or keyboard software using something like CCleaner, then reboot, then update VirtualBox, then reboot again and re-install or repair it, then turn it all back on and see if it's good.

I installed `6.1.x revision 140809` from https://www.virtualbox.org/download/testcase/VirtualBox-6.1.15-140809-OSX.dmg and I'm still getting random segfaults and kernel panics. All of my VMs are Ubuntu 18.04 based, and the crashes aren't predictable. For example, I can run `vagrant up` and get a kernel panic a few seconds after boot, destroy and restart and the VM will boot but processes will segfault.

Likewise, I downloaded a few older releases and they all had similar issues.

For anyone else trying, I think the note on that page about SIP is no longer valid as I was able to load the kernel extensions from the build without issue.

I'm on a MBP 16" / i9 / 10.15.7.

I'm unsure if this is your issue, but it is known that Catalina has some permission issues that causes Guests to crash. There are allegedly some preliminary fixes included in the latest test builds. You can get the latest test build here -

https://www.virtualbox.org/wiki/Testbuilds

>Any idea why articles like this suggest it just works?

Because there may have been some combination of different builds of Wayland and Virtualbox that actually worked with 3D acceleration at the time the articles were written? Because perhaps the authors of said articles did not test all possible configurations with all possible builds of Virtual Box and Wayland? I did not mean to imply that it could never work, but rather it would be less reliable than using XOrg with Virtual Box given these constraints.

That being said, I'd note over the last few months (and perhaps right before said articles were written), there have been a number of changes to Virtual Box, and Virtual Box Guest Additions that may improve compatibility with Wayland. I'd suggest updating to the latest building of Virtual Box if you want to use a Linux Guest that runs Wayland with 3D accelleration. These changes include -

(From: https://www.virtualbox.org/wiki/Changelog).

Changes in Virtual Box 6.1.10 - (Released May 5, 2020)

Guest Additions: Fixed resizing and multi monitor handling for Wayland guests. (bug #19496)

Guest Additions: Fixed VBoxClient error: The parent session seems to be non-X11. (bug #19590)

Changes in VirtualBox 6.1.12 (released July 14 2020)

Guest Additions, 3D: New experimental GLX graphics output

Guest Additions, 3D: Fixed releasing texture objects, which could cause guest crashes

Guest Additions: Improved resize coverage for VMSVGA graphics controller

Note: The current Virtual Box Build is 6.1.14, which was released earlier this month.

In order to emulate a wired network adapter I have to download some program, right?

No you don't, if you configure said OS to use AMD PCNet FAST III virtual network adapter for your Guest. See the Virtual Box manual for additional detalls. - https://www.virtualbox.org/manual/ch06.html#nichardware

>I'm on Debian 10 (Host), and CHK or any related function doesn't work on Debian. On my Ubuntu machine it works perfectly.
>
>One simple example is on my Windows 10 Client. If I press 'Super' to open the start menu on the client, it won't trigger it. Instead it will trigger the function I've set on the Host.

It's not clear from your post what the problem is here. Specifically, I can't tell whether you are comparing the behavior of different Guests on the same Debian 10 Host, or something else.

That being said, if you concerned about switching keyboard input from your Guest and Host via the Host key, then I suggest you look at the Virtual Box manual regarding the Host key, and how to switch input between the Guest and the Host. See - https://www.virtualbox.org/manual/ch01.html#keyb_mouse_normal

Once you setup the VM the way you want, you can simply copy the Virtual Machine directory or folder holding the virtual HD file and *.vbox file for the Guest (something like "$HOME/VirtualBox VMs/Example VM/") to a usb drive. Then copy the contents of the folder to an identical location on the other PC's you want to want to run the VM on.

If that's not good enough for you, once you configure the VM to your liking, merely export it via the OVF / OVA format, and copy the resulting *.OVF /*.OVA file to a USB drive. Then import the OVF / OVA onto the other computers of your choice. See the Virtual Box manual for more info - https://www.virtualbox.org/manual/ch01.html#ovf

Editing the vbox file is not the recommended method.

According to the manual you can remove a keyword by not specifying any data, have you tried that?

I'm guessing something like:

&#x200B;

>VBoxManage.exe setextradata "My VM Name" "CustomVideoMode1"

&#x200B;

Read the manual here https://www.virtualbox.org/manual/ch08.html#vboxmanage-extradata

Okay, assuming you have Guest Additions installed on all said Guests already, write a script or batch file on your Host, to call the following command for each for your Guest VMs.

https://www.virtualbox.org/manual/ch08.html#vboxmanage-sharedfolder

I had the same issue on a couple different OSes running 5.8 kernels. My issues (hard freezes) were fixed with the 6.1.13 test builds here: https://www.virtualbox.org/wiki/Testbuilds (for anyone who needs it)

What you need to do is review the Virtual Box manual on how switch between Host and Guest Inputs. See -

https://www.virtualbox.org/manual/ch01.html#keyb_mouse_normal

Note, installing Guest Additions in your, well Guest, makes this a smoother experience.

>I thought that vram to guest allocation was from guest os ram.

That may still be true, but the Virtual Box documentation does not confirm that. Rather, what the manual says is -

"Video Memory: Sets the size of the memory provided by the virtual graphics card available to the guest, in MB. As with the main memory, the specified amount will be allocated from the host's resident memory. Based on the amount of video memory, higher resolutions and color depths may be available."

https://www.virtualbox.org/manual/ch03.html#settings-display

>Just to clarify, so ideally I can assign only 1 cpu (among the 4 cpus showing up in virtual box) to the guest os, no?

That would be consistent with the standard recommendation, assuming a 2 core cpu, like the one you are using.

Your post was removed because we don't accept posts with the entire question being in the title.

In your case, I would read the VirtualBox manual. It's clear that you don't understand how virtual machines work. Think of them like another computer inside your computer. VirtualBox does not come with operating systems -- you have to provide the installation disk, just like a real computer. You need to download an ISO for whichever distro of Linux you want, then insert that into the virtual CD-ROM, and boot the machine. Then install it to the virtual disk, just go through the normal install process basically. After it's done installing, eject the disk from the virtual CD-ROM and reboot. Voila!

But seriously, read the VirtualBox Manual

1. Minimum recommended HD size for Ubuntu 18.04 is around 25 gigs. That being said it is Linux - you can strip this down significantly by dumping apps and services you don't need. Note, generally speaking the virtual disk for a Guest can only exist on a single partition. However, you can assign multiple virtual disk files to a Guest, and accordingly assign them different mount points in Linux (typically - /, /swap, /home, etc.) .
2. Uninstalling Virtual Box will recover a few hundred megs of space. But the un-installation process generally won't remove the virtual hard drives you created for your Guests. You will have to delete them manually.
3. Running off of USB external disk will negatively impact your Guest's disk I/O. Transfer speeds of USB I and II are below that of SATA III. USB III may have comparable transfer speed to SATA III, but way higher latency. Whether performance will be acceptable depends on your use case. If you are going to be using your Guest for tasks involving heavy disk I/O, I would not recommend it.
4. WSL 2 relies on Hyper-V on Windows Hosts. Virtual Box does not really play well with Hyper-V, so I always recommend turning WSL 2, Hyper-V, and other Hyper-V related services of Windows Hosts.
5. Read the Virtual Box Manual - https://www.virtualbox.org/manual/UserManual.html

Well, running any kind of software that requires significant 3D acceleration in a Virtual Box Guest can be bit of a hit and miss affair. Virtual Box Windows Guests only have limited 3D support (Direct X 8 or 9). This support is limited for Windows Vista and later (i.e. not Windows 98, not Windows XP) in the latest Virtual Box builds.

I suggest you read the Virtual Box Manual, if you are serious about pursuing this.

https://www.virtualbox.org/manual/UserManual.html

See - https://www.virtualbox.org/manual/UserManual.html#max-resolution-guests

Also make sure you are using the recommended vGPU for your guest (VMSVGA for Linux Guests) and have sufficient vram allocated to it for the resolution you want to run.

Note -

1. W/ Virtual Box 6.1.0+ - 3D acceleration was removed from VBoxVGA. See - https://www.virtualbox.org/wiki/Changelog for Virtual Box 6.1.0 (released December 10 2019)). Accordingly, enabling the 3D acceleration switch for Guests running on Virtual Box 6.1.x that use VBoxVGA vGPUs does not do anything.
2. Video memory set to 256 megs- you can set this using "VBoxManage modifyvm "Name of VM" --vram 256"