4:33 p.m.
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
4:42 p.m.
On Tue, 30 Oct 2012, Marko Ristola wrote:
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.
It could be https://bugzilla.redhat.com/show_bug.cgi?id=810040
try removing the fprintd package (plus fprintd-pam I think for
dependencies)
- 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?
I see the invisible cursor as well, though I have never got around to
raising a bug for it for some reason. It seems to be peculiar to gnome
(and not gnome on ubuntu 10.0.4), for example the cursor is shown on text
screens before gnome starts.
Michael Young
12:51 p.m.
30.10.2012 23:42, M A Young kirjoitti:
On Tue, 30 Oct 2012, Marko Ristola wrote:
> 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.
It could be https://bugzilla.redhat.com/show_bug.cgi?id=810040
try removing the fprintd package (plus fprintd-pam I think for dependencies)
> - 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?
I see the invisible cursor as well, though I have never got around to raising a bug for
it for some reason. It seems to be peculiar to gnome (and not gnome on ubuntu 10.0.4), for
example the cursor is shown on text screens before gnome starts.
Michael Young
yum remove fprintd fprintd-pam removed the "Gnome oops".
Now in both GDM and Gnome cursor works, but is invisible.
I think fprintd problem is just a side effect. I think that
Xen folks have already reported the problem.
Underlying problem might be related with this Bugzilla issue:
https://bugzilla.redhat.com/show_bug.cgi?id=523914
According to that Bugzilla entry, Xen PV mouse should advertice itself
only as delivering Absolute events. It should not advertice or deliver relative events.
Then Xen PV driver could be made to work with XOrg evdev events.
Why the Oops comes on GDM with fprintd?
It seems related with following on my Xorg.0.log:
"182.117] (**) Xen Virtual Pointer: Applying InputClass "Xen Virtual Pointer
axis blacklist"
Maybe blacklisting or similar issue is detected or done some way deep within GDM, I
don't know where:
/var/log/messages: Oct 31 18:20:02 f17xen dbus-daemon[538]: ** (fprintd:1096): WARNING **:
fprint i
nit failed with error -99
The Xen PV mouse driver behaviour would better to get fixed.
I don't know how many Fedora users have an active IOMMU: hardware IOMMU would
allow using a real mouse device after hacking.
Fedora Xen would benefit if virt-manager DomU install would work out of the box.
Regards,
Marko Ristola
1:12 p.m.
On Wed, 2012-10-31 at 19:51 +0200, Marko Ristola wrote:
Fedora Xen would benefit if virt-manager DomU install would work out
of the box.
Mmm... You're still talking about F17 right?
I'm asking because I remember the fprintd thing being an issue there.
However, I'm testing F18 beta from a couple of days and I can testify
virt-install and virt-manager _really_are_ working out of the box! :-)
Basically, what I did was just installing the OS, then installing Xen
and the tools (e.g., as described here:
http://wiki.xen.org/wiki/Fedora_Test_Days
or here:
http://wiki.xen.org/wiki/Fedora_Host_Installation ).
After that I was able to start creating guests, and all is working ok.
What is it that is not working 'out of the box' for you?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
3:39 p.m.
31.10.2012 20:12, Dario Faggioli kirjoitti:
On Wed, 2012-10-31 at 19:51 +0200, Marko Ristola wrote:
> Fedora Xen would benefit if virt-manager DomU install would work out of the box.
>
Mmm... You're still talking about F17 right?
Yes: I thought that I might not be able to install F18 test environment in time,
so I decided to check how F17 works.
The Live CD that you published today sounds to be an easy way to test Xen.
I'm asking because I remember the fprintd thing being an issue there.
However, I'm testing F18 beta from a couple of days and I can testify
virt-install and virt-manager _really_are_ working out of the box! :-)
Yes, F17 has the problem.
So it sounds then that the Mouse issue don't exist anymore on F18.
Basically, what I did was just installing the OS, then installing Xen
and the tools (e.g., as described here:
http://wiki.xen.org/wiki/Fedora_Test_Days
or here:
http://wiki.xen.org/wiki/Fedora_Host_Installation ).
After that I was able to start creating guests, and all is working ok.
What is it that is not working 'out of the box' for you?
F17, virt-manager, with no special selections, network HTTP install.
GDM doesn't work, no login page to enter username and password.
I'll consentrate on F18 too.
Regards,
Dario
Regards,
Marko
4199
days inactive
4200
days old
4 comments
3 participants
participants (3)
-
Dario Faggioli -
M A Young -
Marko Ristola