From xen-users-bounces@lists.xen.org Fri Jun 01 00:07:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 00:07: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 1SaFNx-0007hy-Tb; Fri, 01 Jun 2012 00:06:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaFNw-0007ht-12 for xen-users@lists.xen.org; Fri, 01 Jun 2012 00:06:32 +0000 Received: from [193.109.254.147:48350] by server-6.bemta-14.messagelabs.com id 49/C7-10397-78708CF4; Fri, 01 Jun 2012 00:06:31 +0000 X-Env-Sender: anil.rao@ericsson.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1338509189!12236566!1 X-Originating-IP: [198.24.6.9] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDcyMTA=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12144 invoked from network); 1 Jun 2012 00:06:30 -0000 Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jun 2012 00:06:30 -0000 Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5106Pn9005168; Thu, 31 May 2012 19:06:26 -0500 Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Thu, 31 May 2012 20:06:19 -0400 From: Anil Rao To: Anil Rao , "cyberhawk001@gmail.com" , "xen-users@lists.xen.org" Date: Thu, 31 May 2012 20:06:18 -0400 Thread-Topic: [Xen-users] Hotplugging FPGA to running VM Thread-Index: Ac0/Vhm5C5pNhpV9TFOOmZh8J0/GlwAAklogAAxocWA= Message-ID: References: <4FC7AEF5.3000306@gmail.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] Hotplugging FPGA to running VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0902381842454722347==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0902381842454722347== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_" --_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Since I am new to the xen-users list, I was wondering if my question is mor= e appropriate for the xen-devel list. Any thoughts? Thanks. -Anil ________________________________ From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of Anil Rao Sent: Thursday, May 31, 2012 11:25 AM To: cyberhawk001@gmail.com; xen-users@lists.xen.org Subject: Re: [Xen-users] Hotplugging FPGA to running VM This is a proprietary FPGA device. Each control blade in our router chassis= has one of these FPGAs and its primary function is to control certain dedi= cated hardware components on the blade that are responsible for establishin= g connectivity with the high-speed inter-blade fabric on the router. I am s= orry, but I cannot divulge additional details regarding the FPGA. Here is a more detailed description of my actual usage scenario. 1) The FPGA image must be downloaded onto the device before it can be enabl= ed for use. 2) The VM in question is responsible for performing step (1), which means t= hat the FPGA is not visible to Xen/Dom-0 when the VM is powered on. 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci= -hotplug to assign the device to the VM. This operation completes successfully (as reported by the appropriate x= l command). 4) However, the guest OS inside the VM cannot see the FPGA device after ste= p (3). 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th= e FPGA device (and everything then proceeds normally). The troublesome part here is that I need to shutdown and restart the VM. I = would like to avoid this and rely on Xen pci-hotplug to make the device vis= ible to the guest OS inside the VM. Thanks. -Anil ________________________________ From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of cyberhawk001@gmail.com Sent: Thursday, May 31, 2012 10:49 AM To: xen-users@lists.xen.org Subject: Re: [Xen-users] Hotplugging FPGA to running VM Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve= lopment board or something already assembled and functioning that contains = an FPGA device(s)? Well, just being curious... :) Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o= f PCI devices to the VM. The only one that doesn't work is the FPGA device.= Even for this one, the only time it doesn't work, is if the VM was powered= -on prior to the FPGA device being brought on-line on the host. If the FPGA= was present before the VM was powered-on everything works as expected. It somehow seems like new devices that are introduced in the host, after a = VM has been started on it, cannot be hotplugged into the VM. Thanks. -Anil ________________________________ From: theubaz@gmail.com [mailto:theubaz@gmail.com= ] On Behalf Of John Sherwood Sent: Wednesday, May 30, 2012 7:20 PM To: Anil Rao Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Hotplugging FPGA to running VM Are you sure the guest OS has PCI hotplug support? On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote: Hi, I am trying to assign a FPGA (which is a PCI device) to a running VM. The i= nteresting thing here is that the FPGA is not present when the VM was power= ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line= on the host by downloading its image to the device. So far my attempts at using Xen PCI-passthrough have not been successful. A= lthough Xen reports that the pass-through operation was successful, which I= have verified using the appropriate xl command, I am unable to see the FPG= A from within the guest OS. I have tried both manual rescanning of the PCI bus inside the guest as well= as making use of the pciehp driver. The only way I can (reliably) see the = FPGA from within the guest, is to shutdown and restart the VM and then redo= the hotplug operation. I want to avoid a VM reboot and was wondering if th= is is at all possible and if so what do I need to do to realize it. [The virtualization host is based on the default Xen setup that comes with = SLES 11 SP2] Thanks for any help on this matter. -Anil --_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Since I am new to the xen-users list, I was wonder= ing if my=20 question is more appropriate for the xen-devel list. Any=20 thoughts?
 
Thanks.
-Anil

From: xen-users-bounces@lists.xen.org=20 [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil=20 Rao
Sent: Thursday, May 31, 2012 11:25 AM
To:=20 cyberhawk001@gmail.com; xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control bl= ade in=20 our router chassis has one of these FPGAs and its primary function is to co= ntrol=20 certain dedicated hardware components on the blade that are responsible for= =20 establishing connectivity with the high-speed inter-blade fabric on the rou= ter.=20 I am sorry, but I cannot divulge additional details regarding the=20 FPGA.
 
Here is a more detailed description of my actual= usage=20 scenario.
 
1) The FPGA image must be downloaded onto the devi= ce before=20 it can be enabled for use.
2) The VM in question is responsible for performin= g step=20 (1), which means that the FPGA is not visible to Xen/Dom-0 when=20
    the VM is powered=20 on.
3) After the VM performs step (1), the FPGA is see= n in=20 Dom-0. I use Xen pci-hotplug to assign the device to the VM.<= /DIV>
    This operation completes succes= sfully=20 (as reported by the appropriate xl command).
4) However, the guest OS inside the VM cannot see = the FPGA=20 device after step (3).
5) If I shutdown the VM and re-start it, the guest= OS=20 inside the VM sees the FPGA device (and everything then proceeds=20 normally).
 
The troublesome part here is that I need to shutdo= wn and=20 restart the VM. I would like to avoid this and rely on Xen pci-hotplug to m= ake=20 the device visible to the guest OS inside the VM.
 
Thanks.
-Anil
 
From:=20 xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On=20 Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012= =20 10:49 AM
To: xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? = Is it=20 an FPGA development board or something already assembled and functioning th= at=20 contains an FPGA device(s)?

Well, just being curious...=20 :)



<= SPAN=20 class=3D489542717-31052012>Yes, the guest OS has PCI hotplug support. I a= m able=20 to hotplug a variety of PCI devices to the VM. The only one that doesn't = work=20 is the FPGA device. Even for this one, the only time it doesn't work, is = if=20 the VM was powered-on prior to the FPGA device being brought on-line on t= he=20 host. If the FPGA was present before the VM was powered-on everything wor= ks as=20 expected.
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012>It somehow seems like new devices that are int= roduced=20 in the host, after a VM has been started on it, cannot be hotplugged into= the=20 VM.
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012>Thanks.
<= SPAN=20 class=3D489542717-31052012>-Anil
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012> 
From: theubaz@gmail.com [mailto:theubaz@gmail.com] On Beh= alf Of=20 John Sherwood
Sent: Wednesday, May 30, 2012 7:20=20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.c= om
Subject:=20 Re: [Xen-users] Hotplugging FPGA to running VM

Are yo= u=20 sure the guest OS has PCI hotplug support?=20

On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Hi,
 
I am trying to assign a FPGA (which is a PCI device) to a running = VM.=20 The interesting thing here is that the FPGA is not present when the VM = was=20 powered-on. I.e. sometime after the VM was started, the FPGA was brough= t=20 on-line on the host by downloading its image to the device.
 
So far my attempts at using Xen PCI-passthrough have not been=20 successful. Although Xen reports that the pass-through operation was=20 successful, which I have verified using the appropriate xl command, I a= m=20 unable to see the FPGA from within the guest OS.
 
I have tried both manual rescanning of the PCI bus inside the gues= t as=20 well as making use of the pciehp driver. The only way I can (reliably) = see=20 the FPGA from within the guest, is to shutdown and restart the VM and t= hen=20 redo the hotplug operation. I want to avoid a VM reboot and was wonderi= ng if=20 this is at all possible and if so what do I need to do to realize it.
 
[The virtualization host is based on the default Xen setup that co= mes=20 with SLES 11 SP2]
 
Thanks for any help on this matter.
 
-Anil
--_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_-- --===============0902381842454722347== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0902381842454722347==-- From xen-users-bounces@lists.xen.org Fri Jun 01 00:07:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 00:07: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 1SaFNx-0007hy-Tb; Fri, 01 Jun 2012 00:06:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaFNw-0007ht-12 for xen-users@lists.xen.org; Fri, 01 Jun 2012 00:06:32 +0000 Received: from [193.109.254.147:48350] by server-6.bemta-14.messagelabs.com id 49/C7-10397-78708CF4; Fri, 01 Jun 2012 00:06:31 +0000 X-Env-Sender: anil.rao@ericsson.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1338509189!12236566!1 X-Originating-IP: [198.24.6.9] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDcyMTA=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12144 invoked from network); 1 Jun 2012 00:06:30 -0000 Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jun 2012 00:06:30 -0000 Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5106Pn9005168; Thu, 31 May 2012 19:06:26 -0500 Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Thu, 31 May 2012 20:06:19 -0400 From: Anil Rao To: Anil Rao , "cyberhawk001@gmail.com" , "xen-users@lists.xen.org" Date: Thu, 31 May 2012 20:06:18 -0400 Thread-Topic: [Xen-users] Hotplugging FPGA to running VM Thread-Index: Ac0/Vhm5C5pNhpV9TFOOmZh8J0/GlwAAklogAAxocWA= Message-ID: References: <4FC7AEF5.3000306@gmail.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] Hotplugging FPGA to running VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0902381842454722347==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0902381842454722347== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_" --_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Since I am new to the xen-users list, I was wondering if my question is mor= e appropriate for the xen-devel list. Any thoughts? Thanks. -Anil ________________________________ From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of Anil Rao Sent: Thursday, May 31, 2012 11:25 AM To: cyberhawk001@gmail.com; xen-users@lists.xen.org Subject: Re: [Xen-users] Hotplugging FPGA to running VM This is a proprietary FPGA device. Each control blade in our router chassis= has one of these FPGAs and its primary function is to control certain dedi= cated hardware components on the blade that are responsible for establishin= g connectivity with the high-speed inter-blade fabric on the router. I am s= orry, but I cannot divulge additional details regarding the FPGA. Here is a more detailed description of my actual usage scenario. 1) The FPGA image must be downloaded onto the device before it can be enabl= ed for use. 2) The VM in question is responsible for performing step (1), which means t= hat the FPGA is not visible to Xen/Dom-0 when the VM is powered on. 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci= -hotplug to assign the device to the VM. This operation completes successfully (as reported by the appropriate x= l command). 4) However, the guest OS inside the VM cannot see the FPGA device after ste= p (3). 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th= e FPGA device (and everything then proceeds normally). The troublesome part here is that I need to shutdown and restart the VM. I = would like to avoid this and rely on Xen pci-hotplug to make the device vis= ible to the guest OS inside the VM. Thanks. -Anil ________________________________ From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of cyberhawk001@gmail.com Sent: Thursday, May 31, 2012 10:49 AM To: xen-users@lists.xen.org Subject: Re: [Xen-users] Hotplugging FPGA to running VM Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve= lopment board or something already assembled and functioning that contains = an FPGA device(s)? Well, just being curious... :) Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o= f PCI devices to the VM. The only one that doesn't work is the FPGA device.= Even for this one, the only time it doesn't work, is if the VM was powered= -on prior to the FPGA device being brought on-line on the host. If the FPGA= was present before the VM was powered-on everything works as expected. It somehow seems like new devices that are introduced in the host, after a = VM has been started on it, cannot be hotplugged into the VM. Thanks. -Anil ________________________________ From: theubaz@gmail.com [mailto:theubaz@gmail.com= ] On Behalf Of John Sherwood Sent: Wednesday, May 30, 2012 7:20 PM To: Anil Rao Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Hotplugging FPGA to running VM Are you sure the guest OS has PCI hotplug support? On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote: Hi, I am trying to assign a FPGA (which is a PCI device) to a running VM. The i= nteresting thing here is that the FPGA is not present when the VM was power= ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line= on the host by downloading its image to the device. So far my attempts at using Xen PCI-passthrough have not been successful. A= lthough Xen reports that the pass-through operation was successful, which I= have verified using the appropriate xl command, I am unable to see the FPG= A from within the guest OS. I have tried both manual rescanning of the PCI bus inside the guest as well= as making use of the pciehp driver. The only way I can (reliably) see the = FPGA from within the guest, is to shutdown and restart the VM and then redo= the hotplug operation. I want to avoid a VM reboot and was wondering if th= is is at all possible and if so what do I need to do to realize it. [The virtualization host is based on the default Xen setup that comes with = SLES 11 SP2] Thanks for any help on this matter. -Anil --_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Since I am new to the xen-users list, I was wonder= ing if my=20 question is more appropriate for the xen-devel list. Any=20 thoughts?
 
Thanks.
-Anil

From: xen-users-bounces@lists.xen.org=20 [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil=20 Rao
Sent: Thursday, May 31, 2012 11:25 AM
To:=20 cyberhawk001@gmail.com; xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control bl= ade in=20 our router chassis has one of these FPGAs and its primary function is to co= ntrol=20 certain dedicated hardware components on the blade that are responsible for= =20 establishing connectivity with the high-speed inter-blade fabric on the rou= ter.=20 I am sorry, but I cannot divulge additional details regarding the=20 FPGA.
 
Here is a more detailed description of my actual= usage=20 scenario.
 
1) The FPGA image must be downloaded onto the devi= ce before=20 it can be enabled for use.
2) The VM in question is responsible for performin= g step=20 (1), which means that the FPGA is not visible to Xen/Dom-0 when=20
    the VM is powered=20 on.
3) After the VM performs step (1), the FPGA is see= n in=20 Dom-0. I use Xen pci-hotplug to assign the device to the VM.<= /DIV>
    This operation completes succes= sfully=20 (as reported by the appropriate xl command).
4) However, the guest OS inside the VM cannot see = the FPGA=20 device after step (3).
5) If I shutdown the VM and re-start it, the guest= OS=20 inside the VM sees the FPGA device (and everything then proceeds=20 normally).
 
The troublesome part here is that I need to shutdo= wn and=20 restart the VM. I would like to avoid this and rely on Xen pci-hotplug to m= ake=20 the device visible to the guest OS inside the VM.
 
Thanks.
-Anil
 
From:=20 xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On=20 Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012= =20 10:49 AM
To: xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? = Is it=20 an FPGA development board or something already assembled and functioning th= at=20 contains an FPGA device(s)?

Well, just being curious...=20 :)



<= SPAN=20 class=3D489542717-31052012>Yes, the guest OS has PCI hotplug support. I a= m able=20 to hotplug a variety of PCI devices to the VM. The only one that doesn't = work=20 is the FPGA device. Even for this one, the only time it doesn't work, is = if=20 the VM was powered-on prior to the FPGA device being brought on-line on t= he=20 host. If the FPGA was present before the VM was powered-on everything wor= ks as=20 expected.
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012>It somehow seems like new devices that are int= roduced=20 in the host, after a VM has been started on it, cannot be hotplugged into= the=20 VM.
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012>Thanks.
<= SPAN=20 class=3D489542717-31052012>-Anil
<= SPAN=20 class=3D489542717-31052012> 
<= SPAN=20 class=3D489542717-31052012> 
From: theubaz@gmail.com [mailto:theubaz@gmail.com] On Beh= alf Of=20 John Sherwood
Sent: Wednesday, May 30, 2012 7:20=20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.c= om
Subject:=20 Re: [Xen-users] Hotplugging FPGA to running VM

Are yo= u=20 sure the guest OS has PCI hotplug support?=20

On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Hi,
 
I am trying to assign a FPGA (which is a PCI device) to a running = VM.=20 The interesting thing here is that the FPGA is not present when the VM = was=20 powered-on. I.e. sometime after the VM was started, the FPGA was brough= t=20 on-line on the host by downloading its image to the device.
 
So far my attempts at using Xen PCI-passthrough have not been=20 successful. Although Xen reports that the pass-through operation was=20 successful, which I have verified using the appropriate xl command, I a= m=20 unable to see the FPGA from within the guest OS.
 
I have tried both manual rescanning of the PCI bus inside the gues= t as=20 well as making use of the pciehp driver. The only way I can (reliably) = see=20 the FPGA from within the guest, is to shutdown and restart the VM and t= hen=20 redo the hotplug operation. I want to avoid a VM reboot and was wonderi= ng if=20 this is at all possible and if so what do I need to do to realize it.
 
[The virtualization host is based on the default Xen setup that co= mes=20 with SLES 11 SP2]
 
Thanks for any help on this matter.
 
-Anil
--_000_DD729E174A25344F8D7D351BA4CF57272DAD3D734BEUSAACMS0715e_-- --===============0902381842454722347== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0902381842454722347==-- From xen-users-bounces@lists.xen.org Fri Jun 01 04:08:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:08: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 1SaJ8Y-0004Yk-W1; Fri, 01 Jun 2012 04:06:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJ8W-0004Yf-VS for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:06:53 +0000 Received: from [85.158.143.99:16316] by server-1.bemta-4.messagelabs.com id FF/70-27869-CDF38CF4; Fri, 01 Jun 2012 04:06:52 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1338523610!30273279!1 X-Originating-IP: [98.138.91.90] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26319 invoked from network); 1 Jun 2012 04:06:51 -0000 Received: from nm14-vm2.bullet.mail.ne1.yahoo.com (HELO nm14-vm2.bullet.mail.ne1.yahoo.com) (98.138.91.90) by server-3.tower-216.messagelabs.com with SMTP; 1 Jun 2012 04:06:51 -0000 Received: from [98.138.90.52] by nm14.bullet.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 Received: from [98.138.87.8] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 Received: from [127.0.0.1] by omp1008.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 597033.99076.bm@omp1008.mail.ne1.yahoo.com Received: (qmail 39724 invoked by uid 60001); 1 Jun 2012 04:01:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1338523291; bh=nXr1igtFUgxvEHvVb7A48tRkb8ABKiom4evvoca064M=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=mvBlTKFnoIIR3g1lsRJSDtwz8gTvv4sPt9+p4XUPq6wFAuo6RBa1EXIBg7le/4aHQ5t0Gk4AEd5szbLY+VtskqfMvgky0KVACZEoalapwJBjLQTd38e9zAzG8ZoXSDfqKY1YlrA14RPra8XLcHA03NdKsIe9ynkrwv/2bHQH9As= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=d59FRG21ma/EoWiooCvDBMa7V6DByvd16lZPT3JTFVgqSsZK2t+dkzPIkt851ixN1shiwh61An6aifADJXGP+vGW/Jxx8ESITkJixNGlnkvdzc9XP4nMo9cIIgI7ZIU1JOUoYGTs9k+jwZhBJ1QTghBur0jLSXmp9eQPslTm14E=; X-YMail-OSG: diYFJEcVM1k6bQgfgz3QFxpOPKP6ETRDQKWTPYJNsPwYpnk qAkrfSMxQCL5IGjxM2XrZZDdOZqTK7GKQR1rb5KhgvZ56LG3duf7L4znOK0s ts090spCq_l_oqeb2YMaZ0Q8o8lFGBR8hbF8986WgEzethDN8.rPhtZ8RWnL _Mlxb5OC49cpLWDqGUS3s4p862WW8nCKBpBGuYMWc.iuhG.gYHW2gfLLS050 K25UOj_9Oed.Rw5aEWux4NaMZ5thexurRQBD3nFY7RTlvp0.9Ofp8BWOtZlE C5CDjGrfoNVmg.j3mZ8vOxiAUXrdEYTwZ5Kes4OEhq8z_n61EkG9uiw2nfZY FoUGLvDC45Sect7OQAsRNGZySCZOwpV3twhmpeXW9wYsItAhKF7uJSs4XOGD OxWku2fPLPN20EJm1Zlo6sX8HuYYS64cdxZKyiOFiRJElREZGAYUs3JMDvsK O3vHeJCQrKX6xt.TP65L1DgRU Received: from [24.32.26.44] by web121703.mail.ne1.yahoo.com via HTTP; Thu, 31 May 2012 21:01:31 PDT X-Mailer: YahooMailWebService/0.8.118.349524 Message-ID: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Thu, 31 May 2012 21:01:31 -0700 (PDT) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2760915601237183801==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2760915601237183801== Content-Type: multipart/alternative; boundary="1001534069-311671461-1338523291=:10261" --1001534069-311671461-1338523291=:10261 Content-Type: text/plain; charset=us-ascii Is there a simple answer to the question of using Xen on CentOS 6.x? TIA, Eric P. Truckee, CA --1001534069-311671461-1338523291=:10261 Content-Type: text/html; charset=us-ascii
Is there a simple answer to the question of using Xen on CentOS 6.x?

TIA,
Eric P.
Truckee, CA
--1001534069-311671461-1338523291=:10261-- --===============2760915601237183801== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2760915601237183801==-- From xen-users-bounces@lists.xen.org Fri Jun 01 04:08:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:08: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 1SaJ8Y-0004Yk-W1; Fri, 01 Jun 2012 04:06:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJ8W-0004Yf-VS for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:06:53 +0000 Received: from [85.158.143.99:16316] by server-1.bemta-4.messagelabs.com id FF/70-27869-CDF38CF4; Fri, 01 Jun 2012 04:06:52 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1338523610!30273279!1 X-Originating-IP: [98.138.91.90] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26319 invoked from network); 1 Jun 2012 04:06:51 -0000 Received: from nm14-vm2.bullet.mail.ne1.yahoo.com (HELO nm14-vm2.bullet.mail.ne1.yahoo.com) (98.138.91.90) by server-3.tower-216.messagelabs.com with SMTP; 1 Jun 2012 04:06:51 -0000 Received: from [98.138.90.52] by nm14.bullet.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 Received: from [98.138.87.8] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 Received: from [127.0.0.1] by omp1008.mail.ne1.yahoo.com with NNFMP; 01 Jun 2012 04:01:31 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 597033.99076.bm@omp1008.mail.ne1.yahoo.com Received: (qmail 39724 invoked by uid 60001); 1 Jun 2012 04:01:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1338523291; bh=nXr1igtFUgxvEHvVb7A48tRkb8ABKiom4evvoca064M=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=mvBlTKFnoIIR3g1lsRJSDtwz8gTvv4sPt9+p4XUPq6wFAuo6RBa1EXIBg7le/4aHQ5t0Gk4AEd5szbLY+VtskqfMvgky0KVACZEoalapwJBjLQTd38e9zAzG8ZoXSDfqKY1YlrA14RPra8XLcHA03NdKsIe9ynkrwv/2bHQH9As= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=d59FRG21ma/EoWiooCvDBMa7V6DByvd16lZPT3JTFVgqSsZK2t+dkzPIkt851ixN1shiwh61An6aifADJXGP+vGW/Jxx8ESITkJixNGlnkvdzc9XP4nMo9cIIgI7ZIU1JOUoYGTs9k+jwZhBJ1QTghBur0jLSXmp9eQPslTm14E=; X-YMail-OSG: diYFJEcVM1k6bQgfgz3QFxpOPKP6ETRDQKWTPYJNsPwYpnk qAkrfSMxQCL5IGjxM2XrZZDdOZqTK7GKQR1rb5KhgvZ56LG3duf7L4znOK0s ts090spCq_l_oqeb2YMaZ0Q8o8lFGBR8hbF8986WgEzethDN8.rPhtZ8RWnL _Mlxb5OC49cpLWDqGUS3s4p862WW8nCKBpBGuYMWc.iuhG.gYHW2gfLLS050 K25UOj_9Oed.Rw5aEWux4NaMZ5thexurRQBD3nFY7RTlvp0.9Ofp8BWOtZlE C5CDjGrfoNVmg.j3mZ8vOxiAUXrdEYTwZ5Kes4OEhq8z_n61EkG9uiw2nfZY FoUGLvDC45Sect7OQAsRNGZySCZOwpV3twhmpeXW9wYsItAhKF7uJSs4XOGD OxWku2fPLPN20EJm1Zlo6sX8HuYYS64cdxZKyiOFiRJElREZGAYUs3JMDvsK O3vHeJCQrKX6xt.TP65L1DgRU Received: from [24.32.26.44] by web121703.mail.ne1.yahoo.com via HTTP; Thu, 31 May 2012 21:01:31 PDT X-Mailer: YahooMailWebService/0.8.118.349524 Message-ID: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Thu, 31 May 2012 21:01:31 -0700 (PDT) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2760915601237183801==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2760915601237183801== Content-Type: multipart/alternative; boundary="1001534069-311671461-1338523291=:10261" --1001534069-311671461-1338523291=:10261 Content-Type: text/plain; charset=us-ascii Is there a simple answer to the question of using Xen on CentOS 6.x? TIA, Eric P. Truckee, CA --1001534069-311671461-1338523291=:10261 Content-Type: text/html; charset=us-ascii
Is there a simple answer to the question of using Xen on CentOS 6.x?

TIA,
Eric P.
Truckee, CA
--1001534069-311671461-1338523291=:10261-- --===============2760915601237183801== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2760915601237183801==-- From xen-users-bounces@lists.xen.org Fri Jun 01 04:15:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:15: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 1SaJFp-0004n3-57; Fri, 01 Jun 2012 04:14:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJFn-0004mx-Tf for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:14:24 +0000 Received: from [85.158.143.35:39536] by server-3.bemta-4.messagelabs.com id FD/C1-04252-F9148CF4; Fri, 01 Jun 2012 04:14:23 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-21.messagelabs.com!1338524060!10356348!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24004 invoked from network); 1 Jun 2012 04:14:22 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 04:14:22 -0000 Received: by dadv2 with SMTP id v2so2364049dad.32 for ; Thu, 31 May 2012 21:13:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=dncbLXe1tcOQKlnJXx9O++f/Lcyc/XrEtAf4awtD0Gw=; b=f+zp1VXR9262sVo6pc4otvyv2QPVjAKUMKe8ottWzeSIyYjLkwaD/jHJkeIiN0sQsE bRWKnfx+41Q3p49FvhMAQlQlTMYyLG5Ps7k3l497C8FYBCrWluZi7G7+yJg7SOig0bA3 D4j5aFMSwCsXUplofVpq9O4GPuT/qLWGiEb2fh2vZ2EyJx/q7EcgkkibmJqBC5pQ2i6o Z2ALmw1H/JYEZaS1BhVCdzmE6XklGcodxbImO00NvpEeEHKx5hmIFjgDkdGKL5E7GF7j HiWlQFvmvpYxDO60uPZeRVA2J5BVWgzSudlgQte5f/MLRDBtIy+aLnVR1nybIFjQsvbN JzDA== MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr2895254pbc.61.1338524000967; Thu, 31 May 2012 21:13:20 -0700 (PDT) Received: by 10.68.209.1 with HTTP; Thu, 31 May 2012 21:13:20 -0700 (PDT) In-Reply-To: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> References: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Fri, 1 Jun 2012 11:13:20 +0700 Message-ID: From: "Fajar A. Nugraha" To: Eric X-Gm-Message-State: ALoCoQnIr3OMRbRgTyBDIwLCwr+HnaLchGJnJID96j+U8QXRQh/nOEk/qDCtX4cJTrDMNHT7tkUx Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Jun 1, 2012 at 11:01 AM, Eric wrote: > Is there a simple answer to the question of using Xen on CentOS 6.x? Kind of. https://www.google.com/search?q=xen+wiki+rhel6 One thing missing from the wiki (the one first on search result), is that you can use vanilla kernel as dom0 kernel, like the one provided from http://elrepo.org/tiki/kernel-ml -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 04:15:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:15: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 1SaJFp-0004n3-57; Fri, 01 Jun 2012 04:14:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJFn-0004mx-Tf for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:14:24 +0000 Received: from [85.158.143.35:39536] by server-3.bemta-4.messagelabs.com id FD/C1-04252-F9148CF4; Fri, 01 Jun 2012 04:14:23 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-21.messagelabs.com!1338524060!10356348!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24004 invoked from network); 1 Jun 2012 04:14:22 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 04:14:22 -0000 Received: by dadv2 with SMTP id v2so2364049dad.32 for ; Thu, 31 May 2012 21:13:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=dncbLXe1tcOQKlnJXx9O++f/Lcyc/XrEtAf4awtD0Gw=; b=f+zp1VXR9262sVo6pc4otvyv2QPVjAKUMKe8ottWzeSIyYjLkwaD/jHJkeIiN0sQsE bRWKnfx+41Q3p49FvhMAQlQlTMYyLG5Ps7k3l497C8FYBCrWluZi7G7+yJg7SOig0bA3 D4j5aFMSwCsXUplofVpq9O4GPuT/qLWGiEb2fh2vZ2EyJx/q7EcgkkibmJqBC5pQ2i6o Z2ALmw1H/JYEZaS1BhVCdzmE6XklGcodxbImO00NvpEeEHKx5hmIFjgDkdGKL5E7GF7j HiWlQFvmvpYxDO60uPZeRVA2J5BVWgzSudlgQte5f/MLRDBtIy+aLnVR1nybIFjQsvbN JzDA== MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr2895254pbc.61.1338524000967; Thu, 31 May 2012 21:13:20 -0700 (PDT) Received: by 10.68.209.1 with HTTP; Thu, 31 May 2012 21:13:20 -0700 (PDT) In-Reply-To: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> References: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Fri, 1 Jun 2012 11:13:20 +0700 Message-ID: From: "Fajar A. Nugraha" To: Eric X-Gm-Message-State: ALoCoQnIr3OMRbRgTyBDIwLCwr+HnaLchGJnJID96j+U8QXRQh/nOEk/qDCtX4cJTrDMNHT7tkUx Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Jun 1, 2012 at 11:01 AM, Eric wrote: > Is there a simple answer to the question of using Xen on CentOS 6.x? Kind of. https://www.google.com/search?q=xen+wiki+rhel6 One thing missing from the wiki (the one first on search result), is that you can use vanilla kernel as dom0 kernel, like the one provided from http://elrepo.org/tiki/kernel-ml -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 04:17:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:17: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 1SaJHU-0004ss-2j; Fri, 01 Jun 2012 04:16:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJHR-0004sc-Pz for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:16:06 +0000 Received: from [85.158.139.83:20920] by server-7.bemta-5.messagelabs.com id B0/0D-15932-40248CF4; Fri, 01 Jun 2012 04:16:04 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1338524161!29963612!1 X-Originating-IP: [209.85.213.173] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1712 invoked from network); 1 Jun 2012 04:16:02 -0000 Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com) (209.85.213.173) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 04:16:02 -0000 Received: by yenm4 with SMTP id m4so1709468yen.32 for ; Thu, 31 May 2012 21:16:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YVofEvNsRj2G+Wk1RYjJ+0/BBD5Hc+Nwvq6fhURdStQ=; b=VjnhVV+ityZZ0w4yK72SbtUxtn+BWiHHOBBlACUOS6o0oK9xKGhh8+gQLtW86W+YcH K0sM20IN8gcTYOrg2rU0s7XF8scYdOqFxcWdGTV8a6eIaOh0z6VpQU6MMzYUnoobtPh+ YP6VIO+ZAxQonrWQf+J0H9HddXCilEU+3UOi966bi+x0MkSi7IKNL3IYnUJGWN3NbtTq 7AaRkg0Zq0o/zCrZYndNDAYdYf2hp6Qdh7UQqq2ReXnCztqEQARTrtwgso/s08nPCt5t XQG3eHNSbT4Wvdbw+2bT9IVwpIoh92UH7EeT9Cvr8xmcs9P2svwepoo2dI4yszXr0nri bVzg== MIME-Version: 1.0 Received: by 10.50.222.170 with SMTP id qn10mr138185igc.45.1338524160628; Thu, 31 May 2012 21:16:00 -0700 (PDT) Received: by 10.64.25.162 with HTTP; Thu, 31 May 2012 21:16:00 -0700 (PDT) In-Reply-To: References: <4FC7AEF5.3000306@gmail.com> Date: Fri, 1 Jun 2012 00:16:00 -0400 X-Google-Sender-Auth: fCQ2KYOjG1hRQDpMkLLU0q3PmDo Message-ID: From: John Sherwood To: Anil Rao Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Hotplugging FPGA to running VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3681628919443056654==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3681628919443056654== Content-Type: multipart/alternative; boundary=14dae93411111e17f204c16171f4 --14dae93411111e17f204c16171f4 Content-Type: text/plain; charset=ISO-8859-1 If you've never seen this issue before and can't reproduce it with any other PCI devices, I'd suggest trying the devel mailing list, but I'd first collect whatever logs you can that are salient to the issue beforehand. I've never had issues with PCI hot plug that were limited to a single device though, so I'm certainly drawing a blank here on what it could be. On Thu, May 31, 2012 at 8:06 PM, Anil Rao wrote: > ** > Since I am new to the xen-users list, I was wondering if my question is > more appropriate for the xen-devel list. Any thoughts? > > Thanks. > -Anil > > ------------------------------ > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *Anil Rao > *Sent:* Thursday, May 31, 2012 11:25 AM > *To:* cyberhawk001@gmail.com; xen-users@lists.xen.org > > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > This is a proprietary FPGA device. Each control blade in our router > chassis has one of these FPGAs and its primary function is to control > certain dedicated hardware components on the blade that are responsible for > establishing connectivity with the high-speed inter-blade fabric on the > router. I am sorry, but I cannot divulge additional details regarding the > FPGA. > > Here is a more detailed description of my actual usage scenario. > > 1) The FPGA image must be downloaded onto the device before it can be > enabled for use. > 2) The VM in question is responsible for performing step (1), which means > that the FPGA is not visible to Xen/Dom-0 when > the VM is powered on. > 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen > pci-hotplug to assign the device to the VM. > This operation completes successfully (as reported by the appropriate > xl command). > 4) However, the guest OS inside the VM cannot see the FPGA device after > step (3). > 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees > the FPGA device (and everything then proceeds normally). > > The troublesome part here is that I need to shutdown and restart the VM. I > would like to avoid this and rely on Xen pci-hotplug to make the device > visible to the guest OS inside the VM. > > Thanks. > -Anil > > ------------------------------ > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *cyberhawk001@gmail.com > *Sent:* Thursday, May 31, 2012 10:49 AM > *To:* xen-users@lists.xen.org > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > Just out of curiosity, what kind of *FPGA device* is this? Is it an FPGA > development board or something already assembled and functioning that > contains an FPGA device(s)? > > Well, just being curious... :) > > > > Yes, the guest OS has PCI hotplug support. I am able to hotplug a > variety of PCI devices to the VM. The only one that doesn't work is the > FPGA device. Even for this one, the only time it doesn't work, is if the VM > was powered-on prior to the FPGA device being brought on-line on the host. > If the FPGA was present before the VM was powered-on everything works as > expected. > > It somehow seems like new devices that are introduced in the host, after a > VM has been started on it, cannot be hotplugged into the VM. > > Thanks. > -Anil > > > ------------------------------ > *From:* theubaz@gmail.com [mailto:theubaz@gmail.com ] > *On Behalf Of *John Sherwood > *Sent:* Wednesday, May 30, 2012 7:20 PM > *To:* Anil Rao > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > Are you sure the guest OS has PCI hotplug support? > > On Wed, May 30, 2012 at 10:14 PM, Anil Rao wrote: > >> Hi, >> >> I am trying to assign a FPGA (which is a PCI device) to a running VM. The >> interesting thing here is that the FPGA is not present when the VM was >> powered-on. I.e. sometime after the VM was started, the FPGA was brought >> on-line on the host by downloading its image to the device. >> >> So far my attempts at using Xen PCI-passthrough have not been successful. >> Although Xen reports that the pass-through operation was successful, which >> I have verified using the appropriate xl command, I am unable to see the >> FPGA from within the guest OS. >> >> I have tried both manual rescanning of the PCI bus inside the guest as >> well as making use of the pciehp driver. The only way I can (reliably) see >> the FPGA from within the guest, is to shutdown and restart the VM and then >> redo the hotplug operation. I want to avoid a VM reboot and was wondering >> if this is at all possible and if so what do I need to do to realize it. >> >> [The virtualization host is based on the default Xen setup that comes >> with SLES 11 SP2] >> >> Thanks for any help on this matter. >> >> -Anil >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > --14dae93411111e17f204c16171f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you've never seen this issue before and can't reproduce it with = any other PCI devices, I'd suggest trying the devel mailing list, but I= 'd first collect whatever logs you can that are salient to the issue be= forehand. =A0I've never had issues with PCI hot plug that were limited = to a single device though, so I'm certainly drawing a blank here on wha= t it could be.

On Thu, May 31, 2012 at 8:06 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Since I am new to the xen-users list, I was wondering if my=20 question is more appropriate for the xen-devel list. Any=20 thoughts?
=A0
Thanks.
-Anil

From: xen-users-bounces@lists.xen.org=20 [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil=20 Rao
Sent: Thursday, May 31, 2012 11:25 AM
To:=20 cyberhawk001@gm= ail.com; x= en-users@lists.xen.org

Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

=
This is a proprietary FPGA device. Each control blade in=20 our router chassis has one of these FPGAs and its primary function is to co= ntrol=20 certain dedicated hardware components on the blade that are responsible for= =20 establishing connectivity with the high-speed inter-blade fabric on the rou= ter.=20 I am sorry, but I cannot divulge additional details regarding the=20 FPGA.
=A0
Here is a more detailed description of my actual usage=20 scenario.
=A0
1) The FPGA image must be downloaded onto the device before=20 it can be enabled for use.
2) The VM in question is responsible for performing step=20 (1), which means that the FPGA is not visible to Xen/Dom-0 when=20
=A0=A0=A0 the VM is powered=20 on.
3) After the VM performs step (1), the FPGA is seen in=20 Dom-0. I use Xen pci-hotplug to assign the device to the VM.<= /div>
=A0=A0=A0 This operation completes successfully=20 (as reported by the appropriate xl command).
4) However, the guest OS inside the VM cannot see the FPGA=20 device after step (3).
5) If I shutdown the VM and re-start it, the guest OS=20 inside the VM sees the FPGA device (and everything then proceeds=20 normally).
=A0
The troublesome part here is that I need to shutdown and=20 restart the VM. I would like to avoid this and rely on Xen pci-hotplug to m= ake=20 the device visible to the guest OS inside the VM.
=A0
Thanks.
-Anil
=A0
From:=20 xen-us= ers-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On= =20 Behalf Of c= yberhawk001@gmail.com
Sent: Thursday, May 31, 2012=20 10:49 AM
To: xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? = Is it=20 an FPGA development board or something already assembled and functioning th= at=20 contains an FPGA device(s)?

Well, just being curious...=20 :)



=20
Yes, the guest OS has PCI hotplug support. I am able=20 to hotplug a variety of PCI devices to the VM. The only one that doesn= 9;t work=20 is the FPGA device. Even for this one, the only time it doesn't work,= is if=20 the VM was powered-on prior to the FPGA device being brought on-line on t= he=20 host. If the FPGA was present before the VM was powered-on everything wor= ks as=20 expected.
=A0
It somehow seems like new devices that are introduced=20 in the host, after a VM has been started on it, cannot be hotplugged into= the=20 VM.
=A0
Thanks.
-Anil
=A0
=A0
From: theubaz@gmail.com [mailto:theubaz@gmail.co= m] On Behalf Of=20 John Sherwood
Sent: Wednesday, May 30, 2012 7:20=20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
S= ubject:=20 Re: [Xen-users] Hotplugging FPGA to running VM

Are yo= u=20 sure the guest OS has PCI hotplug support?=20

On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Hi,
=A0
I am trying to assign a FPGA (which is a PCI device) to a running = VM.=20 The interesting thing here is that the FPGA is not present when the VM = was=20 powered-on. I.e. sometime after the VM was started, the FPGA was brough= t=20 on-line on the host by downloading its image to the device.
=A0
So far my attempts at using Xen PCI-passthrough have not been=20 successful. Although Xen reports that the pass-through operation was=20 successful, which I have verified using the appropriate xl command, I a= m=20 unable to see the FPGA from within the guest OS.
=A0
I have tried both manual rescanning of the PCI bus inside the gues= t as=20 well as making use of the pciehp driver. The only way I can (reliably) = see=20 the FPGA from within the guest, is to shutdown and restart the VM and t= hen=20 redo the hotplug operation. I want to avoid a VM reboot and was wonderi= ng if=20 this is at all possible and if so what do I need to do to realize it.
=A0
[The virtualization host is based on the default Xen setup that co= mes=20 with SLES 11 SP2]
=A0
Thanks for any help on this matter.
=A0
-Anil

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users


--14dae93411111e17f204c16171f4-- --===============3681628919443056654== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3681628919443056654==-- From xen-users-bounces@lists.xen.org Fri Jun 01 04:17:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 04:17: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 1SaJHU-0004ss-2j; Fri, 01 Jun 2012 04:16:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaJHR-0004sc-Pz for xen-users@lists.xen.org; Fri, 01 Jun 2012 04:16:06 +0000 Received: from [85.158.139.83:20920] by server-7.bemta-5.messagelabs.com id B0/0D-15932-40248CF4; Fri, 01 Jun 2012 04:16:04 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1338524161!29963612!1 X-Originating-IP: [209.85.213.173] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1712 invoked from network); 1 Jun 2012 04:16:02 -0000 Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com) (209.85.213.173) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 04:16:02 -0000 Received: by yenm4 with SMTP id m4so1709468yen.32 for ; Thu, 31 May 2012 21:16:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YVofEvNsRj2G+Wk1RYjJ+0/BBD5Hc+Nwvq6fhURdStQ=; b=VjnhVV+ityZZ0w4yK72SbtUxtn+BWiHHOBBlACUOS6o0oK9xKGhh8+gQLtW86W+YcH K0sM20IN8gcTYOrg2rU0s7XF8scYdOqFxcWdGTV8a6eIaOh0z6VpQU6MMzYUnoobtPh+ YP6VIO+ZAxQonrWQf+J0H9HddXCilEU+3UOi966bi+x0MkSi7IKNL3IYnUJGWN3NbtTq 7AaRkg0Zq0o/zCrZYndNDAYdYf2hp6Qdh7UQqq2ReXnCztqEQARTrtwgso/s08nPCt5t XQG3eHNSbT4Wvdbw+2bT9IVwpIoh92UH7EeT9Cvr8xmcs9P2svwepoo2dI4yszXr0nri bVzg== MIME-Version: 1.0 Received: by 10.50.222.170 with SMTP id qn10mr138185igc.45.1338524160628; Thu, 31 May 2012 21:16:00 -0700 (PDT) Received: by 10.64.25.162 with HTTP; Thu, 31 May 2012 21:16:00 -0700 (PDT) In-Reply-To: References: <4FC7AEF5.3000306@gmail.com> Date: Fri, 1 Jun 2012 00:16:00 -0400 X-Google-Sender-Auth: fCQ2KYOjG1hRQDpMkLLU0q3PmDo Message-ID: From: John Sherwood To: Anil Rao Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Hotplugging FPGA to running VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3681628919443056654==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3681628919443056654== Content-Type: multipart/alternative; boundary=14dae93411111e17f204c16171f4 --14dae93411111e17f204c16171f4 Content-Type: text/plain; charset=ISO-8859-1 If you've never seen this issue before and can't reproduce it with any other PCI devices, I'd suggest trying the devel mailing list, but I'd first collect whatever logs you can that are salient to the issue beforehand. I've never had issues with PCI hot plug that were limited to a single device though, so I'm certainly drawing a blank here on what it could be. On Thu, May 31, 2012 at 8:06 PM, Anil Rao wrote: > ** > Since I am new to the xen-users list, I was wondering if my question is > more appropriate for the xen-devel list. Any thoughts? > > Thanks. > -Anil > > ------------------------------ > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *Anil Rao > *Sent:* Thursday, May 31, 2012 11:25 AM > *To:* cyberhawk001@gmail.com; xen-users@lists.xen.org > > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > This is a proprietary FPGA device. Each control blade in our router > chassis has one of these FPGAs and its primary function is to control > certain dedicated hardware components on the blade that are responsible for > establishing connectivity with the high-speed inter-blade fabric on the > router. I am sorry, but I cannot divulge additional details regarding the > FPGA. > > Here is a more detailed description of my actual usage scenario. > > 1) The FPGA image must be downloaded onto the device before it can be > enabled for use. > 2) The VM in question is responsible for performing step (1), which means > that the FPGA is not visible to Xen/Dom-0 when > the VM is powered on. > 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen > pci-hotplug to assign the device to the VM. > This operation completes successfully (as reported by the appropriate > xl command). > 4) However, the guest OS inside the VM cannot see the FPGA device after > step (3). > 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees > the FPGA device (and everything then proceeds normally). > > The troublesome part here is that I need to shutdown and restart the VM. I > would like to avoid this and rely on Xen pci-hotplug to make the device > visible to the guest OS inside the VM. > > Thanks. > -Anil > > ------------------------------ > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *cyberhawk001@gmail.com > *Sent:* Thursday, May 31, 2012 10:49 AM > *To:* xen-users@lists.xen.org > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > Just out of curiosity, what kind of *FPGA device* is this? Is it an FPGA > development board or something already assembled and functioning that > contains an FPGA device(s)? > > Well, just being curious... :) > > > > Yes, the guest OS has PCI hotplug support. I am able to hotplug a > variety of PCI devices to the VM. The only one that doesn't work is the > FPGA device. Even for this one, the only time it doesn't work, is if the VM > was powered-on prior to the FPGA device being brought on-line on the host. > If the FPGA was present before the VM was powered-on everything works as > expected. > > It somehow seems like new devices that are introduced in the host, after a > VM has been started on it, cannot be hotplugged into the VM. > > Thanks. > -Anil > > > ------------------------------ > *From:* theubaz@gmail.com [mailto:theubaz@gmail.com ] > *On Behalf Of *John Sherwood > *Sent:* Wednesday, May 30, 2012 7:20 PM > *To:* Anil Rao > *Cc:* xen-users@lists.xensource.com > *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM > > Are you sure the guest OS has PCI hotplug support? > > On Wed, May 30, 2012 at 10:14 PM, Anil Rao wrote: > >> Hi, >> >> I am trying to assign a FPGA (which is a PCI device) to a running VM. The >> interesting thing here is that the FPGA is not present when the VM was >> powered-on. I.e. sometime after the VM was started, the FPGA was brought >> on-line on the host by downloading its image to the device. >> >> So far my attempts at using Xen PCI-passthrough have not been successful. >> Although Xen reports that the pass-through operation was successful, which >> I have verified using the appropriate xl command, I am unable to see the >> FPGA from within the guest OS. >> >> I have tried both manual rescanning of the PCI bus inside the guest as >> well as making use of the pciehp driver. The only way I can (reliably) see >> the FPGA from within the guest, is to shutdown and restart the VM and then >> redo the hotplug operation. I want to avoid a VM reboot and was wondering >> if this is at all possible and if so what do I need to do to realize it. >> >> [The virtualization host is based on the default Xen setup that comes >> with SLES 11 SP2] >> >> Thanks for any help on this matter. >> >> -Anil >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > --14dae93411111e17f204c16171f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you've never seen this issue before and can't reproduce it with = any other PCI devices, I'd suggest trying the devel mailing list, but I= 'd first collect whatever logs you can that are salient to the issue be= forehand. =A0I've never had issues with PCI hot plug that were limited = to a single device though, so I'm certainly drawing a blank here on wha= t it could be.

On Thu, May 31, 2012 at 8:06 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Since I am new to the xen-users list, I was wondering if my=20 question is more appropriate for the xen-devel list. Any=20 thoughts?
=A0
Thanks.
-Anil

From: xen-users-bounces@lists.xen.org=20 [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil=20 Rao
Sent: Thursday, May 31, 2012 11:25 AM
To:=20 cyberhawk001@gm= ail.com; x= en-users@lists.xen.org

Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

=
This is a proprietary FPGA device. Each control blade in=20 our router chassis has one of these FPGAs and its primary function is to co= ntrol=20 certain dedicated hardware components on the blade that are responsible for= =20 establishing connectivity with the high-speed inter-blade fabric on the rou= ter.=20 I am sorry, but I cannot divulge additional details regarding the=20 FPGA.
=A0
Here is a more detailed description of my actual usage=20 scenario.
=A0
1) The FPGA image must be downloaded onto the device before=20 it can be enabled for use.
2) The VM in question is responsible for performing step=20 (1), which means that the FPGA is not visible to Xen/Dom-0 when=20
=A0=A0=A0 the VM is powered=20 on.
3) After the VM performs step (1), the FPGA is seen in=20 Dom-0. I use Xen pci-hotplug to assign the device to the VM.<= /div>
=A0=A0=A0 This operation completes successfully=20 (as reported by the appropriate xl command).
4) However, the guest OS inside the VM cannot see the FPGA=20 device after step (3).
5) If I shutdown the VM and re-start it, the guest OS=20 inside the VM sees the FPGA device (and everything then proceeds=20 normally).
=A0
The troublesome part here is that I need to shutdown and=20 restart the VM. I would like to avoid this and rely on Xen pci-hotplug to m= ake=20 the device visible to the guest OS inside the VM.
=A0
Thanks.
-Anil
=A0
From:=20 xen-us= ers-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On= =20 Behalf Of c= yberhawk001@gmail.com
Sent: Thursday, May 31, 2012=20 10:49 AM
To: xen-users@lists.xen.org
Subject: Re:=20 [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? = Is it=20 an FPGA development board or something already assembled and functioning th= at=20 contains an FPGA device(s)?

Well, just being curious...=20 :)



=20
Yes, the guest OS has PCI hotplug support. I am able=20 to hotplug a variety of PCI devices to the VM. The only one that doesn= 9;t work=20 is the FPGA device. Even for this one, the only time it doesn't work,= is if=20 the VM was powered-on prior to the FPGA device being brought on-line on t= he=20 host. If the FPGA was present before the VM was powered-on everything wor= ks as=20 expected.
=A0
It somehow seems like new devices that are introduced=20 in the host, after a VM has been started on it, cannot be hotplugged into= the=20 VM.
=A0
Thanks.
-Anil
=A0
=A0
From: theubaz@gmail.com [mailto:theubaz@gmail.co= m] On Behalf Of=20 John Sherwood
Sent: Wednesday, May 30, 2012 7:20=20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
S= ubject:=20 Re: [Xen-users] Hotplugging FPGA to running VM

Are yo= u=20 sure the guest OS has PCI hotplug support?=20

On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:
Hi,
=A0
I am trying to assign a FPGA (which is a PCI device) to a running = VM.=20 The interesting thing here is that the FPGA is not present when the VM = was=20 powered-on. I.e. sometime after the VM was started, the FPGA was brough= t=20 on-line on the host by downloading its image to the device.
=A0
So far my attempts at using Xen PCI-passthrough have not been=20 successful. Although Xen reports that the pass-through operation was=20 successful, which I have verified using the appropriate xl command, I a= m=20 unable to see the FPGA from within the guest OS.
=A0
I have tried both manual rescanning of the PCI bus inside the gues= t as=20 well as making use of the pciehp driver. The only way I can (reliably) = see=20 the FPGA from within the guest, is to shutdown and restart the VM and t= hen=20 redo the hotplug operation. I want to avoid a VM reboot and was wonderi= ng if=20 this is at all possible and if so what do I need to do to realize it.
=A0
[The virtualization host is based on the default Xen setup that co= mes=20 with SLES 11 SP2]
=A0
Thanks for any help on this matter.
=A0
-Anil

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users


--14dae93411111e17f204c16171f4-- --===============3681628919443056654== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3681628919443056654==-- From xen-users-bounces@lists.xen.org Fri Jun 01 06:41:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 06:41:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaLXM-0000He-KY; Fri, 01 Jun 2012 06:40:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaLXL-0000HQ-VU for xen-users@lists.xen.org; Fri, 01 Jun 2012 06:40:40 +0000 Received: from [85.158.143.35:40657] by server-2.bemta-4.messagelabs.com id 3A/D9-11595-6E368CF4; Fri, 01 Jun 2012 06:40:38 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1338532824!18371458!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA2ODY=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24951 invoked from network); 1 Jun 2012 06:40:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 06:40:24 -0000 X-IronPort-AV: E=Sophos;i="4.75,696,1330905600"; d="scan'208";a="12778396" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Jun 2012 06:40:22 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012 07:40:22 +0100 Message-ID: <1338532821.14877.49.camel@dagon.hellion.org.uk> From: Ian Campbell To: "cyberhawk001@gmail.com" Date: Fri, 1 Jun 2012 07:40:21 +0100 In-Reply-To: <4FC7767B.6040706@gmail.com> References: <4FC7767B.6040706@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Installing XAPI on Debian Wheezy with Xen 4.2-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Questions about XCP and XAPI are best addressed to the xen-api@ list. I've CCd it for you. On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote: > I have not had any luck getting the XAPI to install or even work in > Debian Wheezy 64bit SO figured i ask anyone out there: > > 1.) Has any Xen user(s) have successfully installed the XAPI Toolstack > on Xen 4.2-unstable and how were you able to do it? XAPI needs to be built against the specific hypervisor version it is going to run against. The XAPI packages in Wheezy are built against the 4.1 packages in Wheezy. Why don't you just use the packaged version of both Xen (i.e. 4.1) and xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an XCP system up and running. Unless you have a really strong reason to build the Xen yourself this is something which is best left to the distros. In the past xapi has needed actual porting effort when moving between Xen versions. I don't know if this will be the case for moving 4.1->4.2 but I would suggest that unless you > 2.) Has anyone been able to compile the XAPI Toolstack from source and > again how to do that? This I don't know. Have you checked the wiki pages? Also you could just rebuild the Debian packages in the normal way. > - I had Xen 4.2-unstable installed, removed it and ran sudo apt-get > xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the > XE toolstack i just can't get to load or run, even the XM toolstack > doesn't work either. Following the Wiki guides don't quite help yet. > The /etc/init.d folder only contains xendomains, xen and all of the > xcp-* daemons. > > - I would be nice to know how to just remove/uninstall > xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and > xenstore-utils, so than one can install Xen 4.2-unstable instead. Why do you want to do this? Why not run 4.1 which is what the XCP packages are built against and what people have been testing in the context of Wheezy? > - On the flip-side, it would be nice if it was easy to install JUST > the XAPI Toolstack as a standalone package on top of an existing Xen > Dom0... :) I don't understand this. If you have an existing Xen dom0 can't you just apt-get install xcp-xapi? > Thank you for any input from anyone who has experimented with XAPI > installation on Debian. I've not run XAPI on Debian but it seems to me that by trying to use 4.2-unstable you are making life much more difficult for yourself than it needs to be. Just use the existing packages in Debian and I think things will go much smoother. Even if you do have a good reason for running 4.2 I'd suggest following the guides with 4.1 first so you get a feel for things before striking off and blazing a new trail to 4.2. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 06:41:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 06:41:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaLXM-0000He-KY; Fri, 01 Jun 2012 06:40:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaLXL-0000HQ-VU for xen-users@lists.xen.org; Fri, 01 Jun 2012 06:40:40 +0000 Received: from [85.158.143.35:40657] by server-2.bemta-4.messagelabs.com id 3A/D9-11595-6E368CF4; Fri, 01 Jun 2012 06:40:38 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1338532824!18371458!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA2ODY=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24951 invoked from network); 1 Jun 2012 06:40:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 06:40:24 -0000 X-IronPort-AV: E=Sophos;i="4.75,696,1330905600"; d="scan'208";a="12778396" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Jun 2012 06:40:22 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012 07:40:22 +0100 Message-ID: <1338532821.14877.49.camel@dagon.hellion.org.uk> From: Ian Campbell To: "cyberhawk001@gmail.com" Date: Fri, 1 Jun 2012 07:40:21 +0100 In-Reply-To: <4FC7767B.6040706@gmail.com> References: <4FC7767B.6040706@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Installing XAPI on Debian Wheezy with Xen 4.2-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Questions about XCP and XAPI are best addressed to the xen-api@ list. I've CCd it for you. On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote: > I have not had any luck getting the XAPI to install or even work in > Debian Wheezy 64bit SO figured i ask anyone out there: > > 1.) Has any Xen user(s) have successfully installed the XAPI Toolstack > on Xen 4.2-unstable and how were you able to do it? XAPI needs to be built against the specific hypervisor version it is going to run against. The XAPI packages in Wheezy are built against the 4.1 packages in Wheezy. Why don't you just use the packaged version of both Xen (i.e. 4.1) and xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an XCP system up and running. Unless you have a really strong reason to build the Xen yourself this is something which is best left to the distros. In the past xapi has needed actual porting effort when moving between Xen versions. I don't know if this will be the case for moving 4.1->4.2 but I would suggest that unless you > 2.) Has anyone been able to compile the XAPI Toolstack from source and > again how to do that? This I don't know. Have you checked the wiki pages? Also you could just rebuild the Debian packages in the normal way. > - I had Xen 4.2-unstable installed, removed it and ran sudo apt-get > xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the > XE toolstack i just can't get to load or run, even the XM toolstack > doesn't work either. Following the Wiki guides don't quite help yet. > The /etc/init.d folder only contains xendomains, xen and all of the > xcp-* daemons. > > - I would be nice to know how to just remove/uninstall > xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and > xenstore-utils, so than one can install Xen 4.2-unstable instead. Why do you want to do this? Why not run 4.1 which is what the XCP packages are built against and what people have been testing in the context of Wheezy? > - On the flip-side, it would be nice if it was easy to install JUST > the XAPI Toolstack as a standalone package on top of an existing Xen > Dom0... :) I don't understand this. If you have an existing Xen dom0 can't you just apt-get install xcp-xapi? > Thank you for any input from anyone who has experimented with XAPI > installation on Debian. I've not run XAPI on Debian but it seems to me that by trying to use 4.2-unstable you are making life much more difficult for yourself than it needs to be. Just use the existing packages in Debian and I think things will go much smoother. Even if you do have a good reason for running 4.2 I'd suggest following the guides with 4.1 first so you get a feel for things before striking off and blazing a new trail to 4.2. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 07:37:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 07:37: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 1SaMPN-0001pQ-GZ; Fri, 01 Jun 2012 07:36:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaMPL-0001pL-JO for xen-users@lists.xen.org; Fri, 01 Jun 2012 07:36:27 +0000 Received: from [85.158.139.83:60973] by server-3.bemta-5.messagelabs.com id 92/ED-29112-AF078CF4; Fri, 01 Jun 2012 07:36:26 +0000 X-Env-Sender: xenware@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1338536169!27551036!1 X-Originating-IP: [209.85.160.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDUwNjkgKHRpbWVvdXQp\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25497 invoked from network); 1 Jun 2012 07:36:10 -0000 Received: from mail-gh0-f169.google.com (HELO mail-gh0-f169.google.com) (209.85.160.169) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 07:36:10 -0000 Received: by ghrr18 with SMTP id r18so1836414ghr.28 for ; Fri, 01 Jun 2012 00:36:08 -0700 (PDT) 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=nySV/zzFvq2ujIWGUcHB3WbAqfnx0IJfmF8dTe0PMmg=; b=aw/IRo9ZkuZFwvvk/m0h4RC29inOdQGpIKSd6H/l0ExuacP/rjDSArtCPN5gAHikSx s04Rnk0EnALk7eyY8X0eGQsNb5AbO+lCeQvEpC/hPkUO1AMIXmW8WoksTHtZT1iyDTjx QFnkrkK5NJzPWuCZvP6dCG6h5/PHbiMMAfnU97eiO/sIKx33aeTtPUhr+7fCeGpo3h50 QZUVQJ1bA3MmcjeOZ31I+iTtgcejEMZZD/3R19SQr2rBCOhDCdEk3kEJk4pA6vWEu6Vr ce82CD5IsRx1O60MB3XtZv6oDaY6SMznxKH8FgJbLVZtkbcQ0WDfWGjbvZRmgHsuIVXA N0Dg== MIME-Version: 1.0 Received: by 10.42.87.75 with SMTP id x11mr777767icl.25.1338536168300; Fri, 01 Jun 2012 00:36:08 -0700 (PDT) Received: by 10.50.179.38 with HTTP; Fri, 1 Jun 2012 00:36:08 -0700 (PDT) In-Reply-To: References: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Fri, 1 Jun 2012 09:36:08 +0200 Message-ID: From: Peter Braun To: "Fajar A. Nugraha" Cc: "xen-users@lists.xen.org" , Eric Subject: Re: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org You should check chroon repo: http://choon.net/forum/read.php?16,672307 Excellent work by Giam Teck Choon System Administrator CHOON.NET Another option: http://www.gitco.de/repo/ or http://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ Br Peter 2012/6/1 Fajar A. Nugraha : > On Fri, Jun 1, 2012 at 11:01 AM, Eric wrote: >> Is there a simple answer to the question of using Xen on CentOS 6.x? > > Kind of. > > https://www.google.com/search?q=xen+wiki+rhel6 > > One thing missing from the wiki (the one first on search result), is > that you can use vanilla kernel as dom0 kernel, like the one provided > from http://elrepo.org/tiki/kernel-ml > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 07:37:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 07:37: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 1SaMPN-0001pQ-GZ; Fri, 01 Jun 2012 07:36:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaMPL-0001pL-JO for xen-users@lists.xen.org; Fri, 01 Jun 2012 07:36:27 +0000 Received: from [85.158.139.83:60973] by server-3.bemta-5.messagelabs.com id 92/ED-29112-AF078CF4; Fri, 01 Jun 2012 07:36:26 +0000 X-Env-Sender: xenware@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1338536169!27551036!1 X-Originating-IP: [209.85.160.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDUwNjkgKHRpbWVvdXQp\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25497 invoked from network); 1 Jun 2012 07:36:10 -0000 Received: from mail-gh0-f169.google.com (HELO mail-gh0-f169.google.com) (209.85.160.169) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 07:36:10 -0000 Received: by ghrr18 with SMTP id r18so1836414ghr.28 for ; Fri, 01 Jun 2012 00:36:08 -0700 (PDT) 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=nySV/zzFvq2ujIWGUcHB3WbAqfnx0IJfmF8dTe0PMmg=; b=aw/IRo9ZkuZFwvvk/m0h4RC29inOdQGpIKSd6H/l0ExuacP/rjDSArtCPN5gAHikSx s04Rnk0EnALk7eyY8X0eGQsNb5AbO+lCeQvEpC/hPkUO1AMIXmW8WoksTHtZT1iyDTjx QFnkrkK5NJzPWuCZvP6dCG6h5/PHbiMMAfnU97eiO/sIKx33aeTtPUhr+7fCeGpo3h50 QZUVQJ1bA3MmcjeOZ31I+iTtgcejEMZZD/3R19SQr2rBCOhDCdEk3kEJk4pA6vWEu6Vr ce82CD5IsRx1O60MB3XtZv6oDaY6SMznxKH8FgJbLVZtkbcQ0WDfWGjbvZRmgHsuIVXA N0Dg== MIME-Version: 1.0 Received: by 10.42.87.75 with SMTP id x11mr777767icl.25.1338536168300; Fri, 01 Jun 2012 00:36:08 -0700 (PDT) Received: by 10.50.179.38 with HTTP; Fri, 1 Jun 2012 00:36:08 -0700 (PDT) In-Reply-To: References: <1338523291.10261.YahooMailNeo@web121703.mail.ne1.yahoo.com> Date: Fri, 1 Jun 2012 09:36:08 +0200 Message-ID: From: Peter Braun To: "Fajar A. Nugraha" Cc: "xen-users@lists.xen.org" , Eric Subject: Re: [Xen-users] Xen on CentOS 6.x? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org You should check chroon repo: http://choon.net/forum/read.php?16,672307 Excellent work by Giam Teck Choon System Administrator CHOON.NET Another option: http://www.gitco.de/repo/ or http://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ Br Peter 2012/6/1 Fajar A. Nugraha : > On Fri, Jun 1, 2012 at 11:01 AM, Eric wrote: >> Is there a simple answer to the question of using Xen on CentOS 6.x? > > Kind of. > > https://www.google.com/search?q=xen+wiki+rhel6 > > One thing missing from the wiki (the one first on search result), is > that you can use vanilla kernel as dom0 kernel, like the one provided > from http://elrepo.org/tiki/kernel-ml > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:16:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:16: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 1SaNxP-0004m9-Ju; Fri, 01 Jun 2012 09:15:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNxN-0004m4-NG for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:15:41 +0000 Received: from [85.158.143.35:16591] by server-1.bemta-4.messagelabs.com id 30/48-27869-D3888CF4; Fri, 01 Jun 2012 09:15:41 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1338542138!17081852!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7161 invoked from network); 1 Jun 2012 09:15:39 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:15:39 -0000 Received: by obbwd20 with SMTP id wd20so3409617obb.32 for ; Fri, 01 Jun 2012 02:15:18 -0700 (PDT) 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=0tvDHjRA6rWgRdq/EjinNqyh/HWPHITumQXgGjZMaqY=; b=kl6Zm18oXhCduqL/XSU8Eo2tuvLNW7SUopW7JPoBGiUkyHROkUg06ON+BmpdyaRtAL JUh0cYmjPwdcGO2zvNrwXrSzj9xU/x0DMQzdmFbA46kG87dVxc7qTq1Y+UfgrG88SuF+ 7suuQ/qtq3K5kHVcodHEkkr8dyiBJ8TKkHFPUW/50Icro4nUMzgxxE+6R4qdUXxvMaQl vp1PqdJ7jBtKYH7pCBc5EJPk/Hn2JFwsZX8YfCNuZHeCI+Rjhr6c8eNbbcDpn787BNeW o3fgE599lVPM8KoTPk6c9BjqDiS2Hi+oFvWmTZRVW1jn7aOV4iHQRUGg5neuI3BvECXe 6grQ== MIME-Version: 1.0 Received: by 10.60.3.202 with SMTP id e10mr1736639oee.52.1338542118824; Fri, 01 Jun 2012 02:15:18 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 02:15:18 -0700 (PDT) Date: Fri, 1 Jun 2012 05:15:18 -0400 Message-ID: From: Jane Wayne To: xen-users@lists.xen.org Subject: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org i've installed XCP 1.5-beta. i'm a little confused as to what has happened. everything so far seems to work. however, i need more information on what was done to my hard disk during the installation and how was the file system set up. in particular, i was investigating how to create a new logical volume to place my ISO file to use as my ISO storage (SR). i notice (see below with lvs command) that something like this was already created automatically, BUT, it was not mounted anywhere. i was wondering why this artifact logical volume was created and not mounted? i have a 3 TB hard disk. when i issue: fdisk -l, i get the following output. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). DOS partition table format can not be used on drives for volumes larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID partition table format (GPT). Disk /dev/sda: 3000.5 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 266306 2147483647+ ee EFI GPT the pvs command gives me the following: PV VG Fmt Attr PSize PFree /dev/sda3 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 a- 2.72T 2.62T the vgs command gives me the following: VG #PV #LV #SN Attr VSize VFree VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 1 3 0 wz--n- 2.72T 2.62T the lvs command gives me the following: LV VG Attr LSize Origin Snap% Move Log Copy% Convert MGT VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- 4.00M VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 8.02G iso VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G the mount command gives me the following: /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:16:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:16: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 1SaNxP-0004m9-Ju; Fri, 01 Jun 2012 09:15:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNxN-0004m4-NG for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:15:41 +0000 Received: from [85.158.143.35:16591] by server-1.bemta-4.messagelabs.com id 30/48-27869-D3888CF4; Fri, 01 Jun 2012 09:15:41 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1338542138!17081852!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7161 invoked from network); 1 Jun 2012 09:15:39 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:15:39 -0000 Received: by obbwd20 with SMTP id wd20so3409617obb.32 for ; Fri, 01 Jun 2012 02:15:18 -0700 (PDT) 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=0tvDHjRA6rWgRdq/EjinNqyh/HWPHITumQXgGjZMaqY=; b=kl6Zm18oXhCduqL/XSU8Eo2tuvLNW7SUopW7JPoBGiUkyHROkUg06ON+BmpdyaRtAL JUh0cYmjPwdcGO2zvNrwXrSzj9xU/x0DMQzdmFbA46kG87dVxc7qTq1Y+UfgrG88SuF+ 7suuQ/qtq3K5kHVcodHEkkr8dyiBJ8TKkHFPUW/50Icro4nUMzgxxE+6R4qdUXxvMaQl vp1PqdJ7jBtKYH7pCBc5EJPk/Hn2JFwsZX8YfCNuZHeCI+Rjhr6c8eNbbcDpn787BNeW o3fgE599lVPM8KoTPk6c9BjqDiS2Hi+oFvWmTZRVW1jn7aOV4iHQRUGg5neuI3BvECXe 6grQ== MIME-Version: 1.0 Received: by 10.60.3.202 with SMTP id e10mr1736639oee.52.1338542118824; Fri, 01 Jun 2012 02:15:18 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 02:15:18 -0700 (PDT) Date: Fri, 1 Jun 2012 05:15:18 -0400 Message-ID: From: Jane Wayne To: xen-users@lists.xen.org Subject: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org i've installed XCP 1.5-beta. i'm a little confused as to what has happened. everything so far seems to work. however, i need more information on what was done to my hard disk during the installation and how was the file system set up. in particular, i was investigating how to create a new logical volume to place my ISO file to use as my ISO storage (SR). i notice (see below with lvs command) that something like this was already created automatically, BUT, it was not mounted anywhere. i was wondering why this artifact logical volume was created and not mounted? i have a 3 TB hard disk. when i issue: fdisk -l, i get the following output. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). DOS partition table format can not be used on drives for volumes larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID partition table format (GPT). Disk /dev/sda: 3000.5 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 266306 2147483647+ ee EFI GPT the pvs command gives me the following: PV VG Fmt Attr PSize PFree /dev/sda3 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 a- 2.72T 2.62T the vgs command gives me the following: VG #PV #LV #SN Attr VSize VFree VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 1 3 0 wz--n- 2.72T 2.62T the lvs command gives me the following: LV VG Attr LSize Origin Snap% Move Log Copy% Convert MGT VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- 4.00M VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 8.02G iso VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G the mount command gives me the following: /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:19:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:19:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNzw-0004ti-Ql; Fri, 01 Jun 2012 09:18:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNzv-0004tT-8e for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:18:19 +0000 Received: from [85.158.139.83:63317] by server-10.bemta-5.messagelabs.com id 04/14-22179-AD888CF4; Fri, 01 Jun 2012 09:18:18 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1338542294!27258182!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2005 invoked from network); 1 Jun 2012 09:18:16 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:18:16 -0000 Received: by obbwd20 with SMTP id wd20so3413857obb.32 for ; Fri, 01 Jun 2012 02:18:13 -0700 (PDT) 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=o0FbpGcXFzIXx3dHwT+g8WYAA9ajS4cbrgf7rqTzZcI=; b=oI2Nm6FxbSaJlRdYzdi1ayGNSfIAI/YzENChLNAhVa1kzhop2VovOgoqvW6kNGz0le D0x7K7WxAdQA9aOZw8V5HnX98AO8O/rhXRsud9H6EL81cD1MezHI7mM6EFAhFrwHYygo q3P0zc89vkjJZ2yY9dEW+v/ROWOBj++8aSl9/9bxvSTB1raJSwa0/dr21t9tsc+0Trq/ zRohB/WAJsrxbus0y3Jg2xfKN8kkjHMQom7uAk9GjrxsBzT9sa7imTJTSTyagjPORvcS Xo/8w5r/iNd+s0j1Ayhu3fusSJ0c/oJw+QectDuFv3/6l1NciOkRmgGswDHa7wNuhDEE YEgA== MIME-Version: 1.0 Received: by 10.182.145.4 with SMTP id sq4mr1664550obb.76.1338542293793; Fri, 01 Jun 2012 02:18:13 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 02:18:13 -0700 (PDT) Date: Fri, 1 Jun 2012 05:18:13 -0400 Message-ID: From: Jane Wayne To: xen-users@lists.xen.org Subject: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org i am investigating what the XCP installation process did to my hard drive. when i issue: fdisk -l, i get the following output. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). DOS partition table format can not be used on drives for volumes larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID partition table format (GPT). Disk /dev/sda: 3000.5 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 266306 2147483647+ ee EFI GPT as such, i wanted to run the "parted" command. however, running this command says "command not found." i tried to install the parted utility: yum install parted but the output was Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process No package parted available. Nothing to do what's going on here? what do i have to modify in /etc/yum.repos.d/* if anything? any help is appreciated. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:19:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:19:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNzw-0004ti-Ql; Fri, 01 Jun 2012 09:18:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaNzv-0004tT-8e for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:18:19 +0000 Received: from [85.158.139.83:63317] by server-10.bemta-5.messagelabs.com id 04/14-22179-AD888CF4; Fri, 01 Jun 2012 09:18:18 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1338542294!27258182!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2005 invoked from network); 1 Jun 2012 09:18:16 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:18:16 -0000 Received: by obbwd20 with SMTP id wd20so3413857obb.32 for ; Fri, 01 Jun 2012 02:18:13 -0700 (PDT) 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=o0FbpGcXFzIXx3dHwT+g8WYAA9ajS4cbrgf7rqTzZcI=; b=oI2Nm6FxbSaJlRdYzdi1ayGNSfIAI/YzENChLNAhVa1kzhop2VovOgoqvW6kNGz0le D0x7K7WxAdQA9aOZw8V5HnX98AO8O/rhXRsud9H6EL81cD1MezHI7mM6EFAhFrwHYygo q3P0zc89vkjJZ2yY9dEW+v/ROWOBj++8aSl9/9bxvSTB1raJSwa0/dr21t9tsc+0Trq/ zRohB/WAJsrxbus0y3Jg2xfKN8kkjHMQom7uAk9GjrxsBzT9sa7imTJTSTyagjPORvcS Xo/8w5r/iNd+s0j1Ayhu3fusSJ0c/oJw+QectDuFv3/6l1NciOkRmgGswDHa7wNuhDEE YEgA== MIME-Version: 1.0 Received: by 10.182.145.4 with SMTP id sq4mr1664550obb.76.1338542293793; Fri, 01 Jun 2012 02:18:13 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 02:18:13 -0700 (PDT) Date: Fri, 1 Jun 2012 05:18:13 -0400 Message-ID: From: Jane Wayne To: xen-users@lists.xen.org Subject: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org i am investigating what the XCP installation process did to my hard drive. when i issue: fdisk -l, i get the following output. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). DOS partition table format can not be used on drives for volumes larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID partition table format (GPT). Disk /dev/sda: 3000.5 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 266306 2147483647+ ee EFI GPT as such, i wanted to run the "parted" command. however, running this command says "command not found." i tried to install the parted utility: yum install parted but the output was Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process No package parted available. Nothing to do what's going on here? what do i have to modify in /etc/yum.repos.d/* if anything? any help is appreciated. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:31:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:31: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 1SaOC5-0005tV-BJ; Fri, 01 Jun 2012 09:30:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOC3-0005tJ-Km for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:30:51 +0000 Received: from [85.158.143.35:31920] by server-3.bemta-4.messagelabs.com id FE/D6-04252-ACB88CF4; Fri, 01 Jun 2012 09:30:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1338543047!16054157!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11063 invoked from network); 1 Jun 2012 09:30:48 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:30:48 -0000 X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12781901" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Jun 2012 09:30:47 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012 10:30:47 +0100 Message-ID: <1338543045.17466.47.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jane Wayne Date: Fri, 1 Jun 2012 10:30:45 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Jane, Both this and the other question you sent are more likely to get answers on the xen-api@ list where most XCP discussion happens (not an obvious name, I agree, steps are under way to clarify this!) Ian. On Fri, 2012-06-01 at 10:15 +0100, Jane Wayne wrote: > i've installed XCP 1.5-beta. i'm a little confused as to what has > happened. everything so far seems to work. however, i need more > information on what was done to my hard disk during the installation > and how was the file system set up. > > in particular, i was investigating how to create a new logical volume > to place my ISO file to use as my ISO storage (SR). i notice (see > below with lvs command) that something like this was already created > automatically, BUT, it was not mounted anywhere. i was wondering why > this artifact logical volume was created and not mounted? > > i have a 3 TB hard disk. when i issue: fdisk -l, i get the following output. > > WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util > fdisk doesn't support GPT. Use GNU Parted. > WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). > DOS partition table format can not be used on drives for volumes > larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID > partition table format (GPT). > Disk /dev/sda: 3000.5 GB, 3000592982016 bytes > 256 heads, 63 sectors/track, 363376 cylinders > Units = cylinders of 16128 * 512 = 8257536 bytes > Device Boot Start End Blocks Id System > /dev/sda1 * 1 266306 2147483647+ ee EFI GPT > > the pvs command gives me the following: > > PV VG Fmt > Attr PSize PFree > /dev/sda3 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 > a- 2.72T 2.62T > > the vgs command gives me the following: > > VG #PV #LV #SN Attr > VSize VFree > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 1 3 0 > wz--n- 2.72T 2.62T > > the lvs command gives me the following: > > LV VG > Attr LSize Origin Snap% Move Log Copy% > Convert > MGT > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- 4.00M > VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 8.02G > iso > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G > > the mount command gives me the following: > > /dev/sda1 on / type ext3 (rw) > none on /proc type proc (rw) > none on /sys type sysfs (rw) > none on /dev/pts type devpts (rw) > none on /dev/shm type tmpfs (rw) > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:31:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:31: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 1SaOC5-0005tV-BJ; Fri, 01 Jun 2012 09:30:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOC3-0005tJ-Km for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:30:51 +0000 Received: from [85.158.143.35:31920] by server-3.bemta-4.messagelabs.com id FE/D6-04252-ACB88CF4; Fri, 01 Jun 2012 09:30:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1338543047!16054157!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11063 invoked from network); 1 Jun 2012 09:30:48 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:30:48 -0000 X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12781901" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Jun 2012 09:30:47 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012 10:30:47 +0100 Message-ID: <1338543045.17466.47.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jane Wayne Date: Fri, 1 Jun 2012 10:30:45 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Jane, Both this and the other question you sent are more likely to get answers on the xen-api@ list where most XCP discussion happens (not an obvious name, I agree, steps are under way to clarify this!) Ian. On Fri, 2012-06-01 at 10:15 +0100, Jane Wayne wrote: > i've installed XCP 1.5-beta. i'm a little confused as to what has > happened. everything so far seems to work. however, i need more > information on what was done to my hard disk during the installation > and how was the file system set up. > > in particular, i was investigating how to create a new logical volume > to place my ISO file to use as my ISO storage (SR). i notice (see > below with lvs command) that something like this was already created > automatically, BUT, it was not mounted anywhere. i was wondering why > this artifact logical volume was created and not mounted? > > i have a 3 TB hard disk. when i issue: fdisk -l, i get the following output. > > WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util > fdisk doesn't support GPT. Use GNU Parted. > WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). > DOS partition table format can not be used on drives for volumes > larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID > partition table format (GPT). > Disk /dev/sda: 3000.5 GB, 3000592982016 bytes > 256 heads, 63 sectors/track, 363376 cylinders > Units = cylinders of 16128 * 512 = 8257536 bytes > Device Boot Start End Blocks Id System > /dev/sda1 * 1 266306 2147483647+ ee EFI GPT > > the pvs command gives me the following: > > PV VG Fmt > Attr PSize PFree > /dev/sda3 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 > a- 2.72T 2.62T > > the vgs command gives me the following: > > VG #PV #LV #SN Attr > VSize VFree > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 1 3 0 > wz--n- 2.72T 2.62T > > the lvs command gives me the following: > > LV VG > Attr LSize Origin Snap% Move Log Copy% > Convert > MGT > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- 4.00M > VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 8.02G > iso > VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G > > the mount command gives me the following: > > /dev/sda1 on / type ext3 (rw) > none on /proc type proc (rw) > none on /sys type sysfs (rw) > none on /dev/pts type devpts (rw) > none on /dev/shm type tmpfs (rw) > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:54:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:54:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOYK-0007iy-G3; Fri, 01 Jun 2012 09:53:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOYI-0007is-TB for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:53:51 +0000 Received: from [85.158.139.83:49335] by server-12.bemta-5.messagelabs.com id 6F/12-18374-E2198CF4; Fri, 01 Jun 2012 09:53:50 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1338544427!31856459!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4250 invoked from network); 1 Jun 2012 09:53:49 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:53:49 -0000 Received: by pbbro12 with SMTP id ro12so2906504pbb.32 for ; Fri, 01 Jun 2012 02:53:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=O+5tlsqRs30Ewr+C09mXPSlU2/FMhd77rOGjv+LtjEo=; b=IKZQ1BHJYTRZnDKDRTut6OEwicu9nQh6ytXxW8iKO3+CzakoDzIre2tNniIq20VZUh 1hq9RUcXOLct7R7olpeWqtdKRyTngZGaKZ9j44pqj65Mdhnffc6QXSewPxR2ZLvpmp6H KxzMOZdCPtQ5wxHo/zQoDNkG6bIQ6e0y38x2DpgS1w1wto4YvXBJemnEI3DWUAfrMy4+ sLS2aHOueUjJjOXWIttYqi8Eo3CFScrfuQEwVW6IekYKTMgN7hWG0tzEVDhs19LhvVHt AD/B63pf9Q3Ubj1XFhZzKYPvxvzBKOGZN4+fQnurAwZuOLE9eOWRWWAXGgX4eE/QcDcM yvOg== MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr5457418pbc.61.1338544427427; Fri, 01 Jun 2012 02:53:47 -0700 (PDT) Received: by 10.68.209.1 with HTTP; Fri, 1 Jun 2012 02:53:47 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Jun 2012 16:53:47 +0700 Message-ID: From: "Fajar A. Nugraha" To: Jane Wayne X-Gm-Message-State: ALoCoQlMojwZ2n8pV4lHwM3CsUadlKI7hjHZYuon/6SvyZN5+HPSHYfzstS7ZDDqFtKHB8Ma64v3 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Jun 1, 2012 at 4:18 PM, Jane Wayne wrote: > as such, i wanted to run the "parted" command. however, running this > command says "command not found." i tried to install the parted > utility: > > yum install parted > > but the output was > > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > Setting up Install Process > No package parted available. > Nothing to do That is expected behaviour > > what's going on here? what do i have to modify in /etc/yum.repos.d/* > if anything? Nothing. You're not supposed to install anything on XCP. Forcing to do so is unsupported, and might break the system. Think vmware vsphere hypervisor. Treat XCP the same way. While XCP userland is 90-something-percent centos, some packages are modified to be specific to XCP. Had centos repo been enabled, those packages would be overwritten with, making xcp stop working. So to be safe, the repositories are disabled. If you understand the risks and consequences, and pretty sure you want to do it anyway, you could create your own repo file (or probably just enable existing ones) temporarily. Or just download and copy the RPMS manually (there should only be several needed for parted and its dependencies). Don't complain if anything breaks though. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 09:54:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 09:54:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOYK-0007iy-G3; Fri, 01 Jun 2012 09:53:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOYI-0007is-TB for xen-users@lists.xen.org; Fri, 01 Jun 2012 09:53:51 +0000 Received: from [85.158.139.83:49335] by server-12.bemta-5.messagelabs.com id 6F/12-18374-E2198CF4; Fri, 01 Jun 2012 09:53:50 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1338544427!31856459!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4250 invoked from network); 1 Jun 2012 09:53:49 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 09:53:49 -0000 Received: by pbbro12 with SMTP id ro12so2906504pbb.32 for ; Fri, 01 Jun 2012 02:53:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=O+5tlsqRs30Ewr+C09mXPSlU2/FMhd77rOGjv+LtjEo=; b=IKZQ1BHJYTRZnDKDRTut6OEwicu9nQh6ytXxW8iKO3+CzakoDzIre2tNniIq20VZUh 1hq9RUcXOLct7R7olpeWqtdKRyTngZGaKZ9j44pqj65Mdhnffc6QXSewPxR2ZLvpmp6H KxzMOZdCPtQ5wxHo/zQoDNkG6bIQ6e0y38x2DpgS1w1wto4YvXBJemnEI3DWUAfrMy4+ sLS2aHOueUjJjOXWIttYqi8Eo3CFScrfuQEwVW6IekYKTMgN7hWG0tzEVDhs19LhvVHt AD/B63pf9Q3Ubj1XFhZzKYPvxvzBKOGZN4+fQnurAwZuOLE9eOWRWWAXGgX4eE/QcDcM yvOg== MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr5457418pbc.61.1338544427427; Fri, 01 Jun 2012 02:53:47 -0700 (PDT) Received: by 10.68.209.1 with HTTP; Fri, 1 Jun 2012 02:53:47 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Jun 2012 16:53:47 +0700 Message-ID: From: "Fajar A. Nugraha" To: Jane Wayne X-Gm-Message-State: ALoCoQlMojwZ2n8pV4lHwM3CsUadlKI7hjHZYuon/6SvyZN5+HPSHYfzstS7ZDDqFtKHB8Ma64v3 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Jun 1, 2012 at 4:18 PM, Jane Wayne wrote: > as such, i wanted to run the "parted" command. however, running this > command says "command not found." i tried to install the parted > utility: > > yum install parted > > but the output was > > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > Setting up Install Process > No package parted available. > Nothing to do That is expected behaviour > > what's going on here? what do i have to modify in /etc/yum.repos.d/* > if anything? Nothing. You're not supposed to install anything on XCP. Forcing to do so is unsupported, and might break the system. Think vmware vsphere hypervisor. Treat XCP the same way. While XCP userland is 90-something-percent centos, some packages are modified to be specific to XCP. Had centos repo been enabled, those packages would be overwritten with, making xcp stop working. So to be safe, the repositories are disabled. If you understand the risks and consequences, and pretty sure you want to do it anyway, you could create your own repo file (or probably just enable existing ones) temporarily. Or just download and copy the RPMS manually (there should only be several needed for parted and its dependencies). Don't complain if anything breaks though. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 10:20:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:20: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 1SaOxA-0000Tc-VT; Fri, 01 Jun 2012 10:19:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOx9-0000T7-2k for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:19:31 +0000 Received: from [193.109.254.147:15104] by server-4.bemta-14.messagelabs.com id ED/E7-03148-13798CF4; Fri, 01 Jun 2012 10:19:29 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1338545967!12144200!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10696 invoked from network); 1 Jun 2012 10:19:28 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:19:28 -0000 Received: by eekd41 with SMTP id d41so906638eek.32 for ; Fri, 01 Jun 2012 03:19:27 -0700 (PDT) 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; bh=8uOP5xsUONlrGN/vzHDkvmqAGPNy/l+BTPiVktyxf8w=; b=XdglF9Aq3Synog8YsAu65g47kxgRsmf+PtVj5ESLVHDrYMN94b9xV1ONW84ghxLJWx tGvrFxY3MxvRhZolWuOI3N9lqKC5FXtxi1hogmvlbLCrU7qFUouRWXGJjC79tG8xe+oZ MG9RrwzqsG7g/phsPym0sSYk0qaEvoGKUKwO4UNZ2QaQc4hFKtIOVCKgqmIpSAoeC/nD yUkn5TJAwzL10Hf165imkLvUWaz5RU6Ws3Lf/nPJimYpx3m8ivJEk1YdlyjGFDZXskcZ sZXj6S4oKG5kKG68olmX9m3cvOlH853IKSy2GVMcsxCw8DK2X/SyGjVRioRJX+OZdoLn TUEA== Received: by 10.14.97.77 with SMTP id s53mr1032470eef.104.1338545967713; Fri, 01 Jun 2012 03:19:27 -0700 (PDT) Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233]) by mx.google.com with ESMTPS id u7sm5281597eeb.7.2012.06.01.03.19.25 (version=SSLv3 cipher=OTHER); Fri, 01 Jun 2012 03:19:26 -0700 (PDT) Message-ID: <4FC8972B.6060202@xen.org> Date: Fri, 01 Jun 2012 11:19:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-users@lists.xen.org, "xen-api@lists.xen.org" Subject: [Xen-users] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8659113957222467060==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8659113957222467060== Content-Type: multipart/alternative; boundary="------------010702070000020506000500" This is a multi-part message in MIME format. --------------010702070000020506000500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, at the last Xen Docs Day I got feedback that it is too hard to find useful information from the wiki front page. Also, much of the information on the front page (the list of categories) is actually duplicated on the wiki navigation bar. There were a few items of feedback I received: 1) The front page should be more use-case driven and be aimed at beginners and users 2) Wiki Search is broken. - Actually it is not, the UI design of search in MediaWiki is bad. - Typing "Foo"+return into the search box will actually perform Go(Foo) which searches for "Foo" in titles only - To search you need to type "Foo" and press search 3) Google search is broken. - Some redirects are still needed but mostly we have fixed this now. - The ones we know of are: (e.g. wiki.*xen*source.com is still hanging around) - If you find SEO issues: let us know at http://wiki.xen.org/wiki/SEO_Issues To facilitate the discussion on the new front-page, I created a proposal space for everybody to play with and make proposals - http://wiki.xen.org/wiki/Proposals/ : list of proposals - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed front-page - http://wiki.xen.org/wiki/Talk:Proposals/Main_Page1 : discussion page, feel free to add - http://wiki.xen.org/wiki/Proposals/Main_Page2 : a copy of the previous page, feel free to change - http://wiki.xen.org/wiki/Talk:Proposals/Main_Page2 : discussion page, feel free to add Feel free to add new proposals Best Regards Lars --------------010702070000020506000500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

at the last Xen Docs Day I got feedback that it is too hard to find useful information from the wiki front page. Also, much of the information on the front page (the list of categories) is actually duplicated on the wiki navigation bar.

There were a few items of feedback I received:
1) The front page should be more use-case driven and be aimed at beginners and users
2) Wiki Search is broken.
- Actually it is not, the UI design of search in MediaWiki is bad. 
- Typing "Foo"+return into the search box will actually perform Go(Foo) which searches for "Foo" in titles only
- To search you need to type "Foo" and press search
3) Google search is broken.
- Some redirects are still needed but mostly we have fixed this now.
- The ones we know of are: (e.g. wiki.xensource.com is still hanging around)
- If you find SEO issues: let us know at http://wiki.xen.org/wiki/SEO_Issues

To facilitate the discussion on the new front-page, I created a proposal space for everybody to play with and make proposals
- http://wiki.xen.org/wiki/Proposals/ : list of proposals
- http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed front-page
- http://wiki.xen.org/wiki/Talk:Proposals/Main_Page1 : discussion page, feel free to add
- http://wiki.xen.org/wiki/Proposals/Main_Page2 : a copy of the previous page, feel free to change
- http://wiki.xen.org/wiki/Talk:Proposals/Main_Page2 : discussion page, feel free to add

Feel free to add new proposals

Best Regards
Lars
--------------010702070000020506000500-- --===============8659113957222467060== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8659113957222467060==-- From xen-users-bounces@lists.xen.org Fri Jun 01 10:20:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:20: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 1SaOxA-0000Tc-VT; Fri, 01 Jun 2012 10:19:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaOx9-0000T7-2k for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:19:31 +0000 Received: from [193.109.254.147:15104] by server-4.bemta-14.messagelabs.com id ED/E7-03148-13798CF4; Fri, 01 Jun 2012 10:19:29 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1338545967!12144200!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10696 invoked from network); 1 Jun 2012 10:19:28 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:19:28 -0000 Received: by eekd41 with SMTP id d41so906638eek.32 for ; Fri, 01 Jun 2012 03:19:27 -0700 (PDT) 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; bh=8uOP5xsUONlrGN/vzHDkvmqAGPNy/l+BTPiVktyxf8w=; b=XdglF9Aq3Synog8YsAu65g47kxgRsmf+PtVj5ESLVHDrYMN94b9xV1ONW84ghxLJWx tGvrFxY3MxvRhZolWuOI3N9lqKC5FXtxi1hogmvlbLCrU7qFUouRWXGJjC79tG8xe+oZ MG9RrwzqsG7g/phsPym0sSYk0qaEvoGKUKwO4UNZ2QaQc4hFKtIOVCKgqmIpSAoeC/nD yUkn5TJAwzL10Hf165imkLvUWaz5RU6Ws3Lf/nPJimYpx3m8ivJEk1YdlyjGFDZXskcZ sZXj6S4oKG5kKG68olmX9m3cvOlH853IKSy2GVMcsxCw8DK2X/SyGjVRioRJX+OZdoLn TUEA== Received: by 10.14.97.77 with SMTP id s53mr1032470eef.104.1338545967713; Fri, 01 Jun 2012 03:19:27 -0700 (PDT) Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233]) by mx.google.com with ESMTPS id u7sm5281597eeb.7.2012.06.01.03.19.25 (version=SSLv3 cipher=OTHER); Fri, 01 Jun 2012 03:19:26 -0700 (PDT) Message-ID: <4FC8972B.6060202@xen.org> Date: Fri, 01 Jun 2012 11:19:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-users@lists.xen.org, "xen-api@lists.xen.org" Subject: [Xen-users] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8659113957222467060==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8659113957222467060== Content-Type: multipart/alternative; boundary="------------010702070000020506000500" This is a multi-part message in MIME format. --------------010702070000020506000500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, at the last Xen Docs Day I got feedback that it is too hard to find useful information from the wiki front page. Also, much of the information on the front page (the list of categories) is actually duplicated on the wiki navigation bar. There were a few items of feedback I received: 1) The front page should be more use-case driven and be aimed at beginners and users 2) Wiki Search is broken. - Actually it is not, the UI design of search in MediaWiki is bad. - Typing "Foo"+return into the search box will actually perform Go(Foo) which searches for "Foo" in titles only - To search you need to type "Foo" and press search 3) Google search is broken. - Some redirects are still needed but mostly we have fixed this now. - The ones we know of are: (e.g. wiki.*xen*source.com is still hanging around) - If you find SEO issues: let us know at http://wiki.xen.org/wiki/SEO_Issues To facilitate the discussion on the new front-page, I created a proposal space for everybody to play with and make proposals - http://wiki.xen.org/wiki/Proposals/ : list of proposals - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed front-page - http://wiki.xen.org/wiki/Talk:Proposals/Main_Page1 : discussion page, feel free to add - http://wiki.xen.org/wiki/Proposals/Main_Page2 : a copy of the previous page, feel free to change - http://wiki.xen.org/wiki/Talk:Proposals/Main_Page2 : discussion page, feel free to add Feel free to add new proposals Best Regards Lars --------------010702070000020506000500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

at the last Xen Docs Day I got feedback that it is too hard to find useful information from the wiki front page. Also, much of the information on the front page (the list of categories) is actually duplicated on the wiki navigation bar.

There were a few items of feedback I received:
1) The front page should be more use-case driven and be aimed at beginners and users
2) Wiki Search is broken.
- Actually it is not, the UI design of search in MediaWiki is bad. 
- Typing "Foo"+return into the search box will actually perform Go(Foo) which searches for "Foo" in titles only
- To search you need to type "Foo" and press search
3) Google search is broken.
- Some redirects are still needed but mostly we have fixed this now.
- The ones we know of are: (e.g. wiki.xensource.com is still hanging around)
- If you find SEO issues: let us know at http://wiki.xen.org/wiki/SEO_Issues

To facilitate the discussion on the new front-page, I created a proposal space for everybody to play with and make proposals
- http://wiki.xen.org/wiki/Proposals/ : list of proposals
- http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed front-page
- http://wiki.xen.org/wiki/Talk:Proposals/Main_Page1 : discussion page, feel free to add
- http://wiki.xen.org/wiki/Proposals/Main_Page2 : a copy of the previous page, feel free to change
- http://wiki.xen.org/wiki/Talk:Proposals/Main_Page2 : discussion page, feel free to add

Feel free to add new proposals

Best Regards
Lars
--------------010702070000020506000500-- --===============8659113957222467060== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8659113957222467060==-- From xen-users-bounces@lists.xen.org Fri Jun 01 10:54:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:54:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUE-0003BD-Ie; Fri, 01 Jun 2012 10:53:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUC-0003Ay-WD for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:53:41 +0000 Received: from [85.158.143.99:37522] by server-1.bemta-4.messagelabs.com id 78/D2-27869-43F98CF4; Fri, 01 Jun 2012 10:53:40 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1338548016!28572135!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27140 invoked from network); 1 Jun 2012 10:53:38 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:53:38 -0000 Received: by obbwd20 with SMTP id wd20so3557193obb.32 for ; Fri, 01 Jun 2012 03:53:35 -0700 (PDT) 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=DnLi5/Lrs72x+s5DraIjzVWHboh4QgN4MdogVpSwZ1g=; b=CwM4ncvGQILsNFxN2ufSmpGskZGQBxEDMUDHVawT/7BZrWxRQOG4IQXFd0G7Slnoye CHczB4Xv3dAVceEj4n0/OubkkyRLrz6vtMbcxrOOWhdBVD6FnYNsuJWtF/XJc8M4TjKd Y8KfEtk5SMFamaI5Rykp2czF0UBMb9g/OwBFqHdsRYIAUnhzBBQSKVdHD8v/nIQpMRsq gKmqHFUEeq94TBUZ91S41EubopYRXxNGY6XJvCBBsVerwKZ7YsLYyHfaczAdTOl7BQMm J1BjsBr73l3EfBFGuLpuSVnJ7J8PD897Aj/qV/04jAkgp98G92th03oBDd2BBmCPKiXB +P1Q== MIME-Version: 1.0 Received: by 10.182.2.193 with SMTP id 1mr2111250obw.46.1338548015407; Fri, 01 Jun 2012 03:53:35 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 03:53:35 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Jun 2012 06:53:35 -0400 Message-ID: From: Jane Wayne To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Fajar, thanks. if that behavior is intentional, then i'll accept that. also, thanks for the pointer of "forcing" the install. that really helps if decide to tinker some more. On Fri, Jun 1, 2012 at 5:53 AM, Fajar A. Nugraha wrote: > On Fri, Jun 1, 2012 at 4:18 PM, Jane Wayne wrote: > >> as such, i wanted to run the "parted" command. however, running this >> command says "command not found." i tried to install the parted >> utility: >> >> yum install parted >> >> but the output was >> >> Loaded plugins: fastestmirror >> Loading mirror speeds from cached hostfile >> Setting up Install Process >> No package parted available. >> Nothing to do > > That is expected behaviour > >> >> what's going on here? what do i have to modify in /etc/yum.repos.d/* >> if anything? > > Nothing. You're not supposed to install anything on XCP. Forcing to do > so is unsupported, and might break the system. > > Think vmware vsphere hypervisor. Treat XCP the same way. > > While XCP userland is 90-something-percent centos, some packages are > modified to be specific to XCP. Had centos repo been enabled, those > packages would be overwritten with, making xcp stop working. So to be > safe, the repositories are disabled. > > If you understand the risks and consequences, and pretty sure you want > to do it anyway, you could create your own repo file (or probably just > enable existing ones) temporarily. Or just download and copy the RPMS > manually (there should only be several needed for parted and its > dependencies). > > Don't complain if anything breaks though. > > -- > Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 10:54:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:54:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUE-0003BD-Ie; Fri, 01 Jun 2012 10:53:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUC-0003Ay-WD for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:53:41 +0000 Received: from [85.158.143.99:37522] by server-1.bemta-4.messagelabs.com id 78/D2-27869-43F98CF4; Fri, 01 Jun 2012 10:53:40 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1338548016!28572135!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27140 invoked from network); 1 Jun 2012 10:53:38 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:53:38 -0000 Received: by obbwd20 with SMTP id wd20so3557193obb.32 for ; Fri, 01 Jun 2012 03:53:35 -0700 (PDT) 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=DnLi5/Lrs72x+s5DraIjzVWHboh4QgN4MdogVpSwZ1g=; b=CwM4ncvGQILsNFxN2ufSmpGskZGQBxEDMUDHVawT/7BZrWxRQOG4IQXFd0G7Slnoye CHczB4Xv3dAVceEj4n0/OubkkyRLrz6vtMbcxrOOWhdBVD6FnYNsuJWtF/XJc8M4TjKd Y8KfEtk5SMFamaI5Rykp2czF0UBMb9g/OwBFqHdsRYIAUnhzBBQSKVdHD8v/nIQpMRsq gKmqHFUEeq94TBUZ91S41EubopYRXxNGY6XJvCBBsVerwKZ7YsLYyHfaczAdTOl7BQMm J1BjsBr73l3EfBFGuLpuSVnJ7J8PD897Aj/qV/04jAkgp98G92th03oBDd2BBmCPKiXB +P1Q== MIME-Version: 1.0 Received: by 10.182.2.193 with SMTP id 1mr2111250obw.46.1338548015407; Fri, 01 Jun 2012 03:53:35 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 03:53:35 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Jun 2012 06:53:35 -0400 Message-ID: From: Jane Wayne To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] why can't i install parted on CentOS distributed with XCP ISO binary? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Fajar, thanks. if that behavior is intentional, then i'll accept that. also, thanks for the pointer of "forcing" the install. that really helps if decide to tinker some more. On Fri, Jun 1, 2012 at 5:53 AM, Fajar A. Nugraha wrote: > On Fri, Jun 1, 2012 at 4:18 PM, Jane Wayne wrote: > >> as such, i wanted to run the "parted" command. however, running this >> command says "command not found." i tried to install the parted >> utility: >> >> yum install parted >> >> but the output was >> >> Loaded plugins: fastestmirror >> Loading mirror speeds from cached hostfile >> Setting up Install Process >> No package parted available. >> Nothing to do > > That is expected behaviour > >> >> what's going on here? what do i have to modify in /etc/yum.repos.d/* >> if anything? > > Nothing. You're not supposed to install anything on XCP. Forcing to do > so is unsupported, and might break the system. > > Think vmware vsphere hypervisor. Treat XCP the same way. > > While XCP userland is 90-something-percent centos, some packages are > modified to be specific to XCP. Had centos repo been enabled, those > packages would be overwritten with, making xcp stop working. So to be > safe, the repositories are disabled. > > If you understand the risks and consequences, and pretty sure you want > to do it anyway, you could create your own repo file (or probably just > enable existing ones) temporarily. Or just download and copy the RPMS > manually (there should only be several needed for parted and its > dependencies). > > Don't complain if anything breaks though. > > -- > Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 10:55:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:55:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUv-0003Fm-8N; Fri, 01 Jun 2012 10:54:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUt-0003FU-R2 for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:54:24 +0000 Received: from [85.158.138.51:42541] by server-4.bemta-3.messagelabs.com id F9/EB-32504-E5F98CF4; Fri, 01 Jun 2012 10:54:22 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1338548060!30353175!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4536 invoked from network); 1 Jun 2012 10:54:22 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:54:22 -0000 Received: by obbwd20 with SMTP id wd20so3558221obb.32 for ; Fri, 01 Jun 2012 03:54:20 -0700 (PDT) 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:content-transfer-encoding; bh=RhCEIg29d+zPImL0WvJKuIIhnv1zYcgghiwRdb3THHs=; b=cuH07XbcBKKD4+iW0rSpkTbgJ3gHHvHQ0vDNkE7GzY5zDqhFyI8OwuPJfNYkxFPy6W Wmkmy5arxoLvY5N9zvMZXuW0eaQl4oKlWR6M52bIKwPn6Cf7gg/E//okngL1hw9yN2aG NngTKx309TmaG/Rt1UmboPQP7D17FGq6G9AQQdgm968X8EAFBJxo6Ew+EDDIKC1c3IxA Y9Ne7UwjfNuW8Myv34LLOZx06hakao0MxmVQbOWxe6M4IC2d7iiRF6kxci/XCCcNC6kI 9rvaIrp2qlePd5qy0JHb6HWGWEHgbsrrHG+NawvQrvOhPwgnGXeFQEQGdcauHhdK+3VV LGwA== MIME-Version: 1.0 Received: by 10.182.212.4 with SMTP id ng4mr2178698obc.20.1338548060308; Fri, 01 Jun 2012 03:54:20 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 03:54:20 -0700 (PDT) In-Reply-To: <1338543045.17466.47.camel@zakaz.uk.xensource.com> References: <1338543045.17466.47.camel@zakaz.uk.xensource.com> Date: Fri, 1 Jun 2012 06:54:20 -0400 Message-ID: From: Jane Wayne To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org thanks ian, i've posted on the other list. On Fri, Jun 1, 2012 at 5:30 AM, Ian Campbell wrot= e: > Hi Jane, > > Both this and the other question you sent are more likely to get answers > on the xen-api@ list where most XCP discussion happens (not an obvious > name, I agree, steps are under way to clarify this!) > > Ian. > > On Fri, 2012-06-01 at 10:15 +0100, Jane Wayne wrote: >> i've installed XCP 1.5-beta. i'm a little confused as to what has >> happened. everything so far seems to work. however, i need more >> information on what was done to my hard disk during the installation >> and how was the file system set up. >> >> in particular, i was investigating how to create a new logical volume >> to place my ISO file to use as my ISO storage (SR). i notice (see >> below with lvs command) that something like this was already created >> automatically, BUT, it was not mounted anywhere. i was wondering why >> this artifact logical volume was created and not mounted? >> >> i have a 3 TB hard disk. when i issue: fdisk -l, i get the following out= put. >> >> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util >> fdisk doesn't support GPT. Use GNU Parted. >> WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). >> DOS partition table format can not be used on drives for volumes >> larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID >> partition table format (GPT). >> Disk /dev/sda: 3000.5 GB, 3000592982016 bytes >> 256 heads, 63 sectors/track, 363376 cylinders >> Units =3D cylinders of 16128 * 512 =3D 8257536 bytes >> =A0 =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Block= s =A0 Id =A0System >> /dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0266306 =A02147483647+ = =A0ee =A0EFI GPT >> >> the pvs command gives me the following: >> >> =A0 PV =A0 =A0 =A0 =A0 VG =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Fmt >> Attr PSize PFree >> =A0 /dev/sda3 =A0VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 >> a- =A0 2.72T 2.62T >> >> the vgs command gives me the following: >> >> =A0 VG =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #PV #LV #SN Attr >> =A0VSize VFree >> =A0 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 =A0 1 =A0 3 =A0 0 >> wz--n- 2.72T 2.62T >> >> the lvs command gives me the following: >> >> =A0 LV =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 VG >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Attr =A0 LSize =A0 Origin= Snap% =A0Move Log Copy% >> Convert >> =A0 MGT >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- =A0 4.00M >> =A0 VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- =A0 8.02G >> =A0 iso >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G >> >> the mount command gives me the following: >> >> /dev/sda1 on / type ext3 (rw) >> none on /proc type proc (rw) >> none on /sys type sysfs (rw) >> none on /dev/pts type devpts (rw) >> none on /dev/shm type tmpfs (rw) >> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) >> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 10:55:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 10:55:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUv-0003Fm-8N; Fri, 01 Jun 2012 10:54:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaPUt-0003FU-R2 for xen-users@lists.xen.org; Fri, 01 Jun 2012 10:54:24 +0000 Received: from [85.158.138.51:42541] by server-4.bemta-3.messagelabs.com id F9/EB-32504-E5F98CF4; Fri, 01 Jun 2012 10:54:22 +0000 X-Env-Sender: jane.wayne2978@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1338548060!30353175!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4536 invoked from network); 1 Jun 2012 10:54:22 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 10:54:22 -0000 Received: by obbwd20 with SMTP id wd20so3558221obb.32 for ; Fri, 01 Jun 2012 03:54:20 -0700 (PDT) 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:content-transfer-encoding; bh=RhCEIg29d+zPImL0WvJKuIIhnv1zYcgghiwRdb3THHs=; b=cuH07XbcBKKD4+iW0rSpkTbgJ3gHHvHQ0vDNkE7GzY5zDqhFyI8OwuPJfNYkxFPy6W Wmkmy5arxoLvY5N9zvMZXuW0eaQl4oKlWR6M52bIKwPn6Cf7gg/E//okngL1hw9yN2aG NngTKx309TmaG/Rt1UmboPQP7D17FGq6G9AQQdgm968X8EAFBJxo6Ew+EDDIKC1c3IxA Y9Ne7UwjfNuW8Myv34LLOZx06hakao0MxmVQbOWxe6M4IC2d7iiRF6kxci/XCCcNC6kI 9rvaIrp2qlePd5qy0JHb6HWGWEHgbsrrHG+NawvQrvOhPwgnGXeFQEQGdcauHhdK+3VV LGwA== MIME-Version: 1.0 Received: by 10.182.212.4 with SMTP id ng4mr2178698obc.20.1338548060308; Fri, 01 Jun 2012 03:54:20 -0700 (PDT) Received: by 10.182.188.106 with HTTP; Fri, 1 Jun 2012 03:54:20 -0700 (PDT) In-Reply-To: <1338543045.17466.47.camel@zakaz.uk.xensource.com> References: <1338543045.17466.47.camel@zakaz.uk.xensource.com> Date: Fri, 1 Jun 2012 06:54:20 -0400 Message-ID: From: Jane Wayne To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] installation and configuration documentation for XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org thanks ian, i've posted on the other list. On Fri, Jun 1, 2012 at 5:30 AM, Ian Campbell wrot= e: > Hi Jane, > > Both this and the other question you sent are more likely to get answers > on the xen-api@ list where most XCP discussion happens (not an obvious > name, I agree, steps are under way to clarify this!) > > Ian. > > On Fri, 2012-06-01 at 10:15 +0100, Jane Wayne wrote: >> i've installed XCP 1.5-beta. i'm a little confused as to what has >> happened. everything so far seems to work. however, i need more >> information on what was done to my hard disk during the installation >> and how was the file system set up. >> >> in particular, i was investigating how to create a new logical volume >> to place my ISO file to use as my ISO storage (SR). i notice (see >> below with lvs command) that something like this was already created >> automatically, BUT, it was not mounted anywhere. i was wondering why >> this artifact logical volume was created and not mounted? >> >> i have a 3 TB hard disk. when i issue: fdisk -l, i get the following out= put. >> >> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util >> fdisk doesn't support GPT. Use GNU Parted. >> WARNING: The size of this disk is 3.0 TB (3000592982016 bytes). >> DOS partition table format can not be used on drives for volumes >> larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID >> partition table format (GPT). >> Disk /dev/sda: 3000.5 GB, 3000592982016 bytes >> 256 heads, 63 sectors/track, 363376 cylinders >> Units =3D cylinders of 16128 * 512 =3D 8257536 bytes >> =A0 =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Block= s =A0 Id =A0System >> /dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0266306 =A02147483647+ = =A0ee =A0EFI GPT >> >> the pvs command gives me the following: >> >> =A0 PV =A0 =A0 =A0 =A0 VG =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Fmt >> Attr PSize PFree >> =A0 /dev/sda3 =A0VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 lvm2 >> a- =A0 2.72T 2.62T >> >> the vgs command gives me the following: >> >> =A0 VG =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #PV #LV #SN Attr >> =A0VSize VFree >> =A0 VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 =A0 1 =A0 3 =A0 0 >> wz--n- 2.72T 2.62T >> >> the lvs command gives me the following: >> >> =A0 LV =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 VG >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Attr =A0 LSize =A0 Origin= Snap% =A0Move Log Copy% >> Convert >> =A0 MGT >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi-a- =A0 4.00M >> =A0 VHD-cfa4481f-2553-4dfe-a4aa-bfe5f99186c6 >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- =A0 8.02G >> =A0 iso >> VG_XenStorage-5a32ce29-c98e-1488-273e-263c65d47479 -wi--- 100.00G >> >> the mount command gives me the following: >> >> /dev/sda1 on / type ext3 (rw) >> none on /proc type proc (rw) >> none on /sys type sysfs (rw) >> none on /dev/pts type devpts (rw) >> none on /dev/shm type tmpfs (rw) >> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) >> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jun 01 14:23:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jun 2012 14:23: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 1SaSjt-00039P-VJ; Fri, 01 Jun 2012 14:22:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SaSjs-00039K-K2 for xen-users@lists.xen.org; Fri, 01 Jun 2012 14:22:05 +0000 Received: from [85.158.138.51:43456] by server-8.bemta-3.messagelabs.com id C2/BB-01456-B00D8CF4; Fri, 01 Jun 2012 14:22:03 +0000 X-Env-Sender: cyberhawk001@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1338560520!27505438!1 X-Originating-IP: [209.85.213.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.10; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20604 invoked from network); 1 Jun 2012 14:22:01 -0000 Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com) (209.85.213.173) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jun 2012 14:22:01 -0000 Received: by yenm4 with SMTP id m4so2109568yen.32 for ; Fri, 01 Jun 2012 07:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=2V5gojH/Om8NDw5GfYQ0fZO8dBuHpgGcX/dawcP7u+o=; b=VSMogFw8v+9u7TIepxofyoG7XLKfQGBECU7y/qwc6N1dtFZxqjWQF3YQUxugbBSKOh wa0asNRRvqlLuD4CWEs41PQ+fqTfnPjsFdtQHmxIH6KVbeYuoFNM8iL1KlVISEcg9pZx s9RHvUcljVOyQUr+rJrpuO3nCz/T8EZEqAzpMFM6uHTV/pu5P++SDYvco0W4o7l9WKgg S6PJbzEqcyl60FPxDK0LWlnE49wqFNSaW78Hiirf/Bhg8AjuIY4C/xvLqVbl29EcfiIF P/hpXmpOPXP6a91gICf6X54kjMjACg6wVmpp2cEeltU9HKWGNhfTrfp+KGUD7KwOIILe QlMg== Received: by 10.100.228.3 with SMTP id a3mr893221anh.4.1338560520213; Fri, 01 Jun 2012 07:22:00 -0700 (PDT) Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net. [66.177.73.176]) by mx.google.com with ESMTPS id g4sm7024324yhf.12.2012.06.01.07.21.58 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Jun 2012 07:21:59 -0700 (PDT) Message-ID: <4FC8CFF4.2040100@gmail.com> Date: Fri, 01 Jun 2012 10:21:40 -0400 From: cyberhawk001@gmail.com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Ian Campbell , "xen-users@lists.xen.org" References: <4FC7767B.6040706@gmail.com> <1338532821.14877.49.camel@dagon.hellion.org.uk> In-Reply-To: <1338532821.14877.49.camel@dagon.hellion.org.uk> Subject: Re: [Xen-users] Installing XAPI on Debian Wheezy with Xen 4.2-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3511025905151307911==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3511025905151307911== Content-Type: multipart/alternative; boundary="------------030808020300020306010208" This is a multi-part message in MIME format. --------------030808020300020306010208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 6/1/2012 2:40 AM, Ian Campbell wrote: > Questions about XCP and XAPI are best addressed to the xen-api@ list. > I've CCd it for you. Thank you for writing responding Ian. I know it is best suited in xen-xapi BUT have already asked several questions on the Xen-api list regarding XAPI and only received back a couple responses WHICH didn't really help with all questions. SO, i asked it here on Xen-users to see if any Xen users have messed around with installing XAPI on Debian and see what their experiences where. > On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote: >> I have not had any luck getting the XAPI to install or even work in >> Debian Wheezy 64bit SO figured i ask anyone out there: >> >> 1.) Has any Xen user(s) have successfully installed the XAPI Toolstack >> on Xen 4.2-unstable and how were you able to do it? > XAPI needs to be built against the specific hypervisor version it is > going to run against. The XAPI packages in Wheezy are built against the > 4.1 packages in Wheezy. > > Why don't you just use the packaged version of both Xen (i.e. 4.1) and > xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an > XCP system up and running. Unless you have a really strong reason to > build the Xen yourself this is something which is best left to the > distros. > > In the past xapi has needed actual porting effort when moving between > Xen versions. I don't know if this will be the case for moving 4.1->4.2 > but I would suggest that unless you AHH ok, well the last time i asked if XAPI would work or was compatible with Xen 4.2-unstable, on the list Xen-api, the responses i got back was: "*I don't know, but I hope so If you find out, please let us know. The latest trunk build of xapi should work with xen-unstable, but we haven't released that version of xapi yet, either for XenServer, XCP, or Debian/Ubuntu.* " SO, i was wondering if i couldn't get it to work never the less.... :) AND no one has ever remotely mentioned on the Xen-api list that you have to build XAPI based on what version of Xen it is going to be used with. PLUS i really like and have gotten used to using the XL toolstack in Xen 4.2-unstable as well as not having to do several file modifications or editing that Xen 4.1.2 seems to always need. Plus, i already have a few DomU config files formatted using the XL toolstack and well since that is going to be the standard coming up soon here, might as well start learning and getting used to the latest tools as some things are different in XM vs XL. >> 2.) Has anyone been able to compile the XAPI Toolstack from source and >> again how to do that? > This I don't know. Have you checked the wiki pages? Also you could just > rebuild the Debian packages in the normal way. The ONLY Wiki there is about this is http://wiki.xen.org/wiki/Compile_the_XCP_toolstack_from_source AND it is using the *xapi-autobuilder.git* which again will build the XAPI tools and dependencies AS well as the Xen 4.1 hypgervisor and its dependencies as well. I have already asked about this several times and the only thing i got back was: "Yes, you can download the xapi source from http://github.com/xen-org/xen-api, check out the debian branch, and build from there. Or you can do apt-get source xen-api, and rebuild it. You might be able to use dpkg to install the binary deb package, without installing dependencies, but I don't know. " WHICH i have done that, i can download the the Debian Branch of the above git and have even downloaded it using "*apt-get source xen-api*" BUT the Readme file in there is virtually none existent unlike how it is with Xen, and just simply running "MAKE" doesn't do anything nor compiles; it just gives and error "*make: omake: Command not found*". Again, these i have asked about on Xen-api list BUT are too much of a NOOB question(s) for anyone to answer so never got anywhere with it yet... :). Also, just like with Xen you need to have a list of dependency packages installed before you can even compile Xen, WELL such things are virtually not documented at all so pretty tough to even know where to start with that. I know XAPI and Project Kronos is still very new and just being developed, but some people out there have gotten it to compile and work and etc SO there is a way, i am just too new at this to go poking around some code to figure out how it works and than figure out how to compile or use...hehe >> - I had Xen 4.2-unstable installed, removed it and ran sudo apt-get >> xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the >> XE toolstack i just can't get to load or run, even the XM toolstack >> doesn't work either. Following the Wiki guides don't quite help yet. >> The /etc/init.d folder only contains xendomains, xen and all of the >> xcp-* daemons. >> >> - I would be nice to know how to just remove/uninstall >> xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and >> xenstore-utils, so than one can install Xen 4.2-unstable instead. > Why do you want to do this? Why not run 4.1 which is what the XCP > packages are built against and what people have been testing in the > context of Wheezy? > >> - On the flip-side, it would be nice if it was easy to install JUST >> the XAPI Toolstack as a standalone package on top of an existing Xen >> Dom0... :) > I don't understand this. If you have an existing Xen dom0 can't you just > apt-get install xcp-xapi? Well, NO you can't. I have already tried this. The XAPI toolstack does not come desperately. If you lets say already have Xen 4.2-unstable running or just installed and than you run "*apt-get install xcp-xapi*", it installs the x*cp-xapi, stunnel, xcp-eliloader, xcp-fe, xcp-networkd, xcp-squeezed, xcp-storage-managers, xcp-v6d, xcp-xe, libxenstore3.0,* AND other dependecnies, BUT it will also try to install *xen-hypervisor-4.1-amd64, xen-utils-4.1* and any additional dependencies it needs WHICH will fail with errors not able to install and etc. SO, it never gets installed and could not get it all to work. SO, what i am saying that EVEN if i had my own compiled Xen 4.1.2 installed, the *apt-get install xcp-xapi*" seems to me has NO way of checking to see if you already have Xen 4.1.2 installed and it won't try to re-download and install it form the repository, let alone check if Xen 4.2-Unstable is installed. HENCE what i was saying is that it would be REALLY nice if the XAPI toolstack came as a standalone package, just like most anything, and installs its own dependencies (as it needs several to make it work) BUT not the hypervisor. I am sure it will eventually get there BUT just find it soo puzzling why the XAPI was packaged specifically to include a hypervisor at every turn. However, if what you said at the beginning that "*XAPI needs to be built against the specific hypervisor version*" is how it works, than that would make perfect sense as to why XAPI needs to come with its partnered Xen version. BUT, none of that has every been said or stated on xen-api forum SO again, people there are MOSTLY all XAPI developers and rarely have time to answer simple NOOB questions such as these and focus more on bugs or developer issues.... :). On top of that all of the Project Kronos Wiki pages are pretty outdated and need massive updating which no one as done yet. >> Thank you for any input from anyone who has experimented with XAPI >> installation on Debian. > I've not run XAPI on Debian but it seems to me that by trying to use > 4.2-unstable you are making life much more difficult for yourself than > it needs to be. Just use the existing packages in Debian and I think > things will go much smoother. > > Even if you do have a good reason for running 4.2 I'd suggest following > the guides with 4.1 first so you get a feel for things before striking > off and blazing a new trail to 4.2. > > Ian. Well thanks again Ian, you are always helpful in answering questions on here or helping out. I guess i will mess with XAPI some more, the last time i installed xcp-xapi from debian repo, it installed and booted to Xen 4.1, but could not get any toolstack to load or work. But, i will try again........ :) --------------030808020300020306010208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 6/1/2012 2:40 AM, Ian Campbell wrote: 
Questions about XCP and XAPI are best addressed to the xen-api@ list.
I've CCd it for you.

Thank you for writing responding Ian. I know it is best suited in xen-xapi BUT have already asked several questions on the Xen-api list regarding XAPI and only received back a couple responses WHICH didn't really help with all questions.
SO, i asked it here on Xen-users to see if any Xen users have messed around with installing XAPI on Debian and see what their experiences where.


On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote:

I have not had any luck getting the XAPI to install or even work in
Debian Wheezy 64bit SO figured i ask anyone out there:

1.) Has any Xen user(s) have successfully installed the XAPI Toolstack
on Xen 4.2-unstable and how were you able to do it?

XAPI needs to be built against the specific hypervisor version it is
going to run against. The XAPI packages in Wheezy are built against the
4.1 packages in Wheezy.

Why don't you just use the packaged version of both Xen (i.e. 4.1) and
xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an
XCP system up and running. Unless you have a really strong reason to
build the Xen yourself this is something which is best left to the
distros.

In the past xapi has needed actual porting effort when moving between
Xen versions. I don't know if this will be the case for moving 4.1->4.2
but I would suggest that unless you

AHH ok, well the last time i asked if XAPI would work or was compatible with Xen 4.2-unstable, on the list Xen-api, the responses i got back was:

"I don't know, but I hope so If you find out, please let us know. The latest trunk build of xapi should work with xen-unstable, but we haven't released that version of xapi yet, either for XenServer, XCP, or Debian/Ubuntu. "

SO, i was wondering if i couldn't get it to work never the less.... :) AND no one has ever remotely mentioned on the Xen-api list that you have to build XAPI based on what version of Xen it is going to be used with.

PLUS i really like and have gotten used to using the XL toolstack in Xen 4.2-unstable as well as not having to do several file modifications or editing that Xen 4.1.2 seems to always need. Plus, i already have a few DomU config files formatted using the XL toolstack and well since that is going to be the standard coming up soon here, might as well start learning and getting used to the latest tools as some things are different in XM vs XL.




      

        
2.) Has anyone been able to compile the XAPI Toolstack from source and
again how to do that?


      

      
This I don't know. Have you checked the wiki pages? Also you could just
rebuild the Debian packages in the normal way.

    

    

    The ONLY Wiki there is about this is
    http://wiki.xen.org/wiki/Compile_the_XCP_toolstack_from_source AND
    it is using the xapi-autobuilder.git which again will build
    the XAPI tools and dependencies AS well as the Xen 4.1 hypgervisor
    and its dependencies as well. I have already asked about this
    several times and the only thing i got back was:

    

    "Yes, you can download the xapi source from http://github.com/xen-org/xen-api,
    check out the debian branch, and build from there. Or you can do
    apt-get source xen-api, and rebuild it. You might be able to use
    dpkg to install the binary deb package, without installing
    dependencies, but I don't know.
    "

    

    WHICH i have done that, i can download the the Debian Branch of the
    above git and have even downloaded it using "apt-get source
      xen-api" BUT the Readme file in there is virtually none
    existent unlike how it is with Xen, and just simply running "MAKE"
    doesn't do anything nor compiles; it just gives and error "make:
      omake: Command not found". Again, these i have asked about on
    Xen-api list BUT are too much of a NOOB question(s) for anyone to
    answer so never got anywhere with it yet... :). 

    

    Also, just like with Xen you need to have a list of dependency
    packages installed before you can even compile Xen, WELL such things
    are virtually not documented at all so pretty tough to even know
    where to start with that. I know XAPI and Project Kronos is still
    very new and just being developed, but some  people out there have
    gotten it to compile and work and etc SO there is a way, i am just
    too new at this to go poking around some code to figure out how it
    works and than figure out how to compile or use...hehe

    

    

      

        
- I had Xen 4.2-unstable installed, removed it and ran sudo apt-get
xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the
XE toolstack i just can't get to load or run, even the XM toolstack
doesn't work either. Following the Wiki guides don't quite help yet.
The /etc/init.d folder only contains xendomains, xen and all of the
xcp-* daemons.

- I would be nice to know how to just remove/uninstall
xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and
xenstore-utils, so than one can install Xen 4.2-unstable instead.


      

      
Why do you want to do this? Why not run 4.1 which is what the XCP
packages are built against and what people have been testing in the
context of Wheezy?



      

        
- On the flip-side, it would be nice if it was easy to install JUST
the XAPI Toolstack as a standalone package on top of an existing Xen
Dom0... :)


      

      
I don't understand this. If you have an existing Xen dom0 can't you just
apt-get install xcp-xapi?


    

    

    

    Well, NO you can't. I have already tried this. The XAPI toolstack
    does not come desperately. If you lets say already have Xen
    4.2-unstable running or just installed and than you run "apt-get
      install xcp-xapi", it installs the xcp-xapi, stunnel,
      xcp-eliloader, xcp-fe, xcp-networkd, xcp-squeezed,
      xcp-storage-managers, xcp-v6d, xcp-xe, libxenstore3.0, AND
    other dependecnies, BUT it will also try to install xen-hypervisor-4.1-amd64,
      xen-utils-4.1 and any additional dependencies it needs WHICH
    will fail with errors not able to install and etc. SO, it never gets
    installed and could not get it all to work.

    

    SO, what i am saying that EVEN if i had my own compiled Xen 4.1.2
    installed, the apt-get install xcp-xapi" seems to me has NO
    way of checking to see if you already have Xen 4.1.2 installed and
    it won't try to re-download and install it form the repository, let
    alone check if Xen 4.2-Unstable is installed. HENCE what i was
    saying is that it would be REALLY nice if the XAPI toolstack came as
    a standalone package, just like most anything, and installs its own
    dependencies (as it needs several to make it work) BUT not the
    hypervisor. I am sure it will eventually get there BUT just find it
    soo puzzling why the XAPI was packaged specifically to include a
    hypervisor at every turn.

    

    However, if what you said at the beginning that "XAPI needs to be
      built against the specific hypervisor version" is how it
    works, than that would make perfect sense as to why XAPI needs to
    come with its partnered Xen version. BUT, none of that has every
    been said or stated on xen-api forum SO again, people there are
    MOSTLY all XAPI developers and rarely have time to answer simple
    NOOB questions such as these and focus more on bugs or developer
    issues.... :). On top of that all of the Project Kronos Wiki pages
    are pretty outdated and need massive updating which no one as done
    yet.

    

    

    

      

      

        
Thank you for any input from anyone who has experimented with XAPI
installation on  Debian.


      

      
I've not run XAPI on Debian but it seems to me that by trying to use
4.2-unstable you are making life much more difficult for yourself than
it needs to be. Just use the existing packages in Debian and I think
things will go much smoother.

Even if you do have a good reason for running 4.2 I'd suggest following
the guides with 4.1 first so you get a feel for things before striking
off and blazing a new trail to 4.2.

Ian.


    

    

    

    Well thanks again Ian, you are always helpful in answering questions
    on here or helping out. I guess i will mess with XAPI some more, the
    last time i installed xcp-xapi from debian repo, it installed and
    booted to Xen 4.1, but could not get any toolstack to load or work.
    But, i will try again........ :)

  


--------------030808020300020306010208--


--===============3511025905151307911==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3511025905151307911==--


From xen-users-bounces@lists.xen.org Fri Jun 01 14:23:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 14:23: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 1SaSjt-00039P-VJ; Fri, 01 Jun 2012 14:22:05 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaSjs-00039K-K2
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 14:22:05 +0000
Received: from [85.158.138.51:43456] by server-8.bemta-3.messagelabs.com id
	C2/BB-01456-B00D8CF4; Fri, 01 Jun 2012 14:22:03 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-16.tower-174.messagelabs.com!1338560520!27505438!1
X-Originating-IP: [209.85.213.173]
X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20604 invoked from network); 1 Jun 2012 14:22:01 -0000
Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com)
	(209.85.213.173)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jun 2012 14:22:01 -0000
Received: by yenm4 with SMTP id m4so2109568yen.32
	for ; Fri, 01 Jun 2012 07:22:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=2V5gojH/Om8NDw5GfYQ0fZO8dBuHpgGcX/dawcP7u+o=;
	b=VSMogFw8v+9u7TIepxofyoG7XLKfQGBECU7y/qwc6N1dtFZxqjWQF3YQUxugbBSKOh
	wa0asNRRvqlLuD4CWEs41PQ+fqTfnPjsFdtQHmxIH6KVbeYuoFNM8iL1KlVISEcg9pZx
	s9RHvUcljVOyQUr+rJrpuO3nCz/T8EZEqAzpMFM6uHTV/pu5P++SDYvco0W4o7l9WKgg
	S6PJbzEqcyl60FPxDK0LWlnE49wqFNSaW78Hiirf/Bhg8AjuIY4C/xvLqVbl29EcfiIF
	P/hpXmpOPXP6a91gICf6X54kjMjACg6wVmpp2cEeltU9HKWGNhfTrfp+KGUD7KwOIILe
	QlMg==
Received: by 10.100.228.3 with SMTP id a3mr893221anh.4.1338560520213;
	Fri, 01 Jun 2012 07:22:00 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id g4sm7024324yhf.12.2012.06.01.07.21.58
	(version=TLSv1/SSLv3 cipher=OTHER);
	Fri, 01 Jun 2012 07:21:59 -0700 (PDT)
Message-ID: <4FC8CFF4.2040100@gmail.com>
Date: Fri, 01 Jun 2012 10:21:40 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ian Campbell , 
	"xen-users@lists.xen.org" 
References: <4FC7767B.6040706@gmail.com>
	<1338532821.14877.49.camel@dagon.hellion.org.uk>
In-Reply-To: <1338532821.14877.49.camel@dagon.hellion.org.uk>
Subject: Re: [Xen-users] Installing XAPI on Debian Wheezy with Xen
	4.2-unstable?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3511025905151307911=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============3511025905151307911==
Content-Type: multipart/alternative;
 boundary="------------030808020300020306010208"

This is a multi-part message in MIME format.
--------------030808020300020306010208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/1/2012 2:40 AM, Ian Campbell wrote:
> Questions about XCP and XAPI are best addressed to the xen-api@ list.
> I've CCd it for you.

Thank you for writing responding Ian. I know it is best suited in 
xen-xapi BUT have already asked several questions on the Xen-api list 
regarding XAPI and only received back a couple responses WHICH didn't 
really help with all questions.
SO, i asked it here on Xen-users to see if any Xen users have messed 
around with installing XAPI on Debian and see what their experiences where.


> On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote:
>> I have not had any luck getting the XAPI to install or even work in
>> Debian Wheezy 64bit SO figured i ask anyone out there:
>>
>> 1.) Has any Xen user(s) have successfully installed the XAPI Toolstack
>> on Xen 4.2-unstable and how were you able to do it?
> XAPI needs to be built against the specific hypervisor version it is
> going to run against. The XAPI packages in Wheezy are built against the
> 4.1 packages in Wheezy.
>
> Why don't you just use the packaged version of both Xen (i.e. 4.1) and
> xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an
> XCP system up and running. Unless you have a really strong reason to
> build the Xen yourself this is something which is best left to the
> distros.
>
> In the past xapi has needed actual porting effort when moving between
> Xen versions. I don't know if this will be the case for moving 4.1->4.2
> but I would suggest that unless you

AHH ok, well the last time i asked if XAPI would work or was compatible 
with Xen 4.2-unstable, on the list Xen-api, the responses i got back was:

"*I don't know, but I hope so If you find out, please let us know. The 
latest trunk build of xapi should work with xen-unstable, but we haven't 
released that version of xapi yet, either for XenServer, XCP, or 
Debian/Ubuntu.* "

SO, i was wondering if i couldn't get it to work never the less.... :) 
AND no one has ever remotely mentioned on the Xen-api list that you have 
to build XAPI based on what version of Xen it is going to be used with.

PLUS i really like and have gotten used to using the XL toolstack in Xen 
4.2-unstable as well as not having to do several file modifications or 
editing that Xen 4.1.2 seems to always need. Plus, i already have a few 
DomU config files formatted using the XL toolstack and well since that 
is going to be the standard coming up soon here, might as well start 
learning and getting used to the latest tools as some things are 
different in XM vs XL.



>> 2.) Has anyone been able to compile the XAPI Toolstack from source and
>> again how to do that?
> This I don't know. Have you checked the wiki pages? Also you could just
> rebuild the Debian packages in the normal way.

The ONLY Wiki there is about this is 
http://wiki.xen.org/wiki/Compile_the_XCP_toolstack_from_source AND it is 
using the *xapi-autobuilder.git* which again will build the XAPI tools 
and dependencies AS well as the Xen 4.1 hypgervisor and its dependencies 
as well. I have already asked about this several times and the only 
thing i got back was:

"Yes, you can download the xapi source from 
http://github.com/xen-org/xen-api, check out the debian branch, and 
build from there. Or you can do apt-get source xen-api, and rebuild it. 
You might be able to use dpkg to install the binary deb package, without 
installing dependencies, but I don't know. "

WHICH i have done that, i can download the the Debian Branch of the 
above git and have even downloaded it using "*apt-get source xen-api*" 
BUT the Readme file in there is virtually none existent unlike how it is 
with Xen, and just simply running "MAKE" doesn't do anything nor 
compiles; it just gives and error "*make: omake: Command not found*". 
Again, these i have asked about on Xen-api list BUT are too much of a 
NOOB question(s) for anyone to answer so never got anywhere with it 
yet... :).

Also, just like with Xen you need to have a list of dependency packages 
installed before you can even compile Xen, WELL such things are 
virtually not documented at all so pretty tough to even know where to 
start with that. I know XAPI and Project Kronos is still very new and 
just being developed, but some  people out there have gotten it to 
compile and work and etc SO there is a way, i am just too new at this to 
go poking around some code to figure out how it works and than figure 
out how to compile or use...hehe

>> - I had Xen 4.2-unstable installed, removed it and ran sudo apt-get
>> xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the
>> XE toolstack i just can't get to load or run, even the XM toolstack
>> doesn't work either. Following the Wiki guides don't quite help yet.
>> The /etc/init.d folder only contains xendomains, xen and all of the
>> xcp-* daemons.
>>
>> - I would be nice to know how to just remove/uninstall
>> xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and
>> xenstore-utils, so than one can install Xen 4.2-unstable instead.
> Why do you want to do this? Why not run 4.1 which is what the XCP
> packages are built against and what people have been testing in the
> context of Wheezy?
>
>> - On the flip-side, it would be nice if it was easy to install JUST
>> the XAPI Toolstack as a standalone package on top of an existing Xen
>> Dom0... :)
> I don't understand this. If you have an existing Xen dom0 can't you just
> apt-get install xcp-xapi?


Well, NO you can't. I have already tried this. The XAPI toolstack does 
not come desperately. If you lets say already have Xen 4.2-unstable 
running or just installed and than you run "*apt-get install xcp-xapi*", 
it installs the x*cp-xapi, stunnel, xcp-eliloader, xcp-fe, xcp-networkd, 
xcp-squeezed, xcp-storage-managers, xcp-v6d, xcp-xe, libxenstore3.0,* 
AND other dependecnies, BUT it will also try to install 
*xen-hypervisor-4.1-amd64, xen-utils-4.1* and any additional 
dependencies it needs WHICH will fail with errors not able to install 
and etc. SO, it never gets installed and could not get it all to work.

SO, what i am saying that EVEN if i had my own compiled Xen 4.1.2 
installed, the *apt-get install xcp-xapi*" seems to me has NO way of 
checking to see if you already have Xen 4.1.2 installed and it won't try 
to re-download and install it form the repository, let alone check if 
Xen 4.2-Unstable is installed. HENCE what i was saying is that it would 
be REALLY nice if the XAPI toolstack came as a standalone package, just 
like most anything, and installs its own dependencies (as it needs 
several to make it work) BUT not the hypervisor. I am sure it will 
eventually get there BUT just find it soo puzzling why the XAPI was 
packaged specifically to include a hypervisor at every turn.

However, if what you said at the beginning that "*XAPI needs to be built 
against the specific hypervisor version*" is how it works, than that 
would make perfect sense as to why XAPI needs to come with its partnered 
Xen version. BUT, none of that has every been said or stated on xen-api 
forum SO again, people there are MOSTLY all XAPI developers and rarely 
have time to answer simple NOOB questions such as these and focus more 
on bugs or developer issues.... :). On top of that all of the Project 
Kronos Wiki pages are pretty outdated and need massive updating which no 
one as done yet.


>> Thank you for any input from anyone who has experimented with XAPI
>> installation on  Debian.
> I've not run XAPI on Debian but it seems to me that by trying to use
> 4.2-unstable you are making life much more difficult for yourself than
> it needs to be. Just use the existing packages in Debian and I think
> things will go much smoother.
>
> Even if you do have a good reason for running 4.2 I'd suggest following
> the guides with 4.1 first so you get a feel for things before striking
> off and blazing a new trail to 4.2.
>
> Ian.


Well thanks again Ian, you are always helpful in answering questions on 
here or helping out. I guess i will mess with XAPI some more, the last 
time i installed xcp-xapi from debian repo, it installed and booted to 
Xen 4.1, but could not get any toolstack to load or work. But, i will 
try again........ :)

--------------030808020300020306010208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    On 6/1/2012 2:40 AM, Ian Campbell wrote:
    

      
Questions about XCP and XAPI are best addressed to the xen-api@ list.
I've CCd it for you.


    

    

    Thank you for writing responding Ian. I know it is best suited in
    xen-xapi BUT have already asked several questions on the Xen-api
    list regarding XAPI and only received back a couple responses WHICH
    didn't really help with all questions.

    SO, i asked it here on Xen-users to see if any Xen users have messed
    around with installing XAPI on Debian and see what their experiences
    where.

    

    

    

      
On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@gmail.com wrote:


      

        
I have not had any luck getting the XAPI to install or even work in
Debian Wheezy 64bit SO figured i ask anyone out there:

1.) Has any Xen user(s) have successfully installed the XAPI Toolstack
on Xen 4.2-unstable and how were you able to do it?


      

      
XAPI needs to be built against the specific hypervisor version it is
going to run against. The XAPI packages in Wheezy are built against the
4.1 packages in Wheezy.

Why don't you just use the packaged version of both Xen (i.e. 4.1) and
xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an
XCP system up and running. Unless you have a really strong reason to
build the Xen yourself this is something which is best left to the
distros.

In the past xapi has needed actual porting effort when moving between
Xen versions. I don't know if this will be the case for moving 4.1->4.2
but I would suggest that unless you


    

    

    AHH ok, well the last time i asked if XAPI would work or was
    compatible with Xen 4.2-unstable, on the list Xen-api, the responses
    i got back was:

    

    "I don't know, but I hope so  If you find out, please let us know. The
      latest trunk build of xapi should work with xen-unstable, but we
      haven't released that version of xapi yet, either for XenServer,
      XCP, or Debian/Ubuntu.
    "

    

    SO, i was wondering if i couldn't get it to work never the less....
    :) AND no one has ever remotely mentioned on the Xen-api list that
    you have to build XAPI based on what version of Xen it is going to
    be used with.

    

    PLUS i really like and have gotten used to using the XL toolstack in
    Xen 4.2-unstable as well as not having to do several file
    modifications or editing that Xen 4.1.2 seems to always need. Plus,
    i already have a few DomU config files formatted using the XL
    toolstack and well since that is going to be the standard coming up
    soon here, might as well start learning and getting used to the
    latest tools as some things are different in XM vs XL.

    

    

    

    

      

      

        
2.) Has anyone been able to compile the XAPI Toolstack from source and
again how to do that?


      

      
This I don't know. Have you checked the wiki pages? Also you could just
rebuild the Debian packages in the normal way.

    

    

    The ONLY Wiki there is about this is
    http://wiki.xen.org/wiki/Compile_the_XCP_toolstack_from_source AND
    it is using the xapi-autobuilder.git which again will build
    the XAPI tools and dependencies AS well as the Xen 4.1 hypgervisor
    and its dependencies as well. I have already asked about this
    several times and the only thing i got back was:

    

    "Yes, you can download the xapi source from http://github.com/xen-org/xen-api,
    check out the debian branch, and build from there. Or you can do
    apt-get source xen-api, and rebuild it. You might be able to use
    dpkg to install the binary deb package, without installing
    dependencies, but I don't know.
    "

    

    WHICH i have done that, i can download the the Debian Branch of the
    above git and have even downloaded it using "apt-get source
      xen-api" BUT the Readme file in there is virtually none
    existent unlike how it is with Xen, and just simply running "MAKE"
    doesn't do anything nor compiles; it just gives and error "make:
      omake: Command not found". Again, these i have asked about on
    Xen-api list BUT are too much of a NOOB question(s) for anyone to
    answer so never got anywhere with it yet... :). 

    

    Also, just like with Xen you need to have a list of dependency
    packages installed before you can even compile Xen, WELL such things
    are virtually not documented at all so pretty tough to even know
    where to start with that. I know XAPI and Project Kronos is still
    very new and just being developed, but some  people out there have
    gotten it to compile and work and etc SO there is a way, i am just
    too new at this to go poking around some code to figure out how it
    works and than figure out how to compile or use...hehe

    

    

      

        
- I had Xen 4.2-unstable installed, removed it and ran sudo apt-get
xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the
XE toolstack i just can't get to load or run, even the XM toolstack
doesn't work either. Following the Wiki guides don't quite help yet.
The /etc/init.d folder only contains xendomains, xen and all of the
xcp-* daemons.

- I would be nice to know how to just remove/uninstall
xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and
xenstore-utils, so than one can install Xen 4.2-unstable instead.


      

      
Why do you want to do this? Why not run 4.1 which is what the XCP
packages are built against and what people have been testing in the
context of Wheezy?



      

        
- On the flip-side, it would be nice if it was easy to install JUST
the XAPI Toolstack as a standalone package on top of an existing Xen
Dom0... :)


      

      
I don't understand this. If you have an existing Xen dom0 can't you just
apt-get install xcp-xapi?


    

    

    

    Well, NO you can't. I have already tried this. The XAPI toolstack
    does not come desperately. If you lets say already have Xen
    4.2-unstable running or just installed and than you run "apt-get
      install xcp-xapi", it installs the xcp-xapi, stunnel,
      xcp-eliloader, xcp-fe, xcp-networkd, xcp-squeezed,
      xcp-storage-managers, xcp-v6d, xcp-xe, libxenstore3.0, AND
    other dependecnies, BUT it will also try to install xen-hypervisor-4.1-amd64,
      xen-utils-4.1 and any additional dependencies it needs WHICH
    will fail with errors not able to install and etc. SO, it never gets
    installed and could not get it all to work.

    

    SO, what i am saying that EVEN if i had my own compiled Xen 4.1.2
    installed, the apt-get install xcp-xapi" seems to me has NO
    way of checking to see if you already have Xen 4.1.2 installed and
    it won't try to re-download and install it form the repository, let
    alone check if Xen 4.2-Unstable is installed. HENCE what i was
    saying is that it would be REALLY nice if the XAPI toolstack came as
    a standalone package, just like most anything, and installs its own
    dependencies (as it needs several to make it work) BUT not the
    hypervisor. I am sure it will eventually get there BUT just find it
    soo puzzling why the XAPI was packaged specifically to include a
    hypervisor at every turn.

    

    However, if what you said at the beginning that "XAPI needs to be
      built against the specific hypervisor version" is how it
    works, than that would make perfect sense as to why XAPI needs to
    come with its partnered Xen version. BUT, none of that has every
    been said or stated on xen-api forum SO again, people there are
    MOSTLY all XAPI developers and rarely have time to answer simple
    NOOB questions such as these and focus more on bugs or developer
    issues.... :). On top of that all of the Project Kronos Wiki pages
    are pretty outdated and need massive updating which no one as done
    yet.

    

    

    

      

      

        
Thank you for any input from anyone who has experimented with XAPI
installation on  Debian.


      

      
I've not run XAPI on Debian but it seems to me that by trying to use
4.2-unstable you are making life much more difficult for yourself than
it needs to be. Just use the existing packages in Debian and I think
things will go much smoother.

Even if you do have a good reason for running 4.2 I'd suggest following
the guides with 4.1 first so you get a feel for things before striking
off and blazing a new trail to 4.2.

Ian.


    

    

    

    Well thanks again Ian, you are always helpful in answering questions
    on here or helping out. I guess i will mess with XAPI some more, the
    last time i installed xcp-xapi from debian repo, it installed and
    booted to Xen 4.1, but could not get any toolstack to load or work.
    But, i will try again........ :)

  


--------------030808020300020306010208--


--===============3511025905151307911==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3511025905151307911==--


From xen-users-bounces@lists.xen.org Fri Jun 01 15:47:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 15:47:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SaU3L-0000EG-Ci; Fri, 01 Jun 2012 15:46:15 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaU3F-0008PM-SG
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 15:46:10 +0000
Received: from [85.158.138.51:35469] by server-12.bemta-3.messagelabs.com id
	07/9D-29860-0C3E8CF4; Fri, 01 Jun 2012 15:46:08 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338565567!30465793!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15616 invoked from network); 1 Jun 2012 15:46:08 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jun 2012 15:46:08 -0000
X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12791365"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	01 Jun 2012 15:40:57 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012
	16:40:57 +0100
Message-ID: <1338565256.1077.3.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "lars.kurth@xen.org" 
Date: Fri, 1 Jun 2012 16:40:56 +0100
In-Reply-To: <4FC3A7B4.3020805@xen.org>
References: 
	
	<4FC3A7B4.3020805@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel]  Using XL toolstack (Xen) with DRBD
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, 2012-05-28 at 17:28 +0100, Lars Kurth wrote:
> Is this on the roadmap for 4.2 or 4.3?

This == block hotplug scripts in (lib)xl?

It's on the TODO list for 4.2 as a blocker, marked as following on from
the general hotplug script improvements. I think Roger has most of the
implementation ready, pending a few other dependent changes going in.

Ian.


> Lars
> 
> On 28/05/2012 13:54, Florian Heigl wrote:
> > I wish...
> >
> > The message comes from XL as far as I remember.
> > It told me "Sorry, external blocks aren't implemented yet" or
> > something like that.
> >
> > This also affects stuff like OpenNebula + Moosefs as far as I can tell.
> >
> > Maybe you know some C and can try adding the support?
> >
> > Florian
> >
> > 2012/5/18 Chris Dickson:
> >> Hello,
> >>
> >> Currently it seems that the drbd disk type with Xen's XL toolstack (vs XM)
> >> to get the automatic promotion/demotion behavior of drbd devices is not
> >> supported. Is there something I can tweak with the block-drbd script to get
> >> this to work?
> >>
> >> Thanks,
> >>
> >> Chris
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xen.org
> >> http://lists.xen.org/xen-users
> >
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel







_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 01 15:47:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 15:47:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SaU3L-0000EG-Ci; Fri, 01 Jun 2012 15:46:15 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaU3F-0008PM-SG
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 15:46:10 +0000
Received: from [85.158.138.51:35469] by server-12.bemta-3.messagelabs.com id
	07/9D-29860-0C3E8CF4; Fri, 01 Jun 2012 15:46:08 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338565567!30465793!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15616 invoked from network); 1 Jun 2012 15:46:08 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jun 2012 15:46:08 -0000
X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12791365"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	01 Jun 2012 15:40:57 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 1 Jun 2012
	16:40:57 +0100
Message-ID: <1338565256.1077.3.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "lars.kurth@xen.org" 
Date: Fri, 1 Jun 2012 16:40:56 +0100
In-Reply-To: <4FC3A7B4.3020805@xen.org>
References: 
	
	<4FC3A7B4.3020805@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel]  Using XL toolstack (Xen) with DRBD
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, 2012-05-28 at 17:28 +0100, Lars Kurth wrote:
> Is this on the roadmap for 4.2 or 4.3?

This == block hotplug scripts in (lib)xl?

It's on the TODO list for 4.2 as a blocker, marked as following on from
the general hotplug script improvements. I think Roger has most of the
implementation ready, pending a few other dependent changes going in.

Ian.


> Lars
> 
> On 28/05/2012 13:54, Florian Heigl wrote:
> > I wish...
> >
> > The message comes from XL as far as I remember.
> > It told me "Sorry, external blocks aren't implemented yet" or
> > something like that.
> >
> > This also affects stuff like OpenNebula + Moosefs as far as I can tell.
> >
> > Maybe you know some C and can try adding the support?
> >
> > Florian
> >
> > 2012/5/18 Chris Dickson:
> >> Hello,
> >>
> >> Currently it seems that the drbd disk type with Xen's XL toolstack (vs XM)
> >> to get the automatic promotion/demotion behavior of drbd devices is not
> >> supported. Is there something I can tweak with the block-drbd script to get
> >> this to work?
> >>
> >> Thanks,
> >>
> >> Chris
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xen.org
> >> http://lists.xen.org/xen-users
> >
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel







_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 01 17:57:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 17:57: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 1SaW3Y-0008KP-EP; Fri, 01 Jun 2012 17:54:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaW3X-0008Jx-3A
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 17:54:35 +0000
Received: from [193.109.254.147:18153] by server-9.bemta-14.messagelabs.com id
	71/86-28098-9D109CF4; Fri, 01 Jun 2012 17:54:33 +0000
X-Env-Sender: Ian.Jackson@eu.citrix.com
X-Msg-Ref: server-7.tower-27.messagelabs.com!1338573273!4734467!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28101 invoked from network); 1 Jun 2012 17:54:33 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jun 2012 17:54:33 -0000
X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12793356"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	01 Jun 2012 17:54:33 +0000
Received: from norwich.cam.xci-test.com (10.80.248.129) by
	smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id
	8.3.213.0; Fri, 1 Jun 2012 18:54:33 +0100
Received: from mariner.cam.xci-test.com	([10.80.2.22]
	helo=mariner.uk.xensource.com ident=Debian-exim)	by
	norwich.cam.xci-test.com
	with esmtp (Exim 4.72)	(envelope-from )	id
	1SaW3U-00054o-NT; Fri, 01 Jun 2012 17:54:32 +0000
Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72)
	(envelope-from )	id 1SaW3U-0000L7-Le;
	Fri, 01 Jun 2012 18:54:32 +0100
From: Ian Jackson 
MIME-Version: 1.0
Message-ID: <20425.472.655564.805506@mariner.uk.xensource.com>
Date: Fri, 1 Jun 2012 18:54:32 +0100
To: lars.kurth@xen.org
Newsgroups: chiark.mail.xen.devel
In-Reply-To: 
References: 
X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu)
Cc: xen-users@lists.xen.org, "xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals"):
> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed
> front-page

This one is already much better than the existing front page.  I have
made some more changes.

The links under "Xen Docs" are rather poor.  I don't know what pages
we have that would do better, but the top link being the Wiki category
listing is quite unhelpful.

Ian.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 01 17:57:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 17:57: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 1SaW3Y-0008KP-EP; Fri, 01 Jun 2012 17:54:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaW3X-0008Jx-3A
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 17:54:35 +0000
Received: from [193.109.254.147:18153] by server-9.bemta-14.messagelabs.com id
	71/86-28098-9D109CF4; Fri, 01 Jun 2012 17:54:33 +0000
X-Env-Sender: Ian.Jackson@eu.citrix.com
X-Msg-Ref: server-7.tower-27.messagelabs.com!1338573273!4734467!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDA3ODg=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28101 invoked from network); 1 Jun 2012 17:54:33 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jun 2012 17:54:33 -0000
X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="12793356"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	01 Jun 2012 17:54:33 +0000
Received: from norwich.cam.xci-test.com (10.80.248.129) by
	smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id
	8.3.213.0; Fri, 1 Jun 2012 18:54:33 +0100
Received: from mariner.cam.xci-test.com	([10.80.2.22]
	helo=mariner.uk.xensource.com ident=Debian-exim)	by
	norwich.cam.xci-test.com
	with esmtp (Exim 4.72)	(envelope-from )	id
	1SaW3U-00054o-NT; Fri, 01 Jun 2012 17:54:32 +0000
Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72)
	(envelope-from )	id 1SaW3U-0000L7-Le;
	Fri, 01 Jun 2012 18:54:32 +0100
From: Ian Jackson 
MIME-Version: 1.0
Message-ID: <20425.472.655564.805506@mariner.uk.xensource.com>
Date: Fri, 1 Jun 2012 18:54:32 +0100
To: lars.kurth@xen.org
Newsgroups: chiark.mail.xen.devel
In-Reply-To: 
References: 
X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu)
Cc: xen-users@lists.xen.org, "xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals"):
> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed
> front-page

This one is already much better than the existing front page.  I have
made some more changes.

The links under "Xen Docs" are rather poor.  I don't know what pages
we have that would do better, but the top link being the Wiki category
listing is quite unhelpful.

Ian.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 01 19:15:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 19:15: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 1SaXGy-0002Lo-1o; Fri, 01 Jun 2012 19:12:32 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaXGw-0002Lj-4B
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 19:12:30 +0000
Received: from [193.109.254.147:21788] by server-7.bemta-14.messagelabs.com id
	54/44-07635-D1419CF4; Fri, 01 Jun 2012 19:12:29 +0000
X-Env-Sender: anil.rao@ericsson.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338577947!12372627!1
X-Originating-IP: [198.24.6.9]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDc0NDU=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27409 invoked from network); 1 Jun 2012 19:12:28 -0000
Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9)
	by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 1 Jun 2012 19:12:28 -0000
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181])
	by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id
	q51JCP4h024808; Fri, 1 Jun 2012 14:12:26 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by
	eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi;
	Fri, 1 Jun 2012 15:12:19 -0400
From: Anil Rao 
To: John Sherwood 
Date: Fri, 1 Jun 2012 15:12:18 -0400
Thread-Topic: [Xen-users] Hotplugging FPGA to running VM
Thread-Index: Ac0/rUGlkC/TnlohSamQWkEOLB9CdQAfJc9w
Message-ID: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
In-Reply-To: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6103302825401753920=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6103302825401753920==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_"

--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, John, for your thoughts.

The problem is not about a particular PCI device. Rather, it seems to affec=
t several different types of devices.

What I am seeing is this. If a device is added to the host "after" a VM has=
 been started on it, any attempt to hotplug that device to the (already run=
ning VM) results in the following.

   From Xen's point of view the hotplug operation is successful. The guest =
OS in the VM, however, cannot see the device.

If the VM was started after the device was added to the host, I don't have =
a problem.

So, once again, this is not particular to a single device. It affects all d=
evices if the condition mentioned above is true.

Thanks.
-Anil

________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com] On Behalf Of John Sherwo=
od
Sent: Thursday, May 31, 2012 9:16 PM
To: Anil Rao
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

If you've never seen this issue before and can't reproduce it with any othe=
r PCI devices, I'd suggest trying the devel mailing list, but I'd first col=
lect whatever logs you can that are salient to the issue beforehand.  I've =
never had issues with PCI hot plug that were limited to a single device tho=
ugh, so I'm certainly drawing a blank here on what it could be.

On Thu, May 31, 2012 at 8:06 PM, Anil Rao > wrote:
Since I am new to the xen-users list, I was wondering if my question is mor=
e appropriate for the xen-devel list. Any thoughts?

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com; xen-users@lists.=
xen.org

Subject: Re: [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control blade in our router chassis=
 has one of these FPGAs and its primary function is to control certain dedi=
cated hardware components on the blade that are responsible for establishin=
g connectivity with the high-speed inter-blade fabric on the router. I am s=
orry, but I cannot divulge additional details regarding the FPGA.

Here is a more detailed description of my actual usage scenario.

1) The FPGA image must be downloaded onto the device before it can be enabl=
ed for use.
2) The VM in question is responsible for performing step (1), which means t=
hat the FPGA is not visible to Xen/Dom-0 when
    the VM is powered on.
3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci=
-hotplug to assign the device to the VM.
    This operation completes successfully (as reported by the appropriate x=
l command).
4) However, the guest OS inside the VM cannot see the FPGA device after ste=
p (3).
5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th=
e FPGA device (and everything then proceeds normally).

The troublesome part here is that I need to shutdown and restart the VM. I =
would like to avoid this and rely on Xen pci-hotplug to make the device vis=
ible to the guest OS inside the VM.

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve=
lopment board or something already assembled and functioning that contains =
an FPGA device(s)?

Well, just being curious... :)



Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o=
f PCI devices to the VM. The only one that doesn't work is the FPGA device.=
 Even for this one, the only time it doesn't work, is if the VM was powered=
-on prior to the FPGA device being brought on-line on the host. If the FPGA=
 was present before the VM was powered-on everything works as expected.

It somehow seems like new devices that are introduced in the host, after a =
VM has been started on it, cannot be hotplugged into the VM.

Thanks.
-Anil


________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com=
] On Behalf Of John Sherwood
Sent: Wednesday, May 30, 2012 7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Are you sure the guest OS has PCI hotplug support?

On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote:
Hi,

I am trying to assign a FPGA (which is a PCI device) to a running VM. The i=
nteresting thing here is that the FPGA is not present when the VM was power=
ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line=
 on the host by downloading its image to the device.

So far my attempts at using Xen PCI-passthrough have not been successful. A=
lthough Xen reports that the pass-through operation was successful, which I=
 have verified using the appropriate xl command, I am unable to see the FPG=
A from within the guest OS.

I have tried both manual rescanning of the PCI bus inside the guest as well=
 as making use of the pciehp driver. The only way I can (reliably) see the =
FPGA from within the guest, is to shutdown and restart the VM and then redo=
 the hotplug operation. I want to avoid a VM reboot and was wondering if th=
is is at all possible and if so what do I need to do to realize it.

[The virtualization host is based on the default Xen setup that comes with =
SLES 11 SP2]

Thanks for any help on this matter.

-Anil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable







Thanks, John, for your thoughts.

 


The problem is not about a particular PCI device. =
Rather,=20
it seems to affect several different types of devices.=20



 


What I am seeing is this. If a device is added to=
=20
the host "after" a VM has been started on it, any attempt to hotplug t=
hat=20
device to the (already running VM) results in the following.<=
/DIV>

 


   From Xen's point of view the hotplug =
operation=20
is successful. The guest OS in the VM, however, cannot see the=20
device.


 


If the VM was started after the device was added t=
o the=20
host, I don't have a problem.


 


So, once again, this is not particular to a single=
 device.=20
It affects all devices if the condition mentioned above is=20
true.


 


Thanks.


-Anil






From: theubaz@gmail.com=20
[mailto:theubaz@gmail.com] On Behalf Of John Sherwood
Sent:=20
Thursday, May 31, 2012 9:16 PM
To: Anil Rao
Cc:=20
xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA=
 to=20
running VM



If you've never seen this issue before and can't reproduce it wi=
th=20
any other PCI devices, I'd suggest trying the devel mailing list, but I'd f=
irst=20
collect whatever logs you can that are salient to the issue beforehand.=20
 I've never had issues with PCI hot plug that were limited to a single=
=20
device though, so I'm certainly drawing a blank here on what it could=20
be.



On Thu, May 31, 2012 at 8:06 PM, Anil Rao <anil.rao@ericsson.com> wrote:



  

  
Sinc=
e I am new to=20
  the xen-users list, I was wondering if my question is more appropriate fo=
r the=20
  xen-devel list. Any thoughts?

  
 

  
Thanks.

  
-Anil


  

  

  From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
Anil=20
  Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail=
.com;=20
  xen-users@lists.xen.org
  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This=
 is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
 

  
Here is a more detailed description of my actual us=
age=20
  scenario.

  
 

  
1) T=
he FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) T=
he VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
    the VM is powered on.
  
3) A=
fter the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
    This operation completes successfully =
(as=20
  reported by the appropriate xl command).

  
4) H=
owever, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) I=
f I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
 

  
The =
troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
 

  
Thanks.

  
-Anil

  
 

  

  

  

  
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
cyberhawk001@gmail.com
Sent: Thursday, May =
31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-u=
sers]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
Ye=
s, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for thi=
s=20
    one, the only time it doesn't work, is if the VM was powered-on prior t=
o the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
 

    
It=
 somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
 

    
Thanks.

    
-Anil

    
 

    
 

    

    

    

    
From: theubaz@gmail.com=
 [mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re=
:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
 

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
 

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
 

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
 

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
 

      
Thanks for any help on this matter.

      
 

      
-Anil
<=
/BLOCKQUOTE>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users




--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_--


--===============6103302825401753920==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6103302825401753920==--


From xen-users-bounces@lists.xen.org Fri Jun 01 19:15:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 01 Jun 2012 19:15: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 1SaXGy-0002Lo-1o; Fri, 01 Jun 2012 19:12:32 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SaXGw-0002Lj-4B
	for xen-users@lists.xen.org; Fri, 01 Jun 2012 19:12:30 +0000
Received: from [193.109.254.147:21788] by server-7.bemta-14.messagelabs.com id
	54/44-07635-D1419CF4; Fri, 01 Jun 2012 19:12:29 +0000
X-Env-Sender: anil.rao@ericsson.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338577947!12372627!1
X-Originating-IP: [198.24.6.9]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDc0NDU=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27409 invoked from network); 1 Jun 2012 19:12:28 -0000
Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9)
	by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 1 Jun 2012 19:12:28 -0000
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181])
	by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id
	q51JCP4h024808; Fri, 1 Jun 2012 14:12:26 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by
	eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi;
	Fri, 1 Jun 2012 15:12:19 -0400
From: Anil Rao 
To: John Sherwood 
Date: Fri, 1 Jun 2012 15:12:18 -0400
Thread-Topic: [Xen-users] Hotplugging FPGA to running VM
Thread-Index: Ac0/rUGlkC/TnlohSamQWkEOLB9CdQAfJc9w
Message-ID: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
In-Reply-To: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6103302825401753920=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6103302825401753920==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_"

--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, John, for your thoughts.

The problem is not about a particular PCI device. Rather, it seems to affec=
t several different types of devices.

What I am seeing is this. If a device is added to the host "after" a VM has=
 been started on it, any attempt to hotplug that device to the (already run=
ning VM) results in the following.

   From Xen's point of view the hotplug operation is successful. The guest =
OS in the VM, however, cannot see the device.

If the VM was started after the device was added to the host, I don't have =
a problem.

So, once again, this is not particular to a single device. It affects all d=
evices if the condition mentioned above is true.

Thanks.
-Anil

________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com] On Behalf Of John Sherwo=
od
Sent: Thursday, May 31, 2012 9:16 PM
To: Anil Rao
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

If you've never seen this issue before and can't reproduce it with any othe=
r PCI devices, I'd suggest trying the devel mailing list, but I'd first col=
lect whatever logs you can that are salient to the issue beforehand.  I've =
never had issues with PCI hot plug that were limited to a single device tho=
ugh, so I'm certainly drawing a blank here on what it could be.

On Thu, May 31, 2012 at 8:06 PM, Anil Rao > wrote:
Since I am new to the xen-users list, I was wondering if my question is mor=
e appropriate for the xen-devel list. Any thoughts?

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com; xen-users@lists.=
xen.org

Subject: Re: [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control blade in our router chassis=
 has one of these FPGAs and its primary function is to control certain dedi=
cated hardware components on the blade that are responsible for establishin=
g connectivity with the high-speed inter-blade fabric on the router. I am s=
orry, but I cannot divulge additional details regarding the FPGA.

Here is a more detailed description of my actual usage scenario.

1) The FPGA image must be downloaded onto the device before it can be enabl=
ed for use.
2) The VM in question is responsible for performing step (1), which means t=
hat the FPGA is not visible to Xen/Dom-0 when
    the VM is powered on.
3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci=
-hotplug to assign the device to the VM.
    This operation completes successfully (as reported by the appropriate x=
l command).
4) However, the guest OS inside the VM cannot see the FPGA device after ste=
p (3).
5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th=
e FPGA device (and everything then proceeds normally).

The troublesome part here is that I need to shutdown and restart the VM. I =
would like to avoid this and rely on Xen pci-hotplug to make the device vis=
ible to the guest OS inside the VM.

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve=
lopment board or something already assembled and functioning that contains =
an FPGA device(s)?

Well, just being curious... :)



Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o=
f PCI devices to the VM. The only one that doesn't work is the FPGA device.=
 Even for this one, the only time it doesn't work, is if the VM was powered=
-on prior to the FPGA device being brought on-line on the host. If the FPGA=
 was present before the VM was powered-on everything works as expected.

It somehow seems like new devices that are introduced in the host, after a =
VM has been started on it, cannot be hotplugged into the VM.

Thanks.
-Anil


________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com=
] On Behalf Of John Sherwood
Sent: Wednesday, May 30, 2012 7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Are you sure the guest OS has PCI hotplug support?

On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote:
Hi,

I am trying to assign a FPGA (which is a PCI device) to a running VM. The i=
nteresting thing here is that the FPGA is not present when the VM was power=
ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line=
 on the host by downloading its image to the device.

So far my attempts at using Xen PCI-passthrough have not been successful. A=
lthough Xen reports that the pass-through operation was successful, which I=
 have verified using the appropriate xl command, I am unable to see the FPG=
A from within the guest OS.

I have tried both manual rescanning of the PCI bus inside the guest as well=
 as making use of the pciehp driver. The only way I can (reliably) see the =
FPGA from within the guest, is to shutdown and restart the VM and then redo=
 the hotplug operation. I want to avoid a VM reboot and was wondering if th=
is is at all possible and if so what do I need to do to realize it.

[The virtualization host is based on the default Xen setup that comes with =
SLES 11 SP2]

Thanks for any help on this matter.

-Anil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable







Thanks, John, for your thoughts.

 


The problem is not about a particular PCI device. =
Rather,=20
it seems to affect several different types of devices.=20



 


What I am seeing is this. If a device is added to=
=20
the host "after" a VM has been started on it, any attempt to hotplug t=
hat=20
device to the (already running VM) results in the following.<=
/DIV>

 


   From Xen's point of view the hotplug =
operation=20
is successful. The guest OS in the VM, however, cannot see the=20
device.


 


If the VM was started after the device was added t=
o the=20
host, I don't have a problem.


 


So, once again, this is not particular to a single=
 device.=20
It affects all devices if the condition mentioned above is=20
true.


 


Thanks.


-Anil






From: theubaz@gmail.com=20
[mailto:theubaz@gmail.com] On Behalf Of John Sherwood
Sent:=20
Thursday, May 31, 2012 9:16 PM
To: Anil Rao
Cc:=20
xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA=
 to=20
running VM



If you've never seen this issue before and can't reproduce it wi=
th=20
any other PCI devices, I'd suggest trying the devel mailing list, but I'd f=
irst=20
collect whatever logs you can that are salient to the issue beforehand.=20
 I've never had issues with PCI hot plug that were limited to a single=
=20
device though, so I'm certainly drawing a blank here on what it could=20
be.



On Thu, May 31, 2012 at 8:06 PM, Anil Rao <anil.rao@ericsson.com> wrote:



  

  
Sinc=
e I am new to=20
  the xen-users list, I was wondering if my question is more appropriate fo=
r the=20
  xen-devel list. Any thoughts?

  
 

  
Thanks.

  
-Anil


  

  

  From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
Anil=20
  Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail=
.com;=20
  xen-users@lists.xen.org
  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This=
 is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
 

  
Here is a more detailed description of my actual us=
age=20
  scenario.

  
 

  
1) T=
he FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) T=
he VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
    the VM is powered on.
  
3) A=
fter the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
    This operation completes successfully =
(as=20
  reported by the appropriate xl command).

  
4) H=
owever, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) I=
f I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
 

  
The =
troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
 

  
Thanks.

  
-Anil

  
 

  

  

  

  
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
cyberhawk001@gmail.com
Sent: Thursday, May =
31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-u=
sers]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
Ye=
s, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for thi=
s=20
    one, the only time it doesn't work, is if the VM was powered-on prior t=
o the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
 

    
It=
 somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
 

    
Thanks.

    
-Anil

    
 

    
 

    

    

    

    
From: theubaz@gmail.com=
 [mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re=
:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
 

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
 

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
 

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
 

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
 

      
Thanks for any help on this matter.

      
 

      
-Anil
<=
/BLOCKQUOTE>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users




--_000_DD729E174A25344F8D7D351BA4CF57272DAD45D535EUSAACMS0715e_--


--===============6103302825401753920==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6103302825401753920==--


From xen-users-bounces@lists.xen.org Sat Jun 02 20:37:38 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 02 Jun 2012 20:37:38 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sav2t-0006ed-Jf; Sat, 02 Jun 2012 20:35:35 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sav2r-0006eY-Bf
	for xen-users@lists.xen.org; Sat, 02 Jun 2012 20:35:33 +0000
Received: from [85.158.138.51:37986] by server-3.bemta-3.messagelabs.com id
	09/B6-15793-4197ACF4; Sat, 02 Jun 2012 20:35:32 +0000
X-Env-Sender: rarts@theipcompany.nl
X-Msg-Ref: server-11.tower-174.messagelabs.com!1338669331!30499835!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16654 invoked from network); 2 Jun 2012 20:35:31 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Jun 2012 20:35:31 -0000
Received: by werf3 with SMTP id f3so2525675wer.32
	for ; Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject
	:content-type:content-transfer-encoding:x-gm-message-state;
	bh=COKo1+TSuYDUzvkf3QVWdPraY5ntrQEg9mBrvrbD40U=;
	b=XQZ18WetYtIUTvJbt9sR8eUQSIiWUqz1l5sjyNKyMFDucnRZ0PWhT5GhcsySsOhJ5T
	tgGQQeiDgDlr+h0vdr01U+F5ERJVefNjLW5U/N2dx35bSO2pR6gtY9CgLJPGKeOzN+mJ
	JnCiEhaZv6X/r511DI38PFua0OWYt06jg0cjClSPmzVmXb9hBFMumBNLj3/Suw/71vOk
	NagZEPYh6dobRTxnTUVYKv0Ue0Rj1vDKOPZVnzkYSKJZTp5vkLzLLPB6jC0vJK+WArM4
	5Hs80t4hX1nygyOevmFwh1e14CsD7YlIaNf+jqnuIIGUR+alngVHuMtotjG8u8Z8kmiu
	KSNw==
Received: by 10.216.142.194 with SMTP id i44mr6300810wej.88.1338669330548;
	Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
Received: from MacBook-Air-van-Ron.local (31-151-107-141.dynamic.upc.nl.
	[31.151.107.141])
	by mx.google.com with ESMTPS id et10sm7410363wib.2.2012.06.02.13.35.29
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
Message-ID: <4FCA7911.2030905@oneip.nl>
Date: Sat, 02 Jun 2012 22:35:29 +0200
From: Ron Arts 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQnPwgt9Th4Dk6EMAg7lVon4b3sLy7/EdLFr9/R+Bz5zxO39RXP0TjKjjGcWKou7425lIWRm
Subject: [Xen-users] Redundant setup across two datacenters with two XCP
	hosts
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello all,

I am looking to run only 1 VM on this setup, don't need to do live migration,
although that would be nice, I just want to protect against hardware and
datacenter/network failure. The VM is lightly loaded, not much disk I/O or
CPU load.

I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.
(There is a simple RAID-1 SATA hardware controller on board).

I am willing to spend the time to configure these machines, but buying
extra hardware is pretty much out of the question.

Would it be possible to create a configuration where these two machines
could span two datacenters in a redundant way?

thanks for any insights,
Ron


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Jun 02 20:37:38 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 02 Jun 2012 20:37:38 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sav2t-0006ed-Jf; Sat, 02 Jun 2012 20:35:35 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sav2r-0006eY-Bf
	for xen-users@lists.xen.org; Sat, 02 Jun 2012 20:35:33 +0000
Received: from [85.158.138.51:37986] by server-3.bemta-3.messagelabs.com id
	09/B6-15793-4197ACF4; Sat, 02 Jun 2012 20:35:32 +0000
X-Env-Sender: rarts@theipcompany.nl
X-Msg-Ref: server-11.tower-174.messagelabs.com!1338669331!30499835!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16654 invoked from network); 2 Jun 2012 20:35:31 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Jun 2012 20:35:31 -0000
Received: by werf3 with SMTP id f3so2525675wer.32
	for ; Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject
	:content-type:content-transfer-encoding:x-gm-message-state;
	bh=COKo1+TSuYDUzvkf3QVWdPraY5ntrQEg9mBrvrbD40U=;
	b=XQZ18WetYtIUTvJbt9sR8eUQSIiWUqz1l5sjyNKyMFDucnRZ0PWhT5GhcsySsOhJ5T
	tgGQQeiDgDlr+h0vdr01U+F5ERJVefNjLW5U/N2dx35bSO2pR6gtY9CgLJPGKeOzN+mJ
	JnCiEhaZv6X/r511DI38PFua0OWYt06jg0cjClSPmzVmXb9hBFMumBNLj3/Suw/71vOk
	NagZEPYh6dobRTxnTUVYKv0Ue0Rj1vDKOPZVnzkYSKJZTp5vkLzLLPB6jC0vJK+WArM4
	5Hs80t4hX1nygyOevmFwh1e14CsD7YlIaNf+jqnuIIGUR+alngVHuMtotjG8u8Z8kmiu
	KSNw==
Received: by 10.216.142.194 with SMTP id i44mr6300810wej.88.1338669330548;
	Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
Received: from MacBook-Air-van-Ron.local (31-151-107-141.dynamic.upc.nl.
	[31.151.107.141])
	by mx.google.com with ESMTPS id et10sm7410363wib.2.2012.06.02.13.35.29
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sat, 02 Jun 2012 13:35:30 -0700 (PDT)
Message-ID: <4FCA7911.2030905@oneip.nl>
Date: Sat, 02 Jun 2012 22:35:29 +0200
From: Ron Arts 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQnPwgt9Th4Dk6EMAg7lVon4b3sLy7/EdLFr9/R+Bz5zxO39RXP0TjKjjGcWKou7425lIWRm
Subject: [Xen-users] Redundant setup across two datacenters with two XCP
	hosts
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello all,

I am looking to run only 1 VM on this setup, don't need to do live migration,
although that would be nice, I just want to protect against hardware and
datacenter/network failure. The VM is lightly loaded, not much disk I/O or
CPU load.

I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.
(There is a simple RAID-1 SATA hardware controller on board).

I am willing to spend the time to configure these machines, but buying
extra hardware is pretty much out of the question.

Would it be possible to create a configuration where these two machines
could span two datacenters in a redundant way?

thanks for any insights,
Ron


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Jun 02 20:41:43 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 02 Jun 2012 20:41:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sav6g-0006o7-Fr; Sat, 02 Jun 2012 20:39:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sav6f-0006o0-Ca
	for xen-users@lists.xen.org; Sat, 02 Jun 2012 20:39:29 +0000
Received: from [85.158.138.51:64649] by server-1.bemta-3.messagelabs.com id
	EE/80-06526-00A7ACF4; Sat, 02 Jun 2012 20:39:28 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-11.tower-174.messagelabs.com!1338669566!30500033!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19376 invoked from network); 2 Jun 2012 20:39:27 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Jun 2012 20:39:27 -0000
Received: by obbwd20 with SMTP id wd20so6304505obb.32
	for ; Sat, 02 Jun 2012 13:39:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=HIetXVsZminFiTZNRDJzQVW488aljmsMzbPIuzJ269s=;
	b=ukF2mcV5rr+kUHRBUdfcRzDoVaMZ0Wrpm/P9Blwq6Qz5Z7fwZ9VESddF8Xk46wz34p
	VA4nsyQcpVsvBH3mvA5LdGqD0G7/43DQBA6GMI74PuA2aDNidgL73/MzNwdz25WSHBNq
	NF2ut9JJ1iQdzk5jP26igLfo3Yk9UHNRwdf8XCYQog7ME1zdQc3T3AvgULWH8lOFTNpt
	KHE+WI0IfX/Qe3adlmkih6BSru+DKfsZPuiUHire4f1g1t5zf7h/esC6gO8ZBlIgFLCG
	V1+eeVBZsV7dOJIuMqikgZvRp5u1t/Q4ASf0sWrjlZyZ0wfYkTchF1UthBWae/bz8c4h
	2XMw==
MIME-Version: 1.0
Received: by 10.50.191.200 with SMTP id ha8mr4862883igc.45.1338669565605; Sat,
	02 Jun 2012 13:39:25 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Sat, 2 Jun 2012 13:39:25 -0700 (PDT)
In-Reply-To: <4FCA7911.2030905@oneip.nl>
References: <4FCA7911.2030905@oneip.nl>
Date: Sat, 2 Jun 2012 16:39:25 -0400
X-Google-Sender-Auth: 8efkyBn0wuCi685VTBzPtPmEHfo
Message-ID: 
From: John Sherwood 
To: Ron Arts 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Redundant setup across two datacenters with two XCP
	hosts
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6754835281755637762=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6754835281755637762==
Content-Type: multipart/alternative; boundary=14dae9340fd9edf8ad04c1834be4

--14dae9340fd9edf8ad04c1834be4
Content-Type: text/plain; charset=ISO-8859-1

It sounds like you want to try setting up Remus, though I'm not sure how
well that would work with hosts running in different datacenters.

On Sat, Jun 2, 2012 at 4:35 PM, Ron Arts  wrote:

> Hello all,
>
> I am looking to run only 1 VM on this setup, don't need to do live
> migration,
> although that would be nice, I just want to protect against hardware and
> datacenter/network failure. The VM is lightly loaded, not much disk I/O or
> CPU load.
>
> I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.
> (There is a simple RAID-1 SATA hardware controller on board).
>
> I am willing to spend the time to configure these machines, but buying
> extra hardware is pretty much out of the question.
>
> Would it be possible to create a configuration where these two machines
> could span two datacenters in a redundant way?
>
> thanks for any insights,
> Ron
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--14dae9340fd9edf8ad04c1834be4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It sounds like you want to try setting up Remus, though I'm not sure ho=
w well that would work with hosts running in different datacenters.

=

On Sat, Jun 2, 2012 at 4:35 PM, Ron Arts <ron.a=
rts@oneip.nl> wrote:


Hello all,



I am looking to run only 1 VM on this setup, don't need to do live migr=
ation,

although that would be nice, I just want to protect against hardware and
datacenter/network failure. The VM is lightly loaded, not much disk I/O or<=
br>
CPU load.



I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.

(There is a simple RAID-1 SATA hardware controller on board).



I am willing to spend the time to configure these machines, but buying

extra hardware is pretty much out of the question.



Would it be possible to create a configuration where these two machines

could span two datacenters in a redundant way?



thanks for any insights,

Ron





_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9340fd9edf8ad04c1834be4--


--===============6754835281755637762==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6754835281755637762==--


From xen-users-bounces@lists.xen.org Sat Jun 02 20:41:43 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 02 Jun 2012 20:41:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sav6g-0006o7-Fr; Sat, 02 Jun 2012 20:39:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sav6f-0006o0-Ca
	for xen-users@lists.xen.org; Sat, 02 Jun 2012 20:39:29 +0000
Received: from [85.158.138.51:64649] by server-1.bemta-3.messagelabs.com id
	EE/80-06526-00A7ACF4; Sat, 02 Jun 2012 20:39:28 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-11.tower-174.messagelabs.com!1338669566!30500033!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19376 invoked from network); 2 Jun 2012 20:39:27 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Jun 2012 20:39:27 -0000
Received: by obbwd20 with SMTP id wd20so6304505obb.32
	for ; Sat, 02 Jun 2012 13:39:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=HIetXVsZminFiTZNRDJzQVW488aljmsMzbPIuzJ269s=;
	b=ukF2mcV5rr+kUHRBUdfcRzDoVaMZ0Wrpm/P9Blwq6Qz5Z7fwZ9VESddF8Xk46wz34p
	VA4nsyQcpVsvBH3mvA5LdGqD0G7/43DQBA6GMI74PuA2aDNidgL73/MzNwdz25WSHBNq
	NF2ut9JJ1iQdzk5jP26igLfo3Yk9UHNRwdf8XCYQog7ME1zdQc3T3AvgULWH8lOFTNpt
	KHE+WI0IfX/Qe3adlmkih6BSru+DKfsZPuiUHire4f1g1t5zf7h/esC6gO8ZBlIgFLCG
	V1+eeVBZsV7dOJIuMqikgZvRp5u1t/Q4ASf0sWrjlZyZ0wfYkTchF1UthBWae/bz8c4h
	2XMw==
MIME-Version: 1.0
Received: by 10.50.191.200 with SMTP id ha8mr4862883igc.45.1338669565605; Sat,
	02 Jun 2012 13:39:25 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Sat, 2 Jun 2012 13:39:25 -0700 (PDT)
In-Reply-To: <4FCA7911.2030905@oneip.nl>
References: <4FCA7911.2030905@oneip.nl>
Date: Sat, 2 Jun 2012 16:39:25 -0400
X-Google-Sender-Auth: 8efkyBn0wuCi685VTBzPtPmEHfo
Message-ID: 
From: John Sherwood 
To: Ron Arts 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Redundant setup across two datacenters with two XCP
	hosts
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6754835281755637762=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6754835281755637762==
Content-Type: multipart/alternative; boundary=14dae9340fd9edf8ad04c1834be4

--14dae9340fd9edf8ad04c1834be4
Content-Type: text/plain; charset=ISO-8859-1

It sounds like you want to try setting up Remus, though I'm not sure how
well that would work with hosts running in different datacenters.

On Sat, Jun 2, 2012 at 4:35 PM, Ron Arts  wrote:

> Hello all,
>
> I am looking to run only 1 VM on this setup, don't need to do live
> migration,
> although that would be nice, I just want to protect against hardware and
> datacenter/network failure. The VM is lightly loaded, not much disk I/O or
> CPU load.
>
> I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.
> (There is a simple RAID-1 SATA hardware controller on board).
>
> I am willing to spend the time to configure these machines, but buying
> extra hardware is pretty much out of the question.
>
> Would it be possible to create a configuration where these two machines
> could span two datacenters in a redundant way?
>
> thanks for any insights,
> Ron
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--14dae9340fd9edf8ad04c1834be4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It sounds like you want to try setting up Remus, though I'm not sure ho=
w well that would work with hosts running in different datacenters.

=

On Sat, Jun 2, 2012 at 4:35 PM, Ron Arts <ron.a=
rts@oneip.nl> wrote:


Hello all,



I am looking to run only 1 VM on this setup, don't need to do live migr=
ation,

although that would be nice, I just want to protect against hardware and
datacenter/network failure. The VM is lightly loaded, not much disk I/O or<=
br>
CPU load.



I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB.

(There is a simple RAID-1 SATA hardware controller on board).



I am willing to spend the time to configure these machines, but buying

extra hardware is pretty much out of the question.



Would it be possible to create a configuration where these two machines

could span two datacenters in a redundant way?



thanks for any insights,

Ron





_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9340fd9edf8ad04c1834be4--


--===============6754835281755637762==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6754835281755637762==--


From xen-users-bounces@lists.xen.org Sun Jun 03 05:47:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 05:47: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 1Sb3dN-0001JW-DL; Sun, 03 Jun 2012 05:45:49 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sb3dL-0001JQ-OR
	for xen-users@lists.xensource.com; Sun, 03 Jun 2012 05:45:48 +0000
Received: from [85.158.138.51:26616] by server-8.bemta-3.messagelabs.com id
	3E/87-01456-A0AFACF4; Sun, 03 Jun 2012 05:45:46 +0000
X-Env-Sender: andrewx192@gmail.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338702343!30621918!1
X-Originating-IP: [209.85.210.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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30975 invoked from network); 3 Jun 2012 05:45:45 -0000
Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com)
	(209.85.210.43)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	3 Jun 2012 05:45:45 -0000
Received: by dajz8 with SMTP id z8so5119417daj.30
	for ;
	Sat, 02 Jun 2012 22:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:from:reply-to:to:content-type:date:message-id:mime-version
	:x-mailer; bh=GgCw/OFCU8rVsO6dHnLa4gWZRt7aiitsCTFD9Fww0GU=;
	b=x80LJssq5PXuhY7iRRLn42WO0bj8rfuuh3kSgCSfIQ/G8hD1SnW+s0WhqXo7dlyJnd
	WnshZDrn1vQzQnsiMJQ5aWXIfxNCeuejT4a3w09+C9UTXs9E6XgLfaF0/M+wyBroSLZG
	UU9CjEMw+auQhFBCvtIlZre7hbfc25mgAJKEW+8GUHTsh64WHxTTN8FlbYf8/GA4/g+g
	MaJbBew3UX/A1e1PvspcK5ENapduarMHH2VsLNZ5JN6QFoBqIDAT6m0gFtupCm96m46J
	GqXTeF75DUacdDDWq/DOXYl4wEn8Jagi/W8X3uGlY7Y5veGjII/VSflvXoRAEvgcbUB8
	OHfQ==
Received: by 10.68.223.129 with SMTP id qu1mr25921689pbc.165.1338702343297;
	Sat, 02 Jun 2012 22:45:43 -0700 (PDT)
Received: from [172.16.50.1] (002369d5e799.click-network.com. [131.191.22.34])
	by mx.google.com with ESMTPS id
	vi10sm8646545pbc.4.2012.06.02.22.45.35 (version=SSLv3 cipher=OTHER);
	Sat, 02 Jun 2012 22:45:41 -0700 (PDT)
From: Andrew Sorensen 
To: "Xen-users@lists.xensource.com" 
Date: Sat, 02 Jun 2012 22:45:26 -0700
Message-ID: <1338702326.6450.558.camel@WLN-MSI-201101>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Subject: [Xen-users] Xen on a laptop
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: andrewx192@gmail.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1504441267252765088=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org


--===============1504441267252765088==
Content-Type: multipart/alternative; boundary="=-typv/ryYVJ7LNMJOyTmC"


--=-typv/ryYVJ7LNMJOyTmC
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

I am looking to purchase a new laptop quite soon, and intend to run a
number of virtual machines.

Since I am currently running Xen as my choice of virtualization on other
machines, I would like to run Xen on the laptop. 
Most of the DomU instances on the machine will be purely console, and
pretty straightforward in Xen to setup(DB / Web / etc) servers, however
I would also like to have Windows ready to use.

Here are some of the issues I can see with this sort of setup:

1) Suspend to disk/ram not working -- I figure I would at least need to
hook up my main DomU to handle ACPI events (can I pass through these?)
to tell the Dom0 what to do.

2) Optimus and VGA passthrough (not sure how this would work).

3) Wireless and networking -- I figure I would probably have a single
DomU to handle networking, and passthrough my network cards to this
machine - the guests would then access the network through the DomU.

4) Disk IO issues -- I will probably be getting a SSD to boot from
(mSATA), and then an Intel 520 SSD to run all my machines off of. Data
would be stored on a 500GB HDD in place of the optical drive.

5) Power management -- I would probably automate suspending of DomU
instances when the laptop is running on battery power, though this is
not a huge concern.

6) Windows DomU: I would like to run Windows in addition to Linux, at
the same time - and basically be able to switch between the instances. I
assume I would need to switch the active VGA passthrough somehow (or
secondary virtualization: VMWare Workstation?)

7) USB3 passthrough (I heard this not possible?) - I think I might be
able to use "usbnet" to solve this issue.

Has anyone successfully installed and operated Xen on a laptop, or have
suggestions/answers to the above?

The laptop I am considering is
http://web.eurocom.com/EC/ec_model_config1(1,225,0) if it matters in any
way.


-- 
Andrew Sorensen
Twitter: http://twitter.com/AndrewX192 
Google+: https://plus.google.com/u/0/115244690052850979822/


--=-typv/ryYVJ7LNMJOyTmC
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit




  
  


I am looking to purchase a new laptop quite soon, and intend to run a number of virtual machines.



Since I am currently running Xen as my choice of virtualization on other machines, I would like to run Xen on the laptop. 

Most of the DomU instances on the machine will be purely console, and pretty straightforward in Xen to setup(DB / Web / etc) servers, however I would also like to have Windows ready to use.



Here are some of the issues I can see with this sort of setup:



1) Suspend to disk/ram not working -- I figure I would at least need to hook up my main DomU to handle ACPI events (can I pass through these?) to tell the Dom0 what to do.



2) Optimus and VGA passthrough (not sure how this would work).



3) Wireless and networking -- I figure I would probably have a single DomU to handle networking, and passthrough my network cards to this machine - the guests would then access the network through the DomU.



4) Disk IO issues -- I will probably be getting a SSD to boot from (mSATA), and then an Intel 520 SSD to run all my machines off of. Data would be stored on a 500GB HDD in place of the optical drive.



5) Power management -- I would probably automate suspending of DomU instances when the laptop is running on battery power, though this is not a huge concern.



6) Windows DomU: I would like to run Windows in addition to Linux, at the same time - and basically be able to switch between the instances. I assume I would need to switch the active VGA passthrough somehow (or secondary virtualization: VMWare Workstation?)



7) USB3 passthrough (I heard this not possible?) - I think I might be able to use "usbnet" to solve this issue.



Has anyone successfully installed and operated Xen on a laptop, or have suggestions/answers to the above?



The laptop I am considering is http://web.eurocom.com/EC/ec_model_config1(1,225,0) if it matters in any way.










-- 

Andrew Sorensen

Twitter: http://twitter.com/AndrewX192 

Google+: https://plus.google.com/u/0/115244690052850979822/











--=-typv/ryYVJ7LNMJOyTmC--



--===============1504441267252765088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1504441267252765088==--



From xen-users-bounces@lists.xen.org Sun Jun 03 05:47:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 05:47: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 1Sb3dN-0001JW-DL; Sun, 03 Jun 2012 05:45:49 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sb3dL-0001JQ-OR
	for xen-users@lists.xensource.com; Sun, 03 Jun 2012 05:45:48 +0000
Received: from [85.158.138.51:26616] by server-8.bemta-3.messagelabs.com id
	3E/87-01456-A0AFACF4; Sun, 03 Jun 2012 05:45:46 +0000
X-Env-Sender: andrewx192@gmail.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338702343!30621918!1
X-Originating-IP: [209.85.210.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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30975 invoked from network); 3 Jun 2012 05:45:45 -0000
Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com)
	(209.85.210.43)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	3 Jun 2012 05:45:45 -0000
Received: by dajz8 with SMTP id z8so5119417daj.30
	for ;
	Sat, 02 Jun 2012 22:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:from:reply-to:to:content-type:date:message-id:mime-version
	:x-mailer; bh=GgCw/OFCU8rVsO6dHnLa4gWZRt7aiitsCTFD9Fww0GU=;
	b=x80LJssq5PXuhY7iRRLn42WO0bj8rfuuh3kSgCSfIQ/G8hD1SnW+s0WhqXo7dlyJnd
	WnshZDrn1vQzQnsiMJQ5aWXIfxNCeuejT4a3w09+C9UTXs9E6XgLfaF0/M+wyBroSLZG
	UU9CjEMw+auQhFBCvtIlZre7hbfc25mgAJKEW+8GUHTsh64WHxTTN8FlbYf8/GA4/g+g
	MaJbBew3UX/A1e1PvspcK5ENapduarMHH2VsLNZ5JN6QFoBqIDAT6m0gFtupCm96m46J
	GqXTeF75DUacdDDWq/DOXYl4wEn8Jagi/W8X3uGlY7Y5veGjII/VSflvXoRAEvgcbUB8
	OHfQ==
Received: by 10.68.223.129 with SMTP id qu1mr25921689pbc.165.1338702343297;
	Sat, 02 Jun 2012 22:45:43 -0700 (PDT)
Received: from [172.16.50.1] (002369d5e799.click-network.com. [131.191.22.34])
	by mx.google.com with ESMTPS id
	vi10sm8646545pbc.4.2012.06.02.22.45.35 (version=SSLv3 cipher=OTHER);
	Sat, 02 Jun 2012 22:45:41 -0700 (PDT)
From: Andrew Sorensen 
To: "Xen-users@lists.xensource.com" 
Date: Sat, 02 Jun 2012 22:45:26 -0700
Message-ID: <1338702326.6450.558.camel@WLN-MSI-201101>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Subject: [Xen-users] Xen on a laptop
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: andrewx192@gmail.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1504441267252765088=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org


--===============1504441267252765088==
Content-Type: multipart/alternative; boundary="=-typv/ryYVJ7LNMJOyTmC"


--=-typv/ryYVJ7LNMJOyTmC
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

I am looking to purchase a new laptop quite soon, and intend to run a
number of virtual machines.

Since I am currently running Xen as my choice of virtualization on other
machines, I would like to run Xen on the laptop. 
Most of the DomU instances on the machine will be purely console, and
pretty straightforward in Xen to setup(DB / Web / etc) servers, however
I would also like to have Windows ready to use.

Here are some of the issues I can see with this sort of setup:

1) Suspend to disk/ram not working -- I figure I would at least need to
hook up my main DomU to handle ACPI events (can I pass through these?)
to tell the Dom0 what to do.

2) Optimus and VGA passthrough (not sure how this would work).

3) Wireless and networking -- I figure I would probably have a single
DomU to handle networking, and passthrough my network cards to this
machine - the guests would then access the network through the DomU.

4) Disk IO issues -- I will probably be getting a SSD to boot from
(mSATA), and then an Intel 520 SSD to run all my machines off of. Data
would be stored on a 500GB HDD in place of the optical drive.

5) Power management -- I would probably automate suspending of DomU
instances when the laptop is running on battery power, though this is
not a huge concern.

6) Windows DomU: I would like to run Windows in addition to Linux, at
the same time - and basically be able to switch between the instances. I
assume I would need to switch the active VGA passthrough somehow (or
secondary virtualization: VMWare Workstation?)

7) USB3 passthrough (I heard this not possible?) - I think I might be
able to use "usbnet" to solve this issue.

Has anyone successfully installed and operated Xen on a laptop, or have
suggestions/answers to the above?

The laptop I am considering is
http://web.eurocom.com/EC/ec_model_config1(1,225,0) if it matters in any
way.


-- 
Andrew Sorensen
Twitter: http://twitter.com/AndrewX192 
Google+: https://plus.google.com/u/0/115244690052850979822/


--=-typv/ryYVJ7LNMJOyTmC
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit




  
  


I am looking to purchase a new laptop quite soon, and intend to run a number of virtual machines.



Since I am currently running Xen as my choice of virtualization on other machines, I would like to run Xen on the laptop. 

Most of the DomU instances on the machine will be purely console, and pretty straightforward in Xen to setup(DB / Web / etc) servers, however I would also like to have Windows ready to use.



Here are some of the issues I can see with this sort of setup:



1) Suspend to disk/ram not working -- I figure I would at least need to hook up my main DomU to handle ACPI events (can I pass through these?) to tell the Dom0 what to do.



2) Optimus and VGA passthrough (not sure how this would work).



3) Wireless and networking -- I figure I would probably have a single DomU to handle networking, and passthrough my network cards to this machine - the guests would then access the network through the DomU.



4) Disk IO issues -- I will probably be getting a SSD to boot from (mSATA), and then an Intel 520 SSD to run all my machines off of. Data would be stored on a 500GB HDD in place of the optical drive.



5) Power management -- I would probably automate suspending of DomU instances when the laptop is running on battery power, though this is not a huge concern.



6) Windows DomU: I would like to run Windows in addition to Linux, at the same time - and basically be able to switch between the instances. I assume I would need to switch the active VGA passthrough somehow (or secondary virtualization: VMWare Workstation?)



7) USB3 passthrough (I heard this not possible?) - I think I might be able to use "usbnet" to solve this issue.



Has anyone successfully installed and operated Xen on a laptop, or have suggestions/answers to the above?



The laptop I am considering is http://web.eurocom.com/EC/ec_model_config1(1,225,0) if it matters in any way.










-- 

Andrew Sorensen

Twitter: http://twitter.com/AndrewX192 

Google+: https://plus.google.com/u/0/115244690052850979822/











--=-typv/ryYVJ7LNMJOyTmC--



--===============1504441267252765088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1504441267252765088==--



From xen-users-bounces@lists.xen.org Sun Jun 03 15:31:47 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 15:31: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 1SbCkX-0007iG-Vc; Sun, 03 Jun 2012 15:29:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbCkW-0007iB-7K
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 15:29:48 +0000
Received: from [85.158.143.99:33535] by server-1.bemta-4.messagelabs.com id
	2E/2B-27869-BE28BCF4; Sun, 03 Jun 2012 15:29:47 +0000
X-Env-Sender: werner@xxlwade.de
X-Msg-Ref: server-4.tower-216.messagelabs.com!1338737376!25862281!1
X-Originating-IP: [88.198.0.151]
X-SpamReason: No, hits=3.4 required=7.0 tests=HELO_DYNAMIC_IPADDR
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25990 invoked from network); 3 Jun 2012 15:29:36 -0000
Received: from static.88-198-0-151.clients.your-server.de (HELO
	static-ip-217-172-170-8.inaddr.intergenia.de) (88.198.0.151)
	by server-4.tower-216.messagelabs.com with SMTP;
	3 Jun 2012 15:29:36 -0000
Received: from [192.168.1.2] (localhost [127.0.0.1])
	by static-ip-217-172-170-8.inaddr.intergenia.de (Postfix) with ESMTPA
	id 930AE16273
	for ; Sun,  3 Jun 2012 17:29:34 +0200 (CEST)
Message-ID: <4FCB82DE.4080506@xxlwade.de>
Date: Sun, 03 Jun 2012 17:29:34 +0200
From: Werner Fehn 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] need to load uhci_hcd with acpi=off
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Dear all,

I have running a DOM-0 on debian squeeze with the most recent kernel:

Linux 2.6.32-5-xen-amd64 #1 SMP

On 30% of all reboots the system hangs and only a reset helps.

acpi=off as an additional kernel parameter solves this problem, but
the usb keyboard of the installed ip-kvm is not found then.

with acpi=off Ican find a lot stuff like:

[    7.098747] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.098759] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned 
bus number 1
[    7.098784] uhci_hcd 0000:00:1d.2: request interrupt 14 failed
[    7.098821] uhci_hcd 0000:00:1d.2: USB bus 1 deregistered
[    7.098833] uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -38
[    7.098871] uhci_hcd: probe of 0000:00:1d.2 failed with error -38

looks like a dead look. without acpi=off the system hangs sometimes.
with the parameter i have no access via my ip-kvm (it is a remote 
machine in a farm).

With acpi=off I can reproduce the *hci_hcd error on a system in my home, 
but on this machine reboot runs fine also without acpi=off.

Seems I need acpi=off, but I need to load *hci_hcd to get access to the 
usb-ip-kvm-keyboard.

What I tried:
- thousands of BIOS IRQ/PnP parameters => no luck
- noacpi => kernel panic
- irq=biosirq => no change

Any more idea to get the IRQ with acpi=off parameter set?

Best Regards
Werner

complete dmesg:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-44) 
(dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat May 
5 04:18:09 UTC 2012
[    0.000000] Command line: placeholder 
root=UUID=8622e268-8845-4cd5-82b3-e7fd0568c602 ro quiet acpi=off
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] xen_release_chunk: looking at area pfn bf7e0-bf7ec: 12 
pages freed
[    0.000000] xen_release_chunk: looking at area pfn c0000-fec00: 
257024 pages freed
[    0.000000] xen_release_chunk: looking at area pfn fec01-fee00: 511 
pages freed
[    0.000000] xen_release_chunk: looking at area pfn fee01-ffc00: 3583 
pages freed
[    0.000000] released 261130 pages of unused memory
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009ec00 (usable)
[    0.000000]  Xen: 000000000009ec00 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 00000000bf780000 (usable)
[    0.000000]  Xen: 00000000bf780000 - 00000000bf78e000 (ACPI data)
[    0.000000]  Xen: 00000000bf78e000 - 00000000bf7d0000 (ACPI NVS)
[    0.000000]  Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[    0.000000]  Xen: 00000000bf7ec000 - 00000000c0000000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  Xen: 00000000ffc00000 - 0000000100000000 (reserved)
[    0.000000]  Xen: 0000000100000000 - 00000005e6891000 (usable)
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working 
around it.
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 
(usable) ==> (reserved)
[    0.000000] last_pfn = 0x5e6891 max_arch_pfn = 0x400000000
[    0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 
0x7010600070106
[    0.000000] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000bf780000
[    0.000000]  0000000000 - 00bf780000 page 4k
[    0.000000] kernel direct mapping tables up to bf780000 @ 100000-700000
[    0.000000] init_memory_mapping: 0000000100000000-00000005e6891000
[    0.000000]  0100000000 - 05e6891000 page 4k
[    0.000000] kernel direct mapping tables up to 5e6891000 @ 
6384000-92d2000
[    0.000000] RAMDISK: 01708000 - 03416a00
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-00000005e6891000
[    0.000000] Bootmem setup node 0 0000000000000000-00000005e6891000
[    0.000000]   NODE_DATA [0000000000010000 - 0000000000017fff]
[    0.000000]   bootmap [00000000006c6000 -  0000000000782d17] pages bd
[    0.000000] (9 early reservations) ==> bootmem [0000000000 - 05e6891000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> 
[0000000000 - 0000001000]
[    0.000000]   #1 [000634d000 - 0006384000]   XEN PAGETABLES ==> 
[000634d000 - 0006384000]
[    0.000000]   #2 [0000006000 - 0000008000]       TRAMPOLINE ==> 
[0000006000 - 0000008000]
[    0.000000]   #3 [0001000000 - 00016e7b44]    TEXT DATA BSS ==> 
[0001000000 - 00016e7b44]
[    0.000000]   #4 [0001708000 - 0003416a00]          RAMDISK ==> 
[0001708000 - 0003416a00]
[    0.000000]   #5 [0003417000 - 000634d000]   XEN START INFO ==> 
[0003417000 - 000634d000]
[    0.000000]   #6 [00016e8000 - 00016e812b]              BRK ==> 
[00016e8000 - 00016e812b]
[    0.000000]   #7 [0000100000 - 00006c6000]          PGTABLE ==> 
[0000100000 - 00006c6000]
[    0.000000]   #8 [0006384000 - 0008acd000]          PGTABLE ==> 
[0006384000 - 0008acd000]
[    0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x005e6891
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009e
[    0.000000]     0: 0x00000100 -> 0x000bf780
[    0.000000]     0: 0x00100000 -> 0x005e6891
[    0.000000] On node 0 totalpages: 5922719
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 1481 pages reserved
[    0.000000]   DMA zone: 2445 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14280 pages used for memmap
[    0.000000]   DMA32 zone: 765880 pages, LIFO batch:31
[    0.000000]   Normal zone: 70254 pages used for memmap
[    0.000000]   Normal zone: 5068323 pages, LIFO batch:31
[    0.000000] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
[    0.000000] Intel MultiProcessor Specification v1.4
[    0.000000] MPTABLE: OEM ID: INTEL
[    0.000000] MPTABLE: Product ID: TYLERSBURG
[    0.000000] MPTABLE: APIC at: 0xFEE00000
[    0.000000] I/O APIC #6 Version 32 at 0xFEC00000.
[    0.000000] Processors: 12
[    0.000000] SMP: Allowing 12 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 16
[    0.000000] PM: Registered nosave memory: 000000000009e000 - 
000000000009f000
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 
0000000000100000
[    0.000000] PM: Registered nosave memory: 00000000bf780000 - 
00000000bf78e000
[    0.000000] PM: Registered nosave memory: 00000000bf78e000 - 
00000000bf7d0000
[    0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 
00000000bf7e0000
[    0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 
00000000bf7ec000
[    0.000000] PM: Registered nosave memory: 00000000bf7ec000 - 
00000000c0000000
[    0.000000] PM: Registered nosave memory: 00000000c0000000 - 
00000000fec00000
[    0.000000] PM: Registered nosave memory: 00000000fec00000 - 
00000000fec01000
[    0.000000] PM: Registered nosave memory: 00000000fec01000 - 
00000000fee00000
[    0.000000] PM: Registered nosave memory: 00000000fee00000 - 
00000000fee01000
[    0.000000] PM: Registered nosave memory: 00000000fee01000 - 
00000000ffc00000
[    0.000000] PM: Registered nosave memory: 00000000ffc00000 - 
0000000100000000
[    0.000000] Allocating PCI resources starting at c0000000 (gap: 
c0000000:3ec00000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.0.1 (preserve-AD) (dom0)
[    0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:12 nr_node_ids:1
[    0.000000] PERCPU: Embedded 30 pages/cpu @ffff88001c85d000 s90328 
r8192 d24360 u122880
[    0.000000] pcpu-alloc: s90328 r8192 d24360 u122880 alloc=30*4096
[    0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 
06 [0] 07
[    0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11
[    5.202895] trying to map vcpu_info 0 at ffff88001c868020, mfn 
612a06, offset 32
[    5.202898] cpu 0 using vcpu_info at ffff88001c868020
[    5.202899] trying to map vcpu_info 1 at ffff88001c886020, mfn 
612a24, offset 32
[    5.202901] cpu 1 using vcpu_info at ffff88001c886020
[    5.202903] trying to map vcpu_info 2 at ffff88001c8a4020, mfn 
612a42, offset 32
[    5.202905] cpu 2 using vcpu_info at ffff88001c8a4020
[    5.202906] trying to map vcpu_info 3 at ffff88001c8c2020, mfn 
612a60, offset 32
[    5.202908] cpu 3 using vcpu_info at ffff88001c8c2020
[    5.202909] trying to map vcpu_info 4 at ffff88001c8e0020, mfn 
612a7e, offset 32
[    5.202911] cpu 4 using vcpu_info at ffff88001c8e0020
[    5.202912] trying to map vcpu_info 5 at ffff88001c8fe020, mfn 
612a9c, offset 32
[    5.202914] cpu 5 using vcpu_info at ffff88001c8fe020
[    5.202916] trying to map vcpu_info 6 at ffff88001c91c020, mfn 
612aba, offset 32
[    5.202918] cpu 6 using vcpu_info at ffff88001c91c020
[    5.202919] trying to map vcpu_info 7 at ffff88001c93a020, mfn 
612ad8, offset 32
[    5.202921] cpu 7 using vcpu_info at ffff88001c93a020
[    5.202922] trying to map vcpu_info 8 at ffff88001c958020, mfn 
612af6, offset 32
[    5.202924] cpu 8 using vcpu_info at ffff88001c958020
[    5.202926] trying to map vcpu_info 9 at ffff88001c976020, mfn 
612b14, offset 32
[    5.202928] cpu 9 using vcpu_info at ffff88001c976020
[    5.202929] trying to map vcpu_info 10 at ffff88001c994020, mfn 
612b32, offset 32
[    5.202931] cpu 10 using vcpu_info at ffff88001c994020
[    5.202932] trying to map vcpu_info 11 at ffff88001c9b2020, mfn 
612b50, offset 32
[    5.202934] cpu 11 using vcpu_info at ffff88001c9b2020
[    5.202935] Xen: using vcpu_info placement
[    5.202939] Built 1 zonelists in Zone order, mobility grouping on. 
Total pages: 5836648
[    5.202941] Policy zone: Normal
[    5.202943] Kernel command line: placeholder 
root=UUID=8622e268-8845-4cd5-82b3-e7fd0568c602 ro quiet acpi=off
[    5.202967] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    5.203182] Initializing CPU#0
[    5.209000] DMA: Placing 64MB software IO TLB between 
ffff88001c9ce000 - ffff8800209ce000
[    5.209003] DMA: software IO TLB at phys 0x1c9ce000 - 0x209ce000
[    5.209004] xen_swiotlb_fixup: buf=ffff88001c9ce000 size=67108864
[    5.222223] xen_swiotlb_fixup: buf=ffff880020a2e000 size=32768
[    5.301463] Memory: 23166540k/24748612k available (3152k kernel code, 
1057736k absent, 524336k reserved, 2064k data, 604k init)
[    5.301488] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, 
CPUs=12, Nodes=1
[    5.301511] Hierarchical RCU implementation.
[    5.301518] NR_IRQS:4352 nr_irqs:624
[    5.301567] xen: --> irq=0
[    5.301571] xen: --> irq=1
[    5.301573] xen: --> irq=4
[    5.301575] xen: --> irq=6
[    5.301578] xen: --> irq=7
[    5.301580] xen: --> irq=8
[    5.301582] xen: --> irq=9
[    5.301584] xen: --> irq=12
[    5.301587] xen: --> irq=13
[    5.307201] Console: colour VGA+ 80x25
[    5.307217] console [tty0] enabled
[    5.307235] Xen: using vcpuop timer interface
[    5.307237] installing Xen timer for CPU 0
[    5.307242]   alloc irq_desc for 623 on node -1
[    5.307244]   alloc kstat_irqs on node -1
[    5.307257] Detected 3341.682 MHz processor.
[    5.307263] Calibrating delay loop (skipped), value calculated using 
timer frequency.. 6683.36 BogoMIPS (lpj=13366728)
[    5.307275] Security Framework initialized
[    5.307278] SELinux:  Disabled at boot.
[    5.310847] Dentry cache hash table entries: 4194304 (order: 13, 
33554432 bytes)
[    5.317197] Inode-cache hash table entries: 2097152 (order: 12, 
16777216 bytes)
[    5.319518] Mount-cache hash table entries: 256
[    5.319622] Initializing cgroup subsys ns
[    5.319624] Initializing cgroup subsys cpuacct
[    5.319628] Initializing cgroup subsys devices
[    5.319630] Initializing cgroup subsys freezer
[    5.319631] Initializing cgroup subsys net_cls
[    5.319658] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.319660] CPU: L2 cache: 256K
[    5.319661] CPU: L3 cache: 12288K
[    5.319664] CPU 0/0x0 -> Node 0
[    5.319666] CPU: Unsupported number of siblings 32
[    5.319669] mce: CPU supports 9 MCE banks
[    5.319687] Performance Events: unsupported p6 CPU model 44 no PMU 
driver, software events only.
[    5.319697] SMP alternatives: switching to UP code
[    5.337471]   alloc irq_desc for 622 on node -1
[    5.337473]   alloc kstat_irqs on node -1
[    5.337479]   alloc irq_desc for 621 on node -1
[    5.337481]   alloc kstat_irqs on node -1
[    5.337484]   alloc irq_desc for 620 on node -1
[    5.337485]   alloc kstat_irqs on node -1
[    5.337488]   alloc irq_desc for 619 on node -1
[    5.337489]   alloc kstat_irqs on node -1
[    5.337625] installing Xen timer for CPU 1
[    5.337627]   alloc irq_desc for 618 on node -1
[    5.337628]   alloc kstat_irqs on node -1
[    5.337651] SMP alternatives: switching to SMP code
[    5.354623]   alloc irq_desc for 617 on node -1
[    5.354624]   alloc kstat_irqs on node -1
[    5.354635]   alloc irq_desc for 616 on node -1
[    5.354636]   alloc kstat_irqs on node -1
[    5.354639]   alloc irq_desc for 615 on node -1
[    5.354641]   alloc kstat_irqs on node -1
[    5.354644]   alloc irq_desc for 614 on node -1
[    5.354645]   alloc kstat_irqs on node -1
[    5.354655] Initializing CPU#1
[    5.354682] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354684] CPU: L2 cache: 256K
[    5.354684] CPU: L3 cache: 12288K
[    5.354687] CPU 1/0x0 -> Node 0
[    5.354688] CPU: Unsupported number of siblings 32
[    5.354761] installing Xen timer for CPU 2
[    5.354763]   alloc irq_desc for 613 on node -1
[    5.354765]   alloc kstat_irqs on node -1
[    5.354781]   alloc irq_desc for 612 on node -1
[    5.354782]   alloc kstat_irqs on node -1
[    5.354786]   alloc irq_desc for 611 on node -1
[    5.354787]   alloc kstat_irqs on node -1
[    5.354790]   alloc irq_desc for 610 on node -1
[    5.354791]   alloc kstat_irqs on node -1
[    5.354794]   alloc irq_desc for 609 on node -1
[    5.354796]   alloc kstat_irqs on node -1
[    5.354804] Initializing CPU#2
[    5.354829] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354831] CPU: L2 cache: 256K
[    5.354832] CPU: L3 cache: 12288K
[    5.354834] CPU 2/0x0 -> Node 0
[    5.354835] CPU: Unsupported number of siblings 32
[    5.354899] installing Xen timer for CPU 3
[    5.354901]   alloc irq_desc for 608 on node -1
[    5.354903]   alloc kstat_irqs on node -1
[    5.354918]   alloc irq_desc for 607 on node -1
[    5.354919]   alloc kstat_irqs on node -1
[    5.354923]   alloc irq_desc for 606 on node -1
[    5.354924]   alloc kstat_irqs on node -1
[    5.354927]   alloc irq_desc for 605 on node -1
[    5.354928]   alloc kstat_irqs on node -1
[    5.354933]   alloc irq_desc for 604 on node -1
[    5.354934]   alloc kstat_irqs on node -1
[    5.354942] Initializing CPU#3
[    5.354967] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354969] CPU: L2 cache: 256K
[    5.354970] CPU: L3 cache: 12288K
[    5.354972] CPU 3/0x0 -> Node 0
[    5.354973] CPU: Unsupported number of siblings 32
[    5.355036] installing Xen timer for CPU 4
[    5.355038]   alloc irq_desc for 603 on node -1
[    5.355040]   alloc kstat_irqs on node -1
[    5.355054]   alloc irq_desc for 602 on node -1
[    5.355056]   alloc kstat_irqs on node -1
[    5.355059]   alloc irq_desc for 601 on node -1
[    5.355060]   alloc kstat_irqs on node -1
[    5.355064]   alloc irq_desc for 600 on node -1
[    5.355065]   alloc kstat_irqs on node -1
[    5.355068]   alloc irq_desc for 599 on node -1
[    5.355070]   alloc kstat_irqs on node -1
[    5.355077] Initializing CPU#4
[    5.355102] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355103] CPU: L2 cache: 256K
[    5.355104] CPU: L3 cache: 12288K
[    5.355107] CPU 4/0x0 -> Node 0
[    5.355108] CPU: Unsupported number of siblings 32
[    5.355170] installing Xen timer for CPU 5
[    5.355173]   alloc irq_desc for 598 on node -1
[    5.355174]   alloc kstat_irqs on node -1
[    5.355189]   alloc irq_desc for 597 on node -1
[    5.355190]   alloc kstat_irqs on node -1
[    5.355194]   alloc irq_desc for 596 on node -1
[    5.355195]   alloc kstat_irqs on node -1
[    5.355198]   alloc irq_desc for 595 on node -1
[    5.355200]   alloc kstat_irqs on node -1
[    5.355203]   alloc irq_desc for 594 on node -1
[    5.355204]   alloc kstat_irqs on node -1
[    5.355212] Initializing CPU#5
[    5.355236] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355238] CPU: L2 cache: 256K
[    5.355239] CPU: L3 cache: 12288K
[    5.355241] CPU 5/0x0 -> Node 0
[    5.355242] CPU: Unsupported number of siblings 32
[    5.355308] installing Xen timer for CPU 6
[    5.355311]   alloc irq_desc for 593 on node -1
[    5.355312]   alloc kstat_irqs on node -1
[    5.355329]   alloc irq_desc for 592 on node -1
[    5.355330]   alloc kstat_irqs on node -1
[    5.355334]   alloc irq_desc for 591 on node -1
[    5.355335]   alloc kstat_irqs on node -1
[    5.355339]   alloc irq_desc for 590 on node -1
[    5.355340]   alloc kstat_irqs on node -1
[    5.355343]   alloc irq_desc for 589 on node -1
[    5.355344]   alloc kstat_irqs on node -1
[    5.355352] Initializing CPU#6
[    5.355381] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355384] CPU: L2 cache: 256K
[    5.355385] CPU: L3 cache: 12288K
[    5.355388] CPU 6/0x0 -> Node 0
[    5.355390] CPU: Unsupported number of siblings 32
[    5.355465] installing Xen timer for CPU 7
[    5.355468]   alloc irq_desc for 588 on node -1
[    5.355469]   alloc kstat_irqs on node -1
[    5.355484]   alloc irq_desc for 587 on node -1
[    5.355486]   alloc kstat_irqs on node -1
[    5.355489]   alloc irq_desc for 586 on node -1
[    5.355491]   alloc kstat_irqs on node -1
[    5.355494]   alloc irq_desc for 585 on node -1
[    5.355495]   alloc kstat_irqs on node -1
[    5.355499]   alloc irq_desc for 584 on node -1
[    5.355500]   alloc kstat_irqs on node -1
[    5.355507] Initializing CPU#7
[    5.355529] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355530] CPU: L2 cache: 256K
[    5.355531] CPU: L3 cache: 12288K
[    5.355534] CPU 7/0x0 -> Node 0
[    5.355535] CPU: Unsupported number of siblings 32
[    5.355600] installing Xen timer for CPU 8
[    5.355602]   alloc irq_desc for 583 on node -1
[    5.355604]   alloc kstat_irqs on node -1
[    5.355619]   alloc irq_desc for 582 on node -1
[    5.355620]   alloc kstat_irqs on node -1
[    5.355624]   alloc irq_desc for 581 on node -1
[    5.355625]   alloc kstat_irqs on node -1
[    5.355630]   alloc irq_desc for 580 on node -1
[    5.355631]   alloc kstat_irqs on node -1
[    5.355634]   alloc irq_desc for 579 on node -1
[    5.355636]   alloc kstat_irqs on node -1
[    5.355643] Initializing CPU#8
[    5.355665] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355666] CPU: L2 cache: 256K
[    5.355667] CPU: L3 cache: 12288K
[    5.355669] CPU 8/0x0 -> Node 0
[    5.355671] CPU: Unsupported number of siblings 32
[    5.355733] installing Xen timer for CPU 9
[    5.355735]   alloc irq_desc for 578 on node -1
[    5.355737]   alloc kstat_irqs on node -1
[    5.355751]   alloc irq_desc for 577 on node -1
[    5.355752]   alloc kstat_irqs on node -1
[    5.355756]   alloc irq_desc for 576 on node -1
[    5.355757]   alloc kstat_irqs on node -1
[    5.355760]   alloc irq_desc for 575 on node -1
[    5.355761]   alloc kstat_irqs on node -1
[    5.355765]   alloc irq_desc for 574 on node -1
[    5.355766]   alloc kstat_irqs on node -1
[    5.355773] Initializing CPU#9
[    5.355795] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355796] CPU: L2 cache: 256K
[    5.355797] CPU: L3 cache: 12288K
[    5.355799] CPU 9/0x0 -> Node 0
[    5.355801] CPU: Unsupported number of siblings 32
[    5.355862] installing Xen timer for CPU 10
[    5.355865]   alloc irq_desc for 573 on node -1
[    5.355866]   alloc kstat_irqs on node -1
[    5.355880]   alloc irq_desc for 572 on node -1
[    5.355882]   alloc kstat_irqs on node -1
[    5.355885]   alloc irq_desc for 571 on node -1
[    5.355887]   alloc kstat_irqs on node -1
[    5.355890]   alloc irq_desc for 570 on node -1
[    5.355891]   alloc kstat_irqs on node -1
[    5.355896]   alloc irq_desc for 569 on node -1
[    5.355897]   alloc kstat_irqs on node -1
[    5.355904] Initializing CPU#10
[    5.355926] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355928] CPU: L2 cache: 256K
[    5.355928] CPU: L3 cache: 12288K
[    5.355931] CPU 10/0x0 -> Node 0
[    5.355932] CPU: Unsupported number of siblings 32
[    5.355995] installing Xen timer for CPU 11
[    5.355997]   alloc irq_desc for 568 on node -1
[    5.355999]   alloc kstat_irqs on node -1
[    5.356013]   alloc irq_desc for 567 on node -1
[    5.356014]   alloc kstat_irqs on node -1
[    5.356018]   alloc irq_desc for 566 on node -1
[    5.356019]   alloc kstat_irqs on node -1
[    5.356022]   alloc irq_desc for 565 on node -1
[    5.356024]   alloc kstat_irqs on node -1
[    5.356027]   alloc irq_desc for 564 on node -1
[    5.356028]   alloc kstat_irqs on node -1
[    5.356035] Initializing CPU#11
[    5.356057] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.356059] CPU: L2 cache: 256K
[    5.356059] CPU: L3 cache: 12288K
[    5.356062] CPU 11/0x0 -> Node 0
[    5.356063] CPU: Unsupported number of siblings 32
[    5.356090] Brought up 12 CPUs
[    5.356124] CPU0 attaching sched-domain:
[    5.356127]  domain 0: span 0-11 level CPU
[    5.356129]   groups: group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11
[    5.356144] CPU1 attaching sched-domain:
[    5.356145]  domain 0: span 0-11 level CPU
[    5.356147]   groups: group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0
[    5.356161] CPU2 attaching sched-domain:
[    5.356163]  domain 0: span 0-11 level CPU
[    5.356165]   groups: group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1
[    5.356179] CPU3 attaching sched-domain:
[    5.356180]  domain 0: span 0-11 level CPU
[    5.356182]   groups: group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2
[    5.356196] CPU4 attaching sched-domain:
[    5.356198]  domain 0: span 0-11 level CPU
[    5.356200]   groups: group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3
[    5.356214] CPU5 attaching sched-domain:
[    5.356215]  domain 0: span 0-11 level CPU
[    5.356217]   groups: group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4
[    5.356231] CPU6 attaching sched-domain:
[    5.356232]  domain 0: span 0-11 level CPU
[    5.356234]   groups: group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5
[    5.356248] CPU7 attaching sched-domain:
[    5.356250]  domain 0: span 0-11 level CPU
[    5.356252]   groups: group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6
[    5.356266] CPU8 attaching sched-domain:
[    5.356267]  domain 0: span 0-11 level CPU
[    5.356269]   groups: group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7
[    5.356283] CPU9 attaching sched-domain:
[    5.356285]  domain 0: span 0-11 level CPU
[    5.356286]   groups: group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8
[    5.356301] CPU10 attaching sched-domain:
[    5.356302]  domain 0: span 0-11 level CPU
[    5.356304]   groups: group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9
[    5.356318] CPU11 attaching sched-domain:
[    5.356319]  domain 0: span 0-11 level CPU
[    5.356321]   groups: group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10
[    5.356702] devtmpfs: initialized
[    5.359462] Grant table initialized
[    5.359464] regulator: core version 0.5
[    5.359505] NET: Registered protocol family 16
[    5.359544]   alloc irq_desc for 563 on node -1
[    5.359545]   alloc kstat_irqs on node -1
[    5.359642] sync cpu 0 get result 1 max_id b
[    5.359648] sync cpu 1 get result 1 max_id b
[    5.359653] sync cpu 2 get result 1 max_id b
[    5.359659] sync cpu 3 get result 1 max_id b
[    5.359665] sync cpu 4 get result 1 max_id b
[    5.359671] sync cpu 5 get result 1 max_id b
[    5.359678] sync cpu 6 get result 1 max_id b
[    5.359684] sync cpu 7 get result 1 max_id b
[    5.359689] sync cpu 8 get result 1 max_id b
[    5.359695] sync cpu 9 get result 1 max_id b
[    5.359701] sync cpu a get result 1 max_id b
[    5.359707] sync cpu b get result 1 max_id b
[    5.359709]   alloc irq_desc for 562 on node -1
[    5.359711]   alloc kstat_irqs on node -1
[    5.359762] PCI: Using configuration type 1 for base access
[    5.360880] bio: create slab  at 0
[    5.361122] ACPI: Interpreter disabled.
[    5.361141] xen_balloon: Initialising balloon driver with page order 0.
[    5.361174] vgaarb: loaded
[    5.361221] PCI: Probing PCI hardware
[    5.361223] PCI: Probing PCI hardware (bus 00)
[    5.361335] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[    5.361339] pci 0000:00:00.0: PME# disabled
[    5.361460] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    5.361464] pci 0000:00:01.0: PME# disabled
[    5.361587] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[    5.361591] pci 0000:00:03.0: PME# disabled
[    5.361718] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    5.361722] pci 0000:00:07.0: PME# disabled
[    5.362123] pci 0000:00:1a.0: reg 20 io port: [0xbc00-0xbc1f]
[    5.362235] pci 0000:00:1a.1: reg 20 io port: [0xb880-0xb89f]
[    5.362348] pci 0000:00:1a.2: reg 20 io port: [0xb800-0xb81f]
[    5.362466] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf9ffe000-0xf9ffe3ff]
[    5.362570] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[    5.362575] pci 0000:00:1a.7: PME# disabled
[    5.362692] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    5.362696] pci 0000:00:1c.0: PME# disabled
[    5.362814] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    5.362818] pci 0000:00:1c.4: PME# disabled
[    5.362894] pci 0000:00:1d.0: reg 20 io port: [0xb480-0xb49f]
[    5.363002] pci 0000:00:1d.1: reg 20 io port: [0xb400-0xb41f]
[    5.363111] pci 0000:00:1d.2: reg 20 io port: [0xb080-0xb09f]
[    5.363224] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf9ffc000-0xf9ffc3ff]
[    5.363324] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[    5.363329] pci 0000:00:1d.7: PME# disabled
[    5.363526] pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
[    5.363543] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 
0a00 (mask 00ff)
[    5.363546] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 
0a00 (mask 0017)
[    5.363550] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 
4700 (mask 00ff)
[    5.363657] pci 0000:00:1f.2: reg 10 io port: [0xb000-0xb007]
[    5.363664] pci 0000:00:1f.2: reg 14 io port: [0xac00-0xac03]
[    5.363671] pci 0000:00:1f.2: reg 18 io port: [0xa880-0xa887]
[    5.363679] pci 0000:00:1f.2: reg 1c io port: [0xa800-0xa803]
[    5.363686] pci 0000:00:1f.2: reg 20 io port: [0xa480-0xa49f]
[    5.363693] pci 0000:00:1f.2: reg 24 32bit mmio: [0xf9ffa000-0xf9ffa7ff]
[    5.363762] pci 0000:00:1f.2: PME# supported from D3hot
[    5.363767] pci 0000:00:1f.2: PME# disabled
[    5.363807] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf9ff9c00-0xf9ff9cff]
[    5.363826] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[    5.363946] pci 0000:02:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
[    5.363959] pci 0000:02:00.0: reg 14 64bit mmio pref: 
[0xd0000000-0xdfffffff]
[    5.363971] pci 0000:02:00.0: reg 1c 64bit mmio pref: 
[0xce000000-0xcfffffff]
[    5.363978] pci 0000:02:00.0: reg 24 io port: [0xcc00-0xcc7f]
[    5.363985] pci 0000:02:00.0: reg 30 32bit mmio pref: 
[0xfbc80000-0xfbcfffff]
[    5.364089] pci 0000:02:00.1: reg 10 32bit mmio: [0xfbc7c000-0xfbc7ffff]
[    5.371581] pci 0000:00:03.0: bridge io port: [0xc000-0xcfff]
[    5.371586] pci 0000:00:03.0: bridge 32bit mmio: [0xfa000000-0xfbcfffff]
[    5.371592] pci 0000:00:03.0: bridge 64bit mmio pref: 
[0xce000000-0xdfffffff]
[    5.371763] pci 0000:06:00.0: reg 10 io port: [0xe800-0xe8ff]
[    5.371788] pci 0000:06:00.0: reg 18 64bit mmio: [0xfbeff000-0xfbefffff]
[    5.371806] pci 0000:06:00.0: reg 20 64bit mmio pref: 
[0xf8ff0000-0xf8ffffff]
[    5.371816] pci 0000:06:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[    5.371905] pci 0000:06:00.0: supports D1 D2
[    5.371906] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    5.371912] pci 0000:06:00.0: PME# disabled
[    5.379587] pci 0000:00:1c.4: bridge io port: [0xe000-0xefff]
[    5.379592] pci 0000:00:1c.4: bridge 32bit mmio: [0xfbe00000-0xfbefffff]
[    5.379600] pci 0000:00:1c.4: bridge 64bit mmio pref: 
[0xf8f00000-0xf8ffffff]
[    5.379663] pci 0000:00:1e.0: transparent bridge
[    5.380048] vgaarb: device added: 
PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
[    5.380182] PCI: Discovered primary peer bus 05 [IRQ]
[    5.380196] pci 0000:00:1f.0: PIIX/ICH IRQ router [8086:3a16]
[    5.380438] Switching to clocksource xen
[    5.381744] pnp: PnP ACPI: disabled
[    5.382245] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[    5.382246] pci 0000:00:01.0:   IO window: disabled
[    5.382251] pci 0000:00:01.0:   MEM window: disabled
[    5.382255] pci 0000:00:01.0:   PREFETCH window: disabled
[    5.382262] pci 0000:00:03.0: PCI bridge, secondary bus 0000:02
[    5.382265] pci 0000:00:03.0:   IO window: 0xc000-0xcfff
[    5.382270] pci 0000:00:03.0:   MEM window: 0xfa000000-0xfbcfffff
[    5.382274] pci 0000:00:03.0:   PREFETCH window: 
0x000000ce000000-0x000000dfffffff
[    5.382281] pci 0000:00:07.0: PCI bridge, secondary bus 0000:03
[    5.382282] pci 0000:00:07.0:   IO window: disabled
[    5.382287] pci 0000:00:07.0:   MEM window: disabled
[    5.382291] pci 0000:00:07.0:   PREFETCH window: disabled
[    5.382297] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
[    5.382300] pci 0000:00:1c.0:   IO window: 0x1000-0x1fff
[    5.382306] pci 0000:00:1c.0:   MEM window: 0xc0000000-0xc01fffff
[    5.382310] pci 0000:00:1c.0:   PREFETCH window: 
0x000000c0200000-0x000000c03fffff
[    5.382318] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:06
[    5.382321] pci 0000:00:1c.4:   IO window: 0xe000-0xefff
[    5.382327] pci 0000:00:1c.4:   MEM window: 0xfbe00000-0xfbefffff
[    5.382331] pci 0000:00:1c.4:   PREFETCH window: 
0x000000f8f00000-0x000000f8ffffff
[    5.382338] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:07
[    5.382340] pci 0000:00:1e.0:   IO window: disabled
[    5.382345] pci 0000:00:1e.0:   MEM window: disabled
[    5.382349] pci 0000:00:1e.0:   PREFETCH window: disabled
[    5.382366] pci 0000:00:01.0: setting latency timer to 64
[    5.382378] pci 0000:00:03.0: setting latency timer to 64
[    5.382390] pci 0000:00:07.0: setting latency timer to 64
[    5.382399] pci 0000:00:1c.0: enabling device (0104 -> 0107)
[    5.382407] PCI: setting IRQ 5 as level-triggered
[    5.382410] pci 0000:00:1c.0: found PCI INT A -> IRQ 5
[    5.382435] pci 0000:00:1c.0: sharing IRQ 5 with 0000:00:1c.4
[    5.382455] pci 0000:00:1c.0: sharing IRQ 5 with 0000:02:00.1
[    5.382462] pci 0000:00:1c.0: setting latency timer to 64
[    5.382476] pci 0000:00:1c.4: found PCI INT A -> IRQ 5
[    5.382500] pci 0000:00:1c.4: sharing IRQ 5 with 0000:00:1c.0
[    5.382522] pci 0000:00:1c.4: sharing IRQ 5 with 0000:02:00.1
[    5.382529] pci 0000:00:1c.4: setting latency timer to 64
[    5.382537] pci 0000:00:1e.0: setting latency timer to 64
[    5.382541] pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
[    5.382543] pci_bus 0000:00: resource 1 mem: 
[0x000000-0xffffffffffffffff]
[    5.382545] pci_bus 0000:02: resource 0 io:  [0xc000-0xcfff]
[    5.382546] pci_bus 0000:02: resource 1 mem: [0xfa000000-0xfbcfffff]
[    5.382548] pci_bus 0000:02: resource 2 pref mem [0xce000000-0xdfffffff]
[    5.382550] pci_bus 0000:04: resource 0 io:  [0x1000-0x1fff]
[    5.382552] pci_bus 0000:04: resource 1 mem: [0xc0000000-0xc01fffff]
[    5.382553] pci_bus 0000:04: resource 2 pref mem [0xc0200000-0xc03fffff]
[    5.382555] pci_bus 0000:06: resource 0 io:  [0xe000-0xefff]
[    5.382557] pci_bus 0000:06: resource 1 mem: [0xfbe00000-0xfbefffff]
[    5.382558] pci_bus 0000:06: resource 2 pref mem [0xf8f00000-0xf8ffffff]
[    5.382560] pci_bus 0000:07: resource 3 io:  [0x00-0xffff]
[    5.382562] pci_bus 0000:07: resource 4 mem: 
[0x000000-0xffffffffffffffff]
[    5.382564] pci_bus 0000:05: resource 0 io:  [0x00-0xffff]
[    5.382565] pci_bus 0000:05: resource 1 mem: 
[0x000000-0xffffffffffffffff]
[    5.382582] NET: Registered protocol family 2
[    5.383095] IP route cache hash table entries: 524288 (order: 10, 
4194304 bytes)
[    5.384472] TCP established hash table entries: 524288 (order: 11, 
8388608 bytes)
[    5.385620] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    5.385749] TCP: Hash tables configured (established 524288 bind 65536)
[    5.385752] TCP reno registered
[    5.385828] NET: Registered protocol family 1
[    5.385857] PCI: setting IRQ 10 as level-triggered
[    5.385860] pci 0000:00:1a.0: found PCI INT A -> IRQ 10
[    5.385906] pci 0000:00:1a.0: sharing IRQ 10 with 0000:02:00.0
[    5.385912] pci 0000:00:1a.0: sharing IRQ 10 with 0000:06:00.0
[    5.385940] PCI: setting IRQ 15 as level-triggered
[    5.385943] pci 0000:00:1a.1: found PCI INT B -> IRQ 15
[    5.386015] PCI: setting IRQ 11 as level-triggered
[    5.386018] pci 0000:00:1a.2: found PCI INT D -> IRQ 11
[    5.386048] pci 0000:00:1a.2: sharing IRQ 11 with 0000:00:1d.1
[    5.386059] pci 0000:00:1a.2: sharing IRQ 11 with 0000:00:1f.2
[    5.386099] PCI: setting IRQ 14 as level-triggered
[    5.386102] pci 0000:00:1a.7: found PCI INT C -> IRQ 14
[    5.386133] pci 0000:00:1a.7: sharing IRQ 14 with 0000:00:1d.2
[    5.386144] pci 0000:00:1a.7: sharing IRQ 14 with 0000:00:1f.3
[    5.414581] PCI: setting IRQ 3 as level-triggered
[    5.414587] pci 0000:00:1d.0: found PCI INT A -> IRQ 3
[    5.414631] pci 0000:00:1d.0: sharing IRQ 3 with 0000:00:1d.7
[    5.414672] pci 0000:00:1d.1: found PCI INT B -> IRQ 11
[    5.414692] pci 0000:00:1d.1: sharing IRQ 11 with 0000:00:1a.2
[    5.414712] pci 0000:00:1d.1: sharing IRQ 11 with 0000:00:1f.2
[    5.414747] pci 0000:00:1d.2: found PCI INT C -> IRQ 14
[    5.414769] pci 0000:00:1d.2: sharing IRQ 14 with 0000:00:1a.7
[    5.414789] pci 0000:00:1d.2: sharing IRQ 14 with 0000:00:1f.3
[    5.414828] pci 0000:00:1d.7: found PCI INT A -> IRQ 3
[    5.414855] pci 0000:00:1d.7: sharing IRQ 3 with 0000:00:1d.0
[    7.012713] pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 
01010001
[    7.012852] pci 0000:02:00.0: Boot video device
[    7.012895] Unpacking initramfs...
[    7.028884] Freeing initrd memory: 29754k freed
[    7.032797] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    7.032801] DMA: Placing 64MB software IO TLB between 
ffff88001c9ce000 - ffff8800209ce000
[    7.032803] DMA: software IO TLB at phys 0x1c9ce000 - 0x209ce000
[    7.032879] platform rtc_cmos: registered platform RTC device (no PNP 
device found)
[    7.033534] audit: initializing netlink socket (disabled)
[    7.033542] type=2000 audit(1338671115.003:1): initialized
[    7.036697] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    7.037841] VFS: Disk quotas dquot_6.5.2
[    7.037876] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    7.037933] msgmni has been set to 32768
[    7.038334] alg: No test for stdrng (krng)
[    7.038373] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 253)
[    7.038375] io scheduler noop registered
[    7.038376] io scheduler anticipatory registered
[    7.038378] io scheduler deadline registered
[    7.038414] io scheduler cfq registered (default)
[    7.038549]   alloc irq_desc for 561 on node -1
[    7.038551]   alloc kstat_irqs on node -1
[    7.038586] pcieport 0000:00:01.0: setting latency timer to 64
[    7.038728]   alloc irq_desc for 560 on node -1
[    7.038730]   alloc kstat_irqs on node -1
[    7.038750] pcieport 0000:00:03.0: setting latency timer to 64
[    7.038887]   alloc irq_desc for 559 on node -1
[    7.038888]   alloc kstat_irqs on node -1
[    7.038909] pcieport 0000:00:07.0: setting latency timer to 64
[    7.039035]   alloc irq_desc for 558 on node -1
[    7.039037]   alloc kstat_irqs on node -1
[    7.039060] pcieport 0000:00:1c.0: setting latency timer to 64
[    7.039197]   alloc irq_desc for 557 on node -1
[    7.039198]   alloc kstat_irqs on node -1
[    7.039221] pcieport 0000:00:1c.4: setting latency timer to 64
[    7.044790] registering netback
[    7.044866]   alloc irq_desc for 556 on node -1
[    7.044868]   alloc kstat_irqs on node -1
[    7.045652]   alloc irq_desc for 555 on node -1
[    7.045653]   alloc kstat_irqs on node -1
[    7.045810] Linux agpgart interface v0.103
[    7.045838] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    7.046030] input: Macintosh mouse button emulation as 
/devices/virtual/input/input0
[    7.046062] PNP: No PS/2 controller found. Probing ports directly.
[    7.048150] serio: i8042 KBD port at 0x60,0x64 irq 1
[    7.048155] serio: i8042 AUX port at 0x60,0x64 irq 12
[    7.048211] mice: PS/2 mouse device common for all mice
[    7.048258] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    7.048284] rtc0: alarms up to one day, 114 bytes nvram
[    7.048290] cpuidle: using governor ladder
[    7.048292] cpuidle: using governor menu
[    7.048295] No iBFT detected.
[    7.048480] TCP cubic registered
[    7.048554] NET: Registered protocol family 10
[    7.049045] Mobile IPv6
[    7.049047] NET: Registered protocol family 17
[    7.049097] PM: Resume from disk failed.
[    7.049104] registered taskstats version 1
[    7.049703] rtc_cmos rtc_cmos: setting system clock to 2012-06-02 
21:05:14 UTC (1338671114)
[    7.049735] Initalizing network drop monitor service
[    7.049789] Freeing unused kernel memory: 604k freed
[    7.049868] Write protecting the kernel read-only data: 4336k
[    7.070238] udev[168]: starting version 164
[    7.086267] usbcore: registered new interface driver usbfs
[    7.086282] usbcore: registered new interface driver hub
[    7.086319] usbcore: registered new device driver usb
[    7.087969] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    7.087994] r8169 0000:06:00.0: found PCI INT A -> IRQ 10
[    7.088012] r8169 0000:06:00.0: sharing IRQ 10 with 0000:00:1a.0
[    7.088040] r8169 0000:06:00.0: sharing IRQ 10 with 0000:02:00.0
[    7.088093] r8169 0000:06:00.0: setting latency timer to 64
[    7.088146]   alloc irq_desc for 554 on node -1
[    7.088148]   alloc kstat_irqs on node -1
[    7.088497] r8169 0000:06:00.0: eth0: RTL8168c/8111c at 
0xffffc90003024000, 6c:62:6d:a0:72:05, XID 1c4000c0 IRQ 554
[    7.089153] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    7.089171] ehci_hcd 0000:00:1a.7: found PCI INT C -> IRQ 14
[    7.089204] ehci_hcd 0000:00:1a.7: sharing IRQ 14 with 0000:00:1d.2
[    7.089215] ehci_hcd 0000:00:1a.7: sharing IRQ 14 with 0000:00:1f.3
[    7.089241] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[    7.089244] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[    7.089258] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned 
bus number 1
[    7.089302] ehci_hcd 0000:00:1a.7: debug port 1
[    7.090716] uhci_hcd: USB Universal Host Controller Interface driver
[    7.093188] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[    7.093201] ehci_hcd 0000:00:1a.7: request interrupt 14 failed
[    7.093240] ehci_hcd 0000:00:1a.7: USB bus 1 deregistered
[    7.093258] ehci_hcd 0000:00:1a.7: init 0000:00:1a.7 fail, -38
[    7.093298] ehci_hcd: probe of 0000:00:1a.7 failed with error -38
[    7.093328] uhci_hcd 0000:00:1a.0: found PCI INT A -> IRQ 10
[    7.093384] uhci_hcd 0000:00:1a.0: sharing IRQ 10 with 0000:02:00.0
[    7.093400] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[    7.093404] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[    7.093421] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned 
bus number 1
[    7.093451] uhci_hcd 0000:00:1a.0: request interrupt 10 failed
[    7.093494] uhci_hcd 0000:00:1a.0: USB bus 1 deregistered
[    7.093513] uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -38
[    7.093557] uhci_hcd: probe of 0000:00:1a.0 failed with error -38
[    7.093580] ehci_hcd 0000:00:1d.7: found PCI INT A -> IRQ 3
[    7.093608] ehci_hcd 0000:00:1d.7: sharing IRQ 3 with 0000:00:1d.0
[    7.093649] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[    7.093652] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    7.093664] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned 
bus number 1
[    7.093702] ehci_hcd 0000:00:1d.7: debug port 1
[    7.097582] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[    7.097585] ehci_hcd 0000:00:1d.7: request interrupt 3 failed
[    7.097623] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
[    7.097639] ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -38
[    7.097678] ehci_hcd: probe of 0000:00:1d.7 failed with error -38
[    7.097721] uhci_hcd 0000:00:1a.1: found PCI INT B -> IRQ 15
[    7.097789] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[    7.097793] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[    7.097808] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned 
bus number 1
[    7.097837] uhci_hcd 0000:00:1a.1: request interrupt 15 failed
[    7.097879] uhci_hcd 0000:00:1a.1: USB bus 1 deregistered
[    7.097897] uhci_hcd 0000:00:1a.1: init 0000:00:1a.1 fail, -38
[    7.097942] uhci_hcd: probe of 0000:00:1a.1 failed with error -38
[    7.097958] uhci_hcd 0000:00:1a.2: found PCI INT D -> IRQ 11
[    7.097995] uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1d.1
[    7.098009] uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1f.2
[    7.098013] SCSI subsystem initialized
[    7.098028] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[    7.098032] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[    7.098047] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned 
bus number 1
[    7.098077] uhci_hcd 0000:00:1a.2: request interrupt 11 failed
[    7.098120] uhci_hcd 0000:00:1a.2: USB bus 1 deregistered
[    7.098136] uhci_hcd 0000:00:1a.2: init 0000:00:1a.2 fail, -38
[    7.098180] uhci_hcd: probe of 0000:00:1a.2 failed with error -38
[    7.098198] uhci_hcd 0000:00:1d.0: found PCI INT A -> IRQ 3
[    7.098241] uhci_hcd 0000:00:1d.0: sharing IRQ 3 with 0000:00:1d.7
[    7.098267] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[    7.098271] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    7.098285] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned 
bus number 1
[    7.098315] uhci_hcd 0000:00:1d.0: request interrupt 3 failed
[    7.098356] uhci_hcd 0000:00:1d.0: USB bus 1 deregistered
[    7.098373] uhci_hcd 0000:00:1d.0: init 0000:00:1d.0 fail, -38
[    7.098423] uhci_hcd: probe of 0000:00:1d.0 failed with error -38
[    7.098440] uhci_hcd 0000:00:1d.1: found PCI INT B -> IRQ 11
[    7.098466] uhci_hcd 0000:00:1d.1: sharing IRQ 11 with 0000:00:1a.2
[    7.098493] uhci_hcd 0000:00:1d.1: sharing IRQ 11 with 0000:00:1f.2
[    7.098512] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[    7.098516] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    7.098531] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned 
bus number 1
[    7.098560] uhci_hcd 0000:00:1d.1: request interrupt 11 failed
[    7.098602] uhci_hcd 0000:00:1d.1: USB bus 1 deregistered
[    7.098618] uhci_hcd 0000:00:1d.1: init 0000:00:1d.1 fail, -38
[    7.098672] uhci_hcd: probe of 0000:00:1d.1 failed with error -38
[    7.098687] uhci_hcd 0000:00:1d.2: found PCI INT C -> IRQ 14
[    7.098710] uhci_hcd 0000:00:1d.2: sharing IRQ 14 with 0000:00:1a.7
[    7.098730] uhci_hcd 0000:00:1d.2: sharing IRQ 14 with 0000:00:1f.3
[    7.098744] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[    7.098747] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.098759] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned 
bus number 1
[    7.098784] uhci_hcd 0000:00:1d.2: request interrupt 14 failed
[    7.098821] uhci_hcd 0000:00:1d.2: USB bus 1 deregistered
[    7.098833] uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -38
[    7.098871] uhci_hcd: probe of 0000:00:1d.2 failed with error -38
[    7.099958] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input1
[    7.106033] libata version 3.00 loaded.
[    7.107791] ahci 0000:00:1f.2: version 3.0
[    7.107806] ahci 0000:00:1f.2: found PCI INT B -> IRQ 11
[    7.107826] ahci 0000:00:1f.2: sharing IRQ 11 with 0000:00:1a.2
[    7.107837] ahci 0000:00:1f.2: sharing IRQ 11 with 0000:00:1d.1
[    7.107895]   alloc irq_desc for 553 on node -1
[    7.107897]   alloc kstat_irqs on node -1
[    7.107934] ahci: SSS flag set, parallel bus scan disabled
[    7.107968] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 
0x3f impl SATA mode
[    7.107971] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo 
pio slum part ccc ems sxs
[    7.107976] ahci 0000:00:1f.2: setting latency timer to 64
[    7.144788] scsi0 : ahci
[    7.144855] scsi1 : ahci
[    7.144917] scsi2 : ahci
[    7.144970] scsi3 : ahci
[    7.145031] scsi4 : ahci
[    7.145090] scsi5 : ahci
[    7.145117] ata1: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa100 irq 553
[    7.145119] ata2: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa180 irq 553
[    7.145122] ata3: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa200 irq 553
[    7.145124] ata4: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa280 irq 553
[    7.145126] ata5: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa300 irq 553
[    7.145128] ata6: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa380 irq 553
[    7.460723] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    7.489450] ata1.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    7.489455] ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    7.531403] ata1.00: configured for UDMA/133
[    7.548813] scsi 0:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    8.272724] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    8.301405] ata2.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    8.301410] ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.343349] ata2.00: configured for UDMA/133
[    8.356815] scsi 1:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    9.080722] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.112504] ata3.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    9.112509] ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.154542] ata3.00: configured for UDMA/133
[    9.168803] scsi 2:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    9.892720] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.921522] ata4.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    9.921526] ata4.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.963596] ata4.00: configured for UDMA/133
[    9.976797] scsi 3:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[   10.296721] ata5: SATA link down (SStatus 0 SControl 300)
[   10.636718] ata6: SATA link down (SStatus 0 SControl 300)
[   10.656678] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.656739] sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.656742] sd 0:0:0:0: [sda] Write Protect is off
[   10.656743] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   10.656776] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.656801] sd 1:0:0:0: [sdb] Write Protect is off
[   10.656803] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   10.656823] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.656921]  sda:
[   10.656964]  sdb:
[   10.657032] sd 2:0:0:0: [sdc] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.657079] sd 2:0:0:0: [sdc] Write Protect is off
[   10.657081] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   10.657101] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.657204]  sdc:
[   10.657358] sd 3:0:0:0: [sdd] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.657411] sd 3:0:0:0: [sdd] Write Protect is off
[   10.657413] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[   10.657432] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.657534]  sdd: sda1 sda2 sda3 sda4
[   10.672225] sd 0:0:0:0: [sda] Attached SCSI disk
[   10.674742]  sdd1 sdd2 sdd3 sdd4
[   10.675145] sd 3:0:0:0: [sdd] Attached SCSI disk
[   10.680425]  sdb1 sdb2 sdb3 sdb4
[   10.680814] sd 1:0:0:0: [sdb] Attached SCSI disk
[   10.681216]  sdc1 sdc2 sdc3 sdc4
[   10.681606] sd 2:0:0:0: [sdc] Attached SCSI disk
[   10.951914] md: raid0 personality registered for level 0
[   10.954707] md: raid1 personality registered for level 1
[   10.956749] async_tx: api initialized (async)
[   10.957166] xor: automatically using best checksumming function: 
generic_sse
[   10.974529]    generic_sse:  3767.000 MB/sec
[   10.974531] xor: using function: generic_sse (3767.000 MB/sec)
[   11.042533] raid6: int64x1   3356 MB/s
[   11.110540] raid6: int64x2   4270 MB/s
[   11.178539] raid6: int64x4   2984 MB/s
[   11.246548] raid6: int64x8   2948 MB/s
[   11.314528] raid6: sse2x1    7702 MB/s
[   11.382535] raid6: sse2x2    8938 MB/s
[   11.450532] raid6: sse2x4   10054 MB/s
[   11.450534] raid6: using algorithm sse2x4 (10054 MB/s)
[   11.453150] md: raid6 personality registered for level 6
[   11.453152] md: raid5 personality registered for level 5
[   11.453153] md: raid4 personality registered for level 4
[   11.457829] md: raid10 personality registered for level 10
[   11.460193] 3ware Storage Controller device driver for Linux 
v1.26.02.002.
[   11.462762] 3ware 9000 Storage Controller device driver for Linux 
v2.26.02.013.
[   11.465865] Adaptec aacraid driver 1.1-7[28000]-ms
[   11.526546] mdadm: sending ioctl 1261 to a partition!
[   11.526548] mdadm: sending ioctl 1261 to a partition!
[   11.526852] mdadm: sending ioctl 1261 to a partition!
[   11.526856] mdadm: sending ioctl 1261 to a partition!
[   11.527149] mdadm: sending ioctl 1261 to a partition!
[   11.527151] mdadm: sending ioctl 1261 to a partition!
[   11.527537] mdadm: sending ioctl 1261 to a partition!
[   11.527541] mdadm: sending ioctl 1261 to a partition!
[   11.528129] mdadm: sending ioctl 1261 to a partition!
[   11.528133] mdadm: sending ioctl 1261 to a partition!
[   11.535445] md: md0 stopped.
[   11.537450] md: bind
[   11.537671] md: bind
[   11.539210] md: bind
[   11.540397] md: bind
[   11.541627] raid1: raid set md0 active with 4 out of 4 mirrors
[   11.541643] md0: detected capacity change from 0 to 2152923136
[   11.542611]  md0:
[   11.547251] md: md1 stopped.
[   11.548846] md: bind
[   11.549072] md: bind
[   11.551287] md: bind
[   11.552226] md: bind
[   11.553468] raid1: raid set md1 active with 4 out of 4 mirrors
[   11.553483] md1: detected capacity change from 0 to 271319040
[   11.554467]  md1:
[   11.561426] md: md2 stopped.
[   11.571044]  unknown partition table
[   11.580029] md: bind
[   11.580454] md: bind
[   11.580723] md: bind
[   11.583198] md: bind
[   11.584396] raid5: device sda3 operational as raid disk 0
[   11.584398] raid5: device sdd3 operational as raid disk 3
[   11.584399] raid5: device sdc3 operational as raid disk 2
[   11.584401] raid5: device sdb3 operational as raid disk 1
[   11.584857] raid5: allocated 4282kB for md2
[   11.584884] 0: w=1 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584887] 3: w=2 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584888] 2: w=3 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584890] 1: w=4 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584892] raid5: raid level 6 set md2 active with 4 out of 4 
devices, algorithm 2
[   11.584893] RAID5 conf printout:
[   11.584894]  --- rd:4 wd:4
[   11.584896]  disk 0, o:1, dev:sda3
[   11.584897]  disk 1, o:1, dev:sdb3
[   11.584899]  disk 2, o:1, dev:sdc3
[   11.584900]  disk 3, o:1, dev:sdd3
[   11.584921] md2: detected capacity change from 0 to 4309909504
[   11.585918]  md2: unknown partition table
[   11.593292] md: md3 stopped.
[   11.610190] md: bind
[   11.617251] md: bind
[   11.622250] md: bind
[   11.623085] md: bind
[   11.624231] raid5: device sda4 operational as raid disk 0
[   11.624234] raid5: device sdd4 operational as raid disk 3
[   11.624235] raid5: device sdc4 operational as raid disk 2
[   11.624237] raid5: device sdb4 operational as raid disk 1
[   11.624500] raid5: allocated 4282kB for md3
[   11.624529] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624531] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624533] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624535] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624536] raid5: raid level 5 set md3 active with 4 out of 4 
devices, algorithm 2
[   11.624538] RAID5 conf printout:
[   11.624539]  --- rd:4 wd:4
[   11.624540]  disk 0, o:1, dev:sda4
[   11.624542]  disk 1, o:1, dev:sdb4
[   11.624543]  disk 2, o:1, dev:sdc4
[   11.624544]  disk 3, o:1, dev:sdd4
[   11.624561] md3: detected capacity change from 0 to 4487149780992
[   11.625561]  md3: unknown partition table
[   11.630945] device-mapper: uevent: version 1.0.3
[   11.631026] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) 
initialised: dm-devel@redhat.com
[   11.737748] PM: Starting manual resume from disk
[   11.737750] PM: Resume from partition 8:1
[   11.737752] PM: Checking hibernation image.
[   11.738408] PM: Error -22 checking image file
[   11.738411] PM: Resume from disk failed.
[   11.747092] EXT3-fs: INFO: recovery required on readonly filesystem.
[   11.747096] EXT3-fs: write access will be enabled during recovery.
[   12.001862] kjournald starting.  Commit interval 5 seconds
[   12.001870] EXT3-fs: recovery complete.
[   12.005811] EXT3-fs: mounted filesystem with ordered data mode.
[   12.850243] udev[455]: starting version 164
[   13.003403] input: PC Speaker as /devices/platform/pcspkr/input/input2
[   13.007911] i801_smbus 0000:00:1f.3: found PCI INT C -> IRQ 14
[   13.007935] i801_smbus 0000:00:1f.3: sharing IRQ 14 with 0000:00:1a.7
[   13.007947] i801_smbus 0000:00:1f.3: sharing IRQ 14 with 0000:00:1d.2
[   13.372002] Error: Driver 'pcspkr' is already registered, aborting...
[   13.432617] HDA Intel 0000:02:00.1: found PCI INT B -> IRQ 5
[   13.432668] hda_intel: Disable MSI for Nvidia chipset
[   13.432719] hda-intel: unable to grab IRQ 5, disabling device
[   13.432783] HDA Intel: probe of 0000:02:00.1 failed with error -16
[   13.763984] Adding 2102456k swap on /dev/md0.  Priority:-1 extents:1 
across:2102456k
[   13.766656] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   13.780065] EXT3 FS on md2, internal journal
[   13.854472] loop: module loaded
[   14.332498] kjournald starting.  Commit interval 5 seconds
[   14.332518] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   14.332924] EXT3 FS on md1, internal journal
[   14.332929] EXT3-fs: recovery complete.
[   14.333462] EXT3-fs: mounted filesystem with ordered data mode.
[   14.440947] kjournald starting.  Commit interval 5 seconds
[   14.440953] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   14.487241] EXT3 FS on md3, internal journal
[   14.487246] EXT3-fs: recovery complete.
[   14.487250] EXT3-fs: mounted filesystem with ordered data mode.
[   14.840198] r8169 0000:06:00.0: eth0: link down
[   14.840206] r8169 0000:06:00.0: eth0: link down
[   14.841221] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.343001] fuse init (API version 7.13)
[   15.537238] Event-channel device installed.
[   15.837972]   alloc irq_desc for 552 on node -1
[   15.837974]   alloc kstat_irqs on node -1
[   15.838004]   alloc irq_desc for 551 on node -1
[   15.838006]   alloc kstat_irqs on node -1
[   15.838156] XENBUS: Unable to read cpu state
[   15.838277] XENBUS: Unable to read cpu state
[   15.838423] XENBUS: Unable to read cpu state
[   15.838532] XENBUS: Unable to read cpu state
[   15.838640] XENBUS: Unable to read cpu state
[   15.838748] XENBUS: Unable to read cpu state
[   15.838854] XENBUS: Unable to read cpu state
[   15.838960] XENBUS: Unable to read cpu state
[   15.839065] XENBUS: Unable to read cpu state
[   15.839171] XENBUS: Unable to read cpu state
[   15.839276] XENBUS: Unable to read cpu state
[   15.839384] XENBUS: Unable to read cpu state
[   16.797692] Bridge firewalling registered
[   17.488275] r8169 0000:06:00.0: eth0: link up
[   17.489372] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   28.396708] eth0: no IPv6 routers present
[   50.109845]   alloc irq_desc for 550 on node -1
[   50.109848]   alloc kstat_irqs on node -1
[   50.297549]   alloc irq_desc for 549 on node -1
[   50.297552]   alloc kstat_irqs on node -1
[   50.379961] ip_tables: (C) 2000-2006 Netfilter Core Team
[   50.457516] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   50.457685] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. 
Please use
[   50.457687] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack 
module option or
[   50.457688] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[   50.488368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.499377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.501009] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.501012] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   51.972953] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   51.972985]   alloc irq_desc for 548 on node -1
[   51.972988]   alloc kstat_irqs on node -1
[   51.981918] blkback: ring-ref 768, event-channel 64, protocol 1 
(x86_64-abi)
[   51.981934]   alloc irq_desc for 547 on node -1
[   51.981936]   alloc kstat_irqs on node -1
[   51.999287] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   51.999302]   alloc irq_desc for 546 on node -1
[   51.999304]   alloc kstat_irqs on node -1
[   52.007159]   alloc irq_desc for 545 on node -1
[   52.007162]   alloc kstat_irqs on node -1
[   58.633380]   alloc irq_desc for 544 on node -1
[   58.633383]   alloc kstat_irqs on node -1
[   58.837769] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.837773] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839540] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839543] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839545] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841606] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841610] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841612] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843266] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843269] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843272] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843274] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.892320]   alloc irq_desc for 543 on node -1
[   58.892322]   alloc kstat_irqs on node -1
[   59.486087] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   59.486116]   alloc irq_desc for 542 on node -1
[   59.486118]   alloc kstat_irqs on node -1
[   59.496936] blkback: ring-ref 9, event-channel 64, protocol 1 
(x86_64-abi)
[   59.496949]   alloc irq_desc for 541 on node -1
[   59.496950]   alloc kstat_irqs on node -1
[   59.507401] blkback: ring-ref 10, event-channel 65, protocol 1 
(x86_64-abi)
[   59.507413]   alloc irq_desc for 540 on node -1
[   59.507415]   alloc kstat_irqs on node -1
[   59.614676]   alloc irq_desc for 539 on node -1
[   59.614678]   alloc kstat_irqs on node -1
[   60.332661] vif1.0: no IPv6 routers present
[   68.884954] vif2.0: no IPv6 routers present
[   70.590651]   alloc irq_desc for 538 on node -1
[   70.590654]   alloc kstat_irqs on node -1
[   70.771436] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771441] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771443] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771445] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773897] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773900] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773903] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773905] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773907] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776415] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776419] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776423] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776425] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776428] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778274] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778279] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778283] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778286] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778289] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778292] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.839351]   alloc irq_desc for 537 on node -1
[   70.839354]   alloc kstat_irqs on node -1
[   71.467841]   alloc irq_desc for 536 on node -1
[   71.467844]   alloc kstat_irqs on node -1
[   71.468493] blkback: ring-ref 770, event-channel 64, protocol 1 
(x86_64-abi)
[   71.468505]   alloc irq_desc for 535 on node -1
[   71.468507]   alloc kstat_irqs on node -1
[   71.483003] blkback: ring-ref 771, event-channel 65, protocol 1 
(x86_64-abi)
[   71.483018]   alloc irq_desc for 534 on node -1
[   71.483020]   alloc kstat_irqs on node -1
[   71.491437] blkback: ring-ref 772, event-channel 66, protocol 1 
(x86_64-abi)
[   71.491450]   alloc irq_desc for 533 on node -1
[   71.491452]   alloc kstat_irqs on node -1
[   77.077466]   alloc irq_desc for 532 on node -1
[   77.077469]   alloc kstat_irqs on node -1
[   77.394365] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394370] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394373] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394375] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396069] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396072] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396075] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396077] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396079] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396081] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396083] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398424] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398427] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398430] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398432] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398435] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398438] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398441] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400189] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400193] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400195] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400197] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400199] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400201] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400203] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400205] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.443743]   alloc irq_desc for 531 on node -1
[   77.443745]   alloc kstat_irqs on node -1
[   78.076700] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   78.076735]   alloc irq_desc for 530 on node -1
[   78.076736]   alloc kstat_irqs on node -1
[   78.088947] blkback: ring-ref 770, event-channel 65, protocol 1 
(x86_64-abi)
[   78.088962]   alloc irq_desc for 529 on node -1
[   78.088963]   alloc kstat_irqs on node -1
[   78.153935]   alloc irq_desc for 528 on node -1
[   78.153937]   alloc kstat_irqs on node -1
[   78.154545] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   78.154559]   alloc irq_desc for 527 on node -1
[   78.154561]   alloc kstat_irqs on node -1
[   78.160284] blkback: ring-ref 772, event-channel 67, protocol 1 
(x86_64-abi)
[   78.160299]   alloc irq_desc for 526 on node -1
[   78.160300]   alloc kstat_irqs on node -1
[   81.741939] vif3.0: no IPv6 routers present
[   83.257645]   alloc irq_desc for 525 on node -1
[   83.257647]   alloc kstat_irqs on node -1
[   83.450601] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450606] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450608] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450610] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450612] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450614] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450616] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450619] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452519] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452522] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452524] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452528] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452530] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452532] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452534] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452536] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452538] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455134] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455138] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455141] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455144] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455147] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455149] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455152] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455155] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455157] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457355] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457359] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457361] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457363] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457366] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457370] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457373] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457375] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.493883]   alloc irq_desc for 524 on node -1
[   83.493886]   alloc kstat_irqs on node -1
[   84.988630] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   84.988671]   alloc irq_desc for 523 on node -1
[   84.988673]   alloc kstat_irqs on node -1
[   84.999610] blkback: ring-ref 768, event-channel 64, protocol 1 
(x86_64-abi)
[   84.999635]   alloc irq_desc for 522 on node -1
[   84.999636]   alloc kstat_irqs on node -1
[   85.019939] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   85.019955]   alloc irq_desc for 521 on node -1
[   85.019957]   alloc kstat_irqs on node -1
[   85.032714]   alloc irq_desc for 520 on node -1
[   85.032717]   alloc kstat_irqs on node -1
[   87.492584] vif4.0: no IPv6 routers present
[   89.980170]   alloc irq_desc for 519 on node -1
[   89.980173]   alloc kstat_irqs on node -1
[   90.140856] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140861] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140864] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140867] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140870] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140872] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140875] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140878] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140881] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140884] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142965] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142968] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142970] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142972] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142974] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142977] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142979] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142981] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142983] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142985] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142987] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145194] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145197] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145200] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145202] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145204] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145206] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145208] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145210] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145213] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145215] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145217] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147500] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147504] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147507] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147510] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147513] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147516] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147518] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147523] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147525] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147528] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147531] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147534] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.197690]   alloc irq_desc for 518 on node -1
[   90.197692]   alloc kstat_irqs on node -1
[   90.698961]   alloc irq_desc for 517 on node -1
[   90.698964]   alloc kstat_irqs on node -1
[   90.699858] blkback: ring-ref 770, event-channel 64, protocol 1 
(x86_64-abi)
[   90.699876]   alloc irq_desc for 516 on node -1
[   90.699878]   alloc kstat_irqs on node -1
[   90.711588] blkback: ring-ref 771, event-channel 65, protocol 1 
(x86_64-abi)
[   90.711607]   alloc irq_desc for 515 on node -1
[   90.711608]   alloc kstat_irqs on node -1
[   94.272586] vif5.0: no IPv6 routers present
[  100.332601] vif6.0: no IPv6 routers present
[ 6714.397700] md: data-check of RAID array md1
[ 6714.397702] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6714.397704] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6714.397708] md: using 128k window, over a total of 264960 blocks.
[ 6714.560070] md: delaying data-check of md2 until md1 has finished 
(they share one or more physical units)
[ 6714.578031] md: delaying data-check of md3 until md2 has finished 
(they share one or more physical units)
[ 6714.578038] md: delaying data-check of md2 until md1 has finished 
(they share one or more physical units)
[ 6721.351752] md: md1: data-check done.
[ 6721.365392] md: data-check of RAID array md2
[ 6721.365394] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6721.365396] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6721.365399] md: using 128k window, over a total of 2104448 blocks.
[ 6721.365412] md: delaying data-check of md3 until md2 has finished 
(they share one or more physical units)
[ 6750.942813] md: md2: data-check done.
[ 6750.946200] md: data-check of RAID array md3
[ 6750.946202] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6750.946204] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6750.946207] md: using 128k window, over a total of 1460660736 blocks.
[56197.064117] md: md3: data-check done.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Jun 03 15:31:47 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 15:31: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 1SbCkX-0007iG-Vc; Sun, 03 Jun 2012 15:29:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbCkW-0007iB-7K
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 15:29:48 +0000
Received: from [85.158.143.99:33535] by server-1.bemta-4.messagelabs.com id
	2E/2B-27869-BE28BCF4; Sun, 03 Jun 2012 15:29:47 +0000
X-Env-Sender: werner@xxlwade.de
X-Msg-Ref: server-4.tower-216.messagelabs.com!1338737376!25862281!1
X-Originating-IP: [88.198.0.151]
X-SpamReason: No, hits=3.4 required=7.0 tests=HELO_DYNAMIC_IPADDR
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25990 invoked from network); 3 Jun 2012 15:29:36 -0000
Received: from static.88-198-0-151.clients.your-server.de (HELO
	static-ip-217-172-170-8.inaddr.intergenia.de) (88.198.0.151)
	by server-4.tower-216.messagelabs.com with SMTP;
	3 Jun 2012 15:29:36 -0000
Received: from [192.168.1.2] (localhost [127.0.0.1])
	by static-ip-217-172-170-8.inaddr.intergenia.de (Postfix) with ESMTPA
	id 930AE16273
	for ; Sun,  3 Jun 2012 17:29:34 +0200 (CEST)
Message-ID: <4FCB82DE.4080506@xxlwade.de>
Date: Sun, 03 Jun 2012 17:29:34 +0200
From: Werner Fehn 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] need to load uhci_hcd with acpi=off
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Dear all,

I have running a DOM-0 on debian squeeze with the most recent kernel:

Linux 2.6.32-5-xen-amd64 #1 SMP

On 30% of all reboots the system hangs and only a reset helps.

acpi=off as an additional kernel parameter solves this problem, but
the usb keyboard of the installed ip-kvm is not found then.

with acpi=off Ican find a lot stuff like:

[    7.098747] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.098759] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned 
bus number 1
[    7.098784] uhci_hcd 0000:00:1d.2: request interrupt 14 failed
[    7.098821] uhci_hcd 0000:00:1d.2: USB bus 1 deregistered
[    7.098833] uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -38
[    7.098871] uhci_hcd: probe of 0000:00:1d.2 failed with error -38

looks like a dead look. without acpi=off the system hangs sometimes.
with the parameter i have no access via my ip-kvm (it is a remote 
machine in a farm).

With acpi=off I can reproduce the *hci_hcd error on a system in my home, 
but on this machine reboot runs fine also without acpi=off.

Seems I need acpi=off, but I need to load *hci_hcd to get access to the 
usb-ip-kvm-keyboard.

What I tried:
- thousands of BIOS IRQ/PnP parameters => no luck
- noacpi => kernel panic
- irq=biosirq => no change

Any more idea to get the IRQ with acpi=off parameter set?

Best Regards
Werner

complete dmesg:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-44) 
(dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat May 
5 04:18:09 UTC 2012
[    0.000000] Command line: placeholder 
root=UUID=8622e268-8845-4cd5-82b3-e7fd0568c602 ro quiet acpi=off
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] xen_release_chunk: looking at area pfn bf7e0-bf7ec: 12 
pages freed
[    0.000000] xen_release_chunk: looking at area pfn c0000-fec00: 
257024 pages freed
[    0.000000] xen_release_chunk: looking at area pfn fec01-fee00: 511 
pages freed
[    0.000000] xen_release_chunk: looking at area pfn fee01-ffc00: 3583 
pages freed
[    0.000000] released 261130 pages of unused memory
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009ec00 (usable)
[    0.000000]  Xen: 000000000009ec00 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 00000000bf780000 (usable)
[    0.000000]  Xen: 00000000bf780000 - 00000000bf78e000 (ACPI data)
[    0.000000]  Xen: 00000000bf78e000 - 00000000bf7d0000 (ACPI NVS)
[    0.000000]  Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[    0.000000]  Xen: 00000000bf7ec000 - 00000000c0000000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  Xen: 00000000ffc00000 - 0000000100000000 (reserved)
[    0.000000]  Xen: 0000000100000000 - 00000005e6891000 (usable)
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working 
around it.
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 
(usable) ==> (reserved)
[    0.000000] last_pfn = 0x5e6891 max_arch_pfn = 0x400000000
[    0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 
0x7010600070106
[    0.000000] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000bf780000
[    0.000000]  0000000000 - 00bf780000 page 4k
[    0.000000] kernel direct mapping tables up to bf780000 @ 100000-700000
[    0.000000] init_memory_mapping: 0000000100000000-00000005e6891000
[    0.000000]  0100000000 - 05e6891000 page 4k
[    0.000000] kernel direct mapping tables up to 5e6891000 @ 
6384000-92d2000
[    0.000000] RAMDISK: 01708000 - 03416a00
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-00000005e6891000
[    0.000000] Bootmem setup node 0 0000000000000000-00000005e6891000
[    0.000000]   NODE_DATA [0000000000010000 - 0000000000017fff]
[    0.000000]   bootmap [00000000006c6000 -  0000000000782d17] pages bd
[    0.000000] (9 early reservations) ==> bootmem [0000000000 - 05e6891000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> 
[0000000000 - 0000001000]
[    0.000000]   #1 [000634d000 - 0006384000]   XEN PAGETABLES ==> 
[000634d000 - 0006384000]
[    0.000000]   #2 [0000006000 - 0000008000]       TRAMPOLINE ==> 
[0000006000 - 0000008000]
[    0.000000]   #3 [0001000000 - 00016e7b44]    TEXT DATA BSS ==> 
[0001000000 - 00016e7b44]
[    0.000000]   #4 [0001708000 - 0003416a00]          RAMDISK ==> 
[0001708000 - 0003416a00]
[    0.000000]   #5 [0003417000 - 000634d000]   XEN START INFO ==> 
[0003417000 - 000634d000]
[    0.000000]   #6 [00016e8000 - 00016e812b]              BRK ==> 
[00016e8000 - 00016e812b]
[    0.000000]   #7 [0000100000 - 00006c6000]          PGTABLE ==> 
[0000100000 - 00006c6000]
[    0.000000]   #8 [0006384000 - 0008acd000]          PGTABLE ==> 
[0006384000 - 0008acd000]
[    0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x005e6891
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009e
[    0.000000]     0: 0x00000100 -> 0x000bf780
[    0.000000]     0: 0x00100000 -> 0x005e6891
[    0.000000] On node 0 totalpages: 5922719
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 1481 pages reserved
[    0.000000]   DMA zone: 2445 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14280 pages used for memmap
[    0.000000]   DMA32 zone: 765880 pages, LIFO batch:31
[    0.000000]   Normal zone: 70254 pages used for memmap
[    0.000000]   Normal zone: 5068323 pages, LIFO batch:31
[    0.000000] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
[    0.000000] Intel MultiProcessor Specification v1.4
[    0.000000] MPTABLE: OEM ID: INTEL
[    0.000000] MPTABLE: Product ID: TYLERSBURG
[    0.000000] MPTABLE: APIC at: 0xFEE00000
[    0.000000] I/O APIC #6 Version 32 at 0xFEC00000.
[    0.000000] Processors: 12
[    0.000000] SMP: Allowing 12 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 16
[    0.000000] PM: Registered nosave memory: 000000000009e000 - 
000000000009f000
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 
0000000000100000
[    0.000000] PM: Registered nosave memory: 00000000bf780000 - 
00000000bf78e000
[    0.000000] PM: Registered nosave memory: 00000000bf78e000 - 
00000000bf7d0000
[    0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 
00000000bf7e0000
[    0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 
00000000bf7ec000
[    0.000000] PM: Registered nosave memory: 00000000bf7ec000 - 
00000000c0000000
[    0.000000] PM: Registered nosave memory: 00000000c0000000 - 
00000000fec00000
[    0.000000] PM: Registered nosave memory: 00000000fec00000 - 
00000000fec01000
[    0.000000] PM: Registered nosave memory: 00000000fec01000 - 
00000000fee00000
[    0.000000] PM: Registered nosave memory: 00000000fee00000 - 
00000000fee01000
[    0.000000] PM: Registered nosave memory: 00000000fee01000 - 
00000000ffc00000
[    0.000000] PM: Registered nosave memory: 00000000ffc00000 - 
0000000100000000
[    0.000000] Allocating PCI resources starting at c0000000 (gap: 
c0000000:3ec00000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.0.1 (preserve-AD) (dom0)
[    0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:12 nr_node_ids:1
[    0.000000] PERCPU: Embedded 30 pages/cpu @ffff88001c85d000 s90328 
r8192 d24360 u122880
[    0.000000] pcpu-alloc: s90328 r8192 d24360 u122880 alloc=30*4096
[    0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 
06 [0] 07
[    0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11
[    5.202895] trying to map vcpu_info 0 at ffff88001c868020, mfn 
612a06, offset 32
[    5.202898] cpu 0 using vcpu_info at ffff88001c868020
[    5.202899] trying to map vcpu_info 1 at ffff88001c886020, mfn 
612a24, offset 32
[    5.202901] cpu 1 using vcpu_info at ffff88001c886020
[    5.202903] trying to map vcpu_info 2 at ffff88001c8a4020, mfn 
612a42, offset 32
[    5.202905] cpu 2 using vcpu_info at ffff88001c8a4020
[    5.202906] trying to map vcpu_info 3 at ffff88001c8c2020, mfn 
612a60, offset 32
[    5.202908] cpu 3 using vcpu_info at ffff88001c8c2020
[    5.202909] trying to map vcpu_info 4 at ffff88001c8e0020, mfn 
612a7e, offset 32
[    5.202911] cpu 4 using vcpu_info at ffff88001c8e0020
[    5.202912] trying to map vcpu_info 5 at ffff88001c8fe020, mfn 
612a9c, offset 32
[    5.202914] cpu 5 using vcpu_info at ffff88001c8fe020
[    5.202916] trying to map vcpu_info 6 at ffff88001c91c020, mfn 
612aba, offset 32
[    5.202918] cpu 6 using vcpu_info at ffff88001c91c020
[    5.202919] trying to map vcpu_info 7 at ffff88001c93a020, mfn 
612ad8, offset 32
[    5.202921] cpu 7 using vcpu_info at ffff88001c93a020
[    5.202922] trying to map vcpu_info 8 at ffff88001c958020, mfn 
612af6, offset 32
[    5.202924] cpu 8 using vcpu_info at ffff88001c958020
[    5.202926] trying to map vcpu_info 9 at ffff88001c976020, mfn 
612b14, offset 32
[    5.202928] cpu 9 using vcpu_info at ffff88001c976020
[    5.202929] trying to map vcpu_info 10 at ffff88001c994020, mfn 
612b32, offset 32
[    5.202931] cpu 10 using vcpu_info at ffff88001c994020
[    5.202932] trying to map vcpu_info 11 at ffff88001c9b2020, mfn 
612b50, offset 32
[    5.202934] cpu 11 using vcpu_info at ffff88001c9b2020
[    5.202935] Xen: using vcpu_info placement
[    5.202939] Built 1 zonelists in Zone order, mobility grouping on. 
Total pages: 5836648
[    5.202941] Policy zone: Normal
[    5.202943] Kernel command line: placeholder 
root=UUID=8622e268-8845-4cd5-82b3-e7fd0568c602 ro quiet acpi=off
[    5.202967] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    5.203182] Initializing CPU#0
[    5.209000] DMA: Placing 64MB software IO TLB between 
ffff88001c9ce000 - ffff8800209ce000
[    5.209003] DMA: software IO TLB at phys 0x1c9ce000 - 0x209ce000
[    5.209004] xen_swiotlb_fixup: buf=ffff88001c9ce000 size=67108864
[    5.222223] xen_swiotlb_fixup: buf=ffff880020a2e000 size=32768
[    5.301463] Memory: 23166540k/24748612k available (3152k kernel code, 
1057736k absent, 524336k reserved, 2064k data, 604k init)
[    5.301488] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, 
CPUs=12, Nodes=1
[    5.301511] Hierarchical RCU implementation.
[    5.301518] NR_IRQS:4352 nr_irqs:624
[    5.301567] xen: --> irq=0
[    5.301571] xen: --> irq=1
[    5.301573] xen: --> irq=4
[    5.301575] xen: --> irq=6
[    5.301578] xen: --> irq=7
[    5.301580] xen: --> irq=8
[    5.301582] xen: --> irq=9
[    5.301584] xen: --> irq=12
[    5.301587] xen: --> irq=13
[    5.307201] Console: colour VGA+ 80x25
[    5.307217] console [tty0] enabled
[    5.307235] Xen: using vcpuop timer interface
[    5.307237] installing Xen timer for CPU 0
[    5.307242]   alloc irq_desc for 623 on node -1
[    5.307244]   alloc kstat_irqs on node -1
[    5.307257] Detected 3341.682 MHz processor.
[    5.307263] Calibrating delay loop (skipped), value calculated using 
timer frequency.. 6683.36 BogoMIPS (lpj=13366728)
[    5.307275] Security Framework initialized
[    5.307278] SELinux:  Disabled at boot.
[    5.310847] Dentry cache hash table entries: 4194304 (order: 13, 
33554432 bytes)
[    5.317197] Inode-cache hash table entries: 2097152 (order: 12, 
16777216 bytes)
[    5.319518] Mount-cache hash table entries: 256
[    5.319622] Initializing cgroup subsys ns
[    5.319624] Initializing cgroup subsys cpuacct
[    5.319628] Initializing cgroup subsys devices
[    5.319630] Initializing cgroup subsys freezer
[    5.319631] Initializing cgroup subsys net_cls
[    5.319658] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.319660] CPU: L2 cache: 256K
[    5.319661] CPU: L3 cache: 12288K
[    5.319664] CPU 0/0x0 -> Node 0
[    5.319666] CPU: Unsupported number of siblings 32
[    5.319669] mce: CPU supports 9 MCE banks
[    5.319687] Performance Events: unsupported p6 CPU model 44 no PMU 
driver, software events only.
[    5.319697] SMP alternatives: switching to UP code
[    5.337471]   alloc irq_desc for 622 on node -1
[    5.337473]   alloc kstat_irqs on node -1
[    5.337479]   alloc irq_desc for 621 on node -1
[    5.337481]   alloc kstat_irqs on node -1
[    5.337484]   alloc irq_desc for 620 on node -1
[    5.337485]   alloc kstat_irqs on node -1
[    5.337488]   alloc irq_desc for 619 on node -1
[    5.337489]   alloc kstat_irqs on node -1
[    5.337625] installing Xen timer for CPU 1
[    5.337627]   alloc irq_desc for 618 on node -1
[    5.337628]   alloc kstat_irqs on node -1
[    5.337651] SMP alternatives: switching to SMP code
[    5.354623]   alloc irq_desc for 617 on node -1
[    5.354624]   alloc kstat_irqs on node -1
[    5.354635]   alloc irq_desc for 616 on node -1
[    5.354636]   alloc kstat_irqs on node -1
[    5.354639]   alloc irq_desc for 615 on node -1
[    5.354641]   alloc kstat_irqs on node -1
[    5.354644]   alloc irq_desc for 614 on node -1
[    5.354645]   alloc kstat_irqs on node -1
[    5.354655] Initializing CPU#1
[    5.354682] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354684] CPU: L2 cache: 256K
[    5.354684] CPU: L3 cache: 12288K
[    5.354687] CPU 1/0x0 -> Node 0
[    5.354688] CPU: Unsupported number of siblings 32
[    5.354761] installing Xen timer for CPU 2
[    5.354763]   alloc irq_desc for 613 on node -1
[    5.354765]   alloc kstat_irqs on node -1
[    5.354781]   alloc irq_desc for 612 on node -1
[    5.354782]   alloc kstat_irqs on node -1
[    5.354786]   alloc irq_desc for 611 on node -1
[    5.354787]   alloc kstat_irqs on node -1
[    5.354790]   alloc irq_desc for 610 on node -1
[    5.354791]   alloc kstat_irqs on node -1
[    5.354794]   alloc irq_desc for 609 on node -1
[    5.354796]   alloc kstat_irqs on node -1
[    5.354804] Initializing CPU#2
[    5.354829] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354831] CPU: L2 cache: 256K
[    5.354832] CPU: L3 cache: 12288K
[    5.354834] CPU 2/0x0 -> Node 0
[    5.354835] CPU: Unsupported number of siblings 32
[    5.354899] installing Xen timer for CPU 3
[    5.354901]   alloc irq_desc for 608 on node -1
[    5.354903]   alloc kstat_irqs on node -1
[    5.354918]   alloc irq_desc for 607 on node -1
[    5.354919]   alloc kstat_irqs on node -1
[    5.354923]   alloc irq_desc for 606 on node -1
[    5.354924]   alloc kstat_irqs on node -1
[    5.354927]   alloc irq_desc for 605 on node -1
[    5.354928]   alloc kstat_irqs on node -1
[    5.354933]   alloc irq_desc for 604 on node -1
[    5.354934]   alloc kstat_irqs on node -1
[    5.354942] Initializing CPU#3
[    5.354967] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.354969] CPU: L2 cache: 256K
[    5.354970] CPU: L3 cache: 12288K
[    5.354972] CPU 3/0x0 -> Node 0
[    5.354973] CPU: Unsupported number of siblings 32
[    5.355036] installing Xen timer for CPU 4
[    5.355038]   alloc irq_desc for 603 on node -1
[    5.355040]   alloc kstat_irqs on node -1
[    5.355054]   alloc irq_desc for 602 on node -1
[    5.355056]   alloc kstat_irqs on node -1
[    5.355059]   alloc irq_desc for 601 on node -1
[    5.355060]   alloc kstat_irqs on node -1
[    5.355064]   alloc irq_desc for 600 on node -1
[    5.355065]   alloc kstat_irqs on node -1
[    5.355068]   alloc irq_desc for 599 on node -1
[    5.355070]   alloc kstat_irqs on node -1
[    5.355077] Initializing CPU#4
[    5.355102] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355103] CPU: L2 cache: 256K
[    5.355104] CPU: L3 cache: 12288K
[    5.355107] CPU 4/0x0 -> Node 0
[    5.355108] CPU: Unsupported number of siblings 32
[    5.355170] installing Xen timer for CPU 5
[    5.355173]   alloc irq_desc for 598 on node -1
[    5.355174]   alloc kstat_irqs on node -1
[    5.355189]   alloc irq_desc for 597 on node -1
[    5.355190]   alloc kstat_irqs on node -1
[    5.355194]   alloc irq_desc for 596 on node -1
[    5.355195]   alloc kstat_irqs on node -1
[    5.355198]   alloc irq_desc for 595 on node -1
[    5.355200]   alloc kstat_irqs on node -1
[    5.355203]   alloc irq_desc for 594 on node -1
[    5.355204]   alloc kstat_irqs on node -1
[    5.355212] Initializing CPU#5
[    5.355236] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355238] CPU: L2 cache: 256K
[    5.355239] CPU: L3 cache: 12288K
[    5.355241] CPU 5/0x0 -> Node 0
[    5.355242] CPU: Unsupported number of siblings 32
[    5.355308] installing Xen timer for CPU 6
[    5.355311]   alloc irq_desc for 593 on node -1
[    5.355312]   alloc kstat_irqs on node -1
[    5.355329]   alloc irq_desc for 592 on node -1
[    5.355330]   alloc kstat_irqs on node -1
[    5.355334]   alloc irq_desc for 591 on node -1
[    5.355335]   alloc kstat_irqs on node -1
[    5.355339]   alloc irq_desc for 590 on node -1
[    5.355340]   alloc kstat_irqs on node -1
[    5.355343]   alloc irq_desc for 589 on node -1
[    5.355344]   alloc kstat_irqs on node -1
[    5.355352] Initializing CPU#6
[    5.355381] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355384] CPU: L2 cache: 256K
[    5.355385] CPU: L3 cache: 12288K
[    5.355388] CPU 6/0x0 -> Node 0
[    5.355390] CPU: Unsupported number of siblings 32
[    5.355465] installing Xen timer for CPU 7
[    5.355468]   alloc irq_desc for 588 on node -1
[    5.355469]   alloc kstat_irqs on node -1
[    5.355484]   alloc irq_desc for 587 on node -1
[    5.355486]   alloc kstat_irqs on node -1
[    5.355489]   alloc irq_desc for 586 on node -1
[    5.355491]   alloc kstat_irqs on node -1
[    5.355494]   alloc irq_desc for 585 on node -1
[    5.355495]   alloc kstat_irqs on node -1
[    5.355499]   alloc irq_desc for 584 on node -1
[    5.355500]   alloc kstat_irqs on node -1
[    5.355507] Initializing CPU#7
[    5.355529] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355530] CPU: L2 cache: 256K
[    5.355531] CPU: L3 cache: 12288K
[    5.355534] CPU 7/0x0 -> Node 0
[    5.355535] CPU: Unsupported number of siblings 32
[    5.355600] installing Xen timer for CPU 8
[    5.355602]   alloc irq_desc for 583 on node -1
[    5.355604]   alloc kstat_irqs on node -1
[    5.355619]   alloc irq_desc for 582 on node -1
[    5.355620]   alloc kstat_irqs on node -1
[    5.355624]   alloc irq_desc for 581 on node -1
[    5.355625]   alloc kstat_irqs on node -1
[    5.355630]   alloc irq_desc for 580 on node -1
[    5.355631]   alloc kstat_irqs on node -1
[    5.355634]   alloc irq_desc for 579 on node -1
[    5.355636]   alloc kstat_irqs on node -1
[    5.355643] Initializing CPU#8
[    5.355665] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355666] CPU: L2 cache: 256K
[    5.355667] CPU: L3 cache: 12288K
[    5.355669] CPU 8/0x0 -> Node 0
[    5.355671] CPU: Unsupported number of siblings 32
[    5.355733] installing Xen timer for CPU 9
[    5.355735]   alloc irq_desc for 578 on node -1
[    5.355737]   alloc kstat_irqs on node -1
[    5.355751]   alloc irq_desc for 577 on node -1
[    5.355752]   alloc kstat_irqs on node -1
[    5.355756]   alloc irq_desc for 576 on node -1
[    5.355757]   alloc kstat_irqs on node -1
[    5.355760]   alloc irq_desc for 575 on node -1
[    5.355761]   alloc kstat_irqs on node -1
[    5.355765]   alloc irq_desc for 574 on node -1
[    5.355766]   alloc kstat_irqs on node -1
[    5.355773] Initializing CPU#9
[    5.355795] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355796] CPU: L2 cache: 256K
[    5.355797] CPU: L3 cache: 12288K
[    5.355799] CPU 9/0x0 -> Node 0
[    5.355801] CPU: Unsupported number of siblings 32
[    5.355862] installing Xen timer for CPU 10
[    5.355865]   alloc irq_desc for 573 on node -1
[    5.355866]   alloc kstat_irqs on node -1
[    5.355880]   alloc irq_desc for 572 on node -1
[    5.355882]   alloc kstat_irqs on node -1
[    5.355885]   alloc irq_desc for 571 on node -1
[    5.355887]   alloc kstat_irqs on node -1
[    5.355890]   alloc irq_desc for 570 on node -1
[    5.355891]   alloc kstat_irqs on node -1
[    5.355896]   alloc irq_desc for 569 on node -1
[    5.355897]   alloc kstat_irqs on node -1
[    5.355904] Initializing CPU#10
[    5.355926] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.355928] CPU: L2 cache: 256K
[    5.355928] CPU: L3 cache: 12288K
[    5.355931] CPU 10/0x0 -> Node 0
[    5.355932] CPU: Unsupported number of siblings 32
[    5.355995] installing Xen timer for CPU 11
[    5.355997]   alloc irq_desc for 568 on node -1
[    5.355999]   alloc kstat_irqs on node -1
[    5.356013]   alloc irq_desc for 567 on node -1
[    5.356014]   alloc kstat_irqs on node -1
[    5.356018]   alloc irq_desc for 566 on node -1
[    5.356019]   alloc kstat_irqs on node -1
[    5.356022]   alloc irq_desc for 565 on node -1
[    5.356024]   alloc kstat_irqs on node -1
[    5.356027]   alloc irq_desc for 564 on node -1
[    5.356028]   alloc kstat_irqs on node -1
[    5.356035] Initializing CPU#11
[    5.356057] CPU: L1 I cache: 32K, L1 D cache: 32K
[    5.356059] CPU: L2 cache: 256K
[    5.356059] CPU: L3 cache: 12288K
[    5.356062] CPU 11/0x0 -> Node 0
[    5.356063] CPU: Unsupported number of siblings 32
[    5.356090] Brought up 12 CPUs
[    5.356124] CPU0 attaching sched-domain:
[    5.356127]  domain 0: span 0-11 level CPU
[    5.356129]   groups: group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11
[    5.356144] CPU1 attaching sched-domain:
[    5.356145]  domain 0: span 0-11 level CPU
[    5.356147]   groups: group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0
[    5.356161] CPU2 attaching sched-domain:
[    5.356163]  domain 0: span 0-11 level CPU
[    5.356165]   groups: group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1
[    5.356179] CPU3 attaching sched-domain:
[    5.356180]  domain 0: span 0-11 level CPU
[    5.356182]   groups: group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2
[    5.356196] CPU4 attaching sched-domain:
[    5.356198]  domain 0: span 0-11 level CPU
[    5.356200]   groups: group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3
[    5.356214] CPU5 attaching sched-domain:
[    5.356215]  domain 0: span 0-11 level CPU
[    5.356217]   groups: group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4
[    5.356231] CPU6 attaching sched-domain:
[    5.356232]  domain 0: span 0-11 level CPU
[    5.356234]   groups: group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5
[    5.356248] CPU7 attaching sched-domain:
[    5.356250]  domain 0: span 0-11 level CPU
[    5.356252]   groups: group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6
[    5.356266] CPU8 attaching sched-domain:
[    5.356267]  domain 0: span 0-11 level CPU
[    5.356269]   groups: group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9 group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7
[    5.356283] CPU9 attaching sched-domain:
[    5.356285]  domain 0: span 0-11 level CPU
[    5.356286]   groups: group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10 group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8
[    5.356301] CPU10 attaching sched-domain:
[    5.356302]  domain 0: span 0-11 level CPU
[    5.356304]   groups: group ffff88001c998d00 cpus 10 group 
ffff88001c9b6d00 cpus 11 group ffff88001c86cd00 cpus 0 group 
ffff88001c88ad00 cpus 1 group ffff88001c8a8d00 cpus 2 group 
ffff88001c8c6d00 cpus 3 group ffff88001c8e4d00 cpus 4 group 
ffff88001c902d00 cpus 5 group ffff88001c920d00 cpus 6 group 
ffff88001c93ed00 cpus 7 group ffff88001c95cd00 cpus 8 group 
ffff88001c97ad00 cpus 9
[    5.356318] CPU11 attaching sched-domain:
[    5.356319]  domain 0: span 0-11 level CPU
[    5.356321]   groups: group ffff88001c9b6d00 cpus 11 group 
ffff88001c86cd00 cpus 0 group ffff88001c88ad00 cpus 1 group 
ffff88001c8a8d00 cpus 2 group ffff88001c8c6d00 cpus 3 group 
ffff88001c8e4d00 cpus 4 group ffff88001c902d00 cpus 5 group 
ffff88001c920d00 cpus 6 group ffff88001c93ed00 cpus 7 group 
ffff88001c95cd00 cpus 8 group ffff88001c97ad00 cpus 9 group 
ffff88001c998d00 cpus 10
[    5.356702] devtmpfs: initialized
[    5.359462] Grant table initialized
[    5.359464] regulator: core version 0.5
[    5.359505] NET: Registered protocol family 16
[    5.359544]   alloc irq_desc for 563 on node -1
[    5.359545]   alloc kstat_irqs on node -1
[    5.359642] sync cpu 0 get result 1 max_id b
[    5.359648] sync cpu 1 get result 1 max_id b
[    5.359653] sync cpu 2 get result 1 max_id b
[    5.359659] sync cpu 3 get result 1 max_id b
[    5.359665] sync cpu 4 get result 1 max_id b
[    5.359671] sync cpu 5 get result 1 max_id b
[    5.359678] sync cpu 6 get result 1 max_id b
[    5.359684] sync cpu 7 get result 1 max_id b
[    5.359689] sync cpu 8 get result 1 max_id b
[    5.359695] sync cpu 9 get result 1 max_id b
[    5.359701] sync cpu a get result 1 max_id b
[    5.359707] sync cpu b get result 1 max_id b
[    5.359709]   alloc irq_desc for 562 on node -1
[    5.359711]   alloc kstat_irqs on node -1
[    5.359762] PCI: Using configuration type 1 for base access
[    5.360880] bio: create slab  at 0
[    5.361122] ACPI: Interpreter disabled.
[    5.361141] xen_balloon: Initialising balloon driver with page order 0.
[    5.361174] vgaarb: loaded
[    5.361221] PCI: Probing PCI hardware
[    5.361223] PCI: Probing PCI hardware (bus 00)
[    5.361335] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[    5.361339] pci 0000:00:00.0: PME# disabled
[    5.361460] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    5.361464] pci 0000:00:01.0: PME# disabled
[    5.361587] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[    5.361591] pci 0000:00:03.0: PME# disabled
[    5.361718] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    5.361722] pci 0000:00:07.0: PME# disabled
[    5.362123] pci 0000:00:1a.0: reg 20 io port: [0xbc00-0xbc1f]
[    5.362235] pci 0000:00:1a.1: reg 20 io port: [0xb880-0xb89f]
[    5.362348] pci 0000:00:1a.2: reg 20 io port: [0xb800-0xb81f]
[    5.362466] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf9ffe000-0xf9ffe3ff]
[    5.362570] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[    5.362575] pci 0000:00:1a.7: PME# disabled
[    5.362692] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    5.362696] pci 0000:00:1c.0: PME# disabled
[    5.362814] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    5.362818] pci 0000:00:1c.4: PME# disabled
[    5.362894] pci 0000:00:1d.0: reg 20 io port: [0xb480-0xb49f]
[    5.363002] pci 0000:00:1d.1: reg 20 io port: [0xb400-0xb41f]
[    5.363111] pci 0000:00:1d.2: reg 20 io port: [0xb080-0xb09f]
[    5.363224] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf9ffc000-0xf9ffc3ff]
[    5.363324] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[    5.363329] pci 0000:00:1d.7: PME# disabled
[    5.363526] pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
[    5.363543] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 
0a00 (mask 00ff)
[    5.363546] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 
0a00 (mask 0017)
[    5.363550] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 
4700 (mask 00ff)
[    5.363657] pci 0000:00:1f.2: reg 10 io port: [0xb000-0xb007]
[    5.363664] pci 0000:00:1f.2: reg 14 io port: [0xac00-0xac03]
[    5.363671] pci 0000:00:1f.2: reg 18 io port: [0xa880-0xa887]
[    5.363679] pci 0000:00:1f.2: reg 1c io port: [0xa800-0xa803]
[    5.363686] pci 0000:00:1f.2: reg 20 io port: [0xa480-0xa49f]
[    5.363693] pci 0000:00:1f.2: reg 24 32bit mmio: [0xf9ffa000-0xf9ffa7ff]
[    5.363762] pci 0000:00:1f.2: PME# supported from D3hot
[    5.363767] pci 0000:00:1f.2: PME# disabled
[    5.363807] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf9ff9c00-0xf9ff9cff]
[    5.363826] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[    5.363946] pci 0000:02:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
[    5.363959] pci 0000:02:00.0: reg 14 64bit mmio pref: 
[0xd0000000-0xdfffffff]
[    5.363971] pci 0000:02:00.0: reg 1c 64bit mmio pref: 
[0xce000000-0xcfffffff]
[    5.363978] pci 0000:02:00.0: reg 24 io port: [0xcc00-0xcc7f]
[    5.363985] pci 0000:02:00.0: reg 30 32bit mmio pref: 
[0xfbc80000-0xfbcfffff]
[    5.364089] pci 0000:02:00.1: reg 10 32bit mmio: [0xfbc7c000-0xfbc7ffff]
[    5.371581] pci 0000:00:03.0: bridge io port: [0xc000-0xcfff]
[    5.371586] pci 0000:00:03.0: bridge 32bit mmio: [0xfa000000-0xfbcfffff]
[    5.371592] pci 0000:00:03.0: bridge 64bit mmio pref: 
[0xce000000-0xdfffffff]
[    5.371763] pci 0000:06:00.0: reg 10 io port: [0xe800-0xe8ff]
[    5.371788] pci 0000:06:00.0: reg 18 64bit mmio: [0xfbeff000-0xfbefffff]
[    5.371806] pci 0000:06:00.0: reg 20 64bit mmio pref: 
[0xf8ff0000-0xf8ffffff]
[    5.371816] pci 0000:06:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[    5.371905] pci 0000:06:00.0: supports D1 D2
[    5.371906] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    5.371912] pci 0000:06:00.0: PME# disabled
[    5.379587] pci 0000:00:1c.4: bridge io port: [0xe000-0xefff]
[    5.379592] pci 0000:00:1c.4: bridge 32bit mmio: [0xfbe00000-0xfbefffff]
[    5.379600] pci 0000:00:1c.4: bridge 64bit mmio pref: 
[0xf8f00000-0xf8ffffff]
[    5.379663] pci 0000:00:1e.0: transparent bridge
[    5.380048] vgaarb: device added: 
PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
[    5.380182] PCI: Discovered primary peer bus 05 [IRQ]
[    5.380196] pci 0000:00:1f.0: PIIX/ICH IRQ router [8086:3a16]
[    5.380438] Switching to clocksource xen
[    5.381744] pnp: PnP ACPI: disabled
[    5.382245] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[    5.382246] pci 0000:00:01.0:   IO window: disabled
[    5.382251] pci 0000:00:01.0:   MEM window: disabled
[    5.382255] pci 0000:00:01.0:   PREFETCH window: disabled
[    5.382262] pci 0000:00:03.0: PCI bridge, secondary bus 0000:02
[    5.382265] pci 0000:00:03.0:   IO window: 0xc000-0xcfff
[    5.382270] pci 0000:00:03.0:   MEM window: 0xfa000000-0xfbcfffff
[    5.382274] pci 0000:00:03.0:   PREFETCH window: 
0x000000ce000000-0x000000dfffffff
[    5.382281] pci 0000:00:07.0: PCI bridge, secondary bus 0000:03
[    5.382282] pci 0000:00:07.0:   IO window: disabled
[    5.382287] pci 0000:00:07.0:   MEM window: disabled
[    5.382291] pci 0000:00:07.0:   PREFETCH window: disabled
[    5.382297] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
[    5.382300] pci 0000:00:1c.0:   IO window: 0x1000-0x1fff
[    5.382306] pci 0000:00:1c.0:   MEM window: 0xc0000000-0xc01fffff
[    5.382310] pci 0000:00:1c.0:   PREFETCH window: 
0x000000c0200000-0x000000c03fffff
[    5.382318] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:06
[    5.382321] pci 0000:00:1c.4:   IO window: 0xe000-0xefff
[    5.382327] pci 0000:00:1c.4:   MEM window: 0xfbe00000-0xfbefffff
[    5.382331] pci 0000:00:1c.4:   PREFETCH window: 
0x000000f8f00000-0x000000f8ffffff
[    5.382338] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:07
[    5.382340] pci 0000:00:1e.0:   IO window: disabled
[    5.382345] pci 0000:00:1e.0:   MEM window: disabled
[    5.382349] pci 0000:00:1e.0:   PREFETCH window: disabled
[    5.382366] pci 0000:00:01.0: setting latency timer to 64
[    5.382378] pci 0000:00:03.0: setting latency timer to 64
[    5.382390] pci 0000:00:07.0: setting latency timer to 64
[    5.382399] pci 0000:00:1c.0: enabling device (0104 -> 0107)
[    5.382407] PCI: setting IRQ 5 as level-triggered
[    5.382410] pci 0000:00:1c.0: found PCI INT A -> IRQ 5
[    5.382435] pci 0000:00:1c.0: sharing IRQ 5 with 0000:00:1c.4
[    5.382455] pci 0000:00:1c.0: sharing IRQ 5 with 0000:02:00.1
[    5.382462] pci 0000:00:1c.0: setting latency timer to 64
[    5.382476] pci 0000:00:1c.4: found PCI INT A -> IRQ 5
[    5.382500] pci 0000:00:1c.4: sharing IRQ 5 with 0000:00:1c.0
[    5.382522] pci 0000:00:1c.4: sharing IRQ 5 with 0000:02:00.1
[    5.382529] pci 0000:00:1c.4: setting latency timer to 64
[    5.382537] pci 0000:00:1e.0: setting latency timer to 64
[    5.382541] pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
[    5.382543] pci_bus 0000:00: resource 1 mem: 
[0x000000-0xffffffffffffffff]
[    5.382545] pci_bus 0000:02: resource 0 io:  [0xc000-0xcfff]
[    5.382546] pci_bus 0000:02: resource 1 mem: [0xfa000000-0xfbcfffff]
[    5.382548] pci_bus 0000:02: resource 2 pref mem [0xce000000-0xdfffffff]
[    5.382550] pci_bus 0000:04: resource 0 io:  [0x1000-0x1fff]
[    5.382552] pci_bus 0000:04: resource 1 mem: [0xc0000000-0xc01fffff]
[    5.382553] pci_bus 0000:04: resource 2 pref mem [0xc0200000-0xc03fffff]
[    5.382555] pci_bus 0000:06: resource 0 io:  [0xe000-0xefff]
[    5.382557] pci_bus 0000:06: resource 1 mem: [0xfbe00000-0xfbefffff]
[    5.382558] pci_bus 0000:06: resource 2 pref mem [0xf8f00000-0xf8ffffff]
[    5.382560] pci_bus 0000:07: resource 3 io:  [0x00-0xffff]
[    5.382562] pci_bus 0000:07: resource 4 mem: 
[0x000000-0xffffffffffffffff]
[    5.382564] pci_bus 0000:05: resource 0 io:  [0x00-0xffff]
[    5.382565] pci_bus 0000:05: resource 1 mem: 
[0x000000-0xffffffffffffffff]
[    5.382582] NET: Registered protocol family 2
[    5.383095] IP route cache hash table entries: 524288 (order: 10, 
4194304 bytes)
[    5.384472] TCP established hash table entries: 524288 (order: 11, 
8388608 bytes)
[    5.385620] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    5.385749] TCP: Hash tables configured (established 524288 bind 65536)
[    5.385752] TCP reno registered
[    5.385828] NET: Registered protocol family 1
[    5.385857] PCI: setting IRQ 10 as level-triggered
[    5.385860] pci 0000:00:1a.0: found PCI INT A -> IRQ 10
[    5.385906] pci 0000:00:1a.0: sharing IRQ 10 with 0000:02:00.0
[    5.385912] pci 0000:00:1a.0: sharing IRQ 10 with 0000:06:00.0
[    5.385940] PCI: setting IRQ 15 as level-triggered
[    5.385943] pci 0000:00:1a.1: found PCI INT B -> IRQ 15
[    5.386015] PCI: setting IRQ 11 as level-triggered
[    5.386018] pci 0000:00:1a.2: found PCI INT D -> IRQ 11
[    5.386048] pci 0000:00:1a.2: sharing IRQ 11 with 0000:00:1d.1
[    5.386059] pci 0000:00:1a.2: sharing IRQ 11 with 0000:00:1f.2
[    5.386099] PCI: setting IRQ 14 as level-triggered
[    5.386102] pci 0000:00:1a.7: found PCI INT C -> IRQ 14
[    5.386133] pci 0000:00:1a.7: sharing IRQ 14 with 0000:00:1d.2
[    5.386144] pci 0000:00:1a.7: sharing IRQ 14 with 0000:00:1f.3
[    5.414581] PCI: setting IRQ 3 as level-triggered
[    5.414587] pci 0000:00:1d.0: found PCI INT A -> IRQ 3
[    5.414631] pci 0000:00:1d.0: sharing IRQ 3 with 0000:00:1d.7
[    5.414672] pci 0000:00:1d.1: found PCI INT B -> IRQ 11
[    5.414692] pci 0000:00:1d.1: sharing IRQ 11 with 0000:00:1a.2
[    5.414712] pci 0000:00:1d.1: sharing IRQ 11 with 0000:00:1f.2
[    5.414747] pci 0000:00:1d.2: found PCI INT C -> IRQ 14
[    5.414769] pci 0000:00:1d.2: sharing IRQ 14 with 0000:00:1a.7
[    5.414789] pci 0000:00:1d.2: sharing IRQ 14 with 0000:00:1f.3
[    5.414828] pci 0000:00:1d.7: found PCI INT A -> IRQ 3
[    5.414855] pci 0000:00:1d.7: sharing IRQ 3 with 0000:00:1d.0
[    7.012713] pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 
01010001
[    7.012852] pci 0000:02:00.0: Boot video device
[    7.012895] Unpacking initramfs...
[    7.028884] Freeing initrd memory: 29754k freed
[    7.032797] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    7.032801] DMA: Placing 64MB software IO TLB between 
ffff88001c9ce000 - ffff8800209ce000
[    7.032803] DMA: software IO TLB at phys 0x1c9ce000 - 0x209ce000
[    7.032879] platform rtc_cmos: registered platform RTC device (no PNP 
device found)
[    7.033534] audit: initializing netlink socket (disabled)
[    7.033542] type=2000 audit(1338671115.003:1): initialized
[    7.036697] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    7.037841] VFS: Disk quotas dquot_6.5.2
[    7.037876] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    7.037933] msgmni has been set to 32768
[    7.038334] alg: No test for stdrng (krng)
[    7.038373] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 253)
[    7.038375] io scheduler noop registered
[    7.038376] io scheduler anticipatory registered
[    7.038378] io scheduler deadline registered
[    7.038414] io scheduler cfq registered (default)
[    7.038549]   alloc irq_desc for 561 on node -1
[    7.038551]   alloc kstat_irqs on node -1
[    7.038586] pcieport 0000:00:01.0: setting latency timer to 64
[    7.038728]   alloc irq_desc for 560 on node -1
[    7.038730]   alloc kstat_irqs on node -1
[    7.038750] pcieport 0000:00:03.0: setting latency timer to 64
[    7.038887]   alloc irq_desc for 559 on node -1
[    7.038888]   alloc kstat_irqs on node -1
[    7.038909] pcieport 0000:00:07.0: setting latency timer to 64
[    7.039035]   alloc irq_desc for 558 on node -1
[    7.039037]   alloc kstat_irqs on node -1
[    7.039060] pcieport 0000:00:1c.0: setting latency timer to 64
[    7.039197]   alloc irq_desc for 557 on node -1
[    7.039198]   alloc kstat_irqs on node -1
[    7.039221] pcieport 0000:00:1c.4: setting latency timer to 64
[    7.044790] registering netback
[    7.044866]   alloc irq_desc for 556 on node -1
[    7.044868]   alloc kstat_irqs on node -1
[    7.045652]   alloc irq_desc for 555 on node -1
[    7.045653]   alloc kstat_irqs on node -1
[    7.045810] Linux agpgart interface v0.103
[    7.045838] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    7.046030] input: Macintosh mouse button emulation as 
/devices/virtual/input/input0
[    7.046062] PNP: No PS/2 controller found. Probing ports directly.
[    7.048150] serio: i8042 KBD port at 0x60,0x64 irq 1
[    7.048155] serio: i8042 AUX port at 0x60,0x64 irq 12
[    7.048211] mice: PS/2 mouse device common for all mice
[    7.048258] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    7.048284] rtc0: alarms up to one day, 114 bytes nvram
[    7.048290] cpuidle: using governor ladder
[    7.048292] cpuidle: using governor menu
[    7.048295] No iBFT detected.
[    7.048480] TCP cubic registered
[    7.048554] NET: Registered protocol family 10
[    7.049045] Mobile IPv6
[    7.049047] NET: Registered protocol family 17
[    7.049097] PM: Resume from disk failed.
[    7.049104] registered taskstats version 1
[    7.049703] rtc_cmos rtc_cmos: setting system clock to 2012-06-02 
21:05:14 UTC (1338671114)
[    7.049735] Initalizing network drop monitor service
[    7.049789] Freeing unused kernel memory: 604k freed
[    7.049868] Write protecting the kernel read-only data: 4336k
[    7.070238] udev[168]: starting version 164
[    7.086267] usbcore: registered new interface driver usbfs
[    7.086282] usbcore: registered new interface driver hub
[    7.086319] usbcore: registered new device driver usb
[    7.087969] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    7.087994] r8169 0000:06:00.0: found PCI INT A -> IRQ 10
[    7.088012] r8169 0000:06:00.0: sharing IRQ 10 with 0000:00:1a.0
[    7.088040] r8169 0000:06:00.0: sharing IRQ 10 with 0000:02:00.0
[    7.088093] r8169 0000:06:00.0: setting latency timer to 64
[    7.088146]   alloc irq_desc for 554 on node -1
[    7.088148]   alloc kstat_irqs on node -1
[    7.088497] r8169 0000:06:00.0: eth0: RTL8168c/8111c at 
0xffffc90003024000, 6c:62:6d:a0:72:05, XID 1c4000c0 IRQ 554
[    7.089153] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    7.089171] ehci_hcd 0000:00:1a.7: found PCI INT C -> IRQ 14
[    7.089204] ehci_hcd 0000:00:1a.7: sharing IRQ 14 with 0000:00:1d.2
[    7.089215] ehci_hcd 0000:00:1a.7: sharing IRQ 14 with 0000:00:1f.3
[    7.089241] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[    7.089244] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[    7.089258] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned 
bus number 1
[    7.089302] ehci_hcd 0000:00:1a.7: debug port 1
[    7.090716] uhci_hcd: USB Universal Host Controller Interface driver
[    7.093188] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[    7.093201] ehci_hcd 0000:00:1a.7: request interrupt 14 failed
[    7.093240] ehci_hcd 0000:00:1a.7: USB bus 1 deregistered
[    7.093258] ehci_hcd 0000:00:1a.7: init 0000:00:1a.7 fail, -38
[    7.093298] ehci_hcd: probe of 0000:00:1a.7 failed with error -38
[    7.093328] uhci_hcd 0000:00:1a.0: found PCI INT A -> IRQ 10
[    7.093384] uhci_hcd 0000:00:1a.0: sharing IRQ 10 with 0000:02:00.0
[    7.093400] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[    7.093404] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[    7.093421] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned 
bus number 1
[    7.093451] uhci_hcd 0000:00:1a.0: request interrupt 10 failed
[    7.093494] uhci_hcd 0000:00:1a.0: USB bus 1 deregistered
[    7.093513] uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -38
[    7.093557] uhci_hcd: probe of 0000:00:1a.0 failed with error -38
[    7.093580] ehci_hcd 0000:00:1d.7: found PCI INT A -> IRQ 3
[    7.093608] ehci_hcd 0000:00:1d.7: sharing IRQ 3 with 0000:00:1d.0
[    7.093649] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[    7.093652] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    7.093664] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned 
bus number 1
[    7.093702] ehci_hcd 0000:00:1d.7: debug port 1
[    7.097582] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[    7.097585] ehci_hcd 0000:00:1d.7: request interrupt 3 failed
[    7.097623] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
[    7.097639] ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -38
[    7.097678] ehci_hcd: probe of 0000:00:1d.7 failed with error -38
[    7.097721] uhci_hcd 0000:00:1a.1: found PCI INT B -> IRQ 15
[    7.097789] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[    7.097793] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[    7.097808] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned 
bus number 1
[    7.097837] uhci_hcd 0000:00:1a.1: request interrupt 15 failed
[    7.097879] uhci_hcd 0000:00:1a.1: USB bus 1 deregistered
[    7.097897] uhci_hcd 0000:00:1a.1: init 0000:00:1a.1 fail, -38
[    7.097942] uhci_hcd: probe of 0000:00:1a.1 failed with error -38
[    7.097958] uhci_hcd 0000:00:1a.2: found PCI INT D -> IRQ 11
[    7.097995] uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1d.1
[    7.098009] uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1f.2
[    7.098013] SCSI subsystem initialized
[    7.098028] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[    7.098032] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[    7.098047] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned 
bus number 1
[    7.098077] uhci_hcd 0000:00:1a.2: request interrupt 11 failed
[    7.098120] uhci_hcd 0000:00:1a.2: USB bus 1 deregistered
[    7.098136] uhci_hcd 0000:00:1a.2: init 0000:00:1a.2 fail, -38
[    7.098180] uhci_hcd: probe of 0000:00:1a.2 failed with error -38
[    7.098198] uhci_hcd 0000:00:1d.0: found PCI INT A -> IRQ 3
[    7.098241] uhci_hcd 0000:00:1d.0: sharing IRQ 3 with 0000:00:1d.7
[    7.098267] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[    7.098271] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    7.098285] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned 
bus number 1
[    7.098315] uhci_hcd 0000:00:1d.0: request interrupt 3 failed
[    7.098356] uhci_hcd 0000:00:1d.0: USB bus 1 deregistered
[    7.098373] uhci_hcd 0000:00:1d.0: init 0000:00:1d.0 fail, -38
[    7.098423] uhci_hcd: probe of 0000:00:1d.0 failed with error -38
[    7.098440] uhci_hcd 0000:00:1d.1: found PCI INT B -> IRQ 11
[    7.098466] uhci_hcd 0000:00:1d.1: sharing IRQ 11 with 0000:00:1a.2
[    7.098493] uhci_hcd 0000:00:1d.1: sharing IRQ 11 with 0000:00:1f.2
[    7.098512] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[    7.098516] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    7.098531] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned 
bus number 1
[    7.098560] uhci_hcd 0000:00:1d.1: request interrupt 11 failed
[    7.098602] uhci_hcd 0000:00:1d.1: USB bus 1 deregistered
[    7.098618] uhci_hcd 0000:00:1d.1: init 0000:00:1d.1 fail, -38
[    7.098672] uhci_hcd: probe of 0000:00:1d.1 failed with error -38
[    7.098687] uhci_hcd 0000:00:1d.2: found PCI INT C -> IRQ 14
[    7.098710] uhci_hcd 0000:00:1d.2: sharing IRQ 14 with 0000:00:1a.7
[    7.098730] uhci_hcd 0000:00:1d.2: sharing IRQ 14 with 0000:00:1f.3
[    7.098744] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[    7.098747] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.098759] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned 
bus number 1
[    7.098784] uhci_hcd 0000:00:1d.2: request interrupt 14 failed
[    7.098821] uhci_hcd 0000:00:1d.2: USB bus 1 deregistered
[    7.098833] uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -38
[    7.098871] uhci_hcd: probe of 0000:00:1d.2 failed with error -38
[    7.099958] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input1
[    7.106033] libata version 3.00 loaded.
[    7.107791] ahci 0000:00:1f.2: version 3.0
[    7.107806] ahci 0000:00:1f.2: found PCI INT B -> IRQ 11
[    7.107826] ahci 0000:00:1f.2: sharing IRQ 11 with 0000:00:1a.2
[    7.107837] ahci 0000:00:1f.2: sharing IRQ 11 with 0000:00:1d.1
[    7.107895]   alloc irq_desc for 553 on node -1
[    7.107897]   alloc kstat_irqs on node -1
[    7.107934] ahci: SSS flag set, parallel bus scan disabled
[    7.107968] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 
0x3f impl SATA mode
[    7.107971] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo 
pio slum part ccc ems sxs
[    7.107976] ahci 0000:00:1f.2: setting latency timer to 64
[    7.144788] scsi0 : ahci
[    7.144855] scsi1 : ahci
[    7.144917] scsi2 : ahci
[    7.144970] scsi3 : ahci
[    7.145031] scsi4 : ahci
[    7.145090] scsi5 : ahci
[    7.145117] ata1: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa100 irq 553
[    7.145119] ata2: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa180 irq 553
[    7.145122] ata3: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa200 irq 553
[    7.145124] ata4: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa280 irq 553
[    7.145126] ata5: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa300 irq 553
[    7.145128] ata6: SATA max UDMA/133 abar m2048@0xf9ffa000 port 
0xf9ffa380 irq 553
[    7.460723] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    7.489450] ata1.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    7.489455] ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    7.531403] ata1.00: configured for UDMA/133
[    7.548813] scsi 0:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    8.272724] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    8.301405] ata2.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    8.301410] ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.343349] ata2.00: configured for UDMA/133
[    8.356815] scsi 1:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    9.080722] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.112504] ata3.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    9.112509] ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.154542] ata3.00: configured for UDMA/133
[    9.168803] scsi 2:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[    9.892720] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.921522] ata4.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[    9.921526] ata4.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.963596] ata4.00: configured for UDMA/133
[    9.976797] scsi 3:0:0:0: Direct-Access     ATA      ST31500341AS 
  CC1H PQ: 0 ANSI: 5
[   10.296721] ata5: SATA link down (SStatus 0 SControl 300)
[   10.636718] ata6: SATA link down (SStatus 0 SControl 300)
[   10.656678] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.656739] sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.656742] sd 0:0:0:0: [sda] Write Protect is off
[   10.656743] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   10.656776] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.656801] sd 1:0:0:0: [sdb] Write Protect is off
[   10.656803] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   10.656823] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.656921]  sda:
[   10.656964]  sdb:
[   10.657032] sd 2:0:0:0: [sdc] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.657079] sd 2:0:0:0: [sdc] Write Protect is off
[   10.657081] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   10.657101] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.657204]  sdc:
[   10.657358] sd 3:0:0:0: [sdd] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[   10.657411] sd 3:0:0:0: [sdd] Write Protect is off
[   10.657413] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[   10.657432] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[   10.657534]  sdd: sda1 sda2 sda3 sda4
[   10.672225] sd 0:0:0:0: [sda] Attached SCSI disk
[   10.674742]  sdd1 sdd2 sdd3 sdd4
[   10.675145] sd 3:0:0:0: [sdd] Attached SCSI disk
[   10.680425]  sdb1 sdb2 sdb3 sdb4
[   10.680814] sd 1:0:0:0: [sdb] Attached SCSI disk
[   10.681216]  sdc1 sdc2 sdc3 sdc4
[   10.681606] sd 2:0:0:0: [sdc] Attached SCSI disk
[   10.951914] md: raid0 personality registered for level 0
[   10.954707] md: raid1 personality registered for level 1
[   10.956749] async_tx: api initialized (async)
[   10.957166] xor: automatically using best checksumming function: 
generic_sse
[   10.974529]    generic_sse:  3767.000 MB/sec
[   10.974531] xor: using function: generic_sse (3767.000 MB/sec)
[   11.042533] raid6: int64x1   3356 MB/s
[   11.110540] raid6: int64x2   4270 MB/s
[   11.178539] raid6: int64x4   2984 MB/s
[   11.246548] raid6: int64x8   2948 MB/s
[   11.314528] raid6: sse2x1    7702 MB/s
[   11.382535] raid6: sse2x2    8938 MB/s
[   11.450532] raid6: sse2x4   10054 MB/s
[   11.450534] raid6: using algorithm sse2x4 (10054 MB/s)
[   11.453150] md: raid6 personality registered for level 6
[   11.453152] md: raid5 personality registered for level 5
[   11.453153] md: raid4 personality registered for level 4
[   11.457829] md: raid10 personality registered for level 10
[   11.460193] 3ware Storage Controller device driver for Linux 
v1.26.02.002.
[   11.462762] 3ware 9000 Storage Controller device driver for Linux 
v2.26.02.013.
[   11.465865] Adaptec aacraid driver 1.1-7[28000]-ms
[   11.526546] mdadm: sending ioctl 1261 to a partition!
[   11.526548] mdadm: sending ioctl 1261 to a partition!
[   11.526852] mdadm: sending ioctl 1261 to a partition!
[   11.526856] mdadm: sending ioctl 1261 to a partition!
[   11.527149] mdadm: sending ioctl 1261 to a partition!
[   11.527151] mdadm: sending ioctl 1261 to a partition!
[   11.527537] mdadm: sending ioctl 1261 to a partition!
[   11.527541] mdadm: sending ioctl 1261 to a partition!
[   11.528129] mdadm: sending ioctl 1261 to a partition!
[   11.528133] mdadm: sending ioctl 1261 to a partition!
[   11.535445] md: md0 stopped.
[   11.537450] md: bind
[   11.537671] md: bind
[   11.539210] md: bind
[   11.540397] md: bind
[   11.541627] raid1: raid set md0 active with 4 out of 4 mirrors
[   11.541643] md0: detected capacity change from 0 to 2152923136
[   11.542611]  md0:
[   11.547251] md: md1 stopped.
[   11.548846] md: bind
[   11.549072] md: bind
[   11.551287] md: bind
[   11.552226] md: bind
[   11.553468] raid1: raid set md1 active with 4 out of 4 mirrors
[   11.553483] md1: detected capacity change from 0 to 271319040
[   11.554467]  md1:
[   11.561426] md: md2 stopped.
[   11.571044]  unknown partition table
[   11.580029] md: bind
[   11.580454] md: bind
[   11.580723] md: bind
[   11.583198] md: bind
[   11.584396] raid5: device sda3 operational as raid disk 0
[   11.584398] raid5: device sdd3 operational as raid disk 3
[   11.584399] raid5: device sdc3 operational as raid disk 2
[   11.584401] raid5: device sdb3 operational as raid disk 1
[   11.584857] raid5: allocated 4282kB for md2
[   11.584884] 0: w=1 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584887] 3: w=2 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584888] 2: w=3 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584890] 1: w=4 pa=0 pr=4 m=2 a=2 r=4 op1=0 op2=0
[   11.584892] raid5: raid level 6 set md2 active with 4 out of 4 
devices, algorithm 2
[   11.584893] RAID5 conf printout:
[   11.584894]  --- rd:4 wd:4
[   11.584896]  disk 0, o:1, dev:sda3
[   11.584897]  disk 1, o:1, dev:sdb3
[   11.584899]  disk 2, o:1, dev:sdc3
[   11.584900]  disk 3, o:1, dev:sdd3
[   11.584921] md2: detected capacity change from 0 to 4309909504
[   11.585918]  md2: unknown partition table
[   11.593292] md: md3 stopped.
[   11.610190] md: bind
[   11.617251] md: bind
[   11.622250] md: bind
[   11.623085] md: bind
[   11.624231] raid5: device sda4 operational as raid disk 0
[   11.624234] raid5: device sdd4 operational as raid disk 3
[   11.624235] raid5: device sdc4 operational as raid disk 2
[   11.624237] raid5: device sdb4 operational as raid disk 1
[   11.624500] raid5: allocated 4282kB for md3
[   11.624529] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624531] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624533] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624535] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[   11.624536] raid5: raid level 5 set md3 active with 4 out of 4 
devices, algorithm 2
[   11.624538] RAID5 conf printout:
[   11.624539]  --- rd:4 wd:4
[   11.624540]  disk 0, o:1, dev:sda4
[   11.624542]  disk 1, o:1, dev:sdb4
[   11.624543]  disk 2, o:1, dev:sdc4
[   11.624544]  disk 3, o:1, dev:sdd4
[   11.624561] md3: detected capacity change from 0 to 4487149780992
[   11.625561]  md3: unknown partition table
[   11.630945] device-mapper: uevent: version 1.0.3
[   11.631026] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) 
initialised: dm-devel@redhat.com
[   11.737748] PM: Starting manual resume from disk
[   11.737750] PM: Resume from partition 8:1
[   11.737752] PM: Checking hibernation image.
[   11.738408] PM: Error -22 checking image file
[   11.738411] PM: Resume from disk failed.
[   11.747092] EXT3-fs: INFO: recovery required on readonly filesystem.
[   11.747096] EXT3-fs: write access will be enabled during recovery.
[   12.001862] kjournald starting.  Commit interval 5 seconds
[   12.001870] EXT3-fs: recovery complete.
[   12.005811] EXT3-fs: mounted filesystem with ordered data mode.
[   12.850243] udev[455]: starting version 164
[   13.003403] input: PC Speaker as /devices/platform/pcspkr/input/input2
[   13.007911] i801_smbus 0000:00:1f.3: found PCI INT C -> IRQ 14
[   13.007935] i801_smbus 0000:00:1f.3: sharing IRQ 14 with 0000:00:1a.7
[   13.007947] i801_smbus 0000:00:1f.3: sharing IRQ 14 with 0000:00:1d.2
[   13.372002] Error: Driver 'pcspkr' is already registered, aborting...
[   13.432617] HDA Intel 0000:02:00.1: found PCI INT B -> IRQ 5
[   13.432668] hda_intel: Disable MSI for Nvidia chipset
[   13.432719] hda-intel: unable to grab IRQ 5, disabling device
[   13.432783] HDA Intel: probe of 0000:02:00.1 failed with error -16
[   13.763984] Adding 2102456k swap on /dev/md0.  Priority:-1 extents:1 
across:2102456k
[   13.766656] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   13.780065] EXT3 FS on md2, internal journal
[   13.854472] loop: module loaded
[   14.332498] kjournald starting.  Commit interval 5 seconds
[   14.332518] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   14.332924] EXT3 FS on md1, internal journal
[   14.332929] EXT3-fs: recovery complete.
[   14.333462] EXT3-fs: mounted filesystem with ordered data mode.
[   14.440947] kjournald starting.  Commit interval 5 seconds
[   14.440953] EXT3-fs warning: maximal mount count reached, running 
e2fsck is recommended
[   14.487241] EXT3 FS on md3, internal journal
[   14.487246] EXT3-fs: recovery complete.
[   14.487250] EXT3-fs: mounted filesystem with ordered data mode.
[   14.840198] r8169 0000:06:00.0: eth0: link down
[   14.840206] r8169 0000:06:00.0: eth0: link down
[   14.841221] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.343001] fuse init (API version 7.13)
[   15.537238] Event-channel device installed.
[   15.837972]   alloc irq_desc for 552 on node -1
[   15.837974]   alloc kstat_irqs on node -1
[   15.838004]   alloc irq_desc for 551 on node -1
[   15.838006]   alloc kstat_irqs on node -1
[   15.838156] XENBUS: Unable to read cpu state
[   15.838277] XENBUS: Unable to read cpu state
[   15.838423] XENBUS: Unable to read cpu state
[   15.838532] XENBUS: Unable to read cpu state
[   15.838640] XENBUS: Unable to read cpu state
[   15.838748] XENBUS: Unable to read cpu state
[   15.838854] XENBUS: Unable to read cpu state
[   15.838960] XENBUS: Unable to read cpu state
[   15.839065] XENBUS: Unable to read cpu state
[   15.839171] XENBUS: Unable to read cpu state
[   15.839276] XENBUS: Unable to read cpu state
[   15.839384] XENBUS: Unable to read cpu state
[   16.797692] Bridge firewalling registered
[   17.488275] r8169 0000:06:00.0: eth0: link up
[   17.489372] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   28.396708] eth0: no IPv6 routers present
[   50.109845]   alloc irq_desc for 550 on node -1
[   50.109848]   alloc kstat_irqs on node -1
[   50.297549]   alloc irq_desc for 549 on node -1
[   50.297552]   alloc kstat_irqs on node -1
[   50.379961] ip_tables: (C) 2000-2006 Netfilter Core Team
[   50.457516] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   50.457685] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. 
Please use
[   50.457687] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack 
module option or
[   50.457688] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[   50.488368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.499377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.501009] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   50.501012] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   51.972953] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   51.972985]   alloc irq_desc for 548 on node -1
[   51.972988]   alloc kstat_irqs on node -1
[   51.981918] blkback: ring-ref 768, event-channel 64, protocol 1 
(x86_64-abi)
[   51.981934]   alloc irq_desc for 547 on node -1
[   51.981936]   alloc kstat_irqs on node -1
[   51.999287] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   51.999302]   alloc irq_desc for 546 on node -1
[   51.999304]   alloc kstat_irqs on node -1
[   52.007159]   alloc irq_desc for 545 on node -1
[   52.007162]   alloc kstat_irqs on node -1
[   58.633380]   alloc irq_desc for 544 on node -1
[   58.633383]   alloc kstat_irqs on node -1
[   58.837769] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.837773] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839540] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839543] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.839545] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841606] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841610] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.841612] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843266] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843269] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843272] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.843274] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   58.892320]   alloc irq_desc for 543 on node -1
[   58.892322]   alloc kstat_irqs on node -1
[   59.486087] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   59.486116]   alloc irq_desc for 542 on node -1
[   59.486118]   alloc kstat_irqs on node -1
[   59.496936] blkback: ring-ref 9, event-channel 64, protocol 1 
(x86_64-abi)
[   59.496949]   alloc irq_desc for 541 on node -1
[   59.496950]   alloc kstat_irqs on node -1
[   59.507401] blkback: ring-ref 10, event-channel 65, protocol 1 
(x86_64-abi)
[   59.507413]   alloc irq_desc for 540 on node -1
[   59.507415]   alloc kstat_irqs on node -1
[   59.614676]   alloc irq_desc for 539 on node -1
[   59.614678]   alloc kstat_irqs on node -1
[   60.332661] vif1.0: no IPv6 routers present
[   68.884954] vif2.0: no IPv6 routers present
[   70.590651]   alloc irq_desc for 538 on node -1
[   70.590654]   alloc kstat_irqs on node -1
[   70.771436] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771441] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771443] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.771445] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773897] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773900] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773903] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773905] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.773907] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776415] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776419] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776423] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776425] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.776428] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778274] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778279] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778283] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778286] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778289] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.778292] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   70.839351]   alloc irq_desc for 537 on node -1
[   70.839354]   alloc kstat_irqs on node -1
[   71.467841]   alloc irq_desc for 536 on node -1
[   71.467844]   alloc kstat_irqs on node -1
[   71.468493] blkback: ring-ref 770, event-channel 64, protocol 1 
(x86_64-abi)
[   71.468505]   alloc irq_desc for 535 on node -1
[   71.468507]   alloc kstat_irqs on node -1
[   71.483003] blkback: ring-ref 771, event-channel 65, protocol 1 
(x86_64-abi)
[   71.483018]   alloc irq_desc for 534 on node -1
[   71.483020]   alloc kstat_irqs on node -1
[   71.491437] blkback: ring-ref 772, event-channel 66, protocol 1 
(x86_64-abi)
[   71.491450]   alloc irq_desc for 533 on node -1
[   71.491452]   alloc kstat_irqs on node -1
[   77.077466]   alloc irq_desc for 532 on node -1
[   77.077469]   alloc kstat_irqs on node -1
[   77.394365] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394370] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394373] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394375] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.394377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396069] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396072] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396075] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396077] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396079] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396081] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.396083] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398424] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398427] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398430] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398432] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398435] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398438] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.398441] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400189] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400193] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400195] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400197] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400199] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400201] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400203] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.400205] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   77.443743]   alloc irq_desc for 531 on node -1
[   77.443745]   alloc kstat_irqs on node -1
[   78.076700] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   78.076735]   alloc irq_desc for 530 on node -1
[   78.076736]   alloc kstat_irqs on node -1
[   78.088947] blkback: ring-ref 770, event-channel 65, protocol 1 
(x86_64-abi)
[   78.088962]   alloc irq_desc for 529 on node -1
[   78.088963]   alloc kstat_irqs on node -1
[   78.153935]   alloc irq_desc for 528 on node -1
[   78.153937]   alloc kstat_irqs on node -1
[   78.154545] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   78.154559]   alloc irq_desc for 527 on node -1
[   78.154561]   alloc kstat_irqs on node -1
[   78.160284] blkback: ring-ref 772, event-channel 67, protocol 1 
(x86_64-abi)
[   78.160299]   alloc irq_desc for 526 on node -1
[   78.160300]   alloc kstat_irqs on node -1
[   81.741939] vif3.0: no IPv6 routers present
[   83.257645]   alloc irq_desc for 525 on node -1
[   83.257647]   alloc kstat_irqs on node -1
[   83.450601] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450606] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450608] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450610] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450612] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450614] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450616] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.450619] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452519] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452522] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452524] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452528] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452530] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452532] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452534] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452536] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.452538] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455134] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455138] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455141] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455144] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455147] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455149] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455152] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455155] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.455157] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457355] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457359] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457361] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457363] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457366] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457368] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457370] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457373] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457375] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.457377] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   83.493883]   alloc irq_desc for 524 on node -1
[   83.493886]   alloc kstat_irqs on node -1
[   84.988630] blkback: ring-ref 8, event-channel 63, protocol 1 
(x86_64-abi)
[   84.988671]   alloc irq_desc for 523 on node -1
[   84.988673]   alloc kstat_irqs on node -1
[   84.999610] blkback: ring-ref 768, event-channel 64, protocol 1 
(x86_64-abi)
[   84.999635]   alloc irq_desc for 522 on node -1
[   84.999636]   alloc kstat_irqs on node -1
[   85.019939] blkback: ring-ref 771, event-channel 66, protocol 1 
(x86_64-abi)
[   85.019955]   alloc irq_desc for 521 on node -1
[   85.019957]   alloc kstat_irqs on node -1
[   85.032714]   alloc irq_desc for 520 on node -1
[   85.032717]   alloc kstat_irqs on node -1
[   87.492584] vif4.0: no IPv6 routers present
[   89.980170]   alloc irq_desc for 519 on node -1
[   89.980173]   alloc kstat_irqs on node -1
[   90.140856] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140861] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140864] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140867] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140870] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140872] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140875] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140878] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140881] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.140884] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142965] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142968] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142970] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142972] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142974] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142977] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142979] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142981] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142983] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142985] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.142987] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145194] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145197] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145200] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145202] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145204] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145206] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145208] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145210] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145213] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145215] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.145217] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147500] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147504] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147507] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147510] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147513] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147516] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147518] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147523] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147525] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147528] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147531] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.147534] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[   90.197690]   alloc irq_desc for 518 on node -1
[   90.197692]   alloc kstat_irqs on node -1
[   90.698961]   alloc irq_desc for 517 on node -1
[   90.698964]   alloc kstat_irqs on node -1
[   90.699858] blkback: ring-ref 770, event-channel 64, protocol 1 
(x86_64-abi)
[   90.699876]   alloc irq_desc for 516 on node -1
[   90.699878]   alloc kstat_irqs on node -1
[   90.711588] blkback: ring-ref 771, event-channel 65, protocol 1 
(x86_64-abi)
[   90.711607]   alloc irq_desc for 515 on node -1
[   90.711608]   alloc kstat_irqs on node -1
[   94.272586] vif5.0: no IPv6 routers present
[  100.332601] vif6.0: no IPv6 routers present
[ 6714.397700] md: data-check of RAID array md1
[ 6714.397702] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6714.397704] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6714.397708] md: using 128k window, over a total of 264960 blocks.
[ 6714.560070] md: delaying data-check of md2 until md1 has finished 
(they share one or more physical units)
[ 6714.578031] md: delaying data-check of md3 until md2 has finished 
(they share one or more physical units)
[ 6714.578038] md: delaying data-check of md2 until md1 has finished 
(they share one or more physical units)
[ 6721.351752] md: md1: data-check done.
[ 6721.365392] md: data-check of RAID array md2
[ 6721.365394] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6721.365396] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6721.365399] md: using 128k window, over a total of 2104448 blocks.
[ 6721.365412] md: delaying data-check of md3 until md2 has finished 
(they share one or more physical units)
[ 6750.942813] md: md2: data-check done.
[ 6750.946200] md: data-check of RAID array md3
[ 6750.946202] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 6750.946204] md: using maximum available idle IO bandwidth (but not 
more than 200000 KB/sec) for data-check.
[ 6750.946207] md: using 128k window, over a total of 1460660736 blocks.
[56197.064117] md: md3: data-check done.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Jun 03 21:19:30 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 21:19:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbIAs-0000uU-1S; Sun, 03 Jun 2012 21:17:22 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbIAq-0000uP-VA
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 21:17:21 +0000
Received: from [85.158.143.35:64938] by server-2.bemta-4.messagelabs.com id
	91/A3-11595-064DBCF4; Sun, 03 Jun 2012 21:17:20 +0000
X-Env-Sender: wmcdermott@seq.org
X-Msg-Ref: server-8.tower-21.messagelabs.com!1338758238!13367686!1
X-Originating-IP: [205.132.248.10]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23838 invoked from network); 3 Jun 2012 21:17:19 -0000
Received: from mail.seq.org (HELO mail.seq.org) (205.132.248.10)
	by server-8.tower-21.messagelabs.com with SMTP;
	3 Jun 2012 21:17:19 -0000
Received: from SEQ.nospam (localhost [127.0.0.1])
	by mail.seq.org (Postfix) with ESMTP id B7FA3EA02A3
	for ; Sun,  3 Jun 2012 14:17:17 -0700 (PDT)
Received: from anyhost.local ([127.0.0.1] helo=anyhost.local) by SEQ.nospam
	with ESMTP (ASSP 1.9); 3 Jun 2012 14:17:17 -0700
Received: from SEQ_UHSD-MTA by smtp.seq.org
	with Novell_GroupWise; Sun, 03 Jun 2012 14:17:17 -0700
Message-Id: 
X-Mailer: Novell GroupWise Internet Agent 8.0.2 
Date: Sun, 03 Jun 2012 14:16:23 -0700
From: "Will McDermott" 
To: 
Mime-Version: 1.0
Content-Disposition: inline
Subject: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SGVsbG8sCgpJIGFtIHRyeWluZyB0byBjb21waWxlIHhlbiA0LjIgdW5zdGFibGUgZnJvbSBtZXJj
dXJpYWwuIEkgY2FuJ3QgZ2V0IHBhc3QKdGhlIG1ha2UgdG9vbHMgc3RlcC4gV2hlbiBJIHJ1biBt
YWtlIHRvb2xzLCB0aGUgYnVpbGQgZmFpbHMgd2l0aDoKCkNDICAgIGxpYmh3NjQvOXBmcy9jb3hh
dHRyLm8KICBDQyAgICBsaWJodzY0LzlwZnMvdmlydGlvLTlwLXN5bnRoLm8KICBDQyAgICBsaWJo
dzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCi9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6IEluCmZ1bmN0aW9uIMOiaGFu
ZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKZXJyb3I6IMOiQVRfRU1Q
VFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQovcm9vdC94
ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5jOjcwOjU4Ogpub3RlOiBlYWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBv
bmx5IG9uY2UgZm9yIGVhY2ggZnVuY3Rpb24KaXQgYXBwZWFycyBpbgovcm9vdC94ZW4tdW5zdGFi
bGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgpm
dW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0OgplcnJvcjogw6JBVF9F
TVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCi9yb290
L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFu
ZGxlLmM6IEluCmZ1bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKL3Jvb3QveGVuLXVuc3RhYmxl
LmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6
CmVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm
dW5jdGlvbikKL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZz
L3ZpcnRpby05cC1oYW5kbGUuYzogSW4KZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgovcm9vdC94
ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5jOjMzNzo0NToKZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVz
ZSBpbiB0aGlzIGZ1bmN0aW9uKQovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4t
ZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgpmdW5jdGlvbiDDomhhbmRsZV9jaG93
bsOiOgovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFy
ZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQptYWtlWzRdOiAqKiogWzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5vXSBFcnJvciAxCm1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9y
IDIKbWFrZVszXTogTGVhdmluZyBkaXJlY3RvcnkKYC9yb290L3hlbi11bnN0YWJsZS5oZy90b29s
cy9xZW11LXhlbi1kaXItcmVtb3RlJwptYWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUt
eGVuLWRpcl0gRXJyb3IgMgptYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzJwptYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3IgMgpt
YWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzJwpt
YWtlOiAqKiogW2luc3RhbGwtdG9vbHNdIEVycm9yIDIKCkkgYW0gcnVubmluZyB1YnVudHUgMTIu
MDQsIGtlcm5lbCB2ZXI6IDMuMi4wLTI0LWdlbmVyaWMgCgpBbnkgaWRlYXM/IEkgaGF2ZSBnb29n
bGVkIGZ1cmlvdXNseSBhbmQgZm91bmQgc29tZSBwZW9wbGUgdGFsa2luZyBhYm91dApxZW11LWt2
bSBoYXZpbmcgdGhlIHNhbWUgaXNzdWU6Cmh0dHBzOi8vYnVncy5sYXVuY2hwYWQubmV0L3VidW50
dS8rc291cmNlL3FlbXUta3ZtLytidWcvOTMwMTgxCkJ1dCBJIHdhcyBub3QgYWJsZSB0byBmaW5k
IHRoZSBwYXRjaAoKVGhhbmtzIGluIGFkdmFuY2UhCgoKCk1lcmN1cmlhbG0KCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxp
c3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Sun Jun 03 21:19:30 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 21:19:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbIAs-0000uU-1S; Sun, 03 Jun 2012 21:17:22 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbIAq-0000uP-VA
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 21:17:21 +0000
Received: from [85.158.143.35:64938] by server-2.bemta-4.messagelabs.com id
	91/A3-11595-064DBCF4; Sun, 03 Jun 2012 21:17:20 +0000
X-Env-Sender: wmcdermott@seq.org
X-Msg-Ref: server-8.tower-21.messagelabs.com!1338758238!13367686!1
X-Originating-IP: [205.132.248.10]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23838 invoked from network); 3 Jun 2012 21:17:19 -0000
Received: from mail.seq.org (HELO mail.seq.org) (205.132.248.10)
	by server-8.tower-21.messagelabs.com with SMTP;
	3 Jun 2012 21:17:19 -0000
Received: from SEQ.nospam (localhost [127.0.0.1])
	by mail.seq.org (Postfix) with ESMTP id B7FA3EA02A3
	for ; Sun,  3 Jun 2012 14:17:17 -0700 (PDT)
Received: from anyhost.local ([127.0.0.1] helo=anyhost.local) by SEQ.nospam
	with ESMTP (ASSP 1.9); 3 Jun 2012 14:17:17 -0700
Received: from SEQ_UHSD-MTA by smtp.seq.org
	with Novell_GroupWise; Sun, 03 Jun 2012 14:17:17 -0700
Message-Id: 
X-Mailer: Novell GroupWise Internet Agent 8.0.2 
Date: Sun, 03 Jun 2012 14:16:23 -0700
From: "Will McDermott" 
To: 
Mime-Version: 1.0
Content-Disposition: inline
Subject: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SGVsbG8sCgpJIGFtIHRyeWluZyB0byBjb21waWxlIHhlbiA0LjIgdW5zdGFibGUgZnJvbSBtZXJj
dXJpYWwuIEkgY2FuJ3QgZ2V0IHBhc3QKdGhlIG1ha2UgdG9vbHMgc3RlcC4gV2hlbiBJIHJ1biBt
YWtlIHRvb2xzLCB0aGUgYnVpbGQgZmFpbHMgd2l0aDoKCkNDICAgIGxpYmh3NjQvOXBmcy9jb3hh
dHRyLm8KICBDQyAgICBsaWJodzY0LzlwZnMvdmlydGlvLTlwLXN5bnRoLm8KICBDQyAgICBsaWJo
dzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCi9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6IEluCmZ1bmN0aW9uIMOiaGFu
ZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKZXJyb3I6IMOiQVRfRU1Q
VFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQovcm9vdC94
ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5jOjcwOjU4Ogpub3RlOiBlYWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBv
bmx5IG9uY2UgZm9yIGVhY2ggZnVuY3Rpb24KaXQgYXBwZWFycyBpbgovcm9vdC94ZW4tdW5zdGFi
bGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgpm
dW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0OgplcnJvcjogw6JBVF9F
TVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCi9yb290
L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFu
ZGxlLmM6IEluCmZ1bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKL3Jvb3QveGVuLXVuc3RhYmxl
LmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6
CmVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm
dW5jdGlvbikKL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZz
L3ZpcnRpby05cC1oYW5kbGUuYzogSW4KZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgovcm9vdC94
ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5jOjMzNzo0NToKZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVz
ZSBpbiB0aGlzIGZ1bmN0aW9uKQovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4t
ZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgpmdW5jdGlvbiDDomhhbmRsZV9jaG93
bsOiOgovcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFy
ZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQptYWtlWzRdOiAqKiogWzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5vXSBFcnJvciAxCm1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9y
IDIKbWFrZVszXTogTGVhdmluZyBkaXJlY3RvcnkKYC9yb290L3hlbi11bnN0YWJsZS5oZy90b29s
cy9xZW11LXhlbi1kaXItcmVtb3RlJwptYWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUt
eGVuLWRpcl0gRXJyb3IgMgptYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzJwptYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3IgMgpt
YWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzJwpt
YWtlOiAqKiogW2luc3RhbGwtdG9vbHNdIEVycm9yIDIKCkkgYW0gcnVubmluZyB1YnVudHUgMTIu
MDQsIGtlcm5lbCB2ZXI6IDMuMi4wLTI0LWdlbmVyaWMgCgpBbnkgaWRlYXM/IEkgaGF2ZSBnb29n
bGVkIGZ1cmlvdXNseSBhbmQgZm91bmQgc29tZSBwZW9wbGUgdGFsa2luZyBhYm91dApxZW11LWt2
bSBoYXZpbmcgdGhlIHNhbWUgaXNzdWU6Cmh0dHBzOi8vYnVncy5sYXVuY2hwYWQubmV0L3VidW50
dS8rc291cmNlL3FlbXUta3ZtLytidWcvOTMwMTgxCkJ1dCBJIHdhcyBub3QgYWJsZSB0byBmaW5k
IHRoZSBwYXRjaAoKVGhhbmtzIGluIGFkdmFuY2UhCgoKCk1lcmN1cmlhbG0KCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxp
c3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Sun Jun 03 21:27:23 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 21:27:23 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbIIt-00018N-9n; Sun, 03 Jun 2012 21:25:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbIIs-00018H-5U
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 21:25:38 +0000
Received: from [193.109.254.147:25726] by server-4.bemta-14.messagelabs.com id
	73/AB-03148-156DBCF4; Sun, 03 Jun 2012 21:25:37 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1338758734!12437715!1
X-Originating-IP: [209.85.213.45]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20337 invoked from network); 3 Jun 2012 21:25:35 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	3 Jun 2012 21:25:35 -0000
Received: by yhoo21 with SMTP id o21so2958224yho.32
	for ; Sun, 03 Jun 2012 14:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=y/JXUvzhNA1YK2NT85p7fUIapK44MKIdIpg8SyRZefg=;
	b=btrz9bs4Z0Rm7lCxu4mcUSN7h6OVaQMdRsq2zPEeFC7Y2YIwtmnMm+ZKerCRu0GBqd
	BCg1ZSPzACg1ky9bxDzldw13GnSKmmtipI5iRmzgKZJclMBCCN+6IkaAqBCGsp3XneiP
	aZBKBYMl3OJkkXyO20xKD/0jfnNAiz4DhSzPtPiL7QEAFUuksNAZQ6UWOWnhzqKGY7Sv
	i21k98hNzF5A2XfeLL1L/RDrnzp5uaRZTSfFRkhUaBcxaqSuk0w3pmcDVSAUfg4SDlOR
	1opi3TWRzZjQJCjwH0z7OXrAxrLwzpTp0DYrxHZ9/OEGQTsipq0Y96uiNsTBoEkOv/jf
	bQVA==
Received: by 10.236.197.8 with SMTP id s8mr5089044yhn.9.1338758734353;
	Sun, 03 Jun 2012 14:25:34 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id b58sm31255372yhh.16.2012.06.03.14.25.32
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sun, 03 Jun 2012 14:25:33 -0700 (PDT)
Message-ID: <4FCBD636.5050606@gmail.com>
Date: Sun, 03 Jun 2012 17:25:10 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3615539872426618442=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============3615539872426618442==
Content-Type: multipart/alternative;
 boundary="------------060203040705090008070004"

This is a multi-part message in MIME format.
--------------060203040705090008070004
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the 
link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen 
4.2-Unstable are you trying to compile?


> Hello,
>
> I am trying to compile xen 4.2 unstable from mercurial. I can't get past
> the make tools step. When I run make tools, the build fails with:
>
> CC    libhw64/9pfs/coxattr.o
>    CC    libhw64/9pfs/virtio-9p-synth.o
>    CC    libhw64/9pfs/virtio-9p-handle.o
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_update_file_credâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
> note: each undeclared identifier is reported only once for each function
> it appears in
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_lstatâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_symlinkâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_linkâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_chownâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
> make[3]: *** [subdir-libhw64] Error 2
> make[3]: Leaving directory
> `/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
> make[2]: *** [subdir-install-qemu-xen-dir] Error 2
> make[2]: Leaving directory `/root/xen-unstable.hg/tools'
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory `/root/xen-unstable.hg/tools'
> make: *** [install-tools] Error 2
>
> I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic
>
> Any ideas? I have googled furiously and found some people talking about
> qemu-kvm having the same issue:
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
> But I was not able to find the patch
>
> Thanks in advance!
>
>
>
> Mercurialm
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------060203040705090008070004
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    The latest revision of Xen 4.2-unstable is 25452:6bea63e6c780
    at the link http://xenbits.xen.org/hg/xen-unstable.hg/ What
    reversion of Xen 4.2-Unstable are you trying to compile? 

    

    

    

      
Hello,

I am trying to compile xen 4.2 unstable from mercurial. I can't get past
the make tools step. When I run make tools, the build fails with:

CC    libhw64/9pfs/coxattr.o
  CC    libhw64/9pfs/virtio-9p-synth.o
  CC    libhw64/9pfs/virtio-9p-handle.o
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_update_file_credâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
note: each undeclared identifier is reported only once for each function
it appears in
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_lstatâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_symlinkâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_linkâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_chownâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
make[3]: *** [subdir-libhw64] Error 2
make[3]: Leaving directory
`/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
make[2]: *** [subdir-install-qemu-xen-dir] Error 2
make[2]: Leaving directory `/root/xen-unstable.hg/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/root/xen-unstable.hg/tools'
make: *** [install-tools] Error 2

I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic 

Any ideas? I have googled furiously and found some people talking about
qemu-kvm having the same issue:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
But I was not able to find the patch

Thanks in advance!



Mercurialm

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------060203040705090008070004--


--===============3615539872426618442==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3615539872426618442==--


From xen-users-bounces@lists.xen.org Sun Jun 03 21:27:23 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 03 Jun 2012 21:27:23 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbIIt-00018N-9n; Sun, 03 Jun 2012 21:25:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbIIs-00018H-5U
	for xen-users@lists.xen.org; Sun, 03 Jun 2012 21:25:38 +0000
Received: from [193.109.254.147:25726] by server-4.bemta-14.messagelabs.com id
	73/AB-03148-156DBCF4; Sun, 03 Jun 2012 21:25:37 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1338758734!12437715!1
X-Originating-IP: [209.85.213.45]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20337 invoked from network); 3 Jun 2012 21:25:35 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	3 Jun 2012 21:25:35 -0000
Received: by yhoo21 with SMTP id o21so2958224yho.32
	for ; Sun, 03 Jun 2012 14:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=y/JXUvzhNA1YK2NT85p7fUIapK44MKIdIpg8SyRZefg=;
	b=btrz9bs4Z0Rm7lCxu4mcUSN7h6OVaQMdRsq2zPEeFC7Y2YIwtmnMm+ZKerCRu0GBqd
	BCg1ZSPzACg1ky9bxDzldw13GnSKmmtipI5iRmzgKZJclMBCCN+6IkaAqBCGsp3XneiP
	aZBKBYMl3OJkkXyO20xKD/0jfnNAiz4DhSzPtPiL7QEAFUuksNAZQ6UWOWnhzqKGY7Sv
	i21k98hNzF5A2XfeLL1L/RDrnzp5uaRZTSfFRkhUaBcxaqSuk0w3pmcDVSAUfg4SDlOR
	1opi3TWRzZjQJCjwH0z7OXrAxrLwzpTp0DYrxHZ9/OEGQTsipq0Y96uiNsTBoEkOv/jf
	bQVA==
Received: by 10.236.197.8 with SMTP id s8mr5089044yhn.9.1338758734353;
	Sun, 03 Jun 2012 14:25:34 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id b58sm31255372yhh.16.2012.06.03.14.25.32
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sun, 03 Jun 2012 14:25:33 -0700 (PDT)
Message-ID: <4FCBD636.5050606@gmail.com>
Date: Sun, 03 Jun 2012 17:25:10 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3615539872426618442=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============3615539872426618442==
Content-Type: multipart/alternative;
 boundary="------------060203040705090008070004"

This is a multi-part message in MIME format.
--------------060203040705090008070004
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the 
link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen 
4.2-Unstable are you trying to compile?


> Hello,
>
> I am trying to compile xen 4.2 unstable from mercurial. I can't get past
> the make tools step. When I run make tools, the build fails with:
>
> CC    libhw64/9pfs/coxattr.o
>    CC    libhw64/9pfs/virtio-9p-synth.o
>    CC    libhw64/9pfs/virtio-9p-handle.o
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_update_file_credâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
> note: each undeclared identifier is reported only once for each function
> it appears in
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_lstatâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_symlinkâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_linkâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
> function âhandle_chownâ:
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
> make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
> make[3]: *** [subdir-libhw64] Error 2
> make[3]: Leaving directory
> `/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
> make[2]: *** [subdir-install-qemu-xen-dir] Error 2
> make[2]: Leaving directory `/root/xen-unstable.hg/tools'
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory `/root/xen-unstable.hg/tools'
> make: *** [install-tools] Error 2
>
> I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic
>
> Any ideas? I have googled furiously and found some people talking about
> qemu-kvm having the same issue:
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
> But I was not able to find the patch
>
> Thanks in advance!
>
>
>
> Mercurialm
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------060203040705090008070004
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    The latest revision of Xen 4.2-unstable is 25452:6bea63e6c780
    at the link http://xenbits.xen.org/hg/xen-unstable.hg/ What
    reversion of Xen 4.2-Unstable are you trying to compile? 

    

    

    

      
Hello,

I am trying to compile xen 4.2 unstable from mercurial. I can't get past
the make tools step. When I run make tools, the build fails with:

CC    libhw64/9pfs/coxattr.o
  CC    libhw64/9pfs/virtio-9p-synth.o
  CC    libhw64/9pfs/virtio-9p-handle.o
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_update_file_credâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
note: each undeclared identifier is reported only once for each function
it appears in
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_lstatâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_symlinkâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_linkâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c: In
function âhandle_chownâ:
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
make[3]: *** [subdir-libhw64] Error 2
make[3]: Leaving directory
`/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
make[2]: *** [subdir-install-qemu-xen-dir] Error 2
make[2]: Leaving directory `/root/xen-unstable.hg/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/root/xen-unstable.hg/tools'
make: *** [install-tools] Error 2

I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic 

Any ideas? I have googled furiously and found some people talking about
qemu-kvm having the same issue:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
But I was not able to find the patch

Thanks in advance!



Mercurialm

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------060203040705090008070004--


--===============3615539872426618442==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3615539872426618442==--


From xen-users-bounces@lists.xen.org Mon Jun 04 11:49:13 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 11:49: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 1SbVkO-0001ev-De; Mon, 04 Jun 2012 11:46:56 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbVkM-0001eq-Go
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 11:46:55 +0000
Received: from [85.158.138.51:36668] by server-2.bemta-3.messagelabs.com id
	4C/12-17140-D20ACCF4; Mon, 04 Jun 2012 11:46:53 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338810410!30777588!1
X-Originating-IP: [209.85.161.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28548 invoked from network); 4 Jun 2012 11:46:51 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 11:46:51 -0000
Received: by ggnp1 with SMTP id p1so3380487ggn.32
	for ; Mon, 04 Jun 2012 04:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=02vRv+VdSwB8hXBnbTeO0vWCqThlL+Z+LUhQxv8fBQE=;
	b=a2fMTRdcLts6nlQMs+Nw9wj9cdWfRn08pe+9el8HlHx4B9wy3lQ8xfraP5mdqWe5eg
	b/c2QQFhF6xx0S2ZraV+l8tvutGkD9ZMcg/nsnhw+VBDbyLnInDrVuwsGZhTiibnyhIO
	3d/p8geqgPWG6Ld8x7+CXZj5m71s3pNZmmkU+lWpH/wGoiCgvjI1USmvBuORT3ZveVea
	CfRepcyKVoQ+5RHI3bKXkAS8R9PgJip/++f7LwY4KhtL/sPFPhYg4uZiV2Llr7EuzAuN
	4tL5RBU0QZ1yd3rd01kEz3BS2KQhzRpDj3+cL+a0ckEUCs1zrZp+eHokZV3nF0y7oMH+
	gCvQ==
Received: by 10.236.154.193 with SMTP id h41mr6617498yhk.58.1338810410133;
	Mon, 04 Jun 2012 04:46:50 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id m43sm37516568yhi.13.2012.06.04.04.46.47
	(version=TLSv1/SSLv3 cipher=OTHER);
	Mon, 04 Jun 2012 04:46:48 -0700 (PDT)
Message-ID: <4FCCA00F.5010603@gmail.com>
Date: Mon, 04 Jun 2012 07:46:23 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Will McDermott , 
	"xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2770355119129929133=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============2770355119129929133==
Content-Type: multipart/alternative;
 boundary="------------050002000905040807030006"

This is a multi-part message in MIME format.
--------------050002000905040807030006
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 6/4/2012 2:58 AM, Will McDermott wrote:
> I'm not sure what version (how do I check?) but I just cloned from that
> URL today.
>
> --Will


Well than you probably already have the latest revision. You can also 
check what revision your locally cloned repository is at by going to the 
folder and running:

*cd  ../xen-unstable.hg
hg summary
*
And that will show you a summary of the local mercurial clone and show 
the latest revisions that was cloned.

SO, anyhow, compiling the Xen 4.2-unstable from the mercurial has not 
been working very well for a few weeks now. I have asked the Xen-devel 
about that a several times and there are issues and problems with 
different GCC compilers AND the Xen-devel team knows all that and are 
working on fixing that.

For now, the LAST revision i was able to compile and get running was 
*"revision 25392*", but even that was possibly ONLY if you remove one 
patch. You can try to download and compile THAT version by running the 
following commands:

_*Cloning Xen:*_
*- cd /some/directory/in/home
- rev=25392 && hg clone -r $rev 
http://xenbits.xen.org/hg/xen-unstable.hg/ xen-unstable.hg-rev-${rev}
- cd xen-unstable.hg-rev-25392
- hg backout -r 25364*

This will clone the xen-unstable.hg mercurial and download Xen 
4.2-unstable revision 25392 into the folder 
"*xen-unstable.hg-rev-25392*". Running the command "*hg backour -r 
25364*" removes or backs out that particular patch. It seems that 
without that, even that revision wont compile.

_*Compiling Xen:*_
Than just simply run these commands to compile Xen.

*- cd xen-unstable.hg-rev-25392*
*- ./configure
- sudo make -j5 xen && sudo make -j5 tools && sudo make -j5 stubdom && 
sudo make -j5 deb*

The compile command above just strings together the 4 compiling commands 
to run and will execute one after the other SO you don't have to 
manually run each and every one. Also, In the above "*make*" commands, 
using the "*-j5*" option after each make tells the compile to use more 
than one core to compile with. It speeds up the compiling a lot if you 
have a multi-core CPU. SO in my case, i have a Quad Core CPU, so that 
command option is "*-j1 + number of CPU cores*". You can modify or 
remove that as you wish.

The above will also create for you a nice DEB package after all the 
compiling is done, if you do not want to create a DEB package at the end 
of it all, than just remove the last "*&& sudo make -j5 deb*" command.

Granted, i am running and doing all of this on Debian Wheezy BUT i there 
aren't any differences in compiling it on Ubuntu 12.04.




>
>>>>   06/03/12 2:34 PM>>>
> The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the
> link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen
> 4.2-Unstable are you trying to compile?
>
>
>> Hello,
>>
>> I am trying to compile xen 4.2 unstable from mercurial. I can't get
> past
>> the make tools step. When I run make tools, the build fails with:
>>
>> CC    libhw64/9pfs/coxattr.o
>>     CC    libhw64/9pfs/virtio-9p-synth.o
>>     CC    libhw64/9pfs/virtio-9p-handle.o
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_update_file_credâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
>> note: each undeclared identifier is reported only once for each
> function
>> it appears in
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_lstatâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_symlinkâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_linkâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_chownâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
>> make[3]: *** [subdir-libhw64] Error 2
>> make[3]: Leaving directory
>> `/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
>> make[2]: *** [subdir-install-qemu-xen-dir] Error 2
>> make[2]: Leaving directory `/root/xen-unstable.hg/tools'
>> make[1]: *** [subdirs-install] Error 2
>> make[1]: Leaving directory `/root/xen-unstable.hg/tools'
>> make: *** [install-tools] Error 2
>>
>> I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic
>>
>> Any ideas? I have googled furiously and found some people talking
> about
>> qemu-kvm having the same issue:
>> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
>> But I was not able to find the patch
>>
>> Thanks in advance!
>>
>>
>>
>> Mercurialm
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
>


--------------050002000905040807030006
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    On 6/4/2012 2:58 AM, Will McDermott wrote:
    

      
I'm not sure what version (how do I check?) but I just cloned from that
URL today.

--Will

    

    

    

    Well than you probably already have the latest revision. You can
    also check what revision your locally cloned repository is at by
    going to the folder and running:

    

    cd  ../xen-unstable.hg

      hg summary

    

    And that will show you a summary of the local mercurial clone and
    show the latest revisions that was cloned.

    

    SO, anyhow, compiling the Xen 4.2-unstable from the mercurial has
    not been working very well for a few weeks now. I have asked the
    Xen-devel about that a several times and there are issues and
    problems with different GCC compilers AND the Xen-devel team knows
    all that and are working on fixing that.

    

    For now, the LAST revision i was able to compile and get running was
    "revision 25392", but even that was possibly ONLY if you
    remove one patch. You can try to download and compile THAT version
    by running the following commands:

    

    Cloning Xen:

    - cd /some/directory/in/home

      - rev=25392 && hg clone -r $rev
      http://xenbits.xen.org/hg/xen-unstable.hg/
      xen-unstable.hg-rev-${rev}

      - cd xen-unstable.hg-rev-25392

      - hg backout -r 25364

    

    This will clone the xen-unstable.hg mercurial and download Xen
    4.2-unstable revision 25392 into the folder "xen-unstable.hg-rev-25392".
    Running the command "hg backour -r 25364" removes or backs
    out that particular patch. It seems that without that, even that
    revision wont compile.

    

    Compiling Xen:

    Than just simply run these commands to compile Xen.

    

    - cd xen-unstable.hg-rev-25392

    - ./configure

      - sudo make -j5 xen && sudo make -j5 tools && sudo
      make -j5 stubdom && sudo make -j5 deb

    

    The compile command above just strings together the 4 compiling
    commands to run and will execute one after the other SO you don't
    have to manually run each and every one. Also, In the above "make"
    commands, using the "-j5" option after each make tells the
    compile to use more than one core to compile with. It speeds up the
    compiling a lot if you have a multi-core CPU. SO in my case, i have
    a Quad Core CPU, so that command option is " -j1 + number of CPU
      cores". You can modify or remove that as you wish.

    

    The above will also create for you a nice DEB package after all the
    compiling is done, if you do not want to create a DEB package at the
    end of it all, than just remove the last "&& sudo make
      -j5 deb" command.

    

    Granted, i am running and doing all of this on Debian Wheezy BUT i
    there aren't any differences in compiling it on Ubuntu 12.04.

    

    

    

    

    

      



      

        

          

            
 06/03/12 2:34 PM >>>


          

        

      

      
The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the 
link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen 
4.2-Unstable are you trying to compile?




      

        
Hello,

I am trying to compile xen 4.2 unstable from mercurial. I can't get


      

      
past


      

        
the make tools step. When I run make tools, the build fails with:

CC    libhw64/9pfs/coxattr.o
   CC    libhw64/9pfs/virtio-9p-synth.o
   CC    libhw64/9pfs/virtio-9p-handle.o
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_update_file_credâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:


      

        
note: each undeclared identifier is reported only once for each


      

      
function


      

        
it appears in
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_lstatâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_symlinkâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_linkâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_chownâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
make[3]: *** [subdir-libhw64] Error 2
make[3]: Leaving directory
`/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
make[2]: *** [subdir-install-qemu-xen-dir] Error 2
make[2]: Leaving directory `/root/xen-unstable.hg/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/root/xen-unstable.hg/tools'
make: *** [install-tools] Error 2

I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic

Any ideas? I have googled furiously and found some people talking


      

      
about


      

        
qemu-kvm having the same issue:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
But I was not able to find the patch

Thanks in advance!



Mercurialm

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


      

      




    

    

  


--------------050002000905040807030006--


--===============2770355119129929133==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2770355119129929133==--


From xen-users-bounces@lists.xen.org Mon Jun 04 11:49:13 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 11:49: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 1SbVkO-0001ev-De; Mon, 04 Jun 2012 11:46:56 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbVkM-0001eq-Go
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 11:46:55 +0000
Received: from [85.158.138.51:36668] by server-2.bemta-3.messagelabs.com id
	4C/12-17140-D20ACCF4; Mon, 04 Jun 2012 11:46:53 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-5.tower-174.messagelabs.com!1338810410!30777588!1
X-Originating-IP: [209.85.161.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28548 invoked from network); 4 Jun 2012 11:46:51 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 11:46:51 -0000
Received: by ggnp1 with SMTP id p1so3380487ggn.32
	for ; Mon, 04 Jun 2012 04:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=02vRv+VdSwB8hXBnbTeO0vWCqThlL+Z+LUhQxv8fBQE=;
	b=a2fMTRdcLts6nlQMs+Nw9wj9cdWfRn08pe+9el8HlHx4B9wy3lQ8xfraP5mdqWe5eg
	b/c2QQFhF6xx0S2ZraV+l8tvutGkD9ZMcg/nsnhw+VBDbyLnInDrVuwsGZhTiibnyhIO
	3d/p8geqgPWG6Ld8x7+CXZj5m71s3pNZmmkU+lWpH/wGoiCgvjI1USmvBuORT3ZveVea
	CfRepcyKVoQ+5RHI3bKXkAS8R9PgJip/++f7LwY4KhtL/sPFPhYg4uZiV2Llr7EuzAuN
	4tL5RBU0QZ1yd3rd01kEz3BS2KQhzRpDj3+cL+a0ckEUCs1zrZp+eHokZV3nF0y7oMH+
	gCvQ==
Received: by 10.236.154.193 with SMTP id h41mr6617498yhk.58.1338810410133;
	Mon, 04 Jun 2012 04:46:50 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id m43sm37516568yhi.13.2012.06.04.04.46.47
	(version=TLSv1/SSLv3 cipher=OTHER);
	Mon, 04 Jun 2012 04:46:48 -0700 (PDT)
Message-ID: <4FCCA00F.5010603@gmail.com>
Date: Mon, 04 Jun 2012 07:46:23 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Will McDermott , 
	"xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2770355119129929133=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============2770355119129929133==
Content-Type: multipart/alternative;
 boundary="------------050002000905040807030006"

This is a multi-part message in MIME format.
--------------050002000905040807030006
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 6/4/2012 2:58 AM, Will McDermott wrote:
> I'm not sure what version (how do I check?) but I just cloned from that
> URL today.
>
> --Will


Well than you probably already have the latest revision. You can also 
check what revision your locally cloned repository is at by going to the 
folder and running:

*cd  ../xen-unstable.hg
hg summary
*
And that will show you a summary of the local mercurial clone and show 
the latest revisions that was cloned.

SO, anyhow, compiling the Xen 4.2-unstable from the mercurial has not 
been working very well for a few weeks now. I have asked the Xen-devel 
about that a several times and there are issues and problems with 
different GCC compilers AND the Xen-devel team knows all that and are 
working on fixing that.

For now, the LAST revision i was able to compile and get running was 
*"revision 25392*", but even that was possibly ONLY if you remove one 
patch. You can try to download and compile THAT version by running the 
following commands:

_*Cloning Xen:*_
*- cd /some/directory/in/home
- rev=25392 && hg clone -r $rev 
http://xenbits.xen.org/hg/xen-unstable.hg/ xen-unstable.hg-rev-${rev}
- cd xen-unstable.hg-rev-25392
- hg backout -r 25364*

This will clone the xen-unstable.hg mercurial and download Xen 
4.2-unstable revision 25392 into the folder 
"*xen-unstable.hg-rev-25392*". Running the command "*hg backour -r 
25364*" removes or backs out that particular patch. It seems that 
without that, even that revision wont compile.

_*Compiling Xen:*_
Than just simply run these commands to compile Xen.

*- cd xen-unstable.hg-rev-25392*
*- ./configure
- sudo make -j5 xen && sudo make -j5 tools && sudo make -j5 stubdom && 
sudo make -j5 deb*

The compile command above just strings together the 4 compiling commands 
to run and will execute one after the other SO you don't have to 
manually run each and every one. Also, In the above "*make*" commands, 
using the "*-j5*" option after each make tells the compile to use more 
than one core to compile with. It speeds up the compiling a lot if you 
have a multi-core CPU. SO in my case, i have a Quad Core CPU, so that 
command option is "*-j1 + number of CPU cores*". You can modify or 
remove that as you wish.

The above will also create for you a nice DEB package after all the 
compiling is done, if you do not want to create a DEB package at the end 
of it all, than just remove the last "*&& sudo make -j5 deb*" command.

Granted, i am running and doing all of this on Debian Wheezy BUT i there 
aren't any differences in compiling it on Ubuntu 12.04.




>
>>>>   06/03/12 2:34 PM>>>
> The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the
> link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen
> 4.2-Unstable are you trying to compile?
>
>
>> Hello,
>>
>> I am trying to compile xen 4.2 unstable from mercurial. I can't get
> past
>> the make tools step. When I run make tools, the build fails with:
>>
>> CC    libhw64/9pfs/coxattr.o
>>     CC    libhw64/9pfs/virtio-9p-synth.o
>>     CC    libhw64/9pfs/virtio-9p-handle.o
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_update_file_credâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:
>> note: each undeclared identifier is reported only once for each
> function
>> it appears in
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_lstatâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_symlinkâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_linkâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:
> In
>> function âhandle_chownâ:
>>
> /root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:
>> error: âAT_EMPTY_PATHâ undeclared (first use in this function)
>> make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
>> make[3]: *** [subdir-libhw64] Error 2
>> make[3]: Leaving directory
>> `/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
>> make[2]: *** [subdir-install-qemu-xen-dir] Error 2
>> make[2]: Leaving directory `/root/xen-unstable.hg/tools'
>> make[1]: *** [subdirs-install] Error 2
>> make[1]: Leaving directory `/root/xen-unstable.hg/tools'
>> make: *** [install-tools] Error 2
>>
>> I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic
>>
>> Any ideas? I have googled furiously and found some people talking
> about
>> qemu-kvm having the same issue:
>> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
>> But I was not able to find the patch
>>
>> Thanks in advance!
>>
>>
>>
>> Mercurialm
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
>


--------------050002000905040807030006
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    On 6/4/2012 2:58 AM, Will McDermott wrote:
    

      
I'm not sure what version (how do I check?) but I just cloned from that
URL today.

--Will

    

    

    

    Well than you probably already have the latest revision. You can
    also check what revision your locally cloned repository is at by
    going to the folder and running:

    

    cd  ../xen-unstable.hg

      hg summary

    

    And that will show you a summary of the local mercurial clone and
    show the latest revisions that was cloned.

    

    SO, anyhow, compiling the Xen 4.2-unstable from the mercurial has
    not been working very well for a few weeks now. I have asked the
    Xen-devel about that a several times and there are issues and
    problems with different GCC compilers AND the Xen-devel team knows
    all that and are working on fixing that.

    

    For now, the LAST revision i was able to compile and get running was
    "revision 25392", but even that was possibly ONLY if you
    remove one patch. You can try to download and compile THAT version
    by running the following commands:

    

    Cloning Xen:

    - cd /some/directory/in/home

      - rev=25392 && hg clone -r $rev
      http://xenbits.xen.org/hg/xen-unstable.hg/
      xen-unstable.hg-rev-${rev}

      - cd xen-unstable.hg-rev-25392

      - hg backout -r 25364

    

    This will clone the xen-unstable.hg mercurial and download Xen
    4.2-unstable revision 25392 into the folder "xen-unstable.hg-rev-25392".
    Running the command "hg backour -r 25364" removes or backs
    out that particular patch. It seems that without that, even that
    revision wont compile.

    

    Compiling Xen:

    Than just simply run these commands to compile Xen.

    

    - cd xen-unstable.hg-rev-25392

    - ./configure

      - sudo make -j5 xen && sudo make -j5 tools && sudo
      make -j5 stubdom && sudo make -j5 deb

    

    The compile command above just strings together the 4 compiling
    commands to run and will execute one after the other SO you don't
    have to manually run each and every one. Also, In the above "make"
    commands, using the "-j5" option after each make tells the
    compile to use more than one core to compile with. It speeds up the
    compiling a lot if you have a multi-core CPU. SO in my case, i have
    a Quad Core CPU, so that command option is " -j1 + number of CPU
      cores". You can modify or remove that as you wish.

    

    The above will also create for you a nice DEB package after all the
    compiling is done, if you do not want to create a DEB package at the
    end of it all, than just remove the last "&& sudo make
      -j5 deb" command.

    

    Granted, i am running and doing all of this on Debian Wheezy BUT i
    there aren't any differences in compiling it on Ubuntu 12.04.

    

    

    

    

    

      



      

        

          

            
 06/03/12 2:34 PM >>>


          

        

      

      
The latest revision of Xen 4.2-unstable is *25452:6bea63e6c780* at the 
link *http://xenbits.xen.org/hg/xen-unstable.hg/* What reversion of Xen 
4.2-Unstable are you trying to compile?




      

        
Hello,

I am trying to compile xen 4.2 unstable from mercurial. I can't get


      

      
past


      

        
the make tools step. When I run make tools, the build fails with:

CC    libhw64/9pfs/coxattr.o
   CC    libhw64/9pfs/virtio-9p-synth.o
   CC    libhw64/9pfs/virtio-9p-handle.o
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_update_file_credâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:70:58:


      

        
note: each undeclared identifier is reported only once for each


      

      
function


      

        
it appears in
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_lstatâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:87:34:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_symlinkâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:314:62:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_linkâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:337:45:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:


      

      
In


      

        
function âhandle_chownâ:



      

      
/root/xen-unstable.hg/tools/qemu-xen-dir/hw/9pfs/virtio-9p-handle.c:373:58:


      

        
error: âAT_EMPTY_PATHâ undeclared (first use in this function)
make[4]: *** [9pfs/virtio-9p-handle.o] Error 1
make[3]: *** [subdir-libhw64] Error 2
make[3]: Leaving directory
`/root/xen-unstable.hg/tools/qemu-xen-dir-remote'
make[2]: *** [subdir-install-qemu-xen-dir] Error 2
make[2]: Leaving directory `/root/xen-unstable.hg/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/root/xen-unstable.hg/tools'
make: *** [install-tools] Error 2

I am running ubuntu 12.04, kernel ver: 3.2.0-24-generic

Any ideas? I have googled furiously and found some people talking


      

      
about


      

        
qemu-kvm having the same issue:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181
But I was not able to find the patch

Thanks in advance!



Mercurialm

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


      

      




    

    

  


--------------050002000905040807030006--


--===============2770355119129929133==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2770355119129929133==--


From xen-users-bounces@lists.xen.org Mon Jun 04 16:33:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 16:33: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 1SbaBl-0003jY-9N; Mon, 04 Jun 2012 16:31:29 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbaBk-0003jT-9k
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 16:31:28 +0000
Received: from [193.109.254.147:41294] by server-1.bemta-14.messagelabs.com id
	CF/26-07411-FD2ECCF4; Mon, 04 Jun 2012 16:31:27 +0000
X-Env-Sender: alk@ondore.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1338827485!12745877!1
X-Originating-IP: [184.172.38.138]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12802 invoked from network); 4 Jun 2012 16:31:26 -0000
Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com)
	(184.172.38.138)
	by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 16:31:26 -0000
Received: from [189.253.145.95] (port=52291 helo=mail.ondore.i)
	by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.77) (envelope-from ) id 1SbaBg-0003bK-T9
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 11:31:25 -0500
Received: from [10.13.34.178] (alk-desktop.sys.ondore.i [10.13.34.178])
	by mail.ondore.i (Postfix) with ESMTPSA id 40ECCA1DB
	for ; Mon,  4 Jun 2012 11:31:23 -0500 (CDT)
Message-ID: <4FCCE2DB.9040108@ondore.com>
Date: Mon, 04 Jun 2012 11:31:23 -0500
From: Alexandre Kouznetsov 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <1338702326.6450.558.camel@WLN-MSI-201101>
In-Reply-To: <1338702326.6450.558.camel@WLN-MSI-201101>
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host0a.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
Subject: Re: [Xen-users] Xen on a laptop
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
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-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello.

El 03/06/12 00:45, Andrew Sorensen escribi=F3:
> I am looking to purchase a new laptop quite soon, and intend to run a
> number of virtual machines.

Setting up a complex configuration of a not-too-well-known tool is =

generally a bad idea, unless you pretend to be some kind of full time =

concept tester. No matter how good advices you get about the details, =

you will probably get more pain than benefit and will have reconsider =

your whole concept a few times, before getting something actually usable.

If I may suggest, think of something simpler, focus on what you are =

trying to archive. Too much details to think of would ruin your ambitions.

 From my experience of similar setup:
I need to have various systems (serves) at hand, for testing or =

demonstration purpose, and wish not to overload the main OS with all =

that functionality.
I wish be run untrusted software on a dedicated virtual machine, to =

reduce the risk of security compromise.

So, one VM as a sandbox, and maybe another as a demo server, main work =

is done on the host systems directly. The sandbox is used almost all the =

time, the server VM is turned on only while needed. The tool of choice =

would be not Xen, BTW. Then a need of extra functionality is clear, I =

would consider modifications to this setup.

1) Suspend to disk/ram
"Save" the VM's, after that suspend the host OS as usual.

2) Optimus and VGA passthrough
Forget in on a laptop, for now. It does not run out-of-the-box on a =

average desktop, will be much tricky on a laptop.

3) Wireless and networking
Leave it on the host system, until more prioritized things are running fine.

4) Disk IO issue
Has more to do with what tasks you are actually perform on your laptop, =

than with the virtualization setup.

5) Power management
Same as above, has to do with what you do. If you need you VMs to work, =

you will probably need them even on battery. If there are VM you don't =

need running all the time, better to keep them shot down by default.

6) Windows DomU
If you need decent graphics performance from a Windows VM, specially on =

more than one instance, maybe its not Xen what will work best for you. =

Nested virtualization generally does not works well with Windows, unless =

Windows is the host system.

I have once set up Xen on a laptop, accidentally. (:
Works just fine under "normal" usage, anything tricky tends to be more =

tricky than on a regular server/desktop system.

The link you provided is broken.

-- =

Alexandre Kouznetsov
Systems Officer
Ondore, S.A. de C.V.
Tel. +52(55) 5559-0090
E-mail alk@ondore.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Mon Jun 04 16:33:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 16:33: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 1SbaBl-0003jY-9N; Mon, 04 Jun 2012 16:31:29 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbaBk-0003jT-9k
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 16:31:28 +0000
Received: from [193.109.254.147:41294] by server-1.bemta-14.messagelabs.com id
	CF/26-07411-FD2ECCF4; Mon, 04 Jun 2012 16:31:27 +0000
X-Env-Sender: alk@ondore.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1338827485!12745877!1
X-Originating-IP: [184.172.38.138]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12802 invoked from network); 4 Jun 2012 16:31:26 -0000
Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com)
	(184.172.38.138)
	by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 16:31:26 -0000
Received: from [189.253.145.95] (port=52291 helo=mail.ondore.i)
	by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.77) (envelope-from ) id 1SbaBg-0003bK-T9
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 11:31:25 -0500
Received: from [10.13.34.178] (alk-desktop.sys.ondore.i [10.13.34.178])
	by mail.ondore.i (Postfix) with ESMTPSA id 40ECCA1DB
	for ; Mon,  4 Jun 2012 11:31:23 -0500 (CDT)
Message-ID: <4FCCE2DB.9040108@ondore.com>
Date: Mon, 04 Jun 2012 11:31:23 -0500
From: Alexandre Kouznetsov 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <1338702326.6450.558.camel@WLN-MSI-201101>
In-Reply-To: <1338702326.6450.558.camel@WLN-MSI-201101>
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host0a.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
Subject: Re: [Xen-users] Xen on a laptop
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
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-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello.

El 03/06/12 00:45, Andrew Sorensen escribi=F3:
> I am looking to purchase a new laptop quite soon, and intend to run a
> number of virtual machines.

Setting up a complex configuration of a not-too-well-known tool is =

generally a bad idea, unless you pretend to be some kind of full time =

concept tester. No matter how good advices you get about the details, =

you will probably get more pain than benefit and will have reconsider =

your whole concept a few times, before getting something actually usable.

If I may suggest, think of something simpler, focus on what you are =

trying to archive. Too much details to think of would ruin your ambitions.

 From my experience of similar setup:
I need to have various systems (serves) at hand, for testing or =

demonstration purpose, and wish not to overload the main OS with all =

that functionality.
I wish be run untrusted software on a dedicated virtual machine, to =

reduce the risk of security compromise.

So, one VM as a sandbox, and maybe another as a demo server, main work =

is done on the host systems directly. The sandbox is used almost all the =

time, the server VM is turned on only while needed. The tool of choice =

would be not Xen, BTW. Then a need of extra functionality is clear, I =

would consider modifications to this setup.

1) Suspend to disk/ram
"Save" the VM's, after that suspend the host OS as usual.

2) Optimus and VGA passthrough
Forget in on a laptop, for now. It does not run out-of-the-box on a =

average desktop, will be much tricky on a laptop.

3) Wireless and networking
Leave it on the host system, until more prioritized things are running fine.

4) Disk IO issue
Has more to do with what tasks you are actually perform on your laptop, =

than with the virtualization setup.

5) Power management
Same as above, has to do with what you do. If you need you VMs to work, =

you will probably need them even on battery. If there are VM you don't =

need running all the time, better to keep them shot down by default.

6) Windows DomU
If you need decent graphics performance from a Windows VM, specially on =

more than one instance, maybe its not Xen what will work best for you. =

Nested virtualization generally does not works well with Windows, unless =

Windows is the host system.

I have once set up Xen on a laptop, accidentally. (:
Works just fine under "normal" usage, anything tricky tends to be more =

tricky than on a regular server/desktop system.

The link you provided is broken.

-- =

Alexandre Kouznetsov
Systems Officer
Ondore, S.A. de C.V.
Tel. +52(55) 5559-0090
E-mail alk@ondore.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Mon Jun 04 20:11:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20: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 1Sbdb5-0005T2-Mv; Mon, 04 Jun 2012 20:09:51 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbdb4-0005Sx-H1
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:09:50 +0000
Received: from [85.158.139.83:35729] by server-6.bemta-5.messagelabs.com id
	E6/FE-18700-D061DCF4; Mon, 04 Jun 2012 20:09:49 +0000
X-Env-Sender: werner@xxlwade.de
X-Msg-Ref: server-13.tower-182.messagelabs.com!1338840588!31438023!1
X-Originating-IP: [88.198.0.151]
X-SpamReason: No, hits=3.4 required=7.0 tests=HELO_DYNAMIC_IPADDR
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2960 invoked from network); 4 Jun 2012 20:09:49 -0000
Received: from static.88-198-0-151.clients.your-server.de (HELO
	static-ip-217-172-170-8.inaddr.intergenia.de) (88.198.0.151)
	by server-13.tower-182.messagelabs.com with SMTP;
	4 Jun 2012 20:09:49 -0000
Received: from [192.168.1.2] (localhost [127.0.0.1])
	by static-ip-217-172-170-8.inaddr.intergenia.de (Postfix) with ESMTPA
	id C4C6116273
	for ; Mon,  4 Jun 2012 22:09:48 +0200 (CEST)
Message-ID: <4FCD160C.6030002@xxlwade.de>
Date: Mon, 04 Jun 2012 22:09:48 +0200
From: Werner Fehn 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCB82DE.4080506@xxlwade.de>
In-Reply-To: <4FCB82DE.4080506@xxlwade.de>
Subject: Re: [Xen-users] need to load uhci_hcd with acpi=off
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Dear all,

I tested:

pci=routirq
irq=routeirq
irqpoll (which is not realy an option)
pcu=usepirqmask

without any success :(

But problem is clearer now:

uhci_hcd is requesting an IRQ > 7 with is not supported with ACPI=off.

On another machine I was able to reserve all IRQ>7 for "ISA cards" :). 
Then uhci_hcd requested IRQ5 and everything works fine...

Unfortunately this BIOS option is not available on the target system.

Is there a way to tell the XEN kernel not to use a specific IRQ? Or a 
list of IRQ? Or tell uhci_hcd to use IRQ5?

I tried without success:

pirq=10,...
pnp_reserve_irq=7,10,11
isapnp_reserve_irq=7,10,11  (which seems to be obsolete...)

Any idea from you?

Best Regards
Werner









_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Mon Jun 04 20:11:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20: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 1Sbdb5-0005T2-Mv; Mon, 04 Jun 2012 20:09:51 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbdb4-0005Sx-H1
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:09:50 +0000
Received: from [85.158.139.83:35729] by server-6.bemta-5.messagelabs.com id
	E6/FE-18700-D061DCF4; Mon, 04 Jun 2012 20:09:49 +0000
X-Env-Sender: werner@xxlwade.de
X-Msg-Ref: server-13.tower-182.messagelabs.com!1338840588!31438023!1
X-Originating-IP: [88.198.0.151]
X-SpamReason: No, hits=3.4 required=7.0 tests=HELO_DYNAMIC_IPADDR
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2960 invoked from network); 4 Jun 2012 20:09:49 -0000
Received: from static.88-198-0-151.clients.your-server.de (HELO
	static-ip-217-172-170-8.inaddr.intergenia.de) (88.198.0.151)
	by server-13.tower-182.messagelabs.com with SMTP;
	4 Jun 2012 20:09:49 -0000
Received: from [192.168.1.2] (localhost [127.0.0.1])
	by static-ip-217-172-170-8.inaddr.intergenia.de (Postfix) with ESMTPA
	id C4C6116273
	for ; Mon,  4 Jun 2012 22:09:48 +0200 (CEST)
Message-ID: <4FCD160C.6030002@xxlwade.de>
Date: Mon, 04 Jun 2012 22:09:48 +0200
From: Werner Fehn 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCB82DE.4080506@xxlwade.de>
In-Reply-To: <4FCB82DE.4080506@xxlwade.de>
Subject: Re: [Xen-users] need to load uhci_hcd with acpi=off
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Dear all,

I tested:

pci=routirq
irq=routeirq
irqpoll (which is not realy an option)
pcu=usepirqmask

without any success :(

But problem is clearer now:

uhci_hcd is requesting an IRQ > 7 with is not supported with ACPI=off.

On another machine I was able to reserve all IRQ>7 for "ISA cards" :). 
Then uhci_hcd requested IRQ5 and everything works fine...

Unfortunately this BIOS option is not available on the target system.

Is there a way to tell the XEN kernel not to use a specific IRQ? Or a 
list of IRQ? Or tell uhci_hcd to use IRQ5?

I tried without success:

pirq=10,...
pnp_reserve_irq=7,10,11
isapnp_reserve_irq=7,10,11  (which seems to be obsolete...)

Any idea from you?

Best Regards
Werner









_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Mon Jun 04 20:12:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:12: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 1Sbdc7-0005VH-Fa; Mon, 04 Jun 2012 20:10:55 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbdc6-0005V4-0h
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:10:54 +0000
Received: from [85.158.143.99:32799] by server-3.bemta-4.messagelabs.com id
	BA/2D-29237-D461DCF4; Mon, 04 Jun 2012 20:10:53 +0000
X-Env-Sender: baileyp@ct-itsolutions.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1338840651!27930472!1
X-Originating-IP: [173.201.193.184]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTczLjIwMS4xOTMuMTg0ID0+IDE1MTA3\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15629 invoked from network); 4 Jun 2012 20:10:52 -0000
Received: from p3plsmtp18-02-2.prod.phx3.secureserver.net (HELO
	p3plwbeout18-02.prod.phx3.secureserver.net) (173.201.193.184)
	by server-7.tower-216.messagelabs.com with SMTP;
	4 Jun 2012 20:10:52 -0000
Received: from localhost ([173.201.193.245])
	by p3plwbeout18-02.prod.phx3.secureserver.net with bizsmtp
	id JLAq1j0015J8WZH01LAqTF; Mon, 04 Jun 2012 13:10:50 -0700
x-cmae-analysis: v=2.0 cv=T4AOvo2Q c=1 sm=1 a=s9mnUP56SRzXDLvfRu4LOg==:17
	a=kpwjDOozP74A:10 a=jaiTJcHAWCEA:10 a=uCovVhi4SGIA:10 a=jUMMqpT44fcA:10
	a=IkcTkHD0fZMA:10 a=TAIPOn3lAAAA:8 a=TZb1taSUAAAA:8
	a=0LJ8Da0mnV7pHPDjNdQA:9
	a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10 a=s9mnUP56SRzXDLvfRu4LOg==:117
Received: (qmail 6994 invoked by uid 99); 4 Jun 2012 20:10:50 -0000
X-Originating-IP: 208.47.241.42
User-Agent: Workspace Webmail 5.6.18
Message-Id: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
From: 
To: xen-users@lists.xen.org
Date: Mon, 04 Jun 2012 13:10:49 -0700
Mime-Version: 1.0
Subject: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3060576208609186944=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3060576208609186944==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"


   I need to figure out how powerful a server I need to=
 run Xen. Specifically, I'm looking to replace about 30 Windows XP desktops=
 with low-power thin-clients using VNC to connect to virtual desktops provi=
ded by Xen. This is supposed to be a cheap interim step while we work to re=
place an Access system that most of our employees use with a web-based prog=
ram, at which point most of the VM's would be deprecated (as the thin-clien=
t PC's would simply be used to connect to the intranet site).
&nb=
sp;  So, in short -- I'm looking to replace about 30 WinXP desktops wi=
th VM's hosted by Xen, and I need to figure out how much memory and CPU pow=
er I'll need to make this feasible. Is there some guideline I can use to fi=
gure this out?



--===============3060576208609186944==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3060576208609186944==--

From xen-users-bounces@lists.xen.org Mon Jun 04 20:12:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:12: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 1Sbdc7-0005VH-Fa; Mon, 04 Jun 2012 20:10:55 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbdc6-0005V4-0h
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:10:54 +0000
Received: from [85.158.143.99:32799] by server-3.bemta-4.messagelabs.com id
	BA/2D-29237-D461DCF4; Mon, 04 Jun 2012 20:10:53 +0000
X-Env-Sender: baileyp@ct-itsolutions.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1338840651!27930472!1
X-Originating-IP: [173.201.193.184]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTczLjIwMS4xOTMuMTg0ID0+IDE1MTA3\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15629 invoked from network); 4 Jun 2012 20:10:52 -0000
Received: from p3plsmtp18-02-2.prod.phx3.secureserver.net (HELO
	p3plwbeout18-02.prod.phx3.secureserver.net) (173.201.193.184)
	by server-7.tower-216.messagelabs.com with SMTP;
	4 Jun 2012 20:10:52 -0000
Received: from localhost ([173.201.193.245])
	by p3plwbeout18-02.prod.phx3.secureserver.net with bizsmtp
	id JLAq1j0015J8WZH01LAqTF; Mon, 04 Jun 2012 13:10:50 -0700
x-cmae-analysis: v=2.0 cv=T4AOvo2Q c=1 sm=1 a=s9mnUP56SRzXDLvfRu4LOg==:17
	a=kpwjDOozP74A:10 a=jaiTJcHAWCEA:10 a=uCovVhi4SGIA:10 a=jUMMqpT44fcA:10
	a=IkcTkHD0fZMA:10 a=TAIPOn3lAAAA:8 a=TZb1taSUAAAA:8
	a=0LJ8Da0mnV7pHPDjNdQA:9
	a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10 a=s9mnUP56SRzXDLvfRu4LOg==:117
Received: (qmail 6994 invoked by uid 99); 4 Jun 2012 20:10:50 -0000
X-Originating-IP: 208.47.241.42
User-Agent: Workspace Webmail 5.6.18
Message-Id: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
From: 
To: xen-users@lists.xen.org
Date: Mon, 04 Jun 2012 13:10:49 -0700
Mime-Version: 1.0
Subject: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3060576208609186944=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3060576208609186944==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"


   I need to figure out how powerful a server I need to=
 run Xen. Specifically, I'm looking to replace about 30 Windows XP desktops=
 with low-power thin-clients using VNC to connect to virtual desktops provi=
ded by Xen. This is supposed to be a cheap interim step while we work to re=
place an Access system that most of our employees use with a web-based prog=
ram, at which point most of the VM's would be deprecated (as the thin-clien=
t PC's would simply be used to connect to the intranet site).
&nb=
sp;  So, in short -- I'm looking to replace about 30 WinXP desktops wi=
th VM's hosted by Xen, and I need to figure out how much memory and CPU pow=
er I'll need to make this feasible. Is there some guideline I can use to fi=
gure this out?



--===============3060576208609186944==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3060576208609186944==--

From xen-users-bounces@lists.xen.org Mon Jun 04 20:36:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:36: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 1SbdzH-00068v-Qt; Mon, 04 Jun 2012 20:34:51 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbdzF-00068q-Fe
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:34:49 +0000
Received: from [85.158.139.83:13568] by server-1.bemta-5.messagelabs.com id
	87/33-25424-8EB1DCF4; Mon, 04 Jun 2012 20:34:48 +0000
X-Env-Sender: anil.rao@ericsson.com
X-Msg-Ref: server-4.tower-182.messagelabs.com!1338842085!29272243!1
X-Originating-IP: [198.24.6.9]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDc4MzY=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1567 invoked from network); 4 Jun 2012 20:34:47 -0000
Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9)
	by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 20:34:47 -0000
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181])
	by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id
	q54KYg9e022228
	for ; Mon, 4 Jun 2012 15:34:45 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by
	eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi;
	Mon, 4 Jun 2012 16:34:41 -0400
From: Anil Rao 
To: "xen-users@lists.xen.org" 
Date: Mon, 4 Jun 2012 16:34:41 -0400
Thread-Topic: [Xen-users] Hotplugging FPGA to running VM
Thread-Index: Ac0/rUGlkC/TnlohSamQWkEOLB9CdQAfJc9wAJmnnIA=
Message-ID: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
	
In-Reply-To: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8968964047136748700=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============8968964047136748700==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_"

--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

After poking around some more on my host, I noticed the following differenc=
es in the output of qemu-dm, which are shown below (extracted from /var/log=
/xen/qemu-dm-VMName.log).


Case 1: VM was powered on 'before' PCI device (FPGA) was brought on-line
---------------------------------------------------------------------------=
----------------------------------
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.0 ...
register_real_device: Error: couldn't locate device in libpci structures


Case 2: VM was powered on 'after' PCI device (FPGA) was brought on-line
---------------------------------------------------------------------------=
-------------------------------
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.0 ...
register_real_device: Enable MSI translation via per device option
register_real_device: Disable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No =
such file or directory: 0x1:0x0.0x0
pt_register_regions: IO region registered (size=3D0x00100000 base_addr=3D0x=
c6000000)
pt_register_regions: IO region registered (size=3D0x00100000 base_addr=3D0x=
c6100000)
pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1
register_real_device: Real physical device 01:00.0 registered successfuly!

So clearly, qemu-dm reported an error for case (1) and reported success for=
 case (2).

The interesting thing is why did the Xen xm pci-attach command report succe=
ss in both cases. Also, from Xen's perspective it appears that the afore-me=
ntioned PCI device is assigned to the VM in both cases (as verified by usin=
g the xm commands to get the list of remaining assignable PCI devices and t=
he list of PCI devices attached to the VM).

Something seems wrong here.

Any thoughts?

-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com; xen-users@lists.=
xen.org

Subject: Re: [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control blade in our router chassis=
 has one of these FPGAs and its primary function is to control certain dedi=
cated hardware components on the blade that are responsible for establishin=
g connectivity with the high-speed inter-blade fabric on the router. I am s=
orry, but I cannot divulge additional details regarding the FPGA.

Here is a more detailed description of my actual usage scenario.

1) The FPGA image must be downloaded onto the device before it can be enabl=
ed for use.
2) The VM in question is responsible for performing step (1), which means t=
hat the FPGA is not visible to Xen/Dom-0 when
    the VM is powered on.
3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci=
-hotplug to assign the device to the VM.
    This operation completes successfully (as reported by the appropriate x=
l command).
4) However, the guest OS inside the VM cannot see the FPGA device after ste=
p (3).
5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th=
e FPGA device (and everything then proceeds normally).

The troublesome part here is that I need to shutdown and restart the VM. I =
would like to avoid this and rely on Xen pci-hotplug to make the device vis=
ible to the guest OS inside the VM.

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve=
lopment board or something already assembled and functioning that contains =
an FPGA device(s)?

Well, just being curious... :)



Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o=
f PCI devices to the VM. The only one that doesn't work is the FPGA device.=
 Even for this one, the only time it doesn't work, is if the VM was powered=
-on prior to the FPGA device being brought on-line on the host. If the FPGA=
 was present before the VM was powered-on everything works as expected.

It somehow seems like new devices that are introduced in the host, after a =
VM has been started on it, cannot be hotplugged into the VM.

Thanks.
-Anil


________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com=
] On Behalf Of John Sherwood
Sent: Wednesday, May 30, 2012 7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Are you sure the guest OS has PCI hotplug support?

On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote:
Hi,

I am trying to assign a FPGA (which is a PCI device) to a running VM. The i=
nteresting thing here is that the FPGA is not present when the VM was power=
ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line=
 on the host by downloading its image to the device.

So far my attempts at using Xen PCI-passthrough have not been successful. A=
lthough Xen reports that the pass-through operation was successful, which I=
 have verified using the appropriate xl command, I am unable to see the FPG=
A from within the guest OS.

I have tried both manual rescanning of the PCI bus inside the guest as well=
 as making use of the pciehp driver. The only way I can (reliably) see the =
FPGA from within the guest, is to shutdown and restart the VM and then redo=
 the hotplug operation. I want to avoid a VM reboot and was wondering if th=
is is at all possible and if so what do I need to do to realize it.

[The virtualization host is based on the default Xen setup that comes with =
SLES 11 SP2]

Thanks for any help on this matter.

-Anil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable







After poking around some more on my host, I notice=
d the=20
following differences in the output of qemu-dm, which are shown below (extr=
acted=20
from /var/log/xen/qemu-dm-VMName.log).

 


 




Case 1: VM was powered on 'before' PCI device (FPGA) was brought=20
on-line


----------------------------------------------------------------------=
---------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Error: couldn't locate device in libpci=20
structures


 


 


Case 2: VM was powered on 'after' PCI device (FPGA) was brought=20
on-line


----------------------------------------------------------------------=
------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Enable MSI translation via per device option

register_real_device: Disable power management


pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul=
: No=20
such file or directory: 0x1:0x0.0x0


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6000000)


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6100000)


pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1


register_real_device: Real physical device 01:00.0 registered=20
successfuly!


 


So=20
clearly, qemu-dm reported an error for case (1) and reported success for ca=
se=20
(2).


 


The=20
interesting thing is why did the Xen xm pci-attach command report success i=
n=20
both cases. Also, from Xen's perspective it appears that the afore-mentione=
d PCI=20
device is assigned to the VM in both cases (as verified by using the xm com=
mands=20
to get the list of remaining assignable PCI devices and the list of PCI dev=
ices=20
attached to the VM).


 


Something seems wrong here.


 


Any=20
thoughts?


 


-Anil


 <=
/DIV>







From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of An=
il=20
Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.c=
om;=20
xen-users@lists.xen.org 





  

  

  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This=
 is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
 

  
Here is a more detailed description of my actual us=
age=20
  scenario.

  
 

  
1) T=
he FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) T=
he VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
    the VM is powered on.
  
3) A=
fter the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
    This operation completes successfully =
(as=20
  reported by the appropriate xl command).

  
4) H=
owever, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) I=
f I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
 

  
The =
troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
 

  
Thanks.

  
-Anil

  
 

  

  

  

  
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
cyberhawk001@gmail.com
Sent: Thursday, May =
31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-u=
sers]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
Ye=
s, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for thi=
s=20
    one, the only time it doesn't work, is if the VM was powered-on prior t=
o the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
 

    
It=
 somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
 

    
Thanks.

    
-Anil

    
 

    
 

    

    

    

    
From: theubaz@gmail.com=
 [mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re=
:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
 

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
 

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
 

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
 

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
 

      
Thanks for any help on this matter.

      
 

      
-Anil
<=
/BLOCKQUOTE>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users




--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_--


--===============8968964047136748700==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8968964047136748700==--


From xen-users-bounces@lists.xen.org Mon Jun 04 20:36:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:36: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 1SbdzH-00068v-Qt; Mon, 04 Jun 2012 20:34:51 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbdzF-00068q-Fe
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:34:49 +0000
Received: from [85.158.139.83:13568] by server-1.bemta-5.messagelabs.com id
	87/33-25424-8EB1DCF4; Mon, 04 Jun 2012 20:34:48 +0000
X-Env-Sender: anil.rao@ericsson.com
X-Msg-Ref: server-4.tower-182.messagelabs.com!1338842085!29272243!1
X-Originating-IP: [198.24.6.9]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk4LjI0LjYuOSA9PiAyNDc4MzY=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1567 invoked from network); 4 Jun 2012 20:34:47 -0000
Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9)
	by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 20:34:47 -0000
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181])
	by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id
	q54KYg9e022228
	for ; Mon, 4 Jun 2012 15:34:45 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.66]) by
	eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi;
	Mon, 4 Jun 2012 16:34:41 -0400
From: Anil Rao 
To: "xen-users@lists.xen.org" 
Date: Mon, 4 Jun 2012 16:34:41 -0400
Thread-Topic: [Xen-users] Hotplugging FPGA to running VM
Thread-Index: Ac0/rUGlkC/TnlohSamQWkEOLB9CdQAfJc9wAJmnnIA=
Message-ID: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
	
In-Reply-To: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8968964047136748700=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============8968964047136748700==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_"

--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

After poking around some more on my host, I noticed the following differenc=
es in the output of qemu-dm, which are shown below (extracted from /var/log=
/xen/qemu-dm-VMName.log).


Case 1: VM was powered on 'before' PCI device (FPGA) was brought on-line
---------------------------------------------------------------------------=
----------------------------------
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.0 ...
register_real_device: Error: couldn't locate device in libpci structures


Case 2: VM was powered on 'after' PCI device (FPGA) was brought on-line
---------------------------------------------------------------------------=
-------------------------------
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.0 ...
register_real_device: Enable MSI translation via per device option
register_real_device: Disable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No =
such file or directory: 0x1:0x0.0x0
pt_register_regions: IO region registered (size=3D0x00100000 base_addr=3D0x=
c6000000)
pt_register_regions: IO region registered (size=3D0x00100000 base_addr=3D0x=
c6100000)
pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1
register_real_device: Real physical device 01:00.0 registered successfuly!

So clearly, qemu-dm reported an error for case (1) and reported success for=
 case (2).

The interesting thing is why did the Xen xm pci-attach command report succe=
ss in both cases. Also, from Xen's perspective it appears that the afore-me=
ntioned PCI device is assigned to the VM in both cases (as verified by usin=
g the xm commands to get the list of remaining assignable PCI devices and t=
he list of PCI devices attached to the VM).

Something seems wrong here.

Any thoughts?

-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Anil Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com; xen-users@lists.=
xen.org

Subject: Re: [Xen-users] Hotplugging FPGA to running VM

This is a proprietary FPGA device. Each control blade in our router chassis=
 has one of these FPGAs and its primary function is to control certain dedi=
cated hardware components on the blade that are responsible for establishin=
g connectivity with the high-speed inter-blade fabric on the router. I am s=
orry, but I cannot divulge additional details regarding the FPGA.

Here is a more detailed description of my actual usage scenario.

1) The FPGA image must be downloaded onto the device before it can be enabl=
ed for use.
2) The VM in question is responsible for performing step (1), which means t=
hat the FPGA is not visible to Xen/Dom-0 when
    the VM is powered on.
3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen pci=
-hotplug to assign the device to the VM.
    This operation completes successfully (as reported by the appropriate x=
l command).
4) However, the guest OS inside the VM cannot see the FPGA device after ste=
p (3).
5) If I shutdown the VM and re-start it, the guest OS inside the VM sees th=
e FPGA device (and everything then proceeds normally).

The troublesome part here is that I need to shutdown and restart the VM. I =
would like to avoid this and rely on Xen pci-hotplug to make the device vis=
ible to the guest OS inside the VM.

Thanks.
-Anil

________________________________
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of cyberhawk001@gmail.com
Sent: Thursday, May 31, 2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Just out of curiosity, what kind of FPGA device is this? Is it an FPGA deve=
lopment board or something already assembled and functioning that contains =
an FPGA device(s)?

Well, just being curious... :)



Yes, the guest OS has PCI hotplug support. I am able to hotplug a variety o=
f PCI devices to the VM. The only one that doesn't work is the FPGA device.=
 Even for this one, the only time it doesn't work, is if the VM was powered=
-on prior to the FPGA device being brought on-line on the host. If the FPGA=
 was present before the VM was powered-on everything works as expected.

It somehow seems like new devices that are introduced in the host, after a =
VM has been started on it, cannot be hotplugged into the VM.

Thanks.
-Anil


________________________________
From: theubaz@gmail.com [mailto:theubaz@gmail.com=
] On Behalf Of John Sherwood
Sent: Wednesday, May 30, 2012 7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Hotplugging FPGA to running VM

Are you sure the guest OS has PCI hotplug support?

On Wed, May 30, 2012 at 10:14 PM, Anil Rao > wrote:
Hi,

I am trying to assign a FPGA (which is a PCI device) to a running VM. The i=
nteresting thing here is that the FPGA is not present when the VM was power=
ed-on. I.e. sometime after the VM was started, the FPGA was brought on-line=
 on the host by downloading its image to the device.

So far my attempts at using Xen PCI-passthrough have not been successful. A=
lthough Xen reports that the pass-through operation was successful, which I=
 have verified using the appropriate xl command, I am unable to see the FPG=
A from within the guest OS.

I have tried both manual rescanning of the PCI bus inside the guest as well=
 as making use of the pciehp driver. The only way I can (reliably) see the =
FPGA from within the guest, is to shutdown and restart the VM and then redo=
 the hotplug operation. I want to avoid a VM reboot and was wondering if th=
is is at all possible and if so what do I need to do to realize it.

[The virtualization host is based on the default Xen setup that comes with =
SLES 11 SP2]

Thanks for any help on this matter.

-Anil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable







After poking around some more on my host, I notice=
d the=20
following differences in the output of qemu-dm, which are shown below (extr=
acted=20
from /var/log/xen/qemu-dm-VMName.log).

 


 




Case 1: VM was powered on 'before' PCI device (FPGA) was brought=20
on-line


----------------------------------------------------------------------=
---------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Error: couldn't locate device in libpci=20
structures


 


 


Case 2: VM was powered on 'after' PCI device (FPGA) was brought=20
on-line


----------------------------------------------------------------------=
------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Enable MSI translation via per device option

register_real_device: Disable power management


pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul=
: No=20
such file or directory: 0x1:0x0.0x0


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6000000)


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6100000)


pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1


register_real_device: Real physical device 01:00.0 registered=20
successfuly!


 


So=20
clearly, qemu-dm reported an error for case (1) and reported success for ca=
se=20
(2).


 


The=20
interesting thing is why did the Xen xm pci-attach command report success i=
n=20
both cases. Also, from Xen's perspective it appears that the afore-mentione=
d PCI=20
device is assigned to the VM in both cases (as verified by using the xm com=
mands=20
to get the list of remaining assignable PCI devices and the list of PCI dev=
ices=20
attached to the VM).


 


Something seems wrong here.


 


Any=20
thoughts?


 


-Anil


 <=
/DIV>







From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of An=
il=20
Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.c=
om;=20
xen-users@lists.xen.org 





  

  

  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This=
 is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
 

  
Here is a more detailed description of my actual us=
age=20
  scenario.

  
 

  
1) T=
he FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) T=
he VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
    the VM is powered on.
  
3) A=
fter the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
    This operation completes successfully =
(as=20
  reported by the appropriate xl command).

  
4) H=
owever, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) I=
f I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
 

  
The =
troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
 

  
Thanks.

  
-Anil

  
 

  

  

  

  
From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of =
cyberhawk001@gmail.com
Sent: Thursday, May =
31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-u=
sers]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
Ye=
s, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for thi=
s=20
    one, the only time it doesn't work, is if the VM was powered-on prior t=
o the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
 

    
It=
 somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
 

    
Thanks.

    
-Anil

    
 

    
 

    

    

    

    
From: theubaz@gmail.com=
 [mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com
Subject: Re=
:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
 

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
 

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
 

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
 

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
 

      
Thanks for any help on this matter.

      
 

      
-Anil
<=
/BLOCKQUOTE>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users




--_000_DD729E174A25344F8D7D351BA4CF57272DAD45DC07EUSAACMS0715e_--


--===============8968964047136748700==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8968964047136748700==--


From xen-users-bounces@lists.xen.org Mon Jun 04 20:38:22 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20: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 1Sbe1O-0006F9-KA; Mon, 04 Jun 2012 20:37:02 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbe1N-0006Ew-9h
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:37:01 +0000
Received: from [85.158.143.99:33547] by server-3.bemta-4.messagelabs.com id
	94/3C-29237-C6C1DCF4; Mon, 04 Jun 2012 20:37:00 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-13.tower-216.messagelabs.com!1338842218!30410854!1
X-Originating-IP: [209.85.213.45]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16805 invoked from network); 4 Jun 2012 20:36:59 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 20:36:59 -0000
Received: by yhoo21 with SMTP id o21so3880437yho.32
	for ; Mon, 04 Jun 2012 13:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=GrpqPNm1amX3AeziJtKJlpx56kOZ9ATNIahdWutRfSE=;
	b=O0kLemShLlTfFu8TS3xmtBSdc3FPT4jpaJdeWpjixJM/EP/4PVqikB7a9qcwkI8dD5
	riCUrxX0rdlnx9bdQG92DNkDFk/tVINHKcZOnAXQT4/+bsXxQ/S3t4Rg8kysK//5pccV
	+oUJDwB6hVfPBR95d82G70SL40/AOgUmMr5dAY/rLPBlW8rkREm5ZbkCtlybqs/fvU9l
	e65gJp7hFI+vSBWezj6YEXjJs3Vzjo587VvD4O6oPWBTlC/9URTVWUNy9VlmweJWtdfv
	oXn+mSAvWiFrqwMpurASROBa2/D0KXk+ClriRVeCGeUjzbhBKHdeYXbLi0zvgm0NeoLv
	6BjA==
MIME-Version: 1.0
Received: by 10.50.222.170 with SMTP id qn10mr9513694igc.45.1338842217670;
	Mon, 04 Jun 2012 13:36:57 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Mon, 4 Jun 2012 13:36:57 -0700 (PDT)
In-Reply-To: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
References: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
Date: Mon, 4 Jun 2012 16:36:57 -0400
X-Google-Sender-Auth: DHgCmNc9ElocjzG1M6KfvljfWKU
Message-ID: 
From: John Sherwood 
To: baileyp@ct-itsolutions.com
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5317893033959889842=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5317893033959889842==
Content-Type: multipart/alternative; boundary=14dae9341111cb680f04c1ab7eec

--14dae9341111cb680f04c1ab7eec
Content-Type: text/plain; charset=ISO-8859-1

You don't need a "powerful" server to run Xen by any means, but to run Xen
and 30 VMs is a different story.  Not to be pedantic, but the requirements
for power come entirely from your workload, not from the (extremely
lightweight) Xen hypervisor itself.

Bare minimum you'll want 1 core + 512 MB RAM for each VM, then a core and
additional RAM for the dom0.  With 30 VMs you're going to want a pretty
beefy amount of RAM for your dom0, and you'll probably need another core as
well.  You'd probably want at least 2 NICs so that you have more bandwidth
when you've got a couple dozen VNC connections active.

However: I have no experience running that many HVM machines at once - I've
run 16 VMs on an 8 core, 16 thread host before, but that was with PV.  At
any rate, I suppose my suggestion for your server would be:

   - 32 cores (using either something like opteron 62XX interlagos, or Xeon
   E5-26XX)
   - 32+ GB RAM
   - 3+ NICs, 1 dedicated for management of dom0

If you have any boxes lying around, I might also suggest trying to load an
8 core server with 7 winXP VMs and seeing how it performs with all the VMs
having VNC active - that should give you a decent feel for whether you need
to scale up your requirements before purchasing or allocating more
expensive hardware.  Keep in mind that you want to scale up the dom0 memory
as you add more VMs though, and the load on the dom0 will increase with
more VMs as well - due to the HVMs, the dom0 load will increase with the
number of virtualized peripherals.


On Mon, Jun 4, 2012 at 4:10 PM,  wrote:

>    I need to figure out how powerful a server I need to run Xen.
> Specifically, I'm looking to replace about 30 Windows XP desktops with
> low-power thin-clients using VNC to connect to virtual desktops provided by
> Xen. This is supposed to be a cheap interim step while we work to replace
> an Access system that most of our employees use with a web-based program,
> at which point most of the VM's would be deprecated (as the thin-client
> PC's would simply be used to connect to the intranet site).
>    So, in short -- I'm looking to replace about 30 WinXP desktops with
> VM's hosted by Xen, and I need to figure out how much memory and CPU power
> I'll need to make this feasible. Is there some guideline I can use to
> figure this out?
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
>

--14dae9341111cb680f04c1ab7eec
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


You don't need a "powerful" server to run Xen by any mea=
ns, but to run Xen and 30 VMs is a different story. =A0Not to be pedantic, =
but the requirements for power come entirely from your workload, not from t=
he (extremely lightweight) Xen hypervisor itself.



Bare minimum you'll want 1 core + 512 MB RAM for each VM=
, then a core and additional RAM for the dom0. =A0With 30 VMs you're go=
ing to want a pretty beefy amount of RAM for your dom0, and you'll prob=
ably need another core as well. =A0You'd probably want at least 2 NICs =
so that you have more bandwidth when you've got a couple dozen VNC conn=
ections active.


However: I have no experience running that many HVM machines=
 at once - I've run 16 VMs on an 8 core, 16 thread host before, but tha=
t was with PV. =A0At any rate, I suppose my suggestion for your server woul=
d be:


  • 32 cores (using either something like opteron 62XX interlagos,=
 or Xeon E5-26XX)
  • 32+ GB RAM
  • 3+ NICs, 1 dedicated for manag=
ement of dom0
If you have any boxes lying around, I might als=
o suggest trying to load an 8 core server with 7 winXP VMs and seeing how i=
t performs with all the VMs having VNC active - that should give you a dece=
nt feel for whether you need to scale up your requirements before purchasin=
g or allocating more expensive hardware. =A0Keep in mind that you want to s=
cale up the dom0 memory as you add more VMs though, and the load on the dom=
0 will increase with more VMs as well - due to the HVMs, the dom0 load will=
 increase with the number of virtualized peripherals.




On Mon, Jun 4, 2012=
 at 4:10 PM,  <baileyp@ct-itsolutions.com> wrote:


=A0 =A0I need =
to figure out how powerful a server I need to run Xen. Specifically, I'=
m looking to replace about 30 Windows XP desktops with low-power thin-clien=
ts using VNC to connect to virtual desktops provided by Xen. This is suppos=
ed to be a cheap interim step while we work to replace an Access system tha=
t most of our employees use with a web-based program, at which point most o=
f the VM's would be deprecated (as the thin-client PC's would simpl=
y be used to connect to the intranet site).


=A0 =A0So, in short -- I'm looking to replace about 30 WinXP deskt=
ops with VM's hosted by Xen, and I need to figure out how much memory a=
nd CPU power I'll need to make this feasible. Is there some guideline I=
 can use to figure this out?





_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9341111cb680f04c1ab7eec--


--===============5317893033959889842==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5317893033959889842==--


From xen-users-bounces@lists.xen.org Mon Jun 04 20:38:22 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20: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 1Sbe1O-0006F9-KA; Mon, 04 Jun 2012 20:37:02 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbe1N-0006Ew-9h
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:37:01 +0000
Received: from [85.158.143.99:33547] by server-3.bemta-4.messagelabs.com id
	94/3C-29237-C6C1DCF4; Mon, 04 Jun 2012 20:37:00 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-13.tower-216.messagelabs.com!1338842218!30410854!1
X-Originating-IP: [209.85.213.45]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16805 invoked from network); 4 Jun 2012 20:36:59 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 20:36:59 -0000
Received: by yhoo21 with SMTP id o21so3880437yho.32
	for ; Mon, 04 Jun 2012 13:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=GrpqPNm1amX3AeziJtKJlpx56kOZ9ATNIahdWutRfSE=;
	b=O0kLemShLlTfFu8TS3xmtBSdc3FPT4jpaJdeWpjixJM/EP/4PVqikB7a9qcwkI8dD5
	riCUrxX0rdlnx9bdQG92DNkDFk/tVINHKcZOnAXQT4/+bsXxQ/S3t4Rg8kysK//5pccV
	+oUJDwB6hVfPBR95d82G70SL40/AOgUmMr5dAY/rLPBlW8rkREm5ZbkCtlybqs/fvU9l
	e65gJp7hFI+vSBWezj6YEXjJs3Vzjo587VvD4O6oPWBTlC/9URTVWUNy9VlmweJWtdfv
	oXn+mSAvWiFrqwMpurASROBa2/D0KXk+ClriRVeCGeUjzbhBKHdeYXbLi0zvgm0NeoLv
	6BjA==
MIME-Version: 1.0
Received: by 10.50.222.170 with SMTP id qn10mr9513694igc.45.1338842217670;
	Mon, 04 Jun 2012 13:36:57 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Mon, 4 Jun 2012 13:36:57 -0700 (PDT)
In-Reply-To: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
References: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
Date: Mon, 4 Jun 2012 16:36:57 -0400
X-Google-Sender-Auth: DHgCmNc9ElocjzG1M6KfvljfWKU
Message-ID: 
From: John Sherwood 
To: baileyp@ct-itsolutions.com
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5317893033959889842=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5317893033959889842==
Content-Type: multipart/alternative; boundary=14dae9341111cb680f04c1ab7eec

--14dae9341111cb680f04c1ab7eec
Content-Type: text/plain; charset=ISO-8859-1

You don't need a "powerful" server to run Xen by any means, but to run Xen
and 30 VMs is a different story.  Not to be pedantic, but the requirements
for power come entirely from your workload, not from the (extremely
lightweight) Xen hypervisor itself.

Bare minimum you'll want 1 core + 512 MB RAM for each VM, then a core and
additional RAM for the dom0.  With 30 VMs you're going to want a pretty
beefy amount of RAM for your dom0, and you'll probably need another core as
well.  You'd probably want at least 2 NICs so that you have more bandwidth
when you've got a couple dozen VNC connections active.

However: I have no experience running that many HVM machines at once - I've
run 16 VMs on an 8 core, 16 thread host before, but that was with PV.  At
any rate, I suppose my suggestion for your server would be:

   - 32 cores (using either something like opteron 62XX interlagos, or Xeon
   E5-26XX)
   - 32+ GB RAM
   - 3+ NICs, 1 dedicated for management of dom0

If you have any boxes lying around, I might also suggest trying to load an
8 core server with 7 winXP VMs and seeing how it performs with all the VMs
having VNC active - that should give you a decent feel for whether you need
to scale up your requirements before purchasing or allocating more
expensive hardware.  Keep in mind that you want to scale up the dom0 memory
as you add more VMs though, and the load on the dom0 will increase with
more VMs as well - due to the HVMs, the dom0 load will increase with the
number of virtualized peripherals.


On Mon, Jun 4, 2012 at 4:10 PM,  wrote:

>    I need to figure out how powerful a server I need to run Xen.
> Specifically, I'm looking to replace about 30 Windows XP desktops with
> low-power thin-clients using VNC to connect to virtual desktops provided by
> Xen. This is supposed to be a cheap interim step while we work to replace
> an Access system that most of our employees use with a web-based program,
> at which point most of the VM's would be deprecated (as the thin-client
> PC's would simply be used to connect to the intranet site).
>    So, in short -- I'm looking to replace about 30 WinXP desktops with
> VM's hosted by Xen, and I need to figure out how much memory and CPU power
> I'll need to make this feasible. Is there some guideline I can use to
> figure this out?
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
>

--14dae9341111cb680f04c1ab7eec
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


You don't need a "powerful" server to run Xen by any mea=
ns, but to run Xen and 30 VMs is a different story. =A0Not to be pedantic, =
but the requirements for power come entirely from your workload, not from t=
he (extremely lightweight) Xen hypervisor itself.



Bare minimum you'll want 1 core + 512 MB RAM for each VM=
, then a core and additional RAM for the dom0. =A0With 30 VMs you're go=
ing to want a pretty beefy amount of RAM for your dom0, and you'll prob=
ably need another core as well. =A0You'd probably want at least 2 NICs =
so that you have more bandwidth when you've got a couple dozen VNC conn=
ections active.


However: I have no experience running that many HVM machines=
 at once - I've run 16 VMs on an 8 core, 16 thread host before, but tha=
t was with PV. =A0At any rate, I suppose my suggestion for your server woul=
d be:


  • 32 cores (using either something like opteron 62XX interlagos,=
 or Xeon E5-26XX)
  • 32+ GB RAM
  • 3+ NICs, 1 dedicated for manag=
ement of dom0
If you have any boxes lying around, I might als=
o suggest trying to load an 8 core server with 7 winXP VMs and seeing how i=
t performs with all the VMs having VNC active - that should give you a dece=
nt feel for whether you need to scale up your requirements before purchasin=
g or allocating more expensive hardware. =A0Keep in mind that you want to s=
cale up the dom0 memory as you add more VMs though, and the load on the dom=
0 will increase with more VMs as well - due to the HVMs, the dom0 load will=
 increase with the number of virtualized peripherals.




On Mon, Jun 4, 2012=
 at 4:10 PM,  <baileyp@ct-itsolutions.com> wrote:


=A0 =A0I need =
to figure out how powerful a server I need to run Xen. Specifically, I'=
m looking to replace about 30 Windows XP desktops with low-power thin-clien=
ts using VNC to connect to virtual desktops provided by Xen. This is suppos=
ed to be a cheap interim step while we work to replace an Access system tha=
t most of our employees use with a web-based program, at which point most o=
f the VM's would be deprecated (as the thin-client PC's would simpl=
y be used to connect to the intranet site).


=A0 =A0So, in short -- I'm looking to replace about 30 WinXP deskt=
ops with VM's hosted by Xen, and I need to figure out how much memory a=
nd CPU power I'll need to make this feasible. Is there some guideline I=
 can use to figure this out?





_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9341111cb680f04c1ab7eec--


--===============5317893033959889842==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5317893033959889842==--


From xen-users-bounces@lists.xen.org Mon Jun 04 20:42:03 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:42: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 1Sbe54-0006Xo-Gz; Mon, 04 Jun 2012 20:40:50 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbe52-0006Xc-CW
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:40:48 +0000
Received: from [85.158.143.35:28580] by server-3.bemta-4.messagelabs.com id
	AC/3E-29237-F4D1DCF4; Mon, 04 Jun 2012 20:40:47 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-14.tower-21.messagelabs.com!1338842438!18837449!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23416 invoked from network); 4 Jun 2012 20:40:42 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 20:40:42 -0000
Received: by ggnp1 with SMTP id p1so3994777ggn.32
	for ; Mon, 04 Jun 2012 13:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=goEEUvjUZEr0Ko6fFvZ2mCxtBaHalafDZWMaFIDHtDc=;
	b=YF91NNScGl4R9lHxcdR1NAIJqq0aTysMdosnKdPQwIovleM35tYeQf16q6tOxLX1nK
	Hca7XORXYGbs7SPQtOpA3PGH6tJESeuHWsnAYT5AsfEj/4/KjvdnFiyo4P767rfX+ZPo
	/9HDUVrhKN+jCJ1xpRhlRW6iZM0noeIQx/M6RcPfKOiGlkO0KSLJfUwr9Yx3zEgwI5xn
	a7JoKfhuPNxBouOcxW1V8V5Gbz4K11NYpJNaLs0MscOfRvt1CE3c721rnmmremxJeA07
	7qBGTWwV958eri50d0xF1UHI4TRvHmWkqeFQlhllbD7hGvN+e3Wekws7pXKDKq3gSvV0
	zISA==
MIME-Version: 1.0
Received: by 10.50.222.170 with SMTP id qn10mr9522004igc.45.1338842438136;
	Mon, 04 Jun 2012 13:40:38 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Mon, 4 Jun 2012 13:40:38 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
	
	
Date: Mon, 4 Jun 2012 16:40:38 -0400
X-Google-Sender-Auth: 4GtiDji1ZHZ53eTJsSZYXyCjWIk
Message-ID: 
From: John Sherwood 
To: Anil Rao 
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7823484309714471199=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7823484309714471199==
Content-Type: multipart/alternative; boundary=14dae9341111ef74c904c1ab8bd3

--14dae9341111ef74c904c1ab8bd3
Content-Type: text/plain; charset=ISO-8859-1

It's quite possible that the error simply isn't propagating up to Xen
during the pci-attach command (and that would be my guess, given that
qemu-dm is noticing the error and xen isn't).  It would appear though that
you've found "why" it's failing, although who knows long it might take to
figure out the actual error in register_real_device.  This is probably
where you'll need to contact the developer list to make any progress.

On Mon, Jun 4, 2012 at 4:34 PM, Anil Rao  wrote:

> **
> After poking around some more on my host, I noticed the following
> differences in the output of qemu-dm, which are shown below (extracted from
> /var/log/xen/qemu-dm-VMName.log).
>
>
>  Case 1: VM was powered on 'before' PCI device (FPGA) was brought on-line
>
> -------------------------------------------------------------------------------------------------------------
> dm-command: hot insert pass-through pci dev
> register_real_device: Assigning real physical device 01:00.0 ...
> register_real_device: Error: couldn't locate device in libpci structures
>
>
> Case 2: VM was powered on 'after' PCI device (FPGA) was brought on-line
>
> ----------------------------------------------------------------------------------------------------------
> dm-command: hot insert pass-through pci dev
> register_real_device: Assigning real physical device 01:00.0 ...
> register_real_device: Enable MSI translation via per device option
> register_real_device: Disable power management
> pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No
> such file or directory: 0x1:0x0.0x0
> pt_register_regions: IO region registered (size=0x00100000
> base_addr=0xc6000000)
> pt_register_regions: IO region registered (size=0x00100000
> base_addr=0xc6100000)
> pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=1
> register_real_device: Real physical device 01:00.0 registered successfuly!
>
> So clearly, qemu-dm reported an error for case (1) and reported success
> for case (2).
>
> The interesting thing is why did the Xen xm pci-attach command report
> success in both cases. Also, from Xen's perspective it appears that the
> afore-mentioned PCI device is assigned to the VM in both cases (as verified
> by using the xm commands to get the list of remaining assignable PCI
> devices and the list of PCI devices attached to the VM).
>
> Something seems wrong here.
>
> Any thoughts?
>
> -Anil
>
>  ------------------------------
>  *From:* xen-users-bounces@lists.xen.org [mailto:
> xen-users-bounces@lists.xen.org] *On Behalf Of *Anil Rao
> *Sent:* Thursday, May 31, 2012 11:25 AM
> *To:* cyberhawk001@gmail.com; xen-users@lists.xen.org
>
>>
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>>   This is a proprietary FPGA device. Each control blade in our router
>> chassis has one of these FPGAs and its primary function is to control
>> certain dedicated hardware components on the blade that are responsible for
>> establishing connectivity with the high-speed inter-blade fabric on the
>> router. I am sorry, but I cannot divulge additional details regarding the
>> FPGA.
>>
>> Here is a more detailed description of my actual usage scenario.
>>
>> 1) The FPGA image must be downloaded onto the device before it can be
>> enabled for use.
>> 2) The VM in question is responsible for performing step (1), which means
>> that the FPGA is not visible to Xen/Dom-0 when
>>     the VM is powered on.
>> 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen
>> pci-hotplug to assign the device to the VM.
>>     This operation completes successfully (as reported by the appropriate
>> xl command).
>> 4) However, the guest OS inside the VM cannot see the FPGA device after
>> step (3).
>> 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees
>> the FPGA device (and everything then proceeds normally).
>>
>> The troublesome part here is that I need to shutdown and restart the VM.
>> I would like to avoid this and rely on Xen pci-hotplug to make the device
>> visible to the guest OS inside the VM.
>>
>> Thanks.
>> -Anil
>>
>>  ------------------------------
>>  *From:* xen-users-bounces@lists.xen.org [mailto:
>> xen-users-bounces@lists.xen.org] *On Behalf Of *cyberhawk001@gmail.com
>> *Sent:* Thursday, May 31, 2012 10:49 AM
>> *To:* xen-users@lists.xen.org
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>> Just out of curiosity, what kind of *FPGA device* is this? Is it an FPGA
>> development board or something already assembled and functioning that
>> contains an FPGA device(s)?
>>
>> Well, just being curious... :)
>>
>>
>>
>>  Yes, the guest OS has PCI hotplug support. I am able to hotplug a
>> variety of PCI devices to the VM. The only one that doesn't work is the
>> FPGA device. Even for this one, the only time it doesn't work, is if the VM
>> was powered-on prior to the FPGA device being brought on-line on the host.
>> If the FPGA was present before the VM was powered-on everything works as
>> expected.
>>
>> It somehow seems like new devices that are introduced in the host, after
>> a VM has been started on it, cannot be hotplugged into the VM.
>>
>> Thanks.
>> -Anil
>>
>>
>>  ------------------------------
>>  *From:* theubaz@gmail.com [mailto:theubaz@gmail.com ]
>> *On Behalf Of *John Sherwood
>> *Sent:* Wednesday, May 30, 2012 7:20 PM
>> *To:* Anil Rao
>> *Cc:* xen-users@lists.xensource.com
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>> Are you sure the guest OS has PCI hotplug support?
>>
>> On Wed, May 30, 2012 at 10:14 PM, Anil Rao  wrote:
>>
>>>  Hi,
>>>
>>> I am trying to assign a FPGA (which is a PCI device) to a running VM.
>>> The interesting thing here is that the FPGA is not present when the VM was
>>> powered-on. I.e. sometime after the VM was started, the FPGA was brought
>>> on-line on the host by downloading its image to the device.
>>>
>>> So far my attempts at using Xen PCI-passthrough have not been
>>> successful. Although Xen reports that the pass-through operation was
>>> successful, which I have verified using the appropriate xl command, I am
>>> unable to see the FPGA from within the guest OS.
>>>
>>> I have tried both manual rescanning of the PCI bus inside the guest as
>>> well as making use of the pciehp driver. The only way I can (reliably) see
>>> the FPGA from within the guest, is to shutdown and restart the VM and then
>>> redo the hotplug operation. I want to avoid a VM reboot and was wondering
>>> if this is at all possible and if so what do I need to do to realize it.
>>>
>>> [The virtualization host is based on the default Xen setup that comes
>>> with SLES 11 SP2]
>>>
>>> Thanks for any help on this matter.
>>>
>>> -Anil
>>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
>

--14dae9341111ef74c904c1ab8bd3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It's quite possible that the error simply isn't propagating up to X=
en during the pci-attach command (and that would be my guess, given that qe=
mu-dm is noticing the error and xen isn't). =A0It would appear though t=
hat you've found "why" it's failing, although who knows l=
ong it might take to figure out the actual error in register_real_device. =
=A0This is probably where you'll need to contact the developer list to =
make any progress.


On Mon, Jun 4, 2012 at 4:34 PM, Anil Rao <anil.rao@ericsson.com> wrote:








After poking around some more on my host, I noticed the=20
following differences in the output of qemu-dm, which are shown below (extr=
acted=20
from /var/log/xen/qemu-dm-VMName.log).


=A0


=A0




Case 1: VM was powered on 'before' PCI device (FPGA) was broug=
ht=20
on-line


----------------------------------------------------------------------=
---------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Error: couldn't locate device in libpci=20
structures


=A0


=A0


Case 2: VM was powered on 'after' PCI device (FPGA) was brough=
t=20
on-line


----------------------------------------------------------------------=
------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Enable MSI translation via per device option

register_real_device: Disable power management


pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_i=
omul: No=20
such file or directory: 0x1:0x0.0x0


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6000000)


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6100000)


pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1


register_real_device: Real physical device 01:00.0 registered=20
successfuly!


=A0


So=20
clearly, qemu-dm reported an error for case (1) and reported success for ca=
se=20
(2).


=A0


The=20
interesting thing is why did the Xen xm pci-attach command report success i=
n=20
both cases. Also, from Xen's perspective it appears that the afore-ment=
ioned PCI=20
device is assigned to the VM in both cases (as verified by using the xm com=
mands=20
to get the list of remaining assignable PCI devices and the list of PCI dev=
ices=20
attached to the VM).


=A0


Something seems wrong her=
e.


=A0


Any=20
thoughts?


=A0


-Anil
=



=A0








From: xen-users-bou=
nces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf =
Of Anil=20
Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com=
;=20
xen-users@list=
s.xen.org 





  

  

  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
=A0

  
Here is a more detailed description of my actua=
l usage=20
  scenario.

  
=A0

  
1) The FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) The VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
=A0=A0=A0 the VM is powered on.

  
3) After the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
=A0=A0=A0 This operation completes successfully (as=20
  reported by the appropriate xl command).

  
4) However, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) If I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
=A0

  
The troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
=A0

  
Thanks.

  
-Anil

  
=A0

  

  

  

  
From: xen-users-bo=
unces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf=
 Of cyberha=
wk001@gmail.com

Sent: Thursday, May 31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-use=
rs]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
=
Yes, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for=
 this=20
    one, the only time it doesn't work, is if the VM was powered-on pri=
or to the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
=
=A0

    
=
It somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
=
=A0

    
=
Thanks.

    
=
-Anil

    
=
=A0

    
=
=A0

    

    

    

    
From: theubaz@gmail.com [<=
a href=3D"mailto:theubaz@gmail.com" target=3D"_blank">mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com<=
br>Subject: Re:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <=
span dir=3D"ltr"><anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
=A0

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
=A0

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
=A0

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
=A0

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
=A0

      
Thanks for any help on this matter.

      
=A0

      
-Anil
<=
/blockquote>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users






_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9341111ef74c904c1ab8bd3--


--===============7823484309714471199==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7823484309714471199==--


From xen-users-bounces@lists.xen.org Mon Jun 04 20:42:03 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 20:42: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 1Sbe54-0006Xo-Gz; Mon, 04 Jun 2012 20:40:50 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbe52-0006Xc-CW
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:40:48 +0000
Received: from [85.158.143.35:28580] by server-3.bemta-4.messagelabs.com id
	AC/3E-29237-F4D1DCF4; Mon, 04 Jun 2012 20:40:47 +0000
X-Env-Sender: theubaz@gmail.com
X-Msg-Ref: server-14.tower-21.messagelabs.com!1338842438!18837449!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23416 invoked from network); 4 Jun 2012 20:40:42 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	4 Jun 2012 20:40:42 -0000
Received: by ggnp1 with SMTP id p1so3994777ggn.32
	for ; Mon, 04 Jun 2012 13:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=goEEUvjUZEr0Ko6fFvZ2mCxtBaHalafDZWMaFIDHtDc=;
	b=YF91NNScGl4R9lHxcdR1NAIJqq0aTysMdosnKdPQwIovleM35tYeQf16q6tOxLX1nK
	Hca7XORXYGbs7SPQtOpA3PGH6tJESeuHWsnAYT5AsfEj/4/KjvdnFiyo4P767rfX+ZPo
	/9HDUVrhKN+jCJ1xpRhlRW6iZM0noeIQx/M6RcPfKOiGlkO0KSLJfUwr9Yx3zEgwI5xn
	a7JoKfhuPNxBouOcxW1V8V5Gbz4K11NYpJNaLs0MscOfRvt1CE3c721rnmmremxJeA07
	7qBGTWwV958eri50d0xF1UHI4TRvHmWkqeFQlhllbD7hGvN+e3Wekws7pXKDKq3gSvV0
	zISA==
MIME-Version: 1.0
Received: by 10.50.222.170 with SMTP id qn10mr9522004igc.45.1338842438136;
	Mon, 04 Jun 2012 13:40:38 -0700 (PDT)
Received: by 10.64.25.162 with HTTP; Mon, 4 Jun 2012 13:40:38 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	<4FC7AEF5.3000306@gmail.com>
	
	
	
	
	
Date: Mon, 4 Jun 2012 16:40:38 -0400
X-Google-Sender-Auth: 4GtiDji1ZHZ53eTJsSZYXyCjWIk
Message-ID: 
From: John Sherwood 
To: Anil Rao 
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Hotplugging FPGA to running VM
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7823484309714471199=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7823484309714471199==
Content-Type: multipart/alternative; boundary=14dae9341111ef74c904c1ab8bd3

--14dae9341111ef74c904c1ab8bd3
Content-Type: text/plain; charset=ISO-8859-1

It's quite possible that the error simply isn't propagating up to Xen
during the pci-attach command (and that would be my guess, given that
qemu-dm is noticing the error and xen isn't).  It would appear though that
you've found "why" it's failing, although who knows long it might take to
figure out the actual error in register_real_device.  This is probably
where you'll need to contact the developer list to make any progress.

On Mon, Jun 4, 2012 at 4:34 PM, Anil Rao  wrote:

> **
> After poking around some more on my host, I noticed the following
> differences in the output of qemu-dm, which are shown below (extracted from
> /var/log/xen/qemu-dm-VMName.log).
>
>
>  Case 1: VM was powered on 'before' PCI device (FPGA) was brought on-line
>
> -------------------------------------------------------------------------------------------------------------
> dm-command: hot insert pass-through pci dev
> register_real_device: Assigning real physical device 01:00.0 ...
> register_real_device: Error: couldn't locate device in libpci structures
>
>
> Case 2: VM was powered on 'after' PCI device (FPGA) was brought on-line
>
> ----------------------------------------------------------------------------------------------------------
> dm-command: hot insert pass-through pci dev
> register_real_device: Assigning real physical device 01:00.0 ...
> register_real_device: Enable MSI translation via per device option
> register_real_device: Disable power management
> pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No
> such file or directory: 0x1:0x0.0x0
> pt_register_regions: IO region registered (size=0x00100000
> base_addr=0xc6000000)
> pt_register_regions: IO region registered (size=0x00100000
> base_addr=0xc6100000)
> pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=1
> register_real_device: Real physical device 01:00.0 registered successfuly!
>
> So clearly, qemu-dm reported an error for case (1) and reported success
> for case (2).
>
> The interesting thing is why did the Xen xm pci-attach command report
> success in both cases. Also, from Xen's perspective it appears that the
> afore-mentioned PCI device is assigned to the VM in both cases (as verified
> by using the xm commands to get the list of remaining assignable PCI
> devices and the list of PCI devices attached to the VM).
>
> Something seems wrong here.
>
> Any thoughts?
>
> -Anil
>
>  ------------------------------
>  *From:* xen-users-bounces@lists.xen.org [mailto:
> xen-users-bounces@lists.xen.org] *On Behalf Of *Anil Rao
> *Sent:* Thursday, May 31, 2012 11:25 AM
> *To:* cyberhawk001@gmail.com; xen-users@lists.xen.org
>
>>
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>>   This is a proprietary FPGA device. Each control blade in our router
>> chassis has one of these FPGAs and its primary function is to control
>> certain dedicated hardware components on the blade that are responsible for
>> establishing connectivity with the high-speed inter-blade fabric on the
>> router. I am sorry, but I cannot divulge additional details regarding the
>> FPGA.
>>
>> Here is a more detailed description of my actual usage scenario.
>>
>> 1) The FPGA image must be downloaded onto the device before it can be
>> enabled for use.
>> 2) The VM in question is responsible for performing step (1), which means
>> that the FPGA is not visible to Xen/Dom-0 when
>>     the VM is powered on.
>> 3) After the VM performs step (1), the FPGA is seen in Dom-0. I use Xen
>> pci-hotplug to assign the device to the VM.
>>     This operation completes successfully (as reported by the appropriate
>> xl command).
>> 4) However, the guest OS inside the VM cannot see the FPGA device after
>> step (3).
>> 5) If I shutdown the VM and re-start it, the guest OS inside the VM sees
>> the FPGA device (and everything then proceeds normally).
>>
>> The troublesome part here is that I need to shutdown and restart the VM.
>> I would like to avoid this and rely on Xen pci-hotplug to make the device
>> visible to the guest OS inside the VM.
>>
>> Thanks.
>> -Anil
>>
>>  ------------------------------
>>  *From:* xen-users-bounces@lists.xen.org [mailto:
>> xen-users-bounces@lists.xen.org] *On Behalf Of *cyberhawk001@gmail.com
>> *Sent:* Thursday, May 31, 2012 10:49 AM
>> *To:* xen-users@lists.xen.org
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>> Just out of curiosity, what kind of *FPGA device* is this? Is it an FPGA
>> development board or something already assembled and functioning that
>> contains an FPGA device(s)?
>>
>> Well, just being curious... :)
>>
>>
>>
>>  Yes, the guest OS has PCI hotplug support. I am able to hotplug a
>> variety of PCI devices to the VM. The only one that doesn't work is the
>> FPGA device. Even for this one, the only time it doesn't work, is if the VM
>> was powered-on prior to the FPGA device being brought on-line on the host.
>> If the FPGA was present before the VM was powered-on everything works as
>> expected.
>>
>> It somehow seems like new devices that are introduced in the host, after
>> a VM has been started on it, cannot be hotplugged into the VM.
>>
>> Thanks.
>> -Anil
>>
>>
>>  ------------------------------
>>  *From:* theubaz@gmail.com [mailto:theubaz@gmail.com ]
>> *On Behalf Of *John Sherwood
>> *Sent:* Wednesday, May 30, 2012 7:20 PM
>> *To:* Anil Rao
>> *Cc:* xen-users@lists.xensource.com
>> *Subject:* Re: [Xen-users] Hotplugging FPGA to running VM
>>
>> Are you sure the guest OS has PCI hotplug support?
>>
>> On Wed, May 30, 2012 at 10:14 PM, Anil Rao  wrote:
>>
>>>  Hi,
>>>
>>> I am trying to assign a FPGA (which is a PCI device) to a running VM.
>>> The interesting thing here is that the FPGA is not present when the VM was
>>> powered-on. I.e. sometime after the VM was started, the FPGA was brought
>>> on-line on the host by downloading its image to the device.
>>>
>>> So far my attempts at using Xen PCI-passthrough have not been
>>> successful. Although Xen reports that the pass-through operation was
>>> successful, which I have verified using the appropriate xl command, I am
>>> unable to see the FPGA from within the guest OS.
>>>
>>> I have tried both manual rescanning of the PCI bus inside the guest as
>>> well as making use of the pciehp driver. The only way I can (reliably) see
>>> the FPGA from within the guest, is to shutdown and restart the VM and then
>>> redo the hotplug operation. I want to avoid a VM reboot and was wondering
>>> if this is at all possible and if so what do I need to do to realize it.
>>>
>>> [The virtualization host is based on the default Xen setup that comes
>>> with SLES 11 SP2]
>>>
>>> Thanks for any help on this matter.
>>>
>>> -Anil
>>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
>

--14dae9341111ef74c904c1ab8bd3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It's quite possible that the error simply isn't propagating up to X=
en during the pci-attach command (and that would be my guess, given that qe=
mu-dm is noticing the error and xen isn't). =A0It would appear though t=
hat you've found "why" it's failing, although who knows l=
ong it might take to figure out the actual error in register_real_device. =
=A0This is probably where you'll need to contact the developer list to =
make any progress.


On Mon, Jun 4, 2012 at 4:34 PM, Anil Rao <anil.rao@ericsson.com> wrote:








After poking around some more on my host, I noticed the=20
following differences in the output of qemu-dm, which are shown below (extr=
acted=20
from /var/log/xen/qemu-dm-VMName.log).


=A0


=A0




Case 1: VM was powered on 'before' PCI device (FPGA) was broug=
ht=20
on-line


----------------------------------------------------------------------=
---------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Error: couldn't locate device in libpci=20
structures


=A0


=A0


Case 2: VM was powered on 'after' PCI device (FPGA) was brough=
t=20
on-line


----------------------------------------------------------------------=
------------------------------------


dm-command: hot insert pass-through pci dev


register_real_device: Assigning real physical device 01:00.0 ...


register_real_device: Enable MSI translation via per device option

register_real_device: Disable power management


pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_i=
omul: No=20
such file or directory: 0x1:0x0.0x0


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6000000)


pt_register_regions: IO region registered (size=3D0x00100000=20
base_addr=3D0xc6100000)


pt_msi_setup: msi mapped with pirq 84 pci_intx: intx=3D1


register_real_device: Real physical device 01:00.0 registered=20
successfuly!


=A0


So=20
clearly, qemu-dm reported an error for case (1) and reported success for ca=
se=20
(2).


=A0


The=20
interesting thing is why did the Xen xm pci-attach command report success i=
n=20
both cases. Also, from Xen's perspective it appears that the afore-ment=
ioned PCI=20
device is assigned to the VM in both cases (as verified by using the xm com=
mands=20
to get the list of remaining assignable PCI devices and the list of PCI dev=
ices=20
attached to the VM).


=A0


Something seems wrong her=
e.


=A0


Any=20
thoughts?


=A0


-Anil
=



=A0








From: xen-users-bou=
nces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf =
Of Anil=20
Rao
Sent: Thursday, May 31, 2012 11:25 AM
To: cyberhawk001@gmail.com=
;=20
xen-users@list=
s.xen.org 





  

  

  

  

Subject: Re: [Xen-users] Hotplugging FPGA to running=20
  VM


  

  

  

  
This is a=20
  proprietary FPGA device. Each control blade in our router chassis has one=
 of=20
  these FPGAs and its primary function is to control certain dedicated hard=
ware=20
  components on the blade that are responsible for establishing connectivit=
y=20
  with the high-speed inter-blade fabric on the router. I am sorry, but I c=
annot=20
  divulge additional details regarding the FPGA.

  
=A0

  
Here is a more detailed description of my actua=
l usage=20
  scenario.

  
=A0

  
1) The FPGA image=20
  must be downloaded onto the device before it can be enabled for=20
  use.

  
2) The VM in=20
  question is responsible for performing step (1), which means that the FPG=
A is=20
  not visible to Xen/Dom-0 when 

  
=A0=A0=A0 the VM is powered on.

  
3) After the VM=20
  performs step (1), the FPGA is seen in Dom-0. I use Xen pci-hotplug to as=
sign=20
  the device to the VM.

  
=A0=A0=A0 This operation completes successfully (as=20
  reported by the appropriate xl command).

  
4) However, the=20
  guest OS inside the VM cannot see the FPGA device after step=20
  (3).

  
5) If I shutdown=20
  the VM and re-start it, the guest OS inside the VM sees the FPGA device (=
and=20
  everything then proceeds normally).

  
=A0

  
The troublesome=20
  part here is that I need to shutdown and restart the VM. I would like to =
avoid=20
  this and rely on Xen pci-hotplug to make the device visible to the guest =
OS=20
  inside the VM.

  
=A0

  
Thanks.

  
-Anil

  
=A0

  

  

  

  
From: xen-users-bo=
unces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf=
 Of cyberha=
wk001@gmail.com

Sent: Thursday, May 31,=20
  2012 10:49 AM
To: xen-users@lists.xen.org
Subject: Re: [Xen-use=
rs]=20
  Hotplugging FPGA to running VM


  
Just out of curiosity, what kind of FPGA device is this=
? Is=20
  it an FPGA development board or something already assembled and functioni=
ng=20
  that contains an FPGA device(s)?

Well, just being curious...=20
  :)




  

    
=
Yes, the guest=20
    OS has PCI hotplug support. I am able to hotplug a variety of PCI devic=
es to=20
    the VM. The only one that doesn't work is the FPGA device. Even for=
 this=20
    one, the only time it doesn't work, is if the VM was powered-on pri=
or to the=20
    FPGA device being brought on-line on the host. If the FPGA was present=
=20
    before the VM was powered-on everything works as=20
    expected.

    
=
=A0

    
=
It somehow=20
    seems like new devices that are introduced in the host, after a VM has =
been=20
    started on it, cannot be hotplugged into the VM. 

    
=
=A0

    
=
Thanks.

    
=
-Anil

    
=
=A0

    
=
=A0

    

    

    

    
From: theubaz@gmail.com [<=
a href=3D"mailto:theubaz@gmail.com" target=3D"_blank">mailto:theubaz@gmail.=
com]=20
    On Behalf Of John Sherwood
Sent: Wednesday, May 30, 20=
12=20
    7:20 PM
To: Anil Rao
Cc: xen-users@lists.xensource.com<=
br>Subject: Re:=20
    [Xen-users] Hotplugging FPGA to running VM

Are you =
sure=20
    the guest OS has PCI hotplug support?=20
    


    
On Wed, May 30, 2012 at 10:14 PM, Anil Rao <=
span dir=3D"ltr"><anil.rao@ericsson.com> wrote:

    

      

      
Hi,

      
=A0

      
I am trying to assign a FPGA (which is a PCI device) to a runnin=
g VM.=20
      The interesting thing here is that the FPGA is not present when the V=
M was=20
      powered-on. I.e. sometime after the VM was started, the FPGA was brou=
ght=20
      on-line on the host by downloading its image to the device. 

      
=A0

      
So far my attempts at using Xen PCI-passthrough have not been=20
      successful. Although Xen reports that the pass-through operation was=
=20
      successful, which I have verified using the appropriate xl command, I=
 am=20
      unable to see the FPGA from within the guest OS.

      
=A0

      
I have tried both manual rescanning of the PCI bus inside the gu=
est=20
      as well as making use of the pciehp driver. The only way I can (relia=
bly)=20
      see the FPGA from within the guest, is to shutdown and restart the VM=
 and=20
      then redo the hotplug operation. I want to avoid a VM reboot and was=
=20
      wondering if this is at all possible and if so what do I need to do t=
o=20
      realize it.

      
=A0

      
[The virtualization host is based on the default Xen setup that =
comes=20
      with SLES 11 SP2]

      
=A0

      
Thanks for any help on this matter.

      
=A0

      
-Anil
<=
/blockquote>

_________________________________________=
______
Xen-users=20
  mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users






_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9341111ef74c904c1ab8bd3--


--===============7823484309714471199==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7823484309714471199==--


From xen-users-bounces@lists.xen.org Mon Jun 04 21:00:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 21:00: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 1SbeMy-000775-Ix; Mon, 04 Jun 2012 20:59:20 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbeMx-000770-7m
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:59:19 +0000
Received: from [85.158.143.35:45401] by server-1.bemta-4.messagelabs.com id
	C1/CF-10042-6A12DCF4; Mon, 04 Jun 2012 20:59:18 +0000
X-Env-Sender: smt@vgersoft.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1338843556!8352967!1
X-Originating-IP: [24.97.191.94]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2768 invoked from network); 4 Jun 2012 20:59:17 -0000
Received: from vgersoft.com (HELO vgersoft.com) (24.97.191.94)
	by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 20:59:17 -0000
Received: from helios.vgersoft.com (helios.vgersoft.com [192.168.1.108])
	by vgersoft.com (8.13.8/8.13.8) with ESMTP id q54KxE7g024150
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for ; Mon, 4 Jun 2012 16:59:16 -0400
Date: Mon, 4 Jun 2012 16:59:14 -0400 (EDT)
From: Steve Thompson 
To: xen-users@lists.xen.org
In-Reply-To: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
Message-ID: 
References: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-1463784447-1775579313-1338843556=:8986"
X-Virus-Scanned: clamav-milter 0.97.3 at firefly.vgersoft.com
X-Virus-Status: Clean
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1463784447-1775579313-1338843556=:8986
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Content-Transfer-Encoding: 8BIT

On Mon, 4 Jun 2012, baileyp@ct-itsolutions.com wrote:

>    So, in short -- I'm looking to replace about 30 WinXP desktops with VM's hosted by Xen, and I
> need to figure out how much memory and CPU power I'll need to make this feasible.

I am running 31 KVM VM's on a Dell R710 server with CentOS 5.8. The server 
has 8 cores at 3.06 GHz and 48 GB memory and has hyperthreading turned on 
(for 16 logical cores total). The server has a lot more CPU bandwidth than 
required _for my workload_, except possibly when all the VM's are booting 
at the same time. In normal production use, the CPU usage rarely goes over 
25%. But of course if your VM's are all running a CPU-intensive workload 
at the same time, you will want a core for each of them. If I did it 
again, I'd use just 4 cores and maybe 64 GB memory. But pay particular 
attention to your disk storage; I am using four 450 GB 15K RPM SAS disks 
in a RAID-5 configuration; this is _just_ enough I/O bandwidth. I used to 
run Xen on this server before I switched to KVM, and the CPU requirements 
were considerably higher then.

Steve
---1463784447-1775579313-1338843556=:8986
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
---1463784447-1775579313-1338843556=:8986--


From xen-users-bounces@lists.xen.org Mon Jun 04 21:00:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 04 Jun 2012 21:00: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 1SbeMy-000775-Ix; Mon, 04 Jun 2012 20:59:20 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbeMx-000770-7m
	for xen-users@lists.xen.org; Mon, 04 Jun 2012 20:59:19 +0000
Received: from [85.158.143.35:45401] by server-1.bemta-4.messagelabs.com id
	C1/CF-10042-6A12DCF4; Mon, 04 Jun 2012 20:59:18 +0000
X-Env-Sender: smt@vgersoft.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1338843556!8352967!1
X-Originating-IP: [24.97.191.94]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2768 invoked from network); 4 Jun 2012 20:59:17 -0000
Received: from vgersoft.com (HELO vgersoft.com) (24.97.191.94)
	by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 4 Jun 2012 20:59:17 -0000
Received: from helios.vgersoft.com (helios.vgersoft.com [192.168.1.108])
	by vgersoft.com (8.13.8/8.13.8) with ESMTP id q54KxE7g024150
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for ; Mon, 4 Jun 2012 16:59:16 -0400
Date: Mon, 4 Jun 2012 16:59:14 -0400 (EDT)
From: Steve Thompson 
To: xen-users@lists.xen.org
In-Reply-To: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
Message-ID: 
References: <20120604131049.e0b8cbd812270189f8876d5fa06e6a41.2c7c559a28.wbe@email18.secureserver.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-1463784447-1775579313-1338843556=:8986"
X-Virus-Scanned: clamav-milter 0.97.3 at firefly.vgersoft.com
X-Virus-Status: Clean
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1463784447-1775579313-1338843556=:8986
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Content-Transfer-Encoding: 8BIT

On Mon, 4 Jun 2012, baileyp@ct-itsolutions.com wrote:

>    So, in short -- I'm looking to replace about 30 WinXP desktops with VM's hosted by Xen, and I
> need to figure out how much memory and CPU power I'll need to make this feasible.

I am running 31 KVM VM's on a Dell R710 server with CentOS 5.8. The server 
has 8 cores at 3.06 GHz and 48 GB memory and has hyperthreading turned on 
(for 16 logical cores total). The server has a lot more CPU bandwidth than 
required _for my workload_, except possibly when all the VM's are booting 
at the same time. In normal production use, the CPU usage rarely goes over 
25%. But of course if your VM's are all running a CPU-intensive workload 
at the same time, you will want a core for each of them. If I did it 
again, I'd use just 4 cores and maybe 64 GB memory. But pay particular 
attention to your disk storage; I am using four 450 GB 15K RPM SAS disks 
in a RAID-5 configuration; this is _just_ enough I/O bandwidth. I used to 
run Xen on this server before I switched to KVM, and the CPU requirements 
were considerably higher then.

Steve
---1463784447-1775579313-1338843556=:8986
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
---1463784447-1775579313-1338843556=:8986--


From xen-users-bounces@lists.xen.org Tue Jun 05 00:11:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 00:11: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 1SbhLL-0000Ay-RF; Tue, 05 Jun 2012 00:09:51 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbhLK-0000Aq-2D
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 00:09:50 +0000
Received: from [85.158.143.35:19108] by server-1.bemta-4.messagelabs.com id
	96/68-10042-D4E4DCF4; Tue, 05 Jun 2012 00:09:49 +0000
X-Env-Sender: scr512@gmail.com
X-Msg-Ref: server-7.tower-21.messagelabs.com!1338854988!14798066!1
X-Originating-IP: [209.85.217.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32060 invoked from network); 5 Jun 2012 00:09:48 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 00:09:48 -0000
Received: by lbok6 with SMTP id k6so4366729lbo.32
	for ; Mon, 04 Jun 2012 17:09:47 -0700 (PDT)
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=Cw89q18KHZdXHL3KlCWMLws6RQ5ZvdxazGP8SQIU4Mw=;
	b=uebB0C+AEgsDYvJwRUfF3F6X840dPVomwDrIWh05JA45qnqraScUzSrGI0cFJpP5dV
	FQBXF72Ksl4Y7u2xLgv4LTeYgCq4unovomfJHQ9a1ZA/myDd2rULc0eUHx4c9F5zJ0Df
	rJu4OwY0vQE9VkBNykYzJLt0cuTyOfeUVRGfa2JEHSQTXyj75F6s+qAd6aQ1X9R8/El6
	UgleTRRkQosui4Ea68r4dYBysiwwUDreUgJVzhv24ZKPx2aUKgFPaPK9MelHBQhUfGPv
	LO3DigBCMcUUO5ClhLOPcAEDRG9J9J1rBV9mM8CioYxu7KnCZoDOL7YJlx5XoHocnPbL
	FKGA==
MIME-Version: 1.0
Received: by 10.152.103.11 with SMTP id fs11mr14564253lab.23.1338854635148;
	Mon, 04 Jun 2012 17:03:55 -0700 (PDT)
Received: by 10.112.99.106 with HTTP; Mon, 4 Jun 2012 17:03:55 -0700 (PDT)
Date: Mon, 4 Jun 2012 19:03:55 -0500
Message-ID: 
From: Jason Davis 
To: xen-users@lists.xen.org
Subject: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0143465006436867840=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0143465006436867840==
Content-Type: multipart/alternative; boundary=f46d040715c5ef141104c1ae62a1

--f46d040715c5ef141104c1ae62a1
Content-Type: text/plain; charset=ISO-8859-1

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to
XAPI calls being sent from a CloudStack management server. In the past, a
simple xe-toolstack-restart would do the trick but the script timed out
while restarting the XAPI daemon.

I found the process and first tried to use a simple kill command but the
process was in a "defunct" state. I tried a kill -9 but no joy.

I then found the xapi.pid and manually deleted it and then tried to run
xe-toolstack-restart. Unfortunately this did not work and ultimately I had
to reboot the cluster node.

So... any other ideas on killing a zombie XAPI process? I've like to avoid
rebooting a host :)

--f46d040715c5ef141104c1ae62a1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive t=
o XAPI calls being sent from a CloudStack management server. In the past, a=
 simple xe-toolstack-restart would do the trick but the script timed out wh=
ile restarting the XAPI daemon.



I found the process and first tried to use a simple kil=
l command but the process was in a "defunct" state. I tried a kil=
l -9 but no joy.=A0

I then found the xapi.pid and =
manually deleted it and then tried to run xe-toolstack-restart. Unfortunate=
ly this did not work and ultimately I had to reboot the cluster node.



So... any other ideas on killing a zombie XAPI process?=
 I've like to avoid rebooting a host :)


--f46d040715c5ef141104c1ae62a1--


--===============0143465006436867840==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0143465006436867840==--


From xen-users-bounces@lists.xen.org Tue Jun 05 00:11:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 00:11: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 1SbhLL-0000Ay-RF; Tue, 05 Jun 2012 00:09:51 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbhLK-0000Aq-2D
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 00:09:50 +0000
Received: from [85.158.143.35:19108] by server-1.bemta-4.messagelabs.com id
	96/68-10042-D4E4DCF4; Tue, 05 Jun 2012 00:09:49 +0000
X-Env-Sender: scr512@gmail.com
X-Msg-Ref: server-7.tower-21.messagelabs.com!1338854988!14798066!1
X-Originating-IP: [209.85.217.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32060 invoked from network); 5 Jun 2012 00:09:48 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 00:09:48 -0000
Received: by lbok6 with SMTP id k6so4366729lbo.32
	for ; Mon, 04 Jun 2012 17:09:47 -0700 (PDT)
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=Cw89q18KHZdXHL3KlCWMLws6RQ5ZvdxazGP8SQIU4Mw=;
	b=uebB0C+AEgsDYvJwRUfF3F6X840dPVomwDrIWh05JA45qnqraScUzSrGI0cFJpP5dV
	FQBXF72Ksl4Y7u2xLgv4LTeYgCq4unovomfJHQ9a1ZA/myDd2rULc0eUHx4c9F5zJ0Df
	rJu4OwY0vQE9VkBNykYzJLt0cuTyOfeUVRGfa2JEHSQTXyj75F6s+qAd6aQ1X9R8/El6
	UgleTRRkQosui4Ea68r4dYBysiwwUDreUgJVzhv24ZKPx2aUKgFPaPK9MelHBQhUfGPv
	LO3DigBCMcUUO5ClhLOPcAEDRG9J9J1rBV9mM8CioYxu7KnCZoDOL7YJlx5XoHocnPbL
	FKGA==
MIME-Version: 1.0
Received: by 10.152.103.11 with SMTP id fs11mr14564253lab.23.1338854635148;
	Mon, 04 Jun 2012 17:03:55 -0700 (PDT)
Received: by 10.112.99.106 with HTTP; Mon, 4 Jun 2012 17:03:55 -0700 (PDT)
Date: Mon, 4 Jun 2012 19:03:55 -0500
Message-ID: 
From: Jason Davis 
To: xen-users@lists.xen.org
Subject: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0143465006436867840=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0143465006436867840==
Content-Type: multipart/alternative; boundary=f46d040715c5ef141104c1ae62a1

--f46d040715c5ef141104c1ae62a1
Content-Type: text/plain; charset=ISO-8859-1

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to
XAPI calls being sent from a CloudStack management server. In the past, a
simple xe-toolstack-restart would do the trick but the script timed out
while restarting the XAPI daemon.

I found the process and first tried to use a simple kill command but the
process was in a "defunct" state. I tried a kill -9 but no joy.

I then found the xapi.pid and manually deleted it and then tried to run
xe-toolstack-restart. Unfortunately this did not work and ultimately I had
to reboot the cluster node.

So... any other ideas on killing a zombie XAPI process? I've like to avoid
rebooting a host :)

--f46d040715c5ef141104c1ae62a1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive t=
o XAPI calls being sent from a CloudStack management server. In the past, a=
 simple xe-toolstack-restart would do the trick but the script timed out wh=
ile restarting the XAPI daemon.



I found the process and first tried to use a simple kil=
l command but the process was in a "defunct" state. I tried a kil=
l -9 but no joy.=A0

I then found the xapi.pid and =
manually deleted it and then tried to run xe-toolstack-restart. Unfortunate=
ly this did not work and ultimately I had to reboot the cluster node.



So... any other ideas on killing a zombie XAPI process?=
 I've like to avoid rebooting a host :)


--f46d040715c5ef141104c1ae62a1--


--===============0143465006436867840==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0143465006436867840==--


From xen-users-bounces@lists.xen.org Tue Jun 05 03:36:53 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 03:36: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 1SbkXt-00059V-Tt; Tue, 05 Jun 2012 03:35:01 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbkXs-00059Q-Tp
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 03:35:01 +0000
Received: from [193.109.254.147:42857] by server-12.bemta-14.messagelabs.com
	id 90/FF-12998-46E7DCF4; Tue, 05 Jun 2012 03:35:00 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338867298!12758145!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32088 invoked from network); 5 Jun 2012 03:34:59 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-2.tower-27.messagelabs.com with SMTP;
	5 Jun 2012 03:34:59 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Mon, 4 Jun 2012 20:34:57 -0700
Received: from [192.168.3.101] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 4BFCE38A181
	for ; Mon,  4 Jun 2012 20:34:57 -0700 (PDT)
Message-ID: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Mon, 04 Jun 2012 20:35:09 -0700
From: Bill Beauchemin 
Organization: B2 Bass Adventures
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: bill@b2bassadventures.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello All,
I have been working with Linux since 1999. I am now trying to use 
virtualization useing Xen. I have a project where I have a Dell 2950 
server with two ethernet ports, and one 1TB drive.  I have 64 bit Debian 
Squeeze installed and running.  I need two instances  of vm's one being 
devel and the other is prod. each should connect through one of the eth 
ports. so devel could be eth0 and prod could be on eth1.

I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.

I have had so many issues trying to just get one vm running. make a cfg 
file i get errors about installation files or hotplug issues. currently 
my disk structure is
fdisk -l
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          37      297171   83  Linux
/dev/sda2              38        6117    48837600   83  Linux
/dev/sda3            6118        6604     3911827+  82  Linux swap / Solaris
/dev/sda4            6605      115416   874032390    5  Extended
/dev/sda5            6605       60098   429690523+  83  Linux
/dev/sda6           60099       60706     4883728+  82  Linux swap / Solaris
/dev/sda7           60707      114808   434574283+  83  Linux
/dev/sda8          114809      115416     4883728+  82  Linux swap / Solaris
sda1 is the boot
sda2 is swap for the base debian install and ada3 is swap for that
sda5 is for devel and sda6 is a swap for that
sda7 is for prod and sda8 is swap for that

My main question is if nthere is a tutorial that can help me with getting xen installed and configured correctly, configure a guest, install a guest, and boot the guest using the above configuration?

-- 
Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 03:36:53 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 03:36: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 1SbkXt-00059V-Tt; Tue, 05 Jun 2012 03:35:01 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbkXs-00059Q-Tp
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 03:35:01 +0000
Received: from [193.109.254.147:42857] by server-12.bemta-14.messagelabs.com
	id 90/FF-12998-46E7DCF4; Tue, 05 Jun 2012 03:35:00 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338867298!12758145!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32088 invoked from network); 5 Jun 2012 03:34:59 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-2.tower-27.messagelabs.com with SMTP;
	5 Jun 2012 03:34:59 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Mon, 4 Jun 2012 20:34:57 -0700
Received: from [192.168.3.101] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 4BFCE38A181
	for ; Mon,  4 Jun 2012 20:34:57 -0700 (PDT)
Message-ID: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Mon, 04 Jun 2012 20:35:09 -0700
From: Bill Beauchemin 
Organization: B2 Bass Adventures
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: bill@b2bassadventures.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello All,
I have been working with Linux since 1999. I am now trying to use 
virtualization useing Xen. I have a project where I have a Dell 2950 
server with two ethernet ports, and one 1TB drive.  I have 64 bit Debian 
Squeeze installed and running.  I need two instances  of vm's one being 
devel and the other is prod. each should connect through one of the eth 
ports. so devel could be eth0 and prod could be on eth1.

I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.

I have had so many issues trying to just get one vm running. make a cfg 
file i get errors about installation files or hotplug issues. currently 
my disk structure is
fdisk -l
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          37      297171   83  Linux
/dev/sda2              38        6117    48837600   83  Linux
/dev/sda3            6118        6604     3911827+  82  Linux swap / Solaris
/dev/sda4            6605      115416   874032390    5  Extended
/dev/sda5            6605       60098   429690523+  83  Linux
/dev/sda6           60099       60706     4883728+  82  Linux swap / Solaris
/dev/sda7           60707      114808   434574283+  83  Linux
/dev/sda8          114809      115416     4883728+  82  Linux swap / Solaris
sda1 is the boot
sda2 is swap for the base debian install and ada3 is swap for that
sda5 is for devel and sda6 is a swap for that
sda7 is for prod and sda8 is swap for that

My main question is if nthere is a tutorial that can help me with getting xen installed and configured correctly, configure a guest, install a guest, and boot the guest using the above configuration?

-- 
Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 03:52:48 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 03:52:48 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbknT-0005Sj-1R; Tue, 05 Jun 2012 03:51:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbknR-0005Sd-PZ
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 03:51:05 +0000
Received: from [193.109.254.147:34733] by server-7.bemta-14.messagelabs.com id
	07/5D-29165-9228DCF4; Tue, 05 Jun 2012 03:51:05 +0000
X-Env-Sender: shinepf@gmail.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338868263!12759388!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28187 invoked from network); 5 Jun 2012 03:51:04 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 03:51:04 -0000
Received: by obbwd20 with SMTP id wd20so10831285obb.32
	for ; Mon, 04 Jun 2012 20:51:03 -0700 (PDT)
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=QRNs7/WacabPHJUzoafmIU+vXVxr2/IBiqGoc/G/7CQ=;
	b=jCcR6qTvowQ27kpCeYYVDIG4/vtbvy9IzJvIZG7c2ZbT/JKtrn3HfhAeo0Xd2ShZgi
	+SvZl62pIR+vHwfYM83nDqdXhGV55pbCofg/WWwVXW0GA5+/kM2pESc0GI5jvwbucL+X
	YprCkl1Lto8ImkGj3iQDUkTYJzWUZ9vQkYBE/Kh8Xfd0CHsLvR2/wQXb9wUEt6L4sK0f
	9K8FlIiUO6dz3KFtxc/CWRhuzBwpxYe8cB9x+iCrICc6pGLM84b+inpkw/LK+PCznf3d
	3V10GgCsF5ZCvdQDfFrzcCWC4+gc7/5b55juM+4WtMerWJVvgQk1jWWEKc/i5CgmRuVC
	opVQ==
MIME-Version: 1.0
Received: by 10.182.139.2 with SMTP id qu2mr14206813obb.34.1338868262942; Mon,
	04 Jun 2012 20:51:02 -0700 (PDT)
Received: by 10.182.22.35 with HTTP; Mon, 4 Jun 2012 20:51:02 -0700 (PDT)
Date: Tue, 5 Jun 2012 13:51:02 +1000
Message-ID: 
From: pf shineyear 
To: xen-users@lists.xen.org
Subject: [Xen-users] need your help with xcp vlan
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2639501407822290011=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2639501407822290011==
Content-Type: multipart/alternative; boundary=e89a8f838db136b83b04c1b18f59

--e89a8f838db136b83b04c1b18f59
Content-Type: text/plain; charset=ISO-8859-1

hi all,

im peter, i found the post here
http://www.gossamer-threads.com/lists/xen/users/229738

i build a small test env, with 2 vm in 1 server with xcp 1.1.0

i use xe network-create and xe vlan-create to build the vlan for each vm.

then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list port i
can see all these info about fake-bridge and vlan tag is correct.

but when i start 2 vms, and try to ping the dom0 ip , i got fault, all
iptables in dom0 and vms are closed.

do you know what is the reson of this?

thanks for your help.

--e89a8f838db136b83b04c1b18f59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi all,=A0




i build a small test env, with 2 vm in 1 se=
rver with xcp 1.1.0

i use xe network-c=
reate and xe vlan-create to build the vlan for each vm.


then i got 2 bridge like xapi1 and xapi2, and in the o=
vs-vsctl list port i can see all these info about fake-bridge and vlan tag =
is correct.

but when i start 2 vms, an=
d try to ping the dom0 ip , i got fault, all iptables in dom0 and vms are c=
losed.



do you know what is the reson of this?

thanks for your help.


--e89a8f838db136b83b04c1b18f59--


--===============2639501407822290011==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2639501407822290011==--


From xen-users-bounces@lists.xen.org Tue Jun 05 03:52:48 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 03:52:48 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbknT-0005Sj-1R; Tue, 05 Jun 2012 03:51:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbknR-0005Sd-PZ
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 03:51:05 +0000
Received: from [193.109.254.147:34733] by server-7.bemta-14.messagelabs.com id
	07/5D-29165-9228DCF4; Tue, 05 Jun 2012 03:51:05 +0000
X-Env-Sender: shinepf@gmail.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1338868263!12759388!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28187 invoked from network); 5 Jun 2012 03:51:04 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 03:51:04 -0000
Received: by obbwd20 with SMTP id wd20so10831285obb.32
	for ; Mon, 04 Jun 2012 20:51:03 -0700 (PDT)
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=QRNs7/WacabPHJUzoafmIU+vXVxr2/IBiqGoc/G/7CQ=;
	b=jCcR6qTvowQ27kpCeYYVDIG4/vtbvy9IzJvIZG7c2ZbT/JKtrn3HfhAeo0Xd2ShZgi
	+SvZl62pIR+vHwfYM83nDqdXhGV55pbCofg/WWwVXW0GA5+/kM2pESc0GI5jvwbucL+X
	YprCkl1Lto8ImkGj3iQDUkTYJzWUZ9vQkYBE/Kh8Xfd0CHsLvR2/wQXb9wUEt6L4sK0f
	9K8FlIiUO6dz3KFtxc/CWRhuzBwpxYe8cB9x+iCrICc6pGLM84b+inpkw/LK+PCznf3d
	3V10GgCsF5ZCvdQDfFrzcCWC4+gc7/5b55juM+4WtMerWJVvgQk1jWWEKc/i5CgmRuVC
	opVQ==
MIME-Version: 1.0
Received: by 10.182.139.2 with SMTP id qu2mr14206813obb.34.1338868262942; Mon,
	04 Jun 2012 20:51:02 -0700 (PDT)
Received: by 10.182.22.35 with HTTP; Mon, 4 Jun 2012 20:51:02 -0700 (PDT)
Date: Tue, 5 Jun 2012 13:51:02 +1000
Message-ID: 
From: pf shineyear 
To: xen-users@lists.xen.org
Subject: [Xen-users] need your help with xcp vlan
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2639501407822290011=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2639501407822290011==
Content-Type: multipart/alternative; boundary=e89a8f838db136b83b04c1b18f59

--e89a8f838db136b83b04c1b18f59
Content-Type: text/plain; charset=ISO-8859-1

hi all,

im peter, i found the post here
http://www.gossamer-threads.com/lists/xen/users/229738

i build a small test env, with 2 vm in 1 server with xcp 1.1.0

i use xe network-create and xe vlan-create to build the vlan for each vm.

then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list port i
can see all these info about fake-bridge and vlan tag is correct.

but when i start 2 vms, and try to ping the dom0 ip , i got fault, all
iptables in dom0 and vms are closed.

do you know what is the reson of this?

thanks for your help.

--e89a8f838db136b83b04c1b18f59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi all,=A0




i build a small test env, with 2 vm in 1 se=
rver with xcp 1.1.0

i use xe network-c=
reate and xe vlan-create to build the vlan for each vm.


then i got 2 bridge like xapi1 and xapi2, and in the o=
vs-vsctl list port i can see all these info about fake-bridge and vlan tag =
is correct.

but when i start 2 vms, an=
d try to ping the dom0 ip , i got fault, all iptables in dom0 and vms are c=
losed.



do you know what is the reson of this?

thanks for your help.


--e89a8f838db136b83b04c1b18f59--


--===============2639501407822290011==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2639501407822290011==--


From xen-users-bounces@lists.xen.org Tue Jun 05 04:28:05 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 04:28: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 1SblLn-0005y0-8S; Tue, 05 Jun 2012 04:26:35 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SblLl-0005xv-2a
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 04:26:33 +0000
Received: from [85.158.143.99:57779] by server-2.bemta-4.messagelabs.com id
	12/CE-25135-87A8DCF4; Tue, 05 Jun 2012 04:26:32 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-16.tower-216.messagelabs.com!1338870389!20144541!1
X-Originating-IP: [209.85.214.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9107 invoked from network); 5 Jun 2012 04:26:30 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 04:26:30 -0000
Received: by obbwd20 with SMTP id wd20so10881297obb.32
	for ; Mon, 04 Jun 2012 21:26:28 -0700 (PDT)
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=WrDlqKh9mjQti4nKsIxbOzQwZCI0orC96Q2rlCubJn8=;
	b=afdwnca/SqHtCs4vIlPZFz6+voxEAokKcEjXlU/Lmr/9JivNQvP8GNKvK1kO2ajcyS
	59yBMSruulixzRHaG1vlJRqRyl9sU9/6qvsBuAtIGDo2rkpL/dkzDiSCUfpDkJr0gjtB
	HUPAGg1FUuQPrgun9d7467QkFn5A/hdrtyx7InPm1cXMm1SrN7SB5Kk175JmnCfC+Gbd
	jfvqNu2skcu4HOKjAh4QgGt+Y9qUgaO+jwup5TsqJ2BLtdMco7dodNDt9F4fu/sjgMv/
	qTyQCuZZL42yUt2LElUonXymxcmgl97WywRPhZkT7eul+32j9kaxqthjxgqMWuhja2Qx
	iMRA==
MIME-Version: 1.0
Received: by 10.60.3.194 with SMTP id e2mr9618459oee.1.1338870388784; Mon, 04
	Jun 2012 21:26:28 -0700 (PDT)
Received: by 10.76.122.134 with HTTP; Mon, 4 Jun 2012 21:26:28 -0700 (PDT)
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Tue, 5 Jun 2012 00:26:28 -0400
Message-ID: 
From: Casey DeLorme 
To: bill@b2bassadventures.com
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1713676349909264283=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1713676349909264283==
Content-Type: multipart/alternative; boundary=e89a8fb202a0ec7ff604c1b20dda

--e89a8fb202a0ec7ff604c1b20dda
Content-Type: text/plain; charset=ISO-8859-1

Hello Bill,

I don't know about an all-inclusive guide, but I recommend starting with
Xen Man Pages and the Xen Wiki.  The raw text files provide plenty of
configuration details, and you should be able to search for tutorials:
http://wiki.xen.org/wiki/Xen_Man_Pages

With regards to your objectives, networking should be handled by Dom0 via
the bridge-utils package and /etc/network/interfaces configuration.  Also
you may want to simplify your drive partitions since Xen virtual machines
will treat the partitions as drives, which results in a new partition table
and sub-partitioning each.


Here is a very basic example of the interfaces file you might want:

auto lo dev prod
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
iface prod inet manual
bridge_ports eth0
iface dev inet manual
bridge_ports eth1

Then you add a line like this to each virtual machine:
vif=['bridge=dev,model=e1000']

There is a lot of drive specifics you will want to read up on from the man
pages, and specific configuration details for linux/unix virtual machines.

If you continue to encounter errors, share them and your Xen version.


I am working on a Debian Wheezy x64 platform with Xen 4.2 a Windows,
PFSense, and Debian Wheezy HVM's, so my configuration objectives and syntax
may not be exactly what you need, but if you want an example:
http://pastebin.com/9E1g1BHf

Best of luck, and let me know if any of that was unclear.

~Casey


On Mon, Jun 4, 2012 at 11:35 PM, Bill Beauchemin
wrote:

> Hello All,
> I have been working with Linux since 1999. I am now trying to use
> virtualization useing Xen. I have a project where I have a Dell 2950 server
> with two ethernet ports, and one 1TB drive.  I have 64 bit Debian Squeeze
> installed and running.  I need two instances  of vm's one being devel and
> the other is prod. each should connect through one of the eth ports. so
> devel could be eth0 and prod could be on eth1.
>
> I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.
>
> I have had so many issues trying to just get one vm running. make a cfg
> file i get errors about installation files or hotplug issues. currently my
> disk structure is
> fdisk -l
>  Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1          37      297171   83  Linux
> /dev/sda2              38        6117    48837600   83  Linux
> /dev/sda3            6118        6604     3911827+  82  Linux swap /
> Solaris
> /dev/sda4            6605      115416   874032390    5  Extended
> /dev/sda5            6605       60098   429690523+  83  Linux
> /dev/sda6           60099       60706     4883728+  82  Linux swap /
> Solaris
> /dev/sda7           60707      114808   434574283+  83  Linux
> /dev/sda8          114809      115416     4883728+  82  Linux swap /
> Solaris
> sda1 is the boot
> sda2 is swap for the base debian install and ada3 is swap for that
> sda5 is for devel and sda6 is a swap for that
> sda7 is for prod and sda8 is swap for that
>
> My main question is if nthere is a tutorial that can help me with getting
> xen installed and configured correctly, configure a guest, install a guest,
> and boot the guest using the above configuration?
>
> --
> Bill Beauchemin
> B2 Bass Adventures
> Newark, Ca. 94560
> (510) 552-7571
>
>
> ______________________________**_________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8fb202a0ec7ff604c1b20dda
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Hello Bill,

I don't know about an al=
l-inclusive guide, but I recommend starting with Xen Man Pages and the Xen =
Wiki. =A0The raw text files provide plenty of configuration details, and yo=
u should be able to search for tutorials:



With regards to your objec=
tives, networking should be handled by Dom0 via the bridge-utils package an=
d /etc/network/interfaces configuration. =A0Also you may want to simplify y=
our drive partitions since Xen virtual machines will treat the partitions a=
s drives, which results in a new partition table and sub-partitioning each.=





Here is a very basic example of the inte=
rfaces file you might want:

auto lo dev prod
=

iface lo inet loopback
iface eth0 inet manual

iface eth1 inet manual
iface prod inet manual
	bridge_ports eth0
iface dev inet manual
	bridge_ports eth1



Then you add a line like this to each virtual machine:<=
/div>
vif=3D['bridge=3Ddev,model=3De1000']

=

There is a lot of drive specifics you will want to read up on from the=
 man pages, and specific configuration details for linux/unix virtual machi=
nes.



If you continue to encounter errors, share them and you=
r Xen version.


I am working on a De=
bian Wheezy x64 platform with Xen 4.2 a Windows, PFSense, and Debian Wheezy=
 HVM's, so my configuration objectives and syntax may not be exactly wh=
at you need, but if you want an example:





On Mon, Jun 4, 2012 at 11:3=
5 PM, Bill Beauchemin <bill@b2bassadventures.com> wr=
ote:


Hello All,

I have been working with Linux since 1999. I am now trying to use virtualiz=
ation useing Xen. I have a project where I have a Dell 2950 server with two=
 ethernet ports, and one 1TB drive. =A0I have 64 bit Debian Squeeze install=
ed and running. =A0I need two instances =A0of vm's one being devel and =
the other is prod. each should connect through one of the eth ports. so dev=
el could be eth0 and prod could be on eth1.




I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.



I have had so many issues trying to just get one vm running. make a cfg fil=
e i get errors about installation files or hotplug issues. currently my dis=
k structure is

fdisk -l

 =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Blocks =A0 =
Id =A0System

/dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A037 =A0 =A0 =A02971=
71 =A0 83 =A0Linux

/dev/sda2 =A0 =A0 =A0 =A0 =A0 =A0 =A038 =A0 =A0 =A0 =A06117 =A0 =A048837600=
 =A0 83 =A0Linux

/dev/sda3 =A0 =A0 =A0 =A0 =A0 =A06118 =A0 =A0 =A0 =A06604 =A0 =A0 3911827+ =
=A082 =A0Linux swap / Solaris

/dev/sda4 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0115416 =A0 874032390 =A0 =
=A05 =A0Extended

/dev/sda5 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0 60098 =A0 429690523+ =A08=
3 =A0Linux

/dev/sda6 =A0 =A0 =A0 =A0 =A0 60099 =A0 =A0 =A0 60706 =A0 =A0 4883728+ =A08=
2 =A0Linux swap / Solaris

/dev/sda7 =A0 =A0 =A0 =A0 =A0 60707 =A0 =A0 =A0114808 =A0 434574283+ =A083 =
=A0Linux

/dev/sda8 =A0 =A0 =A0 =A0 =A0114809 =A0 =A0 =A0115416 =A0 =A0 4883728+ =A08=
2 =A0Linux swap / Solaris

sda1 is the boot

sda2 is swap for the base debian install and ada3 is swap for that

sda5 is for devel and sda6 is a swap for that

sda7 is for prod and sda8 is swap for that



My main question is if nthere is a tutorial that can help me with getting x=
en installed and configured correctly, configure a guest, install a guest, =
and boot the guest using the above configuration?




-- 

Bill Beauchemin

B2 Bass Adventures

Newark, Ca. 94560

(510) 552-7571





_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users





--e89a8fb202a0ec7ff604c1b20dda--


--===============1713676349909264283==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1713676349909264283==--


From xen-users-bounces@lists.xen.org Tue Jun 05 04:28:05 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 04:28: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 1SblLn-0005y0-8S; Tue, 05 Jun 2012 04:26:35 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SblLl-0005xv-2a
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 04:26:33 +0000
Received: from [85.158.143.99:57779] by server-2.bemta-4.messagelabs.com id
	12/CE-25135-87A8DCF4; Tue, 05 Jun 2012 04:26:32 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-16.tower-216.messagelabs.com!1338870389!20144541!1
X-Originating-IP: [209.85.214.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9107 invoked from network); 5 Jun 2012 04:26:30 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 04:26:30 -0000
Received: by obbwd20 with SMTP id wd20so10881297obb.32
	for ; Mon, 04 Jun 2012 21:26:28 -0700 (PDT)
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=WrDlqKh9mjQti4nKsIxbOzQwZCI0orC96Q2rlCubJn8=;
	b=afdwnca/SqHtCs4vIlPZFz6+voxEAokKcEjXlU/Lmr/9JivNQvP8GNKvK1kO2ajcyS
	59yBMSruulixzRHaG1vlJRqRyl9sU9/6qvsBuAtIGDo2rkpL/dkzDiSCUfpDkJr0gjtB
	HUPAGg1FUuQPrgun9d7467QkFn5A/hdrtyx7InPm1cXMm1SrN7SB5Kk175JmnCfC+Gbd
	jfvqNu2skcu4HOKjAh4QgGt+Y9qUgaO+jwup5TsqJ2BLtdMco7dodNDt9F4fu/sjgMv/
	qTyQCuZZL42yUt2LElUonXymxcmgl97WywRPhZkT7eul+32j9kaxqthjxgqMWuhja2Qx
	iMRA==
MIME-Version: 1.0
Received: by 10.60.3.194 with SMTP id e2mr9618459oee.1.1338870388784; Mon, 04
	Jun 2012 21:26:28 -0700 (PDT)
Received: by 10.76.122.134 with HTTP; Mon, 4 Jun 2012 21:26:28 -0700 (PDT)
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Tue, 5 Jun 2012 00:26:28 -0400
Message-ID: 
From: Casey DeLorme 
To: bill@b2bassadventures.com
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1713676349909264283=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1713676349909264283==
Content-Type: multipart/alternative; boundary=e89a8fb202a0ec7ff604c1b20dda

--e89a8fb202a0ec7ff604c1b20dda
Content-Type: text/plain; charset=ISO-8859-1

Hello Bill,

I don't know about an all-inclusive guide, but I recommend starting with
Xen Man Pages and the Xen Wiki.  The raw text files provide plenty of
configuration details, and you should be able to search for tutorials:
http://wiki.xen.org/wiki/Xen_Man_Pages

With regards to your objectives, networking should be handled by Dom0 via
the bridge-utils package and /etc/network/interfaces configuration.  Also
you may want to simplify your drive partitions since Xen virtual machines
will treat the partitions as drives, which results in a new partition table
and sub-partitioning each.


Here is a very basic example of the interfaces file you might want:

auto lo dev prod
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
iface prod inet manual
bridge_ports eth0
iface dev inet manual
bridge_ports eth1

Then you add a line like this to each virtual machine:
vif=['bridge=dev,model=e1000']

There is a lot of drive specifics you will want to read up on from the man
pages, and specific configuration details for linux/unix virtual machines.

If you continue to encounter errors, share them and your Xen version.


I am working on a Debian Wheezy x64 platform with Xen 4.2 a Windows,
PFSense, and Debian Wheezy HVM's, so my configuration objectives and syntax
may not be exactly what you need, but if you want an example:
http://pastebin.com/9E1g1BHf

Best of luck, and let me know if any of that was unclear.

~Casey


On Mon, Jun 4, 2012 at 11:35 PM, Bill Beauchemin
wrote:

> Hello All,
> I have been working with Linux since 1999. I am now trying to use
> virtualization useing Xen. I have a project where I have a Dell 2950 server
> with two ethernet ports, and one 1TB drive.  I have 64 bit Debian Squeeze
> installed and running.  I need two instances  of vm's one being devel and
> the other is prod. each should connect through one of the eth ports. so
> devel could be eth0 and prod could be on eth1.
>
> I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.
>
> I have had so many issues trying to just get one vm running. make a cfg
> file i get errors about installation files or hotplug issues. currently my
> disk structure is
> fdisk -l
>  Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1          37      297171   83  Linux
> /dev/sda2              38        6117    48837600   83  Linux
> /dev/sda3            6118        6604     3911827+  82  Linux swap /
> Solaris
> /dev/sda4            6605      115416   874032390    5  Extended
> /dev/sda5            6605       60098   429690523+  83  Linux
> /dev/sda6           60099       60706     4883728+  82  Linux swap /
> Solaris
> /dev/sda7           60707      114808   434574283+  83  Linux
> /dev/sda8          114809      115416     4883728+  82  Linux swap /
> Solaris
> sda1 is the boot
> sda2 is swap for the base debian install and ada3 is swap for that
> sda5 is for devel and sda6 is a swap for that
> sda7 is for prod and sda8 is swap for that
>
> My main question is if nthere is a tutorial that can help me with getting
> xen installed and configured correctly, configure a guest, install a guest,
> and boot the guest using the above configuration?
>
> --
> Bill Beauchemin
> B2 Bass Adventures
> Newark, Ca. 94560
> (510) 552-7571
>
>
> ______________________________**_________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8fb202a0ec7ff604c1b20dda
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Hello Bill,

I don't know about an al=
l-inclusive guide, but I recommend starting with Xen Man Pages and the Xen =
Wiki. =A0The raw text files provide plenty of configuration details, and yo=
u should be able to search for tutorials:



With regards to your objec=
tives, networking should be handled by Dom0 via the bridge-utils package an=
d /etc/network/interfaces configuration. =A0Also you may want to simplify y=
our drive partitions since Xen virtual machines will treat the partitions a=
s drives, which results in a new partition table and sub-partitioning each.=





Here is a very basic example of the inte=
rfaces file you might want:

auto lo dev prod
=

iface lo inet loopback
iface eth0 inet manual

iface eth1 inet manual
iface prod inet manual
	bridge_ports eth0
iface dev inet manual
	bridge_ports eth1



Then you add a line like this to each virtual machine:<=
/div>
vif=3D['bridge=3Ddev,model=3De1000']

=

There is a lot of drive specifics you will want to read up on from the=
 man pages, and specific configuration details for linux/unix virtual machi=
nes.



If you continue to encounter errors, share them and you=
r Xen version.


I am working on a De=
bian Wheezy x64 platform with Xen 4.2 a Windows, PFSense, and Debian Wheezy=
 HVM's, so my configuration objectives and syntax may not be exactly wh=
at you need, but if you want an example:





On Mon, Jun 4, 2012 at 11:3=
5 PM, Bill Beauchemin <bill@b2bassadventures.com> wr=
ote:


Hello All,

I have been working with Linux since 1999. I am now trying to use virtualiz=
ation useing Xen. I have a project where I have a Dell 2950 server with two=
 ethernet ports, and one 1TB drive. =A0I have 64 bit Debian Squeeze install=
ed and running. =A0I need two instances =A0of vm's one being devel and =
the other is prod. each should connect through one of the eth ports. so dev=
el could be eth0 and prod could be on eth1.




I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.



I have had so many issues trying to just get one vm running. make a cfg fil=
e i get errors about installation files or hotplug issues. currently my dis=
k structure is

fdisk -l

 =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Blocks =A0 =
Id =A0System

/dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A037 =A0 =A0 =A02971=
71 =A0 83 =A0Linux

/dev/sda2 =A0 =A0 =A0 =A0 =A0 =A0 =A038 =A0 =A0 =A0 =A06117 =A0 =A048837600=
 =A0 83 =A0Linux

/dev/sda3 =A0 =A0 =A0 =A0 =A0 =A06118 =A0 =A0 =A0 =A06604 =A0 =A0 3911827+ =
=A082 =A0Linux swap / Solaris

/dev/sda4 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0115416 =A0 874032390 =A0 =
=A05 =A0Extended

/dev/sda5 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0 60098 =A0 429690523+ =A08=
3 =A0Linux

/dev/sda6 =A0 =A0 =A0 =A0 =A0 60099 =A0 =A0 =A0 60706 =A0 =A0 4883728+ =A08=
2 =A0Linux swap / Solaris

/dev/sda7 =A0 =A0 =A0 =A0 =A0 60707 =A0 =A0 =A0114808 =A0 434574283+ =A083 =
=A0Linux

/dev/sda8 =A0 =A0 =A0 =A0 =A0114809 =A0 =A0 =A0115416 =A0 =A0 4883728+ =A08=
2 =A0Linux swap / Solaris

sda1 is the boot

sda2 is swap for the base debian install and ada3 is swap for that

sda5 is for devel and sda6 is a swap for that

sda7 is for prod and sda8 is swap for that



My main question is if nthere is a tutorial that can help me with getting x=
en installed and configured correctly, configure a guest, install a guest, =
and boot the guest using the above configuration?




-- 

Bill Beauchemin

B2 Bass Adventures

Newark, Ca. 94560

(510) 552-7571





_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users





--e89a8fb202a0ec7ff604c1b20dda--


--===============1713676349909264283==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1713676349909264283==--


From xen-users-bounces@lists.xen.org Tue Jun 05 06:22:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 06:22: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 1Sbn8S-0006z9-OP; Tue, 05 Jun 2012 06:20:56 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbn8Q-0006z4-Iu
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 06:20:54 +0000
Received: from [85.158.143.99:8703] by server-2.bemta-4.messagelabs.com id
	DC/02-25135-545ADCF4; Tue, 05 Jun 2012 06:20:53 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-4.tower-216.messagelabs.com!1338877251!26072639!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27774 invoked from network); 5 Jun 2012 06:20:52 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 06:20:52 -0000
Received: by dadv2 with SMTP id v2so7395610dad.32
	for ; Mon, 04 Jun 2012 23:20:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding:x-gm-message-state;
	bh=QXcXi8WQAl1V647xVPPfYIwOalbrBHGgUFfN3gmpLMU=;
	b=X50+WvzRF8LIp71owdCdd2pW2oEpHoq059A5yFXxOquRqz3vxPIiTmfB4gGxPu7LhA
	Ji6QPl5QkU3HByjLFTETMeJKYBm1AfTiLusbLHRgL6KImxaOtIs8ytN1z7C3KJG2Rw5M
	WPuADPOIzxz6wsNttqzTtQdQXrHQVMYGzSRHEEaSiVFuNU4ecZZj3+GfdbTlMG8yXb9F
	fRAWu5DbhVrbrDKPsLTHV7UaaNS2Nn0zaXMA6pNvnKArfH/6oUs11CUs99FHxoPzRMHx
	KDOVakwoPEAkbWY3eU4dn9MQlXd2Y3LK2ouNtZd1DwUU6q+ZnVBEwsl1qmiPAza+4t6G
	ghNg==
MIME-Version: 1.0
Received: by 10.68.225.9 with SMTP id rg9mr45645319pbc.137.1338877250565; Mon,
	04 Jun 2012 23:20:50 -0700 (PDT)
Received: by 10.68.209.1 with HTTP; Mon, 4 Jun 2012 23:20:50 -0700 (PDT)
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Tue, 5 Jun 2012 13:20:50 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: bill@b2bassadventures.com
X-Gm-Message-State: ALoCoQnJEZ45uZC7VUMr3OBZkp0SYr20wK94/HMEuecks5hyC2MwG38o5ENraGynNxLFUSgeIp2x
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, Jun 5, 2012 at 10:35 AM, Bill Beauchemin
 wrote:
> Hello All,
> I have been working with Linux since 1999. I am now trying to use
> virtualization useing Xen. I have a project where I have a Dell 2950 serv=
er
> with two ethernet ports, and one 1TB drive. =A0I have 64 bit Debian Squee=
ze
> installed and running. =A0I need two instances =A0of vm's one being devel=
 and
> the other is prod. each should connect through one of the eth ports. so
> devel could be eth0 and prod could be on eth1.
>
> I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.

IIRC debian squeeze is not really the best platform to run xen for
beginners. If you're new to xen, I suggest the archaic-but-just-works
RHEL/Centos5.x.

Or even DON'T use xen, use whatever you're familiar with (e.g. kvm,
vmware, whatever).

And depending on what you run on it, using lxc on ubuntu precise might
actually be a better choice as it is VERY efficient, supported by the
distro, and it looks like:
- you'd be using linux guests anyway
- you'd have full control on all the guests

> I have had so many issues trying to just get one vm running. make a cfg f=
ile
> i get errors about installation files or hotplug issues.

Exactly :)

> currently my disk
> structure is
> fdisk -l
> =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Blocks =A0=
 Id =A0System
> /dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A037 =A0 =A0 =A029=
7171 =A0 83 =A0Linux
> /dev/sda2 =A0 =A0 =A0 =A0 =A0 =A0 =A038 =A0 =A0 =A0 =A06117 =A0 =A0488376=
00 =A0 83 =A0Linux
> /dev/sda3 =A0 =A0 =A0 =A0 =A0 =A06118 =A0 =A0 =A0 =A06604 =A0 =A0 3911827=
+ =A082 =A0Linux swap / Solaris
> /dev/sda4 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0115416 =A0 874032390 =A0=
 =A05 =A0Extended
> /dev/sda5 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0 60098 =A0 429690523+ =
=A083 =A0Linux
> /dev/sda6 =A0 =A0 =A0 =A0 =A0 60099 =A0 =A0 =A0 60706 =A0 =A0 4883728+ =
=A082 =A0Linux swap / Solaris
> /dev/sda7 =A0 =A0 =A0 =A0 =A0 60707 =A0 =A0 =A0114808 =A0 434574283+ =A08=
3 =A0Linux
> /dev/sda8 =A0 =A0 =A0 =A0 =A0114809 =A0 =A0 =A0115416 =A0 =A0 4883728+ =
=A082 =A0Linux swap / Solaris
> sda1 is the boot
> sda2 is swap for the base debian install and ada3 is swap for that
> sda5 is for devel and sda6 is a swap for that
> sda7 is for prod and sda8 is swap for that
>

FWIW, you didn't have to split it with partition (which will be hard
to modify later). Using LVM would probably be a better choice.


> My main question is if nthere is a tutorial that can help me with getting
> xen installed and configured correctly, configure a guest, install a gues=
t,
> and boot the guest using the above configuration?

As Casey mentioned, the wiki is a good place to start. IIRC there
isn't a specific tutorial for squeeze though, so if you DO get it
working, please update the documentation there :)

-- =

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 06:22:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 06:22: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 1Sbn8S-0006z9-OP; Tue, 05 Jun 2012 06:20:56 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbn8Q-0006z4-Iu
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 06:20:54 +0000
Received: from [85.158.143.99:8703] by server-2.bemta-4.messagelabs.com id
	DC/02-25135-545ADCF4; Tue, 05 Jun 2012 06:20:53 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-4.tower-216.messagelabs.com!1338877251!26072639!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27774 invoked from network); 5 Jun 2012 06:20:52 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 06:20:52 -0000
Received: by dadv2 with SMTP id v2so7395610dad.32
	for ; Mon, 04 Jun 2012 23:20:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding:x-gm-message-state;
	bh=QXcXi8WQAl1V647xVPPfYIwOalbrBHGgUFfN3gmpLMU=;
	b=X50+WvzRF8LIp71owdCdd2pW2oEpHoq059A5yFXxOquRqz3vxPIiTmfB4gGxPu7LhA
	Ji6QPl5QkU3HByjLFTETMeJKYBm1AfTiLusbLHRgL6KImxaOtIs8ytN1z7C3KJG2Rw5M
	WPuADPOIzxz6wsNttqzTtQdQXrHQVMYGzSRHEEaSiVFuNU4ecZZj3+GfdbTlMG8yXb9F
	fRAWu5DbhVrbrDKPsLTHV7UaaNS2Nn0zaXMA6pNvnKArfH/6oUs11CUs99FHxoPzRMHx
	KDOVakwoPEAkbWY3eU4dn9MQlXd2Y3LK2ouNtZd1DwUU6q+ZnVBEwsl1qmiPAza+4t6G
	ghNg==
MIME-Version: 1.0
Received: by 10.68.225.9 with SMTP id rg9mr45645319pbc.137.1338877250565; Mon,
	04 Jun 2012 23:20:50 -0700 (PDT)
Received: by 10.68.209.1 with HTTP; Mon, 4 Jun 2012 23:20:50 -0700 (PDT)
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Date: Tue, 5 Jun 2012 13:20:50 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: bill@b2bassadventures.com
X-Gm-Message-State: ALoCoQnJEZ45uZC7VUMr3OBZkp0SYr20wK94/HMEuecks5hyC2MwG38o5ENraGynNxLFUSgeIp2x
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, Jun 5, 2012 at 10:35 AM, Bill Beauchemin
 wrote:
> Hello All,
> I have been working with Linux since 1999. I am now trying to use
> virtualization useing Xen. I have a project where I have a Dell 2950 serv=
er
> with two ethernet ports, and one 1TB drive. =A0I have 64 bit Debian Squee=
ze
> installed and running. =A0I need two instances =A0of vm's one being devel=
 and
> the other is prod. each should connect through one of the eth ports. so
> devel could be eth0 and prod could be on eth1.
>
> I do have kernel vmlinuz-2.6.32-5-xen-amd64 running.

IIRC debian squeeze is not really the best platform to run xen for
beginners. If you're new to xen, I suggest the archaic-but-just-works
RHEL/Centos5.x.

Or even DON'T use xen, use whatever you're familiar with (e.g. kvm,
vmware, whatever).

And depending on what you run on it, using lxc on ubuntu precise might
actually be a better choice as it is VERY efficient, supported by the
distro, and it looks like:
- you'd be using linux guests anyway
- you'd have full control on all the guests

> I have had so many issues trying to just get one vm running. make a cfg f=
ile
> i get errors about installation files or hotplug issues.

Exactly :)

> currently my disk
> structure is
> fdisk -l
> =A0Device Boot =A0 =A0 =A0Start =A0 =A0 =A0 =A0 End =A0 =A0 =A0Blocks =A0=
 Id =A0System
> /dev/sda1 =A0 * =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A037 =A0 =A0 =A029=
7171 =A0 83 =A0Linux
> /dev/sda2 =A0 =A0 =A0 =A0 =A0 =A0 =A038 =A0 =A0 =A0 =A06117 =A0 =A0488376=
00 =A0 83 =A0Linux
> /dev/sda3 =A0 =A0 =A0 =A0 =A0 =A06118 =A0 =A0 =A0 =A06604 =A0 =A0 3911827=
+ =A082 =A0Linux swap / Solaris
> /dev/sda4 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0115416 =A0 874032390 =A0=
 =A05 =A0Extended
> /dev/sda5 =A0 =A0 =A0 =A0 =A0 =A06605 =A0 =A0 =A0 60098 =A0 429690523+ =
=A083 =A0Linux
> /dev/sda6 =A0 =A0 =A0 =A0 =A0 60099 =A0 =A0 =A0 60706 =A0 =A0 4883728+ =
=A082 =A0Linux swap / Solaris
> /dev/sda7 =A0 =A0 =A0 =A0 =A0 60707 =A0 =A0 =A0114808 =A0 434574283+ =A08=
3 =A0Linux
> /dev/sda8 =A0 =A0 =A0 =A0 =A0114809 =A0 =A0 =A0115416 =A0 =A0 4883728+ =
=A082 =A0Linux swap / Solaris
> sda1 is the boot
> sda2 is swap for the base debian install and ada3 is swap for that
> sda5 is for devel and sda6 is a swap for that
> sda7 is for prod and sda8 is swap for that
>

FWIW, you didn't have to split it with partition (which will be hard
to modify later). Using LVM would probably be a better choice.


> My main question is if nthere is a tutorial that can help me with getting
> xen installed and configured correctly, configure a guest, install a gues=
t,
> and boot the guest using the above configuration?

As Casey mentioned, the wiki is a good place to start. IIRC there
isn't a specific tutorial for squeeze though, so if you DO get it
working, please update the documentation there :)

-- =

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 12:22:21 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 12:22:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbskT-0001TI-Hs; Tue, 05 Jun 2012 12:20:33 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbskR-0001TD-0b
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:20:31 +0000
Received: from [85.158.138.51:2823] by server-10.bemta-3.messagelabs.com id
	5D/3A-06494-E89FDCF4; Tue, 05 Jun 2012 12:20:30 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-14.tower-174.messagelabs.com!1338898827!24521426!1
X-Originating-IP: [209.85.160.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2328 invoked from network); 5 Jun 2012 12:20:28 -0000
Received: from mail-gh0-f173.google.com (HELO mail-gh0-f173.google.com)
	(209.85.160.173)
	by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 12:20:28 -0000
Received: by ghrr14 with SMTP id r14so4337710ghr.32
	for ; Tue, 05 Jun 2012 05:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=Ci+y+OpqZw4dq3QE4wVxWKYXxlcIILqfy7gO1JfpF5U=;
	b=wZrEChY/uONQXeUhHvcf0q+GgiJjlnl5sXk27PCnmKDQGglyqtI3ylr6kKTjcFRBYn
	yHNNFs6yyCO6WD5rFeZOP61E0/ZNZh1vKUVK5y3CLUGuS8s5lQpAxfiiI+Ob343e77GS
	MHqj2Rk/lXzF1CPVgSlUTaPSxA+R6ivV0XPctYHiqHXTXo7RNPhkVrgy3z0R4Q7BD53i
	QVYXvL6AVKWBlEnpv3ZmgXvZ+hWDUTaah/DK0ivbBtNSRdf82IUbEfmVPVy/ibT2YcGY
	X4dopx+fA/r+TzROSm/qg/Ngz1M5Wxth2qteSxL6HtsVC7KEXDBoHWORxgl8v4zVk661
	AUwA==
Received: by 10.101.3.34 with SMTP id f34mr4967174ani.3.1338898826892;
	Tue, 05 Jun 2012 05:20:26 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id c12sm1879155ann.15.2012.06.05.05.20.25
	(version=TLSv1/SSLv3 cipher=OTHER);
	Tue, 05 Jun 2012 05:20:26 -0700 (PDT)
Message-ID: <4FCDF96F.2050007@gmail.com>
Date: Tue, 05 Jun 2012 08:19:59 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

aHVtbSwgd2VsbCB0aGF0IHN1Y2tzLiBJIGtub3cgY29tcGlsaW5nIGNoYW5nZXNldCAyNTM5MiB3
b3JrcyBmb3IgbWUsIAp3aXRoIHRoZSBwYWNrYWdlcyBhbmQgaW5zdHJ1Y3Rpb25zIGkgZGVzY3Jp
YmVkLCBpIGhhdmUgY29tcGlsZWQgaXQgCnNldmVyYWwgdGltZXMgbm93LiBJIGtub3cgdGhlIG1h
aW4gcmVhc29uIHdoeSB0aGUgbGF0ZXIgY2hhbmdlc3RzIHdvbid0IApjb21waWxlIGlzIGJlY2F1
c2Ugb2YgdGhlIGRpZmZlcmVudCBHQ0MgdmVyc2lvbiBzZWVtIHRvIGRvIGRpZmZlcmVudCAKZW5v
dWdoIHRvIGZhaWwsIFNPIG1heWJlIFVidW50dSBoYXMgYSBkaWZmZXJlbnQgc3Vic2V0IG9mIEdD
Qy4gSSBoYXZlIG5vIAppZGVhLgoKV2VsbCwgaWYgaXQgd2FzIG5vIHRyb3VibGUgZm9yIHlvdSwg
bWF5YmUgdHJ5IHRvIGluc3RhbGwgRGViaWFuIFdoZWV6eSAKYW5kIHRyeSB0byBjb21waWxlIGFn
YWluLiBPdGhlcndpc2UgaSBjb3VsZCBhbHdheXMgc2VuZCB5b3UgdGhlIFhlbiA0LjIgCnJldi0y
NTM5MiBjb21waWxlZCBERUIgcGFja2FnZSBhbmQgeW91IGNhbiBqdXN0IGluc3RhbGwgdGhhdCwg
QlVUIHRoYXQgCndvdWxkbid0IHNvbHZlIHlvdXIgcHJvYmxlbSBpZiB5b3Ugd2FudGVkIHRvIGNv
bXBpbGUgaXQgbGF0ZXIgb24uCgoKPiBIbW0gc2FtZSBlcnJvcjoKPgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhh
bmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKPiAvcm9v
dC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3Zp
cnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNs
YXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhn
LXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
NzA6NTg6Cj4gbm90ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25s
eSBvbmNlIGZvciBlYWNoIGZ1bmN0aW9uCj4gaXQgYXBwZWFycyBpbgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhh
bmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xzdGF0w6I6Cj4gL3Jvb3QveGVuLXVuc3Rh
YmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFu
ZGxlLmM6ODc6MzQ6Cj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0
IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0
aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1Mzky
L3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6Cj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4t
ZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xp
bmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMzc6NDU6Cj4gZXJyb3I6IMOiQVRfRU1QVFlf
UEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2Nob3duw6I6Cj4gL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8t
OXAtaGFuZGxlLmM6MzczOjU4Ogo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVk
IChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5vXSBFcnJvciAxCj4gbWFrZVs0XTogKioqIFdhaXRpbmcgZm9yIHVuZmluaXNo
ZWQgam9icy4uLi4KPiAgICBDQyAgICBobXAubwo+ICAgIENDICAgIGxpYmRpcy9pMzg2LWRpcy5v
Cj4gICAgTElOSyAgcWVtdS1nYQo+ICAgIExJTksgIHFlbXUtbmJkCj4gICAgTElOSyAgcWVtdS1p
bWcKPiAgICBMSU5LICBxZW11LWlvCj4gbWFrZVszXTogKioqIFtzdWJkaXItbGliaHc2NF0gRXJy
b3IgMgo+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0b3J5Cj4gYC9yb290L3hlbi11bnN0YWJsZS5o
Zy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyLXJlbW90ZScKPiBtYWtlWzJdOiAqKiogW3N1
YmRpci1pbnN0YWxsLXFlbXUteGVuLWRpcl0gRXJyb3IgMgo+IG1ha2VbMl06IExlYXZpbmcgZGly
ZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzJwo+IG1ha2VbMV06
ICoqKiBbc3ViZGlycy1pbnN0YWxsXSBFcnJvciAyCj4gbWFrZVsxXTogTGVhdmluZyBkaXJlY3Rv
cnkgYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMnCj4gbWFrZTogKioqIFtp
bnN0YWxsLXRvb2xzXSBFcnJvciAyCj4KPiBJIGhhZCBtb3N0IG9mIHRoZSBwYWNrYWdzLCBJIHJh
biAiYXB0LWdldCBidWlsZC1kZXAgeGVuIiBmcm9tOgo+IGh0dHA6Ly93aWtpLnhlbi5vcmcvd2lr
aS9Db21waWxpbmdfWGVuX0Zyb21fU291cmNlCj4KPiBCdXQgaXQgc3RpbGwgZXJyb3JzIG9uIHRo
ZSB2aXJ0aW8gZmlsZS4gSSBoYWQgYWxzbyByZWFkIHRoYXQgdGhlc2UKPiBlcnJvcnMgaGFkIHRv
IGRpZmZlcmVudCB3aXRoIGRpZmZlcmVudCBsaWJyYXJ5L2djYyB2ZXJzaW9ucy4gTWF5YmUKPiB3
aGVlenkganVzdCBoYXMgbmV3ZXIvZGlmZmVyZW50IHZlcnNpb25zIG9mIHRob3NlIGJpbmFyaWVz
L2xpYnM/Cj4KPiAtLVdpbGwKPgo+Cj4+Pj4gICAwNi8wNC8xMiAxMTo0NSBBTT4+Pgo+IFdFTEws
IGFjdHVhbGx5IE5PIG5lZWQgdG8gaW5zdGFsbCBXaGVlenkuIEkgYW0gdmVyeSBzdXJlIHlvdSBj
YW4gZ2V0IGl0Cj4gd29ya2luZyBqdXN0IGFzIGVhc2lseSB3aXRoIFVidW50dS4KPgo+IFRoZSBv
dGhlciB0aGluZyBpIGZvcmdvdCB0byBtZW50aW9uIGlzIHlvdSBoYXZlIHRvIGhhdmUgYWxsIG9m
IHRoZQo+IHJlcXVpcmVkIHBhY2thZ2VzIGluc3RhbGxlZCBiZWZvcmUgeW91IGNhbiBjb21waWxl
IFhlbi4gSSB0aGluayB5b3UgYXJlCj4ganVzdCBtaXNzaW5nIGEgYnVuY2ggb2YgZGVwZW5kZW50
IHBhY2thZ2VzLiBUaGUgcGFja2FnZXMgaSB1c2UgYW5kIGhhdmUKPiBpbnN0YWxsZWQgYXJlIGFz
IGZvbGxvd3M6Cj4KPiBzdWRvIGFwdC1nZXQgaW5zdGFsbCB3Z2V0IHRhciBiemlwMiBidWlsZC1l
c3NlbnRpYWwgbGlibmN1cnNlczUtZGV2Cj4ga2VybmVsLXBhY2thZ2UgZmFrZXJvb3QgYmNjIGdj
YyBzc2ggYnJpZGdlLXV0aWxzIHB5dGhvbi1kZXYgdXVpZC1kZXYKPiBsaWJnbGliMi4wLWRldiBs
aWJ5YWpsLWRldiBsaWJhaW8tZGV2IGdjYy1tdWx0aWxpYiBpYXNsIGxpYnBjaS1kZXYgZmxleAo+
IGJpc29uIHF0NC1kZXYtdG9vbHMgcGF0Y2ggb2NhbWwtZmluZGxpYiBsaWJzZGwxLjItZGV2Cj4K
PiBHcmFudGVkIHNvbWUgb2YgdGhlIGFib3ZlIHBhY2thZ2VzIGFyZSBtb3JlIGltcG9ydGFudCBm
b3IgY29tcGlsaW5nIHRoZQo+IGtlcm5lbC4KPgo+IFNPLCBhcyBsb25nIGFzIHlvdSBoYXZlIGFs
bCByZXF1aXJlZCBwYWNrYWdlcyBhbmQgZm9sbG93IHRoZQo+IGluc3RydWN0aW9ucyBiZWZvcmUg
YWJvdXQgZ2V0dGluZyBhbmQgY29tcGlsaW5nIFhlbiA0LjIgcmV2aXNpb24gMjUzOTIsCj4gaXQg
c2hvdWxkIGJlIGZpbmUsIG5vIG1hdHRlciBpZiB5b3UgYXJlIHVzaW5nIERlYmlhbiBvciBVYnVu
dHUuIFVidW50dQo+IGhvd2V2ZXIgIm1pZ2h0IiBuZWVkIG1vcmUgcGFja2FnZXMsIG5vdCBzdXJl
LCAgaSBoYXZlIG5vdCBjb21waWxlZCBYZW4KPiB1bmRlciBVYnVudHUgeWV0Lgo+Cj4KPgo+IE9u
IDYvNC8yMDEyIDEyOjQzIFBNLCBXaWxsIE1jRGVybW90dCB3cm90ZToKPj4gRGFybiwgbWFkZSBp
dCBmYXJ0aGVyIGJ1dCBub3cgSSBnZXQgdGhpczoKPj4KPj4gQ0MgICAgbGliaHc2NC85cGZzL3Zp
cnRpby05cC1zeW50aC5vCj4+ICAgICBDQyAgICBsaWJodzY0LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5vCj4+ICAgICBDQyAgICBxZW11LWNoYXIubwo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+
PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6Cj4+Cj4gL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8t
OXAtaGFuZGxlLmM6NzA6NTg6Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVk
IChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3
MDo1ODoKPj4gbm90ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25s
eSBvbmNlIGZvciBlYWNoCj4gZnVuY3Rpb24KPj4gaXQgYXBwZWFycyBpbgo+Pgo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pgo+IC9yb290
L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNs
YXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxl
LmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6Cj4+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPj4KPiAvcm9vdC94ZW4tdW5z
dGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1o
YW5kbGUuYzozMTQ6NjI6Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChm
aXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2
LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4g
SW4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMz
Nzo0NToKPj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9jaG93bsOiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAx
Cj4+IG1ha2VbNF06ICoqKiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+ICAgICBD
QyAgICBzYXZldm0ubwo+PiAgICAgQ0MgICAgbXNtb3VzZS5vCj4+ICAgICBDQyAgICBwczIubwo+
PiBtYWtlWzNdOiAqKiogW3N1YmRpci1saWJodzY0XSBFcnJvciAyCj4+IG1ha2VbM106ICoqKiBX
YWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0
b3J5Cj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci1yZW1vdGUnCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBF
cnJvciAyCj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUu
aGctcmV2LTI1MzkyL3Rvb2xzJwo+PiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJy
b3IgMgo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhn
LXJldi0yNTM5Mi90b29scycKPj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4+
Cj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNoIGZvciB5b3VyIGNsZWFy
IGluc3RydWN0aW9ucyEgSQo+PiB3aWxsIGluc3RhbGwgd2hlZXp5IHRvbmlnaHQgYW5kIHRyeSB0
aGUgYnVpbGQgYWdhaW4uCj4+Cj4+IC0tV2lsbAo+Pgo+Pj4+PiAgICAwNi8wNC8xMiA0OjU2IEFN
Pj4+Cj4+IE9uIDYvNC8yMDEyIDI6NTggQU0sIFdpbGwgTWNEZXJtb3R0IHdyb3RlOgo+Pj4gSSdt
IG5vdCBzdXJlIHdoYXQgdmVyc2lvbiAoaG93IGRvIEkgY2hlY2s/KSBidXQgSSBqdXN0IGNsb25l
ZCBmcm9tCj4+IHRoYXQKPj4+IFVSTCB0b2RheS4KPj4+Cj4+PiAtLVdpbGwKPj4gV2VsbCB0aGFu
IHlvdSBwcm9iYWJseSBhbHJlYWR5IGhhdmUgdGhlIGxhdGVzdCByZXZpc2lvbi4gWW91IGNhbiBh
bHNvCj4+IGNoZWNrIHdoYXQgcmV2aXNpb24geW91ciBsb2NhbGx5IGNsb25lZCByZXBvc2l0b3J5
IGlzIGF0IGJ5IGdvaW5nIHRvCj4gdGhlCj4+IGZvbGRlciBhbmQgcnVubmluZzoKPj4KPj4gKmNk
ICAuLi94ZW4tdW5zdGFibGUuaGcKPj4gaGcgc3VtbWFyeQo+PiAqCj4+IEFuZCB0aGF0IHdpbGwg
c2hvdyB5b3UgYSBzdW1tYXJ5IG9mIHRoZSBsb2NhbCBtZXJjdXJpYWwgY2xvbmUgYW5kIHNob3cK
Pj4gdGhlIGxhdGVzdCByZXZpc2lvbnMgdGhhdCB3YXMgY2xvbmVkLgo+Pgo+PiBTTywgYW55aG93
LCBjb21waWxpbmcgdGhlIFhlbiA0LjItdW5zdGFibGUgZnJvbSB0aGUgbWVyY3VyaWFsIGhhcyBu
b3QKPj4gYmVlbiB3b3JraW5nIHZlcnkgd2VsbCBmb3IgYSBmZXcgd2Vla3Mgbm93LiBJIGhhdmUg
YXNrZWQgdGhlIFhlbi1kZXZlbAo+PiBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhl
cmUgYXJlIGlzc3VlcyBhbmQgcHJvYmxlbXMgd2l0aAo+PiBkaWZmZXJlbnQgR0NDIGNvbXBpbGVy
cyBBTkQgdGhlIFhlbi1kZXZlbCB0ZWFtIGtub3dzIGFsbCB0aGF0IGFuZCBhcmUKPj4gd29ya2lu
ZyBvbiBmaXhpbmcgdGhhdC4KPj4KPj4gRm9yIG5vdywgdGhlIExBU1QgcmV2aXNpb24gaSB3YXMg
YWJsZSB0byBjb21waWxlIGFuZCBnZXQgcnVubmluZyB3YXMKPj4gKiJyZXZpc2lvbiAyNTM5Mioi
LCBidXQgZXZlbiB0aGF0IHdhcyBwb3NzaWJseSBPTkxZIGlmIHlvdSByZW1vdmUgb25lCj4+IHBh
dGNoLiBZb3UgY2FuIHRyeSB0byBkb3dubG9hZCBhbmQgY29tcGlsZSBUSEFUIHZlcnNpb24gYnkg
cnVubmluZyB0aGUKPj4gZm9sbG93aW5nIGNvbW1hbmRzOgo+Pgo+PiBfKkNsb25pbmcgWGVuOipf
Cj4+ICotIGNkIC9zb21lL2RpcmVjdG9yeS9pbi9ob21lCj4+IC0gcmV2PTI1MzkyJiYgICBoZyBj
bG9uZSAtciAkcmV2Cj4+IGh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvaGcveGVuLXVuc3RhYmxlLmhn
LyB4ZW4tdW5zdGFibGUuaGctcmV2LSR7cmV2fQo+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIKPj4gLSBoZyBiYWNrb3V0IC1yIDI1MzY0Kgo+Pgo+PiBUaGlzIHdpbGwgY2xvbmUgdGhl
IHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbgo+PiA0LjItdW5zdGFi
bGUgcmV2aXNpb24gMjUzOTIgaW50byB0aGUgZm9sZGVyCj4+ICIqeGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5MioiLiBSdW5uaW5nIHRoZSBjb21tYW5kICIqaGcgYmFja291ciAtcgo+PiAyNTM2NCoi
IHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4gSXQgc2VlbXMgdGhh
dAo+PiB3aXRob3V0IHRoYXQsIGV2ZW4gdGhhdCByZXZpc2lvbiB3b250IGNvbXBpbGUuCj4+Cj4+
IF8qQ29tcGlsaW5nIFhlbjoqXwo+PiBUaGFuIGp1c3Qgc2ltcGx5IHJ1biB0aGVzZSBjb21tYW5k
cyB0byBjb21waWxlIFhlbi4KPj4KPj4gKi0gY2QgeGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5MioK
Pj4gKi0gLi9jb25maWd1cmUKPj4gLSBzdWRvIG1ha2UgLWo1IHhlbiYmICAgc3VkbyBtYWtlIFRo
ZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdAo+IHN0cmluZ3MgdG9nZXRoZXIgdGhlIDQgY29t
cGlsaW5nIGNvbW1hbmRzCj4+IHRvIHJ1biBhbmQgd2lsbCBleGVjdXRlIG9uZSBhZnRlciB0aGUg
b3RoZXIgU08geW91IGRvbid0IGhhdmUgdG8KPj4gbWFudWFsbHkgcnVuIGVhY2ggYW5kIGV2ZXJ5
IG9uZS4gQWxzbywgSW4gdGhlIGFib3ZlICIqbWFrZSoiIGNvbW1hbmRzLAo+PiB1c2luZyB0aGUg
IiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtlIHRlbGxzIHRoZSBjb21waWxlIHRvIHVzZSBt
b3JlCj4+IHRoYW4gb25lIGNvcmUgdG8gY29tcGlsZSB3aXRoLiBJdCBzcGVlZHMgdXAgdGhlIGNv
bXBpbGk+ICBoYXZlIGEgbXVsdGktY29yZSBDUFUuIFNPIGluIG15IGNhc2UsIGkgaGF2ZSBhIFF1
YWQgQ29yZSBDUFUsIHNvIHRoYXQKPj4gY29tbWFuZCBvcHRpb24gaXMgIiotajEgKyBudW1iZXIg
b2YgQ1BVIGNvcmVzKiIuIFlvdSBjYW4gbW9kaWZ5IG9yCj4+IHJlbW92ZSB0aGF0IGFzIHlvdSB3
aXNoLgo+Pgo+PiBUaGUgYWJvdmUgd2lsbCBhbHNvIGNyZWF0ZSBmb3IgeW91IGEgbmljZSBERUIg
cGFja2FnZSBhZnRlciBhbGwgdGhlCj4+IGNvbXBpbGluZyBpcyBkb25lLCBpZiB5b3UgZG8gbm90
IHdhbnQgdG8gY3JlYXRlIGEgREVCIHBhY2thZ2UgYXQgdGhlCj4gZW5kCj4+IG9mIGl0IGFsbCwg
dGhhbiBqdXN0IHJlbW92ZSB0aGUgbGFzdCAiKiYmICAgc3VkbyBtYWtlIC1qNSBkZWIqIgo+IGNv
bW1hbmQuCj4+IEdyYW50ZWQsIGkgYW0gcnVubmluZyBhbmQgZG9pbmcgYWxsIG9mIHRoaXMgb24g
RGViaWFuIFdoZWV6eSBCVVQgaQo+IHRoZXJlCj4+IGFyZW4ndCBhbnkgZGlmZmVyZW5jZXMgaW4g
Y29tcGlsaW5nIGl0IG9uIFVidW50dSAxMi4wNC4KPj4KPj4KPj4KPj4KPj4+Pj4+ICAgICAwNi8w
My8xMiAyOjM0IFBNPj4+Cj4+PiBUaGUgbGF0ZXN0IHJldmlzaW9uIG9mIFhlbiA0LjItdW5zdGFi
bGUgaXMgKjI1NDUyOjZiZWE2M2U2Yzc4MCogYXQKPiB0aGUKPj4+IGxpbmsgKmh0dHA6Ly94ZW5i
aXRzLnhlbi5vcmcvaGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YKPj4gWGVu
Cj4+PiA0LjItVW5zdGFibGUgYXJlIHlvdSB0cnlpbmcgdG8gY29tcGlsZT8KPj4+Cj4+Pgo+Pj4+
IEhlbGxvLAo+Pj4+Cj4+Pj4gSSBhbSB0cnlpbmcgdG8gY29tcGlsZSB4ZW4gNC4yIHVuc3RhYmxl
IGZyb20gbWVyY3VyaWFsLiBJIGNhbid0IGdldAo+Pj4gcGFzdAo+Pj4+IHRoZSBtYWtlIHRvb2xz
IHN0ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6Cj4+Pj4K
Pj4+PiBDQyAgICBsaWJodzY0LzlwZnMvY294YXR0ci5vCj4+Pj4gICAgICAgQ0MgICAgbGliaHc2
NC85cGZzL3ZpcnRpby05cC1zeW50aC5vCj4+Pj4gICAgICAgQ0MgICAgbGliaHc2NC85cGZzL3Zp
cnRpby05cC1oYW5kbGUubwo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9uIMOi
aGFuZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKPj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90
b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+Pj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+Pj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9o
dy85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4+PiBub3RlOiBlYWNoIHVuZGVjbGFy
ZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gKPj4+IGZ1bmN0aW9u
Cj4+Pj4gaXQgYXBwZWFycyBpbgo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9u
IMOiaGFuZGxlX2xzdGF0w6I6Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+Pj4+IGVycm9yOiDD
okFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikK
Pj4+PiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOgo+Pj4gSW4KPj4+PiBmdW5jdGlvbiDDomhhbmRsZV9zeW1saW5rw6I6
Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMv
dmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2MjoKPj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6Ig
dW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Pj4gL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoK
Pj4+IEluCj4+Pj4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgo+Pj4+Cj4gL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoz
Mzc6NDU6Cj4+Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVz
ZSBpbiB0aGlzIGZ1bmN0aW9uKQo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9u
IMOiaGFuZGxlX2Nob3duw6I6Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4+PiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4+Pj4gbWFrZVs0XTogKioqIFs5cGZzL3ZpcnRpby05cC1oYW5kbGUub10gRXJyb3IgMQo+Pj4+
IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDIKPj4+PiBtYWtlWzNdOiBMZWF2
aW5nIGRpcmVjdG9yeQo+Pj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4t
ZGlyLXJlbW90ZScKPj4+PiBtYWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUteGVuLWRp
cl0gRXJyb3IgMgo+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5z
dGFibGUuaGcvdG9vbHMnCj4+Pj4gbWFrZVsxXTogKioqIFtzdWJkaXJzLWluc3RhbGxdIEVycm9y
IDIKPj4+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhn
L3Rvb2xzJwo+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMgo+Pj4+Cj4+Pj4g
SSBhbSBydW5uaW5nIHVidW50dSAxMi4wNCwga2VybmVsIHZlcjogMy4yLjAtMjQtZ2VuZXJpYwo+
Pj4+Cj4+Pj4gQW55IGlkZWFzPyBJIGhhdmUgZ29vZ2xlZCBmdXJpb3VzbHkgYW5kIGZvdW5kIHNv
bWUgcGVvcGxlIHRhbGtpbmcKPj4+IGFib3V0Cj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOgo+Pj4+IGh0dHBzOi8vYnVncy5sYXVuY2hwYWQubmV0L3VidW50dS8rc291cmNlL3Fl
bXUta3ZtLytidWcvOTMwMTgxCj4+Pj4gQnV0IEkgd2FzIG5vdCBhYmxlIHRvIGZpbmQgdGhlIHBh
dGNoCj4+Pj4KPj4+PiBUaGFua3MgaW4gYWR2YW5jZSEKPj4+Pgo+Pj4+Cj4+Pj4KPj4+PiBNZXJj
dXJpYWxtCj4+Pj4KPj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+Pj4+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPj4+PiBYZW4tdXNlcnNAbGlzdHMu
eGVuLm9yZwo+Pj4+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycwo+Pgo+Cj4KCgpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp
bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl
bi11c2Vycw==

From xen-users-bounces@lists.xen.org Tue Jun 05 12:22:21 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 12:22:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbskT-0001TI-Hs; Tue, 05 Jun 2012 12:20:33 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbskR-0001TD-0b
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:20:31 +0000
Received: from [85.158.138.51:2823] by server-10.bemta-3.messagelabs.com id
	5D/3A-06494-E89FDCF4; Tue, 05 Jun 2012 12:20:30 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-14.tower-174.messagelabs.com!1338898827!24521426!1
X-Originating-IP: [209.85.160.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2328 invoked from network); 5 Jun 2012 12:20:28 -0000
Received: from mail-gh0-f173.google.com (HELO mail-gh0-f173.google.com)
	(209.85.160.173)
	by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 12:20:28 -0000
Received: by ghrr14 with SMTP id r14so4337710ghr.32
	for ; Tue, 05 Jun 2012 05:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=Ci+y+OpqZw4dq3QE4wVxWKYXxlcIILqfy7gO1JfpF5U=;
	b=wZrEChY/uONQXeUhHvcf0q+GgiJjlnl5sXk27PCnmKDQGglyqtI3ylr6kKTjcFRBYn
	yHNNFs6yyCO6WD5rFeZOP61E0/ZNZh1vKUVK5y3CLUGuS8s5lQpAxfiiI+Ob343e77GS
	MHqj2Rk/lXzF1CPVgSlUTaPSxA+R6ivV0XPctYHiqHXTXo7RNPhkVrgy3z0R4Q7BD53i
	QVYXvL6AVKWBlEnpv3ZmgXvZ+hWDUTaah/DK0ivbBtNSRdf82IUbEfmVPVy/ibT2YcGY
	X4dopx+fA/r+TzROSm/qg/Ngz1M5Wxth2qteSxL6HtsVC7KEXDBoHWORxgl8v4zVk661
	AUwA==
Received: by 10.101.3.34 with SMTP id f34mr4967174ani.3.1338898826892;
	Tue, 05 Jun 2012 05:20:26 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id c12sm1879155ann.15.2012.06.05.05.20.25
	(version=TLSv1/SSLv3 cipher=OTHER);
	Tue, 05 Jun 2012 05:20:26 -0700 (PDT)
Message-ID: <4FCDF96F.2050007@gmail.com>
Date: Tue, 05 Jun 2012 08:19:59 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

aHVtbSwgd2VsbCB0aGF0IHN1Y2tzLiBJIGtub3cgY29tcGlsaW5nIGNoYW5nZXNldCAyNTM5MiB3
b3JrcyBmb3IgbWUsIAp3aXRoIHRoZSBwYWNrYWdlcyBhbmQgaW5zdHJ1Y3Rpb25zIGkgZGVzY3Jp
YmVkLCBpIGhhdmUgY29tcGlsZWQgaXQgCnNldmVyYWwgdGltZXMgbm93LiBJIGtub3cgdGhlIG1h
aW4gcmVhc29uIHdoeSB0aGUgbGF0ZXIgY2hhbmdlc3RzIHdvbid0IApjb21waWxlIGlzIGJlY2F1
c2Ugb2YgdGhlIGRpZmZlcmVudCBHQ0MgdmVyc2lvbiBzZWVtIHRvIGRvIGRpZmZlcmVudCAKZW5v
dWdoIHRvIGZhaWwsIFNPIG1heWJlIFVidW50dSBoYXMgYSBkaWZmZXJlbnQgc3Vic2V0IG9mIEdD
Qy4gSSBoYXZlIG5vIAppZGVhLgoKV2VsbCwgaWYgaXQgd2FzIG5vIHRyb3VibGUgZm9yIHlvdSwg
bWF5YmUgdHJ5IHRvIGluc3RhbGwgRGViaWFuIFdoZWV6eSAKYW5kIHRyeSB0byBjb21waWxlIGFn
YWluLiBPdGhlcndpc2UgaSBjb3VsZCBhbHdheXMgc2VuZCB5b3UgdGhlIFhlbiA0LjIgCnJldi0y
NTM5MiBjb21waWxlZCBERUIgcGFja2FnZSBhbmQgeW91IGNhbiBqdXN0IGluc3RhbGwgdGhhdCwg
QlVUIHRoYXQgCndvdWxkbid0IHNvbHZlIHlvdXIgcHJvYmxlbSBpZiB5b3Ugd2FudGVkIHRvIGNv
bXBpbGUgaXQgbGF0ZXIgb24uCgoKPiBIbW0gc2FtZSBlcnJvcjoKPgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhh
bmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKPiAvcm9v
dC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3Zp
cnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNs
YXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhn
LXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
NzA6NTg6Cj4gbm90ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25s
eSBvbmNlIGZvciBlYWNoIGZ1bmN0aW9uCj4gaXQgYXBwZWFycyBpbgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhh
bmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xzdGF0w6I6Cj4gL3Jvb3QveGVuLXVuc3Rh
YmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFu
ZGxlLmM6ODc6MzQ6Cj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0
IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0
aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1Mzky
L3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6Cj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4t
ZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xp
bmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMzc6NDU6Cj4gZXJyb3I6IMOiQVRfRU1QVFlf
UEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOgo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2Nob3duw6I6Cj4gL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8t
OXAtaGFuZGxlLmM6MzczOjU4Ogo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVk
IChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5vXSBFcnJvciAxCj4gbWFrZVs0XTogKioqIFdhaXRpbmcgZm9yIHVuZmluaXNo
ZWQgam9icy4uLi4KPiAgICBDQyAgICBobXAubwo+ICAgIENDICAgIGxpYmRpcy9pMzg2LWRpcy5v
Cj4gICAgTElOSyAgcWVtdS1nYQo+ICAgIExJTksgIHFlbXUtbmJkCj4gICAgTElOSyAgcWVtdS1p
bWcKPiAgICBMSU5LICBxZW11LWlvCj4gbWFrZVszXTogKioqIFtzdWJkaXItbGliaHc2NF0gRXJy
b3IgMgo+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0b3J5Cj4gYC9yb290L3hlbi11bnN0YWJsZS5o
Zy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyLXJlbW90ZScKPiBtYWtlWzJdOiAqKiogW3N1
YmRpci1pbnN0YWxsLXFlbXUteGVuLWRpcl0gRXJyb3IgMgo+IG1ha2VbMl06IExlYXZpbmcgZGly
ZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzJwo+IG1ha2VbMV06
ICoqKiBbc3ViZGlycy1pbnN0YWxsXSBFcnJvciAyCj4gbWFrZVsxXTogTGVhdmluZyBkaXJlY3Rv
cnkgYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMnCj4gbWFrZTogKioqIFtp
bnN0YWxsLXRvb2xzXSBFcnJvciAyCj4KPiBJIGhhZCBtb3N0IG9mIHRoZSBwYWNrYWdzLCBJIHJh
biAiYXB0LWdldCBidWlsZC1kZXAgeGVuIiBmcm9tOgo+IGh0dHA6Ly93aWtpLnhlbi5vcmcvd2lr
aS9Db21waWxpbmdfWGVuX0Zyb21fU291cmNlCj4KPiBCdXQgaXQgc3RpbGwgZXJyb3JzIG9uIHRo
ZSB2aXJ0aW8gZmlsZS4gSSBoYWQgYWxzbyByZWFkIHRoYXQgdGhlc2UKPiBlcnJvcnMgaGFkIHRv
IGRpZmZlcmVudCB3aXRoIGRpZmZlcmVudCBsaWJyYXJ5L2djYyB2ZXJzaW9ucy4gTWF5YmUKPiB3
aGVlenkganVzdCBoYXMgbmV3ZXIvZGlmZmVyZW50IHZlcnNpb25zIG9mIHRob3NlIGJpbmFyaWVz
L2xpYnM/Cj4KPiAtLVdpbGwKPgo+Cj4+Pj4gICAwNi8wNC8xMiAxMTo0NSBBTT4+Pgo+IFdFTEws
IGFjdHVhbGx5IE5PIG5lZWQgdG8gaW5zdGFsbCBXaGVlenkuIEkgYW0gdmVyeSBzdXJlIHlvdSBj
YW4gZ2V0IGl0Cj4gd29ya2luZyBqdXN0IGFzIGVhc2lseSB3aXRoIFVidW50dS4KPgo+IFRoZSBv
dGhlciB0aGluZyBpIGZvcmdvdCB0byBtZW50aW9uIGlzIHlvdSBoYXZlIHRvIGhhdmUgYWxsIG9m
IHRoZQo+IHJlcXVpcmVkIHBhY2thZ2VzIGluc3RhbGxlZCBiZWZvcmUgeW91IGNhbiBjb21waWxl
IFhlbi4gSSB0aGluayB5b3UgYXJlCj4ganVzdCBtaXNzaW5nIGEgYnVuY2ggb2YgZGVwZW5kZW50
IHBhY2thZ2VzLiBUaGUgcGFja2FnZXMgaSB1c2UgYW5kIGhhdmUKPiBpbnN0YWxsZWQgYXJlIGFz
IGZvbGxvd3M6Cj4KPiBzdWRvIGFwdC1nZXQgaW5zdGFsbCB3Z2V0IHRhciBiemlwMiBidWlsZC1l
c3NlbnRpYWwgbGlibmN1cnNlczUtZGV2Cj4ga2VybmVsLXBhY2thZ2UgZmFrZXJvb3QgYmNjIGdj
YyBzc2ggYnJpZGdlLXV0aWxzIHB5dGhvbi1kZXYgdXVpZC1kZXYKPiBsaWJnbGliMi4wLWRldiBs
aWJ5YWpsLWRldiBsaWJhaW8tZGV2IGdjYy1tdWx0aWxpYiBpYXNsIGxpYnBjaS1kZXYgZmxleAo+
IGJpc29uIHF0NC1kZXYtdG9vbHMgcGF0Y2ggb2NhbWwtZmluZGxpYiBsaWJzZGwxLjItZGV2Cj4K
PiBHcmFudGVkIHNvbWUgb2YgdGhlIGFib3ZlIHBhY2thZ2VzIGFyZSBtb3JlIGltcG9ydGFudCBm
b3IgY29tcGlsaW5nIHRoZQo+IGtlcm5lbC4KPgo+IFNPLCBhcyBsb25nIGFzIHlvdSBoYXZlIGFs
bCByZXF1aXJlZCBwYWNrYWdlcyBhbmQgZm9sbG93IHRoZQo+IGluc3RydWN0aW9ucyBiZWZvcmUg
YWJvdXQgZ2V0dGluZyBhbmQgY29tcGlsaW5nIFhlbiA0LjIgcmV2aXNpb24gMjUzOTIsCj4gaXQg
c2hvdWxkIGJlIGZpbmUsIG5vIG1hdHRlciBpZiB5b3UgYXJlIHVzaW5nIERlYmlhbiBvciBVYnVu
dHUuIFVidW50dQo+IGhvd2V2ZXIgIm1pZ2h0IiBuZWVkIG1vcmUgcGFja2FnZXMsIG5vdCBzdXJl
LCAgaSBoYXZlIG5vdCBjb21waWxlZCBYZW4KPiB1bmRlciBVYnVudHUgeWV0Lgo+Cj4KPgo+IE9u
IDYvNC8yMDEyIDEyOjQzIFBNLCBXaWxsIE1jRGVybW90dCB3cm90ZToKPj4gRGFybiwgbWFkZSBp
dCBmYXJ0aGVyIGJ1dCBub3cgSSBnZXQgdGhpczoKPj4KPj4gQ0MgICAgbGliaHc2NC85cGZzL3Zp
cnRpby05cC1zeW50aC5vCj4+ICAgICBDQyAgICBsaWJodzY0LzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5vCj4+ICAgICBDQyAgICBxZW11LWNoYXIubwo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+
PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6Cj4+Cj4gL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8t
OXAtaGFuZGxlLmM6NzA6NTg6Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVk
IChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3
MDo1ODoKPj4gbm90ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25s
eSBvbmNlIGZvciBlYWNoCj4gZnVuY3Rpb24KPj4gaXQgYXBwZWFycyBpbgo+Pgo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pgo+IC9yb290
L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNs
YXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxl
LmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6Cj4+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPj4KPiAvcm9vdC94ZW4tdW5z
dGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1o
YW5kbGUuYzozMTQ6NjI6Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChm
aXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2
LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4g
SW4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMz
Nzo0NToKPj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9jaG93bsOiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAx
Cj4+IG1ha2VbNF06ICoqKiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+ICAgICBD
QyAgICBzYXZldm0ubwo+PiAgICAgQ0MgICAgbXNtb3VzZS5vCj4+ICAgICBDQyAgICBwczIubwo+
PiBtYWtlWzNdOiAqKiogW3N1YmRpci1saWJodzY0XSBFcnJvciAyCj4+IG1ha2VbM106ICoqKiBX
YWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0
b3J5Cj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci1yZW1vdGUnCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBF
cnJvciAyCj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUu
aGctcmV2LTI1MzkyL3Rvb2xzJwo+PiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJy
b3IgMgo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhn
LXJldi0yNTM5Mi90b29scycKPj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4+
Cj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNoIGZvciB5b3VyIGNsZWFy
IGluc3RydWN0aW9ucyEgSQo+PiB3aWxsIGluc3RhbGwgd2hlZXp5IHRvbmlnaHQgYW5kIHRyeSB0
aGUgYnVpbGQgYWdhaW4uCj4+Cj4+IC0tV2lsbAo+Pgo+Pj4+PiAgICAwNi8wNC8xMiA0OjU2IEFN
Pj4+Cj4+IE9uIDYvNC8yMDEyIDI6NTggQU0sIFdpbGwgTWNEZXJtb3R0IHdyb3RlOgo+Pj4gSSdt
IG5vdCBzdXJlIHdoYXQgdmVyc2lvbiAoaG93IGRvIEkgY2hlY2s/KSBidXQgSSBqdXN0IGNsb25l
ZCBmcm9tCj4+IHRoYXQKPj4+IFVSTCB0b2RheS4KPj4+Cj4+PiAtLVdpbGwKPj4gV2VsbCB0aGFu
IHlvdSBwcm9iYWJseSBhbHJlYWR5IGhhdmUgdGhlIGxhdGVzdCByZXZpc2lvbi4gWW91IGNhbiBh
bHNvCj4+IGNoZWNrIHdoYXQgcmV2aXNpb24geW91ciBsb2NhbGx5IGNsb25lZCByZXBvc2l0b3J5
IGlzIGF0IGJ5IGdvaW5nIHRvCj4gdGhlCj4+IGZvbGRlciBhbmQgcnVubmluZzoKPj4KPj4gKmNk
ICAuLi94ZW4tdW5zdGFibGUuaGcKPj4gaGcgc3VtbWFyeQo+PiAqCj4+IEFuZCB0aGF0IHdpbGwg
c2hvdyB5b3UgYSBzdW1tYXJ5IG9mIHRoZSBsb2NhbCBtZXJjdXJpYWwgY2xvbmUgYW5kIHNob3cK
Pj4gdGhlIGxhdGVzdCByZXZpc2lvbnMgdGhhdCB3YXMgY2xvbmVkLgo+Pgo+PiBTTywgYW55aG93
LCBjb21waWxpbmcgdGhlIFhlbiA0LjItdW5zdGFibGUgZnJvbSB0aGUgbWVyY3VyaWFsIGhhcyBu
b3QKPj4gYmVlbiB3b3JraW5nIHZlcnkgd2VsbCBmb3IgYSBmZXcgd2Vla3Mgbm93LiBJIGhhdmUg
YXNrZWQgdGhlIFhlbi1kZXZlbAo+PiBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhl
cmUgYXJlIGlzc3VlcyBhbmQgcHJvYmxlbXMgd2l0aAo+PiBkaWZmZXJlbnQgR0NDIGNvbXBpbGVy
cyBBTkQgdGhlIFhlbi1kZXZlbCB0ZWFtIGtub3dzIGFsbCB0aGF0IGFuZCBhcmUKPj4gd29ya2lu
ZyBvbiBmaXhpbmcgdGhhdC4KPj4KPj4gRm9yIG5vdywgdGhlIExBU1QgcmV2aXNpb24gaSB3YXMg
YWJsZSB0byBjb21waWxlIGFuZCBnZXQgcnVubmluZyB3YXMKPj4gKiJyZXZpc2lvbiAyNTM5Mioi
LCBidXQgZXZlbiB0aGF0IHdhcyBwb3NzaWJseSBPTkxZIGlmIHlvdSByZW1vdmUgb25lCj4+IHBh
dGNoLiBZb3UgY2FuIHRyeSB0byBkb3dubG9hZCBhbmQgY29tcGlsZSBUSEFUIHZlcnNpb24gYnkg
cnVubmluZyB0aGUKPj4gZm9sbG93aW5nIGNvbW1hbmRzOgo+Pgo+PiBfKkNsb25pbmcgWGVuOipf
Cj4+ICotIGNkIC9zb21lL2RpcmVjdG9yeS9pbi9ob21lCj4+IC0gcmV2PTI1MzkyJiYgICBoZyBj
bG9uZSAtciAkcmV2Cj4+IGh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvaGcveGVuLXVuc3RhYmxlLmhn
LyB4ZW4tdW5zdGFibGUuaGctcmV2LSR7cmV2fQo+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIKPj4gLSBoZyBiYWNrb3V0IC1yIDI1MzY0Kgo+Pgo+PiBUaGlzIHdpbGwgY2xvbmUgdGhl
IHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbgo+PiA0LjItdW5zdGFi
bGUgcmV2aXNpb24gMjUzOTIgaW50byB0aGUgZm9sZGVyCj4+ICIqeGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5MioiLiBSdW5uaW5nIHRoZSBjb21tYW5kICIqaGcgYmFja291ciAtcgo+PiAyNTM2NCoi
IHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4gSXQgc2VlbXMgdGhh
dAo+PiB3aXRob3V0IHRoYXQsIGV2ZW4gdGhhdCByZXZpc2lvbiB3b250IGNvbXBpbGUuCj4+Cj4+
IF8qQ29tcGlsaW5nIFhlbjoqXwo+PiBUaGFuIGp1c3Qgc2ltcGx5IHJ1biB0aGVzZSBjb21tYW5k
cyB0byBjb21waWxlIFhlbi4KPj4KPj4gKi0gY2QgeGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5MioK
Pj4gKi0gLi9jb25maWd1cmUKPj4gLSBzdWRvIG1ha2UgLWo1IHhlbiYmICAgc3VkbyBtYWtlIFRo
ZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdAo+IHN0cmluZ3MgdG9nZXRoZXIgdGhlIDQgY29t
cGlsaW5nIGNvbW1hbmRzCj4+IHRvIHJ1biBhbmQgd2lsbCBleGVjdXRlIG9uZSBhZnRlciB0aGUg
b3RoZXIgU08geW91IGRvbid0IGhhdmUgdG8KPj4gbWFudWFsbHkgcnVuIGVhY2ggYW5kIGV2ZXJ5
IG9uZS4gQWxzbywgSW4gdGhlIGFib3ZlICIqbWFrZSoiIGNvbW1hbmRzLAo+PiB1c2luZyB0aGUg
IiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtlIHRlbGxzIHRoZSBjb21waWxlIHRvIHVzZSBt
b3JlCj4+IHRoYW4gb25lIGNvcmUgdG8gY29tcGlsZSB3aXRoLiBJdCBzcGVlZHMgdXAgdGhlIGNv
bXBpbGk+ICBoYXZlIGEgbXVsdGktY29yZSBDUFUuIFNPIGluIG15IGNhc2UsIGkgaGF2ZSBhIFF1
YWQgQ29yZSBDUFUsIHNvIHRoYXQKPj4gY29tbWFuZCBvcHRpb24gaXMgIiotajEgKyBudW1iZXIg
b2YgQ1BVIGNvcmVzKiIuIFlvdSBjYW4gbW9kaWZ5IG9yCj4+IHJlbW92ZSB0aGF0IGFzIHlvdSB3
aXNoLgo+Pgo+PiBUaGUgYWJvdmUgd2lsbCBhbHNvIGNyZWF0ZSBmb3IgeW91IGEgbmljZSBERUIg
cGFja2FnZSBhZnRlciBhbGwgdGhlCj4+IGNvbXBpbGluZyBpcyBkb25lLCBpZiB5b3UgZG8gbm90
IHdhbnQgdG8gY3JlYXRlIGEgREVCIHBhY2thZ2UgYXQgdGhlCj4gZW5kCj4+IG9mIGl0IGFsbCwg
dGhhbiBqdXN0IHJlbW92ZSB0aGUgbGFzdCAiKiYmICAgc3VkbyBtYWtlIC1qNSBkZWIqIgo+IGNv
bW1hbmQuCj4+IEdyYW50ZWQsIGkgYW0gcnVubmluZyBhbmQgZG9pbmcgYWxsIG9mIHRoaXMgb24g
RGViaWFuIFdoZWV6eSBCVVQgaQo+IHRoZXJlCj4+IGFyZW4ndCBhbnkgZGlmZmVyZW5jZXMgaW4g
Y29tcGlsaW5nIGl0IG9uIFVidW50dSAxMi4wNC4KPj4KPj4KPj4KPj4KPj4+Pj4+ICAgICAwNi8w
My8xMiAyOjM0IFBNPj4+Cj4+PiBUaGUgbGF0ZXN0IHJldmlzaW9uIG9mIFhlbiA0LjItdW5zdGFi
bGUgaXMgKjI1NDUyOjZiZWE2M2U2Yzc4MCogYXQKPiB0aGUKPj4+IGxpbmsgKmh0dHA6Ly94ZW5i
aXRzLnhlbi5vcmcvaGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YKPj4gWGVu
Cj4+PiA0LjItVW5zdGFibGUgYXJlIHlvdSB0cnlpbmcgdG8gY29tcGlsZT8KPj4+Cj4+Pgo+Pj4+
IEhlbGxvLAo+Pj4+Cj4+Pj4gSSBhbSB0cnlpbmcgdG8gY29tcGlsZSB4ZW4gNC4yIHVuc3RhYmxl
IGZyb20gbWVyY3VyaWFsLiBJIGNhbid0IGdldAo+Pj4gcGFzdAo+Pj4+IHRoZSBtYWtlIHRvb2xz
IHN0ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6Cj4+Pj4K
Pj4+PiBDQyAgICBsaWJodzY0LzlwZnMvY294YXR0ci5vCj4+Pj4gICAgICAgQ0MgICAgbGliaHc2
NC85cGZzL3ZpcnRpby05cC1zeW50aC5vCj4+Pj4gICAgICAgQ0MgICAgbGliaHc2NC85cGZzL3Zp
cnRpby05cC1oYW5kbGUubwo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9uIMOi
aGFuZGxlX3VwZGF0ZV9maWxlX2NyZWTDojoKPj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90
b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+Pj4g
ZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1
bmN0aW9uKQo+Pj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9o
dy85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4+PiBub3RlOiBlYWNoIHVuZGVjbGFy
ZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gKPj4+IGZ1bmN0aW9u
Cj4+Pj4gaXQgYXBwZWFycyBpbgo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9u
IMOiaGFuZGxlX2xzdGF0w6I6Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+Pj4+IGVycm9yOiDD
okFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikK
Pj4+PiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOgo+Pj4gSW4KPj4+PiBmdW5jdGlvbiDDomhhbmRsZV9zeW1saW5rw6I6
Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMv
dmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2MjoKPj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6Ig
dW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Pj4gL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoK
Pj4+IEluCj4+Pj4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8OiOgo+Pj4+Cj4gL3Jvb3QveGVuLXVu
c3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoz
Mzc6NDU6Cj4+Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVz
ZSBpbiB0aGlzIGZ1bmN0aW9uKQo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbgo+Pj4+IGZ1bmN0aW9u
IMOiaGFuZGxlX2Nob3duw6I6Cj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4+PiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4+Pj4gbWFrZVs0XTogKioqIFs5cGZzL3ZpcnRpby05cC1oYW5kbGUub10gRXJyb3IgMQo+Pj4+
IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDIKPj4+PiBtYWtlWzNdOiBMZWF2
aW5nIGRpcmVjdG9yeQo+Pj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4t
ZGlyLXJlbW90ZScKPj4+PiBtYWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUteGVuLWRp
cl0gRXJyb3IgMgo+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5z
dGFibGUuaGcvdG9vbHMnCj4+Pj4gbWFrZVsxXTogKioqIFtzdWJkaXJzLWluc3RhbGxdIEVycm9y
IDIKPj4+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhn
L3Rvb2xzJwo+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMgo+Pj4+Cj4+Pj4g
SSBhbSBydW5uaW5nIHVidW50dSAxMi4wNCwga2VybmVsIHZlcjogMy4yLjAtMjQtZ2VuZXJpYwo+
Pj4+Cj4+Pj4gQW55IGlkZWFzPyBJIGhhdmUgZ29vZ2xlZCBmdXJpb3VzbHkgYW5kIGZvdW5kIHNv
bWUgcGVvcGxlIHRhbGtpbmcKPj4+IGFib3V0Cj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOgo+Pj4+IGh0dHBzOi8vYnVncy5sYXVuY2hwYWQubmV0L3VidW50dS8rc291cmNlL3Fl
bXUta3ZtLytidWcvOTMwMTgxCj4+Pj4gQnV0IEkgd2FzIG5vdCBhYmxlIHRvIGZpbmQgdGhlIHBh
dGNoCj4+Pj4KPj4+PiBUaGFua3MgaW4gYWR2YW5jZSEKPj4+Pgo+Pj4+Cj4+Pj4KPj4+PiBNZXJj
dXJpYWxtCj4+Pj4KPj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+Pj4+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPj4+PiBYZW4tdXNlcnNAbGlzdHMu
eGVuLm9yZwo+Pj4+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycwo+Pgo+Cj4KCgpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp
bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl
bi11c2Vycw==

From xen-users-bounces@lists.xen.org Tue Jun 05 12:32:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 12:32:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbsuL-0001iU-Th; Tue, 05 Jun 2012 12:30:45 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbsuK-0001iN-4H
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:30:44 +0000
Received: from [85.158.139.83:39256] by server-1.bemta-5.messagelabs.com id
	E1/3E-25424-3FBFDCF4; Tue, 05 Jun 2012 12:30:43 +0000
X-Env-Sender: baileyp@ct-itsolutions.com
X-Msg-Ref: server-6.tower-182.messagelabs.com!1338899441!28210725!1
X-Originating-IP: [173.201.193.186]
X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30,HTML_MESSAGE,MIME_HTML_ONLY
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32626 invoked from network); 5 Jun 2012 12:30:42 -0000
Received: from p3plsmtp18-03-2.prod.phx3.secureserver.net (HELO
	p3plwbeout18-03.prod.phx3.secureserver.net) (173.201.193.186)
	by server-6.tower-182.messagelabs.com with SMTP;
	5 Jun 2012 12:30:42 -0000
Received: from localhost ([173.201.193.245])
	by p3plwbeout18-03.prod.phx3.secureserver.net with bizsmtp
	id JcWg1j0015J8WZH01cWg3E; Tue, 05 Jun 2012 05:30:40 -0700
x-cmae-analysis: v=2.0 cv=f7fK9ZOM c=1 sm=1 a=s9mnUP56SRzXDLvfRu4LOg==:17
	a=kpwjDOozP74A:10 a=jaiTJcHAWCEA:10 a=BoaYdNz1BosA:10 a=jUMMqpT44fcA:10
	a=IkcTkHD0fZMA:10 a=TAIPOn3lAAAA:8 a=TZb1taSUAAAA:8 a=mLnsDVdbAAAA:8
	a=vbpcHzlMSVUEym1tvd4A:9 a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10
	a=tXsnliwV7b4A:10 a=BRwtCLxlb8gA:10 a=49_gKzuBSYJlupm2:21
	a=ofvVyeaxqMRfvj7-:21 a=s9mnUP56SRzXDLvfRu4LOg==:117
Received: (qmail 22602 invoked by uid 99); 5 Jun 2012 12:30:40 -0000
X-Originating-IP: 208.47.241.42
User-Agent: Workspace Webmail 5.6.18
Message-Id: <20120605053039.e0b8cbd812270189f8876d5fa06e6a41.82ee4c46c7.wbe@email18.secureserver.net>
From: 
To: "John Sherwood" 
Date: Tue, 05 Jun 2012 05:30:39 -0700
Mime-Version: 1.0
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4463188718690126621=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4463188718690126621==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"


Thank you, John. Your advice isn't pedantic, just thorough. =
We'll go ahead with a pilot program with a couple of desktops, as you recom=
mend; we'll also have to review the possibility of upgrading our Windows se=
rver and using Remote Desktop Services as the interim solution, since it so=
unds like the hardware upgrade costs would probably trump the licensing cos=
ts. Meanwhile, we can keep moving our other servers to Xen. Thanks again.
=0A
=0A
=0A--=
------ Original Message --------
=0ASubject: Re: [Xen-users] Hardware re=
quirements for Xen
=0AFrom: John Sherwood <jrs@vt.edu>
=0ADate: Mon, June 04, 2012 1:36 pm
=0ATo: baileyp@ct-itsolutions.com=0ACc: xen-users@lists.xen.org=

=0A
=0A
You don't need a "powerful" server to run Xen by any=
 means, but to run Xen and 30 VMs is a different story.  Not to be ped=
antic, but the requirements for power come entirely from your workload, not=
 from the (extremely lightweight) Xen hypervisor itself.
 

Bare minimum you'll want 1 core + 512 MB RAM for each VM, then a core an=
d additional RAM for the dom0.  With 30 VMs you're going to want a pre=
tty beefy amount of RAM for your dom0, and you'll probably need another cor=
e as well.  You'd probably want at least 2 NICs so that you have more =
bandwidth when you've got a couple dozen VNC connections active.
 
<=
/div>
However: I have no experience running that many HVM machines at o=
nce - I've run 16 VMs on an 8 core, 16 thread host before, but that was wit=
h PV.  At any rate, I suppose my suggestion for your server would be:<=
/div> 
  • 32 cores (using either something like opteron 62XX inter=
lagos, or Xeon E5-26XX)
  • 32+ GB RAM
  • 3+ NICs, 1 dedicated for=
 management of dom0
If you have any boxes lying around, I mig=
ht also suggest trying to load an 8 core server with 7 winXP VMs and seeing=
 how it performs with all the VMs having VNC active - that should give you =
a decent feel for whether you need to scale up your requirements before pur=
chasing or allocating more expensive hardware.  Keep in mind that you =
want to scale up the dom0 memory as you add more VMs though, and the load o=
n the dom0 will increase with more VMs as well - due to the HVMs, the dom0 =
load will increase with the number of virtualized peripherals.
 
=



On Mon, Jun 4, 2012 at 4:=
10 PM, <baileyp@ct-itsolutions.com> wrote:
 
   I need to figure out how powerful a server I need=
 to run Xen. Specifically, I'm looking to replace about 30 Windows XP deskt=
ops with low-power thin-clients using VNC to connect to virtual desktops pr=
ovided by Xen. This is supposed to be a cheap interim step while we work to=
 replace an Access system that most of our employees use with a web-based p=
rogram, at which point most of the VM's would be deprecated (as the thin-cl=
ient PC's would simply be used to connect to the intranet site).
    So, in short -- I'm looking to replace about 30 WinXP desktop=
s with VM's hosted by Xen, and I need to figure out how much memory and CPU=
 power I'll need to make this feasible. Is there some guideline I can use t=
o figure this out?
 
 
________________________________=
_______________
 Xen-users mailing list
 Xen-users@lists.xen.org
 http://lists.xen.org/xen=
-users
 

 =0A
=0A


--===============4463188718690126621==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4463188718690126621==--

From xen-users-bounces@lists.xen.org Tue Jun 05 12:32:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 12:32:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1SbsuL-0001iU-Th; Tue, 05 Jun 2012 12:30:45 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbsuK-0001iN-4H
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:30:44 +0000
Received: from [85.158.139.83:39256] by server-1.bemta-5.messagelabs.com id
	E1/3E-25424-3FBFDCF4; Tue, 05 Jun 2012 12:30:43 +0000
X-Env-Sender: baileyp@ct-itsolutions.com
X-Msg-Ref: server-6.tower-182.messagelabs.com!1338899441!28210725!1
X-Originating-IP: [173.201.193.186]
X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30,HTML_MESSAGE,MIME_HTML_ONLY
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32626 invoked from network); 5 Jun 2012 12:30:42 -0000
Received: from p3plsmtp18-03-2.prod.phx3.secureserver.net (HELO
	p3plwbeout18-03.prod.phx3.secureserver.net) (173.201.193.186)
	by server-6.tower-182.messagelabs.com with SMTP;
	5 Jun 2012 12:30:42 -0000
Received: from localhost ([173.201.193.245])
	by p3plwbeout18-03.prod.phx3.secureserver.net with bizsmtp
	id JcWg1j0015J8WZH01cWg3E; Tue, 05 Jun 2012 05:30:40 -0700
x-cmae-analysis: v=2.0 cv=f7fK9ZOM c=1 sm=1 a=s9mnUP56SRzXDLvfRu4LOg==:17
	a=kpwjDOozP74A:10 a=jaiTJcHAWCEA:10 a=BoaYdNz1BosA:10 a=jUMMqpT44fcA:10
	a=IkcTkHD0fZMA:10 a=TAIPOn3lAAAA:8 a=TZb1taSUAAAA:8 a=mLnsDVdbAAAA:8
	a=vbpcHzlMSVUEym1tvd4A:9 a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10
	a=tXsnliwV7b4A:10 a=BRwtCLxlb8gA:10 a=49_gKzuBSYJlupm2:21
	a=ofvVyeaxqMRfvj7-:21 a=s9mnUP56SRzXDLvfRu4LOg==:117
Received: (qmail 22602 invoked by uid 99); 5 Jun 2012 12:30:40 -0000
X-Originating-IP: 208.47.241.42
User-Agent: Workspace Webmail 5.6.18
Message-Id: <20120605053039.e0b8cbd812270189f8876d5fa06e6a41.82ee4c46c7.wbe@email18.secureserver.net>
From: 
To: "John Sherwood" 
Date: Tue, 05 Jun 2012 05:30:39 -0700
Mime-Version: 1.0
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Hardware requirements for Xen
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4463188718690126621=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4463188718690126621==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"


Thank you, John. Your advice isn't pedantic, just thorough. =
We'll go ahead with a pilot program with a couple of desktops, as you recom=
mend; we'll also have to review the possibility of upgrading our Windows se=
rver and using Remote Desktop Services as the interim solution, since it so=
unds like the hardware upgrade costs would probably trump the licensing cos=
ts. Meanwhile, we can keep moving our other servers to Xen. Thanks again.
=0A
=0A
=0A--=
------ Original Message --------
=0ASubject: Re: [Xen-users] Hardware re=
quirements for Xen
=0AFrom: John Sherwood <jrs@vt.edu>
=0ADate: Mon, June 04, 2012 1:36 pm
=0ATo: baileyp@ct-itsolutions.com=0ACc: xen-users@lists.xen.org=

=0A
=0A
You don't need a "powerful" server to run Xen by any=
 means, but to run Xen and 30 VMs is a different story.  Not to be ped=
antic, but the requirements for power come entirely from your workload, not=
 from the (extremely lightweight) Xen hypervisor itself.
 

Bare minimum you'll want 1 core + 512 MB RAM for each VM, then a core an=
d additional RAM for the dom0.  With 30 VMs you're going to want a pre=
tty beefy amount of RAM for your dom0, and you'll probably need another cor=
e as well.  You'd probably want at least 2 NICs so that you have more =
bandwidth when you've got a couple dozen VNC connections active.
 
<=
/div>
However: I have no experience running that many HVM machines at o=
nce - I've run 16 VMs on an 8 core, 16 thread host before, but that was wit=
h PV.  At any rate, I suppose my suggestion for your server would be:<=
/div> 
  • 32 cores (using either something like opteron 62XX inter=
lagos, or Xeon E5-26XX)
  • 32+ GB RAM
  • 3+ NICs, 1 dedicated for=
 management of dom0
If you have any boxes lying around, I mig=
ht also suggest trying to load an 8 core server with 7 winXP VMs and seeing=
 how it performs with all the VMs having VNC active - that should give you =
a decent feel for whether you need to scale up your requirements before pur=
chasing or allocating more expensive hardware.  Keep in mind that you =
want to scale up the dom0 memory as you add more VMs though, and the load o=
n the dom0 will increase with more VMs as well - due to the HVMs, the dom0 =
load will increase with the number of virtualized peripherals.
 
=



On Mon, Jun 4, 2012 at 4:=
10 PM, <baileyp@ct-itsolutions.com> wrote:
 
   I need to figure out how powerful a server I need=
 to run Xen. Specifically, I'm looking to replace about 30 Windows XP deskt=
ops with low-power thin-clients using VNC to connect to virtual desktops pr=
ovided by Xen. This is supposed to be a cheap interim step while we work to=
 replace an Access system that most of our employees use with a web-based p=
rogram, at which point most of the VM's would be deprecated (as the thin-cl=
ient PC's would simply be used to connect to the intranet site).
    So, in short -- I'm looking to replace about 30 WinXP desktop=
s with VM's hosted by Xen, and I need to figure out how much memory and CPU=
 power I'll need to make this feasible. Is there some guideline I can use t=
o figure this out?
 
 
________________________________=
_______________
 Xen-users mailing list
 Xen-users@lists.xen.org
 http://lists.xen.org/xen=
-users
 

 =0A
=0A


--===============4463188718690126621==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4463188718690126621==--

From xen-users-bounces@lists.xen.org Tue Jun 05 13:51:31 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 13:51: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 1Sbu90-0002Of-NE; Tue, 05 Jun 2012 13:49:58 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbu8z-0002Oa-JA
	for xen-users@lists.xensource.com; Tue, 05 Jun 2012 13:49:57 +0000
Received: from [85.158.139.83:37739] by server-3.bemta-5.messagelabs.com id
	D4/E2-17554-48E0ECF4; Tue, 05 Jun 2012 13:49:56 +0000
X-Env-Sender: cecil.hanjj@gmail.com
X-Msg-Ref: server-12.tower-182.messagelabs.com!1338904193!32072007!1
X-Originating-IP: [209.85.160.43]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17447 invoked from network); 5 Jun 2012 13:49:55 -0000
Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com)
	(209.85.160.43)
	by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 13:49:55 -0000
Received: by pbcwz7 with SMTP id wz7so8544556pbc.30
	for ;
	Tue, 05 Jun 2012 06:49:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=zXm1OE0eNSnrF/g4TTZd2J6gB/Kx0aZzj5GeoF8i/C8=;
	b=HSZTIKV7lQFA+sTnZ28mhjhaUjE8oo7yjpWgwi4GjHbhlu2d44NRflQOvoC98tfeUc
	bY+1xLOuWbbByqJWJQTbm14pfjhcCLEeBwF43ijrqezb+AgubOmXmRgvVJxWGuXK9wfk
	9rO/y48p2oqg8JkODc4OqFbh2RRs/E7fAaRWqNsCD15AKQCc0pUhKoQ9ETrkN9vSX5Jr
	d2op5TMrD+GMUVAj8WXQR/NakUqqQ0fd4ZHRoiSgeo9C/v/w8R5Smit7MMWvAkDxX/yu
	p1Zojk8LU5H4QcprYACD8EQ9f88MsUiQMmryJv0EfQR2qi/sHVFn8CurrBTaC6AQ235b
	78Ag==
Received: by 10.68.191.201 with SMTP id ha9mr46612011pbc.75.1338904193234;
	Tue, 05 Jun 2012 06:49:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.201.74 with HTTP; Tue, 5 Jun 2012 06:49:33 -0700 (PDT)
From: =?UTF-8?B?6Z+p5L2z6aqP?= 
Date: Tue, 5 Jun 2012 21:49:33 +0800
Message-ID: 
To: xen-users 
Subject: [Xen-users] [xen-users] Xen detects duplicated device for SLES 11
	DomU
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi all,

I installed a HVM DomU with SLES 11 on Xen 3.4.3.
If you enter this DomU, you will find both sda and hda after "fdisk -l".
Actually they are the same device with identical UUID.
It works well for both CentOS and Debian DomUs.

Do you know how to fix that on SLES 11?
Any idea would be appreciated!

Regards,
Cecil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 13:51:31 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 13:51: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 1Sbu90-0002Of-NE; Tue, 05 Jun 2012 13:49:58 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbu8z-0002Oa-JA
	for xen-users@lists.xensource.com; Tue, 05 Jun 2012 13:49:57 +0000
Received: from [85.158.139.83:37739] by server-3.bemta-5.messagelabs.com id
	D4/E2-17554-48E0ECF4; Tue, 05 Jun 2012 13:49:56 +0000
X-Env-Sender: cecil.hanjj@gmail.com
X-Msg-Ref: server-12.tower-182.messagelabs.com!1338904193!32072007!1
X-Originating-IP: [209.85.160.43]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17447 invoked from network); 5 Jun 2012 13:49:55 -0000
Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com)
	(209.85.160.43)
	by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 13:49:55 -0000
Received: by pbcwz7 with SMTP id wz7so8544556pbc.30
	for ;
	Tue, 05 Jun 2012 06:49:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=zXm1OE0eNSnrF/g4TTZd2J6gB/Kx0aZzj5GeoF8i/C8=;
	b=HSZTIKV7lQFA+sTnZ28mhjhaUjE8oo7yjpWgwi4GjHbhlu2d44NRflQOvoC98tfeUc
	bY+1xLOuWbbByqJWJQTbm14pfjhcCLEeBwF43ijrqezb+AgubOmXmRgvVJxWGuXK9wfk
	9rO/y48p2oqg8JkODc4OqFbh2RRs/E7fAaRWqNsCD15AKQCc0pUhKoQ9ETrkN9vSX5Jr
	d2op5TMrD+GMUVAj8WXQR/NakUqqQ0fd4ZHRoiSgeo9C/v/w8R5Smit7MMWvAkDxX/yu
	p1Zojk8LU5H4QcprYACD8EQ9f88MsUiQMmryJv0EfQR2qi/sHVFn8CurrBTaC6AQ235b
	78Ag==
Received: by 10.68.191.201 with SMTP id ha9mr46612011pbc.75.1338904193234;
	Tue, 05 Jun 2012 06:49:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.201.74 with HTTP; Tue, 5 Jun 2012 06:49:33 -0700 (PDT)
From: =?UTF-8?B?6Z+p5L2z6aqP?= 
Date: Tue, 5 Jun 2012 21:49:33 +0800
Message-ID: 
To: xen-users 
Subject: [Xen-users] [xen-users] Xen detects duplicated device for SLES 11
	DomU
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi all,

I installed a HVM DomU with SLES 11 on Xen 3.4.3.
If you enter this DomU, you will find both sda and hda after "fdisk -l".
Actually they are the same device with identical UUID.
It works well for both CentOS and Debian DomUs.

Do you know how to fix that on SLES 11?
Any idea would be appreciated!

Regards,
Cecil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 15:19:18 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 15:19: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 1SbvVs-00034Q-43; Tue, 05 Jun 2012 15:17:40 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbvVq-00034K-5d
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 15:17:38 +0000
Received: from [85.158.139.83:44587] by server-8.bemta-5.messagelabs.com id
	B1/6A-02058-1132ECF4; Tue, 05 Jun 2012 15:17:37 +0000
X-Env-Sender: kristian@hagsted.dk
X-Msg-Ref: server-5.tower-182.messagelabs.com!1338909456!32143395!1
X-Originating-IP: [80.160.77.114]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogODAuMTYwLjc3LjExNCA9PiAyNTczODI=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16193 invoked from network); 5 Jun 2012 15:17:36 -0000
Received: from pasmtpa.tele.dk (HELO pasmtpA.tele.dk) (80.160.77.114)
	by server-5.tower-182.messagelabs.com with SMTP;
	5 Jun 2012 15:17:36 -0000
Received: from hagsted.dk (unknown [2.108.99.186])
	by pasmtpA.tele.dk (Postfix) with ESMTP id A2716800275;
	Tue,  5 Jun 2012 17:17:35 +0200 (CEST)
Received: from Hagsted-Aserver.hagsted.dk ([192.168.1.98]) by hagsted-aserver
	([192.168.1.98]) with mapi; Tue, 5 Jun 2012 16:34:34 +0200
From: Kristian Hagsted Rasmussen 
To: "cyberhawk001@gmail.com" ,
	"xen-users@lists.xen.org" 
Date: Tue, 5 Jun 2012 16:34:33 +0200
Thread-Topic: [Xen-users] Xen unstable fails to build on ubutnu 12.04
Thread-Index: Ac1DEk6l4seIZFi2Rq+X/pMZH3jMtQAG79SA
Message-ID: <56EBEBACEA93434C80F27BB249CB6776019294A7A271@hagsted-aserver>
References: 
	<4FCDF96F.2050007@gmail.com>
In-Reply-To: <4FCDF96F.2050007@gmail.com>
Accept-Language: da-DK
Content-Language: da-DK
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-antivirus-status: Clean
x-antivirus: avast!
acceptlanguage: da-DK
MIME-Version: 1.0
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SGkNCg0KSSBoYWQgdGhpcyBwcm9ibGVtLCBhbmQgZm91bmQgYSBwYXRjaCBoZXJlLiBodHRwOi8v
bGlzdHMuZ251Lm9yZy9hcmNoaXZlL2h0bWwvcWVtdS1kZXZlbC8yMDEyLTAyL21zZzAzNDYwLmh0
bWwNCldoaWNoIEkgYXBwbGllZCBtYW51YWxseS4gSXQgc2VlbXMgdG8gYmUgYSBwcm9ibGVtIHdp
dGggdGhlIGdjYyB2ZXJzaW9uLg0KDQpCZXN0IHJlZ2FyZHMgS3Jpc3RpYW4NCg0KLS0tLS1PcHJp
bmRlbGlnIG1lZGRlbGVsc2UtLS0tLQ0KRnJhOiB4ZW4tdXNlcnMtYm91bmNlc0BsaXN0cy54ZW4u
b3JnIFttYWlsdG86eGVuLXVzZXJzLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gUMOlIHZlZ25lIGFm
IGN5YmVyaGF3azAwMUBnbWFpbC5jb20NClNlbmR0OiA1LiBqdW5pIDIwMTIgMTQ6MjANClRpbDog
eGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcNCkVtbmU6IFJlOiBbWGVuLXVzZXJzXSBYZW4gdW5zdGFi
bGUgZmFpbHMgdG8gYnVpbGQgb24gdWJ1dG51IDEyLjA0DQoNCmh1bW0sIHdlbGwgdGhhdCBzdWNr
cy4gSSBrbm93IGNvbXBpbGluZyBjaGFuZ2VzZXQgMjUzOTIgd29ya3MgZm9yIG1lLCB3aXRoIHRo
ZSBwYWNrYWdlcyBhbmQgaW5zdHJ1Y3Rpb25zIGkgZGVzY3JpYmVkLCBpIGhhdmUgY29tcGlsZWQg
aXQgc2V2ZXJhbCB0aW1lcyBub3cuIEkga25vdyB0aGUgbWFpbiByZWFzb24gd2h5IHRoZSBsYXRl
ciBjaGFuZ2VzdHMgd29uJ3QgY29tcGlsZSBpcyBiZWNhdXNlIG9mIHRoZSBkaWZmZXJlbnQgR0ND
IHZlcnNpb24gc2VlbSB0byBkbyBkaWZmZXJlbnQgZW5vdWdoIHRvIGZhaWwsIFNPIG1heWJlIFVi
dW50dSBoYXMgYSBkaWZmZXJlbnQgc3Vic2V0IG9mIEdDQy4gSSBoYXZlIG5vIGlkZWEuDQoNCldl
bGwsIGlmIGl0IHdhcyBubyB0cm91YmxlIGZvciB5b3UsIG1heWJlIHRyeSB0byBpbnN0YWxsIERl
YmlhbiBXaGVlenkgYW5kIHRyeSB0byBjb21waWxlIGFnYWluLiBPdGhlcndpc2UgaSBjb3VsZCBh
bHdheXMgc2VuZCB5b3UgdGhlIFhlbiA0LjINCnJldi0yNTM5MiBjb21waWxlZCBERUIgcGFja2Fn
ZSBhbmQgeW91IGNhbiBqdXN0IGluc3RhbGwgdGhhdCwgQlVUIHRoYXQgd291bGRuJ3Qgc29sdmUg
eW91ciBwcm9ibGVtIGlmIHlvdSB3YW50ZWQgdG8gY29tcGlsZSBpdCBsYXRlciBvbi4NCg0KDQo+
IEhtbSBzYW1lIGVycm9yOg0KPg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4gSW4gZnVuY3Rp
b24gw6JoYW5kbGVfdXBkYXRlX2ZpbGVfY3JlZMOiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3
MDo1ODoNCj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQ0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4gbm90ZTog
ZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNo
IA0KPiBmdW5jdGlvbiBpdCBhcHBlYXJzIGluDQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0KPiBJ
biBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2
LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4Nzoz
NDoNCj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0
aGlzIGZ1bmN0aW9uKQ0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3Fl
bXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4gSW4gZnVuY3Rpb24gw6Jo
YW5kbGVfc3ltbGlua8OiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6DQo+IGVycm9y
OiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlv
bikNCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIv
aHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xpbmvD
ojoNCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIv
aHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzM3OjQ1Og0KPiBlcnJvcjogw6JBVF9FTVBUWV9Q
QVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pDQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOg0KPiBJbiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOg0KPiAvcm9vdC94
ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzozNzM6NTg6DQo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xh
cmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4gbWFrZVs0XTogKioqIFs5cGZzL3Zp
cnRpby05cC1oYW5kbGUub10gRXJyb3IgMQ0KPiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5m
aW5pc2hlZCBqb2JzLi4uLg0KPiAgICBDQyAgICBobXAubw0KPiAgICBDQyAgICBsaWJkaXMvaTM4
Ni1kaXMubw0KPiAgICBMSU5LICBxZW11LWdhDQo+ICAgIExJTksgIHFlbXUtbmJkDQo+ICAgIExJ
TksgIHFlbXUtaW1nDQo+ICAgIExJTksgIHFlbXUtaW8NCj4gbWFrZVszXTogKioqIFtzdWJkaXIt
bGliaHc2NF0gRXJyb3IgMg0KPiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9yeQ0KPiBgL3Jvb3Qv
eGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXItcmVtb3RlJw0KPiBt
YWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUteGVuLWRpcl0gRXJyb3IgMg0KPiBtYWtl
WzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90
b29scycNCj4gbWFrZVsxXTogKioqIFtzdWJkaXJzLWluc3RhbGxdIEVycm9yIDINCj4gbWFrZVsx
XTogTGVhdmluZyBkaXJlY3RvcnkgYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMnDQo+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMg0KPg0KPiBJIGhhZCBtb3N0
IG9mIHRoZSBwYWNrYWdzLCBJIHJhbiAiYXB0LWdldCBidWlsZC1kZXAgeGVuIiBmcm9tOg0KPiBo
dHRwOi8vd2lraS54ZW4ub3JnL3dpa2kvQ29tcGlsaW5nX1hlbl9Gcm9tX1NvdXJjZQ0KPg0KPiBC
dXQgaXQgc3RpbGwgZXJyb3JzIG9uIHRoZSB2aXJ0aW8gZmlsZS4gSSBoYWQgYWxzbyByZWFkIHRo
YXQgdGhlc2UgDQo+IGVycm9ycyBoYWQgdG8gZGlmZmVyZW50IHdpdGggZGlmZmVyZW50IGxpYnJh
cnkvZ2NjIHZlcnNpb25zLiBNYXliZSANCj4gd2hlZXp5IGp1c3QgaGFzIG5ld2VyL2RpZmZlcmVu
dCB2ZXJzaW9ucyBvZiB0aG9zZSBiaW5hcmllcy9saWJzPw0KPg0KPiAtLVdpbGwNCj4NCj4NCj4+
Pj4gICAwNi8wNC8xMiAxMTo0NSBBTT4+Pg0KPiBXRUxMLCBhY3R1YWxseSBOTyBuZWVkIHRvIGlu
c3RhbGwgV2hlZXp5LiBJIGFtIHZlcnkgc3VyZSB5b3UgY2FuIGdldCANCj4gaXQgd29ya2luZyBq
dXN0IGFzIGVhc2lseSB3aXRoIFVidW50dS4NCj4NCj4gVGhlIG90aGVyIHRoaW5nIGkgZm9yZ290
IHRvIG1lbnRpb24gaXMgeW91IGhhdmUgdG8gaGF2ZSBhbGwgb2YgdGhlIA0KPiByZXF1aXJlZCBw
YWNrYWdlcyBpbnN0YWxsZWQgYmVmb3JlIHlvdSBjYW4gY29tcGlsZSBYZW4uIEkgdGhpbmsgeW91
IA0KPiBhcmUganVzdCBtaXNzaW5nIGEgYnVuY2ggb2YgZGVwZW5kZW50IHBhY2thZ2VzLiBUaGUg
cGFja2FnZXMgaSB1c2UgYW5kIA0KPiBoYXZlIGluc3RhbGxlZCBhcmUgYXMgZm9sbG93czoNCj4N
Cj4gc3VkbyBhcHQtZ2V0IGluc3RhbGwgd2dldCB0YXIgYnppcDIgYnVpbGQtZXNzZW50aWFsIGxp
Ym5jdXJzZXM1LWRldiANCj4ga2VybmVsLXBhY2thZ2UgZmFrZXJvb3QgYmNjIGdjYyBzc2ggYnJp
ZGdlLXV0aWxzIHB5dGhvbi1kZXYgdXVpZC1kZXYgDQo+IGxpYmdsaWIyLjAtZGV2IGxpYnlhamwt
ZGV2IGxpYmFpby1kZXYgZ2NjLW11bHRpbGliIGlhc2wgbGlicGNpLWRldiANCj4gZmxleCBiaXNv
biBxdDQtZGV2LXRvb2xzIHBhdGNoIG9jYW1sLWZpbmRsaWIgbGlic2RsMS4yLWRldg0KPg0KPiBH
cmFudGVkIHNvbWUgb2YgdGhlIGFib3ZlIHBhY2thZ2VzIGFyZSBtb3JlIGltcG9ydGFudCBmb3Ig
Y29tcGlsaW5nIA0KPiB0aGUga2VybmVsLg0KPg0KPiBTTywgYXMgbG9uZyBhcyB5b3UgaGF2ZSBh
bGwgcmVxdWlyZWQgcGFja2FnZXMgYW5kIGZvbGxvdyB0aGUgDQo+IGluc3RydWN0aW9ucyBiZWZv
cmUgYWJvdXQgZ2V0dGluZyBhbmQgY29tcGlsaW5nIFhlbiA0LjIgcmV2aXNpb24gDQo+IDI1Mzky
LCBpdCBzaG91bGQgYmUgZmluZSwgbm8gbWF0dGVyIGlmIHlvdSBhcmUgdXNpbmcgRGViaWFuIG9y
IFVidW50dS4gDQo+IFVidW50dSBob3dldmVyICJtaWdodCIgbmVlZCBtb3JlIHBhY2thZ2VzLCBu
b3Qgc3VyZSwgIGkgaGF2ZSBub3QgDQo+IGNvbXBpbGVkIFhlbiB1bmRlciBVYnVudHUgeWV0Lg0K
Pg0KPg0KPg0KPiBPbiA2LzQvMjAxMiAxMjo0MyBQTSwgV2lsbCBNY0Rlcm1vdHQgd3JvdGU6DQo+
PiBEYXJuLCBtYWRlIGl0IGZhcnRoZXIgYnV0IG5vdyBJIGdldCB0aGlzOg0KPj4NCj4+IENDICAg
IGxpYmh3NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubw0KPj4gICAgIENDICAgIGxpYmh3NjQvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLm8NCj4+ICAgICBDQyAgICBxZW11LWNoYXIubw0KPj4NCj4gL3Jv
b3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92
aXJ0aW8tOXAtaGFuZGxlLmM6DQo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9j
cmVkw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4+IGVycm9yOiDDokFU
X0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+
DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3
LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjcwOjU4Og0KPj4gbm90ZTogZWFjaCB1bmRlY2xhcmVk
IGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNoDQo+IGZ1bmN0aW9uDQo+
PiBpdCBhcHBlYXJzIGluDQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+IEluIGZ1bmN0
aW9uIMOiaGFuZGxlX2xzdGF0w6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1
MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4NzozNDoN
Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhp
cyBmdW5jdGlvbikNCj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0KPj4gSW4gZnVuY3Rpb24g
w6JoYW5kbGVfc3ltbGlua8OiOg0KPj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5
Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOg0K
Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlz
IGZ1bmN0aW9uKQ0KPj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+PiBJbiBmdW5jdGlvbiDD
omhhbmRsZV9saW5rw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMzc6NDU6DQo+PiBl
cnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu
Y3Rpb24pDQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+IEluIGZ1bmN0aW9uIMOiaGFu
ZGxlX2Nob3duw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozNzM6NTg6DQo+PiBlcnJv
cjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rp
b24pDQo+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxDQo+
PiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5maW5pc2hlZCBqb2JzLi4uLg0KPj4gICAgIEND
ICAgIHNhdmV2bS5vDQo+PiAgICAgQ0MgICAgbXNtb3VzZS5vDQo+PiAgICAgQ0MgICAgcHMyLm8N
Cj4+IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDINCj4+IG1ha2VbM106ICoq
KiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uDQo+PiBtYWtlWzNdOiBMZWF2aW5nIGRp
cmVjdG9yeQ0KPj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14
ZW4tZGlyLXJlbW90ZScNCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4t
ZGlyXSBFcnJvciAyDQo+PiBtYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycNCj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1pbnN0
YWxsXSBFcnJvciAyDQo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycNCj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10g
RXJyb3IgMg0KPj4NCj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNoIGZv
ciB5b3VyIGNsZWFyIGluc3RydWN0aW9ucyEgSSANCj4+IHdpbGwgaW5zdGFsbCB3aGVlenkgdG9u
aWdodCBhbmQgdHJ5IHRoZSBidWlsZCBhZ2Fpbi4NCj4+DQo+PiAtLVdpbGwNCj4+DQo+Pj4+PiAg
ICAwNi8wNC8xMiA0OjU2IEFNPj4+DQo+PiBPbiA2LzQvMjAxMiAyOjU4IEFNLCBXaWxsIE1jRGVy
bW90dCB3cm90ZToNCj4+PiBJJ20gbm90IHN1cmUgd2hhdCB2ZXJzaW9uIChob3cgZG8gSSBjaGVj
az8pIGJ1dCBJIGp1c3QgY2xvbmVkIGZyb20NCj4+IHRoYXQNCj4+PiBVUkwgdG9kYXkuDQo+Pj4N
Cj4+PiAtLVdpbGwNCj4+IFdlbGwgdGhhbiB5b3UgcHJvYmFibHkgYWxyZWFkeSBoYXZlIHRoZSBs
YXRlc3QgcmV2aXNpb24uIFlvdSBjYW4gYWxzbyANCj4+IGNoZWNrIHdoYXQgcmV2aXNpb24geW91
ciBsb2NhbGx5IGNsb25lZCByZXBvc2l0b3J5IGlzIGF0IGJ5IGdvaW5nIHRvDQo+IHRoZQ0KPj4g
Zm9sZGVyIGFuZCBydW5uaW5nOg0KPj4NCj4+ICpjZCAgLi4veGVuLXVuc3RhYmxlLmhnDQo+PiBo
ZyBzdW1tYXJ5DQo+PiAqDQo+PiBBbmQgdGhhdCB3aWxsIHNob3cgeW91IGEgc3VtbWFyeSBvZiB0
aGUgbG9jYWwgbWVyY3VyaWFsIGNsb25lIGFuZCANCj4+IHNob3cgdGhlIGxhdGVzdCByZXZpc2lv
bnMgdGhhdCB3YXMgY2xvbmVkLg0KPj4NCj4+IFNPLCBhbnlob3csIGNvbXBpbGluZyB0aGUgWGVu
IDQuMi11bnN0YWJsZSBmcm9tIHRoZSBtZXJjdXJpYWwgaGFzIG5vdCANCj4+IGJlZW4gd29ya2lu
ZyB2ZXJ5IHdlbGwgZm9yIGEgZmV3IHdlZWtzIG5vdy4gSSBoYXZlIGFza2VkIHRoZSANCj4+IFhl
bi1kZXZlbCBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhlcmUgYXJlIGlzc3VlcyBh
bmQgDQo+PiBwcm9ibGVtcyB3aXRoIGRpZmZlcmVudCBHQ0MgY29tcGlsZXJzIEFORCB0aGUgWGVu
LWRldmVsIHRlYW0ga25vd3MgDQo+PiBhbGwgdGhhdCBhbmQgYXJlIHdvcmtpbmcgb24gZml4aW5n
IHRoYXQuDQo+Pg0KPj4gRm9yIG5vdywgdGhlIExBU1QgcmV2aXNpb24gaSB3YXMgYWJsZSB0byBj
b21waWxlIGFuZCBnZXQgcnVubmluZyB3YXMgDQo+PiAqInJldmlzaW9uIDI1MzkyKiIsIGJ1dCBl
dmVuIHRoYXQgd2FzIHBvc3NpYmx5IE9OTFkgaWYgeW91IHJlbW92ZSBvbmUgDQo+PiBwYXRjaC4g
WW91IGNhbiB0cnkgdG8gZG93bmxvYWQgYW5kIGNvbXBpbGUgVEhBVCB2ZXJzaW9uIGJ5IHJ1bm5p
bmcgDQo+PiB0aGUgZm9sbG93aW5nIGNvbW1hbmRzOg0KPj4NCj4+IF8qQ2xvbmluZyBYZW46Kl8N
Cj4+ICotIGNkIC9zb21lL2RpcmVjdG9yeS9pbi9ob21lDQo+PiAtIHJldj0yNTM5MiYmICAgaGcg
Y2xvbmUgLXIgJHJldg0KPj4gaHR0cDovL3hlbmJpdHMueGVuLm9yZy9oZy94ZW4tdW5zdGFibGUu
aGcvIHhlbi11bnN0YWJsZS5oZy1yZXYtJHtyZXZ9DQo+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTINCj4+IC0gaGcgYmFja291dCAtciAyNTM2NCoNCj4+DQo+PiBUaGlzIHdpbGwgY2xv
bmUgdGhlIHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbiANCj4+IDQu
Mi11bnN0YWJsZSByZXZpc2lvbiAyNTM5MiBpbnRvIHRoZSBmb2xkZXIgDQo+PiAiKnhlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIqIi4gUnVubmluZyB0aGUgY29tbWFuZCAiKmhnIGJhY2tvdXIgLXIg
DQo+PiAyNTM2NCoiIHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4g
SXQgc2VlbXMgdGhhdCANCj4+IHdpdGhvdXQgdGhhdCwgZXZlbiB0aGF0IHJldmlzaW9uIHdvbnQg
Y29tcGlsZS4NCj4+DQo+PiBfKkNvbXBpbGluZyBYZW46Kl8NCj4+IFRoYW4ganVzdCBzaW1wbHkg
cnVuIHRoZXNlIGNvbW1hbmRzIHRvIGNvbXBpbGUgWGVuLg0KPj4NCj4+ICotIGNkIHhlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIqDQo+PiAqLSAuL2NvbmZpZ3VyZQ0KPj4gLSBzdWRvIG1ha2UgLWo1
IHhlbiYmICAgc3VkbyBtYWtlIFRoZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdA0KPiBzdHJp
bmdzIHRvZ2V0aGVyIHRoZSA0IGNvbXBpbGluZyBjb21tYW5kcw0KPj4gdG8gcnVuIGFuZCB3aWxs
IGV4ZWN1dGUgb25lIGFmdGVyIHRoZSBvdGhlciBTTyB5b3UgZG9uJ3QgaGF2ZSB0byANCj4+IG1h
bnVhbGx5IHJ1biBlYWNoIGFuZCBldmVyeSBvbmUuIEFsc28sIEluIHRoZSBhYm92ZSAiKm1ha2Uq
IiANCj4+IGNvbW1hbmRzLCB1c2luZyB0aGUgIiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtl
IHRlbGxzIHRoZSBjb21waWxlIA0KPj4gdG8gdXNlIG1vcmUgdGhhbiBvbmUgY29yZSB0byBjb21w
aWxlIHdpdGguIEl0IHNwZWVkcyB1cCB0aGUgY29tcGlsaT4gIA0KPj4gaGF2ZSBhIG11bHRpLWNv
cmUgQ1BVLiBTTyBpbiBteSBjYXNlLCBpIGhhdmUgYSBRdWFkIENvcmUgQ1BVLCBzbyB0aGF0IA0K
Pj4gY29tbWFuZCBvcHRpb24gaXMgIiotajEgKyBudW1iZXIgb2YgQ1BVIGNvcmVzKiIuIFlvdSBj
YW4gbW9kaWZ5IG9yIHJlbW92ZSB0aGF0IGFzIHlvdSB3aXNoLg0KPj4NCj4+IFRoZSBhYm92ZSB3
aWxsIGFsc28gY3JlYXRlIGZvciB5b3UgYSBuaWNlIERFQiBwYWNrYWdlIGFmdGVyIGFsbCB0aGUg
DQo+PiBjb21waWxpbmcgaXMgZG9uZSwgaWYgeW91IGRvIG5vdCB3YW50IHRvIGNyZWF0ZSBhIERF
QiBwYWNrYWdlIGF0IHRoZQ0KPiBlbmQNCj4+IG9mIGl0IGFsbCwgdGhhbiBqdXN0IHJlbW92ZSB0
aGUgbGFzdCAiKiYmICAgc3VkbyBtYWtlIC1qNSBkZWIqIg0KPiBjb21tYW5kLg0KPj4gR3JhbnRl
ZCwgaSBhbSBydW5uaW5nIGFuZCBkb2luZyBhbGwgb2YgdGhpcyBvbiBEZWJpYW4gV2hlZXp5IEJV
VCBpDQo+IHRoZXJlDQo+PiBhcmVuJ3QgYW55IGRpZmZlcmVuY2VzIGluIGNvbXBpbGluZyBpdCBv
biBVYnVudHUgMTIuMDQuDQo+Pg0KPj4NCj4+DQo+Pg0KPj4+Pj4+ICAgICAwNi8wMy8xMiAyOjM0
IFBNPj4+DQo+Pj4gVGhlIGxhdGVzdCByZXZpc2lvbiBvZiBYZW4gNC4yLXVuc3RhYmxlIGlzICoy
NTQ1Mjo2YmVhNjNlNmM3ODAqIGF0DQo+IHRoZQ0KPj4+IGxpbmsgKmh0dHA6Ly94ZW5iaXRzLnhl
bi5vcmcvaGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YNCj4+IFhlbg0KPj4+
IDQuMi1VbnN0YWJsZSBhcmUgeW91IHRyeWluZyB0byBjb21waWxlPw0KPj4+DQo+Pj4NCj4+Pj4g
SGVsbG8sDQo+Pj4+DQo+Pj4+IEkgYW0gdHJ5aW5nIHRvIGNvbXBpbGUgeGVuIDQuMiB1bnN0YWJs
ZSBmcm9tIG1lcmN1cmlhbC4gSSBjYW4ndCBnZXQNCj4+PiBwYXN0DQo+Pj4+IHRoZSBtYWtlIHRv
b2xzIHN0ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6DQo+
Pj4+DQo+Pj4+IENDICAgIGxpYmh3NjQvOXBmcy9jb3hhdHRyLm8NCj4+Pj4gICAgICAgQ0MgICAg
bGliaHc2NC85cGZzL3ZpcnRpby05cC1zeW50aC5vDQo+Pj4+ICAgICAgIENDICAgIGxpYmh3NjQv
OXBmcy92aXJ0aW8tOXAtaGFuZGxlLm8NCj4+Pj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+PiBJbg0KPj4+PiBm
dW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6DQo+Pj4+DQo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
NzA6NTg6DQo+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+Pj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4+Pj4gbm90
ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBl
YWNoDQo+Pj4gZnVuY3Rpb24NCj4+Pj4gaXQgYXBwZWFycyBpbg0KPj4+PiAvcm9vdC94ZW4tdW5z
dGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0K
Pj4+IEluDQo+Pj4+IGZ1bmN0aW9uIMOiaGFuZGxlX2xzdGF0w6I6DQo+Pj4+DQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6ODc6MzQ6DQo+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJz
dCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+Pj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+PiBJbg0KPj4+PiBm
dW5jdGlvbiDDomhhbmRsZV9zeW1saW5rw6I6DQo+Pj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5o
Zy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOg0K
Pj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRo
aXMgZnVuY3Rpb24pDQo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+Pj4gSW4NCj4+Pj4gZnVuY3Rpb24gw6Jo
YW5kbGVfbGlua8OiOg0KPj4+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14
ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToNCj4+Pj4gZXJyb3I6IMOi
QVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQ0K
Pj4+PiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOg0KPj4+IEluDQo+Pj4+IGZ1bmN0aW9uIMOiaGFuZGxlX2Nob3duw6I6
DQo+Pj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzczOjU4Og0KPj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRI
w6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pDQo+Pj4+IG1ha2VbNF06
ICoqKiBbOXBmcy92aXJ0aW8tOXAtaGFuZGxlLm9dIEVycm9yIDENCj4+Pj4gbWFrZVszXTogKioq
IFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMg0KPj4+PiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9y
eQ0KPj4+PiBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci1yZW1vdGUn
DQo+Pj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJvciAy
DQo+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcv
dG9vbHMnDQo+Pj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1pbnN0YWxsXSBFcnJvciAyDQo+Pj4+
IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMn
DQo+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMg0KPj4+Pg0KPj4+PiBJIGFt
IHJ1bm5pbmcgdWJ1bnR1IDEyLjA0LCBrZXJuZWwgdmVyOiAzLjIuMC0yNC1nZW5lcmljDQo+Pj4+
DQo+Pj4+IEFueSBpZGVhcz8gSSBoYXZlIGdvb2dsZWQgZnVyaW91c2x5IGFuZCBmb3VuZCBzb21l
IHBlb3BsZSB0YWxraW5nDQo+Pj4gYWJvdXQNCj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOg0KPj4+PiBodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9x
ZW11LWt2bS8rYnVnLzkzMDE4MQ0KPj4+PiBCdXQgSSB3YXMgbm90IGFibGUgdG8gZmluZCB0aGUg
cGF0Y2gNCj4+Pj4NCj4+Pj4gVGhhbmtzIGluIGFkdmFuY2UhDQo+Pj4+DQo+Pj4+DQo+Pj4+DQo+
Pj4+IE1lcmN1cmlhbG0NCj4+Pj4NCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+Pj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdA0KPj4+PiBYZW4t
dXNlcnNAbGlzdHMueGVuLm9yZw0KPj4+PiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMN
Cj4+DQo+DQo+DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NClhlbi11c2VycyBtYWlsaW5nIGxpc3QNClhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQpo
dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxp
c3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Tue Jun 05 15:19:18 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 15:19: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 1SbvVs-00034Q-43; Tue, 05 Jun 2012 15:17:40 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbvVq-00034K-5d
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 15:17:38 +0000
Received: from [85.158.139.83:44587] by server-8.bemta-5.messagelabs.com id
	B1/6A-02058-1132ECF4; Tue, 05 Jun 2012 15:17:37 +0000
X-Env-Sender: kristian@hagsted.dk
X-Msg-Ref: server-5.tower-182.messagelabs.com!1338909456!32143395!1
X-Originating-IP: [80.160.77.114]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogODAuMTYwLjc3LjExNCA9PiAyNTczODI=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16193 invoked from network); 5 Jun 2012 15:17:36 -0000
Received: from pasmtpa.tele.dk (HELO pasmtpA.tele.dk) (80.160.77.114)
	by server-5.tower-182.messagelabs.com with SMTP;
	5 Jun 2012 15:17:36 -0000
Received: from hagsted.dk (unknown [2.108.99.186])
	by pasmtpA.tele.dk (Postfix) with ESMTP id A2716800275;
	Tue,  5 Jun 2012 17:17:35 +0200 (CEST)
Received: from Hagsted-Aserver.hagsted.dk ([192.168.1.98]) by hagsted-aserver
	([192.168.1.98]) with mapi; Tue, 5 Jun 2012 16:34:34 +0200
From: Kristian Hagsted Rasmussen 
To: "cyberhawk001@gmail.com" ,
	"xen-users@lists.xen.org" 
Date: Tue, 5 Jun 2012 16:34:33 +0200
Thread-Topic: [Xen-users] Xen unstable fails to build on ubutnu 12.04
Thread-Index: Ac1DEk6l4seIZFi2Rq+X/pMZH3jMtQAG79SA
Message-ID: <56EBEBACEA93434C80F27BB249CB6776019294A7A271@hagsted-aserver>
References: 
	<4FCDF96F.2050007@gmail.com>
In-Reply-To: <4FCDF96F.2050007@gmail.com>
Accept-Language: da-DK
Content-Language: da-DK
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-antivirus-status: Clean
x-antivirus: avast!
acceptlanguage: da-DK
MIME-Version: 1.0
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SGkNCg0KSSBoYWQgdGhpcyBwcm9ibGVtLCBhbmQgZm91bmQgYSBwYXRjaCBoZXJlLiBodHRwOi8v
bGlzdHMuZ251Lm9yZy9hcmNoaXZlL2h0bWwvcWVtdS1kZXZlbC8yMDEyLTAyL21zZzAzNDYwLmh0
bWwNCldoaWNoIEkgYXBwbGllZCBtYW51YWxseS4gSXQgc2VlbXMgdG8gYmUgYSBwcm9ibGVtIHdp
dGggdGhlIGdjYyB2ZXJzaW9uLg0KDQpCZXN0IHJlZ2FyZHMgS3Jpc3RpYW4NCg0KLS0tLS1PcHJp
bmRlbGlnIG1lZGRlbGVsc2UtLS0tLQ0KRnJhOiB4ZW4tdXNlcnMtYm91bmNlc0BsaXN0cy54ZW4u
b3JnIFttYWlsdG86eGVuLXVzZXJzLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gUMOlIHZlZ25lIGFm
IGN5YmVyaGF3azAwMUBnbWFpbC5jb20NClNlbmR0OiA1LiBqdW5pIDIwMTIgMTQ6MjANClRpbDog
eGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcNCkVtbmU6IFJlOiBbWGVuLXVzZXJzXSBYZW4gdW5zdGFi
bGUgZmFpbHMgdG8gYnVpbGQgb24gdWJ1dG51IDEyLjA0DQoNCmh1bW0sIHdlbGwgdGhhdCBzdWNr
cy4gSSBrbm93IGNvbXBpbGluZyBjaGFuZ2VzZXQgMjUzOTIgd29ya3MgZm9yIG1lLCB3aXRoIHRo
ZSBwYWNrYWdlcyBhbmQgaW5zdHJ1Y3Rpb25zIGkgZGVzY3JpYmVkLCBpIGhhdmUgY29tcGlsZWQg
aXQgc2V2ZXJhbCB0aW1lcyBub3cuIEkga25vdyB0aGUgbWFpbiByZWFzb24gd2h5IHRoZSBsYXRl
ciBjaGFuZ2VzdHMgd29uJ3QgY29tcGlsZSBpcyBiZWNhdXNlIG9mIHRoZSBkaWZmZXJlbnQgR0ND
IHZlcnNpb24gc2VlbSB0byBkbyBkaWZmZXJlbnQgZW5vdWdoIHRvIGZhaWwsIFNPIG1heWJlIFVi
dW50dSBoYXMgYSBkaWZmZXJlbnQgc3Vic2V0IG9mIEdDQy4gSSBoYXZlIG5vIGlkZWEuDQoNCldl
bGwsIGlmIGl0IHdhcyBubyB0cm91YmxlIGZvciB5b3UsIG1heWJlIHRyeSB0byBpbnN0YWxsIERl
YmlhbiBXaGVlenkgYW5kIHRyeSB0byBjb21waWxlIGFnYWluLiBPdGhlcndpc2UgaSBjb3VsZCBh
bHdheXMgc2VuZCB5b3UgdGhlIFhlbiA0LjINCnJldi0yNTM5MiBjb21waWxlZCBERUIgcGFja2Fn
ZSBhbmQgeW91IGNhbiBqdXN0IGluc3RhbGwgdGhhdCwgQlVUIHRoYXQgd291bGRuJ3Qgc29sdmUg
eW91ciBwcm9ibGVtIGlmIHlvdSB3YW50ZWQgdG8gY29tcGlsZSBpdCBsYXRlciBvbi4NCg0KDQo+
IEhtbSBzYW1lIGVycm9yOg0KPg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4gSW4gZnVuY3Rp
b24gw6JoYW5kbGVfdXBkYXRlX2ZpbGVfY3JlZMOiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3
MDo1ODoNCj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQ0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4gbm90ZTog
ZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNo
IA0KPiBmdW5jdGlvbiBpdCBhcHBlYXJzIGluDQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0KPiBJ
biBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2
LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4Nzoz
NDoNCj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0
aGlzIGZ1bmN0aW9uKQ0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3Fl
bXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4gSW4gZnVuY3Rpb24gw6Jo
YW5kbGVfc3ltbGlua8OiOg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6DQo+IGVycm9y
OiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlv
bikNCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIv
aHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+IEluIGZ1bmN0aW9uIMOiaGFuZGxlX2xpbmvD
ojoNCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIv
aHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzM3OjQ1Og0KPiBlcnJvcjogw6JBVF9FTVBUWV9Q
QVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pDQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlv
LTlwLWhhbmRsZS5jOg0KPiBJbiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOg0KPiAvcm9vdC94
ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzozNzM6NTg6DQo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xh
cmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4gbWFrZVs0XTogKioqIFs5cGZzL3Zp
cnRpby05cC1oYW5kbGUub10gRXJyb3IgMQ0KPiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5m
aW5pc2hlZCBqb2JzLi4uLg0KPiAgICBDQyAgICBobXAubw0KPiAgICBDQyAgICBsaWJkaXMvaTM4
Ni1kaXMubw0KPiAgICBMSU5LICBxZW11LWdhDQo+ICAgIExJTksgIHFlbXUtbmJkDQo+ICAgIExJ
TksgIHFlbXUtaW1nDQo+ICAgIExJTksgIHFlbXUtaW8NCj4gbWFrZVszXTogKioqIFtzdWJkaXIt
bGliaHc2NF0gRXJyb3IgMg0KPiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9yeQ0KPiBgL3Jvb3Qv
eGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXItcmVtb3RlJw0KPiBt
YWtlWzJdOiAqKiogW3N1YmRpci1pbnN0YWxsLXFlbXUteGVuLWRpcl0gRXJyb3IgMg0KPiBtYWtl
WzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90
b29scycNCj4gbWFrZVsxXTogKioqIFtzdWJkaXJzLWluc3RhbGxdIEVycm9yIDINCj4gbWFrZVsx
XTogTGVhdmluZyBkaXJlY3RvcnkgYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMnDQo+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMg0KPg0KPiBJIGhhZCBtb3N0
IG9mIHRoZSBwYWNrYWdzLCBJIHJhbiAiYXB0LWdldCBidWlsZC1kZXAgeGVuIiBmcm9tOg0KPiBo
dHRwOi8vd2lraS54ZW4ub3JnL3dpa2kvQ29tcGlsaW5nX1hlbl9Gcm9tX1NvdXJjZQ0KPg0KPiBC
dXQgaXQgc3RpbGwgZXJyb3JzIG9uIHRoZSB2aXJ0aW8gZmlsZS4gSSBoYWQgYWxzbyByZWFkIHRo
YXQgdGhlc2UgDQo+IGVycm9ycyBoYWQgdG8gZGlmZmVyZW50IHdpdGggZGlmZmVyZW50IGxpYnJh
cnkvZ2NjIHZlcnNpb25zLiBNYXliZSANCj4gd2hlZXp5IGp1c3QgaGFzIG5ld2VyL2RpZmZlcmVu
dCB2ZXJzaW9ucyBvZiB0aG9zZSBiaW5hcmllcy9saWJzPw0KPg0KPiAtLVdpbGwNCj4NCj4NCj4+
Pj4gICAwNi8wNC8xMiAxMTo0NSBBTT4+Pg0KPiBXRUxMLCBhY3R1YWxseSBOTyBuZWVkIHRvIGlu
c3RhbGwgV2hlZXp5LiBJIGFtIHZlcnkgc3VyZSB5b3UgY2FuIGdldCANCj4gaXQgd29ya2luZyBq
dXN0IGFzIGVhc2lseSB3aXRoIFVidW50dS4NCj4NCj4gVGhlIG90aGVyIHRoaW5nIGkgZm9yZ290
IHRvIG1lbnRpb24gaXMgeW91IGhhdmUgdG8gaGF2ZSBhbGwgb2YgdGhlIA0KPiByZXF1aXJlZCBw
YWNrYWdlcyBpbnN0YWxsZWQgYmVmb3JlIHlvdSBjYW4gY29tcGlsZSBYZW4uIEkgdGhpbmsgeW91
IA0KPiBhcmUganVzdCBtaXNzaW5nIGEgYnVuY2ggb2YgZGVwZW5kZW50IHBhY2thZ2VzLiBUaGUg
cGFja2FnZXMgaSB1c2UgYW5kIA0KPiBoYXZlIGluc3RhbGxlZCBhcmUgYXMgZm9sbG93czoNCj4N
Cj4gc3VkbyBhcHQtZ2V0IGluc3RhbGwgd2dldCB0YXIgYnppcDIgYnVpbGQtZXNzZW50aWFsIGxp
Ym5jdXJzZXM1LWRldiANCj4ga2VybmVsLXBhY2thZ2UgZmFrZXJvb3QgYmNjIGdjYyBzc2ggYnJp
ZGdlLXV0aWxzIHB5dGhvbi1kZXYgdXVpZC1kZXYgDQo+IGxpYmdsaWIyLjAtZGV2IGxpYnlhamwt
ZGV2IGxpYmFpby1kZXYgZ2NjLW11bHRpbGliIGlhc2wgbGlicGNpLWRldiANCj4gZmxleCBiaXNv
biBxdDQtZGV2LXRvb2xzIHBhdGNoIG9jYW1sLWZpbmRsaWIgbGlic2RsMS4yLWRldg0KPg0KPiBH
cmFudGVkIHNvbWUgb2YgdGhlIGFib3ZlIHBhY2thZ2VzIGFyZSBtb3JlIGltcG9ydGFudCBmb3Ig
Y29tcGlsaW5nIA0KPiB0aGUga2VybmVsLg0KPg0KPiBTTywgYXMgbG9uZyBhcyB5b3UgaGF2ZSBh
bGwgcmVxdWlyZWQgcGFja2FnZXMgYW5kIGZvbGxvdyB0aGUgDQo+IGluc3RydWN0aW9ucyBiZWZv
cmUgYWJvdXQgZ2V0dGluZyBhbmQgY29tcGlsaW5nIFhlbiA0LjIgcmV2aXNpb24gDQo+IDI1Mzky
LCBpdCBzaG91bGQgYmUgZmluZSwgbm8gbWF0dGVyIGlmIHlvdSBhcmUgdXNpbmcgRGViaWFuIG9y
IFVidW50dS4gDQo+IFVidW50dSBob3dldmVyICJtaWdodCIgbmVlZCBtb3JlIHBhY2thZ2VzLCBu
b3Qgc3VyZSwgIGkgaGF2ZSBub3QgDQo+IGNvbXBpbGVkIFhlbiB1bmRlciBVYnVudHUgeWV0Lg0K
Pg0KPg0KPg0KPiBPbiA2LzQvMjAxMiAxMjo0MyBQTSwgV2lsbCBNY0Rlcm1vdHQgd3JvdGU6DQo+
PiBEYXJuLCBtYWRlIGl0IGZhcnRoZXIgYnV0IG5vdyBJIGdldCB0aGlzOg0KPj4NCj4+IENDICAg
IGxpYmh3NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubw0KPj4gICAgIENDICAgIGxpYmh3NjQvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLm8NCj4+ICAgICBDQyAgICBxZW11LWNoYXIubw0KPj4NCj4gL3Jv
b3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92
aXJ0aW8tOXAtaGFuZGxlLmM6DQo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9j
cmVkw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4+IGVycm9yOiDDokFU
X0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+
DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3
LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjcwOjU4Og0KPj4gbm90ZTogZWFjaCB1bmRlY2xhcmVk
IGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNoDQo+IGZ1bmN0aW9uDQo+
PiBpdCBhcHBlYXJzIGluDQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+IEluIGZ1bmN0
aW9uIMOiaGFuZGxlX2xzdGF0w6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1
MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4NzozNDoN
Cj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhp
cyBmdW5jdGlvbikNCj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0KPj4gSW4gZnVuY3Rpb24g
w6JoYW5kbGVfc3ltbGlua8OiOg0KPj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5
Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOg0K
Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlz
IGZ1bmN0aW9uKQ0KPj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+PiBJbiBmdW5jdGlvbiDD
omhhbmRsZV9saW5rw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMzc6NDU6DQo+PiBl
cnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu
Y3Rpb24pDQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUt
eGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+IEluIGZ1bmN0aW9uIMOiaGFu
ZGxlX2Nob3duw6I6DQo+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozNzM6NTg6DQo+PiBlcnJv
cjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rp
b24pDQo+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxDQo+
PiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5maW5pc2hlZCBqb2JzLi4uLg0KPj4gICAgIEND
ICAgIHNhdmV2bS5vDQo+PiAgICAgQ0MgICAgbXNtb3VzZS5vDQo+PiAgICAgQ0MgICAgcHMyLm8N
Cj4+IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDINCj4+IG1ha2VbM106ICoq
KiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uDQo+PiBtYWtlWzNdOiBMZWF2aW5nIGRp
cmVjdG9yeQ0KPj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14
ZW4tZGlyLXJlbW90ZScNCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4t
ZGlyXSBFcnJvciAyDQo+PiBtYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycNCj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1pbnN0
YWxsXSBFcnJvciAyDQo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVu
c3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycNCj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10g
RXJyb3IgMg0KPj4NCj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNoIGZv
ciB5b3VyIGNsZWFyIGluc3RydWN0aW9ucyEgSSANCj4+IHdpbGwgaW5zdGFsbCB3aGVlenkgdG9u
aWdodCBhbmQgdHJ5IHRoZSBidWlsZCBhZ2Fpbi4NCj4+DQo+PiAtLVdpbGwNCj4+DQo+Pj4+PiAg
ICAwNi8wNC8xMiA0OjU2IEFNPj4+DQo+PiBPbiA2LzQvMjAxMiAyOjU4IEFNLCBXaWxsIE1jRGVy
bW90dCB3cm90ZToNCj4+PiBJJ20gbm90IHN1cmUgd2hhdCB2ZXJzaW9uIChob3cgZG8gSSBjaGVj
az8pIGJ1dCBJIGp1c3QgY2xvbmVkIGZyb20NCj4+IHRoYXQNCj4+PiBVUkwgdG9kYXkuDQo+Pj4N
Cj4+PiAtLVdpbGwNCj4+IFdlbGwgdGhhbiB5b3UgcHJvYmFibHkgYWxyZWFkeSBoYXZlIHRoZSBs
YXRlc3QgcmV2aXNpb24uIFlvdSBjYW4gYWxzbyANCj4+IGNoZWNrIHdoYXQgcmV2aXNpb24geW91
ciBsb2NhbGx5IGNsb25lZCByZXBvc2l0b3J5IGlzIGF0IGJ5IGdvaW5nIHRvDQo+IHRoZQ0KPj4g
Zm9sZGVyIGFuZCBydW5uaW5nOg0KPj4NCj4+ICpjZCAgLi4veGVuLXVuc3RhYmxlLmhnDQo+PiBo
ZyBzdW1tYXJ5DQo+PiAqDQo+PiBBbmQgdGhhdCB3aWxsIHNob3cgeW91IGEgc3VtbWFyeSBvZiB0
aGUgbG9jYWwgbWVyY3VyaWFsIGNsb25lIGFuZCANCj4+IHNob3cgdGhlIGxhdGVzdCByZXZpc2lv
bnMgdGhhdCB3YXMgY2xvbmVkLg0KPj4NCj4+IFNPLCBhbnlob3csIGNvbXBpbGluZyB0aGUgWGVu
IDQuMi11bnN0YWJsZSBmcm9tIHRoZSBtZXJjdXJpYWwgaGFzIG5vdCANCj4+IGJlZW4gd29ya2lu
ZyB2ZXJ5IHdlbGwgZm9yIGEgZmV3IHdlZWtzIG5vdy4gSSBoYXZlIGFza2VkIHRoZSANCj4+IFhl
bi1kZXZlbCBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhlcmUgYXJlIGlzc3VlcyBh
bmQgDQo+PiBwcm9ibGVtcyB3aXRoIGRpZmZlcmVudCBHQ0MgY29tcGlsZXJzIEFORCB0aGUgWGVu
LWRldmVsIHRlYW0ga25vd3MgDQo+PiBhbGwgdGhhdCBhbmQgYXJlIHdvcmtpbmcgb24gZml4aW5n
IHRoYXQuDQo+Pg0KPj4gRm9yIG5vdywgdGhlIExBU1QgcmV2aXNpb24gaSB3YXMgYWJsZSB0byBj
b21waWxlIGFuZCBnZXQgcnVubmluZyB3YXMgDQo+PiAqInJldmlzaW9uIDI1MzkyKiIsIGJ1dCBl
dmVuIHRoYXQgd2FzIHBvc3NpYmx5IE9OTFkgaWYgeW91IHJlbW92ZSBvbmUgDQo+PiBwYXRjaC4g
WW91IGNhbiB0cnkgdG8gZG93bmxvYWQgYW5kIGNvbXBpbGUgVEhBVCB2ZXJzaW9uIGJ5IHJ1bm5p
bmcgDQo+PiB0aGUgZm9sbG93aW5nIGNvbW1hbmRzOg0KPj4NCj4+IF8qQ2xvbmluZyBYZW46Kl8N
Cj4+ICotIGNkIC9zb21lL2RpcmVjdG9yeS9pbi9ob21lDQo+PiAtIHJldj0yNTM5MiYmICAgaGcg
Y2xvbmUgLXIgJHJldg0KPj4gaHR0cDovL3hlbmJpdHMueGVuLm9yZy9oZy94ZW4tdW5zdGFibGUu
aGcvIHhlbi11bnN0YWJsZS5oZy1yZXYtJHtyZXZ9DQo+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1y
ZXYtMjUzOTINCj4+IC0gaGcgYmFja291dCAtciAyNTM2NCoNCj4+DQo+PiBUaGlzIHdpbGwgY2xv
bmUgdGhlIHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbiANCj4+IDQu
Mi11bnN0YWJsZSByZXZpc2lvbiAyNTM5MiBpbnRvIHRoZSBmb2xkZXIgDQo+PiAiKnhlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIqIi4gUnVubmluZyB0aGUgY29tbWFuZCAiKmhnIGJhY2tvdXIgLXIg
DQo+PiAyNTM2NCoiIHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4g
SXQgc2VlbXMgdGhhdCANCj4+IHdpdGhvdXQgdGhhdCwgZXZlbiB0aGF0IHJldmlzaW9uIHdvbnQg
Y29tcGlsZS4NCj4+DQo+PiBfKkNvbXBpbGluZyBYZW46Kl8NCj4+IFRoYW4ganVzdCBzaW1wbHkg
cnVuIHRoZXNlIGNvbW1hbmRzIHRvIGNvbXBpbGUgWGVuLg0KPj4NCj4+ICotIGNkIHhlbi11bnN0
YWJsZS5oZy1yZXYtMjUzOTIqDQo+PiAqLSAuL2NvbmZpZ3VyZQ0KPj4gLSBzdWRvIG1ha2UgLWo1
IHhlbiYmICAgc3VkbyBtYWtlIFRoZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdA0KPiBzdHJp
bmdzIHRvZ2V0aGVyIHRoZSA0IGNvbXBpbGluZyBjb21tYW5kcw0KPj4gdG8gcnVuIGFuZCB3aWxs
IGV4ZWN1dGUgb25lIGFmdGVyIHRoZSBvdGhlciBTTyB5b3UgZG9uJ3QgaGF2ZSB0byANCj4+IG1h
bnVhbGx5IHJ1biBlYWNoIGFuZCBldmVyeSBvbmUuIEFsc28sIEluIHRoZSBhYm92ZSAiKm1ha2Uq
IiANCj4+IGNvbW1hbmRzLCB1c2luZyB0aGUgIiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtl
IHRlbGxzIHRoZSBjb21waWxlIA0KPj4gdG8gdXNlIG1vcmUgdGhhbiBvbmUgY29yZSB0byBjb21w
aWxlIHdpdGguIEl0IHNwZWVkcyB1cCB0aGUgY29tcGlsaT4gIA0KPj4gaGF2ZSBhIG11bHRpLWNv
cmUgQ1BVLiBTTyBpbiBteSBjYXNlLCBpIGhhdmUgYSBRdWFkIENvcmUgQ1BVLCBzbyB0aGF0IA0K
Pj4gY29tbWFuZCBvcHRpb24gaXMgIiotajEgKyBudW1iZXIgb2YgQ1BVIGNvcmVzKiIuIFlvdSBj
YW4gbW9kaWZ5IG9yIHJlbW92ZSB0aGF0IGFzIHlvdSB3aXNoLg0KPj4NCj4+IFRoZSBhYm92ZSB3
aWxsIGFsc28gY3JlYXRlIGZvciB5b3UgYSBuaWNlIERFQiBwYWNrYWdlIGFmdGVyIGFsbCB0aGUg
DQo+PiBjb21waWxpbmcgaXMgZG9uZSwgaWYgeW91IGRvIG5vdCB3YW50IHRvIGNyZWF0ZSBhIERF
QiBwYWNrYWdlIGF0IHRoZQ0KPiBlbmQNCj4+IG9mIGl0IGFsbCwgdGhhbiBqdXN0IHJlbW92ZSB0
aGUgbGFzdCAiKiYmICAgc3VkbyBtYWtlIC1qNSBkZWIqIg0KPiBjb21tYW5kLg0KPj4gR3JhbnRl
ZCwgaSBhbSBydW5uaW5nIGFuZCBkb2luZyBhbGwgb2YgdGhpcyBvbiBEZWJpYW4gV2hlZXp5IEJV
VCBpDQo+IHRoZXJlDQo+PiBhcmVuJ3QgYW55IGRpZmZlcmVuY2VzIGluIGNvbXBpbGluZyBpdCBv
biBVYnVudHUgMTIuMDQuDQo+Pg0KPj4NCj4+DQo+Pg0KPj4+Pj4+ICAgICAwNi8wMy8xMiAyOjM0
IFBNPj4+DQo+Pj4gVGhlIGxhdGVzdCByZXZpc2lvbiBvZiBYZW4gNC4yLXVuc3RhYmxlIGlzICoy
NTQ1Mjo2YmVhNjNlNmM3ODAqIGF0DQo+IHRoZQ0KPj4+IGxpbmsgKmh0dHA6Ly94ZW5iaXRzLnhl
bi5vcmcvaGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YNCj4+IFhlbg0KPj4+
IDQuMi1VbnN0YWJsZSBhcmUgeW91IHRyeWluZyB0byBjb21waWxlPw0KPj4+DQo+Pj4NCj4+Pj4g
SGVsbG8sDQo+Pj4+DQo+Pj4+IEkgYW0gdHJ5aW5nIHRvIGNvbXBpbGUgeGVuIDQuMiB1bnN0YWJs
ZSBmcm9tIG1lcmN1cmlhbC4gSSBjYW4ndCBnZXQNCj4+PiBwYXN0DQo+Pj4+IHRoZSBtYWtlIHRv
b2xzIHN0ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6DQo+
Pj4+DQo+Pj4+IENDICAgIGxpYmh3NjQvOXBmcy9jb3hhdHRyLm8NCj4+Pj4gICAgICAgQ0MgICAg
bGliaHc2NC85cGZzL3ZpcnRpby05cC1zeW50aC5vDQo+Pj4+ICAgICAgIENDICAgIGxpYmh3NjQv
OXBmcy92aXJ0aW8tOXAtaGFuZGxlLm8NCj4+Pj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+PiBJbg0KPj4+PiBm
dW5jdGlvbiDDomhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6DQo+Pj4+DQo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
NzA6NTg6DQo+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+Pj4NCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoNCj4+Pj4gbm90
ZTogZWFjaCB1bmRlY2xhcmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBl
YWNoDQo+Pj4gZnVuY3Rpb24NCj4+Pj4gaXQgYXBwZWFycyBpbg0KPj4+PiAvcm9vdC94ZW4tdW5z
dGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOg0K
Pj4+IEluDQo+Pj4+IGZ1bmN0aW9uIMOiaGFuZGxlX2xzdGF0w6I6DQo+Pj4+DQo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6ODc6MzQ6DQo+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJz
dCB1c2UgaW4gdGhpcyBmdW5jdGlvbikNCj4+Pj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoNCj4+PiBJbg0KPj4+PiBm
dW5jdGlvbiDDomhhbmRsZV9zeW1saW5rw6I6DQo+Pj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5o
Zy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOg0K
Pj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRo
aXMgZnVuY3Rpb24pDQo+Pj4+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6DQo+Pj4gSW4NCj4+Pj4gZnVuY3Rpb24gw6Jo
YW5kbGVfbGlua8OiOg0KPj4+Pg0KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14
ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToNCj4+Pj4gZXJyb3I6IMOi
QVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQ0K
Pj4+PiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOg0KPj4+IEluDQo+Pj4+IGZ1bmN0aW9uIMOiaGFuZGxlX2Nob3duw6I6
DQo+Pj4+DQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzczOjU4Og0KPj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRI
w6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pDQo+Pj4+IG1ha2VbNF06
ICoqKiBbOXBmcy92aXJ0aW8tOXAtaGFuZGxlLm9dIEVycm9yIDENCj4+Pj4gbWFrZVszXTogKioq
IFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMg0KPj4+PiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9y
eQ0KPj4+PiBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci1yZW1vdGUn
DQo+Pj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJvciAy
DQo+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcv
dG9vbHMnDQo+Pj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1pbnN0YWxsXSBFcnJvciAyDQo+Pj4+
IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMn
DQo+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMg0KPj4+Pg0KPj4+PiBJIGFt
IHJ1bm5pbmcgdWJ1bnR1IDEyLjA0LCBrZXJuZWwgdmVyOiAzLjIuMC0yNC1nZW5lcmljDQo+Pj4+
DQo+Pj4+IEFueSBpZGVhcz8gSSBoYXZlIGdvb2dsZWQgZnVyaW91c2x5IGFuZCBmb3VuZCBzb21l
IHBlb3BsZSB0YWxraW5nDQo+Pj4gYWJvdXQNCj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOg0KPj4+PiBodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9x
ZW11LWt2bS8rYnVnLzkzMDE4MQ0KPj4+PiBCdXQgSSB3YXMgbm90IGFibGUgdG8gZmluZCB0aGUg
cGF0Y2gNCj4+Pj4NCj4+Pj4gVGhhbmtzIGluIGFkdmFuY2UhDQo+Pj4+DQo+Pj4+DQo+Pj4+DQo+
Pj4+IE1lcmN1cmlhbG0NCj4+Pj4NCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+Pj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdA0KPj4+PiBYZW4t
dXNlcnNAbGlzdHMueGVuLm9yZw0KPj4+PiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMN
Cj4+DQo+DQo+DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NClhlbi11c2VycyBtYWlsaW5nIGxpc3QNClhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQpo
dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxp
c3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Tue Jun 05 17:13:15 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 17:13: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 1SbxIE-0004as-He; Tue, 05 Jun 2012 17:11:42 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbxIC-0004an-KA
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 17:11:40 +0000
Received: from [85.158.139.83:51115] by server-5.bemta-5.messagelabs.com id
	0B/58-04481-BCD3ECF4; Tue, 05 Jun 2012 17:11:39 +0000
X-Env-Sender: alk@ondore.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1338916297!28167672!1
X-Originating-IP: [184.172.38.138]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9031 invoked from network); 5 Jun 2012 17:11:38 -0000
Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com)
	(184.172.38.138)
	by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 5 Jun 2012 17:11:38 -0000
Received: from [189.253.145.95] (port=57725 helo=mail.ondore.i)
	by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.77) (envelope-from ) id 1SbxI9-000664-3A
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:11:37 -0500
Received: from [10.13.34.178] (alk-desktop.sys.ondore.i [10.13.34.178])
	by mail.ondore.i (Postfix) with ESMTPSA id 8ADE9A1DB
	for ; Tue,  5 Jun 2012 12:11:35 -0500 (CDT)
Message-ID: <4FCE3DC7.8010506@ondore.com>
Date: Tue, 05 Jun 2012 12:11:35 -0500
From: Alexandre Kouznetsov 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCD7E6D.5070004@b2bassadventures.com>
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host0a.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
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
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-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello.

El 04/06/12 22:35, Bill Beauchemin escribi=F3:
> I have a project where I have a Dell 2950
> server with two ethernet ports, and one 1TB drive. I have 64 bit Debian
> Squeeze installed and running. I need two instances of vm's one being
> devel and the other is prod. each should connect through one of the eth
> ports. so devel could be eth0 and prod could be on eth1.
Pretty similar to the setup I use all the time on my own. "Just works", =

once you get around some issues, particularly the network setup.

1. Do not dedicate physical partitions to each VMs. It's too unflexible, =

almost nobody uses it so (unless they really know what they are doing), =

you will not find much references about issues specific to that setup. =

The most simple way is to store VM's disks as files. A better one, but =

little bit more complex, to use LVM volumes. If you are already familiar =

with LVM you probably want to go straight for LVM.

2. Set up your network manually, not via xend's network scripts. Do not =

attempt to export raw ethX to your VM's. Instead, set up a ethernet =

bridge on each ethX you wish to use, which is a regular way. Then, in =

the config file of each VM, you may specify to which bridge it should be =

plugged.
http://wiki.xen.org/wiki/XenNetworking

3. Use xen-tools to perform the initial install of the VM's, it does =

good job taking care of lots of small details. The default config file =

is heavily commented.
http://www.virtuatopia.com/index.php/Building_a_Xen_Guest_Domain_using_Xen-=
Tools

> I have had so many issues trying to just get one vm running. make a cfg
> file i get errors about installation files or hotplug issues.
I guess it's possible to debug it as is, but, IMHO, it does not worth =

it. You definitely should consider to change the storage model.

This, in most points, repeats what Casey wrote, his advice about the =

documentation is definitely valid as well.

-- =

Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 17:13:15 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 17:13: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 1SbxIE-0004as-He; Tue, 05 Jun 2012 17:11:42 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbxIC-0004an-KA
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 17:11:40 +0000
Received: from [85.158.139.83:51115] by server-5.bemta-5.messagelabs.com id
	0B/58-04481-BCD3ECF4; Tue, 05 Jun 2012 17:11:39 +0000
X-Env-Sender: alk@ondore.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1338916297!28167672!1
X-Originating-IP: [184.172.38.138]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9031 invoked from network); 5 Jun 2012 17:11:38 -0000
Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com)
	(184.172.38.138)
	by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 5 Jun 2012 17:11:38 -0000
Received: from [189.253.145.95] (port=57725 helo=mail.ondore.i)
	by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.77) (envelope-from ) id 1SbxI9-000664-3A
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 12:11:37 -0500
Received: from [10.13.34.178] (alk-desktop.sys.ondore.i [10.13.34.178])
	by mail.ondore.i (Postfix) with ESMTPSA id 8ADE9A1DB
	for ; Tue,  5 Jun 2012 12:11:35 -0500 (CDT)
Message-ID: <4FCE3DC7.8010506@ondore.com>
Date: Tue, 05 Jun 2012 12:11:35 -0500
From: Alexandre Kouznetsov 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCD7E6D.5070004@b2bassadventures.com>
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host0a.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
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
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-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hello.

El 04/06/12 22:35, Bill Beauchemin escribi=F3:
> I have a project where I have a Dell 2950
> server with two ethernet ports, and one 1TB drive. I have 64 bit Debian
> Squeeze installed and running. I need two instances of vm's one being
> devel and the other is prod. each should connect through one of the eth
> ports. so devel could be eth0 and prod could be on eth1.
Pretty similar to the setup I use all the time on my own. "Just works", =

once you get around some issues, particularly the network setup.

1. Do not dedicate physical partitions to each VMs. It's too unflexible, =

almost nobody uses it so (unless they really know what they are doing), =

you will not find much references about issues specific to that setup. =

The most simple way is to store VM's disks as files. A better one, but =

little bit more complex, to use LVM volumes. If you are already familiar =

with LVM you probably want to go straight for LVM.

2. Set up your network manually, not via xend's network scripts. Do not =

attempt to export raw ethX to your VM's. Instead, set up a ethernet =

bridge on each ethX you wish to use, which is a regular way. Then, in =

the config file of each VM, you may specify to which bridge it should be =

plugged.
http://wiki.xen.org/wiki/XenNetworking

3. Use xen-tools to perform the initial install of the VM's, it does =

good job taking care of lots of small details. The default config file =

is heavily commented.
http://www.virtuatopia.com/index.php/Building_a_Xen_Guest_Domain_using_Xen-=
Tools

> I have had so many issues trying to just get one vm running. make a cfg
> file i get errors about installation files or hotplug issues.
I guess it's possible to debug it as is, but, IMHO, it does not worth =

it. You definitely should consider to change the storage model.

This, in most points, repeats what Casey wrote, his advice about the =

documentation is definitely valid as well.

-- =

Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Tue Jun 05 18:12:45 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 18:12: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 1SbyDt-0005SS-KS; Tue, 05 Jun 2012 18:11:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbyDs-0005SN-Ln
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 18:11:17 +0000
Received: from [85.158.143.35:54696] by server-1.bemta-4.messagelabs.com id
	3A/ED-10042-4CB4ECF4; Tue, 05 Jun 2012 18:11:16 +0000
X-Env-Sender: alden_lava@yahoo.com
X-Msg-Ref: server-15.tower-21.messagelabs.com!1338919873!14157245!1
X-Originating-IP: [98.139.53.220]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22120 invoked from network); 5 Jun 2012 18:11:14 -0000
Received: from nm23-vm0.bullet.mail.ac4.yahoo.com (HELO
	nm23-vm0.bullet.mail.ac4.yahoo.com) (98.139.53.220)
	by server-15.tower-21.messagelabs.com with SMTP;
	5 Jun 2012 18:11:14 -0000
Received: from [98.139.52.197] by nm23.bullet.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
Received: from [98.139.52.153] by tm10.bullet.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
Received: from [127.0.0.1] by omp1036.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 716094.82764.bm@omp1036.mail.ac4.yahoo.com
Received: (qmail 50617 invoked by uid 60001); 5 Jun 2012 18:11:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1338919873; bh=Ukqw9QWBZ7g/t2z+IeSy5bQugiLZ2HdwNuEbHM8ulOs=;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=KLr3y8fSwvdvtaFei0BdGRmHyres0OudbprW59J4h16M5ffMAOwV85L5/PmB8D/vvSAQ7P3d9aytjgGeeCze9pWcH48QSK9peqxo5l+ZtJD1jJd8VQ9X5eTrYPQmI1Yy83RffwKyvl8g1v9sYtM9MVP1TQx0ovQFgpx0uABHXCI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=ekP7G4w2o7qgMFR0tyGjYT1JIkOEQyKHPzLq78Ers7YWWjVETifiUo4O+0ktxrE8wIY3pUOvrzEivBeLnXAEetgfSOsFFOIWi8nNY0HysJuAWQBWbXwKYy0M831nlvBuUdxlOcjd9CWCA+IFs7GmWl4OjOEi3FylKl1ZDsBYG3M=;
X-YMail-OSG: AX08HDQVM1lAJPVy7ohQrXr29OjY0uY9ISqh3QgTXMNwgOs
	O3SNi63mF2yR9fri2j3BkXInojao6N0NUqvUn_5mOa3wRf35NDORmHK1CLEI
	l.fo_UkvGWrJOeHcFOPExdg9zZ3gEEVKESsKH9BzFEp.iQMR8Hxz2kVgzBAp
	1BmS8hjbhk6tZHqvdh5CKJejyrpr3e7W0i8x9d.rni.aIjYaUdpZa8EWeO1x
	mxL4GZWMZ2pzQh99XY19pRa5OhK6dGFDbG.dIZXlmgrqNUh4SH3RfRzS0Z7D
	e_XNFHBWDlxUJECheu9K2fSf7aIehggswCbflmYpS_yi8A63ha7f1pUBM8Is
	bmNWC9L_E3LKYTyoV8PUwGRXyf9OMaELf12ZYt7tA7TPa044D06j7tnFFlxt
	eGU6VP8wYig9RKbI6ZMULsmT79LJc.h82d1aYpOL1CH0Flz66PweJGH9Zyni
	AlOxGsfzRJiWfHUIEUpD4pj3SDZEWkZjFvMVHv12xIK1jxzZDlPXl.RmxLAC
	7M6lCRGg5jqY-
Received: from [116.50.246.68] by web39303.mail.mud.yahoo.com via HTTP;
	Tue, 05 Jun 2012 11:11:12 PDT
X-Mailer: YahooMailWebService/0.8.118.349524
Message-ID: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
Date: Tue, 5 Jun 2012 11:11:12 -0700 (PDT)
From: dhyn lav 
To: "xen-users@lists.xen.org" 
MIME-Version: 1.0
Subject: [Xen-users] xend error in logs file
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: dhyn lav 
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0393157291470737663=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0393157291470737663==
Content-Type: multipart/alternative; boundary="-965286322-1501917689-1338919872=:48944"

---965286322-1501917689-1338919872=:48944
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,=0A=0AI am using Centos 6.2 64bit minimal and xen 4.1.2 from crc.id.au. =
When centos with xen started I noticed some error in xend logs. I try to se=
arch in google but I can't find good answer on this.=0A=0Axend.log=0A=0A[20=
12-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon started=0A[2012-06=
-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset: unavailable.=0A[201=
2-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record count: 8=0A[2012-0=
6-06 01:33:00 2501] DEBUG (XendCPUPool:747) recreate_active_pools=0A[2012-0=
6-06 01:33:00 2501] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'ma=
x_vcpu_id': 0, 'cpu_time': 7012131419L, 'ssidref': 0, 'hvm': 0, 'shutdown_r=
eason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crash=
ed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1=
048576L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,=
 0, 0], 'cpupool': 0, 'name': 'Domain-0'})=0A[2012-06-06 01:33:01 2501] INF=
O (XendDomainInfo:169) Recreating domain 0, UUID 00000000-0000-0000-0000-00=
0000000000. at /local/domain/0=0A[2012-06-06 01:33:01 2501] DEBUG (XendDoma=
inInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'pool_name': 'P=
ool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000=
', 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) (nom=
igrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', =
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0'=
, 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'name': 'Domain-0'}=0A=
[2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1794) Storing domain detai=
ls: {'description': '', 'console/limit': '1048576', 'vm': '/vm/00000000-000=
0-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'm=
emory/target': '1048576', 'control/platform-feature-multiprocessor-suspend'=
: '1', 'console/type': 'xenconsoled', 'name': 'Domain-0'}=0A[2012-06-06 01:=
33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0=0A[2012-06-06 01:33:01 =
2501] DEBUG (XendDomain:410) number of vcpus to use is 0=0A[2012-06-06 01:3=
3:01 2501] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch=
=0A[2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix path=3D/var/lib/xen=
d/xend-socket=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: =
VBD.set_device not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708)=
 API call: VBD.set_type not found=0A[2012-06-06 01:33:01 2501] WARNING (Xen=
dAPI:708) API call: session.get_all_records not found=0A[2012-06-06 01:33:0=
1 2501] WARNING (XendAPI:708) API call: event.get_record not found=0A[2012-=
06-06 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_all not foun=
d=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_devi=
ce not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: V=
IF.set_MAC not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API=
 call: VIF.set_MTU not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:=
708) API call: debug.get_all not found=0A[2012-06-06 01:33:01 2501] INFO (X=
MLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend=
/xen-api.sock; authentication has been disabled for this server.=0A[2012-06=
-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain socket XML-R=
PC server on /var/run/xend/xmlrpc.sock.=0A=0Axend-debug.log=0A=0AXend start=
ed at Wed Jun =A06 01:33:00 2012.=0Acat: /sys/bus/scsi/devices/host0/vendor=
: No such file or directory=0Acat: /sys/bus/scsi/devices/host0/model: No su=
ch file or directory=0Acat: /sys/bus/scsi/devices/host0/type: No such file =
or directory=0Acat: /sys/bus/scsi/devices/host0/rev: No such file or direct=
ory=0Acat: /sys/bus/scsi/devices/host0/scsi_level: No such file or director=
y=0Acat: /sys/bus/scsi/devices/host1/vendor: No such file or directory=0Aca=
t: /sys/bus/scsi/devices/host1/model: No such file or directory=0Acat: /sys=
/bus/scsi/devices/host1/type: No such file or directory=0Acat: /sys/bus/scs=
i/devices/host1/rev: No such file or directory=0Acat: /sys/bus/scsi/devices=
/host1/scsi_level: No such file or directory=0Acat: /sys/bus/scsi/devices/h=
ost2/vendor: No such file or directory=0Acat: /sys/bus/scsi/devices/host2/m=
odel: No such file or directory=0Acat: /sys/bus/scsi/devices/host2/type: No=
 such file or directory=0Acat: /sys/bus/scsi/devices/host2/rev: No such fil=
e or directory=0Acat: /sys/bus/scsi/devices/host2/scsi_level: No such file =
or directory=0Acat: /sys/bus/scsi/devices/host3/vendor: No such file or dir=
ectory=0Acat: /sys/bus/scsi/devices/host3/model: No such file or directory=
=0Acat: /sys/bus/scsi/devices/host3/type: No such file or directory=0Acat: =
/sys/bus/scsi/devices/host3/rev: No such file or directory=0Acat: /sys/bus/=
scsi/devices/host3/scsi_level: No such file or directory=0Acat: /sys/bus/sc=
si/devices/target2:0:1/vendor: No such file or directory=0Acat: /sys/bus/sc=
si/devices/target2:0:1/model: No such file or directory=0Acat: /sys/bus/scs=
i/devices/target2:0:1/type: No such file or directory=0Acat: /sys/bus/scsi/=
devices/target2:0:1/rev: No such file or directory=0Acat: /sys/bus/scsi/dev=
ices/target2:0:1/scsi_level: No such file or directory=0A/usr/lib64/python2=
.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarning: object.__new_=
_() takes no parameters=0A=A0 return object.__new__(cls, *args, **kwds)=0A
---965286322-1501917689-1338919872=:48944
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Hi,

I am using Centos 6.2 64bit m=
inimal and xen 4.1.2 from crc.id.au. When centos with xen started I noticed=
 some error in xend logs. I try to search in google but I can't find good a=
nswer on this.
xend.log

[2012-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon =
started
[2012-06-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset: un=
available.
[2012-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record co=
unt: 8
[2012-06-06 01:33:00 2501] DEBUG (XendCPUPool:747) recreate_active_=
pools
[2012-06-06 01:33:00 2501] DEBUG (XendDomainInfo:151) XendDomainInfo=
.recreate({'max_vcpu_id': 0, 'cpu_time': 7012131419L, 'ssidref': 0, 'hvm': =
0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 0, 'paus=
ed': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': =
0, 'mem_kb': 1048576L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0,
 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'})
=
[2012-06-06 01:3=
3:01 2501] INFO (XendDomainInfo:169) Recreating domain 0, UUID 00000000-000=
0-0000-0000-000000000000. at /local/domain/0
[2012-06-06 01:33:01 2501] DE=
BUG (XendDomainInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'p=
ool_name': 'Pool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000=
-000000000000', 'on_reboot': 'restart', 'image': "(linux (kernel '') (super=
pages 0) (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloade=
r_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restar=
t_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'name': '=
Domain-0'}
[2012-06-06 01:33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0
[2=
012-06-06 01:33:01 2501] DEBUG (XendDomain:410) number of vcpus to use is 0=

[2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix path=
=3D/var/lib/xend/xend-socket
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708)=
 API call: VBD.set_device not found
[2012-06-06 01:33:01 2501] WARNING (Xe=
ndAPI:708) API call: VBD.set_type not found
[2012-06-06 01:33:01 2501] WAR=
NING (XendAPI:708) API call: session.get_all_records not found
=

[2012-06-06=
 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_record not found<=
/font>
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_=
all not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: V=
IF.set_device not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API =
call: VIF.set_MAC not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:70=
8) API call: VIF.set_MTU not found
[2012-06-06 01:33:01 2501] WARNING (Xen=
dAPI:708) API call: debug.get_all not found
[2012-06-06 01:33:01 2501] INF=
O (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/=
xend/xen-api.sock; authentication has been disabled for this server.=

[2012=
-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain socket XM=
L-RPC server on /var/run/xend/xmlrpc.sock.

xend-debug.log

=

Xend s=
tarted at Wed Jun  6 01:33:00 2012.
cat: /sys/bus/scsi/devices/host0/=
vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: =
No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such f=
ile or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or dir=
ectory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or direct=
ory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
ca=
t: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/=
bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/=
devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/ho=
st1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host2=
/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host2/model: =
No such file or directory
cat: /sys/bus/scsi/devices/host2/type: No such f=
ile or directory
cat: /sys/bus/scsi/devices/host2/rev: No such file or dir=
ectory
cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or direct=
ory
cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
ca=
t: /sys/bus/scsi/devices/host3/model: No such file or directory
cat: /sys/=
bus/scsi/devices/host3/type: No such file or directory
cat: /sys/bus/scsi/de=
vices/host3/rev: No such file or directory
cat: /sys/bus/scsi/devices/host=
3/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/ta=
rget2:0:1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/tar=
get2:0:1/model: No such file or directory
cat: /sys/bus/scsi/devices/targe=
t2:0:1/type: No such file or directory
cat: /sys/bus/scsi/devices/target2:=
0:1/rev: No such file or directory
cat:
 /sys/bus/scsi/devices/target2:0:1/scsi_level: No such file or directory
/=
usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarni=
ng: object.__new__() takes no parameters
  return object.__new__(cls,=
 *args, **kwds)


---965286322-1501917689-1338919872=:48944--


--===============0393157291470737663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0393157291470737663==--


From xen-users-bounces@lists.xen.org Tue Jun 05 18:12:45 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 05 Jun 2012 18:12: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 1SbyDt-0005SS-KS; Tue, 05 Jun 2012 18:11:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbyDs-0005SN-Ln
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 18:11:17 +0000
Received: from [85.158.143.35:54696] by server-1.bemta-4.messagelabs.com id
	3A/ED-10042-4CB4ECF4; Tue, 05 Jun 2012 18:11:16 +0000
X-Env-Sender: alden_lava@yahoo.com
X-Msg-Ref: server-15.tower-21.messagelabs.com!1338919873!14157245!1
X-Originating-IP: [98.139.53.220]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22120 invoked from network); 5 Jun 2012 18:11:14 -0000
Received: from nm23-vm0.bullet.mail.ac4.yahoo.com (HELO
	nm23-vm0.bullet.mail.ac4.yahoo.com) (98.139.53.220)
	by server-15.tower-21.messagelabs.com with SMTP;
	5 Jun 2012 18:11:14 -0000
Received: from [98.139.52.197] by nm23.bullet.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
Received: from [98.139.52.153] by tm10.bullet.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
Received: from [127.0.0.1] by omp1036.mail.ac4.yahoo.com with NNFMP;
	05 Jun 2012 18:11:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 716094.82764.bm@omp1036.mail.ac4.yahoo.com
Received: (qmail 50617 invoked by uid 60001); 5 Jun 2012 18:11:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1338919873; bh=Ukqw9QWBZ7g/t2z+IeSy5bQugiLZ2HdwNuEbHM8ulOs=;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=KLr3y8fSwvdvtaFei0BdGRmHyres0OudbprW59J4h16M5ffMAOwV85L5/PmB8D/vvSAQ7P3d9aytjgGeeCze9pWcH48QSK9peqxo5l+ZtJD1jJd8VQ9X5eTrYPQmI1Yy83RffwKyvl8g1v9sYtM9MVP1TQx0ovQFgpx0uABHXCI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=ekP7G4w2o7qgMFR0tyGjYT1JIkOEQyKHPzLq78Ers7YWWjVETifiUo4O+0ktxrE8wIY3pUOvrzEivBeLnXAEetgfSOsFFOIWi8nNY0HysJuAWQBWbXwKYy0M831nlvBuUdxlOcjd9CWCA+IFs7GmWl4OjOEi3FylKl1ZDsBYG3M=;
X-YMail-OSG: AX08HDQVM1lAJPVy7ohQrXr29OjY0uY9ISqh3QgTXMNwgOs
	O3SNi63mF2yR9fri2j3BkXInojao6N0NUqvUn_5mOa3wRf35NDORmHK1CLEI
	l.fo_UkvGWrJOeHcFOPExdg9zZ3gEEVKESsKH9BzFEp.iQMR8Hxz2kVgzBAp
	1BmS8hjbhk6tZHqvdh5CKJejyrpr3e7W0i8x9d.rni.aIjYaUdpZa8EWeO1x
	mxL4GZWMZ2pzQh99XY19pRa5OhK6dGFDbG.dIZXlmgrqNUh4SH3RfRzS0Z7D
	e_XNFHBWDlxUJECheu9K2fSf7aIehggswCbflmYpS_yi8A63ha7f1pUBM8Is
	bmNWC9L_E3LKYTyoV8PUwGRXyf9OMaELf12ZYt7tA7TPa044D06j7tnFFlxt
	eGU6VP8wYig9RKbI6ZMULsmT79LJc.h82d1aYpOL1CH0Flz66PweJGH9Zyni
	AlOxGsfzRJiWfHUIEUpD4pj3SDZEWkZjFvMVHv12xIK1jxzZDlPXl.RmxLAC
	7M6lCRGg5jqY-
Received: from [116.50.246.68] by web39303.mail.mud.yahoo.com via HTTP;
	Tue, 05 Jun 2012 11:11:12 PDT
X-Mailer: YahooMailWebService/0.8.118.349524
Message-ID: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
Date: Tue, 5 Jun 2012 11:11:12 -0700 (PDT)
From: dhyn lav 
To: "xen-users@lists.xen.org" 
MIME-Version: 1.0
Subject: [Xen-users] xend error in logs file
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: dhyn lav 
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0393157291470737663=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0393157291470737663==
Content-Type: multipart/alternative; boundary="-965286322-1501917689-1338919872=:48944"

---965286322-1501917689-1338919872=:48944
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,=0A=0AI am using Centos 6.2 64bit minimal and xen 4.1.2 from crc.id.au. =
When centos with xen started I noticed some error in xend logs. I try to se=
arch in google but I can't find good answer on this.=0A=0Axend.log=0A=0A[20=
12-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon started=0A[2012-06=
-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset: unavailable.=0A[201=
2-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record count: 8=0A[2012-0=
6-06 01:33:00 2501] DEBUG (XendCPUPool:747) recreate_active_pools=0A[2012-0=
6-06 01:33:00 2501] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'ma=
x_vcpu_id': 0, 'cpu_time': 7012131419L, 'ssidref': 0, 'hvm': 0, 'shutdown_r=
eason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crash=
ed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1=
048576L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,=
 0, 0], 'cpupool': 0, 'name': 'Domain-0'})=0A[2012-06-06 01:33:01 2501] INF=
O (XendDomainInfo:169) Recreating domain 0, UUID 00000000-0000-0000-0000-00=
0000000000. at /local/domain/0=0A[2012-06-06 01:33:01 2501] DEBUG (XendDoma=
inInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'pool_name': 'P=
ool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000=
', 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) (nom=
igrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', =
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0'=
, 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'name': 'Domain-0'}=0A=
[2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1794) Storing domain detai=
ls: {'description': '', 'console/limit': '1048576', 'vm': '/vm/00000000-000=
0-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'm=
emory/target': '1048576', 'control/platform-feature-multiprocessor-suspend'=
: '1', 'console/type': 'xenconsoled', 'name': 'Domain-0'}=0A[2012-06-06 01:=
33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0=0A[2012-06-06 01:33:01 =
2501] DEBUG (XendDomain:410) number of vcpus to use is 0=0A[2012-06-06 01:3=
3:01 2501] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch=
=0A[2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix path=3D/var/lib/xen=
d/xend-socket=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: =
VBD.set_device not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708)=
 API call: VBD.set_type not found=0A[2012-06-06 01:33:01 2501] WARNING (Xen=
dAPI:708) API call: session.get_all_records not found=0A[2012-06-06 01:33:0=
1 2501] WARNING (XendAPI:708) API call: event.get_record not found=0A[2012-=
06-06 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_all not foun=
d=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_devi=
ce not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: V=
IF.set_MAC not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API=
 call: VIF.set_MTU not found=0A[2012-06-06 01:33:01 2501] WARNING (XendAPI:=
708) API call: debug.get_all not found=0A[2012-06-06 01:33:01 2501] INFO (X=
MLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend=
/xen-api.sock; authentication has been disabled for this server.=0A[2012-06=
-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain socket XML-R=
PC server on /var/run/xend/xmlrpc.sock.=0A=0Axend-debug.log=0A=0AXend start=
ed at Wed Jun =A06 01:33:00 2012.=0Acat: /sys/bus/scsi/devices/host0/vendor=
: No such file or directory=0Acat: /sys/bus/scsi/devices/host0/model: No su=
ch file or directory=0Acat: /sys/bus/scsi/devices/host0/type: No such file =
or directory=0Acat: /sys/bus/scsi/devices/host0/rev: No such file or direct=
ory=0Acat: /sys/bus/scsi/devices/host0/scsi_level: No such file or director=
y=0Acat: /sys/bus/scsi/devices/host1/vendor: No such file or directory=0Aca=
t: /sys/bus/scsi/devices/host1/model: No such file or directory=0Acat: /sys=
/bus/scsi/devices/host1/type: No such file or directory=0Acat: /sys/bus/scs=
i/devices/host1/rev: No such file or directory=0Acat: /sys/bus/scsi/devices=
/host1/scsi_level: No such file or directory=0Acat: /sys/bus/scsi/devices/h=
ost2/vendor: No such file or directory=0Acat: /sys/bus/scsi/devices/host2/m=
odel: No such file or directory=0Acat: /sys/bus/scsi/devices/host2/type: No=
 such file or directory=0Acat: /sys/bus/scsi/devices/host2/rev: No such fil=
e or directory=0Acat: /sys/bus/scsi/devices/host2/scsi_level: No such file =
or directory=0Acat: /sys/bus/scsi/devices/host3/vendor: No such file or dir=
ectory=0Acat: /sys/bus/scsi/devices/host3/model: No such file or directory=
=0Acat: /sys/bus/scsi/devices/host3/type: No such file or directory=0Acat: =
/sys/bus/scsi/devices/host3/rev: No such file or directory=0Acat: /sys/bus/=
scsi/devices/host3/scsi_level: No such file or directory=0Acat: /sys/bus/sc=
si/devices/target2:0:1/vendor: No such file or directory=0Acat: /sys/bus/sc=
si/devices/target2:0:1/model: No such file or directory=0Acat: /sys/bus/scs=
i/devices/target2:0:1/type: No such file or directory=0Acat: /sys/bus/scsi/=
devices/target2:0:1/rev: No such file or directory=0Acat: /sys/bus/scsi/dev=
ices/target2:0:1/scsi_level: No such file or directory=0A/usr/lib64/python2=
.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarning: object.__new_=
_() takes no parameters=0A=A0 return object.__new__(cls, *args, **kwds)=0A
---965286322-1501917689-1338919872=:48944
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Hi,

I am using Centos 6.2 64bit m=
inimal and xen 4.1.2 from crc.id.au. When centos with xen started I noticed=
 some error in xend logs. I try to search in google but I can't find good a=
nswer on this.
xend.log

[2012-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon =
started
[2012-06-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset: un=
available.
[2012-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record co=
unt: 8
[2012-06-06 01:33:00 2501] DEBUG (XendCPUPool:747) recreate_active_=
pools
[2012-06-06 01:33:00 2501] DEBUG (XendDomainInfo:151) XendDomainInfo=
.recreate({'max_vcpu_id': 0, 'cpu_time': 7012131419L, 'ssidref': 0, 'hvm': =
0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 0, 'paus=
ed': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': =
0, 'mem_kb': 1048576L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0,
 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'})
=
[2012-06-06 01:3=
3:01 2501] INFO (XendDomainInfo:169) Recreating domain 0, UUID 00000000-000=
0-0000-0000-000000000000. at /local/domain/0
[2012-06-06 01:33:01 2501] DE=
BUG (XendDomainInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'p=
ool_name': 'Pool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000=
-000000000000', 'on_reboot': 'restart', 'image': "(linux (kernel '') (super=
pages 0) (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloade=
r_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restar=
t_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'name': '=
Domain-0'}
[2012-06-06 01:33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0
[2=
012-06-06 01:33:01 2501] DEBUG (XendDomain:410) number of vcpus to use is 0=

[2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix path=
=3D/var/lib/xend/xend-socket
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708)=
 API call: VBD.set_device not found
[2012-06-06 01:33:01 2501] WARNING (Xe=
ndAPI:708) API call: VBD.set_type not found
[2012-06-06 01:33:01 2501] WAR=
NING (XendAPI:708) API call: session.get_all_records not found
=

[2012-06-06=
 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_record not found<=
/font>
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: event.get_=
all not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: V=
IF.set_device not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API =
call: VIF.set_MAC not found
[2012-06-06 01:33:01 2501] WARNING (XendAPI:70=
8) API call: VIF.set_MTU not found
[2012-06-06 01:33:01 2501] WARNING (Xen=
dAPI:708) API call: debug.get_all not found
[2012-06-06 01:33:01 2501] INF=
O (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/=
xend/xen-api.sock; authentication has been disabled for this server.=

[2012=
-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain socket XM=
L-RPC server on /var/run/xend/xmlrpc.sock.

xend-debug.log

=

Xend s=
tarted at Wed Jun  6 01:33:00 2012.
cat: /sys/bus/scsi/devices/host0/=
vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: =
No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such f=
ile or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or dir=
ectory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or direct=
ory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
ca=
t: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/=
bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/=
devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/ho=
st1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host2=
/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host2/model: =
No such file or directory
cat: /sys/bus/scsi/devices/host2/type: No such f=
ile or directory
cat: /sys/bus/scsi/devices/host2/rev: No such file or dir=
ectory
cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or direct=
ory
cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
ca=
t: /sys/bus/scsi/devices/host3/model: No such file or directory
cat: /sys/=
bus/scsi/devices/host3/type: No such file or directory
cat: /sys/bus/scsi/de=
vices/host3/rev: No such file or directory
cat: /sys/bus/scsi/devices/host=
3/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/ta=
rget2:0:1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/tar=
get2:0:1/model: No such file or directory
cat: /sys/bus/scsi/devices/targe=
t2:0:1/type: No such file or directory
cat: /sys/bus/scsi/devices/target2:=
0:1/rev: No such file or directory
cat:
 /sys/bus/scsi/devices/target2:0:1/scsi_level: No such file or directory
/=
usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarni=
ng: object.__new__() takes no parameters
  return object.__new__(cls,=
 *args, **kwds)


---965286322-1501917689-1338919872=:48944--


--===============0393157291470737663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0393157291470737663==--


From xen-users-bounces@lists.xen.org Wed Jun 06 07:28:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 07:28: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 1ScAdo-0005fi-7q; Wed, 06 Jun 2012 07:26:52 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScAdm-0005fd-RU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 07:26:51 +0000
Received: from [85.158.143.99:51244] by server-1.bemta-4.messagelabs.com id
	E5/6E-10042-A360FCF4; Wed, 06 Jun 2012 07:26:50 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-10.tower-216.messagelabs.com!1338967608!24953915!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1038 invoked from network); 6 Jun 2012 07:26:49 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 07:26:49 -0000
Received: by werf3 with SMTP id f3so5060369wer.32
	for ; Wed, 06 Jun 2012 00:26:48 -0700 (PDT)
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=9keH/fwwPpCWFK3Wq566M+yuWcfYLflBz9mn01qjbQw=;
	b=wIp+4YkSW8sJ0SqEDNJv3BzrLwU9g7TjN2t4z8M/S3dw9afL+hBT5iSgibdcU8h5c2
	e9OM35EFtIDk9wuf+F0wthv8v+rUdLYBd1cVAjJHwNSDLzrQitOmgRcm+O1+ap3HHxsX
	WO4nuiHjGYPEhZ3Svy06RSxZ4uYHVBEnzBgXtVlw57OT+F/7ciyu0AJHUBW15ru7FB28
	i59jQ0vos3fpn1kUpD6uZk5SmGPaHKcQemgMb540HLnFL0SpB6I8YG0ggNMEcbtbhzVj
	syOgt+7QspDJE0IvPfCmpixNIHd1Ut2J8sdxdyQtUwk/nNScoMKJ9i7NWx78w489QYdR
	GglA==
MIME-Version: 1.0
Received: by 10.216.196.90 with SMTP id q68mr17855622wen.130.1338967608404;
	Wed, 06 Jun 2012 00:26:48 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Wed, 6 Jun 2012 00:26:48 -0700 (PDT)
Date: Wed, 6 Jun 2012 09:26:48 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
Subject: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7310602811363762313=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7310602811363762313==
Content-Type: multipart/alternative; boundary=0016e6d97676aa2bc104c1c8b022

--0016e6d97676aa2bc104c1c8b022
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6d97676aa2bc104c1c8b022
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen and I encount a problem in=
 my new new job with 2 Xen Hyper-visor.
We've 2 HV which access on y=
our NAS by iSCSI to store our VM.
Or
 last time we start a VM on one HV without seen that it's was started o=
n
 the other HV. So we encounter some read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.



But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!



Kind regards,
Fabien

--0016e6d97676aa2bc104c1c8b022--


--===============7310602811363762313==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7310602811363762313==--


From xen-users-bounces@lists.xen.org Wed Jun 06 07:28:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 07:28: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 1ScAdo-0005fi-7q; Wed, 06 Jun 2012 07:26:52 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScAdm-0005fd-RU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 07:26:51 +0000
Received: from [85.158.143.99:51244] by server-1.bemta-4.messagelabs.com id
	E5/6E-10042-A360FCF4; Wed, 06 Jun 2012 07:26:50 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-10.tower-216.messagelabs.com!1338967608!24953915!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1038 invoked from network); 6 Jun 2012 07:26:49 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 07:26:49 -0000
Received: by werf3 with SMTP id f3so5060369wer.32
	for ; Wed, 06 Jun 2012 00:26:48 -0700 (PDT)
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=9keH/fwwPpCWFK3Wq566M+yuWcfYLflBz9mn01qjbQw=;
	b=wIp+4YkSW8sJ0SqEDNJv3BzrLwU9g7TjN2t4z8M/S3dw9afL+hBT5iSgibdcU8h5c2
	e9OM35EFtIDk9wuf+F0wthv8v+rUdLYBd1cVAjJHwNSDLzrQitOmgRcm+O1+ap3HHxsX
	WO4nuiHjGYPEhZ3Svy06RSxZ4uYHVBEnzBgXtVlw57OT+F/7ciyu0AJHUBW15ru7FB28
	i59jQ0vos3fpn1kUpD6uZk5SmGPaHKcQemgMb540HLnFL0SpB6I8YG0ggNMEcbtbhzVj
	syOgt+7QspDJE0IvPfCmpixNIHd1Ut2J8sdxdyQtUwk/nNScoMKJ9i7NWx78w489QYdR
	GglA==
MIME-Version: 1.0
Received: by 10.216.196.90 with SMTP id q68mr17855622wen.130.1338967608404;
	Wed, 06 Jun 2012 00:26:48 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Wed, 6 Jun 2012 00:26:48 -0700 (PDT)
Date: Wed, 6 Jun 2012 09:26:48 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
Subject: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7310602811363762313=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7310602811363762313==
Content-Type: multipart/alternative; boundary=0016e6d97676aa2bc104c1c8b022

--0016e6d97676aa2bc104c1c8b022
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6d97676aa2bc104c1c8b022
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen and I encount a problem in=
 my new new job with 2 Xen Hyper-visor.
We've 2 HV which access on y=
our NAS by iSCSI to store our VM.
Or
 last time we start a VM on one HV without seen that it's was started o=
n
 the other HV. So we encounter some read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.



But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!



Kind regards,
Fabien

--0016e6d97676aa2bc104c1c8b022--


--===============7310602811363762313==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7310602811363762313==--


From xen-users-bounces@lists.xen.org Wed Jun 06 08:38:13 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:38: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 1ScBj9-0007CL-2n; Wed, 06 Jun 2012 08:36:27 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScBj7-0007CG-QU
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 08:36:26 +0000
Received: from [85.158.143.99:21112] by server-3.bemta-4.messagelabs.com id
	3A/61-29237-9861FCF4; Wed, 06 Jun 2012 08:36:25 +0000
X-Env-Sender: felixchu@powerallnetworks.com
X-Msg-Ref: server-8.tower-216.messagelabs.com!1338971780!21739022!1
X-Originating-IP: [203.131.233.195]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12206 invoked from network); 6 Jun 2012 08:36:22 -0000
Received: from mail5.powerallnetworks.com (HELO imail1.powerallnetworks.com)
	(203.131.233.195)
	by server-8.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 6 Jun 2012 08:36:22 -0000
Received: from adminPC ([203.131.232.80])
	by imail1.powerallnetworks.com (8.13.8/8.13.8) with ESMTP id
	q568aHTa011540
	for ; Wed, 6 Jun 2012 16:36:17 +0800
From: "Felix Chu" 
To: 
Date: Wed, 6 Jun 2012 16:35:46 +0800
Message-ID: <619e01cd43bf$5e9574c0$1bc05e40$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Dv141UftAyduKTVajKwR1McB17A==
Content-Language: zh-hk
X-PA-MailFilter-Information: 
X-PA-MailFilter-ID: q568aHTa011540
X-PA-MailFilter-SpamCheck: not spam, SpamAssassin (not cached, score=2.735,
	required 8, autolearn=disabled, DOS_OUTLOOK_TO_MX 1.45,
	FSL_HELO_NON_FQDN_1 0.00, HTML_MESSAGE 0.00, NO_RDNS2 0.01,
	RDNS_NONE 1.27)
X-PA-MailFilter-From: felixchu@powerallnetworks.com
X-Spam-Status: No
Subject: [Xen-users] About 10GE performane on domU (with xen3.4.4)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6984825499234435069=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.

--===============6984825499234435069==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_619F_01CD4402.6CB8B4C0"
Content-Language: zh-hk

This is a multi-part message in MIME format.

------=_NextPart_000_619F_01CD4402.6CB8B4C0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi all,

 

I have two Dell R720xd servers dom0 running with Centos 5.8 (with xen 3.4.4)
installed with Intel 10GE (ixgbe driver) interface. I test TCP transfer rate
between dom0, speed is 7.x Gbps (with Netperf tool).  However, I try similar
test between two domU, speed drop to 1.x Gbps.

 

domU is running with Centos5.8 (64bit) para-virtualized (yum updated to
latest packages). 

 

Test 1:  dom0 -> dom0 , speed 7.x Gbps

Test 2:  domU -> dom0 , speed 7.xGbps

Test 3:  dom0-> domU , speed 1.x Gbps

Test 4:  domU -> domU ,speed 1.x Gbps

 

Above tests are carried between two physical machines. From above 4 tests,
seems bottleneck on domU RX speed. 

 

I suspect related to xen network driver issue on domU. Anyone know any
optimization can be done on domU?

 

Thanks a lot.

Felix


------=_NextPart_000_619F_01CD4402.6CB8B4C0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable


Hi =
all,
 
I have two Dell R720xd servers dom0 running with Centos 5.8 =
(with xen 3.4.4) installed with Intel 10GE (ixgbe driver) interface. I =
test TCP transfer rate between dom0, speed is 7.x Gbps (with Netperf =
tool).  However, I try similar test between two domU, speed drop to =
1.x Gbps.
 
domU is running with Centos5.8 (64bit) para-virtualized =
(yum updated to latest packages). 
 
Test 1:  dom0 -> dom0 , =
speed 7.x Gbps
Test 2:  domU -> dom0 , speed =
7.xGbps
Test 3:  dom0-> domU , speed 1.x =
Gbps
Test =
4:  domU -> domU ,speed 1.x Gbps
 
Above tests are carried between two =
physical machines. From above 4 tests, seems bottleneck on domU RX =
speed. 
 
I suspect related to xen network driver issue on domU. =
Anyone know any optimization can be done on =
domU?
 
Thanks a lot.
Felix

------=_NextPart_000_619F_01CD4402.6CB8B4C0--



--===============6984825499234435069==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6984825499234435069==--



From xen-users-bounces@lists.xen.org Wed Jun 06 08:38:13 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:38: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 1ScBj9-0007CL-2n; Wed, 06 Jun 2012 08:36:27 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScBj7-0007CG-QU
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 08:36:26 +0000
Received: from [85.158.143.99:21112] by server-3.bemta-4.messagelabs.com id
	3A/61-29237-9861FCF4; Wed, 06 Jun 2012 08:36:25 +0000
X-Env-Sender: felixchu@powerallnetworks.com
X-Msg-Ref: server-8.tower-216.messagelabs.com!1338971780!21739022!1
X-Originating-IP: [203.131.233.195]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12206 invoked from network); 6 Jun 2012 08:36:22 -0000
Received: from mail5.powerallnetworks.com (HELO imail1.powerallnetworks.com)
	(203.131.233.195)
	by server-8.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 6 Jun 2012 08:36:22 -0000
Received: from adminPC ([203.131.232.80])
	by imail1.powerallnetworks.com (8.13.8/8.13.8) with ESMTP id
	q568aHTa011540
	for ; Wed, 6 Jun 2012 16:36:17 +0800
From: "Felix Chu" 
To: 
Date: Wed, 6 Jun 2012 16:35:46 +0800
Message-ID: <619e01cd43bf$5e9574c0$1bc05e40$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Dv141UftAyduKTVajKwR1McB17A==
Content-Language: zh-hk
X-PA-MailFilter-Information: 
X-PA-MailFilter-ID: q568aHTa011540
X-PA-MailFilter-SpamCheck: not spam, SpamAssassin (not cached, score=2.735,
	required 8, autolearn=disabled, DOS_OUTLOOK_TO_MX 1.45,
	FSL_HELO_NON_FQDN_1 0.00, HTML_MESSAGE 0.00, NO_RDNS2 0.01,
	RDNS_NONE 1.27)
X-PA-MailFilter-From: felixchu@powerallnetworks.com
X-Spam-Status: No
Subject: [Xen-users] About 10GE performane on domU (with xen3.4.4)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6984825499234435069=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.

--===============6984825499234435069==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_619F_01CD4402.6CB8B4C0"
Content-Language: zh-hk

This is a multi-part message in MIME format.

------=_NextPart_000_619F_01CD4402.6CB8B4C0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi all,

 

I have two Dell R720xd servers dom0 running with Centos 5.8 (with xen 3.4.4)
installed with Intel 10GE (ixgbe driver) interface. I test TCP transfer rate
between dom0, speed is 7.x Gbps (with Netperf tool).  However, I try similar
test between two domU, speed drop to 1.x Gbps.

 

domU is running with Centos5.8 (64bit) para-virtualized (yum updated to
latest packages). 

 

Test 1:  dom0 -> dom0 , speed 7.x Gbps

Test 2:  domU -> dom0 , speed 7.xGbps

Test 3:  dom0-> domU , speed 1.x Gbps

Test 4:  domU -> domU ,speed 1.x Gbps

 

Above tests are carried between two physical machines. From above 4 tests,
seems bottleneck on domU RX speed. 

 

I suspect related to xen network driver issue on domU. Anyone know any
optimization can be done on domU?

 

Thanks a lot.

Felix


------=_NextPart_000_619F_01CD4402.6CB8B4C0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable


Hi =
all,
 
I have two Dell R720xd servers dom0 running with Centos 5.8 =
(with xen 3.4.4) installed with Intel 10GE (ixgbe driver) interface. I =
test TCP transfer rate between dom0, speed is 7.x Gbps (with Netperf =
tool).  However, I try similar test between two domU, speed drop to =
1.x Gbps.
 
domU is running with Centos5.8 (64bit) para-virtualized =
(yum updated to latest packages). 
 
Test 1:  dom0 -> dom0 , =
speed 7.x Gbps
Test 2:  domU -> dom0 , speed =
7.xGbps
Test 3:  dom0-> domU , speed 1.x =
Gbps
Test =
4:  domU -> domU ,speed 1.x Gbps
 
Above tests are carried between two =
physical machines. From above 4 tests, seems bottleneck on domU RX =
speed. 
 
I suspect related to xen network driver issue on domU. =
Anyone know any optimization can be done on =
domU?
 
Thanks a lot.
Felix

------=_NextPart_000_619F_01CD4402.6CB8B4C0--



--===============6984825499234435069==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6984825499234435069==--



From xen-users-bounces@lists.xen.org Wed Jun 06 08:52:10 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:52: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 1ScBwy-0007V9-3X; Wed, 06 Jun 2012 08:50:44 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScBww-0007Ut-6f
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:50:42 +0000
Received: from [85.158.143.99:16960] by server-3.bemta-4.messagelabs.com id
	CE/C9-29237-1E91FCF4; Wed, 06 Jun 2012 08:50:41 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-216.messagelabs.com!1338972639!30627028!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29425 invoked from network); 6 Jun 2012 08:50:40 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:50:40 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852383"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:50:38 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:50:37 +0100
Message-ID: <1338972636.32319.12.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Will McDermott 
Date: Wed, 6 Jun 2012 09:50:36 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: Anthony Perard ,
	"xen-users@lists.xen.org" ,
	Stefano Stabellini ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gU3VuLCAyMDEyLTA2LTAzIGF0IDIyOjE2ICswMTAwLCBXaWxsIE1jRGVybW90dCB3cm90ZToK
PiBIZWxsbywKPiAKPiBJIGFtIHRyeWluZyB0byBjb21waWxlIHhlbiA0LjIgdW5zdGFibGUgZnJv
bSBtZXJjdXJpYWwuIEkgY2FuJ3QgZ2V0IHBhc3QKPiB0aGUgbWFrZSB0b29scyBzdGVwLiBXaGVu
IEkgcnVuIG1ha2UgdG9vbHMsIHRoZSBidWlsZCBmYWlscyB3aXRoOgoKVGhhbmtzIFdpbGwsIHRo
aXMgbG9va3MgbGlrZSBhIG5ldyBvbmUsIEkndmUgbm90IG5vdGljZWQgYW55IHJlcG9ydHMgb2YK
dGhpcyBiZWZvcmUuIENDaW5nIHhlbi1kZXZlbEAgYW5kIG91ciBRZW11IGZvbGtzLgoKR3V5cywg
dGhpcyBsb29rcyBsaWtlCmh0dHA6Ly9saXN0cy5nbnUub3JnL2FyY2hpdmUvaHRtbC9xZW11LWRl
dmVsLzIwMTItMDIvbXNnMDM0NjAuaHRtbCBvcgpodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91
YnVudHUvK3NvdXJjZS9xZW11LWt2bS8rYnVnLzkzMDE4MSAod2hpY2gKV2lsbCByZWZlcmVuY2Vz
IGJlbG93KS4gSSBkaWRuJ3QgbG9vayBpZiBhbnkgcGF0Y2ggaGFzIGdvbmUgaW4gdXBzdHJlYW0K
b3Igbm90LgoKSSBjYW4ndCBleHBsYWluIHdoeSBvdGhlciBVYnVudHUgdXNlcnMgYXJlbid0IHNl
ZWluZyB0aGlzIHRob3VnaC4KCklhbi4KCj4gCj4gQ0MgICAgbGliaHc2NC85cGZzL2NveGF0dHIu
bwo+ICAgQ0MgICAgbGliaHc2NC85cGZzL3ZpcnRpby05cC1zeW50aC5vCj4gICBDQyAgICBsaWJo
dzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDD
omhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzo3MDo1ODoKPiBub3RlOiBlYWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBp
cyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2ggZnVuY3Rpb24KPiBpdCBhcHBlYXJzIGluCj4g
L3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05
cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
ODc6MzQ6Cj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6IEluCj4gZnVuY3Rpb24gw6JoYW5kbGVfc3lt
bGlua8OiOgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOgo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1
bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPiAvcm9vdC94ZW4tdW5zdGFi
bGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgo+
IGZ1bmN0aW9uIMOiaGFuZGxlX2xpbmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOgo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6MzczOjU4Ogo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikKPiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5vXSBFcnJvciAxCj4gbWFrZVszXTogKioqIFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMgo+IG1h
a2VbM106IExlYXZpbmcgZGlyZWN0b3J5Cj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXItcmVtb3RlJwo+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14
ZW4tZGlyXSBFcnJvciAyCj4gbWFrZVsyXTogTGVhdmluZyBkaXJlY3RvcnkgYC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scycKPiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3Ig
Mgo+IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9v
bHMnCj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4gCj4gSSBhbSBydW5uaW5n
IHVidW50dSAxMi4wNCwga2VybmVsIHZlcjogMy4yLjAtMjQtZ2VuZXJpYyAKPiAKPiBBbnkgaWRl
YXM/IEkgaGF2ZSBnb29nbGVkIGZ1cmlvdXNseSBhbmQgZm91bmQgc29tZSBwZW9wbGUgdGFsa2lu
ZyBhYm91dAo+IHFlbXUta3ZtIGhhdmluZyB0aGUgc2FtZSBpc3N1ZToKPiBodHRwczovL2J1Z3Mu
bGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9xZW11LWt2bS8rYnVnLzkzMDE4MQo+IEJ1dCBJ
IHdhcyBub3QgYWJsZSB0byBmaW5kIHRoZSBwYXRjaAo+IAo+IFRoYW5rcyBpbiBhZHZhbmNlIQo+
IAo+IAo+IAo+IE1lcmN1cmlhbG0KPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwo+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPiBYZW4tdXNlcnNAbGlz
dHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2VycwoKCgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBs
aXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vy
cw==

From xen-users-bounces@lists.xen.org Wed Jun 06 08:52:10 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:52: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 1ScBwy-0007V9-3X; Wed, 06 Jun 2012 08:50:44 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScBww-0007Ut-6f
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:50:42 +0000
Received: from [85.158.143.99:16960] by server-3.bemta-4.messagelabs.com id
	CE/C9-29237-1E91FCF4; Wed, 06 Jun 2012 08:50:41 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-216.messagelabs.com!1338972639!30627028!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29425 invoked from network); 6 Jun 2012 08:50:40 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:50:40 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852383"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:50:38 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:50:37 +0100
Message-ID: <1338972636.32319.12.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Will McDermott 
Date: Wed, 6 Jun 2012 09:50:36 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: Anthony Perard ,
	"xen-users@lists.xen.org" ,
	Stefano Stabellini ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gU3VuLCAyMDEyLTA2LTAzIGF0IDIyOjE2ICswMTAwLCBXaWxsIE1jRGVybW90dCB3cm90ZToK
PiBIZWxsbywKPiAKPiBJIGFtIHRyeWluZyB0byBjb21waWxlIHhlbiA0LjIgdW5zdGFibGUgZnJv
bSBtZXJjdXJpYWwuIEkgY2FuJ3QgZ2V0IHBhc3QKPiB0aGUgbWFrZSB0b29scyBzdGVwLiBXaGVu
IEkgcnVuIG1ha2UgdG9vbHMsIHRoZSBidWlsZCBmYWlscyB3aXRoOgoKVGhhbmtzIFdpbGwsIHRo
aXMgbG9va3MgbGlrZSBhIG5ldyBvbmUsIEkndmUgbm90IG5vdGljZWQgYW55IHJlcG9ydHMgb2YK
dGhpcyBiZWZvcmUuIENDaW5nIHhlbi1kZXZlbEAgYW5kIG91ciBRZW11IGZvbGtzLgoKR3V5cywg
dGhpcyBsb29rcyBsaWtlCmh0dHA6Ly9saXN0cy5nbnUub3JnL2FyY2hpdmUvaHRtbC9xZW11LWRl
dmVsLzIwMTItMDIvbXNnMDM0NjAuaHRtbCBvcgpodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91
YnVudHUvK3NvdXJjZS9xZW11LWt2bS8rYnVnLzkzMDE4MSAod2hpY2gKV2lsbCByZWZlcmVuY2Vz
IGJlbG93KS4gSSBkaWRuJ3QgbG9vayBpZiBhbnkgcGF0Y2ggaGFzIGdvbmUgaW4gdXBzdHJlYW0K
b3Igbm90LgoKSSBjYW4ndCBleHBsYWluIHdoeSBvdGhlciBVYnVudHUgdXNlcnMgYXJlbid0IHNl
ZWluZyB0aGlzIHRob3VnaC4KCklhbi4KCj4gCj4gQ0MgICAgbGliaHc2NC85cGZzL2NveGF0dHIu
bwo+ICAgQ0MgICAgbGliaHc2NC85cGZzL3ZpcnRpby05cC1zeW50aC5vCj4gICBDQyAgICBsaWJo
dzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDD
omhhbmRsZV91cGRhdGVfZmlsZV9jcmVkw6I6Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzo3MDo1ODoKPiBub3RlOiBlYWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBp
cyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2ggZnVuY3Rpb24KPiBpdCBhcHBlYXJzIGluCj4g
L3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05
cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
ODc6MzQ6Cj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp
biB0aGlzIGZ1bmN0aW9uKQo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6IEluCj4gZnVuY3Rpb24gw6JoYW5kbGVfc3lt
bGlua8OiOgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzE0OjYyOgo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1
bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKPiAvcm9vdC94ZW4tdW5zdGFi
bGUuaGcvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOiBJbgo+
IGZ1bmN0aW9uIMOiaGFuZGxlX2xpbmvDojoKPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPiBlcnJvcjog
w6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p
Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRp
by05cC1oYW5kbGUuYzogSW4KPiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOgo+IC9yb290L3hl
bi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxl
LmM6MzczOjU4Ogo+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikKPiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRs
ZS5vXSBFcnJvciAxCj4gbWFrZVszXTogKioqIFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMgo+IG1h
a2VbM106IExlYXZpbmcgZGlyZWN0b3J5Cj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXItcmVtb3RlJwo+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14
ZW4tZGlyXSBFcnJvciAyCj4gbWFrZVsyXTogTGVhdmluZyBkaXJlY3RvcnkgYC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scycKPiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3Ig
Mgo+IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9v
bHMnCj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4gCj4gSSBhbSBydW5uaW5n
IHVidW50dSAxMi4wNCwga2VybmVsIHZlcjogMy4yLjAtMjQtZ2VuZXJpYyAKPiAKPiBBbnkgaWRl
YXM/IEkgaGF2ZSBnb29nbGVkIGZ1cmlvdXNseSBhbmQgZm91bmQgc29tZSBwZW9wbGUgdGFsa2lu
ZyBhYm91dAo+IHFlbXUta3ZtIGhhdmluZyB0aGUgc2FtZSBpc3N1ZToKPiBodHRwczovL2J1Z3Mu
bGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9xZW11LWt2bS8rYnVnLzkzMDE4MQo+IEJ1dCBJ
IHdhcyBub3QgYWJsZSB0byBmaW5kIHRoZSBwYXRjaAo+IAo+IFRoYW5rcyBpbiBhZHZhbmNlIQo+
IAo+IAo+IAo+IE1lcmN1cmlhbG0KPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwo+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPiBYZW4tdXNlcnNAbGlz
dHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2VycwoKCgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBs
aXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vy
cw==

From xen-users-bounces@lists.xen.org Wed Jun 06 08:58:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:58: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 1ScC2v-00084D-Tc; Wed, 06 Jun 2012 08:56:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScC2u-000844-LA
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:56:52 +0000
Received: from [193.109.254.147:59859] by server-5.bemta-14.messagelabs.com id
	30/38-31398-35B1FCF4; Wed, 06 Jun 2012 08:56:51 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1338972998!8554612!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12623 invoked from network); 6 Jun 2012 08:56:38 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:56:38 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852525"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:56:38 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:56:37 +0100
Message-ID: <1338972996.32319.16.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Jason Davis 
Date: Wed, 6 Jun 2012 09:56:36 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Jason,

I've no idea about this issue I'm afraid.

This list is for users of the Open Source version of Xen rather than any
particular commercial product.

In general XenServer questions are best addressed to either your
XenServer support rep or to the appropriate forum on forums.citrix.com. 

Thanks,
Ian.

On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:
> One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> to XAPI calls being sent from a CloudStack management server. In the
> past, a simple xe-toolstack-restart would do the trick but the script
> timed out while restarting the XAPI daemon.
> 
> 
> I found the process and first tried to use a simple kill command but
> the process was in a "defunct" state. I tried a kill -9 but no joy. 
> 
> 
> I then found the xapi.pid and manually deleted it and then tried to
> run xe-toolstack-restart. Unfortunately this did not work and
> ultimately I had to reboot the cluster node.
> 
> 
> So... any other ideas on killing a zombie XAPI process? I've like to
> avoid rebooting a host :)



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 08:58:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:58: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 1ScC2v-00084D-Tc; Wed, 06 Jun 2012 08:56:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScC2u-000844-LA
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:56:52 +0000
Received: from [193.109.254.147:59859] by server-5.bemta-14.messagelabs.com id
	30/38-31398-35B1FCF4; Wed, 06 Jun 2012 08:56:51 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1338972998!8554612!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12623 invoked from network); 6 Jun 2012 08:56:38 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:56:38 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852525"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:56:38 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:56:37 +0100
Message-ID: <1338972996.32319.16.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Jason Davis 
Date: Wed, 6 Jun 2012 09:56:36 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Jason,

I've no idea about this issue I'm afraid.

This list is for users of the Open Source version of Xen rather than any
particular commercial product.

In general XenServer questions are best addressed to either your
XenServer support rep or to the appropriate forum on forums.citrix.com. 

Thanks,
Ian.

On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:
> One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> to XAPI calls being sent from a CloudStack management server. In the
> past, a simple xe-toolstack-restart would do the trick but the script
> timed out while restarting the XAPI daemon.
> 
> 
> I found the process and first tried to use a simple kill command but
> the process was in a "defunct" state. I tried a kill -9 but no joy. 
> 
> 
> I then found the xapi.pid and manually deleted it and then tried to
> run xe-toolstack-restart. Unfortunately this did not work and
> ultimately I had to reboot the cluster node.
> 
> 
> So... any other ideas on killing a zombie XAPI process? I've like to
> avoid rebooting a host :)



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 08:59:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:59:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScC3z-0008A5-OJ; Wed, 06 Jun 2012 08:57:59 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScC3y-00089h-Or
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:57:58 +0000
Received: from [193.109.254.147:12740] by server-1.bemta-14.messagelabs.com id
	AA/48-08067-59B1FCF4; Wed, 06 Jun 2012 08:57:57 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1338973077!6192179!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17544 invoked from network); 6 Jun 2012 08:57:57 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:57:57 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852544"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:57:57 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:57:56 +0100
Message-ID: <1338973075.32319.17.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: pf shineyear 
Date: Wed, 6 Jun 2012 09:57:55 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org
Subject: Re: [Xen-users] need your help with xcp vlan
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Peter,

Questions  about XCP are more likely to be answered on the xen-api@ list
(yes, this name is non-obvious -- we are working to fix this). I've CCd
that list for you.

Cheers,
Ian.


On Tue, 2012-06-05 at 04:51 +0100, pf shineyear wrote:
> hi all, 
> 
> 
> im peter, i found the post
> here http://www.gossamer-threads.com/lists/xen/users/229738
> 
> 
> i build a small test env, with 2 vm in 1 server with xcp 1.1.0
> 
> 
> i use xe network-create and xe vlan-create to build the vlan for each
> vm.
> 
> 
> then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list
> port i can see all these info about fake-bridge and vlan tag is
> correct.
> 
> 
> but when i start 2 vms, and try to ping the dom0 ip , i got fault, all
> iptables in dom0 and vms are closed.
> 
> 
> do you know what is the reson of this?
> 
> 
> thanks for your help.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 08:59:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 08:59:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScC3z-0008A5-OJ; Wed, 06 Jun 2012 08:57:59 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScC3y-00089h-Or
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 08:57:58 +0000
Received: from [193.109.254.147:12740] by server-1.bemta-14.messagelabs.com id
	AA/48-08067-59B1FCF4; Wed, 06 Jun 2012 08:57:57 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1338973077!6192179!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17544 invoked from network); 6 Jun 2012 08:57:57 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 08:57:57 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852544"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 08:57:57 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	09:57:56 +0100
Message-ID: <1338973075.32319.17.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: pf shineyear 
Date: Wed, 6 Jun 2012 09:57:55 +0100
In-Reply-To: 
References: 
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org
Subject: Re: [Xen-users] need your help with xcp vlan
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Peter,

Questions  about XCP are more likely to be answered on the xen-api@ list
(yes, this name is non-obvious -- we are working to fix this). I've CCd
that list for you.

Cheers,
Ian.


On Tue, 2012-06-05 at 04:51 +0100, pf shineyear wrote:
> hi all, 
> 
> 
> im peter, i found the post
> here http://www.gossamer-threads.com/lists/xen/users/229738
> 
> 
> i build a small test env, with 2 vm in 1 server with xcp 1.1.0
> 
> 
> i use xe network-create and xe vlan-create to build the vlan for each
> vm.
> 
> 
> then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list
> port i can see all these info about fake-bridge and vlan tag is
> correct.
> 
> 
> but when i start 2 vms, and try to ping the dom0 ip , i got fault, all
> iptables in dom0 and vms are closed.
> 
> 
> do you know what is the reson of this?
> 
> 
> thanks for your help.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 09:08:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:08: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 1ScCDN-0000cl-38; Wed, 06 Jun 2012 09:07:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCDL-0000cf-5U
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:07:39 +0000
Received: from [193.109.254.147:55282] by server-11.bemta-14.messagelabs.com
	id 73/C0-02727-ADD1FCF4; Wed, 06 Jun 2012 09:07:38 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1338973657!7865502!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10836 invoked from network); 6 Jun 2012 09:07:37 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:07:37 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852836"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 09:07:37 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	10:07:37 +0100
Message-ID: <1338973656.32319.24.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "bill@b2bassadventures.com" 
Date: Wed, 6 Jun 2012 10:07:36 +0100
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, 2012-06-05 at 04:35 +0100, Bill Beauchemin wrote:
> My main question is if nthere is a tutorial that can help me with
> getting xen installed and configured correctly, configure a guest,
> install a guest, and boot the guest using the above configuration? 

The Debian wiki has a page on Xen which covers the basic host install
http://wiki.debian.org/Xen . I've been working on this page recently, if
anything isn't clear or you think could be expressed better please do
feel free to edit it (or just send me your feedbak).

That same page also has some discussion of guest install methods, e.g.
using the xen-tools package (which builds on debootstrap). Another
option for installing a Debian guest is to use the normal Debian
installer. This is described in:
http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer

Some other pages of interest:
http://wiki.xen.org/wiki/Category:Debian
http://wiki.xen.org/wiki/Category:Host_Install
http://wiki.xen.org/wiki/Category:Guest_Install
http://wiki.xen.org/wiki/Getting_Started

As others have mentioned you are probably better off using LVM than
dedicating actual partitions to the guests (although this will work).

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 09:08:42 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:08: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 1ScCDN-0000cl-38; Wed, 06 Jun 2012 09:07:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCDL-0000cf-5U
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:07:39 +0000
Received: from [193.109.254.147:55282] by server-11.bemta-14.messagelabs.com
	id 73/C0-02727-ADD1FCF4; Wed, 06 Jun 2012 09:07:38 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1338973657!7865502!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10836 invoked from network); 6 Jun 2012 09:07:37 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:07:37 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852836"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 09:07:37 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	10:07:37 +0100
Message-ID: <1338973656.32319.24.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "bill@b2bassadventures.com" 
Date: Wed, 6 Jun 2012 10:07:36 +0100
In-Reply-To: <4FCD7E6D.5070004@b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, 2012-06-05 at 04:35 +0100, Bill Beauchemin wrote:
> My main question is if nthere is a tutorial that can help me with
> getting xen installed and configured correctly, configure a guest,
> install a guest, and boot the guest using the above configuration? 

The Debian wiki has a page on Xen which covers the basic host install
http://wiki.debian.org/Xen . I've been working on this page recently, if
anything isn't clear or you think could be expressed better please do
feel free to edit it (or just send me your feedbak).

That same page also has some discussion of guest install methods, e.g.
using the xen-tools package (which builds on debootstrap). Another
option for installing a Debian guest is to use the normal Debian
installer. This is described in:
http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer

Some other pages of interest:
http://wiki.xen.org/wiki/Category:Debian
http://wiki.xen.org/wiki/Category:Host_Install
http://wiki.xen.org/wiki/Category:Guest_Install
http://wiki.xen.org/wiki/Getting_Started

As others have mentioned you are probably better off using LVM than
dedicating actual partitions to the guests (although this will work).

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 09:10:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:10: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 1ScCEv-0000jW-QJ; Wed, 06 Jun 2012 09:09:17 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCEt-0000jI-Ev
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:09:15 +0000
Received: from [85.158.138.51:46845] by server-10.bemta-3.messagelabs.com id
	8E/9C-06494-A3E1FCF4; Wed, 06 Jun 2012 09:09:14 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-16.tower-174.messagelabs.com!1338973746!28145367!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n,
	ML_RADAR_SPEW_LINKS_8, spamassassin: ,
	async_handler: YXN5bmNfZGVsYXk6IDcwNDQ5NzAgKHRpbWVvdXQp\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21787 invoked from network); 6 Jun 2012 09:09:06 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:09:06 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852872"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 09:09:05 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	10:09:05 +0100
Message-ID: <1338973744.32319.25.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: dhyn lav 
Date: Wed, 6 Jun 2012 10:09:04 +0100
In-Reply-To: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
References: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xend error in logs file
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, 2012-06-05 at 19:11 +0100, dhyn lav wrote:
> Hi,
> 
> 
> I am using Centos 6.2 64bit minimal and xen 4.1.2 from crc.id.au. When
> centos with xen started I noticed some error in xend logs. I try to
> search in google but I can't find good answer on this.

I see DEBUG, INFO and WARNINGS but no ERRORS and nothing which suggests
something has gone wrong (these logs look pretty typical to me).

What misbehaviour are you observing?

Ian.

> 
> 
> xend.log
> 
> 
> [2012-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon started
> [2012-06-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset:
> unavailable.
> [2012-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record count: 8
> [2012-06-06 01:33:00 2501] DEBUG (XendCPUPool:747)
> recreate_active_pools
> [2012-06-06 01:33:00 2501] DEBUG (XendDomainInfo:151)
> XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 7012131419L,
> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0,
> 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running':
> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1048576L,
> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0], 'cpupool': 0, 'name': 'Domain-0'})
> [2012-06-06 01:33:01 2501] INFO (XendDomainInfo:169) Recreating domain
> 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:3420) Storing VM
> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0',
> 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000',
> 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0)
> (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy',
> 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash':
> 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1',
> 'bootloader': '', 'name': 'Domain-0'}
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1794) Storing domain
> details: {'description': '', 'console/limit': '1048576', 'vm':
> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
> 'cpu/0/availability': 'online', 'memory/target': '1048576',
> 'control/platform-feature-multiprocessor-suspend': '1',
> 'console/type': 'xenconsoled', 'name': 'Domain-0'}
> [2012-06-06 01:33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomain:410) number of vcpus to
> use is 0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1881)
> XendDomainInfo.handleShutdownWatch
> [2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix
> path=/var/lib/xend/xend-socket
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VBD.set_device not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VBD.set_type not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> session.get_all_records not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> event.get_record not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> event.get_all not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VIF.set_device not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_MAC
> not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_MTU
> not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> debug.get_all not found
> [2012-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xen-api.sock; authentication
> has been disabled for this server.
> [2012-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xmlrpc.sock.
> 
> 
> xend-debug.log
> 
> 
> Xend started at Wed Jun  6 01:33:00 2012.
> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host0/model: No such file or directory
> cat: /sys/bus/scsi/devices/host0/type: No such file or directory
> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host1/model: No such file or directory
> cat: /sys/bus/scsi/devices/host1/type: No such file or directory
> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host2/model: No such file or directory
> cat: /sys/bus/scsi/devices/host2/type: No such file or directory
> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host3/model: No such file or directory
> cat: /sys/bus/scsi/devices/host3/type: No such file or directory
> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/vendor: No such file or
> directory
> cat: /sys/bus/scsi/devices/target2:0:1/model: No such file or
> directory
> cat: /sys/bus/scsi/devices/target2:0:1/type: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/rev: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/scsi_level: No such file or
> directory
> /usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551:
> DeprecationWarning: object.__new__() takes no parameters
>   return object.__new__(cls, *args, **kwds)
> 
> 





_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 09:10:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:10: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 1ScCEv-0000jW-QJ; Wed, 06 Jun 2012 09:09:17 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCEt-0000jI-Ev
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:09:15 +0000
Received: from [85.158.138.51:46845] by server-10.bemta-3.messagelabs.com id
	8E/9C-06494-A3E1FCF4; Wed, 06 Jun 2012 09:09:14 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-16.tower-174.messagelabs.com!1338973746!28145367!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDEwODk=\n,
	ML_RADAR_SPEW_LINKS_8, spamassassin: ,
	async_handler: YXN5bmNfZGVsYXk6IDcwNDQ5NzAgKHRpbWVvdXQp\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21787 invoked from network); 6 Jun 2012 09:09:06 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:09:06 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12852872"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 09:09:05 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	10:09:05 +0100
Message-ID: <1338973744.32319.25.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: dhyn lav 
Date: Wed, 6 Jun 2012 10:09:04 +0100
In-Reply-To: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
References: <1338919872.48944.YahooMailNeo@web39303.mail.mud.yahoo.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xend error in logs file
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Tue, 2012-06-05 at 19:11 +0100, dhyn lav wrote:
> Hi,
> 
> 
> I am using Centos 6.2 64bit minimal and xen 4.1.2 from crc.id.au. When
> centos with xen started I noticed some error in xend logs. I try to
> search in google but I can't find good answer on this.

I see DEBUG, INFO and WARNINGS but no ERRORS and nothing which suggests
something has gone wrong (these logs look pretty typical to me).

What misbehaviour are you observing?

Ian.

> 
> 
> xend.log
> 
> 
> [2012-06-06 01:33:00 2501] INFO (SrvDaemon:339) Xend Daemon started
> [2012-06-06 01:33:00 2501] INFO (SrvDaemon:343) Xend changeset:
> unavailable.
> [2012-06-06 01:33:00 2501] DEBUG (XendNode:332) pscsi record count: 8
> [2012-06-06 01:33:00 2501] DEBUG (XendCPUPool:747)
> recreate_active_pools
> [2012-06-06 01:33:00 2501] DEBUG (XendDomainInfo:151)
> XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 7012131419L,
> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0,
> 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running':
> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1048576L,
> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0], 'cpupool': 0, 'name': 'Domain-0'})
> [2012-06-06 01:33:01 2501] INFO (XendDomainInfo:169) Recreating domain
> 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:3420) Storing VM
> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0',
> 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000',
> 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0)
> (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy',
> 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash':
> 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1',
> 'bootloader': '', 'name': 'Domain-0'}
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1794) Storing domain
> details: {'description': '', 'console/limit': '1048576', 'vm':
> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
> 'cpu/0/availability': 'online', 'memory/target': '1048576',
> 'control/platform-feature-multiprocessor-suspend': '1',
> 'console/type': 'xenconsoled', 'name': 'Domain-0'}
> [2012-06-06 01:33:01 2501] DEBUG (XendDomain:476) Adding Domain: 0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomain:410) number of vcpus to
> use is 0
> [2012-06-06 01:33:01 2501] DEBUG (XendDomainInfo:1881)
> XendDomainInfo.handleShutdownWatch
> [2012-06-06 01:33:01 2501] INFO (SrvServer:184) unix
> path=/var/lib/xend/xend-socket
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VBD.set_device not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VBD.set_type not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> session.get_all_records not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> event.get_record not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> event.get_all not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> VIF.set_device not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_MAC
> not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call: VIF.set_MTU
> not found
> [2012-06-06 01:33:01 2501] WARNING (XendAPI:708) API call:
> debug.get_all not found
> [2012-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xen-api.sock; authentication
> has been disabled for this server.
> [2012-06-06 01:33:01 2501] INFO (XMLRPCServer:161) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xmlrpc.sock.
> 
> 
> xend-debug.log
> 
> 
> Xend started at Wed Jun  6 01:33:00 2012.
> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host0/model: No such file or directory
> cat: /sys/bus/scsi/devices/host0/type: No such file or directory
> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host1/model: No such file or directory
> cat: /sys/bus/scsi/devices/host1/type: No such file or directory
> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host2/model: No such file or directory
> cat: /sys/bus/scsi/devices/host2/type: No such file or directory
> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host3/model: No such file or directory
> cat: /sys/bus/scsi/devices/host3/type: No such file or directory
> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/vendor: No such file or
> directory
> cat: /sys/bus/scsi/devices/target2:0:1/model: No such file or
> directory
> cat: /sys/bus/scsi/devices/target2:0:1/type: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/rev: No such file or directory
> cat: /sys/bus/scsi/devices/target2:0:1/scsi_level: No such file or
> directory
> /usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551:
> DeprecationWarning: object.__new__() takes no parameters
>   return object.__new__(cls, *args, **kwds)
> 
> 





_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 09:31:27 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:31:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScCZQ-0002Pt-AG; Wed, 06 Jun 2012 09:30:28 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCZO-0002Po-LU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:30:26 +0000
Received: from [85.158.138.51:53699] by server-8.bemta-3.messagelabs.com id
	DB/82-22118-1332FCF4; Wed, 06 Jun 2012 09:30:25 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1338975024!31045213!1
X-Originating-IP: [74.125.82.51]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4063 invoked from network); 6 Jun 2012 09:30:25 -0000
Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com)
	(74.125.82.51)
	by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:30:25 -0000
Received: by wgbed3 with SMTP id ed3so4341939wgb.32
	for ; Wed, 06 Jun 2012 02:30:24 -0700 (PDT)
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
	:content-type; bh=VmZrG4tGiw/FpS7eq7hQnLIADKLoljdqekhRDbcAsjE=;
	b=zgQoyOI9hySz80nR2EKeBqPjYRJCc4z2esxtNCkl20izvjORa8UO5+YE33bCXWxUAa
	zRkGWgzcgw/d/BfIQju9MFi5zTKYmDKZ3UVZfB4QicxBNSr7uA+x7/fjFzLpKknKCny+
	7TDrgPd2Q4/D+va5JbPC2dqAVuqgp2/tyPGjxgaJa7mjSgd5njD2pr1Ov0hJBId8Tdfu
	rqYrbRokMmUwPzT54qSuAd0opevM6uvhaIIig5cJICUE4Qb+TuZj77QdSCgsTUUKgCyE
	mv7nsTuwdQzG2jsaedWuOd+HFY1h+kdssLwzMHv5rUjbILCgKbw2r5I0FZaapBIzwVE2
	3ZWQ==
MIME-Version: 1.0
Received: by 10.216.143.84 with SMTP id k62mr15749131wej.98.1338975024479;
	Wed, 06 Jun 2012 02:30:24 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Wed, 6 Jun 2012 02:30:24 -0700 (PDT)
In-Reply-To: 
References: 
Date: Wed, 6 Jun 2012 11:30:24 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
Subject: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6515086080692823758=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6515086080692823758==
Content-Type: multipart/alternative; boundary=0016e6d77eb0b27ffc04c1ca6a5e

--0016e6d77eb0b27ffc04c1ca6a5e
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6d77eb0b27ffc04c1ca6a5e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen=
 and I encount a problem in my new new job with 2 Xen Hyper-visor.
We=
9;ve 2 HV which access on your NAS by iSCSI to store our VM.
Or
 last time we start a VM on one HV without seen that it's was started o=
n
 the other HV. So we encounter some read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.




But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!




Kind regards,
Fabien




--0016e6d77eb0b27ffc04c1ca6a5e--


--===============6515086080692823758==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6515086080692823758==--


From xen-users-bounces@lists.xen.org Wed Jun 06 09:31:27 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 09:31:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScCZQ-0002Pt-AG; Wed, 06 Jun 2012 09:30:28 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScCZO-0002Po-LU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 09:30:26 +0000
Received: from [85.158.138.51:53699] by server-8.bemta-3.messagelabs.com id
	DB/82-22118-1332FCF4; Wed, 06 Jun 2012 09:30:25 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1338975024!31045213!1
X-Originating-IP: [74.125.82.51]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4063 invoked from network); 6 Jun 2012 09:30:25 -0000
Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com)
	(74.125.82.51)
	by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 09:30:25 -0000
Received: by wgbed3 with SMTP id ed3so4341939wgb.32
	for ; Wed, 06 Jun 2012 02:30:24 -0700 (PDT)
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
	:content-type; bh=VmZrG4tGiw/FpS7eq7hQnLIADKLoljdqekhRDbcAsjE=;
	b=zgQoyOI9hySz80nR2EKeBqPjYRJCc4z2esxtNCkl20izvjORa8UO5+YE33bCXWxUAa
	zRkGWgzcgw/d/BfIQju9MFi5zTKYmDKZ3UVZfB4QicxBNSr7uA+x7/fjFzLpKknKCny+
	7TDrgPd2Q4/D+va5JbPC2dqAVuqgp2/tyPGjxgaJa7mjSgd5njD2pr1Ov0hJBId8Tdfu
	rqYrbRokMmUwPzT54qSuAd0opevM6uvhaIIig5cJICUE4Qb+TuZj77QdSCgsTUUKgCyE
	mv7nsTuwdQzG2jsaedWuOd+HFY1h+kdssLwzMHv5rUjbILCgKbw2r5I0FZaapBIzwVE2
	3ZWQ==
MIME-Version: 1.0
Received: by 10.216.143.84 with SMTP id k62mr15749131wej.98.1338975024479;
	Wed, 06 Jun 2012 02:30:24 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Wed, 6 Jun 2012 02:30:24 -0700 (PDT)
In-Reply-To: 
References: 
Date: Wed, 6 Jun 2012 11:30:24 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
Subject: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6515086080692823758=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6515086080692823758==
Content-Type: multipart/alternative; boundary=0016e6d77eb0b27ffc04c1ca6a5e

--0016e6d77eb0b27ffc04c1ca6a5e
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6d77eb0b27ffc04c1ca6a5e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen=
 and I encount a problem in my new new job with 2 Xen Hyper-visor.
We=
9;ve 2 HV which access on your NAS by iSCSI to store our VM.
Or
 last time we start a VM on one HV without seen that it's was started o=
n
 the other HV. So we encounter some read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.




But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!




Kind regards,
Fabien




--0016e6d77eb0b27ffc04c1ca6a5e--


--===============6515086080692823758==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6515086080692823758==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:11:46 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:11: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 1ScDC1-0003uf-TL; Wed, 06 Jun 2012 10:10:21 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDC0-0003ua-2l
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 10:10:20 +0000
Received: from [85.158.143.35:13646] by server-3.bemta-4.messagelabs.com id
	C9/98-29237-B8C2FCF4; Wed, 06 Jun 2012 10:10:19 +0000
X-Env-Sender: sr@swisscenter.com
X-Msg-Ref: server-9.tower-21.messagelabs.com!1338977412!7697710!1
X-Originating-IP: [94.103.96.90]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23206 invoked from network); 6 Jun 2012 10:10:13 -0000
Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90)
	by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 6 Jun 2012 10:10:13 -0000
Received: from [10.8.0.18] (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
	q56AA8Se012315
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2012 12:10:11 +0200
Message-ID: <4FCF2C75.7080800@swisscenter.com>
Date: Wed, 06 Jun 2012 12:09:57 +0200
From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Felix Chu 
References: <619e01cd43bf$5e9574c0$1bc05e40$@com>
In-Reply-To: <619e01cd43bf$5e9574c0$1bc05e40$@com>
X-Virus-Scanned: clamav-milter 0.97.3 at mail
X-Virus-Status: Clean
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] About 10GE performane on domU (with xen3.4.4)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8907933497172910620=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8907933497172910620==
Content-Type: multipart/alternative;
 boundary="------------030407010007030303060501"

This is a multi-part message in MIME format.
--------------030407010007030303060501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

Have you already tried thoses suggestions:

http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide

Cheers,
Sébastien

On 06.06.2012 10:35, Felix Chu wrote:
>
> Hi all,
>
> I have two Dell R720xd servers dom0 running with Centos 5.8 (with xen 
> 3.4.4) installed with Intel 10GE (ixgbe driver) interface. I test TCP 
> transfer rate between dom0, speed is 7.x Gbps (with Netperf tool).  
> However, I try similar test between two domU, speed drop to 1.x Gbps.
>
> domU is running with Centos5.8 (64bit) para-virtualized (yum updated 
> to latest packages).
>
> Test 1:  dom0 -> dom0 , speed 7.x Gbps
>
> Test 2:  domU -> dom0 , speed 7.xGbps
>
> Test 3:  dom0-> domU , speed 1.x Gbps
>
> Test 4:  domU -> domU ,speed 1.x Gbps
>
> Above tests are carried between two physical machines. From above 4 
> tests, seems bottleneck on domU RX speed.
>
> I suspect related to xen network driver issue on domU. Anyone know any 
> optimization can be done on domU?
>
> Thanks a lot.
>
> Felix
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------030407010007030303060501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hi,

    

    Have you already tried thoses suggestions:

    

    http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide

    

    Cheers,

    Sébastien

    

    On 06.06.2012 10:35, Felix Chu wrote:
    

      
      
      
      

        
Hi all,

        
 

        
I have two Dell R720xd
            servers dom0 running with Centos 5.8 (with xen 3.4.4)
            installed with Intel 10GE (ixgbe driver) interface. I test
            TCP transfer rate between dom0, speed is 7.x Gbps (with
            Netperf tool).  However, I try similar test between two
            domU, speed drop to 1.x Gbps.

        
 

        
domU is running with
            Centos5.8 (64bit) para-virtualized (yum updated to latest
            packages). 

        
 

        
Test 1:  dom0 -> dom0
            , speed 7.x Gbps

        
Test 2:  domU -> dom0
            , speed 7.xGbps

        
Test 3:  dom0-> domU
            , speed 1.x Gbps

        
Test 4:  domU -> domU
            ,speed 1.x Gbps

        
 

        
Above tests are carried
            between two physical machines. From above 4 tests, seems
            bottleneck on domU RX speed. 

        
 

        
I suspect related to xen
            network driver issue on domU. Anyone know any optimization
            can be done on domU?

        
 

        
Thanks a lot.

        
Felix

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------030407010007030303060501--


--===============8907933497172910620==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8907933497172910620==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:11:46 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:11: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 1ScDC1-0003uf-TL; Wed, 06 Jun 2012 10:10:21 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDC0-0003ua-2l
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 10:10:20 +0000
Received: from [85.158.143.35:13646] by server-3.bemta-4.messagelabs.com id
	C9/98-29237-B8C2FCF4; Wed, 06 Jun 2012 10:10:19 +0000
X-Env-Sender: sr@swisscenter.com
X-Msg-Ref: server-9.tower-21.messagelabs.com!1338977412!7697710!1
X-Originating-IP: [94.103.96.90]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23206 invoked from network); 6 Jun 2012 10:10:13 -0000
Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90)
	by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 6 Jun 2012 10:10:13 -0000
Received: from [10.8.0.18] (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
	q56AA8Se012315
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2012 12:10:11 +0200
Message-ID: <4FCF2C75.7080800@swisscenter.com>
Date: Wed, 06 Jun 2012 12:09:57 +0200
From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Felix Chu 
References: <619e01cd43bf$5e9574c0$1bc05e40$@com>
In-Reply-To: <619e01cd43bf$5e9574c0$1bc05e40$@com>
X-Virus-Scanned: clamav-milter 0.97.3 at mail
X-Virus-Status: Clean
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] About 10GE performane on domU (with xen3.4.4)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8907933497172910620=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8907933497172910620==
Content-Type: multipart/alternative;
 boundary="------------030407010007030303060501"

This is a multi-part message in MIME format.
--------------030407010007030303060501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

Have you already tried thoses suggestions:

http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide

Cheers,
Sébastien

On 06.06.2012 10:35, Felix Chu wrote:
>
> Hi all,
>
> I have two Dell R720xd servers dom0 running with Centos 5.8 (with xen 
> 3.4.4) installed with Intel 10GE (ixgbe driver) interface. I test TCP 
> transfer rate between dom0, speed is 7.x Gbps (with Netperf tool).  
> However, I try similar test between two domU, speed drop to 1.x Gbps.
>
> domU is running with Centos5.8 (64bit) para-virtualized (yum updated 
> to latest packages).
>
> Test 1:  dom0 -> dom0 , speed 7.x Gbps
>
> Test 2:  domU -> dom0 , speed 7.xGbps
>
> Test 3:  dom0-> domU , speed 1.x Gbps
>
> Test 4:  domU -> domU ,speed 1.x Gbps
>
> Above tests are carried between two physical machines. From above 4 
> tests, seems bottleneck on domU RX speed.
>
> I suspect related to xen network driver issue on domU. Anyone know any 
> optimization can be done on domU?
>
> Thanks a lot.
>
> Felix
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------030407010007030303060501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hi,

    

    Have you already tried thoses suggestions:

    

    http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide

    

    Cheers,

    Sébastien

    

    On 06.06.2012 10:35, Felix Chu wrote:
    

      
      
      
      

        
Hi all,

        
 

        
I have two Dell R720xd
            servers dom0 running with Centos 5.8 (with xen 3.4.4)
            installed with Intel 10GE (ixgbe driver) interface. I test
            TCP transfer rate between dom0, speed is 7.x Gbps (with
            Netperf tool).  However, I try similar test between two
            domU, speed drop to 1.x Gbps.

        
 

        
domU is running with
            Centos5.8 (64bit) para-virtualized (yum updated to latest
            packages). 

        
 

        
Test 1:  dom0 -> dom0
            , speed 7.x Gbps

        
Test 2:  domU -> dom0
            , speed 7.xGbps

        
Test 3:  dom0-> domU
            , speed 1.x Gbps

        
Test 4:  domU -> domU
            ,speed 1.x Gbps

        
 

        
Above tests are carried
            between two physical machines. From above 4 tests, seems
            bottleneck on domU RX speed. 

        
 

        
I suspect related to xen
            network driver issue on domU. Anyone know any optimization
            can be done on domU?

        
 

        
Thanks a lot.

        
Felix

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------030407010007030303060501--


--===============8907933497172910620==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8907933497172910620==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:13:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:13: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 1ScDDz-00041N-H2; Wed, 06 Jun 2012 10:12:23 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDDx-00040I-Lv
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:12:22 +0000
Received: from [193.109.254.147:31760] by server-8.bemta-14.messagelabs.com id
	AB/A8-27132-30D2FCF4; Wed, 06 Jun 2012 10:12:19 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-8.tower-27.messagelabs.com!1338977537!11173630!1
X-Originating-IP: [209.85.215.173]
X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_90_100,HTML_MESSAGE,
	RCVD_BY_IP,SUSPICIOUS_RECIPS
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21885 invoked from network); 6 Jun 2012 10:12:18 -0000
Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com)
	(209.85.215.173)
	by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:12:18 -0000
Received: by eaak12 with SMTP id k12so2010881eaa.32
	for ; Wed, 06 Jun 2012 03:12:17 -0700 (PDT)
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;
	bh=j1L6KX7djOOcneGy8ooWyiyXvSUfMTq3wiuC01nevjA=;
	b=GKbeiVIhjFIvtIOIEVEVvayLp42qoACskLE/WymZdrRalMrk7bG1IsytvdqMDtd8zA
	+sZIaTrz5tsje0MB+F7amWvHVsecG4RDaMVH3DKYk+/ReC4QOJ5UXSdTZMG8m1+S2m+0
	mki7mPySi3N+/W/K4Ji4GhzhGB5qKJABkzjsNaPVPfo9mAjkJLSCJSp1p8jcyp/Bfr/U
	CIflsOQF6cxxRqY1KwGP5HA38FsdxsHjXi3uuuNOimuSKC39SHPMTCnD8T1VCCrGccGe
	+Ibcu5RAEKMiKEi2DfIp88iAE9TcTDIZDwnVK4cmSKEqMY4fhNDTxCGkJMOvKnikdjX1
	Hz/w==
Received: by 10.14.100.205 with SMTP id z53mr8992919eef.39.1338977537286;
	Wed, 06 Jun 2012 03:12:17 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id t3sm4605616eeb.15.2012.06.06.03.12.14
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 03:12:16 -0700 (PDT)
Message-ID: <4FCF2CFD.7070606@xen.org>
Date: Wed, 06 Jun 2012 11:12:13 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-announce@lists.xen.org, 
	"xen-api@lists.xen.org" ,
	xen-users@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org
Subject: [Xen-users] Submit a Proposal to Speak at XenSummit North America
 2012 before the CFP Deadline, June 15th!
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8914034647390403900=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8914034647390403900==
Content-Type: multipart/alternative;
 boundary="------------010405050404010608000400"

This is a multi-part message in MIME format.
--------------010405050404010608000400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

XenSummit · August 27-28, 2012 · Sheraton San Diego · San Diego, CA, USA


    Submit a Proposal to Speak at XenSummit North America 2012 before
    the CFP Deadline, June 15th!


        XenSummit North America
        August 27-28, 2012 -- San Diego, CA

Xen.org invites developers, users, researchers, open source projects and 
businesses who are developing and/or using Xen to submit a proposal for 
XenSummit North America 2012.

*Submit a speaking proposal for XenSummit North America 2012 
*


      Suggested topics for XenSummit America include:

  * Latest developments and features in Xen and related projects
  * Developments in upstream projects that impact the Xen community
  * Proposals on how to evolve Xen and related projects in future
  * Research using Xen and related projects
  * Proof of concepts and other interesting technologies related to Xen
  * Other topics related to developing and using Xen
  * Technologies and technology trends that will impact Xen development
    in future

  * User experiences and case studies with Xen or XCP
  * Benchmarks, case studies, improvement suggestions and other lessons
    learned
  * Innovative ways of using Xen and related projects
  * Open source projects and products that interface or build on top of
    Xen or related projects
  * Usage of Xen in server virtualization, cloud computing,
    clientvirtualization, mobile spaces, etc.

  *   Any other topics that you feel are relevant to developers, users,
    researchers and other members of the Xen community


We will have 30, 45 and 60 minute talking slots (including questions). 
Please choose the type of session when you submit a proposal.


      About XenSummit

XenSummit is the annual technical conference for Xen developers and 
users in North America. The conference provides a collaboration and 
education space for the Xen community and brings together a 
cross-section of the leading players in the Xen community, innovative 
and timely content and a wide variety of opportunities for attendee 
collaboration. This year, XenSummit is co-located with other industry 
events such as LinuxCon NA 
, Linux Plumbers 
Conference , Linux Kernel Summit 
, 
CloudOpen  and 
others 
, 
which will maximise opportunities for cross-community collaboration.

*Learn more about XenSummit* 
*Register for XenSummit* 


--------------010405050404010608000400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    
    
    
XenSummit · August 27-28, 2012 · Sheraton San Diego ·
          San
 Diego, CA, USA

    
Submit a Proposal
        to Speak at XenSummit North America 2012 before the CFP
        Deadline, June 15th!

    
XenSummit North
        America

        August 27-28, 2012 – San Diego, CA

    
Xen.org invites developers, users, researchers, open source
      projects and
      businesses who are developing and/or using Xen to submit a
      proposal for
      XenSummit North America 2012.

    
Submit a
            speaking proposal
            for XenSummit North America 2012

    
Suggested topics
        for XenSummit America include:

    
    
      
  • Latest
          developments and features in Xen and related projects
    • 
      
  • Developments
          in upstream projects that impact the Xen community
    • 
      
  • Proposals
          on how to evolve Xen and related projects in future
    • 
      
  • Research
          using Xen and related projects
    • 
      
  • Proof
          of concepts and other interesting technologies related to Xen
    • 
      
  • Other
          topics related to developing and using Xen
    • 
      
  • Technologies
          and technology trends that will impact Xen development in
          future
    • 
    

    
    
      
  • User
          experiences and case studies with Xen or XCP
    • 
      
  • Benchmarks,
          case studies, improvement suggestions and other lessons
          learned
    • 
      
  • Innovative
          ways of using Xen and related projects
    
        
    • 
      
  • Open
          source projects and products that interface or build on top of
          Xen or related projects
    • 
      
  • Usage of Xen in
          server virtualization, cloud computing, client
          virtualization, mobile spaces, etc. 
    
        
    • 
    

    
    
    
      
  •  Any
          other topics that you feel are relevant to developers,
        users, researchers and other members of the Xen community
    
      
    • 
    

    


        We
        will have 30, 45 and 60 minute talking slots (including
        questions). Please
        choose the type of session when you submit a proposal. 

    
About XenSummit

    
XenSummit is the annual technical conference for Xen developers
      and users in
      North America. The conference provides a collaboration and
      education space for
      the Xen community and brings together a cross-section of the
      leading players in
      the Xen community, innovative and timely content and a wide
      variety of
      opportunities for attendee collaboration. This year, XenSummit is
      co-located
      with other industry events such as LinuxCon
        NA, Linux
        Plumbers Conference, Linux
Kernel
        Summit, CloudOpen
      and others,
      which will maximise opportunities for cross-community
      collaboration.

    Learn
          more about XenSummit

      Register
for
          XenSummit
    
    
    
    
    
    
    
    
  


--------------010405050404010608000400--


--===============8914034647390403900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8914034647390403900==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:13:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:13: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 1ScDDz-00041N-H2; Wed, 06 Jun 2012 10:12:23 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDDx-00040I-Lv
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:12:22 +0000
Received: from [193.109.254.147:31760] by server-8.bemta-14.messagelabs.com id
	AB/A8-27132-30D2FCF4; Wed, 06 Jun 2012 10:12:19 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-8.tower-27.messagelabs.com!1338977537!11173630!1
X-Originating-IP: [209.85.215.173]
X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_90_100,HTML_MESSAGE,
	RCVD_BY_IP,SUSPICIOUS_RECIPS
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21885 invoked from network); 6 Jun 2012 10:12:18 -0000
Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com)
	(209.85.215.173)
	by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:12:18 -0000
Received: by eaak12 with SMTP id k12so2010881eaa.32
	for ; Wed, 06 Jun 2012 03:12:17 -0700 (PDT)
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;
	bh=j1L6KX7djOOcneGy8ooWyiyXvSUfMTq3wiuC01nevjA=;
	b=GKbeiVIhjFIvtIOIEVEVvayLp42qoACskLE/WymZdrRalMrk7bG1IsytvdqMDtd8zA
	+sZIaTrz5tsje0MB+F7amWvHVsecG4RDaMVH3DKYk+/ReC4QOJ5UXSdTZMG8m1+S2m+0
	mki7mPySi3N+/W/K4Ji4GhzhGB5qKJABkzjsNaPVPfo9mAjkJLSCJSp1p8jcyp/Bfr/U
	CIflsOQF6cxxRqY1KwGP5HA38FsdxsHjXi3uuuNOimuSKC39SHPMTCnD8T1VCCrGccGe
	+Ibcu5RAEKMiKEi2DfIp88iAE9TcTDIZDwnVK4cmSKEqMY4fhNDTxCGkJMOvKnikdjX1
	Hz/w==
Received: by 10.14.100.205 with SMTP id z53mr8992919eef.39.1338977537286;
	Wed, 06 Jun 2012 03:12:17 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id t3sm4605616eeb.15.2012.06.06.03.12.14
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 03:12:16 -0700 (PDT)
Message-ID: <4FCF2CFD.7070606@xen.org>
Date: Wed, 06 Jun 2012 11:12:13 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-announce@lists.xen.org, 
	"xen-api@lists.xen.org" ,
	xen-users@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org
Subject: [Xen-users] Submit a Proposal to Speak at XenSummit North America
 2012 before the CFP Deadline, June 15th!
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8914034647390403900=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8914034647390403900==
Content-Type: multipart/alternative;
 boundary="------------010405050404010608000400"

This is a multi-part message in MIME format.
--------------010405050404010608000400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

XenSummit · August 27-28, 2012 · Sheraton San Diego · San Diego, CA, USA


    Submit a Proposal to Speak at XenSummit North America 2012 before
    the CFP Deadline, June 15th!


        XenSummit North America
        August 27-28, 2012 -- San Diego, CA

Xen.org invites developers, users, researchers, open source projects and 
businesses who are developing and/or using Xen to submit a proposal for 
XenSummit North America 2012.

*Submit a speaking proposal for XenSummit North America 2012 
*


      Suggested topics for XenSummit America include:

  * Latest developments and features in Xen and related projects
  * Developments in upstream projects that impact the Xen community
  * Proposals on how to evolve Xen and related projects in future
  * Research using Xen and related projects
  * Proof of concepts and other interesting technologies related to Xen
  * Other topics related to developing and using Xen
  * Technologies and technology trends that will impact Xen development
    in future

  * User experiences and case studies with Xen or XCP
  * Benchmarks, case studies, improvement suggestions and other lessons
    learned
  * Innovative ways of using Xen and related projects
  * Open source projects and products that interface or build on top of
    Xen or related projects
  * Usage of Xen in server virtualization, cloud computing,
    clientvirtualization, mobile spaces, etc.

  *   Any other topics that you feel are relevant to developers, users,
    researchers and other members of the Xen community


We will have 30, 45 and 60 minute talking slots (including questions). 
Please choose the type of session when you submit a proposal.


      About XenSummit

XenSummit is the annual technical conference for Xen developers and 
users in North America. The conference provides a collaboration and 
education space for the Xen community and brings together a 
cross-section of the leading players in the Xen community, innovative 
and timely content and a wide variety of opportunities for attendee 
collaboration. This year, XenSummit is co-located with other industry 
events such as LinuxCon NA 
, Linux Plumbers 
Conference , Linux Kernel Summit 
, 
CloudOpen  and 
others 
, 
which will maximise opportunities for cross-community collaboration.

*Learn more about XenSummit* 
*Register for XenSummit* 


--------------010405050404010608000400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    
    
    
XenSummit · August 27-28, 2012 · Sheraton San Diego ·
          San
 Diego, CA, USA

    
Submit a Proposal
        to Speak at XenSummit North America 2012 before the CFP
        Deadline, June 15th!

    
XenSummit North
        America

        August 27-28, 2012 – San Diego, CA

    
Xen.org invites developers, users, researchers, open source
      projects and
      businesses who are developing and/or using Xen to submit a
      proposal for
      XenSummit North America 2012.

    
Submit a
            speaking proposal
            for XenSummit North America 2012

    
Suggested topics
        for XenSummit America include:

    
    
      
  • Latest
          developments and features in Xen and related projects
    • 
      
  • Developments
          in upstream projects that impact the Xen community
    • 
      
  • Proposals
          on how to evolve Xen and related projects in future
    • 
      
  • Research
          using Xen and related projects
    • 
      
  • Proof
          of concepts and other interesting technologies related to Xen
    • 
      
  • Other
          topics related to developing and using Xen
    • 
      
  • Technologies
          and technology trends that will impact Xen development in
          future
    • 
    

    
    
      
  • User
          experiences and case studies with Xen or XCP
    • 
      
  • Benchmarks,
          case studies, improvement suggestions and other lessons
          learned
    • 
      
  • Innovative
          ways of using Xen and related projects
    
        
    • 
      
  • Open
          source projects and products that interface or build on top of
          Xen or related projects
    • 
      
  • Usage of Xen in
          server virtualization, cloud computing, client
          virtualization, mobile spaces, etc. 
    
        
    • 
    

    
    
    
      
  •  Any
          other topics that you feel are relevant to developers,
        users, researchers and other members of the Xen community
    
      
    • 
    

    


        We
        will have 30, 45 and 60 minute talking slots (including
        questions). Please
        choose the type of session when you submit a proposal. 

    
About XenSummit

    
XenSummit is the annual technical conference for Xen developers
      and users in
      North America. The conference provides a collaboration and
      education space for
      the Xen community and brings together a cross-section of the
      leading players in
      the Xen community, innovative and timely content and a wide
      variety of
      opportunities for attendee collaboration. This year, XenSummit is
      co-located
      with other industry events such as LinuxCon
        NA, Linux
        Plumbers Conference, Linux
Kernel
        Summit, CloudOpen
      and others,
      which will maximise opportunities for cross-community
      collaboration.

    Learn
          more about XenSummit

      Register
for
          XenSummit
    
    
    
    
    
    
    
    
  


--------------010405050404010608000400--


--===============8914034647390403900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8914034647390403900==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:18:43 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:18:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDJF-0004m1-Ee; Wed, 06 Jun 2012 10:17:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDJD-0004lj-GK
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:17:47 +0000
Received: from [85.158.143.35:64845] by server-1.bemta-4.messagelabs.com id
	50/F8-10042-A4E2FCF4; Wed, 06 Jun 2012 10:17:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1338977865!14631389!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22106 invoked from network); 6 Jun 2012 10:17:46 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:17:46 -0000
Received: by eekd41 with SMTP id d41so2424043eek.32
	for ; Wed, 06 Jun 2012 03:17:45 -0700 (PDT)
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=o3gcKxT39GRkEilWhrK5OwPew+BeOdHCnysFqiJLrQo=;
	b=Lysxx9p9grPmN3UI1KUKmFbxfBVkwYb/SP76KkESLb/Z+lB0/+KPah8Me/Em5TGK2R
	msCwo5myfVu2DN+ntwl4JYCW3t5ApqddMEW+4HVIB+BJK5IPX3HF8ttj85XUQzzzPt6z
	CoFWx7LU2pVOwVzbIpLTQPRNq2biSVo3bz511UN7Q0fHcdOglz3kXdBrWieW2Uh8qnsa
	9ilmY733qt+NWv7Yfi+E/J45Ik7J0UOZB73OMgRAp10q/RgTUMvEQfTWPwyW8zeimaPL
	LRSCj1igUoSIjD3f8EZ81Nm93x5/3Ifw48KWv/IeFow1++3ykBe9T64MeCra7UCQWaBM
	0cQw==
Received: by 10.14.127.8 with SMTP id c8mr9486092eei.148.1338977865559;
	Wed, 06 Jun 2012 03:17:45 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id a16sm4721303eeg.0.2012.06.06.03.17.43
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 03:17:44 -0700 (PDT)
Message-ID: <4FCF2E46.8040909@xen.org>
Date: Wed, 06 Jun 2012 11:17:42 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCD7E6D.5070004@b2bassadventures.com>
	<1338973656.32319.24.camel@zakaz.uk.xensource.com>
In-Reply-To: <1338973656.32319.24.camel@zakaz.uk.xensource.com>
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Also http://wiki.xen.org/wiki/Xen_Beginners_Guide is a guide that shows =

how to get started with =93Squeeze=94 and Xen 4

On 06/06/2012 10:07, Ian Campbell wrote:
> On Tue, 2012-06-05 at 04:35 +0100, Bill Beauchemin wrote:
>> My main question is if nthere is a tutorial that can help me with
>> getting xen installed and configured correctly, configure a guest,
>> install a guest, and boot the guest using the above configuration?
> The Debian wiki has a page on Xen which covers the basic host install
> http://wiki.debian.org/Xen . I've been working on this page recently, if
> anything isn't clear or you think could be expressed better please do
> feel free to edit it (or just send me your feedbak).
>
> That same page also has some discussion of guest install methods, e.g.
> using the xen-tools package (which builds on debootstrap). Another
> option for installing a Debian guest is to use the normal Debian
> installer. This is described in:
> http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
>
> Some other pages of interest:
> http://wiki.xen.org/wiki/Category:Debian
> http://wiki.xen.org/wiki/Category:Host_Install
> http://wiki.xen.org/wiki/Category:Guest_Install
> http://wiki.xen.org/wiki/Getting_Started
>
> As others have mentioned you are probably better off using LVM than
> dedicating actual partitions to the guests (although this will work).
>
> Ian.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:18:43 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:18:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDJF-0004m1-Ee; Wed, 06 Jun 2012 10:17:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScDJD-0004lj-GK
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:17:47 +0000
Received: from [85.158.143.35:64845] by server-1.bemta-4.messagelabs.com id
	50/F8-10042-A4E2FCF4; Wed, 06 Jun 2012 10:17:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1338977865!14631389!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22106 invoked from network); 6 Jun 2012 10:17:46 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:17:46 -0000
Received: by eekd41 with SMTP id d41so2424043eek.32
	for ; Wed, 06 Jun 2012 03:17:45 -0700 (PDT)
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=o3gcKxT39GRkEilWhrK5OwPew+BeOdHCnysFqiJLrQo=;
	b=Lysxx9p9grPmN3UI1KUKmFbxfBVkwYb/SP76KkESLb/Z+lB0/+KPah8Me/Em5TGK2R
	msCwo5myfVu2DN+ntwl4JYCW3t5ApqddMEW+4HVIB+BJK5IPX3HF8ttj85XUQzzzPt6z
	CoFWx7LU2pVOwVzbIpLTQPRNq2biSVo3bz511UN7Q0fHcdOglz3kXdBrWieW2Uh8qnsa
	9ilmY733qt+NWv7Yfi+E/J45Ik7J0UOZB73OMgRAp10q/RgTUMvEQfTWPwyW8zeimaPL
	LRSCj1igUoSIjD3f8EZ81Nm93x5/3Ifw48KWv/IeFow1++3ykBe9T64MeCra7UCQWaBM
	0cQw==
Received: by 10.14.127.8 with SMTP id c8mr9486092eei.148.1338977865559;
	Wed, 06 Jun 2012 03:17:45 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id a16sm4721303eeg.0.2012.06.06.03.17.43
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 03:17:44 -0700 (PDT)
Message-ID: <4FCF2E46.8040909@xen.org>
Date: Wed, 06 Jun 2012 11:17:42 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCD7E6D.5070004@b2bassadventures.com>
	<1338973656.32319.24.camel@zakaz.uk.xensource.com>
In-Reply-To: <1338973656.32319.24.camel@zakaz.uk.xensource.com>
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Also http://wiki.xen.org/wiki/Xen_Beginners_Guide is a guide that shows =

how to get started with =93Squeeze=94 and Xen 4

On 06/06/2012 10:07, Ian Campbell wrote:
> On Tue, 2012-06-05 at 04:35 +0100, Bill Beauchemin wrote:
>> My main question is if nthere is a tutorial that can help me with
>> getting xen installed and configured correctly, configure a guest,
>> install a guest, and boot the guest using the above configuration?
> The Debian wiki has a page on Xen which covers the basic host install
> http://wiki.debian.org/Xen . I've been working on this page recently, if
> anything isn't clear or you think could be expressed better please do
> feel free to edit it (or just send me your feedbak).
>
> That same page also has some discussion of guest install methods, e.g.
> using the xen-tools package (which builds on debootstrap). Another
> option for installing a Debian guest is to use the normal Debian
> installer. This is described in:
> http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
>
> Some other pages of interest:
> http://wiki.xen.org/wiki/Category:Debian
> http://wiki.xen.org/wiki/Category:Host_Install
> http://wiki.xen.org/wiki/Category:Guest_Install
> http://wiki.xen.org/wiki/Getting_Started
>
> As others have mentioned you are probably better off using LVM than
> dedicating actual partitions to the guests (although this will work).
>
> Ian.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:21 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDKt-0004xg-R6; Wed, 06 Jun 2012 10:19:31 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbwAK-0003WG-DC
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 15:59:28 +0000
Received: from [85.158.138.51:37184] by server-8.bemta-3.messagelabs.com id
	70/46-22118-FDC2ECF4; Tue, 05 Jun 2012 15:59:27 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-9.tower-174.messagelabs.com!1338911966!30953922!1
X-Originating-IP: [209.85.212.169]
X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9885 invoked from network); 5 Jun 2012 15:59:26 -0000
Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com)
	(209.85.212.169)
	by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 15:59:26 -0000
Received: by wibhn14 with SMTP id hn14so3611421wib.2
	for ; Tue, 05 Jun 2012 08:59:26 -0700 (PDT)
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=E5kk3q/yB0W5/iS30EcXLBWXSUQE+St44tYXBvwNAkM=;
	b=V+oXvIeXkX+b2xHI19eVizWutkKph6UUx2nsPMm5q4gVnhChkrj/ahX+KHQHf+cn6h
	ZiWqkq/g5CvBVNxZgYGj9arWxW8TTWgQsD0wbQQv9Ze1geOfIMOynlEEQMJugDv1FqGU
	6Q5kN8QCdu2GKQmePPQlbDZgJvbGSWvrdHlOmUSRjG6ejiyP0YOHh/4JrZzPgbQuV61B
	gdI7spCvKO23ND6ZVDbhNn1BO7RhgksMOYVbQRS3DtQSf48fXGqmb5yrXEsywS2h7DAn
	m3KNA5wgAA/luzrmSHQi6vIGjCcO3R7ykHqHBCa3Xe89PFbVx2h2QJbV+s5ySLyW8Cm4
	2bxA==
MIME-Version: 1.0
Received: by 10.216.206.65 with SMTP id k43mr14546832weo.144.1338911966426;
	Tue, 05 Jun 2012 08:59:26 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Tue, 5 Jun 2012 08:59:26 -0700 (PDT)
Date: Tue, 5 Jun 2012 17:59:26 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] Lock dom0 on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4637887420652894569=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4637887420652894569==
Content-Type: multipart/alternative; boundary=0016e6db7dd724f4d604c1bbbc73

--0016e6db7dd724f4d604c1bbbc73
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6db7dd724f4d604c1bbbc73
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen and I encount a problem in=
 my new new job with 2 Xen Hyper-visor.
We've 2 HV which access on y=
our NAS by iSCSI to store our VM.
Or last time we start a VM on one HV w=
ithout seen that it's was started on the other HV. So we encounter some=
 read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.


But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!


Kind regards,
Fabien


--0016e6db7dd724f4d604c1bbbc73--


--===============4637887420652894569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4637887420652894569==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:21 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDKt-0004xg-R6; Wed, 06 Jun 2012 10:19:31 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbwAK-0003WG-DC
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 15:59:28 +0000
Received: from [85.158.138.51:37184] by server-8.bemta-3.messagelabs.com id
	70/46-22118-FDC2ECF4; Tue, 05 Jun 2012 15:59:27 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-9.tower-174.messagelabs.com!1338911966!30953922!1
X-Originating-IP: [209.85.212.169]
X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9885 invoked from network); 5 Jun 2012 15:59:26 -0000
Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com)
	(209.85.212.169)
	by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 15:59:26 -0000
Received: by wibhn14 with SMTP id hn14so3611421wib.2
	for ; Tue, 05 Jun 2012 08:59:26 -0700 (PDT)
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=E5kk3q/yB0W5/iS30EcXLBWXSUQE+St44tYXBvwNAkM=;
	b=V+oXvIeXkX+b2xHI19eVizWutkKph6UUx2nsPMm5q4gVnhChkrj/ahX+KHQHf+cn6h
	ZiWqkq/g5CvBVNxZgYGj9arWxW8TTWgQsD0wbQQv9Ze1geOfIMOynlEEQMJugDv1FqGU
	6Q5kN8QCdu2GKQmePPQlbDZgJvbGSWvrdHlOmUSRjG6ejiyP0YOHh/4JrZzPgbQuV61B
	gdI7spCvKO23ND6ZVDbhNn1BO7RhgksMOYVbQRS3DtQSf48fXGqmb5yrXEsywS2h7DAn
	m3KNA5wgAA/luzrmSHQi6vIGjCcO3R7ykHqHBCa3Xe89PFbVx2h2QJbV+s5ySLyW8Cm4
	2bxA==
MIME-Version: 1.0
Received: by 10.216.206.65 with SMTP id k43mr14546832weo.144.1338911966426;
	Tue, 05 Jun 2012 08:59:26 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Tue, 5 Jun 2012 08:59:26 -0700 (PDT)
Date: Tue, 5 Jun 2012 17:59:26 +0200
Message-ID: 
From: Xen Xen 
To: xen-users@lists.xen.org
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] Lock dom0 on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4637887420652894569=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4637887420652894569==
Content-Type: multipart/alternative; boundary=0016e6db7dd724f4d604c1bbbc73

--0016e6db7dd724f4d604c1bbbc73
Content-Type: text/plain; charset=ISO-8859-1

Dear everybody!

I'm a new user of Xen and I encount a problem in my new new job with 2 Xen
Hyper-visor.
We've 2 HV which access on your NAS by iSCSI to store our VM.
Or last time we start a VM on one HV without seen that it's was started on
the other HV. So we encounter some read-only file system error...
I want to avoid this problem.

My server run on Debian 6 with Xen 4.0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock-path
/etc/xen/xen_lock) but it unfortunately don't work...
I've another server where I export a folder in NFS. And I mount it on my 2
HV. It's working fine.
But when a VM start, nothing writing in the volume... So I can start the
same VM on the other HV...

Some have an idea why it doesn't work? Or another solution to avoid this
problem?
I'me sure Xen have a tool or something else to do this!

Kind regards,
Fabien

--0016e6db7dd724f4d604c1bbbc73
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear everybody!

I'm a new user of Xen and I encount a problem in=
 my new new job with 2 Xen Hyper-visor.
We've 2 HV which access on y=
our NAS by iSCSI to store our VM.
Or last time we start a VM on one HV w=
ithout seen that it's was started on the other HV. So we encounter some=
 read-only file system error...


I want to avoid this problem. 

My server run on Debian 6 with Xen 4.=
0.1
I try to implement the (xend_domain-lock yes) with (xend-domain-lock=
-path /etc/xen/xen_lock) but it unfortunately don't work...
I've=
 another server where I export a folder in NFS. And I mount it on my 2 HV. =
It's working fine.


But when a VM start, nothing writing in the volume... So I can start the sa=
me VM on the other HV...

Some have an idea why it doesn't work? =
Or another solution to avoid this problem?
I'me sure Xen have a tool=
 or something else to do this!


Kind regards,
Fabien


--0016e6db7dd724f4d604c1bbbc73--


--===============4637887420652894569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4637887420652894569==--


From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:22 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20: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 1ScDKt-0004xR-6Z; Wed, 06 Jun 2012 10:19:31 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbQr8-0008OV-2O
	for Xen-users@lists.xen.org; Mon, 04 Jun 2012 06:33:34 +0000
Received: from [85.158.143.35:17566] by server-2.bemta-4.messagelabs.com id
	6A/6B-11595-DB65CCF4; Mon, 04 Jun 2012 06:33:33 +0000
X-Env-Sender: subbaraobrahma@bel.co.in
X-Msg-Ref: server-8.tower-21.messagelabs.com!1338791610!13406476!1
X-Originating-IP: [117.239.61.165]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13300 invoked from network); 4 Jun 2012 06:33:32 -0000
Received: from mx1.bel.co.in (HELO mx1.bel.co.in) (117.239.61.165)
	by server-8.tower-21.messagelabs.com with SMTP;
	4 Jun 2012 06:33:32 -0000
X-AuditID: ac143209-b7fc56d000000a9d-03-4fcca196ab04
Received: from smtp.bel.co.in ( [172.20.50.5])
	by mx1.bel.co.in (Symantec Messaging Gateway) with SMTP id
	41.17.02717.691ACCF4; Mon,  4 Jun 2012 17:22:54 +0530 (IST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.bel.co.in (Postfix) with ESMTP id 61D52364A1B;
	Mon,  4 Jun 2012 12:11:43 +0530 (IST)
X-Virus-Scanned: amavisd-new at bel.co.in
Received: from smtp.bel.co.in ([127.0.0.1])
	by localhost (mx1.bel.co.in [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y6cdCsK12r9A; Mon,  4 Jun 2012 12:11:28 +0530 (IST)
Received: from imap2.bel.co.in (unknown [172.20.50.2])
	by smtp.bel.co.in (Postfix) with ESMTP id 42882364A06;
	Mon,  4 Jun 2012 12:11:26 +0530 (IST)
Received: from mail.bel.co.in (imap.bel.co.in [172.20.50.10])
	by imap2.bel.co.in (Postfix) with ESMTP id 1F913FFDDC;
	Mon,  4 Jun 2012 11:59:17 +0530 (IST)
Received: from 172.20.50.25 (SquirrelMail authenticated user subbaraobrahma)
	by mail.bel.co.in with HTTP; Mon, 4 Jun 2012 11:59:17 +0530
Message-ID: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
Date: Mon, 4 Jun 2012 11:59:17 +0530
From: subbaraobrahma@bel.co.in
To: Xen-users@lists.xen.org,
 xen-api@lists.xen.org
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
X-Brightmail-Tracker: H4sIAAAAAAAAA12Ta0gUURTHu/tydvXm7Oy63jbzMYSVkGb0oSClB0VFsFZaIYSNOu0urrvb
	zK6vKLYke1tU9tieKhWJaIRBWZisRZZGJSp+ECWsLCV6gqFY3bsPG/t27u9/zv2fc+4MJWe+
	UEbKanfxgp2zsSqNol6/WLnwXHWnadFADbv0mbdFsbSup1W5Qrbu6cMJWQbI1izP523WIl5I
	Sd+psUxMnlE6R5UllUNvVB4wqDgK1BSilyDv73JZIDag1wONqqNAQzH0LYCq3u9XBg5XAGpr
	rsQHCmctQK0XsgK8CaA7tdXBpPMAPfhwOyxwuApQ1+hBFbmXoWsBOvYqncSQXosqvnz1cwU9
	F33rqgUk1tHh6OdIoz9W0bHoz9cGOXHT4/4qPqUSHEXHoeHhfnngGi16fvGdfwQ5nYiePnqk
	CsRxqPzeJXlonFMN4/5YTTPocM8R5Smg90rKvZJyr6T8OpDXAVhYkpqcy9uS8xzJVvtdEFi4
	+j74UBXvAzQF2AjYsazTxCi5IrG00AcKKBkbBTsyMZqZ68gvtXCiJUdw23iR1cOYdRjDKZzr
	thWwRqjIwlQ3Re18sWjjXfiF2Vi4NrLDxERPaaJbdFrzrA63mOMWbD6AKDm+dkYXToL5XGkZ
	LzgCZj4wm1Kw0dDRU2FiaDPn4gt43skLIbWYolgEB0mbWoE38yW7rDZXSMZ1POmJlir+ZufA
	+a+xl0EqSPpNgGGudhNjlMr/tyyj1D5gpiJw387NZB2ikysUreagtQ6eJk1FhKjfdhasIJAJ
	QYnlHEjTpKOQNN3uBdhtjIZ7STFNMixu+9SURgMMf/LcxERKBOJmjIEeMkWUhP8zNMZDHama
	JVGne46APPxZ6GBfBpkD/6r/hmPgzi0YhgehfzYET/pfIcgko8XA1W3YKSqo/O9ixl+aHi4i
	KVB0cS7pDrvFdrLDIA3usI9AJgSn7bCXSIaQNN3J6AH6zNHmwS7Lpqtt85NS5hqGY3+NeS9t
	POwb07yM2FNVlp2W93Nj/97FiZ4T3UsU89Y0cWu2ZQgfk+w/VmlHDn3/llikTXtx7tjIjbOf
	PetbEs86+w4k9Io7VFljq8oTambwpZf3pL7tLTteOd45lL4hLWv7TWZQPblvaGWZ9vG1re13
	6lmFaOFSk+SCyP0FDzu50AIFAAA=
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] hi
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

hi sir,
i want to develop the small private cloud i.e iaas(infrastructure as a
service) using XEN. so i want the information to start up from scratch.
because i am new to this area.i want the sequence of documnets and
downloads from start.
if any personnel mail is there that is also welcome.
awaiting your early reply.


Confidentiality Notice

The information contained in this electronic message and any 
attachments to this message are intended for the exclusive use of
the addressee(s) and may contain confidential or privileged 
information. If you are not the intended recipient, please notify
the sender at Bharat Electronics  or support@bel.co.in immediately
and destroy all copies of this message and any attachments.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:22 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20: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 1ScDKt-0004xR-6Z; Wed, 06 Jun 2012 10:19:31 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SbQr8-0008OV-2O
	for Xen-users@lists.xen.org; Mon, 04 Jun 2012 06:33:34 +0000
Received: from [85.158.143.35:17566] by server-2.bemta-4.messagelabs.com id
	6A/6B-11595-DB65CCF4; Mon, 04 Jun 2012 06:33:33 +0000
X-Env-Sender: subbaraobrahma@bel.co.in
X-Msg-Ref: server-8.tower-21.messagelabs.com!1338791610!13406476!1
X-Originating-IP: [117.239.61.165]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13300 invoked from network); 4 Jun 2012 06:33:32 -0000
Received: from mx1.bel.co.in (HELO mx1.bel.co.in) (117.239.61.165)
	by server-8.tower-21.messagelabs.com with SMTP;
	4 Jun 2012 06:33:32 -0000
X-AuditID: ac143209-b7fc56d000000a9d-03-4fcca196ab04
Received: from smtp.bel.co.in ( [172.20.50.5])
	by mx1.bel.co.in (Symantec Messaging Gateway) with SMTP id
	41.17.02717.691ACCF4; Mon,  4 Jun 2012 17:22:54 +0530 (IST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.bel.co.in (Postfix) with ESMTP id 61D52364A1B;
	Mon,  4 Jun 2012 12:11:43 +0530 (IST)
X-Virus-Scanned: amavisd-new at bel.co.in
Received: from smtp.bel.co.in ([127.0.0.1])
	by localhost (mx1.bel.co.in [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y6cdCsK12r9A; Mon,  4 Jun 2012 12:11:28 +0530 (IST)
Received: from imap2.bel.co.in (unknown [172.20.50.2])
	by smtp.bel.co.in (Postfix) with ESMTP id 42882364A06;
	Mon,  4 Jun 2012 12:11:26 +0530 (IST)
Received: from mail.bel.co.in (imap.bel.co.in [172.20.50.10])
	by imap2.bel.co.in (Postfix) with ESMTP id 1F913FFDDC;
	Mon,  4 Jun 2012 11:59:17 +0530 (IST)
Received: from 172.20.50.25 (SquirrelMail authenticated user subbaraobrahma)
	by mail.bel.co.in with HTTP; Mon, 4 Jun 2012 11:59:17 +0530
Message-ID: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
Date: Mon, 4 Jun 2012 11:59:17 +0530
From: subbaraobrahma@bel.co.in
To: Xen-users@lists.xen.org,
 xen-api@lists.xen.org
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
X-Brightmail-Tracker: H4sIAAAAAAAAA12Ta0gUURTHu/tydvXm7Oy63jbzMYSVkGb0oSClB0VFsFZaIYSNOu0urrvb
	zK6vKLYke1tU9tieKhWJaIRBWZisRZZGJSp+ECWsLCV6gqFY3bsPG/t27u9/zv2fc+4MJWe+
	UEbKanfxgp2zsSqNol6/WLnwXHWnadFADbv0mbdFsbSup1W5Qrbu6cMJWQbI1izP523WIl5I
	Sd+psUxMnlE6R5UllUNvVB4wqDgK1BSilyDv73JZIDag1wONqqNAQzH0LYCq3u9XBg5XAGpr
	rsQHCmctQK0XsgK8CaA7tdXBpPMAPfhwOyxwuApQ1+hBFbmXoWsBOvYqncSQXosqvnz1cwU9
	F33rqgUk1tHh6OdIoz9W0bHoz9cGOXHT4/4qPqUSHEXHoeHhfnngGi16fvGdfwQ5nYiePnqk
	CsRxqPzeJXlonFMN4/5YTTPocM8R5Smg90rKvZJyr6T8OpDXAVhYkpqcy9uS8xzJVvtdEFi4
	+j74UBXvAzQF2AjYsazTxCi5IrG00AcKKBkbBTsyMZqZ68gvtXCiJUdw23iR1cOYdRjDKZzr
	thWwRqjIwlQ3Re18sWjjXfiF2Vi4NrLDxERPaaJbdFrzrA63mOMWbD6AKDm+dkYXToL5XGkZ
	LzgCZj4wm1Kw0dDRU2FiaDPn4gt43skLIbWYolgEB0mbWoE38yW7rDZXSMZ1POmJlir+ZufA
	+a+xl0EqSPpNgGGudhNjlMr/tyyj1D5gpiJw387NZB2ikysUreagtQ6eJk1FhKjfdhasIJAJ
	QYnlHEjTpKOQNN3uBdhtjIZ7STFNMixu+9SURgMMf/LcxERKBOJmjIEeMkWUhP8zNMZDHama
	JVGne46APPxZ6GBfBpkD/6r/hmPgzi0YhgehfzYET/pfIcgko8XA1W3YKSqo/O9ixl+aHi4i
	KVB0cS7pDrvFdrLDIA3usI9AJgSn7bCXSIaQNN3J6AH6zNHmwS7Lpqtt85NS5hqGY3+NeS9t
	POwb07yM2FNVlp2W93Nj/97FiZ4T3UsU89Y0cWu2ZQgfk+w/VmlHDn3/llikTXtx7tjIjbOf
	PetbEs86+w4k9Io7VFljq8oTambwpZf3pL7tLTteOd45lL4hLWv7TWZQPblvaGWZ9vG1re13
	6lmFaOFSk+SCyP0FDzu50AIFAAA=
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] hi
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

hi sir,
i want to develop the small private cloud i.e iaas(infrastructure as a
service) using XEN. so i want the information to start up from scratch.
because i am new to this area.i want the sequence of documnets and
downloads from start.
if any personnel mail is there that is also welcome.
awaiting your early reply.


Confidentiality Notice

The information contained in this electronic message and any 
attachments to this message are intended for the exclusive use of
the addressee(s) and may contain confidential or privileged 
information. If you are not the intended recipient, please notify
the sender at Bharat Electronics  or support@bel.co.in immediately
and destroy all copies of this message and any attachments.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:24 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20:24 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDKu-0004xt-G5; Wed, 06 Jun 2012 10:19:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbydo-0005rb-Tk
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 18:38:05 +0000
Received: from [85.158.139.83:28234] by server-8.bemta-5.messagelabs.com id
	87/B0-02058-C025ECF4; Tue, 05 Jun 2012 18:38:04 +0000
X-Env-Sender: wesley@terpstra.ca
X-Msg-Ref: server-14.tower-182.messagelabs.com!1338921481!27861318!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
  RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 708 invoked from network); 5 Jun 2012 18:38:03 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 18:38:03 -0000
Received: by dadv2 with SMTP id v2so8283891dad.32
	for ; Tue, 05 Jun 2012 11:38:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type
	:x-gm-message-state;
	bh=rbz0gAnKd6ywW9vuXyQYjTvChhG1hhG/JfadYcygkQg=;
	b=TyT3nYDHUwxm43yvB/HVZqp1AHSEAxl53s96B8kfoKxekZ+ZkoFgHlVjVmrqZVMzcE
	F0BEK7GnmdwDj5uQn4CYzm8pW+J5LK+7kFLBehMbUV1IPZQEBPNijkvJtRz4IQ+yZxiQ
	H2py1wVBMeklmdW1XUo87znRHpnIrLvzjjpyT1T430G6LLrrDTZkxmM/tzUA0vlWk/zX
	D1gDbimEBd2mSf0c38iqWDej2KutpFnnV/2EwRml1jldeTUxRUHCjCQZAVPFXs92yI9M
	cakrk9ouwi10p1U6FPgXLegcJZU9JtDEY/U2jPKrQnPJbqo+9NeSHVjtv/r86ADutC6v
	AAzA==
MIME-Version: 1.0
Received: by 10.68.241.162 with SMTP id wj2mr25442766pbc.91.1338921480284;
	Tue, 05 Jun 2012 11:38:00 -0700 (PDT)
Received: by 10.68.119.20 with HTTP; Tue, 5 Jun 2012 11:38:00 -0700 (PDT)
Date: Tue, 5 Jun 2012 20:38:00 +0200
Message-ID: 
From: "Wesley W. Terpstra" 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQmXM/Tbqm8vKft35/NeZumW+ScQbvGPiyguIMEsNONiIBIaPkwKhy6B/KHyWE2/Qn3hBgM0
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] pygrub: reboot causes on_poweroff instead of on_reboot
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Good evening!

I recently switched to using PyGrub to boot my domUs using their own
internal kernel and boot preference. Before I was using manual
"kernel+initd" options in the domu.sxp, both located in the dom0
file-system, I really appreciate this separation of concerns. While
the host boots correctly and I can select the kernel from "xm
console", the behaviour on reboot has changed.

My domu.sxp files contain:
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Before I switched to pygrub, "xm reboot domu" or "ssh domu reboot"
would trigger the on_reboot rule and restart the system. "xm shutdown
domu" or "ssh domu shutdown" would trigger the on_poweroff rule and
destroy the domu, ready to be "xm create"d with a new sxp.

After I switched to pygrub, "xm reboot domu", "ssh domu reboot", "xm
shutdown domu", and "ssh domu shutdown" all trigger the on_poweroff
condition. Since the administrators for the domu systems need to be
able to reboot their machines without access to the dom0, this
presents a problem---they can't "xm create" the host to restart them.

As a work-around, I have set on_poweroff = 'restart'. However, that is
not ideal either, because when I change a domu.sxp file, I used to be
able to "xm shutdown" and "xm create" to load the changes. Now, I must
"xm shutdown" and carefully time a "xm destroy" after the system
finishing quiting.

I am running:
Debian squeeze
dom0 kernel 3.2.0-0.bpo.2-amd64
domU kernel 2.6.32-5-xen-amd64
xen-hypervisor + xen-utils 4.0.1-4
xen-tools 4.2-1
... my pygrub comes from the xen-utils debian package, version 4.0.1-4.

Is this a known bug? Is there a good work around?

Thanks for the help!
Please CC me in your replies.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:20:24 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:20:24 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDKu-0004xt-G5; Wed, 06 Jun 2012 10:19:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sbydo-0005rb-Tk
	for xen-users@lists.xen.org; Tue, 05 Jun 2012 18:38:05 +0000
Received: from [85.158.139.83:28234] by server-8.bemta-5.messagelabs.com id
	87/B0-02058-C025ECF4; Tue, 05 Jun 2012 18:38:04 +0000
X-Env-Sender: wesley@terpstra.ca
X-Msg-Ref: server-14.tower-182.messagelabs.com!1338921481!27861318!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
  RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 708 invoked from network); 5 Jun 2012 18:38:03 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jun 2012 18:38:03 -0000
Received: by dadv2 with SMTP id v2so8283891dad.32
	for ; Tue, 05 Jun 2012 11:38:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type
	:x-gm-message-state;
	bh=rbz0gAnKd6ywW9vuXyQYjTvChhG1hhG/JfadYcygkQg=;
	b=TyT3nYDHUwxm43yvB/HVZqp1AHSEAxl53s96B8kfoKxekZ+ZkoFgHlVjVmrqZVMzcE
	F0BEK7GnmdwDj5uQn4CYzm8pW+J5LK+7kFLBehMbUV1IPZQEBPNijkvJtRz4IQ+yZxiQ
	H2py1wVBMeklmdW1XUo87znRHpnIrLvzjjpyT1T430G6LLrrDTZkxmM/tzUA0vlWk/zX
	D1gDbimEBd2mSf0c38iqWDej2KutpFnnV/2EwRml1jldeTUxRUHCjCQZAVPFXs92yI9M
	cakrk9ouwi10p1U6FPgXLegcJZU9JtDEY/U2jPKrQnPJbqo+9NeSHVjtv/r86ADutC6v
	AAzA==
MIME-Version: 1.0
Received: by 10.68.241.162 with SMTP id wj2mr25442766pbc.91.1338921480284;
	Tue, 05 Jun 2012 11:38:00 -0700 (PDT)
Received: by 10.68.119.20 with HTTP; Tue, 5 Jun 2012 11:38:00 -0700 (PDT)
Date: Tue, 5 Jun 2012 20:38:00 +0200
Message-ID: 
From: "Wesley W. Terpstra" 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQmXM/Tbqm8vKft35/NeZumW+ScQbvGPiyguIMEsNONiIBIaPkwKhy6B/KHyWE2/Qn3hBgM0
X-Mailman-Approved-At: Wed, 06 Jun 2012 10:19:30 +0000
Subject: [Xen-users] pygrub: reboot causes on_poweroff instead of on_reboot
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Good evening!

I recently switched to using PyGrub to boot my domUs using their own
internal kernel and boot preference. Before I was using manual
"kernel+initd" options in the domu.sxp, both located in the dom0
file-system, I really appreciate this separation of concerns. While
the host boots correctly and I can select the kernel from "xm
console", the behaviour on reboot has changed.

My domu.sxp files contain:
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Before I switched to pygrub, "xm reboot domu" or "ssh domu reboot"
would trigger the on_reboot rule and restart the system. "xm shutdown
domu" or "ssh domu shutdown" would trigger the on_poweroff rule and
destroy the domu, ready to be "xm create"d with a new sxp.

After I switched to pygrub, "xm reboot domu", "ssh domu reboot", "xm
shutdown domu", and "ssh domu shutdown" all trigger the on_poweroff
condition. Since the administrators for the domu systems need to be
able to reboot their machines without access to the dom0, this
presents a problem---they can't "xm create" the host to restart them.

As a work-around, I have set on_poweroff = 'restart'. However, that is
not ideal either, because when I change a domu.sxp file, I used to be
able to "xm shutdown" and "xm create" to load the changes. Now, I must
"xm shutdown" and carefully time a "xm destroy" after the system
finishing quiting.

I am running:
Debian squeeze
dom0 kernel 3.2.0-0.bpo.2-amd64
domU kernel 2.6.32-5-xen-amd64
xen-hypervisor + xen-utils 4.0.1-4
xen-tools 4.2-1
... my pygrub comes from the xen-utils debian package, version 4.0.1-4.

Is this a known bug? Is there a good work around?

Thanks for the help!
Please CC me in your replies.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:35:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:35: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 1ScDZM-00083a-Ah; Wed, 06 Jun 2012 10:34:28 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDZK-00083C-TT
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:34:27 +0000
Received: from [85.158.143.35:48230] by server-2.bemta-4.messagelabs.com id
	E8/98-17938-1323FCF4; Wed, 06 Jun 2012 10:34:25 +0000
X-Env-Sender: Stefano.Stabellini@eu.citrix.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1338978865!19001622!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17946 invoked from network); 6 Jun 2012 10:34:25 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:34:25 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12855437"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 10:34:25 +0000
Received: from sstabellini-Precision-WorkStation-T3500.local (10.80.238.169)
	by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id
	8.3.213.0; Wed, 6 Jun 2012 11:34:24 +0100
Date: Wed, 6 Jun 2012 11:34:18 +0100
From: Stefano Stabellini 
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: Ian Campbell 
In-Reply-To: <1338972636.32319.12.camel@zakaz.uk.xensource.com>
Message-ID: 
References: 
	<1338972636.32319.12.camel@zakaz.uk.xensource.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Cc: Anthony Perard ,
	"xen-users@lists.xen.org" ,
	Will McDermott ,
	Stefano Stabellini ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, 6 Jun 2012, Ian Campbell wrote:
> On Sun, 2012-06-03 at 22:16 +0100, Will McDermott wrote:
> > Hello,
> > 
> > I am trying to compile xen 4.2 unstable from mercurial. I can't get past
> > the make tools step. When I run make tools, the build fails with:
> 
> Thanks Will, this looks like a new one, I've not noticed any reports of
> this before. CCing xen-devel@ and our Qemu folks.
> 
> Guys, this looks like
> http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html or
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181 (which
> Will references below). I didn't look if any patch has gone in upstream
> or not.
> 
> I can't explain why other Ubuntu users aren't seeing this though.

You must have libcap and libattr installed, because that's what it takes
to enable virtfs in QEMU by default.
And virtfs at the moment doesn't compile without that patch.

I'll ping the QEMU maintainers about it, and also submit a patch to our
build system to disable virtfs.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 10:35:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 10:35: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 1ScDZM-00083a-Ah; Wed, 06 Jun 2012 10:34:28 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScDZK-00083C-TT
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 10:34:27 +0000
Received: from [85.158.143.35:48230] by server-2.bemta-4.messagelabs.com id
	E8/98-17938-1323FCF4; Wed, 06 Jun 2012 10:34:25 +0000
X-Env-Sender: Stefano.Stabellini@eu.citrix.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1338978865!19001622!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17946 invoked from network); 6 Jun 2012 10:34:25 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 10:34:25 -0000
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="12855437"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 10:34:25 +0000
Received: from sstabellini-Precision-WorkStation-T3500.local (10.80.238.169)
	by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id
	8.3.213.0; Wed, 6 Jun 2012 11:34:24 +0100
Date: Wed, 6 Jun 2012 11:34:18 +0100
From: Stefano Stabellini 
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: Ian Campbell 
In-Reply-To: <1338972636.32319.12.camel@zakaz.uk.xensource.com>
Message-ID: 
References: 
	<1338972636.32319.12.camel@zakaz.uk.xensource.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Cc: Anthony Perard ,
	"xen-users@lists.xen.org" ,
	Will McDermott ,
	Stefano Stabellini ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, 6 Jun 2012, Ian Campbell wrote:
> On Sun, 2012-06-03 at 22:16 +0100, Will McDermott wrote:
> > Hello,
> > 
> > I am trying to compile xen 4.2 unstable from mercurial. I can't get past
> > the make tools step. When I run make tools, the build fails with:
> 
> Thanks Will, this looks like a new one, I've not noticed any reports of
> this before. CCing xen-devel@ and our Qemu folks.
> 
> Guys, this looks like
> http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html or
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/930181 (which
> Will references below). I didn't look if any patch has gone in upstream
> or not.
> 
> I can't explain why other Ubuntu users aren't seeing this though.

You must have libcap and libattr installed, because that's what it takes
to enable virtfs in QEMU by default.
And virtfs at the moment doesn't compile without that patch.

I'll ping the QEMU maintainers about it, and also submit a patch to our
build system to disable virtfs.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 12:51:11 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 12:51: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 1ScFgE-0006b6-Q1; Wed, 06 Jun 2012 12:49:42 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScFgE-0006aq-1V
	for Xen-users@lists.xen.org; Wed, 06 Jun 2012 12:49:42 +0000
Received: from [193.109.254.147:27321] by server-2.bemta-14.messagelabs.com id
	A7/72-27740-5E15FCF4; Wed, 06 Jun 2012 12:49:41 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-3.tower-27.messagelabs.com!1338986978!13143391!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3915 invoked from network); 6 Jun 2012 12:49:40 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 12:49:40 -0000
Received: by dadv2 with SMTP id v2so9507663dad.32
	for ; Wed, 06 Jun 2012 05:49:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=yzeUezAtZ1dV3L9BAYzdNoP5iqjZOsc5gqfhVq6cm8s=;
	b=KPEj6V+k7Yyz7FWb3wm1wTVSJkviZSVEcOYrT2Vy0HY5fjkEoc0MoCs5LDcaVDCZI2
	+OX70jEV+mWxvR++CDK/9sOfwqWizeQ7XuJs8mUbQCFvx2/jj5ULjzZ2U5Uajfq9jnJz
	1jDtDZaCF0jSVxdGBMmJabGyH27MuQO4HWLMdufbmsKyqfYgz+fmaTA561XtfoDaNXf8
	+4nI170RM+s/1Kc7VPNAz30ww1H9SWWvkmr+ObOlNrcGzvVXDzGP0Q/jfIjs5rA5zsvC
	CCSxZ5ZWWsfKPbEetg7jTOBoXCFsWPfKZfGkHdPXtr+rKlZ0gtoWwRbx92dj9SZaLSZ3
	IDog==
MIME-Version: 1.0
Received: by 10.68.238.68 with SMTP id vi4mr58241781pbc.123.1338986978502;
	Wed, 06 Jun 2012 05:49:38 -0700 (PDT)
Received: by 10.68.209.1 with HTTP; Wed, 6 Jun 2012 05:49:38 -0700 (PDT)
In-Reply-To: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
References: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
Date: Wed, 6 Jun 2012 19:49:38 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: subbaraobrahma@bel.co.in
X-Gm-Message-State: ALoCoQkOaWI2zebkbR4qeQ4+jgQm0AdsxNQzyrPjzzKl+kSQoxfytXg3PCh3VYGK9KdXVPKSIqnA
Cc: Xen-users@lists.xen.org, xen-api@lists.xen.org
Subject: Re: [Xen-users] hi
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, Jun 4, 2012 at 1:29 PM,   wrote:
> hi sir,
> i want to develop the small private cloud i.e iaas(infrastructure as a
> service) using XEN. so i want the information to start up from scratch.
> because i am new to this area.i want the sequence of documnets and
> downloads from start.
> if any personnel mail is there that is also welcome.
> awaiting your early reply.

If your definition of IAAS is simply "I want to have a server which
can run VMs", the using either xenserver, XCP, or some distro bundled
with xen and good documentation and support (e.g. RHEL/Centos5) should
be a good place to start.

If your definition of IAAS is more complex than that (e.g. you want to
be able to add users, allow users access to certain VMs only, etc),
then you should probably look at openstack or eucalyptus (both should
support xen in some form).

You need to read the documentation and howto for the solution that you
use. For example, if you decide that RHEL/Centos5 is enough, then
start by reading RHEL5's Virtualization Guide. If you choose other
solutions, read their appropriate documentation. As usual, Google is
your friend. Use it. Seriously.

If you want something that just works and don't want to bother looking
for or reading documentation, then just hire people to do it. For
example, Canonical offers on-site private cloud deployment with its
ubuntu cloud.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 12:51:11 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 12:51: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 1ScFgE-0006b6-Q1; Wed, 06 Jun 2012 12:49:42 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScFgE-0006aq-1V
	for Xen-users@lists.xen.org; Wed, 06 Jun 2012 12:49:42 +0000
Received: from [193.109.254.147:27321] by server-2.bemta-14.messagelabs.com id
	A7/72-27740-5E15FCF4; Wed, 06 Jun 2012 12:49:41 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-3.tower-27.messagelabs.com!1338986978!13143391!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3915 invoked from network); 6 Jun 2012 12:49:40 -0000
Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com)
	(209.85.210.45)
	by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 12:49:40 -0000
Received: by dadv2 with SMTP id v2so9507663dad.32
	for ; Wed, 06 Jun 2012 05:49:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=yzeUezAtZ1dV3L9BAYzdNoP5iqjZOsc5gqfhVq6cm8s=;
	b=KPEj6V+k7Yyz7FWb3wm1wTVSJkviZSVEcOYrT2Vy0HY5fjkEoc0MoCs5LDcaVDCZI2
	+OX70jEV+mWxvR++CDK/9sOfwqWizeQ7XuJs8mUbQCFvx2/jj5ULjzZ2U5Uajfq9jnJz
	1jDtDZaCF0jSVxdGBMmJabGyH27MuQO4HWLMdufbmsKyqfYgz+fmaTA561XtfoDaNXf8
	+4nI170RM+s/1Kc7VPNAz30ww1H9SWWvkmr+ObOlNrcGzvVXDzGP0Q/jfIjs5rA5zsvC
	CCSxZ5ZWWsfKPbEetg7jTOBoXCFsWPfKZfGkHdPXtr+rKlZ0gtoWwRbx92dj9SZaLSZ3
	IDog==
MIME-Version: 1.0
Received: by 10.68.238.68 with SMTP id vi4mr58241781pbc.123.1338986978502;
	Wed, 06 Jun 2012 05:49:38 -0700 (PDT)
Received: by 10.68.209.1 with HTTP; Wed, 6 Jun 2012 05:49:38 -0700 (PDT)
In-Reply-To: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
References: <17f05dbc35c9d56f66e86a5d2635e819.squirrel@mail.bel.co.in>
Date: Wed, 6 Jun 2012 19:49:38 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: subbaraobrahma@bel.co.in
X-Gm-Message-State: ALoCoQkOaWI2zebkbR4qeQ4+jgQm0AdsxNQzyrPjzzKl+kSQoxfytXg3PCh3VYGK9KdXVPKSIqnA
Cc: Xen-users@lists.xen.org, xen-api@lists.xen.org
Subject: Re: [Xen-users] hi
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, Jun 4, 2012 at 1:29 PM,   wrote:
> hi sir,
> i want to develop the small private cloud i.e iaas(infrastructure as a
> service) using XEN. so i want the information to start up from scratch.
> because i am new to this area.i want the sequence of documnets and
> downloads from start.
> if any personnel mail is there that is also welcome.
> awaiting your early reply.

If your definition of IAAS is simply "I want to have a server which
can run VMs", the using either xenserver, XCP, or some distro bundled
with xen and good documentation and support (e.g. RHEL/Centos5) should
be a good place to start.

If your definition of IAAS is more complex than that (e.g. you want to
be able to add users, allow users access to certain VMs only, etc),
then you should probably look at openstack or eucalyptus (both should
support xen in some form).

You need to read the documentation and howto for the solution that you
use. For example, if you decide that RHEL/Centos5 is enough, then
start by reading RHEL5's Virtualization Guide. If you choose other
solutions, read their appropriate documentation. As usual, Google is
your friend. Use it. Seriously.

If you want something that just works and don't want to bother looking
for or reading documentation, then just hire people to do it. For
example, Canonical offers on-site private cloud deployment with its
ubuntu cloud.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 13:25:52 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 13:25: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 1ScGDo-0008RT-FI; Wed, 06 Jun 2012 13:24:24 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScGDm-0008RJ-WF
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 13:24:23 +0000
Received: from [193.109.254.147:57573] by server-7.bemta-14.messagelabs.com id
	2D/88-29165-60A5FCF4; Wed, 06 Jun 2012 13:24:22 +0000
X-Env-Sender: admin@dmarkey.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1338989059!10257539!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 973 invoked from network); 6 Jun 2012 13:24:20 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 13:24:20 -0000
Received: by obbwd20 with SMTP id wd20so13807495obb.32
	for ; Wed, 06 Jun 2012 06:24:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:content-type:x-gm-message-state;
	bh=2tAewPW4EMTypHy0X/ZYCHZ5GOfIDfoGGAF73mj0p5I=;
	b=JNhj2cPG1K6nWymnLa02228rghGm3cDHqBCOPKLX2OYgOsaoRbjSAGvbR57SBc+e9g
	BtE9Ut6YlAOLfX4FAftS5M/xtgx2TQ+FTFPvdFMekE6g9idzods6lGZavCmfYTeSlVA+
	zaL6ksp1UfwyeFg0FsQnFBTc5LA+ikYufNQfIjvpzOr9ff1owFbTnJw6LbGTCeZdWImI
	/GbuZiX0rDZVBRlAPxc5EDH3g3WSIOeod5vBzD4CXOBERvGizMlqrfsaf2b6VhIfYqN+
	iVlLdtqeEOx9zD5LFMkArYCXpQhtPf4IikXCOeOiEaNKwWakpYADAn44voKjntPsrX96
	xKhw==
MIME-Version: 1.0
Received: by 10.182.192.2 with SMTP id hc2mr20072441obc.58.1338989059039; Wed,
	06 Jun 2012 06:24:19 -0700 (PDT)
Received: by 10.60.62.201 with HTTP; Wed, 6 Jun 2012 06:24:18 -0700 (PDT)
In-Reply-To: <1338972996.32319.16.camel@zakaz.uk.xensource.com>
References: 
	<1338972996.32319.16.camel@zakaz.uk.xensource.com>
Date: Wed, 6 Jun 2012 14:24:18 +0100
Message-ID: 
From: David Markey 
To: "xen-users@lists.xen.org" 
X-Gm-Message-State: ALoCoQnEIOQY4MUW0z3SQcGgucCHZIr500FFn6cdhQw+mQluuwR8uGjYlRJxildtt96LT31Z1Ks9
Subject: Re: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: admin@dmarkey.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3916894199919763883=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3916894199919763883==
Content-Type: multipart/alternative; boundary=14dae9399df738e1bb04c1cdaf43

--14dae9399df738e1bb04c1cdaf43
Content-Type: text/plain; charset=ISO-8859-1

If a SIGKILL wont get rid of it, it's probably stuck on a system call.

Any clues in dmesg? Do the guests seem OK?

Like Ian said, try here also
http://forums.citrix.com/category.jspa?categoryID=101

On 6 June 2012 09:56, Ian Campbell  wrote:

> Hi Jason,
>
> I've no idea about this issue I'm afraid.
>
> This list is for users of the Open Source version of Xen rather than any
> particular commercial product.
>
> In general XenServer questions are best addressed to either your
> XenServer support rep or to the appropriate forum on forums.citrix.com.
>
> Thanks,
> Ian.
>
> On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:
> > One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> > to XAPI calls being sent from a CloudStack management server. In the
> > past, a simple xe-toolstack-restart would do the trick but the script
> > timed out while restarting the XAPI daemon.
> >
> >
> > I found the process and first tried to use a simple kill command but
> > the process was in a "defunct" state. I tried a kill -9 but no joy.
> >
> >
> > I then found the xapi.pid and manually deleted it and then tried to
> > run xe-toolstack-restart. Unfortunately this did not work and
> > ultimately I had to reboot the cluster node.
> >
> >
> > So... any other ideas on killing a zombie XAPI process? I've like to
> > avoid rebooting a host :)
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--14dae9399df738e1bb04c1cdaf43
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

If a SIGKILL wont get rid of it, it's probably stuck on a system call.<=
div>
Any clues in dmesg? Do the guests seem OK?
Like Ian said, try here also=A0http://forums.citrix.com/category.jspa?=
categoryID=3D101


On 6 June 2012 09:56, Ian Campbell <I=
an.Campbell@citrix.com> wrote:

Hi Jason,



I've no idea about this issue I'm afraid.



This list is for users of the Open Source version of Xen rather than any
particular commercial product.



In general XenServer questions are best addressed to either your

XenServer support rep or to the appropriate forum on forums.citrix.com.



Thanks,

Ian.




On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:

> One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> to XAPI calls being sent from a CloudStack management server. In the
> past, a simple xe-toolstack-restart would do the trick but the script<=
br>
> timed out while restarting the XAPI daemon.

>

>

> I found the process and first tried to use a simple kill command but
> the process was in a "defunct" state. I tried a kill -9 but =
no joy.

>

>

> I then found the xapi.pid and manually deleted it and then tried to
> run xe-toolstack-restart. Unfortunately this did not work and

> ultimately I had to reboot the cluster node.

>

>

> So... any other ideas on killing a zombie XAPI process? I've like =
to

> avoid rebooting a host :)








_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9399df738e1bb04c1cdaf43--


--===============3916894199919763883==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3916894199919763883==--


From xen-users-bounces@lists.xen.org Wed Jun 06 13:25:52 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 13:25: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 1ScGDo-0008RT-FI; Wed, 06 Jun 2012 13:24:24 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScGDm-0008RJ-WF
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 13:24:23 +0000
Received: from [193.109.254.147:57573] by server-7.bemta-14.messagelabs.com id
	2D/88-29165-60A5FCF4; Wed, 06 Jun 2012 13:24:22 +0000
X-Env-Sender: admin@dmarkey.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1338989059!10257539!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 973 invoked from network); 6 Jun 2012 13:24:20 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 13:24:20 -0000
Received: by obbwd20 with SMTP id wd20so13807495obb.32
	for ; Wed, 06 Jun 2012 06:24:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:content-type:x-gm-message-state;
	bh=2tAewPW4EMTypHy0X/ZYCHZ5GOfIDfoGGAF73mj0p5I=;
	b=JNhj2cPG1K6nWymnLa02228rghGm3cDHqBCOPKLX2OYgOsaoRbjSAGvbR57SBc+e9g
	BtE9Ut6YlAOLfX4FAftS5M/xtgx2TQ+FTFPvdFMekE6g9idzods6lGZavCmfYTeSlVA+
	zaL6ksp1UfwyeFg0FsQnFBTc5LA+ikYufNQfIjvpzOr9ff1owFbTnJw6LbGTCeZdWImI
	/GbuZiX0rDZVBRlAPxc5EDH3g3WSIOeod5vBzD4CXOBERvGizMlqrfsaf2b6VhIfYqN+
	iVlLdtqeEOx9zD5LFMkArYCXpQhtPf4IikXCOeOiEaNKwWakpYADAn44voKjntPsrX96
	xKhw==
MIME-Version: 1.0
Received: by 10.182.192.2 with SMTP id hc2mr20072441obc.58.1338989059039; Wed,
	06 Jun 2012 06:24:19 -0700 (PDT)
Received: by 10.60.62.201 with HTTP; Wed, 6 Jun 2012 06:24:18 -0700 (PDT)
In-Reply-To: <1338972996.32319.16.camel@zakaz.uk.xensource.com>
References: 
	<1338972996.32319.16.camel@zakaz.uk.xensource.com>
Date: Wed, 6 Jun 2012 14:24:18 +0100
Message-ID: 
From: David Markey 
To: "xen-users@lists.xen.org" 
X-Gm-Message-State: ALoCoQnEIOQY4MUW0z3SQcGgucCHZIr500FFn6cdhQw+mQluuwR8uGjYlRJxildtt96LT31Z1Ks9
Subject: Re: [Xen-users] Any tips on dealing with a super hung XAPI process?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: admin@dmarkey.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3916894199919763883=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3916894199919763883==
Content-Type: multipart/alternative; boundary=14dae9399df738e1bb04c1cdaf43

--14dae9399df738e1bb04c1cdaf43
Content-Type: text/plain; charset=ISO-8859-1

If a SIGKILL wont get rid of it, it's probably stuck on a system call.

Any clues in dmesg? Do the guests seem OK?

Like Ian said, try here also
http://forums.citrix.com/category.jspa?categoryID=101

On 6 June 2012 09:56, Ian Campbell  wrote:

> Hi Jason,
>
> I've no idea about this issue I'm afraid.
>
> This list is for users of the Open Source version of Xen rather than any
> particular commercial product.
>
> In general XenServer questions are best addressed to either your
> XenServer support rep or to the appropriate forum on forums.citrix.com.
>
> Thanks,
> Ian.
>
> On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:
> > One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> > to XAPI calls being sent from a CloudStack management server. In the
> > past, a simple xe-toolstack-restart would do the trick but the script
> > timed out while restarting the XAPI daemon.
> >
> >
> > I found the process and first tried to use a simple kill command but
> > the process was in a "defunct" state. I tried a kill -9 but no joy.
> >
> >
> > I then found the xapi.pid and manually deleted it and then tried to
> > run xe-toolstack-restart. Unfortunately this did not work and
> > ultimately I had to reboot the cluster node.
> >
> >
> > So... any other ideas on killing a zombie XAPI process? I've like to
> > avoid rebooting a host :)
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--14dae9399df738e1bb04c1cdaf43
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

If a SIGKILL wont get rid of it, it's probably stuck on a system call.<=
div>
Any clues in dmesg? Do the guests seem OK?
Like Ian said, try here also=A0http://forums.citrix.com/category.jspa?=
categoryID=3D101


On 6 June 2012 09:56, Ian Campbell <I=
an.Campbell@citrix.com> wrote:

Hi Jason,



I've no idea about this issue I'm afraid.



This list is for users of the Open Source version of Xen rather than any
particular commercial product.



In general XenServer questions are best addressed to either your

XenServer support rep or to the appropriate forum on forums.citrix.com.



Thanks,

Ian.




On Tue, 2012-06-05 at 01:03 +0100, Jason Davis wrote:

> One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive
> to XAPI calls being sent from a CloudStack management server. In the
> past, a simple xe-toolstack-restart would do the trick but the script<=
br>
> timed out while restarting the XAPI daemon.

>

>

> I found the process and first tried to use a simple kill command but
> the process was in a "defunct" state. I tried a kill -9 but =
no joy.

>

>

> I then found the xapi.pid and manually deleted it and then tried to
> run xe-toolstack-restart. Unfortunately this did not work and

> ultimately I had to reboot the cluster node.

>

>

> So... any other ideas on killing a zombie XAPI process? I've like =
to

> avoid rebooting a host :)








_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users





--14dae9399df738e1bb04c1cdaf43--


--===============3916894199919763883==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3916894199919763883==--


From xen-users-bounces@lists.xen.org Wed Jun 06 14:19:55 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:19: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 1ScH4L-0002cD-Ve; Wed, 06 Jun 2012 14:18:41 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScH4K-0002c8-Q1
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 14:18:40 +0000
Received: from [85.158.143.99:39041] by server-2.bemta-4.messagelabs.com id
	24/EF-17938-0C66FCF4; Wed, 06 Jun 2012 14:18:40 +0000
X-Env-Sender: sebastien.prouff@ac-poitiers.fr
X-Msg-Ref: server-5.tower-216.messagelabs.com!1338992318!31260032!1
X-Originating-IP: [195.83.12.242]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15127 invoked from network); 6 Jun 2012 14:18:38 -0000
Received: from smtp1.ac-poitiers.fr (HELO smtp1.ac-poitiers.fr) (195.83.12.242)
	by server-5.tower-216.messagelabs.com with SMTP;
	6 Jun 2012 14:18:38 -0000
Received: from localhost (smtp1.ac-poitiers.fr [127.0.0.1])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 8C40B7A2D8
	for ;
	Wed,  6 Jun 2012 16:18:36 +0200 (CEST)
X-Virus-Scanned: Scanned by smtp for ac-poitiers.fr
Received: from smtp1.ac-poitiers.fr ([127.0.0.1])
	by localhost (smtp1.ac-poitiers.fr [127.0.0.1]) (amavisd-new,
	port 51025)
	with ESMTP id 71ADr1Xp8-dG for ;
	Wed,  6 Jun 2012 16:18:36 +0200 (CEST)
Received: from [10.0.17.41] (unknown [195.221.249.6])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 742D47A2CF
	for ;
	Wed,  6 Jun 2012 16:18:35 +0200 (CEST)
Message-ID: <4FCF66BB.2030901@ac-poitiers.fr>
Date: Wed, 06 Jun 2012 16:18:35 +0200
From: sebastien PROUFF 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: xen-users@lists.xensource.com
Subject: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7129869981526869808=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============7129869981526869808==
Content-Type: multipart/alternative;
 boundary="------------060106040104040401050009"

This is a multi-part message in MIME format.
--------------060106040104040401050009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

I want to monitor my XCP server with nut.

So, after a google search I've been there.
http://wiki.xen.org/wiki/XCP_NUT

It sound great, but the nut packet I can download from alyseo seems 
outdated.
I would like to download the right one for my distro but...what is the 
distribution ?

#cat /etc/issue
xen.org XCP 1.1.0-50674c

XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based 
on RHE ?
Whoo, i'm lost !
Please tell me where i can find the right rpm package for my xcp server.

Cheers

-- 
Sébastien Prouff


--------------060106040104040401050009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi, 

    

    I want to monitor my XCP server with nut.

    

    So, after a google search I've been there.

    http://wiki.xen.org/wiki/XCP_NUT

    

    It sound great, but the nut packet I can download from alyseo seems
    outdated.

    I would like to download the right one for my distro but...what is
    the distribution ?

     

    #cat /etc/issue

      xen.org XCP 1.1.0-50674c

    

    XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
    based on RHE ?

    Whoo, i'm lost !

    Please tell me where i can find the right rpm package for my xcp
    server.

    

    Cheers

    

    
-- 
Sébastien Prouff


  


--------------060106040104040401050009--


--===============7129869981526869808==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7129869981526869808==--


From xen-users-bounces@lists.xen.org Wed Jun 06 14:19:55 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:19: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 1ScH4L-0002cD-Ve; Wed, 06 Jun 2012 14:18:41 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScH4K-0002c8-Q1
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 14:18:40 +0000
Received: from [85.158.143.99:39041] by server-2.bemta-4.messagelabs.com id
	24/EF-17938-0C66FCF4; Wed, 06 Jun 2012 14:18:40 +0000
X-Env-Sender: sebastien.prouff@ac-poitiers.fr
X-Msg-Ref: server-5.tower-216.messagelabs.com!1338992318!31260032!1
X-Originating-IP: [195.83.12.242]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15127 invoked from network); 6 Jun 2012 14:18:38 -0000
Received: from smtp1.ac-poitiers.fr (HELO smtp1.ac-poitiers.fr) (195.83.12.242)
	by server-5.tower-216.messagelabs.com with SMTP;
	6 Jun 2012 14:18:38 -0000
Received: from localhost (smtp1.ac-poitiers.fr [127.0.0.1])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 8C40B7A2D8
	for ;
	Wed,  6 Jun 2012 16:18:36 +0200 (CEST)
X-Virus-Scanned: Scanned by smtp for ac-poitiers.fr
Received: from smtp1.ac-poitiers.fr ([127.0.0.1])
	by localhost (smtp1.ac-poitiers.fr [127.0.0.1]) (amavisd-new,
	port 51025)
	with ESMTP id 71ADr1Xp8-dG for ;
	Wed,  6 Jun 2012 16:18:36 +0200 (CEST)
Received: from [10.0.17.41] (unknown [195.221.249.6])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 742D47A2CF
	for ;
	Wed,  6 Jun 2012 16:18:35 +0200 (CEST)
Message-ID: <4FCF66BB.2030901@ac-poitiers.fr>
Date: Wed, 06 Jun 2012 16:18:35 +0200
From: sebastien PROUFF 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: xen-users@lists.xensource.com
Subject: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7129869981526869808=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============7129869981526869808==
Content-Type: multipart/alternative;
 boundary="------------060106040104040401050009"

This is a multi-part message in MIME format.
--------------060106040104040401050009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

I want to monitor my XCP server with nut.

So, after a google search I've been there.
http://wiki.xen.org/wiki/XCP_NUT

It sound great, but the nut packet I can download from alyseo seems 
outdated.
I would like to download the right one for my distro but...what is the 
distribution ?

#cat /etc/issue
xen.org XCP 1.1.0-50674c

XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based 
on RHE ?
Whoo, i'm lost !
Please tell me where i can find the right rpm package for my xcp server.

Cheers

-- 
Sébastien Prouff


--------------060106040104040401050009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi, 

    

    I want to monitor my XCP server with nut.

    

    So, after a google search I've been there.

    http://wiki.xen.org/wiki/XCP_NUT

    

    It sound great, but the nut packet I can download from alyseo seems
    outdated.

    I would like to download the right one for my distro but...what is
    the distribution ?

     

    #cat /etc/issue

      xen.org XCP 1.1.0-50674c

    

    XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
    based on RHE ?

    Whoo, i'm lost !

    Please tell me where i can find the right rpm package for my xcp
    server.

    

    Cheers

    

    
-- 
Sébastien Prouff


  


--------------060106040104040401050009--


--===============7129869981526869808==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7129869981526869808==--


From xen-users-bounces@lists.xen.org Wed Jun 06 14:32:27 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:32:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScHGd-0003B7-NW; Wed, 06 Jun 2012 14:31:23 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHGc-0003Am-8J
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 14:31:22 +0000
Received: from [85.158.143.35:59686] by server-2.bemta-4.messagelabs.com id
	D6/45-17938-9B96FCF4; Wed, 06 Jun 2012 14:31:21 +0000
X-Env-Sender: eross@corp.locatrix.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1338993079!8139776!1
X-Originating-IP: [209.85.216.171]
X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32692 invoked from network); 6 Jun 2012 14:31:20 -0000
Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com)
	(209.85.216.171)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:31:20 -0000
Received: by qcsp15 with SMTP id p15so4335370qcs.30
	for ;
	Wed, 06 Jun 2012 07:31:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=tKHuOHnF2C1asTbTUt5bgbXgjsWmTjovIJTWEPlLl3A=;
	b=cLdjqanbYV3Y3+1YZ8pWPqljoeS33NM1EgZJLKzjL+2HhKwlUCXI4IP2Y7jgdK5TLF
	yOCI+dsUBToeeBa04UDN5/r31arvVcNZwFD2pG7huoObxg0mzFTlrIkYJATx4cwcAP3R
	zOs6MYkDZ6UTXOxAbKalsNhm6b2U5yAHMpqZgdc7K5w8bpyAXd3jWXIlPBeWLwHAMwY+
	1jU7pKALS3kPKhbZikgsELfku/bhcM+4i9RdN5odig4EiJpeAurW/lE6Ewy0AC+gfTVT
	nDb3zhqHlUKNYguQFDYtpzOiZ3MiRT5SNrpA71OCu597mw3UzklqJ32Vi8JxrSJ/X/r3
	nsEQ==
Received: by 10.60.30.233 with SMTP id v9mr20478567oeh.6.1338993079182; Wed,
	06 Jun 2012 07:31:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.128.71 with HTTP; Wed, 6 Jun 2012 07:30:59 -0700 (PDT)
In-Reply-To: <4FCF66BB.2030901@ac-poitiers.fr>
References: <4FCF66BB.2030901@ac-poitiers.fr>
From: Andrew Eross 
Date: Wed, 6 Jun 2012 11:30:59 -0300
Message-ID: 
To: sebastien PROUFF 
X-Gm-Message-State: ALoCoQl9cbUuvJTILp4OtTvE1XHQfutwn3XY4UvQHvu7U5tZGwHQMfX4QMH+J31nastYaDzgtcjk
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4293205376189537795=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4293205376189537795==
Content-Type: multipart/alternative; boundary=e89a8ff1c7c8d7661a04c1ce9e47

--e89a8ff1c7c8d7661a04c1ce9e47
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Sebastien,

I wrote that howto a bit ago, and yeah I couldn't really find a better
package, although I did basically get nut working with my ups.

If you have any additional success here, please share, or update the wiki.

XCP is CentOS, based on XenServer 5.6 FP1 (read
http://wiki.xen.org/wiki/XCP_Introduction)

You can even install normal packages after enabling the repo, using yum,
like this:

sed -i -e "s/enabled=3D0/enabled=3D1/" /etc/yum.repos.d/CentOS-Base.repo
sed -i -e "s/enabled=3D1/enabled=3D0/" /etc/yum.repos.d/Citrix.repo
yum install 

If you're feeling daring, you could try to compile your own nut by
installing build tools first, e.g.
yum install gcc flex rpm-build redhat-rpm-config make (etc)

Wouldn't recommend adding all that junk onto a production box, but you
could do it on a throw-away dev dom0.

Cheers,
Andrew





On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF <
sebastien.prouff@ac-poitiers.fr> wrote:

>  Hi,
>
> I want to monitor my XCP server with nut.
>
> So, after a google search I've been there.
> http://wiki.xen.org/wiki/XCP_NUT
>
> It sound great, but the nut packet I can download from alyseo seems
> outdated.
> I would like to download the right one for my distro but...what is the
> distribution ?
>  
> #cat /etc/issue
> xen.org XCP 1.1.0-50674c
>
> XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based o=
n
> RHE ?
> Whoo, i'm lost !
> Please tell me where i can find the right rpm package for my xcp server.
>
> Cheers
>
> --
> S=E9bastien Prouff
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8ff1c7c8d7661a04c1ce9e47
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Sebastien,

I wrote that howto a bit ago, and yeah I =
couldn't really find a better package, although I did basically get nut=
 working with my ups.

If you have any additional s=
uccess here, please share, or update the wiki.





XCP is CentOS, based on=A0XenServer 5.6 FP1 (read=A0http:/=
/wiki.xen.org/wiki/XCP_Introduction)

You can e=
ven install normal packages after enabling the repo, using yum, like this:<=
/div>




sed -i -e "s/enabled=3D0/enabled=3D1/" /=
etc/yum.repos.d/CentOS-Base.repo
sed -i -e "s/enabled=3D1/en=
abled=3D0/" /etc/yum.repos.d/Citrix.repo
yum install <wha=
tever>





If you're feeling daring, you could try to co=
mpile your own nut by installing build tools first, e.g.
yum inst=
all gcc flex rpm-build redhat-rpm-config make (etc)





Wouldn't recommend adding all that junk onto a production box, but=
 you could do it on a throw-away dev dom0.

Cheers,=

Andrew






On Wed, Jun 6, 2012 at 11:18 AM, sebasti=
en PROUFF <sebastien.prouff@ac-poitiers.fr> wr=
ote:





 =20

   =20
 =20
  

    Hi, 

    

    I want to monitor my XCP server with nut.

    

    So, after a google search I've been there.

    http://w=
iki.xen.org/wiki/XCP_NUT

    

    It sound great, but the nut packet I can download from alyseo seems
    outdated.

    I would like to download the right one for my distro but...what is
    the distribution ?

     
    #cat /etc/issue

      xen.org XCP 1.1.0-50=
674c

    

    XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
    based on RHE ?

    Whoo, i'm lost !

    Please tell me where i can find the right rpm package for my xcp
    server.

    

    Cheers

    

    
--=20
S=E9bastien Prouff


  



_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users



--e89a8ff1c7c8d7661a04c1ce9e47--


--===============4293205376189537795==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4293205376189537795==--


From xen-users-bounces@lists.xen.org Wed Jun 06 14:32:27 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:32:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScHGd-0003B7-NW; Wed, 06 Jun 2012 14:31:23 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHGc-0003Am-8J
	for xen-users@lists.xensource.com; Wed, 06 Jun 2012 14:31:22 +0000
Received: from [85.158.143.35:59686] by server-2.bemta-4.messagelabs.com id
	D6/45-17938-9B96FCF4; Wed, 06 Jun 2012 14:31:21 +0000
X-Env-Sender: eross@corp.locatrix.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1338993079!8139776!1
X-Originating-IP: [209.85.216.171]
X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32692 invoked from network); 6 Jun 2012 14:31:20 -0000
Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com)
	(209.85.216.171)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:31:20 -0000
Received: by qcsp15 with SMTP id p15so4335370qcs.30
	for ;
	Wed, 06 Jun 2012 07:31:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=tKHuOHnF2C1asTbTUt5bgbXgjsWmTjovIJTWEPlLl3A=;
	b=cLdjqanbYV3Y3+1YZ8pWPqljoeS33NM1EgZJLKzjL+2HhKwlUCXI4IP2Y7jgdK5TLF
	yOCI+dsUBToeeBa04UDN5/r31arvVcNZwFD2pG7huoObxg0mzFTlrIkYJATx4cwcAP3R
	zOs6MYkDZ6UTXOxAbKalsNhm6b2U5yAHMpqZgdc7K5w8bpyAXd3jWXIlPBeWLwHAMwY+
	1jU7pKALS3kPKhbZikgsELfku/bhcM+4i9RdN5odig4EiJpeAurW/lE6Ewy0AC+gfTVT
	nDb3zhqHlUKNYguQFDYtpzOiZ3MiRT5SNrpA71OCu597mw3UzklqJ32Vi8JxrSJ/X/r3
	nsEQ==
Received: by 10.60.30.233 with SMTP id v9mr20478567oeh.6.1338993079182; Wed,
	06 Jun 2012 07:31:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.128.71 with HTTP; Wed, 6 Jun 2012 07:30:59 -0700 (PDT)
In-Reply-To: <4FCF66BB.2030901@ac-poitiers.fr>
References: <4FCF66BB.2030901@ac-poitiers.fr>
From: Andrew Eross 
Date: Wed, 6 Jun 2012 11:30:59 -0300
Message-ID: 
To: sebastien PROUFF 
X-Gm-Message-State: ALoCoQl9cbUuvJTILp4OtTvE1XHQfutwn3XY4UvQHvu7U5tZGwHQMfX4QMH+J31nastYaDzgtcjk
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4293205376189537795=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4293205376189537795==
Content-Type: multipart/alternative; boundary=e89a8ff1c7c8d7661a04c1ce9e47

--e89a8ff1c7c8d7661a04c1ce9e47
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Sebastien,

I wrote that howto a bit ago, and yeah I couldn't really find a better
package, although I did basically get nut working with my ups.

If you have any additional success here, please share, or update the wiki.

XCP is CentOS, based on XenServer 5.6 FP1 (read
http://wiki.xen.org/wiki/XCP_Introduction)

You can even install normal packages after enabling the repo, using yum,
like this:

sed -i -e "s/enabled=3D0/enabled=3D1/" /etc/yum.repos.d/CentOS-Base.repo
sed -i -e "s/enabled=3D1/enabled=3D0/" /etc/yum.repos.d/Citrix.repo
yum install 

If you're feeling daring, you could try to compile your own nut by
installing build tools first, e.g.
yum install gcc flex rpm-build redhat-rpm-config make (etc)

Wouldn't recommend adding all that junk onto a production box, but you
could do it on a throw-away dev dom0.

Cheers,
Andrew





On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF <
sebastien.prouff@ac-poitiers.fr> wrote:

>  Hi,
>
> I want to monitor my XCP server with nut.
>
> So, after a google search I've been there.
> http://wiki.xen.org/wiki/XCP_NUT
>
> It sound great, but the nut packet I can download from alyseo seems
> outdated.
> I would like to download the right one for my distro but...what is the
> distribution ?
>  
> #cat /etc/issue
> xen.org XCP 1.1.0-50674c
>
> XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based o=
n
> RHE ?
> Whoo, i'm lost !
> Please tell me where i can find the right rpm package for my xcp server.
>
> Cheers
>
> --
> S=E9bastien Prouff
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8ff1c7c8d7661a04c1ce9e47
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Sebastien,

I wrote that howto a bit ago, and yeah I =
couldn't really find a better package, although I did basically get nut=
 working with my ups.

If you have any additional s=
uccess here, please share, or update the wiki.





XCP is CentOS, based on=A0XenServer 5.6 FP1 (read=A0http:/=
/wiki.xen.org/wiki/XCP_Introduction)

You can e=
ven install normal packages after enabling the repo, using yum, like this:<=
/div>




sed -i -e "s/enabled=3D0/enabled=3D1/" /=
etc/yum.repos.d/CentOS-Base.repo
sed -i -e "s/enabled=3D1/en=
abled=3D0/" /etc/yum.repos.d/Citrix.repo
yum install <wha=
tever>





If you're feeling daring, you could try to co=
mpile your own nut by installing build tools first, e.g.
yum inst=
all gcc flex rpm-build redhat-rpm-config make (etc)





Wouldn't recommend adding all that junk onto a production box, but=
 you could do it on a throw-away dev dom0.

Cheers,=

Andrew






On Wed, Jun 6, 2012 at 11:18 AM, sebasti=
en PROUFF <sebastien.prouff@ac-poitiers.fr> wr=
ote:





 =20

   =20
 =20
  

    Hi, 

    

    I want to monitor my XCP server with nut.

    

    So, after a google search I've been there.

    http://w=
iki.xen.org/wiki/XCP_NUT

    

    It sound great, but the nut packet I can download from alyseo seems
    outdated.

    I would like to download the right one for my distro but...what is
    the distribution ?

     
    #cat /etc/issue

      xen.org XCP 1.1.0-50=
674c

    

    XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
    based on RHE ?

    Whoo, i'm lost !

    Please tell me where i can find the right rpm package for my xcp
    server.

    

    Cheers

    

    
--=20
S=E9bastien Prouff


  



_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users



--e89a8ff1c7c8d7661a04c1ce9e47--


--===============4293205376189537795==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4293205376189537795==--


From xen-users-bounces@lists.xen.org Wed Jun 06 14:35:15 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:35: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 1ScHJK-0003TH-Im; Wed, 06 Jun 2012 14:34:10 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHJJ-0003T2-9p
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:34:09 +0000
Received: from [85.158.138.51:21708] by server-1.bemta-3.messagelabs.com id
	32/B0-01327-06A6FCF4; Wed, 06 Jun 2012 14:34:08 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1338993246!31112572!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14645 invoked from network); 6 Jun 2012 14:34:07 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-2.tower-174.messagelabs.com with SMTP;
	6 Jun 2012 14:34:07 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Wed, 6 Jun 2012 07:34:04 -0700
Received: from [192.168.3.7] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 3F20C38A17E
	for ; Wed,  6 Jun 2012 07:34:04 -0700 (PDT)
From: bill@b2bassadventures.com
To: xen-users@lists.xen.org
Date: Wed, 06 Jun 2012 07:34:08 -0700
MIME-Version: 1.0
Message-ID: <4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
Priority: normal
In-reply-to: <4FCF2E46.8040909@xen.org>
References: <4FCD7E6D.5070004@b2bassadventures.com>,
	<1338973656.32319.24.camel@zakaz.uk.xensource.com>,
	<4FCF2E46.8040909@xen.org>
X-mailer: Pegasus Mail for Windows (4.63)
Content-description: Mail message body
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 6 Jun 2012 at 11:17, Lars Kurth wrote:

> > That same page also has some discussion of guest install methods, e.g.
> > using the xen-tools package (which builds on debootstrap). Another
> > option for installing a Debian guest is to use the normal Debian
> > installer. This is described in:
> > http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
> >
> > Some other pages of interest:
> > http://wiki.xen.org/wiki/Category:Debian
> > http://wiki.xen.org/wiki/Category:Host_Install
> > http://wiki.xen.org/wiki/Category:Guest_Install
> > http://wiki.xen.org/wiki/Getting_Started
> >
> > As others have mentioned you are probably better off using LVM than
> > dedicating actual partitions to the guests (although this will work).
> >
> > Ian.

Thanks Ian and thanks to all that gave me some good info.

I did get both guests up and running but i did use two separate partitions and LVM. I do 
have a few issues.

br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
get them to start.

on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
eth0.

issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
and I can use it.

Big question is how do I get these two guests to autostart if the server is rebooted?


Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 14:35:15 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:35: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 1ScHJK-0003TH-Im; Wed, 06 Jun 2012 14:34:10 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHJJ-0003T2-9p
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:34:09 +0000
Received: from [85.158.138.51:21708] by server-1.bemta-3.messagelabs.com id
	32/B0-01327-06A6FCF4; Wed, 06 Jun 2012 14:34:08 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1338993246!31112572!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14645 invoked from network); 6 Jun 2012 14:34:07 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-2.tower-174.messagelabs.com with SMTP;
	6 Jun 2012 14:34:07 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Wed, 6 Jun 2012 07:34:04 -0700
Received: from [192.168.3.7] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 3F20C38A17E
	for ; Wed,  6 Jun 2012 07:34:04 -0700 (PDT)
From: bill@b2bassadventures.com
To: xen-users@lists.xen.org
Date: Wed, 06 Jun 2012 07:34:08 -0700
MIME-Version: 1.0
Message-ID: <4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
Priority: normal
In-reply-to: <4FCF2E46.8040909@xen.org>
References: <4FCD7E6D.5070004@b2bassadventures.com>,
	<1338973656.32319.24.camel@zakaz.uk.xensource.com>,
	<4FCF2E46.8040909@xen.org>
X-mailer: Pegasus Mail for Windows (4.63)
Content-description: Mail message body
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 6 Jun 2012 at 11:17, Lars Kurth wrote:

> > That same page also has some discussion of guest install methods, e.g.
> > using the xen-tools package (which builds on debootstrap). Another
> > option for installing a Debian guest is to use the normal Debian
> > installer. This is described in:
> > http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
> >
> > Some other pages of interest:
> > http://wiki.xen.org/wiki/Category:Debian
> > http://wiki.xen.org/wiki/Category:Host_Install
> > http://wiki.xen.org/wiki/Category:Guest_Install
> > http://wiki.xen.org/wiki/Getting_Started
> >
> > As others have mentioned you are probably better off using LVM than
> > dedicating actual partitions to the guests (although this will work).
> >
> > Ian.

Thanks Ian and thanks to all that gave me some good info.

I did get both guests up and running but i did use two separate partitions and LVM. I do 
have a few issues.

br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
get them to start.

on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
eth0.

issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
and I can use it.

Big question is how do I get these two guests to autostart if the server is rebooted?


Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 14:50:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:50: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 1ScHXv-0004Mm-O9; Wed, 06 Jun 2012 14:49:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHXt-0004Mh-Rk
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:49:14 +0000
Received: from [85.158.139.83:32597] by server-4.bemta-5.messagelabs.com id
	AA/4F-05858-9ED6FCF4; Wed, 06 Jun 2012 14:49:13 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1338994151!28327590!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11970 invoked from network); 6 Jun 2012 14:49:12 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:49:12 -0000
X-IronPort-AV: E=Sophos;i="4.75,724,1330905600"; d="scan'208";a="12861886"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 14:48:07 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	15:48:07 +0100
Message-ID: <1338994086.32319.119.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "bill@b2bassadventures.com" 
Date: Wed, 6 Jun 2012 15:48:06 +0100
In-Reply-To: <4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
	, <1338973656.32319.24.camel@zakaz.uk.xensource.com>
	, <4FCF2E46.8040909@xen.org>
	<4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, 2012-06-06 at 15:34 +0100, bill@b2bassadventures.com wrote:
> On 6 Jun 2012 at 11:17, Lars Kurth wrote:
> 
> > > That same page also has some discussion of guest install methods, e.g.
> > > using the xen-tools package (which builds on debootstrap). Another
> > > option for installing a Debian guest is to use the normal Debian
> > > installer. This is described in:
> > > http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
> > >
> > > Some other pages of interest:
> > > http://wiki.xen.org/wiki/Category:Debian
> > > http://wiki.xen.org/wiki/Category:Host_Install
> > > http://wiki.xen.org/wiki/Category:Guest_Install
> > > http://wiki.xen.org/wiki/Getting_Started
> > >
> > > As others have mentioned you are probably better off using LVM than
> > > dedicating actual partitions to the guests (although this will work).
> > >
> > > Ian.
> 
> Thanks Ian and thanks to all that gave me some good info.
> 
> I did get both guests up and running but i did use two separate partitions and LVM. I do 
> have a few issues.
> 
> br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
> get them to start.

Do you have "auto br0" etc in your /etc/network/interfaces?

If you still have problems then please show us the config you are using.

> on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
> shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
> eth0.

I'm not entirely sure what you are describing here, can you describe
what you do see vs. what you expected to see?

Did you expect to see eth1 in guest1? or did you expect to see eth0?

What does guest1's vif configuration line look like?

If you expected eth0 then you might have an issue with the udev
persistent net rules, look under /etc/udev/rules.d for things which
might be renaming eth0->eth1 on boot.

If you expected eth1 then obviously you need to have eth1 in the
guest's /etc/network/interfaces if you want to use it.

> issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
> and I can use it.

blocked just means the guest is idle (i.e. it is blocked in the
hypervisor). It is still available to run if something happens. On a
mostly idle system most guests will be blocked...

> Big question is how do I get these two guests to autostart if the server is rebooted?

The xendomains initscript can do this for you. IIRC you just need to put
the config files in /etc/xen/auto instead of /etc/xen.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 14:50:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:50: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 1ScHXv-0004Mm-O9; Wed, 06 Jun 2012 14:49:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHXt-0004Mh-Rk
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:49:14 +0000
Received: from [85.158.139.83:32597] by server-4.bemta-5.messagelabs.com id
	AA/4F-05858-9ED6FCF4; Wed, 06 Jun 2012 14:49:13 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1338994151!28327590!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11970 invoked from network); 6 Jun 2012 14:49:12 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:49:12 -0000
X-IronPort-AV: E=Sophos;i="4.75,724,1330905600"; d="scan'208";a="12861886"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 14:48:07 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	15:48:07 +0100
Message-ID: <1338994086.32319.119.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: "bill@b2bassadventures.com" 
Date: Wed, 6 Jun 2012 15:48:06 +0100
In-Reply-To: <4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>
	, <1338973656.32319.24.camel@zakaz.uk.xensource.com>
	, <4FCF2E46.8040909@xen.org>
	<4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, 2012-06-06 at 15:34 +0100, bill@b2bassadventures.com wrote:
> On 6 Jun 2012 at 11:17, Lars Kurth wrote:
> 
> > > That same page also has some discussion of guest install methods, e.g.
> > > using the xen-tools package (which builds on debootstrap). Another
> > > option for installing a Debian guest is to use the normal Debian
> > > installer. This is described in:
> > > http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer
> > >
> > > Some other pages of interest:
> > > http://wiki.xen.org/wiki/Category:Debian
> > > http://wiki.xen.org/wiki/Category:Host_Install
> > > http://wiki.xen.org/wiki/Category:Guest_Install
> > > http://wiki.xen.org/wiki/Getting_Started
> > >
> > > As others have mentioned you are probably better off using LVM than
> > > dedicating actual partitions to the guests (although this will work).
> > >
> > > Ian.
> 
> Thanks Ian and thanks to all that gave me some good info.
> 
> I did get both guests up and running but i did use two separate partitions and LVM. I do 
> have a few issues.
> 
> br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
> get them to start.

Do you have "auto br0" etc in your /etc/network/interfaces?

If you still have problems then please show us the config you are using.

> on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
> shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
> eth0.

I'm not entirely sure what you are describing here, can you describe
what you do see vs. what you expected to see?

Did you expect to see eth1 in guest1? or did you expect to see eth0?

What does guest1's vif configuration line look like?

If you expected eth0 then you might have an issue with the udev
persistent net rules, look under /etc/udev/rules.d for things which
might be renaming eth0->eth1 on boot.

If you expected eth1 then obviously you need to have eth1 in the
guest's /etc/network/interfaces if you want to use it.

> issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
> and I can use it.

blocked just means the guest is idle (i.e. it is blocked in the
hypervisor). It is still available to run if something happens. On a
mostly idle system most guests will be blocked...

> Big question is how do I get these two guests to autostart if the server is rebooted?

The xendomains initscript can do this for you. IIRC you just need to put
the config files in /etc/xen/auto instead of /etc/xen.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 14:58:40 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:58: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 1ScHg8-0004d0-IX; Wed, 06 Jun 2012 14:57:44 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHg6-0004cR-Mb
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:57:42 +0000
Received: from [85.158.143.99:12525] by server-3.bemta-4.messagelabs.com id
	DF/4B-29237-6EF6FCF4; Wed, 06 Jun 2012 14:57:42 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1338994659!29266485!4
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5528 invoked from network); 6 Jun 2012 14:57:40 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:57:40 -0000
X-IronPort-AV: E=Sophos;i="4.75,724,1330905600"; d="scan'208";a="12862149"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 14:57:27 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	15:57:27 +0100
Message-ID: <1338994645.32319.128.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: 
Date: Wed, 6 Jun 2012 15:57:25 +0100
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: Lars Kurth 
Subject: [Xen-users] Volunteers wanted to help with list moderation
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Most Xen.org mailing lists are moderated for non-subscribers, primarily
as a SPAM prevention measure. We are a little short of moderators at the
moment which means that sometimes mails for genuine posters who happen
to not be subscribed get delayed for a few days.

We are looking for volunteers to help out with this, it should be a
couple of a minutes each day to clear out any SPAM which has made it
through the automated filters and accept the posts from non-subscribers.

The basic policy for moderation is:

    "reject and blacklist spam, accept and whitelist everything else".

Most of the SPAM which gets through the filters is still pretty obvious
to the human eye and there are generally only a small number each day so
it is usually a pretty quick job.

Please let myself and Lars know if you would like to help out with one
or more lists. The only requirement is to be an existing regular poster
to the list.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 14:58:40 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 14:58: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 1ScHg8-0004d0-IX; Wed, 06 Jun 2012 14:57:44 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScHg6-0004cR-Mb
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 14:57:42 +0000
Received: from [85.158.143.99:12525] by server-3.bemta-4.messagelabs.com id
	DF/4B-29237-6EF6FCF4; Wed, 06 Jun 2012 14:57:42 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1338994659!29266485!4
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDExMjA=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5528 invoked from network); 6 Jun 2012 14:57:40 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 14:57:40 -0000
X-IronPort-AV: E=Sophos;i="4.75,724,1330905600"; d="scan'208";a="12862149"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 14:57:27 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 6 Jun 2012
	15:57:27 +0100
Message-ID: <1338994645.32319.128.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: 
Date: Wed, 6 Jun 2012 15:57:25 +0100
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: Lars Kurth 
Subject: [Xen-users] Volunteers wanted to help with list moderation
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Most Xen.org mailing lists are moderated for non-subscribers, primarily
as a SPAM prevention measure. We are a little short of moderators at the
moment which means that sometimes mails for genuine posters who happen
to not be subscribed get delayed for a few days.

We are looking for volunteers to help out with this, it should be a
couple of a minutes each day to clear out any SPAM which has made it
through the automated filters and accept the posts from non-subscribers.

The basic policy for moderation is:

    "reject and blacklist spam, accept and whitelist everything else".

Most of the SPAM which gets through the filters is still pretty obvious
to the human eye and there are generally only a small number each day so
it is usually a pretty quick job.

Please let myself and Lars know if you would like to help out with one
or more lists. The only requirement is to be an existing regular poster
to the list.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 15:36:38 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:36:38 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScIGm-0006iu-3w; Wed, 06 Jun 2012 15:35:36 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIGk-0006iK-F9
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:35:34 +0000
Received: from [85.158.143.99:7050] by server-2.bemta-4.messagelabs.com id
	1A/AA-17938-5C87FCF4; Wed, 06 Jun 2012 15:35:33 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1338996930!29273162!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8418 invoked from network); 6 Jun 2012 15:35:31 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 15:35:31 -0000
Received: by eekd41 with SMTP id d41so2579876eek.32
	for ; Wed, 06 Jun 2012 08:35:29 -0700 (PDT)
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:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=+yE5V7Js7AZgmLLkeb55yBzWJ7itscCyHf5DWAmwO0Y=;
	b=jdrJdA1fm/Y5NjJAPTBlka05ZcfgMnJ0IrsUdfgX1VGNYFI+6FBeG+Ai8f2HD/x14n
	PBiBrAcyOkZs+MgP1++q8+mTcM31sBV+iaUxLKL7wTCgllJlR8HAUWvtgKsVTdZTbObG
	WFnnMgwBd50/aXNOC+pAOY2bpNTwN8ch/8SzTcFOJIq04Ob4nr1w9AFfvHcLeAV5irji
	UQUQVsFWKFV3no0zQRFOwDYPdy5bMOOEISOhdtT6tBUKp2VBcj8Dj5Q70re7EXG4pqCn
	3TBnTdpHVhw4H5eK/xhKTST7zw8aNysTvA72+/ZvYK9X0s9SHwxWl/nnnbX1ViziFP75
	qXfw==
Received: by 10.14.97.131 with SMTP id t3mr856082eef.196.1338996929490;
	Wed, 06 Jun 2012 08:35:29 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id p41sm604637eef.5.2012.06.06.08.35.26
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 08:35:27 -0700 (PDT)
Message-ID: <4FCF78BD.3040909@xen.org>
Date: Wed, 06 Jun 2012 16:35:25 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ian Jackson 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
In-Reply-To: <20425.472.655564.805506@mariner.uk.xensource.com>
Cc: xen-users@lists.xen.org, "xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 01/06/2012 18:54, Ian Jackson wrote:
> Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals"):
>> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed
>> front-page
> This one is already much better than the existing front page.  I have
> made some more changes.
Great!

> The links under "Xen Docs" are rather poor.  I don't know what pages
> we have that would do better, but the top link being the Wiki category
> listing is quite unhelpful.
Would a ...
1) link to http://wiki.xen.org/wiki/Xen_4.x_Manuals instead of 
http://wiki.xen.org/wiki/Category:Manual be better?
2) We could move http://wiki.xen.org/wiki/Xen_Beginners_Guide one up - 
it is a step-by-step tutorial to set up Xen 4 with Squeeze

Part of the problem is that there is a lot of stuff and it is hard to 
choose what is relevant

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 15:36:38 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:36:38 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScIGm-0006iu-3w; Wed, 06 Jun 2012 15:35:36 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIGk-0006iK-F9
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:35:34 +0000
Received: from [85.158.143.99:7050] by server-2.bemta-4.messagelabs.com id
	1A/AA-17938-5C87FCF4; Wed, 06 Jun 2012 15:35:33 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1338996930!29273162!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8418 invoked from network); 6 Jun 2012 15:35:31 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 15:35:31 -0000
Received: by eekd41 with SMTP id d41so2579876eek.32
	for ; Wed, 06 Jun 2012 08:35:29 -0700 (PDT)
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:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=+yE5V7Js7AZgmLLkeb55yBzWJ7itscCyHf5DWAmwO0Y=;
	b=jdrJdA1fm/Y5NjJAPTBlka05ZcfgMnJ0IrsUdfgX1VGNYFI+6FBeG+Ai8f2HD/x14n
	PBiBrAcyOkZs+MgP1++q8+mTcM31sBV+iaUxLKL7wTCgllJlR8HAUWvtgKsVTdZTbObG
	WFnnMgwBd50/aXNOC+pAOY2bpNTwN8ch/8SzTcFOJIq04Ob4nr1w9AFfvHcLeAV5irji
	UQUQVsFWKFV3no0zQRFOwDYPdy5bMOOEISOhdtT6tBUKp2VBcj8Dj5Q70re7EXG4pqCn
	3TBnTdpHVhw4H5eK/xhKTST7zw8aNysTvA72+/ZvYK9X0s9SHwxWl/nnnbX1ViziFP75
	qXfw==
Received: by 10.14.97.131 with SMTP id t3mr856082eef.196.1338996929490;
	Wed, 06 Jun 2012 08:35:29 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id p41sm604637eef.5.2012.06.06.08.35.26
	(version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 08:35:27 -0700 (PDT)
Message-ID: <4FCF78BD.3040909@xen.org>
Date: Wed, 06 Jun 2012 16:35:25 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ian Jackson 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
In-Reply-To: <20425.472.655564.805506@mariner.uk.xensource.com>
Cc: xen-users@lists.xen.org, "xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 01/06/2012 18:54, Ian Jackson wrote:
> Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki Front-Page - need input/mods/creative proposals"):
>> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case focussed
>> front-page
> This one is already much better than the existing front page.  I have
> made some more changes.
Great!

> The links under "Xen Docs" are rather poor.  I don't know what pages
> we have that would do better, but the top link being the Wiki category
> listing is quite unhelpful.
Would a ...
1) link to http://wiki.xen.org/wiki/Xen_4.x_Manuals instead of 
http://wiki.xen.org/wiki/Category:Manual be better?
2) We could move http://wiki.xen.org/wiki/Xen_Beginners_Guide one up - 
it is a step-by-step tutorial to set up Xen 4 with Squeeze

Part of the problem is that there is a lot of stuff and it is hard to 
choose what is relevant

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 15:47:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:47: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 1ScIRT-0007Kt-Pn; Wed, 06 Jun 2012 15:46:39 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIRS-0007Kl-Jg
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:46:38 +0000
Received: from [85.158.139.83:34035] by server-11.bemta-5.messagelabs.com id
	B7/5A-25194-D5B7FCF4; Wed, 06 Jun 2012 15:46:37 +0000
X-Env-Sender: sebastien.prouff@ac-poitiers.fr
X-Msg-Ref: server-8.tower-182.messagelabs.com!1338997596!18457841!1
X-Originating-IP: [195.83.12.242]
X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31383 invoked from network); 6 Jun 2012 15:46:36 -0000
Received: from smtp1.ac-poitiers.fr (HELO smtp1.ac-poitiers.fr) (195.83.12.242)
	by server-8.tower-182.messagelabs.com with SMTP;
	6 Jun 2012 15:46:36 -0000
Received: from localhost (smtp1.ac-poitiers.fr [127.0.0.1])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 958067A380
	for ; Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
X-Virus-Scanned: Scanned by smtp for ac-poitiers.fr
Received: from smtp1.ac-poitiers.fr ([127.0.0.1])
	by localhost (smtp1.ac-poitiers.fr [127.0.0.1]) (amavisd-new,
	port 51025) with ESMTP id SNirAgjEyyz2 for ;
	Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
Received: from [10.0.17.41] (unknown [195.221.249.6])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 6B4CB7A376
	for ; Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
Message-ID: <4FCF7B5B.6010606@ac-poitiers.fr>
Date: Wed, 06 Jun 2012 17:46:35 +0200
From: sebastien PROUFF 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCF66BB.2030901@ac-poitiers.fr>
	
In-Reply-To: 
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2053497512067751378=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============2053497512067751378==
Content-Type: multipart/alternative;
 boundary="------------070001090607060809070402"

This is a multi-part message in MIME format.
--------------070001090607060809070402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Andrew,

thanks for your reply.
OK, always read introduction first, sorry ;

The server I want to install nut on is in production. So, I want to keep 
the basic configuration if possible.
So, I tried to follow your how to ( included the rpm), and it worked 
like a charm !

In my configuration, the nut server is on a debian server and my XCP 
server are connecting on it without problem.

Thanks you

Sébastien Prouff
PS : next thing to do : put the switch on the UPS !

Le 06/06/2012 16:30, Andrew Eross a écrit :
> Hey Sebastien,
>
> I wrote that howto a bit ago, and yeah I couldn't really find a better 
> package, although I did basically get nut working with my ups.
>
> If you have any additional success here, please share, or update the wiki.
>
> XCP is CentOS, based on XenServer 5.6 FP1 (read 
> http://wiki.xen.org/wiki/XCP_Introduction)
>
> You can even install normal packages after enabling the repo, using 
> yum, like this:
>
> sed -i -e "s/enabled=0/enabled=1/" /etc/yum.repos.d/CentOS-Base.repo
> sed -i -e "s/enabled=1/enabled=0/" /etc/yum.repos.d/Citrix.repo
> yum install 
>
> If you're feeling daring, you could try to compile your own nut by 
> installing build tools first, e.g.
> yum install gcc flex rpm-build redhat-rpm-config make (etc)
>
> Wouldn't recommend adding all that junk onto a production box, but you 
> could do it on a throw-away dev dom0.
>
> Cheers,
> Andrew
>
>
>
>
>
> On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF 
>  > wrote:
>
>     Hi,
>
>     I want to monitor my XCP server with nut.
>
>     So, after a google search I've been there.
>     http://wiki.xen.org/wiki/XCP_NUT
>
>     It sound great, but the nut packet I can download from alyseo
>     seems outdated.
>     I would like to download the right one for my distro but...what is
>     the distribution ?
>
>     #cat /etc/issue
>     xen.org  XCP 1.1.0-50674c
>
>     XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
>     based on RHE ?
>     Whoo, i'm lost !
>     Please tell me where i can find the right rpm package for my xcp
>     server.
>
>     Cheers
>
>     -- 
>     Sébastien Prouff
>
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xen.org 
>     http://lists.xen.org/xen-users
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

--------------070001090607060809070402
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hi Andrew, 

    

    thanks for your reply.

    OK, always read introduction first, sorry ;

    

    The server I want to install nut on is in production. So, I want to
    keep the basic configuration if possible.

    So, I tried to follow your how to ( included the rpm), and it worked
    like a charm !

    

    In my configuration, the nut server is on a debian server and my XCP
    server are connecting on it without problem.

    

    Thanks you

    

    
Sébastien Prouff
PS : next thing to do : put the switch on the UPS !


    Le 06/06/2012 16:30, Andrew Eross a écrit :
    
Hey Sebastien,
      


      

      
I wrote that howto a bit ago, and yeah I couldn't really find
        a better package, although I did basically get nut working with
        my ups.

      


      

      
If you have any additional success here, please share, or
        update the wiki.

      


      

      
XCP is CentOS, based on XenServer 5.6 FP1 (read http://wiki.xen.org/wiki/XCP_Introduction)

      


      

      
You can even install normal packages after enabling the repo,
        using yum, like this:

      


      

      

        
sed -i -e "s/enabled=0/enabled=1/"
          /etc/yum.repos.d/CentOS-Base.repo

        
sed -i -e "s/enabled=1/enabled=0/"
          /etc/yum.repos.d/Citrix.repo

        
yum install <whatever>

      

      


      

      
If you're feeling daring, you could try to compile your own
        nut by installing build tools first, e.g.

      
yum install gcc flex rpm-build redhat-rpm-config make (etc)

      


      

      
Wouldn't recommend adding all that junk onto a production
        box, but you could do it on a throw-away dev dom0.

      


      

      
Cheers,

      
Andrew

      


      

      


        

        

        

        
On Wed, Jun 6, 2012 at 11:18 AM,
          sebastien PROUFF <sebastien.prouff@ac-poitiers.fr>
          wrote:

          

            
 Hi, 

              

              I want to monitor my XCP server with nut.

              

              So, after a google search I've been there.

              http://wiki.xen.org/wiki/XCP_NUT

              

              It sound great, but the nut packet I can download from
              alyseo seems outdated.

              I would like to download the right one for my distro
              but...what is the distribution ?

              

              #cat /etc/issue

                xen.org XCP 1.1.0-50674c

              

              XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?)
              with is based on RHE ?

              Whoo, i'm lost !

              Please tell me where i can find the right rpm package for
              my xcp server.

              

              Cheers

                  

                  
-- 
Sébastien Prouff


                

            

            _______________________________________________

            Xen-users mailing list

            Xen-users@lists.xen.org

            http://lists.xen.org/xen-users

          

        

        

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

  


--------------070001090607060809070402--


--===============2053497512067751378==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2053497512067751378==--


From xen-users-bounces@lists.xen.org Wed Jun 06 15:47:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:47: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 1ScIRT-0007Kt-Pn; Wed, 06 Jun 2012 15:46:39 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIRS-0007Kl-Jg
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:46:38 +0000
Received: from [85.158.139.83:34035] by server-11.bemta-5.messagelabs.com id
	B7/5A-25194-D5B7FCF4; Wed, 06 Jun 2012 15:46:37 +0000
X-Env-Sender: sebastien.prouff@ac-poitiers.fr
X-Msg-Ref: server-8.tower-182.messagelabs.com!1338997596!18457841!1
X-Originating-IP: [195.83.12.242]
X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31383 invoked from network); 6 Jun 2012 15:46:36 -0000
Received: from smtp1.ac-poitiers.fr (HELO smtp1.ac-poitiers.fr) (195.83.12.242)
	by server-8.tower-182.messagelabs.com with SMTP;
	6 Jun 2012 15:46:36 -0000
Received: from localhost (smtp1.ac-poitiers.fr [127.0.0.1])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 958067A380
	for ; Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
X-Virus-Scanned: Scanned by smtp for ac-poitiers.fr
Received: from smtp1.ac-poitiers.fr ([127.0.0.1])
	by localhost (smtp1.ac-poitiers.fr [127.0.0.1]) (amavisd-new,
	port 51025) with ESMTP id SNirAgjEyyz2 for ;
	Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
Received: from [10.0.17.41] (unknown [195.221.249.6])
	by smtp1.ac-poitiers.fr (Postfix) with ESMTP id 6B4CB7A376
	for ; Wed,  6 Jun 2012 17:46:36 +0200 (CEST)
Message-ID: <4FCF7B5B.6010606@ac-poitiers.fr>
Date: Wed, 06 Jun 2012 17:46:35 +0200
From: sebastien PROUFF 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: <4FCF66BB.2030901@ac-poitiers.fr>
	
In-Reply-To: 
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2053497512067751378=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============2053497512067751378==
Content-Type: multipart/alternative;
 boundary="------------070001090607060809070402"

This is a multi-part message in MIME format.
--------------070001090607060809070402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Andrew,

thanks for your reply.
OK, always read introduction first, sorry ;

The server I want to install nut on is in production. So, I want to keep 
the basic configuration if possible.
So, I tried to follow your how to ( included the rpm), and it worked 
like a charm !

In my configuration, the nut server is on a debian server and my XCP 
server are connecting on it without problem.

Thanks you

Sébastien Prouff
PS : next thing to do : put the switch on the UPS !

Le 06/06/2012 16:30, Andrew Eross a écrit :
> Hey Sebastien,
>
> I wrote that howto a bit ago, and yeah I couldn't really find a better 
> package, although I did basically get nut working with my ups.
>
> If you have any additional success here, please share, or update the wiki.
>
> XCP is CentOS, based on XenServer 5.6 FP1 (read 
> http://wiki.xen.org/wiki/XCP_Introduction)
>
> You can even install normal packages after enabling the repo, using 
> yum, like this:
>
> sed -i -e "s/enabled=0/enabled=1/" /etc/yum.repos.d/CentOS-Base.repo
> sed -i -e "s/enabled=1/enabled=0/" /etc/yum.repos.d/Citrix.repo
> yum install 
>
> If you're feeling daring, you could try to compile your own nut by 
> installing build tools first, e.g.
> yum install gcc flex rpm-build redhat-rpm-config make (etc)
>
> Wouldn't recommend adding all that junk onto a production box, but you 
> could do it on a throw-away dev dom0.
>
> Cheers,
> Andrew
>
>
>
>
>
> On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF 
>  > wrote:
>
>     Hi,
>
>     I want to monitor my XCP server with nut.
>
>     So, after a google search I've been there.
>     http://wiki.xen.org/wiki/XCP_NUT
>
>     It sound great, but the nut packet I can download from alyseo
>     seems outdated.
>     I would like to download the right one for my distro but...what is
>     the distribution ?
>
>     #cat /etc/issue
>     xen.org  XCP 1.1.0-50674c
>
>     XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is
>     based on RHE ?
>     Whoo, i'm lost !
>     Please tell me where i can find the right rpm package for my xcp
>     server.
>
>     Cheers
>
>     -- 
>     Sébastien Prouff
>
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xen.org 
>     http://lists.xen.org/xen-users
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

--------------070001090607060809070402
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hi Andrew, 

    

    thanks for your reply.

    OK, always read introduction first, sorry ;

    

    The server I want to install nut on is in production. So, I want to
    keep the basic configuration if possible.

    So, I tried to follow your how to ( included the rpm), and it worked
    like a charm !

    

    In my configuration, the nut server is on a debian server and my XCP
    server are connecting on it without problem.

    

    Thanks you

    

    
Sébastien Prouff
PS : next thing to do : put the switch on the UPS !


    Le 06/06/2012 16:30, Andrew Eross a écrit :
    
Hey Sebastien,
      


      

      
I wrote that howto a bit ago, and yeah I couldn't really find
        a better package, although I did basically get nut working with
        my ups.

      


      

      
If you have any additional success here, please share, or
        update the wiki.

      


      

      
XCP is CentOS, based on XenServer 5.6 FP1 (read http://wiki.xen.org/wiki/XCP_Introduction)

      


      

      
You can even install normal packages after enabling the repo,
        using yum, like this:

      


      

      

        
sed -i -e "s/enabled=0/enabled=1/"
          /etc/yum.repos.d/CentOS-Base.repo

        
sed -i -e "s/enabled=1/enabled=0/"
          /etc/yum.repos.d/Citrix.repo

        
yum install <whatever>

      

      


      

      
If you're feeling daring, you could try to compile your own
        nut by installing build tools first, e.g.

      
yum install gcc flex rpm-build redhat-rpm-config make (etc)

      


      

      
Wouldn't recommend adding all that junk onto a production
        box, but you could do it on a throw-away dev dom0.

      


      

      
Cheers,

      
Andrew

      


      

      


        

        

        

        
On Wed, Jun 6, 2012 at 11:18 AM,
          sebastien PROUFF <sebastien.prouff@ac-poitiers.fr>
          wrote:

          

            
 Hi, 

              

              I want to monitor my XCP server with nut.

              

              So, after a google search I've been there.

              http://wiki.xen.org/wiki/XCP_NUT

              

              It sound great, but the nut packet I can download from
              alyseo seems outdated.

              I would like to download the right one for my distro
              but...what is the distribution ?

              

              #cat /etc/issue

                xen.org XCP 1.1.0-50674c

              

              XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?)
              with is based on RHE ?

              Whoo, i'm lost !

              Please tell me where i can find the right rpm package for
              my xcp server.

              

              Cheers

                  

                  
-- 
Sébastien Prouff


                

            

            _______________________________________________

            Xen-users mailing list

            Xen-users@lists.xen.org

            http://lists.xen.org/xen-users

          

        

        

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

  


--------------070001090607060809070402--


--===============2053497512067751378==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2053497512067751378==--


From xen-users-bounces@lists.xen.org Wed Jun 06 15:58:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:58: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 1ScIbq-0007tv-3Y; Wed, 06 Jun 2012 15:57:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIbo-0007tl-Az
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:57:20 +0000
Received: from [193.109.254.147:47898] by server-1.bemta-14.messagelabs.com id
	9F/F9-08067-FDD7FCF4; Wed, 06 Jun 2012 15:57:19 +0000
X-Env-Sender: eross@corp.locatrix.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1338998212!12746349!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16372 invoked from network); 6 Jun 2012 15:56:56 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 15:56:56 -0000
Received: by ggnp1 with SMTP id p1so5980901ggn.32
	for ; Wed, 06 Jun 2012 08:56:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=p7yayf7rcIkwNFydmN8vzOigEFYAxLz5tLfogMdyYU8=;
	b=K1H0JAxXabEQC032c3xb6XMwExf1t6iwuR1W+JnbaMlXzzL2upYouA4KO+m5AhBO1a
	Dhj+HIe6xljQyiynGZ9FnJXfeWjfVjeaq3BJqkdgO/F8k0hJL9853L+aNouWFX4RnpHB
	b5IbFax6uAtaKm9Pwo0oHyyX7tT1ObL6FAdJlOVF4R8L0UFrWfjTUQ/AAT1P3+ivDRW1
	iuVNCdjqjX+1ExB3jMW74kV5ZU58I9ZPLEHVgGhhfLQukvlx5xyLc+KfpvHmcrmaR3ft
	MAY4Fs7OxIcCMUxt92gFONDlaEE4f6Inj6kRj874/NMruL0zaeuqsWvm54sUxDgBSwSA
	xkRg==
Received: by 10.60.3.194 with SMTP id e2mr16356169oee.1.1338998210555; Wed, 06
	Jun 2012 08:56:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.128.71 with HTTP; Wed, 6 Jun 2012 08:56:30 -0700 (PDT)
In-Reply-To: <4FCF7B5B.6010606@ac-poitiers.fr>
References: <4FCF66BB.2030901@ac-poitiers.fr>
	
	<4FCF7B5B.6010606@ac-poitiers.fr>
From: Andrew Eross 
Date: Wed, 6 Jun 2012 12:56:30 -0300
Message-ID: 
To: sebastien PROUFF 
X-Gm-Message-State: ALoCoQl9NGFvw3ynBkhh9cta1b652+gNGNj03YultmvRhF1QBnZ/rxCJBx9uNNsYyluiqxx9p329
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0066084510394294564=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0066084510394294564==
Content-Type: multipart/alternative; boundary=e89a8fb202a0b1efba04c1cfd0f2

--e89a8fb202a0b1efba04c1cfd0f2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Glad to hear it!

Just a suggestion as well, recommend to keep run sheets (e.g. list of
commands you performed) for any changes to the dom0... if you do an XCP
version upgrade in the future, it'll all get wiped out and you'll need to
redo your custom work.

On Wed, Jun 6, 2012 at 12:46 PM, sebastien PROUFF <
sebastien.prouff@ac-poitiers.fr> wrote:

>  Hi Andrew,
>
> thanks for your reply.
> OK, always read introduction first, sorry ;
>
> The server I want to install nut on is in production. So, I want to keep
> the basic configuration if possible.
> So, I tried to follow your how to ( included the rpm), and it worked like
> a charm !
>
> In my configuration, the nut server is on a debian server and my XCP
> server are connecting on it without problem.
>
> Thanks you
>
> S=E9bastien Prouff
> PS : next thing to do : put the switch on the UPS !
>
> Le 06/06/2012 16:30, Andrew Eross a =E9crit :
>
> Hey Sebastien,
>
>  I wrote that howto a bit ago, and yeah I couldn't really find a better
> package, although I did basically get nut working with my ups.
>
>  If you have any additional success here, please share, or update the
> wiki.
>
>  XCP is CentOS, based on XenServer 5.6 FP1 (read
> http://wiki.xen.org/wiki/XCP_Introduction)
>
>  You can even install normal packages after enabling the repo, using yum,
> like this:
>
>  sed -i -e "s/enabled=3D0/enabled=3D1/" /etc/yum.repos.d/CentOS-Base.repo
> sed -i -e "s/enabled=3D1/enabled=3D0/" /etc/yum.repos.d/Citrix.repo
> yum install 
>
>  If you're feeling daring, you could try to compile your own nut by
> installing build tools first, e.g.
> yum install gcc flex rpm-build redhat-rpm-config make (etc)
>
>  Wouldn't recommend adding all that junk onto a production box, but you
> could do it on a throw-away dev dom0.
>
>  Cheers,
> Andrew
>
>
>
>
>
> On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF <
> sebastien.prouff@ac-poitiers.fr> wrote:
>
>>  Hi,
>>
>> I want to monitor my XCP server with nut.
>>
>> So, after a google search I've been there.
>> http://wiki.xen.org/wiki/XCP_NUT
>>
>> It sound great, but the nut packet I can download from alyseo seems
>> outdated.
>> I would like to download the right one for my distro but...what is the
>> distribution ?
>>
>> #cat /etc/issue
>> xen.org XCP 1.1.0-50674c
>>
>> XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based
>> on RHE ?
>> Whoo, i'm lost !
>> Please tell me where i can find the right rpm package for my xcp server.
>>
>> Cheers
>>
>> --
>> S=E9bastien Prouff
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>
>
>
> _______________________________________________
> Xen-users mailing listXen-users@lists.xen.orghttp://lists.xen.org/xen-use=
rs
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8fb202a0b1efba04c1cfd0f2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Glad to hear it!

Just a suggestion as well, recommend to=
 keep run sheets (e.g. list of commands you performed) for any changes to t=
he dom0... if you do an XCP version upgrade in the future, it'll all ge=
t wiped out and you'll need to redo your custom work.





On Wed, Jun 6, 2012 at 12:46=
 PM, sebastien PROUFF <sebastien.prouff@ac-poitiers.fr&g=
t; wrote:





 =20
   =20
 =20
  

    Hi Andrew, 

    

    thanks for your reply.

    OK, always read introduction first, sorry ;

    

    The server I want to install nut on is in production. So, I want to
    keep the basic configuration if possible.

    So, I tried to follow your how to ( included the rpm), and it worked
    like a charm !

    

    In my configuration, the nut server is on a debian server and my XCP
    server are connecting on it without problem.

    

    Thanks you

    

    
S=E9bastien Prouff
PS : next thing to do : put the switch on the UPS !


    Le 06/06/2012 16:30, Andrew Eross a =E9crit=A0:
    
Hey Sebastien,
      


      

      
I wrote that howto a bit ago, and yeah I couldn't really fin=
d
        a better package, although I did basically get nut working with
        my ups.

      


      

      
If you have any additional success here, please share, or
        update the wiki.

      


      

      
XCP is CentOS, based on=A0XenServer 5.6 FP1 (read=A0http://wiki.xen=
.org/wiki/XCP_Introduction)

      


      

      
You can even install normal packages after enabling the repo,
        using yum, like this:

      


      

      

        
sed -i -e "s/enabled=3D0/enabled=3D1/"
          /etc/yum.repos.d/CentOS-Base.repo

        
sed -i -e "s/enabled=3D1/enabled=3D0/"
          /etc/yum.repos.d/Citrix.repo

        
yum install <whatever>

      

      


      

      
If you're feeling daring, you could try to compile your own
        nut by installing build tools first, e.g.

      
yum install gcc flex rpm-build redhat-rpm-config make (etc)
      


      

      
Wouldn't recommend adding all that junk onto a production
        box, but you could do it on a throw-away dev dom0.

      


      

      
Cheers,

      
Andrew

      


      

      


        

        

        

        
On Wed, Jun 6, 2012 at 11:18 AM,
          sebastien PROUFF <sebastien.prouff@ac-poitiers.fr<=
/a>>
          wrote:

          

            
 Hi, 

              

              I want to monitor my XCP server with nut.

              

              So, after a google search I've been there.

              http://wiki.xen.org/wiki/XCP_NUT

              

              It sound great, but the nut packet I can download from
              alyseo seems outdated.

              I would like to download the right one for my distro
              but...what is the distribution ?

              

              #cat /etc/issue

                xen.org XC=
P 1.1.0-50674c

              

              XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?)
              with is based on RHE ?

              Whoo, i'm lost !

              Please tell me where i can find the right rpm package for
              my xcp server.

              

              Cheers

                  

                  
--=20
S=E9bastien Prouff


                

            

            _______________________________________________

            Xen-users mailing list

            Xe=
n-users@lists.xen.org

            ht=
tp://lists.xen.org/xen-users

          

        

        

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@list=
s.xen.org
http://lists.x=
en.org/xen-users

    

  



_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users



--e89a8fb202a0b1efba04c1cfd0f2--


--===============0066084510394294564==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0066084510394294564==--


From xen-users-bounces@lists.xen.org Wed Jun 06 15:58:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 15:58: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 1ScIbq-0007tv-3Y; Wed, 06 Jun 2012 15:57:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScIbo-0007tl-Az
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 15:57:20 +0000
Received: from [193.109.254.147:47898] by server-1.bemta-14.messagelabs.com id
	9F/F9-08067-FDD7FCF4; Wed, 06 Jun 2012 15:57:19 +0000
X-Env-Sender: eross@corp.locatrix.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1338998212!12746349!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16372 invoked from network); 6 Jun 2012 15:56:56 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 15:56:56 -0000
Received: by ggnp1 with SMTP id p1so5980901ggn.32
	for ; Wed, 06 Jun 2012 08:56:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=p7yayf7rcIkwNFydmN8vzOigEFYAxLz5tLfogMdyYU8=;
	b=K1H0JAxXabEQC032c3xb6XMwExf1t6iwuR1W+JnbaMlXzzL2upYouA4KO+m5AhBO1a
	Dhj+HIe6xljQyiynGZ9FnJXfeWjfVjeaq3BJqkdgO/F8k0hJL9853L+aNouWFX4RnpHB
	b5IbFax6uAtaKm9Pwo0oHyyX7tT1ObL6FAdJlOVF4R8L0UFrWfjTUQ/AAT1P3+ivDRW1
	iuVNCdjqjX+1ExB3jMW74kV5ZU58I9ZPLEHVgGhhfLQukvlx5xyLc+KfpvHmcrmaR3ft
	MAY4Fs7OxIcCMUxt92gFONDlaEE4f6Inj6kRj874/NMruL0zaeuqsWvm54sUxDgBSwSA
	xkRg==
Received: by 10.60.3.194 with SMTP id e2mr16356169oee.1.1338998210555; Wed, 06
	Jun 2012 08:56:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.128.71 with HTTP; Wed, 6 Jun 2012 08:56:30 -0700 (PDT)
In-Reply-To: <4FCF7B5B.6010606@ac-poitiers.fr>
References: <4FCF66BB.2030901@ac-poitiers.fr>
	
	<4FCF7B5B.6010606@ac-poitiers.fr>
From: Andrew Eross 
Date: Wed, 6 Jun 2012 12:56:30 -0300
Message-ID: 
To: sebastien PROUFF 
X-Gm-Message-State: ALoCoQl9NGFvw3ynBkhh9cta1b652+gNGNj03YultmvRhF1QBnZ/rxCJBx9uNNsYyluiqxx9p329
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] XCP nut monitoring
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0066084510394294564=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============0066084510394294564==
Content-Type: multipart/alternative; boundary=e89a8fb202a0b1efba04c1cfd0f2

--e89a8fb202a0b1efba04c1cfd0f2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Glad to hear it!

Just a suggestion as well, recommend to keep run sheets (e.g. list of
commands you performed) for any changes to the dom0... if you do an XCP
version upgrade in the future, it'll all get wiped out and you'll need to
redo your custom work.

On Wed, Jun 6, 2012 at 12:46 PM, sebastien PROUFF <
sebastien.prouff@ac-poitiers.fr> wrote:

>  Hi Andrew,
>
> thanks for your reply.
> OK, always read introduction first, sorry ;
>
> The server I want to install nut on is in production. So, I want to keep
> the basic configuration if possible.
> So, I tried to follow your how to ( included the rpm), and it worked like
> a charm !
>
> In my configuration, the nut server is on a debian server and my XCP
> server are connecting on it without problem.
>
> Thanks you
>
> S=E9bastien Prouff
> PS : next thing to do : put the switch on the UPS !
>
> Le 06/06/2012 16:30, Andrew Eross a =E9crit :
>
> Hey Sebastien,
>
>  I wrote that howto a bit ago, and yeah I couldn't really find a better
> package, although I did basically get nut working with my ups.
>
>  If you have any additional success here, please share, or update the
> wiki.
>
>  XCP is CentOS, based on XenServer 5.6 FP1 (read
> http://wiki.xen.org/wiki/XCP_Introduction)
>
>  You can even install normal packages after enabling the repo, using yum,
> like this:
>
>  sed -i -e "s/enabled=3D0/enabled=3D1/" /etc/yum.repos.d/CentOS-Base.repo
> sed -i -e "s/enabled=3D1/enabled=3D0/" /etc/yum.repos.d/Citrix.repo
> yum install 
>
>  If you're feeling daring, you could try to compile your own nut by
> installing build tools first, e.g.
> yum install gcc flex rpm-build redhat-rpm-config make (etc)
>
>  Wouldn't recommend adding all that junk onto a production box, but you
> could do it on a throw-away dev dom0.
>
>  Cheers,
> Andrew
>
>
>
>
>
> On Wed, Jun 6, 2012 at 11:18 AM, sebastien PROUFF <
> sebastien.prouff@ac-poitiers.fr> wrote:
>
>>  Hi,
>>
>> I want to monitor my XCP server with nut.
>>
>> So, after a google search I've been there.
>> http://wiki.xen.org/wiki/XCP_NUT
>>
>> It sound great, but the nut packet I can download from alyseo seems
>> outdated.
>> I would like to download the right one for my distro but...what is the
>> distribution ?
>>
>> #cat /etc/issue
>> xen.org XCP 1.1.0-50674c
>>
>> XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?) with is based
>> on RHE ?
>> Whoo, i'm lost !
>> Please tell me where i can find the right rpm package for my xcp server.
>>
>> Cheers
>>
>> --
>> S=E9bastien Prouff
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>
>
>
> _______________________________________________
> Xen-users mailing listXen-users@lists.xen.orghttp://lists.xen.org/xen-use=
rs
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

--e89a8fb202a0b1efba04c1cfd0f2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Glad to hear it!

Just a suggestion as well, recommend to=
 keep run sheets (e.g. list of commands you performed) for any changes to t=
he dom0... if you do an XCP version upgrade in the future, it'll all ge=
t wiped out and you'll need to redo your custom work.





On Wed, Jun 6, 2012 at 12:46=
 PM, sebastien PROUFF <sebastien.prouff@ac-poitiers.fr&g=
t; wrote:





 =20
   =20
 =20
  

    Hi Andrew, 

    

    thanks for your reply.

    OK, always read introduction first, sorry ;

    

    The server I want to install nut on is in production. So, I want to
    keep the basic configuration if possible.

    So, I tried to follow your how to ( included the rpm), and it worked
    like a charm !

    

    In my configuration, the nut server is on a debian server and my XCP
    server are connecting on it without problem.

    

    Thanks you

    

    
S=E9bastien Prouff
PS : next thing to do : put the switch on the UPS !


    Le 06/06/2012 16:30, Andrew Eross a =E9crit=A0:
    
Hey Sebastien,
      


      

      
I wrote that howto a bit ago, and yeah I couldn't really fin=
d
        a better package, although I did basically get nut working with
        my ups.

      


      

      
If you have any additional success here, please share, or
        update the wiki.

      


      

      
XCP is CentOS, based on=A0XenServer 5.6 FP1 (read=A0http://wiki.xen=
.org/wiki/XCP_Introduction)

      


      

      
You can even install normal packages after enabling the repo,
        using yum, like this:

      


      

      

        
sed -i -e "s/enabled=3D0/enabled=3D1/"
          /etc/yum.repos.d/CentOS-Base.repo

        
sed -i -e "s/enabled=3D1/enabled=3D0/"
          /etc/yum.repos.d/Citrix.repo

        
yum install <whatever>

      

      


      

      
If you're feeling daring, you could try to compile your own
        nut by installing build tools first, e.g.

      
yum install gcc flex rpm-build redhat-rpm-config make (etc)
      


      

      
Wouldn't recommend adding all that junk onto a production
        box, but you could do it on a throw-away dev dom0.

      


      

      
Cheers,

      
Andrew

      


      

      


        

        

        

        
On Wed, Jun 6, 2012 at 11:18 AM,
          sebastien PROUFF <sebastien.prouff@ac-poitiers.fr<=
/a>>
          wrote:

          

            
 Hi, 

              

              I want to monitor my XCP server with nut.

              

              So, after a google search I've been there.

              http://wiki.xen.org/wiki/XCP_NUT

              

              It sound great, but the nut packet I can download from
              alyseo seems outdated.

              I would like to download the right one for my distro
              but...what is the distribution ?

              

              #cat /etc/issue

                xen.org XC=
P 1.1.0-50674c

              

              XCP1.1 is based on XenServer (with version 5.6, v5.6.2 ?)
              with is based on RHE ?

              Whoo, i'm lost !

              Please tell me where i can find the right rpm package for
              my xcp server.

              

              Cheers

                  

                  
--=20
S=E9bastien Prouff


                

            

            _______________________________________________

            Xen-users mailing list

            Xe=
n-users@lists.xen.org

            ht=
tp://lists.xen.org/xen-users

          

        

        

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@list=
s.xen.org
http://lists.x=
en.org/xen-users

    

  



_______________________________________________

Xen-users mailing list

Xen-users@list=
s.xen.org

http://lists.x=
en.org/xen-users



--e89a8fb202a0b1efba04c1cfd0f2--


--===============0066084510394294564==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============0066084510394294564==--


From xen-users-bounces@lists.xen.org Wed Jun 06 16:40:26 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 16:40: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 1ScJGP-0001N7-DC; Wed, 06 Jun 2012 16:39:17 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScJGO-0001N2-Jp
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 16:39:16 +0000
Received: from [85.158.139.83:52324] by server-12.bemta-5.messagelabs.com id
	26/BE-18374-3B78FCF4; Wed, 06 Jun 2012 16:39:15 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-14.tower-182.messagelabs.com!1339000754!28033039!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12253 invoked from network); 6 Jun 2012 16:39:14 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-14.tower-182.messagelabs.com with SMTP;
	6 Jun 2012 16:39:14 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Wed, 6 Jun 2012 09:39:12 -0700
Received: from [192.168.3.7] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 7E62C38A17E;
	Wed,  6 Jun 2012 09:39:12 -0700 (PDT)
From: bill@b2bassadventures.com
To: Ian Campbell 
Date: Wed, 06 Jun 2012 09:39:17 -0700
MIME-Version: 1.0
Message-ID: <4FCF87B5.27314.3C194B0F@bill.b2bassadventures.com>
Priority: normal
In-reply-to: <1338994086.32319.119.camel@zakaz.uk.xensource.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>,
	<4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>,
	<1338994086.32319.119.camel@zakaz.uk.xensource.com>
X-mailer: Pegasus Mail for Windows (4.63)
Content-description: Mail message body
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 6 Jun 2012 at 15:48, Ian Campbell wrote:


> > br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
> > get them to start.
> 
> Do you have "auto br0" etc in your /etc/network/interfaces?
> 
> If you still have problems then please show us the config you are using.
> 
Thanks for that. Clean forgot about the auto part in the file. 

On your other questions/answers I have to get back to ya. Im under a tight schedual today. 
Im retired on disability and do the linux stuff to supliment my income. I also am a bass 
fishing guide and I have a 4 day trip to get ready for today. Ill try and get back to ya later 
today if not it will be monday


> > on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
> > shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
> > eth0.
> 
> I'm not entirely sure what you are describing here, can you describe
> what you do see vs. what you expected to see?
> 
> Did you expect to see eth1 in guest1? or did you expect to see eth0?
> 
> What does guest1's vif configuration line look like?
> 
> If you expected eth0 then you might have an issue with the udev
> persistent net rules, look under /etc/udev/rules.d for things which
> might be renaming eth0->eth1 on boot.
> 
> If you expected eth1 then obviously you need to have eth1 in the
> guest's /etc/network/interfaces if you want to use it.
> 
> > issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
> > and I can use it.
> 
> blocked just means the guest is idle (i.e. it is blocked in the
> hypervisor). It is still available to run if something happens. On a
> mostly idle system most guests will be blocked...
> 
> > Big question is how do I get these two guests to autostart if the server is rebooted?
> 
> The xendomains initscript can do this for you. IIRC you just need to put
> the config files in /etc/xen/auto instead of /etc/xen.
> 
> Ian.
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
> 



Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 16:40:26 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 16:40: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 1ScJGP-0001N7-DC; Wed, 06 Jun 2012 16:39:17 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScJGO-0001N2-Jp
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 16:39:16 +0000
Received: from [85.158.139.83:52324] by server-12.bemta-5.messagelabs.com id
	26/BE-18374-3B78FCF4; Wed, 06 Jun 2012 16:39:15 +0000
X-Env-Sender: bill@b2bassadventures.com
X-Msg-Ref: server-14.tower-182.messagelabs.com!1339000754!28033039!1
X-Originating-IP: [184.105.211.105]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12253 invoked from network); 6 Jun 2012 16:39:14 -0000
Received: from billbeau.net (HELO billbeau.net) (184.105.211.105)
	by server-14.tower-182.messagelabs.com with SMTP;
	6 Jun 2012 16:39:14 -0000
Received: from mail ([71.138.140.231]) by billbeau.net for
	; Wed, 6 Jun 2012 09:39:12 -0700
Received: from [192.168.3.7] (unknown [192.168.1.2])
	by mail (Postfix) with ESMTP id 7E62C38A17E;
	Wed,  6 Jun 2012 09:39:12 -0700 (PDT)
From: bill@b2bassadventures.com
To: Ian Campbell 
Date: Wed, 06 Jun 2012 09:39:17 -0700
MIME-Version: 1.0
Message-ID: <4FCF87B5.27314.3C194B0F@bill.b2bassadventures.com>
Priority: normal
In-reply-to: <1338994086.32319.119.camel@zakaz.uk.xensource.com>
References: <4FCD7E6D.5070004@b2bassadventures.com>,
	<4FCF6A60.28298.3BA6B65C@bill.b2bassadventures.com>,
	<1338994086.32319.119.camel@zakaz.uk.xensource.com>
X-mailer: Pegasus Mail for Windows (4.63)
Content-description: Mail message body
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] xen tutorials?
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 6 Jun 2012 at 15:48, Ian Campbell wrote:


> > br0 and br1 wont start upon dom0 startup. I have added ifup br0 and ifup br1 to rc.local to 
> > get them to start.
> 
> Do you have "auto br0" etc in your /etc/network/interfaces?
> 
> If you still have problems then please show us the config you are using.
> 
Thanks for that. Clean forgot about the auto part in the file. 

On your other questions/answers I have to get back to ya. Im under a tight schedual today. 
Im retired on disability and do the linux stuff to supliment my income. I also am a bass 
fishing guide and I have a 4 day trip to get ready for today. Ill try and get back to ya later 
today if not it will be monday


> > on guest1 using ifconfig I see eth1. Eth1 is not configured in /etc/network/interfaces so it 
> > shouldn't show up. It is not working as you can not ping its ip. Guest2 does use eth1 and not 
> > eth0.
> 
> I'm not entirely sure what you are describing here, can you describe
> what you do see vs. what you expected to see?
> 
> Did you expect to see eth1 in guest1? or did you expect to see eth0?
> 
> What does guest1's vif configuration line look like?
> 
> If you expected eth0 then you might have an issue with the udev
> persistent net rules, look under /etc/udev/rules.d for things which
> might be renaming eth0->eth1 on boot.
> 
> If you expected eth1 then obviously you need to have eth1 in the
> guest's /etc/network/interfaces if you want to use it.
> 
> > issueing xm list shows guest1 as running but guest2 shows a b for blocked but it is running 
> > and I can use it.
> 
> blocked just means the guest is idle (i.e. it is blocked in the
> hypervisor). It is still available to run if something happens. On a
> mostly idle system most guests will be blocked...
> 
> > Big question is how do I get these two guests to autostart if the server is rebooted?
> 
> The xendomains initscript can do this for you. IIRC you just need to put
> the config files in /etc/xen/auto instead of /etc/xen.
> 
> Ian.
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
> 



Bill Beauchemin
B2 Bass Adventures
Newark, Ca. 94560
(510) 552-7571


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 19:11:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 19:11:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScLc1-0004O1-Nm; Wed, 06 Jun 2012 19:09:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScLc0-0004Nq-BU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 19:09:44 +0000
Received: from [85.158.143.99:5520] by server-3.bemta-4.messagelabs.com id
	10/59-29237-7FAAFCF4; Wed, 06 Jun 2012 19:09:43 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-14.tower-216.messagelabs.com!1339009781!21978467!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31355 invoked from network); 6 Jun 2012 19:09:42 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 19:09:42 -0000
Received: by obbwd20 with SMTP id wd20so14311661obb.32
	for ; Wed, 06 Jun 2012 12:09:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=muZRzCr6xQDiJZKOI2XnH9c0x1tZsSGkdrQT5hne09w=;
	b=C6eSfK6rvqn3XBgIIkit6YZX8rwJj41BYcct4+XWfieVy15YujMvU4Sz7JYMG1sKFL
	2ncc1sHcBcrW3dhlO9vU308nsZn1y2JFs49+FPkC81rX7Umwpe8EUz/j7p7bAUCLyReM
	yB3GLoOVOPsNUFbCdoQrIvDGH4Rkr2VZ9/kJ2mKegyBnXO2nnlaZHnah4EYEcJAJKTTs
	oOU30Nu+Syl3rWehksDascATAz8HwJLmeehR+vUC6xlKa+gb1+7F4/kwFgGPF8IYgWWV
	HaCaDBu5dPyQQo1NNafDp41LsPJEdbPjbSbRy4db7p7Se85qMgiC+PsYND0mYgqGnHov
	H/OQ==
Received: by 10.182.112.102 with SMTP id ip6mr21683883obb.39.1339009761761;
	Wed, 06 Jun 2012 12:09:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Wed, 6 Jun 2012 12:09:01 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: <4FCF78BD.3040909@xen.org>
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
From: Rolu 
Date: Wed, 6 Jun 2012 21:09:01 +0200
Message-ID: 
To: lars.kurth@xen.org
X-Gm-Message-State: ALoCoQn82mxvMJmQPNJBRPgmmVkjnd36Lnz1UDvqoAxNGJT+QBRGoPM9V6UyfmCn3VzsIlf9/428
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	Ian Jackson ,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, Jun 6, 2012 at 5:35 PM, Lars Kurth  wrote:
> On 01/06/2012 18:54, Ian Jackson wrote:
>>
>> Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki
>> Front-Page - need input/mods/creative proposals"):
>>>
>>> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case
>>> focussed
>>> front-page
>>
>> This one is already much better than the existing front page. =A0I have
>> made some more changes.
>
> Great!
>

I agree it's much better. Since the main categories are "help with
xen" and "help with xcp" it would be nice if there were a few lines at
the top of the page explaining which is which, so (new) people can
have a better idea of where to look. The descriptions from
http://xen.org/products/ and a link to
http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
The latter is already linked in the "getting started with xen" column
but would be better off at the top since it gives a feature table of
both.

>> The links under "Xen Docs" are rather poor. =A0I don't know what pages
>> we have that would do better, but the top link being the Wiki category
>> listing is quite unhelpful.
>
> Would a ...
> 1) link to http://wiki.xen.org/wiki/Xen_4.x_Manuals instead of
> http://wiki.xen.org/wiki/Category:Manual be better?
> 2) We could move http://wiki.xen.org/wiki/Xen_Beginners_Guide one up - it=
 is
> a step-by-step tutorial to set up Xen 4 with Squeeze
>
> Part of the problem is that there is a lot of stuff and it is hard to cho=
ose
> what is relevant
>

As someone who started with Xen not long ago, I much prefer dedicated
link pages over Category: pages. The latter just give a big unsorted
(alphabetical doesn't count, needs to be sorted by subtopic to be a
useful sort) list of pages of widely varying scope and usefulness.
It's better than nothing, sure, but a page that sorts them by topic or
purpose or something (much like this proposed front page really) is a
lot better.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 19:11:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 19:11:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScLc1-0004O1-Nm; Wed, 06 Jun 2012 19:09:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScLc0-0004Nq-BU
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 19:09:44 +0000
Received: from [85.158.143.99:5520] by server-3.bemta-4.messagelabs.com id
	10/59-29237-7FAAFCF4; Wed, 06 Jun 2012 19:09:43 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-14.tower-216.messagelabs.com!1339009781!21978467!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31355 invoked from network); 6 Jun 2012 19:09:42 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 19:09:42 -0000
Received: by obbwd20 with SMTP id wd20so14311661obb.32
	for ; Wed, 06 Jun 2012 12:09:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=muZRzCr6xQDiJZKOI2XnH9c0x1tZsSGkdrQT5hne09w=;
	b=C6eSfK6rvqn3XBgIIkit6YZX8rwJj41BYcct4+XWfieVy15YujMvU4Sz7JYMG1sKFL
	2ncc1sHcBcrW3dhlO9vU308nsZn1y2JFs49+FPkC81rX7Umwpe8EUz/j7p7bAUCLyReM
	yB3GLoOVOPsNUFbCdoQrIvDGH4Rkr2VZ9/kJ2mKegyBnXO2nnlaZHnah4EYEcJAJKTTs
	oOU30Nu+Syl3rWehksDascATAz8HwJLmeehR+vUC6xlKa+gb1+7F4/kwFgGPF8IYgWWV
	HaCaDBu5dPyQQo1NNafDp41LsPJEdbPjbSbRy4db7p7Se85qMgiC+PsYND0mYgqGnHov
	H/OQ==
Received: by 10.182.112.102 with SMTP id ip6mr21683883obb.39.1339009761761;
	Wed, 06 Jun 2012 12:09:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Wed, 6 Jun 2012 12:09:01 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: <4FCF78BD.3040909@xen.org>
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
From: Rolu 
Date: Wed, 6 Jun 2012 21:09:01 +0200
Message-ID: 
To: lars.kurth@xen.org
X-Gm-Message-State: ALoCoQn82mxvMJmQPNJBRPgmmVkjnd36Lnz1UDvqoAxNGJT+QBRGoPM9V6UyfmCn3VzsIlf9/428
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	Ian Jackson ,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Wed, Jun 6, 2012 at 5:35 PM, Lars Kurth  wrote:
> On 01/06/2012 18:54, Ian Jackson wrote:
>>
>> Lars Kurth writes ("[Xen-devel] Proposals/changes for a new Wiki
>> Front-Page - need input/mods/creative proposals"):
>>>
>>> - http://wiki.xen.org/wiki/Proposals/Main_Page1 : a more use-case
>>> focussed
>>> front-page
>>
>> This one is already much better than the existing front page. =A0I have
>> made some more changes.
>
> Great!
>

I agree it's much better. Since the main categories are "help with
xen" and "help with xcp" it would be nice if there were a few lines at
the top of the page explaining which is which, so (new) people can
have a better idea of where to look. The descriptions from
http://xen.org/products/ and a link to
http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
The latter is already linked in the "getting started with xen" column
but would be better off at the top since it gives a feature table of
both.

>> The links under "Xen Docs" are rather poor. =A0I don't know what pages
>> we have that would do better, but the top link being the Wiki category
>> listing is quite unhelpful.
>
> Would a ...
> 1) link to http://wiki.xen.org/wiki/Xen_4.x_Manuals instead of
> http://wiki.xen.org/wiki/Category:Manual be better?
> 2) We could move http://wiki.xen.org/wiki/Xen_Beginners_Guide one up - it=
 is
> a step-by-step tutorial to set up Xen 4 with Squeeze
>
> Part of the problem is that there is a lot of stuff and it is hard to cho=
ose
> what is relevant
>

As someone who started with Xen not long ago, I much prefer dedicated
link pages over Category: pages. The latter just give a big unsorted
(alphabetical doesn't count, needs to be sorted by subtopic to be a
useful sort) list of pages of widely varying scope and usefulness.
It's better than nothing, sure, but a page that sorts them by topic or
purpose or something (much like this proposed front page really) is a
lot better.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 21:52:57 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 21:52:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScO8K-0007Ws-5O; Wed, 06 Jun 2012 21:51:16 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScO8I-0007Wk-Ek
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 21:51:14 +0000
Received: from [193.109.254.147:57067] by server-3.bemta-14.messagelabs.com id
	DD/66-05653-1D0DFCF4; Wed, 06 Jun 2012 21:51:13 +0000
X-Env-Sender: Edison.su@citrix.com
X-Msg-Ref: server-7.tower-27.messagelabs.com!1339019471!5451359!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxNDkyNTI=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26053 invoked from network); 6 Jun 2012 21:51:12 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 21:51:12 -0000
X-IronPort-AV: E=Sophos;i="4.75,726,1330923600"; d="scan'208";a="27121164"
Received: from sjcpmailmx01.citrite.net ([10.216.14.74])
	by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 17:51:11 -0400
Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by
	SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi;
	Wed, 6 Jun 2012 14:51:10 -0700
From: Edison Su 
To: "'xen-users@lists.xen.org'" 
Date: Wed, 6 Jun 2012 14:51:10 -0700
Thread-Topic: Can't attach an ISO to a PV VM on Ubuntu 12.04 dom0
Thread-Index: Ac1ELnvmb+5dY9FqQlmblCWF81NO+Q==
Message-ID: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: [Xen-users] Can't attach an ISO to a PV VM on Ubuntu 12.04 dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

root@ubuntu:~# xe vbd-param-list uuid=71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0 
uuid ( RO)                        : 71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0
                     vm-uuid ( RO): 246e6121-aa22-17da-a212-ba2b2103f5bf
               vm-name-label ( RO): s-8-VM
                    vdi-uuid ( RO): ef49891a-9774-4d6f-bbbb-31e9a52f4815
              vdi-name-label ( RO): systemvm.iso
          allowed-operations (SRO): pause; unpause; attach; eject; unplug_force; unplug
          current-operations (SRO): 
                       empty ( RO): false
                      device ( RO): xvdd
                  userdevice ( RW): 3
                    bootable ( RW): false
                        mode ( RW): RO
                        type ( RW): CD
                 unpluggable ( RW): true
          currently-attached ( RO): true
                  attachable ( RO): true
                storage-lock ( RO): false
                 status-code ( RO): 0
               status-detail ( RO): 
          qos_algorithm_type ( RW): 
        qos_algorithm_params (MRW): 
    qos_supported_algorithms (SRO): 
                other-config (MRW): 
                 io_read_kbs ( RO): 
                io_write_kbs ( RO): 

root@ubuntu:~# xe vdi-param-list uuid=ef49891a-9774-4d6f-bbbb-31e9a52f4815 
uuid ( RO)                    : ef49891a-9774-4d6f-bbbb-31e9a52f4815
              name-label ( RW): systemvm.iso
        name-description ( RW): 
           is-a-snapshot ( RO): false
             snapshot-of ( RO): 
               snapshots ( RO): 
           snapshot-time ( RO): 19700101T00:00:00Z
      allowed-operations (SRO): clone; snapshot
      current-operations (SRO): 
                 sr-uuid ( RO): 481f1c9d-863c-fcf1-225e-75eec166133e
           sr-name-label ( RO): XenServer Tools
               vbd-uuids (SRO): 71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0
         crashdump-uuids (SRO): 
            virtual-size ( RO): 14280704
    physical-utilisation ( RO): 14280704
                location ( RO): systemvm.iso
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): true
            storage-lock ( RO): false
                 managed ( RO): true
                  parent ( RO): 
                 missing ( RO): false
            other-config (MRW): 
           xenstore-data (MRO): 
               sm-config (MRO): xs-tools: true
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): 
                    tags (SRW):

root@ubuntu:~# xe sr-list uuid=481f1c9d-863c-fcf1-225e-75eec166133e 
uuid ( RO)                : 481f1c9d-863c-fcf1-225e-75eec166133e
          name-label ( RW): XenServer Tools
    name-description ( RW): XenServer Tools ISOs
                host ( RO): ubuntu
                type ( RO): iso
        content-type ( RO): iso

On syslog, I see the following errors:

Jun  6 14:38:55 ubuntu xapi: [20120606T21:38:55.343Z| info|ubuntu|7563 UNIX /var/lib/xcp/xapi|VBD.create R:f4d814ea3dea|audit] ('trackid=bd8429fa72a024f3edc49659f7aa9941' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf') ('VDI' 'systemvm.iso' 'ef49891a-9774-4d6f-bbbb-31e9a52f4815' 'OpaqueRef:a672d623-b8b3-e4f2-d8df-c5caf2d4d381')))
Jun  6 14:38:55 ubuntu udevd[26831]: kernel-provided name 'blktap0' and NAME= 'xen/blktap-2/blktap0' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Jun  6 14:38:55 ubuntu tapdisk[30921]: tapdisk-control: init, 10 x 4k buffers
Jun  6 14:38:55 ubuntu tapdisk[30921]: I/O queue driver: lio
Jun  6 14:38:55 ubuntu tapdisk[30921]: tapdisk-log: started, level 0
Jun  6 14:38:55 ubuntu tapdisk[30921]: received 'attach' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: sending 'attach response' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: received 'open' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: block-aio open('/usr/share/xcp/packages/iso/systemvm.iso')
Jun  6 14:38:55 ubuntu tapdisk[30921]: open(/usr/share/xcp/packages/iso/systemvm.iso) with O_DIRECT
Jun  6 14:38:55 ubuntu tapdisk[30921]: Image size: #012#011pre sector_shift  [14280704]#012#011post sector_shift [27892]
Jun  6 14:38:55 ubuntu tapdisk[30921]: opened image /usr/share/xcp/packages/iso/systemvm.iso (1 users, state: 0x00000003, type: 0, ro)
Jun  6 14:38:55 ubuntu tapdisk[30921]: VBD CHAIN:
Jun  6 14:38:55 ubuntu tapdisk[30921]: /usr/share/xcp/packages/iso/systemvm.iso: type:aio(0) storage:n/a(-1)
Jun  6 14:38:55 ubuntu tapdisk[30921]: bdev: capacity=27892 sector_size=512/512 flags=0
Jun  6 14:38:55 ubuntu tapdisk[30921]: sending 'open response' message (uuid = 0)
Jun  6 14:38:55 ubuntu kernel: [11434.498009] block tda: sector-size: 512/512+0 capacity: 27892 discard: 0+0 flush: 0x0
Jun  6 14:38:55 ubuntu kernel: [11434.651214] xen-blkback:ring-ref 2351, event-channel 8, protocol 2 (x86_32-abi)
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/8/51760
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: Writing backend/vbd/8/51760/hotplug-error /dev/sm/backend/481f1c9d-863c-fcf1-225e-75eec166133e/ef49891a-9774-4d6f-bbbb-31e9a52f4815 does not exist. backend/vbd/8/51760/hotplug-status error to xenstore.
Jun  6 14:38:55 ubuntu xapi: [20120606T21:38:55.946Z| info|ubuntu|7563 UNIX /var/lib/xcp/xapi|VBD.plug R:395bed0c1b4d|audit] ('trackid=bd8429fa72a024f3edc49659f7aa9941' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.plug' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: /dev/sm/backend/481f1c9d-863c-fcf1-225e-75eec166133e/ef49891a-9774-4d6f-bbbb-31e9a52f4815 does not exist.
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.500Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VBD.assert_attachable R:8c1e29a2c394|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.assert_attachable' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.516Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VM.query_data_source D:91a338ea8c6e|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_read ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.523Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VM.query_data_source D:15a5e5856b64|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_write ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:41:28 ubuntu kernel: [11587.004380] ISO 9660 Extensions: RRIP_1991A
Jun  6 14:45:00 ubuntu xapi: [20120606T21:45:00.997Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VBD.assert_attachable R:a17ba41316d0|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.assert_attachable' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:45:01 ubuntu xapi: [20120606T21:45:01.005Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VM.query_data_source D:98177990f4d3|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_read ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:45:01 ubuntu xapi: [20120606T21:45:01.009Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VM.query_data_source D:769d4729e23a|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_write ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
                                                                                                                                                            56069,1       


Inside guest, I see errors like "XENBUS: Timeout connecting to device: device/vbd/5170(local state 3, remote state 2)" .
Any hint how to debug this issue?


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 21:52:57 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 21:52:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScO8K-0007Ws-5O; Wed, 06 Jun 2012 21:51:16 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScO8I-0007Wk-Ek
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 21:51:14 +0000
Received: from [193.109.254.147:57067] by server-3.bemta-14.messagelabs.com id
	DD/66-05653-1D0DFCF4; Wed, 06 Jun 2012 21:51:13 +0000
X-Env-Sender: Edison.su@citrix.com
X-Msg-Ref: server-7.tower-27.messagelabs.com!1339019471!5451359!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxNDkyNTI=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26053 invoked from network); 6 Jun 2012 21:51:12 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	6 Jun 2012 21:51:12 -0000
X-IronPort-AV: E=Sophos;i="4.75,726,1330923600"; d="scan'208";a="27121164"
Received: from sjcpmailmx01.citrite.net ([10.216.14.74])
	by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	06 Jun 2012 17:51:11 -0400
Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by
	SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi;
	Wed, 6 Jun 2012 14:51:10 -0700
From: Edison Su 
To: "'xen-users@lists.xen.org'" 
Date: Wed, 6 Jun 2012 14:51:10 -0700
Thread-Topic: Can't attach an ISO to a PV VM on Ubuntu 12.04 dom0
Thread-Index: Ac1ELnvmb+5dY9FqQlmblCWF81NO+Q==
Message-ID: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: [Xen-users] Can't attach an ISO to a PV VM on Ubuntu 12.04 dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

root@ubuntu:~# xe vbd-param-list uuid=71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0 
uuid ( RO)                        : 71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0
                     vm-uuid ( RO): 246e6121-aa22-17da-a212-ba2b2103f5bf
               vm-name-label ( RO): s-8-VM
                    vdi-uuid ( RO): ef49891a-9774-4d6f-bbbb-31e9a52f4815
              vdi-name-label ( RO): systemvm.iso
          allowed-operations (SRO): pause; unpause; attach; eject; unplug_force; unplug
          current-operations (SRO): 
                       empty ( RO): false
                      device ( RO): xvdd
                  userdevice ( RW): 3
                    bootable ( RW): false
                        mode ( RW): RO
                        type ( RW): CD
                 unpluggable ( RW): true
          currently-attached ( RO): true
                  attachable ( RO): true
                storage-lock ( RO): false
                 status-code ( RO): 0
               status-detail ( RO): 
          qos_algorithm_type ( RW): 
        qos_algorithm_params (MRW): 
    qos_supported_algorithms (SRO): 
                other-config (MRW): 
                 io_read_kbs ( RO): 
                io_write_kbs ( RO): 

root@ubuntu:~# xe vdi-param-list uuid=ef49891a-9774-4d6f-bbbb-31e9a52f4815 
uuid ( RO)                    : ef49891a-9774-4d6f-bbbb-31e9a52f4815
              name-label ( RW): systemvm.iso
        name-description ( RW): 
           is-a-snapshot ( RO): false
             snapshot-of ( RO): 
               snapshots ( RO): 
           snapshot-time ( RO): 19700101T00:00:00Z
      allowed-operations (SRO): clone; snapshot
      current-operations (SRO): 
                 sr-uuid ( RO): 481f1c9d-863c-fcf1-225e-75eec166133e
           sr-name-label ( RO): XenServer Tools
               vbd-uuids (SRO): 71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0
         crashdump-uuids (SRO): 
            virtual-size ( RO): 14280704
    physical-utilisation ( RO): 14280704
                location ( RO): systemvm.iso
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): true
            storage-lock ( RO): false
                 managed ( RO): true
                  parent ( RO): 
                 missing ( RO): false
            other-config (MRW): 
           xenstore-data (MRO): 
               sm-config (MRO): xs-tools: true
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): 
                    tags (SRW):

root@ubuntu:~# xe sr-list uuid=481f1c9d-863c-fcf1-225e-75eec166133e 
uuid ( RO)                : 481f1c9d-863c-fcf1-225e-75eec166133e
          name-label ( RW): XenServer Tools
    name-description ( RW): XenServer Tools ISOs
                host ( RO): ubuntu
                type ( RO): iso
        content-type ( RO): iso

On syslog, I see the following errors:

Jun  6 14:38:55 ubuntu xapi: [20120606T21:38:55.343Z| info|ubuntu|7563 UNIX /var/lib/xcp/xapi|VBD.create R:f4d814ea3dea|audit] ('trackid=bd8429fa72a024f3edc49659f7aa9941' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf') ('VDI' 'systemvm.iso' 'ef49891a-9774-4d6f-bbbb-31e9a52f4815' 'OpaqueRef:a672d623-b8b3-e4f2-d8df-c5caf2d4d381')))
Jun  6 14:38:55 ubuntu udevd[26831]: kernel-provided name 'blktap0' and NAME= 'xen/blktap-2/blktap0' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Jun  6 14:38:55 ubuntu tapdisk[30921]: tapdisk-control: init, 10 x 4k buffers
Jun  6 14:38:55 ubuntu tapdisk[30921]: I/O queue driver: lio
Jun  6 14:38:55 ubuntu tapdisk[30921]: tapdisk-log: started, level 0
Jun  6 14:38:55 ubuntu tapdisk[30921]: received 'attach' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: sending 'attach response' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: received 'open' message (uuid = 0)
Jun  6 14:38:55 ubuntu tapdisk[30921]: block-aio open('/usr/share/xcp/packages/iso/systemvm.iso')
Jun  6 14:38:55 ubuntu tapdisk[30921]: open(/usr/share/xcp/packages/iso/systemvm.iso) with O_DIRECT
Jun  6 14:38:55 ubuntu tapdisk[30921]: Image size: #012#011pre sector_shift  [14280704]#012#011post sector_shift [27892]
Jun  6 14:38:55 ubuntu tapdisk[30921]: opened image /usr/share/xcp/packages/iso/systemvm.iso (1 users, state: 0x00000003, type: 0, ro)
Jun  6 14:38:55 ubuntu tapdisk[30921]: VBD CHAIN:
Jun  6 14:38:55 ubuntu tapdisk[30921]: /usr/share/xcp/packages/iso/systemvm.iso: type:aio(0) storage:n/a(-1)
Jun  6 14:38:55 ubuntu tapdisk[30921]: bdev: capacity=27892 sector_size=512/512 flags=0
Jun  6 14:38:55 ubuntu tapdisk[30921]: sending 'open response' message (uuid = 0)
Jun  6 14:38:55 ubuntu kernel: [11434.498009] block tda: sector-size: 512/512+0 capacity: 27892 discard: 0+0 flush: 0x0
Jun  6 14:38:55 ubuntu kernel: [11434.651214] xen-blkback:ring-ref 2351, event-channel 8, protocol 2 (x86_32-abi)
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/8/51760
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: Writing backend/vbd/8/51760/hotplug-error /dev/sm/backend/481f1c9d-863c-fcf1-225e-75eec166133e/ef49891a-9774-4d6f-bbbb-31e9a52f4815 does not exist. backend/vbd/8/51760/hotplug-status error to xenstore.
Jun  6 14:38:55 ubuntu xapi: [20120606T21:38:55.946Z| info|ubuntu|7563 UNIX /var/lib/xcp/xapi|VBD.plug R:395bed0c1b4d|audit] ('trackid=bd8429fa72a024f3edc49659f7aa9941' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.plug' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:38:55 ubuntu logger: /etc/xen/scripts/block: /dev/sm/backend/481f1c9d-863c-fcf1-225e-75eec166133e/ef49891a-9774-4d6f-bbbb-31e9a52f4815 does not exist.
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.500Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VBD.assert_attachable R:8c1e29a2c394|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.assert_attachable' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.516Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VM.query_data_source D:91a338ea8c6e|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_read ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:39:42 ubuntu xapi: [20120606T21:39:42.523Z| info|ubuntu|7602 UNIX /var/lib/xcp/xapi|VM.query_data_source D:15a5e5856b64|audit] ('trackid=b0d2942c096fec716132a3bbed0d8bf6' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_write ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:41:28 ubuntu kernel: [11587.004380] ISO 9660 Extensions: RRIP_1991A
Jun  6 14:45:00 ubuntu xapi: [20120606T21:45:00.997Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VBD.assert_attachable R:a17ba41316d0|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.assert_attachable' (('self' '' '71a80e20-2cea-9bcb-0c72-d6e39bb4c5c0' 'OpaqueRef:b8c902b1-e003-b2a9-6811-5e3463502e93')))
Jun  6 14:45:01 ubuntu xapi: [20120606T21:45:01.005Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VM.query_data_source D:98177990f4d3|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_read ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
Jun  6 14:45:01 ubuntu xapi: [20120606T21:45:01.009Z| info|ubuntu|7616 UNIX /var/lib/xcp/xapi|VM.query_data_source D:769d4729e23a|audit] ('trackid=6136dfb0c82ceaeb530a37c02df18655' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:INVALID_VALUE: [ data-source; vbd_xvdd_write ]' 'API' 'VM.query_data_source' (('self' 's-8-VM' '246e6121-aa22-17da-a212-ba2b2103f5bf' 'OpaqueRef:ecf9d238-7bc4-309d-17fb-c9cddcf41bdf')))
                                                                                                                                                            56069,1       


Inside guest, I see errors like "XENBUS: Timeout connecting to device: device/vbd/5170(local state 3, remote state 2)" .
Any hint how to debug this issue?


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Wed Jun 06 22:03:52 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 22:03: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 1ScOJA-0007zD-0q; Wed, 06 Jun 2012 22:02:28 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScOJ8-0007z8-Es
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 22:02:26 +0000
Received: from [85.158.138.51:65053] by server-5.bemta-3.messagelabs.com id
	25/AE-03598-173DFCF4; Wed, 06 Jun 2012 22:02:25 +0000
X-Env-Sender: gerard@beekmansworld.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1339020144!31166985!1
X-Originating-IP: [216.171.237.234]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1247 invoked from network); 6 Jun 2012 22:02:24 -0000
Received: from quantum.linuxfromscratch.org (HELO
	quantum.linuxfromscratch.org) (216.171.237.234)
	by server-2.tower-174.messagelabs.com with SMTP;
	6 Jun 2012 22:02:24 -0000
Received: by quantum.linuxfromscratch.org (Postfix, from userid 108)
	id 61B961402B; Wed,  6 Jun 2012 16:00:53 -0600 (MDT)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on 
	quantum.linuxfromscratch.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=ALL_TRUSTED,HTML_10_20,
	HTML_MESSAGE autolearn=disabled version=3.1.7
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com
	[209.85.214.173])
	by quantum.linuxfromscratch.org (Postfix) with ESMTPA id 0A44F14026
	for ; Wed,  6 Jun 2012 16:00:46 -0600 (MDT)
Received: by obbwd20 with SMTP id wd20so14560291obb.32
	for ; Wed, 06 Jun 2012 15:02:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.8.99 with SMTP id q3mr21952187oba.63.1339020136645; Wed,
	06 Jun 2012 15:02:16 -0700 (PDT)
Received: by 10.182.50.97 with HTTP; Wed, 6 Jun 2012 15:02:16 -0700 (PDT)
Date: Wed, 6 Jun 2012 17:02:16 -0500
Message-ID: 
From: Gerard Beekmans 
To: xen-users@lists.xen.org
Subject: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5491590232756641752=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5491590232756641752==
Content-Type: multipart/alternative; boundary=f46d0444ed5997850804c1d4ebb1

--f46d0444ed5997850804c1d4ebb1
Content-Type: text/plain; charset=ISO-8859-1

Hi guys,

I've been experiencing intermittent network problems. I can't be sure if
they are caused by Xen or if using Xen simply aggravates an existing
problem (ie: hardware, driver, software bug, etc) but I thought I'd run it
by you guys in hopes of getting some ideas.

I've narrowed down the problem to be related to the named daemon from
bind9. This may not exclusively be a "named" problem. Other daemons could
be affected but I don't have any others installed yet.

The symptoms are as follows: extremely slow network with a lot of dropped
packets. I can't actually test the machine locally without having to go
over the network because the server is remote from me. Based on the load
averages alone, it appears it's otherwise responsive. Pings to local IP
addresses aren't dropped. Only when the traffic has to leave the physical
machine.

Shutting down named makes the problem go away. Sometimes I can run it for a
few hours or a day before it starts acting up. Once it acts up like this
the only way I can run named again is by rebooting the physical machine
(dom0) and restart the domUs.

Pertinent system info:

Dom0 and DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried
older kernel versions as well with the same issues.
NIC: Intel Gigabit, using the e1000 driver

Network setup is NAT (per requirements of the hosting company I'm with.
Routed or bridged isn't an option for the domUs to have Internet access).

I'm focussing my troubleshooting around named and trying to figure out
exactly what it's doing that triggers this network problem. Do any of you
have suggestions, ideas or a fix if this is a known problem?

If you need additional information, please let me know.

Thanks,

-- 
Gerard Beekmans

--f46d0444ed5997850804c1d4ebb1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi guys,

I've been experiencing intermittent network=
 problems. I can't be sure if they are caused by Xen or if using Xen si=
mply=A0aggravates an existing problem (ie: hardware, driver, software bug, =
etc) but I thought I'd run it by you guys in hopes of getting some idea=
s.



I've narrowed down the problem to be related to the=
 named daemon from bind9. This may not exclusively be a "named" p=
roblem. Other daemons could be affected but I don't have any others ins=
talled yet.



The symptoms are as follows: extremely slow network wit=
h a lot of dropped packets. I can't actually test the machine locally w=
ithout having to go over the network because the server is remote from me. =
Based on the load averages alone, it appears it's otherwise responsive.=
 Pings to local IP addresses aren't dropped. Only when the traffic has =
to leave the physical machine.



Shutting down named makes the problem go away. Sometime=
s I can run it for a few hours or a day before it starts acting up. Once it=
 acts up like this the only way I can run named again is by rebooting the p=
hysical machine (dom0) and restart the domUs.



Pertinent system info:

Dom0 an=
d DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried older kern=
el versions as well with the same issues.
NIC: Intel Gigabit, usi=
ng the e1000 driver



Network setup is NAT (per requirements of the hosting c=
ompany I'm with. Routed or bridged isn't an option for the domUs to=
 have Internet access).

I'm focussing my troub=
leshooting around named and trying to figure out exactly what it's doin=
g that triggers this network problem. Do any of you have suggestions, ideas=
 or a fix if this is a known problem?



If you need additional information, please let me know.=


Thanks,

-- 
Gerard Beekmans








--f46d0444ed5997850804c1d4ebb1--


--===============5491590232756641752==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5491590232756641752==--


From xen-users-bounces@lists.xen.org Wed Jun 06 22:03:52 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 22:03: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 1ScOJA-0007zD-0q; Wed, 06 Jun 2012 22:02:28 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScOJ8-0007z8-Es
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 22:02:26 +0000
Received: from [85.158.138.51:65053] by server-5.bemta-3.messagelabs.com id
	25/AE-03598-173DFCF4; Wed, 06 Jun 2012 22:02:25 +0000
X-Env-Sender: gerard@beekmansworld.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1339020144!31166985!1
X-Originating-IP: [216.171.237.234]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1247 invoked from network); 6 Jun 2012 22:02:24 -0000
Received: from quantum.linuxfromscratch.org (HELO
	quantum.linuxfromscratch.org) (216.171.237.234)
	by server-2.tower-174.messagelabs.com with SMTP;
	6 Jun 2012 22:02:24 -0000
Received: by quantum.linuxfromscratch.org (Postfix, from userid 108)
	id 61B961402B; Wed,  6 Jun 2012 16:00:53 -0600 (MDT)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on 
	quantum.linuxfromscratch.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=ALL_TRUSTED,HTML_10_20,
	HTML_MESSAGE autolearn=disabled version=3.1.7
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com
	[209.85.214.173])
	by quantum.linuxfromscratch.org (Postfix) with ESMTPA id 0A44F14026
	for ; Wed,  6 Jun 2012 16:00:46 -0600 (MDT)
Received: by obbwd20 with SMTP id wd20so14560291obb.32
	for ; Wed, 06 Jun 2012 15:02:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.8.99 with SMTP id q3mr21952187oba.63.1339020136645; Wed,
	06 Jun 2012 15:02:16 -0700 (PDT)
Received: by 10.182.50.97 with HTTP; Wed, 6 Jun 2012 15:02:16 -0700 (PDT)
Date: Wed, 6 Jun 2012 17:02:16 -0500
Message-ID: 
From: Gerard Beekmans 
To: xen-users@lists.xen.org
Subject: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5491590232756641752=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5491590232756641752==
Content-Type: multipart/alternative; boundary=f46d0444ed5997850804c1d4ebb1

--f46d0444ed5997850804c1d4ebb1
Content-Type: text/plain; charset=ISO-8859-1

Hi guys,

I've been experiencing intermittent network problems. I can't be sure if
they are caused by Xen or if using Xen simply aggravates an existing
problem (ie: hardware, driver, software bug, etc) but I thought I'd run it
by you guys in hopes of getting some ideas.

I've narrowed down the problem to be related to the named daemon from
bind9. This may not exclusively be a "named" problem. Other daemons could
be affected but I don't have any others installed yet.

The symptoms are as follows: extremely slow network with a lot of dropped
packets. I can't actually test the machine locally without having to go
over the network because the server is remote from me. Based on the load
averages alone, it appears it's otherwise responsive. Pings to local IP
addresses aren't dropped. Only when the traffic has to leave the physical
machine.

Shutting down named makes the problem go away. Sometimes I can run it for a
few hours or a day before it starts acting up. Once it acts up like this
the only way I can run named again is by rebooting the physical machine
(dom0) and restart the domUs.

Pertinent system info:

Dom0 and DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried
older kernel versions as well with the same issues.
NIC: Intel Gigabit, using the e1000 driver

Network setup is NAT (per requirements of the hosting company I'm with.
Routed or bridged isn't an option for the domUs to have Internet access).

I'm focussing my troubleshooting around named and trying to figure out
exactly what it's doing that triggers this network problem. Do any of you
have suggestions, ideas or a fix if this is a known problem?

If you need additional information, please let me know.

Thanks,

-- 
Gerard Beekmans

--f46d0444ed5997850804c1d4ebb1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi guys,

I've been experiencing intermittent network=
 problems. I can't be sure if they are caused by Xen or if using Xen si=
mply=A0aggravates an existing problem (ie: hardware, driver, software bug, =
etc) but I thought I'd run it by you guys in hopes of getting some idea=
s.



I've narrowed down the problem to be related to the=
 named daemon from bind9. This may not exclusively be a "named" p=
roblem. Other daemons could be affected but I don't have any others ins=
talled yet.



The symptoms are as follows: extremely slow network wit=
h a lot of dropped packets. I can't actually test the machine locally w=
ithout having to go over the network because the server is remote from me. =
Based on the load averages alone, it appears it's otherwise responsive.=
 Pings to local IP addresses aren't dropped. Only when the traffic has =
to leave the physical machine.



Shutting down named makes the problem go away. Sometime=
s I can run it for a few hours or a day before it starts acting up. Once it=
 acts up like this the only way I can run named again is by rebooting the p=
hysical machine (dom0) and restart the domUs.



Pertinent system info:

Dom0 an=
d DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried older kern=
el versions as well with the same issues.
NIC: Intel Gigabit, usi=
ng the e1000 driver



Network setup is NAT (per requirements of the hosting c=
ompany I'm with. Routed or bridged isn't an option for the domUs to=
 have Internet access).

I'm focussing my troub=
leshooting around named and trying to figure out exactly what it's doin=
g that triggers this network problem. Do any of you have suggestions, ideas=
 or a fix if this is a known problem?



If you need additional information, please let me know.=


Thanks,

-- 
Gerard Beekmans








--f46d0444ed5997850804c1d4ebb1--


--===============5491590232756641752==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5491590232756641752==--


From xen-users-bounces@lists.xen.org Wed Jun 06 22:35:29 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 22:35: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 1ScOnh-0000Tp-B1; Wed, 06 Jun 2012 22:34:01 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScOnf-0000Tk-92
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 22:33:59 +0000
Received: from [193.109.254.147:17295] by server-5.bemta-14.messagelabs.com id
	9A/E9-31398-6DADFCF4; Wed, 06 Jun 2012 22:33:58 +0000
X-Env-Sender: gerard@beekmansworld.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1339022035!13219342!1
X-Originating-IP: [216.171.237.234]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20293 invoked from network); 6 Jun 2012 22:33:55 -0000
Received: from quantum.linuxfromscratch.org (HELO
	quantum.linuxfromscratch.org) (216.171.237.234)
	by server-3.tower-27.messagelabs.com with SMTP;
	6 Jun 2012 22:33:55 -0000
Received: by quantum.linuxfromscratch.org (Postfix, from userid 108)
	id BAA571402B; Wed,  6 Jun 2012 16:32:23 -0600 (MDT)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on 
	quantum.linuxfromscratch.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE 
	autolearn=disabled version=3.1.7
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com
	[209.85.214.173])
	by quantum.linuxfromscratch.org (Postfix) with ESMTPA id 1D04214024
	for ; Wed,  6 Jun 2012 16:32:16 -0600 (MDT)
Received: by obbwd20 with SMTP id wd20so14606234obb.32
	for ; Wed, 06 Jun 2012 15:33:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.152.4 with SMTP id uu4mr22137690obb.26.1339022026933; Wed,
	06 Jun 2012 15:33:46 -0700 (PDT)
Received: by 10.182.50.97 with HTTP; Wed, 6 Jun 2012 15:33:46 -0700 (PDT)
In-Reply-To: 
References: 
Date: Wed, 6 Jun 2012 17:33:46 -0500
Message-ID: 
From: Gerard Beekmans 
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1239648571188805959=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1239648571188805959==
Content-Type: multipart/alternative; boundary=f46d0444ece543076a04c1d55ca1

--f46d0444ece543076a04c1d55ca1
Content-Type: text/plain; charset=ISO-8859-1

Allow me to reply to my own email. The issue may not have anything to do
with Xen but perhaps only loosely.

The actual problem is a "simple" DoS attack to my IP addresses. The host is
receiving a huge amount of incoming of DNS requests. As soon as this attack
starts and there's a DNS server listening on any of the domUs that happen
to have that IP address the network slows to a crawl to the point the
machine is overloaded and just locks up.

Of note, the NIC link to the switch is set to 10 Mbit Full Duplex (that's
the speed I've signed up for with the hosting plan). Even if that link is
flooded, the maximum incoming data is finite. I wouldn't have expected a
Linux box to keel over and die at such a speed. Perhaps it's related to the
fact the listening service runs in a DomU?

Thanks,
Gerard

On Wed, Jun 6, 2012 at 5:02 PM, Gerard Beekmans wrote:

> Hi guys,
>
> I've been experiencing intermittent network problems. I can't be sure if
> they are caused by Xen or if using Xen simply aggravates an existing
> problem (ie: hardware, driver, software bug, etc) but I thought I'd run it
> by you guys in hopes of getting some ideas.
>
> I've narrowed down the problem to be related to the named daemon from
> bind9. This may not exclusively be a "named" problem. Other daemons could
> be affected but I don't have any others installed yet.
>
> The symptoms are as follows: extremely slow network with a lot of dropped
> packets. I can't actually test the machine locally without having to go
> over the network because the server is remote from me. Based on the load
> averages alone, it appears it's otherwise responsive. Pings to local IP
> addresses aren't dropped. Only when the traffic has to leave the physical
> machine.
>
> Shutting down named makes the problem go away. Sometimes I can run it for
> a few hours or a day before it starts acting up. Once it acts up like this
> the only way I can run named again is by rebooting the physical machine
> (dom0) and restart the domUs.
>
> Pertinent system info:
>
> Dom0 and DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried
> older kernel versions as well with the same issues.
> NIC: Intel Gigabit, using the e1000 driver
>
> Network setup is NAT (per requirements of the hosting company I'm with.
> Routed or bridged isn't an option for the domUs to have Internet access).
>
> I'm focussing my troubleshooting around named and trying to figure out
> exactly what it's doing that triggers this network problem. Do any of you
> have suggestions, ideas or a fix if this is a known problem?
>
> If you need additional information, please let me know.
>
> Thanks,
>
> --
> Gerard Beekmans
>
>
>
>
>


-- 
Gerard Beekmans

--f46d0444ece543076a04c1d55ca1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Allow me to reply to my own email. The issue may not have anything to do wi=
th Xen but perhaps only loosely.

The actual problem is a=
 "simple" DoS attack to my IP addresses. The host is receiving a =
huge amount of incoming of DNS requests. As soon as this attack starts and =
there's a DNS server listening on any of the domUs that happen to have =
that IP address the network slows to a crawl to the point the machine is ov=
erloaded and just locks up.



Of note, the NIC link to the switch is set to 10 Mbit F=
ull Duplex (that's the speed I've signed up for with the hosting pl=
an). Even if that link is flooded, the maximum incoming data is finite. I w=
ouldn't have expected a Linux box to keel over and die at such a speed.=
 Perhaps it's related to the fact the listening service runs in a DomU?=




Thanks,
Gerard

On Wed, Jun 6, 2012 at 5:02 PM, Gerard Beekmans <<=
a href=3D"mailto:gerard@beekmansworld.com" target=3D"_blank">gerard@beekman=
sworld.com> wrote:


Hi guys,

I've been ex=
periencing intermittent network problems. I can't be sure if they are c=
aused by Xen or if using Xen simply=A0aggravates an existing problem (ie: h=
ardware, driver, software bug, etc) but I thought I'd run it by you guy=
s in hopes of getting some ideas.




I've narrowed down the problem to be related to the=
 named daemon from bind9. This may not exclusively be a "named" p=
roblem. Other daemons could be affected but I don't have any others ins=
talled yet.




The symptoms are as follows: extremely slow network wit=
h a lot of dropped packets. I can't actually test the machine locally w=
ithout having to go over the network because the server is remote from me. =
Based on the load averages alone, it appears it's otherwise responsive.=
 Pings to local IP addresses aren't dropped. Only when the traffic has =
to leave the physical machine.




Shutting down named makes the problem go away. Sometime=
s I can run it for a few hours or a day before it starts acting up. Once it=
 acts up like this the only way I can run named again is by rebooting the p=
hysical machine (dom0) and restart the domUs.




Pertinent system info:

Dom0 an=
d DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried older kern=
el versions as well with the same issues.
NIC: Intel Gigabit, usi=
ng the e1000 driver




Network setup is NAT (per requirements of the hosting c=
ompany I'm with. Routed or bridged isn't an option for the domUs to=
 have Internet access).

I'm focussing my troub=
leshooting around named and trying to figure out exactly what it's doin=
g that triggers this network problem. Do any of you have suggestions, ideas=
 or a fix if this is a known problem?




If you need additional information, please let me know.=


Thanks,

-- 
Gerard Beekmans












-- 
Gerard =
Beekmans






--f46d0444ece543076a04c1d55ca1--


--===============1239648571188805959==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1239648571188805959==--


From xen-users-bounces@lists.xen.org Wed Jun 06 22:35:29 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 06 Jun 2012 22:35: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 1ScOnh-0000Tp-B1; Wed, 06 Jun 2012 22:34:01 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScOnf-0000Tk-92
	for xen-users@lists.xen.org; Wed, 06 Jun 2012 22:33:59 +0000
Received: from [193.109.254.147:17295] by server-5.bemta-14.messagelabs.com id
	9A/E9-31398-6DADFCF4; Wed, 06 Jun 2012 22:33:58 +0000
X-Env-Sender: gerard@beekmansworld.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1339022035!13219342!1
X-Originating-IP: [216.171.237.234]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20293 invoked from network); 6 Jun 2012 22:33:55 -0000
Received: from quantum.linuxfromscratch.org (HELO
	quantum.linuxfromscratch.org) (216.171.237.234)
	by server-3.tower-27.messagelabs.com with SMTP;
	6 Jun 2012 22:33:55 -0000
Received: by quantum.linuxfromscratch.org (Postfix, from userid 108)
	id BAA571402B; Wed,  6 Jun 2012 16:32:23 -0600 (MDT)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on 
	quantum.linuxfromscratch.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE 
	autolearn=disabled version=3.1.7
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com
	[209.85.214.173])
	by quantum.linuxfromscratch.org (Postfix) with ESMTPA id 1D04214024
	for ; Wed,  6 Jun 2012 16:32:16 -0600 (MDT)
Received: by obbwd20 with SMTP id wd20so14606234obb.32
	for ; Wed, 06 Jun 2012 15:33:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.152.4 with SMTP id uu4mr22137690obb.26.1339022026933; Wed,
	06 Jun 2012 15:33:46 -0700 (PDT)
Received: by 10.182.50.97 with HTTP; Wed, 6 Jun 2012 15:33:46 -0700 (PDT)
In-Reply-To: 
References: 
Date: Wed, 6 Jun 2012 17:33:46 -0500
Message-ID: 
From: Gerard Beekmans 
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1239648571188805959=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1239648571188805959==
Content-Type: multipart/alternative; boundary=f46d0444ece543076a04c1d55ca1

--f46d0444ece543076a04c1d55ca1
Content-Type: text/plain; charset=ISO-8859-1

Allow me to reply to my own email. The issue may not have anything to do
with Xen but perhaps only loosely.

The actual problem is a "simple" DoS attack to my IP addresses. The host is
receiving a huge amount of incoming of DNS requests. As soon as this attack
starts and there's a DNS server listening on any of the domUs that happen
to have that IP address the network slows to a crawl to the point the
machine is overloaded and just locks up.

Of note, the NIC link to the switch is set to 10 Mbit Full Duplex (that's
the speed I've signed up for with the hosting plan). Even if that link is
flooded, the maximum incoming data is finite. I wouldn't have expected a
Linux box to keel over and die at such a speed. Perhaps it's related to the
fact the listening service runs in a DomU?

Thanks,
Gerard

On Wed, Jun 6, 2012 at 5:02 PM, Gerard Beekmans wrote:

> Hi guys,
>
> I've been experiencing intermittent network problems. I can't be sure if
> they are caused by Xen or if using Xen simply aggravates an existing
> problem (ie: hardware, driver, software bug, etc) but I thought I'd run it
> by you guys in hopes of getting some ideas.
>
> I've narrowed down the problem to be related to the named daemon from
> bind9. This may not exclusively be a "named" problem. Other daemons could
> be affected but I don't have any others installed yet.
>
> The symptoms are as follows: extremely slow network with a lot of dropped
> packets. I can't actually test the machine locally without having to go
> over the network because the server is remote from me. Based on the load
> averages alone, it appears it's otherwise responsive. Pings to local IP
> addresses aren't dropped. Only when the traffic has to leave the physical
> machine.
>
> Shutting down named makes the problem go away. Sometimes I can run it for
> a few hours or a day before it starts acting up. Once it acts up like this
> the only way I can run named again is by rebooting the physical machine
> (dom0) and restart the domUs.
>
> Pertinent system info:
>
> Dom0 and DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried
> older kernel versions as well with the same issues.
> NIC: Intel Gigabit, using the e1000 driver
>
> Network setup is NAT (per requirements of the hosting company I'm with.
> Routed or bridged isn't an option for the domUs to have Internet access).
>
> I'm focussing my troubleshooting around named and trying to figure out
> exactly what it's doing that triggers this network problem. Do any of you
> have suggestions, ideas or a fix if this is a known problem?
>
> If you need additional information, please let me know.
>
> Thanks,
>
> --
> Gerard Beekmans
>
>
>
>
>


-- 
Gerard Beekmans

--f46d0444ece543076a04c1d55ca1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Allow me to reply to my own email. The issue may not have anything to do wi=
th Xen but perhaps only loosely.

The actual problem is a=
 "simple" DoS attack to my IP addresses. The host is receiving a =
huge amount of incoming of DNS requests. As soon as this attack starts and =
there's a DNS server listening on any of the domUs that happen to have =
that IP address the network slows to a crawl to the point the machine is ov=
erloaded and just locks up.



Of note, the NIC link to the switch is set to 10 Mbit F=
ull Duplex (that's the speed I've signed up for with the hosting pl=
an). Even if that link is flooded, the maximum incoming data is finite. I w=
ouldn't have expected a Linux box to keel over and die at such a speed.=
 Perhaps it's related to the fact the listening service runs in a DomU?=




Thanks,
Gerard

On Wed, Jun 6, 2012 at 5:02 PM, Gerard Beekmans <<=
a href=3D"mailto:gerard@beekmansworld.com" target=3D"_blank">gerard@beekman=
sworld.com> wrote:


Hi guys,

I've been ex=
periencing intermittent network problems. I can't be sure if they are c=
aused by Xen or if using Xen simply=A0aggravates an existing problem (ie: h=
ardware, driver, software bug, etc) but I thought I'd run it by you guy=
s in hopes of getting some ideas.




I've narrowed down the problem to be related to the=
 named daemon from bind9. This may not exclusively be a "named" p=
roblem. Other daemons could be affected but I don't have any others ins=
talled yet.




The symptoms are as follows: extremely slow network wit=
h a lot of dropped packets. I can't actually test the machine locally w=
ithout having to go over the network because the server is remote from me. =
Based on the load averages alone, it appears it's otherwise responsive.=
 Pings to local IP addresses aren't dropped. Only when the traffic has =
to leave the physical machine.




Shutting down named makes the problem go away. Sometime=
s I can run it for a few hours or a day before it starts acting up. Once it=
 acts up like this the only way I can run named again is by rebooting the p=
hysical machine (dom0) and restart the domUs.




Pertinent system info:

Dom0 an=
d DomUs all running Ubuntu Oneiric with kernel 3.0.0-20. I tried older kern=
el versions as well with the same issues.
NIC: Intel Gigabit, usi=
ng the e1000 driver




Network setup is NAT (per requirements of the hosting c=
ompany I'm with. Routed or bridged isn't an option for the domUs to=
 have Internet access).

I'm focussing my troub=
leshooting around named and trying to figure out exactly what it's doin=
g that triggers this network problem. Do any of you have suggestions, ideas=
 or a fix if this is a known problem?




If you need additional information, please let me know.=


Thanks,

-- 
Gerard Beekmans












-- 
Gerard =
Beekmans






--f46d0444ece543076a04c1d55ca1--


--===============1239648571188805959==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1239648571188805959==--


From xen-users-bounces@lists.xen.org Thu Jun 07 07:19:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 07:19: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 1ScWym-0001mi-2G; Thu, 07 Jun 2012 07:18:00 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScWyj-0001md-FT
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 07:17:57 +0000
Received: from [193.109.254.147:15876] by server-6.bemta-14.messagelabs.com id
	80/2F-02426-4A550DF4; Thu, 07 Jun 2012 07:17:56 +0000
X-Env-Sender: linux@thehobsons.co.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1339053475!1650969!1
X-Originating-IP: [81.174.135.208]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17974 invoked from network); 7 Jun 2012 07:17:56 -0000
Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk)
	(81.174.135.208) by server-14.tower-27.messagelabs.com with SMTP;
	7 Jun 2012 07:17:56 -0000
Received: from localhost (localhost [127.0.0.1])
	by patsy.thehobsons.co.uk (Postfix) with ESMTP id 3496210401B
	for ; Thu,  7 Jun 2012 08:17:52 +0100 (BST)
Received: from patsy.thehobsons.co.uk ([127.0.0.1])
	by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id kdAWx4dLAG8w for ;
	Thu,  7 Jun 2012 08:17:52 +0100 (BST)
Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk
	[192.168.0.202])
	by patsy.thehobsons.co.uk (Postfix) with ESMTP id 79CE310401A
	for ; Thu,  7 Jun 2012 08:17:51 +0100 (BST)
Mime-Version: 1.0
Message-Id: 
In-Reply-To: 
References: 
	
Date: Thu, 7 Jun 2012 08:17:27 +0100
To: xen-users@lists.xen.org
From: Simon Hobson 
Subject: Re: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Gerard Beekmans wrote:

>The actual problem is a "simple" DoS attack to my IP addresses. The 
>host is receiving a huge amount of incoming of DNS requests. As soon 
>as this attack starts and there's a DNS server listening on any of 
>the domUs that happen to have that IP address the network slows to a 
>crawl to the point the machine is overloaded and just locks up.
>
>Of note, the NIC link to the switch is set to 10 Mbit Full Duplex 
>(that's the speed I've signed up for with the hosting plan). Even if 
>that link is flooded, the maximum incoming data is finite. I 
>wouldn't have expected a Linux box to keel over and die at such a 
>speed. Perhaps it's related to the fact the listening service runs 
>in a DomU?

Don't forget that if your pipe is being filled, the device(s) at the 
other end of it will "become unresponsive" as you'll get lots of 
dropped packets. You've said yourself that while this is going on, 
internal communications seems OK.

It could just be that you are getting enough traffic that the DNS 
replies (typically larger than the queries) will fill the pipe. Once 
that happens, packets will be dropped. TCP will cope with dropped 
packets up to a point, but if it's severe, throughput will be 
terrible - responsiveness more so.

I do know exactly what that's like, I've worked remotely on machines 
when they've been under that sort of load - in my case, a users 
website had been compromised and the ***** was using it to attempt 
brute force logins against FTP servers. IIRC it had 1000 threads 
running, all doing brute force username/password guessing against a 
different address ! It's the traffic and the effect it had on the 
network that flagged it up.

In your case, there's ***-all you can do about the attack, other than 
to not run a DNS server on that address until the attacker gets bored 
and moves on. *IF* it's from a small number of addresses then your 
hosting provider may be able to block them upstream, but if it's a 
distributed attack then that isn't practical without blocking large 
chunks of the internet.
You could rate-limit requests with an iptables rule - but you'll 
still be paying (I assume) for the bandwidth consumed by the requests.

If it is a single (or small number of) address(es) then a complaint 
to the owner of the IP block would be in order - they be unaware of 
the malware they are hosting.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 07:19:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 07:19: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 1ScWym-0001mi-2G; Thu, 07 Jun 2012 07:18:00 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScWyj-0001md-FT
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 07:17:57 +0000
Received: from [193.109.254.147:15876] by server-6.bemta-14.messagelabs.com id
	80/2F-02426-4A550DF4; Thu, 07 Jun 2012 07:17:56 +0000
X-Env-Sender: linux@thehobsons.co.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1339053475!1650969!1
X-Originating-IP: [81.174.135.208]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17974 invoked from network); 7 Jun 2012 07:17:56 -0000
Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk)
	(81.174.135.208) by server-14.tower-27.messagelabs.com with SMTP;
	7 Jun 2012 07:17:56 -0000
Received: from localhost (localhost [127.0.0.1])
	by patsy.thehobsons.co.uk (Postfix) with ESMTP id 3496210401B
	for ; Thu,  7 Jun 2012 08:17:52 +0100 (BST)
Received: from patsy.thehobsons.co.uk ([127.0.0.1])
	by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id kdAWx4dLAG8w for ;
	Thu,  7 Jun 2012 08:17:52 +0100 (BST)
Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk
	[192.168.0.202])
	by patsy.thehobsons.co.uk (Postfix) with ESMTP id 79CE310401A
	for ; Thu,  7 Jun 2012 08:17:51 +0100 (BST)
Mime-Version: 1.0
Message-Id: 
In-Reply-To: 
References: 
	
Date: Thu, 7 Jun 2012 08:17:27 +0100
To: xen-users@lists.xen.org
From: Simon Hobson 
Subject: Re: [Xen-users] Suspected network problem after domUs come online
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Gerard Beekmans wrote:

>The actual problem is a "simple" DoS attack to my IP addresses. The 
>host is receiving a huge amount of incoming of DNS requests. As soon 
>as this attack starts and there's a DNS server listening on any of 
>the domUs that happen to have that IP address the network slows to a 
>crawl to the point the machine is overloaded and just locks up.
>
>Of note, the NIC link to the switch is set to 10 Mbit Full Duplex 
>(that's the speed I've signed up for with the hosting plan). Even if 
>that link is flooded, the maximum incoming data is finite. I 
>wouldn't have expected a Linux box to keel over and die at such a 
>speed. Perhaps it's related to the fact the listening service runs 
>in a DomU?

Don't forget that if your pipe is being filled, the device(s) at the 
other end of it will "become unresponsive" as you'll get lots of 
dropped packets. You've said yourself that while this is going on, 
internal communications seems OK.

It could just be that you are getting enough traffic that the DNS 
replies (typically larger than the queries) will fill the pipe. Once 
that happens, packets will be dropped. TCP will cope with dropped 
packets up to a point, but if it's severe, throughput will be 
terrible - responsiveness more so.

I do know exactly what that's like, I've worked remotely on machines 
when they've been under that sort of load - in my case, a users 
website had been compromised and the ***** was using it to attempt 
brute force logins against FTP servers. IIRC it had 1000 threads 
running, all doing brute force username/password guessing against a 
different address ! It's the traffic and the effect it had on the 
network that flagged it up.

In your case, there's ***-all you can do about the attack, other than 
to not run a DNS server on that address until the attacker gets bored 
and moves on. *IF* it's from a small number of addresses then your 
hosting provider may be able to block them upstream, but if it's a 
distributed attack then that isn't practical without blocking large 
chunks of the internet.
You could rate-limit requests with an iptables rule - but you'll 
still be paying (I assume) for the bandwidth consumed by the requests.

If it is a single (or small number of) address(es) then a complaint 
to the owner of the IP block would be in order - they be unaware of 
the malware they are hosting.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:11:18 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:11: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 1ScYin-0005Is-26; Thu, 07 Jun 2012 09:09:37 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYim-0005Ik-FG
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:09:36 +0000
Received: from [85.158.143.35:28823] by server-1.bemta-4.messagelabs.com id
	2C/CE-10042-FCF60DF4; Thu, 07 Jun 2012 09:09:35 +0000
X-Env-Sender: dadawan@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1339060174!11246310!1
X-Originating-IP: [209.85.215.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8778 invoked from network); 7 Jun 2012 09:09:34 -0000
Received: from mail-lpp01m010-f45.google.com (HELO
	mail-lpp01m010-f45.google.com) (209.85.215.45)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:09:34 -0000
Received: by lahc1 with SMTP id c1so333772lah.32
	for ; Thu, 07 Jun 2012 02:09:34 -0700 (PDT)
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
	:content-transfer-encoding;
	bh=hEPtwCF2ZnTmhKWen/DulvG17uz/BD2TCm4oNx3w03E=;
	b=EC24DIREDMXMRMb06zylZaI3J9xU1tnPlCFGRQ6gqXo0vWI/e6QLPIN40fKzGClmNI
	M4fpz7+9CIkTvxIsq/UmagNJYbbMYmdoYlb+2ROE9fbn5TeFb7YlyoMlZ0JTVx1kBMBQ
	W43qzHhsgOlEPetUPRwV0g7XTZmTRvIq8yJXa5wV7X4zsUGGx71unEmbFlTuNCdgV5f8
	TENs/fOuJSYUi/pNVR7w6h7F/fuP4EYQSokAX+9qchcCikSwntcaBSyt90SQ6S9MuTBK
	LeYJDmN7fAYXEfeC2MOclg3dtjwFqLmJXnszc4NfEvh8Uw21uXiGvLtaSg0+MPiWDInq
	/Mjw==
MIME-Version: 1.0
Received: by 10.152.148.1 with SMTP id to1mr1550931lab.34.1339060174209; Thu,
	07 Jun 2012 02:09:34 -0700 (PDT)
Received: by 10.112.42.166 with HTTP; Thu, 7 Jun 2012 02:09:34 -0700 (PDT)
Date: Thu, 7 Jun 2012 05:09:34 -0400
Message-ID: 
From: Kevin Stokes 
To: xen-users@lists.xen.org
Subject: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi I am a first time user of XCP.

I have installed XCP 1.4.90 on a PC. =A0 I am interested in setting up a
cloud where the instances will run node.js to provide websockets for a
hobby project I'm working on.

I installed a Maverick Meerkat 64bit =A0vm and it works but I can't get
it to work with openxenmanager so instead I am trying Debian Squeeze
but vm-start fails with INVALID_SOURCE. (see below)

Thanks for any help,
  -Kevin



[root@xenserver-octopus ~]# xe vm-install template=3DDebian\ Squeeze\
6.0\ \(64-bit\) =A0new-name-label=3DHelloDebian
d541ca58-ffcf-e512-0808-7d6d4f09150d

[root@xenserver-octopus ~]# xe vif-create
network-uuid=3D5ad5dd35-31b0-5510-b050-7c9b362df98b
vm-uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d device=3D0
23d16150-1ff2-3f61-fa4c-35711e374cb9

[root@xenserver-octopus ~]# xe vm-param-set
uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
other-config:install-repository=3Dhttp://ftp.us.debian.org/debian/


[root@xenserver-octopus ~]# xe vm-start
uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
Error code: INVALID_SOURCE
Error parameters: Unable to access a required file in the specified
repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-am=
d64/current/images/netboot/xen/vmlinuz.,
,
[root@xenserver-octopus ~]#

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:11:18 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:11: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 1ScYin-0005Is-26; Thu, 07 Jun 2012 09:09:37 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYim-0005Ik-FG
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:09:36 +0000
Received: from [85.158.143.35:28823] by server-1.bemta-4.messagelabs.com id
	2C/CE-10042-FCF60DF4; Thu, 07 Jun 2012 09:09:35 +0000
X-Env-Sender: dadawan@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1339060174!11246310!1
X-Originating-IP: [209.85.215.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8778 invoked from network); 7 Jun 2012 09:09:34 -0000
Received: from mail-lpp01m010-f45.google.com (HELO
	mail-lpp01m010-f45.google.com) (209.85.215.45)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:09:34 -0000
Received: by lahc1 with SMTP id c1so333772lah.32
	for ; Thu, 07 Jun 2012 02:09:34 -0700 (PDT)
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
	:content-transfer-encoding;
	bh=hEPtwCF2ZnTmhKWen/DulvG17uz/BD2TCm4oNx3w03E=;
	b=EC24DIREDMXMRMb06zylZaI3J9xU1tnPlCFGRQ6gqXo0vWI/e6QLPIN40fKzGClmNI
	M4fpz7+9CIkTvxIsq/UmagNJYbbMYmdoYlb+2ROE9fbn5TeFb7YlyoMlZ0JTVx1kBMBQ
	W43qzHhsgOlEPetUPRwV0g7XTZmTRvIq8yJXa5wV7X4zsUGGx71unEmbFlTuNCdgV5f8
	TENs/fOuJSYUi/pNVR7w6h7F/fuP4EYQSokAX+9qchcCikSwntcaBSyt90SQ6S9MuTBK
	LeYJDmN7fAYXEfeC2MOclg3dtjwFqLmJXnszc4NfEvh8Uw21uXiGvLtaSg0+MPiWDInq
	/Mjw==
MIME-Version: 1.0
Received: by 10.152.148.1 with SMTP id to1mr1550931lab.34.1339060174209; Thu,
	07 Jun 2012 02:09:34 -0700 (PDT)
Received: by 10.112.42.166 with HTTP; Thu, 7 Jun 2012 02:09:34 -0700 (PDT)
Date: Thu, 7 Jun 2012 05:09:34 -0400
Message-ID: 
From: Kevin Stokes 
To: xen-users@lists.xen.org
Subject: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi I am a first time user of XCP.

I have installed XCP 1.4.90 on a PC. =A0 I am interested in setting up a
cloud where the instances will run node.js to provide websockets for a
hobby project I'm working on.

I installed a Maverick Meerkat 64bit =A0vm and it works but I can't get
it to work with openxenmanager so instead I am trying Debian Squeeze
but vm-start fails with INVALID_SOURCE. (see below)

Thanks for any help,
  -Kevin



[root@xenserver-octopus ~]# xe vm-install template=3DDebian\ Squeeze\
6.0\ \(64-bit\) =A0new-name-label=3DHelloDebian
d541ca58-ffcf-e512-0808-7d6d4f09150d

[root@xenserver-octopus ~]# xe vif-create
network-uuid=3D5ad5dd35-31b0-5510-b050-7c9b362df98b
vm-uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d device=3D0
23d16150-1ff2-3f61-fa4c-35711e374cb9

[root@xenserver-octopus ~]# xe vm-param-set
uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
other-config:install-repository=3Dhttp://ftp.us.debian.org/debian/


[root@xenserver-octopus ~]# xe vm-start
uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
Error code: INVALID_SOURCE
Error parameters: Unable to access a required file in the specified
repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-am=
d64/current/images/netboot/xen/vmlinuz.,
,
[root@xenserver-octopus ~]#

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:23:00 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:23: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 1ScYuO-0005fn-H2; Thu, 07 Jun 2012 09:21:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYuN-0005fi-B5
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:21:35 +0000
Received: from [193.109.254.147:41322] by server-1.bemta-14.messagelabs.com id
	96/C3-08067-E9270DF4; Thu, 07 Jun 2012 09:21:34 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-8.tower-27.messagelabs.com!1339060893!8569811!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDE0Nzk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10536 invoked from network); 7 Jun 2012 09:21:34 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:21:34 -0000
X-IronPort-AV: E=Sophos;i="4.75,730,1330905600"; d="scan'208";a="12875968"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	07 Jun 2012 09:21:33 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 7 Jun 2012
	10:21:33 +0100
Message-ID: <1339060892.15265.44.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Xen Xen 
Date: Thu, 7 Jun 2012 10:21:32 +0100
In-Reply-To: 
References: 
	
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

You've posted this three separate times now, please don't do that.

On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:
> Dear everybody!
> 
> I'm a new user of Xen and I encount a problem in my new new job with 2
> Xen Hyper-visor.
> We've 2 HV which access on your NAS by iSCSI to store our VM.
> Or last time we start a VM on one HV without seen that it's was
> started on the other HV. So we encounter some read-only file system
> error...
> I want to avoid this problem. 
> 
> My server run on Debian 6 with Xen 4.0.1
> I try to implement the (xend_domain-lock yes) with
> (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don't
> work...

I can't find any mention of either of these options (with any
combination of "-" vs "_") in the xend source code in either unstable or
4.0. Are you sure this functionality actually exists? The threads I've
seen via google suggest that a patch was proposed back in 2008 but that
it was never committed.

> I've another server where I export a folder in NFS. And I mount it on
> my 2 HV. It's working fine.
> But when a VM start, nothing writing in the volume... So I can start
> the same VM on the other HV...
> 
> Some have an idea why it doesn't work? Or another solution to avoid
> this problem?
> I'me sure Xen have a tool or something else to do this!
> 
> Kind regards,
> Fabien
> 



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:23:00 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:23: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 1ScYuO-0005fn-H2; Thu, 07 Jun 2012 09:21:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYuN-0005fi-B5
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:21:35 +0000
Received: from [193.109.254.147:41322] by server-1.bemta-14.messagelabs.com id
	96/C3-08067-E9270DF4; Thu, 07 Jun 2012 09:21:34 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-8.tower-27.messagelabs.com!1339060893!8569811!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDE0Nzk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10536 invoked from network); 7 Jun 2012 09:21:34 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:21:34 -0000
X-IronPort-AV: E=Sophos;i="4.75,730,1330905600"; d="scan'208";a="12875968"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	07 Jun 2012 09:21:33 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 7 Jun 2012
	10:21:33 +0100
Message-ID: <1339060892.15265.44.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Xen Xen 
Date: Thu, 7 Jun 2012 10:21:32 +0100
In-Reply-To: 
References: 
	
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

You've posted this three separate times now, please don't do that.

On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:
> Dear everybody!
> 
> I'm a new user of Xen and I encount a problem in my new new job with 2
> Xen Hyper-visor.
> We've 2 HV which access on your NAS by iSCSI to store our VM.
> Or last time we start a VM on one HV without seen that it's was
> started on the other HV. So we encounter some read-only file system
> error...
> I want to avoid this problem. 
> 
> My server run on Debian 6 with Xen 4.0.1
> I try to implement the (xend_domain-lock yes) with
> (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don't
> work...

I can't find any mention of either of these options (with any
combination of "-" vs "_") in the xend source code in either unstable or
4.0. Are you sure this functionality actually exists? The threads I've
seen via google suggest that a patch was proposed back in 2008 but that
it was never committed.

> I've another server where I export a folder in NFS. And I mount it on
> my 2 HV. It's working fine.
> But when a VM start, nothing writing in the volume... So I can start
> the same VM on the other HV...
> 
> Some have an idea why it doesn't work? Or another solution to avoid
> this problem?
> I'me sure Xen have a tool or something else to do this!
> 
> Kind regards,
> Fabien
> 



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:25:35 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:25: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 1ScYwv-0005pg-Vl; Thu, 07 Jun 2012 09:24:13 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYwu-0005or-FZ
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:24:12 +0000
Received: from [85.158.143.35:50800] by server-2.bemta-4.messagelabs.com id
	36/E8-17938-93370DF4; Thu, 07 Jun 2012 09:24:09 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-21.messagelabs.com!1339061047!4741589!1
X-Originating-IP: [209.85.160.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9956 invoked from network); 7 Jun 2012 09:24:08 -0000
Received: from mail-gh0-f173.google.com (HELO mail-gh0-f173.google.com)
	(209.85.160.173)
	by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:24:08 -0000
Received: by ghrr14 with SMTP id r14so252046ghr.32
	for ; Thu, 07 Jun 2012 02:24:07 -0700 (PDT)
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=BgF56tB79ocML0suJkg4jkjEqu8WCYGoLDR7cjpr3Ik=;
	b=bY+f3wW/wB4vWS6p5MNRlLmWMmfGF6EPboBb4F0JK/kCSRurqdxrBaIFdob7V4y+83
	B3+jQKajYDgRFtoF7REwzC7N37TxcLmP/YC3BrNFhvA4YlGpUdlD+jAz3QvJbcPjhh1g
	xgtFSRSq3hluyHHh6CPH3bJpskTO16r/5K+ifdS1zD2C90SqPlwamuKiXvDqu1EtAZPr
	ud+M1BnRdSrhvKQcTRHV3e0wme3OGiIcEMUrch7dGr76G06+yEHerhZQNM17RtiGcGwx
	NYQLJVEo/q1vpY4GiTELwsYkmoRewvfgL8AQFIuElrmLTuUqrGdl/97MXcGN9ZoDe/Nd
	cQXw==
MIME-Version: 1.0
Received: by 10.42.153.10 with SMTP id k10mr754364icw.24.1339061047023; Thu,
	07 Jun 2012 02:24:07 -0700 (PDT)
Received: by 10.231.205.208 with HTTP; Thu, 7 Jun 2012 02:24:06 -0700 (PDT)
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
Date: Thu, 7 Jun 2012 10:24:06 +0100
Message-ID: 
From: Lars Kurth 
To: Rolu 
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7571424752092635982=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7571424752092635982==
Content-Type: multipart/alternative; boundary=90e6ba2121f70a574404c1de726b

--90e6ba2121f70a574404c1de726b
Content-Type: text/plain; charset=ISO-8859-1

Rolu,

thanks for the feedback.


xen" and "help with xcp" it would be nice if there were a few lines at
> the top of the page explaining which is which, so (new) people can
> have a better idea of where to look.


So you mean a link to Xen and XCP from the headline, or a tagline
describing what Xen/XCP is? Two lines are probably OK; more would probably
break up the navigation too much.


> The descriptions from
> http://xen.org/products/ and a link to
> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
> The latter is already linked in the "getting started with xen" column
> but would be better off at the top since it gives a feature table of
> both.
>
I am wondering whether Xen Features / XCP Features in one of the boxes
would not be better.


> As someone who started with Xen not long ago, I much prefer dedicated
> link pages over Category: pages. The latter just give a big unsorted
> (alphabetical doesn't count, needs to be sorted by subtopic to be a
> useful sort) list of pages of widely varying scope and usefulness.
> It's better than nothing, sure, but a page that sorts them by topic or
> purpose or something (much like this proposed front page really) is a
> lot better.
>
How about a compromise? Category pages have two parts:
1) A fixed part that can be used for any content, such as lists of
important articles by topic or other ciriteria
    An example of this is
http://wiki.xen.org/wiki/Category:Host_Install(and some of the pages
linked from it)
2) The auto-generated index

I know that some people are don't like category pages. However, until
somebody steps up and provides an alternative, which to do well requires
a) Classifying articles
b) Grouping them by topic or purpose
c) Encoding that grouping in some manual index
d) Keeping these up-to-date

... the category pages are all we have and are a lot better than what we
had in the old wiki. And they are self-maintaining.

The fact that we are having this discussion is actually good. I am open to
suggestions and maybe we just need a small number of manually maintained
indexes (or categories with maintained content at the top). Maybe to make
this really work and get better navigability we need some degree of
ownership in the wiki: i.e. community members owning content, categories,
etc. and being responsible for classifying, grouping and making it more
accessible.

I also started experimenting with shortcut boxes on pages such as
http://wiki.xen.org/wiki/Xen_Overview &
http://wiki.xen.org/wiki/Getting_Started and wanted to know what people
thought of these and whether these improve navigability.

Lars

--90e6ba2121f70a574404c1de726b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Rolu,

thanks for the feedback.


xen" and "help with xcp" it would be nice if there were a fe=
w lines at

the top of the page explaining which is which, so (new) people can

have a better idea of where to look.

So you mean a lin=
k to Xen and XCP from the headline, or a tagline describing what Xen/XCP is=
? Two lines are probably OK; more would probably break up the navigation to=
o much. 


=A0
 The description=
s from

http://xen.org/produ=
cts/ and a link to

http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.

The latter is already linked in the "getting started with xen" co=
lumn

but would be better off at the top since it gives a feature table of

both.


As someone who started with Xen not long ago, I much prefer dedicated

link pages over Category: pages. The latter just give a big unsorted

(alphabetical doesn't count, needs to be sorted by subtopic to be a

useful sort) list of pages of widely varying scope and usefulness.

It's better than nothing, sure, but a page that sorts them by topic or<=
br>
purpose or something (much like this proposed front page really) is a

lot better.


How about a compromise? Category pages have two parts: 
1) =
A fixed part that can be used for any content, such as lists of important a=
rticles by topic or other ciriteria
=A0=A0=A0 An example of this is ht=
tp://wiki.xen.org/wiki/Category:Host_Install (and some of the pages lin=
ked from it)


2) The auto-generated index 

I know that some people are don't l=
ike category pages. However, until somebody steps up and provides an altern=
ative, which to do well requires
a) Classifying articles
b) Grouping =
them by topic or purpose 


c) Encoding that grouping in some manual index
d) Keeping these up-to-da=
te

... the category pages are all we have and are a lot better than =
what we had in the old wiki. And they are self-maintaining. 

The fac=
t that we are having this discussion is actually good. I am open to suggest=
ions and maybe we just need a small number of manually maintained indexes (=
or categories with maintained content at the top). Maybe to make this reall=
y work and get better navigability we need some degree of ownership in the =
wiki: i.e. community members owning content, categories, etc. and being res=
ponsible for classifying, grouping and making it more accessible.



I also started experimenting with shortcut boxes on pages such as http://wiki.=
xen.org/wiki/Xen_Overview & http://wiki.xen.org/wiki/Getting_Started and wanted to know what people thought of these and whether these improve=
 navigability.


Lars





--90e6ba2121f70a574404c1de726b--


--===============7571424752092635982==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7571424752092635982==--


From xen-users-bounces@lists.xen.org Thu Jun 07 09:25:35 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:25: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 1ScYwv-0005pg-Vl; Thu, 07 Jun 2012 09:24:13 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScYwu-0005or-FZ
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:24:12 +0000
Received: from [85.158.143.35:50800] by server-2.bemta-4.messagelabs.com id
	36/E8-17938-93370DF4; Thu, 07 Jun 2012 09:24:09 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-21.messagelabs.com!1339061047!4741589!1
X-Originating-IP: [209.85.160.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9956 invoked from network); 7 Jun 2012 09:24:08 -0000
Received: from mail-gh0-f173.google.com (HELO mail-gh0-f173.google.com)
	(209.85.160.173)
	by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:24:08 -0000
Received: by ghrr14 with SMTP id r14so252046ghr.32
	for ; Thu, 07 Jun 2012 02:24:07 -0700 (PDT)
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=BgF56tB79ocML0suJkg4jkjEqu8WCYGoLDR7cjpr3Ik=;
	b=bY+f3wW/wB4vWS6p5MNRlLmWMmfGF6EPboBb4F0JK/kCSRurqdxrBaIFdob7V4y+83
	B3+jQKajYDgRFtoF7REwzC7N37TxcLmP/YC3BrNFhvA4YlGpUdlD+jAz3QvJbcPjhh1g
	xgtFSRSq3hluyHHh6CPH3bJpskTO16r/5K+ifdS1zD2C90SqPlwamuKiXvDqu1EtAZPr
	ud+M1BnRdSrhvKQcTRHV3e0wme3OGiIcEMUrch7dGr76G06+yEHerhZQNM17RtiGcGwx
	NYQLJVEo/q1vpY4GiTELwsYkmoRewvfgL8AQFIuElrmLTuUqrGdl/97MXcGN9ZoDe/Nd
	cQXw==
MIME-Version: 1.0
Received: by 10.42.153.10 with SMTP id k10mr754364icw.24.1339061047023; Thu,
	07 Jun 2012 02:24:07 -0700 (PDT)
Received: by 10.231.205.208 with HTTP; Thu, 7 Jun 2012 02:24:06 -0700 (PDT)
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
Date: Thu, 7 Jun 2012 10:24:06 +0100
Message-ID: 
From: Lars Kurth 
To: Rolu 
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7571424752092635982=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============7571424752092635982==
Content-Type: multipart/alternative; boundary=90e6ba2121f70a574404c1de726b

--90e6ba2121f70a574404c1de726b
Content-Type: text/plain; charset=ISO-8859-1

Rolu,

thanks for the feedback.


xen" and "help with xcp" it would be nice if there were a few lines at
> the top of the page explaining which is which, so (new) people can
> have a better idea of where to look.


So you mean a link to Xen and XCP from the headline, or a tagline
describing what Xen/XCP is? Two lines are probably OK; more would probably
break up the navigation too much.


> The descriptions from
> http://xen.org/products/ and a link to
> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
> The latter is already linked in the "getting started with xen" column
> but would be better off at the top since it gives a feature table of
> both.
>
I am wondering whether Xen Features / XCP Features in one of the boxes
would not be better.


> As someone who started with Xen not long ago, I much prefer dedicated
> link pages over Category: pages. The latter just give a big unsorted
> (alphabetical doesn't count, needs to be sorted by subtopic to be a
> useful sort) list of pages of widely varying scope and usefulness.
> It's better than nothing, sure, but a page that sorts them by topic or
> purpose or something (much like this proposed front page really) is a
> lot better.
>
How about a compromise? Category pages have two parts:
1) A fixed part that can be used for any content, such as lists of
important articles by topic or other ciriteria
    An example of this is
http://wiki.xen.org/wiki/Category:Host_Install(and some of the pages
linked from it)
2) The auto-generated index

I know that some people are don't like category pages. However, until
somebody steps up and provides an alternative, which to do well requires
a) Classifying articles
b) Grouping them by topic or purpose
c) Encoding that grouping in some manual index
d) Keeping these up-to-date

... the category pages are all we have and are a lot better than what we
had in the old wiki. And they are self-maintaining.

The fact that we are having this discussion is actually good. I am open to
suggestions and maybe we just need a small number of manually maintained
indexes (or categories with maintained content at the top). Maybe to make
this really work and get better navigability we need some degree of
ownership in the wiki: i.e. community members owning content, categories,
etc. and being responsible for classifying, grouping and making it more
accessible.

I also started experimenting with shortcut boxes on pages such as
http://wiki.xen.org/wiki/Xen_Overview &
http://wiki.xen.org/wiki/Getting_Started and wanted to know what people
thought of these and whether these improve navigability.

Lars

--90e6ba2121f70a574404c1de726b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Rolu,

thanks for the feedback.


xen" and "help with xcp" it would be nice if there were a fe=
w lines at

the top of the page explaining which is which, so (new) people can

have a better idea of where to look.

So you mean a lin=
k to Xen and XCP from the headline, or a tagline describing what Xen/XCP is=
? Two lines are probably OK; more would probably break up the navigation to=
o much. 


=A0
 The description=
s from

http://xen.org/produ=
cts/ and a link to

http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.

The latter is already linked in the "getting started with xen" co=
lumn

but would be better off at the top since it gives a feature table of

both.


As someone who started with Xen not long ago, I much prefer dedicated

link pages over Category: pages. The latter just give a big unsorted

(alphabetical doesn't count, needs to be sorted by subtopic to be a

useful sort) list of pages of widely varying scope and usefulness.

It's better than nothing, sure, but a page that sorts them by topic or<=
br>
purpose or something (much like this proposed front page really) is a

lot better.


How about a compromise? Category pages have two parts: 
1) =
A fixed part that can be used for any content, such as lists of important a=
rticles by topic or other ciriteria
=A0=A0=A0 An example of this is ht=
tp://wiki.xen.org/wiki/Category:Host_Install (and some of the pages lin=
ked from it)


2) The auto-generated index 

I know that some people are don't l=
ike category pages. However, until somebody steps up and provides an altern=
ative, which to do well requires
a) Classifying articles
b) Grouping =
them by topic or purpose 


c) Encoding that grouping in some manual index
d) Keeping these up-to-da=
te

... the category pages are all we have and are a lot better than =
what we had in the old wiki. And they are self-maintaining. 

The fac=
t that we are having this discussion is actually good. I am open to suggest=
ions and maybe we just need a small number of manually maintained indexes (=
or categories with maintained content at the top). Maybe to make this reall=
y work and get better navigability we need some degree of ownership in the =
wiki: i.e. community members owning content, categories, etc. and being res=
ponsible for classifying, grouping and making it more accessible.



I also started experimenting with shortcut boxes on pages such as http://wiki.=
xen.org/wiki/Xen_Overview & http://wiki.xen.org/wiki/Getting_Started and wanted to know what people thought of these and whether these improve=
 navigability.


Lars





--90e6ba2121f70a574404c1de726b--


--===============7571424752092635982==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7571424752092635982==--


From xen-users-bounces@lists.xen.org Thu Jun 07 09:35:51 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:35: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 1ScZ74-0006sK-UJ; Thu, 07 Jun 2012 09:34:42 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZ72-0006s5-QZ
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:34:41 +0000
Received: from [85.158.139.83:60046] by server-11.bemta-5.messagelabs.com id
	D9/D4-25194-FA570DF4; Thu, 07 Jun 2012 09:34:39 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1339061679!28455157!1
X-Originating-IP: [209.85.212.179]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8959 invoked from network); 7 Jun 2012 09:34:39 -0000
Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com)
	(209.85.212.179)
	by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:34:39 -0000
Received: by wibhr14 with SMTP id hr14so19213wib.14
	for ; Thu, 07 Jun 2012 02:34:39 -0700 (PDT)
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
	:content-type; bh=YvbRXwShOds6dioJMjMr0I/l39hP3pzYn3DRqijPczE=;
	b=xo8PykZ4U2vpir7gjEEhpPazVsDbaBcM/Fky99dQbkJd8Z/2E7+sXE5nzJmoIAHxtE
	92yp/BLJV2RCIfUU9/xHabVRYhNAOCstmhrjIVauLbqjYfE4qY/0eBU633X8QyI6EmdA
	+A2jwWM3eNbO5qqbaG7KgVb82KQKffc2zUE4wqV6Rxyf4ABFL5m8KErM6cNmQ2wenJh9
	AUAHOXhIbsnUDKI0evfrbx2Ntuib+1j8pijI7e7pvrp6BZKXfp7piOvYoi7re4sHFbHs
	NtxPn9JAkMVGhMTkAnt5uIKDVcorvjAHeongkbvwvUC78b3/ZCXW5zIkYvC/euYX/qg3
	nExA==
MIME-Version: 1.0
Received: by 10.216.210.34 with SMTP id t34mr402218weo.171.1339061678960; Thu,
	07 Jun 2012 02:34:38 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Thu, 7 Jun 2012 02:34:38 -0700 (PDT)
In-Reply-To: <1339060892.15265.44.camel@zakaz.uk.xensource.com>
References: 
	
	<1339060892.15265.44.camel@zakaz.uk.xensource.com>
Date: Thu, 7 Jun 2012 11:34:38 +0200
Message-ID: 
From: Xen Xen 
To: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3957584487455197962=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3957584487455197962==
Content-Type: multipart/alternative; boundary=0016e6dab3dab4f01c04c1de977a

--0016e6dab3dab4f01c04c1de977a
Content-Type: text/plain; charset=ISO-8859-1

Dear Ian,

Yes I thinking that my email was not delivered sorry...

Sorry for the wrong synthax too. The option that is found is
(xend-domain-lock) and not (xend_domain-lock).
I found out here:
http://serverfault.com/questions/21699/how-to-manage-xen-virtual-machines-on-shared-san-storage

If this option didn't really exist, how can I do?
Cause in current time  I can start two VM in the same time and cause
read-only file system error...
I've 2 Xen server which stored VM on a NAS with iSCSI. It's works great,
but I've just this problem...
Still exist a solution to resolve this?

Kid regards,
Fabien


2012/6/7 Ian Campbell 

> You've posted this three separate times now, please don't do that.
>
> On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:
> > Dear everybody!
> >
> > I'm a new user of Xen and I encount a problem in my new new job with 2
> > Xen Hyper-visor.
> > We've 2 HV which access on your NAS by iSCSI to store our VM.
> > Or last time we start a VM on one HV without seen that it's was
> > started on the other HV. So we encounter some read-only file system
> > error...
> > I want to avoid this problem.
> >
> > My server run on Debian 6 with Xen 4.0.1
> > I try to implement the (xend_domain-lock yes) with
> > (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don't
> > work...
>
> I can't find any mention of either of these options (with any
> combination of "-" vs "_") in the xend source code in either unstable or
> 4.0. Are you sure this functionality actually exists? The threads I've
> seen via google suggest that a patch was proposed back in 2008 but that
> it was never committed.
>
> > I've another server where I export a folder in NFS. And I mount it on
> > my 2 HV. It's working fine.
> > But when a VM start, nothing writing in the volume... So I can start
> > the same VM on the other HV...
> >
> > Some have an idea why it doesn't work? Or another solution to avoid
> > this problem?
> > I'me sure Xen have a tool or something else to do this!
> >
> > Kind regards,
> > Fabien
> >
>
>
>

--0016e6dab3dab4f01c04c1de977a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Ian,

Yes I thinking that my email was not delivered sorry...
Sorry for the wrong synthax too. The option that is found is=A0 (xend-=
domain-lock) and not (xend_domain-lock).
I found out here: 
http://serverfault.com/questions/21699/how-to-man=
age-xen-virtual-machines-on-shared-san-storage


If this option didn't really exist, how can I do?
Cause in curre=
nt time=A0 I can start two VM in the same time and cause read-only file sys=
tem error...
I've 2 Xen server which stored VM on a NAS with iSCSI. =
It's works great, but I've just this problem...

Still exist a solution to resolve this?

Kid regards,
Fabien

2012/6/7 Ian Campbell &l=
t;Ian.Campbell=
@citrix.com>


You've posted this three separate times =
now, please don't do that.




On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:

> Dear everybody!

>

> I'm a new user of Xen and I encount a problem in my new new job wi=
th 2

> Xen Hyper-visor.

> We've 2 HV which access on your NAS by iSCSI to store our VM.

> Or last time we start a VM on one HV without seen that it's was
> started on the other HV. So we encounter some read-only file system
> error...

> I want to avoid this problem.

>

> My server run on Debian 6 with Xen 4.0.1

> I try to implement the (xend_domain-lock yes) with

> (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don'=
;t

> work...




I can't find any mention of either of these options (with any

combination of "-" vs "_") in the xend source code in e=
ither unstable or

4.0. Are you sure this functionality actually exists? The threads I've<=
br>
seen via google suggest that a patch was proposed back in 2008 but that

it was never committed.




> I've another server where I export a folder in NFS. And I mount it=
 on

> my 2 HV. It's working fine.

> But when a VM start, nothing writing in the volume... So I can start
> the same VM on the other HV...

>

> Some have an idea why it doesn't work? Or another solution to avoi=
d

> this problem?

> I'me sure Xen have a tool or something else to do this!

>

> Kind regards,

> Fabien

>









--0016e6dab3dab4f01c04c1de977a--


--===============3957584487455197962==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3957584487455197962==--


From xen-users-bounces@lists.xen.org Thu Jun 07 09:35:51 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:35: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 1ScZ74-0006sK-UJ; Thu, 07 Jun 2012 09:34:42 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZ72-0006s5-QZ
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:34:41 +0000
Received: from [85.158.139.83:60046] by server-11.bemta-5.messagelabs.com id
	D9/D4-25194-FA570DF4; Thu, 07 Jun 2012 09:34:39 +0000
X-Env-Sender: xenbys@gmail.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1339061679!28455157!1
X-Originating-IP: [209.85.212.179]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8959 invoked from network); 7 Jun 2012 09:34:39 -0000
Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com)
	(209.85.212.179)
	by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:34:39 -0000
Received: by wibhr14 with SMTP id hr14so19213wib.14
	for ; Thu, 07 Jun 2012 02:34:39 -0700 (PDT)
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
	:content-type; bh=YvbRXwShOds6dioJMjMr0I/l39hP3pzYn3DRqijPczE=;
	b=xo8PykZ4U2vpir7gjEEhpPazVsDbaBcM/Fky99dQbkJd8Z/2E7+sXE5nzJmoIAHxtE
	92yp/BLJV2RCIfUU9/xHabVRYhNAOCstmhrjIVauLbqjYfE4qY/0eBU633X8QyI6EmdA
	+A2jwWM3eNbO5qqbaG7KgVb82KQKffc2zUE4wqV6Rxyf4ABFL5m8KErM6cNmQ2wenJh9
	AUAHOXhIbsnUDKI0evfrbx2Ntuib+1j8pijI7e7pvrp6BZKXfp7piOvYoi7re4sHFbHs
	NtxPn9JAkMVGhMTkAnt5uIKDVcorvjAHeongkbvwvUC78b3/ZCXW5zIkYvC/euYX/qg3
	nExA==
MIME-Version: 1.0
Received: by 10.216.210.34 with SMTP id t34mr402218weo.171.1339061678960; Thu,
	07 Jun 2012 02:34:38 -0700 (PDT)
Received: by 10.227.209.146 with HTTP; Thu, 7 Jun 2012 02:34:38 -0700 (PDT)
In-Reply-To: <1339060892.15265.44.camel@zakaz.uk.xensource.com>
References: 
	
	<1339060892.15265.44.camel@zakaz.uk.xensource.com>
Date: Thu, 7 Jun 2012 11:34:38 +0200
Message-ID: 
From: Xen Xen 
To: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3957584487455197962=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3957584487455197962==
Content-Type: multipart/alternative; boundary=0016e6dab3dab4f01c04c1de977a

--0016e6dab3dab4f01c04c1de977a
Content-Type: text/plain; charset=ISO-8859-1

Dear Ian,

Yes I thinking that my email was not delivered sorry...

Sorry for the wrong synthax too. The option that is found is
(xend-domain-lock) and not (xend_domain-lock).
I found out here:
http://serverfault.com/questions/21699/how-to-manage-xen-virtual-machines-on-shared-san-storage

If this option didn't really exist, how can I do?
Cause in current time  I can start two VM in the same time and cause
read-only file system error...
I've 2 Xen server which stored VM on a NAS with iSCSI. It's works great,
but I've just this problem...
Still exist a solution to resolve this?

Kid regards,
Fabien


2012/6/7 Ian Campbell 

> You've posted this three separate times now, please don't do that.
>
> On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:
> > Dear everybody!
> >
> > I'm a new user of Xen and I encount a problem in my new new job with 2
> > Xen Hyper-visor.
> > We've 2 HV which access on your NAS by iSCSI to store our VM.
> > Or last time we start a VM on one HV without seen that it's was
> > started on the other HV. So we encounter some read-only file system
> > error...
> > I want to avoid this problem.
> >
> > My server run on Debian 6 with Xen 4.0.1
> > I try to implement the (xend_domain-lock yes) with
> > (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don't
> > work...
>
> I can't find any mention of either of these options (with any
> combination of "-" vs "_") in the xend source code in either unstable or
> 4.0. Are you sure this functionality actually exists? The threads I've
> seen via google suggest that a patch was proposed back in 2008 but that
> it was never committed.
>
> > I've another server where I export a folder in NFS. And I mount it on
> > my 2 HV. It's working fine.
> > But when a VM start, nothing writing in the volume... So I can start
> > the same VM on the other HV...
> >
> > Some have an idea why it doesn't work? Or another solution to avoid
> > this problem?
> > I'me sure Xen have a tool or something else to do this!
> >
> > Kind regards,
> > Fabien
> >
>
>
>

--0016e6dab3dab4f01c04c1de977a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Ian,

Yes I thinking that my email was not delivered sorry...
Sorry for the wrong synthax too. The option that is found is=A0 (xend-=
domain-lock) and not (xend_domain-lock).
I found out here: 
http://serverfault.com/questions/21699/how-to-man=
age-xen-virtual-machines-on-shared-san-storage


If this option didn't really exist, how can I do?
Cause in curre=
nt time=A0 I can start two VM in the same time and cause read-only file sys=
tem error...
I've 2 Xen server which stored VM on a NAS with iSCSI. =
It's works great, but I've just this problem...

Still exist a solution to resolve this?

Kid regards,
Fabien

2012/6/7 Ian Campbell &l=
t;Ian.Campbell=
@citrix.com>


You've posted this three separate times =
now, please don't do that.




On Wed, 2012-06-06 at 10:30 +0100, Xen Xen wrote:

> Dear everybody!

>

> I'm a new user of Xen and I encount a problem in my new new job wi=
th 2

> Xen Hyper-visor.

> We've 2 HV which access on your NAS by iSCSI to store our VM.

> Or last time we start a VM on one HV without seen that it's was
> started on the other HV. So we encounter some read-only file system
> error...

> I want to avoid this problem.

>

> My server run on Debian 6 with Xen 4.0.1

> I try to implement the (xend_domain-lock yes) with

> (xend-domain-lock-path /etc/xen/xen_lock) but it unfortunately don'=
;t

> work...




I can't find any mention of either of these options (with any

combination of "-" vs "_") in the xend source code in e=
ither unstable or

4.0. Are you sure this functionality actually exists? The threads I've<=
br>
seen via google suggest that a patch was proposed back in 2008 but that

it was never committed.




> I've another server where I export a folder in NFS. And I mount it=
 on

> my 2 HV. It's working fine.

> But when a VM start, nothing writing in the volume... So I can start
> the same VM on the other HV...

>

> Some have an idea why it doesn't work? Or another solution to avoi=
d

> this problem?

> I'me sure Xen have a tool or something else to do this!

>

> Kind regards,

> Fabien

>









--0016e6dab3dab4f01c04c1de977a--


--===============3957584487455197962==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============3957584487455197962==--


From xen-users-bounces@lists.xen.org Thu Jun 07 09:47:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:47: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 1ScZI2-0008FV-Ef; Thu, 07 Jun 2012 09:46:02 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZI1-0008FL-6V
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:46:01 +0000
Received: from [85.158.139.83:9409] by server-8.bemta-5.messagelabs.com id
	F3/71-02058-85870DF4; Thu, 07 Jun 2012 09:46:00 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-12.tower-182.messagelabs.com!1339062358!32384037!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3606 invoked from network); 7 Jun 2012 09:45:59 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:45:59 -0000
Received: by obbwd20 with SMTP id wd20so952445obb.32
	for ; Thu, 07 Jun 2012 02:45:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=qxPLaC2nAgstQMSAebmOUthFSCcIDJyOJFrpK+SV55w=;
	b=RuXfGTgCPg9/o/QC/QnR8v6fmO5kZ23c1U9/bKp4j6S3cJ1fjLf6+HWNubPcw4/XGd
	zimv8yoWj9SgZBBZr0EkweCCJtW9NtKWxsCUxm9ZzqbSHXcE9kQybF4abVKhunuyA9ca
	/0y1vf6tkZsUtTPnlfwnrxva5meEwomr6PXck5KUob6tucO4vmvSrINTTXsgqddGCKed
	/lQpbnQ1MNQO5Vh4TYWxQ6H3XNa0MBSiUwebO3uXVdChKeKxNVm4J1xbqTfulcTom4hK
	stReM4jUYYhrqw9UDMh/9qwZWKAhvuCrVHXd8C/x9de/z8QjU2cvgPMFjXYpBUHr7yUy
	9B0Q==
Received: by 10.182.36.102 with SMTP id p6mr1316619obj.77.1339062357906; Thu,
	07 Jun 2012 02:45:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 02:45:37 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
From: Rolu 
Date: Thu, 7 Jun 2012 11:45:37 +0200
Message-ID: 
To: Kevin Stokes 
X-Gm-Message-State: ALoCoQm1lc6RKkybtulhnCvel+ifOswPxsz2bttehVCNBPjZSqi3faCRTDxYfwDOLg0Tn6xbBRXj
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 11:09 AM, Kevin Stokes  wrote:
> Hi I am a first time user of XCP.
>
> I have installed XCP 1.4.90 on a PC. =A0 I am interested in setting up a
> cloud where the instances will run node.js to provide websockets for a
> hobby project I'm working on.
>
> I installed a Maverick Meerkat 64bit =A0vm and it works but I can't get
> it to work with openxenmanager so instead I am trying Debian Squeeze
> but vm-start fails with INVALID_SOURCE. (see below)
>
> Thanks for any help,
> =A0-Kevin
>
>
>
> [root@xenserver-octopus ~]# xe vm-install template=3DDebian\ Squeeze\
> 6.0\ \(64-bit\) =A0new-name-label=3DHelloDebian
> d541ca58-ffcf-e512-0808-7d6d4f09150d
>
> [root@xenserver-octopus ~]# xe vif-create
> network-uuid=3D5ad5dd35-31b0-5510-b050-7c9b362df98b
> vm-uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d device=3D0
> 23d16150-1ff2-3f61-fa4c-35711e374cb9
>
> [root@xenserver-octopus ~]# xe vm-param-set
> uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
> other-config:install-repository=3Dhttp://ftp.us.debian.org/debian/
>
>
> [root@xenserver-octopus ~]# xe vm-start
> uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
> Error code: INVALID_SOURCE
> Error parameters: Unable to access a required file in the specified
> repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-=
amd64/current/images/netboot/xen/vmlinuz.,
> ,
> [root@xenserver-octopus ~]#
>

At first glance your try seems okay. Are you actually able to access
that file from the server you're trying it on? Might be a network
issue or firewall in the way. Try:

wget http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/cur=
rent/images/netboot/xen/vmlinuz

and see if that works.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:47:28 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:47: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 1ScZI2-0008FV-Ef; Thu, 07 Jun 2012 09:46:02 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZI1-0008FL-6V
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:46:01 +0000
Received: from [85.158.139.83:9409] by server-8.bemta-5.messagelabs.com id
	F3/71-02058-85870DF4; Thu, 07 Jun 2012 09:46:00 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-12.tower-182.messagelabs.com!1339062358!32384037!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3606 invoked from network); 7 Jun 2012 09:45:59 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:45:59 -0000
Received: by obbwd20 with SMTP id wd20so952445obb.32
	for ; Thu, 07 Jun 2012 02:45:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=qxPLaC2nAgstQMSAebmOUthFSCcIDJyOJFrpK+SV55w=;
	b=RuXfGTgCPg9/o/QC/QnR8v6fmO5kZ23c1U9/bKp4j6S3cJ1fjLf6+HWNubPcw4/XGd
	zimv8yoWj9SgZBBZr0EkweCCJtW9NtKWxsCUxm9ZzqbSHXcE9kQybF4abVKhunuyA9ca
	/0y1vf6tkZsUtTPnlfwnrxva5meEwomr6PXck5KUob6tucO4vmvSrINTTXsgqddGCKed
	/lQpbnQ1MNQO5Vh4TYWxQ6H3XNa0MBSiUwebO3uXVdChKeKxNVm4J1xbqTfulcTom4hK
	stReM4jUYYhrqw9UDMh/9qwZWKAhvuCrVHXd8C/x9de/z8QjU2cvgPMFjXYpBUHr7yUy
	9B0Q==
Received: by 10.182.36.102 with SMTP id p6mr1316619obj.77.1339062357906; Thu,
	07 Jun 2012 02:45:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 02:45:37 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
From: Rolu 
Date: Thu, 7 Jun 2012 11:45:37 +0200
Message-ID: 
To: Kevin Stokes 
X-Gm-Message-State: ALoCoQm1lc6RKkybtulhnCvel+ifOswPxsz2bttehVCNBPjZSqi3faCRTDxYfwDOLg0Tn6xbBRXj
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 11:09 AM, Kevin Stokes  wrote:
> Hi I am a first time user of XCP.
>
> I have installed XCP 1.4.90 on a PC. =A0 I am interested in setting up a
> cloud where the instances will run node.js to provide websockets for a
> hobby project I'm working on.
>
> I installed a Maverick Meerkat 64bit =A0vm and it works but I can't get
> it to work with openxenmanager so instead I am trying Debian Squeeze
> but vm-start fails with INVALID_SOURCE. (see below)
>
> Thanks for any help,
> =A0-Kevin
>
>
>
> [root@xenserver-octopus ~]# xe vm-install template=3DDebian\ Squeeze\
> 6.0\ \(64-bit\) =A0new-name-label=3DHelloDebian
> d541ca58-ffcf-e512-0808-7d6d4f09150d
>
> [root@xenserver-octopus ~]# xe vif-create
> network-uuid=3D5ad5dd35-31b0-5510-b050-7c9b362df98b
> vm-uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d device=3D0
> 23d16150-1ff2-3f61-fa4c-35711e374cb9
>
> [root@xenserver-octopus ~]# xe vm-param-set
> uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
> other-config:install-repository=3Dhttp://ftp.us.debian.org/debian/
>
>
> [root@xenserver-octopus ~]# xe vm-start
> uuid=3Dd541ca58-ffcf-e512-0808-7d6d4f09150d
> Error code: INVALID_SOURCE
> Error parameters: Unable to access a required file in the specified
> repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-=
amd64/current/images/netboot/xen/vmlinuz.,
> ,
> [root@xenserver-octopus ~]#
>

At first glance your try seems okay. Are you actually able to access
that file from the server you're trying it on? Might be a network
issue or firewall in the way. Try:

wget http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/cur=
rent/images/netboot/xen/vmlinuz

and see if that works.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:51:31 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:51: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 1ScZMI-00007o-Ru; Thu, 07 Jun 2012 09:50:26 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZMG-00007R-S7
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:50:25 +0000
Received: from [193.109.254.147:62706] by server-9.bemta-14.messagelabs.com id
	DC/59-27072-F5970DF4; Thu, 07 Jun 2012 09:50:23 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1339062616!8535246!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17583 invoked from network); 7 Jun 2012 09:50:16 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:50:16 -0000
Received: by eekd41 with SMTP id d41so156999eek.32
	for ; Thu, 07 Jun 2012 02:50:16 -0700 (PDT)
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=vJx2LsC6f94aFNHdODaKN8HDCv+ciCB5IlYSMj7LApM=;
	b=D88sWExBF0YAbkyi2+DPMYGWv+anb+NkteG3e6lEYjPJKiPl1rBaSqt8/r34t0g0tG
	fgyQ6mocZ749b0TZbDQvaYnj6hVQTq5daPSM8yYNhrfun/bbHqr4DuBaAtO0CLVFhlRr
	m4BW8u0FWo9CjWDrOH3sRej4weFzMlWtgHj0dLYYKfMXCMAc3nvFG3uumh39aK2nEYf1
	riMRA/umB34VM9aXRMeJHi1MiMCwTX6mRrXVe4yXuNJZtN8dDAdeC1UL61pUKk3TiIj8
	xLDZ3y3YxAOdn9JC0I1D44pK+swSdTX/jDMixAB/16nt5ro7BnwjzF9+PApAIy6UjazE
	F3Ig==
Received: by 10.14.127.130 with SMTP id d2mr805955eei.216.1339062615762;
	Thu, 07 Jun 2012 02:50:15 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id g51sm8876065eea.14.2012.06.07.02.50.13
	(version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 02:50:14 -0700 (PDT)
Message-ID: <4FD07954.9050803@xen.org>
Date: Thu, 07 Jun 2012 10:50:12 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org, "xen-api@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Kevin,
the xen-api list is the best place to ask questions for XCP. I am CC'ing 
the list. It's not the best named list and we are looking to rename it, 
but it is not entirely straightforward and may take a little.
Regards
Lars

On 07/06/2012 10:09, Kevin Stokes wrote:
> Hi I am a first time user of XCP.
>
> I have installed XCP 1.4.90 on a PC.   I am interested in setting up a
> cloud where the instances will run node.js to provide websockets for a
> hobby project I'm working on.
>
> I installed a Maverick Meerkat 64bit  vm and it works but I can't get
> it to work with openxenmanager so instead I am trying Debian Squeeze
> but vm-start fails with INVALID_SOURCE. (see below)
>
> Thanks for any help,
>    -Kevin
>
>
>
> [root@xenserver-octopus ~]# xe vm-install template=Debian\ Squeeze\
> 6.0\ \(64-bit\)  new-name-label=HelloDebian
> d541ca58-ffcf-e512-0808-7d6d4f09150d
>
> [root@xenserver-octopus ~]# xe vif-create
> network-uuid=5ad5dd35-31b0-5510-b050-7c9b362df98b
> vm-uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d device=0
> 23d16150-1ff2-3f61-fa4c-35711e374cb9
>
> [root@xenserver-octopus ~]# xe vm-param-set
> uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d
> other-config:install-repository=http://ftp.us.debian.org/debian/
>
>
> [root@xenserver-octopus ~]# xe vm-start
> uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d
> Error code: INVALID_SOURCE
> Error parameters: Unable to access a required file in the specified
> repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/netboot/xen/vmlinuz.,
> ,
> [root@xenserver-octopus ~]#
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:51:31 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:51: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 1ScZMI-00007o-Ru; Thu, 07 Jun 2012 09:50:26 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZMG-00007R-S7
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:50:25 +0000
Received: from [193.109.254.147:62706] by server-9.bemta-14.messagelabs.com id
	DC/59-27072-F5970DF4; Thu, 07 Jun 2012 09:50:23 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1339062616!8535246!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17583 invoked from network); 7 Jun 2012 09:50:16 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 09:50:16 -0000
Received: by eekd41 with SMTP id d41so156999eek.32
	for ; Thu, 07 Jun 2012 02:50:16 -0700 (PDT)
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=vJx2LsC6f94aFNHdODaKN8HDCv+ciCB5IlYSMj7LApM=;
	b=D88sWExBF0YAbkyi2+DPMYGWv+anb+NkteG3e6lEYjPJKiPl1rBaSqt8/r34t0g0tG
	fgyQ6mocZ749b0TZbDQvaYnj6hVQTq5daPSM8yYNhrfun/bbHqr4DuBaAtO0CLVFhlRr
	m4BW8u0FWo9CjWDrOH3sRej4weFzMlWtgHj0dLYYKfMXCMAc3nvFG3uumh39aK2nEYf1
	riMRA/umB34VM9aXRMeJHi1MiMCwTX6mRrXVe4yXuNJZtN8dDAdeC1UL61pUKk3TiIj8
	xLDZ3y3YxAOdn9JC0I1D44pK+swSdTX/jDMixAB/16nt5ro7BnwjzF9+PApAIy6UjazE
	F3Ig==
Received: by 10.14.127.130 with SMTP id d2mr805955eei.216.1339062615762;
	Thu, 07 Jun 2012 02:50:15 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id g51sm8876065eea.14.2012.06.07.02.50.13
	(version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 02:50:14 -0700 (PDT)
Message-ID: <4FD07954.9050803@xen.org>
Date: Thu, 07 Jun 2012 10:50:12 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org, "xen-api@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] xcp beginner questions
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Kevin,
the xen-api list is the best place to ask questions for XCP. I am CC'ing 
the list. It's not the best named list and we are looking to rename it, 
but it is not entirely straightforward and may take a little.
Regards
Lars

On 07/06/2012 10:09, Kevin Stokes wrote:
> Hi I am a first time user of XCP.
>
> I have installed XCP 1.4.90 on a PC.   I am interested in setting up a
> cloud where the instances will run node.js to provide websockets for a
> hobby project I'm working on.
>
> I installed a Maverick Meerkat 64bit  vm and it works but I can't get
> it to work with openxenmanager so instead I am trying Debian Squeeze
> but vm-start fails with INVALID_SOURCE. (see below)
>
> Thanks for any help,
>    -Kevin
>
>
>
> [root@xenserver-octopus ~]# xe vm-install template=Debian\ Squeeze\
> 6.0\ \(64-bit\)  new-name-label=HelloDebian
> d541ca58-ffcf-e512-0808-7d6d4f09150d
>
> [root@xenserver-octopus ~]# xe vif-create
> network-uuid=5ad5dd35-31b0-5510-b050-7c9b362df98b
> vm-uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d device=0
> 23d16150-1ff2-3f61-fa4c-35711e374cb9
>
> [root@xenserver-octopus ~]# xe vm-param-set
> uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d
> other-config:install-repository=http://ftp.us.debian.org/debian/
>
>
> [root@xenserver-octopus ~]# xe vm-start
> uuid=d541ca58-ffcf-e512-0808-7d6d4f09150d
> Error code: INVALID_SOURCE
> Error parameters: Unable to access a required file in the specified
> repository: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/netboot/xen/vmlinuz.,
> ,
> [root@xenserver-octopus ~]#
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 09:54:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:54: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 1ScZP4-0000W0-2d; Thu, 07 Jun 2012 09:53:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZP1-0000Vd-Jj
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:53:17 +0000
Received: from [193.109.254.147:52900] by server-10.bemta-14.messagelabs.com
	id FD/3B-25709-A0A70DF4; Thu, 07 Jun 2012 09:53:14 +0000
X-Env-Sender: itobin@tidyhosts.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1339062784!3391616!1
X-Originating-IP: [83.142.228.126]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14654 invoked from network); 7 Jun 2012 09:53:04 -0000
Received: from london.tidyhosts.com (HELO tidyhosts.com) (83.142.228.126)
	by server-10.tower-27.messagelabs.com with SMTP;
	7 Jun 2012 09:53:04 -0000
Received: from electron.tidyhosts.com ([213.152.51.27]) by tidyhosts.com with
	MailEnable ESMTP; Thu, 7 Jun 2012 10:53:04 +0100
MIME-Version: 1.0
Date: Thu, 7 Jun 2012 10:53:04 +0100
Content-class: urn:content-classes:message
Message-ID: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Xen-users] Pvgrub on Debian dom0
Thread-Index: Ac0392SKIk1WMRdNQxmADXUCDFbv+gMm5XcQ
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
From: "Ian Tobin" 
To: "Ian Campbell" 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SWFuLA0KDQpTb3JyeSBmb3IgdGhlIGRlbGF5Lg0KDQpJbSB1c2luZyBncnViLmNmZyB3aXRoIGEg
c3ltIGxpbmsgdG8gbWVudS5sc3QsIEkgZG9u4oCZdCBhY3R1YWxseSBoYXZlIGdydWIgaW5zdGFs
bGVkIG9uIHRoZSBkb211Lg0KDQpUaGUgZG9tdSB3aWxsIGJvb3QgaWYgSSB0eXBlIHRoZSBwYXRo
IHRvIHRoZSBncnViLmNmZyBvciBtZW51LmxzdCBidXQgd2lsbCBub3QgYXV0b21hdGljYWxseS4N
Cg0KVGhhbmtzDQoNCklhbg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IElhbiBDYW1wYmVsbCBbbWFpbHRvOklhbi5DYW1wYmVsbEBjaXRyaXguY29tXSANClNlbnQ6IDIy
IE1heSAyMDEyIDA5OjQ3DQpUbzogSWFuIFRvYmluDQpDYzogeGVuLXVzZXJzQGxpc3RzLnhlbi5v
cmcNClN1YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBQdmdydWIgb24gRGViaWFuIGRvbTANCg0KT24g
TW9uLCAyMDEyLTA1LTIxIGF0IDE4OjU3ICswMTAwLCBJYW4gVG9iaW4gd3JvdGU6DQo+IEhpLA0K
PiANCj4gSGF2aW5nIGEgcHJvYmxlbSBnZXR0aW5nIGEgZG9tdSB0byBib290IGNvcnJlY3RseS4N
Cj4gDQo+IFdoZW4gSSBlbnRlciB4bCBjcmVhdGUgZ3Vlc3QgaXQgYm9vdHMgc3RyYWlnaHQgaW50
byBncnViZG9tLg0KPiANCj4gSWYgSSBlbnRlciB0aGUgY29uZmlnIGxvY2F0aW9uIGluIGdydWJk
b20gdCBib290cyBhcyBleHBlY3RlZC4NCj4gDQo+IFRoZSBsb2NhdGlvbiBvZiB0aGUgZ3J1Yi5j
ZmcgaXMgdGhlIHNhbWUgaW4gbXkgZG9tdSBjb25maWcgYXMgd2hhdCBpbiBlbnRlcmluZyBidXQg
anVzdCB3aWxsIG5vdCB3b3JrLg0KDQpncnViLmNmZyBpcyB0aGUgZ3J1YjIgZmlsZSwgd2hlcmVh
cyBwdmdydWIgaXMgY3VycmVudGx5IGdydWIxIChzb21ldGltZXMgY2FsbGVkIGdydWIgbGVnYWN5
KS4gQm90aCB0aGUgc3ludGF4IGFuZCB0aGUgbG9jYXRpb24gb2YgdGhlIGNvbmZpZyBmaWxlIGRp
ZmZlcnMgYmV0d2VlbiB0aGUgdHdvIHZlcnNpb25zIG9mIGdydWIuDQoNCkknbSBub3Qgc3VyZSBp
ZiBhbnlvbmUgaXMgd29ya2luZyBvbiBwdmdydWIyLCBJIHRob3VnaHQgSSdkIGhlYXJkIGEgcnVt
b3VyIG9mIGl0Lg0KDQpUaGVyZSBpcyBhIHRvb2wsIHB2LWdydWItbWVudS5sc3QsIHdoaWNoIGhh
cyBiZWVuIHByb3Bvc2VkIGZvciBEZWJpYW5bMF0gd2hpY2ggaGVscHMgeW91IGNyZWF0ZSBhbmQg
bWFuYWdlIGEgbGVnYWN5IHN0eWxlIG1lbnUubHN0Lg0KDQpJIHRoaW5rIGdydWItbGVnYWN5IGlz
IGFsc28gc3RpbGwgaW4gRGViaWFuLCBidXQgeW91IG1pZ2h0IG5lZWQgdG8gZXhwbGljaXRseSBp
bnN0YWxsIGl0IHJhdGhlciB0aGFuIGdydWIyLg0KDQpJYW4uDQoNClswXSBodHRwOi8vYnVncy5k
ZWJpYW4ub3JnLzY3MjEwNA0KDQoNCj4gDQo+IEFueSBpZGVhcz8NCj4gDQo+IElhbg0KPiAuDQo+
IA0KPiANCj4gDQo+ICANCj4gDQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdA0KPiBYZW4tdXNl
cnNAbGlzdHMueGVuLm9yZw0KPiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMNCg0KDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2Vy
cyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5v
cmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Thu Jun 07 09:54:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 09:54: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 1ScZP4-0000W0-2d; Thu, 07 Jun 2012 09:53:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZP1-0000Vd-Jj
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 09:53:17 +0000
Received: from [193.109.254.147:52900] by server-10.bemta-14.messagelabs.com
	id FD/3B-25709-A0A70DF4; Thu, 07 Jun 2012 09:53:14 +0000
X-Env-Sender: itobin@tidyhosts.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1339062784!3391616!1
X-Originating-IP: [83.142.228.126]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14654 invoked from network); 7 Jun 2012 09:53:04 -0000
Received: from london.tidyhosts.com (HELO tidyhosts.com) (83.142.228.126)
	by server-10.tower-27.messagelabs.com with SMTP;
	7 Jun 2012 09:53:04 -0000
Received: from electron.tidyhosts.com ([213.152.51.27]) by tidyhosts.com with
	MailEnable ESMTP; Thu, 7 Jun 2012 10:53:04 +0100
MIME-Version: 1.0
Date: Thu, 7 Jun 2012 10:53:04 +0100
Content-class: urn:content-classes:message
Message-ID: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Xen-users] Pvgrub on Debian dom0
Thread-Index: Ac0392SKIk1WMRdNQxmADXUCDFbv+gMm5XcQ
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
From: "Ian Tobin" 
To: "Ian Campbell" 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SWFuLA0KDQpTb3JyeSBmb3IgdGhlIGRlbGF5Lg0KDQpJbSB1c2luZyBncnViLmNmZyB3aXRoIGEg
c3ltIGxpbmsgdG8gbWVudS5sc3QsIEkgZG9u4oCZdCBhY3R1YWxseSBoYXZlIGdydWIgaW5zdGFs
bGVkIG9uIHRoZSBkb211Lg0KDQpUaGUgZG9tdSB3aWxsIGJvb3QgaWYgSSB0eXBlIHRoZSBwYXRo
IHRvIHRoZSBncnViLmNmZyBvciBtZW51LmxzdCBidXQgd2lsbCBub3QgYXV0b21hdGljYWxseS4N
Cg0KVGhhbmtzDQoNCklhbg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IElhbiBDYW1wYmVsbCBbbWFpbHRvOklhbi5DYW1wYmVsbEBjaXRyaXguY29tXSANClNlbnQ6IDIy
IE1heSAyMDEyIDA5OjQ3DQpUbzogSWFuIFRvYmluDQpDYzogeGVuLXVzZXJzQGxpc3RzLnhlbi5v
cmcNClN1YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBQdmdydWIgb24gRGViaWFuIGRvbTANCg0KT24g
TW9uLCAyMDEyLTA1LTIxIGF0IDE4OjU3ICswMTAwLCBJYW4gVG9iaW4gd3JvdGU6DQo+IEhpLA0K
PiANCj4gSGF2aW5nIGEgcHJvYmxlbSBnZXR0aW5nIGEgZG9tdSB0byBib290IGNvcnJlY3RseS4N
Cj4gDQo+IFdoZW4gSSBlbnRlciB4bCBjcmVhdGUgZ3Vlc3QgaXQgYm9vdHMgc3RyYWlnaHQgaW50
byBncnViZG9tLg0KPiANCj4gSWYgSSBlbnRlciB0aGUgY29uZmlnIGxvY2F0aW9uIGluIGdydWJk
b20gdCBib290cyBhcyBleHBlY3RlZC4NCj4gDQo+IFRoZSBsb2NhdGlvbiBvZiB0aGUgZ3J1Yi5j
ZmcgaXMgdGhlIHNhbWUgaW4gbXkgZG9tdSBjb25maWcgYXMgd2hhdCBpbiBlbnRlcmluZyBidXQg
anVzdCB3aWxsIG5vdCB3b3JrLg0KDQpncnViLmNmZyBpcyB0aGUgZ3J1YjIgZmlsZSwgd2hlcmVh
cyBwdmdydWIgaXMgY3VycmVudGx5IGdydWIxIChzb21ldGltZXMgY2FsbGVkIGdydWIgbGVnYWN5
KS4gQm90aCB0aGUgc3ludGF4IGFuZCB0aGUgbG9jYXRpb24gb2YgdGhlIGNvbmZpZyBmaWxlIGRp
ZmZlcnMgYmV0d2VlbiB0aGUgdHdvIHZlcnNpb25zIG9mIGdydWIuDQoNCkknbSBub3Qgc3VyZSBp
ZiBhbnlvbmUgaXMgd29ya2luZyBvbiBwdmdydWIyLCBJIHRob3VnaHQgSSdkIGhlYXJkIGEgcnVt
b3VyIG9mIGl0Lg0KDQpUaGVyZSBpcyBhIHRvb2wsIHB2LWdydWItbWVudS5sc3QsIHdoaWNoIGhh
cyBiZWVuIHByb3Bvc2VkIGZvciBEZWJpYW5bMF0gd2hpY2ggaGVscHMgeW91IGNyZWF0ZSBhbmQg
bWFuYWdlIGEgbGVnYWN5IHN0eWxlIG1lbnUubHN0Lg0KDQpJIHRoaW5rIGdydWItbGVnYWN5IGlz
IGFsc28gc3RpbGwgaW4gRGViaWFuLCBidXQgeW91IG1pZ2h0IG5lZWQgdG8gZXhwbGljaXRseSBp
bnN0YWxsIGl0IHJhdGhlciB0aGFuIGdydWIyLg0KDQpJYW4uDQoNClswXSBodHRwOi8vYnVncy5k
ZWJpYW4ub3JnLzY3MjEwNA0KDQoNCj4gDQo+IEFueSBpZGVhcz8NCj4gDQo+IElhbg0KPiAuDQo+
IA0KPiANCj4gDQo+ICANCj4gDQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdA0KPiBYZW4tdXNl
cnNAbGlzdHMueGVuLm9yZw0KPiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMNCg0KDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2Vy
cyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5v
cmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Thu Jun 07 10:01:54 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 10:01:54 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScZWc-00017M-7f; Thu, 07 Jun 2012 10:01:06 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZWa-00017A-CP
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 10:01:04 +0000
Received: from [85.158.138.51:17449] by server-2.bemta-3.messagelabs.com id
	15/13-16299-FDB70DF4; Thu, 07 Jun 2012 10:01:03 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-16.tower-174.messagelabs.com!1339063260!28361539!1
X-Originating-IP: [209.85.160.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19558 invoked from network); 7 Jun 2012 10:01:02 -0000
Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com)
	(209.85.160.45)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 10:01:02 -0000
Received: by pbbro12 with SMTP id ro12so903033pbb.32
	for ; Thu, 07 Jun 2012 03:01:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding:x-gm-message-state;
	bh=75pGo8/z3iLn4iRX5svjQnn7mGp6LuA1b6g0hJrq4K0=;
	b=EmvdTInDzcLnlNlmA+ZdrWE0742XHlOQBI110EATiOYosb+CfSZKe4hUzgPzGcabqz
	HTsj6ETtLqaDXC2DdbLi+/AjbAF201t7dvx/AWMuoAyYJTI1xIaheHf1BXZJUUGjNMB7
	BjXyAQ/BbbLgM41910fC0mvsANYBmbqm3lJ6yAj2XbrU4dE2twbT5YBlSVzNqDCvoHjL
	NU4p/mMVUCIDst+6VcEePQX3ZsKUKfhs/ipZ6rv1jOh2RFJbum/xBB8yiEOEFOqrpwS5
	PBnoEkY1ONJItjukFTcAKStBXCRMXGmbWFmr0+Oiu41lprLl0IGEUnnMx/TeQO0zeoN2
	lNPQ==
MIME-Version: 1.0
Received: by 10.68.225.9 with SMTP id rg9mr6798524pbc.137.1339063260190; Thu,
	07 Jun 2012 03:01:00 -0700 (PDT)
Received: by 10.68.213.230 with HTTP; Thu, 7 Jun 2012 03:01:00 -0700 (PDT)
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
Date: Thu, 7 Jun 2012 17:01:00 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Ian Tobin 
X-Gm-Message-State: ALoCoQnwiK/KJP7xcq1/iu7IulykkjeChDIBy2rFEf6bliMyPHDI3EhLpDDz/veFBPEbjpeTtOsw
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 4:53 PM, Ian Tobin  wrote:
> Ian,
>
> Sorry for the delay.
>
> Im using grub.cfg with a sym link to menu.lst, I don=92t actually have gr=
ub installed on the domu.
>
> The domu will boot if I type the path to the grub.cfg or menu.lst but wil=
l not automatically.
>
> Thanks
>
> Ian

What does your domU config file look like? Have you had success with
pv-grub on other environments (e.g xm vs xl, different xen versions,
etc)?

You need to specify the config file location on domU config file, e.g;

kernel =3D "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra =3D "(hd0,0)/grub/menu.lst"

This is from my environment on RHEL5 with xm, so it might be different
on your setup. Worth to try.

-- =

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 10:01:54 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 10:01:54 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScZWc-00017M-7f; Thu, 07 Jun 2012 10:01:06 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScZWa-00017A-CP
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 10:01:04 +0000
Received: from [85.158.138.51:17449] by server-2.bemta-3.messagelabs.com id
	15/13-16299-FDB70DF4; Thu, 07 Jun 2012 10:01:03 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-16.tower-174.messagelabs.com!1339063260!28361539!1
X-Originating-IP: [209.85.160.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19558 invoked from network); 7 Jun 2012 10:01:02 -0000
Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com)
	(209.85.160.45)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 10:01:02 -0000
Received: by pbbro12 with SMTP id ro12so903033pbb.32
	for ; Thu, 07 Jun 2012 03:01:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding:x-gm-message-state;
	bh=75pGo8/z3iLn4iRX5svjQnn7mGp6LuA1b6g0hJrq4K0=;
	b=EmvdTInDzcLnlNlmA+ZdrWE0742XHlOQBI110EATiOYosb+CfSZKe4hUzgPzGcabqz
	HTsj6ETtLqaDXC2DdbLi+/AjbAF201t7dvx/AWMuoAyYJTI1xIaheHf1BXZJUUGjNMB7
	BjXyAQ/BbbLgM41910fC0mvsANYBmbqm3lJ6yAj2XbrU4dE2twbT5YBlSVzNqDCvoHjL
	NU4p/mMVUCIDst+6VcEePQX3ZsKUKfhs/ipZ6rv1jOh2RFJbum/xBB8yiEOEFOqrpwS5
	PBnoEkY1ONJItjukFTcAKStBXCRMXGmbWFmr0+Oiu41lprLl0IGEUnnMx/TeQO0zeoN2
	lNPQ==
MIME-Version: 1.0
Received: by 10.68.225.9 with SMTP id rg9mr6798524pbc.137.1339063260190; Thu,
	07 Jun 2012 03:01:00 -0700 (PDT)
Received: by 10.68.213.230 with HTTP; Thu, 7 Jun 2012 03:01:00 -0700 (PDT)
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
Date: Thu, 7 Jun 2012 17:01:00 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Ian Tobin 
X-Gm-Message-State: ALoCoQnwiK/KJP7xcq1/iu7IulykkjeChDIBy2rFEf6bliMyPHDI3EhLpDDz/veFBPEbjpeTtOsw
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 4:53 PM, Ian Tobin  wrote:
> Ian,
>
> Sorry for the delay.
>
> Im using grub.cfg with a sym link to menu.lst, I don=92t actually have gr=
ub installed on the domu.
>
> The domu will boot if I type the path to the grub.cfg or menu.lst but wil=
l not automatically.
>
> Thanks
>
> Ian

What does your domU config file look like? Have you had success with
pv-grub on other environments (e.g xm vs xl, different xen versions,
etc)?

You need to specify the config file location on domU config file, e.g;

kernel =3D "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra =3D "(hd0,0)/grub/menu.lst"

This is from my environment on RHEL5 with xm, so it might be different
on your setup. Worth to try.

-- =

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 10:56:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 10:56: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 1ScaMt-0004Lm-W1; Thu, 07 Jun 2012 10:55:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScaMr-0004LQ-LC
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 10:55:05 +0000
Received: from [193.109.254.147:44880] by server-7.bemta-14.messagelabs.com id
	95/22-29165-88880DF4; Thu, 07 Jun 2012 10:55:04 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-5.tower-27.messagelabs.com!1339066502!6133898!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30578 invoked from network); 7 Jun 2012 10:55:03 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 10:55:03 -0000
Received: by obbwd20 with SMTP id wd20so1056930obb.32
	for ; Thu, 07 Jun 2012 03:55:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=8zZOsxiJfAEzvWhBHULk+EetGikq7aOd4oFSLa3ORSY=;
	b=j3FYg4USW/B29esN3ybvZNaUY4c2xAAi9bNaxB1MxoXPuA+zUHA007y6Vh6CC6WqmD
	FXAQF2tL6WqUEWAU2c6jWKom/LP+NirUGEk4lqYqcHBD591KjUL0mZr419jw5gDaxPiY
	ndHCx87iqKJwtN0M2YiWiJZhG35oOwDJ8oeTzpk36OUjjvNfXeOIBjT1IDoQfeBQxgY6
	Q+GAUwkpYQNxpTvJ/PZv7nF6IZZmI3fg84YKqF6LMvBZFPE590EkmWRm6ybPlFBvkxA8
	BmBCYQiaI2uQNWNzJ8hG//soY9Q5uQ1r8Q5lYR8Nvy8FTx3eXprUGENt2eKUoktCbgtw
	Uz/A==
Received: by 10.182.145.4 with SMTP id sq4mr1525978obb.76.1339066502192; Thu,
	07 Jun 2012 03:55:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 03:54:42 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
From: Rolu 
Date: Thu, 7 Jun 2012 12:54:42 +0200
Message-ID: 
To: Lars Kurth 
X-Gm-Message-State: ALoCoQlzZGWKqQHhSZnczK058N7u2BZ7T/RNYN4vnSVos9lPMMVW1NIdL2i9YHfA6swBJIUHcFHC
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 11:24 AM, Lars Kurth  wrot=
e:
> Rolu,
>
> thanks for the feedback.
>
>
>> xen" and "help with xcp" it would be nice if there were a few lines at
>> the top of the page explaining which is which, so (new) people can
>> have a better idea of where to look.
>
>
> So you mean a link to Xen and XCP from the headline, or a tagline describ=
ing
> what Xen/XCP is? Two lines are probably OK; more would probably break up =
the
> navigation too much.
>

Yeah, a tagline, as a disambiguation between Xen and XCP. I combined a
few sentences from the various pages and got this:

--
Xen is an open-source type-1 or baremetal hypervisor, which makes it
possible to run many instances of an operating system or indeed
different operating systems in parallel on a single machine (or host).
The Xen Cloud Platform (XCP) is an open source enterprise-ready server
virtualization and cloud computing platform with Xen at the core. XCP
can be thought of as the open source release of the commercial Citrix
XenServer.
See here for a [feature matrix]
--

>>
>> The descriptions from
>> http://xen.org/products/ and a link to
>> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
>> The latter is already linked in the "getting started with xen" column
>> but would be better off at the top since it gives a feature table of
>> both.
>
> I am wondering whether Xen Features / XCP Features in one of the boxes wo=
uld
> not be better.
>

That'd probably work too yes, and might look nicer to boot.

>>
>> As someone who started with Xen not long ago, I much prefer dedicated
>> link pages over Category: pages. The latter just give a big unsorted
>> (alphabetical doesn't count, needs to be sorted by subtopic to be a
>> useful sort) list of pages of widely varying scope and usefulness.
>> It's better than nothing, sure, but a page that sorts them by topic or
>> purpose or something (much like this proposed front page really) is a
>> lot better.
>
> How about a compromise? Category pages have two parts:
> 1) A fixed part that can be used for any content, such as lists of import=
ant
> articles by topic or other ciriteria
> =A0=A0=A0 An example of this is http://wiki.xen.org/wiki/Category:Host_In=
stall
> (and some of the pages linked from it)
> 2) The auto-generated index
>

That does certainly help. That way a manual list can be built while
keeping the category page, and it could replace it once it proves to
be good enough.

> I know that some people are don't like category pages. However, until
> somebody steps up and provides an alternative, which to do well requires
> a) Classifying articles
> b) Grouping them by topic or purpose
> c) Encoding that grouping in some manual index
> d) Keeping these up-to-date
>
> ... the category pages are all we have and are a lot better than what we =
had
> in the old wiki. And they are self-maintaining.
>

Especially d is an issue I think. Self maintenance is an attractive feature.

> The fact that we are having this discussion is actually good. I am open to
> suggestions and maybe we just need a small number of manually maintained
> indexes (or categories with maintained content at the top). Maybe to make
> this really work and get better navigability we need some degree of
> ownership in the wiki: i.e. community members owning content, categories,
> etc. and being responsible for classifying, grouping and making it more
> accessible.
>

I think the most important step would be to flesh out the high level
structure of the wiki a bit more. If that is done well, pages can be
put in their place much easier. The new front page starts this (xen
versus xcp, then the boxes) but the level below that is rather messy.
For example, there are howtos, FAQs, Q&As, books, guides, tutorials,
examples, overviews, and so on, with lots of overlap. These categories
are all about how the information is presented and that might be the
wrong approach. When I come to the wiki I'll have questions like "I
want to know more about how to handle disk storage" or "I want to know
how to install operating system XYZ in a domU" or "I want to know how
to switch toolstacks". I don't care if that info is found in a howto,
FAQ, book, guide, tutorial or example though, as long as I find it.
So, setting up and using categories that tell you what information is
there would help.

> I also started experimenting with shortcut boxes on pages such as
> http://wiki.xen.org/wiki/Xen_Overview &
> http://wiki.xen.org/wiki/Getting_Started and wanted to know what people
> thought of these and whether these improve navigability.
>

Yes, that helps. They would also make a good link page or category
though. For example, the box on the getting started page could be
titled "beginner documentation" or something.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 10:56:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 10:56: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 1ScaMt-0004Lm-W1; Thu, 07 Jun 2012 10:55:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScaMr-0004LQ-LC
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 10:55:05 +0000
Received: from [193.109.254.147:44880] by server-7.bemta-14.messagelabs.com id
	95/22-29165-88880DF4; Thu, 07 Jun 2012 10:55:04 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-5.tower-27.messagelabs.com!1339066502!6133898!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30578 invoked from network); 7 Jun 2012 10:55:03 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 10:55:03 -0000
Received: by obbwd20 with SMTP id wd20so1056930obb.32
	for ; Thu, 07 Jun 2012 03:55:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=8zZOsxiJfAEzvWhBHULk+EetGikq7aOd4oFSLa3ORSY=;
	b=j3FYg4USW/B29esN3ybvZNaUY4c2xAAi9bNaxB1MxoXPuA+zUHA007y6Vh6CC6WqmD
	FXAQF2tL6WqUEWAU2c6jWKom/LP+NirUGEk4lqYqcHBD591KjUL0mZr419jw5gDaxPiY
	ndHCx87iqKJwtN0M2YiWiJZhG35oOwDJ8oeTzpk36OUjjvNfXeOIBjT1IDoQfeBQxgY6
	Q+GAUwkpYQNxpTvJ/PZv7nF6IZZmI3fg84YKqF6LMvBZFPE590EkmWRm6ybPlFBvkxA8
	BmBCYQiaI2uQNWNzJ8hG//soY9Q5uQ1r8Q5lYR8Nvy8FTx3eXprUGENt2eKUoktCbgtw
	Uz/A==
Received: by 10.182.145.4 with SMTP id sq4mr1525978obb.76.1339066502192; Thu,
	07 Jun 2012 03:55:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 03:54:42 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
From: Rolu 
Date: Thu, 7 Jun 2012 12:54:42 +0200
Message-ID: 
To: Lars Kurth 
X-Gm-Message-State: ALoCoQlzZGWKqQHhSZnczK058N7u2BZ7T/RNYN4vnSVos9lPMMVW1NIdL2i9YHfA6swBJIUHcFHC
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org,
	"xen-api@lists.xen.org" 
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 11:24 AM, Lars Kurth  wrot=
e:
> Rolu,
>
> thanks for the feedback.
>
>
>> xen" and "help with xcp" it would be nice if there were a few lines at
>> the top of the page explaining which is which, so (new) people can
>> have a better idea of where to look.
>
>
> So you mean a link to Xen and XCP from the headline, or a tagline describ=
ing
> what Xen/XCP is? Two lines are probably OK; more would probably break up =
the
> navigation too much.
>

Yeah, a tagline, as a disambiguation between Xen and XCP. I combined a
few sentences from the various pages and got this:

--
Xen is an open-source type-1 or baremetal hypervisor, which makes it
possible to run many instances of an operating system or indeed
different operating systems in parallel on a single machine (or host).
The Xen Cloud Platform (XCP) is an open source enterprise-ready server
virtualization and cloud computing platform with Xen at the core. XCP
can be thought of as the open source release of the commercial Citrix
XenServer.
See here for a [feature matrix]
--

>>
>> The descriptions from
>> http://xen.org/products/ and a link to
>> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
>> The latter is already linked in the "getting started with xen" column
>> but would be better off at the top since it gives a feature table of
>> both.
>
> I am wondering whether Xen Features / XCP Features in one of the boxes wo=
uld
> not be better.
>

That'd probably work too yes, and might look nicer to boot.

>>
>> As someone who started with Xen not long ago, I much prefer dedicated
>> link pages over Category: pages. The latter just give a big unsorted
>> (alphabetical doesn't count, needs to be sorted by subtopic to be a
>> useful sort) list of pages of widely varying scope and usefulness.
>> It's better than nothing, sure, but a page that sorts them by topic or
>> purpose or something (much like this proposed front page really) is a
>> lot better.
>
> How about a compromise? Category pages have two parts:
> 1) A fixed part that can be used for any content, such as lists of import=
ant
> articles by topic or other ciriteria
> =A0=A0=A0 An example of this is http://wiki.xen.org/wiki/Category:Host_In=
stall
> (and some of the pages linked from it)
> 2) The auto-generated index
>

That does certainly help. That way a manual list can be built while
keeping the category page, and it could replace it once it proves to
be good enough.

> I know that some people are don't like category pages. However, until
> somebody steps up and provides an alternative, which to do well requires
> a) Classifying articles
> b) Grouping them by topic or purpose
> c) Encoding that grouping in some manual index
> d) Keeping these up-to-date
>
> ... the category pages are all we have and are a lot better than what we =
had
> in the old wiki. And they are self-maintaining.
>

Especially d is an issue I think. Self maintenance is an attractive feature.

> The fact that we are having this discussion is actually good. I am open to
> suggestions and maybe we just need a small number of manually maintained
> indexes (or categories with maintained content at the top). Maybe to make
> this really work and get better navigability we need some degree of
> ownership in the wiki: i.e. community members owning content, categories,
> etc. and being responsible for classifying, grouping and making it more
> accessible.
>

I think the most important step would be to flesh out the high level
structure of the wiki a bit more. If that is done well, pages can be
put in their place much easier. The new front page starts this (xen
versus xcp, then the boxes) but the level below that is rather messy.
For example, there are howtos, FAQs, Q&As, books, guides, tutorials,
examples, overviews, and so on, with lots of overlap. These categories
are all about how the information is presented and that might be the
wrong approach. When I come to the wiki I'll have questions like "I
want to know more about how to handle disk storage" or "I want to know
how to install operating system XYZ in a domU" or "I want to know how
to switch toolstacks". I don't care if that info is found in a howto,
FAQ, book, guide, tutorial or example though, as long as I find it.
So, setting up and using categories that tell you what information is
there would help.

> I also started experimenting with shortcut boxes on pages such as
> http://wiki.xen.org/wiki/Xen_Overview &
> http://wiki.xen.org/wiki/Getting_Started and wanted to know what people
> thought of these and whether these improve navigability.
>

Yes, that helps. They would also make a good link page or category
though. For example, the box on the getting started page could be
titled "beginner documentation" or something.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 11:28:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 11:28:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Scari-0005hw-8G; Thu, 07 Jun 2012 11:26:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scarh-0005hm-J5
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 11:26:57 +0000
Received: from [193.109.254.147:54846] by server-10.bemta-14.messagelabs.com
	id 97/3B-25709-00090DF4; Thu, 07 Jun 2012 11:26:56 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1339068415!8586307!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDE0Nzk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 732 invoked from network); 7 Jun 2012 11:26:55 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 11:26:55 -0000
X-IronPort-AV: E=Sophos;i="4.75,730,1330905600"; d="scan'208";a="12879146"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	07 Jun 2012 11:26:47 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 7 Jun 2012
	12:26:47 +0100
Message-ID: <1339068405.18523.4.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Ian Tobin 
Date: Thu, 7 Jun 2012 12:26:45 +0100
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gVGh1LCAyMDEyLTA2LTA3IGF0IDEwOjUzICswMTAwLCBJYW4gVG9iaW4gd3JvdGU6Cj4gSWFu
LAo+IAo+IFNvcnJ5IGZvciB0aGUgZGVsYXkuCj4gCj4gSW0gdXNpbmcgZ3J1Yi5jZmcgd2l0aCBh
IHN5bSBsaW5rIHRvIG1lbnUubHN0LCBJIGRvbuKAmXQgYWN0dWFsbHkgaGF2ZSBncnViIGluc3Rh
bGxlZCBvbiB0aGUgZG9tdS4KCkRvbid0IGdydWIuY2ZnIGFuZCBtZW51LmxzdCBoYXZlIGRpZmZl
cmVudCBzeW50YXg/IEkgd291bGQgaGF2ZSB0aG91Z2h0CnRoYXQgc3ltbGluayB3b3VsZCBjb25m
dXNlIHNvbWV0aGluZyBzb21ld2hlcmUuLi4KCj4gVGhlIGRvbXUgd2lsbCBib290IGlmIEkgdHlw
ZSB0aGUgcGF0aCB0byB0aGUgZ3J1Yi5jZmcgb3IgbWVudS5sc3QgYnV0IHdpbGwgbm90IGF1dG9t
YXRpY2FsbHkuCgpXaGF0IGlzIHRoZSBwYXRoIHdoaWNoIHlvdSBoYXZlIHRvIHR5cGU/IFdoYXQg
aXMgdGhlIHBhdGggd2l0aGluIHRoZQpndWVzdD8gQXJlIHRoZXJlIGFueSBtb3VudCBwb2ludHMg
KGUuZy4gL2Jvb3QpIGFsb25nIHRoYXQgcGF0aD8KCklhbi4KCj4gCj4gVGhhbmtzCj4gCj4gSWFu
Cj4gCj4gCj4gCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiBJYW4gQ2FtcGJl
bGwgW21haWx0bzpJYW4uQ2FtcGJlbGxAY2l0cml4LmNvbV0gCj4gU2VudDogMjIgTWF5IDIwMTIg
MDk6NDcKPiBUbzogSWFuIFRvYmluCj4gQ2M6IHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCj4gU3Vi
amVjdDogUmU6IFtYZW4tdXNlcnNdIFB2Z3J1YiBvbiBEZWJpYW4gZG9tMAo+IAo+IE9uIE1vbiwg
MjAxMi0wNS0yMSBhdCAxODo1NyArMDEwMCwgSWFuIFRvYmluIHdyb3RlOgo+ID4gSGksCj4gPiAK
PiA+IEhhdmluZyBhIHByb2JsZW0gZ2V0dGluZyBhIGRvbXUgdG8gYm9vdCBjb3JyZWN0bHkuCj4g
PiAKPiA+IFdoZW4gSSBlbnRlciB4bCBjcmVhdGUgZ3Vlc3QgaXQgYm9vdHMgc3RyYWlnaHQgaW50
byBncnViZG9tLgo+ID4gCj4gPiBJZiBJIGVudGVyIHRoZSBjb25maWcgbG9jYXRpb24gaW4gZ3J1
YmRvbSB0IGJvb3RzIGFzIGV4cGVjdGVkLgo+ID4gCj4gPiBUaGUgbG9jYXRpb24gb2YgdGhlIGdy
dWIuY2ZnIGlzIHRoZSBzYW1lIGluIG15IGRvbXUgY29uZmlnIGFzIHdoYXQgaW4gZW50ZXJpbmcg
YnV0IGp1c3Qgd2lsbCBub3Qgd29yay4KPiAKPiBncnViLmNmZyBpcyB0aGUgZ3J1YjIgZmlsZSwg
d2hlcmVhcyBwdmdydWIgaXMgY3VycmVudGx5IGdydWIxIChzb21ldGltZXMgY2FsbGVkIGdydWIg
bGVnYWN5KS4gQm90aCB0aGUgc3ludGF4IGFuZCB0aGUgbG9jYXRpb24gb2YgdGhlIGNvbmZpZyBm
aWxlIGRpZmZlcnMgYmV0d2VlbiB0aGUgdHdvIHZlcnNpb25zIG9mIGdydWIuCj4gCj4gSSdtIG5v
dCBzdXJlIGlmIGFueW9uZSBpcyB3b3JraW5nIG9uIHB2Z3J1YjIsIEkgdGhvdWdodCBJJ2QgaGVh
cmQgYSBydW1vdXIgb2YgaXQuCj4gCj4gVGhlcmUgaXMgYSB0b29sLCBwdi1ncnViLW1lbnUubHN0
LCB3aGljaCBoYXMgYmVlbiBwcm9wb3NlZCBmb3IgRGViaWFuWzBdIHdoaWNoIGhlbHBzIHlvdSBj
cmVhdGUgYW5kIG1hbmFnZSBhIGxlZ2FjeSBzdHlsZSBtZW51LmxzdC4KPiAKPiBJIHRoaW5rIGdy
dWItbGVnYWN5IGlzIGFsc28gc3RpbGwgaW4gRGViaWFuLCBidXQgeW91IG1pZ2h0IG5lZWQgdG8g
ZXhwbGljaXRseSBpbnN0YWxsIGl0IHJhdGhlciB0aGFuIGdydWIyLgo+IAo+IElhbi4KPiAKPiBb
MF0gaHR0cDovL2J1Z3MuZGViaWFuLm9yZy82NzIxMDQKPiAKPiAKPiA+IAo+ID4gQW55IGlkZWFz
Pwo+ID4gCj4gPiBJYW4KPiA+IC4KPiA+IAo+ID4gCj4gPiAKPiA+ICAKPiA+IAo+ID4gCj4gPiAK
PiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gPiBY
ZW4tdXNlcnMgbWFpbGluZyBsaXN0Cj4gPiBYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwo+ID4gaHR0
cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJzCj4gCj4gCj4gCgoKCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVu
LXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Thu Jun 07 11:28:07 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 11:28:07 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Scari-0005hw-8G; Thu, 07 Jun 2012 11:26:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scarh-0005hm-J5
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 11:26:57 +0000
Received: from [193.109.254.147:54846] by server-10.bemta-14.messagelabs.com
	id 97/3B-25709-00090DF4; Thu, 07 Jun 2012 11:26:56 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1339068415!8586307!1
X-Originating-IP: [62.200.22.115]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDE0Nzk=\n
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 732 invoked from network); 7 Jun 2012 11:26:55 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 11:26:55 -0000
X-IronPort-AV: E=Sophos;i="4.75,730,1330905600"; d="scan'208";a="12879146"
Received: from lonpmailmx01.citrite.net ([10.30.203.162])
	by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5;
	07 Jun 2012 11:26:47 +0000
Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net
	(10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 7 Jun 2012
	12:26:47 +0100
Message-ID: <1339068405.18523.4.camel@zakaz.uk.xensource.com>
From: Ian Campbell 
To: Ian Tobin 
Date: Thu, 7 Jun 2012 12:26:45 +0100
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.2.2-1 
MIME-Version: 1.0
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gVGh1LCAyMDEyLTA2LTA3IGF0IDEwOjUzICswMTAwLCBJYW4gVG9iaW4gd3JvdGU6Cj4gSWFu
LAo+IAo+IFNvcnJ5IGZvciB0aGUgZGVsYXkuCj4gCj4gSW0gdXNpbmcgZ3J1Yi5jZmcgd2l0aCBh
IHN5bSBsaW5rIHRvIG1lbnUubHN0LCBJIGRvbuKAmXQgYWN0dWFsbHkgaGF2ZSBncnViIGluc3Rh
bGxlZCBvbiB0aGUgZG9tdS4KCkRvbid0IGdydWIuY2ZnIGFuZCBtZW51LmxzdCBoYXZlIGRpZmZl
cmVudCBzeW50YXg/IEkgd291bGQgaGF2ZSB0aG91Z2h0CnRoYXQgc3ltbGluayB3b3VsZCBjb25m
dXNlIHNvbWV0aGluZyBzb21ld2hlcmUuLi4KCj4gVGhlIGRvbXUgd2lsbCBib290IGlmIEkgdHlw
ZSB0aGUgcGF0aCB0byB0aGUgZ3J1Yi5jZmcgb3IgbWVudS5sc3QgYnV0IHdpbGwgbm90IGF1dG9t
YXRpY2FsbHkuCgpXaGF0IGlzIHRoZSBwYXRoIHdoaWNoIHlvdSBoYXZlIHRvIHR5cGU/IFdoYXQg
aXMgdGhlIHBhdGggd2l0aGluIHRoZQpndWVzdD8gQXJlIHRoZXJlIGFueSBtb3VudCBwb2ludHMg
KGUuZy4gL2Jvb3QpIGFsb25nIHRoYXQgcGF0aD8KCklhbi4KCj4gCj4gVGhhbmtzCj4gCj4gSWFu
Cj4gCj4gCj4gCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiBJYW4gQ2FtcGJl
bGwgW21haWx0bzpJYW4uQ2FtcGJlbGxAY2l0cml4LmNvbV0gCj4gU2VudDogMjIgTWF5IDIwMTIg
MDk6NDcKPiBUbzogSWFuIFRvYmluCj4gQ2M6IHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCj4gU3Vi
amVjdDogUmU6IFtYZW4tdXNlcnNdIFB2Z3J1YiBvbiBEZWJpYW4gZG9tMAo+IAo+IE9uIE1vbiwg
MjAxMi0wNS0yMSBhdCAxODo1NyArMDEwMCwgSWFuIFRvYmluIHdyb3RlOgo+ID4gSGksCj4gPiAK
PiA+IEhhdmluZyBhIHByb2JsZW0gZ2V0dGluZyBhIGRvbXUgdG8gYm9vdCBjb3JyZWN0bHkuCj4g
PiAKPiA+IFdoZW4gSSBlbnRlciB4bCBjcmVhdGUgZ3Vlc3QgaXQgYm9vdHMgc3RyYWlnaHQgaW50
byBncnViZG9tLgo+ID4gCj4gPiBJZiBJIGVudGVyIHRoZSBjb25maWcgbG9jYXRpb24gaW4gZ3J1
YmRvbSB0IGJvb3RzIGFzIGV4cGVjdGVkLgo+ID4gCj4gPiBUaGUgbG9jYXRpb24gb2YgdGhlIGdy
dWIuY2ZnIGlzIHRoZSBzYW1lIGluIG15IGRvbXUgY29uZmlnIGFzIHdoYXQgaW4gZW50ZXJpbmcg
YnV0IGp1c3Qgd2lsbCBub3Qgd29yay4KPiAKPiBncnViLmNmZyBpcyB0aGUgZ3J1YjIgZmlsZSwg
d2hlcmVhcyBwdmdydWIgaXMgY3VycmVudGx5IGdydWIxIChzb21ldGltZXMgY2FsbGVkIGdydWIg
bGVnYWN5KS4gQm90aCB0aGUgc3ludGF4IGFuZCB0aGUgbG9jYXRpb24gb2YgdGhlIGNvbmZpZyBm
aWxlIGRpZmZlcnMgYmV0d2VlbiB0aGUgdHdvIHZlcnNpb25zIG9mIGdydWIuCj4gCj4gSSdtIG5v
dCBzdXJlIGlmIGFueW9uZSBpcyB3b3JraW5nIG9uIHB2Z3J1YjIsIEkgdGhvdWdodCBJJ2QgaGVh
cmQgYSBydW1vdXIgb2YgaXQuCj4gCj4gVGhlcmUgaXMgYSB0b29sLCBwdi1ncnViLW1lbnUubHN0
LCB3aGljaCBoYXMgYmVlbiBwcm9wb3NlZCBmb3IgRGViaWFuWzBdIHdoaWNoIGhlbHBzIHlvdSBj
cmVhdGUgYW5kIG1hbmFnZSBhIGxlZ2FjeSBzdHlsZSBtZW51LmxzdC4KPiAKPiBJIHRoaW5rIGdy
dWItbGVnYWN5IGlzIGFsc28gc3RpbGwgaW4gRGViaWFuLCBidXQgeW91IG1pZ2h0IG5lZWQgdG8g
ZXhwbGljaXRseSBpbnN0YWxsIGl0IHJhdGhlciB0aGFuIGdydWIyLgo+IAo+IElhbi4KPiAKPiBb
MF0gaHR0cDovL2J1Z3MuZGViaWFuLm9yZy82NzIxMDQKPiAKPiAKPiA+IAo+ID4gQW55IGlkZWFz
Pwo+ID4gCj4gPiBJYW4KPiA+IC4KPiA+IAo+ID4gCj4gPiAKPiA+ICAKPiA+IAo+ID4gCj4gPiAK
PiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gPiBY
ZW4tdXNlcnMgbWFpbGluZyBsaXN0Cj4gPiBYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwo+ID4gaHR0
cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJzCj4gCj4gCj4gCgoKCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVu
LXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Thu Jun 07 13:05:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:05: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 1SccNk-0000uJ-W9; Thu, 07 Jun 2012 13:04:08 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccNj-0000uE-6m
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:04:07 +0000
Received: from [85.158.143.99:38992] by server-3.bemta-4.messagelabs.com id
	2D/41-29237-6C6A0DF4; Thu, 07 Jun 2012 13:04:06 +0000
X-Env-Sender: itobin@tidyhosts.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1339074245!28377399!1
X-Originating-IP: [83.142.228.126]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13241 invoked from network); 7 Jun 2012 13:04:05 -0000
Received: from london.tidyhosts.com (HELO tidyhosts.com) (83.142.228.126)
	by server-7.tower-216.messagelabs.com with SMTP;
	7 Jun 2012 13:04:05 -0000
Received: from electron.tidyhosts.com ([213.152.51.27]) by tidyhosts.com with
	MailEnable ESMTP; Thu, 7 Jun 2012 14:04:04 +0100
MIME-Version: 1.0
Date: Thu, 7 Jun 2012 14:03:12 +0100
Content-class: urn:content-classes:message
Message-ID: <039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: [Xen-users] Pvgrub on Debian dom0
Thread-Index: Ac1EoHWQWgJr6jqjThSkMox1uBqMOQADQWJA
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
	<1339068405.18523.4.camel@zakaz.uk.xensource.com>
From: "Ian Tobin" 
To: "Ian Campbell" ,
	
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SWFuLCBGYWphciwNCg0KVGhpcyBpcyBteSBjb25maWcNCg0KIyAgLSotIG1vZGU6IHB5dGhvbjsg
LSotDQprZXJuZWwgPSAiL3Vzci9saWIveGVuL2Jvb3QvcHYtZ3J1Yi14ODZfMzIuZ3oiDQoNCm1l
bW9yeSA9IDUxMg0KbmFtZSA9ICJ0ZXN0bGludXgiDQoNCnZpZiA9IFsnYnJpZGdlPXhlbmJyMCcg
XQ0KDQpkaXNrID0gWydwaHk6L2Rldi9YRU4vdGVzdGxpbnV4LHh2ZGEsdycsJ3BoeTovZGV2L1hF
Ti90ZXN0bGludXhzd2FwLHh2ZGIsdyddDQoNCmlwPSIxNzIuMjAuNDUuMTAiDQpuZXRtYXNrPSIy
NTUuMjU1LjAuMCINCmdhdGV3YXk9IjE3Mi4yMC4wLjEiDQpob3N0bmFtZSA9ICJ0ZXN0bGludXgi
DQogDQpleHRyYSA9ICIoaGQwKS9ib290L2dydWIvbWVudS5sc3QiDQp2Y3B1cyA9IDENCg0KDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBJYW4gQ2FtcGJlbGwgW21haWx0bzpJ
YW4uQ2FtcGJlbGxAY2l0cml4LmNvbV0gDQpTZW50OiAwNyBKdW5lIDIwMTIgMTI6MjcNClRvOiBJ
YW4gVG9iaW4NCkNjOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9yZw0KU3ViamVjdDogUkU6IFtYZW4t
dXNlcnNdIFB2Z3J1YiBvbiBEZWJpYW4gZG9tMA0KDQpPbiBUaHUsIDIwMTItMDYtMDcgYXQgMTA6
NTMgKzAxMDAsIElhbiBUb2JpbiB3cm90ZToNCj4gSWFuLA0KPiANCj4gU29ycnkgZm9yIHRoZSBk
ZWxheS4NCj4gDQo+IEltIHVzaW5nIGdydWIuY2ZnIHdpdGggYSBzeW0gbGluayB0byBtZW51Lmxz
dCwgSSBkb27igJl0IGFjdHVhbGx5IGhhdmUgZ3J1YiBpbnN0YWxsZWQgb24gdGhlIGRvbXUuDQoN
CkRvbid0IGdydWIuY2ZnIGFuZCBtZW51LmxzdCBoYXZlIGRpZmZlcmVudCBzeW50YXg/IEkgd291
bGQgaGF2ZSB0aG91Z2h0IHRoYXQgc3ltbGluayB3b3VsZCBjb25mdXNlIHNvbWV0aGluZyBzb21l
d2hlcmUuLi4NCg0KPiBUaGUgZG9tdSB3aWxsIGJvb3QgaWYgSSB0eXBlIHRoZSBwYXRoIHRvIHRo
ZSBncnViLmNmZyBvciBtZW51LmxzdCBidXQgd2lsbCBub3QgYXV0b21hdGljYWxseS4NCg0KV2hh
dCBpcyB0aGUgcGF0aCB3aGljaCB5b3UgaGF2ZSB0byB0eXBlPyBXaGF0IGlzIHRoZSBwYXRoIHdp
dGhpbiB0aGUgZ3Vlc3Q/IEFyZSB0aGVyZSBhbnkgbW91bnQgcG9pbnRzIChlLmcuIC9ib290KSBh
bG9uZyB0aGF0IHBhdGg/DQoNCklhbi4NCg0KPiANCj4gVGhhbmtzDQo+IA0KPiBJYW4NCj4gDQo+
IA0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSWFuIENhbXBiZWxs
IFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dDQo+IFNlbnQ6IDIyIE1heSAyMDEyIDA5
OjQ3DQo+IFRvOiBJYW4gVG9iaW4NCj4gQ2M6IHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQo+IFN1
YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBQdmdydWIgb24gRGViaWFuIGRvbTANCj4gDQo+IE9uIE1v
biwgMjAxMi0wNS0yMSBhdCAxODo1NyArMDEwMCwgSWFuIFRvYmluIHdyb3RlOg0KPiA+IEhpLA0K
PiA+IA0KPiA+IEhhdmluZyBhIHByb2JsZW0gZ2V0dGluZyBhIGRvbXUgdG8gYm9vdCBjb3JyZWN0
bHkuDQo+ID4gDQo+ID4gV2hlbiBJIGVudGVyIHhsIGNyZWF0ZSBndWVzdCBpdCBib290cyBzdHJh
aWdodCBpbnRvIGdydWJkb20uDQo+ID4gDQo+ID4gSWYgSSBlbnRlciB0aGUgY29uZmlnIGxvY2F0
aW9uIGluIGdydWJkb20gdCBib290cyBhcyBleHBlY3RlZC4NCj4gPiANCj4gPiBUaGUgbG9jYXRp
b24gb2YgdGhlIGdydWIuY2ZnIGlzIHRoZSBzYW1lIGluIG15IGRvbXUgY29uZmlnIGFzIHdoYXQg
aW4gZW50ZXJpbmcgYnV0IGp1c3Qgd2lsbCBub3Qgd29yay4NCj4gDQo+IGdydWIuY2ZnIGlzIHRo
ZSBncnViMiBmaWxlLCB3aGVyZWFzIHB2Z3J1YiBpcyBjdXJyZW50bHkgZ3J1YjEgKHNvbWV0aW1l
cyBjYWxsZWQgZ3J1YiBsZWdhY3kpLiBCb3RoIHRoZSBzeW50YXggYW5kIHRoZSBsb2NhdGlvbiBv
ZiB0aGUgY29uZmlnIGZpbGUgZGlmZmVycyBiZXR3ZWVuIHRoZSB0d28gdmVyc2lvbnMgb2YgZ3J1
Yi4NCj4gDQo+IEknbSBub3Qgc3VyZSBpZiBhbnlvbmUgaXMgd29ya2luZyBvbiBwdmdydWIyLCBJ
IHRob3VnaHQgSSdkIGhlYXJkIGEgcnVtb3VyIG9mIGl0Lg0KPiANCj4gVGhlcmUgaXMgYSB0b29s
LCBwdi1ncnViLW1lbnUubHN0LCB3aGljaCBoYXMgYmVlbiBwcm9wb3NlZCBmb3IgRGViaWFuWzBd
IHdoaWNoIGhlbHBzIHlvdSBjcmVhdGUgYW5kIG1hbmFnZSBhIGxlZ2FjeSBzdHlsZSBtZW51Lmxz
dC4NCj4gDQo+IEkgdGhpbmsgZ3J1Yi1sZWdhY3kgaXMgYWxzbyBzdGlsbCBpbiBEZWJpYW4sIGJ1
dCB5b3UgbWlnaHQgbmVlZCB0byBleHBsaWNpdGx5IGluc3RhbGwgaXQgcmF0aGVyIHRoYW4gZ3J1
YjIuDQo+IA0KPiBJYW4uDQo+IA0KPiBbMF0gaHR0cDovL2J1Z3MuZGViaWFuLm9yZy82NzIxMDQN
Cj4gDQo+IA0KPiA+IA0KPiA+IEFueSBpZGVhcz8NCj4gPiANCj4gPiBJYW4NCj4gPiAuDQo+ID4g
DQo+ID4gDQo+ID4gDQo+ID4gIA0KPiA+IA0KPiA+IA0KPiA+IA0KPiA+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gWGVuLXVzZXJzIG1haWxpbmcg
bGlzdA0KPiA+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQo+ID4gaHR0cDovL2xpc3RzLnhlbi5v
cmcveGVuLXVzZXJzDQo+IA0KPiANCj4gDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0Bs
aXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Thu Jun 07 13:05:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:05: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 1SccNk-0000uJ-W9; Thu, 07 Jun 2012 13:04:08 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccNj-0000uE-6m
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:04:07 +0000
Received: from [85.158.143.99:38992] by server-3.bemta-4.messagelabs.com id
	2D/41-29237-6C6A0DF4; Thu, 07 Jun 2012 13:04:06 +0000
X-Env-Sender: itobin@tidyhosts.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1339074245!28377399!1
X-Originating-IP: [83.142.228.126]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13241 invoked from network); 7 Jun 2012 13:04:05 -0000
Received: from london.tidyhosts.com (HELO tidyhosts.com) (83.142.228.126)
	by server-7.tower-216.messagelabs.com with SMTP;
	7 Jun 2012 13:04:05 -0000
Received: from electron.tidyhosts.com ([213.152.51.27]) by tidyhosts.com with
	MailEnable ESMTP; Thu, 7 Jun 2012 14:04:04 +0100
MIME-Version: 1.0
Date: Thu, 7 Jun 2012 14:03:12 +0100
Content-class: urn:content-classes:message
Message-ID: <039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: [Xen-users] Pvgrub on Debian dom0
Thread-Index: Ac1EoHWQWgJr6jqjThSkMox1uBqMOQADQWJA
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
	<1339068405.18523.4.camel@zakaz.uk.xensource.com>
From: "Ian Tobin" 
To: "Ian Campbell" ,
	
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SWFuLCBGYWphciwNCg0KVGhpcyBpcyBteSBjb25maWcNCg0KIyAgLSotIG1vZGU6IHB5dGhvbjsg
LSotDQprZXJuZWwgPSAiL3Vzci9saWIveGVuL2Jvb3QvcHYtZ3J1Yi14ODZfMzIuZ3oiDQoNCm1l
bW9yeSA9IDUxMg0KbmFtZSA9ICJ0ZXN0bGludXgiDQoNCnZpZiA9IFsnYnJpZGdlPXhlbmJyMCcg
XQ0KDQpkaXNrID0gWydwaHk6L2Rldi9YRU4vdGVzdGxpbnV4LHh2ZGEsdycsJ3BoeTovZGV2L1hF
Ti90ZXN0bGludXhzd2FwLHh2ZGIsdyddDQoNCmlwPSIxNzIuMjAuNDUuMTAiDQpuZXRtYXNrPSIy
NTUuMjU1LjAuMCINCmdhdGV3YXk9IjE3Mi4yMC4wLjEiDQpob3N0bmFtZSA9ICJ0ZXN0bGludXgi
DQogDQpleHRyYSA9ICIoaGQwKS9ib290L2dydWIvbWVudS5sc3QiDQp2Y3B1cyA9IDENCg0KDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBJYW4gQ2FtcGJlbGwgW21haWx0bzpJ
YW4uQ2FtcGJlbGxAY2l0cml4LmNvbV0gDQpTZW50OiAwNyBKdW5lIDIwMTIgMTI6MjcNClRvOiBJ
YW4gVG9iaW4NCkNjOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9yZw0KU3ViamVjdDogUkU6IFtYZW4t
dXNlcnNdIFB2Z3J1YiBvbiBEZWJpYW4gZG9tMA0KDQpPbiBUaHUsIDIwMTItMDYtMDcgYXQgMTA6
NTMgKzAxMDAsIElhbiBUb2JpbiB3cm90ZToNCj4gSWFuLA0KPiANCj4gU29ycnkgZm9yIHRoZSBk
ZWxheS4NCj4gDQo+IEltIHVzaW5nIGdydWIuY2ZnIHdpdGggYSBzeW0gbGluayB0byBtZW51Lmxz
dCwgSSBkb27igJl0IGFjdHVhbGx5IGhhdmUgZ3J1YiBpbnN0YWxsZWQgb24gdGhlIGRvbXUuDQoN
CkRvbid0IGdydWIuY2ZnIGFuZCBtZW51LmxzdCBoYXZlIGRpZmZlcmVudCBzeW50YXg/IEkgd291
bGQgaGF2ZSB0aG91Z2h0IHRoYXQgc3ltbGluayB3b3VsZCBjb25mdXNlIHNvbWV0aGluZyBzb21l
d2hlcmUuLi4NCg0KPiBUaGUgZG9tdSB3aWxsIGJvb3QgaWYgSSB0eXBlIHRoZSBwYXRoIHRvIHRo
ZSBncnViLmNmZyBvciBtZW51LmxzdCBidXQgd2lsbCBub3QgYXV0b21hdGljYWxseS4NCg0KV2hh
dCBpcyB0aGUgcGF0aCB3aGljaCB5b3UgaGF2ZSB0byB0eXBlPyBXaGF0IGlzIHRoZSBwYXRoIHdp
dGhpbiB0aGUgZ3Vlc3Q/IEFyZSB0aGVyZSBhbnkgbW91bnQgcG9pbnRzIChlLmcuIC9ib290KSBh
bG9uZyB0aGF0IHBhdGg/DQoNCklhbi4NCg0KPiANCj4gVGhhbmtzDQo+IA0KPiBJYW4NCj4gDQo+
IA0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSWFuIENhbXBiZWxs
IFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dDQo+IFNlbnQ6IDIyIE1heSAyMDEyIDA5
OjQ3DQo+IFRvOiBJYW4gVG9iaW4NCj4gQ2M6IHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQo+IFN1
YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBQdmdydWIgb24gRGViaWFuIGRvbTANCj4gDQo+IE9uIE1v
biwgMjAxMi0wNS0yMSBhdCAxODo1NyArMDEwMCwgSWFuIFRvYmluIHdyb3RlOg0KPiA+IEhpLA0K
PiA+IA0KPiA+IEhhdmluZyBhIHByb2JsZW0gZ2V0dGluZyBhIGRvbXUgdG8gYm9vdCBjb3JyZWN0
bHkuDQo+ID4gDQo+ID4gV2hlbiBJIGVudGVyIHhsIGNyZWF0ZSBndWVzdCBpdCBib290cyBzdHJh
aWdodCBpbnRvIGdydWJkb20uDQo+ID4gDQo+ID4gSWYgSSBlbnRlciB0aGUgY29uZmlnIGxvY2F0
aW9uIGluIGdydWJkb20gdCBib290cyBhcyBleHBlY3RlZC4NCj4gPiANCj4gPiBUaGUgbG9jYXRp
b24gb2YgdGhlIGdydWIuY2ZnIGlzIHRoZSBzYW1lIGluIG15IGRvbXUgY29uZmlnIGFzIHdoYXQg
aW4gZW50ZXJpbmcgYnV0IGp1c3Qgd2lsbCBub3Qgd29yay4NCj4gDQo+IGdydWIuY2ZnIGlzIHRo
ZSBncnViMiBmaWxlLCB3aGVyZWFzIHB2Z3J1YiBpcyBjdXJyZW50bHkgZ3J1YjEgKHNvbWV0aW1l
cyBjYWxsZWQgZ3J1YiBsZWdhY3kpLiBCb3RoIHRoZSBzeW50YXggYW5kIHRoZSBsb2NhdGlvbiBv
ZiB0aGUgY29uZmlnIGZpbGUgZGlmZmVycyBiZXR3ZWVuIHRoZSB0d28gdmVyc2lvbnMgb2YgZ3J1
Yi4NCj4gDQo+IEknbSBub3Qgc3VyZSBpZiBhbnlvbmUgaXMgd29ya2luZyBvbiBwdmdydWIyLCBJ
IHRob3VnaHQgSSdkIGhlYXJkIGEgcnVtb3VyIG9mIGl0Lg0KPiANCj4gVGhlcmUgaXMgYSB0b29s
LCBwdi1ncnViLW1lbnUubHN0LCB3aGljaCBoYXMgYmVlbiBwcm9wb3NlZCBmb3IgRGViaWFuWzBd
IHdoaWNoIGhlbHBzIHlvdSBjcmVhdGUgYW5kIG1hbmFnZSBhIGxlZ2FjeSBzdHlsZSBtZW51Lmxz
dC4NCj4gDQo+IEkgdGhpbmsgZ3J1Yi1sZWdhY3kgaXMgYWxzbyBzdGlsbCBpbiBEZWJpYW4sIGJ1
dCB5b3UgbWlnaHQgbmVlZCB0byBleHBsaWNpdGx5IGluc3RhbGwgaXQgcmF0aGVyIHRoYW4gZ3J1
YjIuDQo+IA0KPiBJYW4uDQo+IA0KPiBbMF0gaHR0cDovL2J1Z3MuZGViaWFuLm9yZy82NzIxMDQN
Cj4gDQo+IA0KPiA+IA0KPiA+IEFueSBpZGVhcz8NCj4gPiANCj4gPiBJYW4NCj4gPiAuDQo+ID4g
DQo+ID4gDQo+ID4gDQo+ID4gIA0KPiA+IA0KPiA+IA0KPiA+IA0KPiA+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gWGVuLXVzZXJzIG1haWxpbmcg
bGlzdA0KPiA+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnDQo+ID4gaHR0cDovL2xpc3RzLnhlbi5v
cmcveGVuLXVzZXJzDQo+IA0KPiANCj4gDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0Bs
aXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Thu Jun 07 13:15:56 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:15: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 1SccY3-0001KT-St; Thu, 07 Jun 2012 13:14:47 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccY2-0001Jy-JR
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:14:46 +0000
Received: from [85.158.139.83:15513] by server-6.bemta-5.messagelabs.com id
	26/2A-18700-449A0DF4; Thu, 07 Jun 2012 13:14:44 +0000
X-Env-Sender: dunlapg@gmail.com
X-Msg-Ref: server-14.tower-182.messagelabs.com!1339074882!28190265!1
X-Originating-IP: [209.85.216.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6687 invoked from network); 7 Jun 2012 13:14:43 -0000
Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com)
	(209.85.216.45)
	by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 13:14:43 -0000
Received: by qaeb19 with SMTP id b19so122644qae.11
	for ; Thu, 07 Jun 2012 06:14:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=e9TSWflGY7t9BEJAN1WDekuzfXqvwYy2apIGRWkLddQ=;
	b=PUE1se8v0Ch8Lr60prDEsDQ3ygVUo6oFT4FaMAx7mDiWTCvx+Z5+N9n9Iwnh8sC2ZG
	8WKNiPe3ZmKMKjak7ovEnU1+XydhO/2Ic0FObURDN60OxlpFkNrAAju1IOCqmRc8D6ea
	YnAuMq7d2FINuuOQvjrABQMW8zHP4x+ntEzeFVetOkbJPyvKScOkutWBrRNDljbZLcDy
	yMtCr8I4Oc2+KSU8RqkoFwJdYokcuEjpeKr/tPwCG0hPmZdmjX53AxideGmTWROGiLRW
	3TM51Xbou3qQgzaXdBK3TfmTKsxJG0wRrRvBFigYRtauD8eL8YymahcnExdu7TQCFM+m
	JxHQ==
MIME-Version: 1.0
Received: by 10.224.206.198 with SMTP id fv6mr2775401qab.6.1339074881893; Thu,
	07 Jun 2012 06:14:41 -0700 (PDT)
Received: by 10.229.47.140 with HTTP; Thu, 7 Jun 2012 06:14:41 -0700 (PDT)
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
Date: Thu, 7 Jun 2012 14:14:41 +0100
X-Google-Sender-Auth: fKAPQrfr9wpw1pt8PgqIuuQc40U
Message-ID: 
From: George Dunlap 
To: Lars Kurth 
Cc: Rolu , xen-users@lists.xen.org,
	"xen-api@lists.xen.org" , xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 10:24 AM, Lars Kurth  wrot=
e:
> Rolu,
>
> thanks for the feedback.
>
>
>> xen" and "help with xcp" it would be nice if there were a few lines at
>> the top of the page explaining which is which, so (new) people can
>> have a better idea of where to look.
>
>
> So you mean a link to Xen and XCP from the headline, or a tagline describ=
ing
> what Xen/XCP is? Two lines are probably OK; more would probably break up =
the
> navigation too much.
>
>>
>> The descriptions from
>> http://xen.org/products/ and a link to
>> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
>> The latter is already linked in the "getting started with xen" column
>> but would be better off at the top since it gives a feature table of
>> both.
>
> I am wondering whether Xen Features / XCP Features in one of the boxes wo=
uld
> not be better.
>
>>
>> As someone who started with Xen not long ago, I much prefer dedicated
>> link pages over Category: pages. The latter just give a big unsorted
>> (alphabetical doesn't count, needs to be sorted by subtopic to be a
>> useful sort) list of pages of widely varying scope and usefulness.
>> It's better than nothing, sure, but a page that sorts them by topic or
>> purpose or something (much like this proposed front page really) is a
>> lot better.
>
> How about a compromise? Category pages have two parts:
> 1) A fixed part that can be used for any content, such as lists of import=
ant
> articles by topic or other ciriteria
> =A0=A0=A0 An example of this is http://wiki.xen.org/wiki/Category:Host_In=
stall
> (and some of the pages linked from it)
> 2) The auto-generated index
>
> I know that some people are don't like category pages. However, until
> somebody steps up and provides an alternative, which to do well requires
> a) Classifying articles
> b) Grouping them by topic or purpose
> c) Encoding that grouping in some manual index
> d) Keeping these up-to-date
>
> ... the category pages are all we have and are a lot better than what we =
had
> in the old wiki. And they are self-maintaining.

Sorry to throw in a criticism without a constructive solution, but I
just want to register one opinion: To me clicking on a link and seeing
a "Category" page says very strongly, "I couldn't be bothered to
actually do any work here; I'll leave you to do all the work to figure
out what page you need."  When I encounter a Category page on my walk
through the Xen wiki, I don't even look, but immediately turn to
Google.  I think a page which is has some kind of logical flow to it
but perhaps a little out-dated is much better than a page which just
tosses up a bunch of titles in no order and lets you figure it out.

I can certainly see that there were "liveness" problems with summary
pages; but I don't think that the Categories pages, as we have now,
really help that much.

> The fact that we are having this discussion is actually good. I am open to
> suggestions and maybe we just need a small number of manually maintained
> indexes (or categories with maintained content at the top). Maybe to make
> this really work and get better navigability we need some degree of
> ownership in the wiki: i.e. community members owning content, categories,
> etc. and being responsible for classifying, grouping and making it more
> accessible.

I think in an ideal world, we'd have people who were "maintainers" of
the wiki just like there are maintainers of different subsections of
the codebase.  Until that time, could we maybe draw up a set of
"tests" to run on the docs, which can be assigned to people on DocDay?
 One simple thing could be, "Make sure X page is up-to-date" (which
may include, "Look at the Category: page and make sure everything
there is listed somewhere on the manually-generated page"); another
could be a scenario, "Pretend you're a [foo] and you want to know
[bar].  Start at the top level page and make sure you can find all the
information you need."  If each "test" was something any motivated
developer/community member could do, and only took 5-10 minutes, it
should be pretty sustainable.  What do you think?

One thing that might make the Category: page more useful is if we
could include "index tags" on articles, and then sort the Category:
pages by those tags instead of by title.  But I'm not sure how easy
that is to do with the current wiki.

 -George

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 13:15:56 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:15: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 1SccY3-0001KT-St; Thu, 07 Jun 2012 13:14:47 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccY2-0001Jy-JR
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:14:46 +0000
Received: from [85.158.139.83:15513] by server-6.bemta-5.messagelabs.com id
	26/2A-18700-449A0DF4; Thu, 07 Jun 2012 13:14:44 +0000
X-Env-Sender: dunlapg@gmail.com
X-Msg-Ref: server-14.tower-182.messagelabs.com!1339074882!28190265!1
X-Originating-IP: [209.85.216.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6687 invoked from network); 7 Jun 2012 13:14:43 -0000
Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com)
	(209.85.216.45)
	by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 13:14:43 -0000
Received: by qaeb19 with SMTP id b19so122644qae.11
	for ; Thu, 07 Jun 2012 06:14:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=e9TSWflGY7t9BEJAN1WDekuzfXqvwYy2apIGRWkLddQ=;
	b=PUE1se8v0Ch8Lr60prDEsDQ3ygVUo6oFT4FaMAx7mDiWTCvx+Z5+N9n9Iwnh8sC2ZG
	8WKNiPe3ZmKMKjak7ovEnU1+XydhO/2Ic0FObURDN60OxlpFkNrAAju1IOCqmRc8D6ea
	YnAuMq7d2FINuuOQvjrABQMW8zHP4x+ntEzeFVetOkbJPyvKScOkutWBrRNDljbZLcDy
	yMtCr8I4Oc2+KSU8RqkoFwJdYokcuEjpeKr/tPwCG0hPmZdmjX53AxideGmTWROGiLRW
	3TM51Xbou3qQgzaXdBK3TfmTKsxJG0wRrRvBFigYRtauD8eL8YymahcnExdu7TQCFM+m
	JxHQ==
MIME-Version: 1.0
Received: by 10.224.206.198 with SMTP id fv6mr2775401qab.6.1339074881893; Thu,
	07 Jun 2012 06:14:41 -0700 (PDT)
Received: by 10.229.47.140 with HTTP; Thu, 7 Jun 2012 06:14:41 -0700 (PDT)
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
Date: Thu, 7 Jun 2012 14:14:41 +0100
X-Google-Sender-Auth: fKAPQrfr9wpw1pt8PgqIuuQc40U
Message-ID: 
From: George Dunlap 
To: Lars Kurth 
Cc: Rolu , xen-users@lists.xen.org,
	"xen-api@lists.xen.org" , xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 10:24 AM, Lars Kurth  wrot=
e:
> Rolu,
>
> thanks for the feedback.
>
>
>> xen" and "help with xcp" it would be nice if there were a few lines at
>> the top of the page explaining which is which, so (new) people can
>> have a better idea of where to look.
>
>
> So you mean a link to Xen and XCP from the headline, or a tagline describ=
ing
> what Xen/XCP is? Two lines are probably OK; more would probably break up =
the
> navigation too much.
>
>>
>> The descriptions from
>> http://xen.org/products/ and a link to
>> http://wiki.xen.org/wiki/Xen_/_XCP_/_XCP_on_Linux_Overview would work.
>> The latter is already linked in the "getting started with xen" column
>> but would be better off at the top since it gives a feature table of
>> both.
>
> I am wondering whether Xen Features / XCP Features in one of the boxes wo=
uld
> not be better.
>
>>
>> As someone who started with Xen not long ago, I much prefer dedicated
>> link pages over Category: pages. The latter just give a big unsorted
>> (alphabetical doesn't count, needs to be sorted by subtopic to be a
>> useful sort) list of pages of widely varying scope and usefulness.
>> It's better than nothing, sure, but a page that sorts them by topic or
>> purpose or something (much like this proposed front page really) is a
>> lot better.
>
> How about a compromise? Category pages have two parts:
> 1) A fixed part that can be used for any content, such as lists of import=
ant
> articles by topic or other ciriteria
> =A0=A0=A0 An example of this is http://wiki.xen.org/wiki/Category:Host_In=
stall
> (and some of the pages linked from it)
> 2) The auto-generated index
>
> I know that some people are don't like category pages. However, until
> somebody steps up and provides an alternative, which to do well requires
> a) Classifying articles
> b) Grouping them by topic or purpose
> c) Encoding that grouping in some manual index
> d) Keeping these up-to-date
>
> ... the category pages are all we have and are a lot better than what we =
had
> in the old wiki. And they are self-maintaining.

Sorry to throw in a criticism without a constructive solution, but I
just want to register one opinion: To me clicking on a link and seeing
a "Category" page says very strongly, "I couldn't be bothered to
actually do any work here; I'll leave you to do all the work to figure
out what page you need."  When I encounter a Category page on my walk
through the Xen wiki, I don't even look, but immediately turn to
Google.  I think a page which is has some kind of logical flow to it
but perhaps a little out-dated is much better than a page which just
tosses up a bunch of titles in no order and lets you figure it out.

I can certainly see that there were "liveness" problems with summary
pages; but I don't think that the Categories pages, as we have now,
really help that much.

> The fact that we are having this discussion is actually good. I am open to
> suggestions and maybe we just need a small number of manually maintained
> indexes (or categories with maintained content at the top). Maybe to make
> this really work and get better navigability we need some degree of
> ownership in the wiki: i.e. community members owning content, categories,
> etc. and being responsible for classifying, grouping and making it more
> accessible.

I think in an ideal world, we'd have people who were "maintainers" of
the wiki just like there are maintainers of different subsections of
the codebase.  Until that time, could we maybe draw up a set of
"tests" to run on the docs, which can be assigned to people on DocDay?
 One simple thing could be, "Make sure X page is up-to-date" (which
may include, "Look at the Category: page and make sure everything
there is listed somewhere on the manually-generated page"); another
could be a scenario, "Pretend you're a [foo] and you want to know
[bar].  Start at the top level page and make sure you can find all the
information you need."  If each "test" was something any motivated
developer/community member could do, and only took 5-10 minutes, it
should be pretty sustainable.  What do you think?

One thing that might make the Category: page more useful is if we
could include "index tags" on articles, and then sort the Category:
pages by those tags instead of by title.  But I'm not sure how easy
that is to do with the current wiki.

 -George

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 13:16:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:16: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 1SccYl-0001QO-Ng; Thu, 07 Jun 2012 13:15:31 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccYk-0001Pi-PX
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:15:30 +0000
Received: from [85.158.143.35:58843] by server-3.bemta-4.messagelabs.com id
	E6/A5-29237-279A0DF4; Thu, 07 Jun 2012 13:15:30 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-2.tower-21.messagelabs.com!1339074925!8308318!1
X-Originating-IP: [209.85.213.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6064 invoked from network); 7 Jun 2012 13:15:26 -0000
Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com)
	(209.85.213.173)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 13:15:26 -0000
Received: by yenm4 with SMTP id m4so414038yen.32
	for ; Thu, 07 Jun 2012 06:15:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:from:date:message-id:subject:to
	:content-type:x-gm-message-state;
	bh=yXAhUHHqoSgNn5QgY+62Z+Xj6Lc9EhYZZZLk7l3HuUk=;
	b=WDtwqPV+37PB4l5dGQnbCD/Z8dvPQrZdfzn182vBvcwsin2uznOa6iYFvfYNPF2zzB
	41y9yq5HFQwBZgcHOuj8MBAQ2LytK2M0EM1OFm9J1YVQnbf+kZDlyIju7AWhf8YbSVBu
	39B351Wet4V5W+BOZfJNJe7HfdG6/iuqXcwH7ai16rXz9MsZUjqx/p6yJj5EwlF9nEhk
	lZSR/kOLJAXiWBWvgScdD27q0yRPtAlhpa1CSIuhewNTvVzDKgXwMEhD7yG5ep0bwt3q
	+psXkVnmt4ttXZjCFU+xc1XMkhnCwN7ZcCzHxKegL7u3wBmCfZknmr9H+RPGsWY9ZjHL
	DRow==
Received: by 10.60.172.195 with SMTP id be3mr2050323oec.48.1339074924752; Thu,
	07 Jun 2012 06:15:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 06:15:04 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
From: Rolu 
Date: Thu, 7 Jun 2012 15:15:04 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQngtLLTcabZKBJffXfBo3fHIR/G11BvNtS/xSp1JvGbIhaCFgj4RXotsr7ridMWS1hLy36F
Subject: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

I've compiled Xen unstable from source and tried using it. When
booting I do see Xen starting, but at the point where I normally start
getting the dom0 kernel messages I just get a black screen for a few
seconds, and then the machine reboots. It leaves no messages or log
files, of course.

revision I compiled: 25459
OS: ubuntu 12.04
dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
kernel works with Xen 4.1 from the repositories.

I had to apply the patch from
http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
get it to compile. Could this have broken something?

Is there a way to have it display some log messages instead of rebooting?

Any idea how to get it to work?

If anyone else here is successfully using a recent revision, can you
tell me which one, so I can try it too?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 13:16:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 13:16: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 1SccYl-0001QO-Ng; Thu, 07 Jun 2012 13:15:31 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1SccYk-0001Pi-PX
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 13:15:30 +0000
Received: from [85.158.143.35:58843] by server-3.bemta-4.messagelabs.com id
	E6/A5-29237-279A0DF4; Thu, 07 Jun 2012 13:15:30 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-2.tower-21.messagelabs.com!1339074925!8308318!1
X-Originating-IP: [209.85.213.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6064 invoked from network); 7 Jun 2012 13:15:26 -0000
Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com)
	(209.85.213.173)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 13:15:26 -0000
Received: by yenm4 with SMTP id m4so414038yen.32
	for ; Thu, 07 Jun 2012 06:15:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:from:date:message-id:subject:to
	:content-type:x-gm-message-state;
	bh=yXAhUHHqoSgNn5QgY+62Z+Xj6Lc9EhYZZZLk7l3HuUk=;
	b=WDtwqPV+37PB4l5dGQnbCD/Z8dvPQrZdfzn182vBvcwsin2uznOa6iYFvfYNPF2zzB
	41y9yq5HFQwBZgcHOuj8MBAQ2LytK2M0EM1OFm9J1YVQnbf+kZDlyIju7AWhf8YbSVBu
	39B351Wet4V5W+BOZfJNJe7HfdG6/iuqXcwH7ai16rXz9MsZUjqx/p6yJj5EwlF9nEhk
	lZSR/kOLJAXiWBWvgScdD27q0yRPtAlhpa1CSIuhewNTvVzDKgXwMEhD7yG5ep0bwt3q
	+psXkVnmt4ttXZjCFU+xc1XMkhnCwN7ZcCzHxKegL7u3wBmCfZknmr9H+RPGsWY9ZjHL
	DRow==
Received: by 10.60.172.195 with SMTP id be3mr2050323oec.48.1339074924752; Thu,
	07 Jun 2012 06:15:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 06:15:04 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
From: Rolu 
Date: Thu, 7 Jun 2012 15:15:04 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQngtLLTcabZKBJffXfBo3fHIR/G11BvNtS/xSp1JvGbIhaCFgj4RXotsr7ridMWS1hLy36F
Subject: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

I've compiled Xen unstable from source and tried using it. When
booting I do see Xen starting, but at the point where I normally start
getting the dom0 kernel messages I just get a black screen for a few
seconds, and then the machine reboots. It leaves no messages or log
files, of course.

revision I compiled: 25459
OS: ubuntu 12.04
dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
kernel works with Xen 4.1 from the repositories.

I had to apply the patch from
http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
get it to compile. Could this have broken something?

Is there a way to have it display some log messages instead of rebooting?

Any idea how to get it to work?

If anyone else here is successfully using a recent revision, can you
tell me which one, so I can try it too?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 14:26:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 14:26: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 1Scde3-00042T-07; Thu, 07 Jun 2012 14:25:03 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scde1-00042N-3R
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 14:25:01 +0000
Received: from [85.158.139.83:30980] by server-2.bemta-5.messagelabs.com id
	2B/68-20827-9B9B0DF4; Thu, 07 Jun 2012 14:24:57 +0000
X-Env-Sender: mark@nerdish.us
X-Msg-Ref: server-8.tower-182.messagelabs.com!1339079096!18636495!1
X-Originating-IP: [209.85.216.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31583 invoked from network); 7 Jun 2012 14:24:57 -0000
Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com)
	(209.85.216.173)
	by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 14:24:57 -0000
Received: by qcsc20 with SMTP id c20so415672qcs.32
	for ; Thu, 07 Jun 2012 07:24:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:content-type
	:x-gm-message-state;
	bh=y1QYllZaTtsmipJ5trMk7pBZNn/6TLdJYnhUisAORIs=;
	b=nYwTZSKJisIoLbR8StMVlHyFv2BQkJX3ZSG6FiDvo+gyIKFT/kkq7qeFZOYB6eDWb4
	GR7Pbk+hse//bi42OJAsoFoQfbxbh4pFrhYglf5vjwUen1Yyf/IRzibeoU0e9hi9cmZJ
	F0nP5DZjuL/y/CwAulWxgApM9Sv/c8htwXY1pf8Lf3XohrYyxrOcbU8bo3UAyX4JzZMn
	waBBnMc+q/MjCMZNwV9sA2ZVzwG4FbNagO66iHVEspPeCFUgEztRamFjZSPZOE07DlxM
	Ef+u66dRzXlf74b8GAOWl0E9jOTmRZBl6mL2Md64OIDJffbS18RelcKTgsj5q9FaQCI1
	YWUQ==
MIME-Version: 1.0
Received: by 10.224.108.129 with SMTP id f1mr2939824qap.53.1339079095708; Thu,
	07 Jun 2012 07:24:55 -0700 (PDT)
Received: by 10.229.96.148 with HTTP; Thu, 7 Jun 2012 07:24:55 -0700 (PDT)
In-Reply-To: 
References: 
	
	<1339060892.15265.44.camel@zakaz.uk.xensource.com>
	
Date: Thu, 7 Jun 2012 09:24:55 -0500
X-Google-Sender-Auth: T7huot7Kw3wQXco_JZ1WJO1flJY
Message-ID: 
From: xenusers 
To: "xen-users@lists.xen.org" 
X-Gm-Message-State: ALoCoQk0C5XqBNU8vu9JJ2fFIR0KdRyNZgvkh4gjULaFupxmrfTEWT8HWmz3sUu1Ff9wVVLr/w6/
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4850578972908571590=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4850578972908571590==
Content-Type: multipart/alternative; boundary=20cf3074b37ed36c3c04c1e2a509

--20cf3074b37ed36c3c04c1e2a509
Content-Type: text/plain; charset=ISO-8859-1

Hi Fabien

On Thu, Jun 7, 2012 at 4:34 AM, Xen Xen  wrote:

> Dear Ian,
>
> ...

If this option didn't really exist, how can I do?
> Cause in current time  I can start two VM in the same time and cause
> read-only file system error...
> I've 2 Xen server which stored VM on a NAS with iSCSI. It's works great,
> but I've just this problem...
> Still exist a solution to resolve this?
>
>
We're running Xen hosts connected to iSCSI storage as well, and we use the
Pacemaker/Corosync cluster stack to handle starts/stops of the domUs.  The
Pacemaker RA ensures that a VM is only running in one location, and gives
you automatic recovery if a domU or its parent dom0 goes down.

Hope that helps point you towards a solution,
Mark

--20cf3074b37ed36c3c04c1e2a509
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Fabien

On Thu, Jun 7, 2012 at 4:34 AM,=
 Xen Xen <xenbys@gmail.com> wrote:

Dear Ian,

...=A0
If this =
option didn't really exist, how can I do?
Cause in current time=A0 I=
 can start two VM in the same time and cause read-only file system error...=


I've 2 Xen server which stored VM on a NAS with iSCSI. It's works g=
reat, but I've just this problem...

Still exist a solution to resolve this?


=

We're running Xen hosts connected to iSCSI storage as well, and we=
 use the Pacemaker/Corosync cluster stack to handle starts/stops of the dom=
Us. =A0The Pacemaker RA ensures that a VM is only running in one location, =
and gives you automatic recovery if a domU or its parent dom0 goes down.


Hope that helps point you towards a solution,
Mark


--20cf3074b37ed36c3c04c1e2a509--


--===============4850578972908571590==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4850578972908571590==--


From xen-users-bounces@lists.xen.org Thu Jun 07 14:26:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 14:26: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 1Scde3-00042T-07; Thu, 07 Jun 2012 14:25:03 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scde1-00042N-3R
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 14:25:01 +0000
Received: from [85.158.139.83:30980] by server-2.bemta-5.messagelabs.com id
	2B/68-20827-9B9B0DF4; Thu, 07 Jun 2012 14:24:57 +0000
X-Env-Sender: mark@nerdish.us
X-Msg-Ref: server-8.tower-182.messagelabs.com!1339079096!18636495!1
X-Originating-IP: [209.85.216.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31583 invoked from network); 7 Jun 2012 14:24:57 -0000
Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com)
	(209.85.216.173)
	by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 14:24:57 -0000
Received: by qcsc20 with SMTP id c20so415672qcs.32
	for ; Thu, 07 Jun 2012 07:24:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:content-type
	:x-gm-message-state;
	bh=y1QYllZaTtsmipJ5trMk7pBZNn/6TLdJYnhUisAORIs=;
	b=nYwTZSKJisIoLbR8StMVlHyFv2BQkJX3ZSG6FiDvo+gyIKFT/kkq7qeFZOYB6eDWb4
	GR7Pbk+hse//bi42OJAsoFoQfbxbh4pFrhYglf5vjwUen1Yyf/IRzibeoU0e9hi9cmZJ
	F0nP5DZjuL/y/CwAulWxgApM9Sv/c8htwXY1pf8Lf3XohrYyxrOcbU8bo3UAyX4JzZMn
	waBBnMc+q/MjCMZNwV9sA2ZVzwG4FbNagO66iHVEspPeCFUgEztRamFjZSPZOE07DlxM
	Ef+u66dRzXlf74b8GAOWl0E9jOTmRZBl6mL2Md64OIDJffbS18RelcKTgsj5q9FaQCI1
	YWUQ==
MIME-Version: 1.0
Received: by 10.224.108.129 with SMTP id f1mr2939824qap.53.1339079095708; Thu,
	07 Jun 2012 07:24:55 -0700 (PDT)
Received: by 10.229.96.148 with HTTP; Thu, 7 Jun 2012 07:24:55 -0700 (PDT)
In-Reply-To: 
References: 
	
	<1339060892.15265.44.camel@zakaz.uk.xensource.com>
	
Date: Thu, 7 Jun 2012 09:24:55 -0500
X-Google-Sender-Auth: T7huot7Kw3wQXco_JZ1WJO1flJY
Message-ID: 
From: xenusers 
To: "xen-users@lists.xen.org" 
X-Gm-Message-State: ALoCoQk0C5XqBNU8vu9JJ2fFIR0KdRyNZgvkh4gjULaFupxmrfTEWT8HWmz3sUu1Ff9wVVLr/w6/
Subject: Re: [Xen-users] Lock domU on start
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4850578972908571590=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============4850578972908571590==
Content-Type: multipart/alternative; boundary=20cf3074b37ed36c3c04c1e2a509

--20cf3074b37ed36c3c04c1e2a509
Content-Type: text/plain; charset=ISO-8859-1

Hi Fabien

On Thu, Jun 7, 2012 at 4:34 AM, Xen Xen  wrote:

> Dear Ian,
>
> ...

If this option didn't really exist, how can I do?
> Cause in current time  I can start two VM in the same time and cause
> read-only file system error...
> I've 2 Xen server which stored VM on a NAS with iSCSI. It's works great,
> but I've just this problem...
> Still exist a solution to resolve this?
>
>
We're running Xen hosts connected to iSCSI storage as well, and we use the
Pacemaker/Corosync cluster stack to handle starts/stops of the domUs.  The
Pacemaker RA ensures that a VM is only running in one location, and gives
you automatic recovery if a domU or its parent dom0 goes down.

Hope that helps point you towards a solution,
Mark

--20cf3074b37ed36c3c04c1e2a509
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Fabien

On Thu, Jun 7, 2012 at 4:34 AM,=
 Xen Xen <xenbys@gmail.com> wrote:

Dear Ian,

...=A0
If this =
option didn't really exist, how can I do?
Cause in current time=A0 I=
 can start two VM in the same time and cause read-only file system error...=


I've 2 Xen server which stored VM on a NAS with iSCSI. It's works g=
reat, but I've just this problem...

Still exist a solution to resolve this?


=

We're running Xen hosts connected to iSCSI storage as well, and we=
 use the Pacemaker/Corosync cluster stack to handle starts/stops of the dom=
Us. =A0The Pacemaker RA ensures that a VM is only running in one location, =
and gives you automatic recovery if a domU or its parent dom0 goes down.


Hope that helps point you towards a solution,
Mark


--20cf3074b37ed36c3c04c1e2a509--


--===============4850578972908571590==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4850578972908571590==--


From xen-users-bounces@lists.xen.org Thu Jun 07 14:46:44 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 14:46:44 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Scdy1-000573-53; Thu, 07 Jun 2012 14:45:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scdxz-00056i-WB
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 14:45:40 +0000
Received: from [193.109.254.147:51105] by server-9.bemta-14.messagelabs.com id
	4A/E8-27072-39EB0DF4; Thu, 07 Jun 2012 14:45:39 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-9.tower-27.messagelabs.com!1339080336!8596635!1
X-Originating-IP: [209.85.213.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7434 invoked from network); 7 Jun 2012 14:45:37 -0000
Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com)
	(209.85.213.173)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 14:45:37 -0000
Received: by yenm4 with SMTP id m4so520683yen.32
	for ; Thu, 07 Jun 2012 07:45:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=grVyeXaTBaGAN13sNcsp0vjevF0icQX+XOMoECLpnco=;
	b=GMEaw2fvJOPLGVqBKdvnrVQ9ve+/qSDx2gnDHYC8v9fwFH+9+yfwKn1O9LvsV9N74Z
	KOcJ1NJWXGRRI4t6nAGHMQMwp723YbYDL6VUxx/IS81lCF6Y177Tc61KJ10S4W0F0vri
	sriOLIbvvV6axZ/PfYciiFJPOpGXEaZZlQ7mIKFO1e5cJrl1+PermORPwNascfe8P4gt
	/iFD/xCyUHnTy8is9xjb7FjlhnMpFluS9ORaN0CeXt4l5UdiK5PVUQVsUIGUK0p/ZjUJ
	UzE9y/XB0xACfCCaxKCR+9CmPgqCjFG4izZAMkODr5sDJpDcdYVAs423o/4hRDBW6N3n
	FX5Q==
Received: by 10.60.19.67 with SMTP id c3mr2442864oee.2.1339080335836; Thu, 07
	Jun 2012 07:45:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 07:45:15 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
	
From: Rolu 
Date: Thu, 7 Jun 2012 16:45:15 +0200
Message-ID: 
To: George Dunlap 
X-Gm-Message-State: ALoCoQlMO1EY+JKcP6bt+U+FUgeu5iPblO6pijHp71sY6nvXbW0DgsNQGk1VRS6cilqjkpApsGuT
Cc: Lars Kurth , xen-users@lists.xen.org,
	"xen-api@lists.xen.org" , xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 3:14 PM, George Dunlap
 wrote:
> Sorry to throw in a criticism without a constructive solution, but I
> just want to register one opinion: To me clicking on a link and seeing
> a "Category" page says very strongly, "I couldn't be bothered to
> actually do any work here; I'll leave you to do all the work to figure
> out what page you need." =A0When I encounter a Category page on my walk
> through the Xen wiki, I don't even look, but immediately turn to
> Google. =A0I think a page which is has some kind of logical flow to it
> but perhaps a little out-dated is much better than a page which just
> tosses up a bunch of titles in no order and lets you figure it out.
>

I do agree with this, generally. Browsing a wiki and hovering over a
link and seeing that it goes to a Category: page is... somehow
disappointing. Most of the time you won't get any help finding what
you need there so people may already be conditioned to just ignore
them.

> I think in an ideal world, we'd have people who were "maintainers" of
> the wiki just like there are maintainers of different subsections of
> the codebase. =A0Until that time, could we maybe draw up a set of
> "tests" to run on the docs, which can be assigned to people on DocDay?
> =A0One simple thing could be, "Make sure X page is up-to-date" (which
> may include, "Look at the Category: page and make sure everything
> there is listed somewhere on the manually-generated page"); another
> could be a scenario, "Pretend you're a [foo] and you want to know
> [bar]. =A0Start at the top level page and make sure you can find all the
> information you need." =A0If each "test" was something any motivated
> developer/community member could do, and only took 5-10 minutes, it
> should be pretty sustainable. =A0What do you think?
>

I think that's a really good idea. Unit tests for the documentation? ;-)

Related to the discussion: I had a go at a unified books & manuals
page: http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals

Books and manuals are, I think, the only documents that can't really
be linked by topic (beyond something general such as "xcp") as they
are generally quite large, so a page like this makes most sense. Let
me know what you think.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 14:46:44 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 14:46:44 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Scdy1-000573-53; Thu, 07 Jun 2012 14:45:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scdxz-00056i-WB
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 14:45:40 +0000
Received: from [193.109.254.147:51105] by server-9.bemta-14.messagelabs.com id
	4A/E8-27072-39EB0DF4; Thu, 07 Jun 2012 14:45:39 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-9.tower-27.messagelabs.com!1339080336!8596635!1
X-Originating-IP: [209.85.213.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7434 invoked from network); 7 Jun 2012 14:45:37 -0000
Received: from mail-yx0-f173.google.com (HELO mail-yx0-f173.google.com)
	(209.85.213.173)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 14:45:37 -0000
Received: by yenm4 with SMTP id m4so520683yen.32
	for ; Thu, 07 Jun 2012 07:45:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=grVyeXaTBaGAN13sNcsp0vjevF0icQX+XOMoECLpnco=;
	b=GMEaw2fvJOPLGVqBKdvnrVQ9ve+/qSDx2gnDHYC8v9fwFH+9+yfwKn1O9LvsV9N74Z
	KOcJ1NJWXGRRI4t6nAGHMQMwp723YbYDL6VUxx/IS81lCF6Y177Tc61KJ10S4W0F0vri
	sriOLIbvvV6axZ/PfYciiFJPOpGXEaZZlQ7mIKFO1e5cJrl1+PermORPwNascfe8P4gt
	/iFD/xCyUHnTy8is9xjb7FjlhnMpFluS9ORaN0CeXt4l5UdiK5PVUQVsUIGUK0p/ZjUJ
	UzE9y/XB0xACfCCaxKCR+9CmPgqCjFG4izZAMkODr5sDJpDcdYVAs423o/4hRDBW6N3n
	FX5Q==
Received: by 10.60.19.67 with SMTP id c3mr2442864oee.2.1339080335836; Thu, 07
	Jun 2012 07:45:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 07:45:15 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
	
From: Rolu 
Date: Thu, 7 Jun 2012 16:45:15 +0200
Message-ID: 
To: George Dunlap 
X-Gm-Message-State: ALoCoQlMO1EY+JKcP6bt+U+FUgeu5iPblO6pijHp71sY6nvXbW0DgsNQGk1VRS6cilqjkpApsGuT
Cc: Lars Kurth , xen-users@lists.xen.org,
	"xen-api@lists.xen.org" , xen-devel@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 3:14 PM, George Dunlap
 wrote:
> Sorry to throw in a criticism without a constructive solution, but I
> just want to register one opinion: To me clicking on a link and seeing
> a "Category" page says very strongly, "I couldn't be bothered to
> actually do any work here; I'll leave you to do all the work to figure
> out what page you need." =A0When I encounter a Category page on my walk
> through the Xen wiki, I don't even look, but immediately turn to
> Google. =A0I think a page which is has some kind of logical flow to it
> but perhaps a little out-dated is much better than a page which just
> tosses up a bunch of titles in no order and lets you figure it out.
>

I do agree with this, generally. Browsing a wiki and hovering over a
link and seeing that it goes to a Category: page is... somehow
disappointing. Most of the time you won't get any help finding what
you need there so people may already be conditioned to just ignore
them.

> I think in an ideal world, we'd have people who were "maintainers" of
> the wiki just like there are maintainers of different subsections of
> the codebase. =A0Until that time, could we maybe draw up a set of
> "tests" to run on the docs, which can be assigned to people on DocDay?
> =A0One simple thing could be, "Make sure X page is up-to-date" (which
> may include, "Look at the Category: page and make sure everything
> there is listed somewhere on the manually-generated page"); another
> could be a scenario, "Pretend you're a [foo] and you want to know
> [bar]. =A0Start at the top level page and make sure you can find all the
> information you need." =A0If each "test" was something any motivated
> developer/community member could do, and only took 5-10 minutes, it
> should be pretty sustainable. =A0What do you think?
>

I think that's a really good idea. Unit tests for the documentation? ;-)

Related to the discussion: I had a go at a unified books & manuals
page: http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals

Books and manuals are, I think, the only documents that can't really
be linked by topic (beyond something general such as "xcp") as they
are generally quite large, so a page like this makes most sense. Let
me know what you think.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 15:42:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 15:42: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 1ScepU-0007Y1-Gf; Thu, 07 Jun 2012 15:40:56 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScepT-0007Xv-3o
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 15:40:55 +0000
Received: from [85.158.143.99:18528] by server-1.bemta-4.messagelabs.com id
	44/89-10042-68BC0DF4; Thu, 07 Jun 2012 15:40:54 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-5.tower-216.messagelabs.com!1339083645!31453512!1
X-Originating-IP: [209.85.213.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16194 invoked from network); 7 Jun 2012 15:40:46 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 15:40:46 -0000
Received: by yhoo21 with SMTP id o21so606644yho.32
	for ; Thu, 07 Jun 2012 08:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=FMBlyQ7UcRrkLWz8uO+oNao+IyyYLYQ6HFd6Q/tjG6Q=;
	b=J9KDaO4tn1qvLc0iY/0OM4QW1H2GSDyXXfxZ4OEk8vuqrtdoKy9nMSkll7vCpCSA58
	OedMQL4N7i7did8fZp+7zOcbQtJixJle9qTDlj0VxgEH8RVKqLz9ZLrzxlAk7iK+h02/
	nyde4TLWdkswjh4AijiLspuqkzbR7HwR5Nn9wbx+BVk+0OPnTWyKsbKQNGdWloxb/X7c
	iO33OMf9rDEscXgNohXJNhCmJAtqefUnFt2TnrunoaFJhcLtwXKzgSljipqiHx9VBwbH
	YrQYGg5yYpOFMfYwkdhfY5VGFEemA6tvwaH7vtvEStD/9PCG0VSb4IFPE5+9/nwF5JVz
	btIw==
Received: by 10.101.137.39 with SMTP id p39mr732432ann.73.1339083645309;
	Thu, 07 Jun 2012 08:40:45 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id z42sm11199390yhd.1.2012.06.07.08.40.44
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 07 Jun 2012 08:40:44 -0700 (PDT)
Message-ID: <4FD0CB5C.7050402@gmail.com>
Date: Thu, 07 Jun 2012 11:40:12 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SlVTVCBhIGhlYWRzIHVwLCB0aGUgbGF0ZXN0IHJlbGFzZSBvZiB4ZW4tdW5zdGFibGUuaGcgaXMg
IiAyNTQ1OSIgYXMgb2YgCnRvZGF5LCBBTkQgaSBqdXN0IHRyaWVkIGNvbXBpbGluZyBpdCBhbmQg
aXQgZmluYWxseSB3b3JrcyBhbmQgY29tcGlsZXMgCndpdGhvdXQgZXJyb3JzIG9yIGFueSBhZGRp
dGlvbmFsIHBhdGNoZXMuR3JhbnRlZCwgb25seSB0cmllZCBpdCBvbiAKRGViaWFuIFdoZWV6eS4g
SWYgeW91IGFyZSBhZHZhbnRlcmlvdXMsIHlvdSBjb3VsZCB0cnkgaXQgb24gVWJ1bnR1IDEyLjA0
LgoKClNPLCBhbmQgYXdlc29tZSB0aHVtYnMgdXAgZm9yIHRoZSBYZW4tZGV2ZWwgdGVhbSBmb3Ig
Zml4aW5nIGFsbCBvZiB0aGUgCmlzc3VlcyBwcmV2ZW50IGNvbXBpbGUuLi4gOikKCgoKT24gNi81
LzIwMTIgMTI6NTMgUE0sIFdpbGwgTWNEZXJtb3R0IHdyb3RlOgo+IEZpbmFsbHkgZ290IGl0IHRv
IGJ1aWxkLCBuZWVkZWQgdGhpcyBwYXRjaDoKPiBodHRwOi8vbGlzdHMuZ251Lm9yZy9hcmNoaXZl
L2h0bWwvcWVtdS1kZXZlbC8yMDEyLTAyL21zZzAzNDYwLmh0bWwKPiBhbmQgdGhlIHRleGkyaHRt
bCBhbmQgdGV4aW5mbyBwYWNrYWdlcy4KPgo+IEdvb2QgdG8ga25vdyB0aGUgY29tcGlsYXRpb24g
cHJvY2VzcyBvbiBEZWJpYW4gaXMgYSBiaXQgbmljZXIgOikKPgo+IFRoYW5rIHlvdSBzbyBtdWNo
IGZvciB5b3VyIGhlbHAhCj4KPiAtLVdpbGwKPgo+Pj4+ICAgMDYvMDUvMTIgNTozMSBBTT4+Pgo+
IGh1bW0sIHdlbGwgdGhhdCBzdWNrcy4gSSBrbm93IGNvbXBpbGluZyBjaGFuZ2VzZXQgMjUzOTIg
d29ya3MgZm9yIG1lLAo+IHdpdGggdGhlIHBhY2thZ2VzIGFuZCBpbnN0cnVjdGlvbnMgaSBkZXNj
cmliZWQsIGkgaGF2ZSBjb21waWxlZCBpdAo+IHNldmVyYWwgdGltZXMgbm93LiBJIGtub3cgdGhl
IG1haW4gcmVhc29uIHdoeSB0aGUgbGF0ZXIgY2hhbmdlc3RzIHdvbid0Cj4gY29tcGlsZSBpcyBi
ZWNhdXNlIG9mIHRoZSBkaWZmZXJlbnQgR0NDIHZlcnNpb24gc2VlbSB0byBkbyBkaWZmZXJlbnQK
PiBlbm91Z2ggdG8gZmFpbCwgU08gbWF5YmUgVWJ1bnR1IGhhcyBhIGRpZmZlcmVudCBzdWJzZXQg
b2YgR0NDLiBJIGhhdmUgbm8KPgo+IGlkZWEuCj4KPiBXZWxsLCBpZiBpdCB3YXMgbm8gdHJvdWJs
ZSBmb3IgeW91LCBtYXliZSB0cnkgdG8gaW5zdGFsbCBEZWJpYW4gV2hlZXp5Cj4gYW5kIHRyeSB0
byBjb21waWxlIGFnYWluLiBPdGhlcndpc2UgaSBjb3VsZCBhbHdheXMgc2VuZCB5b3UgdGhlIFhl
biA0LjIKPiByZXYtMjUzOTIgY29tcGlsZWQgREVCIHBhY2thZ2UgYW5kIHlvdSBjYW4ganVzdCBp
bnN0YWxsIHRoYXQsIEJVVCB0aGF0Cj4gd291bGRuJ3Qgc29sdmUgeW91ciBwcm9ibGVtIGlmIHlv
dSB3YW50ZWQgdG8gY29tcGlsZSBpdCBsYXRlciBvbi4KPgo+Cj4+IEhtbSBzYW1lIGVycm9yOgo+
Pgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRh
dGVfZmlsZV9jcmVkw6I6Cj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29s
cy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+IGVycm9y
OiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlv
bikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4gbm90ZTogZWFjaCB1bmRlY2xh
cmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNoCj4gZnVuY3Rpb24K
Pj4gaXQgYXBwZWFycyBpbgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9sc3RhdMOiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+PiBl
cnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu
Y3Rpb24pCj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+IEluIGZ1bmN0aW9uIMOiaGFuZGxl
X3N5bWxpbmvDojoKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3Fl
bXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6Cj4+IGVycm9yOiDD
okFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikK
Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9o
dy85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4gSW4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8Oi
Ogo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPj4gZXJyb3I6IMOiQVRfRU1QVFlf
UEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+Pgo+IC9yb290
L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOgo+Pgo+IC9y
b290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMv
dmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVu
ZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+PiBtYWtlWzRdOiAqKiogWzlw
ZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxCj4+IG1ha2VbNF06ICoqKiBXYWl0aW5nIGZv
ciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+ICAgICBDQyAgICBobXAubwo+PiAgICAgQ0MgICAgbGli
ZGlzL2kzODYtZGlzLm8KPj4gICAgIExJTksgIHFlbXUtZ2EKPj4gICAgIExJTksgIHFlbXUtbmJk
Cj4+ICAgICBMSU5LICBxZW11LWltZwo+PiAgICAgTElOSyAgcWVtdS1pbwo+PiBtYWtlWzNdOiAq
KiogW3N1YmRpci1saWJodzY0XSBFcnJvciAyCj4+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0b3J5
Cj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci1y
ZW1vdGUnCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJv
ciAyCj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzJwo+PiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3Ig
Mgo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5Mi90b29scycKPj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4+Cj4+
IEkgaGFkIG1vc3Qgb2YgdGhlIHBhY2thZ3MsIEkgcmFuICJhcHQtZ2V0IGJ1aWxkLWRlcCB4ZW4i
IGZyb206Cj4+IGh0dHA6Ly93aWtpLnhlbi5vcmcvd2lraS9Db21waWxpbmdfWGVuX0Zyb21fU291
cmNlCj4+Cj4+IEJ1dCBpdCBzdGlsbCBlcnJvcnMgb24gdGhlIHZpcnRpbyBmaWxlLiBJIGhhZCBh
bHNvIHJlYWQgdGhhdCB0aGVzZQo+PiBlcnJvcnMgaGFkIHRvIGRpZmZlcmVudCB3aXRoIGRpZmZl
cmVudCBsaWJyYXJ5L2djYyB2ZXJzaW9ucy4gTWF5YmUKPj4gd2hlZXp5IGp1c3QgaGFzIG5ld2Vy
L2RpZmZlcmVudCB2ZXJzaW9ucyBvZiB0aG9zZSBiaW5hcmllcy9saWJzPwo+Pgo+PiAtLVdpbGwK
Pj4KPj4KPj4+Pj4gICAgMDYvMDQvMTIgMTE6NDUgQU0+Pj4KPj4gV0VMTCwgYWN0dWFsbHkgTk8g
bmVlZCB0byBpbnN0YWxsIFdoZWV6eS4gSSBhbSB2ZXJ5IHN1cmUgeW91IGNhbiBnZXQKPiBpdAo+
PiB3b3JraW5nIGp1c3QgYXMgZWFzaWx5IHdpdGggVWJ1bnR1Lgo+Pgo+PiBUaGUgb3RoZXIgdGhp
bmcgaSBmb3Jnb3QgdG8gbWVudGlvbiBpcyB5b3UgaGF2ZSB0byBoYXZlIGFsbCBvZiB0aGUKPj4g
cmVxdWlyZWQgcGFja2FnZXMgaW5zdGFsbGVkIGJlZm9yZSB5b3UgY2FuIGNvbXBpbGUgWGVuLiBJ
IHRoaW5rIHlvdQo+IGFyZQo+PiBqdXN0IG1pc3NpbmcgYSBidW5jaCBvZiBkZXBlbmRlbnQgcGFj
a2FnZXMuIFRoZSBwYWNrYWdlcyBpIHVzZSBhbmQKPiBoYXZlCj4+IGluc3RhbGxlZCBhcmUgYXMg
Zm9sbG93czoKPj4KPj4gc3VkbyBhcHQtZ2V0IGluc3RhbGwgd2dldCB0YXIgYnppcDIgYnVpbGQt
ZXNzZW50aWFsIGxpYm5jdXJzZXM1LWRldgo+PiBrZXJuZWwtcGFja2FnZSBmYWtlcm9vdCBiY2Mg
Z2NjIHNzaCBicmlkZ2UtdXRpbHMgcHl0aG9uLWRldiB1dWlkLWRldgo+PiBsaWJnbGliMi4wLWRl
diBsPiAgYmlzb24gcXQ0LWRldi10b29scyBwYXRjaCBvY2FtbC1maW5kbGliIGxpYnNkbDEuMi1k
ZXYKPj4KPj4gR3JhbnRlZCBzb21lIG9mIHRoZSBhYm92ZSBwYWNrYWdlcyBhcmUgbW9yZSBpbXBv
cnRhbnQgZm9yIGNvbXBpbGluZwo+IHRoZQo+PiBrZXJuZWwuCj4+Cj4+IFNPLCBhcyBsb25nIGFz
IHlvdSBoYXZlIGFsbCByZXF1aXJlZCBwYWNrYWdlcyBhbmQgZm9sbG93IHRoZQo+PiBpbnN0cnVj
dGlvbnMgYmVmb3JlIGFib3V0IGdldHRpbmcgYW5kIGNvbXBpbGluZyBYZW4gNC4yIHJldmlzaW9u
Cj4gMjUzOTIsCj4+IGl0IHNob3VsZCBiZSBmaW5lLCBubyBtYXR0ZXIgaWYgeW91IGFyZSB1c2lu
ZyBEZWJpYW4gb3IgVWJ1bnR1LiBVYnVudHUKPj4gaG93ZXZlciAibWlnaHQiIG5lZWQgbW9yZSBw
YWNrYWdlcywgbm90IHN1cmUsICBpIGhhdmUgbm90IGNvbXBpbGVkIFhlbgo+PiB1bmRlciBVYnVu
dHUgeWV0Lgo+Pgo+Pgo+Pgo+PiBPbiA2LzQvMjAxMiAxMjo0MyBQTSwgV2lsbCBNY0Rlcm1vdHQg
d3JvdGU6Cj4+PiBEYXJuLCBtYWRlIGl0IGZhcnRoZXIgYnV0IG5vdyBJIGdldCB0aGlzOgo+Pj4K
Pj4+IENDICAgIGxpYmh3NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubwo+Pj4gICAgICBDQyAgICBs
aWJodzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCj4+PiAgICAgIENDICAgIHFlbXUtY2hhci5v
Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+Pj4gSW4gZnVuY3Rpb24gw6JoYW5kbGVfdXBk
YXRlX2ZpbGVfY3JlZMOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4+IGVy
cm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5j
dGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+PiBub3RlOiBlYWNoIHVu
ZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gKPj4gZnVu
Y3Rpb24KPj4+IGl0IGFwcGVhcnMgaW4KPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0y
NTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJ
biBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4
NzozNDoKPj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2Ug
aW4gdGhpcyBmdW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90
b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5j
dGlvbiDDomhhbmRsZV9zeW1saW5rw6I6Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2
MjoKPj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4g
dGhpcyBmdW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29s
cy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9saW5rw6I6Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPj4+
IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm
dW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5jdGlvbiDDomhh
bmRsZV9jaG93bsOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozNzM6NTg6Cj4+PiBlcnJv
cjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rp
b24pCj4+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxCj4+
PiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5maW5pc2hlZCBqb2JzLi4uLgo+Pj4gICAgICBD
QyAgICBzYXZldm0ubwo+Pj4gICAgICBDQyAgICBtc21vdXNlLm8KPj4+ICAgICAgQ0MgICAgcHMy
Lm8KPj4+IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDIKPj4+IG1ha2VbM106
ICoqKiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+PiBtYWtlWzNdOiBMZWF2aW5n
IGRpcmVjdG9yeQo+Pj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVt
dS14ZW4tZGlyLXJlbW90ZScKPj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14
ZW4tZGlyXSBFcnJvciAyCj4+PiBtYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycKPj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1p
bnN0YWxsXSBFcnJvciAyCj4+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycKPj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29s
c10gRXJyb3IgMgo+Pj4KPj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNo
IGZvciB5b3VyIGNsZWFyIGluc3RydWN0aW9ucyEgSQo+Pj4gd2lsbCBpbnN0YWxsIHdoZWV6eSB0
b25pZ2h0IGFuZCB0cnkgdGhlIGJ1aWxkIGFnYWluLgo+Pj4KPj4+IC0tV2lsbAo+Pj4KPj4+Pj4+
ICAgICAwNi8wNC8xMiA0OjU2IEFNPj4+Cj4+PiBPbiA2LzQvMjAxMiAyOjU4IEFNLCBXaWxsIE1j
RGVybW90dCB3cm90ZToKPj4+PiBJJ20gbm90IHN1cmUgd2hhdCB2ZXJzaW9uIChob3cgZG8gSSBj
aGVjaz8pIGJ1dCBJIGp1c3QgY2xvbmVkIGZyb20KPj4+IHRoYXQKPj4+PiBVUkwgdG9kYXkuCj4+
Pj4KPj4+PiAtLVdpbGwKPj4+IFdlbGwgdGhhbiB5b3UgcHJvYmFibHkgYWxyZWFkeSBoYXZlIHRo
ZSBsYXRlc3QgcmV2aXNpb24uIFlvdSBjYW4gYWxzbwo+Pj4gY2hlY2sgd2hhdCByZXZpc2lvbiB5
b3VyIGxvY2FsbHkgY2xvbmVkIHJlcG9zaXRvcnkgaXMgYXQgYnkgZ29pbmcgdG8KPj4gdGhlCj4+
PiBmb2xkZXIgYW5kIHJ1bm5pbmc6Cj4+Pgo+Pj4gKmNkICAuLi94ZW4tdW5zdGFibGUuaGcKPj4+
IGhnIHN1bW1hcnkKPj4+ICoKPj4+IEFuZCB0aGF0IHdpbGwgc2hvdyB5b3UgYSBzdW1tYXJ5IG9m
IHRoZSBsb2NhbCBtZXJjdXJpYWwgY2xvbmUgYW5kCj4gc2hvdwo+Pj4gdGhlIGxhdGVzdCByZXZp
c2lvbnMgdGhhdCB3YXMgY2xvbmVkLgo+Pj4KPj4+IFNPLCBhbnlob3csIGNvbXBpbGluZyB0aGUg
WGVuIDQuMi11bnN0YWJsZSBmcm9tIHRoZSBtZXJjdXJpYWwgaGFzIG5vdAo+Pj4gYmVlbiB3b3Jr
aW5nIHZlcnkgd2VsbCBmb3IgYSBmZXcgd2Vla3Mgbm93LiBJIGhhdmUgYXNrZWQgdGhlCj4gWGVu
LWRldmVsCj4+PiBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhlcmUgYXJlIGlzc3Vl
cyBhbmQgcHJvYmxlbXMgd2l0aAo+Pj4gZGlmZmVyZW50IEdDQyBjb21waWxlcnMgQU5EIHRoZSBY
ZW4tZGV2ZWwgdGVhbSBrbm93cyBhbGwgdGhhdCBhbmQgYXJlCj4+PiB3b3JraW5nIG9uIGZpeGlu
ZyB0aGF0Lgo+Pj4KPj4+IEZvciBub3csIHRoZSBMQVNUIHJldmlzaW9uIGkgd2FzIGFibGUgdG8g
Y29tcGlsZSBhbmQgZ2V0IHJ1bm5pbmcgd2FzCj4+PiAqInJldmlzaW9uIDI1MzkyKiIsIGJ1dCBl
dmVuIHRoYXQgd2FzIHBvc3NpYmx5IE9OTFkgaWYgeW91IHJlbW8+PiAgcGF0Y2guIFlvdSBjYW4g
dHJ5IHRvIGRvd25sb2FkIGFuZCBjb21waWxlIFRIQVQgdmVyc2lvbiBieSBydW5uaW5nCj4gdGhl
Cj4+PiBmb2xsb3dpbmcgY29tbWFuZHM6Cj4+Pgo+Pj4gXypDbG9uaW5nIFhlbjoqXwo+Pj4gKi0g
Y2QgL3NvbWUvZGlyZWN0b3J5L2luL2hvbWUKPj4+IC0gcmV2PTI1MzkyJiYgICAgaGcgY2xvbmUg
LXIgJHJldgo+Pj4gaHR0cDovL3hlbmJpdHMueGVuLm9yZy9oZy94ZW4tdW5zdGFibGUuaGcvIHhl
bi11bnN0YWJsZS5oZy1yZXYtJHtyZXZ9Cj4+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1yZXYtMjUz
OTIKPj4+IC0gaGcgYmFja291dCAtciAyNTM2NCoKPj4+Cj4+PiBUaGlzIHdpbGwgY2xvbmUgdGhl
IHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbgo+Pj4gNC4yLXVuc3Rh
YmxlIHJldmlzaW9uIDI1MzkyIGludG8gdGhlIGZvbGRlcgo+Pj4gIip4ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyKiIuIFJ1bm5pbmcgdGhlIGNvbW1hbmQgIipoZyBiYWNrb3VyIC1yCj4+PiAyNTM2
NCoiIHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4gSXQgc2VlbXMg
dGhhdAo+Pj4gd2l0aG91dCB0aGF0LCBldmVuIHRoYXQgcmV2aXNpb24gd29udCBjb21waWxlLgo+
Pj4KPj4+IF8qQ29tcGlsaW5nIFhlbjoqXwo+Pj4gVGhhbiBqdXN0IHNpbXBseSBydW4gdGhlc2Ug
Y29tbWFuZHMgdG8gY29tcGlsZSBYZW4uCj4+Pgo+Pj4gKi0gY2QgeGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5MioKPj4+ICotIC4vY29uZmlndXJlCj4+PiAtIHN1ZG8gbWFrZSAtajUgeGVuJiYgICAg
c3VkbyBtYWtlIFRoZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdAo+PiBzdHJpbmdzIHRvZ2V0
aGVyIHRoZSA0IGNvbXBpbGluZyBjb21tYW5kcwo+Pj4gdG8gcnVuIGFuZCB3aWxsIGV4ZWN1dGUg
b25lIGFmdGVyIHRoZSBvdGhlciBTTyB5b3UgZG9uJ3QgaGF2ZSB0bwo+Pj4gbWFudWFsbHkgcnVu
IGVhY2ggYW5kIGV2ZXJ5IG9uZS4gQWxzbywgSW4gdGhlIGFib3ZlICIqbWFrZSoiCj4gY29tbWFu
ZHMsCj4+PiB1c2luZyB0aGUgIiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtlIHRlbGxzIHRo
ZSBjb21waWxlIHRvIHVzZQo+IG1vcmUKPj4+IHRoYW4gb25lIGNvcmUgdG8gY29tcGlsZSB3aXRo
LiBJdCBzcGVlZHMgdXAgdGhlIGNvbXBpbGk+ICAgaGF2ZSBhCj4gbXVsdGktY29yZSBDUFUuIFNP
IGluIG15IGNhc2UsIGkgaGF2ZSBhIFF1YWQgQ29yZSBDUFUsIHNvIHRoYXQKPj4+IGNvbW1hbmQg
b3B0aW9uIGlzICIqLWoxICsgbnVtYmVyIG9mIENQVSBjb3JlcyoiLiBZb3UgY2FuIG1vZGlmeSBv
cgo+Pj4gcmVtb3ZlIHRoYXQgYXMgeW91IHdpc2guCj4+Pgo+Pj4gVGhlIGFib3ZlIHdpbGwgYWxz
byBjcmVhdGUgZm9yIHlvdSBhIG5pY2UgREVCIHBhY2thZ2UgYWZ0ZXIgYWxsIHRoZQo+Pj4gY29t
cGlsaW5nIGlzIGRvbmUsIGlmIHlvdSBkbyBub3Qgd2FudCB0byBjcmVhdGUgYSBERUIgcGFja2Fn
ZSBhdCB0aGUKPj4gZW5kCj4+PiBvZiBpdCBhbGwsIHRoYW4ganVzdCByZW1vdmUgdGhlIGxhc3Qg
IiomJiAgICBzdWRvIG1ha2UgLWo1IGRlYioiCj4+IGNvbW1hbmQuCj4+PiBHcmFudGVkLCBpIGFt
IHJ1bm5pbmcgYW5kIGRvaW5nIGFsbCBvZiB0aGlzIG9uIERlYmlhbiBXaGVlenkgQlVUIGkKPj4g
dGhlcmUKPj4+IGFyZW4ndCBhbnkgZGlmZmVyZW5jZXMgaW4gY29tcGlsaW5nIGl0IG9uIFVidW50
dSAxMi4wNC4KPj4+Cj4+Pgo+Pj4KPj4+Cj4+Pj4+Pj4gICAgICAwNi8wMy8xMiAyOjM0IFBNPj4+
Cj4+Pj4gVGhlIGxhdGVzdCByZXZpc2lvbiBvZiBYZW4gNC4yLXVuc3RhYmxlIGlzICoyNTQ1Mjo2
YmVhNjNlNmM3ODAqIGF0Cj4+IHRoZQo+Pj4+IGxpbmsgKmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcv
aGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YKPj4+IFhlbgo+Pj4+IDQuMi1V
bnN0YWJsZSBhcmUgeW91IHRyeWluZyB0byBjb21waWxlPwo+Pj4+Cj4+Pj4KPj4+Pj4gSGVsbG8s
Cj4+Pj4+Cj4+Pj4+IEkgYW0gdHJ5aW5nIHRvIGNvbXBpbGUgeGVuIDQuMiB1bnN0YWJsZSBmcm9t
IG1lcmN1cmlhbC4gSSBjYW4ndCBnZXQKPj4+PiBwYXN0Cj4+Pj4+IHRoZSBtYWtlIHRvb2xzIHN0
ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6Cj4+Pj4+Cj4+
Pj4+IENDICAgIGxpYmh3NjQvOXBmcy9jb3hhdHRyLm8KPj4+Pj4gICAgICAgIENDICAgIGxpYmh3
NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubwo+Pj4+PiAgICAgICAgQ0MgICAgbGliaHc2NC85cGZz
L3ZpcnRpby05cC1oYW5kbGUubwo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+Pj4gSW4KPj4+Pj4gZnVu
Y3Rpb24gw6JoYW5kbGVfdXBkYXRlX2ZpbGVfY3JlZMOiOgo+Pj4+Pgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6
NTg6Cj4+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2Ug
aW4gdGhpcyBmdW5jdGlvbikKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjcwOjU4Ogo+Pj4+PiBub3RlOiBl
YWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gK
Pj4+PiBmdW5jdGlvbgo+Pj4+PiBpdCBhcHBlYXJzIGluCj4+Pj4+Cj4gL3Jvb3QveGVuLXVuc3Rh
YmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4+
PiBJbgo+Pj4+PiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pj4+Pgo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
ODc6MzQ6Cj4+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+Pj4+IEluCj4+Pj4+IGZ1
bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2MjoKPj4+
Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlz
IGZ1bmN0aW9uKQo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+Pj4gSW4KPj4+Pj4gZnVuY3Rpb24gw6Jo
YW5kbGVfbGlua8OiOgo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzM3OjQ1Ogo+Pj4+PiBlcnJvcjogw6JB
VF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+
Pj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3Zp
cnRpby05cC1oYW5kbGUuYzoKPj4+PiBJbgo+Pj4+PiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOi
Ogo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzczOjU4Ogo+Pj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRI
w6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Pj4+IG1ha2VbNF06
ICoqKiBbOXBmcy92aXJ0aW8tOXAtaGFuZGxlLm9dIEVycm9yIDEKPj4+Pj4gbWFrZVszXTogKioq
IFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMgo+Pj4+PiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9y
eQo+Pj4+PiBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci1yZW1vdGUn
Cj4+Pj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJvciAy
Cj4+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibD4+Pj4g
IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMn
Cj4+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMgo+Pj4+Pgo+Pj4+PiBJIGFt
IHJ1bm5pbmcgdWJ1bnR1IDEyLjA0LCBrZXJuZWwgdmVyOiAzLjIuMC0yNC1nZW5lcmljCj4+Pj4+
Cj4+Pj4+IEFueSBpZGVhcz8gSSBoYXZlIGdvb2dsZWQgZnVyaW91c2x5IGFuZCBmb3VuZCBzb21l
IHBlb3BsZSB0YWxraW5nCj4+Pj4gYWJvdXQKPj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOgo+Pj4+PiBodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9x
ZW11LWt2bS8rYnVnLzkzMDE4MQo+Pj4+PiBCdXQgSSB3YXMgbm90IGFibGUgdG8gZmluZCB0aGUg
cGF0Y2gKPj4+Pj4KPj4+Pj4gVGhhbmtzIGluIGFkdmFuY2UhCj4+Pj4+Cj4+Pj4+Cj4+Pj4+Cj4+
Pj4+IE1lcmN1cmlhbG0KPj4+Pj4KPj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPj4+Pj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdAo+Pj4+PiBYZW4t
dXNlcnNAbGlzdHMueGVuLm9yZwo+Pj4+PiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMK
Pj4KPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4g
WGVuLXVzZXJzIG1haWxpbmcgbGlzdAo+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCj4gaHR0cDov
L2xpc3RzLnhlbi5vcmcveGVuLXVzZXJzCj4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0
cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Thu Jun 07 15:42:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 15:42: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 1ScepU-0007Y1-Gf; Thu, 07 Jun 2012 15:40:56 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScepT-0007Xv-3o
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 15:40:55 +0000
Received: from [85.158.143.99:18528] by server-1.bemta-4.messagelabs.com id
	44/89-10042-68BC0DF4; Thu, 07 Jun 2012 15:40:54 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-5.tower-216.messagelabs.com!1339083645!31453512!1
X-Originating-IP: [209.85.213.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16194 invoked from network); 7 Jun 2012 15:40:46 -0000
Received: from mail-yw0-f45.google.com (HELO mail-yw0-f45.google.com)
	(209.85.213.45)
	by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 15:40:46 -0000
Received: by yhoo21 with SMTP id o21so606644yho.32
	for ; Thu, 07 Jun 2012 08:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=FMBlyQ7UcRrkLWz8uO+oNao+IyyYLYQ6HFd6Q/tjG6Q=;
	b=J9KDaO4tn1qvLc0iY/0OM4QW1H2GSDyXXfxZ4OEk8vuqrtdoKy9nMSkll7vCpCSA58
	OedMQL4N7i7did8fZp+7zOcbQtJixJle9qTDlj0VxgEH8RVKqLz9ZLrzxlAk7iK+h02/
	nyde4TLWdkswjh4AijiLspuqkzbR7HwR5Nn9wbx+BVk+0OPnTWyKsbKQNGdWloxb/X7c
	iO33OMf9rDEscXgNohXJNhCmJAtqefUnFt2TnrunoaFJhcLtwXKzgSljipqiHx9VBwbH
	YrQYGg5yYpOFMfYwkdhfY5VGFEemA6tvwaH7vtvEStD/9PCG0VSb4IFPE5+9/nwF5JVz
	btIw==
Received: by 10.101.137.39 with SMTP id p39mr732432ann.73.1339083645309;
	Thu, 07 Jun 2012 08:40:45 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id z42sm11199390yhd.1.2012.06.07.08.40.44
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 07 Jun 2012 08:40:44 -0700 (PDT)
Message-ID: <4FD0CB5C.7050402@gmail.com>
Date: Thu, 07 Jun 2012 11:40:12 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org" 
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

SlVTVCBhIGhlYWRzIHVwLCB0aGUgbGF0ZXN0IHJlbGFzZSBvZiB4ZW4tdW5zdGFibGUuaGcgaXMg
IiAyNTQ1OSIgYXMgb2YgCnRvZGF5LCBBTkQgaSBqdXN0IHRyaWVkIGNvbXBpbGluZyBpdCBhbmQg
aXQgZmluYWxseSB3b3JrcyBhbmQgY29tcGlsZXMgCndpdGhvdXQgZXJyb3JzIG9yIGFueSBhZGRp
dGlvbmFsIHBhdGNoZXMuR3JhbnRlZCwgb25seSB0cmllZCBpdCBvbiAKRGViaWFuIFdoZWV6eS4g
SWYgeW91IGFyZSBhZHZhbnRlcmlvdXMsIHlvdSBjb3VsZCB0cnkgaXQgb24gVWJ1bnR1IDEyLjA0
LgoKClNPLCBhbmQgYXdlc29tZSB0aHVtYnMgdXAgZm9yIHRoZSBYZW4tZGV2ZWwgdGVhbSBmb3Ig
Zml4aW5nIGFsbCBvZiB0aGUgCmlzc3VlcyBwcmV2ZW50IGNvbXBpbGUuLi4gOikKCgoKT24gNi81
LzIwMTIgMTI6NTMgUE0sIFdpbGwgTWNEZXJtb3R0IHdyb3RlOgo+IEZpbmFsbHkgZ290IGl0IHRv
IGJ1aWxkLCBuZWVkZWQgdGhpcyBwYXRjaDoKPiBodHRwOi8vbGlzdHMuZ251Lm9yZy9hcmNoaXZl
L2h0bWwvcWVtdS1kZXZlbC8yMDEyLTAyL21zZzAzNDYwLmh0bWwKPiBhbmQgdGhlIHRleGkyaHRt
bCBhbmQgdGV4aW5mbyBwYWNrYWdlcy4KPgo+IEdvb2QgdG8ga25vdyB0aGUgY29tcGlsYXRpb24g
cHJvY2VzcyBvbiBEZWJpYW4gaXMgYSBiaXQgbmljZXIgOikKPgo+IFRoYW5rIHlvdSBzbyBtdWNo
IGZvciB5b3VyIGhlbHAhCj4KPiAtLVdpbGwKPgo+Pj4+ICAgMDYvMDUvMTIgNTozMSBBTT4+Pgo+
IGh1bW0sIHdlbGwgdGhhdCBzdWNrcy4gSSBrbm93IGNvbXBpbGluZyBjaGFuZ2VzZXQgMjUzOTIg
d29ya3MgZm9yIG1lLAo+IHdpdGggdGhlIHBhY2thZ2VzIGFuZCBpbnN0cnVjdGlvbnMgaSBkZXNj
cmliZWQsIGkgaGF2ZSBjb21waWxlZCBpdAo+IHNldmVyYWwgdGltZXMgbm93LiBJIGtub3cgdGhl
IG1haW4gcmVhc29uIHdoeSB0aGUgbGF0ZXIgY2hhbmdlc3RzIHdvbid0Cj4gY29tcGlsZSBpcyBi
ZWNhdXNlIG9mIHRoZSBkaWZmZXJlbnQgR0NDIHZlcnNpb24gc2VlbSB0byBkbyBkaWZmZXJlbnQK
PiBlbm91Z2ggdG8gZmFpbCwgU08gbWF5YmUgVWJ1bnR1IGhhcyBhIGRpZmZlcmVudCBzdWJzZXQg
b2YgR0NDLiBJIGhhdmUgbm8KPgo+IGlkZWEuCj4KPiBXZWxsLCBpZiBpdCB3YXMgbm8gdHJvdWJs
ZSBmb3IgeW91LCBtYXliZSB0cnkgdG8gaW5zdGFsbCBEZWJpYW4gV2hlZXp5Cj4gYW5kIHRyeSB0
byBjb21waWxlIGFnYWluLiBPdGhlcndpc2UgaSBjb3VsZCBhbHdheXMgc2VuZCB5b3UgdGhlIFhl
biA0LjIKPiByZXYtMjUzOTIgY29tcGlsZWQgREVCIHBhY2thZ2UgYW5kIHlvdSBjYW4ganVzdCBp
bnN0YWxsIHRoYXQsIEJVVCB0aGF0Cj4gd291bGRuJ3Qgc29sdmUgeW91ciBwcm9ibGVtIGlmIHlv
dSB3YW50ZWQgdG8gY29tcGlsZSBpdCBsYXRlciBvbi4KPgo+Cj4+IEhtbSBzYW1lIGVycm9yOgo+
Pgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV91cGRh
dGVfZmlsZV9jcmVkw6I6Cj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29s
cy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+IGVycm9y
OiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlv
bikKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRp
ci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4gbm90ZTogZWFjaCB1bmRlY2xh
cmVkIGlkZW50aWZpZXIgaXMgcmVwb3J0ZWQgb25seSBvbmNlIGZvciBlYWNoCj4gZnVuY3Rpb24K
Pj4gaXQgYXBwZWFycyBpbgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9v
bHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9sc3RhdMOiOgo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjg3OjM0Ogo+PiBl
cnJvcjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu
Y3Rpb24pCj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+IEluIGZ1bmN0aW9uIMOiaGFuZGxl
X3N5bWxpbmvDojoKPj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3Fl
bXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozMTQ6NjI6Cj4+IGVycm9yOiDD
okFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikK
Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9o
dy85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4gSW4gZnVuY3Rpb24gw6JoYW5kbGVfbGlua8Oi
Ogo+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPj4gZXJyb3I6IMOiQVRfRU1QVFlf
UEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+Pgo+IC9yb290
L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmly
dGlvLTlwLWhhbmRsZS5jOgo+PiBJbiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOiOgo+Pgo+IC9y
b290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMv
dmlydGlvLTlwLWhhbmRsZS5jOjM3Mzo1ODoKPj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVu
ZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQo+PiBtYWtlWzRdOiAqKiogWzlw
ZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxCj4+IG1ha2VbNF06ICoqKiBXYWl0aW5nIGZv
ciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+ICAgICBDQyAgICBobXAubwo+PiAgICAgQ0MgICAgbGli
ZGlzL2kzODYtZGlzLm8KPj4gICAgIExJTksgIHFlbXUtZ2EKPj4gICAgIExJTksgIHFlbXUtbmJk
Cj4+ICAgICBMSU5LICBxZW11LWltZwo+PiAgICAgTElOSyAgcWVtdS1pbwo+PiBtYWtlWzNdOiAq
KiogW3N1YmRpci1saWJodzY0XSBFcnJvciAyCj4+IG1ha2VbM106IExlYXZpbmcgZGlyZWN0b3J5
Cj4+IGAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci1y
ZW1vdGUnCj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJv
ciAyCj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzJwo+PiBtYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFsbF0gRXJyb3Ig
Mgo+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5Mi90b29scycKPj4gbWFrZTogKioqIFtpbnN0YWxsLXRvb2xzXSBFcnJvciAyCj4+Cj4+
IEkgaGFkIG1vc3Qgb2YgdGhlIHBhY2thZ3MsIEkgcmFuICJhcHQtZ2V0IGJ1aWxkLWRlcCB4ZW4i
IGZyb206Cj4+IGh0dHA6Ly93aWtpLnhlbi5vcmcvd2lraS9Db21waWxpbmdfWGVuX0Zyb21fU291
cmNlCj4+Cj4+IEJ1dCBpdCBzdGlsbCBlcnJvcnMgb24gdGhlIHZpcnRpbyBmaWxlLiBJIGhhZCBh
bHNvIHJlYWQgdGhhdCB0aGVzZQo+PiBlcnJvcnMgaGFkIHRvIGRpZmZlcmVudCB3aXRoIGRpZmZl
cmVudCBsaWJyYXJ5L2djYyB2ZXJzaW9ucy4gTWF5YmUKPj4gd2hlZXp5IGp1c3QgaGFzIG5ld2Vy
L2RpZmZlcmVudCB2ZXJzaW9ucyBvZiB0aG9zZSBiaW5hcmllcy9saWJzPwo+Pgo+PiAtLVdpbGwK
Pj4KPj4KPj4+Pj4gICAgMDYvMDQvMTIgMTE6NDUgQU0+Pj4KPj4gV0VMTCwgYWN0dWFsbHkgTk8g
bmVlZCB0byBpbnN0YWxsIFdoZWV6eS4gSSBhbSB2ZXJ5IHN1cmUgeW91IGNhbiBnZXQKPiBpdAo+
PiB3b3JraW5nIGp1c3QgYXMgZWFzaWx5IHdpdGggVWJ1bnR1Lgo+Pgo+PiBUaGUgb3RoZXIgdGhp
bmcgaSBmb3Jnb3QgdG8gbWVudGlvbiBpcyB5b3UgaGF2ZSB0byBoYXZlIGFsbCBvZiB0aGUKPj4g
cmVxdWlyZWQgcGFja2FnZXMgaW5zdGFsbGVkIGJlZm9yZSB5b3UgY2FuIGNvbXBpbGUgWGVuLiBJ
IHRoaW5rIHlvdQo+IGFyZQo+PiBqdXN0IG1pc3NpbmcgYSBidW5jaCBvZiBkZXBlbmRlbnQgcGFj
a2FnZXMuIFRoZSBwYWNrYWdlcyBpIHVzZSBhbmQKPiBoYXZlCj4+IGluc3RhbGxlZCBhcmUgYXMg
Zm9sbG93czoKPj4KPj4gc3VkbyBhcHQtZ2V0IGluc3RhbGwgd2dldCB0YXIgYnppcDIgYnVpbGQt
ZXNzZW50aWFsIGxpYm5jdXJzZXM1LWRldgo+PiBrZXJuZWwtcGFja2FnZSBmYWtlcm9vdCBiY2Mg
Z2NjIHNzaCBicmlkZ2UtdXRpbHMgcHl0aG9uLWRldiB1dWlkLWRldgo+PiBsaWJnbGliMi4wLWRl
diBsPiAgYmlzb24gcXQ0LWRldi10b29scyBwYXRjaCBvY2FtbC1maW5kbGliIGxpYnNkbDEuMi1k
ZXYKPj4KPj4gR3JhbnRlZCBzb21lIG9mIHRoZSBhYm92ZSBwYWNrYWdlcyBhcmUgbW9yZSBpbXBv
cnRhbnQgZm9yIGNvbXBpbGluZwo+IHRoZQo+PiBrZXJuZWwuCj4+Cj4+IFNPLCBhcyBsb25nIGFz
IHlvdSBoYXZlIGFsbCByZXF1aXJlZCBwYWNrYWdlcyBhbmQgZm9sbG93IHRoZQo+PiBpbnN0cnVj
dGlvbnMgYmVmb3JlIGFib3V0IGdldHRpbmcgYW5kIGNvbXBpbGluZyBYZW4gNC4yIHJldmlzaW9u
Cj4gMjUzOTIsCj4+IGl0IHNob3VsZCBiZSBmaW5lLCBubyBtYXR0ZXIgaWYgeW91IGFyZSB1c2lu
ZyBEZWJpYW4gb3IgVWJ1bnR1LiBVYnVudHUKPj4gaG93ZXZlciAibWlnaHQiIG5lZWQgbW9yZSBw
YWNrYWdlcywgbm90IHN1cmUsICBpIGhhdmUgbm90IGNvbXBpbGVkIFhlbgo+PiB1bmRlciBVYnVu
dHUgeWV0Lgo+Pgo+Pgo+Pgo+PiBPbiA2LzQvMjAxMiAxMjo0MyBQTSwgV2lsbCBNY0Rlcm1vdHQg
d3JvdGU6Cj4+PiBEYXJuLCBtYWRlIGl0IGZhcnRoZXIgYnV0IG5vdyBJIGdldCB0aGlzOgo+Pj4K
Pj4+IENDICAgIGxpYmh3NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubwo+Pj4gICAgICBDQyAgICBs
aWJodzY0LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vCj4+PiAgICAgIENDICAgIHFlbXUtY2hhci5v
Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVtdS14ZW4tZGly
L2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+Pj4gSW4gZnVuY3Rpb24gw6JoYW5kbGVfdXBk
YXRlX2ZpbGVfY3JlZMOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rv
b2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo3MDo1ODoKPj4+IGVy
cm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5j
dGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6NTg6Cj4+PiBub3RlOiBlYWNoIHVu
ZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gKPj4gZnVu
Y3Rpb24KPj4+IGl0IGFwcGVhcnMgaW4KPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0y
NTM5Mi90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJ
biBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzo4
NzozNDoKPj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2Ug
aW4gdGhpcyBmdW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90
b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5j
dGlvbiDDomhhbmRsZV9zeW1saW5rw6I6Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYt
MjUzOTIvdG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2
MjoKPj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4g
dGhpcyBmdW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29s
cy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5jdGlv
biDDomhhbmRsZV9saW5rw6I6Cj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMzNzo0NToKPj4+
IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm
dW5jdGlvbikKPj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scy9xZW11
LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+PiBJbiBmdW5jdGlvbiDDomhh
bmRsZV9jaG93bsOiOgo+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGctcmV2LTI1MzkyL3Rvb2xz
L3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzozNzM6NTg6Cj4+PiBlcnJv
cjogw6JBVF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rp
b24pCj4+PiBtYWtlWzRdOiAqKiogWzlwZnMvdmlydGlvLTlwLWhhbmRsZS5vXSBFcnJvciAxCj4+
PiBtYWtlWzRdOiAqKiogV2FpdGluZyBmb3IgdW5maW5pc2hlZCBqb2JzLi4uLgo+Pj4gICAgICBD
QyAgICBzYXZldm0ubwo+Pj4gICAgICBDQyAgICBtc21vdXNlLm8KPj4+ICAgICAgQ0MgICAgcHMy
Lm8KPj4+IG1ha2VbM106ICoqKiBbc3ViZGlyLWxpYmh3NjRdIEVycm9yIDIKPj4+IG1ha2VbM106
ICoqKiBXYWl0aW5nIGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCj4+PiBtYWtlWzNdOiBMZWF2aW5n
IGRpcmVjdG9yeQo+Pj4gYC9yb290L3hlbi11bnN0YWJsZS5oZy1yZXYtMjUzOTIvdG9vbHMvcWVt
dS14ZW4tZGlyLXJlbW90ZScKPj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14
ZW4tZGlyXSBFcnJvciAyCj4+PiBtYWtlWzJdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycKPj4+IG1ha2VbMV06ICoqKiBbc3ViZGlycy1p
bnN0YWxsXSBFcnJvciAyCj4+PiBtYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVu
LXVuc3RhYmxlLmhnLXJldi0yNTM5Mi90b29scycKPj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29s
c10gRXJyb3IgMgo+Pj4KPj4+IFdpdGggcmV2aXNpb24gMjUzOTIuIFRoYW5rIHlvdSBzbyBtdWNo
IGZvciB5b3VyIGNsZWFyIGluc3RydWN0aW9ucyEgSQo+Pj4gd2lsbCBpbnN0YWxsIHdoZWV6eSB0
b25pZ2h0IGFuZCB0cnkgdGhlIGJ1aWxkIGFnYWluLgo+Pj4KPj4+IC0tV2lsbAo+Pj4KPj4+Pj4+
ICAgICAwNi8wNC8xMiA0OjU2IEFNPj4+Cj4+PiBPbiA2LzQvMjAxMiAyOjU4IEFNLCBXaWxsIE1j
RGVybW90dCB3cm90ZToKPj4+PiBJJ20gbm90IHN1cmUgd2hhdCB2ZXJzaW9uIChob3cgZG8gSSBj
aGVjaz8pIGJ1dCBJIGp1c3QgY2xvbmVkIGZyb20KPj4+IHRoYXQKPj4+PiBVUkwgdG9kYXkuCj4+
Pj4KPj4+PiAtLVdpbGwKPj4+IFdlbGwgdGhhbiB5b3UgcHJvYmFibHkgYWxyZWFkeSBoYXZlIHRo
ZSBsYXRlc3QgcmV2aXNpb24uIFlvdSBjYW4gYWxzbwo+Pj4gY2hlY2sgd2hhdCByZXZpc2lvbiB5
b3VyIGxvY2FsbHkgY2xvbmVkIHJlcG9zaXRvcnkgaXMgYXQgYnkgZ29pbmcgdG8KPj4gdGhlCj4+
PiBmb2xkZXIgYW5kIHJ1bm5pbmc6Cj4+Pgo+Pj4gKmNkICAuLi94ZW4tdW5zdGFibGUuaGcKPj4+
IGhnIHN1bW1hcnkKPj4+ICoKPj4+IEFuZCB0aGF0IHdpbGwgc2hvdyB5b3UgYSBzdW1tYXJ5IG9m
IHRoZSBsb2NhbCBtZXJjdXJpYWwgY2xvbmUgYW5kCj4gc2hvdwo+Pj4gdGhlIGxhdGVzdCByZXZp
c2lvbnMgdGhhdCB3YXMgY2xvbmVkLgo+Pj4KPj4+IFNPLCBhbnlob3csIGNvbXBpbGluZyB0aGUg
WGVuIDQuMi11bnN0YWJsZSBmcm9tIHRoZSBtZXJjdXJpYWwgaGFzIG5vdAo+Pj4gYmVlbiB3b3Jr
aW5nIHZlcnkgd2VsbCBmb3IgYSBmZXcgd2Vla3Mgbm93LiBJIGhhdmUgYXNrZWQgdGhlCj4gWGVu
LWRldmVsCj4+PiBhYm91dCB0aGF0IGEgc2V2ZXJhbCB0aW1lcyBhbmQgdGhlcmUgYXJlIGlzc3Vl
cyBhbmQgcHJvYmxlbXMgd2l0aAo+Pj4gZGlmZmVyZW50IEdDQyBjb21waWxlcnMgQU5EIHRoZSBY
ZW4tZGV2ZWwgdGVhbSBrbm93cyBhbGwgdGhhdCBhbmQgYXJlCj4+PiB3b3JraW5nIG9uIGZpeGlu
ZyB0aGF0Lgo+Pj4KPj4+IEZvciBub3csIHRoZSBMQVNUIHJldmlzaW9uIGkgd2FzIGFibGUgdG8g
Y29tcGlsZSBhbmQgZ2V0IHJ1bm5pbmcgd2FzCj4+PiAqInJldmlzaW9uIDI1MzkyKiIsIGJ1dCBl
dmVuIHRoYXQgd2FzIHBvc3NpYmx5IE9OTFkgaWYgeW91IHJlbW8+PiAgcGF0Y2guIFlvdSBjYW4g
dHJ5IHRvIGRvd25sb2FkIGFuZCBjb21waWxlIFRIQVQgdmVyc2lvbiBieSBydW5uaW5nCj4gdGhl
Cj4+PiBmb2xsb3dpbmcgY29tbWFuZHM6Cj4+Pgo+Pj4gXypDbG9uaW5nIFhlbjoqXwo+Pj4gKi0g
Y2QgL3NvbWUvZGlyZWN0b3J5L2luL2hvbWUKPj4+IC0gcmV2PTI1MzkyJiYgICAgaGcgY2xvbmUg
LXIgJHJldgo+Pj4gaHR0cDovL3hlbmJpdHMueGVuLm9yZy9oZy94ZW4tdW5zdGFibGUuaGcvIHhl
bi11bnN0YWJsZS5oZy1yZXYtJHtyZXZ9Cj4+PiAtIGNkIHhlbi11bnN0YWJsZS5oZy1yZXYtMjUz
OTIKPj4+IC0gaGcgYmFja291dCAtciAyNTM2NCoKPj4+Cj4+PiBUaGlzIHdpbGwgY2xvbmUgdGhl
IHhlbi11bnN0YWJsZS5oZyBtZXJjdXJpYWwgYW5kIGRvd25sb2FkIFhlbgo+Pj4gNC4yLXVuc3Rh
YmxlIHJldmlzaW9uIDI1MzkyIGludG8gdGhlIGZvbGRlcgo+Pj4gIip4ZW4tdW5zdGFibGUuaGct
cmV2LTI1MzkyKiIuIFJ1bm5pbmcgdGhlIGNvbW1hbmQgIipoZyBiYWNrb3VyIC1yCj4+PiAyNTM2
NCoiIHJlbW92ZXMgb3IgYmFja3Mgb3V0IHRoYXQgcGFydGljdWxhciBwYXRjaC4gSXQgc2VlbXMg
dGhhdAo+Pj4gd2l0aG91dCB0aGF0LCBldmVuIHRoYXQgcmV2aXNpb24gd29udCBjb21waWxlLgo+
Pj4KPj4+IF8qQ29tcGlsaW5nIFhlbjoqXwo+Pj4gVGhhbiBqdXN0IHNpbXBseSBydW4gdGhlc2Ug
Y29tbWFuZHMgdG8gY29tcGlsZSBYZW4uCj4+Pgo+Pj4gKi0gY2QgeGVuLXVuc3RhYmxlLmhnLXJl
di0yNTM5MioKPj4+ICotIC4vY29uZmlndXJlCj4+PiAtIHN1ZG8gbWFrZSAtajUgeGVuJiYgICAg
c3VkbyBtYWtlIFRoZSBjb21waWxlIGNvbW1hbmQgYWJvdmUganVzdAo+PiBzdHJpbmdzIHRvZ2V0
aGVyIHRoZSA0IGNvbXBpbGluZyBjb21tYW5kcwo+Pj4gdG8gcnVuIGFuZCB3aWxsIGV4ZWN1dGUg
b25lIGFmdGVyIHRoZSBvdGhlciBTTyB5b3UgZG9uJ3QgaGF2ZSB0bwo+Pj4gbWFudWFsbHkgcnVu
IGVhY2ggYW5kIGV2ZXJ5IG9uZS4gQWxzbywgSW4gdGhlIGFib3ZlICIqbWFrZSoiCj4gY29tbWFu
ZHMsCj4+PiB1c2luZyB0aGUgIiotajUqIiBvcHRpb24gYWZ0ZXIgZWFjaCBtYWtlIHRlbGxzIHRo
ZSBjb21waWxlIHRvIHVzZQo+IG1vcmUKPj4+IHRoYW4gb25lIGNvcmUgdG8gY29tcGlsZSB3aXRo
LiBJdCBzcGVlZHMgdXAgdGhlIGNvbXBpbGk+ICAgaGF2ZSBhCj4gbXVsdGktY29yZSBDUFUuIFNP
IGluIG15IGNhc2UsIGkgaGF2ZSBhIFF1YWQgQ29yZSBDUFUsIHNvIHRoYXQKPj4+IGNvbW1hbmQg
b3B0aW9uIGlzICIqLWoxICsgbnVtYmVyIG9mIENQVSBjb3JlcyoiLiBZb3UgY2FuIG1vZGlmeSBv
cgo+Pj4gcmVtb3ZlIHRoYXQgYXMgeW91IHdpc2guCj4+Pgo+Pj4gVGhlIGFib3ZlIHdpbGwgYWxz
byBjcmVhdGUgZm9yIHlvdSBhIG5pY2UgREVCIHBhY2thZ2UgYWZ0ZXIgYWxsIHRoZQo+Pj4gY29t
cGlsaW5nIGlzIGRvbmUsIGlmIHlvdSBkbyBub3Qgd2FudCB0byBjcmVhdGUgYSBERUIgcGFja2Fn
ZSBhdCB0aGUKPj4gZW5kCj4+PiBvZiBpdCBhbGwsIHRoYW4ganVzdCByZW1vdmUgdGhlIGxhc3Qg
IiomJiAgICBzdWRvIG1ha2UgLWo1IGRlYioiCj4+IGNvbW1hbmQuCj4+PiBHcmFudGVkLCBpIGFt
IHJ1bm5pbmcgYW5kIGRvaW5nIGFsbCBvZiB0aGlzIG9uIERlYmlhbiBXaGVlenkgQlVUIGkKPj4g
dGhlcmUKPj4+IGFyZW4ndCBhbnkgZGlmZmVyZW5jZXMgaW4gY29tcGlsaW5nIGl0IG9uIFVidW50
dSAxMi4wNC4KPj4+Cj4+Pgo+Pj4KPj4+Cj4+Pj4+Pj4gICAgICAwNi8wMy8xMiAyOjM0IFBNPj4+
Cj4+Pj4gVGhlIGxhdGVzdCByZXZpc2lvbiBvZiBYZW4gNC4yLXVuc3RhYmxlIGlzICoyNTQ1Mjo2
YmVhNjNlNmM3ODAqIGF0Cj4+IHRoZQo+Pj4+IGxpbmsgKmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcv
aGcveGVuLXVuc3RhYmxlLmhnLyogV2hhdCByZXZlcnNpb24gb2YKPj4+IFhlbgo+Pj4+IDQuMi1V
bnN0YWJsZSBhcmUgeW91IHRyeWluZyB0byBjb21waWxlPwo+Pj4+Cj4+Pj4KPj4+Pj4gSGVsbG8s
Cj4+Pj4+Cj4+Pj4+IEkgYW0gdHJ5aW5nIHRvIGNvbXBpbGUgeGVuIDQuMiB1bnN0YWJsZSBmcm9t
IG1lcmN1cmlhbC4gSSBjYW4ndCBnZXQKPj4+PiBwYXN0Cj4+Pj4+IHRoZSBtYWtlIHRvb2xzIHN0
ZXAuIFdoZW4gSSBydW4gbWFrZSB0b29scywgdGhlIGJ1aWxkIGZhaWxzIHdpdGg6Cj4+Pj4+Cj4+
Pj4+IENDICAgIGxpYmh3NjQvOXBmcy9jb3hhdHRyLm8KPj4+Pj4gICAgICAgIENDICAgIGxpYmh3
NjQvOXBmcy92aXJ0aW8tOXAtc3ludGgubwo+Pj4+PiAgICAgICAgQ0MgICAgbGliaHc2NC85cGZz
L3ZpcnRpby05cC1oYW5kbGUubwo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9x
ZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+Pj4gSW4KPj4+Pj4gZnVu
Y3Rpb24gw6JoYW5kbGVfdXBkYXRlX2ZpbGVfY3JlZMOiOgo+Pj4+Pgo+IC9yb290L3hlbi11bnN0
YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6NzA6
NTg6Cj4+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1c2Ug
aW4gdGhpcyBmdW5jdGlvbikKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMvcWVt
dS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjcwOjU4Ogo+Pj4+PiBub3RlOiBl
YWNoIHVuZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UgZm9yIGVhY2gK
Pj4+PiBmdW5jdGlvbgo+Pj4+PiBpdCBhcHBlYXJzIGluCj4+Pj4+Cj4gL3Jvb3QveGVuLXVuc3Rh
YmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3ZpcnRpby05cC1oYW5kbGUuYzoKPj4+
PiBJbgo+Pj4+PiBmdW5jdGlvbiDDomhhbmRsZV9sc3RhdMOiOgo+Pj4+Pgo+IC9yb290L3hlbi11
bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6
ODc6MzQ6Cj4+Pj4+IGVycm9yOiDDokFUX0VNUFRZX1BBVEjDoiB1bmRlY2xhcmVkIChmaXJzdCB1
c2UgaW4gdGhpcyBmdW5jdGlvbikKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMv
cWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOgo+Pj4+IEluCj4+Pj4+IGZ1
bmN0aW9uIMOiaGFuZGxlX3N5bWxpbmvDojoKPj4+Pj4KPiAvcm9vdC94ZW4tdW5zdGFibGUuaGcv
dG9vbHMvcWVtdS14ZW4tZGlyL2h3LzlwZnMvdmlydGlvLTlwLWhhbmRsZS5jOjMxNDo2MjoKPj4+
Pj4gZXJyb3I6IMOiQVRfRU1QVFlfUEFUSMOiIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlz
IGZ1bmN0aW9uKQo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1k
aXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6Cj4+Pj4gSW4KPj4+Pj4gZnVuY3Rpb24gw6Jo
YW5kbGVfbGlua8OiOgo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhl
bi1kaXIvaHcvOXBmcy92aXJ0aW8tOXAtaGFuZGxlLmM6MzM3OjQ1Ogo+Pj4+PiBlcnJvcjogw6JB
VF9FTVBUWV9QQVRIw6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+
Pj4+Cj4gL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci9ody85cGZzL3Zp
cnRpby05cC1oYW5kbGUuYzoKPj4+PiBJbgo+Pj4+PiBmdW5jdGlvbiDDomhhbmRsZV9jaG93bsOi
Ogo+Pj4+Pgo+IC9yb290L3hlbi11bnN0YWJsZS5oZy90b29scy9xZW11LXhlbi1kaXIvaHcvOXBm
cy92aXJ0aW8tOXAtaGFuZGxlLmM6MzczOjU4Ogo+Pj4+PiBlcnJvcjogw6JBVF9FTVBUWV9QQVRI
w6IgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCj4+Pj4+IG1ha2VbNF06
ICoqKiBbOXBmcy92aXJ0aW8tOXAtaGFuZGxlLm9dIEVycm9yIDEKPj4+Pj4gbWFrZVszXTogKioq
IFtzdWJkaXItbGliaHc2NF0gRXJyb3IgMgo+Pj4+PiBtYWtlWzNdOiBMZWF2aW5nIGRpcmVjdG9y
eQo+Pj4+PiBgL3Jvb3QveGVuLXVuc3RhYmxlLmhnL3Rvb2xzL3FlbXUteGVuLWRpci1yZW1vdGUn
Cj4+Pj4+IG1ha2VbMl06ICoqKiBbc3ViZGlyLWluc3RhbGwtcWVtdS14ZW4tZGlyXSBFcnJvciAy
Cj4+Pj4+IG1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibD4+Pj4g
IG1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcm9vdC94ZW4tdW5zdGFibGUuaGcvdG9vbHMn
Cj4+Pj4+IG1ha2U6ICoqKiBbaW5zdGFsbC10b29sc10gRXJyb3IgMgo+Pj4+Pgo+Pj4+PiBJIGFt
IHJ1bm5pbmcgdWJ1bnR1IDEyLjA0LCBrZXJuZWwgdmVyOiAzLjIuMC0yNC1nZW5lcmljCj4+Pj4+
Cj4+Pj4+IEFueSBpZGVhcz8gSSBoYXZlIGdvb2dsZWQgZnVyaW91c2x5IGFuZCBmb3VuZCBzb21l
IHBlb3BsZSB0YWxraW5nCj4+Pj4gYWJvdXQKPj4+Pj4gcWVtdS1rdm0gaGF2aW5nIHRoZSBzYW1l
IGlzc3VlOgo+Pj4+PiBodHRwczovL2J1Z3MubGF1bmNocGFkLm5ldC91YnVudHUvK3NvdXJjZS9x
ZW11LWt2bS8rYnVnLzkzMDE4MQo+Pj4+PiBCdXQgSSB3YXMgbm90IGFibGUgdG8gZmluZCB0aGUg
cGF0Y2gKPj4+Pj4KPj4+Pj4gVGhhbmtzIGluIGFkdmFuY2UhCj4+Pj4+Cj4+Pj4+Cj4+Pj4+Cj4+
Pj4+IE1lcmN1cmlhbG0KPj4+Pj4KPj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPj4+Pj4gWGVuLXVzZXJzIG1haWxpbmcgbGlzdAo+Pj4+PiBYZW4t
dXNlcnNAbGlzdHMueGVuLm9yZwo+Pj4+PiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnMK
Pj4KPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4g
WGVuLXVzZXJzIG1haWxpbmcgbGlzdAo+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCj4gaHR0cDov
L2xpc3RzLnhlbi5vcmcveGVuLXVzZXJzCj4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0
cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Thu Jun 07 16:19:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 16:19: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 1ScfPD-00017N-Ay; Thu, 07 Jun 2012 16:17:51 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScfPB-000179-Gf
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 16:17:49 +0000
Received: from [85.158.143.99:34084] by server-2.bemta-4.messagelabs.com id
	3D/92-17938-C24D0DF4; Thu, 07 Jun 2012 16:17:48 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-8.tower-216.messagelabs.com!1339085866!22008390!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1492 invoked from network); 7 Jun 2012 16:17:48 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 16:17:48 -0000
Received: by obbwd20 with SMTP id wd20so1527022obb.32
	for ; Thu, 07 Jun 2012 09:17:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:x-gm-message-state;
	bh=s5OHImrcf85VufGehqBmpg1SQ5Jdik0dww3cDUxJ+Mk=;
	b=FOL/PUGqPIERCZWq3eULALtLPZoAEE3LTlskbYJNpjG1f/dMLyEAOAcrDwqMYK3WKx
	MFCYT73TfnbmfqF7a9HaIPC1fkl1EPVpLIHLbwzOhaNI5PTUUiR2Fp26Nhnxz+5HcAbe
	STquyGlkXOHt7UxgTbbsH+MuZBSpnS1PkWUXYfbFSVnXeZlVy7n/VDFUxrkLy+D9lAkM
	xLJZLouJwXgCihvHtN5+kjDaquRroKUo326L2lQh31Z/LJXeuhmnKw7StexFFfo2MTFO
	rAAqRl5BX35mW3QRdo/lMKwA6RZoaiBeOYZI69sGNgtUkNqF33thv/1GBIr6699bpyVt
	QhnQ==
Received: by 10.182.131.2 with SMTP id oi2mr2751027obb.43.1339085866497; Thu,
	07 Jun 2012 09:17:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 09:17:26 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: <4FD0CB5C.7050402@gmail.com>
References: 
	<4FD0CB5C.7050402@gmail.com>
From: Rolu 
Date: Thu, 7 Jun 2012 18:17:26 +0200
Message-ID: 
To: cyberhawk001@gmail.com
X-Gm-Message-State: ALoCoQkzwd0pWOg0NHo00E14Jy0ruL1c/pI8t3iwbddikfgwgGEoAHN1+OMZtHyvTHuAagVUczkU
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 5:40 PM,   wrote:
> JUST a heads up, the latest relase of xen-unstable.hg is " 25459" as of
> today, AND i just tried compiling it and it finally works and compiles
> without errors or any additional patches.Granted, only tried it on Debian
> Wheezy. If you are advanterious, you could try it on Ubuntu 12.04.
>
>
> SO, and awesome thumbs up for the Xen-devel team for fixing all of the
> issues prevent compile... :)
>

I compiled 25459 on Ubuntu 12.04 today and still needed the patch.
Other than that it compiles properly. It didn't work though, as I
described in another mail to this list. For reference, I needed these
packages to build deb:

apt-get build-dep xen
apt-get install build-essential mercurial pkg-config libglib2.0-dev
libyajl-dev git flex texinfo fakeroot

This was in addition to whatever I got by installing
xen-hypervisor-4.1-amd64 and xen-tools earlier. Other than that, it's
a fresh 12.04 server install.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 16:19:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 16:19: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 1ScfPD-00017N-Ay; Thu, 07 Jun 2012 16:17:51 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScfPB-000179-Gf
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 16:17:49 +0000
Received: from [85.158.143.99:34084] by server-2.bemta-4.messagelabs.com id
	3D/92-17938-C24D0DF4; Thu, 07 Jun 2012 16:17:48 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-8.tower-216.messagelabs.com!1339085866!22008390!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1492 invoked from network); 7 Jun 2012 16:17:48 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 16:17:48 -0000
Received: by obbwd20 with SMTP id wd20so1527022obb.32
	for ; Thu, 07 Jun 2012 09:17:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type:x-gm-message-state;
	bh=s5OHImrcf85VufGehqBmpg1SQ5Jdik0dww3cDUxJ+Mk=;
	b=FOL/PUGqPIERCZWq3eULALtLPZoAEE3LTlskbYJNpjG1f/dMLyEAOAcrDwqMYK3WKx
	MFCYT73TfnbmfqF7a9HaIPC1fkl1EPVpLIHLbwzOhaNI5PTUUiR2Fp26Nhnxz+5HcAbe
	STquyGlkXOHt7UxgTbbsH+MuZBSpnS1PkWUXYfbFSVnXeZlVy7n/VDFUxrkLy+D9lAkM
	xLJZLouJwXgCihvHtN5+kjDaquRroKUo326L2lQh31Z/LJXeuhmnKw7StexFFfo2MTFO
	rAAqRl5BX35mW3QRdo/lMKwA6RZoaiBeOYZI69sGNgtUkNqF33thv/1GBIr6699bpyVt
	QhnQ==
Received: by 10.182.131.2 with SMTP id oi2mr2751027obb.43.1339085866497; Thu,
	07 Jun 2012 09:17:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 09:17:26 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: <4FD0CB5C.7050402@gmail.com>
References: 
	<4FD0CB5C.7050402@gmail.com>
From: Rolu 
Date: Thu, 7 Jun 2012 18:17:26 +0200
Message-ID: 
To: cyberhawk001@gmail.com
X-Gm-Message-State: ALoCoQkzwd0pWOg0NHo00E14Jy0ruL1c/pI8t3iwbddikfgwgGEoAHN1+OMZtHyvTHuAagVUczkU
Cc: "xen-users@lists.xen.org" 
Subject: Re: [Xen-users] Xen unstable fails to build on ubutnu 12.04
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 5:40 PM,   wrote:
> JUST a heads up, the latest relase of xen-unstable.hg is " 25459" as of
> today, AND i just tried compiling it and it finally works and compiles
> without errors or any additional patches.Granted, only tried it on Debian
> Wheezy. If you are advanterious, you could try it on Ubuntu 12.04.
>
>
> SO, and awesome thumbs up for the Xen-devel team for fixing all of the
> issues prevent compile... :)
>

I compiled 25459 on Ubuntu 12.04 today and still needed the patch.
Other than that it compiles properly. It didn't work though, as I
described in another mail to this list. For reference, I needed these
packages to build deb:

apt-get build-dep xen
apt-get install build-essential mercurial pkg-config libglib2.0-dev
libyajl-dev git flex texinfo fakeroot

This was in addition to whatever I got by installing
xen-hypervisor-4.1-amd64 and xen-tools earlier. Other than that, it's
a fresh 12.04 server install.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 17:18:04 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 17:18:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScgKH-0004TQ-Ld; Thu, 07 Jun 2012 17:16:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScgKG-0004Sj-Go
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 17:16:48 +0000
Received: from [85.158.143.99:47780] by server-3.bemta-4.messagelabs.com id
	06/CB-29237-EF1E0DF4; Thu, 07 Jun 2012 17:16:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1339089404!28418877!1
X-Originating-IP: [209.85.215.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_30_40,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7764 invoked from network); 7 Jun 2012 17:16:45 -0000
Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com)
	(209.85.215.173)
	by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 17:16:45 -0000
Received: by eaak12 with SMTP id k12so357265eaa.32
	for ; Thu, 07 Jun 2012 10:16:44 -0700 (PDT)
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:cc
	:subject:references:in-reply-to:content-type;
	bh=+dQE84Lyt4jpZ0IJZeLEfv6m4bSb6fZCJtgrrEQt9mk=;
	b=nMTP2mzqExuIfn26/xtC9g5KcqsUx/BT31cR94P8NimlVSWwCk1wWQ3V2WG4RcIwQJ
	qnD+uDzf06sJVxpnh6EL/0jkISUrejH271+8re6WZ+ipQlIqz1Gp4vpQeA2kZEjf3xJB
	siFpwIDoN+K3XLGGnrXDpW5agPeLg6cX6003SIehW7GTC8t/K9N23JnTCjc3k+5T8kxT
	YgyJTWxZdiGvsYSHNEVTSMPucLHzvbybLxWAm0E6WDyljW3dvAIZB6m2h6UmGKVjDXeY
	odARLxZG11hT8SmwFbY8Q7rOpWDTcU+cetYuqiH6WjIEejzpTkWloPKrFdOYfj5zZHgX
	y0EA==
Received: by 10.14.185.137 with SMTP id u9mr1569216eem.220.1339089404594;
	Thu, 07 Jun 2012 10:16:44 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id m5sm12981044eeh.17.2012.06.07.10.16.40
	(version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 10:16:42 -0700 (PDT)
Message-ID: <4FD0E1F4.4020203@xen.org>
Date: Thu, 07 Jun 2012 18:16:36 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: George Dunlap 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
	
In-Reply-To: 
Cc: Lars Kurth , Rolu ,
	"xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org, xen-users@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4044789401465690797=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============4044789401465690797==
Content-Type: multipart/alternative;
 boundary="------------000207000704050909050209"

This is a multi-part message in MIME format.
--------------000207000704050909050209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/06/2012 14:14, George Dunlap wrote:
> Sorry to throw in a criticism without a constructive solution, but I 
> just want to register one opinion: To me clicking on a link and seeing 
> a "Category" page says very strongly, "I couldn't be bothered to 
> actually do any work here; I'll leave you to do all the work to figure 
> out what page you need." 
One question: do you feel this for any category page, or just "empty" 
category pages? For example, if the content listed in 
http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals was actually the 
first thing you saw when going to 
http://wiki.xen.org/wiki/Category:Manual would you still feel that way?

> When I encounter a Category page on my walk through the Xen wiki, I 
> don't even look, but immediately turn to Google. I think a page which 
> is has some kind of logical flow to it but perhaps a little out-dated 
> is much better than a page which just tosses up a bunch of titles in 
> no order and lets you figure it out. 
There is no reason why a category page cannot have a logical flow at the 
top and just the list of articles at the bottom.

> I can certainly see that there were "liveness" problems with summary 
> pages; but I don't think that the Categories pages, as we have now, 
> really help that much. 
Right now they are just indexes. The advantage of using category pages 
with content at the top is that it is relatively easy to make sure that 
every article in the category is in some kind of logical group.

> I think in an ideal world, we'd have people who were "maintainers" of
> the wiki just like there are maintainers of different subsections of
> the codebase.  Until that time, could we maybe draw up a set of
> "tests" to run on the docs, which can be assigned to people on DocDay?
>   One simple thing could be, "Make sure X page is up-to-date" (which
> may include, "Look at the Category: page and make sure everything
> there is listed somewhere on the manually-generated page"); another
> could be a scenario, "Pretend you're a [foo] and you want to know
> [bar].  Start at the top level page and make sure you can find all the
> information you need."  If each "test" was something any motivated
> developer/community member could do, and only took 5-10 minutes, it
> should be pretty sustainable.  What do you think?
Again, that would be almost a case in point for having some better 
manually created index at the top of a category page.
If there was an easy way of finding out what is new in a category index 
(I am not sure it is), then creating such tests would be relatively easy.

However to be honest, there were already "easy" items like this since 
the beginning of docs days, which have been on the TODO list since day 
1. E.g.
* http://wiki.xen.org/wiki/Category:Contains_Needs_Formatting
* http://wiki.xen.org/wiki/Category:Contains_TODO
* http://wiki.xen.org/wiki/Category:Contains_Needs_Action

But apart from me, nobody really cares. So having some tests won't work, 
unless people will execute them. And I don't have much hope for that.

> One thing that might make the Category: page more useful is if we
> could include "index tags" on articles, and then sort the Category:
> pages by those tags instead of by title.  But I'm not sure how easy
> that is to do with the current wiki.
I am not quite sure what you mean. There are actually a few extensions 
which may deliver what you need, but of course we likely wont be able to 
install these as these dont come as Debian packages.

With those type of plug-ins it would be possible to create indexes 
using  criteria such as:
  - List Xen Tutorials (i.e. articles in Xen and Tutorials)
  - List Xen Tutorials for Debian
  - List XCP FAQs for Debian that have been edited recently
  - Etc.

Examples of such extensions are:

  * Semantic MediaWiki 
      o allows
        further intersection with sets of pages defined in terms of
        relations and attributes
      o provides
        relation- and attribute-related info about the selected pages
        and in-page display on any page of categories the same or
        another page is in

  * DynamicPageList
    
    (ext) or DynamicPageList
    
    (MW) extension can be used to:
      o intersection of categories
      o generate a list of all those articles (or a random sample)
      o show metadata of the articles (popularity, date of last update, ..)
      o show one or more chapters of the articles ('transclude' content)
      o show parameter values which are passed to the common template
      o order articles appropriately
      o present the result in a sortable table (e.g.)
      o use multi column output

  * Forum 
      o intersection of categories and complements of categories
      o provides the time of last edit for each page




--------------000207000704050909050209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    On 07/06/2012 14:14, George Dunlap wrote:
    

      Sorry to throw in a criticism without a constructive solution, but
      I
      just want to register one opinion: To me clicking on a link and
      seeing
      a "Category" page says very strongly, "I couldn't be bothered to
      actually do any work here; I'll leave you to do all the work to
      figure
      out what page you need." 

    One question: do you feel this for any category page, or just
    "empty" category pages? For example, if the content listed in http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals
    was actually the first thing you saw when going to
    http://wiki.xen.org/wiki/Category:Manual would you still feel that
    way?

    

    
When I encounter a Category page on my walk
      through the Xen wiki, I don't even look, but immediately turn to
      Google. I think a page which is has some kind of logical flow to
      it
      but perhaps a little out-dated is much better than a page which
      just
      tosses up a bunch of titles in no order and lets you figure it
      out.
    

    There is no reason why a category page cannot have a logical flow at
    the top and just the list of articles at the bottom.

    

    
I can certainly see that there were "liveness"
      problems with summary
      pages; but I don't think that the Categories pages, as we have
      now,
      really help that much.
    

    Right now they are just indexes. The advantage of using category
    pages with content at the top is that it is relatively easy to make
    sure that every article in the category is in some kind of logical
    group.

     

    

      
I think in an ideal world, we'd have people who were "maintainers" of
the wiki just like there are maintainers of different subsections of
the codebase.  Until that time, could we maybe draw up a set of
"tests" to run on the docs, which can be assigned to people on DocDay?
 One simple thing could be, "Make sure X page is up-to-date" (which
may include, "Look at the Category: page and make sure everything
there is listed somewhere on the manually-generated page"); another
could be a scenario, "Pretend you're a [foo] and you want to know
[bar].  Start at the top level page and make sure you can find all the
information you need."  If each "test" was something any motivated
developer/community member could do, and only took 5-10 minutes, it
should be pretty sustainable.  What do you think?

    

    Again, that would be almost a case in point for having some better
    manually created index at the top of a category page. 

    If there was an easy way of finding out what is new in a category
    index (I am not sure it is), then creating such tests would be
    relatively easy. 

    

    However to be honest, there were already "easy" items like this
    since the beginning of docs days, which have been on the TODO list
    since day 1. E.g.

    * http://wiki.xen.org/wiki/Category:Contains_Needs_Formatting

    * http://wiki.xen.org/wiki/Category:Contains_TODO

    * http://wiki.xen.org/wiki/Category:Contains_Needs_Action

    

    But apart from me, nobody really cares. So having some tests won't
    work, unless people will execute them. And I don't have much hope
    for that.

    

    

      
One thing that might make the Category: page more useful is if we
could include "index tags" on articles, and then sort the Category:
pages by those tags instead of by title.  But I'm not sure how easy
that is to do with the current wiki.


    

    I am not quite sure what you mean. There are actually a few
    extensions which may deliver what you need, but of course we likely
    wont be able to install these as these dont come as Debian packages.
    

    

    With those type of plug-ins it would be possible to create indexes
    using  criteria such as:

     - List Xen Tutorials (i.e. articles in Xen and Tutorials) 

     - List Xen Tutorials for Debian

     - List XCP FAQs for Debian that have been edited recently

     - Etc.

    

    Examples of such extensions are:

    
    
      
  • Semantic MediaWiki
        
      
          
    • allows
            further intersection with sets of pages defined in terms of
            relations and attributes
      • 
          
    • provides
            relation- and attribute-related info about the selected
            pages and in-page display on any page of categories the same
            or another page is in
      • 
        
    
        
    
      
    • 
      
  • DynamicPageList
        (ext) or DynamicPageList
        (MW) extension can be used to:
        
      
          
    • intersection of categories
      • 
          
    • generate a list of all those articles (or a random sample)
      • 
          
    • show metadata of the articles (popularity, date of last
            update, ..)
      • 
          
    • show one or more chapters of the articles ('transclude'
            content)
      • 
          
    • show parameter values which are passed to the common
            template
      • 
          
    • order articles appropriately
      • 
          
    • present the result in a sortable table (e.g.)
      • 
          
    • use multi column output
      • 
        
    
      
    • 
    

    
    
      
  • Forum
        
      
          
    • intersection of categories and complements of categories
      • 
          
    • provides the time of last edit for each page
      • 
        
    
      
    • 
    

    

    

  


--------------000207000704050909050209--


--===============4044789401465690797==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4044789401465690797==--


From xen-users-bounces@lists.xen.org Thu Jun 07 17:18:04 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 17:18:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1ScgKH-0004TQ-Ld; Thu, 07 Jun 2012 17:16:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScgKG-0004Sj-Go
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 17:16:48 +0000
Received: from [85.158.143.99:47780] by server-3.bemta-4.messagelabs.com id
	06/CB-29237-EF1E0DF4; Thu, 07 Jun 2012 17:16:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-7.tower-216.messagelabs.com!1339089404!28418877!1
X-Originating-IP: [209.85.215.173]
X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_30_40,HTML_MESSAGE,RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7764 invoked from network); 7 Jun 2012 17:16:45 -0000
Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com)
	(209.85.215.173)
	by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 17:16:45 -0000
Received: by eaak12 with SMTP id k12so357265eaa.32
	for ; Thu, 07 Jun 2012 10:16:44 -0700 (PDT)
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:cc
	:subject:references:in-reply-to:content-type;
	bh=+dQE84Lyt4jpZ0IJZeLEfv6m4bSb6fZCJtgrrEQt9mk=;
	b=nMTP2mzqExuIfn26/xtC9g5KcqsUx/BT31cR94P8NimlVSWwCk1wWQ3V2WG4RcIwQJ
	qnD+uDzf06sJVxpnh6EL/0jkISUrejH271+8re6WZ+ipQlIqz1Gp4vpQeA2kZEjf3xJB
	siFpwIDoN+K3XLGGnrXDpW5agPeLg6cX6003SIehW7GTC8t/K9N23JnTCjc3k+5T8kxT
	YgyJTWxZdiGvsYSHNEVTSMPucLHzvbybLxWAm0E6WDyljW3dvAIZB6m2h6UmGKVjDXeY
	odARLxZG11hT8SmwFbY8Q7rOpWDTcU+cetYuqiH6WjIEejzpTkWloPKrFdOYfj5zZHgX
	y0EA==
Received: by 10.14.185.137 with SMTP id u9mr1569216eem.220.1339089404594;
	Thu, 07 Jun 2012 10:16:44 -0700 (PDT)
Received: from [172.16.25.10] (b0fb96e9.bb.sky.com. [176.251.150.233])
	by mx.google.com with ESMTPS id m5sm12981044eeh.17.2012.06.07.10.16.40
	(version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 10:16:42 -0700 (PDT)
Message-ID: <4FD0E1F4.4020203@xen.org>
Date: Thu, 07 Jun 2012 18:16:36 +0100
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: George Dunlap 
References: 
	<20425.472.655564.805506@mariner.uk.xensource.com>
	<4FCF78BD.3040909@xen.org>
	
	
	
In-Reply-To: 
Cc: Lars Kurth , Rolu ,
	"xen-api@lists.xen.org" ,
	xen-devel@lists.xen.org, xen-users@lists.xen.org
Subject: Re: [Xen-users] [Xen-devel] Proposals/changes for a new Wiki
 Front-Page - need input/mods/creative proposals
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4044789401465690797=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============4044789401465690797==
Content-Type: multipart/alternative;
 boundary="------------000207000704050909050209"

This is a multi-part message in MIME format.
--------------000207000704050909050209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/06/2012 14:14, George Dunlap wrote:
> Sorry to throw in a criticism without a constructive solution, but I 
> just want to register one opinion: To me clicking on a link and seeing 
> a "Category" page says very strongly, "I couldn't be bothered to 
> actually do any work here; I'll leave you to do all the work to figure 
> out what page you need." 
One question: do you feel this for any category page, or just "empty" 
category pages? For example, if the content listed in 
http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals was actually the 
first thing you saw when going to 
http://wiki.xen.org/wiki/Category:Manual would you still feel that way?

> When I encounter a Category page on my walk through the Xen wiki, I 
> don't even look, but immediately turn to Google. I think a page which 
> is has some kind of logical flow to it but perhaps a little out-dated 
> is much better than a page which just tosses up a bunch of titles in 
> no order and lets you figure it out. 
There is no reason why a category page cannot have a logical flow at the 
top and just the list of articles at the bottom.

> I can certainly see that there were "liveness" problems with summary 
> pages; but I don't think that the Categories pages, as we have now, 
> really help that much. 
Right now they are just indexes. The advantage of using category pages 
with content at the top is that it is relatively easy to make sure that 
every article in the category is in some kind of logical group.

> I think in an ideal world, we'd have people who were "maintainers" of
> the wiki just like there are maintainers of different subsections of
> the codebase.  Until that time, could we maybe draw up a set of
> "tests" to run on the docs, which can be assigned to people on DocDay?
>   One simple thing could be, "Make sure X page is up-to-date" (which
> may include, "Look at the Category: page and make sure everything
> there is listed somewhere on the manually-generated page"); another
> could be a scenario, "Pretend you're a [foo] and you want to know
> [bar].  Start at the top level page and make sure you can find all the
> information you need."  If each "test" was something any motivated
> developer/community member could do, and only took 5-10 minutes, it
> should be pretty sustainable.  What do you think?
Again, that would be almost a case in point for having some better 
manually created index at the top of a category page.
If there was an easy way of finding out what is new in a category index 
(I am not sure it is), then creating such tests would be relatively easy.

However to be honest, there were already "easy" items like this since 
the beginning of docs days, which have been on the TODO list since day 
1. E.g.
* http://wiki.xen.org/wiki/Category:Contains_Needs_Formatting
* http://wiki.xen.org/wiki/Category:Contains_TODO
* http://wiki.xen.org/wiki/Category:Contains_Needs_Action

But apart from me, nobody really cares. So having some tests won't work, 
unless people will execute them. And I don't have much hope for that.

> One thing that might make the Category: page more useful is if we
> could include "index tags" on articles, and then sort the Category:
> pages by those tags instead of by title.  But I'm not sure how easy
> that is to do with the current wiki.
I am not quite sure what you mean. There are actually a few extensions 
which may deliver what you need, but of course we likely wont be able to 
install these as these dont come as Debian packages.

With those type of plug-ins it would be possible to create indexes 
using  criteria such as:
  - List Xen Tutorials (i.e. articles in Xen and Tutorials)
  - List Xen Tutorials for Debian
  - List XCP FAQs for Debian that have been edited recently
  - Etc.

Examples of such extensions are:

  * Semantic MediaWiki 
      o allows
        further intersection with sets of pages defined in terms of
        relations and attributes
      o provides
        relation- and attribute-related info about the selected pages
        and in-page display on any page of categories the same or
        another page is in

  * DynamicPageList
    
    (ext) or DynamicPageList
    
    (MW) extension can be used to:
      o intersection of categories
      o generate a list of all those articles (or a random sample)
      o show metadata of the articles (popularity, date of last update, ..)
      o show one or more chapters of the articles ('transclude' content)
      o show parameter values which are passed to the common template
      o order articles appropriately
      o present the result in a sortable table (e.g.)
      o use multi column output

  * Forum 
      o intersection of categories and complements of categories
      o provides the time of last edit for each page




--------------000207000704050909050209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    On 07/06/2012 14:14, George Dunlap wrote:
    

      Sorry to throw in a criticism without a constructive solution, but
      I
      just want to register one opinion: To me clicking on a link and
      seeing
      a "Category" page says very strongly, "I couldn't be bothered to
      actually do any work here; I'll leave you to do all the work to
      figure
      out what page you need." 

    One question: do you feel this for any category page, or just
    "empty" category pages? For example, if the content listed in http://wiki.xen.org/wiki/User:Rolu/Books_and_Manuals
    was actually the first thing you saw when going to
    http://wiki.xen.org/wiki/Category:Manual would you still feel that
    way?

    

    
When I encounter a Category page on my walk
      through the Xen wiki, I don't even look, but immediately turn to
      Google. I think a page which is has some kind of logical flow to
      it
      but perhaps a little out-dated is much better than a page which
      just
      tosses up a bunch of titles in no order and lets you figure it
      out.
    

    There is no reason why a category page cannot have a logical flow at
    the top and just the list of articles at the bottom.

    

    
I can certainly see that there were "liveness"
      problems with summary
      pages; but I don't think that the Categories pages, as we have
      now,
      really help that much.
    

    Right now they are just indexes. The advantage of using category
    pages with content at the top is that it is relatively easy to make
    sure that every article in the category is in some kind of logical
    group.

     

    

      
I think in an ideal world, we'd have people who were "maintainers" of
the wiki just like there are maintainers of different subsections of
the codebase.  Until that time, could we maybe draw up a set of
"tests" to run on the docs, which can be assigned to people on DocDay?
 One simple thing could be, "Make sure X page is up-to-date" (which
may include, "Look at the Category: page and make sure everything
there is listed somewhere on the manually-generated page"); another
could be a scenario, "Pretend you're a [foo] and you want to know
[bar].  Start at the top level page and make sure you can find all the
information you need."  If each "test" was something any motivated
developer/community member could do, and only took 5-10 minutes, it
should be pretty sustainable.  What do you think?

    

    Again, that would be almost a case in point for having some better
    manually created index at the top of a category page. 

    If there was an easy way of finding out what is new in a category
    index (I am not sure it is), then creating such tests would be
    relatively easy. 

    

    However to be honest, there were already "easy" items like this
    since the beginning of docs days, which have been on the TODO list
    since day 1. E.g.

    * http://wiki.xen.org/wiki/Category:Contains_Needs_Formatting

    * http://wiki.xen.org/wiki/Category:Contains_TODO

    * http://wiki.xen.org/wiki/Category:Contains_Needs_Action

    

    But apart from me, nobody really cares. So having some tests won't
    work, unless people will execute them. And I don't have much hope
    for that.

    

    

      
One thing that might make the Category: page more useful is if we
could include "index tags" on articles, and then sort the Category:
pages by those tags instead of by title.  But I'm not sure how easy
that is to do with the current wiki.


    

    I am not quite sure what you mean. There are actually a few
    extensions which may deliver what you need, but of course we likely
    wont be able to install these as these dont come as Debian packages.
    

    

    With those type of plug-ins it would be possible to create indexes
    using  criteria such as:

     - List Xen Tutorials (i.e. articles in Xen and Tutorials) 

     - List Xen Tutorials for Debian

     - List XCP FAQs for Debian that have been edited recently

     - Etc.

    

    Examples of such extensions are:

    
    
      
  • Semantic MediaWiki
        
      
          
    • allows
            further intersection with sets of pages defined in terms of
            relations and attributes
      • 
          
    • provides
            relation- and attribute-related info about the selected
            pages and in-page display on any page of categories the same
            or another page is in
      • 
        
    
        
    
      
    • 
      
  • DynamicPageList
        (ext) or DynamicPageList
        (MW) extension can be used to:
        
      
          
    • intersection of categories
      • 
          
    • generate a list of all those articles (or a random sample)
      • 
          
    • show metadata of the articles (popularity, date of last
            update, ..)
      • 
          
    • show one or more chapters of the articles ('transclude'
            content)
      • 
          
    • show parameter values which are passed to the common
            template
      • 
          
    • order articles appropriately
      • 
          
    • present the result in a sortable table (e.g.)
      • 
          
    • use multi column output
      • 
        
    
      
    • 
    

    
    
      
  • Forum
        
      
          
    • intersection of categories and complements of categories
      • 
          
    • provides the time of last edit for each page
      • 
        
    
      
    • 
    

    

    

  


--------------000207000704050909050209--


--===============4044789401465690797==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============4044789401465690797==--


From xen-users-bounces@lists.xen.org Thu Jun 07 23:29:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 23:29: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 1Scm7T-0004zr-J7; Thu, 07 Jun 2012 23:27:59 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scm7S-0004zm-R6
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 23:27:59 +0000
Received: from [85.158.138.51:10615] by server-1.bemta-3.messagelabs.com id
	65/52-01327-DF831DF4; Thu, 07 Jun 2012 23:27:57 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-14.tower-174.messagelabs.com!1339111676!25001459!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29502 invoked from network); 7 Jun 2012 23:27:57 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 23:27:57 -0000
Received: by obbwd20 with SMTP id wd20so2142367obb.32
	for ; Thu, 07 Jun 2012 16:27:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:content-type:x-gm-message-state;
	bh=WaaE8a5K8pZRtEa24R4OzDgrflPExt+QUok+7Xd13Lg=;
	b=HCfHc6mz9aQn8V+uJoafSgeeQ1CKKaHfeyOMfXlOMCIxxTFsFXK415uW7vmqiDvg6n
	LTkcJRmbqYc0i0CoEkMimf/A8bi4ldnv6F1gwBOjnkLu0LcGtFGXfQcTMJbqxPLx036R
	KjKtUNk+Y1jiXXlVjc9NCxTSHzv043RjDSNdIG25qt68ycYuOPIsjGLON7rYhuCK0wg+
	jaCd8YlLzZmwg9czUhw0KSYSgrkZ353L3i6CpyyT6su9lHCkuk4wzTx2mrb/6PY0lAiK
	xxMHU74VzfZIFSb2R+YN4QpgBnScBS8TygrkGrCqLc0mH8syLcwxqvvoJBW/BY85kIaJ
	yv6w==
Received: by 10.182.131.2 with SMTP id oi2mr3960412obb.43.1339111675615; Thu,
	07 Jun 2012 16:27:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 16:27:34 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
From: Rolu 
Date: Fri, 8 Jun 2012 01:27:34 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQlp+9TgmwPZiXHIbvAM1PmXvwOq8JwFy46n/grdbbr0Vv8NI2nXMyl3fnJ5ACgvxUM13zxm
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
> I've compiled Xen unstable from source and tried using it. When
> booting I do see Xen starting, but at the point where I normally start
> getting the dom0 kernel messages I just get a black screen for a few
> seconds, and then the machine reboots. It leaves no messages or log
> files, of course.
>
> revision I compiled: 25459
> OS: ubuntu 12.04
> dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
> kernel works with Xen 4.1 from the repositories.
>
> I had to apply the patch from
> http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
> get it to compile. Could this have broken something?
>
> Is there a way to have it display some log messages instead of rebooting?
>
> Any idea how to get it to work?
>
> If anyone else here is successfully using a recent revision, can you
> tell me which one, so I can try it too?
>

I've tried revision 25364 and 25099 (both picked because I found
someone reporting they worked for them). I got both to compile with
one or two patches, but with the same result.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Thu Jun 07 23:29:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 07 Jun 2012 23:29: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 1Scm7T-0004zr-J7; Thu, 07 Jun 2012 23:27:59 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Scm7S-0004zm-R6
	for xen-users@lists.xen.org; Thu, 07 Jun 2012 23:27:59 +0000
Received: from [85.158.138.51:10615] by server-1.bemta-3.messagelabs.com id
	65/52-01327-DF831DF4; Thu, 07 Jun 2012 23:27:57 +0000
X-Env-Sender: rolu@roce.org
X-Msg-Ref: server-14.tower-174.messagelabs.com!1339111676!25001459!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29502 invoked from network); 7 Jun 2012 23:27:57 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	7 Jun 2012 23:27:57 -0000
Received: by obbwd20 with SMTP id wd20so2142367obb.32
	for ; Thu, 07 Jun 2012 16:27:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:from:date
	:message-id:subject:to:content-type:x-gm-message-state;
	bh=WaaE8a5K8pZRtEa24R4OzDgrflPExt+QUok+7Xd13Lg=;
	b=HCfHc6mz9aQn8V+uJoafSgeeQ1CKKaHfeyOMfXlOMCIxxTFsFXK415uW7vmqiDvg6n
	LTkcJRmbqYc0i0CoEkMimf/A8bi4ldnv6F1gwBOjnkLu0LcGtFGXfQcTMJbqxPLx036R
	KjKtUNk+Y1jiXXlVjc9NCxTSHzv043RjDSNdIG25qt68ycYuOPIsjGLON7rYhuCK0wg+
	jaCd8YlLzZmwg9czUhw0KSYSgrkZ353L3i6CpyyT6su9lHCkuk4wzTx2mrb/6PY0lAiK
	xxMHU74VzfZIFSb2R+YN4QpgBnScBS8TygrkGrCqLc0mH8syLcwxqvvoJBW/BY85kIaJ
	yv6w==
Received: by 10.182.131.2 with SMTP id oi2mr3960412obb.43.1339111675615; Thu,
	07 Jun 2012 16:27:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.204.99 with HTTP; Thu, 7 Jun 2012 16:27:34 -0700 (PDT)
X-Originating-IP: [83.117.16.239]
In-Reply-To: 
References: 
From: Rolu 
Date: Fri, 8 Jun 2012 01:27:34 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-Gm-Message-State: ALoCoQlp+9TgmwPZiXHIbvAM1PmXvwOq8JwFy46n/grdbbr0Vv8NI2nXMyl3fnJ5ACgvxUM13zxm
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
> I've compiled Xen unstable from source and tried using it. When
> booting I do see Xen starting, but at the point where I normally start
> getting the dom0 kernel messages I just get a black screen for a few
> seconds, and then the machine reboots. It leaves no messages or log
> files, of course.
>
> revision I compiled: 25459
> OS: ubuntu 12.04
> dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
> kernel works with Xen 4.1 from the repositories.
>
> I had to apply the patch from
> http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
> get it to compile. Could this have broken something?
>
> Is there a way to have it display some log messages instead of rebooting?
>
> Any idea how to get it to work?
>
> If anyone else here is successfully using a recent revision, can you
> tell me which one, so I can try it too?
>

I've tried revision 25364 and 25099 (both picked because I found
someone reporting they worked for them). I got both to compile with
one or two patches, but with the same result.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 08 00:15:45 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 00:15: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 1ScmqH-0006PN-Kq; Fri, 08 Jun 2012 00:14:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScmqG-0006PI-8M
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 00:14:16 +0000
Received: from [85.158.143.99:26608] by server-3.bemta-4.messagelabs.com id
	35/8D-29237-7D341DF4; Fri, 08 Jun 2012 00:14:15 +0000
X-Env-Sender: cplusplus328@gmail.com
X-Msg-Ref: server-11.tower-216.messagelabs.com!1339114454!24293544!1
X-Originating-IP: [209.85.217.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11719 invoked from network); 8 Jun 2012 00:14:14 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 00:14:14 -0000
Received: by lbok6 with SMTP id k6so1202821lbo.32
	for ; Thu, 07 Jun 2012 17:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=iqrKsXJYlqXF8FXK2rdDbrv3Mxy7T7nfpLSnlpwz/jY=;
	b=QcxtpV7sZ+N20L+5CCL6k9ox6e3doG7vVW5kBI12i1YTvXiLjNUCXIMzcbnWvTldPX
	0qnA8Sx8lq3blIMd4nCXvjzhqJxShoUBO7xnU7SU/vJA/gBFIgwp9jy6RLiBkjzzl57g
	J/hUCgdGw39a04K3vCF6XFCf76Z0/nyQ1iBuv+7EbymiEd7cw+iz94PSNHCjnSPa74Xt
	CHuH2huHjPZOhFHL23N59xWC5/KF8MJCi89Uo1Xkd/0fZP925LVIH+QgwQVYEjxQt0YU
	2jT3TnrrAFbKOyzzioUBo50iLM+Fsw6T2A542F07kL+XKBno7aFWopeSAeoIDVh3RbpA
	hfyw==
Received: by 10.112.23.42 with SMTP id j10mr2376217lbf.20.1339114453745; Thu,
	07 Jun 2012 17:14:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.21.5 with HTTP; Thu, 7 Jun 2012 17:13:53 -0700 (PDT)
In-Reply-To: 
References: 
	
From: Aaron Lebahn 
Date: Thu, 7 Jun 2012 18:13:53 -0600
Message-ID: 
To: Rolu 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5227739877773766273=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5227739877773766273==
Content-Type: multipart/alternative; boundary=90e6ba3098265440d104c1eae152

--90e6ba3098265440d104c1eae152
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 7, 2012 at 5:27 PM, Rolu  wrote:

> On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
> > I've compiled Xen unstable from source and tried using it. When
> > booting I do see Xen starting, but at the point where I normally start
> > getting the dom0 kernel messages I just get a black screen for a few
> > seconds, and then the machine reboots. It leaves no messages or log
> > files, of course.
> >
> > revision I compiled: 25459
> > OS: ubuntu 12.04
> > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
> > kernel works with Xen 4.1 from the repositories.
> >
> > I had to apply the patch from
> > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
> > get it to compile. Could this have broken something?
> >
> > Is there a way to have it display some log messages instead of rebooting?
> >
> > Any idea how to get it to work?
> >
> > If anyone else here is successfully using a recent revision, can you
> > tell me which one, so I can try it too?
> >
>
> I've tried revision 25364 and 25099 (both picked because I found
> someone reporting they worked for them). I got both to compile with
> one or two patches, but with the same result.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

I have the same issue running xen 4.2 unstable on ubuntu 12.04. My screen
turns black after starting the hypervisor, the computer reboots, and leaves
no logs. The patch you mentioned shouldn't change any functionality, so
that is probably not the cause. All the messages from the hypervisor seem
typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic
Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com

--90e6ba3098265440d104c1eae152
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@=
roce.org> wrote:



On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org> wrote:

> I've compiled Xen unstable from source and tried using it. When
> booting I do see Xen starting, but at the point where I normally start=


> getting the dom0 kernel messages I just get a black screen for a few
> seconds, and then the machine reboots. It leaves no messages or log
> files, of course.

>

> revision I compiled: 25459

> OS: ubuntu 12.04

> dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This

> kernel works with Xen 4.1 from the repositories.

>

> I had to apply the patch from

> http://lists.gnu.org/archive/html/qemu-devel/201=
2-02/msg03460.html to

> get it to compile. Could this have broken something?

>

> Is there a way to have it display some log messages instead of rebooti=
ng?

>

> Any idea how to get it to work?

>

> If anyone else here is successfully using a recent revision, can you
> tell me which one, so I can try it too?

>




I've tried revision 25364 and 25099 (both picked because I found<=
br>
someone reporting they worked for them). I got both to compile with

one or two patches, but with the same result.




_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users



I have the same issue running xen 4.2 un=
stable on ubuntu 12.04. My=20
screen turns black after starting the hypervisor, the computer reboots,=20
and leaves no logs. The patch you mentioned shouldn't change any functi=
onality, so that is probably not the cause. All the messages from the hyper=
visor seem typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic

Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com=



--90e6ba3098265440d104c1eae152--


--===============5227739877773766273==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5227739877773766273==--


From xen-users-bounces@lists.xen.org Fri Jun 08 00:15:45 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 00:15: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 1ScmqH-0006PN-Kq; Fri, 08 Jun 2012 00:14:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScmqG-0006PI-8M
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 00:14:16 +0000
Received: from [85.158.143.99:26608] by server-3.bemta-4.messagelabs.com id
	35/8D-29237-7D341DF4; Fri, 08 Jun 2012 00:14:15 +0000
X-Env-Sender: cplusplus328@gmail.com
X-Msg-Ref: server-11.tower-216.messagelabs.com!1339114454!24293544!1
X-Originating-IP: [209.85.217.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11719 invoked from network); 8 Jun 2012 00:14:14 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 00:14:14 -0000
Received: by lbok6 with SMTP id k6so1202821lbo.32
	for ; Thu, 07 Jun 2012 17:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=iqrKsXJYlqXF8FXK2rdDbrv3Mxy7T7nfpLSnlpwz/jY=;
	b=QcxtpV7sZ+N20L+5CCL6k9ox6e3doG7vVW5kBI12i1YTvXiLjNUCXIMzcbnWvTldPX
	0qnA8Sx8lq3blIMd4nCXvjzhqJxShoUBO7xnU7SU/vJA/gBFIgwp9jy6RLiBkjzzl57g
	J/hUCgdGw39a04K3vCF6XFCf76Z0/nyQ1iBuv+7EbymiEd7cw+iz94PSNHCjnSPa74Xt
	CHuH2huHjPZOhFHL23N59xWC5/KF8MJCi89Uo1Xkd/0fZP925LVIH+QgwQVYEjxQt0YU
	2jT3TnrrAFbKOyzzioUBo50iLM+Fsw6T2A542F07kL+XKBno7aFWopeSAeoIDVh3RbpA
	hfyw==
Received: by 10.112.23.42 with SMTP id j10mr2376217lbf.20.1339114453745; Thu,
	07 Jun 2012 17:14:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.21.5 with HTTP; Thu, 7 Jun 2012 17:13:53 -0700 (PDT)
In-Reply-To: 
References: 
	
From: Aaron Lebahn 
Date: Thu, 7 Jun 2012 18:13:53 -0600
Message-ID: 
To: Rolu 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5227739877773766273=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5227739877773766273==
Content-Type: multipart/alternative; boundary=90e6ba3098265440d104c1eae152

--90e6ba3098265440d104c1eae152
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 7, 2012 at 5:27 PM, Rolu  wrote:

> On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
> > I've compiled Xen unstable from source and tried using it. When
> > booting I do see Xen starting, but at the point where I normally start
> > getting the dom0 kernel messages I just get a black screen for a few
> > seconds, and then the machine reboots. It leaves no messages or log
> > files, of course.
> >
> > revision I compiled: 25459
> > OS: ubuntu 12.04
> > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
> > kernel works with Xen 4.1 from the repositories.
> >
> > I had to apply the patch from
> > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
> > get it to compile. Could this have broken something?
> >
> > Is there a way to have it display some log messages instead of rebooting?
> >
> > Any idea how to get it to work?
> >
> > If anyone else here is successfully using a recent revision, can you
> > tell me which one, so I can try it too?
> >
>
> I've tried revision 25364 and 25099 (both picked because I found
> someone reporting they worked for them). I got both to compile with
> one or two patches, but with the same result.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

I have the same issue running xen 4.2 unstable on ubuntu 12.04. My screen
turns black after starting the hypervisor, the computer reboots, and leaves
no logs. The patch you mentioned shouldn't change any functionality, so
that is probably not the cause. All the messages from the hypervisor seem
typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic
Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com

--90e6ba3098265440d104c1eae152
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@=
roce.org> wrote:



On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org> wrote:

> I've compiled Xen unstable from source and tried using it. When
> booting I do see Xen starting, but at the point where I normally start=


> getting the dom0 kernel messages I just get a black screen for a few
> seconds, and then the machine reboots. It leaves no messages or log
> files, of course.

>

> revision I compiled: 25459

> OS: ubuntu 12.04

> dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This

> kernel works with Xen 4.1 from the repositories.

>

> I had to apply the patch from

> http://lists.gnu.org/archive/html/qemu-devel/201=
2-02/msg03460.html to

> get it to compile. Could this have broken something?

>

> Is there a way to have it display some log messages instead of rebooti=
ng?

>

> Any idea how to get it to work?

>

> If anyone else here is successfully using a recent revision, can you
> tell me which one, so I can try it too?

>




I've tried revision 25364 and 25099 (both picked because I found<=
br>
someone reporting they worked for them). I got both to compile with

one or two patches, but with the same result.




_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users



I have the same issue running xen 4.2 un=
stable on ubuntu 12.04. My=20
screen turns black after starting the hypervisor, the computer reboots,=20
and leaves no logs. The patch you mentioned shouldn't change any functi=
onality, so that is probably not the cause. All the messages from the hyper=
visor seem typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic

Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com=



--90e6ba3098265440d104c1eae152--


--===============5227739877773766273==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5227739877773766273==--


From xen-users-bounces@lists.xen.org Fri Jun 08 01:34:48 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 01:34:48 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sco4q-0002y7-4y; Fri, 08 Jun 2012 01:33:24 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sco4o-0002y2-HK
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 01:33:22 +0000
Received: from [85.158.139.83:46563] by server-6.bemta-5.messagelabs.com id
	B7/08-18700-06651DF4; Fri, 08 Jun 2012 01:33:20 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-4.tower-182.messagelabs.com!1339119197!29826862!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29223 invoked from network); 8 Jun 2012 01:33:18 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 01:33:18 -0000
Received: by ggnp1 with SMTP id p1so1061199ggn.32
	for ; Thu, 07 Jun 2012 18:33:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=apJoXLWB7qdHswIaonLk4bdJLAXtcSX6jkJRuseV3sw=;
	b=mxiIRnVGpaB0WTywkCP1rBtO5XfNrYALkGgdxrEeQNcB+X3oalQkFp0nGMRZwBR/x7
	Aqm5wcGKpzG/8RgoC1yXPxdFq1VD3S4QQuJtzReSbjaw4lTzn5F+PRRNt6aij+T72rPe
	tvdgM9JYvryYqpOtjEDi1EGXyAHauP4vERlhEgOZnQqqFjfdHWBi8NIAd0ZuGT/s+4Qt
	QGOMcjXn9s3+iWTfgTm+3/5UsYNVlpQS1YOec1P6Ib8/qrybNuD0YcHeNZr83Y1G6Uhz
	DYM277CiGwEsXz30HtoavxSibaUMD6sV3x/rVtkXiijBE9C0U2z6werNK/TiifJ/bQjH
	p/cQ==
Received: by 10.236.173.232 with SMTP id v68mr4121397yhl.97.1339119197253;
	Thu, 07 Jun 2012 18:33:17 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id z9sm15772355yhl.6.2012.06.07.18.33.16
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 07 Jun 2012 18:33:16 -0700 (PDT)
Message-ID: <4FD1565B.1030201@gmail.com>
Date: Thu, 07 Jun 2012 21:33:15 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org >> \"xen-users@lists.xen.org\""
	
References: 
	
	
In-Reply-To: 
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8634286511900730690=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8634286511900730690==
Content-Type: multipart/alternative;
 boundary="------------080707030204070802010201"

This is a multi-part message in MIME format.
--------------080707030204070802010201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
>
>
> On Thu, Jun 7, 2012 at 5:27 PM, Rolu  > wrote:
>
>     On Thu, Jun 7, 2012 at 3:15 PM, Rolu      > wrote:
>     > I've compiled Xen unstable from source and tried using it. When
>     > booting I do see Xen starting, but at the point where I normally
>     start
>     > getting the dom0 kernel messages I just get a black screen for a few
>     > seconds, and then the machine reboots. It leaves no messages or log
>     > files, of course.
>     >
>     > revision I compiled: 25459
>     > OS: ubuntu 12.04
>     > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
>     > kernel works with Xen 4.1 from the repositories.
>     >
>     > I had to apply the patch from
>     >
>     http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
>     > get it to compile. Could this have broken something?
>     >
>     > Is there a way to have it display some log messages instead of
>     rebooting?
>


Well possibly, yes. I had a similar issue before and when i compiled and 
installed xen. But once i tried booting into Xen, it would just hang at 
a black screen, nothing on it. Sometimes it would show a rapidly 
flickering cursor, but that's it.

SO, what i had to try was to enable the Xen serial console. What this 
entails is using a NULL MODEM cable and plugging this into the COM port 
on your XEN computer and connecting the other end to a second computers 
COM port. Than you have to use a Terminal program, just as PuTTY or 
similar (based on your OS on second computer) and this way you can watch 
the Xen boot messages as they happen and could possibly troubleshoot.

To enable the Serial Console, just have to add "loglvl=all 
guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the 
"multiboot  /boot/xen-4.2-unstable.gz placeholder ... "

You can read all about it here 
http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which will 
explain it a lot better anyways.



>     >
>     > Any idea how to get it to work?
>     >
>     > If anyone else here is successfully using a recent revision, can you
>     > tell me which one, so I can try it too?
>     >
>
>     I've tried revision 25364 and 25099 (both picked because I found
>     someone reporting they worked for them). I got both to compile with
>     one or two patches, but with the same result.
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xen.org 
>     http://lists.xen.org/xen-users
>
>
> I have the same issue running xen 4.2 unstable on ubuntu 12.04. My 
> screen turns black after starting the hypervisor, the computer 
> reboots, and leaves no logs. The patch you mentioned shouldn't change 
> any functionality, so that is probably not the cause. All the messages 
> from the hypervisor seem typical.
> Specs:
> Ubuntu 12.04
> Kernel: 3.2.0-24-generic
> Processor: AMD FX-8150
>
> -- 
> Aaron Lebahn
> cplusplus328@gmail.com 
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users



--------------080707030204070802010201
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
    


      

      
On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@roce.org>
        wrote:

        

          
On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org>

            wrote:

            > I've compiled Xen unstable from source and tried using
            it. When

            > booting I do see Xen starting, but at the point where I
            normally start

            > getting the dom0 kernel messages I just get a black
            screen for a few

            > seconds, and then the machine reboots. It leaves no
            messages or log

            > files, of course.

            >

            > revision I compiled: 25459

            > OS: ubuntu 12.04

            > dom0 kernel 3.2.0-24 (also tried -23), from the
            repositories. This

            > kernel works with Xen 4.1 from the repositories.

            >

            > I had to apply the patch from

            > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html
            to

            > get it to compile. Could this have broken something?

            >

            > Is there a way to have it display some log messages
            instead of rebooting?

          

        

      

    

    

    

    Well possibly, yes. I had a similar issue before and when i compiled
    and installed xen. But once i tried booting into Xen, it would just
    hang at a black screen, nothing on it. Sometimes it would show a
    rapidly flickering cursor, but that's it.

    

    SO, what i had to try was to enable the Xen serial console. What
    this entails is using a NULL MODEM cable and plugging this into the
    COM port on your XEN computer and connecting the other end to a
    second computers COM port. Than you have to use a Terminal program,
    just as PuTTY or similar (based on your OS on second computer) and
    this way you can watch the Xen boot messages as they happen and
    could possibly troubleshoot.

    

    To enable the Serial Console, just have to add "loglvl=all
    guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the
    "multiboot  /boot/xen-4.2-unstable.gz placeholder ... " 

    

    You can read all about it here
    http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which
    will explain it a lot better anyways.

    

    

    

    

      

        

          
 >

            > Any idea how to get it to work?

            >

            > If anyone else here is successfully using a recent
            revision, can you

            > tell me which one, so I can try it too?

            >

            

          

          I've tried revision 25364 and 25099 (both picked because I
          found

          someone reporting they worked for them). I got both to compile
          with

          one or two patches, but with the same result.

          

            


              _______________________________________________

              Xen-users mailing list

              Xen-users@lists.xen.org

              http://lists.xen.org/xen-users

            

          

        

      

      

      I have the same issue running xen 4.2 unstable on ubuntu 12.04. My
      screen turns black after starting the hypervisor, the computer
      reboots, and leaves no logs. The patch you mentioned shouldn't
      change any functionality, so that is probably not the cause. All
      the messages from the hypervisor seem typical.

      Specs:

      Ubuntu 12.04

      Kernel: 3.2.0-24-generic

      Processor: AMD FX-8150

      

      -- 

      Aaron Lebahn

      cplusplus328@gmail.com

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

    

  


--------------080707030204070802010201--


--===============8634286511900730690==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8634286511900730690==--


From xen-users-bounces@lists.xen.org Fri Jun 08 01:34:48 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 01:34:48 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1Sco4q-0002y7-4y; Fri, 08 Jun 2012 01:33:24 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1Sco4o-0002y2-HK
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 01:33:22 +0000
Received: from [85.158.139.83:46563] by server-6.bemta-5.messagelabs.com id
	B7/08-18700-06651DF4; Fri, 08 Jun 2012 01:33:20 +0000
X-Env-Sender: cyberhawk001@gmail.com
X-Msg-Ref: server-4.tower-182.messagelabs.com!1339119197!29826862!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29223 invoked from network); 8 Jun 2012 01:33:18 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 01:33:18 -0000
Received: by ggnp1 with SMTP id p1so1061199ggn.32
	for ; Thu, 07 Jun 2012 18:33:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type;
	bh=apJoXLWB7qdHswIaonLk4bdJLAXtcSX6jkJRuseV3sw=;
	b=mxiIRnVGpaB0WTywkCP1rBtO5XfNrYALkGgdxrEeQNcB+X3oalQkFp0nGMRZwBR/x7
	Aqm5wcGKpzG/8RgoC1yXPxdFq1VD3S4QQuJtzReSbjaw4lTzn5F+PRRNt6aij+T72rPe
	tvdgM9JYvryYqpOtjEDi1EGXyAHauP4vERlhEgOZnQqqFjfdHWBi8NIAd0ZuGT/s+4Qt
	QGOMcjXn9s3+iWTfgTm+3/5UsYNVlpQS1YOec1P6Ib8/qrybNuD0YcHeNZr83Y1G6Uhz
	DYM277CiGwEsXz30HtoavxSibaUMD6sV3x/rVtkXiijBE9C0U2z6werNK/TiifJ/bQjH
	p/cQ==
Received: by 10.236.173.232 with SMTP id v68mr4121397yhl.97.1339119197253;
	Thu, 07 Jun 2012 18:33:17 -0700 (PDT)
Received: from [192.168.1.2] (c-66-177-73-176.hsd1.fl.comcast.net.
	[66.177.73.176])
	by mx.google.com with ESMTPS id z9sm15772355yhl.6.2012.06.07.18.33.16
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 07 Jun 2012 18:33:16 -0700 (PDT)
Message-ID: <4FD1565B.1030201@gmail.com>
Date: Thu, 07 Jun 2012 21:33:15 -0400
From: cyberhawk001@gmail.com
User-Agent: Mozilla/5.0 (Windows NT 5.1;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "xen-users@lists.xen.org >> \"xen-users@lists.xen.org\""
	
References: 
	
	
In-Reply-To: 
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8634286511900730690=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8634286511900730690==
Content-Type: multipart/alternative;
 boundary="------------080707030204070802010201"

This is a multi-part message in MIME format.
--------------080707030204070802010201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
>
>
> On Thu, Jun 7, 2012 at 5:27 PM, Rolu  > wrote:
>
>     On Thu, Jun 7, 2012 at 3:15 PM, Rolu      > wrote:
>     > I've compiled Xen unstable from source and tried using it. When
>     > booting I do see Xen starting, but at the point where I normally
>     start
>     > getting the dom0 kernel messages I just get a black screen for a few
>     > seconds, and then the machine reboots. It leaves no messages or log
>     > files, of course.
>     >
>     > revision I compiled: 25459
>     > OS: ubuntu 12.04
>     > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
>     > kernel works with Xen 4.1 from the repositories.
>     >
>     > I had to apply the patch from
>     >
>     http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
>     > get it to compile. Could this have broken something?
>     >
>     > Is there a way to have it display some log messages instead of
>     rebooting?
>


Well possibly, yes. I had a similar issue before and when i compiled and 
installed xen. But once i tried booting into Xen, it would just hang at 
a black screen, nothing on it. Sometimes it would show a rapidly 
flickering cursor, but that's it.

SO, what i had to try was to enable the Xen serial console. What this 
entails is using a NULL MODEM cable and plugging this into the COM port 
on your XEN computer and connecting the other end to a second computers 
COM port. Than you have to use a Terminal program, just as PuTTY or 
similar (based on your OS on second computer) and this way you can watch 
the Xen boot messages as they happen and could possibly troubleshoot.

To enable the Serial Console, just have to add "loglvl=all 
guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the 
"multiboot  /boot/xen-4.2-unstable.gz placeholder ... "

You can read all about it here 
http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which will 
explain it a lot better anyways.



>     >
>     > Any idea how to get it to work?
>     >
>     > If anyone else here is successfully using a recent revision, can you
>     > tell me which one, so I can try it too?
>     >
>
>     I've tried revision 25364 and 25099 (both picked because I found
>     someone reporting they worked for them). I got both to compile with
>     one or two patches, but with the same result.
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xen.org 
>     http://lists.xen.org/xen-users
>
>
> I have the same issue running xen 4.2 unstable on ubuntu 12.04. My 
> screen turns black after starting the hypervisor, the computer 
> reboots, and leaves no logs. The patch you mentioned shouldn't change 
> any functionality, so that is probably not the cause. All the messages 
> from the hypervisor seem typical.
> Specs:
> Ubuntu 12.04
> Kernel: 3.2.0-24-generic
> Processor: AMD FX-8150
>
> -- 
> Aaron Lebahn
> cplusplus328@gmail.com 
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users



--------------080707030204070802010201
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
    


      

      
On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@roce.org>
        wrote:

        

          
On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org>

            wrote:

            > I've compiled Xen unstable from source and tried using
            it. When

            > booting I do see Xen starting, but at the point where I
            normally start

            > getting the dom0 kernel messages I just get a black
            screen for a few

            > seconds, and then the machine reboots. It leaves no
            messages or log

            > files, of course.

            >

            > revision I compiled: 25459

            > OS: ubuntu 12.04

            > dom0 kernel 3.2.0-24 (also tried -23), from the
            repositories. This

            > kernel works with Xen 4.1 from the repositories.

            >

            > I had to apply the patch from

            > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html
            to

            > get it to compile. Could this have broken something?

            >

            > Is there a way to have it display some log messages
            instead of rebooting?

          

        

      

    

    

    

    Well possibly, yes. I had a similar issue before and when i compiled
    and installed xen. But once i tried booting into Xen, it would just
    hang at a black screen, nothing on it. Sometimes it would show a
    rapidly flickering cursor, but that's it.

    

    SO, what i had to try was to enable the Xen serial console. What
    this entails is using a NULL MODEM cable and plugging this into the
    COM port on your XEN computer and connecting the other end to a
    second computers COM port. Than you have to use a Terminal program,
    just as PuTTY or similar (based on your OS on second computer) and
    this way you can watch the Xen boot messages as they happen and
    could possibly troubleshoot.

    

    To enable the Serial Console, just have to add "loglvl=all
    guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the
    "multiboot  /boot/xen-4.2-unstable.gz placeholder ... " 

    

    You can read all about it here
    http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which
    will explain it a lot better anyways.

    

    

    

    

      

        

          
 >

            > Any idea how to get it to work?

            >

            > If anyone else here is successfully using a recent
            revision, can you

            > tell me which one, so I can try it too?

            >

            

          

          I've tried revision 25364 and 25099 (both picked because I
          found

          someone reporting they worked for them). I got both to compile
          with

          one or two patches, but with the same result.

          

            


              _______________________________________________

              Xen-users mailing list

              Xen-users@lists.xen.org

              http://lists.xen.org/xen-users

            

          

        

      

      

      I have the same issue running xen 4.2 unstable on ubuntu 12.04. My
      screen turns black after starting the hypervisor, the computer
      reboots, and leaves no logs. The patch you mentioned shouldn't
      change any functionality, so that is probably not the cause. All
      the messages from the hypervisor seem typical.

      Specs:

      Ubuntu 12.04

      Kernel: 3.2.0-24-generic

      Processor: AMD FX-8150

      

      -- 

      Aaron Lebahn

      cplusplus328@gmail.com

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

    

  


--------------080707030204070802010201--


--===============8634286511900730690==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8634286511900730690==--


From xen-users-bounces@lists.xen.org Fri Jun 08 03:09:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 03:09: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 1ScpYt-0004Iw-4v; Fri, 08 Jun 2012 03:08:31 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScpYr-0004Ir-Cr
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:08:29 +0000
Received: from [85.158.138.51:59744] by server-10.bemta-3.messagelabs.com id
	00/27-06494-CAC61DF4; Fri, 08 Jun 2012 03:08:28 +0000
X-Env-Sender: cplusplus328@gmail.com
X-Msg-Ref: server-16.tower-174.messagelabs.com!1339124906!28502204!1
X-Originating-IP: [209.85.215.45]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6551 invoked from network); 8 Jun 2012 03:08:27 -0000
Received: from mail-lpp01m010-f45.google.com (HELO
	mail-lpp01m010-f45.google.com) (209.85.215.45)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:08:27 -0000
Received: by lahc1 with SMTP id c1so1147488lah.32
	for ; Thu, 07 Jun 2012 20:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=TI5e/ulmNhKkKoQmEvGN9pAlOCfOJnzuVc3DbEgGV+g=;
	b=KIln/Wz9gx1qJ23Mlad+RolUdohS5yzT/Ai3BLfZBr+QzBL4dRUjsakkhHFYYXlsV4
	bMG0Ykn2wRQTTkKwwJFDPIuO0uZwKGs7z/DDD79t5lAGa83Dd3XCCGPd7TESkNIyGEyB
	lJl6o9Vccf2UG6Tf+Y37TRFRy7WmhKfaroruOOsOmsOmVo+K4K2OTCUz3lLBemyAvnHF
	oHEn/UmPGJkxjEwe1By8E1ZbbBBffjhN8nuOLzli+P3KKYyxfGRoDWmBvTyZ/RpqbwrV
	w/q8s0ytb/HgBntrvGerlxrflpNz2/hgzjsDYwLZWv1f5m1c8MpvGUWZJd2tYCsWKM/J
	RR1w==
Received: by 10.112.104.3 with SMTP id ga3mr2489739lbb.77.1339124906272; Thu,
	07 Jun 2012 20:08:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.21.5 with HTTP; Thu, 7 Jun 2012 20:08:06 -0700 (PDT)
In-Reply-To: <4FD1565B.1030201@gmail.com>
References: 
	
	
	<4FD1565B.1030201@gmail.com>
From: Aaron Lebahn 
Date: Thu, 7 Jun 2012 21:08:06 -0600
Message-ID: 
To: cyberhawk001@gmail.com
Cc: "xen-users@lists.xen.org >> \"xen-users@lists.xen.org\""
	
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2408062280358933384=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2408062280358933384==
Content-Type: multipart/alternative; boundary=14dae9d7197659289d04c1ed509d

--14dae9d7197659289d04c1ed509d
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 7, 2012 at 7:33 PM,  wrote:

>  On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
>
>
>
> On Thu, Jun 7, 2012 at 5:27 PM, Rolu  wrote:
>
>> On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
>> > I've compiled Xen unstable from source and tried using it. When
>> > booting I do see Xen starting, but at the point where I normally start
>> > getting the dom0 kernel messages I just get a black screen for a few
>> > seconds, and then the machine reboots. It leaves no messages or log
>> > files, of course.
>> >
>> > revision I compiled: 25459
>> > OS: ubuntu 12.04
>> > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
>> > kernel works with Xen 4.1 from the repositories.
>> >
>> > I had to apply the patch from
>> > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
>> > get it to compile. Could this have broken something?
>> >
>> > Is there a way to have it display some log messages instead of
>> rebooting?
>>
>
>
> Well possibly, yes. I had a similar issue before and when i compiled and
> installed xen. But once i tried booting into Xen, it would just hang at a
> black screen, nothing on it. Sometimes it would show a rapidly flickering
> cursor, but that's it.
>
> SO, what i had to try was to enable the Xen serial console. What this
> entails is using a NULL MODEM cable and plugging this into the COM port on
> your XEN computer and connecting the other end to a second computers COM
> port. Than you have to use a Terminal program, just as PuTTY or similar
> (based on your OS on second computer) and this way you can watch the Xen
> boot messages as they happen and could possibly troubleshoot.
>
> To enable the Serial Console, just have to add "loglvl=all
> guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the
> "multiboot  /boot/xen-4.2-unstable.gz placeholder ... "
>
> You can read all about it here http://wiki.xen.org/wiki/Xen_Serial_Consoleon the Wiki page, which will explain it a lot better anyways.
>
>
>
Personally, I tried this. I bought a pci serial card and a null modem
cable. I attached the cable between my card and the usb-pci adapter
connected to my laptop. I set the grub to:
multiboot       /boot/xen-4.2.gz placeholder  loglvl=all guest_loglvl=all
com5=38400,8n1,0xa030,20 console=com5
and started minicom on the labtop. Noting came up on minicom, and nothing
came up on the desktop's screen (As should be expected).
I tested the connection by running minicom on the desktop as well. That
works fine. My output to dmesg | grep ttyS is:
[    2.393378] 0000:08:05.0: ttyS4 at I/O 0xa030 (irq = 20) is a ST16650V2
[    2.449062] 0000:08:05.1: ttyS5 at I/O 0xa020 (irq = 21) is a ST16650V2
If anyone knows why my serial console isn't working, maybe I can fix it and
get some useful information to debug this problem.

  >
> > Any idea how to get it to work?
> >
> > If anyone else here is successfully using a recent revision, can you
> > tell me which one, so I can try it too?
> >
>
>  I've tried revision 25364 and 25099 (both picked because I found
> someone reporting they worked for them). I got both to compile with
> one or two patches, but with the same result.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

I have the same issue running xen 4.2 unstable on ubuntu 12.04. My screen
turns black after starting the hypervisor, the computer reboots, and leaves
no logs. The patch you mentioned shouldn't change any functionality, so
that is probably not the cause. All the messages from the hypervisor seem
typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic
Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com


_______________________________________________
Xen-users mailing listXen-users@lists.xen.orghttp://lists.xen.org/xen-users




> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>



-- 
Aaron Lebahn
cplusplus328@gmail.com

--14dae9d7197659289d04c1ed509d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On Thu, Jun 7, 2012 at 7:33 PM,  <=
cyberhawk001@gmail.com> wrote:



 =20
   =20
 =20
  

    On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
    


      

      
On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@ro=
ce.org>
        wrote:

        

          
On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org>

            wrote:

            > I've compiled Xen unstable from source and tried using
            it. When

            > booting I do see Xen starting, but at the point where I
            normally start

            > getting the dom0 kernel messages I just get a black
            screen for a few

            > seconds, and then the machine reboots. It leaves no
            messages or log

            > files, of course.

            >

            > revision I compiled: 25459

            > OS: ubuntu 12.04

            > dom0 kernel 3.2.0-24 (also tried -23), from the
            repositories. This

            > kernel works with Xen 4.1 from the repositories.

            >

            > I had to apply the patch from

            > http://lists.gnu.org/archive/html/qe=
mu-devel/2012-02/msg03460.html
            to

            > get it to compile. Could this have broken something?

            >

            > Is there a way to have it display some log messages
            instead of rebooting?

          

        

      

    

    

    

    Well possibly, yes. I had a similar issue before and when i compiled
    and installed xen. But once i tried booting into Xen, it would just
    hang at a black screen, nothing on it. Sometimes it would show a
    rapidly flickering cursor, but that's it.

    

    SO, what i had to try was to enable the Xen serial console. What
    this entails is using a NULL MODEM cable and plugging this into the
    COM port on your XEN computer and connecting the other end to a
    second computers COM port. Than you have to use a Terminal program,
    just as PuTTY or similar (based on your OS on second computer) and
    this way you can watch the Xen boot messages as they happen and
    could possibly troubleshoot.

    

    To enable the Serial Console, just have to add "loglvl=3Dall
    guest_loglvl=3Dall com1=3D115200,8n1,0x3f8,4 console=3Dcom1,vga" a=
fter the
    "multiboot=A0 /boot/xen-4.2-unstable.gz placeholder ... " 
    

    You can read all about it here
    http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which
    will explain it a lot better anyways.


    

Personally, I tried =
this. I bought a pci serial card and a null modem=20
cable. I attached the cable between my card and the usb-pci adapter=20
connected to my laptop. I set the grub to:
multiboot=A0=A0=A0=A0=A0=A0 /=
boot/xen-4.2.gz placeholder=A0 loglvl=3Dall guest_loglvl=3Dall com5=3D38400=
,8n1,0xa030,20 console=3Dcom5

and started minicom on the labtop. Noting came up on minicom, and=20
nothing came up on the desktop's screen (As should be expected).

I tested the connection by running minicom on the desktop as well. That wor=
ks fine. My output to dmesg | grep ttyS is:

[=A0=A0=A0 2.393378] 0000:08:05.0: ttyS4 at I/O 0xa030 (irq =3D 20) is a ST=
16650V2

[=A0=A0=A0 2.449062] 0000:08:05.1: ttyS5 at I/O 0xa020 (irq =3D 21) is a ST=
16650V2
If anyone knows why my serial console isn't working, maybe I=
 can fix it and get some useful information to debug this problem.

    

    

      

        

          
 >

            > Any idea how to get it to work?

            >

            > If anyone else here is successfully using a recent
            revision, can you

            > tell me which one, so I can try it too?

            >

            

          

          I've tried revision 25364 and 25099 (both picked because I
          found

          someone reporting they worked for them). I got both to compile
          with

          one or two patches, but with the same result.

          

            


              _______________________________________________

              Xen-users mailing list

              =
Xen-users@lists.xen.org

              =
http://lists.xen.org/xen-users

            

          

        

      

      

      I have the same issue running xen 4.2 unstable on ubuntu 12.04. My
      screen turns black after starting the hypervisor, the computer
      reboots, and leaves no logs. The patch you mentioned shouldn't
      change any functionality, so that is probably not the cause. All
      the messages from the hypervisor seem typical.

      Specs:

      Ubuntu 12.04

      Kernel: 3.2.0-24-generic

      Processor: AMD FX-8150

      

      -- 

      Aaron Lebahn

      cplusplus=
328@gmail.com

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@list=
s.xen.org
http://lists.x=
en.org/xen-users

    

    

    

  



_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users



-- Aaron Lebahn
cplusplus328@gmail.com




--14dae9d7197659289d04c1ed509d--


--===============2408062280358933384==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2408062280358933384==--


From xen-users-bounces@lists.xen.org Fri Jun 08 03:09:41 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 03:09: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 1ScpYt-0004Iw-4v; Fri, 08 Jun 2012 03:08:31 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScpYr-0004Ir-Cr
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:08:29 +0000
Received: from [85.158.138.51:59744] by server-10.bemta-3.messagelabs.com id
	00/27-06494-CAC61DF4; Fri, 08 Jun 2012 03:08:28 +0000
X-Env-Sender: cplusplus328@gmail.com
X-Msg-Ref: server-16.tower-174.messagelabs.com!1339124906!28502204!1
X-Originating-IP: [209.85.215.45]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6551 invoked from network); 8 Jun 2012 03:08:27 -0000
Received: from mail-lpp01m010-f45.google.com (HELO
	mail-lpp01m010-f45.google.com) (209.85.215.45)
	by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:08:27 -0000
Received: by lahc1 with SMTP id c1so1147488lah.32
	for ; Thu, 07 Jun 2012 20:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=TI5e/ulmNhKkKoQmEvGN9pAlOCfOJnzuVc3DbEgGV+g=;
	b=KIln/Wz9gx1qJ23Mlad+RolUdohS5yzT/Ai3BLfZBr+QzBL4dRUjsakkhHFYYXlsV4
	bMG0Ykn2wRQTTkKwwJFDPIuO0uZwKGs7z/DDD79t5lAGa83Dd3XCCGPd7TESkNIyGEyB
	lJl6o9Vccf2UG6Tf+Y37TRFRy7WmhKfaroruOOsOmsOmVo+K4K2OTCUz3lLBemyAvnHF
	oHEn/UmPGJkxjEwe1By8E1ZbbBBffjhN8nuOLzli+P3KKYyxfGRoDWmBvTyZ/RpqbwrV
	w/q8s0ytb/HgBntrvGerlxrflpNz2/hgzjsDYwLZWv1f5m1c8MpvGUWZJd2tYCsWKM/J
	RR1w==
Received: by 10.112.104.3 with SMTP id ga3mr2489739lbb.77.1339124906272; Thu,
	07 Jun 2012 20:08:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.21.5 with HTTP; Thu, 7 Jun 2012 20:08:06 -0700 (PDT)
In-Reply-To: <4FD1565B.1030201@gmail.com>
References: 
	
	
	<4FD1565B.1030201@gmail.com>
From: Aaron Lebahn 
Date: Thu, 7 Jun 2012 21:08:06 -0600
Message-ID: 
To: cyberhawk001@gmail.com
Cc: "xen-users@lists.xen.org >> \"xen-users@lists.xen.org\""
	
Subject: Re: [Xen-users] reboot on booting xen-unstable
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2408062280358933384=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2408062280358933384==
Content-Type: multipart/alternative; boundary=14dae9d7197659289d04c1ed509d

--14dae9d7197659289d04c1ed509d
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 7, 2012 at 7:33 PM,  wrote:

>  On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
>
>
>
> On Thu, Jun 7, 2012 at 5:27 PM, Rolu  wrote:
>
>> On Thu, Jun 7, 2012 at 3:15 PM, Rolu  wrote:
>> > I've compiled Xen unstable from source and tried using it. When
>> > booting I do see Xen starting, but at the point where I normally start
>> > getting the dom0 kernel messages I just get a black screen for a few
>> > seconds, and then the machine reboots. It leaves no messages or log
>> > files, of course.
>> >
>> > revision I compiled: 25459
>> > OS: ubuntu 12.04
>> > dom0 kernel 3.2.0-24 (also tried -23), from the repositories. This
>> > kernel works with Xen 4.1 from the repositories.
>> >
>> > I had to apply the patch from
>> > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
>> > get it to compile. Could this have broken something?
>> >
>> > Is there a way to have it display some log messages instead of
>> rebooting?
>>
>
>
> Well possibly, yes. I had a similar issue before and when i compiled and
> installed xen. But once i tried booting into Xen, it would just hang at a
> black screen, nothing on it. Sometimes it would show a rapidly flickering
> cursor, but that's it.
>
> SO, what i had to try was to enable the Xen serial console. What this
> entails is using a NULL MODEM cable and plugging this into the COM port on
> your XEN computer and connecting the other end to a second computers COM
> port. Than you have to use a Terminal program, just as PuTTY or similar
> (based on your OS on second computer) and this way you can watch the Xen
> boot messages as they happen and could possibly troubleshoot.
>
> To enable the Serial Console, just have to add "loglvl=all
> guest_loglvl=all com1=115200,8n1,0x3f8,4 console=com1,vga" after the
> "multiboot  /boot/xen-4.2-unstable.gz placeholder ... "
>
> You can read all about it here http://wiki.xen.org/wiki/Xen_Serial_Consoleon the Wiki page, which will explain it a lot better anyways.
>
>
>
Personally, I tried this. I bought a pci serial card and a null modem
cable. I attached the cable between my card and the usb-pci adapter
connected to my laptop. I set the grub to:
multiboot       /boot/xen-4.2.gz placeholder  loglvl=all guest_loglvl=all
com5=38400,8n1,0xa030,20 console=com5
and started minicom on the labtop. Noting came up on minicom, and nothing
came up on the desktop's screen (As should be expected).
I tested the connection by running minicom on the desktop as well. That
works fine. My output to dmesg | grep ttyS is:
[    2.393378] 0000:08:05.0: ttyS4 at I/O 0xa030 (irq = 20) is a ST16650V2
[    2.449062] 0000:08:05.1: ttyS5 at I/O 0xa020 (irq = 21) is a ST16650V2
If anyone knows why my serial console isn't working, maybe I can fix it and
get some useful information to debug this problem.

  >
> > Any idea how to get it to work?
> >
> > If anyone else here is successfully using a recent revision, can you
> > tell me which one, so I can try it too?
> >
>
>  I've tried revision 25364 and 25099 (both picked because I found
> someone reporting they worked for them). I got both to compile with
> one or two patches, but with the same result.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>

I have the same issue running xen 4.2 unstable on ubuntu 12.04. My screen
turns black after starting the hypervisor, the computer reboots, and leaves
no logs. The patch you mentioned shouldn't change any functionality, so
that is probably not the cause. All the messages from the hypervisor seem
typical.
Specs:
Ubuntu 12.04
Kernel: 3.2.0-24-generic
Processor: AMD FX-8150

-- 
Aaron Lebahn
cplusplus328@gmail.com


_______________________________________________
Xen-users mailing listXen-users@lists.xen.orghttp://lists.xen.org/xen-users




> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>



-- 
Aaron Lebahn
cplusplus328@gmail.com

--14dae9d7197659289d04c1ed509d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On Thu, Jun 7, 2012 at 7:33 PM,  <=
cyberhawk001@gmail.com> wrote:



 =20
   =20
 =20
  

    On 6/7/2012 8:13 PM, Aaron Lebahn wrote:
    


      

      
On Thu, Jun 7, 2012 at 5:27 PM, Rolu <rolu@ro=
ce.org>
        wrote:

        

          
On Thu, Jun 7, 2012 at 3:15 PM, Rolu <rolu@roce.org>

            wrote:

            > I've compiled Xen unstable from source and tried using
            it. When

            > booting I do see Xen starting, but at the point where I
            normally start

            > getting the dom0 kernel messages I just get a black
            screen for a few

            > seconds, and then the machine reboots. It leaves no
            messages or log

            > files, of course.

            >

            > revision I compiled: 25459

            > OS: ubuntu 12.04

            > dom0 kernel 3.2.0-24 (also tried -23), from the
            repositories. This

            > kernel works with Xen 4.1 from the repositories.

            >

            > I had to apply the patch from

            > http://lists.gnu.org/archive/html/qe=
mu-devel/2012-02/msg03460.html
            to

            > get it to compile. Could this have broken something?

            >

            > Is there a way to have it display some log messages
            instead of rebooting?

          

        

      

    

    

    

    Well possibly, yes. I had a similar issue before and when i compiled
    and installed xen. But once i tried booting into Xen, it would just
    hang at a black screen, nothing on it. Sometimes it would show a
    rapidly flickering cursor, but that's it.

    

    SO, what i had to try was to enable the Xen serial console. What
    this entails is using a NULL MODEM cable and plugging this into the
    COM port on your XEN computer and connecting the other end to a
    second computers COM port. Than you have to use a Terminal program,
    just as PuTTY or similar (based on your OS on second computer) and
    this way you can watch the Xen boot messages as they happen and
    could possibly troubleshoot.

    

    To enable the Serial Console, just have to add "loglvl=3Dall
    guest_loglvl=3Dall com1=3D115200,8n1,0x3f8,4 console=3Dcom1,vga" a=
fter the
    "multiboot=A0 /boot/xen-4.2-unstable.gz placeholder ... " 
    

    You can read all about it here
    http://wiki.xen.org/wiki/Xen_Serial_Console on the Wiki page, which
    will explain it a lot better anyways.


    

Personally, I tried =
this. I bought a pci serial card and a null modem=20
cable. I attached the cable between my card and the usb-pci adapter=20
connected to my laptop. I set the grub to:
multiboot=A0=A0=A0=A0=A0=A0 /=
boot/xen-4.2.gz placeholder=A0 loglvl=3Dall guest_loglvl=3Dall com5=3D38400=
,8n1,0xa030,20 console=3Dcom5

and started minicom on the labtop. Noting came up on minicom, and=20
nothing came up on the desktop's screen (As should be expected).

I tested the connection by running minicom on the desktop as well. That wor=
ks fine. My output to dmesg | grep ttyS is:

[=A0=A0=A0 2.393378] 0000:08:05.0: ttyS4 at I/O 0xa030 (irq =3D 20) is a ST=
16650V2

[=A0=A0=A0 2.449062] 0000:08:05.1: ttyS5 at I/O 0xa020 (irq =3D 21) is a ST=
16650V2
If anyone knows why my serial console isn't working, maybe I=
 can fix it and get some useful information to debug this problem.

    

    

      

        

          
 >

            > Any idea how to get it to work?

            >

            > If anyone else here is successfully using a recent
            revision, can you

            > tell me which one, so I can try it too?

            >

            

          

          I've tried revision 25364 and 25099 (both picked because I
          found

          someone reporting they worked for them). I got both to compile
          with

          one or two patches, but with the same result.

          

            


              _______________________________________________

              Xen-users mailing list

              =
Xen-users@lists.xen.org

              =
http://lists.xen.org/xen-users

            

          

        

      

      

      I have the same issue running xen 4.2 unstable on ubuntu 12.04. My
      screen turns black after starting the hypervisor, the computer
      reboots, and leaves no logs. The patch you mentioned shouldn't
      change any functionality, so that is probably not the cause. All
      the messages from the hypervisor seem typical.

      Specs:

      Ubuntu 12.04

      Kernel: 3.2.0-24-generic

      Processor: AMD FX-8150

      

      -- 

      Aaron Lebahn

      cplusplus=
328@gmail.com

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@list=
s.xen.org
http://lists.x=
en.org/xen-users

    

    

    

  



_______________________________________________

Xen-users mailing list

Xen-users@lists.xen.org

http://lists.x=
en.org/xen-users



-- Aaron Lebahn
cplusplus328@gmail.com




--14dae9d7197659289d04c1ed509d--


--===============2408062280358933384==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2408062280358933384==--


From xen-users-bounces@lists.xen.org Fri Jun 08 03:53:02 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 03:53: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 1ScqEl-0004v8-BF; Fri, 08 Jun 2012 03:51:47 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScqEj-0004v3-Tw
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:51:46 +0000
Received: from [85.158.138.51:58129] by server-8.bemta-3.messagelabs.com id
	15/A6-22118-1D671DF4; Fri, 08 Jun 2012 03:51:45 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-7.tower-174.messagelabs.com!1339127502!22476227!1
X-Originating-IP: [209.85.160.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20152 invoked from network); 8 Jun 2012 03:51:44 -0000
Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com)
	(209.85.160.45)
	by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:51:44 -0000
Received: by pbbro12 with SMTP id ro12so2117608pbb.32
	for ; Thu, 07 Jun 2012 20:51:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=6kelro2+UcfffA9ZVAZXT+GSOLvKVTdC/hTEtS4aAGM=;
	b=VUXba1iySJl3BYPwfHYUxb/bejUqYdOfrKcaXNhBIX22pQbDVtW3WxY+qjwUQx2d2n
	nAUeRhLzVGR0PqbcGn0QVhnX0fxvhgZcFWE3LBQX2RK2khAKOWnOM7A5M9uMRPBw+YnG
	/BO/y2OP35x3+ZgOLKIV/yQRfiw4m84jqdu/w8Dkr3L4oXnYgRVyPXxCfgdTZO3QRdK/
	WN2zWXvb5FE8qzC5lmj0RWlfQyEWCNZroB0WXuUBbC6YDv/PxQCjyUhkwIs8gNeLR+Bi
	QG/uRWZi53Nu/1fYYL1SQnu7xjMLQ6OYG8kCnn6YfdaoZskc7sq71bCkxv6sq2HHg3r2
	EzSQ==
MIME-Version: 1.0
Received: by 10.68.219.41 with SMTP id pl9mr12625222pbc.61.1339127502130; Thu,
	07 Jun 2012 20:51:42 -0700 (PDT)
Received: by 10.68.213.230 with HTTP; Thu, 7 Jun 2012 20:51:42 -0700 (PDT)
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
	<1339068405.18523.4.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
Date: Fri, 8 Jun 2012 10:51:42 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Ian Tobin 
X-Gm-Message-State: ALoCoQm6phIxH6VtP4T5FN+ReHWOOFMPmgWnrUrqWX7/0jN4eDAm10b+Vc3Vll6xSUGwGdh4im/o
Cc: xen-users@lists.xen.org, Ian Campbell 
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 8:03 PM, Ian Tobin  wrote:

> kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
> extra = "(hd0)/boot/grub/menu.lst"

Does the part in "extra" also the same one you in pvgrub's prompt when booting?

> ip="172.20.45.10"
> netmask="255.255.0.0"
> gateway="172.20.0.1"
> hostname = "testlinux"

IIRC these settings won't work with pvgrub. In fact, it will prevent
pvgrub from working. Something to do with parameter ordering to the
kernel, since those lines basically pass extra parameters to the
kernel as well. Try REMOVING those lines, and see if it works.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 08 03:53:02 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 03:53: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 1ScqEl-0004v8-BF; Fri, 08 Jun 2012 03:51:47 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScqEj-0004v3-Tw
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:51:46 +0000
Received: from [85.158.138.51:58129] by server-8.bemta-3.messagelabs.com id
	15/A6-22118-1D671DF4; Fri, 08 Jun 2012 03:51:45 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-7.tower-174.messagelabs.com!1339127502!22476227!1
X-Originating-IP: [209.85.160.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20152 invoked from network); 8 Jun 2012 03:51:44 -0000
Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com)
	(209.85.160.45)
	by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:51:44 -0000
Received: by pbbro12 with SMTP id ro12so2117608pbb.32
	for ; Thu, 07 Jun 2012 20:51:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=6kelro2+UcfffA9ZVAZXT+GSOLvKVTdC/hTEtS4aAGM=;
	b=VUXba1iySJl3BYPwfHYUxb/bejUqYdOfrKcaXNhBIX22pQbDVtW3WxY+qjwUQx2d2n
	nAUeRhLzVGR0PqbcGn0QVhnX0fxvhgZcFWE3LBQX2RK2khAKOWnOM7A5M9uMRPBw+YnG
	/BO/y2OP35x3+ZgOLKIV/yQRfiw4m84jqdu/w8Dkr3L4oXnYgRVyPXxCfgdTZO3QRdK/
	WN2zWXvb5FE8qzC5lmj0RWlfQyEWCNZroB0WXuUBbC6YDv/PxQCjyUhkwIs8gNeLR+Bi
	QG/uRWZi53Nu/1fYYL1SQnu7xjMLQ6OYG8kCnn6YfdaoZskc7sq71bCkxv6sq2HHg3r2
	EzSQ==
MIME-Version: 1.0
Received: by 10.68.219.41 with SMTP id pl9mr12625222pbc.61.1339127502130; Thu,
	07 Jun 2012 20:51:42 -0700 (PDT)
Received: by 10.68.213.230 with HTTP; Thu, 7 Jun 2012 20:51:42 -0700 (PDT)
In-Reply-To: <039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
References: 
	<1337676390.10118.23.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65EC@electron.tidyhosts.com>
	<1339068405.18523.4.camel@zakaz.uk.xensource.com>
	<039E0B4AA9103344A80DA55DDDC76A936A65F0@electron.tidyhosts.com>
Date: Fri, 8 Jun 2012 10:51:42 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Ian Tobin 
X-Gm-Message-State: ALoCoQm6phIxH6VtP4T5FN+ReHWOOFMPmgWnrUrqWX7/0jN4eDAm10b+Vc3Vll6xSUGwGdh4im/o
Cc: xen-users@lists.xen.org, Ian Campbell 
Subject: Re: [Xen-users] Pvgrub on Debian dom0
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Thu, Jun 7, 2012 at 8:03 PM, Ian Tobin  wrote:

> kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
> extra = "(hd0)/boot/grub/menu.lst"

Does the part in "extra" also the same one you in pvgrub's prompt when booting?

> ip="172.20.45.10"
> netmask="255.255.0.0"
> gateway="172.20.0.1"
> hostname = "testlinux"

IIRC these settings won't work with pvgrub. In fact, it will prevent
pvgrub from working. Something to do with parameter ordering to the
kernel, since those lines basically pass extra parameters to the
kernel as well. Try REMOVING those lines, and see if it works.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Fri Jun 08 04:00:55 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 04:00: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 1ScqMf-0005AY-Hk; Fri, 08 Jun 2012 03:59:57 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScqMe-0005AP-7G
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:59:56 +0000
Received: from [193.109.254.147:51549] by server-2.bemta-14.messagelabs.com id
	DF/F9-27740-BB871DF4; Fri, 08 Jun 2012 03:59:55 +0000
X-Env-Sender: shinepf@gmail.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1339127993!8652710!1
X-Originating-IP: [209.85.214.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24781 invoked from network); 8 Jun 2012 03:59:54 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:59:54 -0000
Received: by obbwd20 with SMTP id wd20so2547491obb.32
	for ; Thu, 07 Jun 2012 20:59:52 -0700 (PDT)
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=mpJmwxkrYSFvcVWuc0aO2d+o5vUQcvjvp12RhwTOAKU=;
	b=XEPlne0RtaDr/CHjWPBsFolNSdmTURfw+DjMmD9/LuHbiBIemzKktDcjWway+rDKLN
	uoTD1zl/UEQ7jBf3KD2ONCTZCjgvYnhHd7XJCLu6JIhq40Op6+wdCfZZnqUllgMAneG1
	BNYd3YuyNSQubcZ4rmLbxDalmnN1Xkp/5TJ/I5BPJKuiRwB1wroDIYYCUCJ5Db+GjOa/
	Y4ecFL79RtVlQlLLZ/Ly7ziclj1z/Qtgva2tZb42dmtWBQ7QrYvNN8yh1zlTnxO6roix
	eXZ4igGRAICflYamuNoFdonaPO1p/Dkm6I/vlIsj4Je/Z9v51pUc46LOYDcxjvSEpeff
	SRPw==
MIME-Version: 1.0
Received: by 10.182.17.8 with SMTP id k8mr4547033obd.25.1339127992787; Thu, 07
	Jun 2012 20:59:52 -0700 (PDT)
Received: by 10.182.22.35 with HTTP; Thu, 7 Jun 2012 20:59:52 -0700 (PDT)
Date: Fri, 8 Jun 2012 13:59:52 +1000
Message-ID: 
From: pf shineyear 
To: xen-users@lists.xen.org, xen-api@lists.xen.org
Subject: [Xen-users] xapi + ubuntu 12.04 out of memory crash
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5400771968727288658=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5400771968727288658==
Content-Type: multipart/alternative; boundary=f46d044473f551a46804c1ee08f2

--f46d044473f551a46804c1ee08f2
Content-Type: text/plain; charset=ISO-8859-1

hi all,

i meet a big problem, when i finish install xcp-xapi on ubuntu 12.04,

i set grub to go into xen 4.1 kernel when startup and set echo
'TOOLSTACK="xapi"' > /etc/default/xen

when i reboot and login to the system , i got a lot out of memory error and
all process be killed, seem like kernel crash.

can anyone help me about that ?

thanks.

--f46d044473f551a46804c1ee08f2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi all,=A0

i meet a big problem, when i finish install x=
cp-xapi on ubuntu 12.04,=A0

i set grub to go into =
xen 4.1 kernel when startup and set=A0echo 'TOOL=
STACK=3D"xapi"' > /etc/default/xen



when i reboot and login to the system , i got a lot out of memo=
ry error and all process be killed, seem like kernel crash.



can anyone help me about that ?

thanks.


--f46d044473f551a46804c1ee08f2--


--===============5400771968727288658==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5400771968727288658==--


From xen-users-bounces@lists.xen.org Fri Jun 08 04:00:55 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 04:00: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 1ScqMf-0005AY-Hk; Fri, 08 Jun 2012 03:59:57 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScqMe-0005AP-7G
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 03:59:56 +0000
Received: from [193.109.254.147:51549] by server-2.bemta-14.messagelabs.com id
	DF/F9-27740-BB871DF4; Fri, 08 Jun 2012 03:59:55 +0000
X-Env-Sender: shinepf@gmail.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1339127993!8652710!1
X-Originating-IP: [209.85.214.173]
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-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24781 invoked from network); 8 Jun 2012 03:59:54 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 03:59:54 -0000
Received: by obbwd20 with SMTP id wd20so2547491obb.32
	for ; Thu, 07 Jun 2012 20:59:52 -0700 (PDT)
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=mpJmwxkrYSFvcVWuc0aO2d+o5vUQcvjvp12RhwTOAKU=;
	b=XEPlne0RtaDr/CHjWPBsFolNSdmTURfw+DjMmD9/LuHbiBIemzKktDcjWway+rDKLN
	uoTD1zl/UEQ7jBf3KD2ONCTZCjgvYnhHd7XJCLu6JIhq40Op6+wdCfZZnqUllgMAneG1
	BNYd3YuyNSQubcZ4rmLbxDalmnN1Xkp/5TJ/I5BPJKuiRwB1wroDIYYCUCJ5Db+GjOa/
	Y4ecFL79RtVlQlLLZ/Ly7ziclj1z/Qtgva2tZb42dmtWBQ7QrYvNN8yh1zlTnxO6roix
	eXZ4igGRAICflYamuNoFdonaPO1p/Dkm6I/vlIsj4Je/Z9v51pUc46LOYDcxjvSEpeff
	SRPw==
MIME-Version: 1.0
Received: by 10.182.17.8 with SMTP id k8mr4547033obd.25.1339127992787; Thu, 07
	Jun 2012 20:59:52 -0700 (PDT)
Received: by 10.182.22.35 with HTTP; Thu, 7 Jun 2012 20:59:52 -0700 (PDT)
Date: Fri, 8 Jun 2012 13:59:52 +1000
Message-ID: 
From: pf shineyear 
To: xen-users@lists.xen.org, xen-api@lists.xen.org
Subject: [Xen-users] xapi + ubuntu 12.04 out of memory crash
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5400771968727288658=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============5400771968727288658==
Content-Type: multipart/alternative; boundary=f46d044473f551a46804c1ee08f2

--f46d044473f551a46804c1ee08f2
Content-Type: text/plain; charset=ISO-8859-1

hi all,

i meet a big problem, when i finish install xcp-xapi on ubuntu 12.04,

i set grub to go into xen 4.1 kernel when startup and set echo
'TOOLSTACK="xapi"' > /etc/default/xen

when i reboot and login to the system , i got a lot out of memory error and
all process be killed, seem like kernel crash.

can anyone help me about that ?

thanks.

--f46d044473f551a46804c1ee08f2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi all,=A0

i meet a big problem, when i finish install x=
cp-xapi on ubuntu 12.04,=A0

i set grub to go into =
xen 4.1 kernel when startup and set=A0echo 'TOOL=
STACK=3D"xapi"' > /etc/default/xen



when i reboot and login to the system , i got a lot out of memo=
ry error and all process be killed, seem like kernel crash.



can anyone help me about that ?

thanks.


--f46d044473f551a46804c1ee08f2--


--===============5400771968727288658==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============5400771968727288658==--


From xen-users-bounces@lists.xen.org Fri Jun 08 06:09:20 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 08 Jun 2012 06:09: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 1ScsMj-0006oU-4L; Fri, 08 Jun 2012 06:08:09 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1ScsMh-0006oP-NC
	for xen-users@lists.xen.org; Fri, 08 Jun 2012 06:08:08 +0000
Received: from [85.158.143.35:7107] by server-3.bemta-4.messagelabs.com id
	43/2A-29237-7C691DF4; Fri, 08 Jun 2012 06:08:07 +0000
X-Env-Sender: sooner1943@gmail.com
X-Msg-Ref: server-14.tower-21.messagelabs.com!1339135683!19399697!1
X-Originating-IP: [209.85.161.173]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Version: 6.5.10; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22003 invoked from network); 8 Jun 2012 06:08:04 -0000
Received: from mail-gg0-f173.google.com (HELO mail-gg0-f173.google.com)
	(209.85.161.173)
	by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	8 Jun 2012 06:08:04 -0000
Received: by ggnp1 with SMTP id p1so1173003ggn.32
	for ; Thu, 07 Jun 2012 23:08:03 -0700 (PDT)
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
	:content-type; bh=Bt6HOf2JCdpFcavf/sUDQdqB9F9bE7LZJvWFIodKtAA=;
	b=k5Vrb8ta6ifnDN7Eps3KNSDHgcds9wCd2QXtrzF4F9jpk3M9TmQmNNBopDaIMHRbp5
	pNTSMY3Bq8pUDCMpjPATxSfmoEYwD5iik633soGViGcPJUjTwYWPISy8lUBSXp7dvasD
	GqEFoLA/jty/5zKa6B6XxjHy+U3Ogxjf/ph+xu8pZAryAQ0VI6sQPel3sTTyKOCMIeWR
	WALeKqClpZCwyHLhfMmYpTC1EKYPnSOK7C2u3HsXjh8YLxOjB3zu/Vx421PaQlBkrYEk
	M/PlT5X6jyX1DqwJafUv31WT0B7HPq/usMC6eWMUB9z2y1rGt8VIIsUeoXKxdcK/G+Gn
	1oBQ==
MIME-Version: 1.0
Received: by 10.50.171.41 with SMTP id ar9mr2509929igc.56.1339135682732; Thu,
	07 Jun 2012 23:08:02 -0700 (PDT)
Received: by 10.231.29.17 with HTTP; Thu, 7 Jun 2012 23:08:02 -0700 (PDT)
In-Reply-To: 
References: 
Date: Fri, 8 Jun 2012 14:08:02 +0800
Message-ID: 
From: =?GB2312?B?zfXYpg==?= 
To: xen-users@lists.xen.org
Subject: [Xen-users] network is only connected for a while when the domU is
	started
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3680905089663685912=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============3680905089663685912==
Content-Type: multipart/alternative; boundary=e89a8f234583ace22c04c1efd22b

--e89a8f234583ace22c04c1efd22b
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hi ALL,

Here is a weird problem comfusing me for a long time. i'v installed xen
4.0.1 with linux kernel 3.1.0-rc9+
Everything works fine except i cannot ping to the gateway in a PVM domU.
i'v installed bridge-utils and brctl show like this

  bridge  name         bridge id                      STP          enabled
interfaces
eth0                      8000.00219b480d56     no             peth0

    vif11.0
virbr0                     8000.000000000000     yes

 The domU is supposed to get a IP from a DHCP server in our network so i
can access to it from any node in that network.
i made the eth0 bridge as a switch and the domU could access to the DHCP
server across it. it works fine on a HVM domU.

 The most weird part is the PVM could get an IP address every time i start
it and i could ping to the gateway too. But after just a few minutes, the
ping process is stuck, and the host become unreacheable. At the same time,
i restart the network, and the eth0 in domU could not get an IP address.

 i post the output here:

 133.133.133.40 is the IP address of gateway
133.133.134.171 is the IP address of the PVM domU

  [root@localhost ~]# ping 133.133.133.40
PING 133.133.133.40 (133.133.133.40) 56(84) bytes of data.
64 bytes from 133.133.133.40: icmp_seq=3D1 ttl=3D64 time=3D0.824 ms
64 bytes from 133.133.133.40: icmp_seq=3D2 ttl=3D64 time=3D0.491 ms
64 bytes from 133.133.133.40: icmp_seq=3D3 ttl=3D64 time=3D0.495 ms
64 bytes from 133.133.133.40: icmp_seq=3D4 ttl=3D64 time=3D0.437 ms
64 bytes from 133.133.133.40: icmp_seq=3D5 ttl=3D64 time=3D0.459 ms
64 bytes from 133.133.133.40: icmp_seq=3D6 ttl=3D64 time=3D1.16 ms
64 bytes from 133.133.133.40: icmp_seq=3D7 ttl=3D64 time=3D0.454 ms
64 bytes from 133.133.133.40: icmp_seq=3D8 ttl=3D64 time=3D0.454 ms
64 bytes from 133.133.133.40: icmp_seq=3D9 ttl=3D64 time=3D0.528 ms
64 bytes from 133.133.133.40: icmp_seq=3D10 ttl=3D64 time=3D0.447 ms
64 bytes from 133.133.133.40: icmp_seq=3D11 ttl=3D64 time=3D0.505 ms
64 bytes from 133.133.133.40: icmp_seq=3D12 ttl=3D64 time=3D0.398 ms
64 bytes from 133.133.133.40: icmp_seq=3D13 ttl=3D64 time=3D0.452 ms
64 bytes from 133.133.133.40: icmp_seq=3D14 ttl=3D64 time=3D0.504 ms
64 bytes from 133.133.133.40: icmp_seq=3D15 ttl=3D64 time=3D0.456 ms
64 bytes from 133.133.133.40: icmp_seq=3D16 ttl=3D64 time=3D0.451 ms
64 bytes from 133.133.133.40: icmp_seq=3D17 ttl=3D64 time=3D0.501 ms
64 bytes from 133.133.133.40: icmp_seq=3D18 ttl=3D64 time=3D0.446 ms
64 bytes from 133.133.133.40: icmp_seq=3D19 ttl=3D64 time=3D0.373 ms
64 bytes from 133.133.133.40: icmp_seq=3D20 ttl=3D64 time=3D0.413 ms
64 bytes from 133.133.133.40: icmp_seq=3D21 ttl=3D64 time=3D0.495 ms
64 bytes from 133.133.133.40: icmp_seq=3D22 ttl=3D64 time=3D0.452 ms
64 bytes from 133.133.133.40: icmp_seq=3D23 ttl=3D64 time=3D0.407 ms
64 bytes from 133.133.133.40: icmp_seq=3D24 ttl=3D64 time=3D0.505 ms
64 bytes from 133.133.133.40: icmp_seq=3D25 ttl=3D64 time=3D0.471 ms
64 bytes from 133.133.133.40: icmp_seq=3D26 ttl=3D64 time=3D0.458 ms
64 bytes from 133.133.133.40: icmp_seq=3D27 ttl=3D64 time=3D0.453 ms
64 bytes from 133.133.133.40: icmp_seq=3D28 ttl=3D64 time=3D0.453 ms
64 bytes from 133.133.133.40: icmp_seq=3D29 ttl=3D64 time=3D0.456 ms
64 bytes from 133.133.133.40: icmp_seq=3D30 ttl=3D64 time=3D0.454 ms
64 bytes from 133.133.133.40: icmp_seq=3D31 ttl=3D64 time=3D0.424 ms
>From 133.133.134.171 icmp_seq=3D85 Destination Host Unreachable
>From 133.133.134.171 icmp_seq=3D86 Destination Host Unreachable
>From 133.133.134.171 icmp_seq=3D87 Destination Host Unreachable
>From 133.133.134.171 icmp_seq=3D89 Destination Host Unreachable
>From 133.133.134.171 icmp_seq=3D90 Destination Host Unreachable
>From 133.133.134.171 icmp_seq=3D91 Destination Host Unreachable

 i also post my configuration of PVM domU here:

  
 centos-para
 67256e52-ac7d-a95e-fd58-8114475e454e
 1048576
 1048576
 1
 /usr/bin/pygrub
 
 linux
 
 
 destroy
 restart
 restart