similar to: Bug#658305: [PATCH] hotplug: vif: fail if a duplicate vifname is used

Displaying 20 results from an estimated 800 matches similar to: "Bug#658305: [PATCH] hotplug: vif: fail if a duplicate vifname is used"

2024 Mar 19
2
Bug#1067151: xen-utils-common: vif-openvswitch ignores MTU
Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also
2012 Feb 01
0
Bug#658305: Prevent silently failing on duplicate vifname
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
2008 Dec 01
1
Error: Device 0 (vif) could not be connected.Hotplug scripts not working.
Hi All I am using xen 3.3.0 version and I want to start network virtual interface on Dom U by using the following command # xend start *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is
2011 Dec 17
12
xl and vifname
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 devices are
2011 Dec 17
12
xl and vifname
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 devices are
2016 Apr 05
1
Xen custom vifname
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
2010 Nov 18
2
How to know which interface DomU sees the Vif device
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
2012 Dec 24
3
vif-route issue with HVM domU only
Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying
2007 Feb 24
0
vifname length
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 thanks in advance if anyone
2013 Jan 28
5
xl nat and wrong IPs
Hi, I''m currently switching from toolstacks from xm to xl. Because I have a rather complex network setup with my domUs, I use xen''s nat capabilities. But what works fine with xm behaves slightly strange in xl: I use something like the following to establish a domU interface within my vif part: ''type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11,
2012 Jul 10
0
Processed: bug 658305 is forwarded to http://lists.xen.org/archives/html/xen-devel/2012-07/msg00493.html
Processing commands for control at bugs.debian.org: > forwarded 658305 http://lists.xen.org/archives/html/xen-devel/2012-07/msg00493.html Bug #658305 [xen-utils-common] Prevent silently failing on duplicate vifname Set Bug forwarded-to-address to 'http://lists.xen.org/archives/html/xen-devel/2012-07/msg00493.html'. > thanks Stopping processing here. Please contact me if you need
2013 Aug 16
0
Processed: closing 658305
Processing commands for control at bugs.debian.org: > close 658305 Bug #658305 [xen-utils-common] Prevent silently failing on duplicate vifname Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 658305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658305 Debian Bug Tracking System Contact owner at bugs.debian.org with problems
2005 May 26
3
Updated Shorewall build and publish scripts
Attached please find updated build and publish scripts. They set the ''ulink.target'' parameter appropriately when converting docbook->HTML. I have always hacked my xhtml/params.xsl file to set this parameter; these updated scripts make that abomination unnecessary. Paul/Mike: It might be a good idea to add a CVS project for these scripts. -Tom -- Tom Eastep \ Nothing is
2008 Jan 18
1
XEN 3.2.0 default bridge changed ?
Hello ! I yesterday updated one server to XEN 3.2 which was running 3.1.2 before. The default bridge setup stopped working (Guests network packets were not forwarded to physical ethernet connection on eth0) My bridge setup looked like this: root@quadxeon2:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.003048359fc0 no
2014 Jun 12
1
Xen PV domU reported as Xen-HVM
Hello, I am running two dom0s, one on CentOS 5 with Xen 4.1.2 (from Gitco) and the other one on CentOS 6 with Xen 4.2.4 (from Xen4CentOS). I host one LVM based domU on both from the same template (CentOS 6 PV) with the same Xen config (see below). However, the domU on Xen 4.1 reports itself as Xen PV while the domU on Xen4CentOS reports itself as Xen HVM. == First domU == virt-what and cPanel
2006 May 21
2
exception looking up device number for sda1
I just tried to setup another domain on a server running 1 domain. When i try to start the domain it gives me an error Error: Device 0 (vif) could not be connected. Backend device not found. The entry in my xen config file for the disks is disk = [''phy:/dev/xen001/xen2-fun,sda1,w'',''phy:/dev/xen001/xen2-fun-swap,sda2,w''] Looking at /var/log/xend.log, i found
2007 Oct 30
1
xen xm list: DomUs blocked
Hi I''m using Xen on my AMD64 / Ubuntu 7.10 server which I recently upgraded, and my 2 VMs are decidedly flaky. They seem to be blocked for most of the time, and networking doesn''t work properly. How can I debug this and get them online reliably? Any tips gratefully received! * I can log in via console or ssh, can ping the server''s NICs but can''t ping the
2011 Jul 10
4
xen 4.1.1 - xl create and python in config files
Hi, I am in the process of upgrading some xen installations from 3.x to 4.1.1 and got into this: box# xl create vm1.cfg warning: Config file looks like it contains Python code. warning: Arbitrary Python is no longer supported. warning: See http://wiki.xen.org/xenwiki/PythonInXlConfig Failed to parse config file: Invalid argument I''m using python stuff to define vifs and disks
2014 Apr 16
0
Bug#744927: No VIF information in xentop with xl
Package: xen-utils-4.3 Version: 4.3.0-3+b1 Using the xl toolstack there's no information about the networks of the domUs in xentop. I have a PV and a HVM domU and both are shown as having 0 network interfaces, while in fact they have functioning interfaces. Here's one of the interfaces that should be shown, from xenstore: 29 = "" 0 = "" frontend =
2012 Jul 30
3
Xen networking disconnect
Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255