summaryrefslogtreecommitdiffstats
path: root/debian/virtualbox.files
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--debian/virtualbox.files/NEWS.Debian25
-rw-r--r--debian/virtualbox.files/README.Debian.xml173
-rwxr-xr-xdebian/virtualbox.files/VBox.sh90
3 files changed, 288 insertions, 0 deletions
diff --git a/debian/virtualbox.files/NEWS.Debian b/debian/virtualbox.files/NEWS.Debian
new file mode 100644
index 00000000..65411b84
--- /dev/null
+++ b/debian/virtualbox.files/NEWS.Debian
@@ -0,0 +1,25 @@
+virtualbox-ose (3.1.4-dfsg-2) unstable; urgency=low
+
+ virtualbox-ose no longer depends on QT4 to not force anyone to install QT4
+ even if the virtualbox-ose provided gui is not installed. However, QT4 is still
+ recommended because there is one little utility in virtualbox-ose that is
+ linked againbt QT4. This utility, VBoxTestOGL, is used to test for OpenGL
+ capabilities. So if you use OpenGL you might want to install QT4 nonetheless.
+ If you know your OpenGL capabilities you can of course also replace VBoxTestOGL
+ by /bin/true or /bin/false depending on your capabilities.
+
+ -- Michael Meskes <meskes@debian.org> Mon, 15 Feb 2010 20:53:12 +0100
+
+virtualbox-ose (2.0.6-dfsg-1) experimental; urgency=low
+
+ The way Host Interface Networking works has been completely rewritten with
+ VirtualBox 2. The main difference is that the complex bridging configuration
+ is no longer necessary. With the new mechanism, to enable Host Interface
+ Networking, all you need to do is to open the Settings dialog of a virtual
+ machine, go to the “Network” page and select “Host Interface” in the drop down
+ list for the “Attached to” field. Finally, select the desired host interface
+ from the list at the bottom of the page, which contains the physical network
+ interfaces.
+
+ -- Michael Meskes <meskes@debian.org> Thu, 20 Nov 2008 14:09:54 +0100
+
diff --git a/debian/virtualbox.files/README.Debian.xml b/debian/virtualbox.files/README.Debian.xml
new file mode 100644
index 00000000..bcec3635
--- /dev/null
+++ b/debian/virtualbox.files/README.Debian.xml
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<article>
+ <title>Virtualbox OSE for Debian</title>
+ <section>
+ <title>Guest utilities</title>
+ <para>
+ The guest utilities are provided as separate Debian packages. These
+ packages contain all features virtualbox-ose offers for Debian guests.
+ Guest utilities for operating systems not offering virtualbox-ose
+ packages have to be downloaded from the internet. The upstream provided
+ ISO images cannot be distributed with this package for licensing reasons.
+ The same holds for the externally provided WineD3D extensions.
+ </para>
+ </section>
+ <section>
+ <title>Different versions</title>
+ <para>
+ The Open Source Edition of VirtualBox contains most but not all
+ features of the closed-source VirtualBox product that is
+ distributed under different terms and available from the
+ <ulink url="http://virtualbox.org/wiki/Downloads"> Virtualbox
+ homepage</ulink>. Missing are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Remote Display Protocol (RDP) Server
+ </para>
+ <para>
+ This component implements a complete RDP server on top of
+ the virtual hardware and allows users to connect to a
+ virtual machine remotely using any RDP compatible client.
+ </para>
+ </listitem>
+ <listitem>
+ <para>USB support</para>
+ <para>
+ VirtualBox implements a virtual USB controller and supports
+ passing through USB 1.1 and USB 2.0 devices to virtual
+ machines.
+ </para>
+ </listitem>
+ <listitem>
+ <para>USB over RDP</para>
+ <para>
+ This is a combination of the RDP server and USB support
+ allowing users to make USB devices available to virtual
+ machines running remotely.
+ </para>
+ </listitem>
+ <listitem>
+ <para>iSCSI initiator</para>
+ <para>
+ VirtualBox contains a builtin iSCSI initiator making it
+ possible to use iSCSI targets as virtual disks without the
+ guest requiring support for iSCSI.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>64-bit guests</title>
+ <para>
+ Starting with version 2.0.0 VirtualBox also supports 64-bit guest operating systems,
+ under the following conditions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ You need a 64-bit processor with hardware virtualization support
+ and a 64-bit host operating system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You must run a 64-bit version of VirtualBox on that OS. This can
+ then run both 32-bit and 64-bit VMs; a 32-bit VirtualBox can only run 32-bit
+ VMs, regardless of the hardware.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You must enable hardware virtualization; software virtualization is not supported
+ for 64-bit VMs.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There is no specific setting to enable 64-bit support for a guest.
+ However, you should enable the I/O APIC for virtual machines that you intend to
+ use in 64-bit mode.
+ </para>
+ </section>
+ <section>
+ <title>How to provide networking to virtual machines</title>
+ <section>
+ <title>Mechanism</title>
+ <para>
+ VirtualBox can use three alternative mechanisms to provide
+ Ethernet networking to its virtual machines:b
+ </para>
+ <section>
+ <title>NAT</title>
+ <para>
+ This is the easiest to use type of setup: The virtual
+ ethernet interface is connected to a virtual NAT router
+ including a DHCP server that is implemented within
+ the VirtualBox host software.
+ </para>
+ <para>
+ This is the default mode. It usually does not require
+ any extra configuration on the host.
+ </para>
+ </section>
+ <section>
+ <title>Internal network</title>
+ <para>
+ In this mode, there is only connectivity within an
+ emulated network shared between two or more virtual
+ machines running in the same VirtualBox instance.
+ </para>
+ </section>
+ <section>
+ <title>Host interface</title>
+ <para>
+ The virtual ethernet interface is connected to a
+ real device on the host filtering out its traffic.
+ </para>
+ </section>
+ </section>
+ </section>
+ <section>
+ <title>Incompatibilities</title>
+ <para>
+ When upgrading from a pre 2.0.0 version to virtualbox might complaing
+ about a missing format attribute in the HardDisk tag of
+ <filename>~/.VirtualBox/VirtualBox.xml</filename>. Manually adding
+ 'format="vdi"' solves this.
+ </para>
+ <para>
+ A bug appeared in kernel 2.6.29 RC5 that broke virtualbox-ose. The fix
+ was added in 2.6.29.1. If you happen to use 2.6.29 and epxerience
+ problems starting your VMs please upgrade. In Debian all
+ linux-image-2.6.29 versions starting with Debian version 2.6.29-2 are
+ fine.
+ </para>
+ </section>
+ <section>
+ <title>See also</title>
+ <para>
+ Additional and updated information may be found on
+ <itemizedlist>
+ <listitem>
+ <para>
+ the
+ <ulink url="http://virtualbox.org/wiki/End-user_documentation">
+ End-user documentation</ulink> section of the official
+ VirtualBox site.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the
+ <ulink url="http://wiki.debian.org/VirtualBox">VirtualBox</ulink>
+ page in the Debian Wiki.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
+</article>
diff --git a/debian/virtualbox.files/VBox.sh b/debian/virtualbox.files/VBox.sh
new file mode 100755
index 00000000..f389681e
--- /dev/null
+++ b/debian/virtualbox.files/VBox.sh
@@ -0,0 +1,90 @@
+#!/bin/sh
+## @file
+# Oracle VM VirtualBox startup script, Linux hosts.
+#
+
+# written by Patrick Winnertz <patrick.winnertz@skolelinux.org> and
+# Michael Meskes <meskes@debian.org>
+# and placed under GPLv2
+#
+# this is based on a script by
+# Oracle VirtualBox
+#
+# Copyright (C) 2006-2015 Oracle Corporation
+#
+# This file is part of VirtualBox Open Source Edition (OSE), as
+# available from http://www.virtualbox.org. This file is free software;
+# you can redistribute it and/or modify it under the terms of the GNU
+# General Public License (GPL) as published by the Free Software
+# Foundation, in version 2 as it comes in the "COPYING" file of the
+# VirtualBox OSE distribution. VirtualBox OSE is distributed in the
+# hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
+#
+
+PATH="/usr/bin:/bin:/usr/sbin:/sbin"
+
+# VirtualBox installation directory
+INSTALL_DIR="/usr/lib/virtualbox"
+
+# Note: This script must not fail if the module was not successfully installed
+# because the user might not want to run a VM but only change VM params!
+
+if [ ! -c /dev/vboxdrv ]; then
+ cat << EOF
+WARNING: The character device /dev/vboxdrv does not exist.
+ Please install the virtualbox-dkms package and the appropriate
+ headers, most likely linux-headers-$(uname -r | cut -d- -f3).
+
+ You will not be able to start VMs until this problem is fixed.
+EOF
+fi
+
+SERVER_PID=`ps -U \`whoami\` | grep VBoxSVC | awk '{ print $1 }'`
+if [ -z "$SERVER_PID" ]; then
+ # Server not running yet/anymore, cleanup socket path.
+ # See IPC_GetDefaultSocketPath()!
+ if [ -n "$LOGNAME" ]; then
+ rm -rf /tmp/.vbox-$LOGNAME-ipc > /dev/null 2>&1
+ else
+ rm -rf /tmp/.vbox-$USER-ipc > /dev/null 2>&1
+ fi
+fi
+
+APP=`basename $0`
+case "$APP" in
+ VirtualBox|virtualbox)
+ exec "$INSTALL_DIR/VirtualBox" "$@"
+ ;;
+ VirtualBoxVM|virtualboxvm)
+ exec "$INSTALL_DIR/VirtualBoxVM" "$@"
+ ;;
+ VBoxManage|vboxmanage)
+ exec "$INSTALL_DIR/VBoxManage" "$@"
+ ;;
+ VBoxSDL|vboxsdl)
+ exec "$INSTALL_DIR/VBoxSDL" "$@"
+ ;;
+ VBoxVRDP|VBoxHeadless|vboxheadless)
+ exec "$INSTALL_DIR/VBoxHeadless" "$@"
+ ;;
+ VBoxAutostart|vboxautostart)
+ exec "$INSTALL_DIR/VBoxAutostart" "$@"
+ ;;
+ VBoxBalloonCtrl|vboxballoonctrl)
+ exec "$INSTALL_DIR/VBoxBalloonCtrl" "$@"
+ ;;
+ VBoxBugReport|vboxbugreport)
+ exec "$INSTALL_DIR/VBoxBugReport" "$@"
+ ;;
+ VBoxDTrace|vboxdtrace)
+ exec "$INSTALL_DIR/VBoxDTrace" "$@"
+ ;;
+ vboxwebsrv)
+ exec "$INSTALL_DIR/vboxwebsrv" "$@"
+ ;;
+ *)
+ echo "Unknown application - $APP"
+ exit 1
+ ;;
+esac
+exit 0
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-17 18:19:27 +0000