Console output with pv_ops kernel

Console output with pv_ops kernel

[jonr]

I am trying to get my Xen-3.4-unstable with 2.6.29-rc3-tip to output  
to the console after Xen releases control back to the kernel. I can  
see the Xen portion but as soon as it scrubs memory it goes to a blank  
screen. It will boot up but I will never see a login prompt. I have to  
ssh into the box.

I have tried various options for grub but have not found the correct  
combination as of yet. Here is what I have for my menu.lst:

This is the latest incantation:

title Xen 3.4 / kernel 2.6.29-tip-rc3
   root(hd0,0)
   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0  
earlyprintk=xen pci=nomsi
   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz

====
Also:
====
title Xen 3.4 / kernel 2.6.29-tip-rc3
   root(hd0,0)
   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0  
earlyprintk=xen pci=nomsi
   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz


Has anybody gotten this to output to the screen? Is there some magic  
that I am missing?

Thanks for any advice,

Jon

Re: Console output with pv_ops kernel

[Jeremy Fitzhardinge]

jonr@destar.net wrote:
> I am trying to get my Xen-3.4-unstable with 2.6.29-rc3-tip to output 
> to the console after Xen releases control back to the kernel. I can 
> see the Xen portion but as soon as it scrubs memory it goes to a blank 
> screen. It will boot up but I will never see a login prompt. I have to 
> ssh into the box.
>
> I have tried various options for grub but have not found the correct 
> combination as of yet. Here is what I have for my menu.lst:
>
> This is the latest incantation:
>
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 
> earlyprintk=xen pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
>
> ====
> Also:
> ====
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 
> earlyprintk=xen pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
>
>
> Has anybody gotten this to output to the screen? Is there some magic 
> that I am missing?
>

This should work if you're using a serial console.  Otherwise, you can 
use a vga console; I use:

title xen-unstable pvops
        kernel /xen-3.gz loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00 ignore_loglevel pci=nomsi earlyprintk=vga console=tty0 
        module /initrd-2.6.29-rc5-tip.img


    J

How to build vmlinuz-2.6.29-rc5-tip ?

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 2827 bytes --]

>title xen-unstable pvops
>       kernel /xen-3.gz loglvl=all guest_loglvl=all
>       module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00
> ignore_loglevel pci=nomsi earlyprintk=vga console=tty0
>  module  /initrd-2.6.29-rc5-tip.img
>   J


I was able to reproduce http://people.redhat.com/mingo/tip.git/README:-

mkdir linux.trees.git || exit -1
cd linux.trees.git

git init
# Add Linus's tree as a remote
git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the -tip tree as a remote
git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
git remote update
git checkout -b tip-latest tip/master

"make menuconfig" doesn't show options for Xen Dom0 support
"make" builds  vmlinuz-2.6.29-rc5-tip, but it's useless.

Sorry, to bother you . It's unknown for myself at least 
how to build kernel via git now . Git repos at kernel.org have
been modified.

Boris




-- On Mon, 2/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Console output with pv_ops kernel
To: jonr@destar.net
Cc: xen-devel@lists.xensource.com
Date: Monday, February 16, 2009, 5:53 PM

jonr@destar.net wrote:
> I am trying to get my Xen-3.4-unstable with 2.6.29-rc3-tip to output to
the console after Xen releases control back to the kernel. I can see the Xen
portion but as soon as it scrubs memory it goes to a blank screen. It will boot
up but I will never see a login prompt. I have to ssh into the box.
> 
> I have tried various options for grub but have not found the correct
combination as of yet. Here is what I have for my menu.lst:
> 
> This is the latest incantation:
> 
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 earlyprintk=xen
pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
> 
> ====
> Also:
> ====
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 earlyprintk=xen
pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
> 
> 
> Has anybody gotten this to output to the screen? Is there some magic that
I am missing?
> 

This should work if you're using a serial console.  Otherwise, you can use
a vga console; I use:

title xen-unstable pvops
       kernel /xen-3.gz loglvl=all guest_loglvl=all
       module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00
