Hi All,

I am new to VMWare server, so bare with me if I sound a bit nooby.

I have a server running Windows 2003 SE 32 bit. I used Windows WMware converter Standalone to create a VM from the physical machine. I selected VMware Servwer 2.x as the target environment. Then I disconnected the drives for the Windows server, put in a new one and installed RH Linux 64bit OS, and the VMware Server 64 bit for it. I got it all up and running without any issues.

However, the Windows VM won't start, throwing out the error shown on the attached PDF file. It is a startup blue screen warning of a serious error and that it is shutting down to avoid damage to the Windows system. It suggests reviewing the hard drive setup. It gets as far as throwing up the very first Windows 2003 Server logo witrh the little activity bar cycling about twice before the blue screen appears.

Is this a reasonable thing to expect to be able to do? That is, to "clone" a Windows system using the Windows version of WMWare Converter Standalone, and copy the resulting files to a Linux system running VMware server? The hardware is the same hardware that the "real" Windows server runs on. The .VMX  file is alos attached.

Hardware: Dell SC1420, Dual Core Xeon, 3Mhz, 4GB RAM, 1TB single SATA drive (under the Linux config), two SATA drives (under the Windows Server Config).

Thanks in advance for any advice for what I am trying.

Bill

Hi all,

Hope I got the right place, I find this forum structure very confusing.  Anyway.  Situation is this:

I have a dual-stack network using router advertisments, putting all systems on the 2001:388:d000:1100::/64 IPv6 subnet.

No firewalls are enabled on any of the systems within the network (any firewalling is being done at the border router).

VMWare Server 2.0 runs on an AMD64 desktop atop Gentoo Linux.  Hostname: beast.redhatters.yi.org, IPs: 192.168.64.32 and 2001:388:d000:1100:6ef0:49ff:feef:847c.

Two VMWare guests run atop the server:

• training3.redhatters.yi.org, IPs: 192.168.64.33 and 2001:388:d000:1100:6ef0:49ff:feef:847c/64 running Windows 2003 Server
• metermaster.redhatters.yi.org, IPs: 192.168.64.35 and 2001:388:d000:1100:6ef0:49ff:feef:847c running Ubuntu 10.04 LTS

Other systems on the same network:

• My P4 laptop, vk4mslp2.redhatters.yi.org, IPs: 192.168.64.38 and 2001:388:d000:1100:208:dff:fe5c:851, running Gentoo
• My netbook, zhouman.redhatters.yi.org, IPs: 192.168.64.36 and 2001:388:d000:1100:223:8bff:fe35:6f71, running Gentoo

I am using bridged networking, connecting the guests to the same physical LAN as the host and other systems.

The guests are able to talk to every other IPv6 capable host without issues.  The Ubuntu VM frequently connects to the local Ubuntu mirror (on AARnet) via IPv6 when downloading updates, no problems there.  Windows 2003 can also be accessed using RDP via IPv6 (using portproxy on the Windows guest) from either of the laptop or the netbook.  e.g.

zhouman ~ # netstat -anlp | grep rdesktop
tcp6       0      0 2001:388:d000:110:37329 2001:388:d000:1100:3389 ESTABLISHED 17978/rdesktop  

The guests however will not communicate with the host, nor vice versa, via IPv6.  Via v4, everything is rosy, everything works.  But when communicating between the host and guests, IPv6 traffic just stalls:

stuartl@beast ~ $ ssh -4 root@metermaster
Linux metermaster 2.6.32-28-generic-pae #55-Ubuntu SMP Mon Jan 10 22:34:08 UTC 2011 i686 GNU/Linux
Ubuntu 10.04.2 LTS

Welcome to Ubuntu!
* Documentation:  https://help.ubuntu.com/

0 packages can be updated.
0 updates are security updates.

Last login: Thu Feb 24 04:44:37 2011 from beast.local
root@metermaster:~# logout
Connection to metermaster closed.

stuartl@beast ~ $ ssh -6 root@metermaster
ssh: connect to host metermaster port 22: Connection timed out

Yet it works elsewhere:

stuartl@beast ~ $ ssh -6 zhouman
Last login: Thu Feb 24 13:46:17 EST 2011 on : 0

KeyChain 2.6.8; http://www.gentoo.org/proj/en/keychain/
Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL

* Found existing ssh-agent (1628)
* Found existing gpg-agent (1656)
* Known ssh key: /home/stuartl/.ssh/id_dsa

stuartl@zhouman ~ $ ssh -6 root@metermaster
The authenticity of host 'metermaster (2001:388:d000:1100:20c:29ff:fee0:c5b8)' can't be established.
RSA key fingerprint is f6:d6:4a:90:2a:a8:5e:a3:7a:b1:7c:ba:ea:71:5e:11.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'metermaster,2001:388:d000:1100:20c:29ff:fee0:c5b8' (RSA) to the list of known hosts.
Linux metermaster 2.6.32-28-generic-pae #55-Ubuntu SMP Mon Jan 10 22:34:08 UTC 2011 i686 GNU/Linux
Ubuntu 10.04.2 LTS

Welcome to Ubuntu!
* Documentation:  https://help.ubuntu.com/

0 packages can be updated.
0 updates are security updates.

Last login: Thu Feb 24 04:57:24 2011 from beast.local
root@metermaster:~#

Has anyone struck this before and have any ideas what might be causing this?  It's getting a little irritating having to force IPv4 all the time.

Hello. This might sound trivial, but obviously I'm missing something here... So here's the setup :

I have a Windows 2008 server (Web Edition) ; this server has a network card that's got a public IP address working OK.

I have VMWare 2.0 installed on that server.

Then I have a VM running a Windows 2003 SBS setup. The network card in the VM is using VMWare's NAT. For convenience I have setup Window 2003 to use a manual IP address rather than a DHCP-obtained one, but that makes no difference with regards to the issue.

The problem :

- within the VM, I can ping outside (like ping www.google.com works allright), DNS requests are resolved Ok (as in ping www.google.com works ) ; querying a DNS on the Internet using nslookup works Ok as well.

- I can not browse outside !? with IE

- I have tried telnetting known working servers on various ports (25, 80, 21, 110...) with no success at all

FWIW, I can also rdp into the Windows 2003 client from anywhere on the Internet, having forwarded the appropriate port in VMWare's NAT configuration.

So far, this sounds like a firewall issue. The thing is, the firewall in the Windows 2003 client is disabled and I tried with the Windows 2008 firewall disabled as well. No luck.

Ideas welcome...

Z.

G'day,

I'm running VMServer 2.0.1 on Ubuntu 9.0.4 (Jaunty) hosting CentOS 4.7 guest VMs.

I am continually seeing the following message when powering on a guest VM:

The network bridge on device vmnet0 is temporarily down because the bridged Ethernet interface is down. The virtual machine may not be able to communicate with the host or with other machines on your network.

The work-around I've discovered is to restart the vmware services, i.e.

$ sudo /etc/init.d/vmware stop

Stopping VMware autostart virtual machines:

  Virtual machines                                                    done

Stopping VMware management services:

VMware Virtual Infrastructure Web Access

  VMware Server Host Agent                                            done

Stopping VMware services:

  VMware Authentication Daemon                                        done

  Virtual machine communication interface                             done

  Virtual machine monitor                                             done

  Bridged networking on /dev/vmnet0                                   done

  Host network detection                                              done

  DHCP server on /dev/vmnet1                                          done

  Host-only networking on /dev/vmnet1                                 done

  DHCP server on /dev/vmnet8                                          done

  NAT service on /dev/vmnet8                                          done

  Host-only networking on /dev/vmnet8                                 done

  Virtual ethernet                                                    done

$ sudo /etc/init.d/vmware start

Starting VMware services:

  Virtual machine monitor                                             done

  Virtual machine communication interface                             done

  Virtual ethernet                                                    done

  Bridged networking on /dev/vmnet0                                   done

  Host-only networking on /dev/vmnet1 (background)                    done

  DHCP server on /dev/vmnet1                                          done

  Host-only networking on /dev/vmnet8 (background)                    done

  DHCP server on /dev/vmnet8                                          done

  NAT service on /dev/vmnet8                                          done

  VMware Server Authentication Daemon (background)                    done

  Shared Memory Available                                             done

Starting VMware management services:

  VMware Server Host Agent (background)                               done

  VMware Virtual Infrastructure Web Access

Starting VMware autostart virtual machines:

Virtual machines                                                    done

