Tag Info

Hot answers tagged

17

This VMware guide on virtual to physical machine migrations should be a good start, though it looks like you're required to use 3rd party tools like Sysprep and Symantec Ghost. PlateSpin makes a commercial tool called PowerConvert that does both Physical-to-Virtual and Virtual-to-Physical conversions.


14

You could try Magical Jelly Bean Keyfinder.


13

You require Intel-VT or AMD-V support for your processor in order to run 64-bit Guests. If your processor supports it, it can usually be enabled through the BIOS. If you can't find the option there, chances are it may not be available. Some more reading here


12

We've pushed a Sun X4100 writing over bonded GigE and iSCSI to an Sun X4500 to 280MB/s. There's a lot that can be done to tune the TCP stack on Solaris to help things out, this my my stock tuning config. (take from some collection of Sun whitepapers): $ cat /etc/rc3.d/S99ndd #!/bin/bash NDD=/usr/sbin/ndd $NDD -set /dev/tcp tcp_xmit_hiwat 1048576 $NDD ...


10

vmware converter will be the simplest way to do it. Once you have ESXi built and the vms copied to a location, just launch converter, you will be asked for the source machine then to give it a destination, that will be your ESXi server, then follow the steps, even if the import fails it will not affect your source vm.


9

There is no product called VMWare Server 5.0, the latest version is 2.0.2, perhaps you mean VMWare's vSphere/ESXi 5.0? If so then no, there's no support yet as Server 2012 isn't released yet (we don't generally deal with unreleased code on serverfault either by the way), but I know that once Server 2012 is released vSphere/ESXi 5.1 will support it within ...


8

I have seen this behaviour when I assign too much memory to the VM's. When I start a VM that grabs memory from the host OS above some threshold, everything dies except for the hard drive LED. It takes an age just to shut down the VM. Fine-tuning the memory footprint of the VM's has done wonders for me.


8

In the VMWare Server GUI, select host in the "Inventory" panel (root node of the tree), to the right "Commands" panel should appear with "Edit Virtual Machine Startup/Shutdown Settings". There will be an option to autostart the guest VM.


8

You don't say what load you expect from the Intranet app. I'm guessing that unless yours is a huge company the Intranet app won't be that big a load. In that case the key target is managability. If so, I would use two Hyper-V VMs. You can put them on the same physical server to start with, and if the load becomes too great put each VM on it's own server. ...


8

Starting a land-war in Asia Inventing the hoola-hoop Trying to VM inside a VM All bad ideas


7

If you're referring to VMware Server as detailed here: http://www.vmware.com/products/server then the answer is yes. You might also try ESXi: http://www.vmware.com/products/esxi/


7

VirtualBox. I've found it to be the most lightweight for home use. You're right about ESXi, the hardware requirements are specific. I'm not a big fan of what VMware did for management of server 2.x either despite my love of them in the enterprise.


7

If you are planning on buying hardware to do this, then it is quite possible to buy hardware that will run ESXi, quite cheaply (I did it a couple of weeks ago). There are a number of sites out there that deal with what whiebox configurations work with ESXi such as Ultimate Whitebox If you have a machine that has enough resources any of these options should ...


7

You must upgrade vCenter to 5.1 in order to add a host with ESXi 5.1. No vCenter version prior to 5.1 supports ESXi 5.1. References Add an ESXI 5.1 host in vcenter server 5.0 [VMWare Communities] VMWare Product Interoperability Matrix [VMWare Compatibility Guide]


6

VMWare outlines this very clearly, as you've noted. Download new ISO containing the ESXi 5.1 distribution. Burn it to CD. Insert into your powered-off server, boot and run the installer. This method preserves your existing VMFS datastore and works without a hitch. Trying to move your VM's off, exporting and all of that other stuff introduces many more ...


6

