Unstable fail to load dom0

Unstable fail to load dom0

[Andrew Lyon]

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?

Thanks
Andy

Re: Unstable fail to load dom0

[Ian Campbell]

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.

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@citrix.com> 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

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 2:26 PM, Andrew Lyon <andrew.lyon@gmail.com> wrote:
> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@citrix.com> 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

Re: Unstable fail to load dom0

[Keir Fraser]

On 27/03/2009 14:52, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:

> 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 ***

Could you try editing xen/arch/x86/boot/reloc.c and delete all lines from
the function reloc() in that file except for the last line 'return mbi;'.
That code is new since 3.3 and one possible cause of your problem.

 -- Keir

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 3:47 PM, Ian Campbell
<Ian.Campbell@eu.citrix.com> wrote:
> On Fri, 2009-03-27 at 10:52 -0400, Andrew Lyon wrote:
>> 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 ***
>
> Does it work with a non-bzImage kernel?

I've never used a bzImage kernel with Xen, it is a vmlinuz image.

/boot/vmlinuz-2.6.29-suse: gzip compressed data, from Unix, last
modified: Fri Mar 27 10:46:40 2009, max compression

Andy

>
> If you do a verbose=y (which is implied by debug=y, I think) build of
> the hypervisor you might get some more output from the ELF parser.
> Otherwise you might need to add your own printk debugging.
>
> Ian.
>
>
>

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 3:49 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 27/03/2009 14:52, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:
>
>> 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 ***
>
> Could you try editing xen/arch/x86/boot/reloc.c and delete all lines from
> the function reloc() in that file except for the last line 'return mbi;'.
> That code is new since 3.3 and one possible cause of your problem.
>
>  -- Keir
>
>
>

Fails to compile:

make -f /usr/src/xen-3.4.0/xen/Rules.mk -C include
make[3]: Entering directory `/usr/src/xen-3.4.0/xen/include'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/xen-3.4.0/xen/include'
make -f /usr/src/xen-3.4.0/xen/Rules.mk -C arch/x86 asm-offsets.s
make[3]: Entering directory `/usr/src/xen-3.4.0/xen/arch/x86'
make[3]: `asm-offsets.s' is up to date.
make[3]: Leaving directory `/usr/src/xen-3.4.0/xen/arch/x86'
make -f /usr/src/xen-3.4.0/xen/Rules.mk include/asm-x86/asm-offsets.h
make[3]: Entering directory `/usr/src/xen-3.4.0/xen'
make[3]: `include/asm-x86/asm-offsets.h' is up to date.
make[3]: Leaving directory `/usr/src/xen-3.4.0/xen'
make -f /usr/src/xen-3.4.0/xen/Rules.mk -C arch/x86 /usr/src/xen-3.4.0/xen/xen
make[3]: Entering directory `/usr/src/xen-3.4.0/xen/arch/x86'
make -f /usr/src/xen-3.4.0/xen/Rules.mk -C
/usr/src/xen-3.4.0/xen/arch/x86/boot built_in.o
make[4]: Entering directory `/usr/src/xen-3.4.0/xen/arch/x86/boot'
RELOC=0x8c000 make -f build32.mk reloc.S
make[5]: Entering directory `/usr/src/xen-3.4.0/xen/arch/x86/boot'
gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m32
-march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-fno-stack-protector -Werror -fno-builtin -msoft-float -c reloc.c -o
reloc.o
reloc.c: In function 'reloc':
reloc.c:62: error: 'mbi' undeclared (first use in this function)
reloc.c:62: error: (Each undeclared identifier is reported only once
reloc.c:62: error: for each function it appears in.)
make[5]: *** [reloc.o] Error 1
make[5]: Leaving directory `/usr/src/xen-3.4.0/xen/arch/x86/boot'
make[4]: *** [reloc.S] Error 2
make[4]: Leaving directory `/usr/src/xen-3.4.0/xen/arch/x86/boot'
make[3]: *** [/usr/src/xen-3.4.0/xen/arch/x86/boot/built_in.o] Error 2
make[3]: Leaving directory `/usr/src/xen-3.4.0/xen/arch/x86'
make[2]: *** [/usr/src/xen-3.4.0/xen/xen] Error 2
make[2]: Leaving directory `/usr/src/xen-3.4.0/xen'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/usr/src/xen-3.4.0/xen'
make: *** [install-xen] Error 2


