WARNING - OLD ARCHIVES

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

xen-devel

RE: [Xen-devel] [RFC] New shadow paging code

To: "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [RFC] New shadow paging code
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Thu, 17 Aug 2006 03:00:55 -0400
Delivery-date: Thu, 17 Aug 2006 00:02:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D3051905AB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbBH8tmiOpo9EQ7QaOXfuBnzNSuVgAl4wpAAACQSlAAA4ZhMA==
Thread-topic: [Xen-devel] [RFC] New shadow paging code
Ooops!!! I realized why I could not bring up more than 8 domains. I was
using loopback devices for the winxp disks and max_loop was by default
set to 8. So once I upped the max_loop number I was able to bring up
more domains.

What I did was, I brought up 20 WinXP x86_32 domains without launching
their respective vncviewers. Once all the domains were up I launched 10
viewers and this caused qemu-dm of the 10 launched domains to hit 40-50%
CPU. All the viewers were sluggish and no real work could be done.

Aravindh

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Puthiyaparambil, Aravindh
> Sent: Thursday, August 17, 2006 12:59 AM
> To: Tim Deegan; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] [RFC] New shadow paging code
> 
> I also found that if I don't bring up vncviewer, qemu-dm does not take
> up 50% CPU. But I still fail trying to bring up the 9th domain with
the
> following error:
> Error: Device 768 (vbd) could not be connected. Backend device not
> found.
> 
> Aravindh
> 
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Puthiyaparambil, Aravindh
> > Sent: Thursday, August 17, 2006 12:48 AM
> > To: Tim Deegan; xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-devel] [RFC] New shadow paging code
> >
> > Tim,
> >
> > I tried the patch on a 4-way x86_64 ES7000 32GB RAM with an x86_64
> > hypervisor.
> >
> > I found that I am still unable to bring up domains with pae=1. I
have
> > attached the error that I am seeing (hvm_pae.txt)
> >
> > I then tried bringing up as many x86_32 WinXP domains as possible.
The
> > qemu-dm process associated with each domain takes up 50% CPU. So I
am
> > unable to bring up more than 8 (2 * NR_CPUS) domains.
> >
> > Let me know if you need any more info.
> > Cheers,
> > Aravindh
> >
> > > -----Original Message-----
> > > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> > > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tim Deegan
> > > Sent: Wednesday, August 16, 2006 6:35 AM
> > > To: xen-devel@xxxxxxxxxxxxxxxxxxx
> > > Subject: Re: [Xen-devel] [RFC] New shadow paging code
> > >
> > > A new version of the shadow2 patch is now available at
> > > http://www.cl.cam.ac.uk/~tjd21/shadow2.patch
> > > (md5: 3a094d3eebf328db887f495c022bf651)
> > > This patch applies to version 0e32095a7b46 of -unstable.
> > >
> > > It should fix the issues that have been seen with memory
allocation
> > and
> > > with 64-bit HVM guests.  SMP HVM guests may still have some
> problems.
> > >
> > > Cheers,
> > >
> > > Tim.
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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