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

RE: [Xen-devel] Unstable fail to load dom0


  • To: Andrew Lyon <andrew.lyon@xxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Sat, 28 Mar 2009 00:09:43 +0800
  • Accept-language: zh-CN, en-US
  • Acceptlanguage: zh-CN, en-US
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 27 Mar 2009 09:10:13 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acmu67S8S6YVp+OiRK2ywrlasmKYBwACh/bw
  • Thread-topic: [Xen-devel] Unstable fail to load dom0

Hi Andy,
Can you try to change the xen parameter 'iommu' to 0?
If with iommu=0 you can boot Xen fine, that may be due to a known BIOS bug and 
you can use xen with c/s >=19270 and use "iommu=1 iommu_inclusive_mapping=1".

Thanks,
-- Dexuan

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Andrew Lyon
Sent: 2009å3æ27æ 22:52
To: Ian Campbell
Cc: Xen-devel
Subject: Re: [Xen-devel] Unstable fail to load dom0

On Fri, Mar 27, 2009 at 2:26 PM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> On Fri, 2009-03-27 at 10:16 -0400, Andrew Lyon wrote:
>>> Hi,
>>>
>>> I just tried to upgrade one of my systems to Xen unstable, Xen itself
>>> boots ok but it hangs after "Loading dom0", I think the cause of the
>>> problem is that the necessary support for loading compressed kernel
>>> (vmlinuz/bzImage) was not compiled in properly, I seem to recall that
>>> recently the compression code was updated and now supports many
>>> different compression schemes, what libs etc are required to build
>>> with support for bzImage and vmlinuz?
>>
>> For domain0 the decompression code is built into the hypervisor itself
>> and only supports gzip style compression (historically the only choice).
>>
>> Therefore your kernel config must have:
>> Â Â Â ÂCONFIG_KERNEL_GZIP=y
>> Â Â Â Â# CONFIG_KERNEL_BZIP2 is not set
>> Â Â Â Â# CONFIG_KERNEL_LZMA is not set
>>
>> Ian.
>>
>>
>>
>>
>
> Hmm, not that then, any ideas why it would hang immeediatly after
> "loading dom0" ?
>
> The same grub entry works perfectly if Xen 3.3.1 is installed, it is
> loading xen.gz which is symlinked to the installed version.
>
> Andy
>

This is not a build issue, the same xen-3.4-unstable.gz + grub stanza
works ok on my Dell Optiplex 755, but on my Supermicro X7DWA-N it
locks up at (XEN) *** LOADING DOMAIN 0 ***


title Xen 3.4 / Linux 2.6.29-suse
root (hd0,0)
kernel /xen.gz iommu=1 com1=115200,8n1 console=vga,com1 noirqbalance
watchdog dom0_vcpus_pin
module /vmlinuz-2.6.29-xen root=/dev/sda2 swiotlb=256 console=xvc0 console=tty1

Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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