From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Spector Subject: Xen 4.1 Feature Request List Date: Tue, 6 Apr 2010 13:41:14 -0400 Message-ID: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0416165218==" Return-path: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============0416165218== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_652FFB2C8F91E3428799B1FFF8B490C9726E68A402FTLPMAILBOX01_" --_000_652FFB2C8F91E3428799B1FFF8B490C9726E68A402FTLPMAILBOX01_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (s= hhhh, don't tell anyone) and I wanted to get submissions underway for Xen 4= .1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.co= m/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. = Feel free to add your ideas or send me your features and I will update the = wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/= products/xen_roadmap.html to be a list of 4.1 features tomorrow, after Xen = 4.0 is announced. Thanks. Stephen Spector Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org http://blog.xen.org | @xen_com_mgr --_000_652FFB2C8F91E3428799B1FFF8B490C9726E68A402FTLPMAILBOX01_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Xen Community:

 

As many of you are aware, the Xen 4.0 hypervisor is du= e to ship tomorrow (shhhh, don’t tell anyone) and I wanted to get submissi= ons underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource= .com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/pr= oducts/xen_roadmap.html to be a list of 4.1 features tomorrow, after Xen 4.0 is announced.

 

Thanks.

 

Stephen Spector

 

Xen.org Community Manager

T: (772) 621-5062 | M: (954) 854-4257

stephen.spector@xen.org

http://blog.xen.org | @xen_com_mgr

 

--_000_652FFB2C8F91E3428799B1FFF8B490C9726E68A402FTLPMAILBOX01_-- --===============0416165218== 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.xensource.com http://lists.xensource.com/xen-users --===============0416165218==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Markey Subject: Re: [Xen-users] Xen 4.1 Feature Request List Date: Tue, 6 Apr 2010 20:10:12 +0100 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Reply-To: admin@dmarkey.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1415193039==" Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector Cc: Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============1415193039== Content-Type: multipart/alternative; boundary=00163649a03b00957d04839632fb --00163649a03b00957d04839632fb Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Stephen. Might be a long shot, but id really like to see SPICE ported to Xen. http://spice-space.org/ On 6 April 2010 18:41, Stephen Spector wrote: > Xen Community: > > > > As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow > (shhhh, don=92t tell anyone) and I wanted to get submissions underway for= Xen > 4.1 features. I have updated the Roadmap Wiki page ( > http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen > 4.1 features to be added. Feel free to add your ideas or send me your > features and I will update the wiki. I also plan to update the Xen.org > roadmap page at http://www.xen.org/products/xen_roadmap.html to be a list > of 4.1 features tomorrow, after Xen 4.0 is announced. > > > > Thanks. > > > > *Stephen Spector* > > > > Xen.org Community Manager > > *T:* (772) 621-5062 | *M:* (954) 854-4257 > > stephen.spector@xen.org > > http://blog.xen.org | @xen_com_mgr > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > --00163649a03b00957d04839632fb Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi Stephen.

Might be a long shot, but id really li= ke to see SPICE ported to Xen.




On 6 April 2010 18:41, Stephen Spector = <stephen= .spector@citrix.com> wrote:

Xen Community:

=A0

As many of you are aware, the Xen 4.0 hypervisor is = due to ship tomorrow (shhhh, don=92t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http:/= /wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/products/xen_roadmap.= html to be a list of 4.1 features tomorrow, after Xen 4.0 is announced.

=A0

Thanks.

=A0

Stephen Spector

=A0

Xen.org Community Manager

T: (772) 621-5062 | M: (954) 854-4257<= /p>

stephen.spector@xen.org

ht= tp://blog.xen.org | @xen_com_mgr

=A0


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.= com
http://l= ists.xensource.com/xen-users

--00163649a03b00957d04839632fb-- --===============1415193039== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1415193039==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 12:07:02 +0100 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: David Markey Cc: Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org On Tue, 6 Apr 2010, David Markey wrote: > Hi Stephen. > > Might be a long shot, but id really like to see SPICE ported to Xen. > http://spice-space.org/ > spice has to be ported to qemu first, then when we complete the merge with upstream qemu, we'll inherit spice as well. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant McWilliams Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 04:15:29 -0700 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0913271501==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: David Markey , Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org --===============0913271501== Content-Type: multipart/alternative; boundary=001485ec0e58357d260483a3af66 --001485ec0e58357d260483a3af66 Content-Type: text/plain; charset=UTF-8 On Wed, Apr 7, 2010 at 4:07 AM, Stefano Stabellini < stefano.stabellini@eu.citrix.com> wrote: > On Tue, 6 Apr 2010, David Markey wrote: > > Hi Stephen. > > > > Might be a long shot, but id really like to see SPICE ported to Xen. > > http://spice-space.org/ > > > > spice has to be ported to qemu first, then when we complete the merge > with upstream qemu, we'll inherit spice as well. > I see Spice listed as being in RHEL 5.5 (with KVM). Is it already in qemu or are they doing something custom? Grant McWilliams --001485ec0e58357d260483a3af66 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Wed, Apr 7, 2010 at 4:07 AM, Stefano = Stabellini <stefano.stabellini@eu.citrix.com> wrote:
On Tue, 6 Apr 2010, David Markey wrote:
> Hi Stephen.
>
> Might be a long shot, but id really like to see SPICE ported to Xen. > http://spice-spa= ce.org/
>

spice has to be ported to qemu first, then when we complete the merge=
with upstream qemu, we'll inherit spice as well.
=
I see Spice listed as being in RHEL 5.5 (with KVM). Is it already in qe= mu or are they doing something
custom?

Grant McWilliams
--001485ec0e58357d260483a3af66-- --===============0913271501== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0913271501==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant McWilliams Subject: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 04:13:07 -0700 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2125944060==" Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector Cc: Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============2125944060== Content-Type: multipart/alternative; boundary=001485e7c806bc00fd0483a3a631 --001485e7c806bc00fd0483a3a631 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Apr 6, 2010 at 10:41 AM, Stephen Spector wrote: > Xen Community: > > > > As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow > (shhhh, don=E2=80=99t tell anyone) and I wanted to get submissions underw= ay for Xen > 4.1 features. I have updated the Roadmap Wiki page ( > http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen > 4.1 features to be added. Feel free to add your ideas or send me your > features and I will update the wiki. I also plan to update the Xen.org > roadmap page at http://www.xen.org/products/xen_roadmap.html to be a list > of 4.1 features tomorrow, after Xen 4.0 is announced. > > > > Thanks. > > > > *Stephen Spector* > These might not be wishes for 4.1 as some may be too big but they're my wishlist anyway. Note they also might not be things that belong to the Hypervisor but rather to tools associated with. 1. Make qcow2 actually work and include backing files. 1. If it can't be made to work then it should be taken out and not mentioned in the docs so we don't waste weeks trying to get it to wor= k. 2. Figure out why you can't start a VM with a disk image residing in = a ramdisk (bug?) 3. Nesting 1. As silly as this feature sounds it may be why I leave Xen for KVM. This would be useful for teaching management of VMs. A student could have a Dom0 and start up DomUs inside it without each on needing their own physical machine. 4. Install PV DomU from CD without FTP/NFS tricks. 1. I don't care how it's done but it would be nice. The "install from network" shuffle can pose a complexity for people getting started in = Xen. I'm aware that HVM does this because of it's use of Qemu but it would= be nice everywhere. Maybe as Xen moves to Hybrid VMs instead of PV/HVM t= his will no longer be an issue. I'm sure I'll think of others but that's off the top of my head. Like I sai= d maybe some of it would be Xen 5 stuff, I don't know. --001485e7c806bc00fd0483a3a631 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Tue, Apr 6, 2010 at 10:41 AM, Stephen= Spector <stephen.spector@citrix.com> wrote:

Xen Community:

=C2=A0

As many of you are aware, the Xen 4.0 hypervisor is = due to ship tomorrow (shhhh, don=E2=80=99t tell anyone) and I wanted to get submis= sions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http:/= /wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/products/xen_roadmap.= html to be a list of 4.1 features tomorrow, after Xen 4.0 is announced.

=C2=A0

Thanks.

=C2=A0

Stephen Spector

<= div>
These might not be wishes for 4.1 as some may be too big but they&#= 39;re my wishlist anyway. Note they also might not be things that belong to= the Hypervisor but rather to tools associated with.

  1. Make qcow2 actually work and include backing files.
      2. If it can't be made to work then it should be taken out and not mentio= ned in the docs so we don't waste weeks trying to get it to work.
  2. Figure out why you can't start a VM with a disk image res= iding in a ramdisk (bug?)
  3. Nesting
    1. As silly as this feat= ure sounds it may be why I leave Xen for KVM. This would be useful for teac= hing management of VMs. A student could have a Dom0 and start up DomUs insi= de it without each on needing their own physical machine.
  4. Install PV DomU from CD without FTP/NFS tricks.
      5. =
    1. I don't care how it's done but it would be nice. The "inst= all from network" shuffle can pose a complexity for people getting sta= rted in Xen. I'm aware that HVM does this because of it's use of Qe= mu but it would be nice everywhere. Maybe as Xen moves to Hybrid VMs instea= d of PV/HVM this will no longer be an issue.

I'm sure I'll think of others but that's of= f the top of my head. Like I said maybe some of it would be Xen 5 stuff, I = don't know.
--001485e7c806bc00fd0483a3a631-- --===============2125944060== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2125944060==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: [Xen-devel] Re: Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 12:18:46 +0100 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Grant McWilliams Cc: Xen-devel , Stefano Stabellini , Spector , David Markey , Stephen, Xen List List-Id: xen-devel@lists.xenproject.org On Wed, 7 Apr 2010, Grant McWilliams wrote: > On Wed, Apr 7, 2010 at 4:07 AM, Stefano Stabellini wrote: > On Tue, 6 Apr 2010, David Markey wrote: > > Hi Stephen. > > > > Might be a long shot, but id really like to see SPICE ported to Xen. > > http://spice-space.org/ > > > > spice has to be ported to qemu first, then when we complete the merge > with upstream qemu, we'll inherit spice as well. > > > I see Spice listed as being in RHEL 5.5 (with KVM). Is it already in qemu or are they doing something > custom? > Spice is not in Qemu yet, they probably have a very big custom patch in their patchqueue. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-devel] Re: Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 14:27:22 +0300 Message-ID: <20100407112722.GS1878@reaktio.net> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Grant McWilliams Cc: David Markey , Xen List , Xen-devel , Stephen Spector , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, Apr 07, 2010 at 04:15:29AM -0700, Grant McWilliams wrote: > On Wed, Apr 7, 2010 at 4:07 AM, Stefano Stabellini > <[1]stefano.stabellini@eu.citrix.com> wrote: > > On Tue, 6 Apr 2010, David Markey wrote: > > Hi Stephen. > > > > Might be a long shot, but id really like to see SPICE ported to Xen. > > [2]http://spice-space.org/ > > > > spice has to be ported to qemu first, then when we complete the merge > with upstream qemu, we'll inherit spice as well. > > I see Spice listed as being in RHEL 5.5 (with KVM). Is it already in qemu > or are they doing something > custom? > It's custom. Spice hasn't been merged to upstream Qemu yet. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Markey Subject: Re: [Xen-devel] Re: Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 14:06:22 +0100 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <20100407112722.GS1878@reaktio.net> Reply-To: admin@dmarkey.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2093042306==" Return-path: In-Reply-To: <20100407112722.GS1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Stephen Spector , Grant McWilliams , Xen List , Xen-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --===============2093042306== Content-Type: multipart/alternative; boundary=001485f5cdde9ab3a80483a53ac7 --001485f5cdde9ab3a80483a53ac7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh yes. It would be great if we could have HVM PV drivers in kernel.org. On 7 April 2010 12:27, Pasi K=E4rkk=E4inen wrote: > On Wed, Apr 07, 2010 at 04:15:29AM -0700, Grant McWilliams wrote: > > On Wed, Apr 7, 2010 at 4:07 AM, Stefano Stabellini > > <[1]stefano.stabellini@eu.citrix.com> wrote: > > > > On Tue, 6 Apr 2010, David Markey wrote: > > > Hi Stephen. > > > > > > Might be a long shot, but id really like to see SPICE ported to > Xen. > > > [2]http://spice-space.org/ > > > > > > > spice has to be ported to qemu first, then when we complete the > merge > > with upstream qemu, we'll inherit spice as well. > > > > I see Spice listed as being in RHEL 5.5 (with KVM). Is it already in > qemu > > or are they doing something > > custom? > > > > It's custom. Spice hasn't been merged to upstream Qemu yet. > > -- Pasi > > --001485f5cdde9ab3a80483a53ac7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh yes.

It would be great if we could have HVM PV driver= s in kernel.org.


On 7 April 2010 12:27, Pasi K=E4rkk=E4inen <pasik@iki.fi> wr= ote:
On Wed, Apr 07, 2010 at 0= 4:15:29AM -0700, Grant McWilliams wrote:
> =A0 =A0On Wed, Apr 7, 2010 at 4:07 AM, Stefano Stabellini
> =A0 =A0<[1]stefano.stabellini@eu.citrix.com> wrote:
>
> =A0 =A0 =A0On Tue, 6 Apr 2010, David Markey wrote:
> =A0 =A0 =A0> Hi Stephen.
> =A0 =A0 =A0>
> =A0 =A0 =A0> Might be a long shot, but id really like to see SPICE = ported to Xen.
> =A0 =A0 =A0> [2]http://spice-space.org/
> =A0 =A0 =A0>
>
> =A0 =A0 =A0spice has to be ported to qemu first, then when we complete= the merge
> =A0 =A0 =A0with upstream qemu, we'll inherit spice as well.
>
> =A0 =A0I see Spice listed as being in RHEL 5.5 (with KVM). Is it alrea= dy in qemu
> =A0 =A0or are they doing something
> =A0 =A0custom?
>

It's custom. =A0Spice hasn't been merged to upstream Qemu yet= .

-- Pasi


--001485f5cdde9ab3a80483a53ac7-- --===============2093042306== 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.xensource.com http://lists.xensource.com/xen-users --===============2093042306==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Sturm Subject: RE: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 09:51:08 -0400 Message-ID: <64D0546C5EBBD147B75DE133D798665F055D8E62@hugo.eprize.local> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0600058021==" Return-path: Content-Class: urn:content-classes:message In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector , Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============0600058021== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD659.604050A4" ------_=_NextPart_001_01CAD659.604050A4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable It would be nice if XenFS, or something like it, ever came to fruition. We've gotten by with clustered filesystems on our domU's, but these are a bit heavyweight in comparison. =20 -Jeff =20 From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Stephen Spector Sent: Tuesday, April 06, 2010 1:41 PM To: Xen-devel; Xen List Subject: [Xen-users] Xen 4.1 Feature Request List =20 Xen Community: =20 As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don't tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/products/xen_roadmap.html to be a list of 4.1 features tomorrow, after Xen 4.0 is announced.=20 =20 Thanks.=20 =20 Stephen Spector =20 Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org=20 http://blog.xen.org | @xen_com_mgr =20 ------_=_NextPart_001_01CAD659.604050A4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

It would be nice if XenFS, or something like it, ever = came to fruition.  We've gotten by with clustered filesystems on our = domU's, but these are a bit heavyweight in comparison.

 

-Jeff

 

From:= xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of = Stephen Spector
Sent: Tuesday, April 06, 2010 1:41 PM
To: Xen-devel; Xen List
Subject: [Xen-users] Xen 4.1 Feature Request = List

 

Xen Community:

 

As many of you are aware, the Xen 4.0 hypervisor is = due to ship tomorrow (shhhh, don’t tell anyone) and I wanted to get = submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensour= ce.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add = your ideas or send me your features and I will update the wiki. I also plan = to update the Xen.org roadmap page at http://www.xen.org/= products/xen_roadmap.html to be a list of 4.1 features tomorrow, after Xen 4.0 is announced. =

 

Thanks.

 

Stephen Spector

 

Xen.org Community Manager

T: (772) 621-5062 | M: (954) = 854-4257

stephen.spector@xen.org

http://blog.xen.org | @xen_com_mgr

 

------_=_NextPart_001_01CAD659.604050A4-- --===============0600058021== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0600058021==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 15:07:40 +0100 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <20100407112722.GS1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: David Markey Cc: Xen-devel , Stefano Stabellini , Xen List , Grant McWilliams , Stephen Spector List-Id: xen-devel@lists.xenproject.org On Wed, 7 Apr 2010, David Markey wrote: > Oh yes. > It would be great if we could have HVM PV drivers in kernel.org. > Yes, it would. I'll work on that. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 17:51:53 +0300 Message-ID: <20100407145153.GT1878@reaktio.net> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Grant McWilliams Cc: Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org On Wed, Apr 07, 2010 at 04:13:07AM -0700, Grant McWilliams wrote: > > These might not be wishes for 4.1 as some may be too big but they're my > wishlist anyway. Note they also might not be things that belong to the > Hypervisor but rather to tools associated with. > > 1. Make qcow2 actually work and include backing files. > Have you checked out blktap2 VHD support? Does it work for you? See: http://wiki.xensource.com/xenwiki/XenCommonProblems for links. > 1. If it can't be made to work then it should be taken out and not > mentioned in the docs so we don't waste weeks trying to get it to > work. > >>From which docs? > 2. Figure out why you can't start a VM with a disk image residing in a > ramdisk (bug?) I have never tried this one. Which disk backend did you use? > 3. Nesting > > 1. As silly as this feature sounds it may be why I leave Xen for > KVM. This would be useful for teaching management of VMs. A > student could have a Dom0 and start up DomUs inside it without > each on needing their own physical machine. > There was a presentation about Xen 'nested' virtualization at Xen Summit 2009: http://www.xen.org/files/xensummit_intel09/xensummit-nested-virt.pdf Youtube also has some videos about the presentation. > 4. Install PV DomU from CD without FTP/NFS tricks. > > 1. I don't care how it's done but it would be nice. The "install > from network" shuffle can pose a complexity for people getting > started in Xen. I'm aware that HVM does this because of it's use > of Qemu but it would be nice everywhere. Maybe as Xen moves to > Hybrid VMs instead of PV/HVM this will no longer be an issue. > There has been work for hybrid HVM+PV Xen guests recently by Intel and Citrix. The problem of booting PV domU installers from a CD/.iso is the fact that the CD needs to have a Xen PV kernel included! Many images don't have that. This is changing now when distros ship kernels with pvops Xen domU support enabled, it has been in the mainline Linux for a couple of years now. > I'm sure I'll think of others but that's off the top of my head. Like I > said maybe some of it would be Xen 5 stuff, I don't know. > -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 07 Apr 2010 10:17:48 -0700 Message-ID: <4BBCBE3C.8030203@goop.org> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Grant McWilliams Cc: Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org On 04/07/2010 04:13 AM, Grant McWilliams wrote: > > 1. Figure out why you can't start a VM with a disk image residing > in a ramdisk (bug?) > What happens if you do that? > 1. Nesting > 1. As silly as this feature sounds it may be why I leave Xen > for KVM. This would be useful for teaching management of > VMs. A student could have a Dom0 and start up DomUs inside > it without each on needing their own physical machine. > Xen nests OK, so long as you're happy running purely PV guests within the inner Xen. > 1. > > > 1. Install PV DomU from CD without FTP/NFS tricks. > 1. I don't care how it's done but it would be nice. The > "install from network" shuffle can pose a complexity for > people getting started in Xen. I'm aware that HVM does > this because of it's use of Qemu but it would be nice > everywhere. Maybe as Xen moves to Hybrid VMs instead of > PV/HVM this will no longer be an issue. > What I typically do is install systems as HVM, then just boot them as PV later on. For Fedora installs, at least, it pretty much just works because they avoid having any direct device references for filesystems, etc. It's a bit more fiddly without having HVM available. J From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 07 Apr 2010 19:07:58 +0100 Message-ID: References: <4BBCBE3C.8030203@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BBCBE3C.8030203@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , Grant McWilliams Cc: Xen-devel , Stephen Spector List-Id: xen-devel@lists.xenproject.org On 07/04/2010 18:17, "Jeremy Fitzhardinge" wrote: >> 1. Nesting >> 1. As silly as this feature sounds it may be why I leave Xen >> for KVM. This would be useful for teaching management of >> VMs. A student could have a Dom0 and start up DomUs inside >> it without each on needing their own physical machine. >> > > Xen nests OK, so long as you're happy running purely PV guests within > the inner Xen. There are patches imminently incoming to do this for HVM-on-HVM, for AMD SVM at least. -- Keir From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant McWilliams Subject: Re: Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 13:59:40 -0700 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <20100407145153.GT1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0144979791==" Return-path: In-Reply-To: <20100407145153.GT1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= Cc: Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org --===============0144979791== Content-Type: multipart/alternative; boundary=0016e64651667220500483abd8c1 --0016e64651667220500483abd8c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Apr 7, 2010 at 7:51 AM, Pasi K=C3=A4rkk=C3=A4inen wr= ote: > On Wed, Apr 07, 2010 at 04:13:07AM -0700, Grant McWilliams wrote: > > > > These might not be wishes for 4.1 as some may be too big but they're > my > > wishlist anyway. Note they also might not be things that belong to t= he > > Hypervisor but rather to tools associated with. > > > > 1. Make qcow2 actually work and include backing files. > > > > Have you checked out blktap2 VHD support? Does it work for you? > I haven't. I thought it was only commercial Xenserver that supported VHD. > See: http://wiki.xensource.com/xenwiki/XenCommonProblems > for links. > > > 1. If it can't be made to work then it should be taken out and > not > > mentioned in the docs so we don't waste weeks trying to get > it to > > work. > > > > From which docs? > The internet! :-) I assumed that qcow was in the docs since Xen supports it and it's mentioned all over the forums. It very well might not be mentioned in the docs but it has some support for qcow that no matter which version o= f xen or Centos I used I ran into some bug that stopped me from using it. As class as I got was to use qcow images as disks but with no backing store which I don't think makes a whole lot of sense. > > 2. Figure out why you can't start a VM with a disk image residing i= n > a > > ramdisk (bug?) > > I have never tried this one. Which disk backend did you use? > I was using tap:aio disk images with Xen 3.4. I really wanted to use a qcow= 2 backing disk in a ram disk so all reads would be super fast then the writes would go to the RAID. I then stepped down from that lofty goal and tried to get any DomU to boot from any image in ramdisk and it would error immediately. It's been a while now so I don't remember the error. I could try it again though. > > > > -- Pasi > > Grant McWilliams --0016e64651667220500483abd8c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Wed, Apr 7, 2010 at 7:51 AM, Pasi K=C3=A4= rkk=C3=A4inen <pasik@i= ki.fi> wrote:
On Wed, Apr 07, 2010 at 04:13:07AM -0700, Grant McWilliam= s wrote:
>
> =C2=A0 =C2=A0These might not be wishes for 4.1 as some may be too big = but they're my
> =C2=A0 =C2=A0wishlist anyway. Note they also might not be things that = belong to the
> =C2=A0 =C2=A0Hypervisor but rather to tools associated with.
>
> =C2=A0 =C2=A0 1. Make qcow2 actually work and include backing files. >

Have you checked out blktap2 VHD support? Does it work for you?

I haven't. I thought it was only commercial Xenserv= er that supported VHD.


=C2=A0
See: http://wiki.xensource.com/xenwiki/XenCommonProblems
for links.

> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01. If it can't be made to work t= hen it should be taken out and not
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mentioned = in the docs so we don't waste weeks trying to get it to
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 work.
>

From which docs?

The internet! :-) I assumed= that qcow was in the docs since Xen supports it and it's mentioned all= over the forums. It very well might not be mentioned in the docs but it ha= s some support for qcow that no matter which version of xen or Centos I use= d I ran into some bug that stopped me from using it. As class as I got was = to use qcow images as disks but with no backing store which I don't thi= nk makes a whole lot of sense.


> =C2=A0 =C2=A0 2. Figure out why you can't start a VM with a disk i= mage residing in a
> =C2=A0 =C2=A0 =C2=A0 =C2=A0ramdisk (bug?)

I have never tried this one. Which disk backend did you use?

I was using tap:aio disk images with Xen 3.4. I really wanted t= o use a qcow2 backing disk in a ram disk so all reads would be super fast t= hen the writes would go to the RAID. I then stepped down from that lofty go= al and tried to get any DomU to boot from any image in ramdisk and it would= error immediately. It's been a while now so I don't remember the e= rror. I could try it again though.

=C2=A0
<= div class=3D"im">


-- Pasi


Grant McWilliams
--0016e64651667220500483abd8c1-- --===============0144979791== 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.xensource.com http://lists.xensource.com/xen-users --===============0144979791==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-users] Xen 4.1 Feature Request List Date: Thu, 8 Apr 2010 00:04:07 +0300 Message-ID: <20100407210407.GA1878@reaktio.net> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <20100407145153.GT1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Grant McWilliams Cc: Xen-devel , Stephen Spector , Xen List List-Id: xen-devel@lists.xenproject.org On Wed, Apr 07, 2010 at 01:59:40PM -0700, Grant McWilliams wrote: > On Wed, Apr 7, 2010 at 7:51 AM, Pasi K=C3=83=E2=82=ACrkk=C3=83=E2=82= =ACinen <[1]pasik@iki.fi> wrote: >=20 > On Wed, Apr 07, 2010 at 04:13:07AM -0700, Grant McWilliams wrote: > > > > =C3=82 =C3=82 These might not be wishes for 4.1 as some may be = too big but > they're my > > =C3=82 =C3=82 wishlist anyway. Note they also might not be thin= gs that belong > to the > > =C3=82 =C3=82 Hypervisor but rather to tools associated with. > > > > =C3=82 =C3=82 1. Make qcow2 actually work and include backing = files. > > >=20 > Have you checked out blktap2 VHD support? Does it work for you? >=20 > I haven't. I thought it was only commercial Xenserver that supported= VHD. >=20 Xen 4.0.0 includes blktap2 support in the tools: http://wiki.xensource.co= m/xenwiki/Xen4.0 You also need a kernel with the blktap2 driver: http://wiki.xensource.com/xenwiki/XenKernelFeatures (that XenKernelFeatures wiki page is still a work-in-progress and might n= ot be complete yet). >=20 > See: [2]http://wiki.xensource.com/xenwiki/XenCommonProblems > for links. >=20 > > =C3=82 =C3=82 =C3=82 =C3=82 =C3=82 1. If it can't be made to= work then it should be taken > out and not > > =C3=82 =C3=82 =C3=82 =C3=82 =C3=82 =C3=82 mentioned in the= docs so we don't waste weeks trying > to get it to > > =C3=82 =C3=82 =C3=82 =C3=82 =C3=82 =C3=82 work. > > >=20 > From which docs? >=20 > The internet! :-) I assumed that qcow was in the docs since Xen supp= orts > it and it's mentioned all over the forums. It very well might not be > mentioned in the docs but it has some support for qcow that no matte= r > which version of xen or Centos I used I ran into some bug that stopp= ed me > from using it. As class as I got was to use qcow images as disks but= with > no backing store which I don't think makes a whole lot of sense. > I guess blktap2/vhd was developed because of qcow wasn't that good. =20 > > =C3=82 =C3=82 2. Figure out why you can't start a VM with a di= sk image > residing in a > > =C3=82 =C3=82 =C3=82 =C3=82 ramdisk (bug?) >=20 > I have never tried this one. Which disk backend did you use? >=20 > I was using tap:aio disk images with Xen 3.4. I really wanted to use= a > qcow2 backing disk in a ram disk so all reads would be super fast th= en the > writes would go to the RAID. I then stepped down from that lofty goa= l and > tried to get any DomU to boot from any image in ramdisk and it would= error > immediately. It's been a while now so I don't remember the error. I = could > try it again though. >=20 Ok. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fantu Subject: Re: Xen 4.1 Feature Request List Date: Thu, 8 Apr 2010 05:33:58 -0700 (PDT) Message-ID: <28177904.post@talk.nabble.com> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On HVM domU make possible boot from cd/dvd from file, now is possible only with do loop for "false physical device" and do work it Stephen Spector wrote: > > Xen Community: > > As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow > (shhhh, don't tell anyone) and I wanted to get submissions underway for > Xen 4.1 features. I have updated the Roadmap Wiki page > (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen > 4.1 features to be added. Feel free to add your ideas or send me your > features and I will update the wiki. I also plan to update the Xen.org > roadmap page at http://www.xen.org/products/xen_roadmap.html to be a list > of 4.1 features tomorrow, after Xen 4.0 is announced. > > Thanks. > > Stephen Spector > > Xen.org Community Manager > T: (772) 621-5062 | M: (954) 854-4257 > stephen.spector@xen.org > http://blog.xen.org | @xen_com_mgr > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > -- View this message in context: http://old.nabble.com/Xen-4.1-Feature-Request-List-tp28155211p28177904.html Sent from the Xen - Dev mailing list archive at Nabble.com. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen 4.1 Feature Request List Date: Thu, 08 Apr 2010 10:30:25 -0700 Message-ID: <4BBE12B1.7020706@goop.org> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <28177904.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <28177904.post@talk.nabble.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Fantu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 04/08/2010 05:33 AM, Fantu wrote: > On HVM domU make possible boot from cd/dvd from file, now is possible only > with do loop for "false physical device" and do work it > Booting an HVM domain works from a CD/DVD image. I use a statement of the form: 'file:/home/jeremy/win7.iso,hdc:cdrom,r' Is that what you mean? J From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fantu Subject: Re: Xen 4.1 Feature Request List Date: Thu, 8 Apr 2010 11:23:40 -0700 (PDT) Message-ID: <28182598.post@talk.nabble.com> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <28177904.post@talk.nabble.com> <4BBE12B1.7020706@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BBE12B1.7020706@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org is already in xen 4.0 boot from cd in hvm on all and not phy? i not see in changelog or commit comment and i not try in 4.0, if there is already sorry Jeremy Fitzhardinge wrote: > > On 04/08/2010 05:33 AM, Fantu wrote: >> On HVM domU make possible boot from cd/dvd from file, now is possible >> only >> with do loop for "false physical device" and do work it >> > > Booting an HVM domain works from a CD/DVD image. I use a statement of > the form: > > 'file:/home/jeremy/win7.iso,hdc:cdrom,r' > > Is that what you mean? > > J > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > -- View this message in context: http://old.nabble.com/Xen-4.1-Feature-Request-List-tp28155211p28182598.html Sent from the Xen - Dev mailing list archive at Nabble.com. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen 4.1 Feature Request List Date: Thu, 08 Apr 2010 11:40:33 -0700 Message-ID: <4BBE2321.2010707@goop.org> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <28177904.post@talk.nabble.com> <4BBE12B1.7020706@goop.org> <28182598.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <28182598.post@talk.nabble.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Fantu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 04/08/2010 11:23 AM, Fantu wrote: > is already in xen 4.0 boot from cd in hvm on all and not phy? i not see in > changelog or commit comment and i not try in 4.0, if there is already sorry > It has always worked. It isn't a new feature. J From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Goirand Subject: Re: Xen 4.1 Feature Request List Date: Fri, 09 Apr 2010 03:00:26 +0800 Message-ID: <4BBE27CA.5090607@goirand.fr> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <28177904.post@talk.nabble.com> <4BBE12B1.7020706@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BBE12B1.7020706@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org What: ==== It'd be great to be able to do something like: 'exportpath:/var/mypath/myvps1,/,rw' so that the folder /var/mypath/myvps1 of a dom0 would be somehow exported to a domU as /. Both the domU and dom0 would have read/write access to it. Why: === I know it is possible to do this with an NFS export on the dom0 then access it from domU over network, but NFS is slow and has lock issues. Using an LVM slice is ok, but then the space not used by a domU cannot be reused by other VMs on the physical server, resulting in a lot of waste. Also, on the desktop, that'd be great to be able to have a folder shared between multiple VMs. Many emulator have this option (for example some Atari emulators). Why not with Xen too? Just my 2c of idea, without even knowing how much effort would be needed for an implementation... Thomas From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carsten Schiers" Subject: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Thu, 8 Apr 2010 21:46:58 +0200 Message-ID: References: <4BBE27CA.5090607@goirand.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4BBE27CA.5090607@goirand.fr> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel Cc: jeremy , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org OK, I am still a bit fuzzy as I had to learn how to git and configure=20 kernels, and I am still unsure whether I did everything=20 right. Nevertheless, and even when I cannot provide a lot of details, I=20 would like to inform you about some anomalies.=20 Currently, I run Xen 3.4.1 and 2.6.18.8 kernels, 64 Bit Dom0 and some 32=20 Bit and 64 Bit DomUs on a Gigabyte M56S-S3 / AMD 4050e=20 with cpufreq on powernow-k8 in cpufreq=3Ddom0-kernel mode. I make use of=20 PCI Passthrough for DVB-C cards and onboard NIC, as well=20 as for USB controller. Compile problem on xen/stable-2.6.32 ------------------------------------ I compiled 2.6.32.10-pvops for DomU only mode, resulting in compile=20 error very similar to=20 =20 http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00925.html I get a "static declaration of 'xen_register_gsi' follows a non-static=20 declaration, because I have set CONFIG_XEN_PCI_MSI and=20 CONFIG_PCI_XEN, but not CONFIG_XEN_DOM0_PCI. It will disappear when=20 compiling a DOM0 kernel. PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 working on xen/stable-2.6.32 on Xen 3.4.1 ------------------------------------------------------------------------ --------------------------------------- It will allow passthrough of all mentioned devices except one of the PCI=20 controllers. It will not be detected. Using=20 xm pci-attach will produce an error: troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 available because of BAR 0 [0xfc102000-0xfc1020ff] collisions troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 available because of BAR 0 [0xfc104000-0xfc104fff] collisions I first tried only with the 2nd function (or whatever it is called), but=20 as you see, we have the same error with both put into=20 the DomU. nVidia forcedeth, working on pvops/Xen 3.4.1, not working on pvops/Xen=20 4.0 ------------------------------------------------------------------------ -- The whole experiment was done because when I use Xen 4.0 with my=20 2.6.18.8 kernels, I cannot use the onboard NIC any longer. The=20 driver forcedeth will report an error. So, as using the pvops DomU on=20 Xen 3.4.1 worked, I tried to also use a pvops Dom0 underneath Xen 4.0, but the problem seems to be related to the Xen 4.0, which is=20 killing forcedeth MAC address detection. By the way: MSI has never worked for me on that NIC. So I had pci=3Dnomsi on kernel. not working example (MAC is random): troi kernel: [ 4.335591] forcedeth: Reverse Engineered nForce=20 ethernet driver. Version 0.64. troi kernel: [ 4.335811] forcedeth 0000:00:00.0: enabling device=20 (0000 -> 0003) troi kernel: [ 4.335942] forcedeth 0000:00:00.0: Xen PCI enabling=20 IRQ: 23 troi kernel: [ 4.336016] forcedeth 0000:00:00.0: setting latency=20 timer to 64 troi kernel: [ 4.336271] forcedeth 0000:00:00.0: Invalid Mac=20 address detected: 00:00:00:00:00:00 troi kernel: [ 4.336295] forcedeth 0000:00:00.0: Please complain to=20 your hardware vendor. Switching to a random MAC. troi kernel: [ 4.860537] forcedeth 0000:00:00.0: ifname eth0, PHY=20 OUI 0x732 @ 1, addr 5e:1a:09:69:77:5d troi kernel: [ 4.860593] forcedeth 0000:00:00.0: highdma pwrctl=20 mgmt gbit lnktim msi desc-v3 working example (real MAC, note different IRQ): =20 troi kernel: [ 1.133102] forcedeth: Reverse Engineered nForce=20 ethernet driver. Version 0.64. troi kernel: [ 1.133376] forcedeth 0000:00:01.0: enabling device=20 (0000 -> 0003) troi kernel: [ 1.133463] forcedeth 0000:00:01.0: Xen PCI enabling=20 IRQ: 19 troi kernel: [ 1.652048] forcedeth 0000:00:01.0: ifname eth0, PHY=20 OUI 0x732 @ 1, addr 00:1d:7d:e8:97:7b troi kernel: [ 1.652139] forcedeth 0000:00:01.0: highdma pwrctl=20 mgmt gbit lnktim msi desc-v3 powernow-k8 in pvops Dom0 doesn't work any longer with Xen 4.0 -------------------------------------------------------------- I found this in the logs, not idea currently what Xen 3.4.1 with pvops=20 or Xen 4.0 with 2.6.18 kernel would say. data kernel: [ 9.030558] powernow-k8: Found 1 AMD Athlon(tm) Dual=20 Core Processor 4050e processors (2 cpu cores) (version 2.20.00) data kernel: [ 9.030955] [Firmware Bug]: powernow-k8: No compatible=20 ACPI _PSS objects found. data kernel: [ 9.030957] [Firmware Bug]: powernow-k8: Try again=20 with latest BIOS. Best Regards, Carsten. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Thu, 8 Apr 2010 23:12:06 +0300 Message-ID: <20100408201206.GF1878@reaktio.net> References: <4BBE27CA.5090607@goirand.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers Cc: jeremy , xen-devel , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org On Thu, Apr 08, 2010 at 09:46:58PM +0200, Carsten Schiers wrote: > > PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > working on xen/stable-2.6.32 on Xen 3.4.1 > ------------------------------------------------------------------------ > --------------------------------------- > > It will allow passthrough of all mentioned devices except one of the PCI > controllers. It will not be detected. Using > xm pci-attach will produce an error: > > troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > available because of BAR 0 [0xfc104000-0xfc104fff] collisions > > I first tried only with the 2nd function (or whatever it is called), but > as you see, we have the same error with both put into > the DomU. > Have you seen this wiki page?: http://wiki.xensource.com/xenwiki/XenPCIpassthrough Try the "I get "non-page-aligned MMIO BAR" error when trying to start the guest" thing.. maybe it helps? > > powernow-k8 in pvops Dom0 doesn't work any longer with Xen 4.0 > -------------------------------------------------------------- > > I found this in the logs, not idea currently what Xen 3.4.1 with pvops > or Xen 4.0 with 2.6.18 kernel would say. > > data kernel: [ 9.030558] powernow-k8: Found 1 AMD Athlon(tm) Dual > Core Processor 4050e processors (2 cpu cores) (version 2.20.00) > data kernel: [ 9.030955] [Firmware Bug]: powernow-k8: No compatible > ACPI _PSS objects found. > data kernel: [ 9.030957] [Firmware Bug]: powernow-k8: Try again > with latest BIOS. > I think xen.git xen/stable-2.6.32.x is still missing the acpi powermanagement patches.. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Thu, 8 Apr 2010 16:46:52 -0400 Message-ID: <20100408204652.GA622@phenom.dumpdata.com> References: <4BBE27CA.5090607@goirand.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers Cc: jeremy , xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Apr 08, 2010 at 09:46:58PM +0200, Carsten Schiers wrote: > OK, I am still a bit fuzzy as I had to learn how to git and configure > kernels, and I am still unsure whether I did everything > right. Nevertheless, and even when I cannot provide a lot of details, I > would like to inform you about some anomalies. > > Currently, I run Xen 3.4.1 and 2.6.18.8 kernels, 64 Bit Dom0 and some 32 > Bit and 64 Bit DomUs on a Gigabyte M56S-S3 / AMD 4050e > with cpufreq on powernow-k8 in cpufreq=dom0-kernel mode. I make use of > PCI Passthrough for DVB-C cards and onboard NIC, as well > as for USB controller. > > > > Compile problem on xen/stable-2.6.32 > ------------------------------------ > > I compiled 2.6.32.10-pvops for DomU only mode, resulting in compile > error very similar to > > > http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00925.html > > I get a "static declaration of 'xen_register_gsi' follows a non-static > declaration, because I have set CONFIG_XEN_PCI_MSI and > CONFIG_PCI_XEN, but not CONFIG_XEN_DOM0_PCI. It will disappear when > compiling a DOM0 kernel. > Can you do a copy-n-paste of your compile problem, please? > > > PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > working on xen/stable-2.6.32 on Xen 3.4.1 > ------------------------------------------------------------------------ > --------------------------------------- > > It will allow passthrough of all mentioned devices except one of the PCI > controllers. It will not be detected. Using > xm pci-attach will produce an error: > > troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > available because of BAR 0 [0xfc104000-0xfc104fff] collisions How much memory did you assign to the guest? If it is below 4GB, say 2GB did you see these errors? > nVidia forcedeth, working on pvops/Xen 3.4.1, not working on pvops/Xen > 4.0 > ------------------------------------------------------------------------ > -- > > The whole experiment was done because when I use Xen 4.0 with my > 2.6.18.8 kernels, I cannot use the onboard NIC any longer. The > driver forcedeth will report an error. So, as using the pvops DomU on > Xen 3.4.1 worked, I tried to also use a pvops Dom0 underneath So.. DomU and Dom0 with the same kernel works? > Xen 4.0, but the problem seems to be related to the Xen 4.0, which is > killing forcedeth MAC address detection. By the way: MSI has > never worked for me on that NIC. So I had pci=nomsi on kernel. > > not working example (MAC is random): > > troi kernel: [ 4.335591] forcedeth: Reverse Engineered nForce > ethernet driver. Version 0.64. > troi kernel: [ 4.335811] forcedeth 0000:00:00.0: enabling device > (0000 -> 0003) > troi kernel: [ 4.335942] forcedeth 0000:00:00.0: Xen PCI enabling > IRQ: 23 > troi kernel: [ 4.336016] forcedeth 0000:00:00.0: setting latency > timer to 64 > troi kernel: [ 4.336271] forcedeth 0000:00:00.0: Invalid Mac > address detected: 00:00:00:00:00:00 > troi kernel: [ 4.336295] forcedeth 0000:00:00.0: Please complain to > your hardware vendor. Switching to a random MAC. > troi kernel: [ 4.860537] forcedeth 0000:00:00.0: ifname eth0, PHY > OUI 0x732 @ 1, addr 5e:1a:09:69:77:5d > troi kernel: [ 4.860593] forcedeth 0000:00:00.0: highdma pwrctl > mgmt gbit lnktim msi desc-v3 > > working example (real MAC, note different IRQ): > > troi kernel: [ 1.133102] forcedeth: Reverse Engineered nForce > ethernet driver. Version 0.64. > troi kernel: [ 1.133376] forcedeth 0000:00:01.0: enabling device > (0000 -> 0003) > troi kernel: [ 1.133463] forcedeth 0000:00:01.0: Xen PCI enabling > IRQ: 19 > troi kernel: [ 1.652048] forcedeth 0000:00:01.0: ifname eth0, PHY > OUI 0x732 @ 1, addr 00:1d:7d:e8:97:7b > troi kernel: [ 1.652139] forcedeth 0000:00:01.0: highdma pwrctl > mgmt gbit lnktim msi desc-v3 I got lost in your description. The failing case happens when your Dom0 is 2.6.18 or the 2.6.31 (or 2.6.32?) And is the DomU pv-ops or 2.6.18? From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Vincent, Pradeep" Subject: Re: Xen 4.1 Feature Request List Date: Fri, 9 Apr 2010 19:09:43 -0700 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0977564272==" Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Content-Language: en List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector , Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============0977564272== Content-Language: en Content-Type: multipart/alternative; boundary="_000_C7E52BF71506Fpradeepvamazoncom_" --_000_C7E52BF71506Fpradeepvamazoncom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Multi-queue functionality in netfront/netbk drivers would be very useful in= improving aggregate network throughput. This is complementary to leveragin= g VMQ functionality via Netchannel2. For Dom-0 transmit queue logic, a simple mechanism to map physical NIC's re= ceive queues to Vif's transmit queues and vice-versa would also be very use= ful and will help Dom-0 leverage NIC's hardware based hashing functionality= such as RSS and guest kernel's transmit queue functionality for end-to-end= network throughput enhancement. Please let me know if you have any questions. Thanks, - Pradeep Vincent On 4/6/10 10:41 AM, "Stephen Spector" wrote: Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (s= hhhh, don't tell anyone) and I wanted to get submissions underway for Xen 4= .1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.co= m/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. = Feel free to add your ideas or send me your features and I will update the = wiki. I also plan to update the Xen.org roadmap page at http://www.xen.org/= products/xen_roadmap.html to be a list of 4.1 features tomorrow, after Xen = 4.0 is announced. Thanks. Stephen Spector Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org http://blog.xen.org | @xen_com_mgr --_000_C7E52BF71506Fpradeepvamazoncom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [Xen-devel] Xen 4.1 Feature Request List Multi-queue functionality in netfront/netbk drivers = would be very useful in improving aggregate network throughput. This is com= plementary to leveraging VMQ functionality via Netchannel2.

For Dom-0 transmit queue logic, a simple mechanism to map physical NIC̵= 7;s receive queues to Vif’s transmit queues and vice-versa would also= be very useful and will help Dom-0 leverage NIC’s hardware based has= hing functionality such as RSS and guest kernel’s transmit queue func= tionality for end-to-end network throughput enhancement.

Please let me know if you have any questions.

Thanks,

- Pradeep Vincent


On 4/6/10 10:41 AM, "Stephen Spector" <stephen.spector@citrix.= com> wrote:

Xen Community:
 
As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (s= hhhh, don’t tell anyone) and I wanted to get submissions underway for= Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/X= enRoadMap) with a new section for Xen 4.1 features to be added. Feel fr= ee to add your ideas or send me your features and I will update the wiki. I= also plan to update the Xen.org roadmap page at http://www.xen.org/products/xen_roadmap.html= to be a list of 4.1 features tomorrow, after Xen 4.0 is announced.  
Thanks.
 
Stephen Spector
Xen.org Community Manager
T: (772) 621-5062 | M: (954) 854-4257
stephen.spector@xen.org
http://blog.xen.org | @xen_com_mgr
 

--_000_C7E52BF71506Fpradeepvamazoncom_-- --===============0977564272== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0977564272==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carsten Schiers" Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Sat, 10 Apr 2010 11:26:53 +0200 Message-ID: References: <20100408201206.GF1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100408201206.GF1878@reaktio.net> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: pasik Cc: jeremy , xen-devel , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org Hi folks, some progress: >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 >> working on xen/stable-2.6.32 on Xen 3.4.1 >>=20 ------------------------------------------------------------------------ >> --------------------------------------- >>=20 >> It will allow passthrough of all mentioned devices except one of the=20 PCI=20 >> controllers. It will not be detected. Using=20 >> xm pci-attach will produce an error: >>=20 >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >>=20 >> I first tried only with the 2nd function (or whatever it is called),=20 but=20 >> as you see, we have the same error with both put into=20 >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 the guest" thing.. maybe it helps?=20 Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 works now with pvops 2.6.32.10 DomU kernel!!!=20 Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one=20 PCI device, so that hectic persons like me see better that a) it's without parenthesis and b) a comma separated=20 list ;o). BR, Carsten. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Tramnitz Subject: Re: Xen 4.1 Feature Request List Date: Sat, 10 Apr 2010 18:07:09 +0200 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> <28177904.post@talk.nabble.com> <4BBE12B1.7020706@goop.org> <4BBE27CA.5090607@goirand.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BBE27CA.5090607@goirand.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 08.04.2010 21:00, Thomas Goirand wrote: > What: > ==== > It'd be great to be able to do something like: > > 'exportpath:/var/mypath/myvps1,/,rw' > > so that the folder /var/mypath/myvps1 of a dom0 would be somehow > exported to a domU as /. Both the domU and dom0 would have read/write > access to it. Thats already work in progress in qemu for "paravirtual file system passthrough" which is what you request I guess. Best regards, Christian From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carsten Schiers" Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Sun, 11 Apr 2010 16:32:30 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel Cc: jeremy , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org Hi, I am sorry to say that I mixed something. What does work now is=20 2.6.31.13 kernel. The error messages are gone now for 2.6.32.11, but it is still not functioning.=20 So, with the 2.6.32.11 kernel, it will not recognize the same USB=20 controller that is recognized=20 by 2.6.31.13.=20 When booting: [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 [ 0.325746] alloc irq_desc for 503 on node 0 [ 0.325753] alloc kstat_irqs on node 0 When I detach and attach from Dom0, it will log in the DomU: [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 [ 202.848550] pcifront pci-0: backend going away! [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses [ 202.903310] pcifront pci-0: 22 freeing event channel 9 [ 224.234600] pcifront pci-0: Installing PCI frontend [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 In Dom0 we have: ACPI: PCI interrupt for device 0000:00:02.1 disabled pciback: vpci: 0000:00:02.1: assign to virtual slot 0 For reference, the log entries when I detach/attach the device in=20 2.6.31.13: [ 47.250686] usb usb1: USB disconnect, address 1 [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 [ 47.938006] pcifront pci-0: backend going away! [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change=20 state on the privileged domain. [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change=20 state on the privileged domain. [ 47.957636] pcifront pci-0: 22 freeing event channel 9 [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change=20 state on the privileged domain. [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change=20 state on the privileged domain. [ 58.868584] pcifront pci-0: Installing PCI frontend [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002) [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned=20 bus number 1 [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 [ 59.497182] usb usb1: New USB device found, idVendor=3D1d6b,=20 idProduct=3D0002 [ 59.497194] usb usb1: New USB device strings: Mfr=3D3, Product=3D2,=20 SerialNumber=3D1 [ 59.497207] usb usb1: Product: EHCI Host Controller [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686=20 ehci_hcd [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 [ 59.497363] usb usb1: configuration #1 chosen from 1 choice [ 59.497447] hub 1-0:1.0: USB hub found [ 59.497643] hub 1-0:1.0: 10 ports detected Relevant XEN config entries in 2.6.32.11: CONFIG_XEN=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D8 CONFIG_XEN_SAVE_RESTORE=3Dy # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=3Dy CONFIG_MICROCODE_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_DOM0_PCI=3Dy CONFIG_XEN_PCI_PASSTHROUGH=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_NETXEN_NIC=3Dm CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_KBDDEV_FRONTEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_XEN_FBDEV_FRONTEND=3Dy CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_TAP=3Dy CONFIG_XEN_BLKBACK_PAGEMAP=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_S3=3Dy BR, Carsten. -----Urspr=FCngliche Nachricht----- Von: Carsten Schiers=20 Gesendet: Samstag, 10. April 2010 11:27 An: 'Pasi K=E4rkk=E4inen' Cc: 'xen-devel'; 'jeremy'; 'konrad.wilk' Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /=20 2.6.32 pvops kernels Hi folks, some progress: >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 >> working on xen/stable-2.6.32 on Xen 3.4.1 >>=20 ------------------------------------------------------------------------ >> --------------------------------------- >>=20 >> It will allow passthrough of all mentioned devices except one of the=20 PCI=20 >> controllers. It will not be detected. Using=20 >> xm pci-attach will produce an error: >>=20 >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >>=20 >> I first tried only with the 2nd function (or whatever it is called),=20 but=20 >> as you see, we have the same error with both put into=20 >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 the guest" thing.. maybe it helps?=20 Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 works now with pvops 2.6.32.10 DomU kernel!!!=20 Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one=20 PCI device, so that hectic persons like me see better that a) it's without parenthesis and b) a comma separated=20 list ;o). BR, Carsten. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carsten Schiers" Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Sun, 11 Apr 2010 16:45:17 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel Cc: jeremy , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org Two additional infos: here lspci of the two USB controllers. The 00:02.0=20 is passed into another DomU. I=20 should mention that I think the 00:02.0 is going down in case I pass=20 00:02.1 into the 2.6.32 domain, but not if I pass it into the 2.6.31 domain. Find what the other DomU says=20 below. 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)=20 (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-=20 ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort-=20 SERR- TAbort-=20 SERR- 0002) [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned=20 bus number 1 [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 [ 59.497182] usb usb1: New USB device found, idVendor=3D1d6b,=20 idProduct=3D0002 [ 59.497194] usb usb1: New USB device strings: Mfr=3D3, Product=3D2,=20 SerialNumber=3D1 [ 59.497207] usb usb1: Product: EHCI Host Controller [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686=20 ehci_hcd [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 [ 59.497363] usb usb1: configuration #1 chosen from 1 choice [ 59.497447] hub 1-0:1.0: USB hub found [ 59.497643] hub 1-0:1.0: 10 ports detected Relevant XEN config entries in 2.6.32.11: CONFIG_XEN=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D8 CONFIG_XEN_SAVE_RESTORE=3Dy # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=3Dy CONFIG_MICROCODE_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_DOM0_PCI=3Dy CONFIG_XEN_PCI_PASSTHROUGH=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_NETXEN_NIC=3Dm CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_KBDDEV_FRONTEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_XEN_FBDEV_FRONTEND=3Dy CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_TAP=3Dy CONFIG_XEN_BLKBACK_PAGEMAP=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_S3=3Dy BR, Carsten. -----Urspr=FCngliche Nachricht----- Von: Carsten Schiers=20 Gesendet: Samstag, 10. April 2010 11:27 An: 'Pasi K=E4rkk=E4inen' Cc: 'xen-devel'; 'jeremy'; 'konrad.wilk' Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /=20 2.6.32 pvops kernels Hi folks, some progress: >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 >> working on xen/stable-2.6.32 on Xen 3.4.1 >>=20 ------------------------------------------------------------------------ >> --------------------------------------- >>=20 >> It will allow passthrough of all mentioned devices except one of the=20 PCI=20 >> controllers. It will not be detected. Using=20 >> xm pci-attach will produce an error: >>=20 >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >>=20 >> I first tried only with the 2nd function (or whatever it is called),=20 but=20 >> as you see, we have the same error with both put into=20 >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 the guest" thing.. maybe it helps?=20 Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 works now with pvops 2.6.32.10 DomU kernel!!!=20 Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one=20 PCI device, so that hectic persons like me see better that a) it's without parenthesis and b) a comma separated=20 list ;o). BR, Carsten. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Mon, 12 Apr 2010 10:59:29 +0300 Message-ID: <20100412075929.GD1878@reaktio.net> References: <20100408201206.GF1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers Cc: jeremy , xen-devel , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org On Sat, Apr 10, 2010 at 11:26:53AM +0200, Carsten Schiers wrote: > Hi folks, some progress: > > >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > > >> working on xen/stable-2.6.32 on Xen 3.4.1 > >> > ------------------------------------------------------------------------ > >> --------------------------------------- > >> > >> It will allow passthrough of all mentioned devices except one of the > PCI > >> controllers. It will not be detected. Using > >> xm pci-attach will produce an error: > >> > >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions > >> > >> I first tried only with the 2nd function (or whatever it is called), > but > >> as you see, we have the same error with both put into > >> the DomU. > >> > > > >Have you seen this wiki page?: > >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start > the guest" thing.. maybe it helps? > > Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It > works now with pvops 2.6.32.10 DomU kernel!!! > > Thanks Pasi!!! > > Eventually, you may put on the Wiki Page an example with more than one > PCI device, so that hectic persons like > me see better that a) it's without parenthesis and b) a comma separated > list ;o). > Actually what's missing from the wiki? :) It already has examples for multiple devices.. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Schiers Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Mon, 12 Apr 2010 15:01:33 +0200 Message-ID: <11672852.21271077293524.JavaMail.root@uhura> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel Cc: jeremy , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org Yet another note: the kernel messages that break 00:02.0 come up when I u= se 2.6.31 kernel, that means, if it is passing through the 00:02.1 into the pvops DomU, it w= ill break 00:02.0. Please note that this will work with 2.6.18.8 BR, Carsten. ----- Originalnachricht ----- Von: Carsten Schiers Gesendet: Son, 11.4.2010 16:45 An: xen-devel Cc: jeremy ; konrad.wilk Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.= 6.32 pvops kernels Two additional infos: here lspci of the two USB controllers. The 00:02.0 i= s passed into another DomU. I=20 should mention that I think the 00:02.0 is going down in case I pass 00:0= 2.1 into the 2.6.32 domain, but not if I pass it into the 2.6.31 domain. Find what the other DomU says be= low. 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (= prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParEr= r- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort- <= TAbort- SERR- TAbort- <= TAbort- SERR- 0002) [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned=20 bus number 1 [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 [ 59.497182] usb usb1: New USB device found, idVendor=3D1d6b,=20 idProduct=3D0002 [ 59.497194] usb usb1: New USB device strings: Mfr=3D3, Product=3D2,=20 SerialNumber=3D1 [ 59.497207] usb usb1: Product: EHCI Host Controller [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686=20 ehci_hcd [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 [ 59.497363] usb usb1: configuration #1 chosen from 1 choice [ 59.497447] hub 1-0:1.0: USB hub found [ 59.497643] hub 1-0:1.0: 10 ports detected Relevant XEN config entries in 2.6.32.11: CONFIG_XEN=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D8 CONFIG_XEN_SAVE_RESTORE=3Dy # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=3Dy CONFIG_MICROCODE_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_DOM0_PCI=3Dy CONFIG_XEN_PCI_PASSTHROUGH=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_NETXEN_NIC=3Dm CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_KBDDEV_FRONTEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_XEN_FBDEV_FRONTEND=3Dy CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_TAP=3Dy CONFIG_XEN_BLKBACK_PAGEMAP=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_S3=3Dy BR, Carsten. -----Urspr=FCngliche Nachricht----- Von: Carsten Schiers=20 Gesendet: Samstag, 10. April 2010 11:27 An: 'Pasi K=E4rkk=E4inen' Cc: 'xen-devel'; 'jeremy'; 'konrad.wilk' Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /=20 2.6.32 pvops kernels Hi folks, some progress: >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 >> working on xen/stable-2.6.32 on Xen 3.4.1 >>=20 ------------------------------------------------------------------------ >> --------------------------------------- >>=20 >> It will allow passthrough of all mentioned devices except one of the=20 PCI=20 >> controllers. It will not be detected. Using=20 >> xm pci-attach will produce an error: >>=20 >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >>=20 >> I first tried only with the 2nd function (or whatever it is called),=20 but=20 >> as you see, we have the same error with both put into=20 >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 the guest" thing.. maybe it helps?=20 Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 works now with pvops 2.6.32.10 DomU kernel!!!=20 Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one=20 PCI device, so that hectic persons like me see better that a) it's without parenthesis and b) a comma separated=20 list ;o). BR, Carsten. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Schiers Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Tue, 13 Apr 2010 08:32:44 +0200 Message-ID: <21168790.101271140364006.JavaMail.root@uhura> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: jeremy , xen-devel , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org I thought so, too, but this doesn't work either. And: it does work in 2.6= =2E18, as I think it's not realy two devices. One is OHCI, the other EHCI. BR, Carsten. ----- Originalnachricht ----- Von: Pasi K=E4rkk=E4inen Gesendet: Mon, 12.4.2010 15:07 An: Carsten Schiers Cc: jeremy ; xen-devel ;= konrad.wilk Betreff: Re: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.= 6.32 pvops kernels On Mon, Apr 12, 2010 at 03:01:33PM +0200, Carsten Schiers wrote: > Yet another note: the kernel messages that break 00:02.0 come up when I= use 2.6.31 kernel, > that means, if it is passing through the 00:02.1 into the pvops DomU, i= t will break 00:02.0. >=20 > Please note that this will work with 2.6.18.8 >=20 Maybe both of these devices need to be passed through at the same time to= the same guest,=20 since they're part of the same device?=20 -- Pasi > BR, > Carsten. >=20 > ----- Originalnachricht ----- > Von: Carsten Schiers > Gesendet: Son, 11.4.2010 16:45 > An: xen-devel > Cc: jeremy ; konrad.wilk > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2= =2E6.32 pvops kernels >=20 > Two additional infos: here lspci of the two USB controllers. The 00:02.= 0 is passed into another DomU. I=20 > should mention that I think the 00:02.0 is going down in case I pass 00= :02.1 into the 2.6.32 domain, but > not if I pass it into the 2.6.31 domain. Find what the other DomU says b= elow. >=20 > 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3= ) (prog-if 10 [OHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- Par= Err- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort= - SERR- Latency: 0 (750ns min, 250ns max) > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=3D= 4K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA PME(D0+,D1= +,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME- > Kernel driver in use: pciback > Kernel modules: ohci-hcd >=20 > 00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3= ) (prog-if 20 [EHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- Par= Err- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort= - SERR- Interrupt: pin B routed to IRQ 20 > Region 0: Memory at c0201000 (32-bit, non-prefetchable) [disabl= ed] [size=3D256] > Capabilities: [44] Debug port: BAR=3D1 offset=3D0098 > Capabilities: [80] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA PME(D0+,D1= +,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME+ > Kernel driver in use: pciback > Kernel modules: ehci-hcd >=20 > Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3 > Apr 11 16:27:26 uhura kernel: kcapi: card 1 down. > Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003 unregiste= red > Apr 11 16:27:26 uhura kernel: fcusb: Driver 'fcusb' detached > Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using o= hci_hcd and address 4 > Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1 c= hoice > Apr 11 16:27:27 uhura kernel: fcusb: Driver 'fcusb' attached to stack. (= 152) > Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached > Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready. > Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4 > Apr 11 16:28:25 uhura kernel: kcapi: card 1 down. > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004 unregiste= red > Apr 11 16:28:25 uhura kernel: fcusb: Driver 'fcusb' detached > Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using o= hci_hcd and address 5 > Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1 c= hoice > Apr 11 16:28:25 uhura kernel: fcusb: Driver 'fcusb' attached to stack. (= 152) > Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached > Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready. >=20 > BR, > Carsten. >=20 >=20 > -----Urspr=FCngliche Nachricht----- > Von: Carsten Schiers=20 > Gesendet: Sonntag, 11. April 2010 16:33 > An: xen-devel > Cc: jeremy; konrad.wilk > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2= =2E6.32 pvops kernels >=20 > Hi, >=20 > I am sorry to say that I mixed something. What does work now is=20 > 2.6.31.13 kernel. The error > messages are gone now for 2.6.32.11, but it is still not functioning.=20 >=20 > So, with the 2.6.32.11 kernel, it will not recognize the same USB=20 > controller that is recognized=20 > by 2.6.31.13.=20 >=20 > When booting: >=20 > [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 0.325746] alloc irq_desc for 503 on node 0 > [ 0.325753] alloc kstat_irqs on node 0 >=20 > When I detach and attach from Dom0, it will log in the DomU: >=20 > [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 202.848550] pcifront pci-0: backend going away! > [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 202.903310] pcifront pci-0: 22 freeing event channel 9 > [ 224.234600] pcifront pci-0: Installing PCI frontend > [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 >=20 > In Dom0 we have: >=20 > ACPI: PCI interrupt for device 0000:00:02.1 disabled > pciback: vpci: 0000:00:02.1: assign to virtual slot 0 >=20 > For reference, the log entries when I detach/attach the device in=20 > 2.6.31.13: >=20 > [ 47.250686] usb usb1: USB disconnect, address 1 > [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered > [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 47.938006] pcifront pci-0: backend going away! > [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change=20 > state on the privileged domain. > [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change=20 > state on the privileged domain. > [ 47.957636] pcifront pci-0: 22 freeing event channel 9 > [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change=20 > state on the privileged domain. > [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change=20 > state on the privileged domain. > [ 58.868584] pcifront pci-0: Installing PCI frontend > [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002) > [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 > [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 > [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller > [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned=20 > bus number 1 > [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM > [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 > [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 > [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 > [ 59.497182] usb usb1: New USB device found, idVendor=3D1d6b,=20 > idProduct=3D0002 > [ 59.497194] usb usb1: New USB device strings: Mfr=3D3, Product=3D2,=20 > SerialNumber=3D1 > [ 59.497207] usb usb1: Product: EHCI Host Controller > [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686=20 > ehci_hcd > [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 > [ 59.497363] usb usb1: configuration #1 chosen from 1 choice > [ 59.497447] hub 1-0:1.0: USB hub found > [ 59.497643] hub 1-0:1.0: 10 ports detected >=20 > Relevant XEN config entries in 2.6.32.11: >=20 > CONFIG_XEN=3Dy > CONFIG_XEN_MAX_DOMAIN_MEMORY=3D8 > CONFIG_XEN_SAVE_RESTORE=3Dy > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_SWIOTLB_XEN=3Dy > CONFIG_MICROCODE_XEN=3Dy > CONFIG_XEN_DOM0=3Dy > CONFIG_XEN_PRIVILEGED_GUEST=3Dy > CONFIG_XEN_DOM0_PCI=3Dy > CONFIG_XEN_PCI_PASSTHROUGH=3Dy > CONFIG_PCI_XEN=3Dy > CONFIG_XEN_PCIDEV_FRONTEND=3Dy > CONFIG_XEN_BLKDEV_FRONTEND=3Dy > CONFIG_NETXEN_NIC=3Dm > CONFIG_XEN_NETDEV_FRONTEND=3Dy > CONFIG_XEN_KBDDEV_FRONTEND=3Dy > CONFIG_HVC_XEN=3Dy > CONFIG_XEN_FBDEV_FRONTEND=3Dy > CONFIG_XEN_BALLOON=3Dy > CONFIG_XEN_SCRUB_PAGES=3Dy > CONFIG_XEN_DEV_EVTCHN=3Dy > CONFIG_XEN_BACKEND=3Dy > CONFIG_XEN_NETDEV_BACKEND=3Dy > CONFIG_XEN_BLKDEV_BACKEND=3Dy > CONFIG_XEN_BLKDEV_TAP=3Dy > CONFIG_XEN_BLKBACK_PAGEMAP=3Dy > CONFIG_XEN_PCIDEV_BACKEND=3Dy > CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set > CONFIG_XENFS=3Dy > CONFIG_XEN_COMPAT_XENFS=3Dy > CONFIG_XEN_SYS_HYPERVISOR=3Dy > CONFIG_XEN_XENBUS_FRONTEND=3Dy > # CONFIG_XEN_GNTDEV is not set > CONFIG_XEN_S3=3Dy >=20 > BR, > Carsten. >=20 > -----Urspr=FCngliche Nachricht----- > Von: Carsten Schiers=20 > Gesendet: Samstag, 10. April 2010 11:27 > An: 'Pasi K=E4rkk=E4inen' > Cc: 'xen-devel'; 'jeremy'; 'konrad.wilk' > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /=20 > 2.6.32 pvops kernels >=20 > Hi folks, some progress: >=20 > >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, no= t=20 >=20 > >> working on xen/stable-2.6.32 on Xen 3.4.1 > >>=20 > -----------------------------------------------------------------------= - > >> --------------------------------------- > >>=20 > >> It will allow passthrough of all mentioned devices except one of the= =20 > PCI=20 > >> controllers. It will not be detected. Using=20 > >> xm pci-attach will produce an error: > >>=20 > >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 > >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 > >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions > >>=20 > >> I first tried only with the 2nd function (or whatever it is called),= =20 > but=20 > >> as you see, we have the same error with both put into=20 > >> the DomU. > >> > > > >Have you seen this wiki page?: > >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 > the guest" thing.. maybe it helps?=20 >=20 > Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 > works now with pvops 2.6.32.10 DomU kernel!!!=20 >=20 > Thanks Pasi!!! >=20 > Eventually, you may put on the Wiki Page an example with more than one=20 > PCI device, so that hectic persons like > me see better that a) it's without parenthesis and b) a comma separated= =20 > list ;o). >=20 > BR, > Carsten. >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: Xen 4.1 Feature Request List Date: Tue, 20 Apr 2010 12:32:11 +0200 Message-ID: <4BCD82AB.9060706@ts.fujitsu.com> References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector Cc: Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org Stephen Spector wrote: > Xen Community: >=20 > =20 >=20 > As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorro= w > (shhhh, don=92t tell anyone) and I wanted to get submissions underway f= or > Xen 4.1 features. I have updated the Roadmap Wiki page > (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for > Xen 4.1 features to be added. Feel free to add your ideas or send me > your features and I will update the wiki. I also plan to update the > Xen.org roadmap page at http://www.xen.org/products/xen_roadmap.html to > be a list of 4.1 features tomorrow, after Xen 4.0 is announced. Support of cpupools in Xen (Patches already sent). Juergen --=20 Juergen Gross Principal Developer Operating Systems TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujits= u.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.= html