This is unfortunate. The version of the software you're using and the age of the hardware you're using are old enough that it's difficult to give proper assistance and support... Sure, your partitioning plan is fine, but the larger problem is that you're deploying anew on antiquated equipment with end-of-life software. It is time to plan for an upgrade. ...


6

You're constrained to what the 32bit host can see. Even with PAE, a single process can only use ~3GB of RAM, so your guest(s) will be limited to that.


6

Yes it is, as long as you are not using Bare-Metal hypervisors you can run many side-by-side. But I hope you have very, very, very solid hard drives because the IO will be off the charts.


6

It sounds like something is seriously wrong with your setup because there's just no way it should take 40 minutes for a couple of VMs to boot. If disk I/O is an issue your best bet is to add drives and dedicate a drive (or RAID array) to each VM.


6

What Mikael said but I would sysprep the image so you get a unique SID if you are involved with a domain. Then it will be real easy to just copy the image, deal with the networking ids, then run though just a few steps depending on how you sysprep the image.


5

I dont have much experience with the MS SQL Express Databases on virtual machines but I think you just ran into the hardware restrictions of the MS SQL Express Edition. I assume that your physical server had 1 cpu with 2 cores. The MS SQL Express 2008 (and I think 2005 also) do support only ONE phyisical cpu but mulitple cores. A VM recognizes each vCPU's ...


5

It's very stable on RedHat variants.


5

Booting two VMs from the same hard drive will cause drive thrashing (the heads jumping from place to place, consuming more time than actually reading data), especially if the host OS is on the same drive. Boot them separately to avoid this thrashing, and your total boot time will be lower. I always try to put my VMs on separate drives and then do not ...


5

Short answer that glosses over the details; VMware will usually provide a unique MAC address for a VM on a network. It will usually provide the same MAC address to a VM so long as the VM is not moved between hosts. In circumstances where this a changing mac address is a problem, you can manually set one. To manually assign an address, edit the config file ...


5

(Please don't do it!) This is possible and can work with certain modifications, but do you have any option to use the VMWare ESXi hypervisor instead? The VMWare Server product is end-of-life as of June 2011, and would be a poor platform for any new deployments. There are a few alternatives listed at the VMWare forums, but you may want to look into ...


5

Creating two symlinks will fix your problem: ln -s /lib/modules/2.6.35-22-generic/build/include/generated/utsrelease.h /lib/modules/2.6.35-22-generic/build/include/linux/utsrelease.h ln -s /lib/modules/2.6.35-22-generic/build/include/generated/autoconf.h /lib/modules/2.6.35-22-generic/build/include/linux/autoconf.h I found the solution on it-psycho.de and ...


5

Just like it says, there is not enough video RAM available in that VM to use the 2560x1600 resolution and you are limited to 1176x885 as maximum resolution. If you want to increase the memory size of that VM's video ram then follow these instructions: To increase the svga.vramSize setting: Power off the virtual machine. Right-click on the virtual machine ...


5

Can you specify whether the unreachable host is a VMWare ESX 3.5 host or a VMWare ESXi 3.5 host? Both exist, and the approach to resolving this issue is slightly different. Let's assume it's an ESXi 3.5 host... Connect to the console of the server or use a keyboard/monitor. Press "F2" and enter your password. You can use the "Restart Management Agents" ...


4

It's possible to run Server 2012 on ESXi5.0 although it's not supported yet. VMWare even has KB entry for this problem: Change the virtual machine to use EFI instead of BIOS. Right-click the virtual machine and click Power > Shut Down Guest. Right-click the virtual machine and click Edit Settings. Click the Options tab. Click Boot Options. Click EFI ...


4

Oh, easy. Don't install new instances of VMWare server, and migrate off any VMWare Server instances you do have now. In January 2010, VMware announced the End of Support for VMware Server with support ending on June 30, 2011. Users are free to continue using VMware Server but are recommended to migrate to another VMware offering to gain the benefits of ...



Only top voted, non community-wiki answers of a minimum length are eligible