ignore_loglevel pci=nomsi earlyprintk=vga console=tty0        module
/initrd-2.6.29-rc5-tip.img


   J

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



      

[-- Attachment #1.2: Type: text/html, Size: 3471 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: How to build vmlinuz-2.6.29-rc5-tip ?

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 7162 bytes --]

Another try:-
root@ServerXen331:/usr/src# mkdir linux.trees.git || exit -1
root@ServerXen331:/usr/src# cd linux.trees.git
root@ServerXen331:/usr/src/linux.trees.git# git init
Initialized empty Git repository in /usr/src/linux.trees.git/.git/
root@ServerXen331:/usr/src/linux.trees.git# git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
root@ServerXen331:/usr/src/linux.trees.git# git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
root@ServerXen331:/usr/src/linux.trees.git# git remote update
Updating linus
warning: no common commits
remote: Counting objects: 1068144, done.
remote: Compressing objects: 100% (178196/178196), done.
remote: Total 1068144 (delta 890175), reused 1062206 (delta 885050)
Receiving objects: 100% (1068144/1068144), 258.76 MiB | 26 KiB/s, done.
Resolving deltas: 100% (890175/890175), done.

. . . . . . . . . . 


Updating tip
remote: Counting objects: 19569, done.
remote: Compressing objects: 100% (7482/7482), done.
remote: Total 18172 (delta 14981), reused 12843 (delta 10122)
Receiving objects: 100% (18172/18172), 3.54 MiB | 107 KiB/s, done.
Resolving deltas: 100% (14981/14981), completed with 1157 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen
 * [new branch]      acpi/map   -> tip/acpi/map
 * [new branch]      mainline/mm -> tip/mainline/mm
 * [new branch]      mainline/net -> tip/mainline/net
 * [new branch]      master     -> tip/master
 * [new branch]      push/xen/dom0/core -> tip/push/xen/dom0/core
 * [new branch]      tip/fixups -> tip/tip/fixups
 * [new branch]      x86/apic   -> tip/x86/apic
 * [new branch]      x86/cpa    -> tip/x86/cpa
 * [new branch]      x86/unify  -> tip/x86/unify
 * [new branch]      x86/unify-base -> tip/x86/unify-base
 * [new branch]      x86/unify-irq -> tip/x86/unify-irq
 * [new branch]      x86/unify-irq-base -> tip/x86/unify-irq-base
 * [new branch]      x86/unify-kmemcheck -> tip/x86/unify-kmemcheck
 * [new branch]      x86/unify-kmemcheck-base -> tip/x86/unify-kmemcheck-base
 * [new branch]      x86/untangle -> tip/x86/untangle
 * [new branch]      x86/untangle2 -> tip/x86/untangle2
 * [new branch]      xen/core   -> tip/xen/core
 * [new branch]      xen/dev-evtchn -> tip/xen/dev-evtchn
 * [new branch]      xen/dom0/apic -> tip/xen/dom0/apic
 * [new branch]      xen/dom0/backend/blkback -> tip/xen/dom0/backend/blkback
 * [new branch]      xen/dom0/backend/core -> tip/xen/dom0/backend/core
 * [new branch]      xen/dom0/backend/netback -> tip/xen/dom0/backend/netback
 * [new branch]      xen/dom0/core -> tip/xen/dom0/core
 * [new branch]      xen/dom0/hackery -> tip/xen/dom0/hackery
 * [new branch]      xen/dom0/mtrr -> tip/xen/dom0/mtrr
 * [new branch]      xen/dom0/pci -> tip/xen/dom0/pci
 * [new branch]      xen/dom0/swiotlb -> tip/xen/dom0/swiotlb
 * [new branch]      xen/dom0/xenfs -> tip/xen/dom0/xenfs
 * [new branch]      xen/frontend/blkfront -> tip/xen/frontend/blkfront
 * [new branch]      xen/fs     -> tip/xen/fs
 * [new branch]      xen/hg-queue-import -> tip/xen/hg-queue-import
 * [new branch]      xen/irq    -> tip/xen/irq
 * [new branch]      xen/master -> tip/xen/master
 * [new branch]      xen/pvhvm  -> tip/xen/pvhvm
 * [new branch]      xen/xenbus -> tip/xen/xenbus

