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-users

Re: [Xen-users] Memory consumption of xend on x86_64

Hi,

If I try to run 32bit hosts on a 64bit dom-0, will they run under HVM?

Also, How can I check whether the guests are running under PV or HVM? I use
virt-manager  it creates the virtual machines without the need to use xm.

Thanks-
Harsha

xen-users-bounces@xxxxxxxxxxxxxxxxxxx wrote on 07/30/2009 05:10:16 PM:

> Sreeharsha Totakura <sreeharsha.totakura@xxxxxxx>
> Sent by: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>
> 07/30/2009 05:10 PM
>
> To
>
> xen-users@xxxxxxxxxxxxxxxxxxx
>
> cc
>
> Subject
>
> [Xen-users] Memory consumption of xend on x86_64
>
>
> Hi,
>
> On one of our servers which has 6GB RAM (dom0 RAM: 3GB), the xend service
> is taking about 46% of the memory. Is this normal? We use xen on other
> servers (8GB, 6GB RAM) too and in them xend is taking about 3% of the
> memory.
>
> This particular server if of x86_64 architecture where as the rest are of
> i386. Is that the reason for xend taking so much RAM?
> Regards,
-
Harsha

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




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

<Prev in Thread] Current Thread [Next in Thread>