hello mukesh
Now,I want debug the xen domU kernel or kernel modules, I found the tools
gdbsx under xen source directory. As the guide of README you wrote, I compile
the xen with:
make gdbsx=y
but I got the errors as below:
remote: Counting objects: 1857338, done.
remote: Compressing objects: 100% (292566/292566), done.
Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, done.
remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
Resolving deltas: 100% (1554805/1554805), done.
Checking out files: 100% (30571/30571), done.
+ cd linux-2.6-pvops.git.tmp
+ git checkout xen/master
error: pathspec 'xen/master' did not match any file(s) known to git.
make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
make[1]: *** [linux-2.6-pvops-install] error 2
make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
make: *** [install-kernels] error 1
could you give me some advice on how to solve this errors?
thanks a lot.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote:> hello mukesh > Now,I want debug the xen domU kernel or kernel modules, I found > the tools gdbsx under xen source directory. As the guide of README you > wrote, I compile the xen with: > make gdbsx=y > > > but I got the errors as below: > remote: Counting objects: 1857338, done. > remote: Compressing objects: 100% (292566/292566), done. > Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, > done. > remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905) > Resolving deltas: 100% (1554805/1554805), done. > Checking out files: 100% (30571/30571), done. > + cd linux-2.6-pvops.git.tmp > + git checkout xen/master > error: pathspec ''xen/master'' did not match any file(s) known to git. > make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1 > make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > make[1]: *** [linux-2.6-pvops-install] error 2 > make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > make: *** [install-kernels] error 1This error message clearly indicates a problem building the kernel and not gdbsx. The fact that your kernel build tried to clone xen/master suggests you are not building in an uptodate Xen source tree (it looks like you have 4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree or at a minimum update to the 4.0.1 release. Since you only need to build the tools and not the kernels or hypervisor you can use the tools targets as described in "make help". e.g. $ make gdbsx=y tools (it looks like gdbsx=y is redundant since building gdbsx is not actually optional, probably tools/debugger/gdbsx/README is out of date) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hi Ian
As your suggestions, I compile the gdbsx tools independently use
make gdbsx=y tools
but when I executed the gdbsx on dom0, I got this error:
ERROR:_check_hyp:Hyp is NOT enabled for gdbsx
ERROR: failed to attach to domain:2 errno:38
It looks like I have to recompile the xen & make it enable gdbsx.
I just do like this: make gdbsx=y
but I still get the error which I offered before.
Should I use xen4.0.1? xen 4.0.0 not support gdbsx?
our system using xen 4.0.0
At 2010-12-07 17:47:44，"Ian Campbell" <Ian.Campbell@citrix.com>
wrote:
>On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote:
>> hello mukesh
>> Now,I want debug the xen domU kernel or kernel modules, I found
>> the tools gdbsx under xen source directory. As the guide of README you
>> wrote, I compile the xen with:
>> make gdbsx=y
>>
>>
>> but I got the errors as below:
>> remote: Counting objects: 1857338, done.
>> remote: Compressing objects: 100% (292566/292566), done.
>> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s,
>> done.
>> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
>> Resolving deltas: 100% (1554805/1554805), done.
>> Checking out files: 100% (30571/30571), done.
>> + cd linux-2.6-pvops.git.tmp
>> + git checkout xen/master
>> error: pathspec 'xen/master' did not match any file(s) known to
git.
>> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
>> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
>> make[1]: *** [linux-2.6-pvops-install] error 2
>> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
>> make: *** [install-kernels] error 1
>
>This error message clearly indicates a problem building the kernel and
>not gdbsx.
>
>The fact that your kernel build tried to clone xen/master suggests you
>are not building in an uptodate Xen source tree (it looks like you have
>4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree
>or at a minimum update to the 4.0.1 release.
>
>Since you only need to build the tools and not the kernels or hypervisor
>you can use the tools targets as described in "make help". e.g.
>
> $ make gdbsx=y tools
>
>(it looks like gdbsx=y is redundant since building gdbsx is not actually
>optional, probably tools/debugger/gdbsx/README is out of date)
>
>Ian.
>
>
>
>
>_______________________________________________
>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
On Thu, 2010-12-09 at 12:06 +0000, topperxin wrote:> hi Ian > As your suggestions, I compile the gdbsx tools independently use > make gdbsx=y tools > but when I executed the gdbsx on dom0, I got this error: > ERROR:_check_hyp:Hyp is NOT enabled for gdbsx > ERROR: failed to attach to domain:2 errno:38 > It looks like I have to recompile the xen & make it enable gdbsx. > I just do like this: make gdbsx=y > but I still get the error which I offered before.Try adding "KERNELS=" to your make line, that will avoid the error compiling the kernel.> Should I use xen4.0.1? xen 4.0.0 not support gdbsx? > our system using xen 4.0.0I''ve no idea but as a general rule using the most recent stable release is a good idea. Ian.> > > > > > At 2010-12-07 17:47:44，"Ian Campbell" <Ian.Campbell@citrix.com> wrote: > > >On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote: > >> hello mukesh > >> Now,I want debug the xen domU kernel or kernel modules, I found > >> the tools gdbsx under xen source directory. As the guide of README you > >> wrote, I compile the xen with: > >> make gdbsx=y > >> > >> > >> but I got the errors as below: > >> remote: Counting objects: 1857338, done. > >> remote: Compressing objects: 100% (292566/292566), done. > >> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, > >> done. > >> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905) > >> Resolving deltas: 100% (1554805/1554805), done. > >> Checking out files: 100% (30571/30571), done. > >> + cd linux-2.6-pvops.git.tmp > >> + git checkout xen/master > >> error: pathspec ''xen/master'' did not match any file(s) known to git. > >> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1 > >> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > >> make[1]: *** [linux-2.6-pvops-install] error 2 > >> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > >> make: *** [install-kernels] error 1 > > > >This error message clearly indicates a problem building the kernel and > >not gdbsx. > > > >The fact that your kernel build tried to clone xen/master suggests you > >are not building in an uptodate Xen source tree (it looks like you have > >4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree > >or at a minimum update to the 4.0.1 release. > > > >Since you only need to build the tools and not the kernels or hypervisor > >you can use the tools targets as described in "make help". e.g. > > > > $ make gdbsx=y tools > > > >(it looks like gdbsx=y is redundant since building gdbsx is not actually > >optional, probably tools/debugger/gdbsx/README is out of date) > > > >Ian. > > > > > > > > > >_______________________________________________ > >Xen-devel mailing list > >Xen-devel@lists.xensource.com > >http://lists.xensource.com/xen-devel > > > > ______________________________________________________________________ > 网易163/126邮箱百分百兼容iphone ipad邮件收发_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2010/12/7 topperxin <topperxin@126.com>:> hello mukesh > Now,I want debug the xen domU kernel or kernel modules, I found the > tools gdbsx under xen source directory. As the guide of README you wrote, I > compile the xen with: > make gdbsx=y > but I got the errors as below: > remote: Counting objects: 1857338, done. > remote: Compressing objects: 100% (292566/292566), done. > Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, done. > remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905) > Resolving deltas: 100% (1554805/1554805), done. > Checking out files: 100% (30571/30571), done. > + cd linux-2.6-pvops.git.tmp > + git checkout xen/master > error: pathspec ''xen/master'' did not match any file(s) known to git. > make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1 > make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > make[1]: *** [linux-2.6-pvops-install] error 2 > make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'' > make: *** [install-kernels] error 1 > could you give me some advice on how to solve this errors? > thanks a lot. >If you use xen-unstable, you don''t need to build gdbsx by itself. It is always built as part of the xen compilation. After installing xen, it should end up in /usr/sbin/gdbsx on dom0. -Bruce> ________________________________ > 网易163/126邮箱百分百兼容iphone ipad邮件收发 > _______________________________________________ > 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