Xen users - Jan 2008 - vanilla kernel and xen (in general), vanilla 2.6.24 and xen

I''d like to understand one thing: 
Is there a way to put the xen stuff inside a vanilla kernel?
If yes, how?

I have seen that in 2.6.24 there''s a lot of xen stuff inside, are these
things enough to run xen or it miss'' something?


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

enough to run your system as DomU, but not enough to run this system as
Dom0.

Emre

On Jan 29, 2008 9:57 AM, zava.zava@libero.it <zava.zava@libero.it> wrote:
> I''d like to understand one thing:
> Is there a way to put the xen stuff inside a vanilla kernel?
> If yes, how?
>
> I have seen that in 2.6.24 there''s a lot of xen stuff inside, are
these
> things enough to run xen or it miss'' something?
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
Emre Erenoglu
erenoglu@gmail.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Tuesday, den 29 January hub Emre Erenoglu folgendes in die Tasten:
> enough to run your system as DomU, but not enough to run this system as
> Dom0.
So what would have to be done to accomplish it?

Thanks,

Ciao
Max
-- 
	Follow the white penguin.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Jan 29, 2008 11:40 PM, Maximilian Wilhelm <max@rfc2324.org> wrote:
> Am Tuesday, den 29 January hub Emre Erenoglu folgendes in die Tasten:
>
> > enough to run your system as DomU, but not enough to run this system
as
> > Dom0.
>
> So what would have to be done to accomplish it?
>
RedHat is leading an effort to put Dom0 support in the Linux kernel using
paravirt ops (pvops)

see this recent post to the devel list:
http://www.nabble.com/Updated-dom0-pvops-for-2.6.24-available-on-git-td15091656.html


>
> Thanks,
>
> Ciao
> Max
> --
>        Follow the white penguin.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

Emre Erenoglu wrote:
> enough to run your system as DomU, but not enough to run this system as
> Dom0.
What do I have to do to get a kernel in version 2.6.24 working as domU? 
I am not able to find the correct options. Any hints would be appreciated.

Thanks in advance.

Cheers,

Jan

-- 
Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
E-Mail: support@artfiles.de | Web: http://www.artfiles.de
Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB 81478

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Jan, just look at other PV domU example configuration files. Steps:

1) Make sure you have the necessary modules in your initrd specific to this
2.6.24 kernel. (if you need)
2) Have the kernel and the initrd somewhere on your filesystem
3) Make sure your DomU config file has the correct filenames for
kernel&initrd and the DomU disk file exists (or physical disk)
4) boot your DomU

You may need to copy the new kernel''s modules from Dom0
/lib/modules/2.6.24-x-y-z to /lib/modules folder of the DomU, chroot to DomU
filesystem rooot and do a depmod. You can do this step inside the DomU also,
after you boot into your new DomU. This step may not be necessary if there
are no drivers that are needed for your DomU.

Hope it''s clear,

Br,

Emre



On Jan 30, 2008 9:24 AM, Jan Marquardt <jm@artfiles.de> wrote:
> Hi,
>
> Emre Erenoglu wrote:
> > enough to run your system as DomU, but not enough to run this system
as
> > Dom0.
>
> What do I have to do to get a kernel in version 2.6.24 working as domU?
> I am not able to find the correct options. Any hints would be appreciated.
>
> Thanks in advance.
>
> Cheers,
>
> Jan
>
> --
> Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
> Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
> E-Mail: support@artfiles.de | Web: http://www.artfiles.de
> Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB 81478
>


-- 
Emre Erenoglu
erenoglu@gmail.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Anyone has working kernel config for 2.6.24 domU?

Peter



