Error: The Virtualization capability of your processor is already in use????

[amaltemara]

Ever since I upgraded to 6.04, and now 6.5beta2 from 6.01, I cannot start my VMs. I

With Workstation 6.5beta2, I am getting this message:

"The virtualization capability of your processor is already in use. Disable any other running hypervisors before running VMware Workstation."

then: "Failed to initialize monitor device."

then: "Unable to change virtual machine power state: Cannot find a valid peer process to connect to."

With Workstation 6.04, I was getting someting like: "RunVM failed, operation not permitted", and: "Unable to change virtual machine power state: Cannot find a valid peer process to connect to."

OS is linux: Ubuntu 8.04.1 - Hardy something-or-other

As far as I know, I have no other virtualization products installed or running...

Anybody have any ideas????

TIA,

-Anthony

Here's a listing of my loaded modules...`lsmod | sort`

ac 6916 0

aes_i586 33536 0

agpgart 34760 2 nvidia,intel_agp

async_memcpy 3712 1 raid456

async_tx 9292 3 raid456,async_xor,async_memcpy

async_xor 4992 1 raid456

ata_generic 8324 0

ata_piix 19588 2

battery 14212 0

binfmt_misc 12808 1

bitblit 6784 1 fbcon

bluetooth 61156 2 rfcomm,l2cap

button 9232 0

cdrom 37408 1 sr_mod

container 5632 0

cpufreq_conservative 8712 0

cpufreq_ondemand 9740 0

cpufreq_powersave 2688 0

cpufreq_stats 7104 0

cpufreq_userspace 5284 0

dm_crypt 15364 0

dm_mod 62660 1 dm_crypt

dock 11280 0

ehci_hcd 37900 0

evdev 13056 4

ext2 73352 1

ext3 136712 2

fan 5636 0

fbcon 42912 0

floppy 59588 0

font 9472 1 fbcon

freq_table 5536 2 cpufreq_stats,cpufreq_ondemand

fuse 50708 1

hid 38784 1 usbhid

i2c_core 24832 1 nvidia

intel_agp 25492 0

iptable_filter 3840 0

ip_tables 14820 1 iptable_filter

iTCO_vendor_support 4868 1 iTCO_wdt

iTCO_wdt 13092 0

jbd 48404 1 ext3

joydev 13120 0

l2cap 25728 3 rfcomm

libata 159344 5 pata_acpi,pata_jmicron,ata_piix,ata_generic,sata_sil24

linear 7296 0

loop 18948 0

lp 12324 0

mbcache 9600 2 ext2,ext3

md_mod 82068 7 raid10,raid456,raid1,raid0,multipath,linear

Module Size Used by

multipath 9600 0

nvidia 7106340 42

output 4736 1 video

parport 37832 3 ppdev,lp,parport_pc

parport_pc 36260 1

pata_acpi 8320 0

pata_jmicron 7040 1

pci_hotplug 30880 1 shpchp

pcspkr 4224 0

ppdev 10372 0

processor 36872 1 thermal

psmouse 40336 0

r8169 32900 0

raid0 9344 0

raid10 25728 0

raid1 25728 1

raid456 129040 0

rfcomm 41744 0

sata_sil24 17796 2

sbs 15112 0

sbshc 7680 1 sbs

scsi_mod 151436 4 sr_mod,sg,sd_mod,libata

sd_mod 30720 7

serio_raw 7940 0

sg 36880 0

shpchp 34452 0

snd 56996 19 snd_rtctimer,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device

snd_hda_intel 344728 3

snd_hwdep 10500 1 snd_hda_intel

snd_mixer_oss 17920 1 snd_pcm_oss

snd_page_alloc 11400 2 snd_hda_intel,snd_pcm

snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss

snd_pcm_oss 42144 0

snd_rawmidi 25760 1 snd_seq_midi

snd_rtctimer 4640 1

snd_seq 54224 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event

snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq

snd_seq_dummy 4868 0

snd_seq_midi 9376 0

snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi

snd_seq_oss 35584 0

snd_timer 24836 3 snd_rtctimer,snd_pcm,snd_seq

softcursor 3072 1 bitblit

soundcore 8800 1 snd

sr_mod 17956 0

thermal 16796 0

tileblit 3456 1 fbcon

uhci_hcd 27024 0

usbcore 146028 4 usbhid,ehci_hcd,uhci_hcd

usbhid 31872 0

video 19856 0

vmblock 16672 3

vmci 54616 0

vmmon 75280 0

vmnet 46272 3

xor 16136 2 raid456,async_xor

x_tables 16132 1 ip_tables

[admin]

One thing to check for is KVM or Xen, as in

[Jazbo]

I am having the exact same problem and the only suggestions I could find were related to kvm and qemu. Neither of these are even installed on my computer and I am not running Xen, yet VMware still complains that "The virtualization capability of your processor is already in use. Disable any other running hypervisors before running VMware Workstation." The strange thing is that I have another computer, running an identical version of Fedora 8, with kvm & qemu installed but not running or loaded, and the same version of VMware works perfectly. Is this a hardware issue that is incorrectly reported as a conflicting VM problem?

[admin]

Can you verify that the output of "uname -r" does not report a kernel with 'xen' in the name and that "lsmod | grep kvm" finds no matches?

[jsa]

Could they also have a bios setting problem?

[admin]

I don't think so. Workstation 6.5 checks to see if CR4.VMXE is set. Enabling or disabling VT in the BIOS should not effect this bit in any way.

[Jazbo]

Hi,

As you can see, neither xen nor kvm are running/loaded:

$ uname -a

2.6.25-14.fc9.x86_64

$ lsmod | grep vm

vmnet 49860 13

vmblock 22608 3

vmci 57616 0

vmmon 76224 0

Only VMware's kernel modules are loaded.

Note: because of other issues I was having, I finally upgraded to Fedora 9 this weekend, but still have the same problem.

I also rebooted and verified that my BIOS does indeed have Intel's VT (Vanderpool) enabled.

~Jason

[admin]

Kernels before 2.6.26 did not clean up when the kvm_intel module was unloaded. Are you sure that the module has never been loaded? Can you double-check /etc/modprobe.conf and make sure that kvm doesn't get loaded at boot? It sounds like perhaps the module has been loaded and subsequently unloaded via rmmod.

[Jazbo]

Kernels before 2.6.26 did not clean up when the kvm_intel module was unloaded. Are you sure that the module has never been loaded? Can you double-check /etc/modprobe.conf and make sure that kvm doesn't get loaded at boot? It sounds like perhaps the module has been loaded and subsequently unloaded via rmmod.

Good catch, that was it! Over a year ago when I started using VMware on Fedora, kvm was getting loaded at boot time without any entries in /etc/modprobe.conf, so I just modified /etc/rc.d/rc.local to rmmod the kvm_intel & kvm modules because of the well known host kernel hang problem. This worked with VMware 6.0.1, but recently I tried upgrading to 6.0.5 and 6.5 and immediately ran into this conflict problem. I assume because of the host hang problems, new versions of VMware check for the conflict before starting, but as you said, a simple rmmod is not sufficient because it does not clean up properly. I replaced the rmmod with these lines in my /etc/modprobe.conf:

alias kvm_intel off

alias kvm off

So, now the modules never get loaded in the first place and VMware starts up just fine. I wish I could just upgrade to the latest 2.6.26.x kernels in Fedora, but sound does not work for me. Thanks for the help.

~Jason

[johnswb]

I was getting the same problem and after removing xen and kvm I was able to power on my VM.