Re: BSD sleep
On Tue, May 28, 2013 at 07:01:40PM -0400, Kenta Suzumoto wrote: # Hi. Is there no built-in way of making sleep sleep in increments # of minutes, hours, etc? The GNU sleep can be invoked like sleep # 1h for an hour. The FreeBSD one's manpage leads me to believe we # can only use seconds, which is kind of annoying. Is there an # undocmented or missing feature here? Seems really trivial to # implement. # # ~ $ sleep 1h # usage: sleep seconds Perfection is reached when there is nothing left to take away. The GNU format is already an incompatibility. If I want to sleep longer than 3 digit amount in secs, I do the math. The POSIXly *portable* way to do this and document it for the mathematically challenged is sleep $((2*60*60))# 2h sleep $((7*24*60*60)) # 1w Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
VIMAGE
Hello all, I am a new bye on the FreeBSD and I am looking at the VIMAGE features experiencing some problems. I added the options : VIMAGE if_bridge and I removed STCP then I recompiled my kernel and install it. After that, following this tutorial http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the Exercise 2 which consist on the following commands: vimage -c n1 vimage -c n2 ngctl mkpeer efface ether ether ngctl mkpeer efface ether ether ngctl mkpeer em0: bridge lower link0 ngctl name em0:lower bridge0 ngctl connect em0: bridge0: upper link1 ngctl connect ngeth0: bridge0: ether link2 ngctl connect ngeth1: bridge0: ether link3 vimage -i n1 ngeth0 e0 But my virtual interface on the n1 vimage does not receive any packet from the external network while I can see the packet go out from it. For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive the answers (which are send, I verified it from wireshark), in adding the ARP request for his IP address (if I try to add it statically) are not received then it can not answer. At the end of the line the question is: how can I make this virtual network and the external real network be able to communicate ? Thanks in advance. Pietro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VIMAGE
Pietro Paolini wrote: Hello all, I am a new bye on the FreeBSD and I am looking at the VIMAGE features experiencing some problems. I added the options : VIMAGE if_bridge and I removed STCP then I recompiled my kernel and install it. After that, following this tutorial http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the Exercise 2 which consist on the following commands: vimage -c n1 vimage -c n2 ngctl mkpeer efface ether ether ngctl mkpeer efface ether ether ngctl mkpeer em0: bridge lower link0 ngctl name em0:lower bridge0 ngctl connect em0: bridge0: upper link1 ngctl connect ngeth0: bridge0: ether link2 ngctl connect ngeth1: bridge0: ether link3 vimage -i n1 ngeth0 e0 But my virtual interface on the n1 vimage does not receive any packet from the external network while I can see the packet go out from it. For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive the answers (which are send, I verified it from wireshark), in adding the ARP request for his IP address (if I try to add it statically) are not received then it can not answer. At the end of the line the question is: how can I make this virtual network and the external real network be able to communicate ? Thanks in advance. Pietro. 1. That link is from 2007. So very much has changed since then. There are more current links on the internet about this subject. Most are for 8.X releases. 2. If your running 8.2-RELEASE or 9.1-RELEASE all you need to add is options vimage statement to your kernel source and recompile. 3. There are 2 networking methods available for creating vnet/vimage jail networks, if_bridge/epair and netgraph. The if_bridge/epair method is far simpler to config and use then the netgraph method. 4. There are 2 methods of jail setup, the rc.d method where your jail definition parameters go into the hosts rc.conf and the jail(8) method where you can place each jails definition parameter in separate files. 5. There are two very important show stopper PRs on vimage, 164763 memory leak and 149050 the rc.d keyword nojail problem. Vimage is a very long way from prime time usage, thats why it's labeled as highly experimental. Host system freezes and page faults are common. 6. When it comes to running a firewall in a vnet/vimage jail your limited to IPFW and it has limitations. Dummynet and in kernel NAT cause system freezes. IPFILTER causes page fault at boot time. PF will run on the host but not run in the vnet/vimage jail. Here are a bunch of PRs on vimage firewall problems, 143621, 176092, 161094, 176992, 143808, 148155, 165252, 178480, 178482 Check out these links http://druidbsd.sourceforge.net/vimage.shtml http://devinteske.com/vimage-jails-on-freebsd-8 http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-September/000747.html http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto http://zewaren.net/site/?q=node/78 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VIMAGE (slightly off topic)
On 5/30/2013 8:29 AM, Joe wrote: Pietro Paolini wrote: Hello all, I am a new bye on the FreeBSD and I am looking at the VIMAGE features experiencing some problems. I added the options : VIMAGE if_bridge and I removed STCP then I recompiled my kernel and install it. After that, following this tutorial http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the Exercise 2 which consist on the following commands: vimage -c n1 vimage -c n2 ngctl mkpeer efface ether ether ngctl mkpeer efface ether ether ngctl mkpeer em0: bridge lower link0 ngctl name em0:lower bridge0 ngctl connect em0: bridge0: upper link1 ngctl connect ngeth0: bridge0: ether link2 ngctl connect ngeth1: bridge0: ether link3 vimage -i n1 ngeth0 e0 But my virtual interface on the n1 vimage does not receive any packet from the external network while I can see the packet go out from it. For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive the answers (which are send, I verified it from wireshark), in adding the ARP request for his IP address (if I try to add it statically) are not received then it can not answer. At the end of the line the question is: how can I make this virtual network and the external real network be able to communicate ? Thanks in advance. Pietro. 1. That link is from 2007. So very much has changed since then. There are more current links on the internet about this subject. Most are for 8.X releases. 2. If your running 8.2-RELEASE or 9.1-RELEASE all you need to add is options vimage statement to your kernel source and recompile. 3. There are 2 networking methods available for creating vnet/vimage jail networks, if_bridge/epair and netgraph. The if_bridge/epair method is far simpler to config and use then the netgraph method. 4. There are 2 methods of jail setup, the rc.d method where your jail definition parameters go into the hosts rc.conf and the jail(8) method where you can place each jails definition parameter in separate files. 5. There are two very important show stopper PRs on vimage, 164763 memory leak and 149050 the rc.d keyword nojail problem. Vimage is a very long way from prime time usage, thats why it's labeled as highly experimental. Host system freezes and page faults are common. 6. When it comes to running a firewall in a vnet/vimage jail your limited to IPFW and it has limitations. Dummynet and in kernel NAT cause system freezes. IPFILTER causes page fault at boot time. PF will run on the host but not run in the vnet/vimage jail. Here are a bunch of PRs on vimage firewall problems, 143621, 176092, 161094, 176992, 143808, 148155, 165252, 178480, 178482 Check out these links http://druidbsd.sourceforge.net/vimage.shtml http://devinteske.com/vimage-jails-on-freebsd-8 http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-September/000747.html http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto http://zewaren.net/site/?q=node/78 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I would like to thank Pietro for asking the question and Joe for answering, as I was looking into vimage myself. This sort of thing really helps a lot of people who are exploring FreeBSD and new features. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: swap partition leads to instability?
On Wed, 29 May 2013 19:52:02 + (UTC) jb wrote: RW rwmaillists at googlemail.com writes: BTW you mean paging, or swap use, rather that swapping. Linux supports only paging, so it can be taken as read that swapping means paging, but FreeBSD supports both. Yes, there is some confusion about the diff, if any, between paging and swapping. Paging - copying or moving pages between physical memory (RAM) and secondary storage (e.g. hard disk), in both directions. Swapping - nowdays is synonymous with paging. But its history is as follows (per Wikipedia): This is a bit Linux-centric. You say that FB supports both, Linux supports paging only. Well, Linux utilizes swap space as part of virtual memory. So, can you elaborate more on that - what is the essence of the diff, why should I avoid the term swapping when referring to Linux, assuming VMM systems on both ? You page-out pages and swap-out processes. When FreeBSD is very short of memory it swaps-out entire processes to concentrate the memory in the running processes. Linux goes directly from paging to killing processes. You can also set vm.swap_idle_enabled to allow idle processes to be swapped during normal use. This may help if a server has a lot memory tied up in processes that tend to be idle for long periods of time - traditionally used on shell servers. These days you'd probably want to be adding more memory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VIMAGE
On May 30, 2013, at 2:29 PM, Joe fb...@a1poweruser.com wrote:
Pietro Paolini wrote:
Hello all,
I am a new bye on the FreeBSD and I am looking at the VIMAGE features
experiencing some problems.
I added the options :
VIMAGE
if_bridge
and I removed
STCP
then I recompiled my kernel and install it.
After that, following this tutorial
http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the
Exercise 2 which consist on the following commands:
vimage -c n1
vimage -c n2
ngctl mkpeer efface ether ether
ngctl mkpeer efface ether ether
ngctl mkpeer em0: bridge lower link0
ngctl name em0:lower bridge0
ngctl connect em0: bridge0: upper link1
ngctl connect ngeth0: bridge0: ether link2
ngctl connect ngeth1: bridge0: ether link3
vimage -i n1 ngeth0 e0
But my virtual interface on the n1 vimage does not receive any packet from
the external network while I can see the packet go out from it.
For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive
the answers (which are send, I verified it from wireshark), in adding
the ARP request for his IP address (if I try to add it statically) are not
received then it can not answer.
At the end of the line the question is: how can I make this virtual
network and the external real network be able to communicate ?
Thanks in advance.
Pietro.
1. That link is from 2007. So very much has changed since then.
There are more current links on the internet about this subject. Most are for
8.X releases.
2. If your running 8.2-RELEASE or 9.1-RELEASE all you need to add is options
vimage statement to your kernel source and recompile.
3. There are 2 networking methods available for creating vnet/vimage jail
networks, if_bridge/epair and netgraph. The if_bridge/epair method is far
simpler to config and use then the netgraph method.
4. There are 2 methods of jail setup, the rc.d method where your jail
definition parameters go into the hosts rc.conf and the jail(8) method where
you can place each jails definition parameter in separate files.
5. There are two very important show stopper PRs on vimage,
164763 memory leak and 149050 the rc.d keyword nojail problem.
Vimage is a very long way from prime time usage, thats why it's labeled as
highly experimental. Host system freezes and page faults are common.
6. When it comes to running a firewall in a vnet/vimage jail your limited to
IPFW and it has limitations. Dummynet and in kernel NAT cause system freezes.
IPFILTER causes page fault at boot time. PF will run on the host but not run
in the vnet/vimage jail. Here are a bunch of PRs on vimage firewall problems,
143621, 176092, 161094, 176992, 143808, 148155, 165252, 178480, 178482
Check out these links
http://druidbsd.sourceforge.net/vimage.shtml
http://devinteske.com/vimage-jails-on-freebsd-8
http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-September/000747.html
http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto
http://zewaren.net/site/?q=node/78
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Thanks so much, really interesting and good links but I can't again accomplish
my task - I followed
http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto as a base tutorial
-
I would like simulate more client for my PC using this technology, and that's
my topology:
1 - Two epairs created
2 - Two jail created
3 - Assign one intf for jail
4 - Add the real interface to a bridge where I put all the interfaces
---
JAIL1
0b
---
---
JAIL2
1b
---
---
HOST
0a
1a
em0 -- REAL
---
Where {0,1}a is the first pair and {0,1}b is the second and em0 is my real
interface (it has an IP address), then I got to the problem, I tried
to :
jexec 2 dhclient epair1b
And I can see the DHCP packet with the correct MAC address going out, the
server reply (I have a sniffer pc) but the transaction does not end
successfully, what is really strange is that if I attach tcpdump on em0 I can
NOT see the answer server sends while when I try
dhclient em0
I can see the packet going in and out and the DHCP transaction finish
successfully. Do you have any idea about how can I accomplish my
target ? Maybe I am using the wrong technology ?
I would not surprised if I make a error on my configuration but what really
interest me is if I CAN do that using jail.
Thanks a lot, and in advance ! :-)
Pietro.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VIMAGE
Pietro Paolini wrote:
On May 30, 2013, at 2:29 PM, Joe fb...@a1poweruser.com wrote:
Pietro Paolini wrote:
Hello all,
I am a new bye on the FreeBSD and I am looking at the VIMAGE features
experiencing some problems.
I added the options :
VIMAGE
if_bridge
and I removed
STCP
then I recompiled my kernel and install it.
After that, following this tutorial
http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the Exercise
2 which consist on the following commands:
vimage -c n1
vimage -c n2
ngctl mkpeer efface ether ether
ngctl mkpeer efface ether ether
ngctl mkpeer em0: bridge lower link0
ngctl name em0:lower bridge0
ngctl connect em0: bridge0: upper link1
ngctl connect ngeth0: bridge0: ether link2
ngctl connect ngeth1: bridge0: ether link3
vimage -i n1 ngeth0 e0
But my virtual interface on the n1 vimage does not receive any packet from the
external network while I can see the packet go out from it.
For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive
the answers (which are send, I verified it from wireshark), in adding
the ARP request for his IP address (if I try to add it statically) are not
received then it can not answer.
At the end of the line the question is: how can I make this virtual network
and the external real network be able to communicate ?
Thanks in advance.
Pietro.
1. That link is from 2007. So very much has changed since then.
There are more current links on the internet about this subject. Most are for
8.X releases.
2. If your running 8.2-RELEASE or 9.1-RELEASE all you need to add is options
vimage statement to your kernel source and recompile.
3. There are 2 networking methods available for creating vnet/vimage jail
networks, if_bridge/epair and netgraph. The if_bridge/epair method is far
simpler to config and use then the netgraph method.
4. There are 2 methods of jail setup, the rc.d method where your jail
definition parameters go into the hosts rc.conf and the jail(8) method where
you can place each jails definition parameter in separate files.
5. There are two very important show stopper PRs on vimage,
164763 memory leak and 149050 the rc.d keyword nojail problem.
Vimage is a very long way from prime time usage, thats why it's labeled as
highly experimental. Host system freezes and page faults are common.
6. When it comes to running a firewall in a vnet/vimage jail your limited to
IPFW and it has limitations. Dummynet and in kernel NAT cause system freezes.
IPFILTER causes page fault at boot time. PF will run on the host but not run in
the vnet/vimage jail. Here are a bunch of PRs on vimage firewall problems,
143621, 176092, 161094, 176992, 143808, 148155, 165252, 178480, 178482
Check out these links
http://druidbsd.sourceforge.net/vimage.shtml
http://devinteske.com/vimage-jails-on-freebsd-8
http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-September/000747.html
http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto
http://zewaren.net/site/?q=node/78
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Thanks so much, really interesting and good links but I can't again accomplish my task - I followed http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto as a base tutorial -
I would like simulate more client for my PC using this technology, and that's
my topology:
1 - Two epairs created
2 - Two jail created
3 - Assign one intf for jail
4 - Add the real interface to a bridge where I put all the interfaces
---
JAIL1
0b
---
---
JAIL2
1b
---
---
HOST
0a
1a
em0 -- REAL
---
Where {0,1}a is the first pair and {0,1}b is the second and em0 is my real interface (it has an IP address), then I got to the problem, I tried
to :
jexec 2 dhclient epair1b
And I can see the DHCP packet with the correct MAC address going out, the
server reply (I have a sniffer pc) but the transaction does not end
successfully, what is really strange is that if I attach tcpdump on em0 I can
NOT see the answer server sends while when I try
dhclient em0
I can see the packet going in and out and the DHCP transaction finish successfully. Do you have any idea about how can I accomplish my
target ? Maybe I am using the wrong technology ?
I would not surprised if I make a error on my configuration but what really
interest me is if I CAN do that using jail.
Thanks a lot, and in advance ! :-)
Pietro.
Pietro;
You really have to provide a lot more info about your host system and
jail configuration.
What version of FreeBSD are you running?
Which method do you use to create your jails, rc.d/rc.conf or jail(8).
How are your creating the if_bridge/epair network, IE entering commands
by hand or using a script? Post the script.
Can you post the output of ifconfig command after you have your jail
Re: VIMAGE
On May 30, 2013, at 3:35 AM, Pietro Paolini wrote: Hello all, I am a new bye on the FreeBSD and I am looking at the VIMAGE features experiencing some problems. I added the options : VIMAGE if_bridge and I removed STCP then I recompiled my kernel and install it. After that, following this tutorial http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the Exercise 2 which consist on the following commands: vimage -c n1 vimage -c n2 ngctl mkpeer efface ether ether ngctl mkpeer efface ether ether Don't you just love autocorrect? (does the same thing to me… turns eiface into efface) ngctl mkpeer em0: bridge lower link0 Looks good. ngctl name em0:lower bridge0 I usually do my connect before the name… but shouldn't matter. Should work all the same. ngctl connect em0: bridge0: upper link1 This looks wrong to me. I'd expect: ngctl connect em0: bridge0:lower upper link1 # The way I see most people using vimage… it seems like almost always a mistake to not hook the upper (unless you have very good reason to make the base machine inaccessible from the jails and vice-versa). Some missing points… # Make sure the bridged-interface is active ifconfig em0 up # Set promiscous mode and # don't override src addr ngctl msg em0: setpromisc 1 ngctl msg em0: setautosrc 0 ngctl connect ngeth0: bridge0: ether link2 ngctl connect ngeth1: bridge0: ether link3 Let's re-work this. Earlier you did 2x mkpeer to pre-create your eiface nodes. I don't do this, as it later requires a connect for each created peer. What you can do instead is _not_ perform those earlier commands (shown below): ngctl mkpeer eiface ether ether ngctl mkpeer eiface ether ether (followed by the above connect statements) But *instead*, you can actually do a contextual mkpeer that connects the nodes as they are created. For example… instead of this: ngctl mkpeer eiface ether ether ngctl mkpeer eiface ether ether ngctl connect ngeth0: bridge0: ether link2 ngctl connect ngeth0: bridge0: ether link3 (which doesn't look right to me, because I'm used to creating an ether edge between bridge:lower and the eiface) You can instead do: ngctl mkpeer em0:lower eiface link2 ether ngctl mkpeer em0:lower eiface link3 ether This simplifies 4 statements into 2. NOTE: I can't remember if em0:lower can be replaced with the new name of bridge0 (that you created with ngctl name em0:lower bridge0). My scripts continue to use the raw name in the mkpeer statements even after a rename of the lower-link. You *may* be able to instead say ngctl mkpeer bridge0: eiface link2 ether etc.) vimage -i n1 ngeth0 e0 But my virtual interface on the n1 vimage does not receive any packet from the external network while I can see the packet go out from it. Try hooking changing your PHY-bridge hook to the lower and hooking your PHY upper into the bridge. For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive the answers (which are send, I verified it from wireshark), in adding the ARP request for his IP address (if I try to add it statically) are not received then it can not answer. At the end of the line the question is: how can I make this virtual network and the external real network be able to communicate ? Thanks in advance. Wondering if you've given my solution a try… http://druidbsd.sf.net/vimage.shtml -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VIMAGE
On May 30, 2013, at 9:18 AM, Joe wrote:
Pietro Paolini wrote:
On May 30, 2013, at 2:29 PM, Joe
fb...@a1poweruser.commailto:fb...@a1poweruser.com wrote:
Pietro Paolini wrote:
Hello all,
I am a new bye on the FreeBSD and I am looking at the VIMAGE features
experiencing some problems.
I added the options :
VIMAGE
if_bridge
and I removed
STCP
then I recompiled my kernel and install it.
After that, following this tutorial
http://imunes.tel.fer.hr/virtnet/eurobsdcon07_tutorial.pdf I tried the
Exercise 2 which consist on the following commands:
vimage -c n1
vimage -c n2
ngctl mkpeer efface ether ether
ngctl mkpeer efface ether ether
ngctl mkpeer em0: bridge lower link0
ngctl name em0:lower bridge0
ngctl connect em0: bridge0: upper link1
ngctl connect ngeth0: bridge0: ether link2
ngctl connect ngeth1: bridge0: ether link3
vimage -i n1 ngeth0 e0
But my virtual interface on the n1 vimage does not receive any packet from the
external network while I can see the packet go out from it.
For instance using DHCP, e0 on n1 sends DHCP packets but it does not receive
the answers (which are send, I verified it from wireshark), in adding
the ARP request for his IP address (if I try to add it statically) are not
received then it can not answer.
At the end of the line the question is: how can I make this virtual network
and the external real network be able to communicate ?
Thanks in advance.
Pietro.
1. That link is from 2007. So very much has changed since then.
There are more current links on the internet about this subject. Most are for
8.X releases.
2. If your running 8.2-RELEASE or 9.1-RELEASE all you need to add is options
vimage statement to your kernel source and recompile.
3. There are 2 networking methods available for creating vnet/vimage jail
networks, if_bridge/epair and netgraph. The if_bridge/epair method is far
simpler to config and use then the netgraph method.
4. There are 2 methods of jail setup, the rc.d method where your jail
definition parameters go into the hosts rc.conf and the jail(8) method where
you can place each jails definition parameter in separate files.
5. There are two very important show stopper PRs on vimage,
164763 memory leak and 149050 the rc.d keyword nojail problem.
Vimage is a very long way from prime time usage, thats why it's labeled as
highly experimental. Host system freezes and page faults are common.
6. When it comes to running a firewall in a vnet/vimage jail your limited to
IPFW and it has limitations. Dummynet and in kernel NAT cause system freezes.
IPFILTER causes page fault at boot time. PF will run on the host but not run in
the vnet/vimage jail. Here are a bunch of PRs on vimage firewall problems,
143621, 176092, 161094, 176992, 143808, 148155, 165252, 178480, 178482
Check out these links
http://druidbsd.sourceforge.net/vimage.shtml
http://devinteske.com/vimage-jails-on-freebsd-8
http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-September/000747.html
http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto
http://zewaren.net/site/?q=node/78
___
freebsd-questions@freebsd.orgmailto:freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.orgmailto:freebsd-questions-unsubscr...@freebsd.org
Thanks so much, really interesting and good links but I can't again accomplish
my task - I followed
http://bsdbased.com/2009/12/06/freebsd-8-vimage-epair-howto as a base tutorial
- I would like simulate more client for my PC using this technology, and that's
my topology:
1 - Two epairs created 2 - Two jail created
3 - Assign one intf for jail
4 - Add the real interface to a bridge where I put all the interfaces
---
JAIL1
0b
---
---
JAIL2 1b
---
---
HOST
0a
1a
em0 -- REAL
---
Where {0,1}a is the first pair and {0,1}b is the second and em0 is my real
interface (it has an IP address), then I got to the problem, I tried to :
jexec 2 dhclient epair1b And I can see the DHCP packet with the correct MAC
address going out, the server reply (I have a sniffer pc) but the transaction
does not end successfully, what is really strange is that if I attach tcpdump
on em0 I can NOT see the answer server sends while when I try
dhclient em0 I can see the packet going in and out and the DHCP transaction
finish successfully. Do you have any idea about how can I accomplish my target
? Maybe I am using the wrong technology ?
I would not surprised if I make a error on my configuration but what really
interest me is if I CAN do that using jail.
Thanks a lot, and in advance ! :-)
Pietro.
Pietro;
You really have to provide a lot more info about your host system and jail
configuration.
What version of FreeBSD are you running?
Which method do you use to create your jails, rc.d/rc.conf or jail(8).
How are your creating the if_bridge/epair network, IE entering
Should I move to amd64 ?
I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Should I move to amd64 ?
I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: swap partition leads to instability?
RW rwmaillists at googlemail.com writes: ... Yes, there is some confusion about the diff, if any, between paging and swapping. Paging - copying or moving pages between physical memory (RAM) and secondary storage (e.g. hard disk), in both directions. Swapping - nowdays is synonymous with paging. But its history is as follows (per Wikipedia): This is a bit Linux-centric. ... You page-out pages and swap-out processes. When FreeBSD is very short of memory it swaps-out entire processes to concentrate the memory in the running processes. Linux goes directly from paging to killing processes. That was helpful - knowing the details of VMM implementation in various OSs helps understand the generalizations, with exceptions ... jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Should I move to amd64 ?
Given your description, no you should not move. On Thu, May 30, 2013 at 1:04 PM, Michael Gass mg...@csbsju.edu wrote: I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: swap partition leads to instability?
RW rwmaillists at googlemail.com writes: On Sun, 26 May 2013 12:36:42 + (UTC) jb wrote: But, swapping is also a symptom, not a problem. It is never a good idea to let it get to that point. No, there are thing that are better on disk than in memory. The most common example is tmpfs. It's much better that files left on tmpfs can sent to disk rather tying up physical memory indefinitely. Yup, tmpfs - in virtual memory. That's an unfortunate excuse. But before its content are swapped out, the critical system like a server will be destabilized and show lame performance. The tmp-on-tmpfs has so many disadvantages that it is difficult to count and follow all of them. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: swap partition leads to instability?
On Sun, 26 May 2013 18:48:18 -0500 Adam Vande More wrote: Um, that is wrong. It is in fact the basically the point of TRIM. And SSD's typically use the best form of wear leveling and it's usually advisable to leave a bit of the drive unpartitioned/unused to ensure the wear leveling works optimally. Would the UFS default 8% reserve achieve that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Should I move to amd64 ?
Hi-- On May 30, 2013, at 10:19 AM, Michael Gass mg...@csbsju.edu wrote: I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. For machines with less than 4GB of RAM, running 32-bit version is probably wise; 32-bit processes use memory more efficiently compared with 64-bit mode. For some math-intensive workloads like SSL/crypto, audio/video transcoding, and such, there is likely to be significant improvement in 64-bit mode compared with running in 32-bit mode. For most other workloads, you're not likely to notice a difference. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? Nope, or at least not in general; AMD64 is very stable nowadays. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
