Hi Benjamin, thanks for the bug.
This sounds like an issue not yet wreaking havoc but could be, so it is nice to
fix it before things get worse.
Limiting to "scsi + vsock" is what is needed I guess.
The rules we have are:
root@j:~# head /lib/udev/rules.d/60-open-vm-tools.rules
/lib/udev/rules.d/99-vmware-scsi-udev.rules
==> /lib/udev/rules.d/60-open-vm-tools.rules <==
# VMWare Virtual Sockets permissions
# after loading the vsock module, a block device /dev/vsock will be created
with permission 0600
# This rule changes permission to 0666 to allow users access to the virtual
sockets
KERNEL=="vsock", MODE="0666"
==> /lib/udev/rules.d/99-vmware-scsi-udev.rules <==
ACTION=="add", SUBSYSTEMS=="scsi", ENV{DEVTYPE}=="scsi_device",
ATTRS{vendor}=="VMware*" , ATTRS{model}=="Virtual disk*", ATTRS{timeout}=="?*",
ATTR{timeout}="180"
ACTION=="add", SUBSYSTEMS=="scsi", ENV{DEVTYPE}=="scsi_device",
ATTRS{vendor}=="VMware*" , ATTRS{model}=="VMware Virtual S",
ATTRS{timeout}=="?*", ATTR{timeout}="180"
@Bryce,
could you have a look at this please?
This should be much smaller to have a look than starting with v12.0.0 right
away :-)
** Changed in: open-vm-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968354
Title:
Please do not run udevadm trigger without parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1968354/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
