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

Re: [Xen-users] Need help setting up guest's networking

  • To: Yevgeniy Goldberg <thegoldberg@xxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Sun, 29 Apr 2007 14:34:35 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 29 Apr 2007 06:31:16 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=fXZrPNFprYNxjxYs2zh6Fw/+J6v2JQVsIf5/ApxeHocMfA26sAbxT2DR3/UNoMtHJ9AlmlWcfEfLkAo0ERjogC21TXEmes1Oh5gSSm6gwRcDHZpMwLpgzWVJt0N4I0OEJZozSq0zozSg+cYJ+JaxSMZhM7F+cXNNMvhxYYqRCvg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Yevgeniy Goldberg wrote:
I did have my firewall turned off.
What would be an example of hard-coding a vif name?
Also, I've discovered that I could manually assign an IP address to a vif interface in Dom0. This way I could network between the Dom0 and DomU, but could not establish an Internet connection from the DomU. My attempt to set the network interface of DomU to dhcp did not work either.
The vifnames are set in the "vif=" configuration statement. So

   vif = [ 'mac=MACADDRESS, bridge=xenbr0' ]

would become

   vif = [ 'vifname=xen0.01,mac=MACADDRESS, bridge=xenbr0' ]

Setting the IP address of a network port is not the right job for Xen itself: it's the right job for the guest domain, which has all the network configuration tools built in normally, and itself needs to know the netmask and gateway address.

Xen-users mailing list



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