On Wed, Jun 04, 2014 at 05:03:48PM -0300, J. Cesar Bertelli wrote: > The last question was 'Does Owl's kernel include xen drivers?'
No, it does not. > ... And the right URL for templates is > ftp://ftp.fr.openwall.com/pub/Owl/current/vztemplate/ ... and OpenVZ templates do not include the kernel. They also don't include some userland packages that are not needed in containers - e.g., there's no bootloader. In Owl/build/installorder.conf, the package names to exclude from OpenVZ templates are prefixed with "H:", which stands for "host-only". $ fgrep H: installorder.conf H:acct H:dmidecode H:ethtool H:hdparm H:pciutils H:usbutils H:usb_modeswitch H:usb_modeswitch-data H:modutils H:mdadm H:lilo H:syslinux H:syslinux-extlinux H:silo H:prtconf H:losetup H:bridge-utils H:vconfig H:smartmontools H:vzquota H:vzctl So if you want to run Owl with its own kernel, starting with an OpenVZ template is not a good idea. These templates are to be used with shared kernels. > On 06/04/2014 at 4:48 PM, "J. Cesar Bertelli" <[email protected]> wrote: > >Does anyone know something important about Owl paravirtualized to > >work under Xen? For full virtualization, you just install into a VM and it should work - obviously, it does under KVM. For paravirtualization, you need to use a suitable kernel build. IIRC, galaxy@ uses Owl on Amazon AWS, but I don't recall whether that is with one of their standard kernels or with a rebuilt Owl kernel. Alexander
