Well, as I said in my previous post, I do have some weird things happening. Apparently adding the domain user to the local group “Administrators” makes everything just works fine, yet he can’t do administrator like stuff (like turning off the write protection, changing local user accounts, …). Also, if you’re looking for a smart way of how to add a certain global group (as in Active Directory group) to a local group, try this: ...
I’m just got back from four days in Rostock over at S&N, where I was attending a VMware design course and here’s a list of questions I did ask the trainer: What’s the disadvantage of having a 1016 ported vSwitch ? Any clues on how to exchange the default certificate of the Virtual Center ? Are there any tools to stress test the virtual system ? Are there any performance impacts of having more than 10 users in Virtual Center ? Any clues and/or guides on how to do time synchronization in VMware guests, especially Linux guests ? What’s the preferred NIC type for Linux guests ? Any clues to using Raw Device Mappings with VMotion ? Is there a way of defining CPU masks on a global level ? Answers: ...
Well, it turns out that building stuff on ppc64 is a real pain in the ass, at least on anything SUSE related. I do have to tweak every damn spec to include this: 1 2 3 %ifarch ppc64 export LDFLAGS="$LDFLAGS -m64" %endif Otherwise, ld is gonna fail when linking, as it’s gonna try linking the generated 64bit code ( -m64 is passed on via RPM_OPT_FLAGS to CFLAGS) as 32bit code, which ain’t gonna work at all … ...
Today I did something horrible. I yet again noticed that I bought the wrong CPU’s (basically I bought Xeon DP’s with four cores). Those have apparently a feature called SSSE3, which makes vMotion with our old Xeon DP’s (dual cores) fail before even trying. But as we had a cooling outage today (basically ‘cause it broke), I needed to turn off some ESX servers. Thus leaving me with the new ones and one of the old ones. * yuck* ...
As virtualization seems to be a trendy thing to do, I went ahead and virtualized our nagios (while reinstalling the whole thing …). Now as I went into work today and started my email client, I received 4 nagios warnings about a LOAD service reaching critical state. Looked at the nagios box itself, opened up the VM console, looked into the syslog. Nothing. Yet over 3/4 of the services were flapping, some ping checks were critical (for whatever reason). So I opened the nagios webinterface again, and noticed it dropping the connection over and over again (had to reauthentificate me again and again). ...
As I wrote earlier, I recently virtualized our nagios. Along with that came a complete " redesign" of how checks are applied. Up till now, I defined checks for each and every single server, thus ending up with ~25 files, each holding roughly 6 checks which are in the same file just sorted by hostname. As you can imagine, it gets quite confusing with that amount of checks (~150). So the last two days I spent on reorganizing (with Visio), on which object/hostgroup placing a check would make sense. Now, this is my first result of two days planning, reorganizing, reordering and moving hosts into different hostgroups. ...
Well, guess my " solution" didn’t work sooo good. Lemme tell you what’s happening. I successfully added the node to the cluster group, but I can’t get any resources online. The node tries bringing it online, then shows a failure and immidiately moves them over to the next node. There the resource is being successfully moved online .. So again, I’m out of ideas .. Already tried reinstalling the box, after that I could get the third node successfully into the cluster, without the " Advanced (minimum)" trick … 🤷 still ain’t bringing any resources online.
We’re currently having a really weird problem with our VM’s. Sometime last week, SUSE released a kernel update. Now, once you install it and you reboot the selected VM with a DVD/CD image present, you’re gonna see this: msg.vmxaiomgr.retrycontabort.unkown The only workaround so far has been to unmount any cleanse any CD-Drives attached to the VM. And yes, this is reproduceable, even reinstalling from scratch doesn’t change the fact, that after installing the patch the VM quits working. ...
Well, after some searching today (we applied the VMware Update 2 today, thus the VMware Tools update too), I finally found out what is causing that problem. Though the problem seems to be not limited to virtual systems alone, I just browsed through this Novell Forum thread which pretty much describes my problem. I found the same error in the VM’s I tried to mount a CD image. ...
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.