Output from ifconfig and ps -ef |grep vmnet is given below.

Why isn't vmnet0 available after booting, and how can I make it so?

Thanks,

Chris.

$ ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:1e:0b:35:d5:12 

inet addr:10.1.1.2  Bcast:10.255.255.255  Mask:255.0.0.0

inet6 addr: fe80::21e:bff:fe35:d512/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:1354 errors:0 dropped:0 overruns:0 frame:0

TX packets:1798 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:100

RX bytes:383251 (383.2 KB)  TX bytes:1126131 (1.1 MB)

Memory:f0500000-f0520000

lo        Link encap:Local Loopback 

inet addr:127.0.0.1  Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING  MTU:16436  Metric:1

RX packets:6225 errors:0 dropped:0 overruns:0 frame:0

TX packets:6225 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:4962948 (4.9 MB)  TX bytes:4962948 (4.9 MB)

pan0      Link encap:Ethernet  HWaddr 96:e2:2c:be:eb:c6 

BROADCAST MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01 

inet addr:172.16.181.1  Bcast:172.16.181.255  Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:26 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet8    Link encap:Ethernet  HWaddr 00:50:56:c0:00:08 

inet addr:192.168.60.1  Bcast:192.168.60.255  Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:27 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

$ ps -ef |grep vmnet

root      2885     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid -n 0 -i eth0

root      2900     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1

root      2911     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1

root      2927     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8

root      2943     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8

root      2948     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf

Everyone has their favorite list of performance tweaks for the old 1.0 Server product.  MemTrimRate, pshare, etc.

Has anyone applied these tweaks to the 2.0 product?  Do they still help with performance?  Do they even still exist as tweaks?

I posted this question back in the RC2 forums and nobody ever responded.  Is nobody interested in improving VM performance under 2.0?

Okay, I am getting a replacment for my little 4 core 1U machine that I have run for the last 18 months and getting a large 16 core 48G machine, and now I have to figure out how to best utilize it.  Here is the issue, and I am interested in what people think. 

The machine is supported with ESXi (in fact could have been purchased with it preinstalled) and comes with 500+G of SAS storage.  The virtual machines I am moving however are on VMware Server 2.0 RC 1, which means I will have to rebuild all them as they are HW Type 7, which isn't supported on ESXi.  I have 14 virtual machines today, and this represents several weeks of rebuilding if I have to start from ground zero.  Understand that the new server was sort of a surprise to me, I thought I was just going to be geting 2 more 1U pancake servers, so I hadn't been planning for this change. 

The PROs for ESXi is the performance characteristics and bare metal install, but the big CON for ESXi is I have no Windows in my arsenal.  My two workstations are pure Linux machines, 13 of the 14 virtual machines are Linux and the 1 Windows virtual machine is fully taxed and belongs to another team who will likely be taking their license when their project ends.  I have no money to buy additional licenses but may be able to get buy with a trial license till the beginning of the year when I may be able to acquire a Windows license.  I know that next year some time VMware is supposed to have a control center for Linux for ESX, but I have to do something this year and would hate to have to do it twice.

Does it really make that much difference in performance, given that I am going from 4 cores to 16 cores, to jump to ESXi find a way to wrangle up the Windows license to manage it temporarily until the Linx client comes along and I can hopefully hook that into IBM System Director (the literature on IBM System Director seems to indicate that I need the VMware console as well as IBM Director).  What do you all think?

I am trying to add a CDROM to my VM using the "Add Hardware Wizard." The only option I can select is to use an ISO image, it will not allow me to use a physical drive on the host.

Is this a bug or is there a trick to this version of VMServer?? I have attached a image of what I option I have.

I am running this Host/VM on an HP Blade and I have connected a virtual CD drive via ILO, the drive is available on the host and I verified I can read from it.

I have a VM on a portable drive.  To add the VM to inventory, I had to create a datastore that points to the portable drive.  On bootup of the server, the portable drive is not connected but is plugged into the USB port as needed.  VMWare Server 2 doesn't recognize that datastore unless the drive is plugged in at boot up time.

If, after plugging in the portable drive, I try to execute a remote console shortcut to that VM, I get this error:

"The attempted operation cannot be performed in the current state (Powered Off)".

If I open the admin console page after plugging in the portable drive, the inventory for this VM says "Unknown (Inaccessible)".

If I remove the VM from inventory in the hopes of re-adding it.  When I try to re-add the VM, the Datastore for the portable drive is listed but when I click to open the datastore the Contents column says:

"The Datastore Browser could not successfully retrieve data from the server."

I then  tried simply double-clicking the VMX file for the VM.  There was no file association in Windows so I didn't pursue this further yet.

My next thought was to remove and re-add the datastore, forcing VMWare Server to see the portable drive (I am able to browse the drive in Windows Explorer).  I cannot find any way to remove a Datastore from the list.  When I try to re-add the Datastore, I get an error that it is the same name.  I could possibly add the Datastore using a different name but since there doesn't seem to be a way to delete them once created, I didn't want to try that yet.

So there are four problems/questions that I have:

1.  Is there a way to refresh the inventory list within the web based admin page?

2.  In VMWare Server 1.x, I could simply double-click a VMX file and it would add to inventory.  This didn't work inVMWare Server 2.  There was no file association in Windows.  Is it possible to fix this?

3.  Is there a way to refresh the Datastore contents?

4.  Is there a way to delete a Datastore that is no longer wanted or used?

The only thing that worked was to reboot the server with the portable drive connected.  This is not always a desirable procedure.

Thanks,

Dale

Message was edited by: dalepres

I needed to use a raw physical disk from within a VMware image.  This works in VMware Workstation and apparantly also in Server 1.x but somehow the ability to use physical disks was removed from the UI of Server 2.0. While I could find some posts about this on the forum none of them really helped me any further.  After a lot of fiddling and comparing with VMware Workstation I finally found how to make it work.  I hope this is usefull for somebody. If it isn't, just ignore me 

I used the following setup:

My server has 2 'disks': /dev/sda is a local raid used for storing the server os and guest images, /dev/sdb is a chunck of a SAN connected via fiberchannel which will be used by one particular guest called 'barbar'.

• Make sure the guest is powered off before making any changes

• The configuration of the VMware guest image is stored in the <guestname>.vmx file in the guests directory.  The virtual disk configuration consists of a few lines which read like this:

-

scsi0:1.present = "TRUE"

scsi0:1.fileName = "barbar-0.vmdk"

scsi0:1.deviceType = "rawDisk"

-

Note the '0:1' denotes the second disk on the first SCSI channel. This is because I'm using 2 disks in the guest: the virtual disk which will hold the OS and the physical disk which will show up as the second disk. 

• The vmx file does not contains any references to the actual physical disk I want to use (/dev/sdb). This information is stored in a second file (in this case barbar-0.vmdk)  This file looks like:

-

1. Disk DescriptorFile

version=1

CID=e6704746

parentCID=ffffffff

createType="fullDevice"

1. Extent description

RW 419430400 FLAT "/dev/sdb" 0

1. The Disk Data Base

#DDB

ddb.toolsVersion = "0"

ddb.encoding = "UTF-8"

ddb.adapterType = "lsilogic"

ddb.geometry.biosSectors = "63"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosCylinders = "26108"

ddb.geometry.sectors = "63"

ddb.geometry.heads = "255"

ddb.geometry.cylinders = "26108"

ddb.virtualHWVersion = "6"

-

Disk DescriptorFile  I have no idea what the first set of options do. I copied these from a Workstation 6.0.4 setup.

Extent description this line defines which physical device will be used.  In this case I'm using my secondary disk which is /dev/sdb.  The number is very importan, this is the size of the disk in 512b blocks. You can find this by doing 'fdisk /dev/sdb' on the server

-

fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 214.7 GB, 214748364800 bytes

255 heads, 63 sectors/track, 26108 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1       26108   209712478+  fd  Linux raid autodetect

-

214748364800 / 512 = 419430400

ddb.geometry*  make sure these also match the  geometry of the physical disk. Again you can get this from 'fdisk /dev/sdb' on the server.

The ddb.geometry* info seems to be less important, however the size in the Extent description should be correct otherwise the image won't start.

• now start the guest from the console.  The physical disk will not show up in the guest summary screen, however when you now run 'fdisk /dev/sdb' from within the guest you should see the partition table of the real physical disk

I hope this is useful to somebody

Nico

Please, please please.

Somebody knows how can I revert to snapshot with vmware Server?

