Date: Mon, 16 Nov 2009 09:30:44 +0000 From: Antonio Costa <costa@di.uminho.pt> To: Marko Zec <zec@icir.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: Imunes and FreeBSD 8.0 RC2 Message-ID: <4B011BC4.8050302@di.uminho.pt> In-Reply-To: <200911111423.39501.zec@icir.org> References: <7401C27DF540DA4D83B9B35C541825E3E97426@MCHP7I5A.ww902.siemens.n et> <200911111423.39501.zec@icir.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Marko Zec wrote:
> here's the procedure which should be sufficient to get IMUNES up and running
> on FreeBSD 8.0-RC3 (I've tested this on amd64, but i386 should work as well):
Hello Marko,
I followed the procedure on a i386 with success!! I am very happy with
my first Free BSD 8.0 RC3 with IMUNES!! It looks very good!
Congratulations on your excellent work!! I use IMUNES since the very
beginning (FreeBSD 4.11), over the last 4-5 years.
I have found a little thing not yet compatible with new version, but
with simple solution: the cpu line on imunes.imn files. Old files or new
ones with quagga generated configs have a line "cpu ..." that is passed
to "vimage -m" that reports a "no such file" error:
===== Example.imn ========
1. node n0 {
2. type router
3. cpu {{min 0} {max 100} {weight 1}}
4. model quagga
5. network-config {
6. hostname n0
7 !
Line 3 is the unsupported jail parameter that Imunes.tcl reports has:
---------------------------------------------------------------------
Error: No such file or directory
Error: No such file or directory
while executing
"exec vimage -m i0b5b0.n0 cpumin 0"
("eval" body line 1)
My current solution is to comment out lines 297-305 of exec.tcl file:
---------------------------------------------------------------------
# if { $cpumin != "" } {
# nexec vimage -m $node_id cpumin $cpumin
# }
# if { $cpumax != "" } {
# nexec vimage -m $node_id cpumax $cpumax
# }
# if { $cpuweight != "" } {
# nexec vimage -m $node_id cpuweight $cpuweight
# }
Many thanks for your excellent work!
--
António Duarte Costa
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLARvLAAoJEEqNsXV89gdWhckIAJavMSk05gnNE//rezCceRA3
6NzW/lckLXTPAKOXtMbx+SsRTdcy9PWRDFX0bq82aEA9xoiBu8n2t8BXemv4oD8k
iW3njfXat/Ywj0O7fn44KIk8SzCUUXUjoAtQOacDGU5++6x5Dt6J+kRBFXff5cHd
4YsKPNEmXwQdB7z4rSiSwnE9PgNDoEzUWdx965IWMwzcXWCDVBuOZZCJv5FimJ/u
GGGUdZm9K3u9JOjyguNCO4vGPShaoBCnwxTQp95uBSP14qtYxUKOLtr9tfss6Otp
N6vhRUjpe6A4+hqXWgHjimaDVkSwuZlFmXro/Ef+Ad3kNrNVd/+zwb4yZXWzlbs=
=zmJU
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B011BC4.8050302>
