WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480

To: jim burns <jim_burn@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480
From: Flavio <fbcyborg@xxxxxxxxx>
Date: Sun, 13 Nov 2011 10:12:00 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, "Fajar A. Nugraha" <list@xxxxxxxxx>
Delivery-date: Sun, 13 Nov 2011 01:14:02 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lj16RHzCiSsl5KQLVNTCaYcUzpllQPf1cmIV/pEmsjM=; b=wXlBb5y3j95S4IKUZ3sPga9HuBpt90CtIf09OlnO2zahaz0rrfrUGFHTYvn8CSQsfN 21rfZmpIff6hHcrhNWt9FwqFVKagnJQMXovjAoijSmOTS3II9HhRMQC55CodY4jt1oVQ dynF2yLabAu/KEF352u2drSaHrMxG6sv93gF8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2615419.04SAjpCCaA@dell4550>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7877809.94pu0BOf0I@dell4550> <4049100.UHdfztDHBv@dell4550> <CAP8Jb=o3-7v1QJ0zx9-4riTtGjAfN3+7Cp_rP0n84w7aP47iog@xxxxxxxxxxxxxx> <2615419.04SAjpCCaA@dell4550>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 13 November 2011 01:13, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
>
> Sorry - I got busy.
No problem!

> Ok - while the domu is running, let's see the output of
> in dom0: ls -alFR /sys/bus/xen* ; ifconfig ; brctl show ; & netstat -tlp |
> grep 59
These are the outputs produced when the new 3.1.0 kernel is running and the
network is not working:
http://pastebin.com/6yRqnzrh

> in domu: ls -alFR /sys/bus/xen* ; ifconfig
http://pastebin.com/eaiVdHz0

Now I came back to 2.6.37 (network working) so I can use ssh.

> Ok - in domu, post the output of:
> lsmod|egrep 'vesa|cirrus'
cirrusfb               32579  0

> egrep -i 'vesa|cirrus' /boot/config*
/boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_BOOT_VESA_SUPPORT=y
/boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_CIRRUS=m
/boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_UVESA=m
/boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_VESA=y
/boot/config-2.6.37.1-1.2-desktop:CONFIG_SND_HDA_CODEC_CIRRUS=y
/boot/config-3.1.0-1.2-desktop:CONFIG_FB_BOOT_VESA_SUPPORT=y
/boot/config-3.1.0-1.2-desktop:CONFIG_FB_CIRRUS=m
/boot/config-3.1.0-1.2-desktop:CONFIG_FB_UVESA=m
/boot/config-3.1.0-1.2-desktop:CONFIG_FB_VESA=y
/boot/config-3.1.0-1.2-desktop:CONFIG_SND_HDA_CODEC_CIRRUS=y

> ls -alF /sys/bus/pci/devices/0000:00:02.0 (your video device)
lrwxrwxrwx 1 root root 0 Nov 13 09:57
/sys/bus/pci/devices/0000:00:02.0 ->
../../../devices/pci0000:00/0000:00:02.0/

> ls -alF /sys/bus/pci/drivers/{vesa,cirrus}*
ls: cannot access /sys/bus/pci/drivers/vesa*: No such file or directory
/sys/bus/pci/drivers/cirrusfb:
total 0
drwxr-xr-x  2 root root    0 Nov 13 09:57 ./
drwxr-xr-x 23 root root    0 Nov 13 09:57 ../
--w-------  1 root root 4096 Nov 13 09:58 bind
lrwxrwxrwx  1 root root    0 Nov 13 09:58 module -> ../../../../module/cirrusfb/
--w-------  1 root root 4096 Nov 13 09:58 new_id
--w-------  1 root root 4096 Nov 13 09:58 remove_id
--w-------  1 root root 4096 Nov 13 09:57 uevent
--w-------  1 root root 4096 Nov 13 09:58 unbind

> modprobe cirrusfb
module is already loaded but no errors reported.

>
> Let's see which driver is servicing the video card. On my systems, cirrusfb is
> a module, vesa is builtin. Builtins will not show up as a kernel driver in
> lspci -vvv. Then we'll see whether the cirrusfb module gets an error on
> loading.
It seems not during loading even I've found this in the dmesg:
[   32.626308] cirrusfb 0000:00:02.0: BAR 0: can't reserve [mem
0xf0000000-0xf1ffffff pref]
[   32.626312] cirrusfb 0000:00:02.0: cannot reserve region 0xf0000000, abort
[   32.626324] cirrusfb: probe of 0000:00:02.0 failed with error -16

> Hmm - that's an error I would expect with earlier versions of xen. Eg - xen <
> 3.4.0 can't boot a pvops domu, without backported patches. What distribution
> is your dom0, and what xen version?
First of all, I say that my dom0 works like a charm with most of my domUs.
Gentoo Linux x86_64 kernel 3.1.0-gentoo
app-emulation/xen-4.1.2
app-emulation/xen-tools-4.1.2
I'm using xl toolstack.


> Which is what we are checking above.
Mmmh, I think it is not, after having seen the result above :|
Do you agree?

>
> Finally, post your full dmesg from your domu. Maybe something will jump out at
> me.
Yes, here it is: http://pastebin.com/vNpumSik

Thanks a lot,
--
Flavio

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

<Prev in Thread] Current Thread [Next in Thread>