WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

Ryan wrote:
On Thu, 2006-05-04 at 16:04 -0700, list user wrote:

Thanks Ryan,

I tried the fix but it just gave a different symptom. (same error, different variable)


Can you post the exact error message you're getting?


So... rpm --erase xen JIC there were any ghosts around. Manually removed all traces of xen from the system. Then did a ./install.sh from the xen-3.0.2-2 directory, which had a clean "make world".

The results are the same.

I've found a more generic error about a local variable being used before assignment, but I think it's referring to dev_config.

Again, this only happens on auto-boot or domU reboot, and only when there is a "pci =" line in the domU's definition file.

Any ideas how I can help debug this?



Can you post the output of /var/log/xend.log? If your file is large,
please don't attach the whole thing! :) Specifically, I'm interested in
any errors in the file and the debug lines that contains the words
"XendDomainInfo.create" followed by some information in lots of square
brackets. Also take a look at the kernel log in dom0 (type 'dmesg') and
look for any strange errors.

I've found an area in the log that _may_ show where the problem arises.

Let me give a refresher.  There are
   1 pci slot: 00:0d.0
   2 vif's on 2 bridges: LAN, DMZ
   3 vbd's: hda1, hda2, hda3

On a boot the following devices are created in this order:
   hda1, hda2, hda3, pci, LAN, DMZ

On a reboot the following devices are created in this order:
   LAN, DMZ, hda1, hda2, hda3

Note that the pci device is _not_ recreated on a reboot.

The following excerpt from xend.log shows the pci creation in a successful boot. This code never happens in a failed reboot.

[2006-05-05 11:31:27 xend] DEBUG (pciif:129) pci: enabling ioport 0xd400/0x100 [2006-05-05 11:31:27 xend] DEBUG (pciif:142) pci: enabling iomem 0xcffffd00/0x100 pfn 0xcffff/0x1 [2006-05-05 11:31:27 xend] DEBUG (pciif:142) pci: enabling iomem 0xcffc0000/0x20000 pfn 0xcffc0/0x20
[2006-05-05 11:31:27 xend] DEBUG (pciif:153) pci: enabling irq 5
[2006-05-05 11:31:27 xend] DEBUG (DevController:103) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/pci/3/0'} to /local/domain/3/device/pci/0. [2006-05-05 11:31:27 xend] DEBUG (DevController:105) DevController: writing {'domain': 'vm1', 'frontend': '/local/domain/3/device/pci/0', 'frontend-id': '3', 'dev-0': '0000:00:0d.00', 'state': '1', 'num_devs': '1'} to /local/domain/0/backend/pci/3/0.

Will keep digging....



Is the pci device appearing correctly in your domU? Do you see any
strange error messages or warnings in your domU before you try and
reboot it?

Ryan


_______________________________________________
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