VMware Cloud Community
andrewpalumbo
Contributor
Contributor
Jump to solution

CentOS 7 in VMWare Player 7 Bug report

Hello,

Not sure if this is the correct place to post this so please let me know if I'm in the wrong spot, but I've been hitting problems with VMWare Player 7 installing CentOS and Ubuntu:

I've had several problems with with anything CPU intensive while trying to setup a CentOS 7

workstation inside of VMWare Player 7.  This is a fresh KDE workstation install out of the box

with maven installed via # yum.  The system was fully updates via # yum update. 

This problem comes up each time I try to build Apache Spark 1.1.0 with maven.  However it seemed

to be happening with other applications including GNOME Desktop.  I've tried the MATE desktop as

well and still have the problem.  

Environment:

Host:

  VMWare Player 7.0.0 build-2305329

  Windows 7 Home Premium, 64-bit 6.1.7601, Service Pack 1

  4 core AMD64 CPU

  16GB RAM

Guest:

  CentOS-7.0-1406-x86_64 (KDE Desktop install)

  2 cores

  ~11GB RAM (have tried with different values)

  60 GB HDD

Any CPU intensive work causes this lockup.

Steps to reproduce exactly: 

1.  Install CentOS-7.0-1406

2.  $ sudo yum install maven

3.  $ sudo yum update

4.  Download Apache Spark 1.1.0 sources from http://spark.apache.org/downloads.html and unzip  

5.  $ cd spark-1.1.0

6.  $ export MAVEN_OPTS="-Xmx2g -XX:MaxPermSize=512M -XX:ReservedCodeCacheSize=512m"

7.  $ mvn -Pyarn -Phadoop-2.2 -Dhadoop.version=2.2.0 -DskipTests clean package

eventually the machine locks up and a hard reset is required.

I'm not sure if this is a CentOS issue, a Kernel issue or more likely a VMWare Player issue. 

sure if this is a CentOS issue, a Kernel issue or more likely a VMWare Player issue.

Attached is a Crash Report.

Thanks,

Andy Palumbo

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
andrewpalumbo
Contributor
Contributor
Jump to solution

Enabling "Virtualization Technologies" in the system bios fixed this problem

View solution in original post

0 Kudos
1 Reply
andrewpalumbo
Contributor
Contributor
Jump to solution

Enabling "Virtualization Technologies" in the system bios fixed this problem

0 Kudos