thr3ads.net - Xen users - [Xen-users] X11 in PV domU: limited success [Jan 2008]

If this information is useful, please help other people find it:
Share via:

Chris Epicier

2008-Jan-18 20:18 UTC

[Xen-users] X11 in PV domU: limited success

Hi there 
My goal is to have a server in one boxe with (at the
moment) one single X11 client. 

Part success with this setup:
Athlon 1300, MSI KT6 delta, 2 G Ram, Suse 10.3
(2.6.22.13-0.3-xenpae), updated 1 hour ago, throughout
the whole setup, LVM, dom0 has a pci graphics card, I
have delegated a matrox G450 AGP graphics card and a
USB controller to a dom U called xlic. I attached a
USb mouse and USB keyboard to it. 
 - xm create xlic => OK
 - ssh -l root xlic
 - sax2 -r
the monitor attached to the G450 inits in the typical
grey and blue colours but nothing is readable. loocks
like a clock problem. I move the mouse, a pattern on
the screen moves accordingly, I hit some keys (tab), I
see some effect at the location I would expect on the
screen.
=> I''d consider this a starting point, given the
rather outdated hardware. 
 - ^C and sax stops. above is reproducible, despite
some mm.c:690 messsages.

So, where do I need to go from here to get it to work?

greets chris

PS: I should mention, I have tested the hardware
desvribed using a second isntall: it works. I have a
couple of boxes at hand and am willing to try it on
many if not all of them, like
- AMD AM2 X86-64, Asus M2N32 WS Pro 4-8 GRam 
- Intel P4 systems, various MB''s, Ram up to 1G



        __________________________________  Ihr erstes Baby? Holen Sie sich
Tipps von anderen Eltern.  www.yahoo.de/clever

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Chris Epicier

2008-Feb-17 09:29 UTC

head link

[Xen-users] Re: X11 in PV domU: limited success

Hi

In this thread
http://lists.xensource.com/archives/html/xen-users/2008-01/msg00516.html
I achieved partial success with an AGP Matrox G400
graphics card. I switched tha card against a pci
Geeforce MX2. Could configure it straight away by
sax2, so it''s up an running now. 

By chance that was the primary graphics card where
dom0 and boot messages were displayed on. I used
/etc/init.d/boot.local script like that to ''steal'' the
card from dom0 this way:

echo -n 0000:00:06.0 >  /sys/bus/pci/drivers/nv/unbind
echo -n 0000:00:06.0 > 
/sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:00:06.0 > 
/sys/bus/pci/drivers/pciback/bind
echo -n 0000:00:06.0 > 
/sys/bus/pci/drivers/pciback/permissive

Actually dom0 is running in textmode only, so no nv
module was loaded.

Now i''d like to move on to an AGP card (01:00.0). I
believe, domU should receive control of the AGP bridge
somehow. lspci in my dom0 looks like that

