similar to: Bug#407210: Invalid argument to echo in qemu-ifup

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

Hi folks I forgot to move qemu-ifup to xen-utils-common. So this needs to be done now. Plan. - Upload xen-common today. xen-utils-common includes the qemu-ifup script and replaces xen-utils-3.0-unstable and xen-utils-3.0.2-1 with versions <= current. - Wait five days so both xen-unstable and xen-common can migrate to testing. - Upload xen-unstable and xen-3.0. The utils packages depends

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

tags 671018 +patch thanks This issue has been fixed upstream for 4.2 by using the same hotplug scripts for tap devices as for vif devices rather than using a special qemu-ifup script. I don't think this is an appropriate thing to backport to 4.1 for wheezy so therefore I think the right fix is as Pierre suggests to set the MAC address in the qemu-ifup script. In terms of a patch to the

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

Regarding change #194: " Add /etc/xen/qemu-ifup to the ioemu package, which Nate says is useful... Btw should that be into scripts? Should it be a config file at all?" This is required to set up hvm domains - it gets called to set up the network interface. It'd probably make more sense to put it in scripts, but I'm not sure where the config file is that controls where it

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the

Hi, I have tried the qemu-ifup script as below with nmcli command as brctl is deprecated on rhel8, but the guest network can not work. I think the script needs update. Could you please help to have a look? Thank you in advance. 1. prepare a linux bridge on the host named br0; 2. prepare the qemu-ifup script as below: # cat /etc/qemu-ifup #!/bin/bash # A br0 bridge should be already set up. #

Processing commands for control at bugs.debian.org: > close 407210 Bug #407210 [xen-utils-common] Invalid argument to echo in qemu-ifup Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 407210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407210 Debian Bug Tracking System Contact owner at bugs.debian.org with problems

Hi all I have a SuSE 9.3 domU. It has a eth0 interface, corresponding to some vif interface in the dom0. Running ifup eth0 doesn''t seem to work. This means I don''t get any network. It seems that /sbin/ifup relies upon /sbin/getcfg but getcfg does not seem to find the right configuration for the eth0 device. A attached a patch below with a work around for this.

Package: xen-utils-common Version: 4.0.0-1 Severity: normal When a qemu hvm with vif=['type=ioemu,bridge=eth0'] is created, xen will successfully create the required vif and tap bridge interfaces, but will create the corresponding iptables filter rules for the vif interface only, not the tap interface. With a FORWARD policy of DROP (e.g. by enabling antispoofing) network traffic from/to

Hello, since updating to Centos 7.4 the ifup-post script in /etc/sysconfig/network-scripts does not behave as it did before the update. I use it to configure additional routes via? /sbin/ifup-local with the parameter of the interface being upped, but it seems to pass only 'lo' as interface name. Before it passed correctly 'eth0:0' of the virtual interface. Added a line in

Dear CentOS, I think i found a "bug" in the /etc/sysconfig/network-scripts/ifup-eth script of CentOS 5.2. i can post the my changed ifup-eth script if you want. Am I the first one with this problem? Situation: - eth2 and eth3 should be in bond1 interface - bond1 should be an interface of bridge named "iscsi" the problem is that the brctl addif command in ifup-eth gets

Anyone know off the top of their head the "right" way to hard set a link automatically to 100Mbps Full Duplex, etc using the ifup or ifcfg files? Don't see options in the scripts that might cover this, but maybe there's a more elegant way to do it than to do something in rc.local or hack up the ifup files myself... Ray

I and testing command line to up and down ethernet connection. if I perform following, client can not re-connect. ????? ifconfig eth0 down ????? ifconfig eth0 up if I use following, client can re-connect: ????? ifconfig eth0 down ????? ifup eth0 What difference between "ifconfig up" and "ifup"? thanks.

Hello List, I have one network card and added two IP-Adresses to it: eth1 192.168.1.1/24 eth1:1 10.1.2.3/24 a want to use static routes on device eth1:1 and added one in /etc/sysconfig/network-scripts/route-eth1:1: GATEWAY0=10.1.2.4 ADDRESS0=10.2.2.0 NETMASK0=255.255.255.0 What the network-script should execute in background is: ip route add 10.2.2.0/24 via 10.1.2.4 dev eth1 but it executes

Hi all, I set up an ADSL connection using rp-pppoe/pppoe-setup. The setting is to persist the connection, so that when the link goes down, it's re-up'd by pppd. The interface is "ppp0" and it appears "/sbin/ifup-local" is not called when re-uppping the ADSL link. It is a problem for me, as I have some routing tables which get cleared from the routes "via

Package: xen-utils-common Followup-For: Bug #706876 The problem here is that network-* scripts are fragile and prone to breakage. Both Debian and upstream recommend configuring networking explicitly using the normal distro mechanisms i.e. /etc/network/intefaces. See http://wiki.xen.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29 Ian. -- System Information: Debian Release: jessie/sid

Package: xen-utils-common Version: 3.2.0-2 Severity: normal Hi, we have a setup with a system that has multiple ethernet interfaces. There is a interface eth2 which has an IP configured and is connected to the network and which is used to administrate that. Another iface is supposed to be used as netdev (eth0). This interface is unconfigured but connected to a network to which the DomUs are

Hi, after a lot of head scratching I found that the ifup-eth script in the initscripts package seems to be corrupt. I filed a bug with the details here: http://bugs.centos.org/view.php?id=5333 Given the nature of the corruption you might be not affected at all, see strange error messages or end up with networking problems on Centos 5.7 depending on what you configuration looks like. I just