similar to: Bug#437127: Info received (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

I agree, please fix this issue! The bug report is over two years old now. -------------- next part -------------- A non-text attachment was scrubbed... Name: saschafroehlich.vcf Type: text/x-vcard Size: 310 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20090820/ede2fd42/attachment.vcf>

Package: logcheck-database Version: 1.2.54 Severity: normal Tags: patch Logcheck fails to ignore certain lines generated by OpenVPN; the attached patch fixes several regular expressions: * OpenVPN does not print the full path to ifconfig or route (at least here) * The interface name can also contain dots and does not always start with "tun" * The startup messages now gets suppressed

Processing commands for control at bugs.debian.org: > # changing olivier.berger at int-edu.eu to olivier.berger at it-sudparis.eu > submitter 454347 ! Bug#454347: reconfiguring twiki won't change rewrite rules Changed Bug submitter from Olivier Berger <olivier.berger at int-edu.eu> to Olivier Berger <olivier.berger at it-sudparis.eu>. > submitter 444448 ! Bug#444448:

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Hi, i''ve set up my puppet on several clients and today i noticed that the facts are loaded twice by the clients. I took strace to get the list of loaded fact file and i found that puppet seems to load the same fact files twice: chdir("/var/lib/puppet/lib/facter") = 0 open(".", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 6 info: Loading facts in vserver

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.0-5 Severity: important The hypervisor loads OK but then fails to load my dom0 kernel. I get an erorr message "not an ELF binary" followed after 5s by a hypervisor reboot. /boot/grub/grub.cfg contains: menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 (single-user mode)" { set root=(hd0,1)

Hi there, I''m running into an problem which I can resolve. It is bugging me for couple of days now. Goal: CentOS 6.4 freshly installed incl puppet 3.2.3 and I want to install puppet master, puppetdb, mod_passenger & apache with "puppet apply". So when this is complete, I should have an puppet master server running so I can create new hosts etc. So this is the command

Hi, I'm just install a debian etch, with lenny repository enabled, and the list o xen package listed below, but i didn't find package of xen-ioemu for hypervisor-3.1-1 . The xen-ioemu-3.0.3-1 package is dependable of xen-utils-3.0.3-1 and recomend the instalation o xen-hypervisor-3.0.3-1. Looking around, I found at http://download.thorstenstrusch.de/debian/etch/ xen-ioemu for

Greetings, So, anyone on this list using OS Virtualization? I've been using OpenVZ for about 1.5 years. I also have some experience with Linux-VServer. In my experience, if you want to do Linux on Linux, both OpenVZ and Linux-VServer offer native performance, better scalability, and higher density than VMware, Xen or KVM... although I must admit I haven't actually tried KVM yet. If

Hi, I am running xen 2.0 for some days now on a local network and it''s running fine :) Every virtual server on my host gets it''s own IP address. But now, I am wondering if it''s possible to run xen on a hosted root server with only one ip address. Lets say I have a domain ''domain.org'' that points to my host, on which xen is running. Is there a

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

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

Hello I''m new to the list. I installed a vserver (http://www.linux-vserver.org/) on my gentoo server As network interface is used an alias (eth1:0) eth1 is the card of my "loc" zone. eth1:0 has an address from the same subnet from the vserver I can connect to eth0 but not to the internet. From my local net everything works fine. I have an entry in "mask" for eth1

What about the REST API to do a graceful shutdown of your VM’s and the vCenter appliance: https://code.vmware.com/web/sdk/6.7/vsphere-automation-rest Bart… From: Lee Damon <nomad at ee.washington.edu> Sent: 14 May 2020 20:29 To: Bart J. Smit <bart at smits.co.uk> Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] NUT control of vCenter & vServer? Thanks Bart.

Processing commands for control at bugs.debian.org: > forwarded 437127 http://lists.xen.org/archives/html/xen-devel/2012-07/msg00455.html Bug #437127 [xen-utils-common] xen-utils-common: vif-common fails to identify ip address of ethernet device Set Bug forwarded-to-address to 'http://lists.xen.org/archives/html/xen-devel/2012-07/msg00455.html'. > thanks Stopping processing here.