Thanks in advanced!

I setup a new nic (USB) on my main linux server, I was having DHCP issues (wont get an IP) but if I set it static it works.  But I only want to use it for bridged VMs so I did not set an IP.  But I just wanted to confirm the nic works, and it does.

So I went through the vmware-config   (is there an easier way to do this?  This is a very long and tedious process) to setup a new bridged VMnet.  I have 25 VM nets bridged to none so I just made one bridged to that nic.

For whatever reason, the VMs can't go out at all.   They wont talk outside of that nic.  I can't get an IP from the router.  (I confirmed the router works, by plugging another PC into it).

Any logs I could check or other troubleshooting I can do from this point?

edit: just found these:

[2008-12-06 18:24:17.581 'NetworkProvider' 139847974512368 info] Unable to load hardware info file /etc/sysconfig/hwconf

Retrieving ip address failed for eth1

Retrieving ip address failed for pan0

Ioctl SIOCGIFHWADDR failed for nic vmnet1

Unable to find interface none bridged to vswitch vmnet9

Ioctl SIOCGIFHWADDR failed for nic vmnet8

Active ftp is 1

Allowanyoui is 1

udptimeout is 60

Unable to find interface none bridged to vswitch vmnet7

Unable to find interface none bridged to vswitch vmnet6

Unable to find interface none bridged to vswitch vmnet5

Unable to find interface none bridged to vswitch vmnet4

Unable to find interface none bridged to vswitch vmnet3

Unable to find interface none bridged to vswitch vmnet25

Unable to find interface none bridged to vswitch vmnet24

Unable to find interface none bridged to vswitch vmnet23

Unable to find interface none bridged to vswitch vmnet22

Unable to find interface none bridged to vswitch vmnet21

Unable to find interface none bridged to vswitch vmnet20

Unable to find interface none bridged to vswitch vmnet19

Unable to find interface none bridged to vswitch vmnet18

Unable to find interface none bridged to vswitch vmnet17

Unable to find interface none bridged to vswitch vmnet16

Unable to find interface none bridged to vswitch vmnet15

Unable to find interface none bridged to vswitch vmnet14

Unable to find interface none bridged to vswitch vmnet13

Unable to find interface none bridged to vswitch vmnet12

Unable to find interface none bridged to vswitch vmnet11

Unable to find interface none bridged to vswitch vmnet10

eth1 is the one it should bridge to.  Why is it erroring out about getting an IP?  Does the nic need an IP to be bridged?  I really can't see why... For my setup it can't have an IP.  I don't want it to be accessible through tcp/ip for security reasons.  I want the vms to be accessible but not the vm server.

Hi there,

I'm trying to add a nic to a VM that does not have one configured using the following command

Command usage is: devices.createnic vmid unit number type network

vmware-vim-cmd vmsvc/devices.createnic 144 0 e1000 Bridged

the output that follows is:

(vim.Network.Summary) {

+   dynamicType = <unset>,+

+   network = 'vim.Network:HaNetwork-Bridged',+

+   name = "Bridged",+

+   accessible = true,+

+   ipConfig = (vim.Network.IpConfigInfo) null,+

}

As this is exaclty the same output as when query a vm that have a nic configured  with the command "vmware-vim-cmd vmsvc/get.networks vmid" I thought this is the trick.

Unfortunatly there is no nic configured in the vmx config file after that.

Looking forward to your feedback .

Regards Agent

Hi,

This subject as been discussed in the past but no solutions of feedback as been posted.

HOST VERSION - VMWARE ESX SERVER 3.5

ACTIVE DIRECTORY INTEGRATED - SECURE DDNS with SCAVENGING ACTIVATED

My VM windows XP hosts does not automaticaly update their DNS records on IP adresses changes.

Normaly they should do so on the following conditions :

1 -The IP adresse is manualy changed

2 -Every 24hours by default

3 -You run  -  IPCONFIG /REGISTERDNS

Now, if i manualy modify the IP adresse the DNS record is not updated... not even after a delay of 48 hours.

The only way to update de record is to run  - IPCONFIG /REGISTERDNS

I installed a fresh Windows XP SP2 VM to eliminate any ''home installed'' reasons for this but  same problem again...

I dont have this problem on Windows 2003 VMs

