WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] failed to build xen from source code

To: wenche_chang@xxxxxxxxxxxx
Subject: Re: [Xen-devel] failed to build xen from source code
From: chris <tknchris@xxxxxxxxx>
Date: Sun, 30 May 2010 22:47:21 -0400
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 30 May 2010 19:55:45 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=XVa/oruSG0/mGi8o2lkZPErAoeK/krE2eL6gzxVTnVE=; b=Rvsqa5ELqhsZChXBZZJm3LKFbhCcQk3XI6EDV+P2yKx1M4uXNoL6S0eHvz7KdoG/ph zwND85KdBBhF2nI8B8Qb0CnlAJxx18efZLutzrND3gf1FX/rBDOCXh1/xcnQgkSgAZ5z xMDiti6s4ZkpBrsvOXjqBSqi+nLUdFB6OGDhE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ImdDQkMB6AmiNehWg607DEH1I8j1RiMhyRqELk/KcIi3oaAiowaS0jf/SAa+4n5L2g JSLJh/voBy2QqiFtCjijFMrQiG7WVklW8/tNu/rZ8MS8OHvlI2iBtG7F3Sc/bj4r/M4L gDezEqy2Uto19+j3VjlmNkpaF3/DszDwPPhE4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43FEA041821E5247942BF0802912D9387572D7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <43FEA041821E5247942BF0802912D9387572D4@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4BFF444A.7020606@xxxxxxxx> <43FEA041821E5247942BF0802912D9387572D5@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100528085114.GA17817@xxxxxxxxxxx> <43FEA041821E5247942BF0802912D938D53C31@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100528094744.GE17817@xxxxxxxxxxx> <43FEA041821E5247942BF0802912D938D53C73@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100528102753.GH17817@xxxxxxxxxxx> <43FEA041821E5247942BF0802912D9387572D7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
If it is <*> then it is compiled in and wont be in the list of loaded modules....

- chris

2010/5/30 <wenche_chang@xxxxxxxxxxxx>
Hi pasi
 
After following the fstab entry on the XenParavirtOps wiki page,there are files in /proc/xen
I also check the dom0 config file, and there is "<*> Xen /dev/xen/evtchn device".
But in lsmod,there is not xen-evtchn.
I tried modprobe xen-evtchn,and it shows "FATAL : xen_evtchn not found"
do I forget something to do??
 
thanks


From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
Sent: 2010/5/28 [星期五] 下午 06:27

To: Wen Che Chang (RD-TW)
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] failed to build xen from source code

On Fri, May 28, 2010 at 06:18:18PM +0800, wenche_chang@xxxxxxxxxxxx wrote:
> Hi pasi
>
> You are right.
> There is not any file in /proc/xen and I can't see xen-evtchn when I run lsmod.
>
> But I don???t know how to fix these problems even I read the link in wiki.
> Can you provide more detail reference?
>

- Check your dom0 kernel .config file. Is the Xen event channel compiled in, or is it built as a module?
  If it's a module, then use "modprobe xen-evtchn" to load it.

- For mounting /proc/xen see the example fstab entry on the XenParavirtOps wiki page. Add the line to /etc/fstab and after that run "mount /proc/xen".
  Xen 3.4.3 and 4.0.0 should automatically mount /proc/xen though.

-- Pasi

> thanks a lot.
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
> Sent: Friday, May 28, 2010 5:48 PM
> To: Wen Che Chang (RD-TW)
> Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] failed to build xen from source code
>
> On Fri, May 28, 2010 at 05:35:09PM +0800, wenche_chang@xxxxxxxxxxxx wrote:
> > Hi
> > I have read  "Xend does not start when using pv_ops dom0 kernel? "in this link and I don???t think it's my problem
> >
> > I download SRPM of XEN 4.0.0 from http://pasik.reaktio.net/fedora/xen-4.0.0-0.7.fc12.src.rpm or http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.7.fc12.src.rpm
> >
> > After installation it in Fedora 12 , xend works well, but it can't start if I install Xen from http://xenbits.xen.org/xen-4.0-testing.hg
> >
>
> I think the init scripts in Fedora rpm do more than the default scripts in upstream Xen.
>
> So:
>       - Do you have /proc/xen (xenfs) mounted? Do you have files in it?
>       - Do you have xen-evtchn driver loaded? Run lsmod if it's compiled as a module in your dom0 kernel.

