Re: [Xen-devel] process killed

[Brian Hays <brian.hays@xxxxxxxxx>]

Just wanted to give an update on this ... I upgraded to the latest
"stable" version and this now runs fine. The process still gets
mysteriously "killed" in the unstable version. I've noticed other
programs getting killed in the unstable version as well, such as
running mozilla during a vnc session, running asterisk CLI, openoffice
via vnc (these run fine in "stable"). ....guess that's why it's called
"unstable" :-) but I thought I'd report it just in case it's a sign of
a bigger problem in the new version.

Thanks,
Brian

On 4/28/05, Brian Hays <brian.hays@xxxxxxxxx> wrote:
> I ran it with strace (see attached file) the last line prints:
> "exit_group(137)                         = ?"
> 
> I'm running this on a test machine using the Java SDK 1.4.2_07 (I've
> also tried other versions with the same result) and the Xen distro
> from the Fedora Core 4 test2 repo.
> 
> Brian
> 
> On 4/28/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> > You could try running it with strace (i.e. "strace digichat") and see if
> > strace spits out any clues when it dies.
> >
> > Whose Java are you using?  What distro is this?
> >
> > Cheers,
> > Mark
> >
> > On Thursday 28 April 2005 15:34, Brian Hays wrote:
> > > Ian,
> > >
> > > No errors show up under 'dmesg' and gdb returns "not in executable 
> > > format".
> > >
> > > If you like I can provide you access via ssh to this domU for testing.
> > > I've seen a few other posts related to java problems ...my debugging
> > > skills in this area are probably lacking.
> > >
> > > Thanks,
> > > Brian
> > >
> > > On 4/28/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > > > > Yeah, Ive tried it with 64MB all the way up to 512MB of RAM
> > > > > allocated to the domU. I definitely think it's related to
> > > > > memory though...As soon as I start the DigiChat process you
> > > > > can see the memory spike full and it doesn't seem to use swap
> > > > > at all....about a second or two after starting it will just
> > > > > give the process ID and say "killed".
> > > >
> > > > Have you tried 'dmesg' to see if the OOM killer logs anything?
> > > > Also, try running the thing under gdb.
> > > > Ian
> > > >
> > > > > Thanks,
> > > > > Brian
> > > > >
> > > > > On 4/28/05, Chris Wedgwood <cw@xxxxxxxx> wrote:
> > > > > > On Wed, Apr 27, 2005 at 08:24:41PM -0400, Brian Hays wrote:
> > > > > > > I've come across a strange problem when installing a particular
> > > > > > > software package in a domU. I'm trying to install DigiChat
> > > > > > > (http://www.digichat.com/downloads.html) and the process is
> > > > > > > immediately killed.
> > > > > >
> > > > > > Killed how?  With what signal?
> > > > > >
> > > > > > My guess is OOM.  Add more memory to domU and see if that helps.
> > > > > >
> > > > > > > Is there anything about Java that Xen doesn't play nice
> > > > >
> > > > > with right
> > > > >
> > > > > > > now?
> > > > > >
> > > > > > My guess is that it uses lots of memory.
> > > > > >
> > > > > > Does the JVM use TLS a lot?  I'm guessing not if it works under UML.
> > > > > > Something else to check anyhow.
> > > > >
> > > > > _______________________________________________
> > > > > 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