00:00.0 Host bridge: VIA Technologies, Inc. VT8377
[KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI
Bridge
00:06.0 VGA compatible controller: nVidia Corporation
NV11 [GeForce2 MX/MX 400] (rev b2)
00:07.0 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:07.1 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:07.2 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:07.3 USB Controller: ALi Corporation USB 2.0
Controller (rev 01)
00:08.0 VGA compatible controller: Trident
Microsystems 3DImage 9750 (rev f3)
00:0b.0 Ethernet controller: Broadcom Corporation
NetXtreme BCM5788 Gigabit Ethernet (rev 03)
00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc.
IEEE 1394 Host Controller (rev 46)
00:0f.0 RAID bus controller: VIA Technologies, Inc.
VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master
IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0
(rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA
bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies,
Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
01:00.0 VGA compatible controller: nVidia Corporation
NV44A [GeForce 6200] (rev a1)

how can I give the AGP slot (dunno if it is the right
term) to domU?

greets chris


       __________________________________  Ihre erste Baustelle? Wissenswertes
für Bastler und Hobby Handwerker. www.yahoo.de/clever

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2008-Feb-18 02:17 UTC

head link

Re: [Xen-users] Re: X11 in PV domU: limited success

On Feb 17, 2008 4:29 AM, Chris Epicier <seuchato@yahoo.de> wrote:
> Hi
>
> In this thread
> http://lists.xensource.com/archives/html/xen-users/2008-01/msg00516.html
> I achieved partial success with an AGP Matrox G400
> graphics card. I switched tha card against a pci
> Geeforce MX2. Could configure it straight away by
> sax2, so it''s up an running now.
>
> By chance that was the primary graphics card where
> dom0 and boot messages were displayed on. I used
> /etc/init.d/boot.local script like that to ''steal'' the
> card from dom0 this way:
>
> echo -n 0000:00:06.0 >  /sys/bus/pci/drivers/nv/unbind
> echo -n 0000:00:06.0 >
> /sys/bus/pci/drivers/pciback/new_slot
> echo -n 0000:00:06.0 >
> /sys/bus/pci/drivers/pciback/bind
> echo -n 0000:00:06.0 >
> /sys/bus/pci/drivers/pciback/permissive
>
> Actually dom0 is running in textmode only, so no nv
> module was loaded.
>
> Now i''d like to move on to an AGP card (01:00.0). I
> believe, domU should receive control of the AGP bridge
> somehow. lspci in my dom0 looks like that
>
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8377
> [KT400/KT600 AGP] Host Bridge (rev 80)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI
> Bridge
> 00:06.0 VGA compatible controller: nVidia Corporation
> NV11 [GeForce2 MX/MX 400] (rev b2)
> 00:07.0 USB Controller: ALi Corporation USB 1.1
> Controller (rev 03)
> 00:07.1 USB Controller: ALi Corporation USB 1.1
> Controller (rev 03)
> 00:07.2 USB Controller: ALi Corporation USB 1.1
> Controller (rev 03)
> 00:07.3 USB Controller: ALi Corporation USB 2.0
> Controller (rev 01)
> 00:08.0 VGA compatible controller: Trident
> Microsystems 3DImage 9750 (rev f3)
> 00:0b.0 Ethernet controller: Broadcom Corporation
> NetXtreme BCM5788 Gigabit Ethernet (rev 03)
> 00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc.
> IEEE 1394 Host Controller (rev 46)
> 00:0f.0 RAID bus controller: VIA Technologies, Inc.
> VIA VT6420 SATA RAID Controller (rev 80)
> 00:0f.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master
> IDE (rev 06)
> 00:10.0 USB Controller: VIA Technologies, Inc.
> VT82xxxxx UHCI USB 1.1 Controller (rev 81)
> 00:10.1 USB Controller: VIA Technologies, Inc.
> VT82xxxxx UHCI USB 1.1 Controller (rev 81)
> 00:10.2 USB Controller: VIA Technologies, Inc.
> VT82xxxxx UHCI USB 1.1 Controller (rev 81)
> 00:10.3 USB Controller: VIA Technologies, Inc.
> VT82xxxxx UHCI USB 1.1 Controller (rev 81)
> 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0
> (rev 86)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA
> bridge [KT600/K8T800/K8T890 South]
> 00:11.5 Multimedia audio controller: VIA Technologies,
> Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
> 01:00.0 VGA compatible controller: nVidia Corporation
> NV44A [GeForce 6200] (rev a1)
>
> how can I give the AGP slot (dunno if it is the right
> term) to domU?
>


Did you try pci=[''0000:00:06.0''] in the domU config?




>
> greets chris
>
>
>       __________________________________  Ihre erste Baustelle?
> Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Chris Epicier

2008-Feb-18 05:49 UTC

head link

Re: [Xen-users] Re: X11 in PV domU: limited success => SOLVED!

Hi Todd

got it sorted out meanwhile!

> Did you try pci=[''0000:00:06.0''] in the domU config?
yes I did but 0000:00:06.0 (lspci on dom0) is the pci
card. The AGP card 01:00.0 (lspci on dom0). To get it
all up and running using nv I do:

in boot.local:
*************
slot=0000:01:00.0
driver=nv
#not really needed if no nv module is loaded
echo -n $slot >  /sys/bus/pci/drivers/$driver/unbind
#these are a must
echo -n $slot >  /sys/bus/pci/drivers/pciback/new_slot
echo -n $slot >  /sys/bus/pci/drivers/pciback/bind
#need to verify, if this is really required
echo -n $slot > 
/sys/bus/pci/drivers/pciback/permissive
*************
did it work?
*********
dmesg | grep seiz
pciback 0000:00:06.0: seizing device
pciback 0000:00:07.0: seizing device
pciback 0000:00:07.1: seizing device
pciback 0000:00:07.2: seizing device
pciback 0000:00:07.3: seizing device
pciback 0000:01:00.0: seizing device
*********

yess, so the domU config looks like that:
*********
name = "xlic"
kernel = "/boot/vmlinuz-xenpae"
ramdisk = "/boot/initrd-xenpae"
memory = 512
vif = [ ''mac=aa:cc:00:00:00:01, bridge=xenbr0'' ]
disk = [ ''phy:system/xlic,hda1,w'' ]
root = "/dev/hda1 rw"
#once successful, change to
#extra = "5"
extra = "3"
# remove xencons=tty to avoid xorg missing VT message
and subsequent death of xorg
#extra = "3 xencons=tty"
# activate for pci GF2 MX
#pci = [
''00:06.0'',''00:07.0'',''00:07.1'',''00:07.2'',''00:07.3''
]
# activate for AGP GF 6200
pci = [
''01:00.0'',''00:07.0'',''00:07.1'',''00:07.2'',''00:07.3''
]
*********

check card delegation inside domU:
*********
lspci
00:00.0 VGA compatible controller: nVidia Corporation
NV44A [GeForce 6200] (rev a1)
00:01.0 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:01.1 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:01.2 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
00:01.3 USB Controller: ALi Corporation USB 2.0
Controller (rev 01)
*********
USB has mouse and keyboard attached, 
configuring xorg using sax2:
*********
sax2 -rp 
Chip: 0  is -> NVidia GeForce 6200 (0x0221)    
00:00:0 0x10de 0x0221 PCI nv
sax2 -r
SaX: initializing please wait...
SaX: your current configuration will not be read in

SaX: no X-Server is running
SaX: will start own server if needed
SPP: prepare device [0] profile: NoModelines
SPP: including prepared profile(s)...

SaX: startup
*********
Once you have the grafical screen up, it''s time to
yodel: you have made it. Then change/adjust your
settings ccordingly, finally
**********
init 5
*********
Thats a full blown success! ok there is no 3D but that
was not the aim so far (now it is!:-])

