From: Mark Schloesser <mark.schloesser@rwth-aachen.de>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com
Subject: Re: [Xen-devel] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
Date: Sun, 06 Sep 2009 17:09:34 +0200 [thread overview]
Message-ID: <4AA3D0AE.2080009@rwth-aachen.de> (raw)
In-Reply-To: <404831.95621.qm@web56104.mail.re3.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 3694 bytes --]
Boris,
actually I used your config. The same config as I used for -rc6 build.
Works just fine for me - but I did not try booting with 3.4.1, only with
xen-unstable.
Mark
Boris Derzhavets wrote:
> Mark,
> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable.
> Looks like i miss some point tuning kernel.
>
> Thanks.
> Boris.
>
> --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
>
> From: Boris Derzhavets <bderzhavets@yahoo.com>
> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de>
> Cc: xen-devel@lists.xensource.com
> Date: Friday, September 4, 2009, 2:02 PM
>
> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support.
> However, attempt to load kernel under Xen 3.4.1 drops
> into stack trace and hangs on both F11 and Ubuntu 9.10.
> Old 2.6.31-rc6's .config file has been used without any changes.
> I can't set up serial console in meantime.
>
> Boris
>
> --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote:
>
> From: Mark Schloesser <mark.schloesser@rwth-aachen.de>
> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: fedora-xen@redhat.com
> Date: Friday, September 4, 2009, 10:26 AM
>
> Hey guys,
>
> I sadly had no luck fixing my X problem. The system seems to run fine
> and as the subject says I moved
> from 3.4.1-3 to xen-unstable. As I am
> already doing fairly bleeding-edge stuff here I thought this would
> probably make most sense.
>
> As I only have an nvs290 gfx card available right now I can't check if
> this is the problem. But I'll try to get my hands on some other cards
> for next week.
>
> Today I read through a lot of mailing list archives and PDFs trying to
> dig deeper into the IOMMU/PCI passthrough stuff and I want to give the
> graphics passthrough situation a shot myself. Sadly it is very confusing
> to read about the different setups and hardware environments with both
> positive and negative results. Also the patchsets and versions everybody
> is talking about do not make it any easier :)
>
> My current questions would be:
> - is the combination of JF git kernel with xen-unstable the right way to
> go for this setup? Or should I perhaps use older xen version and apply
> some patchset? I think some of those
> patches were applied in
> xen-unstable already but I am not quite sure...
>
> - does anyone have hints or clarification regarding the Xorg problem on
> dom0? As I said there are no eye-catching log entries or errors except
> the Xorg backtrace at the end of the log file (posted to list before).
> This happens regardless of which driver I enable (vesa/nv/nouveau). The
> nvidia binary driver compiles without problems and seems to come up but
> only gives me a black screen and also locks the vtys.
>
>
> Thanks to the great help, reports and instructions Boris and others!
>
> Mark
>
>
> -----Inline Attachment Follows-----
>
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2009-09-06 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA12398.1010300@rwth-aachen.de>
2009-09-04 18:02 ` [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Boris Derzhavets
2009-09-04 20:09 ` Jeremy Fitzhardinge
2009-09-05 10:14 ` Boris Derzhavets
2009-09-06 15:09 ` Mark Schloesser [this message]
2009-09-06 15:49 ` Boris Derzhavets
2009-09-06 16:17 ` [Xen-devel] " Mark Schloesser
2009-09-06 16:41 ` Re: [Fedora-xen] " Boris Derzhavets
2009-09-08 13:31 [Xen-devel] " Boris Derzhavets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA3D0AE.2080009@rwth-aachen.de \
--to=mark.schloesser@rwth-aachen.de \
--cc=bderzhavets@yahoo.com \
--cc=fedora-xen@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.