Fabio Fantoni wrote: > 2015-04-30 18:55 GMT+02:00 Jim Fehlig <jfeh...@suse.com > <mailto:jfeh...@suse.com>>: > > Fabio Fantoni wrote: > > Il 29/04/2015 18:39, Jim Fehlig ha scritto: > > linux-tyb8:~/ # dmesg | grep -i qxl > [ 4.901158] [drm] qxl: 16M of VRAM memory size > [ 4.901159] [drm] qxl: 63M of IO pages memory ready (VRAM domain) > [ 4.951545] fb: switching to qxldrmfb from VESA VGA > [ 4.951702] fbcon: qxldrmfb (fb0) is primary device > [ 4.976292] qxl 0000:00:04.0: fb0: qxldrmfb frame buffer device > [ 4.976293] qxl 0000:00:04.0: registered panic notifier > [ 4.976296] [drm] Initialized qxl 0.1.0 20120117 for > 0000:00:04.0 on > minor 0 > linux-tyb8:~/ # hwinfo --gfxcard > 16: PCI 04.0: 0300 VGA compatible controller (VGA) > [Created at pci.328] > Unique ID: 8otl.q8E9rb_JDj6 > SysFS ID: /devices/pci0000:00/0000:00:04.0 > SysFS BusID: 0000:00:04.0 > Hardware Class: graphics card > Model: "Red Hat VGA compatible controller" > Vendor: pci 0x1b36 "Red Hat, Inc." > Device: pci 0x0100 > SubVendor: pci 0x1af4 "Red Hat, Inc" > SubDevice: pci 0x1100 > Revision: 0x04 > Driver: "qxl" > Driver Modules: "drm" > Memory Range: 0xf0000000-0xf3ffffff (rw,non-prefetchable) > Memory Range: 0xf4000000-0xf7ffffff (rw,non-prefetchable) > Memory Range: 0xf9050000-0xf9051fff (rw,non-prefetchable) > I/O Ports: 0xc240-0xc25f (rw) > Memory Range: 0xf9040000-0xf904ffff (ro,non-prefetchable,disabled) > IRQ: 32 (150 events) > I/O Ports: 0x3c0-0x3df (rw) > Module Alias: > "pci:v00001B36d00000100sv00001AF4sd00001100bc03sc00i00" > Driver Info #0: > Driver Status: qxl is active > Driver Activation Cmd: "modprobe qxl" > Config Status: cfg=new, avail=yes, need=no, active=unknown > Primary display adapter: #16 > > > With driver installed should always fails with error similar a what I > > reported FWIK. I mean this: > > http://lists.xen.org/archives/html/xen-devel/2015-04/txtGtntonxpzb.txt > > http://lists.xen.org/archives/html/xen-devel/2015-04/msg03064.html > > I'm not seeing that. > > > Or you have domU with qxl driver installed, used and working? In this > > case we must find solution or workaround present in SLES12 and apply > > it also upstream if missed. > > The base system is SLES12, but Xen and the tools (including qemu) are > fairly recent xen-unstable. So the only thing SLES12 specific > would be > domU kernel and qxl driver. > > > Thanks for your reply. > As you told the more probable fix/workaround can be in dom0's kernel > and/or domU's kernel or qxl driver. > I tried to search about qxl suse package 0.1.0 repository (saw version > in your message) but I not understand exactly what repository see.
Jan, or perhaps Olaf or Juergen, might know of a SLES12 kernel change that allows qxl to work. > About kernel I found this for patches added in suse: > https://github.com/openSUSE/kernel-source/tree/SLE12-SP1 > Is it correct? With a fast look I not found patches related FWIK (but > I had low knowledge) > Next week probably I'll try to restrict the search field trying suse > domU in same dom0 I used (wheezy with kernel from backports and other > packages update manually), I can try latest opensuse or is better try > a SLED12 trial instead? > > About xen I take a look here: > https://build.opensuse.org/package/show/Virtualization/xen > I found one patch probably related: > https://build.opensuse.org/package/view_file/Virtualization/xen/stdvga-cache.patch?expand=1 > you used it in your test? No. > > I saw also that there is a patch anymore needed: > https://build.opensuse.org/package/view_file/Virtualization/xen/qemu-xen-enable-spice-support.patch?expand=1 Yes, agreed... > Since this: > http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=9aa2cef51f3dced396a5ae10de586206956f9ffd > is possible to use configure instead: ./configure > --with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir" ...for Xen releases containing this commit. Regards, Jim _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
