From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc - A. Dahlhaus" Subject: Re: Vt-d not working with 3.4.1 Date: Wed, 19 Aug 2009 14:45:54 +0200 Message-ID: <4A8BF402.7020400@wol.de> References: <20090819092654.GN19938@edu.joroinen.fi> <20090819102014.GO19938@edu.joroinen.fi> <4A8BDE6E.6060804@asiasoftsea.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A8BDE6E.6060804@asiasoftsea.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: enming.teo@asiasoftsea.net Cc: xen-devel@lists.xensource.com, weidong.han@intel.com, "'Bonenkamp, Ralf'" List-Id: xen-devel@lists.xenproject.org Mr. Teo En Ming (Zhang Enming) schrieb: > 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: > > CONFIG_HAVE_KERNEL_BZIP2=y > CONFIG_KERNEL_BZIP2=y > CONFIG_RD_BZIP2=y > CONFIG_DECOMPRESS_BZIP2=y > > 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. > The bzImage has nothing to do with bzip2 compression and the current dom0 loader can only decode that CONFIG_KERNEL_GZIP based image. Please change your config to use CONFIG_KERNEL_GZIP instead of CONFIG_KERNEL_BZIP2. Marc