greets chris


      Heute schon einen Blick in die Zukunft von E-Mails wagen?
www.yahoo.de/mail

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Chris Epicier

2008-Feb-24 06:39 UTC

head link

[Xen-users] X11 in PV domU on AMD X2 64

Hi all

after my success with a rather outdated system (see
http://lists.xensource.com/archives/html/xen-users/2008-02/msg00643.html),
i tried on a new box:

Asus M2N WS Pro, Athlon 64 X2 4600+, 4G Ram, 3x Sata
Raid 5, LVM, Suse 10.3, kernel 2.6.22.17-0.1-xen SMP
i686 athlon i386 GNU/Linux, xen 3.1

lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation
GeForce 8600 GT (rev a1)
02:06.0 VGA compatible controller: ATI Technologies
Inc 264VT [Mach64 VT] (rev 40)

hidden away from  to dom0 through
/etc/init.d/boot.local:

    # hide 8600 GT so it can be used in domU (not
activated as of 080117)
    slot=0000:01:00.0
    echo -n $slot >
/sys/bus/pci/drivers/pciback/new_slot
    echo -n $slot > /sys/bus/pci/drivers/pciback/bind
    echo -n $slot >
/sys/bus/pci/drivers/pciback/permissive

    #02:06.0 VGA compatible controller: ATI
Technologies Inc 264VT [Mach64 VT] (rev 40)
    slot=0000:02:06.0
    echo -n $slot >
/sys/bus/pci/drivers/pciback/new_slot
    echo -n $slot > /sys/bus/pci/drivers/pciback/bind
    echo -n $slot >
/sys/bus/pci/drivers/pciback/permissive

domU config