root@ServerXen331:/usr/src/linux.trees.git# git checkout -b tip-latest tip/master
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of tip/master.
Checking out files: 100% (26687/26687), done.
Branch tip-latest set up to track remote branch refs/remotes/tip/master.
Switched to a new branch "tip-latest"


"make menuconfig" still  doesn't show options for Xen Dom0 support.


--- On Tue, 2/17/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Date: Tuesday, February 17, 2009, 12:14 AM

>title xen-unstable pvops
>       kernel /xen-3.gz loglvl=all guest_loglvl=all
>       module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00
> ignore_loglevel pci=nomsi earlyprintk=vga console=tty0
>  module  /initrd-2.6.29-rc5-tip.img
>   J


I was able to reproduce http://people.redhat.com/mingo/tip.git/README:-

mkdir linux.trees.git || exit -1
cd linux.trees.git

git init
# Add Linus's tree as a remote
git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the -tip tree as a remote
git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
git remote update
git checkout -b tip-latest tip/master

"make menuconfig" doesn't show options for Xen Dom0 support
"make" builds 
 vmlinuz-2.6.29-rc5-tip, but it's useless.

Sorry, to bother you . It's unknown for myself at least 
how to build kernel via git now . Git repos at kernel.org have
been modified.

Boris




-- On Mon, 2/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Console output with pv_ops kernel
To: jonr@destar.net
Cc: xen-devel@lists.xensource.com
Date: Monday, February 16, 2009, 5:53 PM

jonr@destar.net wrote:
> I am trying to get my Xen-3.4-unstable with 2.6.29-rc3-tip to output to
the console after Xen releases control back to the kernel. I can see the Xen
portion but as soon as it scrubs memory it goes to a blank screen. It will boot
up but I will never see a login prompt. I have to ssh
 into the box.
> 
> I have tried various options for grub but have not found the correct
combination as of yet. Here is what I have for my menu.lst:
> 
> This is the latest incantation:
> 
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 earlyprintk=xen
pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
> 
> ====
> Also:
> ====
> title Xen 3.4 / kernel 2.6.29-tip-rc3
>   root(hd0,0)
>   kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
>   module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0 earlyprintk=xen
pci=nomsi
>   module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
> 
> 
> Has anybody gotten this to output to the screen? Is there some magic that
I am missing?
> 

This
 should work if you're using a serial console.  Otherwise, you can use
a vga console; I use:

title xen-unstable pvops
       kernel /xen-3.gz loglvl=all guest_loglvl=all
       module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00
ignore_loglevel pci=nomsi earlyprintk=vga console=tty0        module
/initrd-2.6.29-rc5-tip.img


   J

_______________________________________________
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: Type: text/html, Size: 9670 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: How to build vmlinuz-2.6.29-rc5-tip ?

[Ian Campbell]

On Tue, 2009-02-17 at 03:15 -0500, Boris Derzhavets wrote:
> 
> root@ServerXen331:/usr/src/linux.trees.git# git checkout -b tip-latest
> tip/master
> warning: You appear to be on a branch yet to be born.
> warning: Forcing checkout of tip/master.
> Checking out files: 100% (26687/26687), done.
> Branch tip-latest set up to track remote branch
> refs/remotes/tip/master.
> Switched to a new branch "tip-latest"
> 
> 
> "make menuconfig" still  doesn't show options for Xen Dom0 support.
> 

In Jeremy's announcement of the git tree he said:

> 
> If you want to get started, either xen/dom0/hackery or xen/master are 
> the places to start;
> 
> xen/dom0/hackery
>     Master dom0 branch.  This is all the interesting dom0-related topic
>     branches merged together, and is a superset of xen/master.
> xen/master
>     Master domU branch, with everything interesting merged in.  This is
>     likely to be more stable and closer to upstream than dom0/hackery

So I think you want the xen/dom0/hackery branch which would become
tip/xen/dom0/hackery in your repo (and xen/master=>tip/xen/master not
tip/master).

Ian.

Re: How to build vmlinuz-2.6.29-rc5-tip ?

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 5467 bytes --]

Did all stuf from scratch

rm -fr linux.tree.git
mkdir linux.tree.git || exit -1
cd linux.tree.git

git init
# Add Linus's tree as a remote
git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the -tip tree as a remote

git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
git remote update

. . . . . 

Updating tip
remote: Counting objects: 19569, done.
remote: Compressing objects: 100% (7482/7482), done.
remote: Total 18172 (delta 14981), reused 12843 (delta 10122)
Receiving objects: 100% (18172/18172), 3.54 MiB | 109 KiB/s, done.
Resolving deltas: 100% (14981/14981), completed with 1157 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen
 * [new branch]      acpi/map   -> tip/acpi/map
 * [new branch]      mainline/mm -> tip/mainline/mm
 * [new branch]      mainline/net -> tip/mainline/net
 * [new branch]      master     -> tip/master
 * [new branch]      push/xen/dom0/core -> tip/push/xen/dom0/core
 * [new branch]      tip/fixups -> tip/tip/fixups
 * [new branch]      x86/apic   -> tip/x86/apic
 * [new branch]      x86/cpa    -> tip/x86/cpa
 * [new branch]      x86/unify  -> tip/x86/unify
 * [new branch]      x86/unify-base -> tip/x86/unify-base
 * [new branch]      x86/unify-irq -> tip/x86/unify-irq
 * [new branch]      x86/unify-irq-base -> tip/x86/unify-irq-base
 * [new branch]      x86/unify-kmemcheck -> tip/x86/unify-kmemcheck
 * [new branch]      x86/unify-kmemcheck-base -> tip/x86/unify-kmemcheck-base
 * [new branch]      x86/untangle -> tip/x86/untangle
 * [new branch]      x86/untangle2 -> tip/x86/untangle2
 * [new branch]      xen/core   -> tip/xen/core
 * [new branch]      xen/dev-evtchn -> tip/xen/dev-evtchn
 * [new branch]      xen/dom0/apic -> tip/xen/dom0/apic
 * [new branch]      xen/dom0/backend/blkback -> tip/xen/dom0/backend/blkback
 * [new branch]      xen/dom0/backend/core -> tip/xen/dom0/backend/core
 * [new branch]      xen/dom0/backend/netback -> tip/xen/dom0/backend/netback
 * [new branch]      xen/dom0/core -> tip/xen/dom0/core
 * [new branch]      xen/dom0/hackery -> tip/xen/dom0/hackery
 * [new branch]      xen/dom0/mtrr -> tip/xen/dom0/mtrr
 * [new branch]      xen/dom0/pci -> tip/xen/dom0/pci
 * [new branch]      xen/dom0/swiotlb -> tip/xen/dom0/swiotlb
 * [new branch]      xen/dom0/xenfs -> tip/xen/dom0/xenfs
 * [new branch]      xen/frontend/blkfront -> tip/xen/frontend/blkfront
 * [new branch]      xen/fs     -> tip/xen/fs
 * [new branch]      xen/hg-queue-import -> tip/xen/hg-queue-import
 * [new branch]      xen/irq    -> tip/xen/irq
 * [new branch]      xen/master -> tip/xen/master
 * [new branch]      xen/pvhvm  -> tip/xen/pvhvm
 * [new branch]      xen/xenbus -> tip/xen/xenbus

 . . . . . . . . . 

So, new branch obtained.

As far as i understood Ian :-

git checkout -b xen-latest tip/xen/master

"make menuconfig" still doesn't show options for Xen Dom0 support

Something was done wrong.

 Option "[*] Enable Xen privileged domain support"   is abcent      


************************************************************************

The most recent picture on Mercurial (after applying patch queue)

************************************************************************
  --- Paravirtualized guest support                                                            
    
      [*]   Xen guest support                                                     
      (32)    Maximum allowed size of a domain in gigabytes                       
      [*]     Enable Xen debug and tuning parameters in debugfs                   
      [*]     Enable Xen privileged domain support                   

