Strange error; VMware Server 2.0.1 stopped running virtual machines after update.

I was trying to understand what the problem may be, but I can't find so put my VM in your hands.

It worked perfectly until I updated my x 64 Ubuntu 8.04 to:

root@VisionServer:/usr/lib/VMware# uname - a

Linux visionserver-2.6.24 - 24-server #1 SMP Sat Aug 22 00:59:57 UTC 2009 x86_64 GNU/Linux

I also brought up the RAM from 1 GB to 8 GB, but that should not intervene, or?

The interface is not implemented service (but netstat it also lists open).

root@VisionServer:/usr/lib/VMware# netstat-l

Connections Internet active (only servers)

Proto Recv-Q Send-Q local address foreign address State

tcp        0      0 *:902                   :                     LISTEN

tcp        0      0 *:8333                  :                     LISTEN

TCP 0 0 localhost:8307 : LISTENING

tcp        0      0 *:8222                  :                     LISTEN

tcp6 0 localhost:8005 0 LISTEN :*

tcp6       0      0 :8009               :*                  LISTEN

tcp6       0      0 :8308               :*                  LISTEN

tcp6       0      0 :ssh                :*                  LISTEN

udp        0      0 *:bootpc                :

UDP 0 0 192.168.17.1:ntp :

UDP 0 0 172.16.130.1:ntp :

UDP 0 0 visionserver.vision:ntp :

UDP 0 0 localhost:ntp :

udp        0      0 *:ntp                   :

udp6 0 fe80::250:56ff:fec0:ntp 0 :*

udp6 0 fe80::250:56ff:fec0:ntp 0 :*

udp6 0 fe80::214:5eff:fef8:ntp 0 :*

udp6 0 0 ip6 - localhost:ntp :*

udp6       0      0 :ntp                :*

raw        0      0 *:icmp                  :                     7

UNIX domain sockets active (only servers)

Inode proto RefCnt flags Type State path

UNIX 2 /var/run/vmware/root_0/1253661581394001_8906/ha-nfc-fd STREAM LISTENING 17007

UNIX 2 /var/run/vmware/root_0/1253661581394001_8906/ha-nfcssl-fd STREAM LISTENING 17014

UNIX 2 /var/run/vmware/proxy-Web server STREAM LISTENING 17016

UNIX 2 /var/run/vmware/root_0/1253661581394001_8906/hostd-vmdb-fd STREAM LISTENING 17065

UNIX 2 /var/run/vmware/proxy-mob STREAM LISTENING 17067

UNIX 2 /var/run/vmnat.9485 STREAM LISTEN 17901

root@VisionServer:/usr/lib/VMware# /etc/init.d/vmware-core start

Starting VMware services:

Virtual machine monitor makes

Virtual machine communication interface is

VM communication interface socket family: fact

Virtual Ethernet is

Networks bridged on/dev/vmnet0 made

Network invited only on/dev/vmnet1 (background)

Server DHCP on/dev/vmnet1 did

Network invited only on/dev/vmnet8 (background)

Server DHCP on/dev/vmnet8 is

NAT service on/dev/vmnet8 is

Demon of authentication server makes VMware (background)

Available shared memory is

Yet;

root@VisionServer:/usr/lib/VMware# /etc/init.d/vmware-core State

Networking networking on/dev/vmnet0 is running

Network host detection does not work

Invited only on/dev/vmnet1 network is running

DHCP server on/dev/vmnet1 is running

Network invited only on/dev/vmnet8 is running

DHCP server on/dev/vmnet8 is running

NAT networking on/dev/vmnet8 is running

Responsible vmmon module

Loaded module Vmnet

And no virtual machine work! ... It installs without a hitch and says that everything is good to go, but obviously not! :/

/ Thank you thousand!

Start your old kernel and see if it works.

Tags: VMware