name = "lic"
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
memory = 512
vif = [ ''mac=aa:cc:00:00:00:CA, bridge=xenbr0'' ]
disk = [ ''phy:system/lic-32bit,hda1,w'' ]
root = "/dev/hda1 rw"
#remove xencons=tty to avoid VT errors when starting X
#extra = "3 xencons=tty"
extra = "3"
# nVidia Corporation GeForce 8600 GT
# pci = [
''01:00.0'',''00:0a.0'',''00:0a.1'',''00:0e.0'',''00:0e.1''
]
# ATI Technologies Inc 264VT [Mach64 VT]
pci = [
''02:06.0'',''00:0a.0'',''00:0a.1'',''00:0e.0'',''00:0e.1''
]

in above sample the ATI Mach64 VT is delegated to
domU.
sax2 -rp
Chip: 0  is -> ATI Mach64 VT                   
00:00:0 0x1002 0x5654 PCI ati 
sax2 -r
SaX: initializing please wait...
SaX: no X-Server is running
SaX: will start own server if needed
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.
ISaX: could not import file:
/var/cache/sax/files/config at /usr/sbin/isax line
199.

SaX: startup

xc: sorry could not start configuration server
xc: for details refer to the log file:

    /var/log/SaX.log

xc: abort...

tail /var/logSaX.log
        (II) Module int10: vendor="X.Org Foundation"
        compiled for 7.2.0, module version = 1.0.0
        ABI class: X.Org Video Driver, version 1.2
        (EE) ATI(0): Cannot map SYS BIOS
        (WW) ATI(0): Unable to initialise int10
interface.

        Fatal server error:
        xf86MapVidMem: Could not mmap framebuffer
(0x000a0000,0x10000) (Bad address)

I get a similar error when delegating the 8600 GT to
the domU (Jfyi: the delegation works as described
above, but with 01:00.0 instead of 02:06.0. pci
delegation works for sound and usb):


tail Xorg.0.log.old
(II) NV(0): Initializing int10
(EE) NV(0): Cannot map SYS BIOS
(EE) NV(0): Failed to initialize the int10 module;
this screen will not be initialized.
(II) UnloadModule: "nv"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/xorg/modules//libint10.so
(EE) Screen(s) found, but none have a usable
configuration.

Fatal server error:
no screens found


It looks as video memory is not accessible in domU. Do
I have to set some quirky stuff? If so where and what?

greets chris




      Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel
mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Chris Epicier

2008-Mar-07 13:36 UTC

head link

[Xen-users] native X11 in domU: proposal to collect what works systematically

Hi there

Emre and Stefan have probably figured out a working
combination of hardware and driver / distro
combination for getting X11 up running in domU (see
http://lists.xensource.com/archives/html/xen-users/2007-09/msg00091.html).
So have I (see
http://lists.xensource.com/archives/html/xen-users/2008-02/msg00643.html).

I thought, it would be valuable source of info, if we
could have one thread that lists what is working and
how it was set up to work. I would volunteer to
collect that data, first here, then hopefully add it
in the xen wiki.

I believe the following data should be made available:

- Hardware used: 
  - Mobo
  - ram 
  - cpu(s)
  - eventually bios version
- distro used
  - distro name
  - basic setup info like main partition arrangement, 
    boot loader
  - dom0 and domU config:
    - uname -a output 
    - allocated ram
    - way GPU has been passed to domU
    - xm config file used to boot domU
    - driver for CPU used in domU
    - X11.conf (relevant parts only)
  - short statement / comment how, what works, hints 

I will try to analise that data and find the commons
and throw it back on a +/- digested form.

greets chris


      E-Mails jetzt auf Ihrem Handy.
www.yahoo.de/go

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Jan 2008 - X11 in PV domU: limited success

[Xen-users] X11 in PV domU: limited success

[Xen-users] Re: X11 in PV domU: limited success

Re: [Xen-users] Re: X11 in PV domU: limited success

Re: [Xen-users] Re: X11 in PV domU: limited success => SOLVED!

[Xen-users] X11 in PV domU on AMD X2 64

[Xen-users] native X11 in domU: proposal to collect what works systematically