More VirtualCenter troubles (fini)
Posted on Thursday, 7th August, 2008 in Life
Well, today the support request came back. Seems one of the originally linked VMTN dicussions really is the only way:
- Export the customization specification
- Edit the XML file
- Import it again
The related part inside the customization specification should then look like this:
1 2 3 4 5 | <password> <_type>vim.vm.customization.Password</_type> <plainText>true</plainText> <value>Password01</value> </password> |
So if you ever think about switching the default VirtualCenter certificate (for whatever reason), make sure you use the above workaround. Otherwise VirtualCenter is gonna fail miserably during the customization phase of the cloning process.
More VirtualCenter troubles
Posted on Monday, 4th August, 2008 in Life
Well, after my co-worker switched the VirtualCenter certificates with one produced by our RA a few days ago, I can’t clone anything using a customization specification anymore.
Unable to decrypt passwords in customization specification
Guess, we’re shit outa luck. At least both of those linked VMTN discussions don’t contain any (that is for us) workable solution (well besides storing the password in cleartext in the spec — which ain’t sooo good). Gonna bug him tomorrow to open up a VMware support request, maybe that’ll help somewhat. I sure hope so.
Yet another VMware error
Posted on Wednesday, 30th July, 2008 in Life
Today I was moving a pretty standard SLES10 virtual machine to another host, when the migration dialog showed me this:
fault.MemorySizeNotRecommended
And if you now think, the virtual machine is something special take a look at those settings:
Virtual machine configuration
I don’t know what to think about that error message. Googling for it doesn’t reveal that much about it. If anyone out there got an idea, I’m open for suggestions.