Similar Questions

  • Commands to start and stop a virtual machine hosted by VMware player

    Where can I find the commands to start and stop a virtual machine hosted by VMware player on a host Windows Server 2008 R2 (64-bit)?

    I need to start and stop the virtual computer from a script as I could do this by selecting the ' power on ' and his 'guest stop' or at least 'power off' options of the GUI of VMware player.

    If a control interface is not available, is available if I update to VMware Workstation?

    Concerning

    Marius

    With the player, the VIX API is a separate download (on the same page you downloaded the install drive in), so I guess you will have to install the separate package to use it.  But it's pretty easy to do...

  • Cannot import Microsoft Windows Server 2008 R2 with Hyper-V virtual machines to VMware ESXi 4.

    Hi team,

    I use VMware vCenter Converter Standalone to import certain Microsoft Windows Server 2008 R2 with Hyper-V virtual machines to VMware ESXi 4, using another Windows Server 2008 R2 as the machine Agent Converter. Well, the agent connects to the Windows VM source very well (I used the net use command to create a line of conduct...), perhaps no chance to connect to the computer target VMware ESxi 4 and make the converter doesn't work...

    Following is the error message:

    "Unable to connect to the host specified" from the converter agent machine. " It is perhaps because the host is not available on the network, there is a problem with the network configuration or management on this host services do not react. Check all components of converter to be able to connect.

    So, my question is; is it possible to create a work around (like the net use Windows command above) to make possible the connection of the converter Agent on Linux VMware ESXi 4 machine Windows machine, to directly import the virtual machines of Windows Hyper-V to Linux VMware?

    Thanks in advance,

    It's even easier than that

    Use this: http://www.winimage.com/

    Which will convert *.vhd *.vmdk, so you don't need to do all this... Of course, another way is to start the machines, leaving them on Hyper-V and go through the network and process virtual machine as physical machines and do a P2V on the network...

  • I get an error "the disk hard virtual parent is in a saved state. Discard the saved state or stop the virtual machine and try again. "during the installation of XP mode.

    I have Win7 Pro SP1 x 64.  I downloaded WindowsXPMode_en - us.exe (from Microsoft downloads) and run it.  The installation seems to work OK (I've specified a different location for the parent virtual hard disk file).  Then, installation happening and I provide the information requested (name of user and password for the XP Mode), updates Windows and OK to the issue of sharing.  The installation program then reports the following error:

    The disk hard virtual parent is in a saved state.  Discard the saved state or stop the virtual machine and try again.

    I get the error even if I try manually configure XP Mode (use the Setup Wizard).  I downloaded the installer XPMode (3 times) and reinstalled several times, always with the same result.  If it helps, I can't locate anywhere .vsv file.

    Any idea what's going on?

    Original title: XP Mode Setup error

    Hi smithnr10,

     

     

    You must post your question in the TechNet forums because it caters to an audience of it professionals.

    To do this, you must consult the link-

    http://social.technet.Microsoft.com/forums/en-us/w7itprovirt/threads

     

    Hope this helps!

  • How to activate the Internet connection on Windows Server 2003 is installed in the virtual machine in VMware Workstation 8?

    I have Windows Server 2003 is installed on a virtual machine in VMware Workstation 8. I need it to learn and practice the use of the Active Directory. I've also set up 3 Windows XP workstations connect to it, which means that they can communicate with Server 2003. What is lacking is the Internet connection on all of them. When I run ping 8.8.8.8 in one of these virtual machines, I get, 'Destination host unreachable.'

    I'm not sure, what if the problem comes from the settings in Windows or the settings of the virtual machine.

    Can someone help me?

    Thank you, guys. I was finally able to put in place. It was quite an ordeal to deal with IP addresses and virtual networks. Here's how I did (in the screenshots) in case someone else needs it.

    (I also confess that it is perhaps one of the ways to implement. Maybe there is an easier way to do it with DHCP...)

    1. in your computer where is installed VMware Workstation 8 begin the "Virtual Network Editor." It is located in the folder of installation of VMware Workstation. And implement the network following (VMnet2 in my case):

    2 then in VMware Workstation itself in the virtual machine when Windows Server 2003 is installed set up two network as connections:

    This one is for external access to the Internet:

    And this one for intranet communications AD:

    3. then in the machine virtual de Windows Server 2003 set up what follows for two network adapters:

    For Internet access:

    Then, you need allow this connection to share:

    And then for the ad access to workstations (ensure that the static IP address is in the range specified in the virtual network over VMnet2 network editor). I've also set up DNS to 127.0.0.1 because I installed on this Windows 2003 DNS server:

    4. from the Windows 2003 VM try ping 8.8.8.8. It should work now.

    5. go to each workstation, in my case, Windows XP, each in its own virtual machine and set up the network in the VMware Workstation as follows:

    6. then in the virtual machine, configure the network connection for Windows XP workstation. Don't forget to assign a new static IP address for each workstation, which not coinside with IP of the domain (this IP address must come from the range specified in the virtual network over VMnet2 network editor):

    7. try first ping the domain, in my case ping 192.168.237.128. And then Internet, ping 8.8.8.8. The two should work!

    Continue with steps [5-7].

  • Cannot stop a virtual machine

    ESX 3.5

    Hello

    I can't stop a running virtual machine.

    There's no way to have a clean shutdown because the virtual machine is not responding (os: ubuntu server 4.x)

    Virtual infrastructure client power off command closes with error: operation failed as another task is underway

    Same error to connect to the server esx and vmware-cmd by train

    & gt; VMware-cmd web2.vmx stop

    VMControl error - 999: unknown error: SoapError: ServerFaultCode (0): (the operation failed because another task is in progress.)

    & gt; VMware-cmd web2.vmx hard stop

    VMControl error - 999: unknown error: SoapError: ServerFaultCode (0): (the operation failed because another task is in progress.)

    Thanks for your suggestions,

    Valter

    You can try one of the following methods of the cli:

    VM-help - x - list of vmid

    VM-support - X < vmid > to kill him...

    or

    PS - auxwww | grep-i < vmname >

    Find the PID and kill-9 pid

    See also http://communities.vmware.com/docs/DOC-2290

  • script to stop the virtual machine

    I am writing a script to stop all the virtual machine as follows:

    1. The list of the VM

    VMLIST ='/ usr/bin/vmrun list '

    for a virtual machine in '$VMLIST '.

    do

    echo '$VM '.

    1. stop the virtual machine

    / usr/bin/vmrun stop '$VM' trysoft

    sleep 2

    fact

    But he failed, the news of the error:

    / root/vmware/Windows NT / Windows NT.vmx

    Error: Could not open the virtual machine: unknown suffixNT/Windows NT.vmx file

    the feedback by the command "echo $VM" is the correct path, but why it says file unknown?

    Please refer to the attachment.

    See if that helps...

    vmlist ='/ usr/bin/vmrun list '

    printf "$vmlist" | egrep '\.vmx$ ' | while reading vm; echo '$vm '.

    / usr/bin/vmrun stop soft "$vm".

    sleep 2; fact

  • Stop the virtual machine

    I'm looking for a script to stop vm...

    Script works fine, but I have a few Questions or details

    $csv = import-csv C:\xxx.csv

    Foreach ($line in $csv)

    {

    Write-Host “====================================================================”

    Write-Host "$line treatment".

    $vminfo = get-view-Id ($line.vm) USER.USER

    Write-Host "checking the VMware Tools on $line... »

    # If we have the VMware tools installed

    If ($vminfo.config.Tools.ToolsVersion - eq 0)

    {

    Write-Host "($line.vm) don't have vmware tools installed, strong power this one.

    # Hard power off.

    Stop-VM ($line.vm)-confirm: $false

    }

    on the other

    {

    write-host "I'll try to stop $vm.

    # Turn off with elegance

    Get - VM ($line.vm) | Stop-VMGuest-confirm: $false | Out-Null

    }

    }

    1. my code below what I'm missing / or hurt?

    $vminfo = get-view-Id ($line.vm) USER.USER

    Write-Host "checking the VMware Tools on $line... »

    2. Tools a lot of combination

    Tools installed - but not running

    tools not install

    Are that both will have to stop-vm?

    3.

    I got a simple code, it will cover the tools stuff?

    $vm = Get-VM
    $vm | where {$_. Comments . State -eq "Running"} | Shutdown-VMGuest -confirm:$false
    $vm | where {$_. Comments . State -eq "NotRunning"} | Stop-VM -Confirm:$false


    4. I want to stop 50 virtual machines simultaneously, how the


    Your script seems to be ok.

    When the VMware tools are installed you can do a gracefull shutdown (Stop-VMGuest) within the guest where OS the obligation for the VMware tools.

    The next option is to stop the virtual machine (VM-Stop), with what would be the power button on a physical computer.

    No phasing out of the BONES and a potential risk on the corruption of the OS.

    With switch RunAsync that the cmdlet returns immediately, it will not wait until the underlying vSphere method is complete.

    The method will continue, but in the background.

    You should check these tasks to background (Get-task), to monitor the successful completion.

    To manage VMS in batches of 25 and wait 60 seconds between batches, you could do something like that

    $vms = get - VM

    $step = 25

    $start = 0

    for ($loop = 0; $loop - the ([math]: ceiling ($vms.)) Step Count / $)-1); $loop ++) {}

    $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Running"} | Stop-VMGuest-confirm: $false - RunAsync

    $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Keep"} | Stop-VM-confirm: $false - RunAsync

    sleep 60

    $start += $step

    }

  • SRM 5.5 - vSphere replication - error: impossible to reverse the replication for the Virtual Machine. A snapshot operation cannot be performed

    Hi all, we have just run a test DR failover of a couple of virtual machines in our protected our failover site and all site swung perfectly, two virtual machines came online and all applications work well. However when we cam to r-eprotect machines virtual, we get some errors.

    One of the virtual machines seems to have lived the reprotect end process, it is still running, but has not moved to 89% for some time. The virtual machine has a couple of grand (a little less than 2 TB) VMDK. slow progress is just a consequence of the large VMDK?

    More worrisome is the virtual machine which don't reprotect at all. It generates an error whenever I click on the "Restore" button (error: impossible to reverse the replication for the Virtual Machine.) A snapshot operation can not be performed).


    Does anyone have any ideas as to the cause?

    Thanks in advance for any help.

    Andy

    Finally got to the bottom of this. The issue was that reprotect SRM work was trying to dispel any snapshots that were taken on the computer object virtual destination in VMWare, but could not clean snapshots.

    The reason why snapshots would not consolidate was because it was snapshots of temporary VEEAM who in fact any snapshot file listed in the VSAN data store. So when we looked through the browser data store, no snapshot file existed in the virtual computers folder. Trying a manual removal also failed.

    To fix this, we created a snapshot of the virtual machine in the original data center (note is the engine to the bottom of the virtual machine), this effect was to get rid of the 'fade' snapshot that was visible in the Snapshot Manager that VEEAM backup had left behind. Once this had disappeared, the reprotect back to DCA worked perfectly.

  • I get the error number: 0x80072EE2 when I try to run windows or microsoft update under Win xp

    I get the error number: 0x80072EE2 when I try to run windows or microsoft update under Win xp

    Hello

    I suggest you try all the steps in the following article.
    You may encounter temporary connection related errors when you use Windows Update or Microsoft Update to install updates.
    http://support.Microsoft.com/kb/836941

    I hope this helps.

  • Need more disk space to run virtual machines on R710 server with no available drive slots

    Hello

    We have a server R710 with five $2.5 146 each and three 600 GB SCSI disks SCSI.  We have no more slots.

    We want another 2-4 TB of space.   This server is used to run virtual machines to test software applications.  We have need for decent speed, but more important still need a cost-effective solution for running virtual machines.

    The budget would be in the $1000 range give or take.  I might be able to get $3000, but a $10,000 would be too.  We could consider removing disks from 146 GB 5 and replacing them with those larger, but that might not be the first choice.

    Any ideas?

    Thank you!

    What you ask for is really difficult to do within the budget without sacrificing important performance (from what you have right now in performance).

    Any external storage solution (Dell) is out of the question for $3 k (think MD1200/1220).

    The market, 2.5 "drives max out at 1 TB at 7200 RPM, 900 tr/10 k or 300 GB @ 15 k RPM.

    Dell has disks 1 to 7200 RPM 2.5 "company (for PowerEdges) for ~ $440 (see here). These are not the best choice if you want any kind of good performance.

    You might look into upgrading to 900GB 10 k rpm drives. These run $799 each today on the Dell website (see here).

    If you replace one of the 146 both each and let rebuild you could then use the extra space to another virtual disk. This would give about 2800GB.

    If you can't budget 5 of them, according to the current setup of raid, you can watch a backup and restore of the virtual disk of some 146.

    You could:

    -use 2 of the existing 146 in raid 1 for operating system and the extra space

    -use 3 x 900 in raid 5 (which would give a crude 1800 (Go so ~ 1674 usable))

    -Use the 3 600 existing RAID 5 (which would give ~ 1116 GB usable)

  • How to configure the agent to monitor performance only the vcenter vmware and esx, not need to monitor virtual machines

    How to configure the agent to monitor performance only the vcenter vmware and esx, not need to monitor virtual machines

    This is not possible with the way in which we collect information.

  • Where VMWARE Workstation 11 stores no information about Virtual Machines open

    When you 'open' a virtual machine in VMWARE Workstation 11, then close VMWARE and open again, it remembers what virtual machines have been opened.  Where it does not store this information?

    After a lot of Googling, I found the answer I was looking for.

    The UNK file is located in

    %AppData%\vmware\preferences.ini

    However, the information of the open machine no longer in the UNK file.  It is now located at

    % AppData%\vmware\inventory. VMLS

  • Bluescreen error VmWare Server on Windows 2003 Enterprise R2 64 Bit edition hosts

    Hello

    We have to run VmWare Server on host companies Windows Server 2003 R2 64 Bit edition

    We go through a very strange problem where once in while the host has a blue screen

    We checked everywhere on the net and this forum and found a few things to do and we did it all.

    Please suggest a solution for this problem

    Kind regards

    Virendra shukla

    This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)
    *

    http://social.msdn.Microsoft.com/Forum

    When you get there you please provide DMP files

    We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
    Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here
    If you have any questions regarding the procedure, please ask
  • VMWare Server 2 into conflict with Microsoft Virtual PC 2007

    I use Windows Vista x 64, when I have a virtual VMWare Server 2.0 open, and then start upward a Microsoft Virtual PC 2007 Virtual Machine, VMWare Machine will be output/die. If I already have a MS VPC 2007 open machine, then when I try to start a VMWare VM, I get the following message:


    Unable to connect to the MKS: there is no VMware process running for the C:\Users\Rusty\Documents\VMWare Machines\Ubuntu\Ubuntu.vmx configuration file virtual
    Either run "C:\Program Files (x 86) \VMware\VMware Server\x64\vmware-vmx.exe C:\Users\Rusty\Documents\VMWare virtual Machines\Ubuntu\Ubuntu.vmx" manually on the server.
    or save the configuration file.

    It is likely that VPC 2007 leaves the CPU in operation VMX VMware Server prevents to alternate between legacy and long mode.  Unfortunately, this switch is required for the majority of host/guest under VMware Server 2 configurations.

    I don't know if it is possible to disable VT - x in VPC 2007 support, but if this is the case, maybe it's a work around for this problem.

Maybe you are looking for