WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] XCP resource pool

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] XCP resource pool
From: <admin@xxxxxxxxxxx>
Date: Tue, 4 Jan 2011 07:08:59 -0600
Delivery-date: Tue, 04 Jan 2011 05:10:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <824314.18442.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: admin@xxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acur0otgRFx7QImJRA2UlW7HGD62ugAPZE8g

Each physical node gets a PIF.  Each VM gets a VIF.  When a VM is migrated from one physical node to another, XCP will automatically route the network traffic from the VM’s VIF through the correct PIF using the virtual network switching.  After the initial configuration, you can pretty much just ignore the PIF information and let XCP do its magic.  You don’t need to manually connect a VM to a PIF.  Connect the VM using a VIF.

 

 

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of inas mohamed
Sent:
Monday, January 03, 2011 11:46 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx; admin@xxxxxxxxxxx
Subject: RE: [Xen-users] XCP resource pool

 

Thanks soo much, but as I said before I am very new and by the time I am finding that my question is tooo .......:( 

I read many forums and guides on XCP and VMs and I found that many VDIs can be created on the same storage repository for our VMs.

But regarding vifs, now as a said before I installed XCP on 5 servers and created a resource pool and all my servers joined that pool and when I try:

# xe network-list bridge=xenbr0 params=uuid  --minimal 

I am getting one network uuid but if I said: 

# xe pif-list

I got 5 NICs all are eth0, each have a different uuid but all have the same network uuid

So, I am asking why when we are creating a vif we are using the network uuid not the pif uuid to say the traffic of this VM has to go through this NIC??

 

may be it is another .... question.but it is my question :)

 

Thanks for every one.


--- On Mon, 1/3/11, admin@xxxxxxxxxxx <admin@xxxxxxxxxxx> wrote:


From: admin@xxxxxxxxxxx <admin@xxxxxxxxxxx>
Subject: RE: [Xen-users] XCP resource pool
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date:
Monday, January 3, 2011, 9:58 PM

No, you can create on SR and store all of your VMs on that SR.  For example, if you use an NFS target for your VHD files, all of your VMs could share that SR.

 

You don’t need to assign a separate PIF for each VM.  In fact, most people won’t.  You will assign a separate VIF for each VM and then XCP can route the VIFs through a shared PIF.

 

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of inas mohamed
Sent:
Monday, January 03, 2011 12:55 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XCP resource pool

 

Hi, 

 

I am very new to XCP , and I have couple of questions to make things clear.

 

After creating a resource pool:

Do I have to create a SR for each VM, if I needed to assign 100GB HDD for this VM??

Do I have to assign a pif for each VM to distribute the traffic over my hosts NICs or the master will handle this??

 

Thanks so much for any help

 

 

 


-----Inline Attachment Follows-----

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

 

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