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

Re: [Xen-users] Lost Network on domU's - Please Help


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Thomas Goirand <thomas@xxxxxxxxxx>
  • Date: Sun, 23 Nov 2008 12:06:10 +0800
  • Delivery-date: Sat, 22 Nov 2008 20:07:01 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=goirand.fr; h=message-id:date:from:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=postfix; b= gcVFDl9F90FvArz4oCN9RlxUY1qXWZ4mDdGfv0tYycEVnad24tzki2D/eO5W3BuB JOU1jBHbbiGd69EWqVbVZDq9ef50jQh3TaU57rOX2VCUpxu8ZHWAclswfUDvciiL //DzoadFZg+VBjZKsud78IHfOODPP+8NDJI6IOLz3Yg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Openpgp: id=98EF9A49

James Pifer wrote:
> On Sat, 2008-11-22 at 21:24 -0500, Javier Guerra Giraldez wrote:
>> On Saturday 22 November 2008, James Pifer wrote:
>>> On the domU's that are broken the command gives almost the same output,
>>> but they are all missing the HW address line.
>> Suse net scripts tie the card definitions to the MAC address.  if it 
>> changes, 
>> it will think it's a new card and not configure it by default.
>>
>> it's best to always specify the MAC address.  (also because some other 
>> machines might not like if a server changes a MAC address)
>>
>>
> 
> Any suggestions on a fix? I've even tried deleting them in yast and
> resetting them up, but they still don't come up. 
> 
> Thanks,
> James

My suggestion is that you make the start of xend BEFORE doing a
configuration using the ethX:Y. If you don't, then you might have
serious issues with the bridging. I'm not sure if that helps...

Thomas


_______________________________________________
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®.