[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Balloon driver set up failure
On Thu, 2014-09-25 at 08:23 +0530, Charles wrote: > 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 Did you mount xenfs on /proc/xen? > * 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 makes you say that? It looks like the balloon core is there and running (you have ~128M free, less some normal overheads, which is expected). You haven't asked the balloon driver to change that (e.g. with xl mem-set) so it won't have done anything. Ian. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |