search for: vifn

hi fellow XEN-users: I have been trying hard to get this problem fixed, hope I can get some help here. Thanks in advance for your time. I have a typical dom0 + domU XEN setup. after I start xend and network-bridge, I get the default network setup, , peth0 -------- bridge ------------------------------------------------------- |

Hi ! What is the best way to use eth1 of my dom0 in my domU ? i tried that in Dom0 but bridge don''t want comes up : ./xen-network-common.sh "network-bridge net-dev=eth1 bridge=brint virtnum=1" Thanks Michael _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...you supposed to create guests? Now I can`t get the networking to work. I`ve been reading lots of documentation and still don`t understand how that is supposed to work. As far as I understand, you get three different network interfaces: dom0: a bridge (virbr0) dom0: a virtual network interface (vifN.X) domU: a virtual network interface which doesn`t appear to be virtual to domU And dom0 keeps it`s own network interface(s), like eth0, which is a physical one. Is vifN.X the same as eth0 in domU? Or what is it for? If it`s the same, is it supposed to have the same IP on both sides? Ho...

Hi, Question on setting up networking in xen. I want to do the following on my laptop: dom0 is attached to eth0 and ath0. dom1 is going to by my virtual firewall for all my virtual machines. So I assume 3 interfaces, a bridge to eth0, ath0 and a virtual interface? dom2 and so on will route all their traffic through dom1 (through the virtual interface) I''ve read the documentation a

Hi, For various bad reasons I must run a kernel 2.2.X and I tried to get it running on Xen 3.0.3. The virtual machine freeze every 28s (or less) for 1-3 secs which makes it unusable as demonstrated by: # while true; do date; sleep 1; done Thu Oct 26 18:03:36 PDT 2006 <missing> Thu Oct 26 18:03:38 PDT 2006 or # ping my-xen 64 bytes from 172.21.1.102: icmp_seq=0 ttl=255 time=8.5 ms 64

...oute.patch: this script now looks for two conditions: 1) the type of the vif is ioemu 2) the mailbox file (left by qemu-ifup) is present (in which case it's assumed to contain a VIF interface name) if both conditions are present, then from that point on vif-route ignores the vifN.0 interface and sets up tapM instead. Net result: on this system, ioemu-HVM guests now have working networking (another guest, which uses netfront-HVM [a SLES 11 VM], also works, but taking advantage of the faster VIF scheme) Thanks in advance, -- Cyrille -------------- next part -----------...

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Xen Networking[1] works by creating a new pair of virtual ethernet interfaces (vifN.M in dom0 and ethM in domU with id N) and connecting then by an internal "crossover ethernet cable". My understanding of the "internal crossover" thing is that networking statistics should be the same no matter if you measure it in the dom0 or in the domU. RX/TX values should b...

I am trying to setup Xen virtual servers using a Debian etch with the xen 3.0.3 provided in 32 bits mode. I am using full virtualization. I managed to get things started using the configuration provided below. I was able to run the install (with boot="d"). I even managed to start the system afterwards, and it runs correctly. But now I encounter a problem I already hit when running

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

...* the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny guest, xen-vnif.ko does not exist, xen-netfront refuses to load despite the XenBus PCI device appearing) What xen/qemu-dm did is to build two network interfaces: * vifN.0 was used to send packets from the host to the guest routing was enabled towards this interface. No virtual hardware drivers took care of this network link, so all packets ended up dropped. * tapM was used by the guest to deliver packets from its virtual et...

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

...ilobytes) on the size of the console buffer #(console-limit 1024) ## # To bridge network traffic, like this: # # dom0: fake eth0 -> vif0.0 -+ # | # bridge -> real eth0 -> the network # | # domU: fake eth0 -> vifN.0 -+ # # use # # (network-script network-bridge) # # Your default ethernet device is used as the outgoing interface, by default. # To use a different one (e.g. eth1) use # # (network-script ''network-bridge netdev=eth1'') # # The bridge is named xenbr0, by default. To rename the br...

Hi, I followed Boris'' tutorial to the letter about installing Xen 4 on Ubuntu Lucid. Dom0 starts ok, and xm works, but virt manager can''t connect to xen:///. I''m pretty sure that the problem is with virt-manager''s configuration file. I run xen-4.0.1-rc3-pre with Kernel 2.6.31.13. Here''s xm list''s output: $ sudo xm list Name

[This email is either empty or too large to be displayed at this time]

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel