Any updates on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
Status in udev:
Unknown
Status in linux package in
> I would be happy to unconditionally turning hot-add on and SRU the
udev rule back to Ubuntu 14.04.
As I (and Kay) said, this is okay for an SRU, but unconditionally
second-guessing/changing the kernel defaults is just wrong and
inefficient too. For yakkety and onwards this *really* should be
** Patch added: "0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233466/+attachment/4680556/+files/0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Bug watch added: freedesktop.org Bugzilla #78478
https://bugs.freedesktop.org/show_bug.cgi?id=78478
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=78478
Importance: Unknown
Status: Unknown
** Project changed: linux => udev
--
You received this bug
I fail to come up with a use-case that just wants to add CPU/RAM without
onlining it sooner or later. For virtual environments, you add CPU/RAM
to use it and therefore want to online it once it appears. In a cloud
environment (like ProfitBricks), it makes no sense to add CPU/RAM
without using it,
Maintaining an ever-growing list of vendors is error-prone and TBH quite
silly. Are there any CPUs where we *don't* want hot-add? If not, why
can't the kernel just default to enabling this, instead of userspace
unconditionally turning this on? But if hot-add is supposed to work
everywhere, then
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
Status in linux package in Ubuntu:
Confirmed
Status in
Can we also enable the hotplug udev rules for QEMU guests? See the
attached git format-patch.
** Patch added: "0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233466/+attachment/4679035/+files/0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-2147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
Reopening the kernel task here. We've carried the temporary udev rule
workaround for three releases now; it seems we all agree that it's wrong
(unconditional unbreak my kernel rule) and makes things even worse
under memory pressure. Is there any better solution in sight? Thanks!
** Changed in:
Time is running out for saucy, so I'll upload the rule from comment 14
now, with some correction: I take it you actually mean memory[0-9]*
instead of memory*[0-9] (same for CPU). @Abhishek, I don't see how
these rules would cause any other kernel module to suddenly not load?
All they do is to
** Branch linked: lp:ubuntu/saucy-proposed/systemd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
Status in “linux” package
BTW, where does this rule need to live, in the hypervisor or in the
guests? In the latter case I guess we should ship it in udev, in the
former case they hypervisor package could just ship it? That would avoid
the extra rule for other installs.
--
You received this bug notification because you
Hi Martin, Thanks for accommodating the request for the udev rule. The
rule needs to live in the guest as Hyper-V does not understand udev
rules.
Yes, we did test with Andy's udev rule from comment 14 and it seems to
work. Only issue we saw was that it seemed to suppress some of our other
drivers
In my last comment, I meant to say that the patch that got rejected on
lkml is at:
https://groups.google.com/forum/#!msg/linux.kernel/AxvyuQjr4GY/TLC-
K0sL_NEJ
Thanks,
Abhishek
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi guys,
We went the alternate route of trying to convince kernel folks of fixing
this problem through a patch. Unfortunately, the patch was rejected. The
discussion involved is quoted below. Please also note that in the above
patch we can remove the CPU hotadd request command as that is
Abhishek Gupta, did you really quote the right mails? Because those
mails are just proving my point, it makes no sense to have an
unconditional userspace rule which is just there to always enable new
memory. To the contrary, as this is always going to involve more memory
allocation (like it might
Hi Martin, I will circle back with KY and reply by tomorrow morning on
this. What we are trying to convey here is that this was discussed with
the kernel folks and they shot down the kernel patch which would have
got rid of the udev rule.
Please include the memory hotadd patch
I apologize for
Btw, another thought is that we do realize that the udev rule is not the
best solution here but given the release time frame perhaps we can
compromise a little. We will be more than happy to work with you to
provide an alternate solution. However releasing 13.10 with risks of
panics is more
Yes, I think Andy's udev rule from comment 14 is an acceptable distro-
level compromise for 13.10, until that gets solved more cleanly. I
didn't see a confirmation from you that this worked, is that the one
which got tested?
If you absolutely do not want to include the udev rule we can send you
@Pitti -- for completeness this is the proposed udev rule which is being
tested:
# On Hyper-V Virtual Machines we want to add memory and cpus on demand.
ATTR{[dmi/id]sys_vendor}!=Microsoft Corporation, GOTO=hyperv_hotadd_end
ATTR{[dmi/id]product_name}!=Virtual Machine, GOTO=hyperv_hotadd_end
#
Hi there! The udev rule works but after installing the following udev
package the following drivers do not load anymore:
1. hyperv-fb
2. hv_utils
3. hv_balloon
Is this just a side effect or something else is wrong? Please let us
know.
Thanks,
Abhishek
--
You received this bug notification
Being a little proactive and adding Andy as well as he is fixing the
other bugs. Hope that is ok Ben.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
These commits from mainline which are in v3.12-rc1, v3.11-rc3, and
v3.11-rc3 respectively:
commit 20138d6cb838aa01bb1b382dcb5f3d3a119ff2cb
Author: K. Y. Srinivasan k...@microsoft.com
Date: Wed Jul 17 17:27:27 2013 -0700
Drivers: hv: balloon: Initialize the transaction ID just before
Confirmed that two of the kernel patches are already applied, pulled the
third in and sent kernels for testing.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New = In Progress
** Changed in: systemd (Ubuntu)
Ok I have built a test kernel containing the missing patch above which
is here:
http://people.canonical.com/~apw/hyperv-saucy/
I have also attempted to add the required rule to udev which is here:
http://people.canonical.com/~apw/hyperv-saucy/udev/
If you could test those and confirm
Testing now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
Status in “linux” package in Ubuntu:
Fix Committed
Status in
This bug was fixed in the package linux - 3.11.0-11.17
---
linux (3.11.0-11.17) saucy; urgency=low
[ Andy Whitcroft ]
* [Packaging] tools -- only build common tools package in master
* SAUCE: tools -- report when tool is not available
- LP: #1233376
* [Packaging] tools
I am still testing the fix. It appears that the udev rule installs
correctly but I see two issues:
a) Memory demand from Ubuntu 13.10 is extraordinarily high on Hyper-V. It is
likely to be a bug on our side and we will work on it.
b) After applying all the packages under udev, our mouse driver
Please don't apply this udev rule as it is:
* It can be made *much* more efficient and avoid an extra shell with
SUBSYSTEM==memory, ACTION==add,
DEVPATH==/devices/system/memory/memory*[0-9], ATTR{online}=1
(same for the other rule)
* In this generic way they don't look plausible.
Log files not needed as solution included in bug report.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
33 matches
Mail list logo
