Virtualbox Kurulumu

[Tavarus Calamia]

Incase we have installed the OSE edition of Virtual Box from the repositories we can add the guest additions from the repositories in the guest. This will install guest additions matching the Virtual Box version as obtained from the repositories. It is not recommended to install these in newer releases of Virtual Box as obtained from the Oracle repository (see below).

The .iso file with an image of the OSE edition of the guest additions CD will install in the host directory /usr/share/virtualbox/VBoxGuestAdditions.iso. Mount this .iso file as a CD in your virtual machine's settings. In the guest you will then have access to a CD-ROM with the installer.

In case the Guest Additions fail to build we may have to install the Linux kernel headers (see How do I install kernel header files?) or build-essential tools in addition. It is also recommended to have dkms installed (see below - Note 4). You can run this command in a terminal to install both:

Selecting Devices -> Install Guest Additions (or press Host+D from the Virtual Box Manager) the Guest Additions CD .iso will be loaded but not installed in your guest OS. To install we need to run the installer script VBoxLinuxAdditions.run as root or from the Autorun Prompt (see below).

Next step is to run the autorun.sh script (as root) on this mounted CD by opening the drive and clicking on the "Run Software" button. This will build and install the vbox kernel modules needed.

Note 2

In some systems the Virtual Box Guest Additions CD icon may not be shown on the desktop, but will be accessible from the Places menu. If the CD still was not there you may have to manually add the VBoxGuestAdditions.iso as a CD-ROM in the Virtual Box Manager Storage menu. In an Ubuntu host the disk image is in /usr/share/virtualbox/VBoxGuestAdditions.iso.

Note 3

In some systems (e.g. when running Xubuntu guests) we may not have an Autorun Prompt for the mounted CD. Then we can install the guest additions by opening a terminal on the mounted guest additions .iso to run sudo ./VBoxLinuxAdditions.run. In Lubuntu or Ubuntu Server guests we additionally need to install the GNU C compiler (gcc ) and the make utility in the guest system to be able to compile the guest additions.

Note 4

Running DKMS in the guest OS will keep Guest Additions installed after a guest kernel update. It is not a prerequisite for Guest Additions but if used it should be installed before we install the Guest Additions.

In case Guest Additions are not installed properly we may not be able to boot to the GUI. In this case we need to boot holding the Shift key to access the Grub menu where we access a root shell as depicted in the following question (we do need to mount the filesystem read/write to proceed):

In case something went wrong with installing the guest additions, or the guest OS can not boot after installing we may have to remove the additions. This can also be done from a root shell by running an uninstallation script located in the guest /opt directory.

This found and updated the correct version of the VirtualBox Guest Additions and my system seems to work properly again, and I'm assuming this will also work if Guest Additions are failing to install from the menu item.

Here are the steps I ran which finally worked, but as user named 'pcworld' stated above it may have been the case that only the last command was actually required. I'll never know, but I want to share in case this helps anyone else:

The virtualbox-guest-additions package has to be installed. Furthermore, it may appear that nothing has happened, but all the "Install Guest Additions" button do is mounting the cdrom. You should open the File manager (Nautilus / Dolphin), select the "CD device" and run the installer.

If the VBOXADDITIONS cd does not pop up in File Manager, Use File Manager to open the contents of the VBOXADDITIONS cd, then open a terminal there, by going to File Manager's menu and selecting 'Open Current Folder in Terminal'

Image links keep updating as new Debian versions are published, at the time of writing this was debian-live-12.4.0-amd64-xfce.iso. You can find the latest ones in live amd64 folder on cdimage.debian.org.The screenshots below are from Debian 10, the new 12 might have minor differences.

Install VirtualBox if you don't have it yet. If you're running Linux, it's usually just 'sudo apt-get update && sudo apt-get -y install virtualbox'. If your current computer (host) is Windows or OSX, download VirtualBox installer and run it.

Note: for latest VirtualBox in Windows, you must choose "Expert install" and "Skip Unattended Install". In my tests, installation did not run with Virtualbox "Unattended Install", and you could only select both "Skip Unattended Install" and "Debian (64-bit)" in "Expert mode".

Choose to Live. That's the default option, and it's chosen automatically if you just wait a couple of seconds. Usually, you should boot to live desktop even if you're going to install. That way, you can test Linux before you decide to install. And often the installer on Live mode is faster than the other installers.