> Both of those need to be OK before xend starts.
>
> -- Pasi
>
> > -----Original Message-----
> > From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
> > Sent: Friday, May 28, 2010 4:51 PM
> > To: Wen Che Chang (RD-TW)
> > Cc: jeremy@xxxxxxxx; Xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] failed to build xen from source code
> >
> > On Fri, May 28, 2010 at 03:33:54PM +0800, wenche_chang@xxxxxxxxxxxx wrote:
> > >    Hi
> > >
> > >    after install these two RPMs , I can build and install the xen 4.0.1
> > >
> > >    But there are some troubles about xend , the error message is shown as
> > >    below
> > >
> > >    [root@localhost ~]# xm list
> > >     Unable to connect to xend: No such file or directory. Is xend running?
> > >
> > >    [root@localhost ~]# xend
> > >    ERROR Internal error: Could not obtain handle on privileged command
> > >    interface (2 = No such file or directory)
> > >    Traceback (most recent call last):
> > >      File "/usr/sbin/xend", line 36, in <module>
> > >        from xen.xend.server import SrvDaemon
> > >      File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
> > >    line 26, in <module>
> > >        import relocate
> > >      File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py",
> > >    line 28, in <module>
> > >        from xen.xend import XendDomain
> > >      File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line
> > >    36, in <module>
> > >        from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
> > >      File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py",
> > >    line 20, in <module>
> > >        from xen.xend import balloon, sxp, image
> > >      File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46, in
> > >    <module>
> > >        xc = xen.lowlevel.xc.xc()
> > >    xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on
> > >    privileged command interface (2 = No such file or directory)')
> > >
> > >
> > >    Any idea?
> > >
> >
> >
> > Try reading the troubleshooting tips at:
> > http://wiki.xensource.com/xenwiki/XenParavirtOps
> >
> >
> > -- Pasi
> >
> >
> > >    --------------------------------------------------------------------------
> > >
> > >    From: Jeremy Fitzhardinge [mailto:jeremy@xxxxxxxx]
> > >    Sent: 2010/5/28 [¬PŽÁ€] €U€È 12:19
> > >    To: Wen Che Chang (RD-TW)
> > >    Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
> > >    Subject: Re: [Xen-devel] failed to build xen from source code
> > >
> > >    On 05/27/2010 08:47 PM, wenche_chang@xxxxxxxxxxxx wrote:
> > >    > Hi
> > >    > I tried to install Xen 4.0.1 from
> > >    > [1]http://*xen*bits.*xen*.org/*xen*-*4.0*-testing.hg
> > >    > <[2]http://xenbits.xen.org/xen-4.0-testing.hg>
> > >    > I use the installation step in Xen wiki as shown below
> > >    > yum groupinstall "Development Libraries"
> > >    > yum groupinstall "Development Tools"
> > >    > yum install transfig texi2html libaio-devel dev86 glibc-devel
> > >    e2fsprogs-devel gitk mkinitrd iasl xz-devel bzip2-devel
> > >    > hg clone [3]http://xenbits.xen.org/xen-4.0-testing.hg
> > >    > cd xen-4.0-testing.hg
> > >    > make xen
> > >    > make tools
> > >    > make stubdom
> > >    > I failed in  "make tools" and it shows
> > >    > /usr/bin/ld: cannot find -lpci
> > >    >
> > >
> > >    I think you also need pciutils-libs and pciutils-devel.
> > >
> > >    J
> > >
> > > TREND MICRO EMAIL NOTICE
> > > The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
> > >
> > > References
> > >
> > >    Visible links
> > >    1. http://*xen*bits.*xen*.org/*xen*-*4.0*-testing.hg
> > >    2. http://xenbits.xen.org/xen-4.0-testing.hg
> > >    3. http://xenbits.xen.org/xen-4.0-testing.hg
> >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> >
> >
> > TREND MICRO EMAIL NOTICE
> > The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
>
> TREND MICRO EMAIL NOTICE
> The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.

TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.

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


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