This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] BUG? domU reboot fails when using "pci =" option

To: xen-users@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] BUG? domU reboot fails when using "pci =" option
From: list user <xktnniuymlla@xxxxxxxxxxxxxx>
Date: Thu, 04 May 2006 09:47:51 -0700
Delivery-date: Thu, 04 May 2006 09:44:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513)
Hi all,

I believe I've found a bug.

Running xen-3.0.2-2 with linux-2.6.16 built from sources.

Domain-0 has one hidden PCI slot:  pciback.hide=(00:0d.0)

It is exposed in a domU with pci = ['00:0d.0'].

If that domU is shutdown with xm destroy, or with a shutdown -h now, all
works as expected.  But if instead it is rebooted, either by xm reboot
or shutdown -r now, it shuts down, attempts to restart and fails
silently.  This is evidenced by the fact that an xm list has used up one
increment on its domU counter.  At that point a manual start works.

Now, if the pci device is NOT enabled in the domU config file, reboot
works correctly.

Checking xend.log provides a clue:

  dev_config referenced before assignment in

Not really a python coder but it looks like the invocation in question
is on line 97, which indicates that whole section of code may be borked,
since it now thinks it's xen-2.0.

Hope that's helpful to someone.

Mike Wright

Xen-users mailing list