[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



list user wrote:
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.


Additional info.

If xend and xendomains are set to run automatically at boot time via chkconfig the same error occurs, but ONLY when the pci device has been exported to a domU. An "xm list" starts at domid 2, showing that one domU has failed at startup.

Again, the error is familiar, but this time displays on the domain-0 console:

  local variable dev_config referenced before assignment

:m)

Hope that's helpful to someone.

Mike Wright



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.