similar to: Move qemu-ifup to xen-common

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

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.

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. #

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

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

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 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

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, 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

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-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:

Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor Hi, In /etc/xen/scripts/qemu-ifup -c is not a valid argument to echo, did you mean -n? Thanks Simon

On Tue, Sep 08, 2015 at 05:41:14PM +0800, Jackie wrote: > Hi experts, > > When I hotplug nic into lxc, the nic in lxc seemed to be down status as > following: > > 1224: vnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 > link/ether fa:16:3e:fc:e5:96 brd ff:ff:ff:ff:ff:ff > > > It seems mechanism such as udev is needed here. But I

Hello, I have some domU accounts running CentOS 4.4 and whenever I try to bring up the network interface it fails with the following errors: [root@test5.liquidweb.com] ~ # ifup eth0 Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help'' for more information. Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help'' for more information. Usage: arping [-fqbDUAV] [-c

# HG changeset patch # User Bastian Blank <waldi@debian.org> # Date 1204887078 -3600 # Node ID 5fb1c83d7ec89eb83c7c32eb7ee3b7a6b796478f # Parent 968faff41008504641c5cb700c4e83c6aaa3c009 Remove deprecated and unused features from LaTeX source. Signed-off-by: Bastian Blank <waldi@debian.org> diff -r 968faff41008 -r 5fb1c83d7ec8 docs/src/interface.tex --- a/docs/src/interface.tex Fri

On Sun, Apr 26, 2015 at 10:50:16AM +0200, Daniel Pocock wrote: > On 26/04/15 10:45, Bastian Blank wrote: > > Well, if you can pursuade the release team. We have grub2 for Xen > > in Jessie now and it can be used on Wheezy as well. > Can you be more specific? If somebody is running a wheezy dom0 and > they install grub2 in their domU before rebooting it the first time, >