VMware Communities: Message List - VMware Server Windows 2003 Guest OS SCSI Driver

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 19:40:58 GMT

Thanks everyone for the info, I will report and new finding tomorrow.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

Peter_vm — Thu, 18 Oct 2007 19:37:02 GMT

You are yet to see more "odd" things if you are new to virtualized systems.
Keep in mind that VMs live in short bursts, and their virtual devices do not behave the same as the physical ones. The biggest difference is that they need host CPU for their functions. It can be seen especially for virtual NICs, mass storage controllers and video.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 19:24:57 GMT

I will make those modifications tonight and see what I get.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 19:24:57 GMT

Yes I guess ping is my only benchmark I have been looking at. Compared to physical machines which never change in response time I find it odd the variation in ping response time with VMware virtual machines.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

rsa911 — Thu, 18 Oct 2007 19:22:02 GMT

One is a sql database and the other is the main file server

for your file server, I would assign a single vcpu and max 1gb of ram
3gb of ram is overkill for a dedicated file server

SQL is another story, 3gb of ram and two vcpus are typical for a loaded SQL machine, you did not specified how many DB , DB average size and concurrent users you're expecting...

start by reducing the resources allocated to your file server and see if it brings any improvment

Re: VMware Server Windows 2003 Guest OS SCSI Driver

Peter_vm — Thu, 18 Oct 2007 19:20:01 GMT

Is it a ping issue alone? I would consider that behavior rather normal. When I open a network share and start copying I see this:

Reply from 10.0.0.1: bytes=32 time=19ms TTL=128
Reply from 10.0.0.1: bytes=32 time=2ms TTL=128
Reply from 10.0.0.1: bytes=32 time=3ms TTL=128
Reply from 10.0.0.1: bytes=32 time=2ms TTL=128
Reply from 10.0.0.1: bytes=32 time=7ms TTL=128
Reply from 10.0.0.1: bytes=32 time=3ms TTL=128
Reply from 10.0.0.1: bytes=32 time<1ms TTL=128
Reply from 10.0.0.1: bytes=32 time<1ms TTL=128
Reply from 10.0.0.1: bytes=32 time<1ms TTL=128
Reply from 10.0.0.1: bytes=32 time=1ms TTL=128
Reply from 10.0.0.1: bytes=32 time=3ms TTL=128
Reply from 10.0.0.1: bytes=32 time=2ms TTL=128
Reply from 10.0.0.1: bytes=32 time=7ms TTL=128

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 19:08:57 GMT

I tried they config file additions but with no luck. My next thought is to update the scsi drivers on the local host hardware.

Other than that I thought about upgrading the host to 64bit from 32 bit, would that help any?

Re: VMware Server Windows 2003 Guest OS SCSI Driver

Peter_vm — Thu, 18 Oct 2007 17:08:14 GMT

It was explained already:
http://sanbarrow.com/vmx/vmx-config-ini.html

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 16:49:58 GMT

Thank you but can you explain what they do first?

Thanks,
Chris

Re: VMware Server Windows 2003 Guest OS SCSI Driver

Peter_vm — Thu, 18 Oct 2007 16:47:51 GMT

C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini

prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100"

your-guest.vmx

MemAllowAutoScaleDown = "FALSE"
sched.mem.pshare.enable = "FALSE"
mainMem.useNamedFile = "FALSE"
MemTrimRate = "0"

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 16:21:57 GMT

Could you send mem optimzation settings to define in the global .ini file incase I don't get to it until later tonight?

Thanks,
Chris

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 16:11:57 GMT

Thanks for the replies everyone,

I have tried reserving the ram but with the same end result.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

boydd — Thu, 18 Oct 2007 15:52:24 GMT

Under the host properties in the VS console - how do you have the memory allocation set? I would reserve the RAM needed for the vm's.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 15:36:58 GMT

One is a sql database and the other is the main file server, not sure how to judge how much ram or cpu I need, just thought the more the better.

What will the mainMem.usedNamedFile do?

I see I also have a line left in the config file: buslogic.noDriver = "FALSE"

Should that be removed?

Thanks,
Chris

Re: VMware Server Windows 2003 Guest OS SCSI Driver

rsa911 — Thu, 18 Oct 2007 15:09:50 GMT

do you really need 3 gb of ram and two vcpus per VM ?

if not I would decrease the amount of ram allocated to the real needs of your VMs..

anyway, for such large amount of ram allocated to your VMs, you will want to add this to both VMs .vmx file:

mainMem.useNamedFile = "FALSE"

(power off the VM before editing the file)

if it brings up back perf, report back, I'll send you a list of mem optimzation settings to define in the global .ini file

Re: VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 15:02:59 GMT

One this worth mentioning is when I converted these two machines to Virtual machines they converted with a Buslogic controller. I follow a posting to switch to LSI Driver basically by switching to LSI in the VMX file and saying yes to the warning message on Boot up.

Here is the config file for the first server:

config.version = "8"
virtualHW.version = "4"
memsize = "3000"
MemAllowAutoScaleDown = "FALSE"
MemTrimRate = "0"
displayName = "Database"
guestOS = "winnetstandard"
tools.remindInstall = "FALSE"
floppy0.present = "FALSE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
usb.present = "FALSE"
sound.present = "FALSE"
sound.virtualDev = "es1371"
sound.filename = "-1"
sound.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "custom"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Database.vmdk"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "Database (2).vmdk"
ide0:0.present = "FALSE"
ide0:0.autodetect = "TRUE"
ide0:0.filename = "auto detect"
ide0:0.deviceType = "cdrom-raw"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
buslogic.noDriver = "FALSE"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
tools.syncTime = "TRUE"
ethernet0.generatedAddressOffset = "0"

numvcpus = "2"
autostop = "softpoweroff"
workingDir = "."

scsi0:0.redo = ""
scsi0:1.redo = ""
ide0:0.startConnected = "TRUE"
ethernet0.generatedAddress = "00:0c:29:00:ca:4d"
uuid.location = "56 4d c8 aa 53 98 84 f1-af d6 93 9a a2 00 ca 4d"
uuid.bios = "56 4d c8 aa 53 98 84 f1-af d6 93 9a a2 00 ca 4d"

Ethernet0.vnet = "VMnet0"

scsi1.virtualDev = "lsilogic"
scsi1.present = "TRUE"

Here is the config file for the second:

config.version = "8"
virtualHW.version = "4"
memsize = "3000"
MemAllowAutoScaleDown = "FALSE"
MemTrimRate = "0"
displayName = "LCKFILENAP"
guestOS = "winnetstandard"
tools.remindInstall = "FALSE"
floppy0.present = "FALSE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
usb.present = "TRUE"
sound.present = "FALSE"
sound.virtualDev = "es1371"
sound.filename = "-1"
sound.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "custom"
scsi0:0.present = "FALSE"
scsi0:0.fileName = "LCKFILENAP.vmdk"
ide0:0.present = "TRUE"
ide0:0.autodetect = "FALSE"
ide0:0.filename = "D:"
ide0:0.deviceType = "cdrom-raw"
ide0:1.present = "FALSE"
ide0:1.autodetect = "TRUE"
ide0:1.filename = "auto detect"
ide0:1.deviceType = "cdrom-raw"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
buslogic.noDriver = "FALSE"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
tools.syncTime = "FALSE"
ethernet0.generatedAddressOffset = "0"

workingDir = "."

numvcpus = "2"
Ethernet0.vnet = "VMnet4"
autostop = "softpoweroff"

scsi0:0.redo = ""
ide0:0.startConnected = "FALSE"
ethernet0.generatedAddress = "00:0c:29:59:89:53"
uuid.location = "56 4d 9c c7 0c 5c 7c f4-44 71 db 25 e7 59 89 53"
uuid.bios = "56 4d 9c c7 0c 5c 7c f4-44 71 db 25 e7 59 89 53"
gui.exitOnCLIHLT = "TRUE"

scsi0:2.present = "TRUE"
scsi0:2.fileName = "LCKFILENAP.vmdk"

scsi0:2.redo = ""

Thanks,
Chris

Re: VMware Server Windows 2003 Guest OS SCSI Driver

Peter_vm — Thu, 18 Oct 2007 15:01:43 GMT

Try to create new VM from the scratch to see if it exhibits the same issue.

Re: VMware Server Windows 2003 Guest OS SCSI Driver

rsa911 — Thu, 18 Oct 2007 14:55:24 GMT

Chris,

don't change your VM drivers, the LSI logic driver is fine

the guest VM only sees virtual scsi controller emulated by vmware, it has no idea of your host SAS Raid

can you post your VM(s) config files ? (it's the .vmx file)

VMware Server Windows 2003 Guest OS SCSI Driver

cwitthoft — Thu, 18 Oct 2007 14:40:13 GMT

I have a Dell Poweredge 2950. This machine has (2) quad core processors, 8 gigs of ram, (2) dual port gigabit NIC's, and Windows 2003 R2 Enterprise Edition for the Host OS. I recently uninstalled Microsoft's Virtual Server 2005 R2 and Installed VMware Server. I used VMware's converter to convert my two Virtual Machines to VMware.

The C: drive on this host is (2) 70gig 15k disks in a raid 1 config. My E: drive is (6) 70 gig 15k disks in a raid 10 config. My VMware machines are stored on the E: drive. It has a SAS Raid Perc5/i Controller.

I have gave 2.5 gig of ram to one VM and 3gigs to the other VM. I have already stripped uneeded components such as audio, cdrom ect. I'm currently running 1 VM with 2 processors and the other VM with 1. Each VM has its own Bridged Network Adapter.

My problem is performance of these virtual machines is very spuratic. I noticed anytime I access a VM and put a load on it, (open a file share) my ping response will jump from >1 to >4 or so, I think its a disk issue since its only when I put load on it. I'm running the defualt LSI Logic driver that was installed by default and have even tried the LSI Logic 1020/1030 Ultra 320 SCSI Adapter driver I found on VMware's site for the esx server but still the same problem. Do I need to load a non raid controller SAS Driver from Dell in the Guest OS?

Thanks,

Chris