2008/1/30, Emre Erenoglu <erenoglu@gmail.com>:
> Hi Jan, just look at other PV domU example configuration files. Steps:
>
> 1) Make sure you have the necessary modules in your initrd specific to this
> 2.6.24 kernel. (if you need)
> 2) Have the kernel and the initrd somewhere on your filesystem
>  3) Make sure your DomU config file has the correct filenames for
> kernel&initrd and the DomU disk file exists (or physical disk)
> 4) boot your DomU
>
> You may need to copy the new kernel''s modules from Dom0
> /lib/modules/2.6.24-x-y-z to /lib/modules folder of the DomU, chroot to
DomU
> filesystem rooot and do a depmod. You can do this step inside the DomU
also,
> after you boot into your new DomU. This step may not be necessary if there
> are no drivers that are needed for your DomU.
>
> Hope it''s clear,
>
> Br,
>
> Emre
>
>
>
> On Jan 30, 2008 9:24 AM, Jan Marquardt <jm@artfiles.de> wrote:
> > Hi,
> >
> >
> > Emre Erenoglu wrote:
> > > enough to run your system as DomU, but not enough to run this
system as
> > > Dom0.
> >
> > What do I have to do to get a kernel in version 2.6.24 working as
domU?
> > I am not able to find the correct options. Any hints would be
appreciated.
> >
> > Thanks in advance.
> >
> > Cheers,
> >
> > Jan
> >
> > --
> > Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
> > Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
> > E-Mail: support@artfiles.de | Web: http://www.artfiles.de
> > Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB 81478
> >
>
>
>
> --
> Emre Erenoglu
> erenoglu@gmail.com
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

There shall be nothing special. Take a config for 2.6.18 kernel and just
change the kernel and initrd lines. as long as the build is matching the Xen
capability, PAE nonPAE etc.

Emre

On Jan 30, 2008 5:38 PM, Peter Braun <xenware@gmail.com> wrote:
> Anyone has working kernel config for 2.6.24 domU?
>
> Peter
>
>
>
> 2008/1/30, Emre Erenoglu <erenoglu@gmail.com>:
> > Hi Jan, just look at other PV domU example configuration files. Steps:
> >
> > 1) Make sure you have the necessary modules in your initrd specific to
> this
> > 2.6.24 kernel. (if you need)
> > 2) Have the kernel and the initrd somewhere on your filesystem
> >  3) Make sure your DomU config file has the correct filenames for
> > kernel&initrd and the DomU disk file exists (or physical disk)
> > 4) boot your DomU
> >
> > You may need to copy the new kernel''s modules from Dom0
> > /lib/modules/2.6.24-x-y-z to /lib/modules folder of the DomU, chroot
to
> DomU
> > filesystem rooot and do a depmod. You can do this step inside the DomU
> also,
> > after you boot into your new DomU. This step may not be necessary if
> there
> > are no drivers that are needed for your DomU.
> >
> > Hope it''s clear,
> >
> > Br,
> >
> > Emre
> >
> >
> >
> > On Jan 30, 2008 9:24 AM, Jan Marquardt <jm@artfiles.de> wrote:
> > > Hi,
> > >
> > >
> > > Emre Erenoglu wrote:
> > > > enough to run your system as DomU, but not enough to run
this system
> as
> > > > Dom0.
> > >
> > > What do I have to do to get a kernel in version 2.6.24 working as
> domU?
> > > I am not able to find the correct options. Any hints would be
> appreciated.
> > >
> > > Thanks in advance.
> > >
> > > Cheers,
> > >
> > > Jan
> > >
> > > --
> > > Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
> > > Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
> > > E-Mail: support@artfiles.de | Web: http://www.artfiles.de
> > > Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB
81478
> > >
> >
> >
> >
> > --
> > Emre Erenoglu
> > erenoglu@gmail.com
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
Emre Erenoglu
erenoglu@gmail.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Emre,

thanks for your response.

Do I understand correctly that no special option is needed in the 
configuration? I asking, because I have already tried a kernel in 
version 2.6.24, but I got the error:

Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no
loader found\n'')

Cheers

Jan


