Bug 102256 - Xorg or wayland fail to start with spice-vdagentd started on linux 4.12
Summary: Xorg or wayland fail to start with spice-vdagentd started on linux 4.12
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: unix agent (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-16 12:55 UTC by xiaoliniess
Modified: 2018-06-03 10:26 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg log when graphic interface doesn't show (24.24 KB, text/x-log)
2017-08-16 12:55 UTC, xiaoliniess
Details
spice-vdagentd service status (1.50 KB, text/plain)
2017-08-16 12:56 UTC, xiaoliniess
Details

Description xiaoliniess 2017-08-16 12:55:51 UTC
Created attachment 133550 [details]
xorg log when graphic interface doesn't show

Guest failed to start graphic interface when spice-vdagentd started and auto resize enabled with guest os running kernel 4.12. If I disable spice-vdagentd or disable auto resize or revert to kernel 4.11, then desktop start just fine.

This has been tested with both fedora 26 guest on gentoo host and fedora 26 host. Also tested with archlinux guest on gentoo host. And both fedora 26 with gnome/wayland and fedora 26 with cinnamon/xorg have the same problem.

Related package versions:
spice-vdagent-0.17.0-2.fc26.x86_64(fedora)
qemu-2.9.0(gentoo)
spice-gtk-0.33(gentoo)
spice-protocol-0.12.13(gentoo)
spice-0.13.3(gentoo)

The xorg log is attached.
Comment 1 xiaoliniess 2017-08-16 12:56:37 UTC
Created attachment 133551 [details]
spice-vdagentd service status
Comment 2 xiaoliniess 2017-08-17 01:44:48 UTC
Similar bug report on debian

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872304
Comment 3 Christophe Fergeau 2017-08-28 08:18:18 UTC
"Failed to start"? Do you mean that the boot process hangs, and you never get to the login screen window? Or does Xorg tries to start, and then dies? Something else? Is there anything relevant in dmesg?
Comment 4 xiaoliniess 2017-08-28 08:37:57 UTC
(In reply to Christophe Fergeau from comment #3)
> "Failed to start"? Do you mean that the boot process hangs, and you never
> get to the login screen window? Or does Xorg tries to start, and then dies?
> Something else? Is there anything relevant in dmesg?

If I use gdm on fedora 26, then the graphic login screen never shows up. I can only switch to a tty.
If I use lightdm on fedora 26, then most of the time I can reach graphic login screen, but never be able to see the desktop after login.


Here is some dmesg maybe relevant:

[    4.904916] IPv6: ADDRCONF(NETDEV_UP): ens3: link is not ready
[    4.905183] 8139cp 0000:00:03.0 ens3: link up, 100Mbps, full-duplex, lpa 0x05E1
[    5.011953] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    5.066133] Netfilter messages via NETLINK v0.30.
[    5.075573] ip_set: protocol 6
[   13.130010] input: spice vdagent tablet as /devices/virtual/input/input5
[   13.905498] ISO 9660 Extensions: Microsoft Joliet Level 3
[   13.919964] input: spice vdagent tablet as /devices/virtual/input/input6
[   13.932529] ISO 9660 Extensions: RRIP_1991A
[   16.610256] input: spice vdagent tablet as /devices/virtual/input/input7



And here is a similar bug on redhat's bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=1462381
Comment 5 xiaoliniess 2017-08-28 08:40:08 UTC
And AFAIK fedora gdm use wayland and lightdm use xorg by default.
Comment 6 GitLab Migration User 2018-06-03 10:26:56 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/6.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.