reddragdiva: (Default)
[personal profile] reddragdiva

1. Recent Sun Xxx00 x86 servers are really nice boxes, and actually quite cost-effective for what you buy (a decently-built x86 server with good service, at least in our experience on gold and silver contracts). However, the firmware is so awful and buggy that it simulates hardware failures when there are none. If you call Sun, the first thing they will ask is that you upgrade the iLOM and BIOS firmware to the latest version. They are quite correct in this. (The engineer who looked over our X4600M2 that wouldn't boot claiming defective CPUs and was perfectly fine after a firmware afterward was quite scathing in his characterisation of the base firmware.) The nuisance is that you have to hook up both the iLOM serial (to configure the web version) and Ethernet ports, and upgrade the firmware through the browser interface to achieve, ooh, basic functionality. But it works quite well, the iLOM is really nice and we're still big fans of the boxes in question.

2. OpenBSD doesn't do X11 on VirtualBox because VirtualBox is officially crappy and Sun don't care (and Theo is sick of dmesg logs from known-defective virtual hardware). Guess I'll be sticking to running Windows 2000 on it (and that only to play MP3s over SMB without undue annoyance).

I'm trying to help with problems with current Wine on OpenBSD — the ports version is from 1999! And current versions do work quite well on FreeBSD — and have resorted to qemu, which works perfectly in full emulation (kqemu doesn't work; see above) despite being really slow. Use -std-vga not to need an xorg.conf, though that will give you a 1280×1024 screen every time — for something else, use driver "vesa" in xorg.conf. Good Lord, the yakshaving — including setting up vsftpd on the laptop to serve install tarballs via FTP to its hosted virtual machines, so I don't have to keep re-downloading 221MB.

3. Tomorrow (today, Tuesday) I will be down t' pub with [livejournal.com profile] sweh and [livejournal.com profile] syringavulgaris and the BOFHs. Must get home at a sensible time afterwards, unfortunately. Feh!

(no subject)

Date: 2008-12-23 01:36 am (UTC)
From: [identity profile] pir.livejournal.com
You can upgrade the X2100M2 I have via tftp, you still need the ilom interface hooked up to do so but at least you can do it over ssh.

(no subject)

Date: 2008-12-23 01:55 am (UTC)
From: [identity profile] blarglefiend.livejournal.com
I thought iLOM used DHCP or at least had a sensible default IP so you can hook up a crossover cable when racking the boxes and set the IP properly? In any event you should have iLOM configured when you rack the boxes. Remote console is far too useful.

But yeah, buggy. Not as buggy as the old SAN management software used to be though. At least they seem to have made that better: CAM is actually pretty decent, at least for the couple of low-end arrays I'm managing with it.

(no subject)

Date: 2008-12-23 03:42 am (UTC)
From: [identity profile] hellsop.livejournal.com
Heh. I use OpenBSD all over the house, for every machine that's not needing any more "user interface" than an ssh session. But I've never succeeded in getting anything graphicky and more complicated than xclock functional with it. Your paragraph is a reminder of exactly why I gave up trying.

(no subject)

Date: 2008-12-23 05:21 am (UTC)
From: [identity profile] blarglefiend.livejournal.com
The point is that upgrading the firmware isn't dependent on serial dongles or anything else like them: if you're doing things right then you'll be hooking them up to the network anyway. And finding two (or more) switch ports is only a problem if you haven't planned.

(We had that problem in our old datacentre. Not any more.)

The need to patch the firmware is annoying but far less troublesome to actually do than, oh, a Niagra box. If you think an X4600 is a pain, hope to never deal with a T5140... It looks like it uses iLOM but it's really more a bastard cousin that works completely differently and requires all sorts of buggering about to patch.

In any event the current generation of iLOM seems fairly stable so far. The X4600 problems I'd seen were more to do with the BIOS. Having a BIOS on a server, now that is ludicrous.

(no subject)

Date: 2008-12-23 05:22 am (UTC)
From: [identity profile] blarglefiend.livejournal.com
Mind, that job involved using SPARCstation 5s as desktop machines. fvwm2 was a godsend...

(no subject)

Date: 2008-12-23 05:28 am (UTC)
From: [identity profile] blarglefiend.livejournal.com
Mine stayed an SS5 until we got second-gen U5s and the OK to do a special install of Solaris 8. Those first-round U5s plus Solaris 2.6... grind grind grind. Couldn't get them to reliably play an MP3 while also running FrameMaker. Or a mere web browser. The SS5 could do all three.

fvwm2 with all the pretty turned off was still about the best option, even on the U5s.

(no subject)

Date: 2008-12-23 05:51 am (UTC)
From: [identity profile] neuro42.livejournal.com
Where's the annoyance in mp3 over smb?

(no subject)

Date: 2008-12-23 06:41 am (UTC)
ext_243: (troubleshooting)
From: [identity profile] xlerb.livejournal.com
I'm using twm right now, if you know what I mean, and I think you do.

(no subject)

Date: 2008-12-23 08:03 am (UTC)
From: [identity profile] gths.livejournal.com
Kickin' it old-skool. Ahh the days of DECstations.

(no subject)

Date: 2008-12-23 08:32 am (UTC)
From: [identity profile] mstevens.livejournal.com
I might actually use OpenBSD if the updates were a little easier.

(no subject)

Date: 2008-12-23 10:44 am (UTC)
From: [identity profile] syllopsium.livejournal.com
Use VMWare or VirtualPC (if running Windows) instead - OpenBSD is fine on those. It's possible that VirtualBox 2.1 is better - a March post is really rather old, but the last time I tried VB it really was pretty shit.

(no subject)

Date: 2008-12-23 10:50 am (UTC)
From: [identity profile] syllopsium.livejournal.com
It's not /that/ difficult. Boot install, select upgrade, extract etc.tgz, run sysmerge.

(no subject)

Date: 2008-12-23 03:50 pm (UTC)
vatine: Generated with some CL code and a hand-designed blackletter font (Default)
From: [personal profile] vatine
You should handcraft a virtual machine, using the finest Tasmanian bits (they've gone through a drop-bear, making them excellent for virtualising purposes), lovingly placed in the right spot using unicon-whisker tweezers. That'd do it. Probably see you tonight, then.

(no subject)

Date: 2008-12-23 08:32 pm (UTC)
From: [identity profile] mstevens.livejournal.com
It's a) quickly applying security updates and b) getting security updates at all for ports where I feel OpenBSD is weak.

Compare debian and "aptitude update && aptitude upgrade".

(no subject)

Date: 2008-12-23 08:50 pm (UTC)
From: [identity profile] mstevens.livejournal.com
I'm currently trying to work out why upgrading VirtualBox means X in my debian VM is now cocked up.

(no subject)

Date: 2008-12-24 06:17 am (UTC)
From: [identity profile] mstevens.livejournal.com
FreeBSD seems to come closest in the BSD world (which is one reason why I like it).

(no subject)

Date: 2008-12-24 06:49 am (UTC)
From: [identity profile] mstevens.livejournal.com
Aha, there seems to be a known bug with guest display resizing in 2.1 that's affecting most linux people.

(no subject)

Date: 2008-12-26 11:22 pm (UTC)
From: [identity profile] wintrmute.livejournal.com
tried the kvm-based virtual machine manager stuff in ubuntu?
Seems to work well for us.. Supports fully-virtualised OSs, hardware accelerated, faster than kqemu by a good margin..

(no subject)

Date: 2008-12-29 08:59 pm (UTC)
From: [identity profile] mstevens.livejournal.com
apt is excellent.

The thing that annoys me with the OpenBSD ports tree is that (as I understand it), there's no way to get timely security updates without following CVS, which also requires to track CVS OpenBSD.

(no subject)

Date: 2008-12-30 05:38 am (UTC)
From: [identity profile] ajohnymous.livejournal.com
I really like the RDP remote client management of VirtualBox. That's nice when you are trying to manage remote VM's with a Mac since Cord is such a nice RDP client. With VMware, you have to use VNC which 1) has to be manually/text edited enabled in VMware server, 2) has a broken mouse when there's no VMware tools installed, and 3) forces you into Mac VNC clients with various amounts of suckage.

Of course, remote VM client viewing options are important when managing from a Mac since VMware has NOT seen fit to provide an OSX Remote Console Firefox Plug-in (just a Windows and Linux one).