I'd recommend reading the pages of RFEs and bug fixed in the LDoms s\ware listed in the release notes of 1.1->1.3
Staying on 1.0.3 is generally not good advice... Rob On 02/17/10 16:19, Steve Goldthorpe wrote: > If the aim is for as short a down-time as possible, don't upgrade the LDM > software. You'd need to match it with the relevant hypervisor firmware and > to flash this you'd need to turn all the LDoms off for an extended duration. > > Of course should you already be on a suitable hypervisor level (check the > relevant release notes and patches), then you can ignore this. > > -Steve > > --- On Wed, 17/2/10, Terry Smith <Terry.Smith at Sun.COM> wrote: > >> From: Terry Smith <Terry.Smith at Sun.COM> >> Subject: Re: [ldoms-discuss] update the primary domain without shutting down >> the other LDoms >> To: "Glen Gunselman" <ggunselm at emporia.edu> >> Cc: ldoms-discuss at opensolaris.org >> Date: Wednesday, 17 February, 2010, 15:55 >> Glen >> >> I really would advise you to move to a much more recent >> version of the >> LDM software - 1.3 was recently released. 1.0.3 is >> now over 2 years old >> and there are a lot of fixes in either 1.2 or 1.3 >> software. >> >> T >> >> >> On 17/02/2010 15:38, Glen Gunselman wrote: >>> Terry, >>> >>> Thanks for the reply. >>> >>> I prefer to use Live Upgrade. >>> >>> Here's the hypervisor details that I should have >> included as well: >>> Logical Domain Manager (v 1.0.3) >>> Hypervisor control >> protocol v 1.1 >>> Using Hypervisor MD >> v 1.0 >>> System PROM: >>> Hypervisor >> v. 1.6.7. >> @(#)Hypervisor 1.6.7.a 2008/08/30 >> 05:18\015 >>> OpenBoot >> v. 4.29.0. @(#)OBP >> 4.29.0.a 2008/09/15 12:01 >>> >>> One of the LDoms is running a test Oracle DB but >> others are a mix of production and test web servers (some >> are Oracle Application Servers, some are Apache). >>> I having a problem with the LDoms hanging. >> Support has indicated the problem is: >>> 6661097 I/Os stuck in VDC/VDS layer causing hang >>> >>> and is resolved by kernel patch 139555-08. >>> >>> I've patched some of the LDoms to 141444-09 but I'm >> still seeing the problem. >>> Support did not say anything about needing to patch >> the control domain but I'm thinking I should. >>> >>> Thanks again for the advice, >>> Glen >> _______________________________________________ >> ldoms-discuss mailing list >> ldoms-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >> > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
