Update to r47345:
Update Virtualization chapter: Remove hidden and outdated Xen section. Move sect2 FreeBSD as a guest entries to sect1 entries. They are too detailed to be sect2, and do not show in the TOC that way. Update the VirtualBox guest additions section a bit, mostly about X.
This commit is contained in:
Bjoern Heidotting
parent
cccca20409
commit
dd9376e2d3
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=49099
1 changed files with 32 additions and 351 deletions
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
$FreeBSD$
|
||||
$FreeBSDde: de-docproj/books/handbook/virtualization/chapter.xml,v 1.14 2010/07/03 14:29:30 jkois Exp $
|
||||
basiert auf: r47273
|
||||
basiert auf: r47345
|
||||
-->
|
||||
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="virtualization">
|
||||
<info><title>Virtualisierung</title>
|
||||
|
|
@ -49,15 +49,6 @@
|
|||
&apple; &mac; installieren.</para>
|
||||
</listitem>
|
||||
|
||||
<!--
|
||||
Note: There is no working/end-user ready Xen support for FreeBSD as of 07-2010.
|
||||
Hide all information regarding Xen under FreeBSD.
|
||||
|
||||
<listitem>
|
||||
<para>Wissen Sie, wie man &os; unter Linux mit
|
||||
<application>&xen;</application> installiert.</para>
|
||||
</listitem>
|
||||
-->
|
||||
<listitem>
|
||||
<para>Können Sie &os; unter µsoft.windows;
|
||||
und <application>Virtual PC</application> installieren.</para>
|
||||
|
|
@ -95,12 +86,9 @@
|
|||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
<sect1 xml:id="virtualization-guest">
|
||||
<title>&os; als Gast-Betriebssystem</title>
|
||||
|
||||
<sect2 xml:id="virtualization-guest-parallels">
|
||||
<title><application>Parallels</application> unter
|
||||
&macos; X</title>
|
||||
<sect1 xml:id="virtualization-guest-parallels">
|
||||
<title>&os; als Gast-Betriebssystem unter
|
||||
<application>Parallels</application> für &macos; X</title>
|
||||
|
||||
<para><application>Parallels Desktop</application> für &mac;
|
||||
ist ein kommerzielles Softwareprodukt, welches für
|
||||
|
|
@ -114,7 +102,7 @@
|
|||
in der Sie danach das gewünschte Gast-Betriebssystem (in
|
||||
unserem Fall &os;) installieren.</para>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-parallels-install">
|
||||
<sect2 xml:id="virtualization-guest-parallels-install">
|
||||
<title>Installation von &os; unter
|
||||
Parallels/&macos; X</title>
|
||||
|
||||
|
|
@ -240,9 +228,9 @@
|
|||
<imagedata fileref="virtualization/parallels-freebsd13"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-parallels-configure">
|
||||
<sect2 xml:id="virtualization-guest-parallels-configure">
|
||||
<title>&os; für den Einsatz unter
|
||||
<application>Parallels</application> konfigurieren</title>
|
||||
|
||||
|
|
@ -296,325 +284,13 @@
|
|||
<xref linkend="advanced-networking"/>.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<!--
|
||||
Deactive/hide this section as the instruction in there do NOT work anyore:
|
||||
- FreeBSD 7.0 has reached its EOL a long time ago.
|
||||
- The needed files from www.fsmware.com are not available anymore, as the
|
||||
server is dead. So it is impossible to follow the instructions in here.
|
||||
|
||||
jkois@FreeBSD.org, 2010-06-18
|
||||
|
||||
<sect2 id="virtualization-guest-xen">
|
||||
<sect2info>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Fukang</firstname>
|
||||
<surname>Chen (Loader)</surname>
|
||||
<contrib>Beigetragen von </contrib>
|
||||
</author>
|
||||
</authorgroup>
|
||||
</sect2info>
|
||||
|
||||
<title>&os; mit &xen; unter Linux einsetzen</title>
|
||||
|
||||
<para>Der <application>&xen;</application> Hypervisor ist ein
|
||||
als Open Source verfügbares Para-Virtualisierungsprodukt,
|
||||
das von der kommerziellen Firma XenSource unterstützt wird.
|
||||
Gast-Betriebssysteme werden dabei als domU-Domains,
|
||||
Host-Betriebssysteme hingegen als dom0 bezeichnet. Um eine
|
||||
virtuelle &os;-Instanz unter Linux auszuführen,
|
||||
müssen Sie zuerst <application>&xen;</application>
|
||||
für Linux dom0 installieren. Als Host-Betriebssystem
|
||||
wird im folgenden Beispiel die Distribution Slackware
|
||||
verwendet.</para>
|
||||
|
||||
<sect3 id="xen-slackware-dom0">
|
||||
<title>&xen; 3 unter Linux dom0</title>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>&xen; 3.0 von XenSource herunterladen</title>
|
||||
|
||||
<para>Laden Sie die Datei <ulink
|
||||
url="http://bits.xensource.com/oss-xen/release/3.0.4-1/src.tgz/xen-3.0.4_1-src.tgz">xen-3.0.4_1-src.tgz</ulink>
|
||||
von <ulink url="http://www.xensource.com/"></ulink>
|
||||
herunter.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<title>Den Tarball entpacken</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd xen-3.0.4_1-src</userinput>
|
||||
&prompt.root; <userinput>KERNELS="linux-2.6-xen0 linux-2.6-xenU" make world</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>Den dom0-Kernel neu kompilieren:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd xen-3.0.4_1-src/linux-2.6.16.33-xen0</userinput>
|
||||
&prompt.root; <userinput>make menuconfig</userinput>
|
||||
&prompt.root; <userinput>make</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<para>Ältere Versionen von
|
||||
<application>&xen;</application> müssen
|
||||
gegebenenfalls mit
|
||||
<command>make ARCH=xen menuconfig</command> näher
|
||||
spezifiziert werden.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<title>Einen Menü-Eintrag in die menu.lst von Grub
|
||||
aufnehmen</title>
|
||||
|
||||
<para>Editieren Sie <filename>/boot/grub/menu.lst</filename>
|
||||
und fügen Sie die folgenden Zeilen hinzu:</para>
|
||||
|
||||
<programlisting>title Xen-3.0.4
|
||||
root (hd0,0)
|
||||
kernel /boot/xen-3.0.4-1.gz dom0_mem=262144
|
||||
module /boot/vmlinuz-2.6.16.33-xen0 root=/dev/hda1 ro</programlisting>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<title>Starten Sie Ihren Computer neu, um &xen; zu
|
||||
aktivieren</title>
|
||||
|
||||
<para>Anschließend editieren Sie
|
||||
<filename>/etc/xen/xend-config.sxp</filename> und
|
||||
fügen die folgenden Zeilen hinzu:</para>
|
||||
|
||||
<programlisting>(network-script 'network-bridge netdev=eth0')</programlisting>
|
||||
|
||||
<para>Danach kann <application>&xen;</application>
|
||||
gestartet werden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/etc/init.d/xend start</userinput>
|
||||
&prompt.root; <userinput>/etc/init.d/xendomains start</userinput></screen>
|
||||
|
||||
<para>Damit ist dom0 gestartet:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>xm list</userinput>
|
||||
Name ID Mem VCPUs State Time(s)
|
||||
Domain-0 0 256 1 r––––– 54452.9</screen>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>&os; 7-CURRENT als domU verwenden</title>
|
||||
|
||||
<para>Laden Sie den &os;-domU-Kernel für
|
||||
<application>&xen; 3.0</application> sowie
|
||||
das Festplattenabbild von <ulink
|
||||
url="http://www.fsmware.com/">http://www.fsmware.com/</ulink>
|
||||
herunter:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current">kernel-current</ulink></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2">mdroot-7.0.bz2</ulink></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd">xmexample1.bsd</ulink></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Kopieren Sie <filename>xmexample1.bsd</filename>
|
||||
nach <filename>/etc/xen/</filename> und passen Sie
|
||||
die Einträge für Kernel und Festplattenabbild an
|
||||
Ihre Konfiguration an. Ihre Konfiguration sollte
|
||||
ähnlich dem folgenden Beispiel aussehen:</para>
|
||||
|
||||
<programlisting>kernel = "/opt/kernel-current"
|
||||
memory = 256
|
||||
name = "freebsd"
|
||||
vif = [ '' ]
|
||||
disk = [ 'file:/opt/mdroot-7.0,hda1,w' ]
|
||||
#on_crash = 'preserve'
|
||||
extra = "boot_verbose"
|
||||
extra += ",boot_single"
|
||||
extra += ",kern.hz=100"
|
||||
extra += ",vfs.root.mountfrom=ufs:/dev/xbd769a"</programlisting>
|
||||
|
||||
<para>Die Datei <filename>mdroot-7.0.bz2</filename> sollte
|
||||
unkomprimiert sein.</para>
|
||||
|
||||
<para>Als Nächstes muss der __xen_guest-Abschnitt in
|
||||
<filename>kernel-current</filename> verändert und das
|
||||
von <application>&xen; 3.0.3</application> benötigte
|
||||
VIRT_BASE hinzugefügt werden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>objcopy kernel-current -R __xen_guest</userinput>
|
||||
&prompt.root; <userinput>perl -e 'print "LOADER=generic,GUEST_OS=freebsd,GUEST_VER=7.0,XEN_VER=xen-3.0,BSD_SYMTAB,VIRT_BASE=0xC0000000\x00"' > tmp</userinput>
|
||||
&prompt.root; <userinput>objcopy kernel-current ––add-section __xen_guest=tmp</userinput></screen>
|
||||
|
||||
<screen>&prompt.root; <userinput>objdump -j __xen_guest -s kernel-current</userinput>
|
||||
|
||||
kernel-current: file format elf32-i386
|
||||
|
||||
Contents of section __xen_guest:
|
||||
0000 4c4f4144 45523d67 656e6572 69632c47 LOADER=generic,G
|
||||
0010 55455354 5f4f533d 66726565 6273642c UEST_OS=freebsd,
|
||||
0020 47554553 545f5645 523d372e 302c5845 GUEST_VER=7.0,XE
|
||||
0030 4e5f5645 523d7865 6e2d332e 302c4253 N_VER=xen-3.0,BS
|
||||
0040 445f5359 4d544142 2c564952 545f4241 D_SYMTAB,VIRT_BA
|
||||
0050 53453d30 78433030 30303030 3000 SE=0xC0000000. </screen>
|
||||
|
||||
<para>Nun kann die domU erstellt und gestartet werden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>xm create /etc/xen/xmexample1.bsd -c</userinput>
|
||||
Using config file "/etc/xen/xmexample1.bsd".
|
||||
Started domain freebsd
|
||||
WARNING: loader(8) metadata is missing!
|
||||
Copyright (c) 1992-2006 The FreeBSD Project.
|
||||
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
|
||||
The Regents of the University of California. All rights reserved.
|
||||
FreeBSD 7.0-CURRENT #113: Wed Jan 4 06:25:43 UTC 2006
|
||||
kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF
|
||||
WARNING: DIAGNOSTIC option enabled, expect reduced performance.
|
||||
Xen reported: 1796.927 MHz processor.
|
||||
Timecounter "ixen" frequency 1796927000 Hz quality 0
|
||||
CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1796.93-MHz 686-class CPU)
|
||||
Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
|
||||
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,
|
||||
DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
|
||||
Features2=0x4400<CNTX-ID,<b14>>
|
||||
real memory = 265244672 (252 MB)
|
||||
avail memory = 255963136 (244 MB)
|
||||
xc0: <Xen Console> on motherboard
|
||||
cpu0 on motherboard
|
||||
Timecounters tick every 10.000 msec
|
||||
[XEN] Initialising virtual ethernet driver.
|
||||
xn0: Ethernet address: 00:16:3e:6b:de:3a
|
||||
[XEN]
|
||||
Trying to mount root from ufs:/dev/xbd769a
|
||||
WARNING: / was not properly dismounted
|
||||
Loading configuration files.
|
||||
No suitable dump device was found.
|
||||
Entropy harvesting: interrupts ethernet point_to_point kickstart.
|
||||
Starting file system checks:
|
||||
/dev/xbd769a: 18859 files, 140370 used, 113473 free (10769 frags, 12838 blocks, 4.2% fragmentation)
|
||||
Setting hostname: demo.freebsd.org.
|
||||
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
|
||||
inet6 ::1 prefixlen 128
|
||||
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
|
||||
inet 127.0.0.1 netmask 0xff000000
|
||||
Additional routing options:.
|
||||
Mounting NFS file systems:.
|
||||
Starting syslogd.
|
||||
/etc/rc: WARNING: Dump device does not exist. Savecore not run.
|
||||
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
|
||||
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
|
||||
Starting usbd.
|
||||
usb: Kernel module not available: No such file or directory
|
||||
Starting local daemons:.
|
||||
Updating motd.
|
||||
Starting sshd.
|
||||
Initial i386 initialization:.
|
||||
Additional ABI support: linux.
|
||||
Starting cron.
|
||||
Local package initialization:.
|
||||
Additional TCP options:.
|
||||
Starting background file system checks in 60 seconds.
|
||||
|
||||
Sun Apr 1 02:11:43 UTC 2007
|
||||
|
||||
FreeBSD/i386 (demo.freebsd.org) (xc0)
|
||||
|
||||
login: </screen>
|
||||
|
||||
<para>Die domU sollte nun den
|
||||
&os; 7.0-CURRENT-Kernel ausführen:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>uname -a</userinput>
|
||||
FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan 4 06:25:43 UTC 2006
|
||||
kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF i386</screen>
|
||||
|
||||
<para>Das Netzwerk kann nun unter der domU konfiguriert werden.
|
||||
Die &os;-domU wird ein spezielles Gerät namens
|
||||
<devicename>xn0</devicename> verwenden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ifconfig xn0 10.10.10.200 netmask 255.0.0.0</userinput>
|
||||
&prompt.root; <userinput>ifconfig</userinput>
|
||||
xn0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX> mtu 1500
|
||||
inet 10.10.10.200 netmask 0xff000000 broadcast 10.255.255.255
|
||||
ether 00:16:3e:6b:de:3a
|
||||
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
|
||||
inet6 ::1 prefixlen 128
|
||||
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
|
||||
inet 127.0.0.1 netmask 0xff000000 </screen>
|
||||
|
||||
<para>Unter der Slackware-dom0 sollten einige
|
||||
<application>&xen;</application>-spezifische
|
||||
Netzwerkgeräte erscheinen:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ifconfig</userinput>
|
||||
eth0 Link encap:Ethernet HWaddr 00:07:E9:A0:02:C2
|
||||
inet addr:10.10.10.130 Bcast:0.0.0.0 Mask:255.0.0.0
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:815 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:204857 (200.0 KiB) TX bytes:129915 (126.8 KiB)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
UP LOOPBACK RUNNING MTU:16436 Metric:1
|
||||
RX packets:99 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:9744 (9.5 KiB) TX bytes:9744 (9.5 KiB)
|
||||
|
||||
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
|
||||
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
|
||||
RX packets:1853349 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:952923 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:1000
|
||||
RX bytes:2432115831 (2.2 GiB) TX bytes:86528526 (82.5 MiB)
|
||||
Base address:0xc000 Memory:ef020000-ef040000
|
||||
|
||||
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
|
||||
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
|
||||
RX packets:1400 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:815 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:129915 (126.8 KiB) TX bytes:204857 (200.0 KiB)
|
||||
|
||||
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
|
||||
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
|
||||
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:2 errors:0 dropped:157 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:1
|
||||
RX bytes:140 (140.0 b) TX bytes:158 (158.0 b)
|
||||
|
||||
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
|
||||
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
|
||||
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:112 (112.0 b) TX bytes:0 (0.0 b)</screen>
|
||||
|
||||
<screen>&prompt.root; <userinput>brctl show</userinput>
|
||||
bridge name bridge id STP enabled interfaces
|
||||
xenbr1 8000.feffffffffff no vif0.1
|
||||
peth0
|
||||
vif1.0</screen>
|
||||
</sect3>
|
||||
</sect2>
|
||||
-->
|
||||
<sect2 xml:id="virtualization-guest-virtualpc">
|
||||
<sect1 xml:id="virtualization-guest-virtualpc">
|
||||
<info>
|
||||
<title><application>Virtual PC</application> unter
|
||||
&windows;</title>
|
||||
<title>&os; als Gast-Betriebssystem unter
|
||||
<application>Virtual PC</application> für &windows;</title>
|
||||
|
||||
<authorgroup>
|
||||
<author><personname><firstname>Johann</firstname><surname>Kois</surname></personname><contrib>Übersetzt von </contrib></author>
|
||||
|
|
@ -630,7 +306,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
virtuelle Maschine konfiguriert und das gewünschte
|
||||
Betriebssystem installiert werden.</para>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-virtualpc-install">
|
||||
<sect2 xml:id="virtualization-guest-virtualpc-install">
|
||||
<title>&os; in <application>Virtual PC</application>
|
||||
installieren</title>
|
||||
|
||||
|
|
@ -770,9 +446,9 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
<imagedata fileref="virtualization/virtualpc-freebsd13"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-virtualpc-configure">
|
||||
<sect2 xml:id="virtualization-guest-virtualpc-configure">
|
||||
<title>&os; in <application>Virtual PC</application>
|
||||
konfigurieren</title>
|
||||
|
||||
|
|
@ -832,12 +508,13 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
linkend="advanced-networking"/>.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect2 xml:id="virtualization-guest-vmware">
|
||||
<sect1 xml:id="virtualization-guest-vmware">
|
||||
<info>
|
||||
<title><application>VMware Fusion</application> unter
|
||||
<title>&os; als Gast-Betriebssystem unter
|
||||
<application>VMware Fusion</application> für
|
||||
&macos;</title>
|
||||
|
||||
<authorgroup>
|
||||
|
|
@ -856,7 +533,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
konfigurieren und das gewünschte Gastbetriebssystem
|
||||
installieren.</para>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-vmware-install">
|
||||
<sect2 xml:id="virtualization-guest-vmware-install">
|
||||
<title>&os; in <application>VMware Fusion</application>
|
||||
installieren</title>
|
||||
|
||||
|
|
@ -996,9 +673,9 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
|
||||
<para>Nachdem die Konfiguration abgeschlossen ist, kann &os;
|
||||
gestartet werden.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect3 xml:id="virtualization-guest-vmware-configure">
|
||||
<sect2 xml:id="virtualization-guest-vmware-configure">
|
||||
<title>&os; unter <application>VMware Fusion</application>
|
||||
konfigurieren</title>
|
||||
|
||||
|
|
@ -1050,13 +727,18 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
linkend="advanced-networking"/>.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect2 xml:id="virtualization-guest-virtualbox-guest-additions">
|
||||
<sect1 xml:id="virtualization-guest-virtualbox-guest-additions">
|
||||
<title>&virtualbox; Gasterweiterungen auf einem &os;
|
||||
Gast</title>
|
||||
|
||||
<para>&os; funktioniert einwandfrei als Gast-Betriebssystem
|
||||
unter &virtualbox;. Die Virtualisierungs-Software steht
|
||||
für die meisten Betriebssysteme zur Verfügung, einschließlich
|
||||
&os;.</para>
|
||||
|
||||
<para>Die &virtualbox; Gasterweiterungen bieten Unterstützung
|
||||
für:</para>
|
||||
|
||||
|
|
@ -1083,7 +765,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>Die folgenden Kommandos werden im &os; Gastsystem
|
||||
<para>Diese Kommandos werden im &os; Gastsystem
|
||||
ausgeführt.</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -1166,7 +848,6 @@ EndSection</programlisting>
|
|||
</match>
|
||||
</device>
|
||||
</deviceinfo></programlisting>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 xml:id="virtualization-host-virtualbox">
|
||||
|
|
@ -1224,7 +905,7 @@ EndSection</programlisting>
|
|||
<screen>&prompt.root; <userinput>kldload vboxdrv</userinput></screen>
|
||||
|
||||
<para>Um sicherzustellen, dass das Modul immer nach einem Neustart
|
||||
geladen wird, fügen Sie die folgende Zeile in die Datei
|
||||
geladen wird, fügen Sie die folgende Zeile in
|
||||
<filename>/boot/loader.conf</filename> ein:</para>
|
||||
|
||||
<programlisting>vboxdrv_load="YES"</programlisting>
|
||||
|
|
|
|||
Loading…
Reference in a new issue