RE: [Xen-users] Random dom0 lock up

["Ian Tobin" <itobin@xxxxxxxxxxxxx>]

Ok great, ill give it a shot.

Thanks again

Ian


-----Original Message-----
From: mdlabriola@xxxxxxxxx [mailto:mdlabriola@xxxxxxxxx] 
Sent: 26 May 2010 02:16
To: Ian Tobin; xen-users-bounces@xxxxxxxxxxxxxxxxxxx; 
xen-users@xxxxxxxxxxxxxxxxxxx; Pasi Kärkkäinen
Subject: Re: [Xen-users] Random dom0 lock up

Just use "mem=4095M" instead of "dom0_mem=4095M" in the xen.gz line.

-Mike



---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844

-----Original Message-----
From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
Date: Tue, 25 May 2010 22:46:23 
To: <mdlabriola@xxxxxxxxx>; <xen-users-bounces@xxxxxxxxxxxxxxxxxxx>; 
<xen-users@xxxxxxxxxxxxxxxxxxx>; Pasi Kärkkäinen<pasik@xxxxxx>
Subject: RE: [Xen-users] Random dom0 lock up

Hi,

Im not sure how else to limit it to 4g? In the kernel command line i have 


title           Xen 4.0 / Debian GNU/Linux, kernel 2.6.32.13
root            (hd0,0)
kernel          /xen.gz dom0_mem=4095M
module          /vmlinuz-2.6.32.13 root=/dev/md1 ro console=tty0
module          /initrd.img-2.6.32.13

when you say the whole hypervisor, where else are you setting the limit?

Thanks

Ian



-----Original Message-----
From: mdlabriola@xxxxxxxxx [mailto:mdlabriola@xxxxxxxxx] 
Sent: 25 May 2010 14:15
To: Ian Tobin; xen-users-bounces@xxxxxxxxxxxxxxxxxxx; 
xen-users@xxxxxxxxxxxxxxxxxxx; Pasi Kärkkäinen
Subject: Re: [Xen-users] Random dom0 lock up

I meant limit it to less than 4G.  And by "it" I mean the whole hypervisor, not 
just dom0.  Solved all my issues.

-Mike


---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844

-----Original Message-----
From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
Date: Tue, 25 May 2010 06:13:59 
To: <mdlabriola@xxxxxxxxx>; <xen-users-bounces@xxxxxxxxxxxxxxxxxxx>; 
<xen-users@xxxxxxxxxxxxxxxxxxx>; Pasi Kärkkäinen<pasik@xxxxxx>
Subject: RE: [Xen-users] Random dom0 lock up

Hi,

Its 32bit.  Currently i have it set to 512mb.  So setting it to 4095 might 
help? I will try that when i get back to the office.

On another note is there a way to capture the errors without using a serial 
console? The reason i ask is we are not allowed physical access to our kit in 
the data center which obviously complicates things somewhat.

Thanks

Ian



-----Original Message-----
From: mdlabriola@xxxxxxxxx [mailto:mdlabriola@xxxxxxxxx] 
Sent: 25 May 2010 00:49
To: Ian Tobin; xen-users-bounces@xxxxxxxxxxxxxxxxxxx; 
xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Random dom0 lock up

32 or 64 bit?  One of my newer quad-core boxes had a ton of stability problems 
running 32bit with 4G of RAM.  Telling the hypervisor to only use 4095M made 
things work much better.  Try adding "mem=4095M" to the hypervisor command line.

-Mike


---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844

-----Original Message-----
From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
Date: Mon, 24 May 2010 19:25:11 
To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Random dom0 lock up

_______________________________________________
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


_______________________________________________
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