From: "David J. Allen" <codermotor@gmail.com>
To: documentation@lists.ipfire.org
Subject: Re: Xen Documentation
Date: Mon, 16 Feb 2015 21:07:57 -0800 [thread overview]
Message-ID: <54E2CCAD.4080705@gmail.com> (raw)
In-Reply-To: <54E2BF83.60007@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
On 02/16/2015 08:11 PM, R. W. Rodolico wrote:
> I am in the process of creating documentation for a Xen virtual IPFire
> install. If anyone else is doing it also, please let me know so we can
> collaborate. I'm hopeful to have it complete Friday 20 Feb.
>
> I am trying an install using the scon image. Assuming that works, should
> I also write documentation on how to do it from a standard "installer"
> installation?
>
> Again, if anyone else is doing this, please let me know so we do not
> duplicate efforts.
>
> Rod
I am not writing docs on doing so* but I have been running Ipfire in a
VM under KVM on Scientific Linux 6.x for a couple of years now. I think
setting up Ipfire was easier than getting the KVM set up right.
The VM host box has 2 onboard NICs, but I'm using a dual-NIC card in the
box which is dedicated to the Ipfire VM. The tricky part was figuring
out how to give Ipfire exclusive access to the WAN NIC without it being
accessible to the KVM host and the other VM guests.
* Although I should do it at least for myself - had to redo my
installation a while back after moving and had left no notes for myself.
Which of course resulted in re-inventing my own wheel! ;)
next prev parent reply other threads:[~2015-02-17 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 4:11 R. W. Rodolico
2015-02-17 5:07 ` David J. Allen [this message]
2015-02-17 9:10 ` R. W. Rodolico
2015-02-17 16:05 ` Michael Tremer
2015-02-17 21:34 ` R. W. Rodolico
2015-02-17 22:48 ` R. W. Rodolico
2015-02-20 1:04 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E2CCAD.4080705@gmail.com \
--to=codermotor@gmail.com \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox