![]() If the messages really bother you, you can edit /lib/udev/rules.d/les file to something like the following (though this could be overwritten by future virtualbox updates): # modified orignal rules from vbox install with NAME issue remediated in next three commands udev allows renaming of network interfaces, but does not support renaming of other systems including drive or network controllers like vboxdrv, vboxdrvu and vboxnetctl. These are basically harmless notifications. Graphics Processor: NVIDIA GeForce GT 630/PCIe/SSE2 Processors: 8 × AMD FX™-8350 Eight-Core Processor Jul 19 07:49:30 systemname systemd-udevd: vboxdrvu: /usr/lib/udev/rules.d/les:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu". Jul 19 07:49:30 systemname systemd-udevd: vboxdrv: /usr/lib/udev/rules.d/les:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv". Jul 19 07:49:29 systemname systemd-udevd: vboxnetctl: /usr/lib/udev/rules.d/les:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl". Jul 19 07:49:29 systemname systemd-udevd: vboxdrvu: /usr/lib/udev/rules.d/les:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu". Jul 19 07:49:29 systemname systemd-udevd: vboxdrv: /usr/lib/udev/rules.d/les:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv". After latest kernel & vbox updates journal shows - Boot 2ad129f0c46448448937e2264fb61ae5.
0 Comments
Leave a Reply. |