[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Vt-d not working with 3.4.1
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.
--
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 06:20 PM, Pasi Kärkkäinen wrote:
On Wed, Aug 19, 2009 at 05:45:53PM +0800, Teo En Ming (Zhang Enming) wrote:
Dear Pasi,
I did a "readelf bzImage" command and it is not an ELF image. I even tried
to do a readelf command on the default kernel (without Xen) that ships with
Fedora 11 and it says not an ELF image too.
Strange. Default installing Fedora 11 kernel not ELF image?
Maybe you need to do "bzcat kernel> kernel.elf&& readelf kernel.elf".
When configuring the pv-ops dom 0 kernel, I always select bzip2 compression.
I also carried out the readelf command on vmlinux and vmlinux.bin in the
arch/x86/boot/compressed directory after compiling the kernel. Both files
reported as ELF 64-bit executable but using vmlinux will NOT boot. Only
using vmlinux.bin will boot.
I was talking about the "vmlinux" from the top level directory, not from
arch/x86/boot/compressed.
Here is my grub.conf from my F11 dom0:
title Fedora Xen pv_ops dom0-test (2.6.31-rc6)
root (hd0,0)
kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.31-rc6 ro root=/dev/mapper/vg_dom0test-lv01
module /initrd-2.6.31-rc6.img
Where "vmlinuz-2.6.31-rc6" is arch/x86/boot/bzImage.
-- Pasi
Regards,
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
-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
Sent: Wednesday, August 19, 2009 5:27 PM
To: Teo En Ming (Zhang Enming)
Cc: weidong.han@xxxxxxxxx; 'Bonenkamp, Ralf'; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Vt-d not working with 3.4.1
On Wed, Aug 19, 2009 at 05:10:47PM +0800, Teo En Ming (Zhang Enming) wrote:
Hi,
My hardware configuration is as follows:
Intel Desktop Board DQ45CB
BIOS Flashed from version 0063 to 0093
Intel Pentium Dual Core E6300
PCI Express x16 Graphics card NVIDIA chipset
8 GB DDR2-800
My software configuration is as follows:
Fedora 11 64-bit host operating system
Jeremy's pv-ops dom0 kernel 2.6.30 rc3 and 2.6.31 rc6
Xen 3.4.1 testing
When I tried to download and compile Jeremy's pv-ops dom0 kernel, bzImage
kernel image is compiled successfully for both 2.6.30 rc3 and 2.6.31 rc6.
However, when I tried to boot using bzImage kernel image, it complains of
a
kernel panic on CPU0.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_init: not an ELF binary
I googled around and saw a posting saying to use vmlinux kernel image and
not the bzImage kernel image.
I'm using arch/x86/boot/bzImage from pv_ops dom0 kernel tree as dom0 kernel,
and it works without problems.
Are you using LZMA compression for the kernel? Maybe that's the problem..
So I tried to use vmlinux in arch/x86/boot/compressed to boot but it did
not
work.
Earlier when Xen didn't support bzImage yet, I used "vmlinux" from the top
directory of kernel tree. It's huge, but you can gzip it to make it a bit
smaller.
Xen 3.4.x supports bzImage dom0 kernels.
Not disheartened, I proceeded to try vmlinux.bin as my kernel image.
Now I can successfully boot up the Xen Dom 0 pv-ops kernel, I can see
Domain
0 using "xm list" and I can see the Ethernet bridge created and I can also
surf the internet using a text based browser.
However, I cannot start X server. It crashed. The system complains about
some libraries.
Any idea what goes wrong?
Read "dmesg" and X log.
-- Pasi
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.61/2312 - Release Date: 08/18/09
18:05:00
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.61/2312 - Release Date: 08/18/09
18:05:00
_______________________________________________
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
|
