[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed
> Maybe Xen 3.4.2 logic is much different than 4.0 when it comes to > exchanging MFNs > and Ian's is right. Under 4.0 it I've no trouble exchanging the MFNs > even without > any PCI devices being passed in. > > Can you try this patch to help narrow down the problem: > > diff --git a/arch/x86/xen/pci-swiotlb.c b/arch/x86/xen/pci-swiotlb.c > index ecdbfe2..37fd0e3 100644 > --- a/arch/x86/xen/pci-swiotlb.c > +++ b/arch/x86/xen/pci-swiotlb.c > @@ -960,7 +960,7 @@ xen_swiotlb_fixup(void *buf, size_t size, > unsigned long nslabs) > dma_bits); > } while (rc && dma_bits++ < max_dma_bits); > if (rc) > - panic(KERN_ERR "xen_create_contiguous_region failed\n"); > + panic(KERN_ERR "xen_create_contiguous_region failed: rc: %d\n", rc); > > i += slabs; > } while(i < nslabs); > > And also ensure that your command line for Xen has: console=com1,vga > guest_loglvl=all Made that change and tried again. rc was -12. Do you need the whole dump? I'm not really sure how to capture it... > And tell me what environemtn you are using? Is the hypervisor a 64-bit > while dom0 is 32bit or 64bit? Is DomU 32bit or 64bit? This particular test is on a Dell Precision M4400 w/ 4GB of RAM. Everything is 32-bit. Not using HVM. -Mike _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |