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

Re: [Xen-devel] [BUG] Xen vm kernel crash in get_free_entries.



On 10/18/2013 01:46 PM, Ian Campbell wrote:
On Fri, 2013-10-18 at 10:31 +0100, David Vrabel wrote:

I suspect some of the changes for ARM has caused this (because ARM is
sort of PVHVM without a platform PCI device) but I had a quick look and
couldn't spot anything.  Stefano, any ideas?
If there is no platform device then we should never be going anywhere
near any of the grant table code...

 From the log in the original post it looks like at least some parts of
the kernel think it is running PVHVM (i.e. it does the unplug and says
"Booting paravirtualized kernel on Xen HVM"). I don't think this should
not be the case if there is no platform pci device.

Could this be because XenServer uses this platform_device=2 thing, which
is enough to trigger some of the early setup (because the unplug
protocol is present on I/O ports 0x10) but then the PCI driver in Linux
doesn't know about this ID and so never initialises the rest of it?

Astarta, which of these configurations have you tried:

  - No platform device at all
  - Platform device with ID == 1
  - Platform device with ID == 2

and what happened with each?

Ian.


Hello Ian,

3.11.5 kernel boots OK if platform:device_id=0001 (see attached vm_boot_log_id1.txt and VM config vm_cfg_id1.txt) 3.11.5 kernel crashes if platform:device_id=0002 (see vm_boot_log_id2.txt mv_cfg_id2.txt).

Sorry, but I really dont know and cannot find in google how to test w/o platform:device_id at all. My system doesnt have xl.cfg in /etc/xen/ and I use xe utility to change parameters. I've tried not to specify platform:device_id leaving it empty (i.e. xe vm-param-set uuid=<VM UUID> platform:device_id= ). Kernel crashes. see vm_boot_log_id_empty.txt and vm_cfg_id_empty.txt ).


Let me know if there's anything else I can do to shed some light to the problem.

--
Marina


Attachment: vm_boot_log_id1.txt
Description: Text document

Attachment: vm_boot_log_id2.txt
Description: Text document

Attachment: vm_boot_log_id_empty.txt
Description: Text document

Attachment: vm_cfg_id1.txt
Description: Text document

Attachment: vm_cfg_id2.txt
Description: Text document

Attachment: vm_cfg_id_empty.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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