[Pkg-virtualbox-commits] r445 - in virtualbox-ose/trunk/debian: . virtualbox-ose.files
meskes at alioth.debian.org
meskes at alioth.debian.org
Sat Jan 24 20:04:12 UTC 2009
Author: meskes
Date: 2009-01-24 20:04:11 +0000 (Sat, 24 Jan 2009)
New Revision: 445
Added:
virtualbox-ose/trunk/debian/virtualbox-ose.files/NEWS.Debian
virtualbox-ose/trunk/debian/virtualbox-ose.files/README.Debian.xml
Removed:
virtualbox-ose/trunk/debian/virtualbox-ose.NEWS.Debian
virtualbox-ose/trunk/debian/virtualbox-ose.README.Debian.xml
Modified:
virtualbox-ose/trunk/debian/rules
virtualbox-ose/trunk/debian/virtualbox-ose.docs
Log:
Moved some docs into the corresponding files directory.
Modified: virtualbox-ose/trunk/debian/rules
===================================================================
--- virtualbox-ose/trunk/debian/rules 2009-01-24 19:08:52 UTC (rev 444)
+++ virtualbox-ose/trunk/debian/rules 2009-01-24 20:04:11 UTC (rev 445)
@@ -20,7 +20,7 @@
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
# Generate README.Debian as text/html ...
-debian/README.Debian.html: debian/virtualbox-ose.README.Debian.xml
+debian/README.Debian.html: debian/virtualbox-ose.files/README.Debian.xml
xsltproc --nonet --stringparam section.autolabel 1 \
-o $@ \
/usr/share/xml/docbook/stylesheet/nwalsh/html/docbook.xsl \
Deleted: virtualbox-ose/trunk/debian/virtualbox-ose.NEWS.Debian
===================================================================
--- virtualbox-ose/trunk/debian/virtualbox-ose.NEWS.Debian 2009-01-24 19:08:52 UTC (rev 444)
+++ virtualbox-ose/trunk/debian/virtualbox-ose.NEWS.Debian 2009-01-24 20:04:11 UTC (rev 445)
@@ -1,11 +0,0 @@
-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 at debian.org> Fri, 23 Jan 2009 14:45:54 +0100
-
Deleted: virtualbox-ose/trunk/debian/virtualbox-ose.README.Debian.xml
===================================================================
--- virtualbox-ose/trunk/debian/virtualbox-ose.README.Debian.xml 2009-01-24 19:08:52 UTC (rev 444)
+++ virtualbox-ose/trunk/debian/virtualbox-ose.README.Debian.xml 2009-01-24 20:04:11 UTC (rev 445)
@@ -1,150 +0,0 @@
-<?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>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>
- <listitem>
- <para>Emulation for Intel e1000 network devices</para>
- </listitem>
- <!-- FIXME web services? What else? -->
- </itemizedlist>
- </section>
- <section>
- <title>64-bit guests</title>
- Starting with version 2.0.0 VirtualBox also supports 64-bit guest operating systems,
- under the following conditions:
- <itemizedlist>
- <listitem>
- You need a 64-bit processor with hardware virtualization support
- and a 64-bit host operating system.
- </listitem>
- <listitem>
- 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.
- </listitem>
- <listitem>
- You must enable hardware virtualization; software virtualization is not supported
- for 64-bit VMs.
- </listitem>
- </itemizedlist>
- 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.
- </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 with previous versions</title>
- <para>
- Unfortunately, the configuration files between version version
- 1.4.0-svn4130 and 1.5.0 the configuration files are
- incompatible. In order to fix this issue please delete the
- complete <command><![CDATA[<Uart>]]></command> section in any
- <filename>~/.VirtualBox/Machines/NAME/NAME.xml</filename> files.
- </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>
Modified: virtualbox-ose/trunk/debian/virtualbox-ose.docs
===================================================================
--- virtualbox-ose/trunk/debian/virtualbox-ose.docs 2009-01-24 19:08:52 UTC (rev 444)
+++ virtualbox-ose/trunk/debian/virtualbox-ose.docs 2009-01-24 20:04:11 UTC (rev 445)
@@ -1,3 +1,3 @@
debian/README.Debian.html
debian/virtualbox-ose.files/wiki.html
-debian/NEWS.Debian
+debian/virtualbox-ose.files/NEWS.Debian
Copied: virtualbox-ose/trunk/debian/virtualbox-ose.files/NEWS.Debian (from rev 443, virtualbox-ose/trunk/debian/virtualbox-ose.NEWS.Debian)
===================================================================
--- virtualbox-ose/trunk/debian/virtualbox-ose.files/NEWS.Debian (rev 0)
+++ virtualbox-ose/trunk/debian/virtualbox-ose.files/NEWS.Debian 2009-01-24 20:04:11 UTC (rev 445)
@@ -0,0 +1,11 @@
+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 at debian.org> Fri, 23 Jan 2009 14:45:54 +0100
+
Copied: virtualbox-ose/trunk/debian/virtualbox-ose.files/README.Debian.xml (from rev 443, virtualbox-ose/trunk/debian/virtualbox-ose.README.Debian.xml)
===================================================================
--- virtualbox-ose/trunk/debian/virtualbox-ose.files/README.Debian.xml (rev 0)
+++ virtualbox-ose/trunk/debian/virtualbox-ose.files/README.Debian.xml 2009-01-24 20:04:11 UTC (rev 445)
@@ -0,0 +1,150 @@
+<?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>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>
+ <listitem>
+ <para>Emulation for Intel e1000 network devices</para>
+ </listitem>
+ <!-- FIXME web services? What else? -->
+ </itemizedlist>
+ </section>
+ <section>
+ <title>64-bit guests</title>
+ Starting with version 2.0.0 VirtualBox also supports 64-bit guest operating systems,
+ under the following conditions:
+ <itemizedlist>
+ <listitem>
+ You need a 64-bit processor with hardware virtualization support
+ and a 64-bit host operating system.
+ </listitem>
+ <listitem>
+ 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.
+ </listitem>
+ <listitem>
+ You must enable hardware virtualization; software virtualization is not supported
+ for 64-bit VMs.
+ </listitem>
+ </itemizedlist>
+ 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.
+ </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 with previous versions</title>
+ <para>
+ Unfortunately, the configuration files between version version
+ 1.4.0-svn4130 and 1.5.0 the configuration files are
+ incompatible. In order to fix this issue please delete the
+ complete <command><![CDATA[<Uart>]]></command> section in any
+ <filename>~/.VirtualBox/Machines/NAME/NAME.xml</filename> files.
+ </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>
More information about the Pkg-virtualbox-commits
mailing list