From mboxrd@z Thu Jan 1 00:00:00 1970 From: list user Subject: BUG? domU reboot fails when using "pci =" option Date: Thu, 04 May 2006 09:47:51 -0700 Message-ID: <445A3037.1030208@mailinator.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 /usr/lib/xen/xend/server/pciif.py 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