Let's test that everything works. On top left, open "Applications" menu, choose "Web Browser". I googled "Tero Karvinen", clicked the top link and saw my homepage. Then I closed the browser. This tests the basic functionality of mouse, keyboard, network and display.

On the default option "Debian GNU/Linux", click "e". Update: In Debian 11, use TAB instead of e to edit GRUB options. Find the line that starts with "linux". Add the boot parameter " xforcevesa" to it. Press control-X to boot.

The boot start. In my case, I immediately noticed changes compared to black screen problem. I could see a text cursor blinking, then some funny letters and finally, the login screen. Thanks, xforcevesa!

Update: The few black screens I've seen were solved with xforcevesa trick above. If that does not help and you're feeling advanced, you can try: alt-ctrl-F1 for text mode console (use left ctrl, right ctrl is reserved by VirtualBox). Update all packages, install VirtualBox guest additions, then reboot. If nothing else helps, you could try with a different distribution, such as the latest Xubuntu.

So 'sudo' means use superuser privileges. You are automatically member of sudo group as the first user created in the installer. 'apt-get' is the package manager, it installs software. And "update" just updates information about what we could install.

This will take a while, as it upgrades everything. Don't interrupt the upgrade while it's working, and don't close the window before it's done. Normally, 'apt-get dist-upgrade' does not need a reboot. But here, the kernel "linux-image*" was upgraded, so we need to reboot soon.

With a real computer, you might be on your way now. But with VirtualBox, we still need to install drivers for our virtual devices. Why is the screen so small? If you stretch the window, your desktop doesn't get bigger, but you just get ugly, gray sorrow borders. You need to install VirtualBox Guest Additions. Also, guest additions will allow you to copy-paste between your host computer (the real physical one) and the guest (virtual) one.

So it likely says "blah blah blah".. "Running kernel modules will not be replaced until the system is restarted". It also says the same thing in a techinical way "modprobe vboxsf failed". So let's reboot, so we can start using the kernel modules (virtualbox virtual device drivers) we just built.

M1 and M2 Macs use arm64 architecture - that's ARM with an R. I don't have an M1 mac to test with, but you could try with Debian 11 arm64 image "Small CDs or USB sticks" "arm64". Or you could check Teemu Laine's instructions for running Debian 11 with UTM on Mac M1.

Tags:beginnervirtualboxdebianinstallbullseyelive>CommentsLoading comments... at least if you have JavaScript enabled.Related Articles on TeroKarvinen.comTwo Machine Virtual Network With Debian 11 Bullseye and VagrantStart a two computer virtual network in minutes.

Install VirtualBox for Mac using Homebrew. Run brew cask install virtualbox in your Terminal. VirtualBox lets you run virtual machines on your Mac (like running Windows inside macOS, except for a Kubernetes cluster.)

If you already have VirtualBox installed, start the installation as before with brew cask install virtualbox. You will get a warning that confirms this saying Warning: Cask 'virtualbox' is already installed.. Once this is confirmed, you can reinstall VirtualBox with Homebrew by running brew cask reinstall virtualbox.

If you happen to have VirtualBox already running when you do this, you could see an error saying Failed to unload org.virtualbox.kext.VBoxDrv - (libkern/kext) kext is in use or retained (cannot unload).

Client UI function

HCL homepage has been optimized, including improvements to project operations, project update record, packet capture, HCL Hub interaction, exercise and competition functions, and overall usability.

One-click repair and upgrade functions have been added to the HCL homepage, along with an updated User Guide.

Simulation product updates

Wireless Device Optimization: AP now supports enabling multiple radios, connecting up to 35 terminal devices, and adjusting signal range size through the radio. Additionally, AC and AP now support network card enhancement, while AC supports IRF.

Addition of Cloud devices: Cloud can now connect to other devices with HCL or third-party software through UDP tunneling.

VPCS devices have been added, simulating virtual PCs with expanded functions and optimized resource consumption.

Server2 devices have been added, based on Openwrt and providing basic Openwrt functions for experiments, with customizable configurations for FTP, DNS, Radius authentication, multicast simulation, 802.1x clients, and other services.

Custom devices now support H3C NFV devices and allow configuration of device images in settings, currently supporting VSR/VFW series products.

Certain devices now support network card enhancement function, enabling the expansion of connection interfaces.

Performance optimization of simulated devices.

3a8082e126