On 09/23/09 16:05, Simon Horman wrote:
> On Wed, Sep 23, 2009 at 12:17:23PM -0700, Jeremy Fitzhardinge wrote:
>
>> On 09/22/09 22:32, Simon Horman wrote:
>>
>>> Hi,
>>>
>>> while trying to boot xen/master at the following changest the boot
>>> locks up somewhere around the initialisation of PCI. Boot log and
>>> config attached. Any insights appreciated.
>>>
>>> commit 398b4b4cabdb27c06a7b8214c2044347ffc08c49
>>> Merge: 3973dcf... 6e8f158...
>>> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
>>> Date: Tue Sep 22 15:21:28 2009 -0700
>>>
>>> Merge branch 'xen/dom0/drm' into xen/master
>>>
>>> * xen/dom0/drm:
>>> swiotlb: linux/swiotlb.h needs linux/dma-mapping.h
>>>
>>>
>>> My grub snippet is:
>>>
>>> title Xen
>>> root (hd0,0)
>>> kernel /xen com1=115200,8n1,0x3f8,0 console=com1 loglvl=all
>>> guest_loglvl=all dom0_mem=1G
>>> module /vmlinuz-2.6.31-pvops root=/dev/mapper/sam-root_x86_64
>>> console=ttyS0 loglevel=8 ro earlyprintk=xen
>>> module /initrd.img-2.6.31-pvops
>>>
>>>
>>>
>> You should really be using hvc0 for the console. I think ttyS0
>> "passthrough"/emulation should work, but using the Xen console is more
>> reliable. And you're just losing all console output on the switchover,
>> which suggests that serial isn't actually working. Failing that, can
>> you get more info from the VGA console?
>>
> Hi Jeremy, Hi Pasi,
>
> Thanks for the advice with regards to hvc0, that is working well.
> I am now observing a problem while initialising the iommu.
> I have worked around this by setting iommu=off.
>
Ah, OK, someone else noticed that too. I guess we should inhibit iommu
init somehow.
Keir, is Xen supposed to disable the DMAR for dom0 by stomping on acpi
or something? Or was that about something else?
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home