This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Vt-d not working with 3.4.1

To: enming.teo@xxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Vt-d not working with 3.4.1
From: "Mr. Teo En Ming (Zhang Enming)" <enming.teo@xxxxxxxxxxxxxxx>
Date: Wed, 19 Aug 2009 19:39:13 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, weidong.han@xxxxxxxxx, "'Bonenkamp, Ralf'" <ralf.bonenkamp@xxxxxxxx>
Delivery-date: Wed, 19 Aug 2009 04:39:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8BDE6E.6060804@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20090819092654.GN19938@xxxxxxxxxxxxxxx> <FA2BB24021774A8B894CE6721837D720@ASOITIS16> <20090819102014.GO19938@xxxxxxxxxxxxxxx> <4A8BDE6E.6060804@xxxxxxxxxxxxxxx>
Reply-to: enming.teo@xxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3

The specific details for the X server crash when booting Xen 3.4.1 dom 0 pvops kernel are as follows:

[drm] failed to load kernel module "nouveau"
(EE) [drm] drmOpen failed.
(EE) NOUVEAU(0): [drm] error opening the drm
(!!) NOUVEAU(0): Failing back to NoAccel mode

0: /usr/bin/X(xorg_backtrace+0x26) [0x4e89b6]
1: /usr/bin/X(xf86SigHandler+0x6f) [0x47d63f]
2: /lib64/libc.so.6 [0x3cb4633370]
3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f1914133e15]
4: /usr/lib64/xorg/modules//libint10.so [0x7f191413a3d0]
5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f1914146e81]
6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55) [0x7f1914135585]
7: /usr/lib64/xorg/modules/drivers//nouveau_drv.so [0x7f1914bff194]
8: /usr/bin/X(InitOutput+0x507) [0x467377]
9: /usr/bin/X(main+0x1fe) [0x42cf1e]
10: /lib64/libc.so.6(__libc_start_main+0xfd) [0x3cb461ea2d]
11: /usr/bin/X [0x42c559]

Fatal server error:
Caught signal 11.  Server aborting

Do I have to update the X server and/or the C library?

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) 
BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore

On 08/19/2009 07:13 PM, Mr. Teo En Ming (Zhang Enming) wrote:
Dear Pasi,

I suspect that there may be some problems with the Xen 3.4.1 changeset of 6 August 2009.

The bzImage kernel image that I compiled is not a bzip2 file, hence I cannot bzcat it. If I tried to do so, it will complain that it is not a bzip2 file.

I did specify the following in my kernel configuration:


When I do a "xm dmesg" command, I see the following output:

(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled

So can I confirm that I have VT-d support enabled?

I have checked. Both bzImage and vmlinux.bin inside arch/x86/boot are NOT ELF images.

Only vmlinux and vmlinux.bin inside arch/x86/boot/compressed are ELF64 images.

However, vmlinux inside compressed cannot boot successfully.

Only vmlinux.bin inside compressed can boot successfully, and this is what I am using now.

Regarding X server (GUI) unable to start, I have a backtrace inside /var/log/Xorg.0.log.

It complains about Fatal Server error:
Caught signal 11. Server aborting.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>