search for: vif1.0

Hello folks, I used to work with bridging for my xen networks, but my very last hosting provider doesn''t support multiple mac address on the switch port. So I''m trying to configure some virtual servers on xen 3.2.1 using the network-route and vif-route method instead of bridge. Everything works well, on the virtual server except the network. In the VM definition file, I have :

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.

hi @all sometimes after a reboot the complete network is down the difference in the logs shows: in a failed reboot the eth0 does not entering promiscuous mode; in both cases the eth0 gets sucessful its ip configuration via dhcp - any idea ? the nic is a 3com 3c905C-TX/TX-M and the configuration is a suse 9.3 with xen-kernel 2.6.11.4-21.10-xen and xen 2.0.5.c ----------------[ failed reboot ]

All works fine on my virtual hosts, except the network. The internal interface is created (have an ip address), the external bridge is ok, with the external vif1.0 for the virtual host, but `ping virtual_host_address` dont work. Ok, I try to put on vif1.0 an ip address. When I do an `ifconfig vif1.0 127.1.2.3` the network works fine, `ping virtual_host_address` works and all machines from my

Hi, Creating a new domain is a lot easier in opensuse 11. I follow the instruction on the website and build a virtual machine which uses opensuse 11 as well (I installed it from iso image). Everything works fine except the network. I cannot access the Internet from DomU. Here is some information. P.S. the DomU id is 1. "brctl show" in Dom 0: bridge name bridge id STP

Hi, I have taken the long and winding road and indeed it lead me to your door. I need your help, please. My Xen includes 2 guests. Xen itself (10.2.0.52) gets free access to the outside world and to its guests. Both guests however (10.2.0.54/10.2.0.55) see each other but stay under house arrest! Not a single ping manages to go past the bridge (xenbr0) and get an answer from the default gateway

I don''t know if there was a problem in the archive or not, I just wanted to link to this post of mine, but I could not find it in the archive. So here''s a re-post. -------- Original-Nachricht -------- Betreff: [Xen-users] Xen, NIC bonding, ARP problem Datum: Fri, 30 Mar 2007 10:05:45 +0200 Von: Dominik Klein <dk@in-telegence.net> An: xen-users@lists.xensource.com Hi

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

Hello, I have a Dell PowerEdge 2850 that periodically (6 times in the last 24 hours) freezes, requiring a power cycle in order to come back. The machine is running a Xen 2.0 stable source install. Here is the appropriate Grub entry: title Xen 2.0 / XenLinux 2.6 kernel /boot/xen-2.0.gz dom0_mem=131072 module /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0 Dom0 boots happily, and new

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

Hello everyone, I''ve managed to configure and start Remus. However, it works only while the protected server is not loaded. As soon as I start a memory-intensive server application, the stream of Remus messages stops, leaving me with an error message. I think the message is not always the same, but here is what I''ve got from the last run: PROF: suspending at

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to

Hi Is there anyone who has successfully resolved the low throughput problem in Guest communication. I am using Xen3.4.1 with PV os kernel 2.6.30-rc6-tip On fedora11. While running netperf benchmark on guests throughput results are very low DomU to DomU    0.29 Mbps Why is it so? What would be the problem. Is there any issue with fc11 platform? Regards, Fasiha Ashraf Add whatever you love

Hi Shimizu --- Shimizu Miki <> schrieb: > Hello, > > Doesn''t the vircual nic work at all? After the hint of Timo (http://lists.xensource.com/archives/html/xen-users/2006-05/msg00091.html) I got the virtual xen network card show up in yast. However, when I configured it, yast came up with an error message that''no driver module for the device found''

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

Hi, can anyone help me with this (weirdest problem Ive ever seen) I have the latest Debian Squeeze vendor xen dom0 kernel and 1 domU succesfully installed on it using bridged networking. From dom0, I can ping/telnet etc. to anywhere on the web WHAT IS WORKING > * From my domU I can successfully ping google.com and telnet to 8.8.8.8:53 (googles dns server) * tcpdump vif1.0 and I see SYNs and

> Hi. what creates veth0 and vifu.0, when? what''s the > underlying architecture behind them? Just trying to > understand the internals. netback/loopback.c creates them. It''s effectively a point to point link, allowing domain 0 to connect on to the bridge in the same manner that other domains do. (before, packets to domain 0 were short-cutted and came off the

Hello, I am having some routing troubles with my Xen setup. I have two domUs, one running as a firewall and another running as a dmz: The dom0 has the following: - eth0 bridge (10.0.0.3/24) The domU-firewall has the following: - Direct passthrough PCI NIC (Public Internet) - Virtual NIC connected to the eth0 bridge on dom0 (10.0.0.1/24) - Bridge called brdmz for the dmz zone (10.0.2.1/24)