Cyrille Moureaux wrote:
> If we encounter an error while trying to get the recommendation, we log
it, and that generates that stack. It shouldn't, however, impact the
actual startup of the machine, especially considering that you only have
one host in your cluster to begin with. I'm a bit surprised, though,
that your cluster object doesn't support the command we're trying to
use, I thought this to be a basic feature of the VC. May I ask which
versions of Virtual Center and ESX you're using for your host?
ESX 3.0.1 - 35804
VC 2.0.1 - 33643
Regardless of this, these errors shouldn't prevent you from working, you
may need to have a couple more machines in your pool to avoid the first
one (depends on your usage of the system), and if you're satisfied that
the system works and just want to avoid having your log fill up, you can
lower the log level to INFO for instance (in vda.properties. property
General.LogLevel), which would stop the logging of such errors. Note
that you'll need to restart the VDA service for this change to take
effect, and that you won't see other errors either after it, though.
Thanks for the feedback, we'll definitely try to get rid of that first
exception in future versions.
Not really an issue, especially for a test/demo. But it's something I'm
sure I will eventually asked about.
There's only one important feature I can't seem to get working, I
realize this is an ESX issue but maybe you will have some insight. I
can't seem to get the automatic suspend feature working at all. Looking
through ESX documentation the only thing I can find even slightly
related to this is from the release notes:
<snip>
Support for Guest ACPI S1 Sleep Allows You to Wake up a Sleeping Virtual
Machine
VMware Tools provides support for guest operating systems that enable
ACPI S1 sleep. This feature requires you to have the latest version of
VMware Tools installed."
</snip>
If it has the support to wake up (like wake on lan), I assume ESX should
detect this ACPI call when you Shutdown/Standby and suspend the VM?
The VDA cookbook had a link on how to install third party software to
suspend through an AD GPO. I just set the power management options to
suspend after 30 minutes in my golden image. Nothing happens, but even
when I shutdown/standby a VM through the console, it usually goes to a
black screen for a second then comes right out. (with console session
locked)
The desktop VMs are all XP Pro, which is what our 250 user
implementation will be using. Latest vmware tools installed of course.
I appreciate the help, thanks again!
- Trev
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users