From subbsd at gmail.com  Thu Apr  2 10:00:48 2009
From: subbsd at gmail.com (subbsd)
Date: Thu Apr  2 10:00:55 2009
Subject: how to move physical interface into multiple vimage interfaces
Message-ID: <200904022043.57984.subbsd@gmail.com>

Hello maillist

i fetch and apply latest http://imunes.tel.fer.hr/virtnet/vimage-20081015.tgz 
patches for 7.2 i386 for testing vimage.

All according man page work done. 
Small bug: vimage -i with 1 arguments make core dumped:

# vimage -i onearg
Segmentation fault (core dumped)

and bridge cannot worked:
kldload if_bridge.ko
link_elf: symbol ifnet undefined
KLD if_bridge.ko: depends on bridgestp - not available


And i've want asking:
may i using 1 physical or vlan interface as parent for multiple vimage 
interfaces? something like
vimage -c sw1
vimage -c sw2
vimage -c sw3

vimage -i sw1,sw2,sw3 em0

Thanks for information




From zec at icir.org  Thu Apr  2 10:53:22 2009
From: zec at icir.org (Marko Zec)
Date: Thu Apr  2 10:53:28 2009
Subject: how to move physical interface into multiple vimage interfaces
In-Reply-To: <200904022043.57984.subbsd@gmail.com>
References: <200904022043.57984.subbsd@gmail.com>
Message-ID: <200904021935.25688.zec@icir.org>

On Thursday 02 April 2009 18:43:57 subbsd wrote:
> Hello maillist
>
> i fetch and apply latest
> http://imunes.tel.fer.hr/virtnet/vimage-20081015.tgz patches for 7.2
> i386 for testing vimage.

Hi,

if you're running 7.2-PRERELASE or similar you'll probably have more 
luck trying out the latest sys tarball tracking 7-stable: 
http://imunes.tel.fer.hr/virtnet/vimage_7_20090401.tgz

> All according man page work done.
> Small bug: vimage -i with 1 arguments make core dumped:
>
> # vimage -i onearg
> Segmentation fault (core dumped)

You're right, this needs to be fixed...

> and bridge cannot worked:
> kldload if_bridge.ko
> link_elf: symbol ifnet undefined
> KLD if_bridge.ko: depends on bridgestp - not available

if_bridge is not virtualized yet, so as an alternative, I'd suggest you 
try out netgraph bridging which works quite well vith virtual stacks.  
There's a tutorial describing how to use netgraph with vimages - pls. 
take a look at this: 
http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf

> And i've want asking:
> may i using 1 physical or vlan interface as parent for multiple
> vimage interfaces? something like
> vimage -c sw1
> vimage -c sw2
> vimage -c sw3
>
> vimage -i sw1,sw2,sw3 em0

No it won't work that way - a single interface (physical, vlan, 
whatever) can be assigned to only one vimage at a time.  So to make 
multiple vimages visible via a single physical card you should create 
virtual interfaces for vimages and bridge them to the physical one.  
Here's an example:

tpx32# vimage -c sw1
tpx32# vimage -c sw2
tpx32# vimage -c sw3
tpx32# ngctl mkpeer eiface ether ether
tpx32# ngctl mkpeer eiface ether ether
tpx32# ngctl mkpeer eiface ether ether
tpx32# kldload ng_ether
tpx32# ngctl mkpeer em0: bridge lower link0
tpx32# ngctl name em0:lower b0
tpx32# ngctl connect em0: b0: upper link9
tpx32# ngctl connect ngeth0: b0: ether link1
tpx32# ngctl connect ngeth1: b0: ether link2
tpx32# ngctl connect ngeth2: b0: ether link3
tpx32# vimage -i sw1 ngeth0
eth0@sw1
tpx32# vimage -i sw2 ngeth1
eth0@sw2
tpx32# vimage -i sw3 ngeth2
eth0@sw3
tpx32# 
tpx32# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:16:41:15:4d:3e
        inet6 fe80::216:41ff:fe15:4d3e%em0 prefixlen 64 scopeid 0x3 
        inet6 a:2::51 prefixlen 64 
        inet 192.168.200.110 netmask 0xffffff00 broadcast 
192.168.200.255
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 
        inet 127.0.0.1 netmask 0xff000000 
tpx32# ping 192.168.200.1
PING 192.168.200.1 (192.168.200.1): 56 data bytes
64 bytes from 192.168.200.1: icmp_seq=0 ttl=255 time=4.668 ms
64 bytes from 192.168.200.1: icmp_seq=1 ttl=255 time=2.625 ms
^C
--- 192.168.200.1 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.625/3.647/4.668/1.022 ms
tpx32# ifconfig em0 promisc
tpx32# vimage sw1
Switched to vimage sw1
# ifconfig
lo0: flags=8008<LOOPBACK,MULTICAST> metric 0 mtu 16384
eth0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:00:00:00:00:00
# ifconfig lo0 localhost
# ifconfig eth0 link 42:1:2:3:4:1
# dhclient eth0
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPNAK from 192.168.200.31
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.200.31
DHCPOFFER from 192.168.200.32
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.200.31
bound to 192.168.200.112 -- renewal in 1800 seconds.
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
eth0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
        ether 42:01:02:03:04:01
        inet6 fe80::d41d:8cd9:8f00:b204%eth0 prefixlen 64 scopeid 0x2 
        inet 192.168.200.112 netmask 0xffffff00 broadcast 
192.168.200.255
# ping 192.168.200.1
PING 192.168.200.1 (192.168.200.1): 56 data bytes
64 bytes from 192.168.200.1: icmp_seq=0 ttl=255 time=4.833 ms
64 bytes from 192.168.200.1: icmp_seq=1 ttl=255 time=2.619 ms
64 bytes from 192.168.200.1: icmp_seq=2 ttl=255 time=2.544 ms
^C
--- 192.168.200.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.544/3.332/4.833/1.062 ms
# 
From julian at elischer.org  Thu Apr  2 10:55:46 2009
From: julian at elischer.org (Julian Elischer)
Date: Thu Apr  2 10:55:54 2009
Subject: how to move physical interface into multiple vimage interfaces
In-Reply-To: <200904022043.57984.subbsd@gmail.com>
References: <200904022043.57984.subbsd@gmail.com>
Message-ID: <49D4F932.3060704@elischer.org>

subbsd wrote:
> Hello maillist
> 
> i fetch and apply latest http://imunes.tel.fer.hr/virtnet/vimage-20081015.tgz 
> patches for 7.2 i386 for testing vimage.
> 
> All according man page work done. 
> Small bug: vimage -i with 1 arguments make core dumped:
> 
> # vimage -i onearg
> Segmentation fault (core dumped)
> 
> and bridge cannot worked:
> kldload if_bridge.ko
> link_elf: symbol ifnet undefined
> KLD if_bridge.ko: depends on bridgestp - not available

thankyou. will inverstigate.

BTW most work on vimage is happening in -currrent
so it may taek time to fix this..

> 
> 
> And i've want asking:
> may i using 1 physical or vlan interface as parent for multiple vimage 
> interfaces? something like
> vimage -c sw1
> vimage -c sw2
> vimage -c sw3
> 
> vimage -i sw1,sw2,sw3 em0

no

an interface can only be in one vimage at a time.

Marko uses the netgraph bridge node (ng_bridge) and netgraph ng_eiface
nodes to 'bridge' a single interface to many virtual interfaces, and
then puts different virtual interfaces in each vimage.

Hopefully he can provide you with more detailed information on how he 
does this.

> 
> Thanks for information
> 
> 
> 
> 
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"

From subbsd at gmail.com  Sun Apr  5 12:18:04 2009
From: subbsd at gmail.com (subbsd)
Date: Sun Apr  5 12:18:10 2009
Subject: how to apply latest vimage patch for 8-HEAD
Message-ID: <200904052250.06913.subbsd@gmail.com>

Hello maillist,

I've try to test latest vimage on 8.0-CURRENT FreeBSD. Upgrade to latest HEAD
version FreeBSD is succesfull (using i386 arch):

--- (my steps) ---
1) svn checkout svn://svn.freebsd.org/base/head /usr/src
2) cd /usr/src; 
3) make buildworld; make kernel KERNCONF="GENERIC";
5) nextboot -k kernel -o "-s"; reboot
 (in single mode): 
6) cd /usr/src 
7) make installworld
8) yes |make delete-old
9) yes| make delete-old-libs
10) mergemaster
11) /sbin/reboot
---

So, i get what i want:
%sysctl -a | grep kern.osr\*
kern.ostype: FreeBSD
kern.osrelease: 8.0-CURRENT
kern.osrevision: 199506
kern.osreldate: 800074


Next, i've fetch latest vimage patch for HEAD:

fetch http://imunes.tel.fer.hr/virtnet/vimage-20081015.tgz
tar xfz vimage-20081015.tgz
cp -R vimage/src/usr.sbin/vimage /usr/src/usr.sbin/
mv /usr/src/sys /usr/src/sys-orig (for backup original)
mv vimage/src/sys /usr/src

and running make buildworld but it unsuccessful with messages in stdout:
--
...
--------------------------------------------------------------
>>> stage 3.2: building everything
--------------------------------------------------------------
cd /usr/obj/usr/src/sys/VIMAGE; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  
MACHINE=i386  CPUTYPE=  GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font  
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac  
_SHLIBDIRPREFIX=/usr/obj/usr/src/tmp  VERSION="FreeBSD 8.0-CURRENT i386 
800062"  INSTALL="sh /usr/src/tools/install.sh"  
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin 
NO_CTF=1 make KERNEL=kernel all -DNO_MODULES_OBJ
cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -
Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -
Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  
-I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -
DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-
limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000  
-mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -
mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror  
/usr/src/sys/netinet/tcp_timewait.c
/usr/src/sys/netinet/tcp_timewait.c: In function 'tcp_twstart':
/usr/src/sys/netinet/tcp_timewait.c:219: error: 'vnet_inet' undeclared (first 
use in this function)
/usr/src/sys/netinet/tcp_timewait.c:219: error: (Each undeclared identifier is 
reported only once
/usr/src/sys/netinet/tcp_timewait.c:219: error: for each function it appears 
in.)
*** Error code 1

Stop in /usr/obj/usr/src/sys/VIMAGE.
*** Error code 1


--



And.. I could not understand how to use update.sh ;(
I install (/usr/ports/devel/perforce) p4 utility , then have copied contents 
vimage in/usr/src and have started update.sh

bs0# sh update.sh
--
Current working directory is: /usr/src
confirm you have cd'd to the base of the correct tree. (^C to exit)
========= printing open files ==========
Perforce client error:
        Connect to server failed; check $P4PORT.
        TCP connect to perforce failed.
        perforce: host unknown.
confirm you have no open files that would conflict. (^C to exit)
---


Tracking of update.sh did not give me a clear answer what values should I use 
for the p4 repository for environment. Where i can some readme for usage 
update.sh scripts? Thanks a lot for any helps


From subbsd at gmail.com  Fri Apr 10 05:48:04 2009
From: subbsd at gmail.com (subbsd)
Date: Fri Apr 10 05:48:28 2009
Subject: chroot is not ready?
Message-ID: <200904101647.47690.subbsd@gmail.com>

Hello maillist

i try to setup vimage chrootet to another "installworld/distribution" places:

1)mkdir -p /usr/jail/vbsd2.my.domain

2) cd /usr/src && make installworld DESTDIR="/usr/jail/vbsd2.my.domain" && 
make distribution DESTDIR="/usr/jail/vbsd2.my.domain"

//file for test
3) date > /nochroot.txt

//create v1 image with chroot 
4) vimage -c v1 chroot /usr/jail/vbsd1.my.domain/

//this step for test chroot not necessary? but assign anyway
5) vimage -i v1 bge1
eth0@v1

6) vimage v1
Switched to vimage v1

// i see nochroot.txt:
7) vimage v1 /usr/bin/file /nochroot.txt
/nochroot.txt: ASCII text

;(
chroot not ready yet? Thanks!

PS: using vimage_7_20090401.tgz for 7-RELENG



From saifi.khan at twincling.org  Sun Apr 12 11:02:28 2009
From: saifi.khan at twincling.org (Saifi Khan)
Date: Mon Apr 13 02:03:04 2009
Subject: FreeBSD 8.x, Xen 3.3.x Dom0 support
Message-ID: <Pine.LNX.4.64.0904122308430.7356@localhost>

Hi:

Does anybody know the extent of Dom0 support for 
FreeBSD 8.x with Xen 3.3.x ?

My interest is to run multiple guest OS hosted on a Xen-ified
(aka paravirtualized) FreeBSD 8.x on a multi-core intel or AMD64
box.

Any pointers or observations ?


thanks
Saifi.
From vivek at nixcraft.com  Wed Apr 22 06:59:17 2009
From: vivek at nixcraft.com (Vivek Gite)
Date: Wed Apr 22 06:59:24 2009
Subject: Regarding multi-ip Bjoern head patch
Message-ID: <49EEB93E.9080503@nixcraft.com>

Hi,

I'm running FreeBSD 7.1_AMD_P4 release with 4 jails. Recently, our ISP 
provided us IPv6 and I'd like to use both multiple IPv4 and IPv6 for my 
jails. According to FreeBSD wiki (http://wiki.freebsd.org/Jails) - there 
is a patch  
http://svn.freebsd.org/viewvc/base?view=revision&revision=188281 ; 
which  is committed to FreeBSD. But I'm not able to use it under said 
version. So I'm looking to grab this one and manually patch it up. Is 
there any tar-ball to grab a patch? Is it included in FreeBSD 7.2RC1? 
How do I grab HEADS UP r185435?

TIA,

Vivek
From bzeeb-lists at lists.zabbadoz.net  Wed Apr 22 08:51:15 2009
From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb)
Date: Wed Apr 22 08:51:22 2009
Subject: Regarding multi-ip Bjoern head patch
In-Reply-To: <49EEB93E.9080503@nixcraft.com>
References: <49EEB93E.9080503@nixcraft.com>
Message-ID: <20090422083240.Q15361@maildrop.int.zabbadoz.net>

On Wed, 22 Apr 2009, Vivek Gite wrote:

> Hi,
>
> I'm running FreeBSD 7.1_AMD_P4 release with 4 jails. Recently, our ISP 
> provided us IPv6 and I'd like to use both multiple IPv4 and IPv6 for my 
> jails. According to FreeBSD wiki (http://wiki.freebsd.org/Jails) - there is a 
> patch  http://svn.freebsd.org/viewvc/base?view=revision&revision=188281 ; 
> which  is committed to FreeBSD. But I'm not able to use it under said 
> version. So I'm looking to grab this one and manually patch it up. Is there 
> any tar-ball to grab a patch? Is it included in FreeBSD 7.2RC1? How do I grab 
> HEADS UP r185435?

Yes, all of FreeBSD 7.2 (BETA, RC1, upcomig RC2 and RELEASE) have and
will have it.  So if you are going to update your system to any of
those versions you'll have it.

/bz

PS: in case of reply please remove the -virtualization Cc:

-- 
Bjoern A. Zeeb                      The greatest risk is not taking one.
From clcchu at hotmail.com  Thu Apr 23 05:05:25 2009
From: clcchu at hotmail.com (Clarence Chu)
Date: Thu Apr 23 05:05:34 2009
Subject: about vimage_7_20090401.tgz
Message-ID: <COL101-W9AA3755BA7E42CA7148F6DD750@phx.gbl>



Hi All,

Seems to me the vimage_7_20090401.tgz
doesn't work, yet on FreeBSD-7.2-PRERELEASE/amd64
as of Apr 22, 2009 for:
a) IPFIREWALL
b) device pf
c) ZFS
d) rpc.lockd

about a year ago, vimage refused to work with PCCARD NICs,
not to mention building a static kernel by:
hints          "GENERIC.hints" 

How's your mileage? Does IMUNES require "most up-dated" version
as a year ago?

Best wishes,

Clarence CHU

_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
From zec at icir.org  Thu Apr 23 08:43:58 2009
From: zec at icir.org (Marko Zec)
Date: Thu Apr 23 08:44:05 2009
Subject: about vimage_7_20090401.tgz
In-Reply-To: <COL101-W9AA3755BA7E42CA7148F6DD750@phx.gbl>
References: <COL101-W9AA3755BA7E42CA7148F6DD750@phx.gbl>
Message-ID: <200904231043.46799.zec@icir.org>

On Thursday 23 April 2009 06:52:45 Clarence Chu wrote:
> Hi All,
>
> Seems to me the vimage_7_20090401.tgz
> doesn't work, yet on FreeBSD-7.2-PRERELEASE/amd64
> as of Apr 22, 2009 for:
> a) IPFIREWALL
> b) device pf
> c) ZFS
> d) rpc.lockd

Basically three separate vimage-related efforts are underway, listed in order 
of priority:

1) merging vimage -> head
2) maintaining vimage branch (tracking head)
3) maintaining vimage_7 branch (tracking stable/7)

So you are mosltly right - in both vimage and vimage_7 branches many kernel 
susbsystems do not work (yet) with options VIMAGE enabled.  The current focus 
is on merging the base network stack infrastructure to head, and deal with 
those remaining subsystems later.

> about a year ago, vimage refused to work with PCCARD NICs,
> not to mention building a static kernel by:
> hints          "GENERIC.hints"
>
> How's your mileage? Does IMUNES require "most up-dated" version
> as a year ago?

IMUNES should work with both latest vimage and vimage_7 kernels from the 
imunes.net/virtnet page, though in general IMUNES mailing list would be a 
more appropriate place to discuss any IMUNES specific issues.

Cheers,

Marko