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] Correct memory allocation for Dom0 ?

This is sort of a shot in the dark, but is it possible the Windows guests are sleeping?

They would be woken back up when you moved the mouse or touched the keyboard, right?

:-)

--
-- Tom Mornini, CTO
-- Engine Yard, Ruby on Rails Hosting
-- Reliability, Ease of Use, Scalability
-- (866) 518-YARD (9273)

On Mar 10, 2007, at 6:33 AM, Ian Tobin wrote:

Hi,

we are running Windows and Linux guests and are experiencing network disconnects from the Windows guests, if you connect to it via VNC the Windows guest comes back to life straight away.

We think it may be memory on the Dom0 which is currently set to 320MB Ram which is all used up, even when it was set to 256MB it was used up but hardly touched the swap file, same as now.

So does anyone know what the correct setting for Dom0 should be to make it stable running multiple Windows and Linux DomUs?

thanks

Ian

Tidyhosts UK - Server & Web Specialists
0871 910 6732

This email and its attachments are scanned by TidyHosts UK. All emails and attachments should also be scanned by the recipient. TidyHosts UK accept no responsibility for any damage caused by any virus attached to this email. This email is confidential and is intended only for the addressee(s). Information copied from it is prohibited unless clearly stated by TidyHosts UK. If you have received this email in error please reply to the sender.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


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

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