I have two zones configured and run: ipkg zone (shared ip) and lx zone.
run: ps -aef cause some pauses during display (5 to 20 seconds)
same problem when using flash plugin in Firefox - opening page with flash
content cause Firefox freeze for 10-30 seconds.
This all when one of zones (or both)
this sounds like a bug that dan price tracked down to:
6906514 sdev_attrinit ignores va_mask, leading to whacky /dev/zcons vattrs
it should be fixed in snv_130.
ed
On Mon, Dec 21, 2009 at 11:56:20AM -0800, Eugene Turkulevich wrote:
I have two zones configured and run: ipkg zone (shared ip) and
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129 generated error
from an s10 zone due to boot-archive
My webrev is accessible via
http://cr.opensolaris.org/~flippedb/onnv-s10c
Thanks,
Jordan
___
The bug mentions that this can also impact a nevada zone that was p2v'ed.
Should you fix usr/src/lib/brand/native/zone as well?
-Steve
On Mon, Dec 21, 2009 at 03:46:00PM -0800, Jordan Vaughan wrote:
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129
Minor nit. You could use != POC_STRING, put the Z_NO_ENTRY in the {}, and
put the success case after. Not a required change.
LGTM.
-Steve
On Fri, Dec 18, 2009 at 07:28:52PM -0800, Jordan Vaughan wrote:
I expanded my webrev to include my fix for
6910339 zonecfg coredumps with badly formed
That's a good idea. I updated the webrev.
Thanks,
Jordan
On 12/21/09 05:08 PM, Steve Lawrence wrote:
Minor nit. You could use != POC_STRING, put the Z_NO_ENTRY in the {}, and
put the success case after. Not a required change.
LGTM.
-Steve
On Fri, Dec 18, 2009 at 07:28:52PM -0800, Jordan
lgtm.
ed
On Mon, Dec 21, 2009 at 05:41:29PM -0800, Jordan Vaughan wrote:
That's a good idea. I updated the webrev.
Thanks,
Jordan
On 12/21/09 05:08 PM, Steve Lawrence wrote:
Minor nit. You could use != POC_STRING, put the Z_NO_ENTRY in the {}, and
put the success case after. Not a
i'd probably leave out the XXX comment and instead update 6912451 to
mention that part of the fix for 6912451 would involve removing the fix
for 6909222 (since it would essentially be obsoleting this fix.)
ed
On Mon, Dec 21, 2009 at 03:46:00PM -0800, Jordan Vaughan wrote:
I need someone to
Excellent suggestion. I'll update CR 6912451. Meanwhile, I removed the
XXX comments and regenerated the webrev.
Thanks,
Jordan
On 12/21/09 06:12 PM, Edward Pilatowicz wrote:
i'd probably leave out the XXX comment and instead update 6912451 to
mention that part of the fix for 6912451 would
