similar to: Setting up virtual ''ethX'' devices in Xen 3.4

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: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

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

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,

Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0

Hello, I have a network issue in dom0; I''m not sure if it''s a configuration problem or a design problem in my setup. My setup: The server (dom0) runs Ubuntu 7.10, Xen was installed using apt-get (means version: Xen 3.10, Kernel 2.6.22-14). This server has 4 NICs. I use bridged networking with my own script which creates 4 bridges ("$dir/network-bridge"

wiki name: HavardSorli Page for update : https://wiki.centos.org/FAQ/CentOS7 some notes / comments / open points to: FAQ "4. .... want it to work and to hand-edit the configuration files." My user case: "Adding an extra ip to the same interface" in the "old days" an alias. ( I am not sure if this should be an extra faq question, or incorporated in FAQ 4) I have

Hello, I''m new to Xen (and this mailing-list) and facing some problems with the network. I''m stuck and don''t know how to continue. And Google isn''t very helpful either... My setup: - Ubuntu 7.10 for dom0 and Debian 4.0 for all domU - 4 physical NIC (DHCP from my ISP, internal LAN, DMZ & WLAN) - 1 Dom as firewall/router - 1 domU with internal services

Here are three small patches that I have applied to the Fedora xen builds and I think are are suitable for xen-4.1.0. The first patch fixes an anomaly in /etc/xen/scripts/network-route. Currently this script contains netdev=${netdev:-eth${vifnum}} ie. netdev is set to eth${vifnum} by default. Unfortunately vifnum is not set anywhere in the xen code so the default is actually the broken

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Hello CentOS gurus, and a belated Happy New Year (or an early Happy Chinese New Year). I'm in the process of building a CentOS-6 KVM host machine whose only function will be to run four independent 'm0n0wall' firewall guest instances. I have a couple of quad-port Intel NICs to provide four WAN-side and four LAN-side ports, which will not be shared with any other guests. Remote

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Running CentOS 5.5 x86_64 on Dell R710 boxes. I have the server(s) configured for bonding/vlan and will be using iscsi to a SAN. I am in the pre-deployment stage so I am just setting up the basic cookie cutter configurations so I haven't initiated the iscsi connection to a SAN yet. While going through the error messages I noticed this error: kernel: bnx2i: iSCSI not supported, dev=ethX.

Nicolas Kovacs wrote: > Hi, > > I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd > like to swap the interface names, but I don't know how to go about that > under CentOS. > > Here's what I would do on a Slackware server (I have one next to me in > my office). > > Open /etc/udev/rules.d/70-persistent-net.rules and edit it: > >

Hi I have a Centos 6.X router/firewall/gateway for a /29 network all connected to one ETHX that has a switch behind it. This setup works very well but does NOT allow me to QOS one of the devices (a VOIP phone, many lines) as for "tc" to work I need a device, not ipaddress. I thought to connect the VOIP phone directly to the router, but in doing so I need that interface to ACT like the

Hi, I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd like to swap the interface names, but I don't know how to go about that under CentOS. Here's what I would do on a Slackware server (I have one next to me in my office). Open /etc/udev/rules.d/70-persistent-net.rules and edit it: # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:04.0/0000:03:00.0 (e1000e)

Hi all. What is the canonical way of getting xen to fully work with 802.1q (vlans) ? After (re)searching i found many ways but so far none is working. platform is gentoo (x86/32) and netwerk card a tg3. xen is v3. my config is as follows ... eth0 is simply up (with no ip) and i created several eth0.x interfaces corresponding to several vlans. eth0.10 is de ''default'' vlan

Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.

Hi All, We have a single Centos 5.11 server running a xen hypervisor that went down hard after an extended power outage this weekend. I'm mostly familiar for KVM as that is the majority of what our guests run under and have tried getting up to speed on xen bridging to no avail. The problem is that after the xen server spun back up, the previously defined xen bridges were lost. I've