I used a physical machine with the same OS (windows XP sp2) and i dont have this problem

Anyone experiencing the same thing ?

I want to perform a P to V of my old laptop (XP pro) before I decommision it and tried using the facility in ghost 12 to create a vmware disk.  However the process did not go as planned.

Although the laptop has an ide disk, when I tried to start the VM I'd created it failed saying the disk was a scsi disk.  So I recreated using a scsi profile for the disk, and it started up.  The windows installer started to setup new hardware, it finally rebooted, but now blue screens complaining about a device driver.  I suspect the scsi driver is not available.

Is Ghost 12 capable of performing a PtoV, or just creating a disk which you can add to an existing VM?  If it can do a PtoV, how do I do it?

I i'm trying to install CentOS 5.3 in VMWare Server 2.x. The host system is running Windows 2000 SP4 with an AMD Athelon XP 1800 CPU, 1G RAM and an NVidia FX5200. Every time i try to install CentOS 5.3  the result is always the same, a kernel panic/kernel oops. I have other VM's running in the same host hardware without problem, but those VM's are running FC4 and previous RedHat versions.

As far i can diagnose the problem doesn't seams to be CentOS related. I believe this is true because i have tried to install CentOS 5.3 directly in the host system and i can reach the step where the partitions are created, stage that i can't reach when trying to install CentOS 5.3 in my VMWare Server 2.0 virtual machine.

I have tried to raise the RAM in use by the guest OS, but the problem persists. I have tried to disable acpi (setting the acpi=no as a boot option), doing the install using text mode, but the same problem, kernel panic.

Acording to the kernel panic diagnostic info the problem happens in function xor_sse_2.

The call trace shows the following:

-

apic_timer_interrupt

xor_sse_2

do_xor_speed

calibrate_xor_block

sys_init_module

syscall_call

Code: Bad EIP value

-

I have upploaded the kernel panic message as it has been printed in the VMWare Console.

I have tried to disable all kinds of acceleration in the VM configuration, changed the SCSI vitual controller type from BusLogic to LSI, but the same issue. I have searched for the functions reported in the call trace, and it seams that calibrate_xor_block is used inside module/driver md, so this must be a virtual hardware issue (disk, cdrom, etc). I have changed the virtual CDrom hardware from IDE to SCSI and now the guest OS can't find the CDRom nor the hard disk, but there is also no kernel panic!. Is there any LSI driver disk that can be used so the virtual SCSI cdrom and hardisk can be accessed?

Does any one has any hint?

Thanks

Mike

Good morning all. I was wondering if there is a way I can connect an .iso file to my host os (win xp pro 64 in this case) so that I can save files dorectly to the .iso. Is there a way I can make the .iso be emulated as either a harddrive, or perhaps turn my 'cd rom' into a cd-rw to where i can just keep 'burning' my RW disc with new software? Thank you for your assistance!

I'm sure this question has been asked, but I have no idea of how to phrase my search.

My issue is this - we have a NAS that's squashing root, the virtual machines reside on an NFS export on said NAS, and the vmware-vmx processes are owned by root.  Even if I choose a non-root user during the vmware-config.pl script, it still runs the processes as root.  When it comes time to spin up the VM, it barks that it doesn't have sufficient privs to the disk (regardless of how I chmod it).  The easy way out is to disable root_squash, but that's not an option.  Is there a place to modify who owns the vmware processes during VM execution?

Thanks in advance.

VMware Server 2.0.1 and latest RHEL5 kernel (both host & guest) = RANDOM REBOOTS !

I have VMware Server 2.0.1 running on CentOS 5.3 (x64 kernel-2.6.18-128.2.1.el5).

Lately I started experiencing random reboots of host and had to investigate it a bit.

At first I suspected hardware problems and specificly RAM corruption. 24h memtest86+ and no errors.

I had my guests migrated to another VMware-server 2.0.1 running on FC11 (2.6.29.6-213.fc11.x86_64).

No more host reboots but the guests (CentOS 5.3 x86 2.6.18-128.2.1.el5) still keep random rebooting.

Had a look at the guest logs and found this:

-

Aug 01 11:08:40.120: Worker#1| Caught signal 6 -- tid 5362

Aug 01 11:08:40.120: Worker#1| SIGNAL: eip 0x369b0332f5 esp 0x7fa1e0b01d88 ebp 0x2

