![]() I worked around this by creating a second NAT interface for the guest, and assigning static IP’s as follows: The only caveat with VEPA is that your host machine CAN NOT communicate to the guest machine over this interface (unless you have some special hair pin switch.) (Here ethXX is your host machines outgoing interface.) Set Network source to Host device ethXX : macvtap.The 3Mbps of traffic barely puts a dent on my CPU usage. I switched my networking setup to macvtap, and got a huge performance improvement. I’m guessing this is because the bridged setup put eth0 in promiscuous mode, and the host kernel has to inspect each packet and decide whether to pass it to the VM guest or not. This caused my host machine CPU usage to rise to 40%! Recently (), however, one of the other machines on my subnet generated some 3Mbps of traffic (to an external server). The VM needs a public IP of course, so I used a bridged setup. I’ve been using KVM based virtual machine as a web server for a while.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |