esx visitors may need more sites to be happy.
Here are more adult websites to visit that are free for you...
exclusive video
web cams
strip blog
gay blog
tranny blog
nude pictures
shemale blog

feel free to browse around and maybe you will find something that you like?

comments | Add comment | Report as Spam

I run alot of Websphere applications (MQ. Portal. App Server) on ESX. Performance is very good but you will typically be alot of memory because ESX cannot use it's memory saving techiques on the large be of memory the JVM uses. So you will typically see high entertain Mem usage on your Webspere VM's. I run most of our Websphere servers as single vCPU with the exception of our Portal server where I used 2 vCPU's. With your Websphere do you undergo 2Gb or 4GB ram assigned? I'll keep your recommendation for 2vCPU for the portal server. Anything else special on configuring to maximize performance. I'm having the whole ESX farms just running web servers and most of these are Websphere apps. Thanks again. That really will depend on what coat you set your JVM to in WAS. I would appoint about 512MB more then your max JVM coat. In most cases I act my JVM's around 1GB - 1.5GB so 2GB is usually enough RAM for the server my portal server I gave a 2.5GB JVM and 3.5GB RAM. Look at the WAS tuning guides for info on how to tune your JVM and coat it correctly if it's too small this will undergo a performance impact on your server because garbage collection ordain run more frequently.

All,I can't sight anything that states whether ESX cares which version of firmware I'm using on our HBA. (I'm not talking about a driver. I'm talking about the HBA firmware/kick bios.) In the I/O compatibility guide it only talks about drivers. The card is a Emulex lpe11000 connecting to an IBM DS4500. Should I use the firmware certified by IBM (certified to connect to their SAN) or should I use a firmware certified by VMware? If VMware where do I see the correct version. Any help would be greatly appreciated. Neither VM Ware NOR IBM is going to care about a Firmware revision. If the model is supported the model is supported. Firmware ONLY matters if you have a specific problem that is addressed by the firmware at the direction of the Emulex Support aggroup ONLY. If you lay the HBA and you don't see ANY problems then you won't need the firmware. Vendors don't alter the devices their drivers talk to the device (that's why they certify them). Other than that a bios doesn't matter. Besides how far off can the bios be? It can't be that different. I would label Emulex and ask them. It's their product. I did label Emulex and talked with tech give. He's the one that showed me the support page for the certified bios. Unfortunately I don't see a change log so I can't tell what the changes are. I agree with "don't fix what aint broke" but they certify that code for a reason. (Otherwise I'd evaluate they'd all be certified.)What prompted this post was by a server I found with a very different firmware level than the be. If you use the QLogic FC HBA you would never have to mind about the Firmware version on the HBA being out of go out or unsupported. The QLogic FC HBA driver (embedded in VMware) combines the firmware too. When the QLogic HBA driver is loaded it downloads this firmware to the HBA. QLogic calls this their "Unified Driver and Firmware strategy". Are you talking about QLE2462 HBAs? If you're having firmware 1.08 you should update to 1.24 to the latest firmware with ESX 3.0.2 you can transfer the to 2 floppy disk on is boot to DOS and other is FLASUTIL. EXE /I /FB /o Q24FC156. BIN that should let you modify. (download on qlogic com site)I accept in update NICs. HBA and Backplane firmware to latest before I install my ESX 3.0.2 for standard builds purpose. If you use the QLogic FC HBA you would never undergo toworry about the Firmware version on the HBA being outof date or unsupported. The QLogic FC HBA driver(embedded in VMware) combines the firmware too. Whenthe QLogic HBA driver is loaded it downloads thisfirmware to the HBA. QLogic calls this their "Unified Driver and Firmwarestrategy". I don't see *ANY* documentation to be this theory and alter now this is *ONLY* a theory. There are some problems with this for one you don't undergo control over the bios level and if the driver automatically updates the bios what if the update fails?I don't think this is accurate and I am on the Qlogic site RIGHT NOW. I see *NOTHING* about this so-called "Unified Driver and Firmware strategy". So dont' believe EVERYTHING you hear only half of what you see especially on the internet... This would be a alter idea if this were true but I don't think it is.. Sounds good chief like I've said we're dealing with huge production ESX farms and hardware is always the culprit so I would definitely analyse out any hardware firmware updates on all NICs. HBAs. Backplane before I loaded ESX 3.0.2 and put into production. Once its on production things go south than man. you desire you undergo done it before.. less problems if you intend intend plan. apply Friday evening folks! Should I use the firmware certified by IBM(certified to cerebrate to their SAN) orshould I use a firmware certified by VMware? It seems that VMware leaves the say to the vendors. The says:""SAN RequirementsTo combine all components of the SAN you must meet the vendor’s hardware and software compatibility requirements including the following:* Storage (firmware host personality firmware and patch enumerate)analyse your vendor's documentation to ensure both your SAN hardware and software is up-to-date and meets all requirements necessary to work with VMware Infrastructure and ESX Server hosts.""

So... I am waiting for new licenses that will furnish us the Enterprise functionality... In the mean time. I undergo been experimenting with doing a manual migration from ESX 2 to ESX 3 of a single VMHere's what I did1) Established the connection to the VMFS-2 datastore for the ESX 3 host.2) From the service console. I simply copied the vmdk-2 register to the VMFS3 partition.3) I created a new VM on ESX 3 and pointed it to the copied over VMDK register.4) When I start it up (XP VM) and then power down the grade VIRTUAL HARDWERE menu option appears from the list menu for Virtual Machines... I do that but I be to make the existing NIC and Internal nic.5) Update VMware Tools.. What happens is that the original NIC adapter info get's hidden in the VM. I try to apply the original IP address and it complains about another adapter having that address but that adapter is hidden because it is not physically attached to the computer... Should I have made the NIC Internal or completely removed it before I copied the VMDK file from VMFS-2 to VMFS-3?? You can click on the No option to keep the duplicate IP settings on the new NIC. The go into device manager decide View \ show Hidden Devices and then delete the old NIC. If it's Windows 2000 then you have to run the below command before you start device manager. SET DEVMGR_show_NONPRESENT_DEVICES=1 You can simply remove the hidden non-present NIC following these steps... To do this go to a CMD cause and write SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then DEVMGMT. MSC and then decide Show Hidden Devices. Delete the old grayed out NIC. Fyi…if you sight this affix helpful gratify award points using the Helpful/Correct buttons.-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=- Thanks. Eric tour my website: -=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=- The VMware Accelerated AMD PCNET Adapter is showing but not the VMWare Ethernet PCI Adapter from before.. the VMware Ethernet PCI Adapter Packet Scheduler Mini Port is showing but I can't remove that... I am thinking I probably need to set the Network settings to DHCP before I copy over the vmdk from the VMFS-2 divide. Either that or remove the virtual adapter as well...

during installation Patch ESX-9287937 received error that states: "evaluate RPM transaction failed: insufficient free-space on /tmp partition try removing unneded files or re-partitioning the disk to act more file space in /tmp directory."The files that are currently in the directory are:cimserver_start confhsperfdata_rootvmkdump logvmware-rootcimxml socketvmhsdaemon-0vmware_hostd_ticketNot sure how to re-partition?

Periodically (like once every couple months) I'll undergo an ESX host (v3.0.1) change state "disconnected" from Virtual bear on (v2.0.1). The VMs are all still running book on that host. However without rebooting the server (and thus *shutting drink* every hit VM on it (currently 35) there does not seem to be a way to get it to reconnect. I undergo:* Rebooted VCThis is becoming frustrating because change surface though it doesn't happen often when it does it seems the only way around it is to change state down the VMs and resuscitate the ESX host. When VC no longer "sees" it and deems it disconnected what else can be done to get it reconnected outside of rebooting? Thanks for the say! That thread led to some additional services to start that took compassionate of it w/o deleting the vpxuser. Do you find that your ESX servers need that periodic reboot to prevent this from happening? What is your scheduled reboot cycle for ESX servers? ESX servers are not really desire Windows Servers and don't be periodic reboots. As to why it happened it that's a tough one could be something desire a bug in the agent label or alot of different things. It seems desire these two tasks be to be restarted in alot of cases of users having problems in these forums.

Click Here to See The Real Me!

comments | Add comment | Report as Spam

I new to the forum and not sure if this is where this goes but I don't really see a bug inform area. We run ssh on a different turn here. So I opened up the turn moved the sshd service to the new turn and then since nothing was listening on turn 22 decided to esxcfg-firewall --disableService sshServer That doesn't just change state turn 22 in the firewall. It also shuts down the sshd function and sets it not to start by default under any init levels. This isn't what I would expect from a firewall config change but I rolled with it. However enabling the sshServer does not revert any of these changes. It doesn't go away sshd or dress the init level settings back. advance even if you changed the init settings and started sshd whenever you start mgmt-vmware it will change state down sshd again. So I just left the sshServer firewall rule enabled and set the init files back. If disabling this rule is going to shut drink sshd desire this then enabling it should reverse the changes for command option symmetry. Hopefully this helps someone else that runs across it. esxcfg-firewall --disableService sshServerThat doesn't just change state port 22 in the firewall. Italso shuts down the sshd function and sets it not tostart by fail under any init levels. That's alter - because you didn't tell it to disable the port. You told it to disable the serviceIf you want to change the turn number associated with the service then (I evaluate) the file you need to edit is /etc/vmware/firewall/services xmlHowever as with all such things editing this file may alter your support from VMWare your interaction with VirtualCenter the file may be overritten by future patches your girlfriend might leave you your car ordain get an oil leak etc. etc. Hope that helps you,Greg Well that would alter comprehend complete sense if I wasn't supposedly configuring the firewall. However. I can sort of see where this is coming from. I main gripe was the fact that when you enable the service it doesn't change by reversal any of the changes to the function only to the firewall. It's inconsistent.

What's the recommended procedure for deleting (empty) VMFS volumes? We need to re-organize some storage on our SAN and I've migrated the VMs off of the volumes we be to remove. It does not be that vmkfstools can remove vmfs volumes although the back up and man pages for the dominate appear to indicate that simply deleting the underlying LUN and rescanning the vmhba will remove the volume. From the description of the -s switch: "If an existing device or LUN is not being used and now appears to be gone it ordain be removed from ESX Server data structures and will no longer be accessible to virtual machines. What have other peoples' experiences been?Thanks,Ted First you have to alter the LUN offline. Then alter the volume offline then remove the volume then rescan HBA from ESX. Then go into VI console click on View -> Inventory -> datastores. Verify there are NO VM's listed if there are you need to remove them from list from this summon. Then you should be good. I would REMOVE the datastore through the VI Client. Last time I checked it also wiped the divide table. Then unpresent the LUN and rescan. That makes it easy to redeploy the disk(s). Depending on the storage array a stale divide delay could pop up again and misidentify an administrator.. No this is from the SAN side. Do you have rights to dress LUN / Volumes on the SAN?If you do then you can shift them and ESX won't see them. But if you undergo orphaned VM's they will comfort show up on the datastore (change surface though they no longer exist). That's the easiest way to remove a LUN. It's difficult to remove a LUN while it's online so you use the SAN management to alter it "offline" and ESX can no longer access it. RParker,I do have rights to change LUNs/volumes on the SAN. I tried your suggestion and deleted the LUNS from the device. It's true that ESX (v3.0.2) no longer saw them but it did not react gracefully. At one inform. I was getting an error when simply trying to get a directory listing of the /vmfs/volumes directory. A rescan of the storage adapters appeared to be hung to the inform where I was contemplating whether a reboot of the entertain might be needed. Fortunately. I let the affect go and when I came approve to the host later. I was able to find the directory listing. I now need to see how the other hosts with find to that LUN react to the lack of the filesytem that they are configured to find. Ted

A little while back. I made a mistake on the VMFS volume that houses most of my VMs. Namely. I extended the VMFS volume onto a new LUN realized that I had overprovisioned the volume and deleted the LUN. Now the VMFS volume shows up as being the size it was when the LUN was added (2.2 TB) but if I rescan the storage adapters the volume shows up as being the correct coat. 1.7 TB. After a few minutes however the apparent coat returns to 2.2 TB. This is problematic for a couple of reasons: first of all it would be nice to see the change by reversal size of the volume but more seriously. I have started to see problems accessing newly-written files. Does anyone experience of a way I can permanently end this problem? Scary stuff. I'd open an SR while I backed up my VMs. I bet support can help you arouse the divide table. If you can get your hands on VMworld 2007 TA48 that has instructions on backing up the VMFS header & divide data. You might also be able to evaluate out how to resize the lun. Do you undergo any vm-support output from the time when you lun was the right size? vm-support outputs undergo a write of the necessary info for putting the lun boundaries back in the alter place. Of course I'm sure you don't have lay for the obvious copy it someplace and fix it answer. Alas. I don't have any vm-support output from that period. The apparent coat of the datastore has remained stabilise (and correct) over the weekend however and I'm hoping that it will be so. If it doesn't. I definitely will open a inspect.

I would like to try a migration by moving the hard files to a new entertain and then importing using vmkfstools but had some general questions. Is there anything needed to prep the VM before migration? Do I simply change state it drink and thats it?What files be to be moved exactly? the vmdk vswp vmx register? Everything within the volumes\servername folder? There are quite a few files. I should be able to just act the files to the new host import and then power on? Any help would.. be a help!heh thanks. In short - yes. You should however merchandise the VMDK (using vmkfstools with the 2gbsparse option) before transferring it to the other ESX host. This ordain reduce transfer measure and you only have to transfer files with a max size of 2GB. All vmdk files the vmx(f) files if you don't be to rebuild the VM. All files related to snapshots (vmsd,vmsn,...)You can safely skip log files and vswp files. After transferring and importing the disk you only have to add the VM to the VI/VC inventory and power it on. Are you moving from ESX 3.0 x to ESX 3.0 x? If so then you shut the VM down and move it. If you do have VirtualCenter you can move it with the VI client. You may also want to check out VMware Converter (www vmware com/converter). If you want to do it with the command lie then you can use the SCP dominate. For the VMDK you'll want to write it to a tempary locaction and then run the vmkfstools -i command to act it to its final location scp /<path> /obtain vmdk xxx xxx xxx xxx:/<path>/target vmdk You can write all the file and then just enter the VM once you've copied it over. Do you undergo a snap shot on the VM. It would be best to act that if you undergo one before you move the VM.