Aug 01 11:08:40.120: Worker#1| SIGNAL: eax 0x0 ebx 0x369b132efe ecx 0xffffffffffffffff edx 0x6 esi 0x14f2 edi 0x14ed

Aug 01 11:08:40.120: Worker#1| r8 0x2c55020 r9 0x3 r10 0x8 r11 0x3206 r12 0xa57c9a000 r13 0x10000 r14 0x284f4d0 r15 0x7fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01D88 : 0x9b034b20 0x00000036 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01D98 : 0x00000000 0x00000000 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DA8 : 0x00000000 0x00000000 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DB8 : 0x00003000 0x00000000 0x9b369e80 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DC8 : 0x00010000 0x00000000 0x9b369e80 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DD8 : 0x00010010 0x00000000 0xe0b01f20 0x00007fa1

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DE8 : 0x00000000 0x00000000 0x9b369ee8 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DF8 : 0x9b077f32 0x00000036 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| Backtrace:

Aug 01 11:08:40.120: Worker#1| Backtrace[0] 00007fa1e0b01830 rip=000000000041521c rbx=0000000000000000 rbp=0000000000415500 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.120: Worker#1| Backtrace[1] 00007fa1e0b01850 rip=0000000000468cf5 rbx=0000000000000080 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.120: Worker#1| Backtrace[2] 00007fa1e0b01940 rip=000000369bc0ee90 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[3] 00007fa1e0b01d88 rip=000000369b0332f5 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[4] 00007fa1e0b01d90 rip=000000369b034b20 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[5] 00007fa1e0b01ec0 rip=000000369b075a50 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[6] 00007fa1e0b01f00 rip=000000000047eb93 rbx=0000000000000000 rbp=0000000002c55020 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[7] 00007fa1e0b01f70 rip=000000000054cc9b rbx=000000000274ebd0 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.120: Worker#1| Backtrace[8] 00007fa1e0b01f90 rip=00000000004f165d rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.120: Worker#1| Backtrace[9] 00007fa1e0b01fe0 rip=00000000004f186c rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000000 r13=00000000027f4244 r14=0000000000edfca0 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace10 00007fa1e0b02010 rip=000000000048542a rbx=0000000000ee0c08 rbp=0000000000000000 r12=00007fff609f6b50 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace11 00007fa1e0b02110 rip=000000369bc0686a rbx=0000000000000000 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace12 00007fa1e0b02220 rip=000000369b0de25d rbx=00007fa1e0b02910 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| SymBacktrace[0] 00007fa1e0b01830 rip=000000000041521c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.120: Worker#1| SymBacktrace[1] 00007fa1e0b01850 rip=0000000000468cf5 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.120: Worker#1| SymBacktrace[2] 00007fa1e0b01940 rip=000000369bc0ee90 in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[3] 00007fa1e0b01d88 rip=000000369b0332f5 in function gsignal in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[4] 00007fa1e0b01d90 rip=000000369b034b20 in function abort in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[5] 00007fa1e0b01ec0 rip=000000369b075a50 in function (null) in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[6] 00007fa1e0b01f00 rip=000000000047eb93 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[7] 00007fa1e0b01f70 rip=000000000054cc9b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[8] 00007fa1e0b01f90 rip=00000000004f165d in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[9] 00007fa1e0b01fe0 rip=00000000004f186c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace10 00007fa1e0b02010 rip=000000000048542a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace11 00007fa1e0b02110 rip=000000369bc0686a in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.121: Worker#1| SymBacktrace12 00007fa1e0b02220 rip=000000369b0de25d in function clone in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| Unexpected signal: 6.

Aug 01 11:08:40.121: Worker#1| Panic: can't get userlevel lock.

Aug 01 11:08:40.121: Worker#1| Core dump limit is 0 KB.

Aug 01 11:08:40.139: Worker#1| Child process 13550 failed to dump core (status 0x6).

Aug 01 11:08:40.139: Worker#1| Backtrace:

