similar to: Bug#437127: xen-utils-common: vif-common fails to identify ip address of ethernet device

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal On my systen, the script vif-common fails to retrieve the primary IP address of my ethernet device, preventing a domU from starting. I tracked this issue down to the file /etc/xen/script/vif-common. The function ip_of uses the following shell code to extract the address: ip addr show "$1" | awk "/^.*inet.*$1\$/{print

I did some fine tuning on the command line, and this one should be an even better alternative: ip -4 -o addr show primary dev $1 | awk '$3 == "inet" {print $4; exit}' | sed 's!/.*!!'

I can confirm the problem. The provided patch fixed it for me. Greets, Peter

Anything new here? The bug still perisists and is quiet annoying, especially when considering the simplicity of its fix. On a side note, vserver-debiantools had a similiar problem which got fixed within 2 days (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539448), while the faulty line of shell code still resides in vif-common after 2 years and several confirmations.

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

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

Package: xen-utils-common Version: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 Severity: important Tags: patch security -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),

Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:

Hi List, I am running a 64 bit 5.3 kernel on an intel mb and all has been well. Today I thought it would be okay to reboot so that the latest kernel was running - i.e move from 128.2.1 to 128.4.1 release. The system passes POST fine, grub passes control to the 128.4.1 kernel and the boot process is under way. after some 30 secs the system starts beeping - continuously. After I hooked up a

This isn''t even close to ready for release, but in case anybody is interested, has feedback, finds it useful as is, or even wants to collaborate... I''ve been working on a "personal information server", something of a protocol multiplexer. Right now it serves calendar feeds for: - a local calendar folder (iCal 1.x''s Library/Calendars) - rss for local todos

When start a domU through xl create. The domU associated ip in the configuration file is not recorded in the xenstore. For this reason vif-common.sh antispoof scripts fails. *xl create * /usr/bin/xenstore-ls /local/domain/0/backend/vif/5/0 frontend = "/local/domain/5/device/vif/0" frontend-id = "5" online = "1" state = "4" script =

I had some problems getting Xen to work on my machine. I tracked down the problem to the function dom0_ip in vif-common.sh which shall retrieve the ip address of the main network device of dom0. This function, however, fails in some admittedly unusual configurations. The machine in question is a rented server. The LAN adapter is configured with a /32 netmask. I have debian, and this is an excerpt

What would be the effect of changing the password field in "/etc/passwd" from "x" to "*"? I noticed I have an "/etc/passwd.rpmnew" file which changes the password of many service accounts from "x" to "*". I am wondering if I should merge those changes into my "/etc/passwd" file. -- Matt Seitz Manager, File System

My ocfs filesystems used to mount automatically at boot, but now I've noticed that I have to do a mount -a after the boot up is completed to mount them. I've checked the init state to see that ocfs is enabled at run levels 3, 4, & 5 # chkconfig --list ocfs ocfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off Nothing shows up in the /var/log/messages file that would

Does the /dev/urandom issue apply to Solaris 9 as well??? Thanks Ron -- Dr. Ronald Barker Senior Technology Manager Vodafone Group Research & Development - D Vodafone Pilotentwicklung GmbH Chiemgaustrasse 116 81549 Munich Germany Fon: + 49 (89) 95 410-0 Fax: + 49 (89) 95 410-111 mailto:ron.barker at v-pe.de http://www.vodafone-rnd.com <<Barker, Ron, vpe.vcf>>

Hi to all, We are a bit of newbes to imap etc, so may be we just not doing it right. Nevertheless, We have compiled dovecot to run under Solaris 8/9 for IPv6 test. We are going crazy. After a successful compilation, the troubles really began. Solaris 9 1. Every?time we reboot- the directory /var/run/dovecot/auth is gone ???? 2. After the dir is created manually, the server starts.

First attempt was unsuccessful... -------------- next part -------------- An embedded message was scrubbed... From: Evan Panagiotopoulos <panagiot@frontiernet.net> Subject: Rad Hat installation by newbie Date: Fri, 10 Jul 1998 22:22:09 -0400 Size: 2011 Url: http://lists.samba.org/archive/samba/attachments/19980712/8a69f3c0/attachment.eml -------------- next part -------------- A non-text

After going through the /usr/doc/samba-1.9.17p4/DIAGNOSIS.txt file (GREAT debug/diagnostic tool!!!!!!!) I'm closer than ever!!!!!!!! I now SEE THE Linux machine name in my Network Neighborhood!!!!!!!!! I can ping both machines without any problem from both machines (W98 and Red Hat 5.1). I have edited the registry to allow plain text passwords. When I try net view from my W98 machine I see

We want to expand the LUN's on our SAN. I have expanded the LUN's, rebooted the hosts, now want the hosts to mount up the larger LUN, but they still see the original size. How risky is it to use tuneocfs to grow the filesystem after the expanded LUN is presented to the host? I was unable to find anything outside the man page for it. -------------- next part -------------- A non-text

> From: Johnny Hughes <johnny at centos.org> > > In this case you DO NOT want to integrate these changes [...] > This issue was caused in CentOS-4 (a /etc/passwd.rpmnew file) > due to an > update to the "setup" rpm in March ... and in this case, you can > remove/ignore that file. Thank you for explaining all of this. Is this issue documented somewhere?