This bug was fixed in the package linux - 3.2.0-116.158
---
linux (3.2.0-116.158) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1640549
* xen:balloon errors in 14.04 beta (LP: #1304001)
- xen/balloon: cancel ballooning if adding new memory
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
** Changed in: linux (Ubuntu Precise)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications
https://lists.ubuntu.com/archives/kernel-team/2016-November/080739.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage
This bug still exists in Precise with 3.2.0-113.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
** Tags removed: verification-done-trusty verification-done-utopic
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
Awesome, thanks a lot Martijn. I'm tagging this bug as verified.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking good. I'm no expert on testing pre-release packages so please
correct me if I've done something wrong.
Tested on Utopic today (ami-540ba523 on a m3.medium amd64 hvm). It came
with kernel 3.16.0-24.32 which exhibits the xen:balloon error messages.
Upgraded to 3.16.0.24.25, the latest
Hello
Is possible for anyone to test Utopic kernel so we can flag this as
verification-done and push it to -proposed asap ?
Thank you very much
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello
Is possible for anyone to test Utopic kernel so we can flag this as
verification-done and push this to be released asap ?
Thank you very much
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
Will this patch go out in 3.13.0-38 this week?
I'm assuming that the discussion around 'linux-keystone' is something
different. Regardless, please do not drop this fix from 3.13.0-38 as
we're expecting it this week per Stefan's comments above - and we have
already verified it resolves the issue.
I tested with the latest 3.13 kernel in trusty-proposed:
Version table:
3.13.0.40.47 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
I can confirm that the xen:balloon: Cannot add additional memory (-17)
message do not occur with this kernel in AWS
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage
linux-keystone in trusty-proposed is available at
https://launchpad.net/ubuntu/+source/linux-keystone/3.13.0-18.28
** Tags removed: verification-failed verification-failed-trusty
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Ubuntu
** Branch unlinked: lp:ubuntu/precise-security/linux-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this
It looks like the patches missed the current cycle. But that might move
to updates this week (maybe today). They are queued for the next round.
So maybe around next week status here should indicate it wen into
proposed.
--
You received this bug notification because you are a member of Ubuntu
Is there a time frame for when the 2nd fix will make its way out to
trusty/utopic? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage
I've also tested with the kernel from Rafael's PPA, and can confirm that
the alerts are gone for me.
Thanks to everyone involved!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
FYI,
I've received information that this indeed fixes the described problem.
Thank you Stefan, Tim, Boris.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in
Updated test kernels at http://people.canonical.com/~smb/lp1304001/
(again for normal installs based on cloud-images the linux-image-extra
is not needed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Trusty)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Utopic)
Assignee: Tim Gardner (timg-tpi) = Stefan Bader (smb)
** Changed in: linux (Ubuntu)
Status:
I have created one PPA located at :
https://launchpad.net/~inaddy/+archive/ubuntu/lp1304001
Containing both fixes to address this issue:
commit 3dcf63677d4eb7fdfc13290c8558c301d2588fe8 (already present in Trusty)
Author: David Vrabel david.vra...@citrix.com
Date: Mon Sep 1 18:52:44 2014 +0100
It is now in mainline, commit fd8b79511349.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
It doesn't appear fixed to me. Please reopen?
I just installed an m3.medium instance, updated to kernel 3.13.0-37.64
(which should contain the fix) and rebooted.
The errors appear as soon as booting is nearly complete.
From dmesg:
[6.631751] xen:balloon: Cannot add additional memory (-17)
[
This looks like to be requiring even more. I found the following patch
which supposedly was queued for 3.18 but I cannot find it in upstream
git, yet: xen/balloon: Don't continue ballooning when BP_ECANCELED is
encountered.
Commit 3dcf63677d4e (xen/balloon: cancel ballooning if adding new
memory
I was waiting for this patch to be pulled into the mainline before
posting a pointer/commitID here. It's not there yet.
But yes, you need that commit (on top of 3dcf63677d4e) to make kernel
shut up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
This bug was fixed in the package linux - 3.13.0-37.64
---
linux (3.13.0-37.64) trusty; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1372576
[ dann frazier ]
* [Config] CONFIG_HW_RANDOM_XGENE=m on arm64
[ Edward Lin ]
* SAUCE: Add
This bug was fixed in the package linux - 3.13.0-37.64
---
linux (3.13.0-37.64) trusty; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1372576
[ dann frazier ]
* [Config] CONFIG_HW_RANDOM_XGENE=m on arm64
[ Edward Lin ]
* SAUCE: Add
Hmm, yes, the patch may not work if something (AWS, I guess) keeps
requesting to balloon memory.
Can someone try the attached patch (on top of David's)? I only compile-
tested it.
** Patch added: cancel_balloon.patch
Actually, this (v2) is a slightly better one to try.
** Patch added: cancel_balloon_v2.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4223585/+files/cancel_balloon_v2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: verification-failed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
** Tags removed: kernel-request-3.13.0-24.46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go
I think that this is a verification-failed. Upgrading the kernel in
-proposed does not fix the issue:
ubuntu@ip-10-11-165-53:~$ uname -a
Linux ip-10-11-165-53 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-10-11-165-53:~$ dpkg-query --show
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug
This bug was fixed in the package linux - 3.16.0-16.22
---
linux (3.16.0-16.22) utopic; urgency=low
[ Andy Whitcroft ]
* Revert SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
* [Config] tools -- only build common tools when enabled
* [Config] follow rename of
If it is only exactly one message like that, this would be what we
expect from the quick aid. The hint about scaling up certain factors
could be something to keep in mind. Might not be exactly the same as it
seems to happen on guests with less than 4G, but still. Maybe I can take
a bit of time and
Some additional information. Even with the syslog message i ran 55 GB
utilization all night and all processes finished with success on AWS
c3.large. The message also appears to be missing after reboot on
c3.large (~60 GiB).
On a c3.large (3.75 GiB) the message is spamming syslog (many messages)
Sorry for incorrect information. The message is gone from r3.2xlarge
(~60 GiB) and present on c3.large (3.75 GiB).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors
Syslog shows:
kernel: [ 832.224074] xen:balloon: reserve_additional_memory:
add_memory() failed: -17
On latest AMI as of today (https://cloud-
images.ubuntu.com/locator/ec2/):
eu-west-1 trusty 14.04 LTS amd64 hvm:ebs 20140829
ami-acc41cdb hvm
Running on instance type
I had this problem on a PC with Xen and Linux VMs. The VMs are configured to
boot with just 400 MB of RAM allotted to them and up to 8GB max RAM.
I was never able to get above some 4.3GB in any VM, and log showed the
reserve_additional_memory: add_memory() failed: -17 message at that point
The
The suggested (minimal) fix is now upstream.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8
I did /not/ tag it for stable because I do not consider this bug
sufficiently critical.
--
You received this bug notification because
** Also affects: linux (Ubuntu Utopic)
Importance: High
Status: Confirmed
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
You received this bug notification
** Changed in: linux (Ubuntu Utopic)
Status: In Progress = Fix Committed
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee:
I am not sure the bug should be closed. David's fix made system behavior
tolerable to users (because the error is now only reported once) but the
problem is still there. If possible I'd suggest lowering bug's priority
but keeoping it open.
--
You received this bug notification because you are a
** Description changed:
+ SRU Justification:
+ [Impact]
+ The following errors may occur on HVM instances on EC2: xen:balloon:
reserve_additional_memory: add_memory() failed: -17
+
+ [Test Case]
+ Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error
message.
+
+ [Fix]
+
Cherry picked 3dcf63677d4eb7fdfc13290c8558c301d2588fe8 for Trusty which
will mark this bug as fix released as soon as the kernel is promoted to
-updates.
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a
Problem also without hvm:
Kernels:
Linux version 3.13.0-27-generic (buildd@akateko) (gcc version 4.8.2
(Ubuntu 4.8.2-19ubuntu1) ) #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014
(Ubuntu 3.13.0-27.50-generic 3.13.11)
Linux version 3.13.0-35-generic (buildd@panlong) (gcc version 4.8.2
(Ubuntu
Ok, so the test-kernels containing David's patch are at
http://people.canonical.com/~smb/lp1304001/. This should at least
prevent repeated messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you try this patch?
8--
xen/balloon: cancel ballooning if adding new memory failed
If the balloon driver is adding additional memory regions to the
balloon and add_memory() fails it will likely continuously fail so
cancel the balloon operation.
Signed-off-by: David
Sorry, it appears launchpad ate all the tabs.
** Patch added: xen/balloon: cancel ballooning if adding new memory failed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4189295/+files/0001-xen-balloon-cancel-ballooning-if-adding-new-memory-f.patch
--
You received
Thanks David, I will pre-build some test-kernels tomorrow and post them
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
xen:balloon: reserve_additional_memory: add_memory() failed: -17 can
only occur in HVM guests if the balloon target is set above the maximum
allowed by the guest's memory map.
This is likely a bug in the EC2 toolstack. Perhaps this was introduced
as a workaround for the problem fixed by
http://marc.info/?l=xen-develm=135939492007293w=1
This option is incompatible with PCI hotplug. This is a known problem.
We recommend Canonical disable this option as does upstream. From that
note:
Inside dom0, yes?
Looking at the balloon driver, it doesn't seem to handle
I've seen this error occur on m3.medium (3.75GB RAM) and c3.large
(3.75GB) EC2 instances, but not on m3.large (7.5GB), m3.xlarge (15GB) or
t2.small (4GB) instances.
Interestingly, it also does not occur on t2.micro (1GB) instances.
All of the VMs in question are running kernel 3.13.0-29-generic
No fix (from me, that is)
I need to be able to reproduce this and this appears to only be
happening in AWS environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon
The same issue with latest kernel:
Linux ip-10-0-0-232 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04.1 LTS \n \l
Aug 10 20:22:53 ip-10-0-0-232 kernel: [ 896.352081] xen:balloon:
reserve_additional_memory: add_memory() failed: -17
Aug
also happening to me on a m3.medium
not wanting to compile a custom kernel version the only way of getting rid of
these annoying messages was adding to /etc/rc.local:
cat /sys/devices/system/xen_memory/xen_memory0/info/current_kb
/sys/devices/system/xen_memory/xen_memory0/target_kb
--
You
Just ran into this error on Amazon VPC today on a newly created
instance. I know very little about Xen (just an AWS user) but maybe this
extra info will be useful to someone. If I can provide more information,
let me know.
Instance type: m3.medium (HVM)
AMI ID:
Matt, can you post config file that you used? I tried a few different
configurations and (again) could not reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon
Not precisely. What toolstack are you using? I can try to reproduce
outside of our control plane with a config file that would work on your
toolstack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am using 4.2 stable tree, configured with default parameters (i.e. no
options to ./configure script):
[root@ovs103 install]# xm info
host : ovs103.us.oracle.com
release: 3.16.0-rc1-pmu-dom0
version: #1 SMP Mon Jul 7 14:09:40 EDT 2014
machine
And this is my guest (14.04 desktop):
Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2
(Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014
(Ubuntu 3.13.0-24.46-generic 3.13.9)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Boris, all:
We did a test with disabling the SRAT entirely, but the balloon messages
persisted.
ami-af8d9ac6 (ubuntu/images-milestone/hvm/ubuntu-
trusty-14.04-beta2-amd64-server-20140326)
$ dmesg | grep -i 'srat\|node\|numa\|balloon' |grep -iv inode
[0.00] No NUMA configuration found
[
Same xen:balloon errors still present inlinux-image-3.13.0-29-generic
(3.13.0-29.53).
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
So given that you are seeing this on 3.2 guest this would be a different
problem. Having said that, I don't see any errors in dmesg_domu.txt
anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's no errors in the dmesg because that's taken from a clean boot.
When the guest runs and the PV drivers start, then the logs start flooding with:
[34279.205229] xen:balloon: reserve_additional_memory: add_memory() failed: -17
[34281.237272] xen:balloon: reserve_additional_memory:
If you don't specify debug and loglevel boot options I think you won't
see these. Of course, the underlying problem would still be there.
Do you observe this on guests with newer kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
dmesg_dom0.txt
** Attachment added: dmesg_dom0.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123329/+files/dmesg_dom0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
dmidecode_domu.txt
** Attachment added: dmidecode_domu.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123332/+files/dmidecode_domu.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did some further testing. Running Ubuntu LTS 14.04 as a domU doesn't
seem to create the problem. The specific VM which is causing the error
messages is running Linux 3.2.40. So I guess the bug could be in the
guest's kernel. I can't really upgrade it as it's using a customised
version that's
xl_dmesg.txt
** Attachment added: xl_dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123327/+files/xl_dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
xl_info.txt
** Attachment added: xl_info.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123328/+files/xl_info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
dmesg_domu.txt
** Attachment added: dmesg_domu.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123331/+files/dmesg_domu.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
domu.cfg.txt
** Attachment added: domu.cfg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4123330/+files/domu.cfg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry I meant trusty not jaunty.
Distributor ID: Ubuntu
Description:Ubuntu 14.04 LTS
Release:14.04
Codename: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
Hi,
Thought I'd mention that I'm having this problem too. The kernel logs are
flooded with this error:
ubuntu kernel: [129626.648070] xen:balloon: reserve_additional_memory:
add_memory() failed: -17
I'm running XEN on a dedicated i5 PC with Jaunty with up to date packages.
I haven't installed
Can you please post:
1. Guest configuration file
2. boot log from dom0 (please boot loglevel=8)
3. xl dmesg and xl info from dom0
4. boot log from guest (also loglevel=8)
5. dmidecode from guest (I am mostly interested in BIOS object)
-boris
--
You received this bug notification because you
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go
Yes, those would be helpful although now I think understanding EC's BIOS
(seabios I assume?) may be more important. Neither I nor Stefan have
been able to reproduce this problem and it seems that EC does something
in BIOS (and possibly qemu) that may not be available in vanilla Xen,
most
Boris, do you still need our Xen configurations to proceed further then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications
[14Ah 0330 4] Proximity Domain :
[14Eh 0334 2]Reserved1 :
[150h 0336 8] Base Address :0001
[158h 0344 8] Address Length : 1000===
This looks wrong
[160h 0352 4]
Hi Andrew,
sorry about the dyndbg. It all lokked like it would be tied to that but right
now I am not sure it is. I need to check the code again. If anything else fails
we can do a special kernel. I have the same issue as Boris in that I am not
able to cause the same problem on HVM guests
This warning implies that SRAT may be wrong. And I just noticed that this may
not be vanilla 4.2:
[0.00] DMI: Xen HVM domU, BIOS 4.2.amazon 01/24/2014
Are we on a custom HVM BIOS? That's where memory is described to domain.
Although NUMA issue may be somewhat orthogonal, it still may
** Attachment added: srat.dsl
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4086876/+files/srat.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
I would think Boris is after memory related special settings on the host and
guest (if you can reveal those). Could be you are hinting that at least for the
host the config was not modified. I assume still using the xm/xend stack. The
other info there would be the number assigned to mem of
I would like to reproduce this first and for that I will need at least
config file that is used for launching the guest ('memory' and 'maxmem'
for sure but having the whole file would be better) as well as guest's
kernel config file. Knowing what xen boot options are as well as if
there is
** Attachment added: config-3.13.0-24-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4085875/+files/config-3.13.0-24-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Stefan, Boris,
I booted my EC2 guest with the following kernel options:
kernel /boot/vmlinuz-3.13.0-24-generic root=LABEL=cloudimg-
rootfs ro console=hvc0 dyndbg=file xen-balloon.c +p debug loglevel=8
memblock=debug
as requested, but I'm not seeing any additional debug messages
Apologies for the hold up everyone. I'm trying to get somebody within
AWS management to sign off on what we can and can't disclose regarding
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Boris, this is EC2. Xen 4.2 with a default config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
1 - 100 of 110 matches
Mail list logo
