Скачать virtualbox 6

Установка пакетов в ОС ОН Орёл

Пакет VirtualBox и пакет расширений доступны в репозитории ОС ОН Орёл, но при установке системы эти пакеты по умолчанию не устанавливается.

Установка базового пакета

Установить пакеты virtualbox  и linux-headres-generic в ОС ОН Орёл можно из графического менеджера пакетов, или из командной строки командой:

Для нормальной работы старых версий базового пакета virtualbox требуется дополнительно установить пакет linux-headers-generic (в современных версиях устанавливается автоматически).

После установки пакета желательно перезагрузить машину.

Установка пакета расширений (при наличии доступа в Интернет)

Пакет расширений virtualbox-ext-pack доступен в репозитории ОС ОН Орёл, при установке системы по умолчанию не устанавливается.При установке пакет virtualbox-ext-pack обращается в Интернет для скачивания свежих обновлений, процедуру установки при отсутствии доступа к сети Интернет см. ниже.При наличии доступа к сети Интернет установить  пакет virtualbox-ext-pack в ОС ОН Орёл можно из графического менеджера пакетов, или из командной строки командой: 

sudo apt install virtualbox-ext-pack

Установка пакета расширений (в изолированной сети)

• Запустить VirtualBox.
• Выбрать в меню VirtualBox «Файл» — «Настройки» — «Плагины».
• Для добавления нового плагина нажать на кнопку с зелёным плюсом.
• Найти и выбрать ранее скачанный файл, и нажать кнопку «Открыть».
• Подтвердить согласие с установкой, прокрутить лицензионное соглашение до конца, подтвердить свой согласие с ним.
• Ввести пароль администратора.
• После этого пакет должен установиться.

Starting

Desktop

• Скачать virtualbox — установка множество ос на компьютер

  In KDE, go to: KDE menu > System > Oracle VM VirtualBox

• In GNOME, go to: Activities > List Applications > all (super + A) > Oracle VM Virtualbox

• In Mate, go to: Mate menu > Applications > System tools > Oracle VM VirtualBox

• In Xfce, go to: Application > System tools > Oracle VM VirtualBox

• From an X terminal:

  $ virtualbox
  
  Or
  
  $ VirtualBox

Server

You can start VirtualBox in Headless mode using VBoxHeadless like this:

$ VBoxHeadless -startvm "VMName"

You should run this inside a screen instance and detach the screen after starting the VM with Ctrl+a d. At least in version 4.0.x you won’t need to use screen. Just start the vm with:

$ VBoxManage startvm "VMName" --type headless

and a VBoxSVC process appears in the background. You can loggoff without problems.

Troubleshooting

The character device /dev/vboxdrv does not exist

When starting VirtualBox, the following message is shown:

WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-ose-modules package for your kernel and
load the module named vboxdrv into your system.

You will not be able to start VMs until this problem is fixed.

Load the VirtualBox kernel module (also load vboxnetflt in Debian Squeeze):

$ su
# modprobe vboxdrv

If the module is not found, refer to to provide a virtualbox-dkms* package to your system.

You are not a member of the «vboxusers» group

As stated by VirtualBox:

WARNING: You are not a member of the «vboxusers» group. Please add yourself
to this group before starting VirtualBox.

You will not be able to start VMs until this problem is fixed.

Add your user account to the vboxusers group via adduser(8), as described in :

$ su
# adduser yourusername vboxusers

Log out and log back in to your system to apply the group membership change.

Kernel driver not installed (rc=-1908)

You receive the following message

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

‘/etc/init.d/vboxdrv setup’

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

After running

$sudo /etc/init.d/vboxdrv setup

VirtualBox works fine until you reboot the system. This is because «vboxdrv» is not loaded during system boot. Solution. Make sure that you actually have these packages in your system1) dkms;2) build-essential;3) linux-headers-$(uname -r)Then, append the following line to /etc/modules

vboxdrv

See above.

RDP not working out of the box?

To get RDP working you need to install the VirtualBox Extensions Pack from the vendors website VirtualBox Downloads.

Simply download the extensions pack, click «File» => «Preferences» => «Extensions» => «Down arrow». Select the file you downloaded above. Click «OK». Restart VirtualBox.

Tips & Tricks

Switching consoles

The normal way to switch consoles in Linux is to use the ctrl-alt-Fx key combination. This does not work for a VirtualBox virtual machine (VM); it will switch consoles for the host system instead.

You should use <Host Key>-Fx instead, where <Host Key> is the key defined in File->Preferences->Input.

This also works for ctrl-alt-del and ctrl-alt-backspace

This is documented in the VirtualBox user manual in the section «Keyboard and mouse support in virtual machines», subsection «Typing special characters».

(An alternative method to switch between text consoles is to use alt-left and alt-right, but that does not work for graphical consoles like XOrg or DirectFB.)

How to remotely start virtual machines using VNC

Remote:

• log onto your remote box

• install tightvncserver

• launch it (you don’t need a display), pick a password
• determine which port it is using, a way to do so:

  • netstat -tap | grep vnc

  • Let’s say it’s 5901
• unlog from there since the server forked in the background

Local:

• install xtightvncviewer

• create a ssh tunnel to your box:

  ssh -L 5901:localhost:5901 you@remote

• use it: (note there are two colons)

  xtightvncviewer localhost::5901

• then VBoxManage startvm $yourvm &

• and start as many virtual machines as wanted.

Other Packages Related to virtualbox

• dep:
  adduser

  add and remove users and groups

• dep:
  init-system-helpers
  (>= 1.18~)

  helper tools for all init systems

• dep:
  iproute2

  networking and traffic control tools

• dep:
  libc6
  (>= 2.15)

  GNU C Library: Shared libraries also a virtual package provided by

  libc6-udeb

• dep:
  libcurl3-gnutls
  (>= 7.16.2)

  easy-to-use client-side URL transfer library (GnuTLS flavour)

• dep:
  libdevmapper1.02.1
  (>= 2:1.02.97)

  Linux Kernel Device Mapper userspace library

• dep:
  libgcc1
  (>= 1:3.0)

  GCC support library

  dep:
  libgcc1
  (>= 1:4.2)

• dep:
  libgsoap8

  Runtime libraries for gSOAP

• dep:
  libpng12-0
  (>= 1.2.13-4)

  PNG library — runtime

• dep:
  libpython3.5
  (>= 3.5.0~b1)

  Shared Python runtime library (version 3.5)

• dep:
  libsdl1.2debian
  (>= 1.2.11)

  Simple DirectMedia Layer

• dep:
  libssl1.0.0
  (>= 1.0.0)

  Secure Sockets Layer toolkit — shared libraries

• dep:
  libstdc++6
  (>= 5.2)

  GNU Standard C++ Library v3

• dep:
  libvncserver1
  (>= 0.9.10)

  API to write one’s own VNC server

• dep:
  libvpx3
  (>= 1.5.0)

  VP8 and VP9 video codec (shared library)

• dep:
  libx11-6

  X11 client-side library

• dep:
  libxcursor1
  (>> 1.1.2)

  X cursor management library

• dep:
  libxext6

  X11 miscellaneous extension library

• dep:
  libxml2
  (>= 2.7.4)

  GNOME XML library

• dep:
  libxmu6

  X11 miscellaneous utility library

• dep:
  libxt6

  X11 toolkit intrinsics library

• dep:
  procps

  /proc file system utilities

