Xen users - Feb 2009 - Minimum kernel.config requirements for domU?

Hello list,

What are the absolut minimum requirements for a domU selfmade paravirtualized
kernel?

I am asking because i want to build a domU kernel w/o any additional features,
just able to directly boot into the provided blockdevice...

All tries until now didn't boot completely (stops after "freeing
memory"), so i must have missed something i don't know? What about IDE,
scsi, sata, pata, network-devices, serial, framebuffer, etc..?

AFAIK, i need to enable following flags:
- The root-filesystem
- CONFIG_X86_SMP if wanted
- CONFIG_X86_64 if dom0 supports it
- CONFIG_x86_64_SMP if dom0 supports it
- CONFIG_X86_XEN or CONFIG_X86_64_XEN
- X86_XEN_GENAPIC
- CONFIG_XEN_PCIDEV_FRONTEND
- CONFIG_XEN
- CONFIG_XEN_UNPRIVILEGED_GUEST
- CONFIG_XEN_PRIVCMD
- CONFIG_XEN_XENBUS_DEV
- CONFIG_XEN_BLKDEV_FRONTEND
- CONFIG_XEN_NETDEV_FRONTEND
- CONFIG_XEN_FRAMEBUFFER
- CONFIG_XEN_KEYBOARD
- CONFIG_XEN_DISABLE_SERIAL
- CONFIG_XEN_SYSFS
- CONFIG_XEN_COMPAT_030004_AND_LATER=y
- CONFIG_XEN_COMPAT=0x030004
- CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
- CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
- CONFIG_IRQ_PER_CPU=y
- CONFIG_NO_IDLE_HZ=y
- CONFIG_XEN_SMPBOOT=y
- CONFIG_XEN_DEVMEM=y
- CONFIG_XEN_BALLOON=y
- CONFIG_XEN_SCRUB_PAGES=y

What else ist absolutely needed for a working domU boot?

Kind regards, Florian
**********************************************************************************************
IMPORTANT: The contents of this email and any attachments are confidential. They
are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or
the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
**********************************************************************************************

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

On Wed, Feb 18, 2009 at 11:39 PM, Rustedt, Florian
<Florian.Rustedt@smartnet.de> wrote:
> What are the absolut minimum requirements for a domU selfmade
paravirtualized kernel?
>
Try looking at this
http://wiki.xensource.com/xenwiki/XenParavirtOps
> I am asking because i want to build a domU kernel w/o any additional
features, just able to directly boot into the provided blockdevice...
What are you planning to use it for? From my experince, if you''re
going to use it for production purposes, it''s MUCH simpler to simply
use vendor-provided kernels.
>
> All tries until now didn''t boot completely (stops after
"freeing memory"), so i must have missed something i don''t
know? What about IDE, scsi, sata, pata, network-devices, serial, framebuffer,
etc..?
Well, I just tried using kernel 2.6.28.6 (32bit PAE), disable modules,
unselecting IDE, scsi, etc. (basically selecting only the xen frontend
for disk and network), and it works (using busybox as init, stored on
ext3).

Here''s my .config : http://pastebin.com/f2ad5ed12
Here''s screen capture when domU starting :
http://pastebin.com/d7c810afc

My dom0 is RHEL 5.3 x86_64, Xen 3.3.1 from gitco

Regards,

Fajar

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

On Fri, Feb 20, 2009 at 1:46 PM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
>> All tries until now didn''t boot completely (stops after
"freeing memory"), so i must have missed something i don''t
know? What about IDE, scsi, sata, pata, network-devices, serial, framebuffer,
etc..?
>
> Here''s screen capture when domU starting :
http://pastebin.com/d7c810afc
>
Oh and if you already got this far (from my screen capture)

EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 252k freed

Then the domU kernel has succesfully run and mount the root block
device. After that it''s a matter of adjusting the content of
"/". What
I did is create a minimum "/" file system using busybox. You might
want to try the same thing.

Regards,

Fajar

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

You''re right! 

My fault was a misconfigured console/vnc. I just had to vnc into and had a
login.... :(

Kind regards, Florian
> -----Ursprüngliche Nachricht-----
> Von: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von 
> Fajar A. Nugraha
> Gesendet: Freitag, 20. Februar 2009 07:56
> An: Rustedt, Florian
> Cc: xen-users@lists.xensource.com
> Betreff: Re: [Xen-users] Minimum kernel.config requirements for domU?
> 
> On Fri, Feb 20, 2009 at 1:46 PM, Fajar A. Nugraha 
> <fajar@fajar.net> wrote:
> >> All tries until now didn''t boot completely (stops after 
> "freeing memory"), so i must have missed something i
don''t
> know? What about IDE, scsi, sata, pata, network-devices, 
> serial, framebuffer, etc..?
> >
> > Here''s screen capture when domU starting : 
> > http://pastebin.com/d7c810afc
> >
> 
> Oh and if you already got this far (from my screen capture)
> 
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 252k freed
> 
> Then the domU kernel has succesfully run and mount the root 
> block device. After that it''s a matter of adjusting the 
> content of "/". What I did is create a minimum "/" file
> system using busybox. You might want to try the same thing.
> 
> Regards,
> 
> Fajar
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
**********************************************************************************************
IMPORTANT: The contents of this email and any attachments are confidential. They
are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or
the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
**********************************************************************************************


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