RE: [Xen-users] how can I use this patch xen-patches-2.6.34-1.tar.bz2 for dom0

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

> What modules (listed above or not) are loaded by the RHEL5 xend service? What BACKEND modules should be hard linked if one's xend service does not start any modules?

On opensuse 11.3 xend starts like that :-

case "$1" in
  start)
    check $1
    echo -n "Starting xend "
    if [ ! -z "$XEND" ]; then
        echo -n "(already running pid $XEND) "
    else
        cleanup
    fi
    # Load XEN backend modules
    # Sidenote: They could be loaded later:
    # - netbk and blkbk when the dom0 hotplug events occur
    #   (in xen-network-common.sh and block-common.sh)
    # - xenblk when xend prepares for bootloader
    # but for now it's safest to have them loaded when xend starts in dom0.
    modprobe evtchn 2>/dev/null || true
    modprobe blktap 2>/dev/null || true
    modprobe blkbk 2>/dev/null || true
    modprobe xenblk 2>/dev/null || true
    modprobe netbk 2>/dev/null || true
    modprobe gntdev 2>/dev/null || true
    modprobe usbbk 2>/dev/null || true
    xend start
    await_daemons_up
    ;;

Attached is config of "KOTD" ( kernel of the day)

Boris.

--- On Fri, 8/6/10, Mike Viau <viaum@xxxxxxxxxxxxxxx> wrote:

From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] how can I use this patch xen-patches-2.6.34-1.tar.bz2 for dom0
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, August 6, 2010, 1:32 PM

> On Sun, 18 Jul 2010 09:47:07 +0700
> Subject: Re: [Xen-users] how can I use this patch xen-patches-2.6.34-1.tar.bz2 for dom0
> From: fajar@xxxxxxxxx
> To: xen-users@xxxxxxxxxxxxxxxxxxx
>
> > 1. Have backend Dom0 drivers described as modules <M> , what causes "Hotplug scripts not working" issue to raise up right away. Exactly as for pvops kernel backend Dom0 drivers should be described as hard linked <*>  to avoid issue mentioned above at least on Ubuntu 10.04 Server.
>
> correct. As I mentioned, it was tested on RHEL5. The kernel config is
> created to be as close as possible to RHEL's kernel-xen configuration
> (which loads the modules from xend service).

I noticed the following BACKEND options in the config previously mentioned.

CONFIG_XEN_BACKEND=m
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_XEN_PCIDEV_BACKEND=m
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XEN_TPMDEV_BACKEND=m
CONFIG_XEN_SCSI_BACKEND=m
CONFIG_XEN_USB_BACKEND=m

What modules (listed above or not) are loaded by the RHEL5 xend service? What BACKEND modules should be hard linked if one's xend service does not start any modules?

Also what consideration should be taken on the *DEV options such as:

BLKDEV, NETDEV, PCIDEV, TPMDEV


Thanks.

>
> > 2. CONFIG_SYSFS_DEPRECATED should not be set also at least on Ubuntu 10.04 Server.
>
> correct. I did mention "newer distros don't need
> CONFIG_SYSFS_DEPRECATED=y and CONFIG_SYSFS_DEPRECATED_V2=y".
>
> --
> Fajar

-M

-----Inline Attachment Follows-----

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

config-2.6.34.2-0.0.2.6f27a23-xen
Description: Binary data

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