aborted vms

12 views
Skip to first unread message

P. Oscar Boykin

unread,
Jan 10, 2011, 11:38:01 AM1/10/11
to acisp2...@googlegroups.com
David,

It's not uncommon for me to return to my VirtualBox machine that
started many (1200) jobs (each of which requires about 1-2MB data
transfer on start, very little on finish), and find the machine has
aborted and is no longer running.

I guess this could be a virtualbox bug, it could be a linux bug, it
could be a severe out-of-memory condition related to IPOP transferring
too many files, I just don't know.

What do you need from me to diagnose the problem?
--
P. Oscar Boykin                            http://boykin.acis.ufl.edu
Assistant Professor, Department of Electrical and Computer Engineering
University of Florida

David Isaac Wolinsky

unread,
Jan 10, 2011, 2:17:33 PM1/10/11
to acisp2...@googlegroups.com
The easiest thing to do is to skim through your VBox logs and see if
there are any weird messages towards the tail of the log. Feel free to
post it here, I run Windows on VBox and it never crashes, so maybe,
there's something here. (Logs are available from Machine -> Show Log on
the main VBox window.) From my prespective, this is clearly a VBox bug,
but perhaps something in your setup whether it is GA or an older version
is triggering the issue. Which version of VBox are you running?

David

(Sorry I had written this earlier and thought I had sent it but it was
sitting in my drafts)

P. Oscar Boykin

unread,
Jan 10, 2011, 2:20:43 PM1/10/11
to acisp2...@googlegroups.com
Interestingly the last 30-40 lines in the most recent logs are:

NAT: can't alloc memory for outgoing buffer

Perhaps this is related to the amount of data transfer I'm doing.

> --
> You received this message because you are subscribed to the Google Groups
> "acis.p2p.users" group.
> To post to this group, send email to acisp2...@googlegroups.com.
> To unsubscribe from this group, send email to
> acisp2pusers...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/acisp2pusers?hl=en.

P. Oscar Boykin

unread,
Jan 10, 2011, 2:22:06 PM1/10/11
to acisp2...@googlegroups.com
VirtualBox 3.2.8 OSE (the version packaged in Ubuntu 10.10, I believe).

David Isaac Wolinsky

unread,
Jan 10, 2011, 2:23:31 PM1/10/11
to acisp2...@googlegroups.com
Is the host running out of memory?

P. Oscar Boykin

unread,
Jan 10, 2011, 2:24:54 PM1/10/11
to acisp2...@googlegroups.com
Hard to say, because I'm not at the machine when the failure occurs
and everything is (usually) okay when I return.

On a few occasions, I did find the machine in the off state, but I was
not sure how that happened.

--

David Isaac Wolinsky

unread,
Jan 10, 2011, 2:30:21 PM1/10/11
to acisp2...@googlegroups.com
Hmm, maybe the easiest thing to do is verify that the error message is
accurate. Want to run the machine in bridged mode?

David

P. Oscar Boykin

unread,
Jan 10, 2011, 2:53:37 PM1/10/11
to acisp2...@googlegroups.com
After the next crash I'll do that.

--

David Isaac Wolinsky

unread,
Jan 10, 2011, 11:42:50 AM1/10/11
to acisp2...@googlegroups.com
The easiest thing to do is to skim through your VBox logs and see if
there are any weird messages towards the tail of the log. Feel free to
post it here, I run Windows on VBox and it never crashes, so maybe,
there's something here. (Logs are available from Machine -> Show Log on
the main VBox window.) From my prespective, this is clearly a VBox bug,
but perhaps something in your setup whether it is GA or an older version
is triggering the issue. Which version of VBox are you running?

David

Reply all
Reply to author
Forward
0 new messages