[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Balloon driver set up failure
I have failed to set up xen balloon driver. maxmem was added to a working /etc/xen/*.cfg file giving: kernel = '/boot/vmlinuz-3.2.0-4-amd64' extra = 'ipv6.disable=1' ramdisk = '/boot/initrd.img-3.2.0-4-amd64' vcpus = '1' memory = '128' maxmem = '512' root = '/dev/xvda2 ro' disk = [ 'phy:/dev/blav2/dns2.XXXXXX.org-disk,xvda2,w', 'phy:/dev/blav2/dns2.XXXXXX.org-swap,xvda1,w', ] name = 'dns2.XXXXXX.org' vif = [ 'ip=192.168.42.101, mac=00:16:3E:26:9E:41, script=/etc/xen/scripts/vif-bridge, vifname=vif101.0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' The DomU was created. xl list showed the DomU with 128 M memory. In the DomU: * /proc/xen/balloon did not exist * dmesg | grep balloon showed: [ 0.012061] xen/balloon: Initialising balloon driver. [ 0.012761] xen-balloon: Initialising balloon driver. * grep CONFIG_XEN_BALLOON /boot/config-3.2.0-4-amd64 showed: CONFIG_XEN_BALLOON=y # CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set * The free command showed total memory 110 M On this evidence the xen balloon driver is not running. What can I try next to further analyse or fix? Versions: * Hypervisor/Dom0 OS: Debian 7 Wheezy (from Hetzner's image) * DomU OS: Debian 7 Wheezy (from Debian repos) * Xen by installing xen-linux-system and xen-tools, giving: libxen-4.1 libxenstore3.0 xen-hypervisor-4.1-amd64 xen-tools 4.3.1 xen-utils-4.1 xen-utils-common 4.1.4 xenstore-utils 4.1.4 Configuration: xl toolstack replacing default xm Best, Charles _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |