Re: [Xen-users] Xcp and xencenter

[Andrew Wells <agwells0714@xxxxxxxxx>]

Just to spell it out better

xe pif-list host-uuid=`xe host-list name-label=xen0 --minimal` params=host-uuid,uuid,device

uuid ( RO)         : efbee715-756e-174d-26ef-0318cb4c2015

       device ( RO): eth3

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : a6651755-b519-d3a0-8090-740486d054f5

       device ( RO): bond0

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 2b7a416d-0c24-cf3b-aa16-909384a9a364

       device ( RO): eth5

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 86a29164-c262-5a86-2ec0-de177abe3cb1

       device ( RO): eth6

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 30aefe5c-4ad8-cf07-7ae0-0ec7ae5d800b

       device ( RO): eth0

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 56670423-c178-01b3-633d-be14a75cbbca

       device ( RO): eth2

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 8d9566dc-3066-a310-2ddd-c77f3265df83

       device ( RO): eth7

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : 6b8b84a4-095e-4681-f58f-d7e196d08242

       device ( RO): eth1

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

uuid ( RO)         : f3f0f746-2d4b-7bee-caef-efd56e3ed44e

       device ( RO): eth4

    host-uuid ( RO): 962c7059-b8cb-42e7-86db-18c9110543bc

but ask another one not master and I get this

xe pif-list host-uuid=`xe host-list name-label=xen1 --minimal` params=host-uuid,uuid,device

uuid ( RO)         : 53455e8a-7689-be8b-520a-e3462cc77f9d

       device ( RO): eth0

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 0e514e2c-b28c-e18c-0bd9-2d4888e8ccdd

       device ( RO): eth2

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : b8c36e00-0346-747b-6ff0-dbc79c43d43b

       device ( RO): eth1

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 8e051263-1ba1-e52e-e356-6446f718cce2

       device ( RO): eth3

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 0d4c4546-3cc0-aa79-5a7d-365cc13d0a96

       device ( RO): eth7

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : d237633e-329a-3469-c554-dacf421d4cb2

       device ( RO): eth5

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 4660c3bd-ae57-5bf8-0051-c1fac4477518

       device ( RO): eth2

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 9b9149a3-d89e-aae5-bf0a-2d28a3e71b94

       device ( RO): eth4

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 5803bf5e-aad1-1a75-efb2-4660a51972e0

       device ( RO): eth5

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 48d900ad-abfd-513c-c344-49c5896e3bfb

       device ( RO): eth4

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : f49165ef-58ab-17ec-3237-03c11bd601c8

       device ( RO): eth1

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : b45da176-13cd-e6f3-6c74-3bbc5e8f6d40

       device ( RO): eth4

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 98e32162-8742-cb6b-5d6f-a00c3da0c60f

       device ( RO): eth5

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : fac05e25-bcce-312b-811c-98d88a444d13

       device ( RO): eth0

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 413d24ce-1c48-41eb-f0e4-d31723599923

       device ( RO): eth0

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 22321fa2-7504-df84-5258-93d7af4866e6

       device ( RO): eth2

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 919cb5fc-7d6c-1296-da8f-c67abbe32189

       device ( RO): eth5

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : b74937e5-2041-1829-1acb-eeb1612cdb12

       device ( RO): eth6

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 5bfc37dc-f958-6072-b8b1-eea6a0ebf5b1

       device ( RO): eth0

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

uuid ( RO)         : 8c23d125-5ae4-a4c7-ca86-adf32c7b815f

       device ( RO): eth2

    host-uuid ( RO): 3c80aa10-b590-4665-a51f-af2251b5c494

there are more pif on the second host [xen1] then there are on [xen0] and these systems are identical. Each system in the pool seem to have more and more pif's, then the one joined previously.

On Wed, Oct 5, 2011 at 3:15 PM, Andrew Wells <agwells0714@xxxxxxxxx> wrote:

So, if I do that on the master, it give me the correct list, however if I ask the master to list devices on a different machine in the pool, it returns devices on that host, and others not on that host.

On Tue, Oct 4, 2011 at 4:28 PM, George Shuklin <george.shuklin@xxxxxxxxx> wrote:

You saying strange things. Never saw this and I doubt if any management software via XenAPI can do this.

Please, recheck if you use correct parameters.

And just for test:

xe pif-list host-uuid=`xe host-list name-label=$(hostname) --minimal` params=host-uuid

On 04.10.2011 19:43, Andrew Wells wrote:

So I installed and used both the OpenXenManager and XenWebManager. but I can't say that either would be good for production uses. Mainly that they are very buggy and could not pickup that I had a pool setup.

Then after I told them to create a pool, it correctly identifies that a pool exists.

However now, when I am using

xe pif-list host-uuid=<host-uuid>

it will list other physical interfaces that are on a different machine in the same pool.

is this caused by openxenmanager or xenwebmanager?

is this a bug with pools?

On Sun, Oct 2, 2011 at 2:54 PM, Morten Christensen <mc-mail@xxxxxxx> wrote:

Den 01-10-2011 04:46, Andrew Wells skrev:

I recently started using xcp, but how do I acquire xencenter? Is it only available with xcp 1.1?

No. It is possible to use it with 1.0. Xencenter is written for XenServer without thoughts on XCP, so it has some version-number-problems on XCP 1.0.

This patch might help
http://www.gossamer-threads.com/lists/xen/api/199147
http://www.xensemaking.com/misc/patchxcp.sh


Morten Christensen

_______________________________________________
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

_______________________________________________
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