thanks ;) The host is an Intel Xeon X3350, running a Debian Lenny
64bits. I use on it the package "xen-hypervisor-3.2-1-amd64" from Debian
and kernel "linux-image-2.6.26-1-xen-amd64" from Debian too.
For the DomU, it was running the same Debian kernel, but I change it for
a "home made" vanilla Kernel 184.108.40.206 (to can use the last version of
the config : http://apt.daevel.fr:9999/daevel/config-2.6.28.N-dae-xen
the kernel :
And the diff for .config with my "normal" kernel :
daevel@may:~/linux$ diff config-2.6.28.N-dae-core2 config-2.6.28.N-dae-xen
< # CONFIG_FREEZER is not set
< # CONFIG_PARAVIRT_GUEST is not set
> # CONFIG_KVM_CLOCK is not set
> # CONFIG_KVM_GUEST is not set
< # CONFIG_HOTPLUG_CPU is not set
< # CONFIG_ACPI_CONTAINER is not set
< # CONFIG_VIRTUALIZATION is not set
> # CONFIG_KVM is not set
> # CONFIG_VIRTIO_PCI is not set
> # CONFIG_VIRTIO_BALLOON is not set
I hope this will help.
Thanks for your advise. I want to limit "overhead" or "memory
consuption" on DomU, but if I well understand you, there is not a big
So for simplicity I think I will add the required Xen options on my
For LVM, in fact I was not thinking we can use it directly from DomU ;)
Fajar A. Nugraha a écrit :
On Fri, Feb 20, 2009 at 11:02 PM, Olivier B. <xen.list@xxxxxxxxx> wrote:
On a DomU I've just replaced the Debian's 2.6.26 kernel by a Vanilly
220.127.116.11 version (amd64). It seems to work very well (ext4 !), but should I
Can you share your setup? It IS a pv domU, right?
I tried 18.104.22.168 as domU kernel, and only able to get it working as
32bit PAE domU. 64bit domU doesn't work. Can you share :
- what Xen version you use and from where (debian or vanilla xen.org)
- what is your domU kernel .config
reduce the size of the kernel ?
For example, since the DomU use the "noop" scheduler, I can remove
anticipatory, deadline, and cfq from my kernel, no ? And... is there any
interest to do that ?
Also the Dom0 use software raid and LVM, can I remove that support in DomU ?
Depends on what you're trying to do. If you want it to be "easy", it
should be as similar as possible as your domU distros' vendor kernel.
However if all your domU has the same kernel requirements (for
example: all of them uses ext4 and none of them needs iptables) it
might be beneficial to have a specialized kernel with all needed
Some "features" can be built as module anyway, so having them would allow
- easy loading when needed
- taking very little or no resource when not loaded
As for LVM on domU, as of now it is the only way to be able to extend
domU's storage online (using xm block-attach and extending domU's VG).
If you don't need to extend storage online (i.e. you can afford
rebooting domU to add storage) then you can safely remove, but IMHO
the space and memory savings will be somewhat insignificant.
Xen-users mailing list