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

Re: [Xen-users] problems using domu as network backend domain (fedora 7)


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Stefanie Braun" <fannys@xxxxxxx>
  • Date: Fri, 8 Feb 2008 15:02:58 +0100
  • Delivery-date: Fri, 08 Feb 2008 06:03:34 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=O5mwH8u7+hQBMwcFvW96BmeSPW2f9ZhgOJjrT3shPxeAUiqx3jD4Cf89gzdNwrC0Bu1FGFC9OZFSV7ie1v0doraEQQcG33g3kWRf2uE90u/oqI1qIyn2GhMmOP03F3HFTDSaBLzrhi56TPlmhgmW8M6AaHN8KMXJlQiUi1Bg73k=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello
problem solved, network setting is working.
The bug just means that domu1 has not enough privileges.
To give domu1 enough privileges it seems to be necessary to pass through a hardware device.
Then domu1 has the right privileges and no bug occurs.

For PCI passthrough the hardware needs to be deactivated (or hidden) in dom-0 and the hardware id of the device
needs to be specified in the domain-u config file.

new config parameter for domu1:
pci = ['00:12.0']
netif    = "yes"

Greetings Fanny







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