No eth0 after installation

No eth0 after installation

[Kathy Chen]

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Hi,
 
I just installed the latest unstable version.
"make world" and "make install" seem both successful.
After setting the correct boot entry and rebooting the machine, eth0 doesn't work.
"ifconfig" shows only lo, and in the menu "System Settings/Network", it shows eth0 is inactive. Clicking "Activate" results in an error saying that eth0 is not present.
 
Another thing is that on my other machine, although "make world" and "make install" are both successful, command 'xend' doesn't work. Error message says 
--Traceback (most recent call last):
--  File "/usr/sbin/xend", line 23, in ?
--    from xen.xend.server import SrvDaemon
--  File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
--line 18, in ?
--    from twisted.internet import pollreactor
--ImportError: No module named twisted.internet
I seached the related messages in the mailing list, but they don't help.
 
Any suggestions?
 
Thanks.
Kathy.
 
 

		
---------------------------------
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!

[-- Attachment #2: Type: text/html, Size: 1394 bytes --]

Re: No eth0 after installation

[Ian Pratt]

> Hi,
>  
> I just installed the latest unstable version.
> "make world" and "make install" seem both successful.
> After setting the correct boot entry and rebooting the machine, eth0 doesn't work.
> "ifconfig" shows only lo, and in the menu "System Settings/Network", it shows eth0 is inactive. Clicking "Activate" results in an error saying that eth0 is not present.

Sounds like the driver for your ethernet card isn't in the
standard domain 0 build.

edit install/boot/config-2.4.26-xen0 and run 'make world' 'make
install' again. e.g. if you had an SK98 card change:

# CONFIG_SK98LIN is not set

to:

CONFIG_SK98LIN=y

[once you find your way around the build system there's a much
quicker way to do this, but I won't complicate matters]

> Another thing is that on my other machine, although "make world" and "make install" are both successful, command 'xend' doesn't work. Error message says 
> --Traceback (most recent call last):
> --  File "/usr/sbin/xend", line 23, in ?
> --    from xen.xend.server import SrvDaemon
> --  File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> --line 18, in ?
> --    from twisted.internet import pollreactor
> --ImportError: No module named twisted.internet
> I seached the related messages in the mailing list, but they don't help.
>  
> Any suggestions?

You need to install Twisted version 1.3.0. (earlier versions
don't work).

If there's no suitable package you can download for your distro,
you can install from source with 'make install-twisted'


Ian


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: No eth0 after installation

[Niraj Tolia]

Kathy,

You need to install twisted
<http://twisted.sourceforge.net/Twisted_NoDocs-1.3.0.tar.gz>. I
believe that Ian had mentioned that the makefile also has a
'twisted-install' option but I haven't tried it.

Let us know if things don't work after you do this.

Niraj


----- Original Message -----
From: Kathy Chen <kathy_ios@yahoo.com>
Date: Thu, 15 Jul 2004 09:31:05 -0700 (PDT)
Subject: [Xen-devel] No eth0 after installation
To: xen-devel@lists.sourceforge.net


Hi,

 

I just installed the latest unstable version.

"make world" and "make install" seem both successful.

After setting the correct boot entry and rebooting the machine, eth0
doesn't work.

"ifconfig" shows only lo, and in the menu "System Settings/Network",
it shows eth0 is inactive. Clicking "Activate" results in an error
saying that eth0 is not present.

 

Another thing is that on my other machine, although "make world" and
"make install" are both successful, command 'xend' doesn't work. Error
message says

--Traceback (most recent call last):
--  File "/usr/sbin/xend", line 23, in ?
--    from xen.xend.server import SrvDaemon
--  File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
--line 18, in ?
--    from twisted.internet import pollreactor
--ImportError: No module named twisted.internet
I seached the related messages in the mailing list, but they don't help.

 

Any suggestions?

 

Thanks.

Kathy.

 

 


		________________________________
Do you Yahoo!?

Yahoo! Mail is new and improved - Check it out!


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

'xm_vars' not defined error

[Kathy Chen]

First, thanks Ian and Niraj's replies.
The previous prolem got solved.

Now I have some new problem when starting a new
domain.
Everything goes well when I installed the latest
version, rebooted the machine, and made "xend start".
But when I modified the xmdefaults to create a new
domain, some error appears, shown as following:

$xm create -D vmid=1 -f dom1.conf -i ***.***.***.***
Traceback (most recent call last):
  File "/usr/sbin/xm", line 6, in ?
    main.main(sys.argv)
  File
"/usr/lib/python2.2/site-packages/xen/xm/main.py",
line 448, in main
    xm.main(args)
  File
"/usr/lib/python2.2/site-packages/xen/xm/main.py",
line 79, in main
    p.main(args[1:])
  File
"/usr/lib/python2.2/site-packages/xen/xm/main.py",
line 153, in main
    create.main(args)
  File
"/usr/lib/python2.2/site-packages/xen/xm/create.py",
line 359, in main
    opts.load_defaults()
  File
"/usr/lib/python2.2/site-packages/xen/xm/opts.py",
line 273, in load_defaults
    self.load(p)
  File
"/usr/lib/python2.2/site-packages/xen/xm/opts.py",
line 297, in load
    execfile(defaults, globals, locals)
  File "dom1.conf", line 16, in ?
    xm_vars.var('vmid', use="Virtual machine id.
Integer greater than 0.", check=vmid_check)
NameError: name 'xm_vars' is not defined.

In the xmdefaults' comment, it says that 'xm_vars' is
defined automatically. So what's the possible reason
fo r this error?

Thanks a lot for your hard work!
Kathy

Besides, the following is the output of the "xend
start", I guess it shows xend starts correctly:

brctl addbr nbe-br
brctl sethello nbe-br 0
brctl setfd nbe-br 0
brctl stp nbe-br off
ifconfig nbe-br *.*.*.*.* netmask *.*.*.*.* broadcast
*.*.*.*.* up
route add default gateway *.*.*.*.* dev nbe-br
brctl addif nbe-br eth0
ifconfig eth0 0.0.0.0
initial_refresh>
db dom= ['domain', ['id', '0'], ['name', 'Domain-0'],
['memory', '119']]
xc dom= {'cpu_time': 348750378835L, 'name':
'Domain-0', 'dying': 0, 'dom': 0, 'maxmem_kb': 131072,
'paused': 0, 'crashed': 0, 'running': 1,
'shutdown_reason': 0, 'shutdown': 0, 'mem_kb': 121856,
'cpu': 0, 'blocked': 0}
dom= 0 config= ['domain', ['id', '0'], ['name',
'Domain-0'], ['memory', '119']]
dom= 0 new
XendDomain>reap>
XendDomain>reap<
XendDomain>initial_refresh> doms:
dom domain id=0 name=Domain-0 memory=119
EVENT> xend.start 0


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: 'xm_vars' not defined error

[Ian Pratt]

> But when I modified the xmdefaults to create a new
> domain, some error appears, shown as following:

The error message is pants, but I think it's a duff invocation is
the root cause of your problem.

First, you no longer need '-D' infront of defining variables. I
believe variables need to come at the end of the command line.
Further, you can no longer use '-i' to define the domain's IP
address: use ip=. So:

xm create -f dom1.conf vmid=1 ip='1.2.3.4'

If you're creating a config file per VM (as the name dom1.conf
implies), then I'd be inclined just to either remove the vmid
variable from the config file (along with the xm_vars stuff), or
just hardwire it at the top of the file. You can hardwire ip
too. 

The 'executable' configuration file format is really only useful
if you're using a single file to define a number of VMs.

BTW: 'vm1.conf' might be a better name for your config file: if
the domain reboots, it'll end up with a different domid (think
unix PID). 'domid' is purely an internal convention between xen
and xend -- we shouldn't be exposing users to this. Indeed, we
are thinking of changing the tools so that they're never exposed
to users: domains would be manipulated by their user configured
name (which must be unique). If anyone has any strong views on
this, shout up!

Best,
Ian


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click