[Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

[Christian Reis]

Note that same udevd rule exists as far back as 16.04 LTS:

ubuntu at xenial-test:~$ md5sum /lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4  /lib/udev/rules.d/40-vm-hotadd.rules

ubuntu at focal-test:~$ md5sum /usr/lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4  /usr/lib/udev/rules.d/40-vm-hotadd.rules

There is a previous bug,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457 which
addressed a different symptom but may be related.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1876018

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

Status in systemd package in Ubuntu:
  New

Bug description:
  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+subscriptions