Wouter van Eekelen
2011-Jun-02 08:39 UTC
[Xen-users] Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I installed Debian Squeeze 6.0 on a server and am now trying to install Xen 4.1.0 on it (compiled from source, since the packages don''t include Remus support). Here are the steps I did to install it and get around several errors. 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 2) Installed the dom0 kernel for Debian as shown at http://wiki.xensource.com/xenwiki/XenDom0Kernels 3) Rebooted into the kernel and made sure it was running: Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 GNU/Linux 4) Installed the requirements for compiling: apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext bcc iasl latex2rtf-doc gcc g++ build-essential 5) Downloaded the 4.1.0 source, untarred it and ran "make world" 6) No errors except a warning about latex for documentation, so I ran "make install" 7) Rebooted again At first, when running "xm list", I received this error: _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 08:42 UTC
[Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Seems like part of my e-mail was lost, here is the rest... -- At first, when running "xm list", I received this error: "ImportError: No module named xen.xm" I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved Then I received this error: Error: Unable to connect to xend: No such file or directory. Is xend running? So I try starting xend: xencommons should be started first. So I try starting xencommons: grep: /proc/xen/capabilities: No such file or directory A thread on this mailing list suggested I added "none /proc/xen xenfs defaults 0 0" to /etc/fstab I''ve done so, rebooted, but the issue persisted. Another thread suggested I ran ''insmod xen-evtchn'' and ''modprobe xen-evtchn'', which gave me this error: FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device And now I''m rather stuck. What am I doing wrong? On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote:> I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > Here are the steps I did to install it and get around several errors. > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > 3) Rebooted into the kernel and made sure it was running: > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > 4) Installed the requirements for compiling: > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > 6) No errors except a warning about latex for documentation, so I ran "make > install" > 7) Rebooted again > > At first, when running "xm list", I received this error: > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 10:02 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Statically compile the XEN stuff rather than using it as modules, I had the same grief as you but went away after doing that. Also xm commands do not work for some reason but xl works fine. Ian From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen Sent: 02 June 2011 09:42 To: xen-users@lists.xensource.com Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Seems like part of my e-mail was lost, here is the rest... -- At first, when running "xm list", I received this error: "ImportError: No module named xen.xm" I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved Then I received this error: Error: Unable to connect to xend: No such file or directory. Is xend running? So I try starting xend: xencommons should be started first. So I try starting xencommons: grep: /proc/xen/capabilities: No such file or directory A thread on this mailing list suggested I added "none /proc/xen xenfs defaults 0 0" to /etc/fstab I''ve done so, rebooted, but the issue persisted. Another thread suggested I ran ''insmod xen-evtchn'' and ''modprobe xen-evtchn'', which gave me this error: FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device And now I''m rather stuck. What am I doing wrong? On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: I installed Debian Squeeze 6.0 on a server and am now trying to install Xen 4.1.0 on it (compiled from source, since the packages don''t include Remus support). Here are the steps I did to install it and get around several errors. 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 2) Installed the dom0 kernel for Debian as shown at http://wiki.xensource.com/xenwiki/XenDom0Kernels 3) Rebooted into the kernel and made sure it was running: Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 GNU/Linux 4) Installed the requirements for compiling: apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext bcc iasl latex2rtf-doc gcc g++ build-essential 5) Downloaded the 4.1.0 source, untarred it and ran "make world" 6) No errors except a warning about latex for documentation, so I ran "make install" 7) Rebooted again At first, when running "xm list", I received this error: _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 10:06 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Do you have any tutorial/hint on how to statically compile it? And is there any reason it won''t just work out of the box? I''ve tried this on CentOs 5 too, but the same errors occur there.. And what exactly is the difference between xm and xl? On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Statically compile the XEN stuff rather than using it as modules, I had the > same grief as you but went away after doing that. > > > > Also xm commands do not work for some reason but xl works fine. > > > > Ian > > > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Wouter van Eekelen > *Sent:* 02 June 2011 09:42 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Seems like part of my e-mail was lost, here is the rest... > > -- > > > > At first, when running "xm list", I received this error: > > "ImportError: No module named xen.xm" > > > > I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of > Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved > > > > Then I received this error: > > Error: Unable to connect to xend: No such file or directory. Is xend > running? > > > > So I try starting xend: > > xencommons should be started first. > > > > So I try starting xencommons: > > grep: /proc/xen/capabilities: No such file or directory > > > > A thread on this mailing list suggested I added "none /proc/xen xenfs > defaults 0 0" to /etc/fstab > > I''ve done so, rebooted, but the issue persisted. > > > > Another thread suggested I ran ''insmod xen-evtchn'' and > ''modprobe xen-evtchn'', which gave me this error: > > FATAL: Error inserting xen_evtchn > (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such > device > > > > And now I''m rather stuck. What am I doing wrong? > > > > On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: > > I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > > Here are the steps I did to install it and get around several errors. > > > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > 3) Rebooted into the kernel and made sure it was running: > > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > > > 4) Installed the requirements for compiling: > > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > > 6) No errors except a warning about latex for documentation, so I ran "make > install" > > 7) Rebooted again > > > > At first, when running "xm list", I received this error: > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 10:11 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
When your in the make menuconfig screen, under Device Drivers select the same as mine, * is for static compile where M is to be used as a module. Xm is based on python which is being depreciated. From: Wouter van Eekelen [mailto:me@woet.me] Sent: 02 June 2011 11:06 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Do you have any tutorial/hint on how to statically compile it? And is there any reason it won''t just work out of the box? I''ve tried this on CentOs 5 too, but the same errors occur there.. And what exactly is the difference between xm and xl? On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: Statically compile the XEN stuff rather than using it as modules, I had the same grief as you but went away after doing that. Also xm commands do not work for some reason but xl works fine. Ian From: xen-users-bounces@lists.xensource.com [mailto: xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen Sent: 02 June 2011 09:42 To: xen-users@lists.xensource.com Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Seems like part of my e-mail was lost, here is the rest... -- At first, when running "xm list", I received this error: "ImportError: No module named xen.xm" I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved Then I received this error: Error: Unable to connect to xend: No such file or directory. Is xend running? So I try starting xend: xencommons should be started first. So I try starting xencommons: grep: /proc/xen/capabilities: No such file or directory A thread on this mailing list suggested I added "none /proc/xen xenfs defaults 0 0" to /etc/fstab I''ve done so, rebooted, but the issue persisted. Another thread suggested I ran ''insmod xen-evtchn'' and ''modprobe xen-evtchn'', which gave me this error: FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device And now I''m rather stuck. What am I doing wrong? On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: I installed Debian Squeeze 6.0 on a server and am now trying to install Xen 4.1.0 on it (compiled from source, since the packages don''t include Remus support). Here are the steps I did to install it and get around several errors. 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 2) Installed the dom0 kernel for Debian as shown at http://wiki.xensource.com/xenwiki/XenDom0Kernels 3) Rebooted into the kernel and made sure it was running: Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 GNU/Linux 4) Installed the requirements for compiling: apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext bcc iasl latex2rtf-doc gcc g++ build-essential 5) Downloaded the 4.1.0 source, untarred it and ran "make world" 6) No errors except a warning about latex for documentation, so I ran "make install" 7) Rebooted again At first, when running "xm list", I received this error: _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 10:13 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Okay, I''m not compiling my own kernel though - I''m using the one in the Debian packages (2.6.32-5-xen-amd64) as suggested at http://wiki.xensource.com/xenwiki/XenDom0Kernels Should I compile my own kernel instead? On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> When your in the make menuconfig screen, under Device Drivers select the > same as mine, * is for static compile where M is to be used as a module. > > > > > > > > Xm is based on python which is being depreciated. > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:06 > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Do you have any tutorial/hint on how to statically compile it? > > And is there any reason it won''t just work out of the box? > I''ve tried this on CentOs 5 too, but the same errors occur there.. > > > > And what exactly is the difference between xm and xl? > > > > On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Statically compile the XEN stuff rather than using it as modules, I had the > same grief as you but went away after doing that. > > > > Also xm commands do not work for some reason but xl works fine. > > > > Ian > > > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Wouter van Eekelen > *Sent:* 02 June 2011 09:42 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Seems like part of my e-mail was lost, here is the rest... > > -- > > > > At first, when running "xm list", I received this error: > > "ImportError: No module named xen.xm" > > > > I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of > Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved > > > > Then I received this error: > > Error: Unable to connect to xend: No such file or directory. Is xend > running? > > > > So I try starting xend: > > xencommons should be started first. > > > > So I try starting xencommons: > > grep: /proc/xen/capabilities: No such file or directory > > > > A thread on this mailing list suggested I added "none /proc/xen xenfs > defaults 0 0" to /etc/fstab > > I''ve done so, rebooted, but the issue persisted. > > > > Another thread suggested I ran ''insmod xen-evtchn'' and > ''modprobe xen-evtchn'', which gave me this error: > > FATAL: Error inserting xen_evtchn > (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such > device > > > > And now I''m rather stuck. What am I doing wrong? > > > > On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: > > I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > > Here are the steps I did to install it and get around several errors. > > > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > 3) Rebooted into the kernel and made sure it was running: > > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > > > 4) Installed the requirements for compiling: > > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > > 6) No errors except a warning about latex for documentation, so I ran "make > install" > > 7) Rebooted again > > > > At first, when running "xm list", I received this error: > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 10:28 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Sorry I didn''t realise. What steps are you doing to compile XEN? From: Wouter van Eekelen [mailto:me@woet.me] Sent: 02 June 2011 11:14 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Okay, I''m not compiling my own kernel though - I''m using the one in the Debian packages (2.6.32-5-xen-amd64) as suggested at http://wiki.xensource.com/xenwiki/XenDom0Kernels Should I compile my own kernel instead? On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote: When your in the make menuconfig screen, under Device Drivers select the same as mine, * is for static compile where M is to be used as a module. Xm is based on python which is being depreciated. From: Wouter van Eekelen [mailto:me@woet.me] Sent: 02 June 2011 11:06 To: Ian Tobin Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Do you have any tutorial/hint on how to statically compile it? And is there any reason it won''t just work out of the box? I''ve tried this on CentOs 5 too, but the same errors occur there.. And what exactly is the difference between xm and xl? On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: Statically compile the XEN stuff rather than using it as modules, I had the same grief as you but went away after doing that. Also xm commands do not work for some reason but xl works fine. Ian From: xen-users-bounces@lists.xensource.com [mailto: xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen Sent: 02 June 2011 09:42 To: xen-users@lists.xensource.com Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0 Seems like part of my e-mail was lost, here is the rest... -- At first, when running "xm list", I received this error: "ImportError: No module named xen.xm" I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved Then I received this error: Error: Unable to connect to xend: No such file or directory. Is xend running? So I try starting xend: xencommons should be started first. So I try starting xencommons: grep: /proc/xen/capabilities: No such file or directory A thread on this mailing list suggested I added "none /proc/xen xenfs defaults 0 0" to /etc/fstab I''ve done so, rebooted, but the issue persisted. Another thread suggested I ran ''insmod xen-evtchn'' and ''modprobe xen-evtchn'', which gave me this error: FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device And now I''m rather stuck. What am I doing wrong? On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: I installed Debian Squeeze 6.0 on a server and am now trying to install Xen 4.1.0 on it (compiled from source, since the packages don''t include Remus support). Here are the steps I did to install it and get around several errors. 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 2) Installed the dom0 kernel for Debian as shown at http://wiki.xensource.com/xenwiki/XenDom0Kernels 3) Rebooted into the kernel and made sure it was running: Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 GNU/Linux 4) Installed the requirements for compiling: apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext bcc iasl latex2rtf-doc gcc g++ build-essential 5) Downloaded the 4.1.0 source, untarred it and ran "make world" 6) No errors except a warning about latex for documentation, so I ran "make install" 7) Rebooted again At first, when running "xm list", I received this error: _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 10:29 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I''m simply following the README, "make world" and then "make install" afterwards. On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Sorry I didn’t realise. What steps are you doing to compile XEN? > > > > > > > > > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:14 > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Okay, I''m not compiling my own kernel though - I''m using the one in the > Debian packages (2.6.32-5-xen-amd64) as suggested at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > Should I compile my own kernel instead? > > > > On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > When your in the make menuconfig screen, under Device Drivers select the > same as mine, * is for static compile where M is to be used as a module. > > > > > > > > Xm is based on python which is being depreciated. > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:06 > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Do you have any tutorial/hint on how to statically compile it? > > And is there any reason it won''t just work out of the box? > I''ve tried this on CentOs 5 too, but the same errors occur there.. > > > > And what exactly is the difference between xm and xl? > > > > On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Statically compile the XEN stuff rather than using it as modules, I had the > same grief as you but went away after doing that. > > > > Also xm commands do not work for some reason but xl works fine. > > > > Ian > > > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Wouter van Eekelen > *Sent:* 02 June 2011 09:42 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Seems like part of my e-mail was lost, here is the rest... > > -- > > > > At first, when running "xm list", I received this error: > > "ImportError: No module named xen.xm" > > > > I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of > Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved > > > > Then I received this error: > > Error: Unable to connect to xend: No such file or directory. Is xend > running? > > > > So I try starting xend: > > xencommons should be started first. > > > > So I try starting xencommons: > > grep: /proc/xen/capabilities: No such file or directory > > > > A thread on this mailing list suggested I added "none /proc/xen xenfs > defaults 0 0" to /etc/fstab > > I''ve done so, rebooted, but the issue persisted. > > > > Another thread suggested I ran ''insmod xen-evtchn'' and > ''modprobe xen-evtchn'', which gave me this error: > > FATAL: Error inserting xen_evtchn > (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such > device > > > > And now I''m rather stuck. What am I doing wrong? > > > > On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: > > I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > > Here are the steps I did to install it and get around several errors. > > > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > 3) Rebooted into the kernel and made sure it was running: > > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > > > 4) Installed the requirements for compiling: > > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > > 6) No errors except a warning about latex for documentation, so I ran "make > install" > > 7) Rebooted again > > > > At first, when running "xm list", I received this error: > > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 10:32 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I think make world also compiles a kernel which you don''t need in this
case.
Have you tried
cd /usr/src
wget
http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz
<http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz>
tar xvf xen-4.1.0.tar.gz
cd xen-4.1.0
make xen
make tools
make stubdom
cd dist/install
cp -R * /
cd usr/lib64 (if 64bit)
cp -R * /usr/lib64 (if 64bit)
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:30
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
I''m simply following the README, "make world" and then
"make install"
afterwards.
On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Sorry I didn''t realise. What steps are you doing to compile XEN?
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:14
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Okay, I''m not compiling my own kernel though - I''m using the
one in the
Debian packages (2.6.32-5-xen-amd64) as suggested at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
Should I compile my own kernel instead?
On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
When your in the make menuconfig screen, under Device Drivers select the
same as mine, * is for static compile where M is to be used as a module.
Xm is based on python which is being depreciated.
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:06
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Do you have any tutorial/hint on how to statically compile it?
And is there any reason it won''t just work out of the box?
I''ve tried this on CentOs 5 too, but the same errors occur there..
And what exactly is the difference between xm and xl?
On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Statically compile the XEN stuff rather than using it as modules, I had
the same grief as you but went away after doing that.
Also xm commands do not work for some reason but xl works fine.
Ian
From: xen-users-bounces@lists.xensource.com [mailto:
xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen
Sent: 02 June 2011 09:42
To: xen-users@lists.xensource.com
Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Seems like part of my e-mail was lost, here is the rest...
--
At first, when running "xm list", I received this error:
"ImportError: No module named xen.xm"
I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of
Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved
Then I received this error:
Error: Unable to connect to xend: No such file or directory. Is xend
running?
So I try starting xend:
xencommons should be started first.
So I try starting xencommons:
grep: /proc/xen/capabilities: No such file or directory
A thread on this mailing list suggested I added "none /proc/xen xenfs
defaults 0 0" to /etc/fstab
I''ve done so, rebooted, but the issue persisted.
Another thread suggested I ran ''insmod xen-evtchn'' and
''modprobe
xen-evtchn'', which gave me this error:
FATAL: Error inserting xen_evtchn
(/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No
such device
And now I''m rather stuck. What am I doing wrong?
On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote:
I installed Debian Squeeze 6.0 on a server and am now trying to install
Xen 4.1.0 on it (compiled from source, since the packages don''t include
Remus support).
Here are the steps I did to install it and get around several errors.
1) Installed Debian Squeeze 6.0 with default options and software RAID 1
2) Installed the dom0 kernel for Debian as shown at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
3) Rebooted into the kernel and made sure it was running:
Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011
x86_64 GNU/Linux
4) Installed the requirements for compiling:
apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev
libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++
gettext bcc iasl latex2rtf-doc gcc g++ build-essential
5) Downloaded the 4.1.0 source, untarred it and ran "make world"
6) No errors except a warning about latex for documentation, so I ran
"make install"
7) Rebooted again
At first, when running "xm list", I received this error:
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 11:29 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I''ve reinstalled Debian Squeeze and followed those exact commands, getting the same error: root@node1:~# /etc/init.d/xencommons start grep: /proc/xen/capabilities: No such file or directory I don''t think the kernel would be the issue in the first place, because I don''t believe it''s included in the source. As quoted from the README: "Second, you need to acquire a suitable kernel for use in domain 0. If possible you should use a kernel provided by your OS distributor." On Thu, Jun 2, 2011 at 12:32 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I think make world also compiles a kernel which you don’t need in this > case. > > > > Have you tried > > > > cd /usr/src > > > > wget > http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz<http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz> > > tar xvf xen-4.1.0.tar.gz > > > > cd xen-4.1.0 > > make xen > > make tools > > make stubdom > > > > cd dist/install > > cp -R * / > > > > cd usr/lib64 (if 64bit) > > > > cp -R * /usr/lib64 (if 64bit) > > > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:30 > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > I''m simply following the README, "make world" and then "make install" > afterwards. > > > > On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Sorry I didn’t realise. What steps are you doing to compile XEN? > > > > > > > > > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:14 > > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Okay, I''m not compiling my own kernel though - I''m using the one in the > Debian packages (2.6.32-5-xen-amd64) as suggested at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > Should I compile my own kernel instead? > > > > On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > When your in the make menuconfig screen, under Device Drivers select the > same as mine, * is for static compile where M is to be used as a module. > > > > > > > > Xm is based on python which is being depreciated. > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:06 > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Do you have any tutorial/hint on how to statically compile it? > > And is there any reason it won''t just work out of the box? > I''ve tried this on CentOs 5 too, but the same errors occur there.. > > > > And what exactly is the difference between xm and xl? > > > > On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Statically compile the XEN stuff rather than using it as modules, I had the > same grief as you but went away after doing that. > > > > Also xm commands do not work for some reason but xl works fine. > > > > Ian > > > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Wouter van Eekelen > *Sent:* 02 June 2011 09:42 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Seems like part of my e-mail was lost, here is the rest... > > -- > > > > At first, when running "xm list", I received this error: > > "ImportError: No module named xen.xm" > > > > I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of > Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved > > > > Then I received this error: > > Error: Unable to connect to xend: No such file or directory. Is xend > running? > > > > So I try starting xend: > > xencommons should be started first. > > > > So I try starting xencommons: > > grep: /proc/xen/capabilities: No such file or directory > > > > A thread on this mailing list suggested I added "none /proc/xen xenfs > defaults 0 0" to /etc/fstab > > I''ve done so, rebooted, but the issue persisted. > > > > Another thread suggested I ran ''insmod xen-evtchn'' and > ''modprobe xen-evtchn'', which gave me this error: > > FATAL: Error inserting xen_evtchn > (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such > device > > > > And now I''m rather stuck. What am I doing wrong? > > > > On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: > > I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > > Here are the steps I did to install it and get around several errors. > > > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > 3) Rebooted into the kernel and made sure it was running: > > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > > > 4) Installed the requirements for compiling: > > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > > 6) No errors except a warning about latex for documentation, so I ran "make > install" > > 7) Rebooted again > > > > At first, when running "xm list", I received this error: > > > > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 12:16 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I would compile it from source and use the menu options I suggested.
Do you have the xen fs mounted?
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 12:29
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
I''ve reinstalled Debian Squeeze and followed those exact commands,
getting the same error:
root@node1:~# /etc/init.d/xencommons start
grep: /proc/xen/capabilities: No such file or directory
I don''t think the kernel would be the issue in the first place, because
I don''t believe it''s included in the source.
As quoted from the README: "Second, you need to acquire a suitable
kernel for use in domain 0. If
possible you should use a kernel provided by your OS distributor."
On Thu, Jun 2, 2011 at 12:32 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
I think make world also compiles a kernel which you don''t need in this
case.
Have you tried
cd /usr/src
wget
http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz
<http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz>
tar xvf xen-4.1.0.tar.gz
cd xen-4.1.0
make xen
make tools
make stubdom
cd dist/install
cp -R * /
cd usr/lib64 (if 64bit)
cp -R * /usr/lib64 (if 64bit)
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:30
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
I''m simply following the README, "make world" and then
"make install"
afterwards.
On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Sorry I didn''t realise. What steps are you doing to compile XEN?
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:14
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Okay, I''m not compiling my own kernel though - I''m using the
one in the
Debian packages (2.6.32-5-xen-amd64) as suggested at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
Should I compile my own kernel instead?
On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
When your in the make menuconfig screen, under Device Drivers select the
same as mine, * is for static compile where M is to be used as a module.
Xm is based on python which is being depreciated.
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:06
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Do you have any tutorial/hint on how to statically compile it?
And is there any reason it won''t just work out of the box?
I''ve tried this on CentOs 5 too, but the same errors occur there..
And what exactly is the difference between xm and xl?
On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Statically compile the XEN stuff rather than using it as modules, I had
the same grief as you but went away after doing that.
Also xm commands do not work for some reason but xl works fine.
Ian
From: xen-users-bounces@lists.xensource.com [mailto:
xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen
Sent: 02 June 2011 09:42
To: xen-users@lists.xensource.com
Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Seems like part of my e-mail was lost, here is the rest...
--
At first, when running "xm list", I received this error:
"ImportError: No module named xen.xm"
I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of
Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved
Then I received this error:
Error: Unable to connect to xend: No such file or directory. Is xend
running?
So I try starting xend:
xencommons should be started first.
So I try starting xencommons:
grep: /proc/xen/capabilities: No such file or directory
A thread on this mailing list suggested I added "none /proc/xen xenfs
defaults 0 0" to /etc/fstab
I''ve done so, rebooted, but the issue persisted.
Another thread suggested I ran ''insmod xen-evtchn'' and
''modprobe
xen-evtchn'', which gave me this error:
FATAL: Error inserting xen_evtchn
(/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No
such device
And now I''m rather stuck. What am I doing wrong?
On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote:
I installed Debian Squeeze 6.0 on a server and am now trying to install
Xen 4.1.0 on it (compiled from source, since the packages don''t include
Remus support).
Here are the steps I did to install it and get around several errors.
1) Installed Debian Squeeze 6.0 with default options and software RAID 1
2) Installed the dom0 kernel for Debian as shown at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
3) Rebooted into the kernel and made sure it was running:
Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011
x86_64 GNU/Linux
4) Installed the requirements for compiling:
apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev
libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++
gettext bcc iasl latex2rtf-doc gcc g++ build-essential
5) Downloaded the 4.1.0 source, untarred it and ran "make world"
6) No errors except a warning about latex for documentation, so I ran
"make install"
7) Rebooted again
At first, when running "xm list", I received this error:
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 12:24 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
But the Xen manual very clearly mentions the kernel from Debian, and that it''s highly recommended over compiling from source? Is this really the best way? Why doesn''t it work with the kernel it says it should work with? I just want to run Xen with Remus support on either CentOs or Debian. The packages of Debian work perfectly, they just lack Remus support. Can''t I add remus separately? (e.g. like before it was integrated into xen) On Thu, Jun 2, 2011 at 2:16 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> I would compile it from source and use the menu options I suggested. > > > > Do you have the xen fs mounted? > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 12:29 > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > I''ve reinstalled Debian Squeeze and followed those exact commands, getting > the same error: > > root@node1:~# /etc/init.d/xencommons start > > grep: /proc/xen/capabilities: No such file or directory > > > > I don''t think the kernel would be the issue in the first place, because I > don''t believe it''s included in the source. > > As quoted from the README: "Second, you need to acquire a suitable kernel > for use in domain 0. If > > possible you should use a kernel provided by your OS distributor." > > > > On Thu, Jun 2, 2011 at 12:32 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > I think make world also compiles a kernel which you don’t need in this > case. > > > > Have you tried > > > > cd /usr/src > > > > wget > http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz<http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz> > > tar xvf xen-4.1.0.tar.gz > > > > cd xen-4.1.0 > > make xen > > make tools > > make stubdom > > > > cd dist/install > > cp -R * / > > > > cd usr/lib64 (if 64bit) > > > > cp -R * /usr/lib64 (if 64bit) > > > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:30 > > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > I''m simply following the README, "make world" and then "make install" > afterwards. > > > > On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Sorry I didn’t realise. What steps are you doing to compile XEN? > > > > > > > > > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:14 > > > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Okay, I''m not compiling my own kernel though - I''m using the one in the > Debian packages (2.6.32-5-xen-amd64) as suggested at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > Should I compile my own kernel instead? > > > > On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > When your in the make menuconfig screen, under Device Drivers select the > same as mine, * is for static compile where M is to be used as a module. > > > > > > > > Xm is based on python which is being depreciated. > > > > > > *From:* Wouter van Eekelen [mailto:me@woet.me] > *Sent:* 02 June 2011 11:06 > *To:* Ian Tobin > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Do you have any tutorial/hint on how to statically compile it? > > And is there any reason it won''t just work out of the box? > I''ve tried this on CentOs 5 too, but the same errors occur there.. > > > > And what exactly is the difference between xm and xl? > > > > On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Statically compile the XEN stuff rather than using it as modules, I had the > same grief as you but went away after doing that. > > > > Also xm commands do not work for some reason but xl works fine. > > > > Ian > > > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Wouter van Eekelen > *Sent:* 02 June 2011 09:42 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] Re: Xen 4.1.0 compiled from source on Debian > Squeeze 6.0 > > > > Seems like part of my e-mail was lost, here is the rest... > > -- > > > > At first, when running "xm list", I received this error: > > "ImportError: No module named xen.xm" > > > > I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of > Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved > > > > Then I received this error: > > Error: Unable to connect to xend: No such file or directory. Is xend > running? > > > > So I try starting xend: > > xencommons should be started first. > > > > So I try starting xencommons: > > grep: /proc/xen/capabilities: No such file or directory > > > > A thread on this mailing list suggested I added "none /proc/xen xenfs > defaults 0 0" to /etc/fstab > > I''ve done so, rebooted, but the issue persisted. > > > > Another thread suggested I ran ''insmod xen-evtchn'' and > ''modprobe xen-evtchn'', which gave me this error: > > FATAL: Error inserting xen_evtchn > (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such > device > > > > And now I''m rather stuck. What am I doing wrong? > > > > On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote: > > I installed Debian Squeeze 6.0 on a server and am now trying to install Xen > 4.1.0 on it (compiled from source, since the packages don''t include Remus > support). > > Here are the steps I did to install it and get around several errors. > > > > 1) Installed Debian Squeeze 6.0 with default options and software RAID 1 > > 2) Installed the dom0 kernel for Debian as shown at > http://wiki.xensource.com/xenwiki/XenDom0Kernels > > 3) Rebooted into the kernel and made sure it was running: > > Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011 x86_64 > GNU/Linux > > > > 4) Installed the requirements for compiling: > > apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev > libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++ gettext > bcc iasl latex2rtf-doc gcc g++ build-essential > > > > 5) Downloaded the 4.1.0 source, untarred it and ran "make world" > > 6) No errors except a warning about latex for documentation, so I ran "make > install" > > 7) Rebooted again > > > > At first, when running "xm list", I received this error: > > > > > > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-Jun-02 12:29 UTC
RE: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I cant answer that im not a developer J
I always use from source but that is my preference. Im guessing remus
support needs to be compiled in but I maybe wrong. All im saying is that
I have from source a working system on Debian 6 - XEN 4.1
Ian
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 13:24
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
But the Xen manual very clearly mentions the kernel from Debian, and
that it''s highly recommended over compiling from source?
Is this really the best way? Why doesn''t it work with the kernel it
says
it should work with?
I just want to run Xen with Remus support on either CentOs or Debian.
The packages of Debian work perfectly, they just lack Remus support.
Can''t I add remus separately? (e.g. like before it was integrated into
xen)
On Thu, Jun 2, 2011 at 2:16 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
I would compile it from source and use the menu options I suggested.
Do you have the xen fs mounted?
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 12:29
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
I''ve reinstalled Debian Squeeze and followed those exact commands,
getting the same error:
root@node1:~# /etc/init.d/xencommons start
grep: /proc/xen/capabilities: No such file or directory
I don''t think the kernel would be the issue in the first place, because
I don''t believe it''s included in the source.
As quoted from the README: "Second, you need to acquire a suitable
kernel for use in domain 0. If
possible you should use a kernel provided by your OS distributor."
On Thu, Jun 2, 2011 at 12:32 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
I think make world also compiles a kernel which you don''t need in this
case.
Have you tried
cd /usr/src
wget
http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz
<http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz>
tar xvf xen-4.1.0.tar.gz
cd xen-4.1.0
make xen
make tools
make stubdom
cd dist/install
cp -R * /
cd usr/lib64 (if 64bit)
cp -R * /usr/lib64 (if 64bit)
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:30
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
I''m simply following the README, "make world" and then
"make install"
afterwards.
On Thu, Jun 2, 2011 at 12:28 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Sorry I didn''t realise. What steps are you doing to compile XEN?
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:14
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Okay, I''m not compiling my own kernel though - I''m using the
one in the
Debian packages (2.6.32-5-xen-amd64) as suggested at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
Should I compile my own kernel instead?
On Thu, Jun 2, 2011 at 12:11 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
When your in the make menuconfig screen, under Device Drivers select the
same as mine, * is for static compile where M is to be used as a module.
Xm is based on python which is being depreciated.
From: Wouter van Eekelen [mailto:me@woet.me]
Sent: 02 June 2011 11:06
To: Ian Tobin
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Do you have any tutorial/hint on how to statically compile it?
And is there any reason it won''t just work out of the box?
I''ve tried this on CentOs 5 too, but the same errors occur there..
And what exactly is the difference between xm and xl?
On Thu, Jun 2, 2011 at 12:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote:
Statically compile the XEN stuff rather than using it as modules, I had
the same grief as you but went away after doing that.
Also xm commands do not work for some reason but xl works fine.
Ian
From: xen-users-bounces@lists.xensource.com [mailto:
xen-users-bounces@lists.xensource.com] On Behalf Of Wouter van Eekelen
Sent: 02 June 2011 09:42
To: xen-users@lists.xensource.com
Subject: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian
Squeeze 6.0
Seems like part of my e-mail was lost, here is the rest...
--
At first, when running "xm list", I received this error:
"ImportError: No module named xen.xm"
I saw that /usr/lib/python2.6/site-packages/xen wasn''t in sys.path of
Python, so I symlinked it to /usr/lib/python2.6/xen - problem solved
Then I received this error:
Error: Unable to connect to xend: No such file or directory. Is xend
running?
So I try starting xend:
xencommons should be started first.
So I try starting xencommons:
grep: /proc/xen/capabilities: No such file or directory
A thread on this mailing list suggested I added "none /proc/xen xenfs
defaults 0 0" to /etc/fstab
I''ve done so, rebooted, but the issue persisted.
Another thread suggested I ran ''insmod xen-evtchn'' and
''modprobe
xen-evtchn'', which gave me this error:
FATAL: Error inserting xen_evtchn
(/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No
such device
And now I''m rather stuck. What am I doing wrong?
On Thu, Jun 2, 2011 at 10:39 AM, Wouter van Eekelen <me@woet.me> wrote:
I installed Debian Squeeze 6.0 on a server and am now trying to install
Xen 4.1.0 on it (compiled from source, since the packages don''t include
Remus support).
Here are the steps I did to install it and get around several errors.
1) Installed Debian Squeeze 6.0 with default options and software RAID 1
2) Installed the dom0 kernel for Debian as shown at
http://wiki.xensource.com/xenwiki/XenDom0Kernels
3) Rebooted into the kernel and made sure it was running:
Linux node1 2.6.32-5-xen-amd64 #1 SMP Thu May 19 01:16:47 UTC 2011
x86_64 GNU/Linux
4) Installed the requirements for compiling:
apt-get install zlib1g-dev python-dev libncurses-dev uuid-dev python-dev
libncurses-dev libssl-dev xorg-dev uuid-dev build-essential gcc g++
gettext bcc iasl latex2rtf-doc gcc g++ build-essential
5) Downloaded the 4.1.0 source, untarred it and ran "make world"
6) No errors except a warning about latex for documentation, so I ran
"make install"
7) Rebooted again
At first, when running "xm list", I received this error:
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fantu
2011-Jun-02 12:30 UTC
[Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
you must add in /etc/modules xenfs xen-evtchn blktap about start of xend and xendomains you must apply this patch: http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/99e9bed36e2e for xl only also this: http://xen.1045712.n5.nabble.com/PATCH-2-of-2-xendomains-remove-unnecessary-dependency-of-xend-tp4429591p4429914.html And for enable service: - for xl only and xend: insserv xencommons - for xend: insserv xend - for xendomains insserv xendomains -- View this message in context: http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4447910.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 13:14 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I''ve done that, this does not solve the issue. When I load them manually, I get this error: root@node1:~# modprobe xenfs root@node1:~# modprobe xen-evtchn FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device root@node1:~# modprobe blktap FATAL: Error inserting blktap (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/blktap/blktap.ko): No such device On Thu, Jun 2, 2011 at 2:30 PM, Fantu <fantonifabio@tiscali.it> wrote:> you must add in /etc/modules > xenfs > xen-evtchn > blktap > > about start of xend and xendomains you must apply this patch: > http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/99e9bed36e2e > for xl only also this: > > http://xen.1045712.n5.nabble.com/PATCH-2-of-2-xendomains-remove-unnecessary-dependency-of-xend-tp4429591p4429914.html > And for enable service: > - for xl only and xend: > insserv xencommons > - for xend: > insserv xend > - for xendomains > insserv xendomains > > -- > View this message in context: > http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4447910.html > Sent from the Xen - User mailing list archive at Nabble.com. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fantu
2011-Jun-02 13:30 UTC
[Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
your message show how files are missed but in squeeze package there are: http://packages.debian.org/squeeze/amd64/linux-image-2.6.32-5-xen-amd64/filelist Also I have xen dom0 Squeeze with 2.6.32-5-xen-amd64 kernel from Squeeze repository, xen from source ecc and work -- View this message in context: http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4448125.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 13:34 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
No, the error says it cannot find the device. The files are there. root@node1:~# modprobe xen-evtchn FATAL: Error inserting xen_evtchn (/lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/xen-evtchn.ko): No such device root@node1:~# ls -la /lib/modules/2.6.32-5-xen-amd64/kernel/drivers/xen/ total 52 drwxr-xr-x 4 root root 4096 Jun 2 13:12 . drwxr-xr-x 60 root root 4096 Jun 2 13:12 .. -rw-r--r-- 1 root root 8744 May 19 03:47 acpi_processor.ko drwxr-xr-x 2 root root 4096 Jun 2 13:12 blktap -rw-r--r-- 1 root root 7456 May 19 03:47 xen_acpi_memhotplug.ko -rw-r--r-- 1 root root 14656 May 19 03:47 xen-evtchn.ko drwxr-xr-x 2 root root 4096 Jun 2 13:12 xenfs root@node1:~# On Thu, Jun 2, 2011 at 3:30 PM, Fantu <fantonifabio@tiscali.it> wrote:> your message show how files are missed but in squeeze package there are: > > http://packages.debian.org/squeeze/amd64/linux-image-2.6.32-5-xen-amd64/filelist > Also I have xen dom0 Squeeze with 2.6.32-5-xen-amd64 kernel from Squeeze > repository, xen from source ecc and work > > -- > View this message in context: > http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4448125.html > Sent from the Xen - User mailing list archive at Nabble.com. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fantu
2011-Jun-02 13:41 UTC
[Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
try to check grub.cfg, for example from my config:
menuentry ''Squeeze con Linux 2.6.32-5-xen-amd64 e XEN 4 -
RAID'' --class
debian --class gnu-linux --class gnu --class os --class xen {
set root=''(RAID-ROOT)''
echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
multiboot /boot/xen.gz placeholder dom0_mem=1024M
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
root=/dev/mapper/RAID-ROOT ro quiet
echo ''Loading initial ramdisk ...''
module /boot/initrd.img-2.6.32-5-xen-amd64
}
in particular must have:
multiboot /boot/xen.gz placeholder
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
--
View this message in context:
http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4448153.html
Sent from the Xen - User mailing list archive at Nabble.com.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Wouter van Eekelen
2011-Jun-02 13:50 UTC
Re: [Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
Those lines weren''t in my grub.cfg, I''ve changed it, but the
problem is the
same.
root@node1:~# /etc/init.d/xencommons start
grep: /proc/xen/capabilities: No such file or directory
menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64''
--class debian
--class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root=''(md0)''
search --no-floppy --fs-uuid --set
db1ec457-961b-4af7-87f9-6427955363e4
echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
multiboot /boot/xen.gz placeholder
linux /vmlinuz-2.6.32-5-xen-amd64
root=UUID=4b009e73-747e-4f43-98bf-56d89069318c ro quiet
echo ''Loading initial ramdisk ...''
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
initrd /initrd.img-2.6.32-5-xen-amd64
}
On Thu, Jun 2, 2011 at 3:41 PM, Fantu <fantonifabio@tiscali.it> wrote:
> try to check grub.cfg, for example from my config:
>
> menuentry ''Squeeze con Linux 2.6.32-5-xen-amd64 e XEN 4 -
RAID'' --class
> debian --class gnu-linux --class gnu --class os --class xen {
> set root=''(RAID-ROOT)''
> echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
> multiboot /boot/xen.gz placeholder dom0_mem=1024M
> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> root=/dev/mapper/RAID-ROOT ro quiet
> echo ''Loading initial ramdisk ...''
> module /boot/initrd.img-2.6.32-5-xen-amd64
> }
>
> in particular must have:
> multiboot /boot/xen.gz placeholder
> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
>
> --
> View this message in context:
>
http://xen.1045712.n5.nabble.com/Xen-4-1-0-compiled-from-source-on-Debian-Squeeze-6-0-tp4447571p4448153.html
> Sent from the Xen - User mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Iordan
2011-Jun-03 21:15 UTC
[Xen-users] Re: Xen 4.1.0 compiled from source on Debian Squeeze 6.0
I also had the same problem, but the resolution was indeed to make sure
I am booting with the multiboot and module lines in grub.cfg.
Here is the menuentry which works for me (please note, I had to break up
the line that starts with "module" into two lines):
menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
4.0-amd64'' --
class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set 417d0db7-ff6f-421e-bf6c-cc28f43b548e
echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
multiboot /xen-4.0-amd64.gz placeholder
module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=bd344e4b-db98-48c8-8de2-5777d78eeb94 ro quiet
echo ''Loading initial ramdisk ...''
module /initrd.img-2.6.32-5-xen-amd64
}
I also thought that I was going crazy, because I was sure I am booting with
those lines, but I wasn''t. There was another entry above this one,
titled
very similarly (except, it was missing the "XEN 4.0-amd64" at the end
of the
title, which DIDN''T have these lines.
Cheers!
Iordan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users