[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] dynamic memory extension not working on Debian Squeeze

  • To: xen-users <xen-users@xxxxxxxxxxxxx>
  • From: Peter Viskup <skupko.sk@xxxxxxxxx>
  • Date: Thu, 15 Nov 2012 20:59:57 +0100
  • Delivery-date: Thu, 15 Nov 2012 20:01:27 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

On 11/15/2012 10:20 AM, Ian Campbell wrote:
On Thu, 2012-11-15 at 00:17 +0000, Peter Viskup wrote:
Hi Ian and Alexander,
it's good to hear I am not the onlyone experienced this issue.
The removal of tdb file solved the xenstore issue.

Now I am able to provide you the outputs you requested. They are very
similar to those provided by Alexander.

server1:~# xenstore-ls -fp | grep ldap
When I asked for "xenstore-ls -fp | grep target" I meant the literal
string "target" not the name of the target VM, sorry if this wasn't

I just increased the memory for ldap domU to 512MB:
ldap:~# grep MemTotal /proc/meminfo
MemTotal:         250320 kB
ldap:~# cat /sys/devices/system/xen_memory/xen_memory0/target_kb
OOI what happens if you
        echo -n 524288>  /sys/devices/system/xen_memory/xen_memory0/target_kb

Do you get anything in your dom0 or domU dmesg when you try and balloon
up in this way? What about Xen's dmesg?

Actually, it would be useful to see the full domU dmesg at least.


Here is additional info:
- attached whole domU's dmesg since the reboot, xen balloon driver initialized
 - attached is 'xm dmesg' output - could help probably
 - tried echo <number> into target_kb with no effect and no messages
- during the xm memory commands no kernel messages were logged by dom0 nor domU
 - the only messages from xend.log are:
[2012-11-15 20:24:14 2948] DEBUG (XendDomainInfo:1477) Setting memory target of domain ldap (2) to 512 MiB. [2012-11-15 20:24:19 2948] DEBUG (XendDomainInfo:1504) Setting memory maximum of domain ldap (2) to 512 MiB. [2012-11-15 20:24:21 2948] DEBUG (XendDomainInfo:1477) Setting memory target of domain ldap (2) to 512 MiB. [2012-11-15 20:25:50 2948] DEBUG (XendDomainInfo:1477) Setting memory target of domain ldap (2) to 256 MiB. - I probably found something in Xen's domain-builder-ng.log log file - messages from last domU build process are saved in attached file domU-build.log (there are some xen-3.0 statements) - not sure if these are ok or not
elf_xen_parse_note: GUEST_OS = "linux"
elf_xen_parse_note: GUEST_VERSION = "2.6"
elf_xen_parse_note: XEN_VERSION = "xen-3.0"
x86_compat: guest xen-3.0-x86_64, address size 64
xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches

This is dom0 boot config:
multiboot /xen-4.0-amd64.gz placeholder dom0_mem=756M numa=off loglvl=all guest_loglvl=all module /vmlinuz-2.6.32-5-xen-amd64 placeholder root=/dev/mapper/system_xen-root ro numa=off quiet

Just for your information - the disk and cpu hotplug is working like a charm - the only issue is with memory ballooning.

Not sure what else I could provide to all of you.

Best regards,
Peter Viskup

Attachment: domU-build.log
Description: Text Data

Attachment: dmesg.2012-11-15.log
Description: Text Data

Attachment: xen.dmesg.2012-11-15.log
Description: Text Data

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.