Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Xen>
  3. Users
xend startup problem (xen 2.0.5)
michi+xen at relay3
Apr 15, 2005, 2:09 AM
Post #1 of 4 (1125 views)
Permalink
Hi all,

if´ve started looking at xen, and got some 'newbie' problems on Fedora
Core3. I´ve already searched google and the ListArchives but didnt find
any clue for solving the following startup Error of xend.

-After booting xen Kernel (2.6.10-xen0), i tryed to start 'xend' with
command `$ xend start`
`$ echo $? prints 0`

the /var/log/xend.log shows
`[2005-04-15 10:53:27 xend] INFO (SrvDaemon:612) Xend Daemon started`
but /var/log/xend-debug.log shows
Traceback (most recent call last):
File "/usr/sbin/xend", line 121, in ?
sys.exit(main())
File "/usr/sbin/xend", line 107, in main
return daemon.start()
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 527, in
start
self.run()
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 616, in run
self.listenVirq()
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 641, in
listenVirq
virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC)
File "/usr/lib/python/xen/xend/server/channel.py", line 110, in
virqChannel
chan = VirqChannel(self, virq)
File "/usr/lib/python/xen/xend/server/channel.py", line 201, in
__init__
self.port = factory.notifier.bind_virq(virq)
AttributeError: bind_virq

so there seems to bee one bug == exit code,
and doest anyone knows how to solve this Problem ?
my /etc/xen/xend-config.sxp is unchanged as from 2.0.5 source
and contains following values
`$egrep -ve '^#' /etc/xen/xend-config.sxp`
(xend-port 8000)
(xend-event-port 8001)
(xend-address 'localhost')
(console-port-base 9600)
(console-address 'localhost')
(network-script network)
(vif-bridge xen-br0)
(vif-script vif-bridge)
(vif-antispoof no)
(block-file block-file)
(block-enbd block-enbd)

thanks for any hints
Kind regards
Michael Lang

--
Michael Lang <Michael.Lang@eunet.co.at>
--
Michael Lang <michi+xen@relay3.jackal-net.at>


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: xend startup problem (xen 2.0.5) [ In reply to ]
maw48 at cl
Apr 15, 2005, 6:49 AM
Post #2 of 4 (1108 views)
Permalink
That looks weird - how did you install this system? If the install worked
properly, that error shouldn't be possible...

Mark

On Friday 15 April 2005 10:09, Michael Lang wrote:
> Hi all,
>
> if´ve started looking at xen, and got some 'newbie' problems on Fedora
> Core3. I´ve already searched google and the ListArchives but didnt find
> any clue for solving the following startup Error of xend.
>
> -After booting xen Kernel (2.6.10-xen0), i tryed to start 'xend' with
> command `$ xend start`
> `$ echo $? prints 0`
>
> the /var/log/xend.log shows
> `[2005-04-15 10:53:27 xend] INFO (SrvDaemon:612) Xend Daemon started`
> but /var/log/xend-debug.log shows
> Traceback (most recent call last):
> File "/usr/sbin/xend", line 121, in ?
> sys.exit(main())
> File "/usr/sbin/xend", line 107, in main
> return daemon.start()
> File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 527, in
> start
> self.run()
> File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 616, in run
> self.listenVirq()
> File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 641, in
> listenVirq
> virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC)
> File "/usr/lib/python/xen/xend/server/channel.py", line 110, in
> virqChannel
> chan = VirqChannel(self, virq)
> File "/usr/lib/python/xen/xend/server/channel.py", line 201, in
> __init__
> self.port = factory.notifier.bind_virq(virq)
> AttributeError: bind_virq
>
> so there seems to bee one bug == exit code,
> and doest anyone knows how to solve this Problem ?
> my /etc/xen/xend-config.sxp is unchanged as from 2.0.5 source
> and contains following values
> `$egrep -ve '^#' /etc/xen/xend-config.sxp`
> (xend-port 8000)
> (xend-event-port 8001)
> (xend-address 'localhost')
> (console-port-base 9600)
> (console-address 'localhost')
> (network-script network)
> (vif-bridge xen-br0)
> (vif-script vif-bridge)
> (vif-antispoof no)
> (block-file block-file)
> (block-enbd block-enbd)
>
> thanks for any hints
> Kind regards
> Michael Lang
>
> --
> Michael Lang <Michael.Lang@eunet.co.at>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: xend startup problem (xen 2.0.5) [ In reply to ]
michi+xen at relay3
Apr 15, 2005, 7:26 AM
Post #3 of 4 (1104 views)
Permalink
On Fri, 2005-04-15 at 14:49 +0100, Mark Williamson wrote:
> That looks weird - how did you install this system? If the install worked
> properly, that error shouldn't be possible...

installed as written in FAQ/Readme.

downloaded xen-2.0.5-src.tgz
untared it
did
`$ sh install.sh` # initial the script downloade
linux-2.6.10.tar.gz for me
`$ make && make install`

i attached the install.sh ; make ; make install log, hope you
can help me solve this ....

Kind regards
Michael Lang

