Re: Vt-d not working with 3.4.1

["Mr. Teo En Ming (Zhang Enming)" <enming.teo@asiasoftsea.net>]

Dear Marc,

I am aware that bzImage is not related to bzip2 compression at all. In 
fact bzImage stands for big zImage.

http://en.wikipedia.org/wiki/Vmlinux

In the past, I was able to use bzip2 for Xen kernel in OpenSUSE 11.1 
successfully. Why is it I am only able to use gzip now?

-- 
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@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore



On 08/19/2009 08:45 PM, Marc - A. Dahlhaus wrote:
> 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
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel