[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 went into arch/x86/boot:- [root@fedora11-x86-64-host ~]# cd /usr/src/2.6.30-rc3-xen/arch/x86/boot/ [root@fedora11-x86-64-host boot]# file bzImagebzImage: Linux kernel x86 boot executable bzImage, version 2.6.30-rc3-enming.teo-tip (root, RO-rootFS, swap_dev 0x2, Normal VGA [root@fedora11-x86-64-host boot]# file vmlinux.bin vmlinux.bin: data If I go into arch/x86/boot/compressed:- [root@fedora11-x86-64-host compressed]# file vmlinuxvmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped [root@fedora11-x86-64-host compressed]# file vmlinux.binvmlinux.bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped If I try to boot with vmlinux inside compressed (not stripped), I get the following error: (XEN) elf_xen_note_check: ERROR: Not a Xen-ELF image: No ELF notes or '__xen_guest' section found. Panic on CPU 0: Could not set up DOM0 guest OSI can only boot Xen Dom 0 successfully with vmlinux.bin inside compressed directory (stripped). So in summary,I cannot boot with bzImage and vmlinux.bin inside arch/x86/boot. I also cannot boot with vmlinux inside arch/x86/boot/compressed. I can only boot Xen Dom 0 successfully with vmlinux.bin inside arch/x86/boot/compressed. Hence I am wondering if there are any problems or bugs with the Xen 3.4.1 changeset of 6 August 2009. -- 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 08:32 PM, Pasi Kärkkäinen wrote: On Wed, Aug 19, 2009 at 07:13:50PM +0800, 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.What does "file<kernel>" say?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.Please run "file bzImage" and "file vmlinux.bin".Only vmlinux and vmlinux.bin inside arch/x86/boot/compressed are ELF64 images. However, vmlinux inside compressed cannot boot successfully.What's the error with that?Only vmlinux.bin inside compressed can boot successfully, and this is what I am using now.Well good that something works..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.Can you pastebin the backtrace? Or the whole x.org log. -- Pasi _______________________________________________ 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
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |