Suse10.1 under FC6

[Lee Hornby]

Hello

Has anybody managed to get suse10.1 to run as an pae FC6 guest.

Any pointers/help greatly appreciated.

I get the following after xm create

Using config file "suse-install".
Error: (22, 'Invalid argument')

Config in question

ramdisk = "/root/xenprep/suse/usr/sbin/suse-xen-ramdisk"
kernel = "/root/xenprep/suse/boot/vmlinuz-2.6.16.21-0.25-xen"
name = "ramdisk"
memory= 512

XM log

[2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
(XendDomainInfo:1253) XendDomainInfo.construct: None
[2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
(XendDomainInfo:1285) XendDomainInfo.initDomain: 40 1.0
[2006-12-02 16:32:56 xend 2947] INFO (image:214) configuring linux guest
[2006-12-02 16:32:56 xend 2947] DEBUG (balloon:127) Balloon: 1048960 KiB
free; need 524288; done.
[2006-12-02 16:32:56 xend 2947] INFO (image:138) buildDomain os=linux
dom=40 vcpus=1
[2006-12-02 16:32:56 xend 2947] DEBUG (image:193) dom            = 40
[2006-12-02 16:32:56 xend 2947] DEBUG (image:194) image
= /root/xenprep/suse/boot/vmlinuz-2.6.16.21-0.25-xen
[2006-12-02 16:32:56 xend 2947] DEBUG (image:195) store_evtchn   = 1
[2006-12-02 16:32:56 xend 2947] DEBUG (image:196) console_evtchn = 2
[2006-12-02 16:32:56 xend 2947] DEBUG (image:197) cmdline        =
root=/dev/ram0
[2006-12-02 16:32:56 xend 2947] DEBUG (image:198) ramdisk
= /root/xenprep/suse/usr/sbin/suse-xen-ramdisk
[2006-12-02 16:32:56 xend 2947] DEBUG (image:199) vcpus          = 1
[2006-12-02 16:32:56 xend 2947] DEBUG (image:200) features       = 
[2006-12-02 16:32:56 xend.XendDomainInfo 2947] ERROR
(XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 195, in create
    vm.initDomain()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1363, in initDomain
    raise VmError(str(exn))
VmError: (22, \047Invalid argument\047)
[2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
(XendDomainInfo:1449) XendDomainInfo.destroy: domid=40
[2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
(XendDomainInfo:1457) XendDomainInfo.destroyDomain(40)

Regards
Lee

[Daniel P. Berrange]

On Sat, Dec 02, 2006 at 04:37:05PM +0000, Lee Hornby wrote:
> Hello
>
> Has anybody managed to get suse10.1 to run as an pae FC6 guest.
>
> Any pointers/help greatly appreciated.
>
> I get the following after xm create
>
> Using config file "suse-install".
> Error: (22, 'Invalid argument')

Are you sure you got the PAE version of the SUSE Xen kernel ? The
'Invalid Argument' error message usually means you either have the
non-PAE version, or the wrong architecture (eg x86_64 on i686).

Regards,
Dan.

[Andrew Cathrow]

I've not got openSUSE installed - but I downloaded the kernel-xen and
kernel-xenpae RPM's to check the file names.
What I saw was that the pae kernels were in the kernel-xenpae rpm and
had a pae suffix.

vmlinuz-2.6.16.13-4-xenpae

The invalid argument error (helpful eh?) typically means pae /non-pae
mismatch.

Aic

On Sat, 2006-12-02 at 16:37 +0000, Lee Hornby wrote:
> Hello
>
> Has anybody managed to get suse10.1 to run as an pae FC6 guest.
>
> Any pointers/help greatly appreciated.
>
> I get the following after xm create
>
> Using config file "suse-install".
> Error: (22, 'Invalid argument')
>
> Config in question
>
> ramdisk = "/root/xenprep/suse/usr/sbin/suse-xen-ramdisk"
> kernel = "/root/xenprep/suse/boot/vmlinuz-2.6.16.21-0.25-xen"
> name = "ramdisk"
> memory= 512
>
> XM log
>
> [2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
> (XendDomainInfo:1253) XendDomainInfo.construct: None
> [2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
> (XendDomainInfo:1285) XendDomainInfo.initDomain: 40 1.0
> [2006-12-02 16:32:56 xend 2947] INFO (image:214) configuring linux guest
> [2006-12-02 16:32:56 xend 2947] DEBUG (balloon:127) Balloon: 1048960 KiB
> free; need 524288; done.
> [2006-12-02 16:32:56 xend 2947] INFO (image:138) buildDomain os=linux
> dom=40 vcpus=1
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:193) dom            = 40
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:194) image
> = /root/xenprep/suse/boot/vmlinuz-2.6.16.21-0.25-xen
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:195) store_evtchn   = 1
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:196) console_evtchn = 2
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:197) cmdline        =
> root=/dev/ram0
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:198) ramdisk
> = /root/xenprep/suse/usr/sbin/suse-xen-ramdisk
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:199) vcpus          = 1
> [2006-12-02 16:32:56 xend 2947] DEBUG (image:200) features       = 
> [2006-12-02 16:32:56 xend.XendDomainInfo 2947] ERROR
> (XendDomainInfo:202) Domain construction failed
> Traceback (most recent call last):
>   File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 195, in create
>     vm.initDomain()
>   File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 1363, in initDomain
>     raise VmError(str(exn))
> VmError: (22, \047Invalid argument\047)
> [2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
> (XendDomainInfo:1449) XendDomainInfo.destroy: domid=40
> [2006-12-02 16:32:56 xend.XendDomainInfo 2947] DEBUG
> (XendDomainInfo:1457) XendDomainInfo.destroyDomain(40)
>
> Regards
> Lee
>
> --
> Fedora-xen mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-xen

[Paul Wouters]

On Sat, 2 Dec 2006, Andrew Cathrow wrote:
> I've not got openSUSE installed - but I downloaded the kernel-xen and
> kernel-xenpae RPM's to check the file names.
> What I saw was that the pae kernels were in the kernel-xenpae rpm and
> had a pae suffix.
> vmlinuz-2.6.16.13-4-xenpae
>
> The invalid argument error (helpful eh?) typically means pae /non-pae
> mismatch.

Perhaps it is an ABI change? Eg xen 3.0.3 vs 3.0.2?

Can't you boot the redhat xen kernel on the suse OS. There can't be much
serious differences. The only catch here is that you will need to hack
the redhat initrd image if you install it on the dom0, or grab an initrd
from a guest installed redhat machine.

Paul

[Andrew Cathrow]

If we're talking about a para-virtualised machine rather than hardware
virtualisation then you have to watch out for PAE and also 32/64 bit.

The FC6 xen kernel is PAE, which means that the guest kernel must also
be pae, you can't mix them. You'd see the same thing if you tried to run
the FC5 domU kernel on FC6
Also you can't run a 64bit kernel on a 32bit host.

Given the file names I saw I'd suspect that the issue is that you've
picked SUSE's non-pae kernel.

Aic

On Sat, 2006-12-02 at 23:29 +0100, Paul Wouters wrote:
> On Sat, 2 Dec 2006, Andrew Cathrow wrote:
> > I've not got openSUSE installed - but I downloaded the kernel-xen and
> > kernel-xenpae RPM's to check the file names.
> > What I saw was that the pae kernels were in the kernel-xenpae rpm and
> > had a pae suffix.
> > vmlinuz-2.6.16.13-4-xenpae
> >
> > The invalid argument error (helpful eh?) typically means pae /non-pae
> > mismatch.
>
> Perhaps it is an ABI change? Eg xen 3.0.3 vs 3.0.2?
>
> Can't you boot the redhat xen kernel on the suse OS. There can't be much
> serious differences. The only catch here is that you will need to hack
> the redhat initrd image if you install it on the dom0, or grab an initrd
> from a guest installed redhat machine.
>
> Paul

[Lee Hornby]

Thanks All

It was indeed the wrong kernel!

vmlinuz-2.6.16.21-0.25-xenpae worked (well started anyway).
Suspect I have more fun to come yet.

Although I did google the kernel RPM I was using and one the RMPfinders
had notes saying it was ok for both VT and pae.

Regards
Lee

On Sat, 2006-12-02 at 17:46 -0500, Andrew Cathrow wrote:
> If we're talking about a para-virtualised machine rather than hardware
> virtualisation then you have to watch out for PAE and also 32/64 bit.
>
> The FC6 xen kernel is PAE, which means that the guest kernel must also
> be pae, you can't mix them. You'd see the same thing if you tried to
> run the FC5 domU kernel on FC6
> Also you can't run a 64bit kernel on a 32bit host.
>
> Given the file names I saw I'd suspect that the issue is that you've
> picked SUSE's non-pae kernel.
>
> Aic
>
> On Sat, 2006-12-02 at 23:29 +0100, Paul Wouters wrote:
> > On Sat, 2 Dec 2006, Andrew Cathrow wrote:
> > > I've not got openSUSE installed - but I downloaded the kernel-xen and
> > > kernel-xenpae RPM's to check the file names.
> > > What I saw was that the pae kernels were in the kernel-xenpae rpm and
> > > had a pae suffix.
> > > vmlinuz-2.6.16.13-4-xenpae
> > >
> > > The invalid argument error (helpful eh?) typically means pae /non-pae
> > > mismatch.
> >
> > Perhaps it is an ABI change? Eg xen 3.0.3 vs 3.0.2?
> >
> > Can't you boot the redhat xen kernel on the suse OS. There can't be much
> > serious differences. The only catch here is that you will need to hack
> > the redhat initrd image if you install it on the dom0, or grab an initrd
> > from a guest installed redhat machine.
> >
> > Paul
>
> --
>
> Andrew Cathrow
> Red Hat, Inc.
>
> [phone] - Mobile
> [phone] - Home Office
>
> [e-mail]