Emre Erenoglu wrote:
> Hi Jan, just look at other PV domU example configuration files. Steps:
> 
> 1) Make sure you have the necessary modules in your initrd specific to this
> 2.6.24 kernel. (if you need)
> 2) Have the kernel and the initrd somewhere on your filesystem
> 3) Make sure your DomU config file has the correct filenames for
> kernel&initrd and the DomU disk file exists (or physical disk)
> 4) boot your DomU
> 
> You may need to copy the new kernel''s modules from Dom0
> /lib/modules/2.6.24-x-y-z to /lib/modules folder of the DomU, chroot to
DomU
> filesystem rooot and do a depmod. You can do this step inside the DomU
also,
> after you boot into your new DomU. This step may not be necessary if there
> are no drivers that are needed for your DomU.
> 
> Hope it''s clear,
> 
> Br,
> 
> Emre
> 
> 
> 
> On Jan 30, 2008 9:24 AM, Jan Marquardt <jm@artfiles.de> wrote:
> 
>> Hi,
>>
>> Emre Erenoglu wrote:
>>> enough to run your system as DomU, but not enough to run this
system as
>>> Dom0.
>> What do I have to do to get a kernel in version 2.6.24 working as domU?
>> I am not able to find the correct options. Any hints would be
appreciated.
>>
>> Thanks in advance.
>>
>> Cheers,
>>
>> Jan
>>
>> --
>> Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
>> Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
>> E-Mail: support@artfiles.de | Web: http://www.artfiles.de
>> Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB 81478
>>
> 
> 
> 
-- 
Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
E-Mail: support@artfiles.de | Web: http://www.artfiles.de
Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB 81478

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Jan 31, 2008 9:48 AM, Jan Marquardt <jm@artfiles.de> wrote:
> Hi Emre,
>
> thanks for your response.
>
> Do I understand correctly that no special option is needed in the
> configuration? I asking, because I have already tried a kernel in
> version 2.6.24, but I got the error:
>
Normally not, maybe your kernel was not built with the XEN options enabled
in the kernel configuration file?

Emre


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emre Erenoglu írta:
> On Jan 31, 2008 9:48 AM, Jan Marquardt <jm@artfiles.de
> <mailto:jm@artfiles.de>> wrote:
>
>     Hi Emre,
>
>     thanks for your response.
>
>     Do I understand correctly that no special option is needed in the
>     configuration? I asking, because I have already tried a kernel in
>     version 2.6.24, but I got the error:
>
>
> Normally not, maybe your kernel was not built with the XEN options
> enabled in the kernel configuration file?
>
> Emre
>  
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
Hi everybody,

After some fighting with the hvc console and xvd disks I figured out how
to write such a config file.
Here is my quite minimalistic example:

name = ''whatever''
memory = ''1024''
disk = [ ''phy:/dev/xenU/fsys,0x20201,w'', 
''phy:/dev/xenU/swap,0x20202,w'' ]
vif = [ ''mac=00:16:3e:00:00:ff, bridge=lanbr'' ]
kernel = ''/boot/vmlinuz-2.6.24-1-xen-686''
ramdisk = ''/boot/initrd.img-2.6.24-1-xen-686''
#extra = ''earlyprintk=xen console=hvc root=/dev/sda1 ro''
extra = ''console=hvc root=/dev/xvda1 ro''


As you can see I use lvm for domU storage. The Dom0 is runing Debian
etch with xen kernel from the distro, and xen-3.2 backported from sid
(kernel 2.6.24 from the same source).
For me the tricky part was to figure out the right console=hvc and the
right block major/minor numbers for my (xvda1 ad xvda2) partitions
(because the Dom0 has no xvd devices it has no idea what numbers to
report to the DomU if you just put xvda1 and xvda2 instead of numbers).

Best regards,

Geza

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> There shall be nothing special. Take a config for 2.6.18 kernel and just
> change the kernel and initrd lines. as long as the build is matching the
> Xen capability, PAE nonPAE etc.
The Xen code that''s in 2.6.24 from kernel.org is rather different to
that in
2.6.18 XenLinux from XenSource.  So just reusing the same config file will 
probably not work on its own, sorry :-(

Cheers,
Mark
> Emre
>
> On Jan 30, 2008 5:38 PM, Peter Braun <xenware@gmail.com> wrote:
> > Anyone has working kernel config for 2.6.24 domU?
> >
> > Peter
> >
> > 2008/1/30, Emre Erenoglu <erenoglu@gmail.com>:
> > > Hi Jan, just look at other PV domU example configuration files.
Steps:
> > >
> > > 1) Make sure you have the necessary modules in your initrd
specific to
> >
> > this
> >
> > > 2.6.24 kernel. (if you need)
> > > 2) Have the kernel and the initrd somewhere on your filesystem
> > >  3) Make sure your DomU config file has the correct filenames for
> > > kernel&initrd and the DomU disk file exists (or physical
disk)
> > > 4) boot your DomU
> > >
> > > You may need to copy the new kernel''s modules from Dom0
> > > /lib/modules/2.6.24-x-y-z to /lib/modules folder of the DomU,
chroot to
> >
> > DomU
> >
> > > filesystem rooot and do a depmod. You can do this step inside the
DomU
> >
> > also,
> >
> > > after you boot into your new DomU. This step may not be necessary
if
> >
> > there
> >
> > > are no drivers that are needed for your DomU.
> > >
> > > Hope it''s clear,
> > >
> > > Br,
> > >
> > > Emre
> > >
> > > On Jan 30, 2008 9:24 AM, Jan Marquardt <jm@artfiles.de>
wrote:
> > > > Hi,
> > > >
> > > > Emre Erenoglu wrote:
> > > > > enough to run your system as DomU, but not enough to
run this
> > > > > system
> >
> > as
> >
> > > > > Dom0.
> > > >
> > > > What do I have to do to get a kernel in version 2.6.24
working as
> >
> > domU?
> >
> > > > I am not able to find the correct options. Any hints would
be
> >
> > appreciated.
> >
> > > > Thanks in advance.
> > > >
> > > > Cheers,
> > > >
> > > > Jan
> > > >
> > > > --
> > > > Artfiles New Media GmbH | Spaldingstr. 160 b | 20097 Hamburg
> > > > Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
> > > > E-Mail: support@artfiles.de | Web: http://www.artfiles.de
> > > > Geschäftsführer Carsten Bals | Handelsregister Hamburg - HRB
81478
> > >
> > > --
> > > Emre Erenoglu
> > > erenoglu@gmail.com
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Mark,


Mark Williamson schreef:
>> There shall be nothing special. Take a config for 2.6.18 kernel and
just
>> change the kernel and initrd lines. as long as the build is matching
the
>> Xen capability, PAE nonPAE etc.
> 
> The Xen code that''s in 2.6.24 from kernel.org is rather different
to that in
> 2.6.18 XenLinux from XenSource.  So just reusing the same config file will 
> probably not work on its own, sorry :-(


Can you comment on that a bit more? Are there now like 2 different
branches of kernel Xen for a domain user?


Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHpTbVYH1+F2Rqwn0RCjzrAJ9IvGWP5yBBzTfEOT5L2dWdRM3XYQCfYLm1
mB0DP45cx+HXFylX5WhKWIw=KBTH
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> On Jan 31, 2008 9:48 AM, Jan Marquardt <jm@artfiles.de> wrote:
> > Hi Emre,
> >
> > thanks for your response.
> >
> > Do I understand correctly that no special option is needed in the
> > configuration? I asking, because I have already tried a kernel in
> > version 2.6.24, but I got the error:
>
> Normally not, maybe your kernel was not built with the XEN options enabled
> in the kernel configuration file?
2.6.24 from kernel.org does not build with Xen support by default.  To enable 
this, you''ll need to go into make xconfig / make menuconfig and tweak
some
options...

Under "Processor type and features", there is an option for
"Paravirtualized
guest support".  Enable that.

Under "Paravirtualized guest support", enabled the "Xen guest
support" option.

I think this will automatically enable support for Xen block and network 
devices; otherwise you''ll have to enable them under the relevant menus
in the
configurator.

The kernel you build in this way will have support for the Linux paravirt-ops 
feature, and so it''ll be able to either boot natively or
paravirtualised on
one of the hypervisors you''ve selected support for (e.g. Xen).  It can
only
run as a domU under Xen and it does not have full functionality (For example, 
it *does* support SMP, paravirt net and block; it *does not* support live 
migrate, save / resume, paravirt framebuffer, memory ballooning)

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> >> There shall be nothing special. Take a config for 2.6.18 kernel
and just
> >> change the kernel and initrd lines. as long as the build is
matching the
> >> Xen capability, PAE nonPAE etc.
> >
> > The Xen code that''s in 2.6.24 from kernel.org is rather
different to that
> > in 2.6.18 XenLinux from XenSource.  So just reusing the same config
file
> > will probably not work on its own, sorry :-(
>
> Can you comment on that a bit more? Are there now like 2 different
> branches of kernel Xen for a domain user?
Essentially, yes.

The XenLinux kernel which XenSource hosts and develops and that is the basis 
of the existing distro kernels is based on a source tree whose history dates 
back to the really early days of Xen.  This has full support for all the cool 
bits of functionality Xen supports and can run as dom0 or domU; however it 
can''t be booted as a "native" kernel on bare-metal and
it''s based on the
2.6.18 kernel, which is getting old.

kernel.org Linux has support for running as a Xen domU since Linux 2.6.23 was 
released.  The Xen-aware code in that is derived from that in the XenSource 
XenLinux kernel - in many places it''s a port of the same code, not a 
different implementation.  However, quite a lot of changes were required to 
make the addition of Xen support acceptable to the mainline kernel developers 
(using paravirt-ops) to the XenLinux 2.6.18 (which uses a separate Xen 
subarchitecture).  Jeremy Fitzhardinge at XenSource took on the difficult 
task of getting Xen support in mainline Linux and managed to get a basic set 
of functionality merged into 2.6.23.

The current situation is still not ideal, since the XenLinux kernel is still 
based on 2.6.18 and it''s hard work for distros to forward-port Xen
support to
whatever kernel they''re running.  Meanwhile the kernel.org port
doesn''t
support all the juicy features that XenLinux 2.6.18 supports.

A number of people - Red Hat are helping spearhead this - are working on 
turning all the juicy features of XenLinux 2.6.18 into patches on top of 
mainline Linux''s existing Xen support.  This includes support for
running as
dom0.

The end goal, I believe, is to get as much Xen support upstream as possible 
(e.g. paravirt framebuffer, live migration support, maybe dom0 support).  
Anything that''s left can be maintained by the Xen developers as a patch
on
top of mainline linux, rather than maintaining their own separate kernel.

This involves some short term pain but the end result should be that Xen 
support is available for newer kernels quicker, kernel.org Linux will come 
with more Xen functionality by default, and it may even be possible for 
distros to ship the same kernel for use as the native kernel, as dom0 and as 
domU (and for lguest, and for VMI).  Which would be awesome :-)

Does that clear things up a bit?

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Feb 03, 2008 at 03:49:06AM +0000, Mark Williamson
wrote:
> 2.6.24 from kernel.org does not build with Xen support by default.  To
enable
> this, you''ll need to go into make xconfig / make menuconfig and
tweak some
> options...
> 
> Under "Processor type and features", there is an option for
"Paravirtualized
> guest support".  Enable that.
> 
> Under "Paravirtualized guest support", enabled the "Xen
guest support" option.
> 
> I think this will automatically enable support for Xen block and network 
> devices; otherwise you''ll have to enable them under the relevant
menus in the
> configurator.
	I''m trying to boot 2.6.24 as a paravirt guest.  I''m using all
the config selections you describe.  I''ve done all this, from the day
"Xen" support landed up until 2.6.24 release.  I''ve never
gotten it to
boot, not once.  These days (2.6.24), I get it starting, but it can
never mount /dev/root.  I tried the 0x20201/xvda1 trick, but that
doesn''t help either.  I''ve often wondered - which file should
I be
using from my build?  arch/x86/boot/bzImage?  ./vmlinux?  I really would
appreciate any help - I''m currently stuck with HVM when it comes to
mainline kernel, and that''s slow.

Joel

-- 

 One look at the From:
 understanding has blossomed
 .procmailrc grows
	- Alexander Viro

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, 3 Feb 2008, Mark Williamson wrote:
> Does that clear things up a bit?
Yes, does it make me happy... no not really ;)


Stefan


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 	I''m trying to boot 2.6.24 as a paravirt guest.  I''m
using all
> the config selections you describe.  I''ve done all this, from the
day
> "Xen" support landed up until 2.6.24 release.  I''ve
never gotten it to
> boot, not once.  These days (2.6.24), I get it starting, but it can
> never mount /dev/root.  I tried the 0x20201/xvda1 trick, but that
> doesn''t help either.  I''ve often wondered - which file
should I be
> using from my build?  arch/x86/boot/bzImage?  ./vmlinux?
Use the vmlinux.  By the way, if you strip it and maybe gzip it, it comes down 
to a much less unwieldy size.