--- On Tue, 2/17/09, Ian Campbell <Ian.Campbell@citrix.com> wrote:
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?
To: "bderzhavets@yahoo.com" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, February 17, 2009, 3:28 AM

On Tue, 2009-02-17 at 03:15 -0500, Boris Derzhavets wrote:
> 
> root@ServerXen331:/usr/src/linux.trees.git# git checkout -b tip-latest
> tip/master
> warning: You appear to be on a branch yet to be born.
> warning: Forcing checkout of tip/master.
> Checking out files: 100% (26687/26687), done.
> Branch tip-latest set up to track remote branch
> refs/remotes/tip/master.
> Switched to a new branch "tip-latest"
> 
> 
> "make menuconfig" still  doesn't show options for Xen Dom0
support.
> 

In Jeremy's announcement of the git tree he said:

> 
> If you want to get started, either xen/dom0/hackery or xen/master are 
> the places to start;
> 
> xen/dom0/hackery
>     Master dom0 branch.  This is all the interesting dom0-related topic
>     branches merged together, and is a superset of xen/master.
> xen/master
>     Master domU branch, with everything interesting merged in.  This is
>     likely to be more stable and closer to upstream than dom0/hackery

So I think you want the xen/dom0/hackery branch which would become
tip/xen/dom0/hackery in your repo (and xen/master=>tip/xen/master not
tip/master).

Ian.


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



      

[-- Attachment #1.2: Type: text/html, Size: 8443 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: How to build vmlinuz-2.6.29-rc5-tip ?

[M A Young]

On Tue, 17 Feb 2009, Boris Derzhavets wrote:

> Did all stuf from scratch
> 
> rm -fr linux.tree.git
> mkdir linux.tree.git || exit -1
> cd linux.tree.git
> 
> git init
> # Add Linus's tree as a remote
> git remote add linus
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> 
> # Add the -tip tree as a remote
> 
> git remote add tip
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> git remote update

That is a potential source of confusion since this is the xen git repo, 
not the tip one.
git remote add xen git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
would make more sense.

...

> git checkout -b xen-latest tip/xen/master
> 
> "make menuconfig" still doesn't show options for Xen Dom0 support
> 
> Something was done wrong.

You are still looking at the wrong branch. The xen/master branch in the 
xen.git repository is the DomU head, so won't necessarily contain the Dom0 
stuff I assume you want to test. Maybe the more stable bits of Dom0 will 
be added to that branch in due course, but at the moment key bits of Dom0 
are missing.

Thus you should be replacing xen/master with xen/dom0/hackery

 	Michael Young

Re: How to build vmlinuz-2.6.29-rc5-tip ?

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1756 bytes --]

xen/dom0/hackery works fine.
Thank you.
Boris


--- On Tue, 2/17/09, M A Young <m.a.young@durham.ac.uk> wrote:

From: M A Young <m.a.young@durham.ac.uk>
Subject: Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, February 17, 2009, 5:00 AM

On Tue, 17 Feb 2009, Boris Derzhavets wrote:

> Did all stuf from scratch
> 
> rm -fr linux.tree.git
> mkdir linux.tree.git || exit -1
> cd linux.tree.git
> 
> git init
> # Add Linus's tree as a remote
> git remote add linus
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> 
> # Add the -tip tree as a remote
> 
> git remote add tip
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> git remote update

That is a potential source of confusion since this is the xen git repo, not the
tip one.
git remote add xen git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
would make more sense.

...

> git checkout -b xen-latest tip/xen/master
> 
> "make menuconfig" still doesn't show options for Xen Dom0
support
> 
> Something was done wrong.

You are still looking at the wrong branch. The xen/master branch in the xen.git
repository is the DomU head, so won't necessarily contain the Dom0 stuff I
assume you want to test. Maybe the more stable bits of Dom0 will be added to
that branch in due course, but at the moment key bits of Dom0 are missing.

Thus you should be replacing xen/master with xen/dom0/hackery

	Michael Young

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



      

[-- Attachment #1.2: Type: text/html, Size: 2162 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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