Andy

RE: Unstable fail to load dom0

[Cui, Dexuan]

[-- Attachment #1: Type: text/plain, Size: 2395 bytes --]

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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] 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@gmail.com> wrote:
> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@citrix.com> 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@lists.xensource.com
http://lists.xensource.com/xen-devel

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Unstable fail to load dom0

[Keir Fraser]

On 27/03/2009 15:59, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:

>> Could you try editing xen/arch/x86/boot/reloc.c and delete all lines from
>> the function reloc() in that file except for the last line 'return mbi;'.
>> That code is new since 3.3 and one possible cause of your problem.
> 
> Fails to compile:

Sorry. Change the one remaining line in reloc() to 'return mbi_old;'.

 -- Keir

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 4:09 PM, Cui, Dexuan <dexuan.cui@intel.com> wrote:
> 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

iommu_inclusive_mapping=1 fixed the problem.

There is a newer bios for my board, I will try updating it.

Andy

Re: Unstable fail to load dom0

[Andrew Lyon]

On Fri, Mar 27, 2009 at 4:29 PM, Andrew Lyon <andrew.lyon@gmail.com> wrote:
> On Fri, Mar 27, 2009 at 4:09 PM, Cui, Dexuan <dexuan.cui@intel.com> wrote:
>> 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
>
> iommu_inclusive_mapping=1 fixed the problem.
>
> There is a newer bios for my board, I will try updating it.
>
> Andy
>

Same problem even with the latest bios, so I will use iommu_inclusive_mapping=1

Thanks
Andy

Re: Unstable fail to load dom0

[Andrew Lyon]

Hi,

Can anybody tell me what bug it is that makes it necessary to set
iommu_inclusive_mapping=1 in order to run Xen 3.4 on my Supermicro
X7DWA-N ?

Without it the system hangs immediately after printing "*** LOADING
DOMAIN 0 ***", with the setting in place it seems to work ok but I
would like to report this bug to Supermicro so I need to give them a
good description about what is wrong.

Perhaps it is related to this error I get:

(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff53000
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Read: 0:1e.0 addr bfc54000
REASON 6 iommu->reg = ffff828bfff53000
(XEN) print_vtd_entries: iommu = ffff83043fde1db0 bdf = 0:1e:0 gmfn = bfc54
(XEN)     root_entry = ffff83043fd7a000
(XEN)     root_entry[0] = 43214c001
(XEN)     context = ffff83043214c000
(XEN)     context[f0] = 102_43fd5f001
(XEN)     l4 = ffff83043fd5f000
(XEN)     l4_index = 0
(XEN)     l4[0] = 43fd5e003
(XEN)     l3 = ffff83043fd5e000
(XEN)     l3_index = 2
(XEN)     l3[2] = 433f5b003
(XEN)     l2 = ffff830433f5b000
(XEN)     l2_index = 1fe
(XEN)     l2[1fe] = 433d5c003
(XEN)     l1 = ffff830433d5c000
(XEN)     l1_index = 54
(XEN)     l1[54] = 0
(XEN)     l1[54] not present


Andy

On Fri, Mar 27, 2009 at 5:09 PM, Cui, Dexuan <dexuan.cui@intel.com> wrote:
> 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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] 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@gmail.com> wrote:
>> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@citrix.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

RE: Unstable fail to load dom0

[Cui, Dexuan]

Your SuperMicro BIOS fails to report RMRR (please see Intel VT-d spec for details) correctly.

-- Dexuan

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Andrew Lyon
Sent: 2009年4月16日 23:26
To: Xen-devel
Subject: Re: [Xen-devel] Unstable fail to load dom0