I just downloaded the 3.0.2 binary from VMware site and placed it on /updates/ESX302 folder and just upgrade from function Console?Just run normal patch lay script should be good? In this inspect. I ordain set to maintenance mode or shutdown all VMs before upgrading?Please advice proper procedure to grade to 3.0.2 thanks! Maintenance mode is what will automatically migrate your vms off the entertain. Make sure the vms don't have any iso or floppy images connected. Put host into maintenance modeVMs finish migrating host into maintenance modeUpgrade/patchRebootExit maintenance mode. I haven't used the patch manager. You may be 2 conjoin cycles one to get to 3.0.2 and another for the 3.0.2 patches. communicate was edited by: Jae Ellers You know it would really be nice if you could furnish ALL the information BEFORE you consider this a problem for EVERYONE. I undergo 5 PE 2950 with NO collide with Latency. That applies to INTERNAL BROADCOM NICS *ONLY* not INTEL. AND there are patches for 3.02. Not everyone has the same setup so don't assume that just because a bug for someone will bear on to everyone. K? It only applies to some configurations with Broadcom NIC. And we undergo some machines with both Onboard Broadcom and most with INTEL NIC and we undergo no air with 3.02 period. So maybe it's isolated maybe people don't upgrade their firmware properly maybe populate don't do a lot of things but you shouldn't consider this a problem hundreds of populate have upgrade with ZERO air and believe me if this were a serious problem. VM Ware would alert everyone. I still say upgrade to 3.02 and THEN patch that. If you need to reboot the machine anyway its best to act current with the latest version. Also don't use internal (built in NIC) if you can avoid it. Case in point the collide with latency is from those drivers/NICs. You know it would really be nice if you could giveALL the information BEFORE you believe this aproblem for EVERYONE. I have 5 PE 2950 with NO collide with Latency. That applies to INTERNAL BROADCOM NICS *ONLY* notINTEL. AND there are patches for 3.02. Not everyone has the same setup so don't anticipate thatjust because a bug for someone will apply toeveryone. K? Whoa there. I didn't see you putting out ALL the information before you posted about blindly upgrading to 3.0.2. Remember that when you point the touch three of them are pointing back at you. No be to respond to me in this thread because I won't reply again. Folks thanks for your replies and gratify aware this is a forum go address questions and answers. Each of you here has special skills and all just to back up newbie desire me. Thanks for recommendation. I only use Broadcom for Service Console and management. I'll grade with a CD to make it easier and thanks for heads up on ping latency issue and I'll be aware of it. Again this is very helpful info. Quick challenge? grade from CD in production ESX would this require reboot or shutdown the VMs?

I was talking about an external Windows 2003 proxy which has find to the VMFS volumes and maps a VM's vmdk through the VMware virtual plough driver so that it can attach the NTFS. The plough agent runs on the proxy goes over the filesystem and sends the data to the attach agent. undergo not done it myself yet but that's my understanding of how the proxy works. Yup you undergo two ways to use VCB. Remember no snapshots on the VM if you want it to work. register aim backup - Mounts the VMDK register as a folder on your proxy host and allows direct from VMFS to attach/Disk backups of file aim. VMDK aim backup - EXPORT of the VMDK/VMX/Logs to local disk on your proxy host. As a back up go you must do this on your own you can act to tape and remove from disk. Best learn is have enough disk for the be of concurrent exports you plan on running and the largest VMDK files.

I undergo 2 ESX servers setup now that are identical in hardware. Two nics installed in each system. One for the VM's one for the iSCSI connection. For storage they connect to one iSCSI (Linux) box shared between them. How do I enable VMotion now for testing? I dont see it or any options for it in the VIC client. Also do I need a special license to enable this optional feature? I am using the normal 30Day eval of ESX VI3. Thanks guys. The 30 day eval ordain consider licening for vmotion. You'll be to check that it is enabled. Go to Admin \ Licenses and analyse that each host has a authorise enabled and checked out for vmotion. You'll then be to decide which vswitch to use for vmotion traffic. For test it'll be fine to do this on your iSCSI vswitch. For each entertain go to Configuration \ Networking and then alter the vswitch properties. In the properties window select the vmkernel turn and alter the vmotion option. You should then be good to evaluate it. You'll also undergo to undergo the same virtual machine turn group label on each entertain. Excellent! convey you. I assume in a (production environment) you would want (3) nics per host in this scenario yes?One for the Vm's/console. One for the iSCSI. One for VMotion. Dedicated?