[Bug 1242794] Re: Missing virtio-port symlinks

[Matt Whiteley]

There is no `name` in that directory which certainly would explain the
lack of a named symlink. I provided a name (id) to the virtserialport
device in the qemu options.

  -r--r--r-- 1 root root 4096 Oct 30 07:22 dev
  lrwxrwxrwx 1 root root    0 Oct 30 07:22 device -> ../../../virtio0
  drwxr-xr-x 2 root root    0 Oct 30 07:22 power
  lrwxrwxrwx 1 root root    0 Oct 30 07:22 subsystem -> ../../../../../../class/virtio-ports
  -rw-r--r-- 1 root root 4096 Oct 30 07:21 uevent


** Attachment added: "vport0p2.txt"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1242794/+attachment/3895460/+files/vport0p2.txt

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