search for: vifname

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341941699 -3600 # Node ID efb7fee3573b68e895de0341dd67df83cb68acc6 # Parent ca5c306052791edf6d96da3f80aecd750b86a5e4 hotplug: vif: fail if a duplicate vifname is used. This is based on a patch from Hans van Kranenburg in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658305. Quoting that bug report: When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error...

Hello, While using xen 4.1-testing.hg (r23202) I noticed that the ''vifname'' config value is not handled by xl, but is handled by xm. Is there a workaround or patch for this? My firewall and scripts depend on static vifnames. XM works good - it adds multiple interfaces to multiple bridges and configures them appropriately. But with xl it differs -- here only tap...

Hello, While using xen 4.1-testing.hg (r23202) I noticed that the ''vifname'' config value is not handled by xl, but is handled by xm. Is there a workaround or patch for this? My firewall and scripts depend on static vifnames. XM works good - it adds multiple interfaces to multiple bridges and configures them appropriately. But with xl it differs -- here only tap...

Hi, Centos 7 Xen4CentOS - 4.6.1 Open vSwitch When i specify custom name of the domU NIC than it refues to start vif = [ 'vifname=vNIC1' ] libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-openvswitch online [10168] exited with error status 1 libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script: ip link set vif38.0 name vNIC1 failed libxl: error: libxl_create.c:1381:do...

Package: xen-utils-common Version: 4.1.2-3 Severity: normal When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error), the hotplug scripts fail silently to rename the new vifX.0 to the custom vifname, if it's already existing. The result of this, is that the domU will start normally, but no network traffic bet...

Hello to all, Does anyone know if there is a maximum length of the vifname string? Is this a xen limit or a kernel limit? Say a string 10 characters long, other than the obvious hassle of ifconfig truncating the name are there any other issues to think of? Has anyone used a longer vifname and experience any quirks like possibly snmp truncating the string too? Many tha...

Is there a way to dinamically know on which network interface domU sees the Vif Dom0 "gives" to them. Ex: on Dom0: Vifname: vif111.0 on DomU: vif111.0 on network interface : eth0 Best Regards, Diego Dias _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...uot; bridge = "xenbr0" domain = "test1" handle = "0" script = "/etc/xen/scripts/vif-bridge" state = "4" frontend = "/local/domain/111/device/vif/0" mac = "00:16:3e:00:67:fc" vifname = "v-test1" frontend-id = "111" hotplug-status = "connected" 160 = "" 0 = "" bridge = "xenbr0" domain = "test1" handle = "0" script = "/etc/xen/scripts/vif-bridg...

...e # tail -35 /var/log/xen/xen-hotplug.log /etc/xen/scripts/vif-bridge: /etc/xen/scripts/vif-common.sh: line 66: syntax error: Bad fd number /etc/xen/scripts/vif-bridge: line 94: syntax error: Bad fd number i have checked the /etc/xen/scripts/vif-common.sh file i think there is no syntax error 57vifname=$(xenstore_read_default "$XENBUS_PATH/vifname" "") 58if [ "$vifname" ] 59then 60 if [ "$command" == "online" ] && ! ip link show "$vifname" >&/dev/null 61 then 62 do_or_die ip link set "$vif" name "$vifnam...

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

...bridge id STP enabled interfaces eth0 8000.003048359fc0 no peth0 xenbr0 8000.feffffffffff no vm01 Of course this can not work. I changed the client vif setup from; if = [''mac=00:16:3e:12:af:01, bridge=xenbr0, vifname=vm01'' ] to: if = [''mac=00:16:3e:12:af:01, bridge=eth0, vifname=vm01'' ] root@quadxeon2:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.003048359fc0 no peth0...

...ckend.rules. evalVariables (line 202) searches for arguments with an ''='', like ''foo=bar'', and sets those variables accordingly (like $foo == ''bar''). This is a nice trick I found in xen-script-common.sh. On to line 220-292. This searches for the vifname and bridge name. If $command is ''offline'' or ''remove'' then I found that it does not know the vifname so it needs a way to find that. In all cases $vifname is set to the requested vifname. Openvswitch does not require a bridge name if you remove a device. So $brid...

...virt-what and cPanel scripts report domU as: xenpv dom0: 2.6.18-371.6.1.el5xen Xen 4.1.2 domU Config: bootloader = '/usr/bin/pygrub' extra = '' memory = 6144 hostname = 'web2.x.ca' cpu_weight = 256 name = 'vm115' vif = ['ip=205.X.X.X, vifname=vifvm115.0, mac=00:16:3e:7a:X:X'] vnc = 0 vcpus = 6 vncviewer = 0 serial = 'pty' disk = ['phy:/dev/xen/vm115_img,xvda1,w', 'phy:/dev/xen/vm115_swap,xvda2,w'] domU kernel: 2.6.32-431.5.1.el6.x86_64 root at web2 [~]# virt-what xen root at web2 [~]#...

Hi guys! Can i use a IPv6 adress at XEN 4.0.1 of Debain 6? In my cfg I use this setting: vif = [ ''ip=85.10.210.154 46.4.44.162 2a01:4f8:130:9301::3'' ] But i get the error message: Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed; error detected. Best regards, Stefan _______________________________________________ Xen-users

...#39;], [''dev'', ''sda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''ip'', ''x.x.x.x''], [''mac'', ''AA:00:00:18:98:FD''], [''vifname'', ''vm03'']]]]) [2006-05-22 00:13:02 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) parseConfig: config is [''vm'', [''name'', ''xen3''], [''memory'', 128], [''vcpus'', 1], [''image'...

I am attempting to setup a firewall in a DomU. The firewall program I eventually want to run is Shorewall. Both my Dom0 and DomU are Debian Lenny 64 bit systems. The Dom0 has four physical network interfaces installed. Currently, one of the NICs is hidden using the pciback.hide command in the /boot/grub/menu.lst file. Similarly, the hidden NIC is passed to the DomU using the pci =

...[''dev'', ''hda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''ip'', ''192.168.2.6''], [''mac'', ''00:16:3e:b1:d7:91''], [''vifname'', ''vif2.0'']]]]) [2007-10-30 11:57:01 xend.XendDomainInfo 16192] DEBUG (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''work''], [''memory'', ''128''], [''on_poweroff...

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now

.../xenwiki/PythonInXlConfig Failed to parse config file: Invalid argument I''m using python stuff to define vifs and disks related to vm name: bootloader = "/usr/bin/pygrub" memory = 1024 name = "vm1" vcpus = 4 vif = [ ''ip=10.111.5.10 10.111.5.11, bridge=trunk0, vifname=%s.0'' % (name), ''ip=192.168.50.83, bridge=trunk1, vifname=%s.1'' % (name) ] disk = [ ''tap2:vhd:/cloud/data2/machines/%s.vhd,xvda,w'' % (name) ] root = "/dev/xvda1" extra = "fastboot" ip = "10.111.5.10" netmask = "255.255...

...ckend.rules. evalVariables (line 202) searches for arguments with an ''='', like ''foo=bar'', and sets those variables accordingly (like $foo == ''bar''). This is a nice trick I found in xen-script-common.sh. On to line 220-292. This searches for the vifname and bridge name. If $command is ''offline'' or ''remove'' then I found that it does not know the vifname so it needs a way to find that. In all cases $vifname is set to the requested vifname. Openvswitch does not require a bridge name if you remove a device. So $brid...