Hi,

Can anybody tell me what bug it is that makes it necessary to set
iommu_inclusive_mapping=1 in order to run Xen 3.4 on my Supermicro
X7DWA-N ?

Without it the system hangs immediately after printing "*** LOADING
DOMAIN 0 ***", with the setting in place it seems to work ok but I
would like to report this bug to Supermicro so I need to give them a
good description about what is wrong.

Perhaps it is related to this error I get:

(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff53000
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Read: 0:1e.0 addr bfc54000
REASON 6 iommu->reg = ffff828bfff53000
(XEN) print_vtd_entries: iommu = ffff83043fde1db0 bdf = 0:1e:0 gmfn = bfc54
(XEN)     root_entry = ffff83043fd7a000
(XEN)     root_entry[0] = 43214c001
(XEN)     context = ffff83043214c000
(XEN)     context[f0] = 102_43fd5f001
(XEN)     l4 = ffff83043fd5f000
(XEN)     l4_index = 0
(XEN)     l4[0] = 43fd5e003
(XEN)     l3 = ffff83043fd5e000
(XEN)     l3_index = 2
(XEN)     l3[2] = 433f5b003
(XEN)     l2 = ffff830433f5b000
(XEN)     l2_index = 1fe
(XEN)     l2[1fe] = 433d5c003
(XEN)     l1 = ffff830433d5c000
(XEN)     l1_index = 54
(XEN)     l1[54] = 0
(XEN)     l1[54] not present


Andy

On Fri, Mar 27, 2009 at 5:09 PM, Cui, Dexuan <dexuan.cui@intel.com> wrote:
> 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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] 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@gmail.com> wrote:
>> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell <Ian.Campbell@citrix.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

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

RE: Unstable fail to load dom0

[Cui, Dexuan]

[-- Attachment #1: Type: text/plain, Size: 4712 bytes --]

Hi Andy,
Could you please check if your BIOS vendor (e.g., the Suppermicro website) has released a new BIOS update?
I guess there may be a new BIOS update available.

BTW, for the xen parameter iommu_inclusive_mapping, you could see http://xenbits.xensource.com/xen-unstable.hg?rev/5dee49f3a86e.

Thanks,
-- Dexuan

Cui, Dexuan wrote:
> Your SuperMicro BIOS fails to report RMRR (please see Intel VT-d spec
> for details) correctly. 
> 
> -- Dexuan
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Andrew
> Lyon Sent: 2009年4月16日 23:26 
> To: Xen-devel
> Subject: Re: [Xen-devel] Unstable fail to load dom0
> 
> Hi,
> 
> Can anybody tell me what bug it is that makes it necessary to set
> iommu_inclusive_mapping=1 in order to run Xen 3.4 on my Supermicro
> X7DWA-N ?
> 
> Without it the system hangs immediately after printing "*** LOADING
> DOMAIN 0 ***", with the setting in place it seems to work ok but I
> would like to report this bug to Supermicro so I need to give them a
> good description about what is wrong.
> 
> Perhaps it is related to this error I get:
> 
> (XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg =
> ffff828bfff53000 (XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary
> Pending Fault (XEN) [VT-D]iommu.c:676: iommu_fault:DMA Read: 0:1e.0
> addr bfc54000 
> REASON 6 iommu->reg = ffff828bfff53000
> (XEN) print_vtd_entries: iommu = ffff83043fde1db0 bdf = 0:1e:0 gmfn =
> bfc54 (XEN)     root_entry = ffff83043fd7a000
> (XEN)     root_entry[0] = 43214c001
> (XEN)     context = ffff83043214c000
> (XEN)     context[f0] = 102_43fd5f001
> (XEN)     l4 = ffff83043fd5f000
> (XEN)     l4_index = 0
> (XEN)     l4[0] = 43fd5e003
> (XEN)     l3 = ffff83043fd5e000
> (XEN)     l3_index = 2
> (XEN)     l3[2] = 433f5b003
> (XEN)     l2 = ffff830433f5b000
> (XEN)     l2_index = 1fe
> (XEN)     l2[1fe] = 433d5c003
> (XEN)     l1 = ffff830433d5c000
> (XEN)     l1_index = 54
> (XEN)     l1[54] = 0
> (XEN)     l1[54] not present
> 
> 
> Andy
> 
> On Fri, Mar 27, 2009 at 5:09 PM, Cui, Dexuan <dexuan.cui@intel.com>
> wrote: 
>> 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@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] 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@gmail.com>
>> wrote: 
>>> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell
>>> <Ian.Campbell@citrix.com> 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
>> 
>> _______________________________________________




[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Unstable fail to load dom0

[Andrew Lyon]

2009/4/17 Cui, Dexuan <dexuan.cui@intel.com>:
> Hi Andy,
> Could you please check if your BIOS vendor (e.g., the Suppermicro website) has released a new BIOS update?
> I guess there may be a new BIOS update available.
>

I've already updated the bios to the latest version (1.2) but it did
not fix the problem.


Andy

> BTW, for the xen parameter iommu_inclusive_mapping, you could see http://xenbits.xensource.com/xen-unstable.hg?rev/5dee49f3a86e.
>
> Thanks,
> -- Dexuan
>
> Cui, Dexuan wrote:
>> Your SuperMicro BIOS fails to report RMRR (please see Intel VT-d spec
>> for details) correctly.
>>
>> -- Dexuan
>>
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Andrew
>> Lyon Sent: 2009年4月16日 23:26
>> To: Xen-devel
>> Subject: Re: [Xen-devel] Unstable fail to load dom0
>>
>> Hi,
>>
>> Can anybody tell me what bug it is that makes it necessary to set
>> iommu_inclusive_mapping=1 in order to run Xen 3.4 on my Supermicro
>> X7DWA-N ?
>>
>> Without it the system hangs immediately after printing "*** LOADING
>> DOMAIN 0 ***", with the setting in place it seems to work ok but I
>> would like to report this bug to Supermicro so I need to give them a
>> good description about what is wrong.
>>
>> Perhaps it is related to this error I get:
>>
>> (XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg =
>> ffff828bfff53000 (XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary
>> Pending Fault (XEN) [VT-D]iommu.c:676: iommu_fault:DMA Read: 0:1e.0
>> addr bfc54000
>> REASON 6 iommu->reg = ffff828bfff53000
>> (XEN) print_vtd_entries: iommu = ffff83043fde1db0 bdf = 0:1e:0 gmfn =
>> bfc54 (XEN)     root_entry = ffff83043fd7a000
>> (XEN)     root_entry[0] = 43214c001
>> (XEN)     context = ffff83043214c000
>> (XEN)     context[f0] = 102_43fd5f001
>> (XEN)     l4 = ffff83043fd5f000
>> (XEN)     l4_index = 0
>> (XEN)     l4[0] = 43fd5e003
>> (XEN)     l3 = ffff83043fd5e000
>> (XEN)     l3_index = 2
>> (XEN)     l3[2] = 433f5b003
>> (XEN)     l2 = ffff830433f5b000
>> (XEN)     l2_index = 1fe
>> (XEN)     l2[1fe] = 433d5c003
>> (XEN)     l1 = ffff830433d5c000
>> (XEN)     l1_index = 54
>> (XEN)     l1[54] = 0
>> (XEN)     l1[54] not present
>>
>>
>> Andy
>>
>> On Fri, Mar 27, 2009 at 5:09 PM, Cui, Dexuan <dexuan.cui@intel.com>
>> wrote:
>>> 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@lists.xensource.com
>>> [mailto:xen-devel-bounces@lists.xensource.com] 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@gmail.com>
>>> wrote:
>>>> On Fri, Mar 27, 2009 at 2:21 PM, Ian Campbell
>>>> <Ian.Campbell@citrix.com> 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
>>>
>>> _______________________________________________
>
>
>
>