Hi
I don't have a bugzilla report item from this yet, maybe later.
I have now Xen Dom0 Fedora 17 configuration, no experimental packages.
Desktop computer is rather new and supports hardware virtualization, but not IOMMU.
Test: Install paravirtual 64 bit Xen guest, Fedora 17 with HTTP based install.
- With Virt-manager installing went flawlessly.
- After reboot, I got in Finnish with a graphical picture: "Voi ei! Jotain meni pieleen".
This means "Oh no, something got wrong."
So it seems that GDM doesn't work with Xen with default virt-manager settings.
- I can make Login screen by switching from GDM to KDM. Mouse works there:
/etc/sysconfig/desktop: DISPLAYMANAGER=KDE
- From KDM I can start Gnome. Mouse works but Mouse cursor is invisible.
- If I start, via KDM, IceWM, mouse works and is visible.
I don't know if Fedora 18 will have this issue too.
It would be nice if Fedora as Dom0 would just work for Fedora Xen DomU
with default options. Maybe plain AbsoluteAxis for paravirtual mouse
would be the best option, no relative axis enabled by default?
Maybe co-operation with Gnome people is needed to finish this issue?
Regards,
Marko Ristola
Fail case, from guest's /var/log/Xorg.0.log:
[ 182.116] (II) config/udev: Adding input device Xen Virtual Pointer (/dev/input/event1)
[ 182.116] (**) Xen Virtual Pointer: Applying InputClass "evdev pointer catchall"
[ 182.116] (**) Xen Virtual Pointer: Applying InputClass "Xen Virtual Pointer axis blacklist"
[ 182.116] (II) Using input driver 'evdev' for 'Xen Virtual Pointer'
[ 182.116] Option "XkbRules" "evdev"
[ 182.116] Option "XkbModel" "evdev"
[ 182.116] Option "XkbLayout" "us"
[ 182.116] Option "_source" "server/udev"
[ 182.116] Option "name" "Xen Virtual Pointer"
[ 182.116] Option "path" "/dev/input/event1"
[ 182.116] Option "device" "/dev/input/event1"
[ 182.116] Option "config_info" "udev:/sys/devices/virtual/input/input1/event1"
[ 182.116] Option "driver" "evdev"
[ 182.116] Option "IgnoreAbsoluteAxes" "off"
[ 182.116] Option "IgnoreRelativeAxes" "off"
[ 182.116] (**) Xen Virtual Pointer: always reports core events
[ 182.116] (**) evdev: Xen Virtual Pointer: Device: "/dev/input/event1"
[ 182.116] (--) evdev: Xen Virtual Pointer: absolute axis 0 [800..0]
[ 182.116] (--) evdev: Xen Virtual Pointer: absolute axis 0x1 [600..0]
[ 182.116] (--) evdev: Xen Virtual Pointer: Vendor 0x5853 Product 0xfffe
[ 182.116] (**) Option "IgnoreRelativeAxes" "off"
[ 182.116] (**) Option "IgnoreAbsoluteAxes" "off"
[ 182.116] (--) evdev: Xen Virtual Pointer: Found 12 mouse buttons
[ 182.116] (--) evdev: Xen Virtual Pointer: Found scroll wheel(s)
[ 182.116] (--) evdev: Xen Virtual Pointer: Found relative axes
[ 182.116] (--) evdev: Xen Virtual Pointer: Found absolute axes
[ 182.116] (--) evdev: Xen Virtual Pointer: Found x and y absolute axes
[ 182.116] (--) evdev: Xen Virtual Pointer: Found absolute touchscreen
[ 182.116] (II) evdev: Xen Virtual Pointer: Configuring as touchscreen
[ 182.116] (II) evdev: Xen Virtual Pointer: Adding scrollwheel support
[ 182.116] (**) evdev: Xen Virtual Pointer: YAxisMapping: buttons 4 and 5
[ 182.116] (**) evdev: Xen Virtual Pointer: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 182.116] (**) Option "config_info" "udev:/sys/devices/virtual/input/input1/event1"
[ 182.116] (II) XINPUT: Adding extended input device "Xen Virtual Pointer" (type: TOUCHSCREEN, id 7)
[ 182.116] (II) evdev: Xen Virtual Pointer: initialized for relative axes.
[ 182.116] (II) evdev: Xen Virtual Pointer: initialized for absolute axes.
[ 182.116] (**) Xen Virtual Pointer: (accel) keeping acceleration scheme 1
[ 182.116] (**) Xen Virtual Pointer: (accel) acceleration profile 0
[ 182.117] (**) Xen Virtual Pointer: (accel) acceleration factor: 2.000
[ 182.117] (**) Xen Virtual Pointer: (accel) acceleration threshold: 4
[ 182.117] (II) config/udev: Adding input device Xen Virtual Pointer (/dev/input/mouse0)
[ 182.117] (**) Xen Virtual Pointer: Applying InputClass "Xen Virtual Pointer axis blacklist"
[ 182.117] (II) No input driver specified, ignoring this device.
[ 182.117] (II) This device may have been added with another device file.
[ 182.123] (EE) FBDEV(0): FBIOBLANK: Invalid argument