[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable


  • To: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Tue, 8 Sep 2009 08:20:54 -0700 (PDT)
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
  • Delivery-date: Tue, 08 Sep 2009 08:21:21 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=QoS+NjhRHmT4RuEl0z31XIMwXvuXt1j01yhOpNFdZvZG5jFxRQVOoltBsbb9Ta0760PzYzlNBfRxfUJAL5byQfuQVzKJJUfE1Rki6q6GlBHUX6I1b5zJHKQaF2riOdEqFQ0tsYXNtmxHyVDq6ZsZg5jtAPuYQ4xaTYrjrPDqODo=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

That's a working grub entry :

title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
  root (hd1,0)
  kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all
  module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
  module /initrd-2.6.31-rc8.img

B.

--- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Mark Schloesser" <mark.schloesser@xxxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
Date: Tuesday, September 8, 2009, 9:31 AM

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:-

title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
  root (hd1,0)
  kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
  module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen
  module /initrd-2.6.31-rc8.img

Then disconnected NUL modem cable and loaded Dom0 via :

title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
  root (hd1,0)
  kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
  module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
  module /initrd-2.6.31-rc8.img

Usual Grub entry drops console to stack trace.
Dmesg output is attached.

Boris.
--- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx> wrote:

From: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: fedora-xen@xxxxxxxxxx
Date: Tuesday, September 8, 2009, 8:13 AM

Top commit in my checkout is:

commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
Date:   Thu Sep 3 16:25:12 2009 -0700

Mark


Boris Derzhavets wrote:
> Yep ;)
>
> Please, run
> # git log|more
> in linux-2.6-xen ( obtained via git clone).
> I am wondering what was the top commit for good build 2.6.31-rc8
> I am trying to bisect.
>
> Boris.
>
>
> --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx> wrote:
>
> From: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
> Date: Sunday, September 6, 2009, 12:17 PM
>
> I am on standard F11, using a fresh install and then updated all
> packages before doing anything xen related. Xen build was done with
> current xen-unstable checkout using only "xen" and "tools" build
> targets. I have no libvirt or libvirt-preview currently. My Xorg still
> does not want to come up btw :)
>
> Do you need anything else?
>
> Mark
>
>
>
>
>
>
>



-----Inline Attachment Follows-----


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.