1 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/118/none/2032 b/results/classifier/118/none/2032
new file mode 100644
index 000000000..0d060b616
--- /dev/null
+++ b/results/classifier/118/none/2032
@@ -0,0 +1,61 @@
+files: 0.784
+device: 0.769
+graphic: 0.712
+socket: 0.710
+PID: 0.658
+debug: 0.640
+kernel: 0.605
+network: 0.585
+performance: 0.571
+permissions: 0.563
+register: 0.549
+semantic: 0.540
+architecture: 0.537
+mistranslation: 0.528
+x86: 0.510
+boot: 0.502
+ppc: 0.502
+i386: 0.489
+VMM: 0.472
+TCG: 0.468
+hypervisor: 0.468
+peripherals: 0.456
+vnc: 0.453
+arm: 0.450
+user-level: 0.448
+risc-v: 0.442
+assembly: 0.413
+virtual: 0.387
+KVM: 0.367
+
+qemu-guest-agent not starting
+Description of problem:
+Trace found in syslog :
+```
+syslog:Dec 11 13:45:08 mail systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out.
+syslog:Dec 11 13:45:08 mail systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0.
+syslog:Dec 11 13:45:08 mail systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
+syslog:Dec 11 13:45:08 mail systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'.
+```
+Steps to reproduce:
+systemctl start qemu-guest-agent
+Additional information:
+Messages when installing the systemd unit : 
+```
+systemctl enable qemu-guest-agent
+Synchronizing state of qemu-guest-agent.service with SysV service script with /lib/systemd/systemd-sysv-install.
+Executing: /lib/systemd/systemd-sysv-install enable qemu-guest-agent
+The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
+Alias= settings in the [Install] section, and DefaultInstance= for template
+units). This means they are not meant to be enabled using systemctl.
+
+Possible reasons for having this kind of units are:
+• A unit may be statically enabled by being symlinked from another unit's
+  .wants/ or .requires/ directory.
+• A unit's purpose may be to act as a helper for some other unit which has
+  a requirement dependency on it.
+• A unit may be started when needed via activation (socket, path, timer,
+  D-Bus, udev, scripted systemctl call, ...).
+• In case of template units, the unit is meant to be enabled with some
+  instance name specified.
+ ```