Software for virtualisation for FreeBSD needed

[Marco]

>Okay, *now* I'm intrigued ... can you recommend a good 'setup guide'
for qemu
>under FreeBSD?  Or, a good generic one?
Actually its pretty simple to setup a qemu machine, what i realy enjoy
in qemu is the ability to emulate different architectures, for that
however i also have a "guide" i used when setting up a linux arm based
system on my fbsd. It's pretty much the same(actually its even easier)
to setup a x86 qemu based vm.

http://www.aurel32.net/info/debian_arm_qemu.php

hth,
 marco


Marc G. Fournier wrote:
>
> Okay, *now* I'm intrigued ... can you recommend a good 'setup guide'
> for qemu
> under FreeBSD?  Or, a good generic one?
>
> --On Friday, October 17, 2008 22:38:04 -0400 "Alexandre \"Sunny\"
> Kovalenko"
> <gaijin.k at gmail.com> wrote:
>
> > On Fri, 2008-10-17 at 21:28 -0300, Marc G. Fournier wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >>
> >>
> >> - --On Friday, October 17, 2008 08:05:14 -0400 "Alexandre \"Sunny\"
> >> Kovalenko"  <gaijin.k at gmail.com> wrote:
> >>
> >>> I am using VMware extensively on Linux and Windows hosts and QEMU on
> >>> FreeBSD host (with Windows, Linux and OpenSolaris guests)
> >> Can you run multiple guest QEMU environments simultaneously?  With
> >> networking?
> > Yes. <tentative>Yes.</tentative> ;)
>
> > I can definitely run multiple QEMU guests simultaneously. Did you have
> > any problems doing that?
>
> > Now, networking part is slightly trickier to answer. Let me try to map
> > this into VMware experience:
>
> > -- assigning IP addresses. I am doing static configurations. It Should
> > Not Be Hard (sm) to beat isc-dhcp into serving different address ranges
> > to different tapX, but I have not done it.
>
> > -- guest-to-guest internal networking. Easy: you have separate tapX with
> > their separate IP addresses, as long as you have
> > net.inet.ip.forwarding=1 set, it "just works".
>
> > -- nat-to-outside-world. Slightly harder, but doable:
> >   sunny:RabbitsDen>cat pf.nat.conf
> >   # Internal interfaces (for QEMU and or Bluetooth clients)
> >   int_if_0 = "tap0"
> >   int_if_1 = "tap1"
>
> >   # Private network for QEMU and Bluetooth clients
> >   private_network_0 = $int_if_0:network
> >   private_network_1 = $int_if_1:network
>
> >   # External interface (if we are providing NAT for the clients above)
> >   ext_if = "ath0"
>
> >   # Provide NAT services for private clients
> >   nat on $ext_if from $private_network_0 to any -> ($ext_if)
> >   nat on $ext_if from $private_network_1 to any -> ($ext_if)
>
> >   pass from { lo0, $private_network_0 } to any
> >   pass from { lo0, $private_network_1 } to any
> >   sunny:RabbitsDen>sudo pfctl -F nat
> >   sunny:RabbitsDen>sudo pfctl -f pf.nat.conf
>
> >   We are done. Admittedly, if you have many clients which flicker in and
> > out of existence, this gets very messy very quickly. Some scripting is
> > advised.
>
> > -- bridging-to-outside world. Have not tried it for the lack of need.
>
> > HTH,
>
> > --
> > Alexandre "Sunny" Kovalenko (
;5:A0=4@ >20;5=:>)
>
>
>
>