I've been looking into enabling audio recording in VMware View Desktops. This would be useful as it would allow the use of applications such as Skype and TeamSpeak within VMware View published desktops.
By default, the VMware View Agent which is installed within the desktop operating system installs the VMware Virtual Audio Driver. The VMware Virtual Audio Driver enables audio playback from the View Desktop to be played through the VMware View Client. However, the VMware Virtual Audio Driver does not enable analog audio input from the View Client to the View desktop. With the VMware Virtual Audio Driver, audio recording within the View Desktop from an audio source connected to the View Client, such as a microphone, is not possible and applications that rely on Audio input will not function correctly.
In ESX 3.5, when trying to create a new snapshot, the following error is reported in the VI Client:
An invalid snapshot configuration was detected
Also, when reading the Virtual Machine log file (vmware.log) located in the same location as the VM, you may find references to delta files such as "vm_name-000001.vmdk", but when browsing the datastore, the delta file does not exists. Also, when running vmware-cmd hassnapshot, "hassnapshot ()= " is returned, which means that the VM has no snapshots in place.
If this is truly the case, why is "An invalid snapshot configuration was detected" returned when trying to create a new snapshot?
VMware records snapshot information about the current VM in a .vmsd file. This file is located with the rest of the virtual machine configuration and VMDK files on the datastore. The file is normally called .vmsd. This file will contain information, even if your VM has no snapshots in place.
It is possible that in some cases, ESX fails to properly clean up after previous snapshots were removed. The information for previous snapshots may still be recorded in the .vmsd file. The file may indicate that you still have snapshots in pace, although all previous snapshots were removed and the dalta files have been merged. When you then try to create a snapshot, the .vmsd file will inform the ESX host that there is a delta file in place and that it has to create a second or third delta file. When the ESX host interigates the VMFS file system, it's unable to find the snapshot delta files specified in the .vmsd file and therefore errors with "an invalid snapshot configuration was detected."
I've been told about a flash video that demonstrates some of the features included in Citrix XenServer. Some of the features look very handy indeed. But, will it be good enough to give VMware a good run for their money? Well, unfortunately I am not in a position to comment on that, as I've never touched XenServer before.
Anyway, have a look at the flash video