That ought to at least be loadable by the domain builder, which is a start.  
Then we could see where it crashes next :-)  Have you managed to get it this 
far?  If so, what happened?
> I really would 
> appreciate any help - I''m currently stuck with HVM when it comes
to
> mainline kernel, and that''s slow.
:-(

You might be able to get the unmodified_drivers stuff to work so that you get 
PV drivers under HVM.  I''m not sure if that supports 2.6.24 kernels yet
though...  That''d improve performance a bit once it does work.

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> > Does that clear things up a bit?
>
> Yes, does it make me happy... no not really ;)
Well, it''s not the way one would have wanted it to be.  But the end
goal is to
have full-featured XenLinux either be upstream entirely, or a patch on the 
side of upstream, which will be an improvement on the current situation.

Right now all the distros have to do extensive forward-porting work on the Xen 
patches (with varying degrees of success, from what I''ve heard), which
is
generally bad for everyone.

FWIW, Stephen Tweedie at RedHat has been working on adding dom0 support to 
mainline Linux''s pvops implementation.  He already has a pvops kernel
which
can boot either as a dom0 (and therefore as domU, too) or as a native kernel.  
Some problems still to be worked out, but this is coming along...  He has a 
public git tree somewhere too.  I can find a link if you''re interested.

Fingers crossed that this stuff keeps moving forwards quickly!

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Feb 03, 2008 at 03:59:10AM +0000, Mark Williamson
wrote:
> > >> There shall be nothing special. Take a config for 2.6.18
kernel and just
> > >> change the kernel and initrd lines. as long as the build is
matching the
> > >> Xen capability, PAE nonPAE etc.
> > >
> > > The Xen code that''s in 2.6.24 from kernel.org is rather
different to that
> > > in 2.6.18 XenLinux from XenSource.  So just reusing the same
config file
> > > will probably not work on its own, sorry :-(
> >
> > Can you comment on that a bit more? Are there now like 2 different
> > branches of kernel Xen for a domain user?
> 
> Essentially, yes.
> 
> The XenLinux kernel which XenSource hosts and develops and that is the
basis
> of the existing distro kernels is based on a source tree whose history
dates
> back to the really early days of Xen.  This has full support for all the
cool
> bits of functionality Xen supports and can run as dom0 or domU; however it 
> can''t be booted as a "native" kernel on bare-metal and
it''s based on the
> 2.6.18 kernel, which is getting old.
> 
> kernel.org Linux has support for running as a Xen domU since Linux 2.6.23
was
> released.  The Xen-aware code in that is derived from that in the XenSource
> XenLinux kernel - in many places it''s a port of the same code, not
a
> different implementation.  However, quite a lot of changes were required to
> make the addition of Xen support acceptable to the mainline kernel
developers
> (using paravirt-ops) to the XenLinux 2.6.18 (which uses a separate Xen 
> subarchitecture).  Jeremy Fitzhardinge at XenSource took on the difficult 
> task of getting Xen support in mainline Linux and managed to get a basic
set
> of functionality merged into 2.6.23.
> 
> The current situation is still not ideal, since the XenLinux kernel is
still
> based on 2.6.18 and it''s hard work for distros to forward-port Xen
support to
> whatever kernel they''re running.  Meanwhile the kernel.org port
doesn''t
> support all the juicy features that XenLinux 2.6.18 supports.
> 
> A number of people - Red Hat are helping spearhead this - are working on 
> turning all the juicy features of XenLinux 2.6.18 into patches on top of 
> mainline Linux''s existing Xen support.  This includes support for
running as
> dom0.
> 
> The end goal, I believe, is to get as much Xen support upstream as possible
> (e.g. paravirt framebuffer, live migration support, maybe dom0 support).  
> Anything that''s left can be maintained by the Xen developers as a
patch on
> top of mainline linux, rather than maintaining their own separate kernel.
> 
> This involves some short term pain but the end result should be that Xen 
> support is available for newer kernels quicker, kernel.org Linux will come 
> with more Xen functionality by default, and it may even be possible for 
> distros to ship the same kernel for use as the native kernel, as dom0 and
as
> domU (and for lguest, and for VMI).  Which would be awesome :-)
> 
> Does that clear things up a bit?
> 
Upcoming Fedora 9 (from RedHat) should have "full" Xen support in
2.6.24+ kernel,
in a form that it can be sent/submitted upstream for inclusion in kernel.org
vanilla
kernel.

RedHat people are working on this. There have been some mails about the
progress on xen-devel list. 

-- Pasi

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Feb 03, 2008 at 03:08:13PM +0000, Mark Williamson
wrote:
> > 	I''m trying to boot 2.6.24 as a paravirt guest.  I''m
using all
> > the config selections you describe.  I''ve done all this, from
the day
> > "Xen" support landed up until 2.6.24 release.  I''ve
never gotten it to
> > boot, not once.  These days (2.6.24), I get it starting, but it can
> > never mount /dev/root.  I tried the 0x20201/xvda1 trick, but that
> > doesn''t help either.  I''ve often wondered - which
file should I be
> > using from my build?  arch/x86/boot/bzImage?  ./vmlinux?
> 
> Use the vmlinux.  By the way, if you strip it and maybe gzip it, it comes
down
> to a much less unwieldy size.
> 
> That ought to at least be loadable by the domain builder, which is a start.
> Then we could see where it crashes next :-)  Have you managed to get it
this
> far?  If so, what happened?
	Haha, with 2.6.24 I don''t even get any boot messages past pygrub
now.  Someone else is telling me that to use a pv_ops guest I need some
special xen tree?  Is that true? 

Joel

-- 

"Senator let''s be sincere,
 As much as you can."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> > > 	I''m trying to boot 2.6.24 as a paravirt guest. 
I''m using all
> > > the config selections you describe.  I''ve done all this,
from the day
> > > "Xen" support landed up until 2.6.24 release. 
I''ve never gotten it to
> > > boot, not once.  These days (2.6.24), I get it starting, but it
can
> > > never mount /dev/root.  I tried the 0x20201/xvda1 trick, but that
> > > doesn''t help either.  I''ve often wondered -
which file should I be
> > > using from my build?  arch/x86/boot/bzImage?  ./vmlinux?
> >
> > Use the vmlinux.  By the way, if you strip it and maybe gzip it, it
comes
> > down to a much less unwieldy size.
> >
> > That ought to at least be loadable by the domain builder, which is a
> > start. Then we could see where it crashes next :-)  Have you managed
to
> > get it this far?  If so, what happened?
>
> 	Haha, with 2.6.24 I don''t even get any boot messages past pygrub
> now.  Someone else is telling me that to use a pv_ops guest I need some
> special xen tree?  Is that true?
You don''t need a special Xen tree to get pvops guest support.  2.6.24
can run
as a domU using pvops, albeit slightly limited (no 64-bit guests, no 
migration or save / restore, etc).  There is a special kernel tree that 
contains dom0 pvops support, but you shouldn''t need that just yet! 
Lets get
domU working first, eh? ;-)

You need to pass the argument "console=hvc0" (e.g. in the extra=
section of
the config file) or no boot output will come out.  Note that this is 
different from the previous Xen convention of calling the console device xvc0 
or tty1 or ttyS0, etc.

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Mark,

On Thu, Feb 07, 2008 at 02:26:28AM +0000, Mark Williamson
wrote:
> You don''t need a special Xen tree to get pvops guest support. 
2.6.24 can run
> as a domU using pvops, albeit slightly limited (no 64-bit guests, no 
> migration or save / restore, etc).  There is a special kernel tree that 
> contains dom0 pvops support, but you shouldn''t need that just yet!
Lets get
> domU working first, eh? ;-)
I''m having the same problems.  Trying to get fedora 8 working as a
domU on a Debian Etch dom0using stock Debian Xen packages.  So that
means xen 3.0.3 hypervisor and Debian 2.6.18-based Xen kernel.
> You need to pass the argument "console=hvc0" (e.g. in the extra=
section of
> the config file) or no boot output will come out.  Note that this is 
> different from the previous Xen convention of calling the console device
xvc0
> or tty1 or ttyS0, etc.
It still crashes immediately before giving any output:

[2008-02-07 11:55:48 xend.XendDomainInfo 3525] DEBUG (__init__:1072) Storing VM
details: {''shadow_memory'': ''0'',
''uuid'':
''4a54f878-822d-b690-0cce-e562ae26234c'',
''on_reboot'': ''restart'',
''start_time'': ''1202385348.89'',
''on_poweroff'': ''destroy'',
''name'': ''fedora8'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''120'',
''on_crash'': ''restart'',
''image'': "(linux (ramdisk /var/lib/xen/initrd.5wFAEZ)
(kernel /var/lib/xen/vmlinuz.p36_aL) (args ''ro root=LABEL=/
console=hvc0''))", ''maxmem'':
''120''}
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] DEBUG (__init__:1072) Storing
domain details: {''console/ring-ref'':
''294508'', ''console/port'':
''2'', ''name'': ''fedora8'',
''console/limit'': ''1048576'',
''vm'':
''/vm/4a54f878-822d-b690-0cce-e562ae26234c'',
''domid'': ''42'',
''cpu/0/availability'': ''online'',
''memory/target'': ''122880'',
''store/ring-ref'': ''294509'',
''store/port'': ''1''}
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] DEBUG (__init__:1072)
XendDomainInfo.handleShutdownWatch
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] WARNING (__init__:1072) Domain
has crashed: name=fedora8 id=42.
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] ERROR (__init__:1072) VM fedora8
restarting too fast (1.342405 seconds since the last restart).  Refusing to
restart to avoid loops.
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] DEBUG (__init__:1072)
XendDomainInfo.destroy: domid=42
[2008-02-07 11:55:49 xend.XendDomainInfo 3525] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(42)

config file:

name = ''fedora8''
memory = 120
disk = [ ''phy:mapper/mainvg-domu_fedora8_root,xvda1,w'',
         ''phy:mapper/mainvg-domu_fedora8_swap,xvda2,w'' ]
vif = [ ''mac=00:16:3e:1b:b2:f8, bridge=xenbr0,
vifname=v-fedora8'' ]
bootloader = ''/usr/lib/xen-3.0.3-1/bin/pygrub''

Any ideas?

Cheers,
Andy


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Feb 07, 2008 at 02:26:28AM +0000, Mark Williamson
wrote:
> > > > 	I''m trying to boot 2.6.24 as a paravirt guest. 
I''m using all
> > > > the config selections you describe.  I''ve done all
this, from the day
> > > > "Xen" support landed up until 2.6.24 release. 
I''ve never gotten it to
> > > > boot, not once.  These days (2.6.24), I get it starting, but
it can
> > > > never mount /dev/root.  I tried the 0x20201/xvda1 trick, but
that
> > > > doesn''t help either.  I''ve often wondered
- which file should I be
> > > > using from my build?  arch/x86/boot/bzImage?  ./vmlinux?
	Ok, I have it working now!  Thanks everyone for your help!

Joel

-- 

"A narcissist is someone better looking than you are."  
         - Gore Vidal

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

For the record, I''ve started a howto guide for this here: 
http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen

Cheers,
Mark

On Sunday 03 February 2008, Joel Becker wrote:
> On Sun, Feb 03, 2008 at 03:49:06AM +0000, Mark Williamson wrote:
> > 2.6.24 from kernel.org does not build with Xen support by default.  To
> > enable this, you''ll need to go into make xconfig / make
menuconfig and
> > tweak some options...
> >
> > Under "Processor type and features", there is an option for
> > "Paravirtualized guest support".  Enable that.
> >
> > Under "Paravirtualized guest support", enabled the "Xen
guest support"
> > option.
> >
> > I think this will automatically enable support for Xen block and
network
> > devices; otherwise you''ll have to enable them under the
relevant menus in
> > the configurator.
>
> 	I''m trying to boot 2.6.24 as a paravirt guest.  I''m
using all
> the config selections you describe.  I''ve done all this, from the
day
> "Xen" support landed up until 2.6.24 release.  I''ve
never gotten it to
> boot, not once.  These days (2.6.24), I get it starting, but it can
> never mount /dev/root.  I tried the 0x20201/xvda1 trick, but that
> doesn''t help either.  I''ve often wondered - which file
should I be
> using from my build?  arch/x86/boot/bzImage?  ./vmlinux?  I really would
> appreciate any help - I''m currently stuck with HVM when it comes
to
> mainline kernel, and that''s slow.
>
> Joel


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users