Failure to start X windows in Dom0 under Xen 4.1.2

Failure to start X windows in Dom0 under Xen 4.1.2

[Jan Vejvalka]

Hi *,

   after two unsuccessful attempts to get help on xen-users, I dare to
re-post my problem to zen-devel.
I'll be grateful for any hint.

Trying to run X windows on Linux 3.1.1 Dom0 kernel under Xen 4.1.2
(built as http://slackbuilds.org/repository/13.37/system/xen/) on
Slackware 64-13.37. (The next step should be a HVM guest driven through
a vnc window from Dom0).

On the same kernel booted natively, all works fine; when booting under
Xen, Xorg does not start. The (relevant?) error messages that I find in
Xorg.0.log are

(WW) System lacks support for changing MTRRs
(EE) VESA(0): V_BIOS address 0x0 out of range

(the full diff of the respective Xorg.0.log-s is at
http://camelot.lf2.cuni.cz/vejvalka/posts/xlog-diff)

What is it that I am missing ?
Thanks for any hint,

Jan

Re: Failure to start X windows in Dom0 under Xen 4.1.2

[Konrad Rzeszutek Wilk]

On Wed, Dec 14, 2011 at 07:12:53PM +0100, Jan Vejvalka wrote:
> Hi *,
> 
>   after two unsuccessful attempts to get help on xen-users, I dare to
> re-post my problem to zen-devel.
> I'll be grateful for any hint.

I am going to need some more details
[http://wiki.xen.org/xenwiki/XenParavirtOpsHelp.html]

If you can't get the full serial console, you can give the 'xl dmesg'
and 'dmesg' output.

Also did you look in:
http://wiki.xen.org/xenwiki/XenParavirtOps.html#head-214e7c90d504695bacd261fbeed67f6a0d1e73a7

and
http://wiki.xen.org/xenwiki/XenParavirtOps.html#head-9fb34d1cf597800d371b844568797d4db8587dce

> 
> Trying to run X windows on Linux 3.1.1 Dom0 kernel under Xen 4.1.2
> (built as http://slackbuilds.org/repository/13.37/system/xen/) on
> Slackware 64-13.37. (The next step should be a HVM guest driven through
> a vnc window from Dom0).
> 
> On the same kernel booted natively, all works fine; when booting under
> Xen, Xorg does not start. The (relevant?) error messages that I find in
> Xorg.0.log are
> 
> (WW) System lacks support for changing MTRRs
> (EE) VESA(0): V_BIOS address 0x0 out of range
> 
> (the full diff of the respective Xorg.0.log-s is at
> http://camelot.lf2.cuni.cz/vejvalka/posts/xlog-diff)
> 
> What is it that I am missing ?

>From a first glance it looks as if the KMS drivers hadn't been loaded -
but I don't know which ones (since I don't know what drivers you have).

> Thanks for any hint,
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Failure to start X windows in Dom0 under Xen 4.1.2

[Konrad Rzeszutek Wilk]

On Tue, Dec 20, 2011 at 09:25:21AM -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 20, 2011 at 06:44:03AM +0100, Jan Vejvalka wrote:
> > Dear Konrad,
> > 
> >   thank you for your interest.
> 
> Please don't top post.

And do not remove the xen-devel from the CC. I put it back in this
email.

> > 
> > In the meantime, I found a post that helped at least partially:
> > http://forums.gentoo.org/viewtopic-t-901234-start-0.html .
> > 
> > I added the nopat option to grub, and things got a bit better.
> > I moved one step further, now facing a somewhat different problem:
> > 
> > - on my 3.1.1 kernel without Xen, things work fine
> 
> Can you provide the dmesg of that please.
> 
> I am curious to see why you have:
> 
> [    2.967316] [drm] VGACON disable radeon kernel modesetting.
> 
> Can you also boot the baremetal (so without Xen) and with Xen
> with: "drm.debug=255" and remove the "nomodeset" option on the Linux
> command line?
> 
> Uou are also missing the "debug loglevel=8" options. I need those to
> get a better idea of why the radeon driver is not initializing properly.
> 
> > - on the same kernel with Xen, the first (and sometimes even some
> >     further) attempts to run startx fail
> > - after a couple of tries, startx finally succeeds if the kernel
> >     is loaded with the nopat parameter
> > - without the nopat parameter, it seems it does not work: in the best
> >     attempts, the screen enters the graphic mode for a short while
> >     before the final crash.
> > 
> > The info you asked for is at
> > http://camelot.lf2.cuni.cz/vejvalka/temp/kon .
> > 
> > Thanks for help
> > Dziekuje bardzo
> 
> Oczywiscie.

Re: Failure to start X windows in Dom0 under Xen 4.1.2

[Jan Vejvalka]

On 20.12.2011 15:26, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 20, 2011 at 09:25:21AM -0500, Konrad Rzeszutek Wilk wrote:
>> On Tue, Dec 20, 2011 at 06:44:03AM +0100, Jan Vejvalka wrote:

>> In the meantime, I found a post that helped at least partially:
>> http://forums.gentoo.org/viewtopic-t-901234-start-0.html .
>>
>> I added the nopat option to grub, and things got a bit better.
>> I moved one step further, now facing a somewhat different problem:
>>
>> - on my 3.1.1 kernel without Xen, things work fine
>
> Can you provide the dmesg of that please.
>
> I am curious to see why you have:
>
> [    2.967316] [drm] VGACON disable radeon kernel modesetting.
>
> Can you also boot the baremetal (so without Xen) and with Xen
> with: "drm.debug=255" and remove the "nomodeset" option on the Linux
> command line?
> Uou are also missing the "debug loglevel=8" options. I need those to
> get a better idea of why the radeon driver is not initializing properly.

See http://camelot.lf2.cuni.cz/vejvalka/temp/kon2 . Missing firmware.
Just distorted graphics came up on the console after boot in both cases.

Found the R600_rlc.bin at
http://people.freedesktop.org/~agd5f/radeon_ucode (as linked from
http://www.x.org/wiki/radeonBuildHowTo ) ... and things started
working, also the X windows start under Xen at the first attempt,
even without the nopat kernel option.

See logs at http://camelot.lf2.cuni.cz/vejvalka/temp/kon3 .

Thanks !

Jan

>> - on the same kernel with Xen, the first (and sometimes even some
>>      further) attempts to run startx fail
>> - after a couple of tries, startx finally succeeds if the kernel
>>      is loaded with the nopat parameter
>> - without the nopat parameter, it seems it does not work: in the best
>>      attempts, the screen enters the graphic mode for a short while
>>      before the final crash.
>>
>> The info you asked for is at
>> http://camelot.lf2.cuni.cz/vejvalka/temp/kon .