• dep:
  python3
  (

  interactive high-level object-oriented language (default python3 version)

  dep:
  python3
  (>= 3.5~)

• dep:
  python3.5

  Interactive high-level object-oriented language (version 3.5)

• dep:
  virtualbox-dkms
  (>= 5.1.38-dfsg-0ubuntu1.16.04.2)

  x86 virtualization solution — kernel module sources for dkms

  or
  virtualbox-source
  (>= 5.1.38-dfsg-0ubuntu1.16.04.2)

  x86 virtualization solution — kernel module source

  or
  virtualbox-modules

  virtual package provided by

  virtualbox-dkms

• dep:
  zlib1g
  (>= 1:1.1.4)

  compression library — runtime

• rec:
  libgl1-mesa-glx

  free implementation of the OpenGL API — GLX runtime

  or
  libgl1

  virtual package provided by

  libgl1-mesa-glx

• rec:
  libqt5core5a
  (>= 5.0.2)

  Qt 5 core module

• rec:
  libqt5opengl5
  (>= 5.0.2)

  Qt 5 OpenGL module

  or
  libqt5opengl5-gles
  (>= 5.0.2)

  Qt 5 OpenGL module — OpenGLES

• rec:
  libqt5widgets5
  (>= 5.0.2)

  Qt 5 widgets module

• rec:
  virtualbox-qt
  (= 5.1.38-dfsg-0ubuntu1.16.04.2)

  x86 virtualization solution — Qt based user interface

The VirtualBox development model

The source code of VirtualBox resides in a public Subversion repository which is hosted on this site. Currently, only Oracle employees have write access to ensure that only reviewed and tested patches find their way to the repository. However, over time, we would like to extend the group of people with write access.

Patches are always first applied to an internal Oracle repository and then automatically synchronized to the public repository. A large test laboratory at Oracle’s facilities and a dedicated test team in 24/7 operation ensure that the code quality remains excellent: dozens of test machines perform automated tests to spot regressions and monitor performance.

Automated build servers for all supported platforms create ready-to-run VirtualBox installers every time changes are made to the VirtualBox source code. These development builds provide end users with the latest features but may not necessarily be well tested or stable.

In addition to development builds, we also perform regular product releases based on a milestone plan. As we work hard to produce high quality software releases, it is important for all VirtualBox contributors to respect these milestones.

Alternatives

How to submit your contributions

If you have developed a patch for VirtualBox which you think could be useful for others and fits within the product’s architecture, then you should submit it for inclusion. As a first step, you should execute the Contributor’s Agreement as described above, which is a very straightforward and risk-free process. Then you should submit your patch to the vbox-dev mailing list or to the Developers Corner forum (see the «Community» page) along with a description of what it does. In case you have not signed the CA, please explicitly state that you are licensing the patch under the MIT license.

Please keep in mind that it might take some time to review your patch and integrate it. Also, please expect feedback from other developers on how to improve your patch and address potential issues. We can only incorporate your patch if it does not harm the product stability.

HAL

The hardware dependent portion of the Windows kernel is dubbed «Hardware Abstraction Layer» (HAL). While hardware vendor specific HALs have become very rare, there are still a number of HALs shipped by Microsoft. Here are the most common HALs (for more information, refer to this article: http://support.microsoft.com/kb/309283):

• Hal.dll (Standard PC)
• Halacpi.dll (ACPI HAL)
• Halaacpi.dll (ACPI HAL with IO APIC)

If you perform a Windows installation with default settings in VirtualBox, Halacpi.dll will be chosen as VirtualBox enables ACPI by default but disables the IO APIC by default. A standard installation on a modern physical PC or VMware will usually result in Halaacpi.dll being chosen as most systems nowadays have an IO APIC and VMware chose to virtualize it by default (VirtualBox disables the IO APIC because it is more expensive to virtualize than a standard PIC). So as a first step, you either have to enable IO APIC support in VirtualBox or replace the HAL. Replacing the HAL can be done by booting the VM from the Windows CD and performing a repair installation.

Allowing Oracle to incorporate your contributions

Even though VirtualBox’ source code is licensed to you under the GPL, it’s not enough to submit your patches under the GPL. The Licensing FAQ will tell you more about how Oracle handles VirtualBox licensing.

In any event, if you like to contribute anything that is subject to copyright (text, media, or code), Oracle must be legally certain they can redistribute the code you have contributed to their own customers who have purchased closed-source editions of VirtualBox. In order to be able to accept your contribution, we must therefore ask you to do one of two things:

1. Fill out the Contributor’s Agreement (CA) and send it to Oracle. With the CA, you give Oracle permission to use your contribution under licenses other than the main VirtualBox license. This is a once-in-a-lifetime event: once we have your CA, we will never again ask you to undergo any bureaucratic procedures, and all future contributions are covered.

1. If you don’t want to sign such an agreement, you can alternatively submit your contribution under the MIT license. This is a liberal, wide-spread Open Source license that allows Oracle (and anyone else) to use your contribution in both open-source and closed-source projects.

Basically, the main difference between the two options is this: With the CA, a written statement is necessary, but then only Oracle is allowed to relicense your code (unless you give other people the same permission). With the MIT license, you save the paperwork, but everyone else can use your code as well. It’s your choice.