>
> Mark
>
> On Friday 15 April 2005 10:09, Michael Lang wrote:
> > Hi all,
> >
> > if´ve started looking at xen, and got some 'newbie' problems on Fedora
> > Core3. I´ve already searched google and the ListArchives but didnt find
> > any clue for solving the following startup Error of xend.
> >
> > -After booting xen Kernel (2.6.10-xen0), i tryed to start 'xend' with
> > command `$ xend start`
> > `$ echo $? prints 0`
> >
> > the /var/log/xend.log shows
> > `[2005-04-15 10:53:27 xend] INFO (SrvDaemon:612) Xend Daemon started`
> > but /var/log/xend-debug.log shows
> > Traceback (most recent call last):
> > File "/usr/sbin/xend", line 121, in ?
> > sys.exit(main())
> > File "/usr/sbin/xend", line 107, in main
> > return daemon.start()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 527, in
> > start
> > self.run()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 616, in run
> > self.listenVirq()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 641, in
> > listenVirq
> > virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC)
> > File "/usr/lib/python/xen/xend/server/channel.py", line 110, in
> > virqChannel
> > chan = VirqChannel(self, virq)
> > File "/usr/lib/python/xen/xend/server/channel.py", line 201, in
> > __init__
> > self.port = factory.notifier.bind_virq(virq)
> > AttributeError: bind_virq
> >
> > so there seems to bee one bug == exit code,
> > and doest anyone knows how to solve this Problem ?
> > my /etc/xen/xend-config.sxp is unchanged as from 2.0.5 source
> > and contains following values
> > `$egrep -ve '^#' /etc/xen/xend-config.sxp`
> > (xend-port 8000)
> > (xend-event-port 8001)
> > (xend-address 'localhost')
> > (console-port-base 9600)
> > (console-address 'localhost')
> > (network-script network)
> > (vif-bridge xen-br0)
> > (vif-script vif-bridge)
> > (vif-antispoof no)
> > (block-file block-file)
> > (block-enbd block-enbd)
> >
> > thanks for any hints
> > Kind regards
> > Michael Lang
> >
> > --
> > Michael Lang <Michael.Lang@eunet.co.at>

Attached Files:

Re: xend startup problem (xen 2.0.5) [ In reply to ]
michi+xen at relay3
Apr 16, 2005, 10:23 PM
Post #4 of 4 (1107 views)
Permalink
On Fri, 2005-04-15 at 14:49 +0100, Mark Williamson wrote:
> That looks weird - how did you install this system? If the install worked
> properly, that error shouldn't be possible...

Hi Mark,

i retryed on a different FedoraCore3 where it worked without any
problem, so possible my enviroment is/was as mess or did someone already
report, that trying to build NFORCE Driver broke there XEN ? (i´ve found
the NFORCE dosesnt work rigth now in the archives later)

But i can report that building and using Xen on a VMWare GSX Server
3.1.0-9089 using FedoraCore3 as Guest OS works just fine.

Greetz mIke

>
> Mark
>
> On Friday 15 April 2005 10:09, Michael Lang wrote:
> > Hi all,
> >
> > if´ve started looking at xen, and got some 'newbie' problems on Fedora
> > Core3. I´ve already searched google and the ListArchives but didnt find
> > any clue for solving the following startup Error of xend.
> >
> > -After booting xen Kernel (2.6.10-xen0), i tryed to start 'xend' with
> > command `$ xend start`
> > `$ echo $? prints 0`
> >
> > the /var/log/xend.log shows
> > `[2005-04-15 10:53:27 xend] INFO (SrvDaemon:612) Xend Daemon started`
> > but /var/log/xend-debug.log shows
> > Traceback (most recent call last):
> > File "/usr/sbin/xend", line 121, in ?
> > sys.exit(main())
> > File "/usr/sbin/xend", line 107, in main
> > return daemon.start()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 527, in
> > start
> > self.run()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 616, in run
> > self.listenVirq()
> > File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 641, in
> > listenVirq
> > virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC)
> > File "/usr/lib/python/xen/xend/server/channel.py", line 110, in
> > virqChannel
> > chan = VirqChannel(self, virq)
> > File "/usr/lib/python/xen/xend/server/channel.py", line 201, in
> > __init__
> > self.port = factory.notifier.bind_virq(virq)
> > AttributeError: bind_virq
> >
> > so there seems to bee one bug == exit code,
> > and doest anyone knows how to solve this Problem ?
> > my /etc/xen/xend-config.sxp is unchanged as from 2.0.5 source
> > and contains following values
> > `$egrep -ve '^#' /etc/xen/xend-config.sxp`
> > (xend-port 8000)
> > (xend-event-port 8001)
> > (xend-address 'localhost')
> > (console-port-base 9600)
> > (console-address 'localhost')
> > (network-script network)
> > (vif-bridge xen-br0)
> > (vif-script vif-bridge)
> > (vif-antispoof no)
> > (block-file block-file)
> > (block-enbd block-enbd)
> >
> > thanks for any hints
> > Kind regards
> > Michael Lang
> >
> > --
> > Michael Lang <Michael.Lang@eunet.co.at>
--
Michael Lang <michi+xen@relay3.jackal-net.at>


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

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal