Using a VM with OE

Hi. Any known issues in developing using OE within a VMWare player
running Ubuntu?

Thanks, Bill

Are you facing problems? Normally, if you are getting the cross-
compiler working properly on your VM, you should not have problems.

BR, Amine

Hi Bill,

As far as I'm aware there should be no real problems:
More info can be found at:
http://code.google.com/p/beagleboard/wiki/HowToSetupLinuxInWindows

Make sure to assign at least 1.5-2GB of memory to your virtual machine,
since you might else end up in a situation where OE/GCC fails due to running
out of memory during compilation of i.e. firefox...

I'm myself using coLinux under Windows, but I'm sure WMPlayer should work at
least as well..

Best regards - Happy New Year to all
  Søren

I develop using OE running under Ubuntu (32-bit) which runs as a virtual
machine within VMWare Workstation under Windows XP. I allocated only 1GB of
ram to the VM and still everything built just fine. I was following the
cookbook instructions from here:
http://elinux.org/BeagleBoardAndOpenEmbeddedGit.

I started out with 1 GB of RAM and zero Swap Space, which caused me trouble
until I increased the RAM amount. I think the limit is just around 1GB, and
it might be, that I had more stuff running in the background
(SSH/Samba/X11/Apache/etc) causing me to reach the limit and not you,
although we both allocated 1GB for the virtual machine...

My concern was mainly to emphasize that he should allocate as much memory as
possible and at very least >=1GB in order to make sure not to run into
memory-related/caused-problems :slight_smile:

Best regards
  Søren

-----Oprindelig meddelelse-----

Quoting Søren Steen Christensen <sorenschristensen@stofanet.dk>:

My concern was mainly to emphasize that he should allocate as much memory as
possible and at very least >=1GB in order to make sure not to run into

I've been running a VirtualPC with Debian (console mode only, no X) The machine has 1GB; I don't recall off hand if the VM gets 256 or 512. I've tried increasing it during builds and it wasn't clear that there was a measurable difference. However, I'm building a console image plus some extras like mplayer and directfb, so I'm not dealing with the larger applications like Firefox.

- Justin Love

Hi Justin,

I have only seen the problem with firefox and one other (huge) application
which I unfortunately currently can't remember what was... All other stuff I
have tried worked fine with 512MB.

I mainly wanted to warn about, that running out of memory can give strange
results, which might be difficult to track/hunt/understand, since in my
attempt compiling on its own (not using OE) worked, while compiling the same
source using OE failed. I guess I was just on the edge of memory... :slight_smile:

Best regards
  Søren

Quoting Søren Steen Christensen <sorenschristensen@stofanet.dk>:

My concern was mainly to emphasize that he should allocate as much memory

as

possible and at very least >=1GB in order to make sure not to run into

I've been running a VirtualPC with Debian (console mode only, no X)
The machine has 1GB; I don't recall off hand if the VM gets 256 or
512. I've tried increasing it during builds and it wasn't clear that
there was a measurable difference. However, I'm building a console
image plus some extras like mplayer and directfb, so I'm not dealing
with the larger applications like Firefox.

- Justin Love

No problems. I seemed to be able to build without errors, but was not
sure if using the VM is a viable, permanent development platform.

Btw, if I ran out of memory wouldn't it show as an error in the
console messages during the build?

Thank you all for the excellent feedback.
Bill

Bill:
Btw, if I ran out of memory wouldn't it show as an error in the
console messages during the build?

I had once, where my coLinux instance crashed totally, and once where OE/GCC
(I can't remember) failed with some kind of strange error, which didn't
point in the direction of an "out of memory"-problem...
  Søren

I just checked on a Ubuntu JeOS VM I built just for open embedded and
it was set to 320MB allocated for the VM. I've built base and console
in it so far without any problems. That's bummer, I had just started
'git pull' to see how an update would do but instead of Ctl-Alt to
escape the VM, I hit Ctl-C and no 'git pull' fails with "fatal: the
remote end hung up unexpectedly". I remember this happening before
and git clone..... was what it took to get working again.

FYI, here's the documentation I have on setting up the Ubuntu JeOS
v8.04.1 VM for openembedded:

sudo apt-get install ccache sed wget cvs subversion git-core coreutils
unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk help2man
diffstat gtk-doc-tools file
sudo apt-get install python-psyco
ln -s /bin/sh
sudo dpkg-reconfigure dash
#and select no
ln -s /bin/sh

echo "vm.vdso_enabled = 0" >> /tmp/vmtmp
echo "vm.mmap_min_addr = 0" > /tmp/vmtmp
sudo vi /tmp/vmtmp /etc/sysctl.conf
sudo sysctl -p