[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Fwd: no network for dom0


  • To: "dror shenkar" <dror.shenkar@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Tue, 15 May 2007 12:18:56 +0200
  • Delivery-date: Tue, 15 May 2007 03:17:35 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AceW18BSX8mvPIUvSUq+zm4phj9dYwAAdusQ
  • Thread-topic: [Xen-users] Fwd: no network for dom0

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> dror shenkar
> Sent: 15 May 2007 10:59
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Fwd: no network for dom0
> 
> 
> 
> ---------- Forwarded message ----------
> From: dror shenkar <dror.shenkar@xxxxxxxxx>
> Date: May 13, 2007 10:39 PM 
> Subject: no network for dom0
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> 
> 
> I installed Ubuntu Feisty successfully, then I configured the 
> network (static IP) and things worked well.
> Then I installed Xen using "apt-get install ubuntu-xen-desktop".
> I could boot the xen kernel, and booted succesfully to dom0, 
> however, there's no network for dom0.
> According to network manager, I saw that Ubuntu recognizes 
> now 4 unconfigured adapters (veth0, veth1, veth2, veth3).
> I'm not sure how I need to configure them to:
> 1> have network for dom0

It's probably because your network setup script is using "eth0" rather
than the xen new-name of "peth0" (as in "physical eth0"). I can't
guarantee this, but I suspect that's what it is. [It depends on the
startup-sequence between Xen and IP address setup if this is the case or
not].

> 2> later, have network for other domains

That is a different problem, and it depends on how you want to set up
your guest network. If you have a range of IP-addresses, you could set
Dom0 to use "dhcp" to issue addresses to your guest-domains, or you can
set them to static addresses there too. For para-virtual domains, you do
this by adding "ip=x.y.z.w" to your "vif=..." line in the configuration.
For HVM (fully-virtualized domains), you will need to use the same type
of setup that you'd do if you have a "real" machine - this depends on
which OS you're using, but just follow the normal setup for IP-addresses
on the OS itself. [e.g. use Windows Control panel, or SuSE "Yast2" to
set the network up within the guest itself].

--
Mats
>  
> Thanks, Dror
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.