From xen-api-bounces@lists.xen.org Wed Jan 01 20:11:34 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 01 Jan 2014 20:11:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS8E-0002bC-DX; Wed, 01 Jan 2014 20:11:10 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS8C-0002b7-Ng for xen-api@lists.xen.org; Wed, 01 Jan 2014 20:11:08 +0000 Received: from [193.109.254.147:26745] by server-12.bemta-14.messagelabs.com id 05/F3-13681-C5674C25; Wed, 01 Jan 2014 20:11:08 +0000 X-Env-Sender: aholway@nsslabs.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1388607066!8336385!1 X-Originating-IP: [66.162.222.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25177 invoked from network); 1 Jan 2014 20:11:06 -0000 Received: from mail.nsslabs.com (HELO mail.nsslabs.com) (66.162.222.51) by server-12.tower-27.messagelabs.com with SMTP; 1 Jan 2014 20:11:06 -0000 From: Andrew Holway To: "xen-api@lists.xen.org" Thread-Topic: AttributeError: 'module' object has no attribute 'getProvisionSpec' Thread-Index: AQHPBy2ZcX2LqgPpnkq+W7ReYb614A== Date: Wed, 1 Jan 2014 20:11:04 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.106.144.17] MIME-Version: 1.0 Subject: [Xen-API] AttributeError: 'module' object has no attribute 'getProvisionSpec' X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2656316164585344986==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2656316164585344986== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_" --_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I have been using the install.py from the xen-api github[1] and have just s= tarted getting this error after I restarted my XenServer node. Adding noniteractive to the kernel commandline Choosing an SR to instaniate the VM's disks Choosing SR: Local (uuid d94bbf44-f957-d448-6704-fb7b197a056a) Rewriting the disk provisioning XML 'module' object has no attribute 'getProvisionSpec' Traceback (most recent call last): File "./install.py", line 134, in main(session) File "./install.py", line 83, in main spec =3D provision.getProvisionSpec(session, vm) AttributeError: 'module' object has no attribute =91getProvisionSpec' "'module' object has no attribute =91getProvisionSpec=92=94 turns a complet= e google blank. Any ideas? Thanks, Andrew [1] - https://raw.github.com/xapi-project/xen-api/master/scripts/examples/p= ython/install.py --_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable I have been using the install.py from the xen-api github[1] and have just started get= ting this error after I restarted my XenServer node.

Adding non= iteractive to the kernel commandline
Choosing a= n SR to instaniate the VM's disks
Choosing S= R: Local (uuid d94bbf44-f957-d448-6704-fb7b197a056a)
Rewriting = the disk provisioning XML
'module' o= bject has no attribute 'getProvisionSpec'
Traceback = (most recent call last):
  Fil= e "./install.py", line 134, in <module>
  &nb= sp; main(session)
  Fil= e "./install.py", line 83, in main
  &nb= sp; spec =3D provision.getProvisionSpec(session, vm)
AttributeE= rror: 'module' object has no attribute =91getProvisionSpec'

"'mod= ule' object has no attribute =91getProvisionSpec=92=94 turns a complete goo= gle blank.

Any ideas?=

Thanks,

Andrew

--_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_-- --===============2656316164585344986== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2656316164585344986==-- From xen-api-bounces@lists.xen.org Wed Jan 01 20:11:34 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 01 Jan 2014 20:11:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS8E-0002bC-DX; Wed, 01 Jan 2014 20:11:10 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS8C-0002b7-Ng for xen-api@lists.xen.org; Wed, 01 Jan 2014 20:11:08 +0000 Received: from [193.109.254.147:26745] by server-12.bemta-14.messagelabs.com id 05/F3-13681-C5674C25; Wed, 01 Jan 2014 20:11:08 +0000 X-Env-Sender: aholway@nsslabs.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1388607066!8336385!1 X-Originating-IP: [66.162.222.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25177 invoked from network); 1 Jan 2014 20:11:06 -0000 Received: from mail.nsslabs.com (HELO mail.nsslabs.com) (66.162.222.51) by server-12.tower-27.messagelabs.com with SMTP; 1 Jan 2014 20:11:06 -0000 From: Andrew Holway To: "xen-api@lists.xen.org" Thread-Topic: AttributeError: 'module' object has no attribute 'getProvisionSpec' Thread-Index: AQHPBy2ZcX2LqgPpnkq+W7ReYb614A== Date: Wed, 1 Jan 2014 20:11:04 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.106.144.17] MIME-Version: 1.0 Subject: [Xen-API] AttributeError: 'module' object has no attribute 'getProvisionSpec' X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2656316164585344986==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2656316164585344986== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_" --_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I have been using the install.py from the xen-api github[1] and have just s= tarted getting this error after I restarted my XenServer node. Adding noniteractive to the kernel commandline Choosing an SR to instaniate the VM's disks Choosing SR: Local (uuid d94bbf44-f957-d448-6704-fb7b197a056a) Rewriting the disk provisioning XML 'module' object has no attribute 'getProvisionSpec' Traceback (most recent call last): File "./install.py", line 134, in main(session) File "./install.py", line 83, in main spec =3D provision.getProvisionSpec(session, vm) AttributeError: 'module' object has no attribute =91getProvisionSpec' "'module' object has no attribute =91getProvisionSpec=92=94 turns a complet= e google blank. Any ideas? Thanks, Andrew [1] - https://raw.github.com/xapi-project/xen-api/master/scripts/examples/p= ython/install.py --_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable I have been using the install.py from the xen-api github[1] and have just started get= ting this error after I restarted my XenServer node.

Adding non= iteractive to the kernel commandline
Choosing a= n SR to instaniate the VM's disks
Choosing S= R: Local (uuid d94bbf44-f957-d448-6704-fb7b197a056a)
Rewriting = the disk provisioning XML
'module' o= bject has no attribute 'getProvisionSpec'
Traceback = (most recent call last):
  Fil= e "./install.py", line 134, in <module>
  &nb= sp; main(session)
  Fil= e "./install.py", line 83, in main
  &nb= sp; spec =3D provision.getProvisionSpec(session, vm)
AttributeE= rror: 'module' object has no attribute =91getProvisionSpec'

"'mod= ule' object has no attribute =91getProvisionSpec=92=94 turns a complete goo= gle blank.

Any ideas?=

Thanks,

Andrew

--_000_F874293D9CFA5340B770DC034129326229094CF3exchangelabnssl_-- --===============2656316164585344986== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2656316164585344986==-- From xen-api-bounces@lists.xen.org Wed Jan 01 20:12:18 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 01 Jan 2014 20:12:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS9D-0002cU-Mm; Wed, 01 Jan 2014 20:12:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS9C-0002cK-Hj for xen-api@lists.xen.org; Wed, 01 Jan 2014 20:12:10 +0000 Received: from [193.109.254.147:31771] by server-13.bemta-14.messagelabs.com id 06/DC-19374-99674C25; Wed, 01 Jan 2014 20:12:09 +0000 X-Env-Sender: aholway@nsslabs.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1388607127!6042311!1 X-Originating-IP: [66.162.222.51] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17816 invoked from network); 1 Jan 2014 20:12:08 -0000 Received: from mail.nsslabs.com (HELO mail.nsslabs.com) (66.162.222.51) by server-13.tower-27.messagelabs.com with SMTP; 1 Jan 2014 20:12:08 -0000 From: Andrew Holway To: Dave Scott Thread-Topic: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value, and this is required for the selected distribution type. Thread-Index: AQHPAxfx/1CoyYqeZEehZSuf8iplFZpslZrQgAQkRoA= Date: Wed, 1 Jan 2014 20:12:06 +0000 Message-ID: References: <6FB4516F0E9B0F43B54F88D855ABB790DC80F1@AMSPEX01CL03.citrite.net> In-Reply-To: <6FB4516F0E9B0F43B54F88D855ABB790DC80F1@AMSPEX01CL03.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.106.144.17] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value, and this is required for the selected distribution type. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4903143339815424893==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4903143339815424893== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_" --_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable session.xenapi.VM.add_to_other_config(vm, =93install-repository=94, =93=94) Perfect, thank you. just before the session.xenapi.VM.start() HTH Dave From: xen-api-bounces@lists.xen.org [= mailto:xen-api-bounces@lists.xen.org] On Behalf Of Andrew Holway Sent: 27 December 2013 3:26 PM To: xen-api@lists.xen.org Subject: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an= appropriate value, and this is required for the selected distribution type= . Hello, I am struggling to understand how to clone from templates via the XenAPI us= ing Python using the code samples in the This is the python I am trying with: https://gist.github.com/mooperd/33ab0b= 908dc411443652 If, in the GUI I use =93quick create=94, it works fine. The error is below. Thanks, Andrew Asking server to provision storage from the template specification Starting VM ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', 'UN= SUPPORTED_INSTALL_METHOD\nother-config:install-repository was not set to an= appropriate value, and this is required for the selected distribution type= .\n\n'] Traceback (most recent call last): File "./install.py", line 140, in main(session) File "./install.py", line 95, in main session.xenapi.VM.start(vm, False, True) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 245, in __ca= ll__ return self.__send(self.__name, args) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 149, in xena= pi_request result =3D _parse_result(getattr(self, methodname)(*full_params)) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 219, in _par= se_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f= 4ce172d3d1', 'UNSUPPORTED_INSTALL_METHOD\nother-config:install-repository w= as not set to an appropriate value, and this is required for the selected d= istribution type.\n\n'] --_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_ Content-Type: text/html; charset="Windows-1252" Content-ID: <9B1B8528D79C1D4FBDA381EA7A8B6D5B@nsslabs.com> Content-Transfer-Encoding: quoted-printable
= session.xenapi.VM.add_to_other_config(vm, =93install-repository=94, =93<= my URL>=94)

Perfect, thank you.

 
just before the session.xenapi.VM.start()
 
HTH
Dave
 
 
From: = xen-api-bounces@lis= ts.xen.org [mailto:xen-api-bounces@l= ists.xen.org] On B= ehalf Of Andrew Holwa= y
Sent: 27 December = 2013 3:26 PM
To: xen-api@lists.xen.org
Subject: [Xen-API]= 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value= , and this is required for the selected distribution type.
 
Hello, 
 <= /div>
I am strugglin= g to understand how to clone from templates via the XenAPI using Python usi= ng the code samples in the 
 <= /div>
This is the py= thon I am trying with: http= s://gist.github.com/mooperd/33ab0b908dc411443652
 <= /div>
If, in the GUI= I use =93quick create=94, it works fine. The error is below.
 <= /div>
Thanks,
 <= /div>
Andrew
 <= /div>
Asking server = to provision storage from the template specification
Starting VM
['BOOTLOADER_F= AILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', 'UNSUPPORTED_INST= ALL_METHOD\nother-config:install-repository was not set to an appropriate v= alue, and this is required for the selected distribution type.\n\n']
Traceback (mos= t recent call last):
  File &q= uot;./install.py", line 140, in <module>
    = main(session)
  File &q= uot;./install.py", line 95, in main
    = session.xenapi.VM.start(vm, False, True)
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 245, in __c= all__
    = return self.__send(self.__name, args)
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 149, in xen= api_request
    = result =3D _parse_result(getattr(self, methodname)(*full_params))
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 219, in _pa= rse_result
    = raise Failure(result['ErrorDescription'])
XenAPI.Failure= : ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', '= UNSUPPORTED_INSTALL_METHOD\nother-config:install-repository was not set to = an appropriate value, and this is required for the selected distribution type.\n\n']

--_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_-- --===============4903143339815424893== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4903143339815424893==-- From xen-api-bounces@lists.xen.org Wed Jan 01 20:12:18 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 01 Jan 2014 20:12:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS9D-0002cU-Mm; Wed, 01 Jan 2014 20:12:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyS9C-0002cK-Hj for xen-api@lists.xen.org; Wed, 01 Jan 2014 20:12:10 +0000 Received: from [193.109.254.147:31771] by server-13.bemta-14.messagelabs.com id 06/DC-19374-99674C25; Wed, 01 Jan 2014 20:12:09 +0000 X-Env-Sender: aholway@nsslabs.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1388607127!6042311!1 X-Originating-IP: [66.162.222.51] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17816 invoked from network); 1 Jan 2014 20:12:08 -0000 Received: from mail.nsslabs.com (HELO mail.nsslabs.com) (66.162.222.51) by server-13.tower-27.messagelabs.com with SMTP; 1 Jan 2014 20:12:08 -0000 From: Andrew Holway To: Dave Scott Thread-Topic: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value, and this is required for the selected distribution type. Thread-Index: AQHPAxfx/1CoyYqeZEehZSuf8iplFZpslZrQgAQkRoA= Date: Wed, 1 Jan 2014 20:12:06 +0000 Message-ID: References: <6FB4516F0E9B0F43B54F88D855ABB790DC80F1@AMSPEX01CL03.citrite.net> In-Reply-To: <6FB4516F0E9B0F43B54F88D855ABB790DC80F1@AMSPEX01CL03.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.106.144.17] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value, and this is required for the selected distribution type. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4903143339815424893==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4903143339815424893== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_" --_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable session.xenapi.VM.add_to_other_config(vm, =93install-repository=94, =93=94) Perfect, thank you. just before the session.xenapi.VM.start() HTH Dave From: xen-api-bounces@lists.xen.org [= mailto:xen-api-bounces@lists.xen.org] On Behalf Of Andrew Holway Sent: 27 December 2013 3:26 PM To: xen-api@lists.xen.org Subject: [Xen-API] 'BOOTLOADER_FAILED' install-repository was not set to an= appropriate value, and this is required for the selected distribution type= . Hello, I am struggling to understand how to clone from templates via the XenAPI us= ing Python using the code samples in the This is the python I am trying with: https://gist.github.com/mooperd/33ab0b= 908dc411443652 If, in the GUI I use =93quick create=94, it works fine. The error is below. Thanks, Andrew Asking server to provision storage from the template specification Starting VM ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', 'UN= SUPPORTED_INSTALL_METHOD\nother-config:install-repository was not set to an= appropriate value, and this is required for the selected distribution type= .\n\n'] Traceback (most recent call last): File "./install.py", line 140, in main(session) File "./install.py", line 95, in main session.xenapi.VM.start(vm, False, True) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 245, in __ca= ll__ return self.__send(self.__name, args) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 149, in xena= pi_request result =3D _parse_result(getattr(self, methodname)(*full_params)) File "/root/xen-api/scripts/examples/python/XenAPI.py", line 219, in _par= se_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f= 4ce172d3d1', 'UNSUPPORTED_INSTALL_METHOD\nother-config:install-repository w= as not set to an appropriate value, and this is required for the selected d= istribution type.\n\n'] --_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_ Content-Type: text/html; charset="Windows-1252" Content-ID: <9B1B8528D79C1D4FBDA381EA7A8B6D5B@nsslabs.com> Content-Transfer-Encoding: quoted-printable
= session.xenapi.VM.add_to_other_config(vm, =93install-repository=94, =93<= my URL>=94)

Perfect, thank you.

 
just before the session.xenapi.VM.start()
 
HTH
Dave
 
 
From: = xen-api-bounces@lis= ts.xen.org [mailto:xen-api-bounces@l= ists.xen.org] On B= ehalf Of Andrew Holwa= y
Sent: 27 December = 2013 3:26 PM
To: xen-api@lists.xen.org
Subject: [Xen-API]= 'BOOTLOADER_FAILED' install-repository was not set to an appropriate value= , and this is required for the selected distribution type.
 
Hello, 
 <= /div>
I am strugglin= g to understand how to clone from templates via the XenAPI using Python usi= ng the code samples in the 
 <= /div>
This is the py= thon I am trying with: http= s://gist.github.com/mooperd/33ab0b908dc411443652
 <= /div>
If, in the GUI= I use =93quick create=94, it works fine. The error is below.
 <= /div>
Thanks,
 <= /div>
Andrew
 <= /div>
Asking server = to provision storage from the template specification
Starting VM
['BOOTLOADER_F= AILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', 'UNSUPPORTED_INST= ALL_METHOD\nother-config:install-repository was not set to an appropriate v= alue, and this is required for the selected distribution type.\n\n']
Traceback (mos= t recent call last):
  File &q= uot;./install.py", line 140, in <module>
    = main(session)
  File &q= uot;./install.py", line 95, in main
    = session.xenapi.VM.start(vm, False, True)
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 245, in __c= all__
    = return self.__send(self.__name, args)
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 149, in xen= api_request
    = result =3D _parse_result(getattr(self, methodname)(*full_params))
  File &q= uot;/root/xen-api/scripts/examples/python/XenAPI.py", line 219, in _pa= rse_result
    = raise Failure(result['ErrorDescription'])
XenAPI.Failure= : ['BOOTLOADER_FAILED', 'OpaqueRef:13ac7347-c597-50b3-c66e-8f4ce172d3d1', '= UNSUPPORTED_INSTALL_METHOD\nother-config:install-repository was not set to = an appropriate value, and this is required for the selected distribution type.\n\n']

--_000_F874293D9CFA5340B770DC034129326229094D00exchangelabnssl_-- --===============4903143339815424893== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4903143339815424893==-- From xen-api-bounces@lists.xen.org Fri Jan 03 05:01:03 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Jan 2014 05:01:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VywsN-00029v-1S; Fri, 03 Jan 2014 05:00:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VywsL-00029n-AZ; Fri, 03 Jan 2014 05:00:49 +0000 Received: from [85.158.143.35:10464] by server-1.bemta-4.messagelabs.com id 9A/9F-02132-00446C25; Fri, 03 Jan 2014 05:00:48 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1388725247!2228148!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4868 invoked from network); 3 Jan 2014 05:00:47 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2014 05:00:47 -0000 Received: by mail-la0-f43.google.com with SMTP id n7so7807497lam.16 for ; Thu, 02 Jan 2014 21:00:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=uyBRe/PKKMFirc6GvolNCU2czzQMUFbeJPcem/ApyoI=; b=jBM55XIMUTltE04CsohMNKue39CS8rEJNYoJ5iWj62P6v3UjrhdO08c/bsLN2Ki8L3 rgr8ZRYpblOhkf0xp8I8yzeG4GmDGmBlk9N1CpXpWHlECX2hVfAlm1F75t4ukaYcf7Be fM3u8I15xCJM8OFdV/f82Bm7BmB9g/R3Wj8NgqDGvESPMfus4e1UrMywJvR6B776qVsw 9WiqvgWQR4INaJEg4AxkfOkyPWpXPJ6mPbS9vUlwisarzw8VMV0ckhCzGzVXc0nv1g1Q kwsBaR27kgAN53d6fsQjS7UARDodbtFW9uqaTcHIN6CcxQyXjQIEnpsihE4Owo5Nbu+Y Ctjg== MIME-Version: 1.0 X-Received: by 10.112.52.6 with SMTP id p6mr56275lbo.67.1388725246615; Thu, 02 Jan 2014 21:00:46 -0800 (PST) Received: by 10.112.184.16 with HTTP; Thu, 2 Jan 2014 21:00:46 -0800 (PST) Date: Fri, 3 Jan 2014 00:00:46 -0500 X-Google-Sender-Auth: opXSo1nzmjFGLZLz1JXKhpx-Q-E Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: [Xen-API] XenProject Q&A: /etc/init.d/xcp-xapi doesn't start: 'Error: Connection refused (calling connect )' X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On the XenProject.org Q&A section, user "Mark" asks the following: ---- Topic: /etc/init.d/xcp-xapi doesn't start: 'Error: Connection refused (calling connect )' I'm stumped by the above. Fresh install of debian wheezy. install params: netcfg/disable_autoconfig=true cdrom-detect/eject=false base-installer/install-recommends=false Followed http://wiki.xenproject.org/wiki/XAPI_toolstack_on_a_Debian-based_distribution. /etc/xcp$ cat inventory CURRENT_INTERFACES='xenbr0' BUILD_NUMBER='0' CONTROL_DOMAIN_UUID='226e9869-72bc-4680-bf98-686dbfcc9bbe' INSTALLATION_UUID='226e9869-72bc-4680-bf98-686dbfcc9bbe' MANAGEMENT_INTERFACE='xenbr0' PRIMARY_DISK='/dev/sda1' PRODUCT_VERSION='6.0.0' Then xcp-xapi returned FATAL: Module blktap not found. I installed the linux-headers for the kernel and rebuilt dkms. Now I get the above error and in the xcp-xapi.log: Caught exception at toplevel: 'Db_exn.Uniqueness_constraint_violation("VM", "uuid", "226e9869-72bc-4680-bf98-686dbfcc9bbe")' which I can't find anything on. The log file for more info is here http://phosph.re/s2c/xcp-xapi.txt. XAPI will not start right now, and I cannot play with xen as a result. ---- If anyone has insight for Mark, please email me so I can forward it to the Q&A entry (or you can enter it yourself, if you feel so inclined, at http://xenproject.org/help/questions-and-answers/etc-init-d-xcp-xapi-doesn-t-start-error-connection-refused-calling-connect.html Thanks, Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 03 05:01:03 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Jan 2014 05:01:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VywsN-00029v-1S; Fri, 03 Jan 2014 05:00:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VywsL-00029n-AZ; Fri, 03 Jan 2014 05:00:49 +0000 Received: from [85.158.143.35:10464] by server-1.bemta-4.messagelabs.com id 9A/9F-02132-00446C25; Fri, 03 Jan 2014 05:00:48 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1388725247!2228148!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4868 invoked from network); 3 Jan 2014 05:00:47 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2014 05:00:47 -0000 Received: by mail-la0-f43.google.com with SMTP id n7so7807497lam.16 for ; Thu, 02 Jan 2014 21:00:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=uyBRe/PKKMFirc6GvolNCU2czzQMUFbeJPcem/ApyoI=; b=jBM55XIMUTltE04CsohMNKue39CS8rEJNYoJ5iWj62P6v3UjrhdO08c/bsLN2Ki8L3 rgr8ZRYpblOhkf0xp8I8yzeG4GmDGmBlk9N1CpXpWHlECX2hVfAlm1F75t4ukaYcf7Be fM3u8I15xCJM8OFdV/f82Bm7BmB9g/R3Wj8NgqDGvESPMfus4e1UrMywJvR6B776qVsw 9WiqvgWQR4INaJEg4AxkfOkyPWpXPJ6mPbS9vUlwisarzw8VMV0ckhCzGzVXc0nv1g1Q kwsBaR27kgAN53d6fsQjS7UARDodbtFW9uqaTcHIN6CcxQyXjQIEnpsihE4Owo5Nbu+Y Ctjg== MIME-Version: 1.0 X-Received: by 10.112.52.6 with SMTP id p6mr56275lbo.67.1388725246615; Thu, 02 Jan 2014 21:00:46 -0800 (PST) Received: by 10.112.184.16 with HTTP; Thu, 2 Jan 2014 21:00:46 -0800 (PST) Date: Fri, 3 Jan 2014 00:00:46 -0500 X-Google-Sender-Auth: opXSo1nzmjFGLZLz1JXKhpx-Q-E Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: [Xen-API] XenProject Q&A: /etc/init.d/xcp-xapi doesn't start: 'Error: Connection refused (calling connect )' X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On the XenProject.org Q&A section, user "Mark" asks the following: ---- Topic: /etc/init.d/xcp-xapi doesn't start: 'Error: Connection refused (calling connect )' I'm stumped by the above. Fresh install of debian wheezy. install params: netcfg/disable_autoconfig=true cdrom-detect/eject=false base-installer/install-recommends=false Followed http://wiki.xenproject.org/wiki/XAPI_toolstack_on_a_Debian-based_distribution. /etc/xcp$ cat inventory CURRENT_INTERFACES='xenbr0' BUILD_NUMBER='0' CONTROL_DOMAIN_UUID='226e9869-72bc-4680-bf98-686dbfcc9bbe' INSTALLATION_UUID='226e9869-72bc-4680-bf98-686dbfcc9bbe' MANAGEMENT_INTERFACE='xenbr0' PRIMARY_DISK='/dev/sda1' PRODUCT_VERSION='6.0.0' Then xcp-xapi returned FATAL: Module blktap not found. I installed the linux-headers for the kernel and rebuilt dkms. Now I get the above error and in the xcp-xapi.log: Caught exception at toplevel: 'Db_exn.Uniqueness_constraint_violation("VM", "uuid", "226e9869-72bc-4680-bf98-686dbfcc9bbe")' which I can't find anything on. The log file for more info is here http://phosph.re/s2c/xcp-xapi.txt. XAPI will not start right now, and I cannot play with xen as a result. ---- If anyone has insight for Mark, please email me so I can forward it to the Q&A entry (or you can enter it yourself, if you feel so inclined, at http://xenproject.org/help/questions-and-answers/etc-init-d-xcp-xapi-doesn-t-start-error-connection-refused-calling-connect.html Thanks, Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 07 20:28:09 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 Jan 2014 20:28:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0dFl-0006zm-Dc; Tue, 07 Jan 2014 20:27:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W0dFj-0006zh-Qu for xen-api@lists.xensource.com; Tue, 07 Jan 2014 20:27:56 +0000 Received: from [85.158.137.68:3545] by server-13.bemta-3.messagelabs.com id 19/D5-28603-B436CC25; Tue, 07 Jan 2014 20:27:55 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1389126473!7733710!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20007 invoked from network); 7 Jan 2014 20:27:54 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 20:27:54 -0000 Received: by mail-wg0-f43.google.com with SMTP id k14so637486wgh.22 for ; Tue, 07 Jan 2014 12:27:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=O3hrIxe0U93KaFvbSrOB0WDO4eBZjPs3VZfXKiS41co=; b=WQzZTZPyBCNxhRNX6GFspPKvCnyUFCOAcJSttiGCDOvKJW/WLByO1t0iSpPJtsaQwt 8nrz8eXiKTZFQG/oIiSTBE8kqJVrizsxBZQkc5YGyktl37nFeeqz9NV5CVio/3zZGt3s 1DKmwpyMsdtnPpscWQ4ofOlLIp+wg3vIFVmCm6+XLtg6hJiMo8LT1dCCPUnQJCXbjbZG GOw7lNWZAWWAXH3MkwmWc2+5K7CAiYzV4ymbgA69B/vgVRwAg8Rf2fpl/4MnBV5NwL3B BKoi8HUefMFTgr3uOvndsSRIkBPDGHldeWyigpvi5zXh7nCx3hBETK2TL/DmK2m16Zgm ytVw== MIME-Version: 1.0 X-Received: by 10.180.206.138 with SMTP id lo10mr18401465wic.25.1389126473590; Tue, 07 Jan 2014 12:27:53 -0800 (PST) Received: by 10.216.45.147 with HTTP; Tue, 7 Jan 2014 12:27:53 -0800 (PST) Date: Wed, 8 Jan 2014 01:57:53 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xensource.com" , xs-devel@lists.xenserver.org Subject: [Xen-API] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8555943507950787952==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8555943507950787952== Content-Type: multipart/alternative; boundary=001a11c26b2601adf704ef67364b --001a11c26b2601adf704ef67364b Content-Type: text/plain; charset=ISO-8859-1 Hello List, I have few questions about XenTools Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ? How does one handles mass tools update after the xen upgrade ? e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ? Are there any logs inside VM/Host about tools driver errors to look in case of problems ? Regards, Rishi --001a11c26b2601adf704ef67364b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello List,

I have f= ew questions about XenTools

Is it compulsory to update to= ols of Linux/Windows VMs if the XenServer is upgraded ?

How do= es one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools = interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?<= br>
Are there any logs inside VM/Host about tools driver erro= rs to look in case of problems ?



Regards,
Rishi
--001a11c26b2601adf704ef67364b-- --===============8555943507950787952== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8555943507950787952==-- From xen-api-bounces@lists.xen.org Tue Jan 07 20:28:09 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 Jan 2014 20:28:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0dFl-0006zm-Dc; Tue, 07 Jan 2014 20:27:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W0dFj-0006zh-Qu for xen-api@lists.xensource.com; Tue, 07 Jan 2014 20:27:56 +0000 Received: from [85.158.137.68:3545] by server-13.bemta-3.messagelabs.com id 19/D5-28603-B436CC25; Tue, 07 Jan 2014 20:27:55 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1389126473!7733710!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20007 invoked from network); 7 Jan 2014 20:27:54 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 20:27:54 -0000 Received: by mail-wg0-f43.google.com with SMTP id k14so637486wgh.22 for ; Tue, 07 Jan 2014 12:27:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=O3hrIxe0U93KaFvbSrOB0WDO4eBZjPs3VZfXKiS41co=; b=WQzZTZPyBCNxhRNX6GFspPKvCnyUFCOAcJSttiGCDOvKJW/WLByO1t0iSpPJtsaQwt 8nrz8eXiKTZFQG/oIiSTBE8kqJVrizsxBZQkc5YGyktl37nFeeqz9NV5CVio/3zZGt3s 1DKmwpyMsdtnPpscWQ4ofOlLIp+wg3vIFVmCm6+XLtg6hJiMo8LT1dCCPUnQJCXbjbZG GOw7lNWZAWWAXH3MkwmWc2+5K7CAiYzV4ymbgA69B/vgVRwAg8Rf2fpl/4MnBV5NwL3B BKoi8HUefMFTgr3uOvndsSRIkBPDGHldeWyigpvi5zXh7nCx3hBETK2TL/DmK2m16Zgm ytVw== MIME-Version: 1.0 X-Received: by 10.180.206.138 with SMTP id lo10mr18401465wic.25.1389126473590; Tue, 07 Jan 2014 12:27:53 -0800 (PST) Received: by 10.216.45.147 with HTTP; Tue, 7 Jan 2014 12:27:53 -0800 (PST) Date: Wed, 8 Jan 2014 01:57:53 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xensource.com" , xs-devel@lists.xenserver.org Subject: [Xen-API] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8555943507950787952==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8555943507950787952== Content-Type: multipart/alternative; boundary=001a11c26b2601adf704ef67364b --001a11c26b2601adf704ef67364b Content-Type: text/plain; charset=ISO-8859-1 Hello List, I have few questions about XenTools Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ? How does one handles mass tools update after the xen upgrade ? e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ? Are there any logs inside VM/Host about tools driver errors to look in case of problems ? Regards, Rishi --001a11c26b2601adf704ef67364b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello List,

I have f= ew questions about XenTools

Is it compulsory to update to= ols of Linux/Windows VMs if the XenServer is upgraded ?

How do= es one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools = interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?<= br>
Are there any logs inside VM/Host about tools driver erro= rs to look in case of problems ?



Regards,
Rishi
--001a11c26b2601adf704ef67364b-- --===============8555943507950787952== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8555943507950787952==-- From xen-api-bounces@lists.xen.org Tue Jan 07 23:41:37 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 Jan 2014 23:41:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0gH2-0007s1-W5; Tue, 07 Jan 2014 23:41:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0gH1-0007rw-Iv for xen-api@lists.xensource.com; Tue, 07 Jan 2014 23:41:27 +0000 Received: from [193.109.254.147:40042] by server-1.bemta-14.messagelabs.com id 1A/19-15600-6A09CC25; Tue, 07 Jan 2014 23:41:26 +0000 X-Env-Sender: jesse.benedict@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1389138083!9422077!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19408 invoked from network); 7 Jan 2014 23:41:24 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 23:41:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="90692910" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 07 Jan 2014 23:41:22 +0000 Received: from FTLPEX01CL02.citrite.net ([169.254.2.8]) by FTLPEX01CL03.citrite.net ([169.254.1.174]) with mapi id 14.02.0342.004; Tue, 7 Jan 2014 18:41:22 -0500 From: Jesse Benedict To: "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Thread-Topic: "Eject ISO Image" Mechanism Proposal Thread-Index: Ac8MAe9mZooMHbODQaSCdpuWlKK1Rg== Date: Tue, 7 Jan 2014 23:41:21 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.11.24.65] MIME-Version: 1.0 X-DLP: MIA1 Subject: [Xen-API] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4958799442350634349==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4958799442350634349== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_" --_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am setting up my own dev environment, but in the mean-time I would like t= o propose the following: PROPOSAL Auto Ejection of All Mounted CDs PURPOSE To make application of patches/hotfixes easier in large environments where = ISO images may be mounted to VMs TARGET COMPONENTS XE command line, ie: xe eject-all-isos XenCenter (API call to eject-all-isos) OR in our XSxxxxx.upadate package format as a pre-req script. EXAMPLE CODE An example is a file I wrote, xe-eject-all-isos (using Bash for simplicity)= : #!/bin/bash echo "CHECKING" # Get list of VMs from xe vm-list -- specifically UUID VMLIST=3D`xe vm-list is-control-domain=3Dfalse | grep uuid | awk '{print $5= }'` # Loop through list and see if a DVD/CDROM is present for VMUUID in $VMLIST do VMNAME=3D`xe vm-list uuid=3D$VMUUID | grep "name-label" | awk '{print = $4}'` ISOMOUNTED=3D`xe vm-cd-list uuid=3D$VMUUID | grep "empty" | awk '{print= $4}'` if [ "$ISOMOUNTED" =3D "false" ] ; then xe vm-cd-eject uuid=3D$VMUUID echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME" fi done # END echo "DONE" Sincerely, Jesse Benedict, CCA Citrix, Inc. | XenServer, XenClient Support Team --_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am setting up my own dev environment, but in the m= ean-time I would like to propose the following:

 

PROPOSAL

Auto Ejection of All Mounted CDs

 

PURPOSE

To make application of patches/hotfixes easier in la= rge environments where ISO images may be mounted to VMs

 

TARGET COMPONENTS

XE command line, ie:

xe eject-all-isos

 

XenCenter (API call to eject-all-isos)

 

OR in our XSxxxxx.upadate package format as a pre-re= q script.

 

EXAMPLE CODE

An example is a file I wrote, xe-eject-all-isos (usi= ng Bash for simplicity):

 

= #!/bin/bash

=  

= echo "CHECKING"

=  

= # Get list of VMs from xe vm-list -- specifically UUID

= VMLIST=3D`xe vm-list is-control-domain=3Dfalse | grep uuid | awk '{print $5= }'`

=  

= # Loop through list and see if a DVD/CDROM is present

= for VMUUID in $VMLIST

= do

=      VMNAME=3D`xe vm-list uuid=3D$VMUUID | grep "n= ame-label" | awk '{print $4}'`

=     ISOMOUNTED=3D`xe vm-cd-list uuid=3D$VMUUID | grep "= empty" | awk '{print $4}'`

=  

=      if [ "$ISOMOUNTED" =3D "false"= ] ; then

=            xe vm-cd-eject= uuid=3D$VMUUID

=            echo "UNM= OUNTED DVD/CD IMAGE FROM $VMNAME"

=      fi     

= done

=  

= # END

= echo "DONE"

=  

 

 

Sincerely,

 

 

Jesse Benedict, CCA

Citrix, Inc= . | XenServer, XenClient Support Team

 

--_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_-- --===============4958799442350634349== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4958799442350634349==-- From xen-api-bounces@lists.xen.org Tue Jan 07 23:41:37 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 Jan 2014 23:41:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0gH2-0007s1-W5; Tue, 07 Jan 2014 23:41:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0gH1-0007rw-Iv for xen-api@lists.xensource.com; Tue, 07 Jan 2014 23:41:27 +0000 Received: from [193.109.254.147:40042] by server-1.bemta-14.messagelabs.com id 1A/19-15600-6A09CC25; Tue, 07 Jan 2014 23:41:26 +0000 X-Env-Sender: jesse.benedict@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1389138083!9422077!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19408 invoked from network); 7 Jan 2014 23:41:24 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 23:41:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="90692910" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 07 Jan 2014 23:41:22 +0000 Received: from FTLPEX01CL02.citrite.net ([169.254.2.8]) by FTLPEX01CL03.citrite.net ([169.254.1.174]) with mapi id 14.02.0342.004; Tue, 7 Jan 2014 18:41:22 -0500 From: Jesse Benedict To: "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Thread-Topic: "Eject ISO Image" Mechanism Proposal Thread-Index: Ac8MAe9mZooMHbODQaSCdpuWlKK1Rg== Date: Tue, 7 Jan 2014 23:41:21 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.11.24.65] MIME-Version: 1.0 X-DLP: MIA1 Subject: [Xen-API] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4958799442350634349==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4958799442350634349== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_" --_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am setting up my own dev environment, but in the mean-time I would like t= o propose the following: PROPOSAL Auto Ejection of All Mounted CDs PURPOSE To make application of patches/hotfixes easier in large environments where = ISO images may be mounted to VMs TARGET COMPONENTS XE command line, ie: xe eject-all-isos XenCenter (API call to eject-all-isos) OR in our XSxxxxx.upadate package format as a pre-req script. EXAMPLE CODE An example is a file I wrote, xe-eject-all-isos (using Bash for simplicity)= : #!/bin/bash echo "CHECKING" # Get list of VMs from xe vm-list -- specifically UUID VMLIST=3D`xe vm-list is-control-domain=3Dfalse | grep uuid | awk '{print $5= }'` # Loop through list and see if a DVD/CDROM is present for VMUUID in $VMLIST do VMNAME=3D`xe vm-list uuid=3D$VMUUID | grep "name-label" | awk '{print = $4}'` ISOMOUNTED=3D`xe vm-cd-list uuid=3D$VMUUID | grep "empty" | awk '{print= $4}'` if [ "$ISOMOUNTED" =3D "false" ] ; then xe vm-cd-eject uuid=3D$VMUUID echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME" fi done # END echo "DONE" Sincerely, Jesse Benedict, CCA Citrix, Inc. | XenServer, XenClient Support Team --_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am setting up my own dev environment, but in the m= ean-time I would like to propose the following:

 

PROPOSAL

Auto Ejection of All Mounted CDs

 

PURPOSE

To make application of patches/hotfixes easier in la= rge environments where ISO images may be mounted to VMs

 

TARGET COMPONENTS

XE command line, ie:

xe eject-all-isos

 

XenCenter (API call to eject-all-isos)

 

OR in our XSxxxxx.upadate package format as a pre-re= q script.

 

EXAMPLE CODE

An example is a file I wrote, xe-eject-all-isos (usi= ng Bash for simplicity):

 

= #!/bin/bash

=  

= echo "CHECKING"

=  

= # Get list of VMs from xe vm-list -- specifically UUID

= VMLIST=3D`xe vm-list is-control-domain=3Dfalse | grep uuid | awk '{print $5= }'`

=  

= # Loop through list and see if a DVD/CDROM is present

= for VMUUID in $VMLIST

= do

=      VMNAME=3D`xe vm-list uuid=3D$VMUUID | grep "n= ame-label" | awk '{print $4}'`

=     ISOMOUNTED=3D`xe vm-cd-list uuid=3D$VMUUID | grep "= empty" | awk '{print $4}'`

=  

=      if [ "$ISOMOUNTED" =3D "false"= ] ; then

=            xe vm-cd-eject= uuid=3D$VMUUID

=            echo "UNM= OUNTED DVD/CD IMAGE FROM $VMNAME"

=      fi     

= done

=  

= # END

= echo "DONE"

=  

 

 

Sincerely,

 

 

Jesse Benedict, CCA

Citrix, Inc= . | XenServer, XenClient Support Team

 

--_000_B8C24FCCBFC459419478083491FF39E21DE13FFTLPEX01CL02citri_-- --===============4958799442350634349== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4958799442350634349==-- From xen-api-bounces@lists.xen.org Wed Jan 08 01:34:35 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 01:34:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0i2K-0004XY-Gi; Wed, 08 Jan 2014 01:34:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0i2J-0004XT-9g for xen-api@lists.xensource.com; Wed, 08 Jan 2014 01:34:23 +0000 Received: from [85.158.137.68:38058] by server-9.bemta-3.messagelabs.com id 8E/F0-13104-E1BACC25; Wed, 08 Jan 2014 01:34:22 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1389144860!7810492!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32214 invoked from network); 8 Jan 2014 01:34:21 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 01:34:21 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="88558254" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 01:34:19 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 20:34:19 -0500 Received: from [10.68.19.21] (10.68.19.21) by AMSPEX01CL02.citrite.net (10.69.46.33) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 02:34:17 +0100 Message-ID: <52CCAB19.9090200@citrix.com> Date: Wed, 8 Jan 2014 01:34:17 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Rishi <2rushikeshj@gmail.com>, "xen-api@lists.xensource.com" , References: In-Reply-To: X-Originating-IP: [10.68.19.21] X-DLP: MIA1 Subject: Re: [Xen-API] [xs-devel] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8574246524163221218==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8574246524163221218== Content-Type: multipart/alternative; boundary="------------070200090400050208090705" --------------070200090400050208090705 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 07/01/2014 20:27, Rishi wrote: > Hello List, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? > > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? > > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? > > > > Regards, > Rishi In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update. (We make no explicit guarantee that they will work, but we do do our best not to break things.) The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially. ~Andrew --------------070200090400050208090705 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 07/01/2014 20:27, Rishi wrote:
Hello List,

I have few questions about XenTools

Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ?

How does one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?

Are there any logs inside VM/Host about tools driver errors to look in case of problems ?



Regards,
Rishi

In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update.  (We make no explicit guarantee that they will work, but we do do our best not to break things.)

The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially.

~Andrew
--------------070200090400050208090705-- --===============8574246524163221218== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8574246524163221218==-- From xen-api-bounces@lists.xen.org Wed Jan 08 01:34:35 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 01:34:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0i2K-0004XY-Gi; Wed, 08 Jan 2014 01:34:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0i2J-0004XT-9g for xen-api@lists.xensource.com; Wed, 08 Jan 2014 01:34:23 +0000 Received: from [85.158.137.68:38058] by server-9.bemta-3.messagelabs.com id 8E/F0-13104-E1BACC25; Wed, 08 Jan 2014 01:34:22 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1389144860!7810492!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32214 invoked from network); 8 Jan 2014 01:34:21 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 01:34:21 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="88558254" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 01:34:19 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 20:34:19 -0500 Received: from [10.68.19.21] (10.68.19.21) by AMSPEX01CL02.citrite.net (10.69.46.33) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 02:34:17 +0100 Message-ID: <52CCAB19.9090200@citrix.com> Date: Wed, 8 Jan 2014 01:34:17 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Rishi <2rushikeshj@gmail.com>, "xen-api@lists.xensource.com" , References: In-Reply-To: X-Originating-IP: [10.68.19.21] X-DLP: MIA1 Subject: Re: [Xen-API] [xs-devel] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8574246524163221218==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8574246524163221218== Content-Type: multipart/alternative; boundary="------------070200090400050208090705" --------------070200090400050208090705 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 07/01/2014 20:27, Rishi wrote: > Hello List, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? > > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? > > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? > > > > Regards, > Rishi In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update. (We make no explicit guarantee that they will work, but we do do our best not to break things.) The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially. ~Andrew --------------070200090400050208090705 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 07/01/2014 20:27, Rishi wrote:
Hello List,

I have few questions about XenTools

Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ?

How does one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?

Are there any logs inside VM/Host about tools driver errors to look in case of problems ?



Regards,
Rishi

In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update.  (We make no explicit guarantee that they will work, but we do do our best not to break things.)

The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially.

~Andrew
--------------070200090400050208090705-- --===============8574246524163221218== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8574246524163221218==-- From xen-api-bounces@lists.xen.org Wed Jan 08 02:10:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 02:10:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0ib0-0007Fn-5P; Wed, 08 Jan 2014 02:10:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0iay-0007Fi-3r for xen-api@lists.xensource.com; Wed, 08 Jan 2014 02:10:12 +0000 Received: from [85.158.143.35:36402] by server-1.bemta-4.messagelabs.com id 7F/AB-02132-383BCC25; Wed, 08 Jan 2014 02:10:11 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1389147008!10243553!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27136 invoked from network); 8 Jan 2014 02:10:09 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 02:10:09 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="90720353" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 08 Jan 2014 02:10:07 +0000 Received: from AMSPEX01CL01.citrite.net (10.69.46.32) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 21:10:06 -0500 Received: from [10.68.19.21] (10.68.19.21) by AMSPEX01CL01.citrite.net (10.69.46.32) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 03:10:04 +0100 Message-ID: <52CCB37C.8040900@citrix.com> Date: Wed, 8 Jan 2014 02:10:04 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Jesse Benedict , "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" References: In-Reply-To: X-Originating-IP: [10.68.19.21] X-DLP: MIA2 Subject: Re: [Xen-API] [xs-devel] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4144166874666114527==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4144166874666114527== Content-Type: multipart/alternative; boundary="------------030803040908010401070608" --------------030803040908010401070608 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 07/01/2014 23:41, Jesse Benedict wrote: > > I am setting up my own dev environment, but in the mean-time I would > like to propose the following: > > > > *PROPOSAL* > > Auto Ejection of All Mounted CDs > > > > *PURPOSE* > > To make application of patches/hotfixes easier in large environments > where ISO images may be mounted to VMs > > > > *TARGET COMPONENTS* > > XE command line, ie: > > xe eject-all-isos > > > > XenCenter (API call to eject-all-isos) > > > > OR in our XSxxxxx.upadate package format as a pre-req script. > Looks very sensible and useful. However, when scripting xe calls, "params=some,list,of,parameter,you,are,interested,in" and "--minimal" are your friends. See inline below. > > > *EXAMPLE CODE* > > An example is a file I wrote, xe-eject-all-isos (using Bash for > simplicity): > > > > #!/bin/bash > > > > echo "CHECKING" > > > > # Get list of VMs from xe vm-list -- specifically UUID > > VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'` > VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr ',' ' ') should do that without grep or awk, (but sadly still using tr) (Note for Ring3: It would be lovely for shell scripts to get a space-delimited list from --minimal rather than comma-delimited, but I cant see a convenient option for that) > > > # Loop through list and see if a DVD/CDROM is present > > for VMUUID in $VMLIST > > do > > VMNAME=`xe vm-list uuid=$VMUUID | grep "name-label" | awk '{print > $4}'` > VMNAME="$(xe vm-list uuid=$VMUUID params=name-label --minimal)" You need to quote in case the VM name has spaces in. > ISOMOUNTED=`xe vm-cd-list uuid=$VMUUID | grep "empty" | awk > '{print $4}'` > vm-cd-list doesn't take a uuid parameter, but then again doesn't appear to function correctly. Note for Ring3: This appears to be a bug (tested on XS 6.2 SP1). `xe vm-cd-list uuid=` tab completes to VM uuids, but rejects them, and the help description doesn't mention uuid= as a valid parameter. The help text indicates that it accepts the meta-option "vm=", which works for vm names, but not for vm uuids. Running a bare `xe vm-cd-list` insists on having the '--multiple' option, and (when provided) hands back a list of vbd uuids of cds for each vm. Also, unlike some of the other $FOO-list options, vm-cd-list doesn't appear to like "params=". Jesse: Best as I can tell, you probably want: ISOMOUNTED=$(xe vm-cd-list vm=$VMNAME | grep "empty" | awk '{print $4}) > > > if [ "$ISOMOUNTED" = "false" ] ; then > > xe vm-cd-eject uuid=$VMUUID > xe vm-cd-eject also tab completes uuid= to VM uuids but rejects them, and yet accepts vm=$VMNAME > echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME" > > fi > > done > > > > # END > > echo "DONE" > > > > > > > > Sincerely, > I occurs to me that all of this can be achieved with the single call xe vm-cd-eject --multiple So long as you are happy to accept "operation failed on $VMUUID: Operation could not be performed because the drive is empty" for PV guests, and "operation failed on $VMUUID: INTERNAL_ERROR: [ Cli_util.Cli_failure("No CDs found") ]" for HVM guests, when CDs are not actually present in the first place. (Again, tested on XS 6.2 SP1) ~Andrew --------------030803040908010401070608 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 07/01/2014 23:41, Jesse Benedict wrote:

I am setting up my own dev environment, but in the mean-time I would like to propose the following:

 

PROPOSAL

Auto Ejection of All Mounted CDs

 

PURPOSE

To make application of patches/hotfixes easier in large environments where ISO images may be mounted to VMs

 

TARGET COMPONENTS

XE command line, ie:

xe eject-all-isos

 

XenCenter (API call to eject-all-isos)

 

OR in our XSxxxxx.upadate package format as a pre-req script.


Looks very sensible and useful.

However, when scripting xe calls, "params=some,list,of,parameter,you,are,interested,in" and "--minimal" are your friends.  See inline below.

 

EXAMPLE CODE

An example is a file I wrote, xe-eject-all-isos (using Bash for simplicity):

 

#!/bin/bash

 

echo "CHECKING"

 

# Get list of VMs from xe vm-list -- specifically UUID

VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'`


VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr ',' ' ')

should do that without grep or awk, (but sadly still using tr)

(Note for Ring3: It would be lovely for shell scripts to get a space-delimited list from --minimal rather than comma-delimited, but I cant see a convenient option for that)

 

# Loop through list and see if a DVD/CDROM is present

for VMUUID in $VMLIST

do

     VMNAME=`xe vm-list uuid=$VMUUID | grep "name-label" | awk '{print $4}'`


VMNAME="$(xe vm-list uuid=$VMUUID params=name-label --minimal)"

You need to quote in case the VM name has spaces in.

    ISOMOUNTED=`xe vm-cd-list uuid=$VMUUID | grep "empty" | awk '{print $4}'`


vm-cd-list doesn't take a uuid parameter, but then again doesn't appear to function correctly.

Note for Ring3: This appears to be a bug (tested on XS 6.2 SP1).  `xe vm-cd-list uuid=` tab completes to VM uuids, but rejects them, and the help description doesn't mention uuid= as a valid parameter.  The help text indicates that it accepts the meta-option "vm=", which works for vm names, but not for vm uuids.  Running a bare `xe vm-cd-list` insists on having the '--multiple' option, and (when provided) hands back a list of vbd uuids of cds for each vm.

Also, unlike some of the other $FOO-list options, vm-cd-list doesn't appear to like "params=".

Jesse:

Best as I can tell, you probably want:

ISOMOUNTED=$(xe vm-cd-list vm=$VMNAME | grep "empty" | awk '{print $4})

 

     if [ "$ISOMOUNTED" = "false" ] ; then

           xe vm-cd-eject uuid=$VMUUID


xe vm-cd-eject also tab completes uuid= to VM uuids but rejects them, and yet accepts vm=$VMNAME

           echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME"

     fi     

done

 

# END

echo "DONE"

 

 

 

Sincerely,


I occurs to me that all of this can be achieved with the single call

xe vm-cd-eject --multiple

So long as you are happy to accept

"operation failed on $VMUUID: Operation could not be performed because the drive is empty"

for PV guests, and

"operation failed on $VMUUID: INTERNAL_ERROR: [ Cli_util.Cli_failure("No CDs found") ]"

for HVM guests, when CDs are not actually present in the first place.  (Again, tested on XS 6.2 SP1)


~Andrew
--------------030803040908010401070608-- --===============4144166874666114527== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4144166874666114527==-- From xen-api-bounces@lists.xen.org Wed Jan 08 02:10:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 02:10:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0ib0-0007Fn-5P; Wed, 08 Jan 2014 02:10:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0iay-0007Fi-3r for xen-api@lists.xensource.com; Wed, 08 Jan 2014 02:10:12 +0000 Received: from [85.158.143.35:36402] by server-1.bemta-4.messagelabs.com id 7F/AB-02132-383BCC25; Wed, 08 Jan 2014 02:10:11 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1389147008!10243553!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27136 invoked from network); 8 Jan 2014 02:10:09 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 02:10:09 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208,217";a="90720353" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 08 Jan 2014 02:10:07 +0000 Received: from AMSPEX01CL01.citrite.net (10.69.46.32) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 21:10:06 -0500 Received: from [10.68.19.21] (10.68.19.21) by AMSPEX01CL01.citrite.net (10.69.46.32) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 03:10:04 +0100 Message-ID: <52CCB37C.8040900@citrix.com> Date: Wed, 8 Jan 2014 02:10:04 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Jesse Benedict , "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" References: In-Reply-To: X-Originating-IP: [10.68.19.21] X-DLP: MIA2 Subject: Re: [Xen-API] [xs-devel] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4144166874666114527==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4144166874666114527== Content-Type: multipart/alternative; boundary="------------030803040908010401070608" --------------030803040908010401070608 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 07/01/2014 23:41, Jesse Benedict wrote: > > I am setting up my own dev environment, but in the mean-time I would > like to propose the following: > > > > *PROPOSAL* > > Auto Ejection of All Mounted CDs > > > > *PURPOSE* > > To make application of patches/hotfixes easier in large environments > where ISO images may be mounted to VMs > > > > *TARGET COMPONENTS* > > XE command line, ie: > > xe eject-all-isos > > > > XenCenter (API call to eject-all-isos) > > > > OR in our XSxxxxx.upadate package format as a pre-req script. > Looks very sensible and useful. However, when scripting xe calls, "params=some,list,of,parameter,you,are,interested,in" and "--minimal" are your friends. See inline below. > > > *EXAMPLE CODE* > > An example is a file I wrote, xe-eject-all-isos (using Bash for > simplicity): > > > > #!/bin/bash > > > > echo "CHECKING" > > > > # Get list of VMs from xe vm-list -- specifically UUID > > VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'` > VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr ',' ' ') should do that without grep or awk, (but sadly still using tr) (Note for Ring3: It would be lovely for shell scripts to get a space-delimited list from --minimal rather than comma-delimited, but I cant see a convenient option for that) > > > # Loop through list and see if a DVD/CDROM is present > > for VMUUID in $VMLIST > > do > > VMNAME=`xe vm-list uuid=$VMUUID | grep "name-label" | awk '{print > $4}'` > VMNAME="$(xe vm-list uuid=$VMUUID params=name-label --minimal)" You need to quote in case the VM name has spaces in. > ISOMOUNTED=`xe vm-cd-list uuid=$VMUUID | grep "empty" | awk > '{print $4}'` > vm-cd-list doesn't take a uuid parameter, but then again doesn't appear to function correctly. Note for Ring3: This appears to be a bug (tested on XS 6.2 SP1). `xe vm-cd-list uuid=` tab completes to VM uuids, but rejects them, and the help description doesn't mention uuid= as a valid parameter. The help text indicates that it accepts the meta-option "vm=", which works for vm names, but not for vm uuids. Running a bare `xe vm-cd-list` insists on having the '--multiple' option, and (when provided) hands back a list of vbd uuids of cds for each vm. Also, unlike some of the other $FOO-list options, vm-cd-list doesn't appear to like "params=". Jesse: Best as I can tell, you probably want: ISOMOUNTED=$(xe vm-cd-list vm=$VMNAME | grep "empty" | awk '{print $4}) > > > if [ "$ISOMOUNTED" = "false" ] ; then > > xe vm-cd-eject uuid=$VMUUID > xe vm-cd-eject also tab completes uuid= to VM uuids but rejects them, and yet accepts vm=$VMNAME > echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME" > > fi > > done > > > > # END > > echo "DONE" > > > > > > > > Sincerely, > I occurs to me that all of this can be achieved with the single call xe vm-cd-eject --multiple So long as you are happy to accept "operation failed on $VMUUID: Operation could not be performed because the drive is empty" for PV guests, and "operation failed on $VMUUID: INTERNAL_ERROR: [ Cli_util.Cli_failure("No CDs found") ]" for HVM guests, when CDs are not actually present in the first place. (Again, tested on XS 6.2 SP1) ~Andrew --------------030803040908010401070608 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 07/01/2014 23:41, Jesse Benedict wrote:

I am setting up my own dev environment, but in the mean-time I would like to propose the following:

 

PROPOSAL

Auto Ejection of All Mounted CDs

 

PURPOSE

To make application of patches/hotfixes easier in large environments where ISO images may be mounted to VMs

 

TARGET COMPONENTS

XE command line, ie:

xe eject-all-isos

 

XenCenter (API call to eject-all-isos)

 

OR in our XSxxxxx.upadate package format as a pre-req script.


Looks very sensible and useful.

However, when scripting xe calls, "params=some,list,of,parameter,you,are,interested,in" and "--minimal" are your friends.  See inline below.

 

EXAMPLE CODE

An example is a file I wrote, xe-eject-all-isos (using Bash for simplicity):

 

#!/bin/bash

 

echo "CHECKING"

 

# Get list of VMs from xe vm-list -- specifically UUID

VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'`


VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr ',' ' ')

should do that without grep or awk, (but sadly still using tr)

(Note for Ring3: It would be lovely for shell scripts to get a space-delimited list from --minimal rather than comma-delimited, but I cant see a convenient option for that)

 

# Loop through list and see if a DVD/CDROM is present

for VMUUID in $VMLIST

do

     VMNAME=`xe vm-list uuid=$VMUUID | grep "name-label" | awk '{print $4}'`


VMNAME="$(xe vm-list uuid=$VMUUID params=name-label --minimal)"

You need to quote in case the VM name has spaces in.

    ISOMOUNTED=`xe vm-cd-list uuid=$VMUUID | grep "empty" | awk '{print $4}'`


vm-cd-list doesn't take a uuid parameter, but then again doesn't appear to function correctly.

Note for Ring3: This appears to be a bug (tested on XS 6.2 SP1).  `xe vm-cd-list uuid=` tab completes to VM uuids, but rejects them, and the help description doesn't mention uuid= as a valid parameter.  The help text indicates that it accepts the meta-option "vm=", which works for vm names, but not for vm uuids.  Running a bare `xe vm-cd-list` insists on having the '--multiple' option, and (when provided) hands back a list of vbd uuids of cds for each vm.

Also, unlike some of the other $FOO-list options, vm-cd-list doesn't appear to like "params=".

Jesse:

Best as I can tell, you probably want:

ISOMOUNTED=$(xe vm-cd-list vm=$VMNAME | grep "empty" | awk '{print $4})

 

     if [ "$ISOMOUNTED" = "false" ] ; then

           xe vm-cd-eject uuid=$VMUUID


xe vm-cd-eject also tab completes uuid= to VM uuids but rejects them, and yet accepts vm=$VMNAME

           echo "UNMOUNTED DVD/CD IMAGE FROM $VMNAME"

     fi     

done

 

# END

echo "DONE"

 

 

 

Sincerely,


I occurs to me that all of this can be achieved with the single call

xe vm-cd-eject --multiple

So long as you are happy to accept

"operation failed on $VMUUID: Operation could not be performed because the drive is empty"

for PV guests, and

"operation failed on $VMUUID: INTERNAL_ERROR: [ Cli_util.Cli_failure("No CDs found") ]"

for HVM guests, when CDs are not actually present in the first place.  (Again, tested on XS 6.2 SP1)


~Andrew
--------------030803040908010401070608-- --===============4144166874666114527== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4144166874666114527==-- From xen-api-bounces@lists.xen.org Wed Jan 08 03:06:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 03:06:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0jSw-0001wv-2W; Wed, 08 Jan 2014 03:05:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0jSu-0001wq-FU for xen-api@lists.xensource.com; Wed, 08 Jan 2014 03:05:56 +0000 Received: from [85.158.139.211:59229] by server-8.bemta-5.messagelabs.com id 5F/33-29838-390CCC25; Wed, 08 Jan 2014 03:05:55 +0000 X-Env-Sender: Jonathan.Davies@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1389150353!8252097!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3516 invoked from network); 8 Jan 2014 03:05:55 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 03:05:55 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208";a="88573728" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 03:05:53 +0000 Received: from AMSPEX01CL01.citrite.net (10.69.46.32) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 22:05:52 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL01.citrite.net ([10.69.46.32]) with mapi id 14.02.0342.004; Wed, 8 Jan 2014 04:05:50 +0100 From: Jonathan Davies To: Andrew Cooper , Jesse Benedict , "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Thread-Topic: [xs-devel] "Eject ISO Image" Mechanism Proposal Thread-Index: Ac8MAe9mZooMHbODQaSCdpuWlKK1RgADG04AAAGYvYA= Date: Wed, 8 Jan 2014 03:05:50 +0000 Message-ID: <0A601460A6633D4A83831E1F345227051EAF55@AMSPEX01CL03.citrite.net> References: <52CCB37C.8040900@citrix.com> In-Reply-To: <52CCB37C.8040900@citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 x-account-key: account3 x-identity-key: id2 x-mozilla-draft-info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0 fcc: imap://jonathandav@mail.citrix.com/Sent x-ms-exchange-imapappendstamp: AMSPEX01CL03.citrite.net (14.02.0341.000) x-originating-ip: [10.69.129.151] Content-ID: MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-API] [xs-devel] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 08/01/2014 10:10, Andrew Cooper wrote: > On 07/01/2014 23:41, Jesse Benedict wrote: --snip-- >> *EXAMPLE CODE* >> >> An example is a file I wrote, xe-eject-all-isos (using Bash for >> simplicity): >> >> #!/bin/bash >> >> echo "CHECKING" >> >> # Get list of VMs from xe vm-list -- specifically UUID >> >> VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'` >> > > VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr > ',' ' ') > > should do that without grep or awk, (but sadly still using tr) > > (Note for Ring3: It would be lovely for shell scripts to get a > space-delimited list from --minimal rather than comma-delimited, but I > cant see a convenient option for that) You can avoid the tr by inviting bash to treat the comma character as the delimiter: VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal) IFS=, for VMUUID in $VMLIST; do ... done Jonathan _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 03:06:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 03:06:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0jSw-0001wv-2W; Wed, 08 Jan 2014 03:05:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0jSu-0001wq-FU for xen-api@lists.xensource.com; Wed, 08 Jan 2014 03:05:56 +0000 Received: from [85.158.139.211:59229] by server-8.bemta-5.messagelabs.com id 5F/33-29838-390CCC25; Wed, 08 Jan 2014 03:05:55 +0000 X-Env-Sender: Jonathan.Davies@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1389150353!8252097!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3516 invoked from network); 8 Jan 2014 03:05:55 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 03:05:55 -0000 X-IronPort-AV: E=Sophos;i="4.95,621,1384300800"; d="scan'208";a="88573728" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 03:05:53 +0000 Received: from AMSPEX01CL01.citrite.net (10.69.46.32) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 7 Jan 2014 22:05:52 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL01.citrite.net ([10.69.46.32]) with mapi id 14.02.0342.004; Wed, 8 Jan 2014 04:05:50 +0100 From: Jonathan Davies To: Andrew Cooper , Jesse Benedict , "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Thread-Topic: [xs-devel] "Eject ISO Image" Mechanism Proposal Thread-Index: Ac8MAe9mZooMHbODQaSCdpuWlKK1RgADG04AAAGYvYA= Date: Wed, 8 Jan 2014 03:05:50 +0000 Message-ID: <0A601460A6633D4A83831E1F345227051EAF55@AMSPEX01CL03.citrite.net> References: <52CCB37C.8040900@citrix.com> In-Reply-To: <52CCB37C.8040900@citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 x-account-key: account3 x-identity-key: id2 x-mozilla-draft-info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0 fcc: imap://jonathandav@mail.citrix.com/Sent x-ms-exchange-imapappendstamp: AMSPEX01CL03.citrite.net (14.02.0341.000) x-originating-ip: [10.69.129.151] Content-ID: MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-API] [xs-devel] "Eject ISO Image" Mechanism Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 08/01/2014 10:10, Andrew Cooper wrote: > On 07/01/2014 23:41, Jesse Benedict wrote: --snip-- >> *EXAMPLE CODE* >> >> An example is a file I wrote, xe-eject-all-isos (using Bash for >> simplicity): >> >> #!/bin/bash >> >> echo "CHECKING" >> >> # Get list of VMs from xe vm-list -- specifically UUID >> >> VMLIST=`xe vm-list is-control-domain=false | grep uuid | awk '{print $5}'` >> > > VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal | tr > ',' ' ') > > should do that without grep or awk, (but sadly still using tr) > > (Note for Ring3: It would be lovely for shell scripts to get a > space-delimited list from --minimal rather than comma-delimited, but I > cant see a convenient option for that) You can avoid the tr by inviting bash to treat the comma character as the delimiter: VMLIST=$(xe vm-list is-control-domain=false params=uuid --minimal) IFS=, for VMUUID in $VMLIST; do ... done Jonathan _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 08:03:01 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 08:03:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0o6F-0007sD-6D; Wed, 08 Jan 2014 08:02:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0o6D-0007s8-PG for xen-api@lists.xensource.com; Wed, 08 Jan 2014 08:02:49 +0000 Received: from [85.158.139.211:16331] by server-11.bemta-5.messagelabs.com id AD/D2-23268-8260DC25; Wed, 08 Jan 2014 08:02:48 +0000 X-Env-Sender: shafiontherise@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1389168167!8426875!1 X-Originating-IP: [209.85.223.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10749 invoked from network); 8 Jan 2014 08:02:48 -0000 Received: from mail-ie0-f169.google.com (HELO mail-ie0-f169.google.com) (209.85.223.169) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 08:02:48 -0000 Received: by mail-ie0-f169.google.com with SMTP id e14so1645117iej.0 for ; Wed, 08 Jan 2014 00:02:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JeKlD9h+A/gG5WaErWZCq80nyu0CmcJG/VL5+ftq64I=; b=xWiahRrrf/aUVd3wPr+8kms0A5PJJ6w/9xbA0ZGDQ4Pt92qfs2gGzydv05mHQuHdVG U8Hhpt9Ll3QMyHoQdYsa9yOUuxELzp9RrGvvSvQgGso1IeTyY1R8FURtjZCl8z2xblpo ICc2L/zwKeDpZ2tlJdi4OPYSYjNYTJfwvATWBS+DnF2Sza1KEQWKVOAj6A3COH2QnNib +4HpFF91bMKHAy1fe1hNpHYBnYfwn+IUHdIGn356BO6H8OwfRmUuxGD+3CfGpPGOUp5R 2wyRZLyeevtHQLu5Vfuj3A7fIJLpl0+qiQ6RyWddA/bFecWmPFZ/QJvI0h3E9UywmdI2 DE3w== MIME-Version: 1.0 X-Received: by 10.51.15.130 with SMTP id fo2mr30329231igd.28.1389168166801; Wed, 08 Jan 2014 00:02:46 -0800 (PST) Received: by 10.64.73.42 with HTTP; Wed, 8 Jan 2014 00:02:46 -0800 (PST) Date: Wed, 8 Jan 2014 13:32:46 +0530 Message-ID: From: Shafi Mohammed To: xen-api@lists.xensource.com Subject: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi , I am working on a backup application . Our solution works fine for a single Xen host . But on A Xen Pool Configuration, session() call works only for the master , Is there any call to retrieve the IP of the master when we are working with the slave nodes ,so that a redirection can be made to that obtained master IP when slave node is enquired for backup . Thank you Shafi Mohammed _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 08:03:01 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 08:03:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0o6F-0007sD-6D; Wed, 08 Jan 2014 08:02:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0o6D-0007s8-PG for xen-api@lists.xensource.com; Wed, 08 Jan 2014 08:02:49 +0000 Received: from [85.158.139.211:16331] by server-11.bemta-5.messagelabs.com id AD/D2-23268-8260DC25; Wed, 08 Jan 2014 08:02:48 +0000 X-Env-Sender: shafiontherise@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1389168167!8426875!1 X-Originating-IP: [209.85.223.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10749 invoked from network); 8 Jan 2014 08:02:48 -0000 Received: from mail-ie0-f169.google.com (HELO mail-ie0-f169.google.com) (209.85.223.169) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 08:02:48 -0000 Received: by mail-ie0-f169.google.com with SMTP id e14so1645117iej.0 for ; Wed, 08 Jan 2014 00:02:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JeKlD9h+A/gG5WaErWZCq80nyu0CmcJG/VL5+ftq64I=; b=xWiahRrrf/aUVd3wPr+8kms0A5PJJ6w/9xbA0ZGDQ4Pt92qfs2gGzydv05mHQuHdVG U8Hhpt9Ll3QMyHoQdYsa9yOUuxELzp9RrGvvSvQgGso1IeTyY1R8FURtjZCl8z2xblpo ICc2L/zwKeDpZ2tlJdi4OPYSYjNYTJfwvATWBS+DnF2Sza1KEQWKVOAj6A3COH2QnNib +4HpFF91bMKHAy1fe1hNpHYBnYfwn+IUHdIGn356BO6H8OwfRmUuxGD+3CfGpPGOUp5R 2wyRZLyeevtHQLu5Vfuj3A7fIJLpl0+qiQ6RyWddA/bFecWmPFZ/QJvI0h3E9UywmdI2 DE3w== MIME-Version: 1.0 X-Received: by 10.51.15.130 with SMTP id fo2mr30329231igd.28.1389168166801; Wed, 08 Jan 2014 00:02:46 -0800 (PST) Received: by 10.64.73.42 with HTTP; Wed, 8 Jan 2014 00:02:46 -0800 (PST) Date: Wed, 8 Jan 2014 13:32:46 +0530 Message-ID: From: Shafi Mohammed To: xen-api@lists.xensource.com Subject: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi , I am working on a backup application . Our solution works fine for a single Xen host . But on A Xen Pool Configuration, session() call works only for the master , Is there any call to retrieve the IP of the master when we are working with the slave nodes ,so that a redirection can be made to that obtained master IP when slave node is enquired for backup . Thank you Shafi Mohammed _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 12:10:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 12:10:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0rxT-0005pH-5j; Wed, 08 Jan 2014 12:10:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0rxQ-0005p8-OU for xen-api@lists.xensource.com; Wed, 08 Jan 2014 12:10:00 +0000 Received: from [85.158.143.35:28256] by server-1.bemta-4.messagelabs.com id B7/E5-02132-8104DC25; Wed, 08 Jan 2014 12:10:00 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1389182998!3264823!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3045 invoked from network); 8 Jan 2014 12:09:59 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 12:09:59 -0000 X-IronPort-AV: E=Sophos;i="4.95,624,1384300800"; d="scan'208";a="90831978" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 08 Jan 2014 12:09:57 +0000 Received: from AMSPEX01CL03.citrite.net (10.69.46.34) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Wed, 8 Jan 2014 07:09:57 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL03.citrite.net ([10.69.46.34]) with mapi id 14.02.0342.004; Wed, 8 Jan 2014 13:09:56 +0100 From: John Else To: Shafi Mohammed , "xen-api@lists.xensource.com" Thread-Topic: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API Thread-Index: AQHPDEiQQHbh3VKmPEKeLo/XMdHsE5p6t+zQ Date: Wed, 8 Jan 2014 12:09:55 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.237.222] MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > Hi , > I am working on a backup application . Our solution works fine for a single Xen host . But on A Xen Pool Configuration, session() call works only for the master , Is there any call to retrieve the IP of the master when we are working with the slave nodes ,so that a > redirection can be made to that obtained master IP when slave node is enquired for backup . > Thank you > Shafi Mohammed Hi Shafi, If you attempt to make an API call to a slave (even something trivial like pool.get_all()), you'll get the HOST_IS_SLAVE exception, along with the master's IP address. Here's the (C#) code XenCenter uses to extract the IP address from the exception: https://github.com/xenserver/xenadmin/blob/da00b13bb94603b369b873b0a555d44f15fa0ca5/XenAdmin/Network/XenConnectionUI.cs#L117 Hope this helps, John _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 12:10:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 12:10:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0rxT-0005pH-5j; Wed, 08 Jan 2014 12:10:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0rxQ-0005p8-OU for xen-api@lists.xensource.com; Wed, 08 Jan 2014 12:10:00 +0000 Received: from [85.158.143.35:28256] by server-1.bemta-4.messagelabs.com id B7/E5-02132-8104DC25; Wed, 08 Jan 2014 12:10:00 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1389182998!3264823!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3045 invoked from network); 8 Jan 2014 12:09:59 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 12:09:59 -0000 X-IronPort-AV: E=Sophos;i="4.95,624,1384300800"; d="scan'208";a="90831978" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 08 Jan 2014 12:09:57 +0000 Received: from AMSPEX01CL03.citrite.net (10.69.46.34) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Wed, 8 Jan 2014 07:09:57 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL03.citrite.net ([10.69.46.34]) with mapi id 14.02.0342.004; Wed, 8 Jan 2014 13:09:56 +0100 From: John Else To: Shafi Mohammed , "xen-api@lists.xensource.com" Thread-Topic: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API Thread-Index: AQHPDEiQQHbh3VKmPEKeLo/XMdHsE5p6t+zQ Date: Wed, 8 Jan 2014 12:09:55 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.237.222] MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > Hi , > I am working on a backup application . Our solution works fine for a single Xen host . But on A Xen Pool Configuration, session() call works only for the master , Is there any call to retrieve the IP of the master when we are working with the slave nodes ,so that a > redirection can be made to that obtained master IP when slave node is enquired for backup . > Thank you > Shafi Mohammed Hi Shafi, If you attempt to make an API call to a slave (even something trivial like pool.get_all()), you'll get the HOST_IS_SLAVE exception, along with the master's IP address. Here's the (C#) code XenCenter uses to extract the IP address from the exception: https://github.com/xenserver/xenadmin/blob/da00b13bb94603b369b873b0a555d44f15fa0ca5/XenAdmin/Network/XenConnectionUI.cs#L117 Hope this helps, John _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 22:51:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 22:51:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y5-0001vm-5t; Wed, 08 Jan 2014 22:51:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y3-0001vL-Kd; Wed, 08 Jan 2014 22:51:19 +0000 Received: from [193.109.254.147:47051] by server-7.bemta-14.messagelabs.com id AC/5E-15500-666DDC25; Wed, 08 Jan 2014 22:51:18 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389221466!9619514!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTE5NTIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26946 invoked from network); 8 Jan 2014 22:51:08 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 22:51:08 -0000 X-IronPort-AV: E=Sophos;i="4.95,626,1384300800"; d="asc'?scan'208";a="88938087" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 22:50:49 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 17:50:48 -0500 Message-ID: <1389221447.16457.24.camel@Solace> From: Dario Faggioli To: Date: Wed, 8 Jan 2014 23:50:47 +0100 In-Reply-To: <52C2CD67.6050603@xen.org> References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> <52C2CD67.6050603@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "publicity@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7628262663614535382==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7628262663614535382== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W8K1qlr634eyxl2U9E1o" --=-W8K1qlr634eyxl2U9E1o Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-31 at 13:57 +0000, Lars Kurth wrote: > On 28/12/2013 15:57, Dario Faggioli wrote: > > So I was wondering, we did not get that much of a response about this > > (or perhaps we did, but not in public, in which case, ignore me). > > > > I know, holidays are not helping, etc. but, anyway, should we turn this > > e-mail into a blog post to send out in early January? I'm up for it if > > we think it's a good thing to do. > It is probably the holidays: I know that Cloudious Systems (the makers= =20 > of OSv) are interested showing OSv running on top of Xen and so do the= =20 > XO guys. >=20 > A blog post could be a good idea (tying it up with the DevRoom program,= =20 > which has not yet been published). > Ok. I checked this out earlier today, and the program for Saturday is out... Still waiting for Sunday. As soon as that will be available, I think, as you suggest, we should blog about these two things, i.e.: - the devroom program - the chance of showing demos at the booth (mentioning which ones we=20 already know will be performed) > Another approach would be to reach out pro-actively to people we want to= =20 > do demos (e.g. Samsung, people/projects with RT schedulers, ...).=20 > Unfortunuately I will struggle to do this given that I am in China. >=20 Right. I did that for Qubes, and it worked, as it did for OSv. I'll try to ping some more people directly, let's see how that goes. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-W8K1qlr634eyxl2U9E1o Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlLN1kcACgkQk4XaBE3IOsS/BQCeKkExjbBjYrffaDvQ8Y1Uljtg 7hsAnifpbMIrvyYu/l69uVvPIszvAalN =WHwC -----END PGP SIGNATURE----- --=-W8K1qlr634eyxl2U9E1o-- --===============7628262663614535382== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7628262663614535382==-- From xen-api-bounces@lists.xen.org Wed Jan 08 22:51:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 22:51:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y5-0001vm-5t; Wed, 08 Jan 2014 22:51:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y3-0001vL-Kd; Wed, 08 Jan 2014 22:51:19 +0000 Received: from [193.109.254.147:47051] by server-7.bemta-14.messagelabs.com id AC/5E-15500-666DDC25; Wed, 08 Jan 2014 22:51:18 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389221466!9619514!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTE5NTIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26946 invoked from network); 8 Jan 2014 22:51:08 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 22:51:08 -0000 X-IronPort-AV: E=Sophos;i="4.95,626,1384300800"; d="asc'?scan'208";a="88938087" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 22:50:49 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 8 Jan 2014 17:50:48 -0500 Message-ID: <1389221447.16457.24.camel@Solace> From: Dario Faggioli To: Date: Wed, 8 Jan 2014 23:50:47 +0100 In-Reply-To: <52C2CD67.6050603@xen.org> References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> <52C2CD67.6050603@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "publicity@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7628262663614535382==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7628262663614535382== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W8K1qlr634eyxl2U9E1o" --=-W8K1qlr634eyxl2U9E1o Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-31 at 13:57 +0000, Lars Kurth wrote: > On 28/12/2013 15:57, Dario Faggioli wrote: > > So I was wondering, we did not get that much of a response about this > > (or perhaps we did, but not in public, in which case, ignore me). > > > > I know, holidays are not helping, etc. but, anyway, should we turn this > > e-mail into a blog post to send out in early January? I'm up for it if > > we think it's a good thing to do. > It is probably the holidays: I know that Cloudious Systems (the makers= =20 > of OSv) are interested showing OSv running on top of Xen and so do the= =20 > XO guys. >=20 > A blog post could be a good idea (tying it up with the DevRoom program,= =20 > which has not yet been published). > Ok. I checked this out earlier today, and the program for Saturday is out... Still waiting for Sunday. As soon as that will be available, I think, as you suggest, we should blog about these two things, i.e.: - the devroom program - the chance of showing demos at the booth (mentioning which ones we=20 already know will be performed) > Another approach would be to reach out pro-actively to people we want to= =20 > do demos (e.g. Samsung, people/projects with RT schedulers, ...).=20 > Unfortunuately I will struggle to do this given that I am in China. >=20 Right. I did that for Qubes, and it worked, as it did for OSv. I'll try to ping some more people directly, let's see how that goes. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-W8K1qlr634eyxl2U9E1o Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlLN1kcACgkQk4XaBE3IOsS/BQCeKkExjbBjYrffaDvQ8Y1Uljtg 7hsAnifpbMIrvyYu/l69uVvPIszvAalN =WHwC -----END PGP SIGNATURE----- --=-W8K1qlr634eyxl2U9E1o-- --===============7628262663614535382== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7628262663614535382==-- From xen-api-bounces@lists.xen.org Wed Jan 08 23:39:32 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 23:39:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W12iX-0005rJ-Hl; Wed, 08 Jan 2014 23:39:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W12iW-0005qe-QQ for xen-api@lists.xen.org; Wed, 08 Jan 2014 23:39:20 +0000 Received: from [193.109.254.147:61008] by server-9.bemta-14.messagelabs.com id 70/57-13957-8A1EDC25; Wed, 08 Jan 2014 23:39:20 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1389224357!7427495!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10478 invoked from network); 8 Jan 2014 23:39:19 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 23:39:19 -0000 Received: by mail-pb0-f52.google.com with SMTP id uo5so2223963pbc.39 for ; Wed, 08 Jan 2014 15:39:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=QW78dQMY9E0+92ek+g3Tl1mTJoGi/LLNpupCiFFV3AM=; b=bd1jLM2pxSji/BCUDMqIGswt5P/dcb4pz8fpahWlZ8fj7uf/mZP8qvTC3WiwcSgxLE STJp8hMmbh254TpERIVMA4mcIfA02/d5STLJqIT6Di4D+CcZFmjWnCodCsH9cS6Pe4uZ xmNa/H44ngzP5c4KP6LGkMr1ASSUyo6OPQ/9R6Fqw6GMkKsMy5TDItAwWgRY7Z0sRPRN Lpw7JMt9J1LcxGco6yt5Tg241uBCU5j7VvC3PBMmm9aQTgoPFWm/uew2WKYxyVVX9fRO E+Rjml7Q1mxcwlhDfn28lacbCDvVjv7VyaHmRlUqF7jtIb8NZWp2IKKsikNpTlRc0OuH 9ORg== X-Gm-Message-State: ALoCoQkdp2/1A59c9SX7etiBbOyHXvbwjSx4oSI+xkI1wl8gLhQMwuZLA84YGzrvy0ZpAGVY9eRY X-Received: by 10.66.4.226 with SMTP id n2mr16322474pan.84.1389224357084; Wed, 08 Jan 2014 15:39:17 -0800 (PST) Received: from [10.101.99.68] ([66.151.128.105]) by mx.google.com with ESMTPSA id pa1sm6507427pac.17.2014.01.08.15.39.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 15:39:16 -0800 (PST) From: Amit More Message-Id: Date: Wed, 8 Jan 2014 15:39:14 -0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] Strange Log Entries X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I'm running XCP 1.1.0-50674c on a Dell PowerEdge 2950 server, and I'm seeing a lot of the following logs in /var/log/user.log file. Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr protect...) exitted with code 0 Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted with code 0 The first message is repeated every 15 minutes, and the second message is repeated every 90 minutes. On some research I found out that there is a cron job that executes /opt/xensource/sm/runvmpr every 15 minutes which is generating the first message. The exit status of the two scripts (/opt/xensource/sm/runvmpr, and /usr/bin/ovs-vsctl list-br) when ran manually is 0. I wonder what these log entries mean, and why the exit status 0 is recorded in the log entries. Is it something concerning or should I just ignore the errors? Any help would be greatly appreciated. Thanks in advance. Amit More _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 08 23:39:32 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 Jan 2014 23:39:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W12iX-0005rJ-Hl; Wed, 08 Jan 2014 23:39:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W12iW-0005qe-QQ for xen-api@lists.xen.org; Wed, 08 Jan 2014 23:39:20 +0000 Received: from [193.109.254.147:61008] by server-9.bemta-14.messagelabs.com id 70/57-13957-8A1EDC25; Wed, 08 Jan 2014 23:39:20 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1389224357!7427495!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10478 invoked from network); 8 Jan 2014 23:39:19 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 23:39:19 -0000 Received: by mail-pb0-f52.google.com with SMTP id uo5so2223963pbc.39 for ; Wed, 08 Jan 2014 15:39:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=QW78dQMY9E0+92ek+g3Tl1mTJoGi/LLNpupCiFFV3AM=; b=bd1jLM2pxSji/BCUDMqIGswt5P/dcb4pz8fpahWlZ8fj7uf/mZP8qvTC3WiwcSgxLE STJp8hMmbh254TpERIVMA4mcIfA02/d5STLJqIT6Di4D+CcZFmjWnCodCsH9cS6Pe4uZ xmNa/H44ngzP5c4KP6LGkMr1ASSUyo6OPQ/9R6Fqw6GMkKsMy5TDItAwWgRY7Z0sRPRN Lpw7JMt9J1LcxGco6yt5Tg241uBCU5j7VvC3PBMmm9aQTgoPFWm/uew2WKYxyVVX9fRO E+Rjml7Q1mxcwlhDfn28lacbCDvVjv7VyaHmRlUqF7jtIb8NZWp2IKKsikNpTlRc0OuH 9ORg== X-Gm-Message-State: ALoCoQkdp2/1A59c9SX7etiBbOyHXvbwjSx4oSI+xkI1wl8gLhQMwuZLA84YGzrvy0ZpAGVY9eRY X-Received: by 10.66.4.226 with SMTP id n2mr16322474pan.84.1389224357084; Wed, 08 Jan 2014 15:39:17 -0800 (PST) Received: from [10.101.99.68] ([66.151.128.105]) by mx.google.com with ESMTPSA id pa1sm6507427pac.17.2014.01.08.15.39.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 15:39:16 -0800 (PST) From: Amit More Message-Id: Date: Wed, 8 Jan 2014 15:39:14 -0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] Strange Log Entries X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I'm running XCP 1.1.0-50674c on a Dell PowerEdge 2950 server, and I'm seeing a lot of the following logs in /var/log/user.log file. Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr protect...) exitted with code 0 Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted with code 0 The first message is repeated every 15 minutes, and the second message is repeated every 90 minutes. On some research I found out that there is a cron job that executes /opt/xensource/sm/runvmpr every 15 minutes which is generating the first message. The exit status of the two scripts (/opt/xensource/sm/runvmpr, and /usr/bin/ovs-vsctl list-br) when ran manually is 0. I wonder what these log entries mean, and why the exit status 0 is recorded in the log entries. Is it something concerning or should I just ignore the errors? Any help would be greatly appreciated. Thanks in advance. Amit More _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 09 06:29:11 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 06:29:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W196v-0003CM-UD; Thu, 09 Jan 2014 06:28:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W196u-0003CH-Av for xen-api@lists.xen.org; Thu, 09 Jan 2014 06:28:56 +0000 Received: from [193.109.254.147:58861] by server-7.bemta-14.messagelabs.com id E5/30-15500-7A14EC25; Thu, 09 Jan 2014 06:28:55 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1389248933!7462538!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=1.7 required=7.0 tests=HTML_20_30,HTML_MESSAGE, IP_LINK_PLUS,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22546 invoked from network); 9 Jan 2014 06:28:54 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 06:28:54 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so2202137qcy.12 for ; Wed, 08 Jan 2014 22:28:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=WAR8if4hbAgJp/eZtKxR+RiO+UkyjTTufo9bUeIvX58=; b=ZZW7zPBfSfZSRaBmbmrTXvVyPfxsmVqKdnwmF1f3KxDz6tzMKpzwfLibnP3HbYBc4/ mW91+LhltFK5UhBAf2STe6sDZ7GO20yf6VXMbrQG5XbC8PviW8GeH/Yw+AY6i/w+bJXs MJTQUKu1YU6Ha1yHDCO4W1Xngu/v4OK9wjGCDiwZLBRpsR2wQq5ZIMIZtzAsrHzL3BjM 11uiwzOZ5znfI5wQC4WWio53ypwB9zU20vN4pk6kXBo2RbqSTc7RWj/dzz8TxnFl2pLN hFwEZ26UMtkWsIZq2s6TxzjxT3fdePPmZqJgR6ex7I7z1Z7MNihfk3l1aluDI15T1AKY FVqQ== X-Gm-Message-State: ALoCoQnqSxgg3j0vTSWQZ5qPuet64LxL/Jbync81si199B9chKZJYwwPxDf799JsaQi1svEk8sP8 MIME-Version: 1.0 X-Received: by 10.229.194.1 with SMTP id dw1mr3730325qcb.20.1389248933244; Wed, 08 Jan 2014 22:28:53 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 8 Jan 2014 22:28:53 -0800 (PST) Date: Thu, 9 Jan 2014 11:58:53 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] Snapshot Download of Slave node VMs fails . X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4726280115619232406==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4726280115619232406== Content-Type: multipart/alternative; boundary=001a11c2c7362bce1b04ef83b9e0 --001a11c2c7362bce1b04ef83b9e0 Content-Type: text/plain; charset=ISO-8859-1 Hi all , I am working on a backup solution for Xen . We use your API to create a snapshot of a VM and then we download the file using curl and the URL supplied to curl library is of the form " http://192.168.0.248/export?uuid=439997cb-19ac-5d19-90b4-ec6a7454df8f" . The download works fine except in the case of a Xen Pool configuration . That it works for The VMs of the master node . Only when snapshots of Slave nodes are encountered using the master node IP in the URL , a redirection initially takes place and then an unauthorized error is recieved . Code : curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYPEER, 0); // No Need to verify the SSL certificate curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYHOST, 0); curl_easy_setopt(curlHandle, CURLOPT_CUSTOMREQUEST, "GET"); //set method of getting values curl_easy_setopt(curlHandle, CURLOPT_URL, _urlPathName.c_str()); // Here _urlPathName=" http://192.168.0.248/export?uuid=439997cb-19ac-5d19-90b4-ec6a7454df8f" curl_easy_setopt(curlHandle, CURLOPT_VERBOSE, 0); // 1- for debug curl_easy_setopt(curlHandle, CURLOPT_USERPWD, authKey.c_str()); // set credentials curl_easy_setopt(curlHandle, CURLOPT_FOLLOWLOCATION ,true); curl_easy_setopt(curlHandle, CURLOPT_WRITEFUNCTION, ClientBackupObject::ReadAndSendData); curl_easy_setopt(curlHandle, CURLOPT_WRITEDATA, this); // fourth argument curl_easy_perform(curlHandle); Should I make any configuration changes to curl or a change to the URL ? DO you have any API calls to download the file ? please help me out on this Thanks, Shafi, Vembu Technologies. --001a11c2c7362bce1b04ef83b9e0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all ,

I am working on = a backup solution for Xen . We use your API to create a snapshot of a VM an= d then we download the file using curl and the URL supplied to curl library= is of the form=A0 "http://192.168.0.248/export?uuid=3D439997= cb-19ac-5d19-90b4-ec6a7454df8f"=A0 . The download works fine excep= t=A0 in the case of a Xen Pool configuration .

That it works for The VMs of the master node . Only when snapshot= s of Slave nodes are encountered using the master node IP in the URL , a re= direction initially takes place and then an unauthorized error=A0 is reciev= ed .

Code :
curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYPEER, 0)= ;=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // No Need to verify the SSL certificate
= =A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYHOST, 0);
=A0= =A0=A0 curl_easy_setopt(curlHandle, CURLOPT_CUSTOMREQUEST, "GET")= ;=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 //set method of getting values
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_URL, _urlPathName.c_str());= =A0=A0=A0=A0 // Here _urlPathName=3D"http://192.168.0.248/exp= ort?uuid=3D439997cb-19ac-5d19-90b4-ec6a7454df8f"
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_VERBOSE, 0);=A0=A0=A0 =A0=A0= =A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // 1- for debug
=A0=A0=A0 curl_easy_se= topt(curlHandle, CURLOPT_USERPWD, authKey.c_str());=A0=A0=A0 =A0=A0=A0 // s= et credentials
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_FOLLOWLOCA= TION ,true);
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_WRITEFUNCTION, ClientBackupO= bject::ReadAndSendData);
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_= WRITEDATA, this);=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // fourth argument=
=A0
=A0=A0 curl_easy_perform(curlHandle);
=A0=A0
=A0 Should I make any configuration changes to curl or a c= hange to the URL ? DO you have any API calls to download the file ? please = help me out on this


=A0
<= div>
Thanks,
Shafi,
Vembu Technologies.

--001a11c2c7362bce1b04ef83b9e0-- --===============4726280115619232406== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4726280115619232406==-- From xen-api-bounces@lists.xen.org Thu Jan 09 06:29:11 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 06:29:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W196v-0003CM-UD; Thu, 09 Jan 2014 06:28:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W196u-0003CH-Av for xen-api@lists.xen.org; Thu, 09 Jan 2014 06:28:56 +0000 Received: from [193.109.254.147:58861] by server-7.bemta-14.messagelabs.com id E5/30-15500-7A14EC25; Thu, 09 Jan 2014 06:28:55 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1389248933!7462538!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=1.7 required=7.0 tests=HTML_20_30,HTML_MESSAGE, IP_LINK_PLUS,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22546 invoked from network); 9 Jan 2014 06:28:54 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 06:28:54 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so2202137qcy.12 for ; Wed, 08 Jan 2014 22:28:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=WAR8if4hbAgJp/eZtKxR+RiO+UkyjTTufo9bUeIvX58=; b=ZZW7zPBfSfZSRaBmbmrTXvVyPfxsmVqKdnwmF1f3KxDz6tzMKpzwfLibnP3HbYBc4/ mW91+LhltFK5UhBAf2STe6sDZ7GO20yf6VXMbrQG5XbC8PviW8GeH/Yw+AY6i/w+bJXs MJTQUKu1YU6Ha1yHDCO4W1Xngu/v4OK9wjGCDiwZLBRpsR2wQq5ZIMIZtzAsrHzL3BjM 11uiwzOZ5znfI5wQC4WWio53ypwB9zU20vN4pk6kXBo2RbqSTc7RWj/dzz8TxnFl2pLN hFwEZ26UMtkWsIZq2s6TxzjxT3fdePPmZqJgR6ex7I7z1Z7MNihfk3l1aluDI15T1AKY FVqQ== X-Gm-Message-State: ALoCoQnqSxgg3j0vTSWQZ5qPuet64LxL/Jbync81si199B9chKZJYwwPxDf799JsaQi1svEk8sP8 MIME-Version: 1.0 X-Received: by 10.229.194.1 with SMTP id dw1mr3730325qcb.20.1389248933244; Wed, 08 Jan 2014 22:28:53 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 8 Jan 2014 22:28:53 -0800 (PST) Date: Thu, 9 Jan 2014 11:58:53 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] Snapshot Download of Slave node VMs fails . X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4726280115619232406==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4726280115619232406== Content-Type: multipart/alternative; boundary=001a11c2c7362bce1b04ef83b9e0 --001a11c2c7362bce1b04ef83b9e0 Content-Type: text/plain; charset=ISO-8859-1 Hi all , I am working on a backup solution for Xen . We use your API to create a snapshot of a VM and then we download the file using curl and the URL supplied to curl library is of the form " http://192.168.0.248/export?uuid=439997cb-19ac-5d19-90b4-ec6a7454df8f" . The download works fine except in the case of a Xen Pool configuration . That it works for The VMs of the master node . Only when snapshots of Slave nodes are encountered using the master node IP in the URL , a redirection initially takes place and then an unauthorized error is recieved . Code : curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYPEER, 0); // No Need to verify the SSL certificate curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYHOST, 0); curl_easy_setopt(curlHandle, CURLOPT_CUSTOMREQUEST, "GET"); //set method of getting values curl_easy_setopt(curlHandle, CURLOPT_URL, _urlPathName.c_str()); // Here _urlPathName=" http://192.168.0.248/export?uuid=439997cb-19ac-5d19-90b4-ec6a7454df8f" curl_easy_setopt(curlHandle, CURLOPT_VERBOSE, 0); // 1- for debug curl_easy_setopt(curlHandle, CURLOPT_USERPWD, authKey.c_str()); // set credentials curl_easy_setopt(curlHandle, CURLOPT_FOLLOWLOCATION ,true); curl_easy_setopt(curlHandle, CURLOPT_WRITEFUNCTION, ClientBackupObject::ReadAndSendData); curl_easy_setopt(curlHandle, CURLOPT_WRITEDATA, this); // fourth argument curl_easy_perform(curlHandle); Should I make any configuration changes to curl or a change to the URL ? DO you have any API calls to download the file ? please help me out on this Thanks, Shafi, Vembu Technologies. --001a11c2c7362bce1b04ef83b9e0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all ,

I am working on = a backup solution for Xen . We use your API to create a snapshot of a VM an= d then we download the file using curl and the URL supplied to curl library= is of the form=A0 "http://192.168.0.248/export?uuid=3D439997= cb-19ac-5d19-90b4-ec6a7454df8f"=A0 . The download works fine excep= t=A0 in the case of a Xen Pool configuration .

That it works for The VMs of the master node . Only when snapshot= s of Slave nodes are encountered using the master node IP in the URL , a re= direction initially takes place and then an unauthorized error=A0 is reciev= ed .

Code :
curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYPEER, 0)= ;=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // No Need to verify the SSL certificate
= =A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYHOST, 0);
=A0= =A0=A0 curl_easy_setopt(curlHandle, CURLOPT_CUSTOMREQUEST, "GET")= ;=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 //set method of getting values
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_URL, _urlPathName.c_str());= =A0=A0=A0=A0 // Here _urlPathName=3D"http://192.168.0.248/exp= ort?uuid=3D439997cb-19ac-5d19-90b4-ec6a7454df8f"
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_VERBOSE, 0);=A0=A0=A0 =A0=A0= =A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // 1- for debug
=A0=A0=A0 curl_easy_se= topt(curlHandle, CURLOPT_USERPWD, authKey.c_str());=A0=A0=A0 =A0=A0=A0 // s= et credentials
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_FOLLOWLOCA= TION ,true);
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_WRITEFUNCTION, ClientBackupO= bject::ReadAndSendData);
=A0=A0=A0 curl_easy_setopt(curlHandle, CURLOPT_= WRITEDATA, this);=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 // fourth argument=
=A0
=A0=A0 curl_easy_perform(curlHandle);
=A0=A0
=A0 Should I make any configuration changes to curl or a c= hange to the URL ? DO you have any API calls to download the file ? please = help me out on this


=A0
<= div>
Thanks,
Shafi,
Vembu Technologies.

--001a11c2c7362bce1b04ef83b9e0-- --===============4726280115619232406== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4726280115619232406==-- From xen-api-bounces@lists.xen.org Thu Jan 09 13:42:15 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 13:42:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Fs6-00066o-7H; Thu, 09 Jan 2014 13:42:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W1Fs5-00066i-5U for xen-api@lists.xensource.com; Thu, 09 Jan 2014 13:42:05 +0000 Received: from [193.109.254.147:15455] by server-9.bemta-14.messagelabs.com id 05/00-13957-C27AEC25; Thu, 09 Jan 2014 13:42:04 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1389274923!9828430!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21603 invoked from network); 9 Jan 2014 13:42:03 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 13:42:03 -0000 Received: by mail-wi0-f180.google.com with SMTP id hm19so3475266wib.1 for ; Thu, 09 Jan 2014 05:42:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CLMZtH7AhmolxfmKP7VCPLyFWTd9ErkqkupjipX2zqc=; b=wM2Ovmvs5/LNCo+BMWiQgJqGRo428JlwgjzBkzM20b2PW09xV94QkY2f2yj7dzbBgh nmNli94Hiht47b05qswPaYxTFIUtw4u5Z/mK9+x7UAfMardnbkUyTISOEL+0+xYIVTWZ YoyyF9dAY6RuHoVMUnTmwe0V88lDHkzxoHv0Vq5TS24L9Fb2DOd85ZXKnTCwKbKcgjZS 209aQ/klzaoM8Ob8isC4SzKlwuXrjxDCgbD3Tj2IQwitXJdkc/kyU98lMgUVZkQaRN2r sCMQjYIj2ShBa+TJkFmXMyDNbmTmgDy79D6WK+kiZ639PVZOpfueMFaSpM4kVEX63S53 Kl6A== MIME-Version: 1.0 X-Received: by 10.180.108.132 with SMTP id hk4mr3472854wib.12.1389274923274; Thu, 09 Jan 2014 05:42:03 -0800 (PST) Received: by 10.216.45.147 with HTTP; Thu, 9 Jan 2014 05:42:03 -0800 (PST) In-Reply-To: <52CCAB19.9090200@citrix.com> References: <52CCAB19.9090200@citrix.com> Date: Thu, 9 Jan 2014 19:12:03 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: Andrew Cooper Cc: xs-devel@lists.xenserver.org, "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [xs-devel] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4260608210481321679==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4260608210481321679== Content-Type: multipart/alternative; boundary=e89a8f3baad54c160904ef89c61b --e89a8f3baad54c160904ef89c61b Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 8, 2014 at 7:04 AM, Andrew Cooper wrote: > On 07/01/2014 20:27, Rishi wrote: > > Hello List, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? > > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? > > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? > > > > Regards, > Rishi > > > In general, the tools from older versions of XenServer(/XCP) should work > with newer versions of XenServer(/XenServer-Core), but you are advised to > update. (We make no explicit guarantee that they will work, but we do do > our best not to break things.) > > The Linux tools don't really change too much from release to release, but > the Windows tools do change quite substantially. > Thanks Andrew, so since Xenserver6.2 is released, is it good that the tools should be upgraded to latest 6.2 for Windows irrespective of underlying XCP/Xenserver version ? Is there a known/published method for mass upgrade ? I saw an experimental script in XS6.2 to do this. We are currently benchmarking XenServer6.2 tools on XCP1.1 / XCP1.6 and Xenserver 6.2. Will share the result if it creates some value. Sorry Andrew to hit reply to you instead reply all :( > > ~Andrew > --e89a8f3baad54c160904ef89c61b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Wed, Jan 8, 2014 at 7:04 AM, Andrew Cooper <= ;andrew.coop= er3@citrix.com> wrote:
=20 =20 =20
On 07/01/2014 20:27, Rishi wrote:
=20
Hello List,

I have few questions about XenTools

Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ?

How does one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?

Are there any logs inside VM/Host about tools driver errors to look in case of problems ?



Regards,
Rishi

In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update.=A0 (We make no explicit guarantee that they will work, but we do do our best not to break things.)

The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially.
Thanks Andrew, so since Xenserver6.2 is released, is it good that=20 the=A0 tools should be upgraded to latest 6.2 for Windows irrespective of= =20 underlying XCP/Xenserver version ?

Is there a=A0 known/published method for mass upgrade ? I sa= w an experimental script in XS6.2 to do this.

We are currently benchmarking XenServer6.2 tools on XCP1.1 / XCP1.6 and=20 Xenserver 6.2. Will share the result if it creates some value.

Sorry Andrew to hit reply to you instead reply all :(
= =A0

~Andrew

--e89a8f3baad54c160904ef89c61b-- --===============4260608210481321679== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4260608210481321679==-- From xen-api-bounces@lists.xen.org Thu Jan 09 13:42:15 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 13:42:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Fs6-00066o-7H; Thu, 09 Jan 2014 13:42:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W1Fs5-00066i-5U for xen-api@lists.xensource.com; Thu, 09 Jan 2014 13:42:05 +0000 Received: from [193.109.254.147:15455] by server-9.bemta-14.messagelabs.com id 05/00-13957-C27AEC25; Thu, 09 Jan 2014 13:42:04 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1389274923!9828430!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21603 invoked from network); 9 Jan 2014 13:42:03 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 13:42:03 -0000 Received: by mail-wi0-f180.google.com with SMTP id hm19so3475266wib.1 for ; Thu, 09 Jan 2014 05:42:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CLMZtH7AhmolxfmKP7VCPLyFWTd9ErkqkupjipX2zqc=; b=wM2Ovmvs5/LNCo+BMWiQgJqGRo428JlwgjzBkzM20b2PW09xV94QkY2f2yj7dzbBgh nmNli94Hiht47b05qswPaYxTFIUtw4u5Z/mK9+x7UAfMardnbkUyTISOEL+0+xYIVTWZ YoyyF9dAY6RuHoVMUnTmwe0V88lDHkzxoHv0Vq5TS24L9Fb2DOd85ZXKnTCwKbKcgjZS 209aQ/klzaoM8Ob8isC4SzKlwuXrjxDCgbD3Tj2IQwitXJdkc/kyU98lMgUVZkQaRN2r sCMQjYIj2ShBa+TJkFmXMyDNbmTmgDy79D6WK+kiZ639PVZOpfueMFaSpM4kVEX63S53 Kl6A== MIME-Version: 1.0 X-Received: by 10.180.108.132 with SMTP id hk4mr3472854wib.12.1389274923274; Thu, 09 Jan 2014 05:42:03 -0800 (PST) Received: by 10.216.45.147 with HTTP; Thu, 9 Jan 2014 05:42:03 -0800 (PST) In-Reply-To: <52CCAB19.9090200@citrix.com> References: <52CCAB19.9090200@citrix.com> Date: Thu, 9 Jan 2014 19:12:03 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: Andrew Cooper Cc: xs-devel@lists.xenserver.org, "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [xs-devel] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4260608210481321679==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4260608210481321679== Content-Type: multipart/alternative; boundary=e89a8f3baad54c160904ef89c61b --e89a8f3baad54c160904ef89c61b Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 8, 2014 at 7:04 AM, Andrew Cooper wrote: > On 07/01/2014 20:27, Rishi wrote: > > Hello List, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? > > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? > > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? > > > > Regards, > Rishi > > > In general, the tools from older versions of XenServer(/XCP) should work > with newer versions of XenServer(/XenServer-Core), but you are advised to > update. (We make no explicit guarantee that they will work, but we do do > our best not to break things.) > > The Linux tools don't really change too much from release to release, but > the Windows tools do change quite substantially. > Thanks Andrew, so since Xenserver6.2 is released, is it good that the tools should be upgraded to latest 6.2 for Windows irrespective of underlying XCP/Xenserver version ? Is there a known/published method for mass upgrade ? I saw an experimental script in XS6.2 to do this. We are currently benchmarking XenServer6.2 tools on XCP1.1 / XCP1.6 and Xenserver 6.2. Will share the result if it creates some value. Sorry Andrew to hit reply to you instead reply all :( > > ~Andrew > --e89a8f3baad54c160904ef89c61b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Wed, Jan 8, 2014 at 7:04 AM, Andrew Cooper <= ;andrew.coop= er3@citrix.com> wrote:
=20 =20 =20
On 07/01/2014 20:27, Rishi wrote:
=20
Hello List,

I have few questions about XenTools

Is it compulsory to update tools of Linux/Windows VMs if the XenServer is upgraded ?

How does one handles mass tools update after the xen upgrade ?
e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ?

Are the tools interoperable ? Will VMs with tools from XCP1.1 work on XCP1.6 and so on ?

Are there any logs inside VM/Host about tools driver errors to look in case of problems ?



Regards,
Rishi

In general, the tools from older versions of XenServer(/XCP) should work with newer versions of XenServer(/XenServer-Core), but you are advised to update.=A0 (We make no explicit guarantee that they will work, but we do do our best not to break things.)

The Linux tools don't really change too much from release to release, but the Windows tools do change quite substantially.
Thanks Andrew, so since Xenserver6.2 is released, is it good that=20 the=A0 tools should be upgraded to latest 6.2 for Windows irrespective of= =20 underlying XCP/Xenserver version ?

Is there a=A0 known/published method for mass upgrade ? I sa= w an experimental script in XS6.2 to do this.

We are currently benchmarking XenServer6.2 tools on XCP1.1 / XCP1.6 and=20 Xenserver 6.2. Will share the result if it creates some value.

Sorry Andrew to hit reply to you instead reply all :(
= =A0

~Andrew

--e89a8f3baad54c160904ef89c61b-- --===============4260608210481321679== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4260608210481321679==-- From xen-api-bounces@lists.xen.org Thu Jan 09 15:24:41 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 15:24:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1HTC-0006Ts-E8; Thu, 09 Jan 2014 15:24:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1HTB-0006Tn-Uw for xen-api@lists.xensource.com; Thu, 09 Jan 2014 15:24:30 +0000 Received: from [85.158.137.68:60656] by server-12.bemta-3.messagelabs.com id D5/6C-20055-D2FBEC25; Thu, 09 Jan 2014 15:24:29 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1389281067!8153253!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27971 invoked from network); 9 Jan 2014 15:24:28 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-14.tower-31.messagelabs.com with SMTP; 9 Jan 2014 15:24:28 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d42 with ME id BrQR1n00A3zjds103rQRmp; Thu, 09 Jan 2014 16:24:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4447C161D78; Thu, 9 Jan 2014 16:24:25 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3g3YRpaVDajK; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CAFCF162063; Thu, 9 Jan 2014 16:24:22 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id e_imCMnyKaFb; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8EA32161D78; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Message-ID: <52CEBF26.6080102@tranquil-it-systems.fr> Date: Thu, 09 Jan 2014 16:24:22 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Rishi <2rushikeshj@gmail.com> References: In-Reply-To: Cc: xs-devel@lists.xenserver.org, "xen-api@lists.xensource.com" Subject: Re: [Xen-API] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Rishi, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? for linux VM, I never had issue even if pv driver are well out of = datedate. However for Windows I had a few win2k3 vm crash after = migrating from XCP1.1 to XCP1.6 where the driver was not yet updated = (different vms on different xen servers with different applicative = workload) . So I'd say it is better to update, even if in most case it = is not technically necessary. > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? it is not yet a big enough PITA for us, so we have not yet automated the = process. However we are using a WAPT = (http://dev.tranquil.it/index.php/WAPT_-_apt-get_pour_Windows , sorry = French only..., disclaimer : I work on that GPL project) for similar = windows automation stuff, so we may use it one day for that purpose. > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? cf above, mostly working, but beware. > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? I don't know about this one, when we had issue with the win2k3 virtual = machines, we had BSOD, so not much debug to gather unless you enable = serial console I guess. Cheers, Denis > > > > Regards, > Rishi > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 09 15:24:41 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 15:24:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1HTC-0006Ts-E8; Thu, 09 Jan 2014 15:24:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1HTB-0006Tn-Uw for xen-api@lists.xensource.com; Thu, 09 Jan 2014 15:24:30 +0000 Received: from [85.158.137.68:60656] by server-12.bemta-3.messagelabs.com id D5/6C-20055-D2FBEC25; Thu, 09 Jan 2014 15:24:29 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1389281067!8153253!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27971 invoked from network); 9 Jan 2014 15:24:28 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-14.tower-31.messagelabs.com with SMTP; 9 Jan 2014 15:24:28 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d42 with ME id BrQR1n00A3zjds103rQRmp; Thu, 09 Jan 2014 16:24:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4447C161D78; Thu, 9 Jan 2014 16:24:25 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3g3YRpaVDajK; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CAFCF162063; Thu, 9 Jan 2014 16:24:22 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id e_imCMnyKaFb; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8EA32161D78; Thu, 9 Jan 2014 16:24:22 +0100 (CET) Message-ID: <52CEBF26.6080102@tranquil-it-systems.fr> Date: Thu, 09 Jan 2014 16:24:22 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Rishi <2rushikeshj@gmail.com> References: In-Reply-To: Cc: xs-devel@lists.xenserver.org, "xen-api@lists.xensource.com" Subject: Re: [Xen-API] Question about XenTools in Mass environment X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Rishi, > > I have few questions about XenTools > > Is it compulsory to update tools of Linux/Windows VMs if the XenServer > is upgraded ? for linux VM, I never had issue even if pv driver are well out of = datedate. However for Windows I had a few win2k3 vm crash after = migrating from XCP1.1 to XCP1.6 where the driver was not yet updated = (different vms on different xen servers with different applicative = workload) . So I'd say it is better to update, even if in most case it = is not technically necessary. > How does one handles mass tools update after the xen upgrade ? > e.g XCP1.1 to XCP1.6 or XCP1.6 to XS6.2 ? it is not yet a big enough PITA for us, so we have not yet automated the = process. However we are using a WAPT = (http://dev.tranquil.it/index.php/WAPT_-_apt-get_pour_Windows , sorry = French only..., disclaimer : I work on that GPL project) for similar = windows automation stuff, so we may use it one day for that purpose. > Are the tools interoperable ? Will VMs with tools from XCP1.1 work on > XCP1.6 and so on ? cf above, mostly working, but beware. > > Are there any logs inside VM/Host about tools driver errors to look in > case of problems ? I don't know about this one, when we had issue with the win2k3 virtual = machines, we had BSOD, so not much debug to gather unless you enable = serial console I guess. Cheers, Denis > > > > Regards, > Rishi > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 09 17:56:00 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 17:56:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Jpf-0004yy-PH; Thu, 09 Jan 2014 17:55:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Jpf-0004yj-19 for xen-api@lists.xen.org; Thu, 09 Jan 2014 17:55:51 +0000 Received: from [85.158.139.211:20672] by server-1.bemta-5.messagelabs.com id 37/B1-21065-6A2EEC25; Thu, 09 Jan 2014 17:55:50 +0000 X-Env-Sender: ADanso@infolocktech.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1389290148!8854709!1 X-Originating-IP: [206.225.166.166] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA2LjIyNS4xNjYuMTY2ID0+IDEyNzcx\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18711 invoked from network); 9 Jan 2014 17:55:49 -0000 Received: from hub026-nj-3.exch026.serverdata.net (HELO hub026-NJ-3.exch026.serverdata.net) (206.225.166.166) by server-12.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 17:55:49 -0000 Received: from MBX026-E1-NJ-4.exch026.domain.local ([10.240.14.54]) by HUB026-NJ-3.exch026.domain.local ([10.240.14.36]) with mapi id 14.03.0158.001; Thu, 9 Jan 2014 09:55:48 -0800 From: "Agyeman B. Danso Jr." To: "xen-api@lists.xen.org" Thread-Topic: Help Hypervisor VM IP reconfig Thread-Index: Ac8NZATC/HqslTFTRqqxb0TIBoYjQA== Date: Thu, 9 Jan 2014 17:55:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.79.175.105] MIME-Version: 1.0 Subject: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7520384959022905621==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7520384959022905621== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_" --_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi XAPI team, Can you help me with the command to change ip address of a vm while on hype= rvisor? In my case if access to xen center is disabled and a user changes the ipadd= ress of a vm and no longer can ssh to the vm, I would like to be able to re= set the ip address, netmask, and gateway from the hypervisor. The command below shows me network info but how to I change that network in= fo? xe vm-list params=3Dname-label,networks Thank you, Agyeman B. Danso Jr. Security Engineer infoLock Technologies 877.610.5625 x253 - direct ADanso@infolocktech.com --_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi XAPI team,

 

Can you help me with the command to change ip addres= s of a vm while on hypervisor?

In my case if access to xen center is disabled and a= user changes the ipaddress of a vm and no longer can ssh to the vm, I woul= d like to be able to reset the ip address, netmask, and gateway from the hy= pervisor.

 

The command below shows me network info but how to I= change that network info?

xe vm-list params=3Dname-= label,networks

 

 

Thank you,

Agyeman B. Danso Jr.

Security Engineer=

infoLock Technologies

877.610.5625 x253 - direct ADanso@infolocktech.com=

 

--_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_-- --===============7520384959022905621== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7520384959022905621==-- From xen-api-bounces@lists.xen.org Thu Jan 09 17:56:00 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 17:56:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Jpf-0004yy-PH; Thu, 09 Jan 2014 17:55:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Jpf-0004yj-19 for xen-api@lists.xen.org; Thu, 09 Jan 2014 17:55:51 +0000 Received: from [85.158.139.211:20672] by server-1.bemta-5.messagelabs.com id 37/B1-21065-6A2EEC25; Thu, 09 Jan 2014 17:55:50 +0000 X-Env-Sender: ADanso@infolocktech.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1389290148!8854709!1 X-Originating-IP: [206.225.166.166] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA2LjIyNS4xNjYuMTY2ID0+IDEyNzcx\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18711 invoked from network); 9 Jan 2014 17:55:49 -0000 Received: from hub026-nj-3.exch026.serverdata.net (HELO hub026-NJ-3.exch026.serverdata.net) (206.225.166.166) by server-12.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 17:55:49 -0000 Received: from MBX026-E1-NJ-4.exch026.domain.local ([10.240.14.54]) by HUB026-NJ-3.exch026.domain.local ([10.240.14.36]) with mapi id 14.03.0158.001; Thu, 9 Jan 2014 09:55:48 -0800 From: "Agyeman B. Danso Jr." To: "xen-api@lists.xen.org" Thread-Topic: Help Hypervisor VM IP reconfig Thread-Index: Ac8NZATC/HqslTFTRqqxb0TIBoYjQA== Date: Thu, 9 Jan 2014 17:55:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.79.175.105] MIME-Version: 1.0 Subject: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7520384959022905621==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7520384959022905621== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_" --_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi XAPI team, Can you help me with the command to change ip address of a vm while on hype= rvisor? In my case if access to xen center is disabled and a user changes the ipadd= ress of a vm and no longer can ssh to the vm, I would like to be able to re= set the ip address, netmask, and gateway from the hypervisor. The command below shows me network info but how to I change that network in= fo? xe vm-list params=3Dname-label,networks Thank you, Agyeman B. Danso Jr. Security Engineer infoLock Technologies 877.610.5625 x253 - direct ADanso@infolocktech.com --_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi XAPI team,

 

Can you help me with the command to change ip addres= s of a vm while on hypervisor?

In my case if access to xen center is disabled and a= user changes the ipaddress of a vm and no longer can ssh to the vm, I woul= d like to be able to reset the ip address, netmask, and gateway from the hy= pervisor.

 

The command below shows me network info but how to I= change that network info?

xe vm-list params=3Dname-= label,networks

 

 

Thank you,

Agyeman B. Danso Jr.

Security Engineer=

infoLock Technologies

877.610.5625 x253 - direct ADanso@infolocktech.com=

 

--_000_A83030E68B23D543AE9E11F3B53EBD7608C75ED0mbx026e1nj4exch_-- --===============7520384959022905621== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7520384959022905621==-- From xen-api-bounces@lists.xen.org Thu Jan 09 20:07:17 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 20:07:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Lsi-0000MB-MO; Thu, 09 Jan 2014 20:07:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Lsg-0000M1-Tc for xen-api@lists.xen.org; Thu, 09 Jan 2014 20:07:07 +0000 Received: from [85.158.139.211:42793] by server-12.bemta-5.messagelabs.com id FA/48-30017-A610FC25; Thu, 09 Jan 2014 20:07:06 +0000 X-Env-Sender: q@phosph.re X-Msg-Ref: server-8.tower-206.messagelabs.com!1389298025!8837966!1 X-Originating-IP: [79.170.44.53] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzkuMTcwLjQ0LjUzID0+IDY5ODE0\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31693 invoked from network); 9 Jan 2014 20:07:05 -0000 Received: from mail53.extendcp.co.uk (HELO mail53.extendcp.co.uk) (79.170.44.53) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jan 2014 20:07:05 -0000 Received: from host109-151-220-140.range109-151.btcentralplus.com ([109.151.220.140] helo=[192.168.69.101]) by mail53.extendcp.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) id 1W1Lsd-0007FO-Ux; Thu, 09 Jan 2014 20:07:04 +0000 Mime-Version: 1.0 (Apple Message framework v1283) From: Mark Lewis In-Reply-To: Date: Thu, 9 Jan 2014 20:07:03 +0000 Message-Id: <51A56300-9928-4CDC-AFFC-7482B82EBD95@phosph.re> References: To: "Agyeman B. Danso Jr." X-Mailer: Apple Mail (2.1283) X-Authenticated-As: q@phosph.re Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2632720141844459893==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2632720141844459893== Content-Type: multipart/alternative; boundary="Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433" --Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii +1. I would like to find the reverse - I would like to be locked out of mine = so only the person with the root password of the VM would be able to = access the command line etc in there. Mark -- phosph.re On 2014 Jan 9, at 17:55, Agyeman B. Danso Jr. wrote: > Hi XAPI team, > =20 > Can you help me with the command to change ip address of a vm while on = hypervisor? > In my case if access to xen center is disabled and a user changes the = ipaddress of a vm and no longer can ssh to the vm, I would like to be = able to reset the ip address, netmask, and gateway from the hypervisor. > =20 > The command below shows me network info but how to I change that = network info? > xe vm-list params=3Dname-label,networks > =20 > =20 > Thank you, > Agyeman B. Danso Jr. > Security Engineer > infoLock Technologies > 877.610.5625 x253 - direct > ADanso@infolocktech.com > =20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii +1.
I would like to find the reverse - I would = like to be locked out of mine so only the person with the root password = of the VM would be able to access the command line etc in = there.
Mark

On 2014 Jan 9, at 17:55, Agyeman B. Danso Jr. = wrote:

Hi XAPI team,
Can you help me with the command to = change ip address of a vm while on hypervisor?
In my case if access to xen center is disabled and a user = changes the ipaddress of a vm and no longer can ssh to the vm, I would = like to be able to reset the ip address, netmask, and gateway from the = hypervisor.
 
The command below shows me network info but how to I = change that network info?
xe vm-list = params=3Dname-label,networks
 
 
Thank you,
Agyeman B. Danso = Jr.
Security = Engineer
infoLock = Technologies
877.610.5625 x253 = - direct
 Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 20:07:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Lsi-0000MB-MO; Thu, 09 Jan 2014 20:07:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Lsg-0000M1-Tc for xen-api@lists.xen.org; Thu, 09 Jan 2014 20:07:07 +0000 Received: from [85.158.139.211:42793] by server-12.bemta-5.messagelabs.com id FA/48-30017-A610FC25; Thu, 09 Jan 2014 20:07:06 +0000 X-Env-Sender: q@phosph.re X-Msg-Ref: server-8.tower-206.messagelabs.com!1389298025!8837966!1 X-Originating-IP: [79.170.44.53] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzkuMTcwLjQ0LjUzID0+IDY5ODE0\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31693 invoked from network); 9 Jan 2014 20:07:05 -0000 Received: from mail53.extendcp.co.uk (HELO mail53.extendcp.co.uk) (79.170.44.53) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jan 2014 20:07:05 -0000 Received: from host109-151-220-140.range109-151.btcentralplus.com ([109.151.220.140] helo=[192.168.69.101]) by mail53.extendcp.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) id 1W1Lsd-0007FO-Ux; Thu, 09 Jan 2014 20:07:04 +0000 Mime-Version: 1.0 (Apple Message framework v1283) From: Mark Lewis In-Reply-To: Date: Thu, 9 Jan 2014 20:07:03 +0000 Message-Id: <51A56300-9928-4CDC-AFFC-7482B82EBD95@phosph.re> References: To: "Agyeman B. Danso Jr." X-Mailer: Apple Mail (2.1283) X-Authenticated-As: q@phosph.re Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2632720141844459893==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2632720141844459893== Content-Type: multipart/alternative; boundary="Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433" --Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii +1. I would like to find the reverse - I would like to be locked out of mine = so only the person with the root password of the VM would be able to = access the command line etc in there. Mark -- phosph.re On 2014 Jan 9, at 17:55, Agyeman B. Danso Jr. wrote: > Hi XAPI team, > =20 > Can you help me with the command to change ip address of a vm while on = hypervisor? > In my case if access to xen center is disabled and a user changes the = ipaddress of a vm and no longer can ssh to the vm, I would like to be = able to reset the ip address, netmask, and gateway from the hypervisor. > =20 > The command below shows me network info but how to I change that = network info? > xe vm-list params=3Dname-label,networks > =20 > =20 > Thank you, > Agyeman B. Danso Jr. > Security Engineer > infoLock Technologies > 877.610.5625 x253 - direct > ADanso@infolocktech.com > =20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_651497F9-E55F-4FF6-A304-F78EB937E433 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii +1.
I would like to find the reverse - I would = like to be locked out of mine so only the person with the root password = of the VM would be able to access the command line etc in = there.
Mark

On 2014 Jan 9, at 17:55, Agyeman B. Danso Jr. = wrote:

Hi XAPI team,
Can you help me with the command to = change ip address of a vm while on hypervisor?
In my case if access to xen center is disabled and a user = changes the ipaddress of a vm and no longer can ssh to the vm, I would = like to be able to reset the ip address, netmask, and gateway from the = hypervisor.
 
The command below shows me network info but how to I = change that network info?
xe vm-list = params=3Dname-label,networks
 
 
Thank you,
Agyeman B. Danso = Jr.
Security = Engineer
infoLock = Technologies
877.610.5625 x253 = - direct
 Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 21:17:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1MyN-0005Ct-DZ; Thu, 09 Jan 2014 21:17:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1MkC-0004UJ-W9 for xen-api@lists.xen.org; Thu, 09 Jan 2014 21:02:25 +0000 Received: from [85.158.143.35:55272] by server-2.bemta-4.messagelabs.com id 7E/50-11386-06E0FC25; Thu, 09 Jan 2014 21:02:24 +0000 X-Env-Sender: schakrava@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1389301342!10805313!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17967 invoked from network); 9 Jan 2014 21:02:23 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 21:02:23 -0000 Received: by mail-qa0-f44.google.com with SMTP id o15so3343448qap.3 for ; Thu, 09 Jan 2014 13:02:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rVn7sxOxjjO1o9hCXQ8FpSWf+obpQrZcUHb1IIl4vow=; b=h9ksUxWO4XF08KPrlHTvB8MRqqwSzUZP3NOrPa/2Vx0qzHmGW2O5s8Pvxh+mbpHcEZ f7++rnIxodI8gsPLVVj5A+6p46v/Csb4EdUe03e4DlkWdQk+SnxIoSLJra7ktRNyRy0u wvdLryqIcDoGdJupuCYNKrss9i9kv5t6IX2M7Jp03fp77ooZItR6HcM6pGbtnbxteiWG PTmcxI9at7jKMMSUfxahc+8RUz0IFgTnPOvFTZFnCv5vF6vfqVi6z9Q45bIRCTK6m4JA xm8AvbDFKPriSWrOQK+i/46ZXQVsBmWRObimiKlsiVoiJboUpfGJ82OMnZDtZvBuFOke XN/A== MIME-Version: 1.0 X-Received: by 10.49.101.9 with SMTP id fc9mr11958487qeb.42.1389301342368; Thu, 09 Jan 2014 13:02:22 -0800 (PST) Received: by 10.224.59.201 with HTTP; Thu, 9 Jan 2014 13:02:22 -0800 (PST) Date: Thu, 9 Jan 2014 13:02:22 -0800 Message-ID: From: Suman C To: xen-api@lists.xen.org X-Mailman-Approved-At: Thu, 09 Jan 2014 21:17:00 +0000 Subject: [Xen-API] Number of hosts limit per resource pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2268789385212971011==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2268789385212971011== Content-Type: multipart/alternative; boundary=001a11c2bd38ff955904ef8fec25 --001a11c2bd38ff955904ef8fec25 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to 6.2. One of the configuration limits is 16 hosts per resource pool. I don't have more than 16 hosts to test right away, so I am asking. Is this limit enforced by the code? Or is it a matter of supportability from Citrix? It would be greatly helpful to know among the list of configuration limits, which ones are enforced by the code and why. Can someone address these questions? Thanks Suman --001a11c2bd38ff955904ef8fec25 Content-Type: text/html; charset=ISO-8859-1
Hi,

I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to 6.2.

One of the configuration limits is 16 hosts per resource pool. I don't have more than 16 hosts to test right away, so I am asking. Is this limit enforced by the code? Or is it a matter of supportability from Citrix?

It would be greatly helpful to know among the list of configuration limits, which ones are enforced by the code and why. Can someone address these questions?

Thanks
Suman
--001a11c2bd38ff955904ef8fec25-- --===============2268789385212971011== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2268789385212971011==-- From xen-api-bounces@lists.xen.org Thu Jan 09 21:17:18 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 Jan 2014 21:17:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1MyN-0005Ct-DZ; Thu, 09 Jan 2014 21:17:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1MkC-0004UJ-W9 for xen-api@lists.xen.org; Thu, 09 Jan 2014 21:02:25 +0000 Received: from [85.158.143.35:55272] by server-2.bemta-4.messagelabs.com id 7E/50-11386-06E0FC25; Thu, 09 Jan 2014 21:02:24 +0000 X-Env-Sender: schakrava@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1389301342!10805313!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17967 invoked from network); 9 Jan 2014 21:02:23 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 21:02:23 -0000 Received: by mail-qa0-f44.google.com with SMTP id o15so3343448qap.3 for ; Thu, 09 Jan 2014 13:02:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rVn7sxOxjjO1o9hCXQ8FpSWf+obpQrZcUHb1IIl4vow=; b=h9ksUxWO4XF08KPrlHTvB8MRqqwSzUZP3NOrPa/2Vx0qzHmGW2O5s8Pvxh+mbpHcEZ f7++rnIxodI8gsPLVVj5A+6p46v/Csb4EdUe03e4DlkWdQk+SnxIoSLJra7ktRNyRy0u wvdLryqIcDoGdJupuCYNKrss9i9kv5t6IX2M7Jp03fp77ooZItR6HcM6pGbtnbxteiWG PTmcxI9at7jKMMSUfxahc+8RUz0IFgTnPOvFTZFnCv5vF6vfqVi6z9Q45bIRCTK6m4JA xm8AvbDFKPriSWrOQK+i/46ZXQVsBmWRObimiKlsiVoiJboUpfGJ82OMnZDtZvBuFOke XN/A== MIME-Version: 1.0 X-Received: by 10.49.101.9 with SMTP id fc9mr11958487qeb.42.1389301342368; Thu, 09 Jan 2014 13:02:22 -0800 (PST) Received: by 10.224.59.201 with HTTP; Thu, 9 Jan 2014 13:02:22 -0800 (PST) Date: Thu, 9 Jan 2014 13:02:22 -0800 Message-ID: From: Suman C To: xen-api@lists.xen.org X-Mailman-Approved-At: Thu, 09 Jan 2014 21:17:00 +0000 Subject: [Xen-API] Number of hosts limit per resource pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2268789385212971011==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2268789385212971011== Content-Type: multipart/alternative; boundary=001a11c2bd38ff955904ef8fec25 --001a11c2bd38ff955904ef8fec25 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to 6.2. One of the configuration limits is 16 hosts per resource pool. I don't have more than 16 hosts to test right away, so I am asking. Is this limit enforced by the code? Or is it a matter of supportability from Citrix? It would be greatly helpful to know among the list of configuration limits, which ones are enforced by the code and why. Can someone address these questions? Thanks Suman --001a11c2bd38ff955904ef8fec25 Content-Type: text/html; charset=ISO-8859-1
Hi,

I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to 6.2.

One of the configuration limits is 16 hosts per resource pool. I don't have more than 16 hosts to test right away, so I am asking. Is this limit enforced by the code? Or is it a matter of supportability from Citrix?

It would be greatly helpful to know among the list of configuration limits, which ones are enforced by the code and why. Can someone address these questions?

Thanks
Suman
--001a11c2bd38ff955904ef8fec25-- --===============2268789385212971011== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2268789385212971011==-- From xen-api-bounces@lists.xen.org Fri Jan 10 08:40:55 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 08:40:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Xe0-0005fW-Bw; Fri, 10 Jan 2014 08:40:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Xdx-0005fP-If for xen-api@lists.xensource.com; Fri, 10 Jan 2014 08:40:41 +0000 Received: from [85.158.139.211:44664] by server-9.bemta-5.messagelabs.com id A4/8D-15098-802BFC25; Fri, 10 Jan 2014 08:40:40 +0000 X-Env-Sender: castrillo@sarenet.es X-Msg-Ref: server-14.tower-206.messagelabs.com!1389343239!8908169!1 X-Originating-IP: [195.16.151.151] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24204 invoked from network); 10 Jan 2014 08:40:39 -0000 Received: from cu01176b.smtpx.saremail.com (HELO cu01176b.smtpx.saremail.com) (195.16.151.151) by server-14.tower-206.messagelabs.com with SMTP; 10 Jan 2014 08:40:39 -0000 Received: from [172.16.1.220] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPA id 0D21D9DC583 for ; Fri, 10 Jan 2014 09:40:36 +0100 (CET) From: Alberto Castrillo Date: Fri, 10 Jan 2014 09:40:36 +0100 Message-Id: <874F9063-EB8C-4C83-945A-583D9D3C3539@sarenet.es> To: xen-api@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Subject: [Xen-API] Backup of NFS Storage X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8695738177708114830==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8695738177708114830== Content-Type: multipart/alternative; boundary=Apple-Mail-679-866659732 --Apple-Mail-679-866659732 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi All We are running several pools with XCP 1.6 and XS 6.2, with NFS-based = storage, and we have daily snapshots of each VM. We have 15 snapshots, = and when we create one, we delete the oldest. Weekly we backup the content of each SR using DDAR = (http://www.synctus.com/ddar/), which is basically a tar of the = directory. But, correct me if I'm wrong, when we create a new snapshot = of any VM, the "ddar" of the SR is no longer valid, as a new VHD has = been added to the chain, and the oldest has been removed. Would it be possible to go back in time in the VHD chain? We use the = DDAR for Disaster Recover of the storage system. If it's not possible, then we will change the DR procedure to snapshot = the VM and then create the backup with DDAR in a daily basis. Thanks in advance and kind regards ------------------------------- Alberto Castrillo Ingenier=EDa de Servicios SARENET Parque Tecnol=F3gico, Ed. 103 Tel. 944 209 470 Zamudio - Vizcaya ------------------------------- --Apple-Mail-679-866659732 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 http://www.synctus.com/ddar/), = which is basically a tar of the directory. But, correct me if I'm wrong, = when we create a new snapshot of any VM, the "ddar" of the SR is no = longer valid, as a new VHD has been added to the chain, and the oldest = has been removed.
Would it be possible to go back in time in = the VHD chain? We use the DDAR for Disaster Recover of the storage = system.
If it's not possible, then we will change the DR = procedure to snapshot the VM and then create the backup with DDAR in a = daily basis.

Thanks in advance and kind = regards

Alberto Castrillo
Parque Tecnol=F3gico, = Ed. 103
Tel. 944 209 = 470
Zamudio - = Vizcaya
Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 08:40:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Xe0-0005fW-Bw; Fri, 10 Jan 2014 08:40:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1Xdx-0005fP-If for xen-api@lists.xensource.com; Fri, 10 Jan 2014 08:40:41 +0000 Received: from [85.158.139.211:44664] by server-9.bemta-5.messagelabs.com id A4/8D-15098-802BFC25; Fri, 10 Jan 2014 08:40:40 +0000 X-Env-Sender: castrillo@sarenet.es X-Msg-Ref: server-14.tower-206.messagelabs.com!1389343239!8908169!1 X-Originating-IP: [195.16.151.151] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24204 invoked from network); 10 Jan 2014 08:40:39 -0000 Received: from cu01176b.smtpx.saremail.com (HELO cu01176b.smtpx.saremail.com) (195.16.151.151) by server-14.tower-206.messagelabs.com with SMTP; 10 Jan 2014 08:40:39 -0000 Received: from [172.16.1.220] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPA id 0D21D9DC583 for ; Fri, 10 Jan 2014 09:40:36 +0100 (CET) From: Alberto Castrillo Date: Fri, 10 Jan 2014 09:40:36 +0100 Message-Id: <874F9063-EB8C-4C83-945A-583D9D3C3539@sarenet.es> To: xen-api@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Subject: [Xen-API] Backup of NFS Storage X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8695738177708114830==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8695738177708114830== Content-Type: multipart/alternative; boundary=Apple-Mail-679-866659732 --Apple-Mail-679-866659732 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi All We are running several pools with XCP 1.6 and XS 6.2, with NFS-based = storage, and we have daily snapshots of each VM. We have 15 snapshots, = and when we create one, we delete the oldest. Weekly we backup the content of each SR using DDAR = (http://www.synctus.com/ddar/), which is basically a tar of the = directory. But, correct me if I'm wrong, when we create a new snapshot = of any VM, the "ddar" of the SR is no longer valid, as a new VHD has = been added to the chain, and the oldest has been removed. Would it be possible to go back in time in the VHD chain? We use the = DDAR for Disaster Recover of the storage system. If it's not possible, then we will change the DR procedure to snapshot = the VM and then create the backup with DDAR in a daily basis. Thanks in advance and kind regards ------------------------------- Alberto Castrillo Ingenier=EDa de Servicios SARENET Parque Tecnol=F3gico, Ed. 103 Tel. 944 209 470 Zamudio - Vizcaya ------------------------------- --Apple-Mail-679-866659732 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 http://www.synctus.com/ddar/), = which is basically a tar of the directory. But, correct me if I'm wrong, = when we create a new snapshot of any VM, the "ddar" of the SR is no = longer valid, as a new VHD has been added to the chain, and the oldest = has been removed.
Would it be possible to go back in time in = the VHD chain? We use the DDAR for Disaster Recover of the storage = system.
If it's not possible, then we will change the DR = procedure to snapshot the VM and then create the backup with DDAR in a = daily basis.

Thanks in advance and kind = regards

Alberto Castrillo
Parque Tecnol=F3gico, = Ed. 103
Tel. 944 209 = 470
Zamudio - = Vizcaya
Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 13:23:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1c3a-0003Ka-JI; Fri, 10 Jan 2014 13:23:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1c3Z-0003KU-37 for xen-api@lists.xen.org; Fri, 10 Jan 2014 13:23:25 +0000 Received: from [85.158.143.35:15367] by server-1.bemta-4.messagelabs.com id 98/1B-02132-C44FFC25; Fri, 10 Jan 2014 13:23:24 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389360200!10884469!1 X-Originating-IP: [209.85.216.51] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21324 invoked from network); 10 Jan 2014 13:23:21 -0000 Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com) (209.85.216.51) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 13:23:21 -0000 Received: by mail-qa0-f51.google.com with SMTP id i13so4027034qae.24 for ; Fri, 10 Jan 2014 05:23:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=jLrIi5VmhyCaHMYmlgvZD0jCCWTHtgL683LHzZQLVbQ=; b=HaWb9AoBh+isLmUjSUR8+cpQlwEqx/7/TbOrfg+Ca1Dqu14bB8DAjSpRztwm9+ul2L /EzKdVId4atD+VqAqXc9IA65ynggnbJVIs1O3zibTSriEjWbqVtlyeAs55F0SrWk6nxF ygPxW31HrnubKrAt0i3EVC2vArqbodyRIjq/v9KKXY5rqEkSIYayjP8um7Z3uJP1+BnK qMqSSsgyQGRMU0mg1CkPodkq4D/OeKm/0nrMz1pPKESuVjgBn0K6vLF9mgWTNbpiJm7B VL8Bfu0EcbnjCvDFMD4+HRiO4C+vxza1uYm7wOP+jaeKPdiDbCPMZJ9TRbJP1xUquael 6GZQ== X-Gm-Message-State: ALoCoQm288G2Z0EMeKpLMFgNcQVMfr/f8Q7lWTw9lwgco8040kFc48qV1170Duw+VstvNEoRPGkw MIME-Version: 1.0 X-Received: by 10.49.28.101 with SMTP id a5mr7368471qeh.70.1389360200020; Fri, 10 Jan 2014 05:23:20 -0800 (PST) Received: by 10.140.49.174 with HTTP; Fri, 10 Jan 2014 05:23:19 -0800 (PST) Date: Fri, 10 Jan 2014 18:53:19 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] Solution for downloading the created snapshot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5759241675323630436==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5759241675323630436== Content-Type: multipart/alternative; boundary=047d7bd6adbc30870204ef9da128 --047d7bd6adbc30870204ef9da128 Content-Type: text/plain; charset=ISO-8859-1 Hi , I am working on a Xen backup solution . I need a solution to download the snapshot created in a remote Xen Host . We are using Curl at the moment to serve this purpose . Is there an API call which will serve the purpose ? Any info on this wud be immensely heplful . Regards, Shafi, Vembu Technologies. --047d7bd6adbc30870204ef9da128 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi ,
=A0 I am working on a Xen backup solution . I need= a solution to download the snapshot created in =A0a remote Xen Host . We a= re using Curl =A0at the moment to serve this purpose . Is there an API call= which will serve the purpose =A0? Any info on this
wud be immensely heplful .




Regards,
Shafi,=
Vembu Technologies.

--047d7bd6adbc30870204ef9da128-- --===============5759241675323630436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5759241675323630436==-- From xen-api-bounces@lists.xen.org Fri Jan 10 13:23:39 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 13:23:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1c3a-0003Ka-JI; Fri, 10 Jan 2014 13:23:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1c3Z-0003KU-37 for xen-api@lists.xen.org; Fri, 10 Jan 2014 13:23:25 +0000 Received: from [85.158.143.35:15367] by server-1.bemta-4.messagelabs.com id 98/1B-02132-C44FFC25; Fri, 10 Jan 2014 13:23:24 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389360200!10884469!1 X-Originating-IP: [209.85.216.51] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21324 invoked from network); 10 Jan 2014 13:23:21 -0000 Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com) (209.85.216.51) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 13:23:21 -0000 Received: by mail-qa0-f51.google.com with SMTP id i13so4027034qae.24 for ; Fri, 10 Jan 2014 05:23:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=jLrIi5VmhyCaHMYmlgvZD0jCCWTHtgL683LHzZQLVbQ=; b=HaWb9AoBh+isLmUjSUR8+cpQlwEqx/7/TbOrfg+Ca1Dqu14bB8DAjSpRztwm9+ul2L /EzKdVId4atD+VqAqXc9IA65ynggnbJVIs1O3zibTSriEjWbqVtlyeAs55F0SrWk6nxF ygPxW31HrnubKrAt0i3EVC2vArqbodyRIjq/v9KKXY5rqEkSIYayjP8um7Z3uJP1+BnK qMqSSsgyQGRMU0mg1CkPodkq4D/OeKm/0nrMz1pPKESuVjgBn0K6vLF9mgWTNbpiJm7B VL8Bfu0EcbnjCvDFMD4+HRiO4C+vxza1uYm7wOP+jaeKPdiDbCPMZJ9TRbJP1xUquael 6GZQ== X-Gm-Message-State: ALoCoQm288G2Z0EMeKpLMFgNcQVMfr/f8Q7lWTw9lwgco8040kFc48qV1170Duw+VstvNEoRPGkw MIME-Version: 1.0 X-Received: by 10.49.28.101 with SMTP id a5mr7368471qeh.70.1389360200020; Fri, 10 Jan 2014 05:23:20 -0800 (PST) Received: by 10.140.49.174 with HTTP; Fri, 10 Jan 2014 05:23:19 -0800 (PST) Date: Fri, 10 Jan 2014 18:53:19 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] Solution for downloading the created snapshot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5759241675323630436==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5759241675323630436== Content-Type: multipart/alternative; boundary=047d7bd6adbc30870204ef9da128 --047d7bd6adbc30870204ef9da128 Content-Type: text/plain; charset=ISO-8859-1 Hi , I am working on a Xen backup solution . I need a solution to download the snapshot created in a remote Xen Host . We are using Curl at the moment to serve this purpose . Is there an API call which will serve the purpose ? Any info on this wud be immensely heplful . Regards, Shafi, Vembu Technologies. --047d7bd6adbc30870204ef9da128 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi ,
=A0 I am working on a Xen backup solution . I need= a solution to download the snapshot created in =A0a remote Xen Host . We a= re using Curl =A0at the moment to serve this purpose . Is there an API call= which will serve the purpose =A0? Any info on this
wud be immensely heplful .




Regards,
Shafi,=
Vembu Technologies.

--047d7bd6adbc30870204ef9da128-- --===============5759241675323630436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5759241675323630436==-- From xen-api-bounces@lists.xen.org Fri Jan 10 14:43:46 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 14:43:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dJC-0003EA-0O; Fri, 10 Jan 2014 14:43:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dJA-0003E1-Lv for xen-api@lists.xen.org; Fri, 10 Jan 2014 14:43:36 +0000 Received: from [85.158.143.35:13865] by server-1.bemta-4.messagelabs.com id C7/92-02132-81700D25; Fri, 10 Jan 2014 14:43:36 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-12.tower-21.messagelabs.com!1389365015!10824884!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22947 invoked from network); 10 Jan 2014 14:43:35 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-12.tower-21.messagelabs.com with SMTP; 10 Jan 2014 14:43:35 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CEjZ1n00L3zjds103EjadC; Fri, 10 Jan 2014 15:43:35 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9B814161D75; Fri, 10 Jan 2014 15:43:33 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id xIUsVgAiotkZ; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9D131162063; Fri, 10 Jan 2014 15:43:32 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id swN9v_gpIdER; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 57F55161D75; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Message-ID: <52D00714.9010601@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 15:43:32 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed S References: In-Reply-To: Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Solution for downloading the created snapshot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > I am working on a Xen backup solution . I need a solution to download > the snapshot created in a remote Xen Host . We are using Curl at the > moment to serve this purpose . Is there an API call which will serve the > purpose ? Any info on this > wud be immensely heplful . we are using python http call with some xapi call to make our vm exports = for backup. We have published the source of our inhouse backup scripts = tisbackup. You can browse the source on github = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py). We also sometime alse use xe command in scripts to copy the snapshot to = our backup server. In order to use the xe binary, you just have to copy = the /opt/xensource/bin folder to your backup server, install stunnel4 = (for a debian wheezy) and then you can use the xe command the same way = you do on the xen server. Hope this helps, Denis > > > > > Regards, > Shafi, > Vembu Technologies. > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 14:43:46 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 14:43:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dJC-0003EA-0O; Fri, 10 Jan 2014 14:43:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dJA-0003E1-Lv for xen-api@lists.xen.org; Fri, 10 Jan 2014 14:43:36 +0000 Received: from [85.158.143.35:13865] by server-1.bemta-4.messagelabs.com id C7/92-02132-81700D25; Fri, 10 Jan 2014 14:43:36 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-12.tower-21.messagelabs.com!1389365015!10824884!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22947 invoked from network); 10 Jan 2014 14:43:35 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-12.tower-21.messagelabs.com with SMTP; 10 Jan 2014 14:43:35 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CEjZ1n00L3zjds103EjadC; Fri, 10 Jan 2014 15:43:35 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9B814161D75; Fri, 10 Jan 2014 15:43:33 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id xIUsVgAiotkZ; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9D131162063; Fri, 10 Jan 2014 15:43:32 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id swN9v_gpIdER; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 57F55161D75; Fri, 10 Jan 2014 15:43:32 +0100 (CET) Message-ID: <52D00714.9010601@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 15:43:32 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed S References: In-Reply-To: Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Solution for downloading the created snapshot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > I am working on a Xen backup solution . I need a solution to download > the snapshot created in a remote Xen Host . We are using Curl at the > moment to serve this purpose . Is there an API call which will serve the > purpose ? Any info on this > wud be immensely heplful . we are using python http call with some xapi call to make our vm exports = for backup. We have published the source of our inhouse backup scripts = tisbackup. You can browse the source on github = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py). We also sometime alse use xe command in scripts to copy the snapshot to = our backup server. In order to use the xe binary, you just have to copy = the /opt/xensource/bin folder to your backup server, install stunnel4 = (for a debian wheezy) and then you can use the xe command the same way = you do on the xen server. Hope this helps, Denis > > > > > Regards, > Shafi, > Vembu Technologies. > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:10:47 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:10:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1djM-0006gU-Aq; Fri, 10 Jan 2014 15:10:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1djK-0006gL-Mq for xen-api@lists.xen.org; Fri, 10 Jan 2014 15:10:38 +0000 Received: from [85.158.143.35:12933] by server-2.bemta-4.messagelabs.com id A8/AF-11386-E6D00D25; Fri, 10 Jan 2014 15:10:38 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-21.messagelabs.com!1389366637!10910965!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12832 invoked from network); 10 Jan 2014 15:10:37 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-7.tower-21.messagelabs.com with SMTP; 10 Jan 2014 15:10:37 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFAb1n00M3zjds103FAcSq; Fri, 10 Jan 2014 16:10:36 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CB2F5161D75; Fri, 10 Jan 2014 16:10:35 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id pdVNM48AOZar; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B2394162063; Fri, 10 Jan 2014 16:10:34 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id umm1ArUnAZNO; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 77244161D75; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Message-ID: <52D00D6A.6020901@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:10:34 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "Agyeman B. Danso Jr." References: In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Agyeman, > Can you help me with the command to change ip address of a vm while on > hypervisor? > > In my case if access to xen center is disabled and a user changes the > ipaddress of a vm and no longer can ssh to the vm, I would like to be > able to reset the ip address, netmask, and gateway from the hypervisor. > > The command below shows me network info but how to I change that network > info? > > xe vm-list params=3Dname-label,networks I think this command is read only and show you the ip address that has = been reported by xentools to the hypervisor. However I don't think there is a default mechanism in xapi to set the ip = address of a virtual machine. In some VDI deployement solution, the = software install a service inside the VDI machine to get the ip address = from a deployement server. However you don't need xencenter to get access to the vnc frame buffer = of the virtual machine. You can get the vnc port using the following = command line (change my_vm_name, and be sure to be on the server where = the vm is running if the server is in a pool) : xenstore-read /local/domain/$(xe vm-list params=3Ddom-id = name-label=3Dmy_vm_name --minimal)/console/vnc-port Take the port number that is given by the above command line (for = example 5908), and then, just do a ssh port forwarding : ssh my_xen_server -L 5908:srvxen1:5908 -l root then from the same machine, run vncviewer localhost:8 Another method for a linux VM : use xe-edit-bootloader -n my_vm_name, = then from another shell, you can find the vm mounted on /var/run/fix-xxxxxx when you have fixed the network configuration, you get out of the mount = point, then get out of the grub editing window, the xe-edit-bootloader = script will umount the partition by itself. Cheers, Denis > > *Thank you,* > > *Agyeman B. Danso Jr.* > > Security Engineer > > infoLock Technologies > > 877.610.5625 x253 - direct > ADanso@infolocktech.com > > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:10:47 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:10:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1djM-0006gU-Aq; Fri, 10 Jan 2014 15:10:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1djK-0006gL-Mq for xen-api@lists.xen.org; Fri, 10 Jan 2014 15:10:38 +0000 Received: from [85.158.143.35:12933] by server-2.bemta-4.messagelabs.com id A8/AF-11386-E6D00D25; Fri, 10 Jan 2014 15:10:38 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-21.messagelabs.com!1389366637!10910965!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12832 invoked from network); 10 Jan 2014 15:10:37 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-7.tower-21.messagelabs.com with SMTP; 10 Jan 2014 15:10:37 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFAb1n00M3zjds103FAcSq; Fri, 10 Jan 2014 16:10:36 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CB2F5161D75; Fri, 10 Jan 2014 16:10:35 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id pdVNM48AOZar; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B2394162063; Fri, 10 Jan 2014 16:10:34 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id umm1ArUnAZNO; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 77244161D75; Fri, 10 Jan 2014 16:10:34 +0100 (CET) Message-ID: <52D00D6A.6020901@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:10:34 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "Agyeman B. Danso Jr." References: In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Agyeman, > Can you help me with the command to change ip address of a vm while on > hypervisor? > > In my case if access to xen center is disabled and a user changes the > ipaddress of a vm and no longer can ssh to the vm, I would like to be > able to reset the ip address, netmask, and gateway from the hypervisor. > > The command below shows me network info but how to I change that network > info? > > xe vm-list params=3Dname-label,networks I think this command is read only and show you the ip address that has = been reported by xentools to the hypervisor. However I don't think there is a default mechanism in xapi to set the ip = address of a virtual machine. In some VDI deployement solution, the = software install a service inside the VDI machine to get the ip address = from a deployement server. However you don't need xencenter to get access to the vnc frame buffer = of the virtual machine. You can get the vnc port using the following = command line (change my_vm_name, and be sure to be on the server where = the vm is running if the server is in a pool) : xenstore-read /local/domain/$(xe vm-list params=3Ddom-id = name-label=3Dmy_vm_name --minimal)/console/vnc-port Take the port number that is given by the above command line (for = example 5908), and then, just do a ssh port forwarding : ssh my_xen_server -L 5908:srvxen1:5908 -l root then from the same machine, run vncviewer localhost:8 Another method for a linux VM : use xe-edit-bootloader -n my_vm_name, = then from another shell, you can find the vm mounted on /var/run/fix-xxxxxx when you have fixed the network configuration, you get out of the mount = point, then get out of the grub editing window, the xe-edit-bootloader = script will umount the partition by itself. Cheers, Denis > > *Thank you,* > > *Agyeman B. Danso Jr.* > > Security Engineer > > infoLock Technologies > > 877.610.5625 x253 - direct > ADanso@infolocktech.com > > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:14:33 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:14:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dn4-00076O-Mi; Fri, 10 Jan 2014 15:14:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dn3-00075P-5w for xen-api@lists.xen.org; Fri, 10 Jan 2014 15:14:29 +0000 Received: from [85.158.139.211:22559] by server-16.bemta-5.messagelabs.com id BE/72-11843-45E00D25; Fri, 10 Jan 2014 15:14:28 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-206.messagelabs.com!1389366867!9011960!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6868 invoked from network); 10 Jan 2014 15:14:27 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-206.messagelabs.com with SMTP; 10 Jan 2014 15:14:27 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFET1n0023zjds103FETlJ; Fri, 10 Jan 2014 16:14:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 081A0161D75; Fri, 10 Jan 2014 16:14:27 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id h6VrvnlS3eMu; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id C84FD162063; Fri, 10 Jan 2014 16:14:25 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cCFr6Eqpqs0M; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8CED0161D75; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Message-ID: <52D00E51.5070304@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:14:25 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Amit More References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Strange Log Entries X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Amit, > > I'm running XCP 1.1.0-50674c on a Dell PowerEdge 2950 server, and I'm see= ing a lot of the following logs in /var/log/user.log file. > > Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr <= methodName>protect...) exitted with code 0 > Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted wi= th code 0 > > The first message is repeated every 15 minutes, and the second message is= repeated every 90 minutes. On some research I found out that there is a cr= on job that executes /opt/xensource/sm/runvmpr every 15 minutes which is ge= nerating the first message. > > The exit status of the two scripts (/opt/xensource/sm/runvmpr, and /usr/b= in/ovs-vsctl list-br) when ran manually is 0. I wonder what these log entri= es mean, and why the exit status 0 is recorded in the log entries. Is it so= mething concerning or should I just ignore the errors? exit code 0 should mean "program executed successfully and exited". So I = think you can ignore those messages. Perhaps there is somewhere a = loglevel attribute in order to avoid those message. By the way, you should upgrade to XCP 1.6 or better XS6.2, I remember = that there was a snapshot coaslesing bug in XCP 1.1 that eat one of my = VMs once. Cheers, Denis > > Any help would be greatly appreciated. Thanks in advance. > > Amit More > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:14:33 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:14:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dn4-00076O-Mi; Fri, 10 Jan 2014 15:14:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dn3-00075P-5w for xen-api@lists.xen.org; Fri, 10 Jan 2014 15:14:29 +0000 Received: from [85.158.139.211:22559] by server-16.bemta-5.messagelabs.com id BE/72-11843-45E00D25; Fri, 10 Jan 2014 15:14:28 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-206.messagelabs.com!1389366867!9011960!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6868 invoked from network); 10 Jan 2014 15:14:27 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-206.messagelabs.com with SMTP; 10 Jan 2014 15:14:27 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFET1n0023zjds103FETlJ; Fri, 10 Jan 2014 16:14:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 081A0161D75; Fri, 10 Jan 2014 16:14:27 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id h6VrvnlS3eMu; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id C84FD162063; Fri, 10 Jan 2014 16:14:25 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cCFr6Eqpqs0M; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8CED0161D75; Fri, 10 Jan 2014 16:14:25 +0100 (CET) Message-ID: <52D00E51.5070304@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:14:25 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Amit More References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Strange Log Entries X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Amit, > > I'm running XCP 1.1.0-50674c on a Dell PowerEdge 2950 server, and I'm see= ing a lot of the following logs in /var/log/user.log file. > > Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr <= methodName>protect...) exitted with code 0 > Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted wi= th code 0 > > The first message is repeated every 15 minutes, and the second message is= repeated every 90 minutes. On some research I found out that there is a cr= on job that executes /opt/xensource/sm/runvmpr every 15 minutes which is ge= nerating the first message. > > The exit status of the two scripts (/opt/xensource/sm/runvmpr, and /usr/b= in/ovs-vsctl list-br) when ran manually is 0. I wonder what these log entri= es mean, and why the exit status 0 is recorded in the log entries. Is it so= mething concerning or should I just ignore the errors? exit code 0 should mean "program executed successfully and exited". So I = think you can ignore those messages. Perhaps there is somewhere a = loglevel attribute in order to avoid those message. By the way, you should upgrade to XCP 1.6 or better XS6.2, I remember = that there was a snapshot coaslesing bug in XCP 1.1 that eat one of my = VMs once. Cheers, Denis > > Any help would be greatly appreciated. Thanks in advance. > > Amit More > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:27:06 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:27:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dz9-0001RN-Pe; Fri, 10 Jan 2014 15:26:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dz9-0001RD-3F for xen-api@lists.xensource.com; Fri, 10 Jan 2014 15:26:59 +0000 Received: from [85.158.137.68:51477] by server-7.bemta-3.messagelabs.com id EA/65-27599-24110D25; Fri, 10 Jan 2014 15:26:58 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1389367617!8377236!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1259 invoked from network); 10 Jan 2014 15:26:57 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-31.messagelabs.com with SMTP; 10 Jan 2014 15:26:57 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFSw1n00M3zjds103FSww1; Fri, 10 Jan 2014 16:26:57 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id BE360161D75; Fri, 10 Jan 2014 16:26:56 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 2H4-6eJnm_I0; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CFCEA162063; Fri, 10 Jan 2014 16:26:55 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HXLQbn9IYuIg; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9CCB8161D75; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Message-ID: <52D0113F.2040801@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:26:55 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed References: In-Reply-To: Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > I am working on a backup application . Our solution works fine for a > single Xen host . But on A Xen Pool Configuration, session() call > works only for the master , Is there any call to retrieve the IP of > the master when we are working with the slave nodes ,so that a > redirection can be made to that obtained master IP when slave node is > enquired for backup . In python, you can use the following code : session =3D XenAPI.Session('https://'+self.xcphost) try: session.login_with_password(user_xen,password_xen) except XenAPI.Failure, error: msg,ip =3D error.details if msg =3D=3D 'HOST_IS_SLAVE': xcphost =3D ip session =3D XenAPI.Session('https://'+xcphost) session.login_with_password(user_xen,password_xen) (from our inhouse backup application = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py) HTH, Denis > > Thank you > Shafi Mohammed > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 15:27:06 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 15:27:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dz9-0001RN-Pe; Fri, 10 Jan 2014 15:26:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1dz9-0001RD-3F for xen-api@lists.xensource.com; Fri, 10 Jan 2014 15:26:59 +0000 Received: from [85.158.137.68:51477] by server-7.bemta-3.messagelabs.com id EA/65-27599-24110D25; Fri, 10 Jan 2014 15:26:58 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1389367617!8377236!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1259 invoked from network); 10 Jan 2014 15:26:57 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-31.messagelabs.com with SMTP; 10 Jan 2014 15:26:57 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d07 with ME id CFSw1n00M3zjds103FSww1; Fri, 10 Jan 2014 16:26:57 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id BE360161D75; Fri, 10 Jan 2014 16:26:56 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 2H4-6eJnm_I0; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CFCEA162063; Fri, 10 Jan 2014 16:26:55 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HXLQbn9IYuIg; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9CCB8161D75; Fri, 10 Jan 2014 16:26:55 +0100 (CET) Message-ID: <52D0113F.2040801@tranquil-it-systems.fr> Date: Fri, 10 Jan 2014 16:26:55 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed References: In-Reply-To: Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Xen-Api -Retrieving the Xen master node IP using Xen API X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > I am working on a backup application . Our solution works fine for a > single Xen host . But on A Xen Pool Configuration, session() call > works only for the master , Is there any call to retrieve the IP of > the master when we are working with the slave nodes ,so that a > redirection can be made to that obtained master IP when slave node is > enquired for backup . In python, you can use the following code : session =3D XenAPI.Session('https://'+self.xcphost) try: session.login_with_password(user_xen,password_xen) except XenAPI.Failure, error: msg,ip =3D error.details if msg =3D=3D 'HOST_IS_SLAVE': xcphost =3D ip session =3D XenAPI.Session('https://'+xcphost) session.login_with_password(user_xen,password_xen) (from our inhouse backup application = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py) HTH, Denis > > Thank you > Shafi Mohammed > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 21:40:20 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 21:40:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1joI-0004Wg-Kx; Fri, 10 Jan 2014 21:40:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1joF-0004WV-3e for xen-api@lists.xen.org; Fri, 10 Jan 2014 21:40:09 +0000 Received: from [85.158.137.68:49558] by server-14.bemta-3.messagelabs.com id 80/A8-06105-6B860D25; Fri, 10 Jan 2014 21:40:06 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1389390003!8467171!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25559 invoked from network); 10 Jan 2014 21:40:05 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 21:40:05 -0000 Received: by mail-pb0-f45.google.com with SMTP id rp16so4973884pbb.4 for ; Fri, 10 Jan 2014 13:40:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=h5x6JivkmbQqIxSvkJA13AEZ2kPf6WM1Klw6S3/18Qs=; b=iIn7RUk3cbiFcPesKoRX6UI1rxq5e1yHK7EtIi/FyFK5xY2MKBLw7e00Z3DaYTT1vn 6eyp2wCtj7/j5XOpvjI+y4lA5OpTIY/uPSSmOAZ0FpO4qdyC8jSkOQM3o8qfjR6IIG1+ pFGfbb0EG7xMnjVaLWUA+iCoXdFJEA3TC28qQelYRYZ7R0KVlITE11QJIKwyrp9DLPeZ EgOqIhlIbBvtPQ8rYOpY3ux4ar2P1KQYylQwAlmnhwlTEjWtx33sp18UAFUlGByldFI0 p6/HONYpexNb7QknPtpxcyvoxZTNcBMyDQmSf5z2o6keZBQwZoqgqXEC9td20q35SWnC VkEA== X-Gm-Message-State: ALoCoQnqnWwvQNknnSOtnjHBVboFxTL4sBeo73BxhsN1bA+IfnfrgQ1zLWlEx/E4J95NevvlLv0q X-Received: by 10.68.229.36 with SMTP id sn4mr14258667pbc.23.1389390003230; Fri, 10 Jan 2014 13:40:03 -0800 (PST) Received: from [10.101.99.70] ([66.151.128.105]) by mx.google.com with ESMTPSA id iq10sm6422716pbc.14.2014.01.10.13.40.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 Jan 2014 13:40:02 -0800 (PST) From: Amit More Message-Id: <2786D386-4C42-45E3-8BDB-107688005A6B@xetus.com> Date: Fri, 10 Jan 2014 13:39:58 -0800 To: "xen-api@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] ATA Kernel Warnings X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I have a bunch of Dell PowerEdge 2950 servers with TEAC DV-28E-V DVD ROM running XCP 1.1. My kernel logs are filled with the following messages. 2014.01.10 - 13:17:22 vmhost1 Warning kernel kernel: ata1: device not ready (errno=-16), forcing hardreset 2014.01.10 - 13:17:17 vmhost1 Warning kernel kernel: ata1: link is slow to respond, please be patient (ready=0) 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: status: { DRDY ERR } 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout) 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen 2014.01.10 - 13:17:12 vmhost1 Warning kernel kernel: ata1.00: qc timeout (cmd 0xa0) I also have other Dell PowerEdge systems with non TEAC DV-28E-V DVD ROM running XCP 1.1 and those systems are not reporting any of the above kernel warnings. Looking into the issue I found that there is a bug in XenServer 5.6 running on systems with TEAC DV-28E-V DVD ROM. The bug report can be found at http://support.citrix.com/article/CTX126919. Though this bug is not causing my Dom0 CPU to overload, I suspect ATA kernel warnings are related to this bug. There is a driver update that was released by Citrix. I believe that the updated driver is included in XCP 1.1. This can be confirmed by executing "modinfo ata_generic" command. This leaves me wondering if the ATA kernel warnings are related to the bug mentioned above. Any insights would be greatly appreciated. Thanks in Advance, Amit _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 21:40:20 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 21:40:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1joI-0004Wg-Kx; Fri, 10 Jan 2014 21:40:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1joF-0004WV-3e for xen-api@lists.xen.org; Fri, 10 Jan 2014 21:40:09 +0000 Received: from [85.158.137.68:49558] by server-14.bemta-3.messagelabs.com id 80/A8-06105-6B860D25; Fri, 10 Jan 2014 21:40:06 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1389390003!8467171!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25559 invoked from network); 10 Jan 2014 21:40:05 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 21:40:05 -0000 Received: by mail-pb0-f45.google.com with SMTP id rp16so4973884pbb.4 for ; Fri, 10 Jan 2014 13:40:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=h5x6JivkmbQqIxSvkJA13AEZ2kPf6WM1Klw6S3/18Qs=; b=iIn7RUk3cbiFcPesKoRX6UI1rxq5e1yHK7EtIi/FyFK5xY2MKBLw7e00Z3DaYTT1vn 6eyp2wCtj7/j5XOpvjI+y4lA5OpTIY/uPSSmOAZ0FpO4qdyC8jSkOQM3o8qfjR6IIG1+ pFGfbb0EG7xMnjVaLWUA+iCoXdFJEA3TC28qQelYRYZ7R0KVlITE11QJIKwyrp9DLPeZ EgOqIhlIbBvtPQ8rYOpY3ux4ar2P1KQYylQwAlmnhwlTEjWtx33sp18UAFUlGByldFI0 p6/HONYpexNb7QknPtpxcyvoxZTNcBMyDQmSf5z2o6keZBQwZoqgqXEC9td20q35SWnC VkEA== X-Gm-Message-State: ALoCoQnqnWwvQNknnSOtnjHBVboFxTL4sBeo73BxhsN1bA+IfnfrgQ1zLWlEx/E4J95NevvlLv0q X-Received: by 10.68.229.36 with SMTP id sn4mr14258667pbc.23.1389390003230; Fri, 10 Jan 2014 13:40:03 -0800 (PST) Received: from [10.101.99.70] ([66.151.128.105]) by mx.google.com with ESMTPSA id iq10sm6422716pbc.14.2014.01.10.13.40.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 Jan 2014 13:40:02 -0800 (PST) From: Amit More Message-Id: <2786D386-4C42-45E3-8BDB-107688005A6B@xetus.com> Date: Fri, 10 Jan 2014 13:39:58 -0800 To: "xen-api@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] ATA Kernel Warnings X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I have a bunch of Dell PowerEdge 2950 servers with TEAC DV-28E-V DVD ROM running XCP 1.1. My kernel logs are filled with the following messages. 2014.01.10 - 13:17:22 vmhost1 Warning kernel kernel: ata1: device not ready (errno=-16), forcing hardreset 2014.01.10 - 13:17:17 vmhost1 Warning kernel kernel: ata1: link is slow to respond, please be patient (ready=0) 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: status: { DRDY ERR } 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout) 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 2014.01.10 - 13:17:12 vmhost1 Error kernel kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen 2014.01.10 - 13:17:12 vmhost1 Warning kernel kernel: ata1.00: qc timeout (cmd 0xa0) I also have other Dell PowerEdge systems with non TEAC DV-28E-V DVD ROM running XCP 1.1 and those systems are not reporting any of the above kernel warnings. Looking into the issue I found that there is a bug in XenServer 5.6 running on systems with TEAC DV-28E-V DVD ROM. The bug report can be found at http://support.citrix.com/article/CTX126919. Though this bug is not causing my Dom0 CPU to overload, I suspect ATA kernel warnings are related to this bug. There is a driver update that was released by Citrix. I believe that the updated driver is included in XCP 1.1. This can be confirmed by executing "modinfo ata_generic" command. This leaves me wondering if the ATA kernel warnings are related to the bug mentioned above. Any insights would be greatly appreciated. Thanks in Advance, Amit _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 10 22:23:56 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 22:23:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1kUa-00088A-87; Fri, 10 Jan 2014 22:23:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1kUY-000885-RU for xen-api@lists.xen.org; Fri, 10 Jan 2014 22:23:51 +0000 Received: from [85.158.139.211:38667] by server-12.bemta-5.messagelabs.com id 16/ED-30017-5F270D25; Fri, 10 Jan 2014 22:23:49 +0000 X-Env-Sender: arnagara@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1389392628!9115661!1 X-Originating-IP: [209.85.214.182] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19977 invoked from network); 10 Jan 2014 22:23:49 -0000 Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 22:23:49 -0000 Received: by mail-ob0-f182.google.com with SMTP id wn1so3471689obc.41 for ; Fri, 10 Jan 2014 14:23:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=PzgtNKyXxyZsWQFPdxjuqY0lEdkui97vj5OO95NVYUs=; b=0tcY4Hjm2Y4bnK9v8tkYkvmJeNO7SOQB4vSO7Drh5BLYd8CeW3htGdMh3YZoDZt+sz 28KfUQhfCf1SR7+s8/mwFfT4nDfp5lPpDmCA/noMeum9ZRSd6CdOTiSDqNW6Dg/ksKBf F0q4MEuBnyTZOzlomqiOlqE1u2jevSIJ5hZ6kUCetqEk6uox2QLj+fFbKAixaniGpyYr FtTnJKmZEYGKWoQBaDSzG8XndHCdsTBRg5I8v8N5ENMqSICH7nfWQLxd/JdYTU/XPI1W LW635dsW/lnh8I7BHnNQ/Zn3+6fdgJ8lxDyZx5zcR7e5Cz3iaoVNlD0pQTDlLGQ0OkPm 0exQ== MIME-Version: 1.0 X-Received: by 10.182.233.228 with SMTP id tz4mr9165361obc.56.1389392627636; Fri, 10 Jan 2014 14:23:47 -0800 (PST) Received: by 10.76.107.146 with HTTP; Fri, 10 Jan 2014 14:23:47 -0800 (PST) Date: Fri, 10 Jan 2014 14:23:47 -0800 Message-ID: From: Arvind Nagarajan To: xen-api@lists.xen.org Subject: [Xen-API] debug xen-api plugin X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3301404228701030159==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3301404228701030159== Content-Type: multipart/alternative; boundary=001a11c3060006205204efa52ea4 --001a11c3060006205204efa52ea4 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a startup script that does the following: xe host-call-plugin host-uuid="$INSTALLATION_UUID" plugin="plug-in-name" fn="function" The python plugin invokes a bunch of our internal commands which can throw success/error messages on the console. We would like to have view those messages in the console (instead of logging the messages into syslog/file) to debug this startup/boot issue. The python plugin invoked as part of 'xe host-call-plugin' does not seem to turn on the stdout/stderr. Using sys.stderr/sys.stdout in the python plugin does not display any message on the console. How may I enable the stdout/stderr of the python plugin. Any pointers will be helpful. Thanks, --Arvind --001a11c3060006205204efa52ea4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I have a startup script = that does the following:
xe host-call-plugin host-uuid=3D"$I= NSTALLATION_UUID" plugin=3D"plug-in-name" fn=3D"functio= n"

The python plugin invokes a bunch of our internal comma= nds which can throw success/error messages on the console. We would like to= have view those messages in the console (instead of logging the messages i= nto syslog/file) to debug this startup/boot issue.

The python plugin invoked as part of 'xe host-call-= plugin' does not seem to turn on the stdout/stderr.
Using sys= .stderr/sys.stdout in the python plugin does not display any message on the= console.

How may I enable the stdout/stderr of the python plugin= .
Any pointers will be helpful.

Thanks,<= br>
--Arvind
--001a11c3060006205204efa52ea4-- --===============3301404228701030159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3301404228701030159==-- From xen-api-bounces@lists.xen.org Fri Jan 10 22:23:56 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 Jan 2014 22:23:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1kUa-00088A-87; Fri, 10 Jan 2014 22:23:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1kUY-000885-RU for xen-api@lists.xen.org; Fri, 10 Jan 2014 22:23:51 +0000 Received: from [85.158.139.211:38667] by server-12.bemta-5.messagelabs.com id 16/ED-30017-5F270D25; Fri, 10 Jan 2014 22:23:49 +0000 X-Env-Sender: arnagara@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1389392628!9115661!1 X-Originating-IP: [209.85.214.182] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19977 invoked from network); 10 Jan 2014 22:23:49 -0000 Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 22:23:49 -0000 Received: by mail-ob0-f182.google.com with SMTP id wn1so3471689obc.41 for ; Fri, 10 Jan 2014 14:23:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=PzgtNKyXxyZsWQFPdxjuqY0lEdkui97vj5OO95NVYUs=; b=0tcY4Hjm2Y4bnK9v8tkYkvmJeNO7SOQB4vSO7Drh5BLYd8CeW3htGdMh3YZoDZt+sz 28KfUQhfCf1SR7+s8/mwFfT4nDfp5lPpDmCA/noMeum9ZRSd6CdOTiSDqNW6Dg/ksKBf F0q4MEuBnyTZOzlomqiOlqE1u2jevSIJ5hZ6kUCetqEk6uox2QLj+fFbKAixaniGpyYr FtTnJKmZEYGKWoQBaDSzG8XndHCdsTBRg5I8v8N5ENMqSICH7nfWQLxd/JdYTU/XPI1W LW635dsW/lnh8I7BHnNQ/Zn3+6fdgJ8lxDyZx5zcR7e5Cz3iaoVNlD0pQTDlLGQ0OkPm 0exQ== MIME-Version: 1.0 X-Received: by 10.182.233.228 with SMTP id tz4mr9165361obc.56.1389392627636; Fri, 10 Jan 2014 14:23:47 -0800 (PST) Received: by 10.76.107.146 with HTTP; Fri, 10 Jan 2014 14:23:47 -0800 (PST) Date: Fri, 10 Jan 2014 14:23:47 -0800 Message-ID: From: Arvind Nagarajan To: xen-api@lists.xen.org Subject: [Xen-API] debug xen-api plugin X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3301404228701030159==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3301404228701030159== Content-Type: multipart/alternative; boundary=001a11c3060006205204efa52ea4 --001a11c3060006205204efa52ea4 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a startup script that does the following: xe host-call-plugin host-uuid="$INSTALLATION_UUID" plugin="plug-in-name" fn="function" The python plugin invokes a bunch of our internal commands which can throw success/error messages on the console. We would like to have view those messages in the console (instead of logging the messages into syslog/file) to debug this startup/boot issue. The python plugin invoked as part of 'xe host-call-plugin' does not seem to turn on the stdout/stderr. Using sys.stderr/sys.stdout in the python plugin does not display any message on the console. How may I enable the stdout/stderr of the python plugin. Any pointers will be helpful. Thanks, --Arvind --001a11c3060006205204efa52ea4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I have a startup script = that does the following:
xe host-call-plugin host-uuid=3D"$I= NSTALLATION_UUID" plugin=3D"plug-in-name" fn=3D"functio= n"

The python plugin invokes a bunch of our internal comma= nds which can throw success/error messages on the console. We would like to= have view those messages in the console (instead of logging the messages i= nto syslog/file) to debug this startup/boot issue.

The python plugin invoked as part of 'xe host-call-= plugin' does not seem to turn on the stdout/stderr.
Using sys= .stderr/sys.stdout in the python plugin does not display any message on the= console.

How may I enable the stdout/stderr of the python plugin= .
Any pointers will be helpful.

Thanks,<= br>
--Arvind
--001a11c3060006205204efa52ea4-- --===============3301404228701030159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3301404228701030159==-- From xen-api-bounces@lists.xen.org Tue Jan 14 08:55:02 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 14 Jan 2014 08:55:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W2zln-0000MK-Rf; Tue, 14 Jan 2014 08:54:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W2zlm-0000MF-EN for xen-api@lists.xen.org; Tue, 14 Jan 2014 08:54:46 +0000 Received: from [85.158.137.68:30267] by server-12.bemta-3.messagelabs.com id 4D/4C-20055-55BF4D25; Tue, 14 Jan 2014 08:54:45 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-31.messagelabs.com!1389689684!5308006!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7774 invoked from network); 14 Jan 2014 08:54:44 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-15.tower-31.messagelabs.com with SMTP; 14 Jan 2014 08:54:44 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d69 with ME id Dkuk1n00A3zjds103kukS3; Tue, 14 Jan 2014 09:54:44 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 08A3F161D78 for ; Tue, 14 Jan 2014 09:54:44 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id KOET4x-tdHMS; Tue, 14 Jan 2014 09:54:43 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F3AC6162063; Tue, 14 Jan 2014 09:54:42 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tMZMqGzccy5n; Tue, 14 Jan 2014 09:54:42 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B9A5C161D78; Tue, 14 Jan 2014 09:54:42 +0100 (CET) Message-ID: <52D4FB52.1070403@tranquil-it-systems.fr> Date: Tue, 14 Jan 2014 09:54:42 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] xenserver vhd compression and TRIM instruction X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everyone, I would like to hear from you all about the strategies you use to = compress your VHD file. I mostly use lvmoiscsi shared storage, so the = VHD compression is not that much for gaining space on the active = storage, but merely for speeding up XVA exports and transfert. There is a tool from microsoft for compression [1], but it is Windows = only and so would require to have access to the VHD file from a Windows = VM. There is an article on Citrix knowledge database, but with the same = constraint. Moreover those two articles only talks about NTFS = filesystem, and not ext3/ext4. With the new TRIM io instruction for SSD, couldn't it be possible for = the virtual machine to flag the no-more-used VHD block with TRIM flag, = so that the vhd compression could happend without needing filesystem = semantic? So I'd like to hear from you if you know of anything that could help = trim unused block from VHD files from xenserver dom0. Cheers, keep on the good job, and see you in FOSDEM Denis [1] http://technet.microsoft.com/en-us/library/hh848458.aspx [2] http://support.citrix.com/article/CTX133254 -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 14 08:55:02 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 14 Jan 2014 08:55:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W2zln-0000MK-Rf; Tue, 14 Jan 2014 08:54:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W2zlm-0000MF-EN for xen-api@lists.xen.org; Tue, 14 Jan 2014 08:54:46 +0000 Received: from [85.158.137.68:30267] by server-12.bemta-3.messagelabs.com id 4D/4C-20055-55BF4D25; Tue, 14 Jan 2014 08:54:45 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-31.messagelabs.com!1389689684!5308006!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7774 invoked from network); 14 Jan 2014 08:54:44 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-15.tower-31.messagelabs.com with SMTP; 14 Jan 2014 08:54:44 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d69 with ME id Dkuk1n00A3zjds103kukS3; Tue, 14 Jan 2014 09:54:44 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 08A3F161D78 for ; Tue, 14 Jan 2014 09:54:44 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id KOET4x-tdHMS; Tue, 14 Jan 2014 09:54:43 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F3AC6162063; Tue, 14 Jan 2014 09:54:42 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tMZMqGzccy5n; Tue, 14 Jan 2014 09:54:42 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B9A5C161D78; Tue, 14 Jan 2014 09:54:42 +0100 (CET) Message-ID: <52D4FB52.1070403@tranquil-it-systems.fr> Date: Tue, 14 Jan 2014 09:54:42 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] xenserver vhd compression and TRIM instruction X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everyone, I would like to hear from you all about the strategies you use to = compress your VHD file. I mostly use lvmoiscsi shared storage, so the = VHD compression is not that much for gaining space on the active = storage, but merely for speeding up XVA exports and transfert. There is a tool from microsoft for compression [1], but it is Windows = only and so would require to have access to the VHD file from a Windows = VM. There is an article on Citrix knowledge database, but with the same = constraint. Moreover those two articles only talks about NTFS = filesystem, and not ext3/ext4. With the new TRIM io instruction for SSD, couldn't it be possible for = the virtual machine to flag the no-more-used VHD block with TRIM flag, = so that the vhd compression could happend without needing filesystem = semantic? So I'd like to hear from you if you know of anything that could help = trim unused block from VHD files from xenserver dom0. Cheers, keep on the good job, and see you in FOSDEM Denis [1] http://technet.microsoft.com/en-us/library/hh848458.aspx [2] http://support.citrix.com/article/CTX133254 -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 00:14:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 00:14:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3E7Y-0003YL-OO; Wed, 15 Jan 2014 00:14:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3E7X-0003YG-28 for xen-api@lists.xen.org; Wed, 15 Jan 2014 00:14:11 +0000 Received: from [85.158.137.68:21096] by server-11.bemta-3.messagelabs.com id 24/D9-19379-1D2D5D25; Wed, 15 Jan 2014 00:14:09 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1389744847!9120696!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31093 invoked from network); 15 Jan 2014 00:14:09 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 00:14:09 -0000 Received: by mail-pa0-f52.google.com with SMTP id kx10so359350pab.11 for ; Tue, 14 Jan 2014 16:14:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=dkd9878Axqe3UhyD+RbkElSu8PgLrI4jnJxtOFANvSs=; b=Q/cV8H+kTL9s/bqZpUgY/5aSXzXldTPzmHIk+Sy24Q2PA4Fgv3e0GP+qSN8pde8Dcv Gm/xiyPcV9ebesd4fEig7UM9Gd24eyl0I6kI9Q+/ZZdhg74QGVvdGvIM5T25YNNx9PGr ipFfOeRL5a3md0rWw3o3uj766N3qWaetHeqj/QlJy5akE+c28DI6GQ3fUMx9L5Hd5FWJ AudWgi/fZ7wVjzOEEbnfOCxFCsCA9cbu3WM34JrOSEaCbIVAIgukqioNkun6Jw4gzP+j T0I86If3cDe+t/dT7xTNt8u7cWZ0ZPbZJqKUphA/7aVrtSoQUBDcs4QkukwNDkOm2EhY vxOg== X-Gm-Message-State: ALoCoQm2fGuYPTjcsjJLqR6zMk1UKIYe4vZT0poUs4xG4eeiEOkdqtPInBOF7WDCXzZwBfQXHGvx X-Received: by 10.66.65.134 with SMTP id x6mr5001921pas.12.1389744846989; Tue, 14 Jan 2014 16:14:06 -0800 (PST) Received: from [10.101.99.2] ([66.151.128.105]) by mx.google.com with ESMTPSA id ju10sm3816452pbd.33.2014.01.14.16.14.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 16:14:05 -0800 (PST) From: Amit More Message-Id: Date: Tue, 14 Jan 2014 16:14:03 -0800 To: "xen-api@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] Modify Log Facility and Severity X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello All, I have XCP 1.1 running on a Dell PE2950 system with a bunch of following log messages. Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr protect...) exitted with code 0 Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted with code 0 Is there any way I can disable "exitted with code 0" messages from being logged? Any help or advice would be greatly appreciated. Thanks, Amit _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 00:14:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 00:14:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3E7Y-0003YL-OO; Wed, 15 Jan 2014 00:14:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3E7X-0003YG-28 for xen-api@lists.xen.org; Wed, 15 Jan 2014 00:14:11 +0000 Received: from [85.158.137.68:21096] by server-11.bemta-3.messagelabs.com id 24/D9-19379-1D2D5D25; Wed, 15 Jan 2014 00:14:09 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1389744847!9120696!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31093 invoked from network); 15 Jan 2014 00:14:09 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 00:14:09 -0000 Received: by mail-pa0-f52.google.com with SMTP id kx10so359350pab.11 for ; Tue, 14 Jan 2014 16:14:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=dkd9878Axqe3UhyD+RbkElSu8PgLrI4jnJxtOFANvSs=; b=Q/cV8H+kTL9s/bqZpUgY/5aSXzXldTPzmHIk+Sy24Q2PA4Fgv3e0GP+qSN8pde8Dcv Gm/xiyPcV9ebesd4fEig7UM9Gd24eyl0I6kI9Q+/ZZdhg74QGVvdGvIM5T25YNNx9PGr ipFfOeRL5a3md0rWw3o3uj766N3qWaetHeqj/QlJy5akE+c28DI6GQ3fUMx9L5Hd5FWJ AudWgi/fZ7wVjzOEEbnfOCxFCsCA9cbu3WM34JrOSEaCbIVAIgukqioNkun6Jw4gzP+j T0I86If3cDe+t/dT7xTNt8u7cWZ0ZPbZJqKUphA/7aVrtSoQUBDcs4QkukwNDkOm2EhY vxOg== X-Gm-Message-State: ALoCoQm2fGuYPTjcsjJLqR6zMk1UKIYe4vZT0poUs4xG4eeiEOkdqtPInBOF7WDCXzZwBfQXHGvx X-Received: by 10.66.65.134 with SMTP id x6mr5001921pas.12.1389744846989; Tue, 14 Jan 2014 16:14:06 -0800 (PST) Received: from [10.101.99.2] ([66.151.128.105]) by mx.google.com with ESMTPSA id ju10sm3816452pbd.33.2014.01.14.16.14.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 16:14:05 -0800 (PST) From: Amit More Message-Id: Date: Tue, 14 Jan 2014 16:14:03 -0800 To: "xen-api@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [Xen-API] Modify Log Facility and Severity X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello All, I have XCP 1.1 running on a Dell PE2950 system with a bunch of following log messages. Jan 3 06:00:02 vmhost1 fe: 22523 (/etc/xapi.d/plugins/vmpr protect...) exitted with code 0 Jan 3 06:02:44 vmhost1 fe: 22573 (/usr/bin/ovs-vsctl list-br) exitted with code 0 Is there any way I can disable "exitted with code 0" messages from being logged? Any help or advice would be greatly appreciated. Thanks, Amit _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 10:48:52 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 10:48:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3O1b-0001wi-RD; Wed, 15 Jan 2014 10:48:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3O1Z-0001wS-Kx for xen-api@lists.xen.org; Wed, 15 Jan 2014 10:48:42 +0000 Received: from [85.158.137.68:32638] by server-15.bemta-3.messagelabs.com id 2D/AB-11556-88766D25; Wed, 15 Jan 2014 10:48:40 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1389782918!5583151!1 X-Originating-IP: [209.85.128.49] X-SpamReason: No, hits=2.6 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_SUBJECT,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26319 invoked from network); 15 Jan 2014 10:48:39 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 10:48:39 -0000 Received: by mail-qe0-f49.google.com with SMTP id w4so830876qeb.36 for ; Wed, 15 Jan 2014 02:48:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ez17f/1VbEUY3Vynijo4KFLyktYogJf+q8sAPdyNOX8=; b=FMIFwRdbXQpPOsMOvqCu8vJuPNZ1l3ciQRey8jS4JBlroIT5/t3BnJ6j9CDvFloxc7 4rJL1vxCR9XprPg71caTHQUgPSBxdTcj8OyKC3NQKZZfhkW7r8eNqpYWkrWq2Nt/s7R9 qTs+0Uu8R0FpYV+7fuUEpy4eJuXhAkhpxdSfqLKwRwoPM0NN5RXo46p/V1S0xiYbGxes p3mPHNfOpwQswsfeLZPId2WtcWusZvHfzbkuyBqabSvyQTP6mUM0Di2R78z2ja2ft+c+ BLvsiwkTi245w6vQJn+0MYFkgxcFdCaiMaLHhcLmDcao6t7McOpLbn+o+8/0NuEM+b4u bIrA== X-Gm-Message-State: ALoCoQluZ//VWPvmpMWOCP69V26kd1G73AynmgbKhGLbCMkprAQ4WpHh61FmJN2ch23RgNr2s71r MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr3316362qav.4.1389782918487; Wed, 15 Jan 2014 02:48:38 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 15 Jan 2014 02:48:38 -0800 (PST) Date: Wed, 15 Jan 2014 16:18:38 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Subject: [Xen-API] (no subject) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4425163089734679400==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4425163089734679400== Content-Type: multipart/alternative; boundary=089e01493f162c145204f0000dba --089e01493f162c145204f0000dba Content-Type: text/plain; charset=ISO-8859-1 HI all , I have a couple of doubts . How to get the IP of the host using by passing the vm uuid (Is there any API call ?). In a Xen pool Configuration should all the hosts have the same credentials ? Is it possible to get the credentials of all the slave nodes from the master ? Regards, Shafi, Vembu Technologies. --089e01493f162c145204f0000dba Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
HI all ,

I have a =A0couple of doubts .
How= to get the IP of the host using by passing the vm uuid (Is there any API c= all ?).=A0


In a Xen pool Configuration sh= ould all the hosts have the same credentials ?


Is it possible to get the credentials of= all the slave nodes from the master ?


Regards,
Shafi,
Vembu Technologies.<= br>

--089e01493f162c145204f0000dba-- --===============4425163089734679400== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4425163089734679400==-- From xen-api-bounces@lists.xen.org Wed Jan 15 10:48:52 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 10:48:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3O1b-0001wi-RD; Wed, 15 Jan 2014 10:48:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3O1Z-0001wS-Kx for xen-api@lists.xen.org; Wed, 15 Jan 2014 10:48:42 +0000 Received: from [85.158.137.68:32638] by server-15.bemta-3.messagelabs.com id 2D/AB-11556-88766D25; Wed, 15 Jan 2014 10:48:40 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1389782918!5583151!1 X-Originating-IP: [209.85.128.49] X-SpamReason: No, hits=2.6 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_SUBJECT,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26319 invoked from network); 15 Jan 2014 10:48:39 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 10:48:39 -0000 Received: by mail-qe0-f49.google.com with SMTP id w4so830876qeb.36 for ; Wed, 15 Jan 2014 02:48:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ez17f/1VbEUY3Vynijo4KFLyktYogJf+q8sAPdyNOX8=; b=FMIFwRdbXQpPOsMOvqCu8vJuPNZ1l3ciQRey8jS4JBlroIT5/t3BnJ6j9CDvFloxc7 4rJL1vxCR9XprPg71caTHQUgPSBxdTcj8OyKC3NQKZZfhkW7r8eNqpYWkrWq2Nt/s7R9 qTs+0Uu8R0FpYV+7fuUEpy4eJuXhAkhpxdSfqLKwRwoPM0NN5RXo46p/V1S0xiYbGxes p3mPHNfOpwQswsfeLZPId2WtcWusZvHfzbkuyBqabSvyQTP6mUM0Di2R78z2ja2ft+c+ BLvsiwkTi245w6vQJn+0MYFkgxcFdCaiMaLHhcLmDcao6t7McOpLbn+o+8/0NuEM+b4u bIrA== X-Gm-Message-State: ALoCoQluZ//VWPvmpMWOCP69V26kd1G73AynmgbKhGLbCMkprAQ4WpHh61FmJN2ch23RgNr2s71r MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr3316362qav.4.1389782918487; Wed, 15 Jan 2014 02:48:38 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 15 Jan 2014 02:48:38 -0800 (PST) Date: Wed, 15 Jan 2014 16:18:38 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Subject: [Xen-API] (no subject) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4425163089734679400==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4425163089734679400== Content-Type: multipart/alternative; boundary=089e01493f162c145204f0000dba --089e01493f162c145204f0000dba Content-Type: text/plain; charset=ISO-8859-1 HI all , I have a couple of doubts . How to get the IP of the host using by passing the vm uuid (Is there any API call ?). In a Xen pool Configuration should all the hosts have the same credentials ? Is it possible to get the credentials of all the slave nodes from the master ? Regards, Shafi, Vembu Technologies. --089e01493f162c145204f0000dba Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
HI all ,

I have a =A0couple of doubts .
How= to get the IP of the host using by passing the vm uuid (Is there any API c= all ?).=A0


In a Xen pool Configuration sh= ould all the hosts have the same credentials ?


Is it possible to get the credentials of= all the slave nodes from the master ?


Regards,
Shafi,
Vembu Technologies.<= br>

--089e01493f162c145204f0000dba-- --===============4425163089734679400== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4425163089734679400==-- From xen-api-bounces@lists.xen.org Wed Jan 15 13:44:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 13:44:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlK-00030F-TJ; Wed, 15 Jan 2014 13:44:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlJ-000303-LS; Wed, 15 Jan 2014 13:44:05 +0000 Received: from [193.109.254.147:44535] by server-5.bemta-14.messagelabs.com id 0D/44-03510-4A096D25; Wed, 15 Jan 2014 13:44:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1389793444!11043042!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7116 invoked from network); 15 Jan 2014 13:44:04 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 13:44:04 -0000 Received: by mail-wi0-f172.google.com with SMTP id ex4so3355679wid.11 for ; Wed, 15 Jan 2014 05:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8whw3+xWZC/Yq08lhyIWI0l8xIKifE2c2xjfyCk2l5c=; b=UhnqoJuCvmaefP9sLNV/bB/702BBcHsuUIalsVO/q4gxEVHNLV7AtV1F95zOIFMVCR 6kOs7WmbR3IShuiTjvNZ7GcjkCyZw+6V2Ptu1a8n5GadNRuRs4wMxGij/Umk9FxTOkXx H4K2elXNK+R7KKwONAub91+kcWgEiDPSl5tBH5NegQRksfZcGplkwkSrslva6wZSHt2O ISj0HTnq/zM2/UcJUBIVJ9Ww61i9fFzLcgq9imVgFDiv9+TjrePVdnqWiElGCVz0TwtC wrB/oYCgouDp5jU0/jUQSn+2YwVn4w4p6URAFj3ozRPs/02EF2etjTlO22piDPNJojWg LIPA== X-Received: by 10.194.185.205 with SMTP id fe13mr2475541wjc.23.1389793443723; Wed, 15 Jan 2014 05:44:03 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id ot9sm3327688wjc.0.2014.01.15.05.44.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 05:44:02 -0800 (PST) Message-ID: <52D690A1.5060204@xen.org> Date: Wed, 15 Jan 2014 13:44:01 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> Subject: Re: [Xen-API] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I just talked to KB from CentOS about this and we agreed that we don't have enough time to pull this off this time. Both KB and I have too much on our plates right now, to make this happen. Sorry for any inconvenience caused. Regards Lars On 20/12/2013 13:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and > it is possible that we can have some space (including sponsored food) > on the 31st of Jan in Brussells to collaborate with other projects. > If we get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. > Regards > Lars > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 13:44:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 13:44:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlK-00030F-TJ; Wed, 15 Jan 2014 13:44:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlJ-000303-LS; Wed, 15 Jan 2014 13:44:05 +0000 Received: from [193.109.254.147:44535] by server-5.bemta-14.messagelabs.com id 0D/44-03510-4A096D25; Wed, 15 Jan 2014 13:44:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1389793444!11043042!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7116 invoked from network); 15 Jan 2014 13:44:04 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 13:44:04 -0000 Received: by mail-wi0-f172.google.com with SMTP id ex4so3355679wid.11 for ; Wed, 15 Jan 2014 05:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8whw3+xWZC/Yq08lhyIWI0l8xIKifE2c2xjfyCk2l5c=; b=UhnqoJuCvmaefP9sLNV/bB/702BBcHsuUIalsVO/q4gxEVHNLV7AtV1F95zOIFMVCR 6kOs7WmbR3IShuiTjvNZ7GcjkCyZw+6V2Ptu1a8n5GadNRuRs4wMxGij/Umk9FxTOkXx H4K2elXNK+R7KKwONAub91+kcWgEiDPSl5tBH5NegQRksfZcGplkwkSrslva6wZSHt2O ISj0HTnq/zM2/UcJUBIVJ9Ww61i9fFzLcgq9imVgFDiv9+TjrePVdnqWiElGCVz0TwtC wrB/oYCgouDp5jU0/jUQSn+2YwVn4w4p6URAFj3ozRPs/02EF2etjTlO22piDPNJojWg LIPA== X-Received: by 10.194.185.205 with SMTP id fe13mr2475541wjc.23.1389793443723; Wed, 15 Jan 2014 05:44:03 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id ot9sm3327688wjc.0.2014.01.15.05.44.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 05:44:02 -0800 (PST) Message-ID: <52D690A1.5060204@xen.org> Date: Wed, 15 Jan 2014 13:44:01 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> Subject: Re: [Xen-API] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I just talked to KB from CentOS about this and we agreed that we don't have enough time to pull this off this time. Both KB and I have too much on our plates right now, to make this happen. Sorry for any inconvenience caused. Regards Lars On 20/12/2013 13:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and > it is possible that we can have some space (including sponsored food) > on the 31st of Jan in Brussells to collaborate with other projects. > If we get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. > Regards > Lars > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 15:57:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 15:57:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3Sqb-0005ve-JC; Wed, 15 Jan 2014 15:57:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3Sqa-0005v6-Qq for xen-api@lists.xen.org; Wed, 15 Jan 2014 15:57:41 +0000 Received: from [85.158.143.35:48320] by server-3.bemta-4.messagelabs.com id 90/60-32360-4FFA6D25; Wed, 15 Jan 2014 15:57:40 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1389801458!9263524!1 X-Originating-IP: [184.172.38.139] X-SpamReason: No, hits=1.7 required=7.0 tests=BIZ_TLD X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20216 invoked from network); 15 Jan 2014 15:57:39 -0000 Received: from unknown (HELO host1a.ondore-systems.com) (184.172.38.139) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2014 15:57:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ondore.com; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=1IQ9tzIzVMvW2Rz0s/vDUnc42Hz2bH3huPQFsCVHX4M=; b=cqHonz1SPAZBlE4Qp1OuzunkFqoqPoH+n/K6Q23aevOZSG0BGzTwllo3n/ZBS6SKFRTIJiBqIh9+KHxtGtQwWm6EYYgH6Vomj37l3Athw05v1IE1AtnxOfDzV0Vl8ubErKaoISZS6npnDHGmGobQLj9gtBWRsSub/0ai5cqvDy8=; Received: from [189.253.158.196] (port=57356 helo=mail.ondore.i) by host1a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1W3Sq9-0000nn-W4 for xen-api@lists.xen.org; Wed, 15 Jan 2014 09:57:14 -0600 Received: from [10.13.37.245] (alk-desktop.adm.ondore.i [10.13.37.245]) by mail.ondore.i (Postfix) with ESMTPSA id CFF48A20D for ; Wed, 15 Jan 2014 09:57:12 -0600 (CST) Message-ID: <52D6AFD8.6060504@ondore.com> Date: Wed, 15 Jan 2014 09:57:12 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host1a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host1a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Login credential in XCP Pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. (please consider using a descriptive Subject in your mails) El 15/01/14 04:48, Shafi Mohammed S escribi=F3: > How to get the IP of the host using by passing the vm uuid (Is there any > API call ?). No general way. http://www.cyberciti.biz/tips/linux-xen-server-vps-monitoring-commands.html= #comment-147046 > In a Xen pool Configuration should all the hosts have the same credential= s ? Before a new host has joined a pool, it's root password may be whatever = you wish. When it joins the pool, it's root password is overwritten and = becomes the same as the pool master's root password. Normally, while = configuring a pool, there is no need to do anything special about root's = password. If you wish to change root password of the hosts already in pool, it's = recommended to do that via XenCenter GUI, this way the password will be = synced across all the pool members. > Is it possible to get the credentials of all the slave nodes from the > master ? By design, there is no direct way to extract plain login credentials = (user and password) from a Linux system, doing it locally or remotely. = This also apply to XCP and XenServer. If you meant something else in you = question, please re-formulate. Greetings. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 15:57:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 15:57:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3Sqb-0005ve-JC; Wed, 15 Jan 2014 15:57:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3Sqa-0005v6-Qq for xen-api@lists.xen.org; Wed, 15 Jan 2014 15:57:41 +0000 Received: from [85.158.143.35:48320] by server-3.bemta-4.messagelabs.com id 90/60-32360-4FFA6D25; Wed, 15 Jan 2014 15:57:40 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1389801458!9263524!1 X-Originating-IP: [184.172.38.139] X-SpamReason: No, hits=1.7 required=7.0 tests=BIZ_TLD X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20216 invoked from network); 15 Jan 2014 15:57:39 -0000 Received: from unknown (HELO host1a.ondore-systems.com) (184.172.38.139) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2014 15:57:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ondore.com; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=1IQ9tzIzVMvW2Rz0s/vDUnc42Hz2bH3huPQFsCVHX4M=; b=cqHonz1SPAZBlE4Qp1OuzunkFqoqPoH+n/K6Q23aevOZSG0BGzTwllo3n/ZBS6SKFRTIJiBqIh9+KHxtGtQwWm6EYYgH6Vomj37l3Athw05v1IE1AtnxOfDzV0Vl8ubErKaoISZS6npnDHGmGobQLj9gtBWRsSub/0ai5cqvDy8=; Received: from [189.253.158.196] (port=57356 helo=mail.ondore.i) by host1a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1W3Sq9-0000nn-W4 for xen-api@lists.xen.org; Wed, 15 Jan 2014 09:57:14 -0600 Received: from [10.13.37.245] (alk-desktop.adm.ondore.i [10.13.37.245]) by mail.ondore.i (Postfix) with ESMTPSA id CFF48A20D for ; Wed, 15 Jan 2014 09:57:12 -0600 (CST) Message-ID: <52D6AFD8.6060504@ondore.com> Date: Wed, 15 Jan 2014 09:57:12 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host1a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host1a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Login credential in XCP Pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. (please consider using a descriptive Subject in your mails) El 15/01/14 04:48, Shafi Mohammed S escribi=F3: > How to get the IP of the host using by passing the vm uuid (Is there any > API call ?). No general way. http://www.cyberciti.biz/tips/linux-xen-server-vps-monitoring-commands.html= #comment-147046 > In a Xen pool Configuration should all the hosts have the same credential= s ? Before a new host has joined a pool, it's root password may be whatever = you wish. When it joins the pool, it's root password is overwritten and = becomes the same as the pool master's root password. Normally, while = configuring a pool, there is no need to do anything special about root's = password. If you wish to change root password of the hosts already in pool, it's = recommended to do that via XenCenter GUI, this way the password will be = synced across all the pool members. > Is it possible to get the credentials of all the slave nodes from the > master ? By design, there is no direct way to extract plain login credentials = (user and password) from a Linux system, doing it locally or remotely. = This also apply to XCP and XenServer. If you meant something else in you = question, please re-formulate. Greetings. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 16:11:42 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 16:11:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3T49-0007XN-DI; Wed, 15 Jan 2014 16:11:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3T47-0007X5-Il; Wed, 15 Jan 2014 16:11:39 +0000 Received: from [193.109.254.147:49997] by server-8.bemta-14.messagelabs.com id D7/4F-30921-A33B6D25; Wed, 15 Jan 2014 16:11:38 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389802297!11013005!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14088 invoked from network); 15 Jan 2014 16:11:37 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 16:11:37 -0000 Received: by mail-la0-f41.google.com with SMTP id mc6so1572050lab.14 for ; Wed, 15 Jan 2014 08:11:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=l1njGk/LszfPhbnS+kcUlN+EoCsuOfdEK52e/qTjze8=; b=nJy5y0PRviKm3yt+d32kCo7/310hyOev4eP9pX1WagCe3rxTs+4AsHxQM5eshdcdFG a5fL4mXD4AMyVx4spbKwT9ZwqnX75Y7FJtlsfnhCwtXBwCqqHD/sF8S5pRPpZRL3E1RY h6Si/2EX1LHl+bbuwu1tdHvpFoKxquCWWxHb70buE90/ZGgBEN1e4jWMcHIpYTMjdA8Y tnvusffVt4AHc3yqxpyOiUHWeMkutIR/mU6nY4Ac0qVAHpdWEhAhsKCgRn3T+f55yPoN w/L67hS3R70nVTBPKQr68uYLE16S65z7adqzJnl2MGtCdZc7Q9dwj5lV+A+P3H/BtyZ1 pzdQ== MIME-Version: 1.0 X-Received: by 10.112.139.72 with SMTP id qw8mr1965072lbb.16.1389802292853; Wed, 15 Jan 2014 08:11:32 -0800 (PST) Received: by 10.112.184.16 with HTTP; Wed, 15 Jan 2014 08:11:32 -0800 (PST) Date: Wed, 15 Jan 2014 11:11:32 -0500 X-Google-Sender-Auth: 8TgF-0cOYRoyEzJ5HwQzJv2uR-Q Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] Reminder: Next Xen Project Document Day is Monday, January 27 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Please mark your calendars that the next Xen Project Document Day will be held on the final Monday of the month, January 27. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xen.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on January 27! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 15 16:11:42 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 15 Jan 2014 16:11:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3T49-0007XN-DI; Wed, 15 Jan 2014 16:11:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3T47-0007X5-Il; Wed, 15 Jan 2014 16:11:39 +0000 Received: from [193.109.254.147:49997] by server-8.bemta-14.messagelabs.com id D7/4F-30921-A33B6D25; Wed, 15 Jan 2014 16:11:38 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389802297!11013005!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14088 invoked from network); 15 Jan 2014 16:11:37 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 16:11:37 -0000 Received: by mail-la0-f41.google.com with SMTP id mc6so1572050lab.14 for ; Wed, 15 Jan 2014 08:11:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=l1njGk/LszfPhbnS+kcUlN+EoCsuOfdEK52e/qTjze8=; b=nJy5y0PRviKm3yt+d32kCo7/310hyOev4eP9pX1WagCe3rxTs+4AsHxQM5eshdcdFG a5fL4mXD4AMyVx4spbKwT9ZwqnX75Y7FJtlsfnhCwtXBwCqqHD/sF8S5pRPpZRL3E1RY h6Si/2EX1LHl+bbuwu1tdHvpFoKxquCWWxHb70buE90/ZGgBEN1e4jWMcHIpYTMjdA8Y tnvusffVt4AHc3yqxpyOiUHWeMkutIR/mU6nY4Ac0qVAHpdWEhAhsKCgRn3T+f55yPoN w/L67hS3R70nVTBPKQr68uYLE16S65z7adqzJnl2MGtCdZc7Q9dwj5lV+A+P3H/BtyZ1 pzdQ== MIME-Version: 1.0 X-Received: by 10.112.139.72 with SMTP id qw8mr1965072lbb.16.1389802292853; Wed, 15 Jan 2014 08:11:32 -0800 (PST) Received: by 10.112.184.16 with HTTP; Wed, 15 Jan 2014 08:11:32 -0800 (PST) Date: Wed, 15 Jan 2014 11:11:32 -0500 X-Google-Sender-Auth: 8TgF-0cOYRoyEzJ5HwQzJv2uR-Q Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] Reminder: Next Xen Project Document Day is Monday, January 27 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Please mark your calendars that the next Xen Project Document Day will be held on the final Monday of the month, January 27. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xen.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on January 27! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 03:50:28 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 03:50:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3dyA-0004Og-Fb; Thu, 16 Jan 2014 03:50:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3dy9-0004Ob-0q for xen-api@lists.xen.org; Thu, 16 Jan 2014 03:50:13 +0000 Received: from [85.158.139.211:30007] by server-13.bemta-5.messagelabs.com id 98/EC-11357-4F657D25; Thu, 16 Jan 2014 03:50:12 +0000 X-Env-Sender: fgaudreault@cloudops.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1389844210!8820219!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4631 invoked from network); 16 Jan 2014 03:50:11 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 03:50:11 -0000 Received: by mail-qa0-f50.google.com with SMTP id cm18so1694148qab.37 for ; Wed, 15 Jan 2014 19:50:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=vP5LtmzTpJ3bvBKD0Nx3MM5ToTiv27Rua7PhGZ9VNUE=; b=Uuh3EMWrvWGEd0CGuphGs3WLrD9jJGGGO80WnBKK1tuCFH+DYmRxBOaeMR3OFhqmVt TPZ9tLQWqJXvtj7vfIsCbZ9YZkrnPqrZkDGS8cjOM2PxzJpf316749REviaRBv6pbMhj jM4Gpzz62u6wxaP3rP+hrUTFBa/0HZ7FMWJuYlo7AXAbCzYMENJM7JuIadxcCSuB+Wft TDNZnpmaORvSf6lPzEk2S9y6pSyjH4ao8lsBq1cM4aW0XawlKApRsNZMs71V6HPpgIFw iOdfI1WbYg+j5DY9qWdQpZft6qL5Q22GKrL1O6m6bQ4Zwkl6BEenMRKDYrqseX1rN11O JllA== X-Gm-Message-State: ALoCoQkR+0HxDnzmqodzJt6RYMX7ptbg3cjM2+0z1CN1cp8cDtvuAFCbifFUXRyTH4TYTdDI9Ole X-Received: by 10.140.83.112 with SMTP id i103mr4070677qgd.100.1389844209796; Wed, 15 Jan 2014 19:50:09 -0800 (PST) Received: from Francoiss-MacBook-Pro-3.local ([67.68.158.90]) by mx.google.com with ESMTPSA id b3sm10339104qeh.17.2014.01.15.19.50.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 19:50:09 -0800 (PST) Message-ID: <52D756EF.6090807@cloudops.com> Date: Wed, 15 Jan 2014 22:50:07 -0500 From: Francois Gaudreault User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Trying to compile xapi on fedora X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: fgaudreault@cloudops.com List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I am trying to compile xapi on fedora 20, but I can't make it work. I = have couple issues, especially with libvhd 0.9.1. For some reason, = xen-devel doesn't contains the libvhd headers, so I had to pull them = from source. I tried with opam, with the xenserver provided spec, no luck. Here are = the errors I get: http://pastebin.com/S0CAynqa message_switch also failed: # File "core/protocol_lwt.ml", line 79, characters 40-42: # Error: Signature mismatch: # ... # The field `flush' is required but not provided # Command exited with code 2. As well as xenctrl: ### stdout ### # ...[truncated] # xenlight/xenlight_stubs.c:2790:12: warning: =91sched_credit_params_val=92 = defined but not used [-Wunused-function] # static int sched_credit_params_val (libxl_ctx *ctx, = libxl_sched_credit_params *c_val, value v) # ^ # xenlight/xenlight_stubs.c:2831:12: warning: =91domain_remus_info_val=92 = defined but not used [-Wunused-function] # static int domain_remus_info_val (libxl_ctx *ctx, = libxl_domain_remus_info *c_val, value v) # ^ # xenlight/xenlight_stubs.c:2909:12: warning: =91event_val=92 defined but = not used [-Wunused-function] # static int event_val (libxl_ctx *ctx, libxl_event *c_val, value v) # ^ # Command exited with code 2. ### stderr ### # Makefile:6: config.mk: No such file or directory Am I doing something wrong? Anyone can shed some lights on how to make = this work on fedora 20? -- = Francois Gaudreault Architecte de Solution Cloud | Cloud Solutions Architect fgaudreault@cloudops.com 514-629-6775 - - - CloudOps 420 rue Guy Montr=E9al QC H3J 1S6 www.cloudops.com @CloudOps_ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 03:50:28 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 03:50:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3dyA-0004Og-Fb; Thu, 16 Jan 2014 03:50:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3dy9-0004Ob-0q for xen-api@lists.xen.org; Thu, 16 Jan 2014 03:50:13 +0000 Received: from [85.158.139.211:30007] by server-13.bemta-5.messagelabs.com id 98/EC-11357-4F657D25; Thu, 16 Jan 2014 03:50:12 +0000 X-Env-Sender: fgaudreault@cloudops.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1389844210!8820219!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4631 invoked from network); 16 Jan 2014 03:50:11 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 03:50:11 -0000 Received: by mail-qa0-f50.google.com with SMTP id cm18so1694148qab.37 for ; Wed, 15 Jan 2014 19:50:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=vP5LtmzTpJ3bvBKD0Nx3MM5ToTiv27Rua7PhGZ9VNUE=; b=Uuh3EMWrvWGEd0CGuphGs3WLrD9jJGGGO80WnBKK1tuCFH+DYmRxBOaeMR3OFhqmVt TPZ9tLQWqJXvtj7vfIsCbZ9YZkrnPqrZkDGS8cjOM2PxzJpf316749REviaRBv6pbMhj jM4Gpzz62u6wxaP3rP+hrUTFBa/0HZ7FMWJuYlo7AXAbCzYMENJM7JuIadxcCSuB+Wft TDNZnpmaORvSf6lPzEk2S9y6pSyjH4ao8lsBq1cM4aW0XawlKApRsNZMs71V6HPpgIFw iOdfI1WbYg+j5DY9qWdQpZft6qL5Q22GKrL1O6m6bQ4Zwkl6BEenMRKDYrqseX1rN11O JllA== X-Gm-Message-State: ALoCoQkR+0HxDnzmqodzJt6RYMX7ptbg3cjM2+0z1CN1cp8cDtvuAFCbifFUXRyTH4TYTdDI9Ole X-Received: by 10.140.83.112 with SMTP id i103mr4070677qgd.100.1389844209796; Wed, 15 Jan 2014 19:50:09 -0800 (PST) Received: from Francoiss-MacBook-Pro-3.local ([67.68.158.90]) by mx.google.com with ESMTPSA id b3sm10339104qeh.17.2014.01.15.19.50.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 19:50:09 -0800 (PST) Message-ID: <52D756EF.6090807@cloudops.com> Date: Wed, 15 Jan 2014 22:50:07 -0500 From: Francois Gaudreault User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Trying to compile xapi on fedora X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: fgaudreault@cloudops.com List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I am trying to compile xapi on fedora 20, but I can't make it work. I = have couple issues, especially with libvhd 0.9.1. For some reason, = xen-devel doesn't contains the libvhd headers, so I had to pull them = from source. I tried with opam, with the xenserver provided spec, no luck. Here are = the errors I get: http://pastebin.com/S0CAynqa message_switch also failed: # File "core/protocol_lwt.ml", line 79, characters 40-42: # Error: Signature mismatch: # ... # The field `flush' is required but not provided # Command exited with code 2. As well as xenctrl: ### stdout ### # ...[truncated] # xenlight/xenlight_stubs.c:2790:12: warning: =91sched_credit_params_val=92 = defined but not used [-Wunused-function] # static int sched_credit_params_val (libxl_ctx *ctx, = libxl_sched_credit_params *c_val, value v) # ^ # xenlight/xenlight_stubs.c:2831:12: warning: =91domain_remus_info_val=92 = defined but not used [-Wunused-function] # static int domain_remus_info_val (libxl_ctx *ctx, = libxl_domain_remus_info *c_val, value v) # ^ # xenlight/xenlight_stubs.c:2909:12: warning: =91event_val=92 defined but = not used [-Wunused-function] # static int event_val (libxl_ctx *ctx, libxl_event *c_val, value v) # ^ # Command exited with code 2. ### stderr ### # Makefile:6: config.mk: No such file or directory Am I doing something wrong? Anyone can shed some lights on how to make = this work on fedora 20? -- = Francois Gaudreault Architecte de Solution Cloud | Cloud Solutions Architect fgaudreault@cloudops.com 514-629-6775 - - - CloudOps 420 rue Guy Montr=E9al QC H3J 1S6 www.cloudops.com @CloudOps_ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 07:49:33 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 07:49:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3hhX-0007XL-JL; Thu, 16 Jan 2014 07:49:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3hhU-0007Uf-Fv for xen-api@lists.xen.org; Thu, 16 Jan 2014 07:49:16 +0000 Received: from [85.158.137.68:13316] by server-13.bemta-3.messagelabs.com id 96/C5-28603-BFE87D25; Thu, 16 Jan 2014 07:49:15 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1389858552!9397803!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=2.6 required=7.0 tests=BIZ_TLD,HTML_40_50, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25003 invoked from network); 16 Jan 2014 07:49:13 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 07:49:13 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so2031870qcy.12 for ; Wed, 15 Jan 2014 23:49:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iQxcl3+3x1SaJRCxlD3eQGkZJzcxVcvM32JQmCuiN2o=; b=jkcqNM8+XF7H72XLYQXLUnD+OBZduo7ow+Yp/28mZS6QEa0jaDrVDfgL2SUf9rO7TF FbKRWyb9/bOINuxVqqFFRZtBmc9ZbsFV6LTc2IzP5FIJOzEf7BAjx7yTWPnUgZHyXBmr c2W6v9NivEithbH9XX9Df4xKouShzbBDjk+NapUFwTCF9FOPRCR2Au2EhRvbzWHH51yC If6DaFk1XRcOsFtex89qn27dW1jtDmFd6bVtpE4X4Aw741m1Q/ld/zZltW8iKkYLsmvP LyiUvLdvQ7NLPhqGZxdbs1HFKHesvu7svPahptEvuySXBZyuYh94PQpyqrDo4e5miY4r cAFA== X-Gm-Message-State: ALoCoQl/gLD4hzV/QWFBMFeyms7+fMru127yqLD4G51N8K+a9GvzyPuQbXo1EXNf8aJhFwkD+lks MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr13216619qav.4.1389858552670; Wed, 15 Jan 2014 23:49:12 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 15 Jan 2014 23:49:12 -0800 (PST) In-Reply-To: <52D6AFD8.6060504@ondore.com> References: <52D6AFD8.6060504@ondore.com> Date: Thu, 16 Jan 2014 13:19:12 +0530 Message-ID: From: Shafi Mohammed S To: Alexandre Kouznetsov Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Login credential in XCP Pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6194386057507458557==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6194386057507458557== Content-Type: multipart/alternative; boundary=089e01493f1651fdc504f011a9b9 --089e01493f1651fdc504f011a9b9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Alexandre , Thanks a lot for the Info . But I tried changing the password of the slave node through its CLI once it has been added to the pool . Now the Master and the slave nodes are having different credentials . Thanks , Regards, Shafi, Vembu Technologies. On Wed, Jan 15, 2014 at 9:27 PM, Alexandre Kouznetsov wrote= : > Hello. > > (please consider using a descriptive Subject in your mails) > > El 15/01/14 04:48, Shafi Mohammed S escribi=F3: > >> How to get the IP of the host using by passing the vm uuid (Is there any >> API call ?). >> > No general way. > http://www.cyberciti.biz/tips/linux-xen-server-vps- > monitoring-commands.html#comment-147046 > > In a Xen pool Configuration should all the hosts have the same >> credentials ? >> > Before a new host has joined a pool, it's root password may be whatever > you wish. When it joins the pool, it's root password is overwritten and > becomes the same as the pool master's root password. Normally, while > configuring a pool, there is no need to do anything special about root's > password. > If you wish to change root password of the hosts already in pool, it's > recommended to do that via XenCenter GUI, this way the password will be > synced across all the pool members. > > Is it possible to get the credentials of all the slave nodes from the >> master ? >> > By design, there is no direct way to extract plain login credentials (use= r > and password) from a Linux system, doing it locally or remotely. This als= o > apply to XCP and XenServer. If you meant something else in you question, > please re-formulate. > > Greetings. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --089e01493f1651fdc504f011a9b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
=A0Hi Alexandre ,

=A0 Thanks a lot for the Info . B= ut I tried changing the password of the slave node through its CLI once it = has been added to the pool . Now the Master and the slave nodes are having = different credentials .

Thanks ,

Regards,
Shafi,
Vembu Technologies.



On Wed, Jan 15, 2014 at 9:27 PM, Alexand= re Kouznetsov <alk@ondore.com> wrote:
Hello.

(please consider using a descriptive Subject in your mails)

El 15/01/14 04:48, Shafi Mohammed S escribi=F3:
How to get the IP of the host using by passing the vm uuid (Is there any API call ?).
No general way.
http://www.cyberciti.biz/tips= /linux-xen-server-vps-monitoring-commands.html#comment= -147046

In a Xen pool Configuration should all the hosts have the same credentials = ?
Before a new host has joined a pool, it's root password may be whatever= you wish. When it joins the pool, it's root password is overwritten an= d becomes the same as the pool master's root password. Normally, while = configuring a pool, there is no need to do anything special about root'= s password.
If you wish to change root password of the hosts already in pool, it's = recommended to do that via XenCenter GUI, this way the password will be syn= ced across all the pool members.

Is it possible to get the credentials of all the slave nodes from the
master ?
By design, there is no direct way to extract plain login credentials (user = and password) from a Linux system, doing it locally or remotely. This also = apply to XCP and XenServer. If you meant something else in you question, pl= ease re-formulate.

Greetings.

--
Alexandre Kouznetsov


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--089e01493f1651fdc504f011a9b9-- --===============6194386057507458557== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6194386057507458557==-- From xen-api-bounces@lists.xen.org Thu Jan 16 07:49:33 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 07:49:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3hhX-0007XL-JL; Thu, 16 Jan 2014 07:49:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3hhU-0007Uf-Fv for xen-api@lists.xen.org; Thu, 16 Jan 2014 07:49:16 +0000 Received: from [85.158.137.68:13316] by server-13.bemta-3.messagelabs.com id 96/C5-28603-BFE87D25; Thu, 16 Jan 2014 07:49:15 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1389858552!9397803!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=2.6 required=7.0 tests=BIZ_TLD,HTML_40_50, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25003 invoked from network); 16 Jan 2014 07:49:13 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 07:49:13 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so2031870qcy.12 for ; Wed, 15 Jan 2014 23:49:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iQxcl3+3x1SaJRCxlD3eQGkZJzcxVcvM32JQmCuiN2o=; b=jkcqNM8+XF7H72XLYQXLUnD+OBZduo7ow+Yp/28mZS6QEa0jaDrVDfgL2SUf9rO7TF FbKRWyb9/bOINuxVqqFFRZtBmc9ZbsFV6LTc2IzP5FIJOzEf7BAjx7yTWPnUgZHyXBmr c2W6v9NivEithbH9XX9Df4xKouShzbBDjk+NapUFwTCF9FOPRCR2Au2EhRvbzWHH51yC If6DaFk1XRcOsFtex89qn27dW1jtDmFd6bVtpE4X4Aw741m1Q/ld/zZltW8iKkYLsmvP LyiUvLdvQ7NLPhqGZxdbs1HFKHesvu7svPahptEvuySXBZyuYh94PQpyqrDo4e5miY4r cAFA== X-Gm-Message-State: ALoCoQl/gLD4hzV/QWFBMFeyms7+fMru127yqLD4G51N8K+a9GvzyPuQbXo1EXNf8aJhFwkD+lks MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr13216619qav.4.1389858552670; Wed, 15 Jan 2014 23:49:12 -0800 (PST) Received: by 10.140.49.174 with HTTP; Wed, 15 Jan 2014 23:49:12 -0800 (PST) In-Reply-To: <52D6AFD8.6060504@ondore.com> References: <52D6AFD8.6060504@ondore.com> Date: Thu, 16 Jan 2014 13:19:12 +0530 Message-ID: From: Shafi Mohammed S To: Alexandre Kouznetsov Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Login credential in XCP Pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6194386057507458557==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6194386057507458557== Content-Type: multipart/alternative; boundary=089e01493f1651fdc504f011a9b9 --089e01493f1651fdc504f011a9b9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Alexandre , Thanks a lot for the Info . But I tried changing the password of the slave node through its CLI once it has been added to the pool . Now the Master and the slave nodes are having different credentials . Thanks , Regards, Shafi, Vembu Technologies. On Wed, Jan 15, 2014 at 9:27 PM, Alexandre Kouznetsov wrote= : > Hello. > > (please consider using a descriptive Subject in your mails) > > El 15/01/14 04:48, Shafi Mohammed S escribi=F3: > >> How to get the IP of the host using by passing the vm uuid (Is there any >> API call ?). >> > No general way. > http://www.cyberciti.biz/tips/linux-xen-server-vps- > monitoring-commands.html#comment-147046 > > In a Xen pool Configuration should all the hosts have the same >> credentials ? >> > Before a new host has joined a pool, it's root password may be whatever > you wish. When it joins the pool, it's root password is overwritten and > becomes the same as the pool master's root password. Normally, while > configuring a pool, there is no need to do anything special about root's > password. > If you wish to change root password of the hosts already in pool, it's > recommended to do that via XenCenter GUI, this way the password will be > synced across all the pool members. > > Is it possible to get the credentials of all the slave nodes from the >> master ? >> > By design, there is no direct way to extract plain login credentials (use= r > and password) from a Linux system, doing it locally or remotely. This als= o > apply to XCP and XenServer. If you meant something else in you question, > please re-formulate. > > Greetings. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --089e01493f1651fdc504f011a9b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
=A0Hi Alexandre ,

=A0 Thanks a lot for the Info . B= ut I tried changing the password of the slave node through its CLI once it = has been added to the pool . Now the Master and the slave nodes are having = different credentials .

Thanks ,

Regards,
Shafi,
Vembu Technologies.



On Wed, Jan 15, 2014 at 9:27 PM, Alexand= re Kouznetsov <alk@ondore.com> wrote:
Hello.

(please consider using a descriptive Subject in your mails)

El 15/01/14 04:48, Shafi Mohammed S escribi=F3:
How to get the IP of the host using by passing the vm uuid (Is there any API call ?).
No general way.
http://www.cyberciti.biz/tips= /linux-xen-server-vps-monitoring-commands.html#comment= -147046

In a Xen pool Configuration should all the hosts have the same credentials = ?
Before a new host has joined a pool, it's root password may be whatever= you wish. When it joins the pool, it's root password is overwritten an= d becomes the same as the pool master's root password. Normally, while = configuring a pool, there is no need to do anything special about root'= s password.
If you wish to change root password of the hosts already in pool, it's = recommended to do that via XenCenter GUI, this way the password will be syn= ced across all the pool members.

Is it possible to get the credentials of all the slave nodes from the
master ?
By design, there is no direct way to extract plain login credentials (user = and password) from a Linux system, doing it locally or remotely. This also = apply to XCP and XenServer. If you meant something else in you question, pl= ease re-formulate.

Greetings.

--
Alexandre Kouznetsov


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--089e01493f1651fdc504f011a9b9-- --===============6194386057507458557== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6194386057507458557==-- From xen-api-bounces@lists.xen.org Thu Jan 16 11:28:52 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 11:28:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3l7p-0007Kh-JJ; Thu, 16 Jan 2014 11:28:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3l7o-0007KL-Bv; Thu, 16 Jan 2014 11:28:40 +0000 Received: from [85.158.139.211:50125] by server-15.bemta-5.messagelabs.com id 94/EA-08490-762C7D25; Thu, 16 Jan 2014 11:28:39 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1389871718!10119819!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22880 invoked from network); 16 Jan 2014 11:28:38 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 11:28:38 -0000 Received: by mail-lb0-f180.google.com with SMTP id n15so1746666lbi.25 for ; Thu, 16 Jan 2014 03:28:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=/3NBddMFWKbty/jJvL2z6kbrEszi1Zvngj6QJLhggEc=; b=UA6jdcgbQ1/+BgYRD9nObxkSXGxuvNDrEIwNUiDb/IfzieTEABcVNc8mchcQKVDDQ5 P39tFkYV49/icakDgrJEsAEHN/uwJQu/bb8R5isxG241ZUYYZe5o+6l0UMthxD6SF8w3 8W7zRJ44rKRtcLlpNMQeAMnRp/yFZuG3KHGiq3MJHlWMFwDUX5j6C1lMmZWNtI33XHn+ rjJSo3VW+UfTJj5kShx2PWwADXZc7JZmtR6gmfjWcfdOHSSeGYEv0sZb2XkKm9qb0MM/ pRcA8wpAwc6Jz3XwjIsYniowLT4+Z13H9Xh6g6OYfxFvz/ZZuINKctjgIts4ZiBDdzjW CkEw== MIME-Version: 1.0 X-Received: by 10.152.42.230 with SMTP id r6mr4983104lal.18.1389871717815; Thu, 16 Jan 2014 03:28:37 -0800 (PST) Received: by 10.112.184.16 with HTTP; Thu, 16 Jan 2014 03:28:37 -0800 (PST) Date: Thu, 16 Jan 2014 06:28:37 -0500 X-Google-Sender-Auth: Hlbaitrbqxkc9fOt8bRdiaoWCCk Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, publicity@lists.xenproject.org Subject: [Xen-API] Xen Project Test Day: Test 4.4 RC2 on January 20 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Release time is approaching, so Test Days have arrived! On Monday, January 20, we are holding a Test Day for Xen 4.4. Release Candidate 2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC2, we need to know about it and how to test it. Either edit the instructions page or send me a few lines describing the feature and how it should be tested. Right now, RC2 is labelled a general test (e.g., "Does Xen compile, install, and do the things Xen normally does?"). We don't have any specific tests of new functionality identified. If you have something new which needs testing in RC2, we need to know about it. EVERYONE: Please join us on Monday, January 20, and help make sure the next release of Xen is the best one yet! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 11:28:52 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 11:28:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3l7p-0007Kh-JJ; Thu, 16 Jan 2014 11:28:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3l7o-0007KL-Bv; Thu, 16 Jan 2014 11:28:40 +0000 Received: from [85.158.139.211:50125] by server-15.bemta-5.messagelabs.com id 94/EA-08490-762C7D25; Thu, 16 Jan 2014 11:28:39 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1389871718!10119819!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22880 invoked from network); 16 Jan 2014 11:28:38 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 11:28:38 -0000 Received: by mail-lb0-f180.google.com with SMTP id n15so1746666lbi.25 for ; Thu, 16 Jan 2014 03:28:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=/3NBddMFWKbty/jJvL2z6kbrEszi1Zvngj6QJLhggEc=; b=UA6jdcgbQ1/+BgYRD9nObxkSXGxuvNDrEIwNUiDb/IfzieTEABcVNc8mchcQKVDDQ5 P39tFkYV49/icakDgrJEsAEHN/uwJQu/bb8R5isxG241ZUYYZe5o+6l0UMthxD6SF8w3 8W7zRJ44rKRtcLlpNMQeAMnRp/yFZuG3KHGiq3MJHlWMFwDUX5j6C1lMmZWNtI33XHn+ rjJSo3VW+UfTJj5kShx2PWwADXZc7JZmtR6gmfjWcfdOHSSeGYEv0sZb2XkKm9qb0MM/ pRcA8wpAwc6Jz3XwjIsYniowLT4+Z13H9Xh6g6OYfxFvz/ZZuINKctjgIts4ZiBDdzjW CkEw== MIME-Version: 1.0 X-Received: by 10.152.42.230 with SMTP id r6mr4983104lal.18.1389871717815; Thu, 16 Jan 2014 03:28:37 -0800 (PST) Received: by 10.112.184.16 with HTTP; Thu, 16 Jan 2014 03:28:37 -0800 (PST) Date: Thu, 16 Jan 2014 06:28:37 -0500 X-Google-Sender-Auth: Hlbaitrbqxkc9fOt8bRdiaoWCCk Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, publicity@lists.xenproject.org Subject: [Xen-API] Xen Project Test Day: Test 4.4 RC2 on January 20 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Release time is approaching, so Test Days have arrived! On Monday, January 20, we are holding a Test Day for Xen 4.4. Release Candidate 2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC2, we need to know about it and how to test it. Either edit the instructions page or send me a few lines describing the feature and how it should be tested. Right now, RC2 is labelled a general test (e.g., "Does Xen compile, install, and do the things Xen normally does?"). We don't have any specific tests of new functionality identified. If you have something new which needs testing in RC2, we need to know about it. EVERYONE: Please join us on Monday, January 20, and help make sure the next release of Xen is the best one yet! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 19:39:51 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 19:39:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3sn0-0007O9-41; Thu, 16 Jan 2014 19:39:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3smy-0007Ns-W0; Thu, 16 Jan 2014 19:39:41 +0000 Received: from [193.109.254.147:32491] by server-11.bemta-14.messagelabs.com id D2/60-20576-C7538D25; Thu, 16 Jan 2014 19:39:40 +0000 X-Env-Sender: jesse.benedict@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389901177!11310746!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6905 invoked from network); 16 Jan 2014 19:39:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 19:39:39 -0000 X-IronPort-AV: E=Sophos;i="4.95,669,1384300800"; d="scan'208";a="93621470" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 16 Jan 2014 19:39:10 +0000 Received: from FTLPEX01CL02.citrite.net ([169.254.2.8]) by FTLPEX01CL03.citrite.net ([169.254.1.174]) with mapi id 14.02.0342.004; Thu, 16 Jan 2014 14:39:10 -0500 From: Jesse Benedict To: 'Russ Pavlicek' , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xs-devel@lists.xenserver.org" , "cl-mirage@lists.cam.ac.uk" , "publicity@lists.xenproject.org" Thread-Topic: [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 Thread-Index: AQHPErDL+s+s1Grh7UyexLHJALpZMpqHv8Vw Date: Thu, 16 Jan 2014 19:39:10 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.11.24.188] MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-API] [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Count me in, sir! I will review the links you have provided! Sincerely, Jesse Benedict, CCA | Citrix, Inc. | XenServer, XenClient Support Team Work Better. Live Better. Call us at 1-800-4CITRIX! Join the Community: support.citrix.com | discussions.citrix.com | blogs.citrix.com | taas.citrix.com Customer Satisfaction is our goal. If you have feedback regarding my performance, please feel free to contact my Manager william.aycock@citrix.com CONFIDENTIALITY NOTICE This e-mail message and all documents which accompany it are intended only for the use of the individual or entity to which addressed, and may contain privileged or confidential information. Any unauthorized disclosure or distribution of this e-mail message is prohibited. Any private files or utilities that are included in this e-mail are intended only for the use of the individual or entity to which this is addressed and distribution of these files or utilities is prohibited. If you have received this e-mail message in error, please notify me immediately. Thank you. -----Original Message----- From: russell.pavlicek.xen@gmail.com [mailto:russell.pavlicek.xen@gmail.com] On Behalf Of Russ Pavlicek Sent: Thursday, January 16, 2014 6:29 AM To: xen-devel@lists.xen.org; xen-users@lists.xen.org; xen-api@lists.xen.org; xs-devel@lists.xenserver.org; cl-mirage@lists.cam.ac.uk; publicity@lists.xenproject.org Subject: [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 Release time is approaching, so Test Days have arrived! On Monday, January 20, we are holding a Test Day for Xen 4.4. Release Candidate 2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC2, we need to know about it and how to test it. Either edit the instructions page or send me a few lines describing the feature and how it should be tested. Right now, RC2 is labelled a general test (e.g., "Does Xen compile, install, and do the things Xen normally does?"). We don't have any specific tests of new functionality identified. If you have something new which needs testing in RC2, we need to know about it. EVERYONE: Please join us on Monday, January 20, and help make sure the next release of Xen is the best one yet! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 19:39:51 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 19:39:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3sn0-0007O9-41; Thu, 16 Jan 2014 19:39:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3smy-0007Ns-W0; Thu, 16 Jan 2014 19:39:41 +0000 Received: from [193.109.254.147:32491] by server-11.bemta-14.messagelabs.com id D2/60-20576-C7538D25; Thu, 16 Jan 2014 19:39:40 +0000 X-Env-Sender: jesse.benedict@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1389901177!11310746!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6905 invoked from network); 16 Jan 2014 19:39:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2014 19:39:39 -0000 X-IronPort-AV: E=Sophos;i="4.95,669,1384300800"; d="scan'208";a="93621470" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 16 Jan 2014 19:39:10 +0000 Received: from FTLPEX01CL02.citrite.net ([169.254.2.8]) by FTLPEX01CL03.citrite.net ([169.254.1.174]) with mapi id 14.02.0342.004; Thu, 16 Jan 2014 14:39:10 -0500 From: Jesse Benedict To: 'Russ Pavlicek' , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xs-devel@lists.xenserver.org" , "cl-mirage@lists.cam.ac.uk" , "publicity@lists.xenproject.org" Thread-Topic: [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 Thread-Index: AQHPErDL+s+s1Grh7UyexLHJALpZMpqHv8Vw Date: Thu, 16 Jan 2014 19:39:10 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.11.24.188] MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-API] [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Count me in, sir! I will review the links you have provided! Sincerely, Jesse Benedict, CCA | Citrix, Inc. | XenServer, XenClient Support Team Work Better. Live Better. Call us at 1-800-4CITRIX! Join the Community: support.citrix.com | discussions.citrix.com | blogs.citrix.com | taas.citrix.com Customer Satisfaction is our goal. If you have feedback regarding my performance, please feel free to contact my Manager william.aycock@citrix.com CONFIDENTIALITY NOTICE This e-mail message and all documents which accompany it are intended only for the use of the individual or entity to which addressed, and may contain privileged or confidential information. Any unauthorized disclosure or distribution of this e-mail message is prohibited. Any private files or utilities that are included in this e-mail are intended only for the use of the individual or entity to which this is addressed and distribution of these files or utilities is prohibited. If you have received this e-mail message in error, please notify me immediately. Thank you. -----Original Message----- From: russell.pavlicek.xen@gmail.com [mailto:russell.pavlicek.xen@gmail.com] On Behalf Of Russ Pavlicek Sent: Thursday, January 16, 2014 6:29 AM To: xen-devel@lists.xen.org; xen-users@lists.xen.org; xen-api@lists.xen.org; xs-devel@lists.xenserver.org; cl-mirage@lists.cam.ac.uk; publicity@lists.xenproject.org Subject: [xs-devel] Xen Project Test Day: Test 4.4 RC2 on January 20 Release time is approaching, so Test Days have arrived! On Monday, January 20, we are holding a Test Day for Xen 4.4. Release Candidate 2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC2, we need to know about it and how to test it. Either edit the instructions page or send me a few lines describing the feature and how it should be tested. Right now, RC2 is labelled a general test (e.g., "Does Xen compile, install, and do the things Xen normally does?"). We don't have any specific tests of new functionality identified. If you have something new which needs testing in RC2, we need to know about it. EVERYONE: Please join us on Monday, January 20, and help make sure the next release of Xen is the best one yet! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 20:32:58 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 20:32:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3tcS-0001Ye-1H; Thu, 16 Jan 2014 20:32:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3tcQ-0001YZ-Pe for xen-api@lists.xen.org; Thu, 16 Jan 2014 20:32:51 +0000 Received: from [85.158.143.35:18462] by server-3.bemta-4.messagelabs.com id A9/4F-32360-2F148D25; Thu, 16 Jan 2014 20:32:50 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1389904368!12103460!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25122 invoked from network); 16 Jan 2014 20:32:49 -0000 Received: from mx.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2014 20:32:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softlayer.com; s=ex13; h=MIME-Version:Content-Type:In-Reply-To:References:Message-ID:Date:Subject:To:From; bh=QuAmxrNiL3vLuexwIh7q03gOPiaB0n/iSzZh2Q4Uhvo=; b=YmvkZSvvSb9ZHJmV5BZFTiQcD7iKr9EVF74kUujrAGqVzx6skBppfp/7W3JU0QYp1N4AnUlcp9BBKByuAtbcteL3kOLXs6uGnojEMJXyfZN2iJgyy0Yc+vY0Y+6umbBowiUGDMsKzABX/IxB7aY9eBug3wIHrjFKHj5Q4v09Pr0MRzWIWnmMTfxzRmVpaKC5ZSVuBgNuZyP4TZVkZGRhr6K3xs1Jav+dBtpzhISwjSLzg6iLz/BxF/qvGrNsE2hjHrSpULLxh8jsShTeGkfHgWDecAN6JttqslRKJI4sBSy9UtVnL29rks98VXdxp5yGASbQb43mhlf5OzKsai1Wlw==; Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1W3tcN-000JCa-Fm; Thu, 16 Jan 2014 14:32:47 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by sm-tmg153.softlayer.local (172.18.18.71) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 16 Jan 2014 14:32:47 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0342.003; Thu, 16 Jan 2014 14:32:47 -0600 From: Joseph Hom To: Suman C , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] Number of hosts limit per resource pool Thread-Index: AQHPDYBX/U008gozFEWaGW/uvoNeo5qH2IgA Date: Thu, 16 Jan 2014 20:32:45 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F135520704F7C@SM-DAG151.softlayer.local> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.179] MIME-Version: 1.0 Subject: Re: [Xen-API] Number of hosts limit per resource pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1677700930639717380==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1677700930639717380== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_" --_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The node count isn't enforced. You can build huge pools if you want. Not sure if this is current, but in the past xapi is/was single threaded. W= hen you move beyond 16 nodes it starts to become painful to manage the syst= em in the event of a pool outage. The master node spends almost 100% of its= time sending/receiving updates from the slave and becomes useless to run v= ms on. Not to mention trying to manage it via XenCenter becomes an exercise= in futility. From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Suman C Sent: Thursday, January 09, 2014 3:02 PM To: xen-api@lists.xen.org Subject: [Xen-API] Number of hosts limit per resource pool Hi, I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to = 6.2. One of the configuration limits is 16 hosts per resource pool. I don't have= more than 16 hosts to test right away, so I am asking. Is this limit enfor= ced by the code? Or is it a matter of supportability from Citrix? It would be greatly helpful to know among the list of configuration limits,= which ones are enforced by the code and why. Can someone address these que= stions? Thanks Suman --_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The node count isn’= t enforced. You can build huge pools if you want.

 <= /p>

Not sure if this is curre= nt, but in the past xapi is/was single threaded. When you move beyond 16 no= des it starts to become painful to manage the system in the event of a pool outage. The master node spends almost 100% of its time= sending/receiving updates from the slave and becomes useless to run vms on= . Not to mention trying to manage it via XenCenter becomes an exercise in f= utility.

 <= /p>

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Suman C
Sent: Thursday, January 09, 2014 3:02 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] Number of hosts limit per resource pool

 

Hi,

I am using both Xen S= erver 6.2 and XCP 1.4, slowly migrating everything to 6.2.

One of the configuration limits is 16 hosts per resource pool. I don't have= more than 16 hosts to test right away, so I am asking. Is this limit enfor= ced by the code? Or is it a matter of supportability from Citrix?

It would be greatly helpful to know among the list o= f configuration limits, which ones are enforced by the code and why. Can so= meone address these questions?

Thanks

Suman

--_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_-- --===============1677700930639717380== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1677700930639717380==-- From xen-api-bounces@lists.xen.org Thu Jan 16 20:32:58 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 20:32:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3tcS-0001Ye-1H; Thu, 16 Jan 2014 20:32:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3tcQ-0001YZ-Pe for xen-api@lists.xen.org; Thu, 16 Jan 2014 20:32:51 +0000 Received: from [85.158.143.35:18462] by server-3.bemta-4.messagelabs.com id A9/4F-32360-2F148D25; Thu, 16 Jan 2014 20:32:50 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1389904368!12103460!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25122 invoked from network); 16 Jan 2014 20:32:49 -0000 Received: from mx.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2014 20:32:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softlayer.com; s=ex13; h=MIME-Version:Content-Type:In-Reply-To:References:Message-ID:Date:Subject:To:From; bh=QuAmxrNiL3vLuexwIh7q03gOPiaB0n/iSzZh2Q4Uhvo=; b=YmvkZSvvSb9ZHJmV5BZFTiQcD7iKr9EVF74kUujrAGqVzx6skBppfp/7W3JU0QYp1N4AnUlcp9BBKByuAtbcteL3kOLXs6uGnojEMJXyfZN2iJgyy0Yc+vY0Y+6umbBowiUGDMsKzABX/IxB7aY9eBug3wIHrjFKHj5Q4v09Pr0MRzWIWnmMTfxzRmVpaKC5ZSVuBgNuZyP4TZVkZGRhr6K3xs1Jav+dBtpzhISwjSLzg6iLz/BxF/qvGrNsE2hjHrSpULLxh8jsShTeGkfHgWDecAN6JttqslRKJI4sBSy9UtVnL29rks98VXdxp5yGASbQb43mhlf5OzKsai1Wlw==; Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1W3tcN-000JCa-Fm; Thu, 16 Jan 2014 14:32:47 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by sm-tmg153.softlayer.local (172.18.18.71) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 16 Jan 2014 14:32:47 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0342.003; Thu, 16 Jan 2014 14:32:47 -0600 From: Joseph Hom To: Suman C , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] Number of hosts limit per resource pool Thread-Index: AQHPDYBX/U008gozFEWaGW/uvoNeo5qH2IgA Date: Thu, 16 Jan 2014 20:32:45 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F135520704F7C@SM-DAG151.softlayer.local> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.179] MIME-Version: 1.0 Subject: Re: [Xen-API] Number of hosts limit per resource pool X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1677700930639717380==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1677700930639717380== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_" --_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The node count isn't enforced. You can build huge pools if you want. Not sure if this is current, but in the past xapi is/was single threaded. W= hen you move beyond 16 nodes it starts to become painful to manage the syst= em in the event of a pool outage. The master node spends almost 100% of its= time sending/receiving updates from the slave and becomes useless to run v= ms on. Not to mention trying to manage it via XenCenter becomes an exercise= in futility. From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Suman C Sent: Thursday, January 09, 2014 3:02 PM To: xen-api@lists.xen.org Subject: [Xen-API] Number of hosts limit per resource pool Hi, I am using both Xen Server 6.2 and XCP 1.4, slowly migrating everything to = 6.2. One of the configuration limits is 16 hosts per resource pool. I don't have= more than 16 hosts to test right away, so I am asking. Is this limit enfor= ced by the code? Or is it a matter of supportability from Citrix? It would be greatly helpful to know among the list of configuration limits,= which ones are enforced by the code and why. Can someone address these que= stions? Thanks Suman --_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The node count isn’= t enforced. You can build huge pools if you want.

 <= /p>

Not sure if this is curre= nt, but in the past xapi is/was single threaded. When you move beyond 16 no= des it starts to become painful to manage the system in the event of a pool outage. The master node spends almost 100% of its time= sending/receiving updates from the slave and becomes useless to run vms on= . Not to mention trying to manage it via XenCenter becomes an exercise in f= utility.

 <= /p>

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Suman C
Sent: Thursday, January 09, 2014 3:02 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] Number of hosts limit per resource pool

 

Hi,

I am using both Xen S= erver 6.2 and XCP 1.4, slowly migrating everything to 6.2.

One of the configuration limits is 16 hosts per resource pool. I don't have= more than 16 hosts to test right away, so I am asking. Is this limit enfor= ced by the code? Or is it a matter of supportability from Citrix?

It would be greatly helpful to know among the list o= f configuration limits, which ones are enforced by the code and why. Can so= meone address these questions?

Thanks

Suman

--_000_602C5EB92F9AFB4D89D11B9F5B7F135520704F7CSMDAG151softlay_-- --===============1677700930639717380== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1677700930639717380==-- From xen-api-bounces@lists.xen.org Thu Jan 16 20:34:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 20:34:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3teC-0001cI-EW; Thu, 16 Jan 2014 20:34:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3teA-0001cA-Mx for xen-api@lists.xen.org; Thu, 16 Jan 2014 20:34:38 +0000 Received: from [85.158.143.35:44565] by server-1.bemta-4.messagelabs.com id 21/57-02132-E5248D25; Thu, 16 Jan 2014 20:34:38 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1389904475!12270973!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29703 invoked from network); 16 Jan 2014 20:34:37 -0000 Received: from mx.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2014 20:34:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softlayer.com; s=ex13; h=MIME-Version:Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Message-ID:Date:Subject:CC:To:From; bh=X6v0yselYURUtukLtWSe3ji9MzgRgNBDrI0IOAHWxNU=; b=aYjqzVO2IhGAuss1okU0xCz5k2gMOEly08ifdqVtSjcxbtvXoe6sFYqXI5kHk2ceLvcjDnhyHPFUz55+CQNTj9qEWTrFCnkbcO+WSNB0rTwhixdT4qdaY26flXT/10TcpQcFp3IgRFap6AcHXZneZN+DHCoJhdY+/yaxoEojcaXEOdZpWTRDp2ONt38ublvn9jOvav3ADERhTbjHMY1Lt9xMaDUkVAgRkeDYJUmSyZ4Yz8B/Xx9NaU3HvHDSE13zWVqLYLb83M67RNqJaIhIk7slUS2HZTV13yBkLNy5WNkm+9W5Eh73LgCQq96R+2Ix4PvzFGDn3r9nIHjN9qhJiw==; Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1W3te6-000JIa-Qi; Thu, 16 Jan 2014 14:34:34 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by sm-tmg153.softlayer.local (172.18.18.71) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 16 Jan 2014 14:34:35 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0342.003; Thu, 16 Jan 2014 14:34:34 -0600 From: Joseph Hom To: Denis Cardon , "Agyeman B. Danso Jr." Thread-Topic: [Xen-API] Help Hypervisor VM IP reconfig Thread-Index: Ac8NZATC/HqslTFTRqqxb0TIBoYjQAA5GHoAASx4HTA= Date: Thu, 16 Jan 2014 20:34:33 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F135520704F99@SM-DAG151.softlayer.local> References: <52D00D6A.6020901@tranquil-it-systems.fr> In-Reply-To: <52D00D6A.6020901@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.179] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org If you have access to dom0 you can also grab the dom-id of the vm and use "= xl console " to access the console as well. -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Denis Cardon Sent: Friday, January 10, 2014 9:11 AM To: Agyeman B. Danso Jr. Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig Hi Agyeman, > Can you help me with the command to change ip address of a vm while on = > hypervisor? > > In my case if access to xen center is disabled and a user changes the = > ipaddress of a vm and no longer can ssh to the vm, I would like to be = > able to reset the ip address, netmask, and gateway from the hypervisor. > > The command below shows me network info but how to I change that = > network info? > > xe vm-list params=3Dname-label,networks I think this command is read only and show you the ip address that has been= reported by xentools to the hypervisor. However I don't think there is a default mechanism in xapi to set the ip ad= dress of a virtual machine. In some VDI deployement solution, the software = install a service inside the VDI machine to get the ip address from a deplo= yement server. However you don't need xencenter to get access to the vnc frame buffer of t= he virtual machine. You can get the vnc port using the following command li= ne (change my_vm_name, and be sure to be on the server where the vm is runn= ing if the server is in a pool) : xenstore-read /local/domain/$(xe vm-list params=3Ddom-id name-label=3Dmy_vm= _name --minimal)/console/vnc-port Take the port number that is given by the above command line (for example 5= 908), and then, just do a ssh port forwarding : ssh my_xen_server -L 5908:srvxen1:5908 -l root then from the same machine, run vncviewer localhost:8 Another method for a linux VM : use xe-edit-bootloader -n my_vm_name, then = from another shell, you can find the vm mounted on /var/run/fix-xxxxxx when= you have fixed the network configuration, you get out of the mount point, = then get out of the grub editing window, the xe-edit-bootloader script will= umount the partition by itself. Cheers, Denis > > *Thank you,* > > *Agyeman B. Danso Jr.* > > Security Engineer > > infoLock Technologies > > 877.610.5625 x253 - direct > ADanso@infolocktech.com > p_RKqup9rLCEc88I-S2ldrpjnNwv925Zia6zIs5wqMGKxN-DtjqIozN4Cqg.&URL=3Dmailt > o%3aADanso%40infolocktech.com> > > > > This body part will be downloaded on demand. > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 16 20:34:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 Jan 2014 20:34:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3teC-0001cI-EW; Thu, 16 Jan 2014 20:34:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3teA-0001cA-Mx for xen-api@lists.xen.org; Thu, 16 Jan 2014 20:34:38 +0000 Received: from [85.158.143.35:44565] by server-1.bemta-4.messagelabs.com id 21/57-02132-E5248D25; Thu, 16 Jan 2014 20:34:38 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1389904475!12270973!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29703 invoked from network); 16 Jan 2014 20:34:37 -0000 Received: from mx.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2014 20:34:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softlayer.com; s=ex13; h=MIME-Version:Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Message-ID:Date:Subject:CC:To:From; bh=X6v0yselYURUtukLtWSe3ji9MzgRgNBDrI0IOAHWxNU=; b=aYjqzVO2IhGAuss1okU0xCz5k2gMOEly08ifdqVtSjcxbtvXoe6sFYqXI5kHk2ceLvcjDnhyHPFUz55+CQNTj9qEWTrFCnkbcO+WSNB0rTwhixdT4qdaY26flXT/10TcpQcFp3IgRFap6AcHXZneZN+DHCoJhdY+/yaxoEojcaXEOdZpWTRDp2ONt38ublvn9jOvav3ADERhTbjHMY1Lt9xMaDUkVAgRkeDYJUmSyZ4Yz8B/Xx9NaU3HvHDSE13zWVqLYLb83M67RNqJaIhIk7slUS2HZTV13yBkLNy5WNkm+9W5Eh73LgCQq96R+2Ix4PvzFGDn3r9nIHjN9qhJiw==; Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1W3te6-000JIa-Qi; Thu, 16 Jan 2014 14:34:34 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by sm-tmg153.softlayer.local (172.18.18.71) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 16 Jan 2014 14:34:35 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0342.003; Thu, 16 Jan 2014 14:34:34 -0600 From: Joseph Hom To: Denis Cardon , "Agyeman B. Danso Jr." Thread-Topic: [Xen-API] Help Hypervisor VM IP reconfig Thread-Index: Ac8NZATC/HqslTFTRqqxb0TIBoYjQAA5GHoAASx4HTA= Date: Thu, 16 Jan 2014 20:34:33 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F135520704F99@SM-DAG151.softlayer.local> References: <52D00D6A.6020901@tranquil-it-systems.fr> In-Reply-To: <52D00D6A.6020901@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.179] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org If you have access to dom0 you can also grab the dom-id of the vm and use "= xl console " to access the console as well. -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Denis Cardon Sent: Friday, January 10, 2014 9:11 AM To: Agyeman B. Danso Jr. Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Help Hypervisor VM IP reconfig Hi Agyeman, > Can you help me with the command to change ip address of a vm while on = > hypervisor? > > In my case if access to xen center is disabled and a user changes the = > ipaddress of a vm and no longer can ssh to the vm, I would like to be = > able to reset the ip address, netmask, and gateway from the hypervisor. > > The command below shows me network info but how to I change that = > network info? > > xe vm-list params=3Dname-label,networks I think this command is read only and show you the ip address that has been= reported by xentools to the hypervisor. However I don't think there is a default mechanism in xapi to set the ip ad= dress of a virtual machine. In some VDI deployement solution, the software = install a service inside the VDI machine to get the ip address from a deplo= yement server. However you don't need xencenter to get access to the vnc frame buffer of t= he virtual machine. You can get the vnc port using the following command li= ne (change my_vm_name, and be sure to be on the server where the vm is runn= ing if the server is in a pool) : xenstore-read /local/domain/$(xe vm-list params=3Ddom-id name-label=3Dmy_vm= _name --minimal)/console/vnc-port Take the port number that is given by the above command line (for example 5= 908), and then, just do a ssh port forwarding : ssh my_xen_server -L 5908:srvxen1:5908 -l root then from the same machine, run vncviewer localhost:8 Another method for a linux VM : use xe-edit-bootloader -n my_vm_name, then = from another shell, you can find the vm mounted on /var/run/fix-xxxxxx when= you have fixed the network configuration, you get out of the mount point, = then get out of the grub editing window, the xe-edit-bootloader script will= umount the partition by itself. Cheers, Denis > > *Thank you,* > > *Agyeman B. Danso Jr.* > > Security Engineer > > infoLock Technologies > > 877.610.5625 x253 - direct > ADanso@infolocktech.com > p_RKqup9rLCEc88I-S2ldrpjnNwv925Zia6zIs5wqMGKxN-DtjqIozN4Cqg.&URL=3Dmailt > o%3aADanso%40infolocktech.com> > > > > This body part will be downloaded on demand. > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 18 05:29:12 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 18 Jan 2014 05:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4OSp-0001FB-Fj; Sat, 18 Jan 2014 05:28:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4OSo-0001F6-ME for xen-api@lists.xen.org; Sat, 18 Jan 2014 05:28:58 +0000 Received: from [85.158.137.68:44740] by server-3.bemta-3.messagelabs.com id 42/55-10658-9111AD25; Sat, 18 Jan 2014 05:28:57 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1390022936!9888704!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13276 invoked from network); 18 Jan 2014 05:28:57 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 05:28:57 -0000 Received: by mail-qa0-f54.google.com with SMTP id i13so4087067qae.27 for ; Fri, 17 Jan 2014 21:28:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VwXZVZ7u0T9KSIt5qigRnFQI06kRKnqj0g16nZV2EaA=; b=HH55ki5sr7Z+7MgMw+xyiBrYaJlm6tUIj/MuAGC/JKGJgAfsDDn4HJYQbwbapcPLha iiRNqKi+9LxYxk99JZWVQcmU3Qs9OOW6seo0+nTuya5QLC1P7t+gK/4MYy3RXQR71x/7 6706VlPwehRZ09TpkwzF4DqBNlGELA2e8ehtuZvCxdUEE4tEiU6rEyAcRAGLtPq7OHar 4hxoUeN4ST6evkOB0jsjr2PyWZ5/KhPbKD3Meh8VniKlEB8GFacTPS7WHGc1d9X3VS2q ofNGMYBVE9o5UOZDzrz6K7dU0DCgCGPZTjIQsTIKigCoiw+tNosS4cjEkuskTSdEc81K lA0Q== X-Gm-Message-State: ALoCoQkCX3OMM6Jcv9+wYUksR84ZE/3dYdIEWx1QRL+7O/onQZs618gc9lf90CjeZHEO8tBKCu87 MIME-Version: 1.0 X-Received: by 10.224.55.197 with SMTP id v5mr9771820qag.9.1390022935800; Fri, 17 Jan 2014 21:28:55 -0800 (PST) Received: by 10.140.49.174 with HTTP; Fri, 17 Jan 2014 21:28:55 -0800 (PST) Date: Sat, 18 Jan 2014 10:58:55 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org, Thileepan S Subject: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4586390796413509568==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4586390796413509568== Content-Type: multipart/alternative; boundary=001a11c2ef8e51981c04f037ef07 --001a11c2ef8e51981c04f037ef07 Content-Type: text/plain; charset=ISO-8859-1 Hi All , Is there any API call or any other method to detect whether the host in question is a Pool master or a member of a Xen POOL ? And is there a call to get the host info using the snapshot (UUID) of its VMS ? Thanks . Regards, Shafi, Vembu Technologies. --001a11c2ef8e51981c04f037ef07 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All ,
=A0 =A0 =A0 Is there any API call or any other= method to detect whether the host in question is a Pool master or a member= of a Xen POOL ?=A0

=A0 =A0 And is there a call to get the host info= using =A0the snapshot (UUID) of its VMS ?
=A0 =A0
Thanks .


Regards,
Shafi,
Vembu Technologie= s.

--001a11c2ef8e51981c04f037ef07-- --===============4586390796413509568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4586390796413509568==-- From xen-api-bounces@lists.xen.org Sat Jan 18 05:29:12 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 18 Jan 2014 05:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4OSp-0001FB-Fj; Sat, 18 Jan 2014 05:28:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4OSo-0001F6-ME for xen-api@lists.xen.org; Sat, 18 Jan 2014 05:28:58 +0000 Received: from [85.158.137.68:44740] by server-3.bemta-3.messagelabs.com id 42/55-10658-9111AD25; Sat, 18 Jan 2014 05:28:57 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1390022936!9888704!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13276 invoked from network); 18 Jan 2014 05:28:57 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 05:28:57 -0000 Received: by mail-qa0-f54.google.com with SMTP id i13so4087067qae.27 for ; Fri, 17 Jan 2014 21:28:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VwXZVZ7u0T9KSIt5qigRnFQI06kRKnqj0g16nZV2EaA=; b=HH55ki5sr7Z+7MgMw+xyiBrYaJlm6tUIj/MuAGC/JKGJgAfsDDn4HJYQbwbapcPLha iiRNqKi+9LxYxk99JZWVQcmU3Qs9OOW6seo0+nTuya5QLC1P7t+gK/4MYy3RXQR71x/7 6706VlPwehRZ09TpkwzF4DqBNlGELA2e8ehtuZvCxdUEE4tEiU6rEyAcRAGLtPq7OHar 4hxoUeN4ST6evkOB0jsjr2PyWZ5/KhPbKD3Meh8VniKlEB8GFacTPS7WHGc1d9X3VS2q ofNGMYBVE9o5UOZDzrz6K7dU0DCgCGPZTjIQsTIKigCoiw+tNosS4cjEkuskTSdEc81K lA0Q== X-Gm-Message-State: ALoCoQkCX3OMM6Jcv9+wYUksR84ZE/3dYdIEWx1QRL+7O/onQZs618gc9lf90CjeZHEO8tBKCu87 MIME-Version: 1.0 X-Received: by 10.224.55.197 with SMTP id v5mr9771820qag.9.1390022935800; Fri, 17 Jan 2014 21:28:55 -0800 (PST) Received: by 10.140.49.174 with HTTP; Fri, 17 Jan 2014 21:28:55 -0800 (PST) Date: Sat, 18 Jan 2014 10:58:55 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org, Thileepan S Subject: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4586390796413509568==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4586390796413509568== Content-Type: multipart/alternative; boundary=001a11c2ef8e51981c04f037ef07 --001a11c2ef8e51981c04f037ef07 Content-Type: text/plain; charset=ISO-8859-1 Hi All , Is there any API call or any other method to detect whether the host in question is a Pool master or a member of a Xen POOL ? And is there a call to get the host info using the snapshot (UUID) of its VMS ? Thanks . Regards, Shafi, Vembu Technologies. --001a11c2ef8e51981c04f037ef07 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All ,
=A0 =A0 =A0 Is there any API call or any other= method to detect whether the host in question is a Pool master or a member= of a Xen POOL ?=A0

=A0 =A0 And is there a call to get the host info= using =A0the snapshot (UUID) of its VMS ?
=A0 =A0
Thanks .


Regards,
Shafi,
Vembu Technologie= s.

--001a11c2ef8e51981c04f037ef07-- --===============4586390796413509568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4586390796413509568==-- From xen-api-bounces@lists.xen.org Sat Jan 18 06:49:55 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 18 Jan 2014 06:49:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Pj1-0005DT-1C; Sat, 18 Jan 2014 06:49:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Piz-0005DO-Uy for xen-api@lists.xen.org; Sat, 18 Jan 2014 06:49:46 +0000 Received: from [193.109.254.147:6611] by server-7.bemta-14.messagelabs.com id A5/57-15500-8042AD25; Sat, 18 Jan 2014 06:49:44 +0000 X-Env-Sender: turbo124@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1390027782!10162149!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31155 invoked from network); 18 Jan 2014 06:49:43 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 06:49:43 -0000 Received: by mail-qc0-f182.google.com with SMTP id c9so4479288qcz.13 for ; Fri, 17 Jan 2014 22:49:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kg4rwc7f9nPX5RH/ZwGShysCkIqdh86pLcyMLYiRdh8=; b=plEy5fpW2l1w26ZGIVzuKdWF7+YexGc0UC0Ezlwt1cvFSyCdjIw9CvQRmT38V+V8gj BylUTAltakS7jjnYxwjzyNGpF+hCnGSA2QQSQ5Di3T9xmEqkpqdA6/ZCCt6iPtva2wOF DpIGyvj8a4Hm5O88j+bb/YmTSQs0OG5YPBS4I/us/AH02QfpdQFJD+b0yLSJ0sRA+Qgl 1ptEm4eAWYwMIZrsDZxXMeAVxj7mSDiMDdecYtr5tD01ER+1W0uODMfcR39ri8J8nvG7 ao6dNtCr/kapKuvgKNVuAn2pyo8b1WdL1FXu9cC0xt/fU8ofj3xw3gbnXhKpPn+tRO6o 0cIQ== MIME-Version: 1.0 X-Received: by 10.224.103.131 with SMTP id k3mr10091478qao.102.1390027781988; Fri, 17 Jan 2014 22:49:41 -0800 (PST) Received: by 10.229.87.196 with HTTP; Fri, 17 Jan 2014 22:49:41 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 17:49:41 +1100 Message-ID: From: David Bomba To: Shafi Mohammed S Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0678064435666940173==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0678064435666940173== Content-Type: multipart/alternative; boundary=047d7b5d891b2c669f04f03910ed --047d7b5d891b2c669f04f03910ed Content-Type: text/plain; charset=ISO-8859-1 Hi Shafi, Please refer directly to the API documentation. This is extremely well documented and the answer to your question is there. http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/api/ On 18 January 2014 16:28, Shafi Mohammed S wrote: > Hi All , > Is there any API call or any other method to detect whether the host > in question is a Pool master or a member of a Xen POOL ? > > And is there a call to get the host info using the snapshot (UUID) of > its VMS ? > > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7b5d891b2c669f04f03910ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Shafi,

Please refer directly to the A= PI documentation. This is extremely well documented and the answer to your = question is there.

http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/a= pi/



On = 18 January 2014 16:28, Shafi Mohammed S <shafi@vembu.com> wrot= e:
Hi All ,
=A0 =A0 =A0 Is = there any API call or any other method to detect whether the host in questi= on is a Pool master or a member of a Xen POOL ?=A0

=A0 =A0 And is there a call to get the host info using =A0the snapshot = (UUID) of its VMS ?
=A0 =A0
Thanks .


Regards,
Shafi,
Vembu Technologie= s.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--047d7b5d891b2c669f04f03910ed-- --===============0678064435666940173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0678064435666940173==-- From xen-api-bounces@lists.xen.org Sat Jan 18 06:49:55 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 18 Jan 2014 06:49:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Pj1-0005DT-1C; Sat, 18 Jan 2014 06:49:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Piz-0005DO-Uy for xen-api@lists.xen.org; Sat, 18 Jan 2014 06:49:46 +0000 Received: from [193.109.254.147:6611] by server-7.bemta-14.messagelabs.com id A5/57-15500-8042AD25; Sat, 18 Jan 2014 06:49:44 +0000 X-Env-Sender: turbo124@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1390027782!10162149!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31155 invoked from network); 18 Jan 2014 06:49:43 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 06:49:43 -0000 Received: by mail-qc0-f182.google.com with SMTP id c9so4479288qcz.13 for ; Fri, 17 Jan 2014 22:49:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kg4rwc7f9nPX5RH/ZwGShysCkIqdh86pLcyMLYiRdh8=; b=plEy5fpW2l1w26ZGIVzuKdWF7+YexGc0UC0Ezlwt1cvFSyCdjIw9CvQRmT38V+V8gj BylUTAltakS7jjnYxwjzyNGpF+hCnGSA2QQSQ5Di3T9xmEqkpqdA6/ZCCt6iPtva2wOF DpIGyvj8a4Hm5O88j+bb/YmTSQs0OG5YPBS4I/us/AH02QfpdQFJD+b0yLSJ0sRA+Qgl 1ptEm4eAWYwMIZrsDZxXMeAVxj7mSDiMDdecYtr5tD01ER+1W0uODMfcR39ri8J8nvG7 ao6dNtCr/kapKuvgKNVuAn2pyo8b1WdL1FXu9cC0xt/fU8ofj3xw3gbnXhKpPn+tRO6o 0cIQ== MIME-Version: 1.0 X-Received: by 10.224.103.131 with SMTP id k3mr10091478qao.102.1390027781988; Fri, 17 Jan 2014 22:49:41 -0800 (PST) Received: by 10.229.87.196 with HTTP; Fri, 17 Jan 2014 22:49:41 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 17:49:41 +1100 Message-ID: From: David Bomba To: Shafi Mohammed S Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0678064435666940173==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0678064435666940173== Content-Type: multipart/alternative; boundary=047d7b5d891b2c669f04f03910ed --047d7b5d891b2c669f04f03910ed Content-Type: text/plain; charset=ISO-8859-1 Hi Shafi, Please refer directly to the API documentation. This is extremely well documented and the answer to your question is there. http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/api/ On 18 January 2014 16:28, Shafi Mohammed S wrote: > Hi All , > Is there any API call or any other method to detect whether the host > in question is a Pool master or a member of a Xen POOL ? > > And is there a call to get the host info using the snapshot (UUID) of > its VMS ? > > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7b5d891b2c669f04f03910ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Shafi,

Please refer directly to the A= PI documentation. This is extremely well documented and the answer to your = question is there.

http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/a= pi/



On = 18 January 2014 16:28, Shafi Mohammed S <shafi@vembu.com> wrot= e:
Hi All ,
=A0 =A0 =A0 Is = there any API call or any other method to detect whether the host in questi= on is a Pool master or a member of a Xen POOL ?=A0

=A0 =A0 And is there a call to get the host info using =A0the snapshot = (UUID) of its VMS ?
=A0 =A0
Thanks .


Regards,
Shafi,
Vembu Technologie= s.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--047d7b5d891b2c669f04f03910ed-- --===============0678064435666940173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0678064435666940173==-- From xen-api-bounces@lists.xen.org Mon Jan 20 05:01:26 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 05:01:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W56z4-0008BH-DS; Mon, 20 Jan 2014 05:01:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W56z2-0008B6-IW; Mon, 20 Jan 2014 05:01:12 +0000 Received: from [85.158.139.211:31443] by server-14.bemta-5.messagelabs.com id 3E/5A-24200-79DACD25; Mon, 20 Jan 2014 05:01:11 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1390194070!10660588!1 X-Originating-IP: [209.85.215.47] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10077 invoked from network); 20 Jan 2014 05:01:10 -0000 Received: from mail-la0-f47.google.com (HELO mail-la0-f47.google.com) (209.85.215.47) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 05:01:10 -0000 Received: by mail-la0-f47.google.com with SMTP id el20so2662035lab.34 for ; Sun, 19 Jan 2014 21:01:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=ehGQBRHrnMmb4M8a+J7d8rRfXvyxjbRe/9ZUvxQl9no=; b=SFfe0IdLHj99RbLRw+jffCIhA90hIM8/sTS4CNEB0VB9DkzzNL3p2T6R4iWkcGiwfk gm/Prejfcq2xUEYIw0YT9LEVGK7s2Bt/St6beTxaXwksH7OKdL+1kcnmlg5XECBMG9Ni TQQfd2hC5+aroo5CiDAyjc2KhewkEbW9bFaLesp2QWStkXVySP9ZN1Wtb0E8uo9rkVwQ eWbz4yYBMExSXHdCeBYKFIY5wTPBt1u9gR7hUcxz82Hbt1dyW+ZV7BvlhoJ0g7MakUky tlT+BXlIrPIK2aGByO+YP87BOfVS74XjOUhCa09uFXENOUxBOaHe2FjB33D0zzf40brN FHRg== MIME-Version: 1.0 X-Received: by 10.112.139.35 with SMTP id qv3mr274lbb.47.1390194069888; Sun, 19 Jan 2014 21:01:09 -0800 (PST) Received: by 10.112.184.16 with HTTP; Sun, 19 Jan 2014 21:01:09 -0800 (PST) Date: Mon, 20 Jan 2014 00:01:09 -0500 X-Google-Sender-Auth: R1NXL8tGNB9r_mx1Iy__oFmxjdU Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] TODAY, Jan. 20, is Xen Test Day for Xen 4.4 RC2 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a reminder that today is the Xen Test Day for Xen 4.4 RC2. This is the first Test Day for the 4.4 codebase (we had no Test Day for RC1 due to the number of people taking time off in late December). As such, it is extremely important that we take some time to make sure the code is functioning properly. Please try to spend some time today loading and testing Xen 4.4 RC2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions Developers: please consider monitoring the Freenode IRC channel #xentest today to make sure that people are able to build and test the code. Hope to see you today on #xentest! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 20 05:01:26 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 05:01:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W56z4-0008BH-DS; Mon, 20 Jan 2014 05:01:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W56z2-0008B6-IW; Mon, 20 Jan 2014 05:01:12 +0000 Received: from [85.158.139.211:31443] by server-14.bemta-5.messagelabs.com id 3E/5A-24200-79DACD25; Mon, 20 Jan 2014 05:01:11 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1390194070!10660588!1 X-Originating-IP: [209.85.215.47] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10077 invoked from network); 20 Jan 2014 05:01:10 -0000 Received: from mail-la0-f47.google.com (HELO mail-la0-f47.google.com) (209.85.215.47) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 05:01:10 -0000 Received: by mail-la0-f47.google.com with SMTP id el20so2662035lab.34 for ; Sun, 19 Jan 2014 21:01:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=ehGQBRHrnMmb4M8a+J7d8rRfXvyxjbRe/9ZUvxQl9no=; b=SFfe0IdLHj99RbLRw+jffCIhA90hIM8/sTS4CNEB0VB9DkzzNL3p2T6R4iWkcGiwfk gm/Prejfcq2xUEYIw0YT9LEVGK7s2Bt/St6beTxaXwksH7OKdL+1kcnmlg5XECBMG9Ni TQQfd2hC5+aroo5CiDAyjc2KhewkEbW9bFaLesp2QWStkXVySP9ZN1Wtb0E8uo9rkVwQ eWbz4yYBMExSXHdCeBYKFIY5wTPBt1u9gR7hUcxz82Hbt1dyW+ZV7BvlhoJ0g7MakUky tlT+BXlIrPIK2aGByO+YP87BOfVS74XjOUhCa09uFXENOUxBOaHe2FjB33D0zzf40brN FHRg== MIME-Version: 1.0 X-Received: by 10.112.139.35 with SMTP id qv3mr274lbb.47.1390194069888; Sun, 19 Jan 2014 21:01:09 -0800 (PST) Received: by 10.112.184.16 with HTTP; Sun, 19 Jan 2014 21:01:09 -0800 (PST) Date: Mon, 20 Jan 2014 00:01:09 -0500 X-Google-Sender-Auth: R1NXL8tGNB9r_mx1Iy__oFmxjdU Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] TODAY, Jan. 20, is Xen Test Day for Xen 4.4 RC2 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a reminder that today is the Xen Test Day for Xen 4.4 RC2. This is the first Test Day for the 4.4 codebase (we had no Test Day for RC1 due to the number of people taking time off in late December). As such, it is extremely important that we take some time to make sure the code is functioning properly. Please try to spend some time today loading and testing Xen 4.4 RC2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions Developers: please consider monitoring the Freenode IRC channel #xentest today to make sure that people are able to build and test the code. Hope to see you today on #xentest! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 20 09:19:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 09:19:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0U-0002J0-3p; Mon, 20 Jan 2014 09:18:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0S-0002In-Io; Mon, 20 Jan 2014 09:18:56 +0000 Received: from [85.158.137.68:31579] by server-3.bemta-3.messagelabs.com id DB/F8-10658-EF9ECD25; Mon, 20 Jan 2014 09:18:54 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1390209533!10068126!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6898 invoked from network); 20 Jan 2014 09:18:54 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 09:18:54 -0000 Received: by mail-wg0-f52.google.com with SMTP id b13so6673065wgh.7 for ; Mon, 20 Jan 2014 01:18:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=DfSP2czzc9IdvCvH2tQ6nprfgk2OyR/BVtAB4BFQCGw=; b=kdqAOZuQEvURpmBZcDBqAnPGyJw7QkP3OydYo82k58pLQWbOlXByr22tPoKbZ4AMrn Jnsq3grCIw4PlcGaofzw23tETHs3SBlYo0FND1VUn5LKJSrwT8SCuJciEq8G85WcjiHh izicAEbjeb859+H+3qgK9aO8lwbJh1NeLFXmtVqW6o26rbPo/6EW3c/gptNTMk+m0Ezz VytDtH5iAPnLXm/anbWhfEEm8Wl//PXUr92iGHM/kczf33GR1im22+Hu1cMQ+poZjN+Z DQ0QxA4dXnOCkwslKEN9Gj5lUWDwn45c/o9Id7eTdL6Oz3DoiKs4ifiUhvdmbMt90bzR Jbpw== X-Received: by 10.194.63.228 with SMTP id j4mr13538806wjs.34.1390209533631; Mon, 20 Jan 2014 01:18:53 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id eo4sm1090422wib.9.2014.01.20.01.18.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 01:18:52 -0800 (PST) Message-ID: <52DCE9FA.6010400@xen.org> Date: Mon, 20 Jan 2014 09:18:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [Xen-API] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, the GSoC application deadline is coming up : Feb 2014. If we want to have any chance of getting accepted this year, we ought to get our project list into good shape. The project list and how the project and menters present themselves has a bigger impact on whether we get accepted than the actual application. Also, I would like to add a mentor section this year: a short bio, what the mentor cares about and a picture. This will help make the project list more real. We have *4 weeks* to do this. The bar for GSoC has been getting increasingly high. I know, we are tied down with Xen 4.4, but this is something you need to do if you want the Xen Project to participate. a) Please, update http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently (these need to be in good shape *before* the application). What I need you to do is: a.1) Remove items that are done a.2) Add new work items : we ought to have a few sexy topics on say Real-time, mobile and some of the other segments (assuming we can get HW) a.3) All project proposals need to be peer reviewed *and* clear ... The peer review process for projects we put in place last year worked well, by which we had past mentors sign of project proposals that were in good enough state. b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get these listed on the respective other programs. And we should link to these from our project page. Best Regards Lars P.S.: I will also see whether we can participate as Xen Project under the LF GSoC program, but last year there was push-back and I don't expect this to change _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 20 09:19:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 09:19:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0U-0002J0-3p; Mon, 20 Jan 2014 09:18:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0S-0002In-Io; Mon, 20 Jan 2014 09:18:56 +0000 Received: from [85.158.137.68:31579] by server-3.bemta-3.messagelabs.com id DB/F8-10658-EF9ECD25; Mon, 20 Jan 2014 09:18:54 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1390209533!10068126!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6898 invoked from network); 20 Jan 2014 09:18:54 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 09:18:54 -0000 Received: by mail-wg0-f52.google.com with SMTP id b13so6673065wgh.7 for ; Mon, 20 Jan 2014 01:18:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=DfSP2czzc9IdvCvH2tQ6nprfgk2OyR/BVtAB4BFQCGw=; b=kdqAOZuQEvURpmBZcDBqAnPGyJw7QkP3OydYo82k58pLQWbOlXByr22tPoKbZ4AMrn Jnsq3grCIw4PlcGaofzw23tETHs3SBlYo0FND1VUn5LKJSrwT8SCuJciEq8G85WcjiHh izicAEbjeb859+H+3qgK9aO8lwbJh1NeLFXmtVqW6o26rbPo/6EW3c/gptNTMk+m0Ezz VytDtH5iAPnLXm/anbWhfEEm8Wl//PXUr92iGHM/kczf33GR1im22+Hu1cMQ+poZjN+Z DQ0QxA4dXnOCkwslKEN9Gj5lUWDwn45c/o9Id7eTdL6Oz3DoiKs4ifiUhvdmbMt90bzR Jbpw== X-Received: by 10.194.63.228 with SMTP id j4mr13538806wjs.34.1390209533631; Mon, 20 Jan 2014 01:18:53 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id eo4sm1090422wib.9.2014.01.20.01.18.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 01:18:52 -0800 (PST) Message-ID: <52DCE9FA.6010400@xen.org> Date: Mon, 20 Jan 2014 09:18:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [Xen-API] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, the GSoC application deadline is coming up : Feb 2014. If we want to have any chance of getting accepted this year, we ought to get our project list into good shape. The project list and how the project and menters present themselves has a bigger impact on whether we get accepted than the actual application. Also, I would like to add a mentor section this year: a short bio, what the mentor cares about and a picture. This will help make the project list more real. We have *4 weeks* to do this. The bar for GSoC has been getting increasingly high. I know, we are tied down with Xen 4.4, but this is something you need to do if you want the Xen Project to participate. a) Please, update http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently (these need to be in good shape *before* the application). What I need you to do is: a.1) Remove items that are done a.2) Add new work items : we ought to have a few sexy topics on say Real-time, mobile and some of the other segments (assuming we can get HW) a.3) All project proposals need to be peer reviewed *and* clear ... The peer review process for projects we put in place last year worked well, by which we had past mentors sign of project proposals that were in good enough state. b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get these listed on the respective other programs. And we should link to these from our project page. Best Regards Lars P.S.: I will also see whether we can participate as Xen Project under the LF GSoC program, but last year there was push-back and I don't expect this to change _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 20 09:35:36 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 09:35:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5BGV-0003D7-Us; Mon, 20 Jan 2014 09:35:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5BGV-0003D2-7s for xen-api@lists.xen.org; Mon, 20 Jan 2014 09:35:31 +0000 Received: from [85.158.143.35:64041] by server-3.bemta-4.messagelabs.com id A7/88-32360-2EDECD25; Mon, 20 Jan 2014 09:35:30 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-4.tower-21.messagelabs.com!1390210529!12763159!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25247 invoked from network); 20 Jan 2014 09:35:29 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-4.tower-21.messagelabs.com with SMTP; 20 Jan 2014 09:35:29 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d58 with ME id G9bV1n0033zjds1039bVxv; Mon, 20 Jan 2014 10:35:29 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id E6DF5161D14; Mon, 20 Jan 2014 10:35:28 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id K9H5HneQTs9g; Mon, 20 Jan 2014 10:35:28 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F05CB161D75; Mon, 20 Jan 2014 10:35:27 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id F7YTp69m2v9J; Mon, 20 Jan 2014 10:35:27 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B4C8A161D14; Mon, 20 Jan 2014 10:35:27 +0100 (CET) Message-ID: <52DCEDDF.3030101@tranquil-it-systems.fr> Date: Mon, 20 Jan 2014 10:35:27 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed S References: In-Reply-To: Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > Is there any API call or any other method to detect whether the > host in question is a Pool master or a member of a Xen POOL ? This question was covered a few days ago... Using python : session =3D XenAPI.Session('https://'+self.xcphost) try: session.login_with_password(user_xen,password_xen) except XenAPI.Failure, error: msg,ip =3D error.details if msg =3D=3D 'HOST_IS_SLAVE': xcphost =3D ip session =3D XenAPI.Session('https://'+xcphost) session.login_with_password(user_xen,password_xen) (sample code from = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py) > And is there a call to get the host info using the snapshot (UUID) > of its VMS ? by host info, do you mean the param-list of the host where the vm is = running? You can get the VM uuid from snapshot uuid using xe vm-list uuid=3D$(xe snapshot-param-get param-name=3Dsnapshot-of = uuid=3D35e68b3d-cadd-afc6-0f57-833be773b9ba ) Then you can query the resident-on value (at least for running vm) xe vm-param-get param-name=3Dresident-on = uuid=3D71e1795e-a1fa-16ea-4f22-77048d9c1e02 It shouldn't be too hard to translate this in api calls. And like David = told earlier, xapi API doc is your best friend. Cheers, Denis > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 20 09:35:36 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 Jan 2014 09:35:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5BGV-0003D7-Us; Mon, 20 Jan 2014 09:35:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5BGV-0003D2-7s for xen-api@lists.xen.org; Mon, 20 Jan 2014 09:35:31 +0000 Received: from [85.158.143.35:64041] by server-3.bemta-4.messagelabs.com id A7/88-32360-2EDECD25; Mon, 20 Jan 2014 09:35:30 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-4.tower-21.messagelabs.com!1390210529!12763159!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25247 invoked from network); 20 Jan 2014 09:35:29 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-4.tower-21.messagelabs.com with SMTP; 20 Jan 2014 09:35:29 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d58 with ME id G9bV1n0033zjds1039bVxv; Mon, 20 Jan 2014 10:35:29 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id E6DF5161D14; Mon, 20 Jan 2014 10:35:28 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id K9H5HneQTs9g; Mon, 20 Jan 2014 10:35:28 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F05CB161D75; Mon, 20 Jan 2014 10:35:27 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id F7YTp69m2v9J; Mon, 20 Jan 2014 10:35:27 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B4C8A161D14; Mon, 20 Jan 2014 10:35:27 +0100 (CET) Message-ID: <52DCEDDF.3030101@tranquil-it-systems.fr> Date: Mon, 20 Jan 2014 10:35:27 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shafi Mohammed S References: In-Reply-To: Cc: Thileepan S , xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shafi, > Is there any API call or any other method to detect whether the > host in question is a Pool master or a member of a Xen POOL ? This question was covered a few days ago... Using python : session =3D XenAPI.Session('https://'+self.xcphost) try: session.login_with_password(user_xen,password_xen) except XenAPI.Failure, error: msg,ip =3D error.details if msg =3D=3D 'HOST_IS_SLAVE': xcphost =3D ip session =3D XenAPI.Session('https://'+xcphost) session.login_with_password(user_xen,password_xen) (sample code from = https://github.com/tranquilit/TISbackup/blob/master/libtisbackup/backup_xva= .py) > And is there a call to get the host info using the snapshot (UUID) > of its VMS ? by host info, do you mean the param-list of the host where the vm is = running? You can get the VM uuid from snapshot uuid using xe vm-list uuid=3D$(xe snapshot-param-get param-name=3Dsnapshot-of = uuid=3D35e68b3d-cadd-afc6-0f57-833be773b9ba ) Then you can query the resident-on value (at least for running vm) xe vm-param-get param-name=3Dresident-on = uuid=3D71e1795e-a1fa-16ea-4f22-77048d9c1e02 It shouldn't be too hard to translate this in api calls. And like David = told earlier, xapi API doc is your best friend. Cheers, Denis > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 10:17:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 10:17:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YOW-0001dC-7A; Tue, 21 Jan 2014 10:17:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YOV-0001d4-It for xen-api@lists.xen.org; Tue, 21 Jan 2014 10:17:19 +0000 Received: from [85.158.137.68:53096] by server-3.bemta-3.messagelabs.com id 69/5D-10658-E294ED25; Tue, 21 Jan 2014 10:17:18 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1390299436!10327294!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14420 invoked from network); 21 Jan 2014 10:17:17 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 10:17:17 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so6914833qcy.12 for ; Tue, 21 Jan 2014 02:17:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=lfIgh4aDQe0Sdgf6ZZWoYwt8NqurtztCd730On8Z4+Y=; b=hqjaFm0TT/Ce+nCgQLX6+QXNA72SPt7vaOfzuopTMrHFHI50GCXhCljUoAzDsf892C 96ssivszB/kABidyxy4nTGYeH3eonfN44efWM5NMp4I9WbnQh06e+3AYCa77yOO5Q3Lj YUzu9j3YbYIp9hZWc6MK2MWPzAAvbFCgeRnmO/coKbd9MAyVebigzG9I56OacharFYhN ek0G0ukvPHMrUJrYYHQSpqf3NsJ6E2Jm4xQ1yzwP4jgCbAYC4D/ddQFIl2P6ZnNXIx7A qs+pczopOdSG/5IW8lWVgOO5fdtsGBAKr3IusZGZV8eBZxcv+VYtpo5fMIeanWddu+AG G7XA== X-Gm-Message-State: ALoCoQm3dm05YPOCtWQ1OiryaA7LjDhc8gRovj566hT31alO9JYbBj3Ini40Gl7lOUA/AmnzGE/s MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr36067646qav.4.1390299436632; Tue, 21 Jan 2014 02:17:16 -0800 (PST) Received: by 10.140.49.174 with HTTP; Tue, 21 Jan 2014 02:17:16 -0800 (PST) Date: Tue, 21 Jan 2014 15:47:16 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] import XVA programatically into a XenHost X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4451262065854830121==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4451262065854830121== Content-Type: multipart/alternative; boundary=089e01493f160d7a4104f0785020 --089e01493f160d7a4104f0785020 Content-Type: text/plain; charset=ISO-8859-1 Hi all , Can we import an XVA (a VM) into A XenHost by using XAPI calls ? ANy info on this would be of great use . Thanks . Regards, Shafi, Vembu Technologies. --089e01493f160d7a4104f0785020 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all ,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0 Can we import an XVA (a VM) into A XenHost by using XAPI= calls ? ANy info on this would be of great use .


Thanks .


Regards,
Shafi,=
Vembu Technologies.

--089e01493f160d7a4104f0785020-- --===============4451262065854830121== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4451262065854830121==-- From xen-api-bounces@lists.xen.org Tue Jan 21 10:17:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 10:17:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YOW-0001dC-7A; Tue, 21 Jan 2014 10:17:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YOV-0001d4-It for xen-api@lists.xen.org; Tue, 21 Jan 2014 10:17:19 +0000 Received: from [85.158.137.68:53096] by server-3.bemta-3.messagelabs.com id 69/5D-10658-E294ED25; Tue, 21 Jan 2014 10:17:18 +0000 X-Env-Sender: shafi@vembu.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1390299436!10327294!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14420 invoked from network); 21 Jan 2014 10:17:17 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 10:17:17 -0000 Received: by mail-qc0-f181.google.com with SMTP id e9so6914833qcy.12 for ; Tue, 21 Jan 2014 02:17:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=lfIgh4aDQe0Sdgf6ZZWoYwt8NqurtztCd730On8Z4+Y=; b=hqjaFm0TT/Ce+nCgQLX6+QXNA72SPt7vaOfzuopTMrHFHI50GCXhCljUoAzDsf892C 96ssivszB/kABidyxy4nTGYeH3eonfN44efWM5NMp4I9WbnQh06e+3AYCa77yOO5Q3Lj YUzu9j3YbYIp9hZWc6MK2MWPzAAvbFCgeRnmO/coKbd9MAyVebigzG9I56OacharFYhN ek0G0ukvPHMrUJrYYHQSpqf3NsJ6E2Jm4xQ1yzwP4jgCbAYC4D/ddQFIl2P6ZnNXIx7A qs+pczopOdSG/5IW8lWVgOO5fdtsGBAKr3IusZGZV8eBZxcv+VYtpo5fMIeanWddu+AG G7XA== X-Gm-Message-State: ALoCoQm3dm05YPOCtWQ1OiryaA7LjDhc8gRovj566hT31alO9JYbBj3Ini40Gl7lOUA/AmnzGE/s MIME-Version: 1.0 X-Received: by 10.224.12.5 with SMTP id v5mr36067646qav.4.1390299436632; Tue, 21 Jan 2014 02:17:16 -0800 (PST) Received: by 10.140.49.174 with HTTP; Tue, 21 Jan 2014 02:17:16 -0800 (PST) Date: Tue, 21 Jan 2014 15:47:16 +0530 Message-ID: From: Shafi Mohammed S To: xen-api@lists.xen.org Cc: Thileepan S Subject: [Xen-API] import XVA programatically into a XenHost X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4451262065854830121==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4451262065854830121== Content-Type: multipart/alternative; boundary=089e01493f160d7a4104f0785020 --089e01493f160d7a4104f0785020 Content-Type: text/plain; charset=ISO-8859-1 Hi all , Can we import an XVA (a VM) into A XenHost by using XAPI calls ? ANy info on this would be of great use . Thanks . Regards, Shafi, Vembu Technologies. --089e01493f160d7a4104f0785020 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all ,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0 Can we import an XVA (a VM) into A XenHost by using XAPI= calls ? ANy info on this would be of great use .


Thanks .


Regards,
Shafi,=
Vembu Technologies.

--089e01493f160d7a4104f0785020-- --===============4451262065854830121== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4451262065854830121==-- From xen-api-bounces@lists.xen.org Tue Jan 21 10:24:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 10:24:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YVP-00027f-0y; Tue, 21 Jan 2014 10:24:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YVN-00027Z-U4 for xen-api@lists.xen.org; Tue, 21 Jan 2014 10:24:26 +0000 Received: from [193.109.254.147:22844] by server-4.bemta-14.messagelabs.com id 75/10-03916-9DA4ED25; Tue, 21 Jan 2014 10:24:25 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1390299863!12182005!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22224 invoked from network); 21 Jan 2014 10:24:24 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 10:24:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,695,1384300800"; d="scan'208";a="92751829" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 21 Jan 2014 10:24:22 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 21 Jan 2014 05:24:22 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Tue, 21 Jan 2014 11:24:21 +0100 From: Dave Scott To: Shafi Mohammed S Thread-Topic: [Xen-API] import XVA programatically into a XenHost Thread-Index: AQHPFpJEwqCik1cr4kSL9Or5MoJLg5qO+L+Q Date: Tue, 21 Jan 2014 10:24:20 +0000 Message-ID: <4D8B96BA-81AA-4900-AFEF-BD55CCA16905@eu.citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: MIA1 Cc: Thileepan S , "xen-api@lists.xen.org" Subject: Re: [Xen-API] import XVA programatically into a XenHost X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, The simplest way to do it is to use an HTTP PUT. Try running the "xe vm-import" command with the "--debug" argument to see what an HTTP operation looks like. Cheers, -- Dave Scott XenServer System Architect > On Jan 21, 2014, at 10:19 AM, "Shafi Mohammed S" wrote: > > Hi all , > Can we import an XVA (a VM) into A XenHost by using XAPI calls ? ANy info on this would be of great use . > > > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 10:24:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 10:24:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YVP-00027f-0y; Tue, 21 Jan 2014 10:24:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5YVN-00027Z-U4 for xen-api@lists.xen.org; Tue, 21 Jan 2014 10:24:26 +0000 Received: from [193.109.254.147:22844] by server-4.bemta-14.messagelabs.com id 75/10-03916-9DA4ED25; Tue, 21 Jan 2014 10:24:25 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1390299863!12182005!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22224 invoked from network); 21 Jan 2014 10:24:24 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 10:24:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,695,1384300800"; d="scan'208";a="92751829" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 21 Jan 2014 10:24:22 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 21 Jan 2014 05:24:22 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Tue, 21 Jan 2014 11:24:21 +0100 From: Dave Scott To: Shafi Mohammed S Thread-Topic: [Xen-API] import XVA programatically into a XenHost Thread-Index: AQHPFpJEwqCik1cr4kSL9Or5MoJLg5qO+L+Q Date: Tue, 21 Jan 2014 10:24:20 +0000 Message-ID: <4D8B96BA-81AA-4900-AFEF-BD55CCA16905@eu.citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: MIA1 Cc: Thileepan S , "xen-api@lists.xen.org" Subject: Re: [Xen-API] import XVA programatically into a XenHost X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, The simplest way to do it is to use an HTTP PUT. Try running the "xe vm-import" command with the "--debug" argument to see what an HTTP operation looks like. Cheers, -- Dave Scott XenServer System Architect > On Jan 21, 2014, at 10:19 AM, "Shafi Mohammed S" wrote: > > Hi all , > Can we import an XVA (a VM) into A XenHost by using XAPI calls ? ANy info on this would be of great use . > > > Thanks . > > > Regards, > Shafi, > Vembu Technologies. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 20:07:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 20:07:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5hbW-00058V-4E; Tue, 21 Jan 2014 20:07:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5hbU-00058K-KT; Tue, 21 Jan 2014 20:07:20 +0000 Received: from [85.158.143.35:52682] by server-2.bemta-4.messagelabs.com id 23/FC-11386-773DED25; Tue, 21 Jan 2014 20:07:19 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1390334838!13014639!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2878 invoked from network); 21 Jan 2014 20:07:19 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 20:07:19 -0000 Received: by mail-lb0-f169.google.com with SMTP id q8so6444841lbi.28 for ; Tue, 21 Jan 2014 12:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=RlyEKLbyDhNYHRtAGPpG0WftxP57geFc7v0fM5HMuwk=; b=O8nIln8mqtbHujwAQN+zs0BZsv4GQeC6AfBsdPqgF7qpq26QA0Y4MgRTsTLHTxbcrR HGGpvxrNss5Rq3uN9bhrDwABi3HLwIWT9OrhbyBADxLTPhOXFFAGlees4aoiSDUmMlEF fWSmry//dTjnc8YXv7exdqmx3YLsUWwd6VrowT8egetqQZNwckU7r6X1ldVm/4sFR1hZ i5lvgUElwm8OUydX1zW3RJZaaAtRR8GXCl+LQRmXpu+ovnspOJy/kKGUk4vdJxXpe5Rw UbJ2Tic5dRObwVzyJptdcUuQNGEGIk3CpjMruttiQH9s4zzOivE2dHQYA4KumSx2t3bU puPg== MIME-Version: 1.0 X-Received: by 10.152.20.6 with SMTP id j6mr17216121lae.8.1390334838063; Tue, 21 Jan 2014 12:07:18 -0800 (PST) Received: by 10.112.184.16 with HTTP; Tue, 21 Jan 2014 12:07:18 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 15:07:18 -0500 X-Google-Sender-Auth: tKBBZCMe1AfEvXa9eek3Lvi5POA Message-ID: From: Russ Pavlicek To: Russ Pavlicek Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, xen-devel@lists.xen.org Subject: Re: [Xen-API] TODAY, Jan. 20, is Xen Test Day for Xen 4.4 RC2 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Thank you to all who participated in Monday's Xen Project Test Day for Xen 4.4 RC2! We will be holding another Test Day in a couple weeks. February 3 is currently earmarked for the next round. If you know people who rely on Xen, please let them know. This is their opportunity to test the new release in their environment. Thanks again, and see you in a couple weeks! Russ Pavlicek Xen Project Evangelist On Mon, Jan 20, 2014 at 12:01 AM, Russ Pavlicek wrote: > This is a reminder that today is the Xen Test Day for Xen 4.4 RC2. > > This is the first Test Day for the 4.4 codebase (we had no Test Day > for RC1 due to the number of people taking time off in late December). > As such, it is extremely important that we take some time to make > sure the code is functioning properly. Please try to spend some time > today loading and testing Xen 4.4 RC2. > > General Information about Test Days can be found here: > http://wiki.xenproject.org/wiki/Xen_Test_Days > > and specific instructions for this Test Day are located here: > http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions > > Developers: please consider monitoring the Freenode IRC channel > #xentest today to make sure that people are able to build and test the > code. > > Hope to see you today on #xentest! > > Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 20:07:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 20:07:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5hbW-00058V-4E; Tue, 21 Jan 2014 20:07:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5hbU-00058K-KT; Tue, 21 Jan 2014 20:07:20 +0000 Received: from [85.158.143.35:52682] by server-2.bemta-4.messagelabs.com id 23/FC-11386-773DED25; Tue, 21 Jan 2014 20:07:19 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1390334838!13014639!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2878 invoked from network); 21 Jan 2014 20:07:19 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 20:07:19 -0000 Received: by mail-lb0-f169.google.com with SMTP id q8so6444841lbi.28 for ; Tue, 21 Jan 2014 12:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=RlyEKLbyDhNYHRtAGPpG0WftxP57geFc7v0fM5HMuwk=; b=O8nIln8mqtbHujwAQN+zs0BZsv4GQeC6AfBsdPqgF7qpq26QA0Y4MgRTsTLHTxbcrR HGGpvxrNss5Rq3uN9bhrDwABi3HLwIWT9OrhbyBADxLTPhOXFFAGlees4aoiSDUmMlEF fWSmry//dTjnc8YXv7exdqmx3YLsUWwd6VrowT8egetqQZNwckU7r6X1ldVm/4sFR1hZ i5lvgUElwm8OUydX1zW3RJZaaAtRR8GXCl+LQRmXpu+ovnspOJy/kKGUk4vdJxXpe5Rw UbJ2Tic5dRObwVzyJptdcUuQNGEGIk3CpjMruttiQH9s4zzOivE2dHQYA4KumSx2t3bU puPg== MIME-Version: 1.0 X-Received: by 10.152.20.6 with SMTP id j6mr17216121lae.8.1390334838063; Tue, 21 Jan 2014 12:07:18 -0800 (PST) Received: by 10.112.184.16 with HTTP; Tue, 21 Jan 2014 12:07:18 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 15:07:18 -0500 X-Google-Sender-Auth: tKBBZCMe1AfEvXa9eek3Lvi5POA Message-ID: From: Russ Pavlicek To: Russ Pavlicek Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, xen-devel@lists.xen.org Subject: Re: [Xen-API] TODAY, Jan. 20, is Xen Test Day for Xen 4.4 RC2 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Thank you to all who participated in Monday's Xen Project Test Day for Xen 4.4 RC2! We will be holding another Test Day in a couple weeks. February 3 is currently earmarked for the next round. If you know people who rely on Xen, please let them know. This is their opportunity to test the new release in their environment. Thanks again, and see you in a couple weeks! Russ Pavlicek Xen Project Evangelist On Mon, Jan 20, 2014 at 12:01 AM, Russ Pavlicek wrote: > This is a reminder that today is the Xen Test Day for Xen 4.4 RC2. > > This is the first Test Day for the 4.4 codebase (we had no Test Day > for RC1 due to the number of people taking time off in late December). > As such, it is extremely important that we take some time to make > sure the code is functioning properly. Please try to spend some time > today loading and testing Xen 4.4 RC2. > > General Information about Test Days can be found here: > http://wiki.xenproject.org/wiki/Xen_Test_Days > > and specific instructions for this Test Day are located here: > http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions > > Developers: please consider monitoring the Freenode IRC channel > #xentest today to make sure that people are able to build and test the > code. > > Hope to see you today on #xentest! > > Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 21:48:15 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 21:48:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mw-Og; Tue, 21 Jan 2014 21:48:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mm-0N for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:48:06 +0000 Received: from [85.158.137.68:33893] by server-13.bemta-3.messagelabs.com id 13/C5-28603-51BEED25; Tue, 21 Jan 2014 21:48:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1390340884!10499802!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2604 invoked from network); 21 Jan 2014 21:48:04 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 21 Jan 2014 21:48:04 -0000 Received: (qmail 7733 invoked by uid 634); 21 Jan 2014 21:48:03 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:48:03 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:48:01 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8817676451384626192==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8817676451384626192== Content-Type: multipart/alternative; boundary="Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419" --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:31, David Scott wrote: > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" = optionally depends on "lwt & ipaddr"; some other package depends on = "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? = Perhaps I've misunderstood the meaning of depopts in opam. A workaround = is just to install "ipaddr" first. The intention here is to have: - a 'mirage-types' package that is completely dependency free, and only = has module type definitions with completely abstract types. - a 'mirage-types.lwt' package which specializes the above types with = some concrete common defaults, specifically Lwt for IO and Cstruct for = buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the = module signature, you now need those libraries installed to get the cmi = files for them. The OPAM line of: depopts: [ ("lwt" & "cstruct" & "ipaddr") ] means that if all three of the packages are present, then an optional = dependency (the mirage-types.lwt) will be compiled. However, upstream = users of mirage-types.lwt will thus need to explicitly depend on = lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be = present. -anil --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> = wrote:

NB: I = think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally = depends on "lwt & ipaddr"; some other package depends on "lwt"; but = "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've = misunderstood the meaning of depopts in opam. A workaround is just to = install "ipaddr" first.

The intention = here is to have:

- a 'mirage-types' package = that is completely dependency free, and only has module type definitions = with completely abstract types.
- a 'mirage-types.lwt' package = which specializes the above types with some concrete common defaults, = specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. =  Because these are concrete types in the module signature, you now = need those libraries installed to get the cmi files for = them.

The OPAM line = of:

depopts: [ ("lwt" & "cstruct" & = "ipaddr") ]

means that if all three of the = packages are present, then an optional dependency (the mirage-types.lwt) = will be compiled.  However, upstream users of mirage-types.lwt will = thus need to explicitly depend on lwt/cstruct/ipaddr to ensure that = mirage-types.lwt will actually be = present.

-anil

= --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419-- --===============8817676451384626192== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8817676451384626192==-- From xen-api-bounces@lists.xen.org Tue Jan 21 21:48:15 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 21:48:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mw-Og; Tue, 21 Jan 2014 21:48:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mm-0N for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:48:06 +0000 Received: from [85.158.137.68:33893] by server-13.bemta-3.messagelabs.com id 13/C5-28603-51BEED25; Tue, 21 Jan 2014 21:48:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1390340884!10499802!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2604 invoked from network); 21 Jan 2014 21:48:04 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 21 Jan 2014 21:48:04 -0000 Received: (qmail 7733 invoked by uid 634); 21 Jan 2014 21:48:03 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:48:03 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:48:01 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8817676451384626192==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8817676451384626192== Content-Type: multipart/alternative; boundary="Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419" --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:31, David Scott wrote: > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" = optionally depends on "lwt & ipaddr"; some other package depends on = "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? = Perhaps I've misunderstood the meaning of depopts in opam. A workaround = is just to install "ipaddr" first. The intention here is to have: - a 'mirage-types' package that is completely dependency free, and only = has module type definitions with completely abstract types. - a 'mirage-types.lwt' package which specializes the above types with = some concrete common defaults, specifically Lwt for IO and Cstruct for = buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the = module signature, you now need those libraries installed to get the cmi = files for them. The OPAM line of: depopts: [ ("lwt" & "cstruct" & "ipaddr") ] means that if all three of the packages are present, then an optional = dependency (the mirage-types.lwt) will be compiled. However, upstream = users of mirage-types.lwt will thus need to explicitly depend on = lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be = present. -anil --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> = wrote:

NB: I = think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally = depends on "lwt & ipaddr"; some other package depends on "lwt"; but = "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've = misunderstood the meaning of depopts in opam. A workaround is just to = install "ipaddr" first.

The intention = here is to have:

- a 'mirage-types' package = that is completely dependency free, and only has module type definitions = with completely abstract types.
- a 'mirage-types.lwt' package = which specializes the above types with some concrete common defaults, = specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. =  Because these are concrete types in the module signature, you now = need those libraries installed to get the cmi files for = them.

The OPAM line = of:

depopts: [ ("lwt" & "cstruct" & = "ipaddr") ]

means that if all three of the = packages are present, then an optional dependency (the mirage-types.lwt) = will be compiled.  However, upstream users of mirage-types.lwt will = thus need to explicitly depend on lwt/cstruct/ipaddr to ensure that = mirage-types.lwt will actually be = present.

-anil

= --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419-- --===============8817676451384626192== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8817676451384626192==-- From xen-api-bounces@lists.xen.org Tue Jan 21 21:52:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 21:52:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF4-0002qP-Qq; Tue, 21 Jan 2014 21:52:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF3-0002px-I9 for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:52:17 +0000 Received: from [85.158.137.68:23176] by server-1.bemta-3.messagelabs.com id F2/9A-29598-01CEED25; Tue, 21 Jan 2014 21:52:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1390341135!6849250!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1636 invoked from network); 21 Jan 2014 21:52:15 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 21 Jan 2014 21:52:15 -0000 Received: (qmail 23958 invoked by uid 634); 21 Jan 2014 21:52:15 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:52:15 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:52:13 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 21 Jan 2014, at 21:49, Richard Mortier wrote: > > On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > >> The intention here is to have: >> >> - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. >> - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. > > ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? That's correct. I have a branch in: https://github.com/avsm/mirage/tree/split-libs/types ...with the unified repository, but it's not ready to merge yet. I'm preparing the patch at the moment and will send a separate update about it. -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 21:52:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 21:52:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF4-0002qP-Qq; Tue, 21 Jan 2014 21:52:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF3-0002px-I9 for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:52:17 +0000 Received: from [85.158.137.68:23176] by server-1.bemta-3.messagelabs.com id F2/9A-29598-01CEED25; Tue, 21 Jan 2014 21:52:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1390341135!6849250!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1636 invoked from network); 21 Jan 2014 21:52:15 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 21 Jan 2014 21:52:15 -0000 Received: (qmail 23958 invoked by uid 634); 21 Jan 2014 21:52:15 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:52:15 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:52:13 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 21 Jan 2014, at 21:49, Richard Mortier wrote: > > On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > >> The intention here is to have: >> >> - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. >> - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. > > ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? That's correct. I have a branch in: https://github.com/avsm/mirage/tree/split-libs/types ...with the unified repository, but it's not ready to merge yet. I'm preparing the patch at the moment and will send a separate update about it. -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAZ-0006Hw-Rp; Tue, 21 Jan 2014 22:51:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5iuc-0001dc-2t; Tue, 21 Jan 2014 21:31:10 +0000 Received: from [85.158.139.211:48602] by server-4.bemta-5.messagelabs.com id 0A/FF-26791-D17EED25; Tue, 21 Jan 2014 21:31:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390339866!11110709!1 X-Originating-IP: [209.85.192.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16463 invoked from network); 21 Jan 2014 21:31:08 -0000 Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com) (209.85.192.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:31:08 -0000 Received: by mail-pd0-f177.google.com with SMTP id x10so7394516pdj.36 for ; Tue, 21 Jan 2014 13:31:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=79rxb3QmQKspzbzZKLGCBrPahxUfKFeeI97JuiW7RMM=; b=Rf4NzOpBUsj+zWGwJIDM354jObMWw72xSKjWrhSzNTCBWt34pCr54RMKRBsYkqHAz+ u/ijlbr8FapJaG2mCDzJiUPghxzz9HWeX8cvD/7f/zIwBCdULC52vRqpyEHnXfCS7pKj NyvzBU6iO8QX6Shwhsv4zy8Jl0yIvIlBmQ6a+5WVVfTBnr6qo+KulYnHFudilG2xCdCa kvCWBTTATWcuA9fUGGIF9Zt68EalL42e2weIwM1M7d2mtdKQIDUlp0Xy9wZ+5xILDAXF QeFFLHeqts6ASo1S5THnylrO0UeZbnJ6lli6AuRZh2D0UvD47bkWUEGyCzj9OpEsCzZb e64Q== MIME-Version: 1.0 X-Received: by 10.66.154.169 with SMTP id vp9mr26808862pab.39.1390339864215; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Date: Tue, 21 Jan 2014 21:31:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: xen-api@lists.xenproject.org Subject: [Xen-API] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0827999843848900912==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0827999843848900912== Content-Type: multipart/alternative; boundary=047d7b6dd008b948c404f081b963 --047d7b6dd008b948c404f081b963 Content-Type: text/plain; charset=ISO-8859-1 [cc:d xen-api since the event channel / grant code lives in xapi-project] Hi, I've completed the refactoring I mentioned on the mirage call this afternoon. I've removed the package conflicts between mirage-xen and xenctrl over the virtual package "xenctrl". As a result the packages can be installed in parallel and you can choose between Unix and Xen at application final link-time. If you see any library depend on "xenctrl" or 'xen-event" or "xen-grant", these should be changed to 'xen-evtchn" and "xen-gnt". A Xen application can be built with the "mirage" tool as normal: all the Xen stubs are still in the mirage-xen package. A Unix application which wants to implement a Xen block device (e.g. if you want to boot a regular VM from some fancy new storage type) needs to link with the stubs in the packages: "xen-evtchn.unix" "xen-evtchn.unix.activations" "xen-gnt.unix". For an example of this see: https://github.com/mirage/xen-disk To build this, run: $ opam init git://github.com/mirage/opam-repository#mirage-1.1.0 $ opam install xen-disk NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've misunderstood the meaning of depopts in opam. A workaround is just to install "ipaddr" first. Just to demonstrate that a Mirage Xen kernel can still be built with no conflict: $ opam install mirage $ git checkout git://github.com/avsm/mirage-skeleton $ cd mirage-skeleton/basic $ mirage configure --xen $ mirage build $ sudo xl create -c console.xl Cheers, -- Dave Scott --047d7b6dd008b948c404f081b963 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
[cc:d xen-api since the event channel / grant code li= ves in xapi-project]

Hi,

I've co= mpleted the refactoring I mentioned on the mirage call this afternoon. I= 9;ve removed the package conflicts between mirage-xen and xenctrl over the = virtual package "xenctrl". As a result the packages can be instal= led in parallel and you can choose between Unix and Xen at application fina= l link-time.

If you see any library depend on "xenctrl" or= 'xen-event" or "xen-grant", these should be changed to = 'xen-evtchn" and "xen-gnt". A Xen application can be bui= lt with the "mirage" tool as normal: all the Xen stubs are still = in the mirage-xen package. A Unix application which wants to implement a Xe= n block device (e.g. if you want to boot a regular VM from some fancy new s= torage type) needs to link with the stubs in the packages: "xen-evtchn= .unix" "xen-evtchn.unix.activations" "xen-gnt.unix"= ;. For an example of this see:


To build this, run:=

$ opam install xen-disk

NB: I think I&#= 39;m hitting an opam 1.1.0-beta bug where "mirage-types" optional= ly depends on "lwt & ipaddr"; some other package depends on &= quot;lwt"; but "ipaddr" is not being demanded. Anyone else s= eeing this? Perhaps I've misunderstood the meaning of depopts in opam. = A workaround is just to install "ipaddr" first.

Just to demonstrate that a Mirage Xen kernel can still = be built with no conflict:

$ opam install mirage
$ git checkout git://github.com/avsm/mirage-skeleton
$ cd mirage-skeleton/basic
$ mirage configure --xen
$ mirage build
$ sudo xl create -c console.xl

Cheers,
--=A0
Dave Scott
--047d7b6dd008b948c404f081b963-- --===============0827999843848900912== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0827999843848900912==-- From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAa-0006I1-1I; Tue, 21 Jan 2014 22:51:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jCn-0002mX-MB for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:49:57 +0000 Received: from [85.158.139.211:27964] by server-6.bemta-5.messagelabs.com id FB/52-16310-48BEED25; Tue, 21 Jan 2014 21:49:56 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1390340996!11112626!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11258 invoked from network); 21 Jan 2014 21:49:56 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-8.tower-206.messagelabs.com with SMTP; 21 Jan 2014 21:49:56 -0000 Received: (qmail 6236 invoked from network); 21 Jan 2014 21:49:50 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 21 Jan 2014 21:49:50 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 05301-09 for ; Tue, 21 Jan 2014 21:49:49 +0000 (GMT) Received: (qmail 6220 invoked by uid 599); 21 Jan 2014 21:49:49 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 21 Jan 2014 21:49:49 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1W5jCi-0004MC-8Z; Tue, 21 Jan 2014 21:49:52 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 21 Jan 2014 21:49:51 +0000 Thread-Topic: [MirageOS-devel] xen event channels, grants, block devices etc Thread-Index: Ac8W8rZankjaEodDTP2UuK1Xxunksg== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" , David Scott Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAa-0006I8-7f; Tue, 21 Jan 2014 22:51:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jKC-000350-0Y; Tue, 21 Jan 2014 21:57:36 +0000 Received: from [193.109.254.147:44752] by server-2.bemta-14.messagelabs.com id EC/73-00361-F4DEED25; Tue, 21 Jan 2014 21:57:35 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1390341452!12346542!1 X-Originating-IP: [209.85.192.179] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26850 invoked from network); 21 Jan 2014 21:57:33 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:57:33 -0000 Received: by mail-pd0-f179.google.com with SMTP id q10so6723146pdj.10 for ; Tue, 21 Jan 2014 13:57:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rv8mROIxALEi3n6k7/eETegSPmU+TgKw86rsG6RzVhQ=; b=SSzyOSNS28b+29qz38hitQ0YSjG9YvJo61CbxCiy//1L7J7sRs74gvD50ZWkN0Ia/v CTdhCdgLSMHqNV+d1yHu5OxpbIHTlsgjHm2bA8O/WJMPWbIGA6Nr47WBQpcLXkVBeC3b rQAoR0EB/er1lZ/tpB9ACFZfMApQF+5f/Dg55q2jPchVJ+B+1J+4uq2nm8/1YCShjtXB /GXc+Fad7kxG9czHxQUdkSlWg/oRcH3cQc2NTbL6mCPZGYIWN1NwaQH33uB+KWRXbKMI pVVFNKEw0XN1oCFYAHcUvX3H+Uv62K3a0jkMGSV1tt88Ox0W3rSKGEsvhtkKHZmjPMbi 9BPQ== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr27289809pbc.41.1390341451657; Tue, 21 Jan 2014 13:57:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:57:31 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 21:57:31 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8795526165254384143==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8795526165254384143== Content-Type: multipart/alternative; boundary=047d7b2e14f557b96d04f08218db --047d7b2e14f557b96d04f08218db Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy wrote: > On 21 Jan 2014, at 21:31, David Scott wrote: > > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" > optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; > but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've > misunderstood the meaning of depopts in opam. A workaround is just to > install "ipaddr" first. > > > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only > has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some > concrete common defaults, specifically Lwt for IO and Cstruct for buffer, > Ipaddr.V4.t for ipaddr. Because these are concrete types in the module > signature, you now need those libraries installed to get the cmi files for > them. > > The OPAM line of: > > depopts: [ ("lwt" & "cstruct" & "ipaddr") ] > > means that if all three of the packages are present, then an optional > dependency (the mirage-types.lwt) will be compiled. However, upstream > users of mirage-types.lwt will thus need to explicitly depend on > lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be present. > Ah ok. In my case the BLOCK signature is being used by mirage-block-xen, so I guess I should explicitly add ipaddr to its depends (I'm sure lwt and cstruct are already there). Pity I can't say it depends on 'mirage-types.lwt' -- I guess that would require yet another package. I notice the new mirage-types.lwt will try to build IFF 'lwt' is present: https://github.com/avsm/mirage/blob/split-libs/build#L3 Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the error manifests as a 'mirage-types.lwt' is missing higher up the dependency chain where the missing dependency on 'ipaddr' is? Cheers, Dave --047d7b2e14f557b96d04f08218db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy <anil@recoil.org<= /a>> wrote:
On 2= 1 Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> wrote:

NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types= " optionally depends on "lwt & ipaddr"; some other packa= ge depends on "lwt"; but "ipaddr" is not being demanded= . Anyone else seeing this? Perhaps I've misunderstood the meaning of de= popts in opam. A workaround is just to install "ipaddr" first.

The intention here is to have:
=
- a 'mirage-types' package that is completely depend= ency free, and only has module type definitions with completely abstract ty= pes.
- a 'mirage-types.lwt' package which specializes the above typ= es with some concrete common defaults, specifically Lwt for IO and Cstruct = for buffer, Ipaddr.V4.t for ipaddr. =A0Because these are concrete types in = the module signature, you now need those libraries installed to get the cmi= files for them.

The OPAM line of:

depopts: [ (= "lwt" & "cstruct" & "ipaddr") ]
=

means that if all three of the packages are present, th= en an optional dependency (the mirage-types.lwt) will be compiled. =A0Howev= er, upstream users of mirage-types.lwt will thus need to explicitly depend = on lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be pres= ent.

Ah ok. In my case the BLOCK signatur= e is being used by mirage-block-xen, so I guess I should explicitly add ipa= ddr to its depends (I'm sure lwt and cstruct are already there). Pity I= can't say it depends on 'mirage-types.lwt' -- I guess that wou= ld require yet another package.

I notice the new mirage-types.lwt will try to build IFF= 'lwt' is present:


Perhaps we should change this to IFF 'lwt &am= p; cstruct & ipaddr' so the error manifests as a 'mirage-types.= lwt' is missing higher up the dependency chain where the missing depend= ency on 'ipaddr' is?

Cheers,
Dave
--047d7b2e14f557b96d04f08218db-- --===============8795526165254384143== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8795526165254384143==-- From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAZ-0006Hw-Rp; Tue, 21 Jan 2014 22:51:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5iuc-0001dc-2t; Tue, 21 Jan 2014 21:31:10 +0000 Received: from [85.158.139.211:48602] by server-4.bemta-5.messagelabs.com id 0A/FF-26791-D17EED25; Tue, 21 Jan 2014 21:31:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390339866!11110709!1 X-Originating-IP: [209.85.192.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16463 invoked from network); 21 Jan 2014 21:31:08 -0000 Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com) (209.85.192.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:31:08 -0000 Received: by mail-pd0-f177.google.com with SMTP id x10so7394516pdj.36 for ; Tue, 21 Jan 2014 13:31:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=79rxb3QmQKspzbzZKLGCBrPahxUfKFeeI97JuiW7RMM=; b=Rf4NzOpBUsj+zWGwJIDM354jObMWw72xSKjWrhSzNTCBWt34pCr54RMKRBsYkqHAz+ u/ijlbr8FapJaG2mCDzJiUPghxzz9HWeX8cvD/7f/zIwBCdULC52vRqpyEHnXfCS7pKj NyvzBU6iO8QX6Shwhsv4zy8Jl0yIvIlBmQ6a+5WVVfTBnr6qo+KulYnHFudilG2xCdCa kvCWBTTATWcuA9fUGGIF9Zt68EalL42e2weIwM1M7d2mtdKQIDUlp0Xy9wZ+5xILDAXF QeFFLHeqts6ASo1S5THnylrO0UeZbnJ6lli6AuRZh2D0UvD47bkWUEGyCzj9OpEsCzZb e64Q== MIME-Version: 1.0 X-Received: by 10.66.154.169 with SMTP id vp9mr26808862pab.39.1390339864215; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Date: Tue, 21 Jan 2014 21:31:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: xen-api@lists.xenproject.org Subject: [Xen-API] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0827999843848900912==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0827999843848900912== Content-Type: multipart/alternative; boundary=047d7b6dd008b948c404f081b963 --047d7b6dd008b948c404f081b963 Content-Type: text/plain; charset=ISO-8859-1 [cc:d xen-api since the event channel / grant code lives in xapi-project] Hi, I've completed the refactoring I mentioned on the mirage call this afternoon. I've removed the package conflicts between mirage-xen and xenctrl over the virtual package "xenctrl". As a result the packages can be installed in parallel and you can choose between Unix and Xen at application final link-time. If you see any library depend on "xenctrl" or 'xen-event" or "xen-grant", these should be changed to 'xen-evtchn" and "xen-gnt". A Xen application can be built with the "mirage" tool as normal: all the Xen stubs are still in the mirage-xen package. A Unix application which wants to implement a Xen block device (e.g. if you want to boot a regular VM from some fancy new storage type) needs to link with the stubs in the packages: "xen-evtchn.unix" "xen-evtchn.unix.activations" "xen-gnt.unix". For an example of this see: https://github.com/mirage/xen-disk To build this, run: $ opam init git://github.com/mirage/opam-repository#mirage-1.1.0 $ opam install xen-disk NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've misunderstood the meaning of depopts in opam. A workaround is just to install "ipaddr" first. Just to demonstrate that a Mirage Xen kernel can still be built with no conflict: $ opam install mirage $ git checkout git://github.com/avsm/mirage-skeleton $ cd mirage-skeleton/basic $ mirage configure --xen $ mirage build $ sudo xl create -c console.xl Cheers, -- Dave Scott --047d7b6dd008b948c404f081b963 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
[cc:d xen-api since the event channel / grant code li= ves in xapi-project]

Hi,

I've co= mpleted the refactoring I mentioned on the mirage call this afternoon. I= 9;ve removed the package conflicts between mirage-xen and xenctrl over the = virtual package "xenctrl". As a result the packages can be instal= led in parallel and you can choose between Unix and Xen at application fina= l link-time.

If you see any library depend on "xenctrl" or= 'xen-event" or "xen-grant", these should be changed to = 'xen-evtchn" and "xen-gnt". A Xen application can be bui= lt with the "mirage" tool as normal: all the Xen stubs are still = in the mirage-xen package. A Unix application which wants to implement a Xe= n block device (e.g. if you want to boot a regular VM from some fancy new s= torage type) needs to link with the stubs in the packages: "xen-evtchn= .unix" "xen-evtchn.unix.activations" "xen-gnt.unix"= ;. For an example of this see:


To build this, run:=

$ opam install xen-disk

NB: I think I&#= 39;m hitting an opam 1.1.0-beta bug where "mirage-types" optional= ly depends on "lwt & ipaddr"; some other package depends on &= quot;lwt"; but "ipaddr" is not being demanded. Anyone else s= eeing this? Perhaps I've misunderstood the meaning of depopts in opam. = A workaround is just to install "ipaddr" first.

Just to demonstrate that a Mirage Xen kernel can still = be built with no conflict:

$ opam install mirage
$ git checkout git://github.com/avsm/mirage-skeleton
$ cd mirage-skeleton/basic
$ mirage configure --xen
$ mirage build
$ sudo xl create -c console.xl

Cheers,
--=A0
Dave Scott
--047d7b6dd008b948c404f081b963-- --===============0827999843848900912== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0827999843848900912==-- From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAa-0006I1-1I; Tue, 21 Jan 2014 22:51:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jCn-0002mX-MB for xen-api@lists.xenproject.org; Tue, 21 Jan 2014 21:49:57 +0000 Received: from [85.158.139.211:27964] by server-6.bemta-5.messagelabs.com id FB/52-16310-48BEED25; Tue, 21 Jan 2014 21:49:56 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1390340996!11112626!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11258 invoked from network); 21 Jan 2014 21:49:56 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-8.tower-206.messagelabs.com with SMTP; 21 Jan 2014 21:49:56 -0000 Received: (qmail 6236 invoked from network); 21 Jan 2014 21:49:50 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 21 Jan 2014 21:49:50 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 05301-09 for ; Tue, 21 Jan 2014 21:49:49 +0000 (GMT) Received: (qmail 6220 invoked by uid 599); 21 Jan 2014 21:49:49 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 21 Jan 2014 21:49:49 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1W5jCi-0004MC-8Z; Tue, 21 Jan 2014 21:49:52 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 21 Jan 2014 21:49:51 +0000 Thread-Topic: [MirageOS-devel] xen event channels, grants, block devices etc Thread-Index: Ac8W8rZankjaEodDTP2UuK1Xxunksg== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" , David Scott Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 21 22:51:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 Jan 2014 22:51:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5kAa-0006I8-7f; Tue, 21 Jan 2014 22:51:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jKC-000350-0Y; Tue, 21 Jan 2014 21:57:36 +0000 Received: from [193.109.254.147:44752] by server-2.bemta-14.messagelabs.com id EC/73-00361-F4DEED25; Tue, 21 Jan 2014 21:57:35 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1390341452!12346542!1 X-Originating-IP: [209.85.192.179] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26850 invoked from network); 21 Jan 2014 21:57:33 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:57:33 -0000 Received: by mail-pd0-f179.google.com with SMTP id q10so6723146pdj.10 for ; Tue, 21 Jan 2014 13:57:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rv8mROIxALEi3n6k7/eETegSPmU+TgKw86rsG6RzVhQ=; b=SSzyOSNS28b+29qz38hitQ0YSjG9YvJo61CbxCiy//1L7J7sRs74gvD50ZWkN0Ia/v CTdhCdgLSMHqNV+d1yHu5OxpbIHTlsgjHm2bA8O/WJMPWbIGA6Nr47WBQpcLXkVBeC3b rQAoR0EB/er1lZ/tpB9ACFZfMApQF+5f/Dg55q2jPchVJ+B+1J+4uq2nm8/1YCShjtXB /GXc+Fad7kxG9czHxQUdkSlWg/oRcH3cQc2NTbL6mCPZGYIWN1NwaQH33uB+KWRXbKMI pVVFNKEw0XN1oCFYAHcUvX3H+Uv62K3a0jkMGSV1tt88Ox0W3rSKGEsvhtkKHZmjPMbi 9BPQ== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr27289809pbc.41.1390341451657; Tue, 21 Jan 2014 13:57:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:57:31 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 21:57:31 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy X-Mailman-Approved-At: Tue, 21 Jan 2014 22:51:42 +0000 Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8795526165254384143==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8795526165254384143== Content-Type: multipart/alternative; boundary=047d7b2e14f557b96d04f08218db --047d7b2e14f557b96d04f08218db Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy wrote: > On 21 Jan 2014, at 21:31, David Scott wrote: > > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" > optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; > but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've > misunderstood the meaning of depopts in opam. A workaround is just to > install "ipaddr" first. > > > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only > has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some > concrete common defaults, specifically Lwt for IO and Cstruct for buffer, > Ipaddr.V4.t for ipaddr. Because these are concrete types in the module > signature, you now need those libraries installed to get the cmi files for > them. > > The OPAM line of: > > depopts: [ ("lwt" & "cstruct" & "ipaddr") ] > > means that if all three of the packages are present, then an optional > dependency (the mirage-types.lwt) will be compiled. However, upstream > users of mirage-types.lwt will thus need to explicitly depend on > lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be present. > Ah ok. In my case the BLOCK signature is being used by mirage-block-xen, so I guess I should explicitly add ipaddr to its depends (I'm sure lwt and cstruct are already there). Pity I can't say it depends on 'mirage-types.lwt' -- I guess that would require yet another package. I notice the new mirage-types.lwt will try to build IFF 'lwt' is present: https://github.com/avsm/mirage/blob/split-libs/build#L3 Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the error manifests as a 'mirage-types.lwt' is missing higher up the dependency chain where the missing dependency on 'ipaddr' is? Cheers, Dave --047d7b2e14f557b96d04f08218db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy <anil@recoil.org<= /a>> wrote:
On 2= 1 Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> wrote:

NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types= " optionally depends on "lwt & ipaddr"; some other packa= ge depends on "lwt"; but "ipaddr" is not being demanded= . Anyone else seeing this? Perhaps I've misunderstood the meaning of de= popts in opam. A workaround is just to install "ipaddr" first.

The intention here is to have:
=
- a 'mirage-types' package that is completely depend= ency free, and only has module type definitions with completely abstract ty= pes.
- a 'mirage-types.lwt' package which specializes the above typ= es with some concrete common defaults, specifically Lwt for IO and Cstruct = for buffer, Ipaddr.V4.t for ipaddr. =A0Because these are concrete types in = the module signature, you now need those libraries installed to get the cmi= files for them.

The OPAM line of:

depopts: [ (= "lwt" & "cstruct" & "ipaddr") ]
=

means that if all three of the packages are present, th= en an optional dependency (the mirage-types.lwt) will be compiled. =A0Howev= er, upstream users of mirage-types.lwt will thus need to explicitly depend = on lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be pres= ent.

Ah ok. In my case the BLOCK signatur= e is being used by mirage-block-xen, so I guess I should explicitly add ipa= ddr to its depends (I'm sure lwt and cstruct are already there). Pity I= can't say it depends on 'mirage-types.lwt' -- I guess that wou= ld require yet another package.

I notice the new mirage-types.lwt will try to build IFF= 'lwt' is present:


Perhaps we should change this to IFF 'lwt &am= p; cstruct & ipaddr' so the error manifests as a 'mirage-types.= lwt' is missing higher up the dependency chain where the missing depend= ency on 'ipaddr' is?

Cheers,
Dave
--047d7b2e14f557b96d04f08218db-- --===============8795526165254384143== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8795526165254384143==-- From xen-api-bounces@lists.xen.org Wed Jan 22 14:47:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 22 Jan 2014 14:47:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5z5O-0002Yh-My; Wed, 22 Jan 2014 14:47:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5z5M-0002YW-RE; Wed, 22 Jan 2014 14:47:21 +0000 Received: from [193.109.254.147:32743] by server-9.bemta-14.messagelabs.com id E7/0C-13957-8F9DFD25; Wed, 22 Jan 2014 14:47:20 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1390402038!12534118!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21028 invoked from network); 22 Jan 2014 14:47:19 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2014 14:47:19 -0000 Received: by mail-la0-f53.google.com with SMTP id e16so386710lan.26 for ; Wed, 22 Jan 2014 06:47:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=poOZXL6dnw1WAAIM3KV3tVKr6oK+uwaV4B62XxzVA5I=; b=e7osWRLfjnOxVW9ztSiFcEbe6/q8o+Tqn3QB1zEyTcul5lK4rp7w+axP6eG9r1glL1 PvAZVMJtQRZk/RK415oIMqTuGijPUg9f2F6RhMS+s7YeSEvJ06u6dJ6psraLf4KVkWHZ iFh44DE7P46t/T47TAosthTfYPrhf/0WaPZLK+zIqAvFPJSuqdiJGsKVKTKNV+j0Z4eM z5k9XKYq8Joe7WCRbAyqtl/09nyyEkup5omHugTE7dOpy2GD2l3YeQ9pwkoSDxJQszE8 6/1awrJyFd9xQX714vPpjBDfl7hM9flB7XXaWiakgGglHc8vqBPfhXN60ByWYq5wF4/l C9Ag== MIME-Version: 1.0 X-Received: by 10.152.42.129 with SMTP id o1mr1326289lal.19.1390402038526; Wed, 22 Jan 2014 06:47:18 -0800 (PST) Received: by 10.112.184.16 with HTTP; Wed, 22 Jan 2014 06:47:18 -0800 (PST) Date: Wed, 22 Jan 2014 09:47:18 -0500 X-Google-Sender-Auth: r47kH2GdkpR3E2nl1MW8NcvIRXM Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] REMINDER: Next Monday is Xen Project Document Day X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Remember that the next Xen Project Document Day will be held next Monday, January 27. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on Monday! _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 22 14:47:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 22 Jan 2014 14:47:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5z5O-0002Yh-My; Wed, 22 Jan 2014 14:47:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5z5M-0002YW-RE; Wed, 22 Jan 2014 14:47:21 +0000 Received: from [193.109.254.147:32743] by server-9.bemta-14.messagelabs.com id E7/0C-13957-8F9DFD25; Wed, 22 Jan 2014 14:47:20 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1390402038!12534118!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21028 invoked from network); 22 Jan 2014 14:47:19 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2014 14:47:19 -0000 Received: by mail-la0-f53.google.com with SMTP id e16so386710lan.26 for ; Wed, 22 Jan 2014 06:47:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=poOZXL6dnw1WAAIM3KV3tVKr6oK+uwaV4B62XxzVA5I=; b=e7osWRLfjnOxVW9ztSiFcEbe6/q8o+Tqn3QB1zEyTcul5lK4rp7w+axP6eG9r1glL1 PvAZVMJtQRZk/RK415oIMqTuGijPUg9f2F6RhMS+s7YeSEvJ06u6dJ6psraLf4KVkWHZ iFh44DE7P46t/T47TAosthTfYPrhf/0WaPZLK+zIqAvFPJSuqdiJGsKVKTKNV+j0Z4eM z5k9XKYq8Joe7WCRbAyqtl/09nyyEkup5omHugTE7dOpy2GD2l3YeQ9pwkoSDxJQszE8 6/1awrJyFd9xQX714vPpjBDfl7hM9flB7XXaWiakgGglHc8vqBPfhXN60ByWYq5wF4/l C9Ag== MIME-Version: 1.0 X-Received: by 10.152.42.129 with SMTP id o1mr1326289lal.19.1390402038526; Wed, 22 Jan 2014 06:47:18 -0800 (PST) Received: by 10.112.184.16 with HTTP; Wed, 22 Jan 2014 06:47:18 -0800 (PST) Date: Wed, 22 Jan 2014 09:47:18 -0500 X-Google-Sender-Auth: r47kH2GdkpR3E2nl1MW8NcvIRXM Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk Subject: [Xen-API] REMINDER: Next Monday is Xen Project Document Day X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Remember that the next Xen Project Document Day will be held next Monday, January 27. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on Monday! _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 22 18:32:45 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 22 Jan 2014 18:32:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W62bK-0000wc-Qq; Wed, 22 Jan 2014 18:32:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W62bI-0000wX-Kd for xen-api@lists.xen.org; Wed, 22 Jan 2014 18:32:32 +0000 Received: from [85.158.137.68:46030] by server-1.bemta-3.messagelabs.com id D2/BB-29598-FBE00E25; Wed, 22 Jan 2014 18:32:31 +0000 X-Env-Sender: dan@leesolutions.net X-Msg-Ref: server-2.tower-31.messagelabs.com!1390415549!10730120!1 X-Originating-IP: [209.85.213.172] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7153 invoked from network); 22 Jan 2014 18:32:31 -0000 Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2014 18:32:31 -0000 Received: by mail-ig0-f172.google.com with SMTP id k19so14674173igc.5 for ; Wed, 22 Jan 2014 10:32:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=x2C9w8D0oE1A7Ao3P2r7VUfSy2/htc2C4Z3sxa666V8=; b=mnRkNduS8gCRq8XYUpnOAuKXZv8jRxInIkpvWe2/H2Mbx3ehRffiw9R1Bihoyr9CYy 941wssuYynLLuTn4RuMRa+so7NYpmEHBsBQq6BMtCrfG7+SnKozNftlD5RM+7it2B0vQ GvNzKE/yebIQvE3FUxlZxziw/Gx9dpJciNUtbx0IA/0HQybZu/pb16XYd3WAV4bGJ1z+ AFFC11cdTmeDCnbNFwDl20azh6vN4zJdkoIE73AzCDKcEXyYZWNe/3GMiYOu4r0ZGfTT BhR0HltxvXbKsQJ+LA0f/eGROyMadsW8O1AyzLNY8HNTGFBYC1dQlJhVJb+FrLlvmI4/ GeVQ== X-Gm-Message-State: ALoCoQmG6JMxOV3aJEuo/S/W2nShhnHWzDchPECvnY+Bjng4i56xgVQhiCvhuwWUzR1VS6YJQvWu MIME-Version: 1.0 X-Received: by 10.50.66.139 with SMTP id f11mr24836866igt.41.1390415549436; Wed, 22 Jan 2014 10:32:29 -0800 (PST) Received: by 10.64.232.205 with HTTP; Wed, 22 Jan 2014 10:32:29 -0800 (PST) X-Originating-IP: [23.243.102.54] Date: Wed, 22 Jan 2014 10:32:29 -0800 Message-ID: From: Dan Lee To: "xen-api@lists.xen.org" Subject: [Xen-API] Need a XCP specialist/consultant X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5718582697688367293==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5718582697688367293== Content-Type: multipart/alternative; boundary=047d7bd6b2f4ea247604f09358e8 --047d7bd6b2f4ea247604f09358e8 Content-Type: text/plain; charset=ISO-8859-1 Hi. One of my clients is in desperate need of maintenance on one of their XCP server. Their disk usage bloated to 99% then the vm's started to crash. They have no in-house XCP/XAPI/XenServer expert. They've looked to me to assist but I lack the level of expertise in this arena to be of any useful help. I'm reaching out to the community to find recommendations for an XCP expert-consultant. Feel free to write me and I'll set up a three-way call w/ myself, the client and you. Please let me know your bill rate and I'll pass that along to the client. Thanks a bunch! Dan --047d7bd6b2f4ea247604f09358e8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi. =A0One of my clients is in desperate need of main= tenance on one of their XCP server. =A0Their disk usage bloated to 99% then= the vm's started to crash. =A0They have no in-house XCP/XAPI/XenServer= expert. =A0They've looked to me to assist but I lack the level of expe= rtise in this arena to be of any useful help. =A0I'm reaching out to th= e community to find recommendations for an XCP expert-consultant. =A0Feel f= ree to write me and I'll set up a three-way call w/ myself, the client = and you. =A0Please let me know your bill rate and I'll pass that along = to the client. =A0Thanks a bunch!

Dan
--047d7bd6b2f4ea247604f09358e8-- --===============5718582697688367293== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5718582697688367293==-- From xen-api-bounces@lists.xen.org Wed Jan 22 18:32:45 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 22 Jan 2014 18:32:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W62bK-0000wc-Qq; Wed, 22 Jan 2014 18:32:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W62bI-0000wX-Kd for xen-api@lists.xen.org; Wed, 22 Jan 2014 18:32:32 +0000 Received: from [85.158.137.68:46030] by server-1.bemta-3.messagelabs.com id D2/BB-29598-FBE00E25; Wed, 22 Jan 2014 18:32:31 +0000 X-Env-Sender: dan@leesolutions.net X-Msg-Ref: server-2.tower-31.messagelabs.com!1390415549!10730120!1 X-Originating-IP: [209.85.213.172] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7153 invoked from network); 22 Jan 2014 18:32:31 -0000 Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2014 18:32:31 -0000 Received: by mail-ig0-f172.google.com with SMTP id k19so14674173igc.5 for ; Wed, 22 Jan 2014 10:32:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=x2C9w8D0oE1A7Ao3P2r7VUfSy2/htc2C4Z3sxa666V8=; b=mnRkNduS8gCRq8XYUpnOAuKXZv8jRxInIkpvWe2/H2Mbx3ehRffiw9R1Bihoyr9CYy 941wssuYynLLuTn4RuMRa+so7NYpmEHBsBQq6BMtCrfG7+SnKozNftlD5RM+7it2B0vQ GvNzKE/yebIQvE3FUxlZxziw/Gx9dpJciNUtbx0IA/0HQybZu/pb16XYd3WAV4bGJ1z+ AFFC11cdTmeDCnbNFwDl20azh6vN4zJdkoIE73AzCDKcEXyYZWNe/3GMiYOu4r0ZGfTT BhR0HltxvXbKsQJ+LA0f/eGROyMadsW8O1AyzLNY8HNTGFBYC1dQlJhVJb+FrLlvmI4/ GeVQ== X-Gm-Message-State: ALoCoQmG6JMxOV3aJEuo/S/W2nShhnHWzDchPECvnY+Bjng4i56xgVQhiCvhuwWUzR1VS6YJQvWu MIME-Version: 1.0 X-Received: by 10.50.66.139 with SMTP id f11mr24836866igt.41.1390415549436; Wed, 22 Jan 2014 10:32:29 -0800 (PST) Received: by 10.64.232.205 with HTTP; Wed, 22 Jan 2014 10:32:29 -0800 (PST) X-Originating-IP: [23.243.102.54] Date: Wed, 22 Jan 2014 10:32:29 -0800 Message-ID: From: Dan Lee To: "xen-api@lists.xen.org" Subject: [Xen-API] Need a XCP specialist/consultant X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5718582697688367293==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5718582697688367293== Content-Type: multipart/alternative; boundary=047d7bd6b2f4ea247604f09358e8 --047d7bd6b2f4ea247604f09358e8 Content-Type: text/plain; charset=ISO-8859-1 Hi. One of my clients is in desperate need of maintenance on one of their XCP server. Their disk usage bloated to 99% then the vm's started to crash. They have no in-house XCP/XAPI/XenServer expert. They've looked to me to assist but I lack the level of expertise in this arena to be of any useful help. I'm reaching out to the community to find recommendations for an XCP expert-consultant. Feel free to write me and I'll set up a three-way call w/ myself, the client and you. Please let me know your bill rate and I'll pass that along to the client. Thanks a bunch! Dan --047d7bd6b2f4ea247604f09358e8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi. =A0One of my clients is in desperate need of main= tenance on one of their XCP server. =A0Their disk usage bloated to 99% then= the vm's started to crash. =A0They have no in-house XCP/XAPI/XenServer= expert. =A0They've looked to me to assist but I lack the level of expe= rtise in this arena to be of any useful help. =A0I'm reaching out to th= e community to find recommendations for an XCP expert-consultant. =A0Feel f= ree to write me and I'll set up a three-way call w/ myself, the client = and you. =A0Please let me know your bill rate and I'll pass that along = to the client. =A0Thanks a bunch!

Dan
--047d7bd6b2f4ea247604f09358e8-- --===============5718582697688367293== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5718582697688367293==-- From xen-api-bounces@lists.xen.org Fri Jan 24 02:34:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 24 Jan 2014 02:34:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W6Wb4-0006mE-Ph; Fri, 24 Jan 2014 02:34:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W6Wb3-0006m6-9g for xen-api@lists.xen.org; Fri, 24 Jan 2014 02:34:17 +0000 Received: from [193.109.254.147:33099] by server-7.bemta-14.messagelabs.com id B4/BD-15500-821D1E25; Fri, 24 Jan 2014 02:34:16 +0000 X-Env-Sender: shakeel.butt@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1390530854!12792353!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2744 invoked from network); 24 Jan 2014 02:34:15 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2014 02:34:15 -0000 Received: by mail-oa0-f46.google.com with SMTP id n16so3134831oag.5 for ; Thu, 23 Jan 2014 18:34:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=isamV1a0KT4gv6mYlLHOgMw/kABW7LtBzTsLGPJJMgI=; b=PAUO2ZKuI++lT9TDw08cYwyHfwbbrL0nw6gPka8Mv63geJ6U5RDTwKMdo/OntEF9ro 30ZKDLRoZUG3jj5UonPe0lUxblHBTo9Cw4c5tr2JI0chtywe1w460Q2uNg+c6ttNq5aR yIo9PxvspTQInpIN3yPZo+W9NEPkPJSbcL6lMo3bljVy0X2K2lI2VgbkgBlsGU77wuG0 ufND+PVXLZ6RjXYURDGPHJIPPc9uJYUsczanj2dr+48SYsCoak/e9w/dw0B54jBUSGMP axLoXlp13qd7T63Dmo1IHqKp0iFLpo/OOz5/VF73nKbUOuq/6Nd5FLVDKOcMq7Ek2WPb YZEw== MIME-Version: 1.0 X-Received: by 10.60.59.162 with SMTP id a2mr666279oer.17.1390530854098; Thu, 23 Jan 2014 18:34:14 -0800 (PST) Received: by 10.76.19.13 with HTTP; Thu, 23 Jan 2014 18:34:13 -0800 (PST) Date: Thu, 23 Jan 2014 18:34:13 -0800 Message-ID: From: Shakeel Butt To: xen-api@lists.xen.org Subject: [Xen-API] query regarding Single Server Private Network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I am trying to setup Single Server Private Network (SSPN) on XenServer 6.2 but I also want Dom0 to be able to communicate with the VMs on that private network. I can easily setup this by manually assign internal ip to the bridge created for SSPN but I want to know if I can do this through xapi. thanks, Shakeel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 24 02:34:31 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 24 Jan 2014 02:34:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W6Wb4-0006mE-Ph; Fri, 24 Jan 2014 02:34:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W6Wb3-0006m6-9g for xen-api@lists.xen.org; Fri, 24 Jan 2014 02:34:17 +0000 Received: from [193.109.254.147:33099] by server-7.bemta-14.messagelabs.com id B4/BD-15500-821D1E25; Fri, 24 Jan 2014 02:34:16 +0000 X-Env-Sender: shakeel.butt@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1390530854!12792353!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2744 invoked from network); 24 Jan 2014 02:34:15 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2014 02:34:15 -0000 Received: by mail-oa0-f46.google.com with SMTP id n16so3134831oag.5 for ; Thu, 23 Jan 2014 18:34:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=isamV1a0KT4gv6mYlLHOgMw/kABW7LtBzTsLGPJJMgI=; b=PAUO2ZKuI++lT9TDw08cYwyHfwbbrL0nw6gPka8Mv63geJ6U5RDTwKMdo/OntEF9ro 30ZKDLRoZUG3jj5UonPe0lUxblHBTo9Cw4c5tr2JI0chtywe1w460Q2uNg+c6ttNq5aR yIo9PxvspTQInpIN3yPZo+W9NEPkPJSbcL6lMo3bljVy0X2K2lI2VgbkgBlsGU77wuG0 ufND+PVXLZ6RjXYURDGPHJIPPc9uJYUsczanj2dr+48SYsCoak/e9w/dw0B54jBUSGMP axLoXlp13qd7T63Dmo1IHqKp0iFLpo/OOz5/VF73nKbUOuq/6Nd5FLVDKOcMq7Ek2WPb YZEw== MIME-Version: 1.0 X-Received: by 10.60.59.162 with SMTP id a2mr666279oer.17.1390530854098; Thu, 23 Jan 2014 18:34:14 -0800 (PST) Received: by 10.76.19.13 with HTTP; Thu, 23 Jan 2014 18:34:13 -0800 (PST) Date: Thu, 23 Jan 2014 18:34:13 -0800 Message-ID: From: Shakeel Butt To: xen-api@lists.xen.org Subject: [Xen-API] query regarding Single Server Private Network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I am trying to setup Single Server Private Network (SSPN) on XenServer 6.2 but I also want Dom0 to be able to communicate with the VMs on that private network. I can easily setup this by manually assign internal ip to the bridge created for SSPN but I want to know if I can do this through xapi. thanks, Shakeel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 26 09:55:53 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 26 Jan 2014 09:55:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRK-0006Wg-OD; Sun, 26 Jan 2014 09:55:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRJ-0006WS-Bb for xen-api@lists.xenproject.org; Sun, 26 Jan 2014 09:55:41 +0000 Received: from [193.109.254.147:64190] by server-4.bemta-14.messagelabs.com id 4D/E2-03916-C9BD4E25; Sun, 26 Jan 2014 09:55:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1390730139!11729995!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15554 invoked from network); 26 Jan 2014 09:55:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 26 Jan 2014 09:55:39 -0000 Received: (qmail 1934 invoked by uid 634); 26 Jan 2014 09:55:38 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 09:55:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 09:55:36 +0000 Message-Id: <4C257AB4-AF84-4C3F-AB76-78D5A6CEE281@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8856583803922012058==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8856583803922012058== Content-Type: multipart/alternative; boundary="Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3" --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:57, David Scott wrote: >=20 > I notice the new mirage-types.lwt will try to build IFF 'lwt' is = present: >=20 > https://github.com/avsm/mirage/blob/split-libs/build#L3 >=20 > Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the = error manifests as a 'mirage-types.lwt' is missing higher up the = dependency chain where the missing dependency on 'ipaddr' is? Thanks for spotting this. I've pushed a fix to my branch with the = correct dependencies. cheers, Anil= --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:57, David Scott <scott.dj@gmail.com> = wrote:


I notice the new mirage-types.lwt = will try to build IFF 'lwt' is present:


Perhaps we should change this to IFF = 'lwt & cstruct & ipaddr' so the error manifests as a = 'mirage-types.lwt' is missing higher up the dependency chain where the = missing dependency on 'ipaddr' = is?

Thanks for spotting this. =  I've pushed a fix to my branch with the correct = dependencies.

cheers,
Anil
= = --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3-- --===============8856583803922012058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8856583803922012058==-- From xen-api-bounces@lists.xen.org Sun Jan 26 09:55:53 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 26 Jan 2014 09:55:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRK-0006Wg-OD; Sun, 26 Jan 2014 09:55:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRJ-0006WS-Bb for xen-api@lists.xenproject.org; Sun, 26 Jan 2014 09:55:41 +0000 Received: from [193.109.254.147:64190] by server-4.bemta-14.messagelabs.com id 4D/E2-03916-C9BD4E25; Sun, 26 Jan 2014 09:55:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1390730139!11729995!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15554 invoked from network); 26 Jan 2014 09:55:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 26 Jan 2014 09:55:39 -0000 Received: (qmail 1934 invoked by uid 634); 26 Jan 2014 09:55:38 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 09:55:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 09:55:36 +0000 Message-Id: <4C257AB4-AF84-4C3F-AB76-78D5A6CEE281@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [Xen-API] [MirageOS-devel] xen event channels, grants, block devices etc X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8856583803922012058==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8856583803922012058== Content-Type: multipart/alternative; boundary="Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3" --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:57, David Scott wrote: >=20 > I notice the new mirage-types.lwt will try to build IFF 'lwt' is = present: >=20 > https://github.com/avsm/mirage/blob/split-libs/build#L3 >=20 > Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the = error manifests as a 'mirage-types.lwt' is missing higher up the = dependency chain where the missing dependency on 'ipaddr' is? Thanks for spotting this. I've pushed a fix to my branch with the = correct dependencies. cheers, Anil= --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:57, David Scott <scott.dj@gmail.com> = wrote:


I notice the new mirage-types.lwt = will try to build IFF 'lwt' is present:


Perhaps we should change this to IFF = 'lwt & cstruct & ipaddr' so the error manifests as a = 'mirage-types.lwt' is missing higher up the dependency chain where the = missing dependency on 'ipaddr' = is?

Thanks for spotting this. =  I've pushed a fix to my branch with the correct = dependencies.

cheers,
Anil
= = --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3-- --===============8856583803922012058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8856583803922012058==-- From xen-api-bounces@lists.xen.org Sun Jan 26 14:50:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 26 Jan 2014 14:50:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7R2c-0006ig-TI; Sun, 26 Jan 2014 14:50:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7R2b-0006ia-Jd for xen-api@lists.xen.org; Sun, 26 Jan 2014 14:50:29 +0000 Received: from [85.158.137.68:48394] by server-9.bemta-3.messagelabs.com id 87/42-13104-4B025E25; Sun, 26 Jan 2014 14:50:28 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-16.tower-31.messagelabs.com!1390747827!10576501!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7482 invoked from network); 26 Jan 2014 14:50:28 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-16.tower-31.messagelabs.com with SMTP; 26 Jan 2014 14:50:28 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d69 with ME id JeqS1n00G3zjds103eqS3n; Sun, 26 Jan 2014 15:50:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B48B1161D78; Sun, 26 Jan 2014 15:50:26 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Z8LxrQabS5iw; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A2069162064; Sun, 26 Jan 2014 15:50:25 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IfnnCnFJuefA; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 648C4161D78; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Message-ID: <52E520B1.3050409@tranquil-it-systems.fr> Date: Sun, 26 Jan 2014 15:50:25 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shakeel Butt References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] query regarding Single Server Private Network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shakeel, > I am trying to setup Single Server Private Network (SSPN) on XenServer > 6.2 but I also want Dom0 to be able to communicate with the VMs on > that private network. better than having a direct connection between your private network and = the dom0 bridge, I'd rather advise you to setup a virtual vm as a router = with a network port in dom0 management interface bridge and a network = port in the SSPN. This way you can have better control on what flows to = and fro you private network. Cheers, Denis > > I can easily setup this by manually assign internal ip to the bridge > created for SSPN but I want to know if I can do this through xapi. > > thanks, > Shakeel > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 26 14:50:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 26 Jan 2014 14:50:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7R2c-0006ig-TI; Sun, 26 Jan 2014 14:50:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7R2b-0006ia-Jd for xen-api@lists.xen.org; Sun, 26 Jan 2014 14:50:29 +0000 Received: from [85.158.137.68:48394] by server-9.bemta-3.messagelabs.com id 87/42-13104-4B025E25; Sun, 26 Jan 2014 14:50:28 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-16.tower-31.messagelabs.com!1390747827!10576501!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7482 invoked from network); 26 Jan 2014 14:50:28 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-16.tower-31.messagelabs.com with SMTP; 26 Jan 2014 14:50:28 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d69 with ME id JeqS1n00G3zjds103eqS3n; Sun, 26 Jan 2014 15:50:27 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B48B1161D78; Sun, 26 Jan 2014 15:50:26 +0100 (CET) Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Z8LxrQabS5iw; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A2069162064; Sun, 26 Jan 2014 15:50:25 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IfnnCnFJuefA; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 648C4161D78; Sun, 26 Jan 2014 15:50:25 +0100 (CET) Message-ID: <52E520B1.3050409@tranquil-it-systems.fr> Date: Sun, 26 Jan 2014 15:50:25 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Shakeel Butt References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] query regarding Single Server Private Network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shakeel, > I am trying to setup Single Server Private Network (SSPN) on XenServer > 6.2 but I also want Dom0 to be able to communicate with the VMs on > that private network. better than having a direct connection between your private network and = the dom0 bridge, I'd rather advise you to setup a virtual vm as a router = with a network port in dom0 management interface bridge and a network = port in the SSPN. This way you can have better control on what flows to = and fro you private network. Cheers, Denis > > I can easily setup this by manually assign internal ip to the bridge > created for SSPN but I want to know if I can do this through xapi. > > thanks, > Shakeel > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 27 13:52:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 27 Jan 2014 13:52:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7mbc-0006FY-5P; Mon, 27 Jan 2014 13:52:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7mbb-0006FN-2T; Mon, 27 Jan 2014 13:52:03 +0000 Received: from [85.158.143.35:43261] by server-3.bemta-4.messagelabs.com id 1C/2F-32360-28466E25; Mon, 27 Jan 2014 13:52:02 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1390830720!1069730!1 X-Originating-IP: [209.85.215.46] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32597 invoked from network); 27 Jan 2014 13:52:01 -0000 Received: from mail-la0-f46.google.com (HELO mail-la0-f46.google.com) (209.85.215.46) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 13:52:01 -0000 Received: by mail-la0-f46.google.com with SMTP id b8so4436323lan.5 for ; Mon, 27 Jan 2014 05:52:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=vMnuYiRqs9H8ftj71Fqt+goDY1muv+xoMcrcel79nLQ=; b=q8QZBHwGf5dIJlKjW6ycvOEpXiDhovgmeeRUBmVRGuTdi2tjyYOWodI66iRMAo0iWi msLSeGC95IvW4i5egW9YzJLv7LYo6sh+ig/uqnAC7Y5P5hyu7w8hbM+q2+PjRgGdT++O Q+MRQ40blRkgyZXCfO35QmWh1iERgrcbThW3x/TLl7d7fkklarqT8Fg5K8gddZOiWW1C UtD8h+EjAjbwVU2h9xNR1tY0jjXpOLvMnF2R9qndzDLUB2Pe0IWd+nnzoUXPOG2Ko5uA IIQLM0TPqGazjeALOjICCk4hFVFDg7JRLxdDwoOTR8zRjGRwChoN5lhKzYZUrK75HU/E 6Kfg== MIME-Version: 1.0 X-Received: by 10.152.164.166 with SMTP id yr6mr17584163lab.1.1390830720257; Mon, 27 Jan 2014 05:52:00 -0800 (PST) Received: by 10.112.72.72 with HTTP; Mon, 27 Jan 2014 05:52:00 -0800 (PST) Date: Mon, 27 Jan 2014 08:52:00 -0500 X-Google-Sender-Auth: 5NSolALttpOH3jOAEHdMxnURh7E Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org Subject: [Xen-API] TODAY is Xen Document Day! X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Today is the day! Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Not sure what needs attention? Here is the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! If you haven't requested to be made a Wiki editor, just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html Hope to see you in #xendocs! Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 27 13:52:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 27 Jan 2014 13:52:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7mbc-0006FY-5P; Mon, 27 Jan 2014 13:52:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7mbb-0006FN-2T; Mon, 27 Jan 2014 13:52:03 +0000 Received: from [85.158.143.35:43261] by server-3.bemta-4.messagelabs.com id 1C/2F-32360-28466E25; Mon, 27 Jan 2014 13:52:02 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1390830720!1069730!1 X-Originating-IP: [209.85.215.46] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32597 invoked from network); 27 Jan 2014 13:52:01 -0000 Received: from mail-la0-f46.google.com (HELO mail-la0-f46.google.com) (209.85.215.46) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 13:52:01 -0000 Received: by mail-la0-f46.google.com with SMTP id b8so4436323lan.5 for ; Mon, 27 Jan 2014 05:52:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=vMnuYiRqs9H8ftj71Fqt+goDY1muv+xoMcrcel79nLQ=; b=q8QZBHwGf5dIJlKjW6ycvOEpXiDhovgmeeRUBmVRGuTdi2tjyYOWodI66iRMAo0iWi msLSeGC95IvW4i5egW9YzJLv7LYo6sh+ig/uqnAC7Y5P5hyu7w8hbM+q2+PjRgGdT++O Q+MRQ40blRkgyZXCfO35QmWh1iERgrcbThW3x/TLl7d7fkklarqT8Fg5K8gddZOiWW1C UtD8h+EjAjbwVU2h9xNR1tY0jjXpOLvMnF2R9qndzDLUB2Pe0IWd+nnzoUXPOG2Ko5uA IIQLM0TPqGazjeALOjICCk4hFVFDg7JRLxdDwoOTR8zRjGRwChoN5lhKzYZUrK75HU/E 6Kfg== MIME-Version: 1.0 X-Received: by 10.152.164.166 with SMTP id yr6mr17584163lab.1.1390830720257; Mon, 27 Jan 2014 05:52:00 -0800 (PST) Received: by 10.112.72.72 with HTTP; Mon, 27 Jan 2014 05:52:00 -0800 (PST) Date: Mon, 27 Jan 2014 08:52:00 -0500 X-Google-Sender-Auth: 5NSolALttpOH3jOAEHdMxnURh7E Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org Subject: [Xen-API] TODAY is Xen Document Day! X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Today is the day! Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Not sure what needs attention? Here is the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! If you haven't requested to be made a Wiki editor, just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html Hope to see you in #xendocs! Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 27 16:11:12 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 27 Jan 2014 16:11:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7om7-0005Gu-8q; Mon, 27 Jan 2014 16:11:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7om5-0005Gn-Cx for xen-api@lists.xen.org; Mon, 27 Jan 2014 16:11:02 +0000 Received: from [85.158.143.35:59880] by server-3.bemta-4.messagelabs.com id A7/6F-32360-41586E25; Mon, 27 Jan 2014 16:11:00 +0000 X-Env-Sender: witold.krecicki@techstorage.pl X-Msg-Ref: server-12.tower-21.messagelabs.com!1390839060!1107855!1 X-Originating-IP: [193.17.41.200] X-SpamReason: No, hits=0.0 required=7.0 tests=FROM_EXCESS_QP, SUBJECT_EXCESS_QP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20208 invoked from network); 27 Jan 2014 16:11:00 -0000 Received: from moh2-ve2.go2.pl (HELO moh2-ve2.go2.pl) (193.17.41.200) by server-12.tower-21.messagelabs.com with SMTP; 27 Jan 2014 16:11:00 -0000 Received: from moh2-ve2.go2.pl (unknown [10.0.0.200]) by moh2-ve2.go2.pl (Postfix) with ESMTP id DBD76B006E4 for ; Mon, 27 Jan 2014 17:10:58 +0100 (CET) Received: from o2.pl (unknown [10.0.0.4]) by moh2-ve2.go2.pl (Postfix) with SMTP for ; Mon, 27 Jan 2014 17:10:58 +0100 (CET) From: =?UTF-8?Q?Witold_Krecicki?= To: xen-api@lists.xen.org Mime-Version: 1.0 Message-ID: <7239457e.27b45df4.52e68512.bfa84@techstorage.pl> Date: Mon, 27 Jan 2014 17:10:58 +0100 X-Originator: 37.233.96.69 Subject: [Xen-API] =?utf-8?q?Kronos=40ubuntu_13=2E10_-_Message_too_long_wh?= =?utf-8?q?en_trying_to_migrate_VM?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org When trying to migrate VM from one host to another I get: message: INTERNAL_ERROR: [ XenguestHelper.Xenctrl_domain_restore_failure(1, " Error when reading batch (90 = Message too long)\\\"") ] And in log: Sender Caught exception: VM_MIGRATE_FAILED: [ OpaqueRef:c2091c34-2541-6d5c-934e-28e53f4cf16e; OpaqueRef:b3bb7bd5-2e97-c586-d554-c3f576384c46; OpaqueRef:1db9124e-8168-7bc0-21c5-7ed730b19266; INTERNAL_ERROR: [ Domain.Xenguest_failure("Received error from xenguesthelper: xc_domain_save 1 Error when flushing output buffer (32 = Broken pipe)\\\"") ] ] Task object contains error: INTERNAL_ERROR [ INTERNAL_ERROR: [ XenguestHelper.Xenctrl_domain_restore_failure(1, " Error when reading batch (90 = Message too long)\\\"") ] ] Is that a problem with Xen-API or with Xen (4.3) itself? WK _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 27 16:11:12 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 27 Jan 2014 16:11:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7om7-0005Gu-8q; Mon, 27 Jan 2014 16:11:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7om5-0005Gn-Cx for xen-api@lists.xen.org; Mon, 27 Jan 2014 16:11:02 +0000 Received: from [85.158.143.35:59880] by server-3.bemta-4.messagelabs.com id A7/6F-32360-41586E25; Mon, 27 Jan 2014 16:11:00 +0000 X-Env-Sender: witold.krecicki@techstorage.pl X-Msg-Ref: server-12.tower-21.messagelabs.com!1390839060!1107855!1 X-Originating-IP: [193.17.41.200] X-SpamReason: No, hits=0.0 required=7.0 tests=FROM_EXCESS_QP, SUBJECT_EXCESS_QP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20208 invoked from network); 27 Jan 2014 16:11:00 -0000 Received: from moh2-ve2.go2.pl (HELO moh2-ve2.go2.pl) (193.17.41.200) by server-12.tower-21.messagelabs.com with SMTP; 27 Jan 2014 16:11:00 -0000 Received: from moh2-ve2.go2.pl (unknown [10.0.0.200]) by moh2-ve2.go2.pl (Postfix) with ESMTP id DBD76B006E4 for ; Mon, 27 Jan 2014 17:10:58 +0100 (CET) Received: from o2.pl (unknown [10.0.0.4]) by moh2-ve2.go2.pl (Postfix) with SMTP for ; Mon, 27 Jan 2014 17:10:58 +0100 (CET) From: =?UTF-8?Q?Witold_Krecicki?= To: xen-api@lists.xen.org Mime-Version: 1.0 Message-ID: <7239457e.27b45df4.52e68512.bfa84@techstorage.pl> Date: Mon, 27 Jan 2014 17:10:58 +0100 X-Originator: 37.233.96.69 Subject: [Xen-API] =?utf-8?q?Kronos=40ubuntu_13=2E10_-_Message_too_long_wh?= =?utf-8?q?en_trying_to_migrate_VM?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org When trying to migrate VM from one host to another I get: message: INTERNAL_ERROR: [ XenguestHelper.Xenctrl_domain_restore_failure(1, " Error when reading batch (90 = Message too long)\\\"") ] And in log: Sender Caught exception: VM_MIGRATE_FAILED: [ OpaqueRef:c2091c34-2541-6d5c-934e-28e53f4cf16e; OpaqueRef:b3bb7bd5-2e97-c586-d554-c3f576384c46; OpaqueRef:1db9124e-8168-7bc0-21c5-7ed730b19266; INTERNAL_ERROR: [ Domain.Xenguest_failure("Received error from xenguesthelper: xc_domain_save 1 Error when flushing output buffer (32 = Broken pipe)\\\"") ] ] Task object contains error: INTERNAL_ERROR [ INTERNAL_ERROR: [ XenguestHelper.Xenctrl_domain_restore_failure(1, " Error when reading batch (90 = Message too long)\\\"") ] ] Is that a problem with Xen-API or with Xen (4.3) itself? WK _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 28 00:49:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 00:49:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7wrs-0002iv-6R; Tue, 28 Jan 2014 00:49:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W7wrp-0002iV-SS for xen-api@lists.xen.org; Tue, 28 Jan 2014 00:49:30 +0000 Received: from [193.109.254.147:3245] by server-2.bemta-14.messagelabs.com id 05/03-00361-99EF6E25; Tue, 28 Jan 2014 00:49:29 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1390870167!228494!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6103 invoked from network); 28 Jan 2014 00:49:28 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 00:49:28 -0000 Received: by mail-qa0-f50.google.com with SMTP id cm18so8445885qab.9 for ; Mon, 27 Jan 2014 16:49:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hAgpcxpE8vQBcJ9Hz3jMV+Qxbsk5fidXZ+G0+fJgV+M=; b=I+QmCGWnyeMgf7V0lX9UZ9f82zG5OqKTKOkSYo/4G4if7xTVjtDiP4aCiCoM/tR1mp WN0pXFdDBMSWFe8IQUMDL5E2Ifi116Sy7aQ4LNznTbYfIaobdiCuWpZ37Y/WJJGNJpHf uQUbGTkBsyU1/6QVuH5Ltt/I3dyF4ATLVgS6Eq+ZfnY/ljQuMS+RAMgwbp6HbxhB0Stm aeTcZHrefuAkGAX2uIYtZP3qkT4GwfMHFHtetdajJtuz3gWFli0KDCvXPHSwOKU/H8p3 F84t6hyhMn/Bg04m3Qh/BasByCND9YIar8pboI9bR1FliDspsAZoXauCO0FwvhlnAdfL eYYA== MIME-Version: 1.0 X-Received: by 10.140.51.170 with SMTP id u39mr45395925qga.69.1390870166865; Mon, 27 Jan 2014 16:49:26 -0800 (PST) Received: by 10.224.78.12 with HTTP; Mon, 27 Jan 2014 16:49:26 -0800 (PST) Date: Tue, 28 Jan 2014 06:19:26 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , "xs-devel@lists.xenserver.org" Subject: [Xen-API] How to enable blkio cgroup in xenserver X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3751354922698528321==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3751354922698528321== Content-Type: multipart/alternative; boundary=001a11351916398af904f0fd3239 --001a11351916398af904f0fd3239 Content-Type: text/plain; charset=ISO-8859-1 Hi Devops, I'm trying to figure out a way to enable blkio cgroup in xenserver as per https://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt Xenserver 6.1 linux-xen kernel has support for CGROUP but to my surprise CONFIG_BLK_CGROUP looks to be removed & CGROUP is not enabled at all. There is also no source related to blkio in src/block/Kconfig however I was able to recompile and install-test kernel with CONFIG_CGROUPS=yes. Can anyone help out about how this can be added ? Is it okay to add relative source files in src/block/ and update the Kconfig to recompile and try ? Xenserver seriously lacks behind without VM Disk QoS control like in VmWare or HyperV2012, CGROUP seems the right way to do it unless there is another option. Regards, Rushikesh --001a11351916398af904f0fd3239 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Devops,

I'm trying to figure out= a way to enable blkio cgroup in xenserver as per=A0https://www.kern= el.org/doc/Documentation/cgroups/blkio-controller.txt

Xenserver 6.1 linux-xen kernel has support for CGROUP b= ut to my surprise CONFIG_BLK_CGROUP looks to be removed & CGROUP is not= enabled at all. There is also no source related to blkio in src/block/Kcon= fig however I was able to recompile and install-test kernel with CONFIG_CGR= OUPS=3Dyes.


Can anyone help out about how this can b= e added ? Is it okay to add relative source files in src/block/ and update = the Kconfig to recompile and try ?

Xenserver serio= usly lacks behind without VM Disk QoS control like in VmWare or HyperV2012,= CGROUP seems the right way to do it unless there is another option.


Regards,
Rushikesh
--001a11351916398af904f0fd3239-- --===============3751354922698528321== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3751354922698528321==-- From xen-api-bounces@lists.xen.org Tue Jan 28 00:49:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 00:49:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7wrs-0002iv-6R; Tue, 28 Jan 2014 00:49:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1W7wrp-0002iV-SS for xen-api@lists.xen.org; Tue, 28 Jan 2014 00:49:30 +0000 Received: from [193.109.254.147:3245] by server-2.bemta-14.messagelabs.com id 05/03-00361-99EF6E25; Tue, 28 Jan 2014 00:49:29 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1390870167!228494!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6103 invoked from network); 28 Jan 2014 00:49:28 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 00:49:28 -0000 Received: by mail-qa0-f50.google.com with SMTP id cm18so8445885qab.9 for ; Mon, 27 Jan 2014 16:49:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hAgpcxpE8vQBcJ9Hz3jMV+Qxbsk5fidXZ+G0+fJgV+M=; b=I+QmCGWnyeMgf7V0lX9UZ9f82zG5OqKTKOkSYo/4G4if7xTVjtDiP4aCiCoM/tR1mp WN0pXFdDBMSWFe8IQUMDL5E2Ifi116Sy7aQ4LNznTbYfIaobdiCuWpZ37Y/WJJGNJpHf uQUbGTkBsyU1/6QVuH5Ltt/I3dyF4ATLVgS6Eq+ZfnY/ljQuMS+RAMgwbp6HbxhB0Stm aeTcZHrefuAkGAX2uIYtZP3qkT4GwfMHFHtetdajJtuz3gWFli0KDCvXPHSwOKU/H8p3 F84t6hyhMn/Bg04m3Qh/BasByCND9YIar8pboI9bR1FliDspsAZoXauCO0FwvhlnAdfL eYYA== MIME-Version: 1.0 X-Received: by 10.140.51.170 with SMTP id u39mr45395925qga.69.1390870166865; Mon, 27 Jan 2014 16:49:26 -0800 (PST) Received: by 10.224.78.12 with HTTP; Mon, 27 Jan 2014 16:49:26 -0800 (PST) Date: Tue, 28 Jan 2014 06:19:26 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , "xs-devel@lists.xenserver.org" Subject: [Xen-API] How to enable blkio cgroup in xenserver X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3751354922698528321==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3751354922698528321== Content-Type: multipart/alternative; boundary=001a11351916398af904f0fd3239 --001a11351916398af904f0fd3239 Content-Type: text/plain; charset=ISO-8859-1 Hi Devops, I'm trying to figure out a way to enable blkio cgroup in xenserver as per https://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt Xenserver 6.1 linux-xen kernel has support for CGROUP but to my surprise CONFIG_BLK_CGROUP looks to be removed & CGROUP is not enabled at all. There is also no source related to blkio in src/block/Kconfig however I was able to recompile and install-test kernel with CONFIG_CGROUPS=yes. Can anyone help out about how this can be added ? Is it okay to add relative source files in src/block/ and update the Kconfig to recompile and try ? Xenserver seriously lacks behind without VM Disk QoS control like in VmWare or HyperV2012, CGROUP seems the right way to do it unless there is another option. Regards, Rushikesh --001a11351916398af904f0fd3239 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Devops,

I'm trying to figure out= a way to enable blkio cgroup in xenserver as per=A0https://www.kern= el.org/doc/Documentation/cgroups/blkio-controller.txt

Xenserver 6.1 linux-xen kernel has support for CGROUP b= ut to my surprise CONFIG_BLK_CGROUP looks to be removed & CGROUP is not= enabled at all. There is also no source related to blkio in src/block/Kcon= fig however I was able to recompile and install-test kernel with CONFIG_CGR= OUPS=3Dyes.


Can anyone help out about how this can b= e added ? Is it okay to add relative source files in src/block/ and update = the Kconfig to recompile and try ?

Xenserver serio= usly lacks behind without VM Disk QoS control like in VmWare or HyperV2012,= CGROUP seems the right way to do it unless there is another option.


Regards,
Rushikesh
--001a11351916398af904f0fd3239-- --===============3751354922698528321== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3751354922698528321==-- From xen-api-bounces@lists.xen.org Tue Jan 28 13:55:10 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 13:55:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897z-0006UB-N8; Tue, 28 Jan 2014 13:54:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897y-0006Tt-Fn; Tue, 28 Jan 2014 13:54:58 +0000 Received: from [85.158.143.35:13578] by server-2.bemta-4.messagelabs.com id 13/3F-11386-1B6B7E25; Tue, 28 Jan 2014 13:54:57 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1390917296!1359153!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8882 invoked from network); 28 Jan 2014 13:54:56 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:54:56 -0000 Received: by mail-wg0-f45.google.com with SMTP id n12so842750wgh.24 for ; Tue, 28 Jan 2014 05:54:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1KZm4BjhqSNlL7j3KoXkcYOsI5joh9Z2wFRDmUrUbnM=; b=Gk21K3oqXclgM6IXLhBFefRObLR54Op9UZgYzrde4UnRUiE9vEY9TyefIFHLINocQ4 qJvZDc66nqJs6IdUSVf6fnMeQCZqzzM64Bog9a9Gms6EZ/HYDmK7qutxxdeuOoCRDgP6 hUCjM+P7qjp+5qOU/OQ8s1FEqjpkLJ+H3cIjolkvbuhCJphGwUdAj7ETs2mOYHc4PLNM MlD1/SlyM6RebilWbtcBw/bqT5INmQVSfcRjOuh7znDY/+vkg2IEjIqEkXlU6B/2CP7z tWe5HBC24iJz6xiXEUQFLwkqEhj/6EVWXyX4Xjn99LKLP9EkxZedeq2ZKU4A6+uz117Z 7M+w== X-Received: by 10.181.13.40 with SMTP id ev8mr2134573wid.16.1390917296523; Tue, 28 Jan 2014 05:54:56 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id fb8sm11574023wic.3.2014.01.28.05.54.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 05:54:55 -0800 (PST) Message-ID: <52E7B6AF.3050604@xen.org> Date: Tue, 28 Jan 2014 13:54:55 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52DCE9FA.6010400@xen.org> In-Reply-To: <52DCE9FA.6010400@xen.org> Subject: Re: [Xen-API] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I have not gotten any reply to this thread. I saw Wei Lui and Andr=E9s = Lagar-Cavilla make changes to the project list. Please go through the = items below and make changes as suggested. Otherwise, our chances to get = into GSoC 2014 will be relatively slim. Lars On 20/01/2014 09:18, Lars Kurth wrote: > Hi all, > > the GSoC application deadline is coming up : Feb 2014. If we want to = > have any chance of getting accepted this year, we ought to get our = > project list into good shape. The project list and how the project and = > menters present themselves has a bigger impact on whether we get = > accepted than the actual application. > > Also, I would like to add a mentor section this year: a short bio, = > what the mentor cares about and a picture. This will help make the = > project list more real. > > We have *4 weeks* to do this. The bar for GSoC has been getting = > increasingly high. I know, we are tied down with Xen 4.4, but this is = > something you need to do if you want the Xen Project to participate. > > a) Please, update = > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently = > (these need to be in good shape *before* the application). What I need = > you to do is: > a.1) Remove items that are done > a.2) Add new work items : we ought to have a few sexy topics on say = > Real-time, mobile and some of the other segments (assuming we can get HW) > a.3) All project proposals need to be peer reviewed *and* clear ... = > The peer review process for projects we put in place last year worked = > well, by which we had past mentors sign of project proposals that were = > in good enough state. > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should = > get these listed on the respective other programs. And we should link = > to these from our project page. > > Best Regards > Lars > P.S.: I will also see whether we can participate as Xen Project under = > the LF GSoC program, but last year there was push-back and I don't = > expect this to change > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 28 13:55:10 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 13:55:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897z-0006UB-N8; Tue, 28 Jan 2014 13:54:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897y-0006Tt-Fn; Tue, 28 Jan 2014 13:54:58 +0000 Received: from [85.158.143.35:13578] by server-2.bemta-4.messagelabs.com id 13/3F-11386-1B6B7E25; Tue, 28 Jan 2014 13:54:57 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1390917296!1359153!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8882 invoked from network); 28 Jan 2014 13:54:56 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:54:56 -0000 Received: by mail-wg0-f45.google.com with SMTP id n12so842750wgh.24 for ; Tue, 28 Jan 2014 05:54:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1KZm4BjhqSNlL7j3KoXkcYOsI5joh9Z2wFRDmUrUbnM=; b=Gk21K3oqXclgM6IXLhBFefRObLR54Op9UZgYzrde4UnRUiE9vEY9TyefIFHLINocQ4 qJvZDc66nqJs6IdUSVf6fnMeQCZqzzM64Bog9a9Gms6EZ/HYDmK7qutxxdeuOoCRDgP6 hUCjM+P7qjp+5qOU/OQ8s1FEqjpkLJ+H3cIjolkvbuhCJphGwUdAj7ETs2mOYHc4PLNM MlD1/SlyM6RebilWbtcBw/bqT5INmQVSfcRjOuh7znDY/+vkg2IEjIqEkXlU6B/2CP7z tWe5HBC24iJz6xiXEUQFLwkqEhj/6EVWXyX4Xjn99LKLP9EkxZedeq2ZKU4A6+uz117Z 7M+w== X-Received: by 10.181.13.40 with SMTP id ev8mr2134573wid.16.1390917296523; Tue, 28 Jan 2014 05:54:56 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id fb8sm11574023wic.3.2014.01.28.05.54.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 05:54:55 -0800 (PST) Message-ID: <52E7B6AF.3050604@xen.org> Date: Tue, 28 Jan 2014 13:54:55 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52DCE9FA.6010400@xen.org> In-Reply-To: <52DCE9FA.6010400@xen.org> Subject: Re: [Xen-API] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I have not gotten any reply to this thread. I saw Wei Lui and Andr=E9s = Lagar-Cavilla make changes to the project list. Please go through the = items below and make changes as suggested. Otherwise, our chances to get = into GSoC 2014 will be relatively slim. Lars On 20/01/2014 09:18, Lars Kurth wrote: > Hi all, > > the GSoC application deadline is coming up : Feb 2014. If we want to = > have any chance of getting accepted this year, we ought to get our = > project list into good shape. The project list and how the project and = > menters present themselves has a bigger impact on whether we get = > accepted than the actual application. > > Also, I would like to add a mentor section this year: a short bio, = > what the mentor cares about and a picture. This will help make the = > project list more real. > > We have *4 weeks* to do this. The bar for GSoC has been getting = > increasingly high. I know, we are tied down with Xen 4.4, but this is = > something you need to do if you want the Xen Project to participate. > > a) Please, update = > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently = > (these need to be in good shape *before* the application). What I need = > you to do is: > a.1) Remove items that are done > a.2) Add new work items : we ought to have a few sexy topics on say = > Real-time, mobile and some of the other segments (assuming we can get HW) > a.3) All project proposals need to be peer reviewed *and* clear ... = > The peer review process for projects we put in place last year worked = > well, by which we had past mentors sign of project proposals that were = > in good enough state. > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should = > get these listed on the respective other programs. And we should link = > to these from our project page. > > Best Regards > Lars > P.S.: I will also see whether we can participate as Xen Project under = > the LF GSoC program, but last year there was push-back and I don't = > expect this to change > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 28 16:38:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 16:38:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8Bfu-0002j7-9Q; Tue, 28 Jan 2014 16:38:10 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8Bft-0002j2-6q for xen-api@lists.xen.org; Tue, 28 Jan 2014 16:38:09 +0000 Received: from [193.109.254.147:31332] by server-14.bemta-14.messagelabs.com id 0F/11-12628-0FCD7E25; Tue, 28 Jan 2014 16:38:08 +0000 X-Env-Sender: qqshfox@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1390927085!406916!1 X-Originating-IP: [209.85.192.173] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16107 invoked from network); 28 Jan 2014 16:38:07 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 16:38:07 -0000 Received: by mail-pd0-f173.google.com with SMTP id y10so554904pdj.4 for ; Tue, 28 Jan 2014 08:38:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=wIWmEd1JiRqlpqIZxGiH/FOXHmHXWvN/SalgDAbo0jk=; b=F1kY+2dAxBIFf3fSLEgcp21gcC6jAB4gk7Va05Zv2vzZ4TrjG2dhVr0PA93aI2etYm yk5iGi2coKOZjzZNLDfpjNVpRe1tjQO20GAZwkaUI9BnNaUMqGgrFCjZg3wXaKxtL2Gl 7WK3LFj3BSok6xY1gQyXMvXtNXLs3ny08rT4dxM2QL++QlAv7MYpolDIqx0/twyskaW2 L3BCrrXDftM7aXsTOg7NqDz7ky3coWNkSBJ5RuLjYrHeE1cGpgnRUnx62lLUubQU9VOv YuA5UL2IJ+UuSzkZ0Tf9ycCW+ckQsXxXyLpWAzEOJARC6uJI1FJwH/+QL5QPA/0c0toJ 8nkQ== X-Received: by 10.66.142.132 with SMTP id rw4mr2667002pab.6.1390927084878; Tue, 28 Jan 2014 08:38:04 -0800 (PST) Received: from [10.0.1.15] ([222.65.69.179]) by mx.google.com with ESMTPSA id de1sm44118617pbc.7.2014.01.28.08.37.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 08:38:01 -0800 (PST) From: Hanfei Shen Message-Id: <1F21F55A-72AF-48C8-A08F-ACBC6217C642@gmail.com> Date: Wed, 29 Jan 2014 00:37:45 +0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [Xen-API] Question about vm hardware configs (nic model) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5569743435427483410==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5569743435427483410== Content-Type: multipart/alternative; boundary="Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94" --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, I wonder where these configs come from: qemu-dm-48 -d 48 -m 4096 -boot dc -serial pty -vcpus 4 -videoram 4 = -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net = nic,vlan=3D0,macaddr=3Dae:af:b1:b2:94:1a,model=3Drtl8139 -net = tap,vlan=3D0,bridge=3Dxenbr0,ifname=3Dtap48.0 -acpi -monitor pty Is it possible to make changes to the hardware of VMs? For example change NIC model (to virtio)? I know there's a hack to rewrite = the `/usr/lib/xen/bin/qemu-dm` or = `/opt/xensource/libexec/qemu-dm-wrapper` to replace the `rtl8139` to = `virtio`. It will have a effect on all the VMs created later. I've made several attempts to solve this by myself, such as changing the = vif params: # xe vif-param-list uuid=3Dc08d1381-ed1c-0880-8e5f-ac238a556160 uuid ( RO) : c08d1381-ed1c-0880-8e5f-ac238a556160 vm-uuid ( RO): f092bb24-11ee-e5a3-3cfd-1c8c83161407 vm-name-label ( RO): Other install media (1) allowed-operations (SRO): attach current-operations (SRO): device ( RO): 0 MAC ( RO): 92:61:9c:7a:da:09 MAC-autogenerated ( RO): true MTU ( RO): 1500 currently-attached ( RO): false qos_algorithm_type ( RW): qos_algorithm_params (MRW): qos_supported_algorithms (SRO): other-config (MRW): network-uuid ( RO): 8afa3eea-9ec0-0a6c-1208-580cad692cb2 network-name-label ( RO): Pool-wide network associated with = eth0 io_read_kbs ( RO): io_write_kbs ( RO): locking-mode ( RW): network_default ipv4-allowed (SRW): ipv6-allowed (SRW): Add a config (`other-config:model=3Dvirtio`) into the `other-config` = section, but no luck. Is there a better way to change the setting for a = specific VM? Best regards, Hanfei= --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi all,

I wonder where these configs come = from:
qemu-dm-48 -d 48 -m 4096 -boot dc = -serial pty -vcpus 4 -videoram 4 -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net = nic,vlan=3D0,macaddr=3Dae:af:b1:b2:94:1a,model=3Drtl8139 -net = tap,vlan=3D0,bridge=3Dxenbr0,ifname=3Dtap48.0 = -acpi -monitor pty

Is it possible to make changes to = the hardware of VMs? For
example change = NIC model (to virtio)? I know there's a hack to rewrite the = `/usr/lib/xen/bin/qemu-dm` or `/opt/xensource/libexec/qemu-dm-wrapper` to replace the `rtl8139` to `virtio`. It will = have a effect on all the VMs created later.

I've made several attempts to = solve this by myself, such as changing the vif params:

# xe = vif-param-list uuid=3Dc08d1381-ed1c-0880-8e5f-ac238a556160
uuid ( RO) =                     =    : c08d1381-ed1c-0880-8e5f-ac238a556160
    =                  vm-uuid ( = RO): f092bb24-11ee-e5a3-3cfd-1c8c83161407
    =            vm-name-label ( RO): Other = install media (1)
    =       allowed-operations (SRO): attach
          current-operations = (SRO):
        =               device ( RO): = 0
        =                  MAC ( RO): = 92:61:9c:7a:da:09
    =        MAC-autogenerated ( RO): true
                =          MTU ( RO): 1500
          currently-attached ( RO): = false
        =   qos_algorithm_type ( RW):
    =     qos_algorithm_params (MRW):
  =   qos_supported_algorithms (SRO):
  =               other-config = (MRW):
        =         network-uuid ( RO): = 8afa3eea-9ec0-0a6c-1208-580cad692cb2
    =       network-name-label ( RO): Pool-wide network = associated with eth0
    =              io_read_kbs ( RO): = <unknown>
        =         io_write_kbs ( RO): = <unknown>
        =         locking-mode ( RW): = network_default
        =         ipv4-allowed (SRW):
  =               ipv6-allowed = (SRW):

Add a config (`other-config:model=3Dvirtio`) into the = `other-config` section, but no luck. Is there a better way to change the = setting for a specific VM?

Best regards,
Hanfei= --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94-- --===============5569743435427483410== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5569743435427483410==-- From xen-api-bounces@lists.xen.org Tue Jan 28 16:38:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 16:38:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8Bfu-0002j7-9Q; Tue, 28 Jan 2014 16:38:10 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8Bft-0002j2-6q for xen-api@lists.xen.org; Tue, 28 Jan 2014 16:38:09 +0000 Received: from [193.109.254.147:31332] by server-14.bemta-14.messagelabs.com id 0F/11-12628-0FCD7E25; Tue, 28 Jan 2014 16:38:08 +0000 X-Env-Sender: qqshfox@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1390927085!406916!1 X-Originating-IP: [209.85.192.173] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16107 invoked from network); 28 Jan 2014 16:38:07 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 16:38:07 -0000 Received: by mail-pd0-f173.google.com with SMTP id y10so554904pdj.4 for ; Tue, 28 Jan 2014 08:38:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=wIWmEd1JiRqlpqIZxGiH/FOXHmHXWvN/SalgDAbo0jk=; b=F1kY+2dAxBIFf3fSLEgcp21gcC6jAB4gk7Va05Zv2vzZ4TrjG2dhVr0PA93aI2etYm yk5iGi2coKOZjzZNLDfpjNVpRe1tjQO20GAZwkaUI9BnNaUMqGgrFCjZg3wXaKxtL2Gl 7WK3LFj3BSok6xY1gQyXMvXtNXLs3ny08rT4dxM2QL++QlAv7MYpolDIqx0/twyskaW2 L3BCrrXDftM7aXsTOg7NqDz7ky3coWNkSBJ5RuLjYrHeE1cGpgnRUnx62lLUubQU9VOv YuA5UL2IJ+UuSzkZ0Tf9ycCW+ckQsXxXyLpWAzEOJARC6uJI1FJwH/+QL5QPA/0c0toJ 8nkQ== X-Received: by 10.66.142.132 with SMTP id rw4mr2667002pab.6.1390927084878; Tue, 28 Jan 2014 08:38:04 -0800 (PST) Received: from [10.0.1.15] ([222.65.69.179]) by mx.google.com with ESMTPSA id de1sm44118617pbc.7.2014.01.28.08.37.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 08:38:01 -0800 (PST) From: Hanfei Shen Message-Id: <1F21F55A-72AF-48C8-A08F-ACBC6217C642@gmail.com> Date: Wed, 29 Jan 2014 00:37:45 +0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [Xen-API] Question about vm hardware configs (nic model) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5569743435427483410==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5569743435427483410== Content-Type: multipart/alternative; boundary="Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94" --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, I wonder where these configs come from: qemu-dm-48 -d 48 -m 4096 -boot dc -serial pty -vcpus 4 -videoram 4 = -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net = nic,vlan=3D0,macaddr=3Dae:af:b1:b2:94:1a,model=3Drtl8139 -net = tap,vlan=3D0,bridge=3Dxenbr0,ifname=3Dtap48.0 -acpi -monitor pty Is it possible to make changes to the hardware of VMs? For example change NIC model (to virtio)? I know there's a hack to rewrite = the `/usr/lib/xen/bin/qemu-dm` or = `/opt/xensource/libexec/qemu-dm-wrapper` to replace the `rtl8139` to = `virtio`. It will have a effect on all the VMs created later. I've made several attempts to solve this by myself, such as changing the = vif params: # xe vif-param-list uuid=3Dc08d1381-ed1c-0880-8e5f-ac238a556160 uuid ( RO) : c08d1381-ed1c-0880-8e5f-ac238a556160 vm-uuid ( RO): f092bb24-11ee-e5a3-3cfd-1c8c83161407 vm-name-label ( RO): Other install media (1) allowed-operations (SRO): attach current-operations (SRO): device ( RO): 0 MAC ( RO): 92:61:9c:7a:da:09 MAC-autogenerated ( RO): true MTU ( RO): 1500 currently-attached ( RO): false qos_algorithm_type ( RW): qos_algorithm_params (MRW): qos_supported_algorithms (SRO): other-config (MRW): network-uuid ( RO): 8afa3eea-9ec0-0a6c-1208-580cad692cb2 network-name-label ( RO): Pool-wide network associated with = eth0 io_read_kbs ( RO): io_write_kbs ( RO): locking-mode ( RW): network_default ipv4-allowed (SRW): ipv6-allowed (SRW): Add a config (`other-config:model=3Dvirtio`) into the `other-config` = section, but no luck. Is there a better way to change the setting for a = specific VM? Best regards, Hanfei= --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi all,

I wonder where these configs come = from:
qemu-dm-48 -d 48 -m 4096 -boot dc = -serial pty -vcpus 4 -videoram 4 -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net = nic,vlan=3D0,macaddr=3Dae:af:b1:b2:94:1a,model=3Drtl8139 -net = tap,vlan=3D0,bridge=3Dxenbr0,ifname=3Dtap48.0 = -acpi -monitor pty

Is it possible to make changes to = the hardware of VMs? For
example change = NIC model (to virtio)? I know there's a hack to rewrite the = `/usr/lib/xen/bin/qemu-dm` or `/opt/xensource/libexec/qemu-dm-wrapper` to replace the `rtl8139` to `virtio`. It will = have a effect on all the VMs created later.

I've made several attempts to = solve this by myself, such as changing the vif params:

# xe = vif-param-list uuid=3Dc08d1381-ed1c-0880-8e5f-ac238a556160
uuid ( RO) =                     =    : c08d1381-ed1c-0880-8e5f-ac238a556160
    =                  vm-uuid ( = RO): f092bb24-11ee-e5a3-3cfd-1c8c83161407
    =            vm-name-label ( RO): Other = install media (1)
    =       allowed-operations (SRO): attach
          current-operations = (SRO):
        =               device ( RO): = 0
        =                  MAC ( RO): = 92:61:9c:7a:da:09
    =        MAC-autogenerated ( RO): true
                =          MTU ( RO): 1500
          currently-attached ( RO): = false
        =   qos_algorithm_type ( RW):
    =     qos_algorithm_params (MRW):
  =   qos_supported_algorithms (SRO):
  =               other-config = (MRW):
        =         network-uuid ( RO): = 8afa3eea-9ec0-0a6c-1208-580cad692cb2
    =       network-name-label ( RO): Pool-wide network = associated with eth0
    =              io_read_kbs ( RO): = <unknown>
        =         io_write_kbs ( RO): = <unknown>
        =         locking-mode ( RW): = network_default
        =         ipv4-allowed (SRW):
  =               ipv6-allowed = (SRW):

Add a config (`other-config:model=3Dvirtio`) into the = `other-config` section, but no luck. Is there a better way to change the = setting for a specific VM?

Best regards,
Hanfei= --Apple-Mail=_5E9753AF-F02E-418F-8BB3-F470626F3C94-- --===============5569743435427483410== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5569743435427483410==-- From xen-api-bounces@lists.xen.org Tue Jan 28 19:41:50 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 19:41:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8EXX-0004UE-Ho; Tue, 28 Jan 2014 19:41:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8EXW-0004U0-10; Tue, 28 Jan 2014 19:41:42 +0000 Received: from [85.158.139.211:31548] by server-13.bemta-5.messagelabs.com id 3D/DB-11357-5F708E25; Tue, 28 Jan 2014 19:41:41 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390938100!214129!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23573 invoked from network); 28 Jan 2014 19:41:40 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 19:41:40 -0000 Received: by mail-lb0-f175.google.com with SMTP id p9so741474lbv.6 for ; Tue, 28 Jan 2014 11:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Mv+r0FlS87lKIyw8LkLOBsLqUVF5h5qOsM2brwqdlWM=; b=O1TxlKd2PsfuLM/82R7Vmg5/NTsf2xhh+RDXZyr+IgEWwNBKqryc51TMC7fT372h7u 5wzcqwbKkBKvvasePbaH0BKP97BodKeDn0TdvX0iWjSad89fxz+I1fPjTH9Mel13t3uE 1pSqSGT2RGmnCt/Lt4Dx4dr9ly2yt+RrscKPgSh6J14aK5q6jCaXRr2WtY4/GStV/0Cx m4J2U0sJtD1BKJDmO7iKv4E0wO4o/MzesGnGviYTVc7rVZ6lZKMNQ9dMRWK/7vvrBWar ZncDf50dkDBmEdX263XnkPWTTdskGCayuOYG+hsRmAMIDHijY30UF/CRDskgHI5tiuej 7L9g== MIME-Version: 1.0 X-Received: by 10.112.242.134 with SMTP id wq6mr2023624lbc.24.1390938099762; Tue, 28 Jan 2014 11:41:39 -0800 (PST) Received: by 10.112.72.72 with HTTP; Tue, 28 Jan 2014 11:41:39 -0800 (PST) Date: Tue, 28 Jan 2014 14:41:39 -0500 X-Google-Sender-Auth: hrSngXopcGAG5SM2Ip-mwZ1fMy4 Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org Subject: [Xen-API] Thank you for participating in Xen Project Document Day! X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Thank you for everyone who pitched in during the Xen Project Document Day on Monday. Special thanks to Mneilsen and Ijc for the amount of work they performed during the day. You've helped move our project forward in the area of documentation! Our next Document Day is scheduled for February 24. In the meantime, if you see pages which need improvements, please add them to: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO I hope to see you all in #xendocs next month! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 28 19:41:50 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 Jan 2014 19:41:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8EXX-0004UE-Ho; Tue, 28 Jan 2014 19:41:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8EXW-0004U0-10; Tue, 28 Jan 2014 19:41:42 +0000 Received: from [85.158.139.211:31548] by server-13.bemta-5.messagelabs.com id 3D/DB-11357-5F708E25; Tue, 28 Jan 2014 19:41:41 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390938100!214129!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23573 invoked from network); 28 Jan 2014 19:41:40 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 19:41:40 -0000 Received: by mail-lb0-f175.google.com with SMTP id p9so741474lbv.6 for ; Tue, 28 Jan 2014 11:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Mv+r0FlS87lKIyw8LkLOBsLqUVF5h5qOsM2brwqdlWM=; b=O1TxlKd2PsfuLM/82R7Vmg5/NTsf2xhh+RDXZyr+IgEWwNBKqryc51TMC7fT372h7u 5wzcqwbKkBKvvasePbaH0BKP97BodKeDn0TdvX0iWjSad89fxz+I1fPjTH9Mel13t3uE 1pSqSGT2RGmnCt/Lt4Dx4dr9ly2yt+RrscKPgSh6J14aK5q6jCaXRr2WtY4/GStV/0Cx m4J2U0sJtD1BKJDmO7iKv4E0wO4o/MzesGnGviYTVc7rVZ6lZKMNQ9dMRWK/7vvrBWar ZncDf50dkDBmEdX263XnkPWTTdskGCayuOYG+hsRmAMIDHijY30UF/CRDskgHI5tiuej 7L9g== MIME-Version: 1.0 X-Received: by 10.112.242.134 with SMTP id wq6mr2023624lbc.24.1390938099762; Tue, 28 Jan 2014 11:41:39 -0800 (PST) Received: by 10.112.72.72 with HTTP; Tue, 28 Jan 2014 11:41:39 -0800 (PST) Date: Tue, 28 Jan 2014 14:41:39 -0500 X-Google-Sender-Auth: hrSngXopcGAG5SM2Ip-mwZ1fMy4 Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org Subject: [Xen-API] Thank you for participating in Xen Project Document Day! X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Thank you for everyone who pitched in during the Xen Project Document Day on Monday. Special thanks to Mneilsen and Ijc for the amount of work they performed during the day. You've helped move our project forward in the area of documentation! Our next Document Day is scheduled for February 24. In the meantime, if you see pages which need improvements, please add them to: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO I hope to see you all in #xendocs next month! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 29 10:50:55 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 Jan 2014 10:50:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8SjD-00017O-Ja; Wed, 29 Jan 2014 10:50:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8SjC-00017H-Cg for xen-api@lists.xen.org; Wed, 29 Jan 2014 10:50:42 +0000 Received: from [85.158.143.35:50064] by server-1.bemta-4.messagelabs.com id 75/0A-31661-10DD8E25; Wed, 29 Jan 2014 10:50:41 +0000 X-Env-Sender: piotr.teodorowski@unity.pl X-Msg-Ref: server-8.tower-21.messagelabs.com!1390992640!1586120!1 X-Originating-IP: [213.199.154.10] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26733 invoked from network); 29 Jan 2014 10:50:41 -0000 Received: from mail-am1lp0010.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (213.199.154.10) by server-8.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 29 Jan 2014 10:50:41 -0000 Received: from AM2PRD0311HT003.eurprd03.prod.outlook.com (10.255.162.38) by DB3PR03MB153.eurprd03.prod.outlook.com (10.242.130.146) with Microsoft SMTP Server (TLS) id 15.0.851.15; Wed, 29 Jan 2014 10:50:39 +0000 Received: from [192.168.0.12] (193.178.214.60) by pod51013.outlook.com (10.255.162.38) with Microsoft SMTP Server (TLS) id 14.16.395.1; Wed, 29 Jan 2014 10:50:39 +0000 Message-ID: <52E8DCFC.1060602@unity.pl> Date: Wed, 29 Jan 2014 11:50:36 +0100 From: Piotr Teodorowski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: X-Enigmail-Version: 1.6 X-Originating-IP: [193.178.214.60] X-Forefront-PRVS: 01068D0A20 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009001)(6009001)(11905935001)(189002)(199002)(76176001)(81686001)(49866001)(79102001)(81342001)(76796001)(69226001)(76786001)(92566001)(93516002)(36756003)(59766001)(87936001)(81542001)(50466002)(47976001)(81816001)(85852003)(77982001)(4396001)(86362001)(50986001)(92726001)(94316002)(15975445006)(83322001)(74502001)(54356001)(80022001)(74706001)(80316001)(93136001)(33656001)(63696002)(66066001)(46102001)(83506001)(51856001)(83072002)(53806001)(64126003)(47776003)(54316002)(76482001)(19580395003)(31966008)(74482001)(74662001)(80976001)(59896001)(15202345003)(85306002)(23676002)(47446002)(56816005)(74366001)(90146001)(47736001)(74876001)(56776001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR03MB153; H:AM2PRD0311HT003.eurprd03.prod.outlook.com; CLIP:193.178.214.60; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; X-OriginatorOrg: unity.pl Subject: [Xen-API] Procedure for change management interface and subnet X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, please recommend a way to change management interface and IP subnet for this interface in a pool. I tried to (pool members XenServer 6.2): 1) change address using this article: http://support.citrix.com/article/CTX123477 but pool-members weren't in emergency mode after changing IP and restart toolstack 2) change interface from xsconsole but there was no infromation about any interface in xsconsole after xe pool-emergency-reset-master master-address=IP_OF_THE_MASTER. reboot helped to resolve this problem. Changing management interface caused problem with one ip assigned to old and new interface. Routing to management subnet was set for 2 interfaces. To resolve problems i had to use pif-reconfigure with mode=none, changing /etc/xensource-inventory manually and some reboots. Is it possible to change management interface and IP address without reboot? Are there any difference doing this steps for XenServer 6.2 and XCP? Best Regards Piotr Teodorowski _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 29 10:50:55 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 Jan 2014 10:50:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8SjD-00017O-Ja; Wed, 29 Jan 2014 10:50:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8SjC-00017H-Cg for xen-api@lists.xen.org; Wed, 29 Jan 2014 10:50:42 +0000 Received: from [85.158.143.35:50064] by server-1.bemta-4.messagelabs.com id 75/0A-31661-10DD8E25; Wed, 29 Jan 2014 10:50:41 +0000 X-Env-Sender: piotr.teodorowski@unity.pl X-Msg-Ref: server-8.tower-21.messagelabs.com!1390992640!1586120!1 X-Originating-IP: [213.199.154.10] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26733 invoked from network); 29 Jan 2014 10:50:41 -0000 Received: from mail-am1lp0010.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (213.199.154.10) by server-8.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 29 Jan 2014 10:50:41 -0000 Received: from AM2PRD0311HT003.eurprd03.prod.outlook.com (10.255.162.38) by DB3PR03MB153.eurprd03.prod.outlook.com (10.242.130.146) with Microsoft SMTP Server (TLS) id 15.0.851.15; Wed, 29 Jan 2014 10:50:39 +0000 Received: from [192.168.0.12] (193.178.214.60) by pod51013.outlook.com (10.255.162.38) with Microsoft SMTP Server (TLS) id 14.16.395.1; Wed, 29 Jan 2014 10:50:39 +0000 Message-ID: <52E8DCFC.1060602@unity.pl> Date: Wed, 29 Jan 2014 11:50:36 +0100 From: Piotr Teodorowski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: X-Enigmail-Version: 1.6 X-Originating-IP: [193.178.214.60] X-Forefront-PRVS: 01068D0A20 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009001)(6009001)(11905935001)(189002)(199002)(76176001)(81686001)(49866001)(79102001)(81342001)(76796001)(69226001)(76786001)(92566001)(93516002)(36756003)(59766001)(87936001)(81542001)(50466002)(47976001)(81816001)(85852003)(77982001)(4396001)(86362001)(50986001)(92726001)(94316002)(15975445006)(83322001)(74502001)(54356001)(80022001)(74706001)(80316001)(93136001)(33656001)(63696002)(66066001)(46102001)(83506001)(51856001)(83072002)(53806001)(64126003)(47776003)(54316002)(76482001)(19580395003)(31966008)(74482001)(74662001)(80976001)(59896001)(15202345003)(85306002)(23676002)(47446002)(56816005)(74366001)(90146001)(47736001)(74876001)(56776001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR03MB153; H:AM2PRD0311HT003.eurprd03.prod.outlook.com; CLIP:193.178.214.60; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; X-OriginatorOrg: unity.pl Subject: [Xen-API] Procedure for change management interface and subnet X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, please recommend a way to change management interface and IP subnet for this interface in a pool. I tried to (pool members XenServer 6.2): 1) change address using this article: http://support.citrix.com/article/CTX123477 but pool-members weren't in emergency mode after changing IP and restart toolstack 2) change interface from xsconsole but there was no infromation about any interface in xsconsole after xe pool-emergency-reset-master master-address=IP_OF_THE_MASTER. reboot helped to resolve this problem. Changing management interface caused problem with one ip assigned to old and new interface. Routing to management subnet was set for 2 interfaces. To resolve problems i had to use pif-reconfigure with mode=none, changing /etc/xensource-inventory manually and some reboots. Is it possible to change management interface and IP address without reboot? Are there any difference doing this steps for XenServer 6.2 and XCP? Best Regards Piotr Teodorowski _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 29 19:24:34 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 Jan 2014 19:24:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8akI-0007cW-L6; Wed, 29 Jan 2014 19:24:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8akH-0007cF-EU; Wed, 29 Jan 2014 19:24:21 +0000 Received: from [193.109.254.147:48562] by server-7.bemta-14.messagelabs.com id 7B/B3-23424-46559E25; Wed, 29 Jan 2014 19:24:20 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1391023457!701851!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14823 invoked from network); 29 Jan 2014 19:24:18 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2014 19:24:18 -0000 Received: by mail-lb0-f170.google.com with SMTP id u14so1843445lbd.29 for ; Wed, 29 Jan 2014 11:24:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=qkUf5Z9nqOptmoVdn8M9Ha3nW02XWTc1w9HiGCp+2Yc=; b=MjdbB48ZBhKYEcfrePxwm9OofDMU9ZiOtTdO3kd6TTzJShW8xGtSXn2yEQwI4h26z0 ymKVUfINRuMlFKqNdT3J7khBHIm3XFuAQYvi85wNRRsNWPewCo8i6Rbr9LOHHjF1HLx3 uX8RBgpbNCOe564+fSLq5DEFq8jQA2vdTLRe9WJpoDNwkk2jjnKbUqPJJyLY2sJfL+2u GZqRJaYGsAI8lYZnP/afzxteh8IMKabseMswWjGjUc4s7fpiRSQisETcbnDxYIqChJpU xPksWKfrcEH0/chnEoaDxroacPCUGofVH4xEe7Q7Aj7rY6S7hD+6t8EotkP/x0q4sjDf d2fg== MIME-Version: 1.0 X-Received: by 10.112.154.202 with SMTP id vq10mr6258691lbb.3.1391023457531; Wed, 29 Jan 2014 11:24:17 -0800 (PST) Received: by 10.112.72.72 with HTTP; Wed, 29 Jan 2014 11:24:17 -0800 (PST) Date: Wed, 29 Jan 2014 14:24:17 -0500 X-Google-Sender-Auth: vEYCqxoYv1b4IzElmMrYaeKyyiY Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, "publicity@lists.xenproject.org" Subject: [Xen-API] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Next Monday, February 3, is the Test Day for Xen 4.4. Release Candidate 3. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC3_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC3, we need to know about it and how to test it. Please edit the instructions page this week to reflect suggested configuration and testing instructions. EVERYONE: Please join us on Monday, February 3, to flush out any potential bugs before the next release. Thank you! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 29 19:24:34 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 Jan 2014 19:24:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8akI-0007cW-L6; Wed, 29 Jan 2014 19:24:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W8akH-0007cF-EU; Wed, 29 Jan 2014 19:24:21 +0000 Received: from [193.109.254.147:48562] by server-7.bemta-14.messagelabs.com id 7B/B3-23424-46559E25; Wed, 29 Jan 2014 19:24:20 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1391023457!701851!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14823 invoked from network); 29 Jan 2014 19:24:18 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2014 19:24:18 -0000 Received: by mail-lb0-f170.google.com with SMTP id u14so1843445lbd.29 for ; Wed, 29 Jan 2014 11:24:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=qkUf5Z9nqOptmoVdn8M9Ha3nW02XWTc1w9HiGCp+2Yc=; b=MjdbB48ZBhKYEcfrePxwm9OofDMU9ZiOtTdO3kd6TTzJShW8xGtSXn2yEQwI4h26z0 ymKVUfINRuMlFKqNdT3J7khBHIm3XFuAQYvi85wNRRsNWPewCo8i6Rbr9LOHHjF1HLx3 uX8RBgpbNCOe564+fSLq5DEFq8jQA2vdTLRe9WJpoDNwkk2jjnKbUqPJJyLY2sJfL+2u GZqRJaYGsAI8lYZnP/afzxteh8IMKabseMswWjGjUc4s7fpiRSQisETcbnDxYIqChJpU xPksWKfrcEH0/chnEoaDxroacPCUGofVH4xEe7Q7Aj7rY6S7hD+6t8EotkP/x0q4sjDf d2fg== MIME-Version: 1.0 X-Received: by 10.112.154.202 with SMTP id vq10mr6258691lbb.3.1391023457531; Wed, 29 Jan 2014 11:24:17 -0800 (PST) Received: by 10.112.72.72 with HTTP; Wed, 29 Jan 2014 11:24:17 -0800 (PST) Date: Wed, 29 Jan 2014 14:24:17 -0500 X-Google-Sender-Auth: vEYCqxoYv1b4IzElmMrYaeKyyiY Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, cl-mirage@lists.cam.ac.uk, "publicity@lists.xenproject.org" Subject: [Xen-API] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Next Monday, February 3, is the Test Day for Xen 4.4. Release Candidate 3. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC3_test_instructions XEN 4.4 FEATURE DEVELOPERS: If you have a new feature which is cooked and ready for testing in RC3, we need to know about it and how to test it. Please edit the instructions page this week to reflect suggested configuration and testing instructions. EVERYONE: Please join us on Monday, February 3, to flush out any potential bugs before the next release. Thank you! Russ Pavlicek _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 31 22:59:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 31 Jan 2014 22:59:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9N3f-0000S4-4g; Fri, 31 Jan 2014 22:59:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9Lwi-00062O-BP for xen-api@lists.xen.org; Fri, 31 Jan 2014 21:48:20 +0000 Received: from [85.158.143.35:43092] by server-2.bemta-4.messagelabs.com id C8/3B-10891-32A1CE25; Fri, 31 Jan 2014 21:48:19 +0000 X-Env-Sender: ehouby@yahoo.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1391204897!2292450!1 X-Originating-IP: [216.109.115.156] X-SpamReason: No, hits=2.8 required=7.0 tests=FORGED_YAHOO_RCVD, ML_RADAR_SPEW_LINKS_14,SUSPICIOUS_RECIPS,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25873 invoked from network); 31 Jan 2014 21:48:18 -0000 Received: from nm48-vm1.bullet.mail.bf1.yahoo.com (HELO nm48-vm1.bullet.mail.bf1.yahoo.com) (216.109.115.156) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Jan 2014 21:48:18 -0000 Received: from [66.196.81.172] by nm48.bullet.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 Received: from [98.139.211.206] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 Received: from [127.0.0.1] by smtp215.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1391204897; bh=8Ig91VcSKsS+AwCsIXIreANyz1BAku1PF173k9HyLAY=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=U60ALqDNDUqupIAX7a8McjZufbnRPwj3ntXGf5qbCqad3/VqlWLTmMuO45SCkBqHiFlmwA3D2k11GX79+gcCJe7Zkx1JFAwS43Js6HbQPqvNtu4cw2JyMeZn7rs1DuD8Kz45f+LsfYBkPXOWqLCUnEedxYz/3IkjrJW4cASQkX8= X-Yahoo-Newman-Id: 516073.73947.bm@smtp215.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: WhCuM5cVM1nF6kQp.pNceGdAHI1TuD.S7mrm6lrs0MWCZ.e .mux3zhhFHPeU_IHLwneWqz64kG11Vye00KC4s931kmOAbLwk5btF1HRrS1t ox0pbch7g7Ss7xa8oRCzecaEB2fUDe0RZOsWEHdh7yfsOg8sQAXRgRREmE8j 4DlxkVFRlJGNcvvCh0EBi34qj.xNbl5cxMcDQqFo4wtJ8bgQdOzIa3F1kpm5 SdxbR8No0pNQ90.gsg9Cu7.ihiiPj9YAnYM4E_Qq2KqY6Qhk.FrCS.WR_3mW nDzptvjYjKm4RBuAuA7H.luVGo9FiOZlMUpKIAuPKdHGoaySlcys_ZefgOJ. Pz3dkECERjCofSV3xU.Qx22oVYnb1oZlpMnNuOZZaKrxAulxKkpfnjKDybyU Ojsk9pcbpwQL6eueeJTiyF1jKAdKmk7GVtLjrFbo0IrESn9kKzyS5ZdvatAw KNLin0iRgpQrAc9rtJyzx7f0GZFW91p7DDPKWN6Js8WF19TRIcIzKUKaEHwo 21Fb1pCQufY.YeP05EJD.g7m2y7trWuPeyZrSoE47XOmiQrYTSlJKPZbxlBc .XDUxeuB.f1JAQssXUzA8ZC3NOBSh1w5C8jYnO2gJ142I0MLCNhbTyM8bLYG S69IZo7EqfJx4KkcAJGcwwA-- X-Yahoo-SMTP: QpZsTh.swBBbiXoX3lukB1DLTA-- X-Rocket-Received: from phobos (ehouby@71.196.207.87 with plain [98.139.211.125]) by smtp215.mail.bf1.yahoo.com with SMTP; 31 Jan 2014 13:48:17 -0800 PST From: "Eric Houby" To: "'Russ Pavlicek'" , , , , , , References: In-Reply-To: Date: Fri, 31 Jan 2014 14:48:17 -0700 Message-ID: <009c01cf1ece$2739a820$75acf860$@yahoo.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQFjy0dgAXkVho5qIRcBav+bbzk7pZt2AEDw Content-Language: en-us X-Mailman-Approved-At: Fri, 31 Jan 2014 22:59:33 +0000 Subject: Re: [Xen-API] [Xen-users] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > > Next Monday, February 3, is the Test Day for Xen 4.4. Release Candidate 3. > > General Information about Test Days can be found here: > http://wiki.xenproject.org/wiki/Xen_Test_Days > > and specific instructions for this Test Day are located here: > http://wiki.xenproject.org/wiki/Xen_4.4_RC3_test_instructions > Russ, On the RC3 test instructions page, the link for the RC3 RPMS are pointing to what looks like the RC2 RPMs from 1/16. Will there be updated RPMs for this test day? Thanks, Eric _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 31 22:59:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 31 Jan 2014 22:59:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9N3f-0000S4-4g; Fri, 31 Jan 2014 22:59:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9Lwi-00062O-BP for xen-api@lists.xen.org; Fri, 31 Jan 2014 21:48:20 +0000 Received: from [85.158.143.35:43092] by server-2.bemta-4.messagelabs.com id C8/3B-10891-32A1CE25; Fri, 31 Jan 2014 21:48:19 +0000 X-Env-Sender: ehouby@yahoo.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1391204897!2292450!1 X-Originating-IP: [216.109.115.156] X-SpamReason: No, hits=2.8 required=7.0 tests=FORGED_YAHOO_RCVD, ML_RADAR_SPEW_LINKS_14,SUSPICIOUS_RECIPS,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25873 invoked from network); 31 Jan 2014 21:48:18 -0000 Received: from nm48-vm1.bullet.mail.bf1.yahoo.com (HELO nm48-vm1.bullet.mail.bf1.yahoo.com) (216.109.115.156) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Jan 2014 21:48:18 -0000 Received: from [66.196.81.172] by nm48.bullet.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 Received: from [98.139.211.206] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 Received: from [127.0.0.1] by smtp215.mail.bf1.yahoo.com with NNFMP; 31 Jan 2014 21:48:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1391204897; bh=8Ig91VcSKsS+AwCsIXIreANyz1BAku1PF173k9HyLAY=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=U60ALqDNDUqupIAX7a8McjZufbnRPwj3ntXGf5qbCqad3/VqlWLTmMuO45SCkBqHiFlmwA3D2k11GX79+gcCJe7Zkx1JFAwS43Js6HbQPqvNtu4cw2JyMeZn7rs1DuD8Kz45f+LsfYBkPXOWqLCUnEedxYz/3IkjrJW4cASQkX8= X-Yahoo-Newman-Id: 516073.73947.bm@smtp215.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: WhCuM5cVM1nF6kQp.pNceGdAHI1TuD.S7mrm6lrs0MWCZ.e .mux3zhhFHPeU_IHLwneWqz64kG11Vye00KC4s931kmOAbLwk5btF1HRrS1t ox0pbch7g7Ss7xa8oRCzecaEB2fUDe0RZOsWEHdh7yfsOg8sQAXRgRREmE8j 4DlxkVFRlJGNcvvCh0EBi34qj.xNbl5cxMcDQqFo4wtJ8bgQdOzIa3F1kpm5 SdxbR8No0pNQ90.gsg9Cu7.ihiiPj9YAnYM4E_Qq2KqY6Qhk.FrCS.WR_3mW nDzptvjYjKm4RBuAuA7H.luVGo9FiOZlMUpKIAuPKdHGoaySlcys_ZefgOJ. Pz3dkECERjCofSV3xU.Qx22oVYnb1oZlpMnNuOZZaKrxAulxKkpfnjKDybyU Ojsk9pcbpwQL6eueeJTiyF1jKAdKmk7GVtLjrFbo0IrESn9kKzyS5ZdvatAw KNLin0iRgpQrAc9rtJyzx7f0GZFW91p7DDPKWN6Js8WF19TRIcIzKUKaEHwo 21Fb1pCQufY.YeP05EJD.g7m2y7trWuPeyZrSoE47XOmiQrYTSlJKPZbxlBc .XDUxeuB.f1JAQssXUzA8ZC3NOBSh1w5C8jYnO2gJ142I0MLCNhbTyM8bLYG S69IZo7EqfJx4KkcAJGcwwA-- X-Yahoo-SMTP: QpZsTh.swBBbiXoX3lukB1DLTA-- X-Rocket-Received: from phobos (ehouby@71.196.207.87 with plain [98.139.211.125]) by smtp215.mail.bf1.yahoo.com with SMTP; 31 Jan 2014 13:48:17 -0800 PST From: "Eric Houby" To: "'Russ Pavlicek'" , , , , , , References: In-Reply-To: Date: Fri, 31 Jan 2014 14:48:17 -0700 Message-ID: <009c01cf1ece$2739a820$75acf860$@yahoo.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQFjy0dgAXkVho5qIRcBav+bbzk7pZt2AEDw Content-Language: en-us X-Mailman-Approved-At: Fri, 31 Jan 2014 22:59:33 +0000 Subject: Re: [Xen-API] [Xen-users] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > > Next Monday, February 3, is the Test Day for Xen 4.4. Release Candidate 3. > > General Information about Test Days can be found here: > http://wiki.xenproject.org/wiki/Xen_Test_Days > > and specific instructions for this Test Day are located here: > http://wiki.xenproject.org/wiki/Xen_4.4_RC3_test_instructions > Russ, On the RC3 test instructions page, the link for the RC3 RPMS are pointing to what looks like the RC2 RPMs from 1/16. Will there be updated RPMs for this test day? Thanks, Eric _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 31 23:44:51 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 31 Jan 2014 23:44:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9NlL-0001xc-Em; Fri, 31 Jan 2014 23:44:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9NlJ-0001xX-L5 for xen-api@lists.xen.org; Fri, 31 Jan 2014 23:44:41 +0000 Received: from [85.158.143.35:52256] by server-2.bemta-4.messagelabs.com id 6D/8A-10891-8653CE25; Fri, 31 Jan 2014 23:44:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1391211879!2301750!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12003 invoked from network); 31 Jan 2014 23:44:39 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Jan 2014 23:44:39 -0000 Received: from [10.8.0.22] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id s0VNicqu017847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 1 Feb 2014 00:44:38 +0100 From: =?utf-8?q?S=c3=a9bastien=20RICCIO?= To: "Denis Cardon" Date: Fri, 31 Jan 2014 23:44:36 +0000 In-Reply-To: <52DCEDDF.3030101@tranquil-it-systems.fr> Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/6.0.19714.0 X-Virus-Scanned: clamav-milter 0.97.8 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?utf-8?q?S=c3=a9bastien=20RICCIO?= List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SnVzdCBteSB0d28gY2VudHMgYnV0IHRvIGRldGVybWluYXRlIGlmIGEgaG9zdCBpcyB0aGUgcG9v bCBtYXN0ZXIsIGkgCmp1c3QgbG9vayBmb3IgdGhlIHdvcmQgIm1hc3RlciIgaW4gL2V0Yy94ZW5z b3VyY2UvcG9vbC5jb25mCgpsaWtlIDoKCiMgQ2hlY2sgaWYgd2UncmUgcnVubmluZyBvbiB0aGUg cG9vbCBtYXN0ZXIKaWYgWyBgY2F0IC9ldGMveGVuc291cmNlL3Bvb2wuY29uZmAgIT0gIm1hc3Rl ciIgXTsgdGhlbgogICBleGl0IDAKZmkKClPDqWJhc3RpZW4KCgotLS0tLS0gT3JpZ2luYWwgTWVz c2FnZSAtLS0tLS0KRnJvbTogIkRlbmlzIENhcmRvbiIgPGRlbmlzLmNhcmRvbkB0cmFucXVpbC1p dC1zeXN0ZW1zLmZyPgpUbzogIlNoYWZpIE1vaGFtbWVkIFMiIDxzaGFmaUB2ZW1idS5jb20+CkNj OiAiVGhpbGVlcGFuIFMiIDx0aGlsZWVwYW5AdmVtYnUuY29tPjsgeGVuLWFwaUBsaXN0cy54ZW4u b3JnClNlbnQ6IDIwLjAxLjIwMTQgMTA6MzU6MjcKU3ViamVjdDogUmU6IFtYZW4tQVBJXSBJcyB0 aGUgaG9zdCBhIFhlbiBNYXN0ZXIgPz8KCj5IaSBTaGFmaSwKPgo+PiAgICAgICAgSXMgdGhlcmUg YW55IEFQSSBjYWxsIG9yIGFueSBvdGhlciBtZXRob2QgdG8gZGV0ZWN0IHdoZXRoZXIgdGhlCj4+ aG9zdCBpbiBxdWVzdGlvbiBpcyBhIFBvb2wgbWFzdGVyIG9yIGEgbWVtYmVyIG9mIGEgWGVuIFBP T0wgPwo+Cj5UaGlzIHF1ZXN0aW9uIHdhcyBjb3ZlcmVkIGEgZmV3IGRheXMgYWdvLi4uIFVzaW5n IHB5dGhvbiA6Cj4KPnNlc3Npb24gPSBYZW5BUEkuU2Vzc2lvbignaHR0cHM6Ly8nK3NlbGYueGNw aG9zdCkKPiAgICAgICAgIHRyeToKPiAgICAgICAgICAgICBzZXNzaW9uLmxvZ2luX3dpdGhfcGFz c3dvcmQodXNlcl94ZW4scGFzc3dvcmRfeGVuKQo+ICAgICAgICAgZXhjZXB0IFhlbkFQSS5GYWls dXJlLCBlcnJvcjoKPiAgICAgICAgICAgICBtc2csaXAgPSBlcnJvci5kZXRhaWxzCj4KPiAgICAg ICAgICAgICBpZiBtc2cgPT0gJ0hPU1RfSVNfU0xBVkUnOgo+ICAgICAgICAgICAgICAgICB4Y3Bo b3N0ID0gaXAKPiAgICAgICAgICAgICAgICAgc2Vzc2lvbiA9IFhlbkFQSS5TZXNzaW9uKCdodHRw czovLycreGNwaG9zdCkKPiAgICAgICAgICAgICAgICAgc2Vzc2lvbi5sb2dpbl93aXRoX3Bhc3N3 b3JkKHVzZXJfeGVuLHBhc3N3b3JkX3hlbikKPgo+KHNhbXBsZSBjb2RlIGZyb20gCj5odHRwczov L2dpdGh1Yi5jb20vdHJhbnF1aWxpdC9USVNiYWNrdXAvYmxvYi9tYXN0ZXIvbGlidGlzYmFja3Vw L2JhY2t1cF94dmEucHkpCj4KPj4gICAgICBBbmQgaXMgdGhlcmUgYSBjYWxsIHRvIGdldCB0aGUg aG9zdCBpbmZvIHVzaW5nIHRoZSBzbmFwc2hvdCAKPj4oVVVJRCkKPj5vZiBpdHMgVk1TID8KPgo+ YnkgaG9zdCBpbmZvLCBkbyB5b3UgbWVhbiB0aGUgcGFyYW0tbGlzdCBvZiB0aGUgaG9zdCB3aGVy ZSB0aGUgdm0gaXMgCj5ydW5uaW5nPwo+Cj5Zb3UgY2FuIGdldCB0aGUgVk0gdXVpZCBmcm9tIHNu YXBzaG90IHV1aWQgdXNpbmcKPnhlIHZtLWxpc3QgdXVpZD0kKHhlIHNuYXBzaG90LXBhcmFtLWdl dCBwYXJhbS1uYW1lPXNuYXBzaG90LW9mIAo+dXVpZD0zNWU2OGIzZC1jYWRkLWFmYzYtMGY1Ny04 MzNiZTc3M2I5YmEgKQo+Cj5UaGVuIHlvdSBjYW4gcXVlcnkgdGhlIHJlc2lkZW50LW9uIHZhbHVl IChhdCBsZWFzdCBmb3IgcnVubmluZyB2bSkKPgo+eGUgdm0tcGFyYW0tZ2V0IHBhcmFtLW5hbWU9 cmVzaWRlbnQtb24gCj51dWlkPTcxZTE3OTVlLWExZmEtMTZlYS00ZjIyLTc3MDQ4ZDljMWUwMgo+ Cj5JdCBzaG91bGRuJ3QgYmUgdG9vIGhhcmQgdG8gdHJhbnNsYXRlIHRoaXMgaW4gYXBpIGNhbGxz LiBBbmQgbGlrZSBEYXZpZCAKPnRvbGQgZWFybGllciwgeGFwaSBBUEkgZG9jIGlzIHlvdXIgYmVz dCBmcmllbmQuCj4KPkNoZWVycywKPgo+RGVuaXMKPgo+PlRoYW5rcyAuCj4+Cj4+Cj4+UmVnYXJk cywKPj5TaGFmaSwKPj5WZW1idSBUZWNobm9sb2dpZXMuCj4+Cj4+Cj4+Cj4+VGhpcyBib2R5IHBh cnQgd2lsbCBiZSBkb3dubG9hZGVkIG9uIGRlbWFuZC4KPj4KPgo+Cj4tLSBEZW5pcyBDYXJkb24K PlRyYW5xdWlsIElUIFN5c3RlbXMKPkxlcyBFc3BhY2VzIEp1bGVzIFZlcm5lLCBiw6J0aW1lbnQg QQo+MTIgYXZlbnVlIEp1bGVzIFZlcm5lCj40NDIzMCBTYWludCBTw6liYXN0aWVuIHN1ciBMb2ly ZQo+dGVsIDogKzMzICgwKSAyLjQwLjk3LjU3LjU1Cj5odHRwOi8vd3d3LnRyYW5xdWlsLWl0LXN5 c3RlbXMuZnIKPgo+Cj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwo+WGVuLWFwaSBtYWlsaW5nIGxpc3QKPlhlbi1hcGlAbGlzdHMueGVuLm9yZwo+aHR0cDov L2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgoKCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGlu ZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 31 23:44:51 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 31 Jan 2014 23:44:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9NlL-0001xc-Em; Fri, 31 Jan 2014 23:44:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W9NlJ-0001xX-L5 for xen-api@lists.xen.org; Fri, 31 Jan 2014 23:44:41 +0000 Received: from [85.158.143.35:52256] by server-2.bemta-4.messagelabs.com id 6D/8A-10891-8653CE25; Fri, 31 Jan 2014 23:44:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1391211879!2301750!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12003 invoked from network); 31 Jan 2014 23:44:39 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Jan 2014 23:44:39 -0000 Received: from [10.8.0.22] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id s0VNicqu017847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 1 Feb 2014 00:44:38 +0100 From: =?utf-8?q?S=c3=a9bastien=20RICCIO?= To: "Denis Cardon" Date: Fri, 31 Jan 2014 23:44:36 +0000 In-Reply-To: <52DCEDDF.3030101@tranquil-it-systems.fr> Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/6.0.19714.0 X-Virus-Scanned: clamav-milter 0.97.8 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is the host a Xen Master ?? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?utf-8?q?S=c3=a9bastien=20RICCIO?= List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SnVzdCBteSB0d28gY2VudHMgYnV0IHRvIGRldGVybWluYXRlIGlmIGEgaG9zdCBpcyB0aGUgcG9v bCBtYXN0ZXIsIGkgCmp1c3QgbG9vayBmb3IgdGhlIHdvcmQgIm1hc3RlciIgaW4gL2V0Yy94ZW5z b3VyY2UvcG9vbC5jb25mCgpsaWtlIDoKCiMgQ2hlY2sgaWYgd2UncmUgcnVubmluZyBvbiB0aGUg cG9vbCBtYXN0ZXIKaWYgWyBgY2F0IC9ldGMveGVuc291cmNlL3Bvb2wuY29uZmAgIT0gIm1hc3Rl ciIgXTsgdGhlbgogICBleGl0IDAKZmkKClPDqWJhc3RpZW4KCgotLS0tLS0gT3JpZ2luYWwgTWVz c2FnZSAtLS0tLS0KRnJvbTogIkRlbmlzIENhcmRvbiIgPGRlbmlzLmNhcmRvbkB0cmFucXVpbC1p dC1zeXN0ZW1zLmZyPgpUbzogIlNoYWZpIE1vaGFtbWVkIFMiIDxzaGFmaUB2ZW1idS5jb20+CkNj OiAiVGhpbGVlcGFuIFMiIDx0aGlsZWVwYW5AdmVtYnUuY29tPjsgeGVuLWFwaUBsaXN0cy54ZW4u b3JnClNlbnQ6IDIwLjAxLjIwMTQgMTA6MzU6MjcKU3ViamVjdDogUmU6IFtYZW4tQVBJXSBJcyB0 aGUgaG9zdCBhIFhlbiBNYXN0ZXIgPz8KCj5IaSBTaGFmaSwKPgo+PiAgICAgICAgSXMgdGhlcmUg YW55IEFQSSBjYWxsIG9yIGFueSBvdGhlciBtZXRob2QgdG8gZGV0ZWN0IHdoZXRoZXIgdGhlCj4+ aG9zdCBpbiBxdWVzdGlvbiBpcyBhIFBvb2wgbWFzdGVyIG9yIGEgbWVtYmVyIG9mIGEgWGVuIFBP T0wgPwo+Cj5UaGlzIHF1ZXN0aW9uIHdhcyBjb3ZlcmVkIGEgZmV3IGRheXMgYWdvLi4uIFVzaW5n IHB5dGhvbiA6Cj4KPnNlc3Npb24gPSBYZW5BUEkuU2Vzc2lvbignaHR0cHM6Ly8nK3NlbGYueGNw aG9zdCkKPiAgICAgICAgIHRyeToKPiAgICAgICAgICAgICBzZXNzaW9uLmxvZ2luX3dpdGhfcGFz c3dvcmQodXNlcl94ZW4scGFzc3dvcmRfeGVuKQo+ICAgICAgICAgZXhjZXB0IFhlbkFQSS5GYWls dXJlLCBlcnJvcjoKPiAgICAgICAgICAgICBtc2csaXAgPSBlcnJvci5kZXRhaWxzCj4KPiAgICAg ICAgICAgICBpZiBtc2cgPT0gJ0hPU1RfSVNfU0xBVkUnOgo+ICAgICAgICAgICAgICAgICB4Y3Bo b3N0ID0gaXAKPiAgICAgICAgICAgICAgICAgc2Vzc2lvbiA9IFhlbkFQSS5TZXNzaW9uKCdodHRw czovLycreGNwaG9zdCkKPiAgICAgICAgICAgICAgICAgc2Vzc2lvbi5sb2dpbl93aXRoX3Bhc3N3 b3JkKHVzZXJfeGVuLHBhc3N3b3JkX3hlbikKPgo+KHNhbXBsZSBjb2RlIGZyb20gCj5odHRwczov L2dpdGh1Yi5jb20vdHJhbnF1aWxpdC9USVNiYWNrdXAvYmxvYi9tYXN0ZXIvbGlidGlzYmFja3Vw L2JhY2t1cF94dmEucHkpCj4KPj4gICAgICBBbmQgaXMgdGhlcmUgYSBjYWxsIHRvIGdldCB0aGUg aG9zdCBpbmZvIHVzaW5nIHRoZSBzbmFwc2hvdCAKPj4oVVVJRCkKPj5vZiBpdHMgVk1TID8KPgo+ YnkgaG9zdCBpbmZvLCBkbyB5b3UgbWVhbiB0aGUgcGFyYW0tbGlzdCBvZiB0aGUgaG9zdCB3aGVy ZSB0aGUgdm0gaXMgCj5ydW5uaW5nPwo+Cj5Zb3UgY2FuIGdldCB0aGUgVk0gdXVpZCBmcm9tIHNu YXBzaG90IHV1aWQgdXNpbmcKPnhlIHZtLWxpc3QgdXVpZD0kKHhlIHNuYXBzaG90LXBhcmFtLWdl dCBwYXJhbS1uYW1lPXNuYXBzaG90LW9mIAo+dXVpZD0zNWU2OGIzZC1jYWRkLWFmYzYtMGY1Ny04 MzNiZTc3M2I5YmEgKQo+Cj5UaGVuIHlvdSBjYW4gcXVlcnkgdGhlIHJlc2lkZW50LW9uIHZhbHVl IChhdCBsZWFzdCBmb3IgcnVubmluZyB2bSkKPgo+eGUgdm0tcGFyYW0tZ2V0IHBhcmFtLW5hbWU9 cmVzaWRlbnQtb24gCj51dWlkPTcxZTE3OTVlLWExZmEtMTZlYS00ZjIyLTc3MDQ4ZDljMWUwMgo+ Cj5JdCBzaG91bGRuJ3QgYmUgdG9vIGhhcmQgdG8gdHJhbnNsYXRlIHRoaXMgaW4gYXBpIGNhbGxz LiBBbmQgbGlrZSBEYXZpZCAKPnRvbGQgZWFybGllciwgeGFwaSBBUEkgZG9jIGlzIHlvdXIgYmVz dCBmcmllbmQuCj4KPkNoZWVycywKPgo+RGVuaXMKPgo+PlRoYW5rcyAuCj4+Cj4+Cj4+UmVnYXJk cywKPj5TaGFmaSwKPj5WZW1idSBUZWNobm9sb2dpZXMuCj4+Cj4+Cj4+Cj4+VGhpcyBib2R5IHBh cnQgd2lsbCBiZSBkb3dubG9hZGVkIG9uIGRlbWFuZC4KPj4KPgo+Cj4tLSBEZW5pcyBDYXJkb24K PlRyYW5xdWlsIElUIFN5c3RlbXMKPkxlcyBFc3BhY2VzIEp1bGVzIFZlcm5lLCBiw6J0aW1lbnQg QQo+MTIgYXZlbnVlIEp1bGVzIFZlcm5lCj40NDIzMCBTYWludCBTw6liYXN0aWVuIHN1ciBMb2ly ZQo+dGVsIDogKzMzICgwKSAyLjQwLjk3LjU3LjU1Cj5odHRwOi8vd3d3LnRyYW5xdWlsLWl0LXN5 c3RlbXMuZnIKPgo+Cj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwo+WGVuLWFwaSBtYWlsaW5nIGxpc3QKPlhlbi1hcGlAbGlzdHMueGVuLm9yZwo+aHR0cDov L2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgoKCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGlu ZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo=