[Bug 1242794] Re: Missing virtio-port symlinks

[Martin Pitt]

The older udev had this rule:
  KERNEL=="vport*", ATTR{name}=="?*", SYMLINK+="virtio-ports/$attr{name}"
while the current one added the SUBSYSTEM check:
 SUBSYSTEM=="virtio-ports", KERNEL=="vport*", ATTR{name}=="?*", SYMLINK+="virtio-ports/$attr{name}"

(in /lib/udev/rules.d/50-udev-default.rules)

Can you please run

  udevadm info --export-db > /tmp/udev.txt

and attach /tmp/udev.txt here? I'd like to see what SUBSYSTEM your
/dev/vport1p1 actually has.

This was changed in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=378f2e074e
without much commentary, so I suppose/hope there's just some typo in the
SUBSYSTEM.

** Changed in: systemd (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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/1242794

Title:
  Missing virtio-port symlinks

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Raring to Saucy, our libguestfs system stopped
  working. I then tried a fresh install of Saucy with the same results.
  I narrowed the issue down to the udev package. I was able to downgrade
  the udev package to the previous non-systemd (175-0ubuntu29) version
  and it works again with no other changes. This leads me to believe the
  issues isn't related to the updates of libguestfs, qemu, etc.

  1) Ubuntu 13.10

  2) systemd_204-0ubuntu18

  3) libguestfs-test-tool should succeed as it does on Ubuntu 13.04.

  4) libguestfs fails to communicate to the virtual machine due to
  missing /dev/virtio-ports (org.libguestfs.channel.0 in this case)
  symlink to /dev/vport1p1 (which is correctly created).

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