Aug 01 11:08:40.139: Worker#1| Backtrace[0] 00007fa1e0b01350 rip=000000000041521c rbx=0000000000000000 rbp=0000000000415500 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[1] 00007fa1e0b01370 rip=00000000004db650 rbx=00007fa1e0b01880 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[2] 00007fa1e0b01850 rip=0000000000468ea8 rbx=00007fa1e0b01880 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[3] 00007fa1e0b01940 rip=000000369bc0ee90 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[4] 00007fa1e0b01d88 rip=000000369b0332f5 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[5] 00007fa1e0b01d90 rip=000000369b034b20 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[6] 00007fa1e0b01ec0 rip=000000369b075a50 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[7] 00007fa1e0b01f00 rip=000000000047eb93 rbx=0000000000000000 rbp=0000000002c55020 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[8] 00007fa1e0b01f70 rip=000000000054cc9b rbx=000000000274ebd0 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.139: Worker#1| Backtrace[9] 00007fa1e0b01f90 rip=00000000004f165d rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.139: Worker#1| Backtrace10 00007fa1e0b01fe0 rip=00000000004f186c rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000000 r13=00000000027f4244 r14=0000000000edfca0 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace11 00007fa1e0b02010 rip=000000000048542a rbx=0000000000ee0c08 rbp=0000000000000000 r12=00007fff609f6b50 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace12 00007fa1e0b02110 rip=000000369bc0686a rbx=0000000000000000 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace13 00007fa1e0b02220 rip=000000369b0de25d rbx=00007fa1e0b02910 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| SymBacktrace[0] 00007fa1e0b01350 rip=000000000041521c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[1] 00007fa1e0b01370 rip=00000000004db650 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[2] 00007fa1e0b01850 rip=0000000000468ea8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[3] 00007fa1e0b01940 rip=000000369bc0ee90 in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[4] 00007fa1e0b01d88 rip=000000369b0332f5 in function gsignal in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[5] 00007fa1e0b01d90 rip=000000369b034b20 in function abort in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[6] 00007fa1e0b01ec0 rip=000000369b075a50 in function (null) in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[7] 00007fa1e0b01f00 rip=000000000047eb93 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[8] 00007fa1e0b01f70 rip=000000000054cc9b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[9] 00007fa1e0b01f90 rip=00000000004f165d in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace10 00007fa1e0b01fe0 rip=00000000004f186c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace11 00007fa1e0b02010 rip=000000000048542a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace12 00007fa1e0b02110 rip=000000369bc0686a in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.139: Worker#1| SymBacktrace13 00007fa1e0b02220 rip=000000369b0de25d in function clone in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| Msg_Post: Error

Aug 01 11:08:40.139: Worker#1| http://msg.log.error.unrecoverable VMware Server unrecoverable error: (Worker#1)

Aug 01 11:08:40.139: Worker#1| Unexpected signal: 6.

Aug 01 11:08:40.139: Worker#1| http://msg.panic.haveLog A log file is available in "/storage/VirtualMachines/srv01.ctg.ee/vmware.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport.windowsOrLinux

Aug 01 11:08:40.139: Worker#1| To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

Aug 01 11:08:40.139: Worker#1| http://msg.panic.response We will respond on the basis of your support entitlement.

Aug 01 11:08:40.221: vmx| VTHREAD watched thread 37 "Worker#1" died

Aug 01 11:08:40.222: vcpu-0| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.320: Worker#13| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.320: Worker#8| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.320: Worker#16| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.321: Worker#3| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#0| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#9| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#2| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#7| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#12| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#15| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#10| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.322: Worker#5| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#14| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.323: Worker#4| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.323: Worker#11| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.324: Worker#6| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.554: mks| VTHREAD watched thread 0 "vmx" died

-

I've looked around and that seems to be quite a common problem here and there?

I am using VMware Server 2.0.1 on HP server with OS RHEL5.

I have two HP servers on same LAN with same subnet. On the first server, I installed VMware, and created a HostOnly interface, then I get vmnet1 as 169.254.64.1. But I found that from the other PC, I can ping 169.254.64.1. As it's a HostOnly interface, how an external server can ping the HostOnly IP? I strongly suspect that's a bug of VMware Server.

After upgrading to firefox 3.6 I can't open up my virtual machine through the browser.

I downgraded to 3.5 and it worked.

This is the message I get:

Cannot access virtual machine console. The request timed out

The attempt to acquire a valid session ticket for * took longer than expected. If this problem persists, contact your system administrator.

Anyone know how to fix this?