any ideas ? (did not get response on xen-users list) /Jd --------------------------------- Access over 1 million songs - Yahoo! Music Unlimited. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2006-Nov-09 18:55 UTC
Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3
Do you have /var/log/xen/xend-debug.log? That may contain something useful. -- Keir On 9/11/06 6:47 pm, "jdsw" <jdsw2002@yahoo.com> wrote:> any ideas ? (did not get response on xen-users list) > /Jd > > > > > Access over 1 million songs - Yahoo! Music Unlimited. > <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com > /unlimited/> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor
2006-Nov-09 18:59 UTC
Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3
On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:> Hi > I have the following file, which is not working on 3.0.3. I am on a HVM > capable machine with xen 3.0.3 installed. > It fails with > > Using config file "/etc/xen/T1". > Error: (22, ''Invalid argument'') > > -------- > ramdisk = ''/var/cache/xenman/anaconda_install/initrd.default'' > kernel = ''/var/cache/xenman/anaconda_install/vmlinuz.default'' > #vif = '''' > name = ''T1'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > memory = 256 > disk = [''file:/mnt/images/dom_disks/T1.disk.xm,hda,w''] > ----- > I tried it with vif = "" and vif = [ ''''] (similar to xmexample1) > > The xend log file is attached. > > Any ideas. > a. I am assuming that on HVM capable machine, u can still run > paravirtualized domUsYes you can.> b. Where can I set of changes in 3.0.3 ? (I remember reading about cdrom > directive being changed...)The example file in the 3.0.3 release should show you what''s current: tools/examples/xmexample.hvm shows you the new CD-ROM format, for example. I don''t think this is your problem though. I suspect that you are using an old version of libxenctrl. This library and your hypervisor need to be matched, otherwise you will get weird errors like this. If that''s not it, please send "xm dmesg" and /var/log/xen/xend-debug.log. HTH, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel P. Berrange
2006-Nov-09 19:00 UTC
Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3
On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:> any ideas ? (did not get response on xen-users list) > > --------------------------------- > Access over 1 million songs - Yahoo! Music Unlimited. > Date: Wed, 8 Nov 2006 07:43:47 -0800 (PST) > From: jdsw <jdsw2002@yahoo.com> > Subject: 3.0.2 domu files not working on 3.0.3 > To: XenUsers <xen-users@lists.xensource.com> > > Hi > I have the following file, which is not working on 3.0.3. I am on a HVM capable machine with xen 3.0.3 installed. > It fails with > > Using config file "/etc/xen/T1". > Error: (22, ''Invalid argument'')This typically means the kernel being used for the guest is incompatible with the hypervisor or Dom0 kernel. Common causes being PAE vs non-PAE mismatch, or wrong archtecture, or using a baremetal kernel. The xend.log or xend-debug.log may give you further details on the precise error.> > -------- > ramdisk = ''/var/cache/xenman/anaconda_install/initrd.default'' > kernel = ''/var/cache/xenman/anaconda_install/vmlinuz.default'' > #vif = '''' > name = ''T1'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > memory = 256 > disk = [''file:/mnt/images/dom_disks/T1.disk.xm,hda,w''] > ----- > I tried it with vif = "" and vif = [ ''''] (similar to xmexample1) > > The xend log file is attached. > > Any ideas. > a. I am assuming that on HVM capable machine, u can still run paravirtualized domUs > > b. Where can I set of changes in 3.0.3 ? (I remember reading about cdrom directive being changed...) >Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
My machine has PAE and xen with PAE. I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory. From the xend-debug.log it seems you may be right, these may not be PAE kernels. example site : ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/ The errors in the debug file xend-debug.log ERROR: Unrecognized image format ERROR: Error constructing guest OS ERROR: Unrecognized image format ERROR: Error constructing guest OS 1. how do I determine, if the kernel is PAE enabled or not. a. when the system is running b. when I just have the kernel files as in this case ? I tried the kernel from /boot/vmlinuz-2.6-xen (as this is supposed to work with domU and Dom0 both right ?) I used the old initrd. The error 22, Invalid argument is gone...and the domU starts but it crashes. (probably because of the mismatched initrd ?) 2. Where do I get PAE enabled Xen kernels where I can possibly kick of installation similar to bare metal ? When I tried the following... http://www.xensource.com/download/dl_303guest_rhel4.html #rpm -i kernel-xenU-2.6.9-42.0.2.EL.xs148.i686.rpm error: Failed dependencies: kernel < 2.6.13 conflicts with kudzu-1.2.34.3-1.i386 kernel < 2.6.12 conflicts with initscripts-8.31.5-1.i386 kernel < 2.6.15 conflicts with hal-0.5.7.1-2.fc5.i386 #uname -a Linux test 2.6.16.29-xen #4 SMP Sun Oct 15 13:20:46 BST 2006 i686 athlon i386 GNU/Linux What are my options ? Any pointers ? Thanks /Jd "Daniel P. Berrange" <berrange@redhat.com> wrote: On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:> any ideas ? (did not get response on xen-users list) > > --------------------------------- > Access over 1 million songs - Yahoo! Music Unlimited. > Date: Wed, 8 Nov 2006 07:43:47 -0800 (PST) > From: jdsw > Subject: 3.0.2 domu files not working on 3.0.3 > To: XenUsers > > Hi > I have the following file, which is not working on 3.0.3. I am on a HVM capable machine with xen 3.0.3 installed. > It fails with > > Using config file "/etc/xen/T1". > Error: (22, ''Invalid argument'')This typically means the kernel being used for the guest is incompatible with the hypervisor or Dom0 kernel. Common causes being PAE vs non-PAE mismatch, or wrong archtecture, or using a baremetal kernel. The xend.log or xend-debug.log may give you further details on the precise error.> > -------- > ramdisk = ''/var/cache/xenman/anaconda_install/initrd.default'' > kernel = ''/var/cache/xenman/anaconda_install/vmlinuz.default'' > #vif = '''' > name = ''T1'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > memory = 256 > disk = [''file:/mnt/images/dom_disks/T1.disk.xm,hda,w''] > ----- > I tried it with vif = "" and vif = [ ''''] (similar to xmexample1) > > The xend log file is attached. > > Any ideas. > a. I am assuming that on HVM capable machine, u can still run paravirtualized domUs > > b. Where can I set of changes in 3.0.3 ? (I remember reading about cdrom directive being changed...) >Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --------------------------------- Cheap Talk? Check out Yahoo! Messenger''s low PC-to-Phone call rates. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel P. Berrange
2006-Nov-09 22:10 UTC
Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3
On Thu, Nov 09, 2006 at 01:53:54PM -0800, jdsw wrote:> My machine has PAE and xen with PAE. > > I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory. From the xend-debug.log it seems you may be right, these may not be PAE kernels. > > example site : > ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/ > > The errors in the debug file > xend-debug.log > ERROR: Unrecognized image format > ERROR: Error constructing guest OS > ERROR: Unrecognized image format > ERROR: Error constructing guest OS > > 1. how do I determine, if the kernel is PAE enabled or not. > a. when the system is running > b. when I just have the kernel files as in this case ?For Fedora the naming of the kernel tells you. The non-PAE kernels are called kernel-xenU / kernel-xen0, while the PAE kernels are kernel-xen. FC5 was non-PAE, but FC6 is PAE. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2006-Nov-09 22:21 UTC
Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3
The error ³Unrecognized image format² means you didn¹t even get as far as checking PAE vs non-PAE, or 64-bit vs 32-bit. The image wasn¹t recognised as an Elf image at all. Perhaps you grabbed a native kernel image by mistake? A valid Xen kernel image should be Elf or gzipped Elf. You might want to confirm that (try gunzipping it, then try readelf¹ on the result). -- Keir On 9/11/06 9:53 pm, "jdsw" <jdsw2002@yahoo.com> wrote:> I got the domU kernel and ramdisk from one of the fedora mirror from under the > xen directory. From the xend-debug.log it seems you may be right, these may > not be PAE kernels. > > example site : > ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/ > > The errors in the debug file > xend-debug.log > ERROR: Unrecognized image format > ERROR: Error constructing guest OS_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir/Daniel oops. The mirror had problems so it was a wrong file. (some 404 html). Got the correct files now the error is meaningful. ERROR: Non PAE-kernel on PAE host. ERROR: Error constructing guest OS This kind of mismatch is irrelavent in HVM case, right ? i.e. I can install non-pae HVM DomUs on PAE Dom0 machines ? Also, got kernels from FC6 and the DomU is starting. :) (This is not related to this thread.. but now the installation does not detect any drivers to do either network or CDROM installation) Thanks /Jd Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3 The error “Unrecognized image format” means you didn’t even get as far as checking PAE vs non-PAE, or 64-bit vs 32-bit. The image wasn’t recognised as an Elf image at all. Perhaps you grabbed a native kernel image by mistake? A valid Xen kernel image should be Elf or gzipped Elf. You might want to confirm that (try gunzipping it, then try ‘readelf’ on the result). -- Keir On 9/11/06 9:53 pm, "jdsw" <jdsw2002@yahoo.com> wrote: I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory. From the xend-debug.log it seems you may be right, these may not be PAE kernels. example site : ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/ The errors in the debug file xend-debug.log ERROR: Unrecognized image format ERROR: Error constructing guest OS --------------------------------- Want to start your own business? Learn how on Yahoo! Small Business. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel