Bugzilla – Bug 861318
xentop reports "Found interface vif101.0 but domain 101 does not exist."
Last modified: 2016-03-21 15:58:31 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 This xenhost used to run 12.2, and was upgrasded to 13.1. When I run 'xentop', on every update, I get a line with "Found interface vif101.0 but domain 101 does not exist." Reproducible: Always
I wonder if some of the scripts from /etc/xen/scripts didn't get updated appropriately when the update happened? Or perhaps this is a host migration issue with upgrading from 12.2 using xm/xend to 13.1 which uses libxl? What xen packages are currently installed on your host? (rpm -qa | grep xen-)
(In reply to comment #1) > I wonder if some of the scripts from /etc/xen/scripts didn't get updated > appropriately when the update happened? > Or perhaps this is a host migration issue with upgrading from 12.2 using > xm/xend to 13.1 which uses libxl? I was using xl on 12.2 too. FYI, the message also appears with a newly created guest with vifname=vif271.0. I am not sure, but if I leave the vifname to be auto-generated, I don't believe I see the message. > What xen packages are currently installed on your host? > (rpm -qa | grep xen-) kernel-xen-devel-3.11.6-4.1.x86_64 kernel-xen-devel-3.3.0-2.4.x86_64 kernel-xen-devel-3.5.0-4.2.x86_64 xen-kmp-default-4.3.1_02_k3.11.6_4-4.4.x86_64 xen-libs-4.3.1_02-4.4.x86_64 kernel-xen-3.3.0-2.4.x86_64 xen-kmp-default-4.1.2_15_k3.3.0_2-2.6.x86_64 kernel-xen-3.11.6-4.1.x86_64 kernel-xen-3.4.2-1.1.x86_64 kernel-xen-3.5.0-4.2.x86_64 xen-4.3.1_02-4.4.x86_64 xen-tools-4.3.1_02-4.4.x86_64
Almost a year later - same problem on openSUSE 13.2
(In reply to Per Jessen from comment #3) > Almost a year later - same problem on openSUSE 13.2 Forgot to mention, this is a clean installation, not an upgrade.
(In reply to Per Jessen from comment #4) > (In reply to Per Jessen from comment #3) > > Almost a year later - same problem on openSUSE 13.2 > > Forgot to mention, this is a clean installation, not an upgrade. I have not seen this problem on my 13.1/2 hosts. Try running 'xenstore-ls' and attaching the output (as a file). Maybe something there will give us a clue. Also, what does 'xl list' show?
Created attachment 618696 [details] output from xenstore-ls
(In reply to Charles Arnold from comment #5) > (In reply to Per Jessen from comment #4) > > (In reply to Per Jessen from comment #3) > > > Almost a year later - same problem on openSUSE 13.2 > > > > Forgot to mention, this is a clean installation, not an upgrade. > > I have not seen this problem on my 13.1/2 hosts. > Try running 'xenstore-ls' and attaching the output (as a file). Maybe > something there will give us a clue. Also, what does 'xl list' show? Hi, thanks for looking into this. # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 420 4 r----- 1484.1 dupont5 18 768 1 -b---- 330.5
(In reply to Per Jessen from comment #6) > Created attachment 618696 [details] > output from xenstore-ls I am not seeing anything with 'vif101.0' in the xenstore database. Could you attach the following. 1) The output of 'ifconfig' 2) The configuration file for the dupont5 VM from /etc/xen/vm (both the regular version and the '.xml' version). Do you see the problem running xentop when no VMs are running? Thanks.
Created attachment 619075 [details] ifconfig output from airbus (xen host)
Created attachment 619076 [details] xen config for dupont5
(In reply to Charles Arnold from comment #8) > I am not seeing anything with 'vif101.0' in the xenstore database. > Could you attach the following. > 1) The output of 'ifconfig' > 2) The configuration file for the dupont5 VM from /etc/xen/vm (both > the regular version and the '.xml' version). I'm not sure where to look for the xml version? I guess there's a way of dumping it? > Do you see the problem running xentop when no VMs are running? No, only when there are active guests.
(In reply to Per Jessen from comment #10) > Created attachment 619076 [details] > xen config for dupont5 xentop assumes the domain ID to part of the vif interface name. For example with vif10 hardcoded in your config file it assumes the domain ID for this VM is 10 but doesn't find it (accept in the instance when 10 just happens to be the domid). Failing to find a matching domain ID (10) with any actual running VM causes xentop to print the error you are seeing. In your attached config file, edit the 'vif' line and remove just this, "vifname=vif10,". This will allow the toolstack to assign a vifname automatically which will contain the domain ID number in the name and xentop will parse it correctly.
(In reply to Charles Arnold from comment #12) > In your attached config file, edit the 'vif' line and remove > just this, "vifname=vif10,". This will allow the toolstack > to assign a vifname automatically which will contain the domain > ID number in the name and xentop will parse it correctly. Yes, I know that will work, but I need to assign reliable interface names, e.g. for use in firewall scripts and accounting. Is there a certain syntax I need to use?
I have just noticed that xentop will only complain when the most recent interface does not contain a matching domain-id. Earlier ones do not seem to pose a problem.
Can you update your Xen packages for os13.2 from this repo, Virtualization:openSUSE13.2/xen You will need version 4.4.1_09-1.1 (or newer). It contains a fix for xentop (among other bug fixes). Please let me know if this solves your problem.
See also, http://download.opensuse.org/repositories/Virtualization:/openSUSE13.2/openSUSE_13.2/
(In reply to Charles Arnold from comment #15) > Can you update your Xen packages for os13.2 from this repo, > > Virtualization:openSUSE13.2/xen > > You will need version 4.4.1_09-1.1 (or newer). > > It contains a fix for xentop (among other bug fixes). Please let me > know if this solves your problem. I can confirm this solves the problem, thanks.
SUSE-SU-2015:0613-1: An update that solves 8 vulnerabilities and has 7 fixes is now available. Category: security (important) Bug References: 861318,882089,895528,901488,903680,904255,906996,910254,910681,912011,918995,918998,919098,919464,919663 CVE References: CVE-2014-3615,CVE-2014-9065,CVE-2014-9066,CVE-2015-0361,CVE-2015-2044,CVE-2015-2045,CVE-2015-2151,CVE-2015-2152 Sources used: SUSE Linux Enterprise Software Development Kit 12 (src): xen-4.4.1_10-9.1 SUSE Linux Enterprise Server 12 (src): xen-4.4.1_10-9.1 SUSE Linux Enterprise Desktop 12 (src): xen-4.4.1_10-9.1
openSUSE-SU-2015:0732-1: An update that solves 7 vulnerabilities and has 5 fixes is now available. Category: security (important) Bug References: 861318,895528,901488,903680,910254,918995,918998,919098,919464,919663,922705,922706 CVE References: CVE-2014-3615,CVE-2015-2044,CVE-2015-2045,CVE-2015-2151,CVE-2015-2152,CVE-2015-2752,CVE-2015-2756 Sources used: openSUSE 13.1 (src): xen-4.3.4_02-41.1
openSUSE-SU-2015:1092-1: An update that solves 17 vulnerabilities and has 10 fixes is now available. Category: security (important) Bug References: 861318,882089,895528,901488,903680,906689,910254,912011,918995,918998,919098,919464,919663,921842,922705,922706,922709,923758,927967,929339,931625,931626,931627,931628,932770,932790,932996 CVE References: CVE-2014-3615,CVE-2015-2044,CVE-2015-2045,CVE-2015-2151,CVE-2015-2152,CVE-2015-2751,CVE-2015-2752,CVE-2015-2756,CVE-2015-3209,CVE-2015-3340,CVE-2015-3456,CVE-2015-4103,CVE-2015-4104,CVE-2015-4105,CVE-2015-4106,CVE-2015-4163,CVE-2015-4164 Sources used: openSUSE 13.2 (src): xen-4.4.2_06-23.1