similar to: How vifX.Y and eth talk on dom0 with NAT configuration?

Hello guys I have the following problem with xen 3.0.1 compiled from sources on Debian Sarge, kernel 2.6.12.6 which can be easily reproduced at least on my installation: after I log in to domU console or via ssh and run "shutdown" I get deadlocked network interface with error message: unregister_netdevice: waiting for vifX.0 to become free. Usage count = n After this happen I

Hi, I''ve a working xen 3.0.2 booting a gentoo linux on Dom0. I have setup a Windows XP in a DomU OK with no problems except the network!! My problem is that I wanted to give a working network interface on the DomU and the best I could. making the windows detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu,

Hi list, following my last mail I added a small jpg to clarify my request... How do I have to configure my dumm0 to enable communication between my firewall domU and my dom0. As mentioned I can ping/ssh from outside to domU (FW), I can ping ssh from there to domU(2.1) and domU(2.2). But I can''t get through to dom0. As most of the basic understanding is missing on my side even a

Hello, My first post on Xen-Users, so .. i''ve discovered a strange problem. Setup: -A Windows server 2003R2 (x86) with GPL PV driver 0.9.9 ipferf 1.7.0 (from 2003) -dom0 a opensuse 11.0 xen: # rpm -q -a |grep -i xen kqemu-kmp-xen-1.3.0pre11_2.6.25.5_1.1-7.1 kiwi-desc-xenboot-2.38-67.1 xen-3.2.1_16881_04-4.2 xen-tools-3.2.1_16881_04-4.2 xen-libs-3.2.1_16881_04-4.2

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt at centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E at MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I cannot find a use the network-nat and vif-nat provided in the general case, where I'd like to NAT between vifx.0 and ethx interfaces. I have setup the following in /etc/xen/xend-config.sxp : ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above.

Hi all Really silly question here: do the vif interfaces require IP addresses? I''m totally stuck with getting IP traffic to my guest domain, layer 2 traffic (ie ARP queries/responces, broadcasts, etc) is all OK. Another question, what is peth0 used for? Thanks again CC Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 251

Hi All, I have a weird issue I''m not sure how to solve.  I''ve got Xen 3.2.1 working under RHEL 5.2 x86_64 just fine.  I fired off a CentOS 5.2 PV install and everything went smoothly... except that when I fire up the PV, the tap0 for bridging isn''t being created.  This results in the CentOS 5.2 domU''s bridged eth0 only being able to ping the RHEL5

Easy one. I have win98 clients that login and connect to the shares fine. My problem is the user home directory, each user can see their folders and can even open them but they cannot save to their home directory. Each users home dir is setup as 0700 (-rwx------), as are the files and subdir's, which I believe is Read, Write, Execute for the owner of the file. What am I missing? Chris.

Hi, I've been testing the Debian packages ahead of the Debian 7 release (which is very imminent) I believe this is a serious bug[1] in the package, as it appears that HVM networking is broken, or at the very least, requires some undocumented configuration step Specifically: - I can start the HVM domU without any vif - if I attach a vif, the domU will not start Looking at

When does vif0.0 get created? Is there some shell magic? I''m trying to figure out how to do a similar peth1/veth1 split for eth1. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I have a box with XEN enabled. Specs : Gentoo 10.0 AMD64 XEN 4.0.0 The server is connected on our network through two physicals NIC. Actually, I''m using a VLAN on each NIC and bridge the domU in it. But now I must create an additional domU which should be in an different VLAN. The best solution is to set a trunk on the switch and use 802.1q directly on the dom0. I found this site

Hi, i have a problem with xen. the output of uname is:Linux xen 2.6.12-gentoo-r6 #9 SMP Mon Jan 23 18:13:25 CET 2006 i686 AMD Opteron(tm) Processor 844 AuthenticAMD GNU/Linux i user the SAME config of the kernel, for xen0 domain, and when i boot with xen0 kernel it reboots after this output... . . . ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.

Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

hello, I want to configure 2 interface like this eth0 for LAN is 172.16.0.3 eth1 for SAN is 192.168.0.13 I want all VM can access to all network my configuration is : (network-script ''network-bridge netdev=eth0'') to have peth0 and I have a peth0 interface (network-script ''network-bridge netdev=eth1'') to have peth1but I don''t have a peth1 interface

Hi all, With help from others, I''ve been able to get Olaf''s patch for enabling MTUs >1500 for vifX.y and tapZ devices working. I''ve been able to boot dom0, launch domU and live-migrate without having the bridge''s MTU degrade at any time. Would the Xen RPM maintainers (and others) mind taking a look at the following patches? Kernel part:

Hello, I was following the steps on creating a new bridge and attaching a physical nic to it. ******Steps mentioned in http://wiki.xensource.com/xenwiki/XenNetworking#head-d5446face7e308f577e5aee1c72cf9d156903722 ***************** if you want to use multiple bridges, you must create them yourself, either manually, or via your own startup script, or via a custom script to replace network-bridge.

Hi *, having built Xen 4.1.0 and running my Dom0 on Slackware 13.1, I''m trying to assign different physical network interfaces to different DomU guests: vif = [ ''bridge=ethX'' ] in the DomU configuration files. My /etc/xen/scripts/network-bridge script, however, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start

Hi, I just tested in the lab the new CentOS 5.1 Xen and find out it breaks network connectivity, at least in my setup. It seems it is somehow making use of the 3.1 Xen version (altought I am not sure about that) but whatever changes it introduce is not documented at the location one would expect, the obvious new thing (at least for me) is this thing I will call out of guessing a virtual