Date: Fri, 24 Jul 2015 10:52:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 201787] Better documentation for Xen domU support Message-ID: <bug-201787-9-b7r6Z7sIpi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201787-9@https.bugs.freebsd.org/bugzilla/> References: <bug-201787-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201787 --- Comment #4 from Jeroen <freebsd@dckd.nl> --- I've attached an example configuration that works on a Debian Dom0 with Xen 4.4 and the (now default) xl toolkit, this works with a 10.1 system. The configuration features two networking interfaces, which will be xl0 and xl1 consecutively in the FreeBSD. The IP addresses are not strictly necessary, but may be useful for administration on the Dom0 side. There are also two disks in the configuration, in this case the first is a LogicalVolume made on the Dom0. This disk will be presented as a raw disk to the Xen instance, and can be partitioned as desired, including ZFS. The `boot='c'` statement makes sure that the domU instance will boot from CD-ROM when one is connected. The `serial='pty'` statement makes sure that the console is properly connected, this can then be approached using `xl console` or using the `-c` flag when creating the domU. Finally the `vnc=0` statement disables VNC connection. This can be enabled by setting it to `1`, and uncommenting the following two lines. A VNC connection can then be made by using an SSH tunnel to the dom0 host, protected by a password, if desired. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201787-9-b7r6Z7sIpi>