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

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



Ryan wrote:
On Tue, 2006-05-09 at 09:14 -0400, Ryan wrote:

Apparently there's a function missing (DevController::configuration) in
tools/python/xen/xend/server/pciif.py that rebuilds the configuration
for situations like reboot. If time allows, I'll add the function and
submit it, but if you or someone else needs it now, it should be pretty
trivial to write.

Ryan


Mike,

I was able to reproduce your problem on my box. The attached patch
should fix the problem (at least it does for me).

Can you apply it to your copy of Xen, reinstall, reboot Xen, and try
restarting your domU?

Thanks Ryan,

I applied the patch and restarted xend.

We're definitely much closer. The domain creation still bombed but for other reasons. The value of ['func','0x1'] is being erroneously reported as ['func','0x0'], which explains the following error:

"Failed to open & read /sys/bus/pci/devices/0000:00:0f.0/resource: No such file or directory".

Here's a snippet from xend.log from "reason=reboot" through "create".

[2006-05-09 09:05:37 xend.XendDomainInfo] INFO (XendDomainInfo:836) Domain has shutdown: name=vm2 id=7 reason=reboot. [2006-05-09 09:05:37 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) XendDomainInfo.destroyDomain(7) [2006-05-09 09:05:37 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainInfo.create(['domain', ['domid', 7], ['uuid', '5b2ac02f-11f4-9e15-0846-d119b768340f'], ['ssidref', 0], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 64], ['maxmem', 64], ['name', 'vm2'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-xen'], ['ramdisk', '/boot/initrd-2.6.16-xen.img'], ['root', '/dev/hda1 ro'], ['args', 'netloop.nloopbacks=0 4']]], ['device', ['vif', ['backend', 0], ['script', 'my-vif-bridge'], ['bridge', 'DMZ'], ['mac', '00:16:3e:22:22:02']]], ['device', ['vbd', ['backend', 0], ['dev', 'hda1'], ['uname', 'phy:vg0/vm2'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'hda2'], ['uname', 'phy:vg0/usr'], ['mode', 'r']]], ['device', ['vbd', ['backend', 0], ['dev', 'hda3'], ['uname', 'phy:vg0/sw2'], ['mode', 'w']]], ['device', ['pci', ['backend', 0], ['dev', ['domain', '0x0000'], ['bus', '0x00'], ['slot', '0x0f'], ['func', '0x0']]]], ['state', '---s--'], ['shutdown_reason', 'reboot'], ['cpu_time', 31.049057046000001], ['online_vcpus', 1], ['up_time', '95.3671748638'], ['start_time', '1147190641.98'], ['store_mfn', 39253], ['console_mfn', 39252]])

As you can see, near the end above, func is misreporting its value.

Your help is really appreciated.


I'll submit it to xen-unstable as soon as I can confirm that this fixes
your issue.

Ryan



_______________________________________________
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®.