Table
3-25
Problems
resolved
in
Oracle
Solaris
11.2
(continued)
SPARC
M10-
Bug
1
4
4S
Description
Workaround
16292272
x
If
you
configure
many
guest
domains
in
a
system
where
16
BBs
compose
one
physical
partition
(PPAR),
it
takes
time
to
perform
binding
for
the
guest
domains.
It
takes
approximately
(the
number
of
guest
domains
for
which
binding
has
already
been
performed
+
1)
x
6
+
10
seconds
to
perform
binding.
Therefore,
if
there
are
no
domains
for
which
binding
has
been
performed,
and
binding
is
performed
for
the
guest
domains
one
by
one
through
the
ldm
bind-domain
command,
the
required
time
is
obtained
by
summing
the
times
taken
to
perform
binding
for
all
of
them.
This
has
been
improved
with
SRU11.1.16.
4.0,
and
patch
150011-03
for
Oracle
Solaris
10.
We
recommend
that
you
do
not
configure
the
system
with
a
single
PPAR
but
divide
it
into
multiple
PPARs
and
then
configure
guest
domains
in
each
PPAR.
Using
the
recommended
configuration
described
above,
not
only
mitigates
the
described
phenomenon
but
also
helps
improve
fault
tolerance.
If
a
virtual
network
switch
(vsw)
is
configured,
you
can
reduce
the
time
for
binding
by
half
by
setting
inter-vnet-link
to
off.
For
notes
when
inter-vnet-link
is
set
to
off,
see
Oracle
VM
Server
for
SPARC
Administration
Guide
or
Oracle
VM
Server
for
SPARC
Release
Notes
.
17510986
x
x
x
If
the
guest
domain
is
Oracle
Solaris
11.1
and
SRU11.1.9
or
later
is
applied
to
it,
or
if
the
guest
domain
is
Oracle
Solaris
10
and
150400-01
or
newer
is
applied
to
it,
system
panic
may
occur
when
conducting
live
migration
or
dynamic
reconfiguration
of
physical
partitions.
It
has
been
modified
with
SRU11.1.14.5.0
and
the
Oracle
Solaris
10
patch
150400-07.
17627526
x
x
x
Messages
like
the
following
are
output
to
the
console
at
the
time
of
starting
Oracle
Solaris
and
the
ldoms/ldmd
service
is
put
to
maintenance
mode.
[Example
of
the
messages]
Jan
20
16:01:37
svc.startd[11]:
svc:/ldoms/
ldmd:default:
Method
"/opt/SUNWldm/
bin/ldmd_start"
failed
with
exit
status
96.
Jan
20
16:01:38
svc.startd[11]:
ldoms/
ldmd:default
misconfigured:
transitioned
to
maintenance
(see
'svcs
-xv'
for
details)
At
this
time,
messages
like
the
following
will
be
registered
to
the
log
file
(/var/svc/log/ldoms-ldmd:default.log)
of
the
ldoms/ldmd
service.
[Example
of
the
messages]
[
Jan
21
20:08:55
Executing
start
method
("/opt/SUNWldm/bin/ldmd_start").
]
ldmd
cannot
communicate
with
the
hypervisor
as
the
required
device
does
not
exist:
/devices/virtual-devices@100/channel-
devices@200/virtual-channel@0:hvctl
It
has
been
modified
with
SRU11.1.19.6.0
and
the
Oracle
Solaris
10
patch
150840-04.
[How
to
restore]
After
confirming
that
the
device
file
in
question
exists,
restore
the
ldoms/ldmd
service
using
the
svcadm(1M)
command.
#
ls
-l
/devices/virtual-devices@100/channel-
devices@200/virtual-channel@0:hvctl
crw-------
1
root
sys
148,
2048
Jan
21
20:08
/devices/virtual-devices@
100/channel-devices@200/virtual-
channel@0:hvctl
#
svcadm
clear
ldmd
Chapter
3
Information
on
Software
173
Summary of Contents for M10 Series
Page 8: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 viii ...
Page 14: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 xiv ...
Page 24: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 10 ...
Page 192: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 178 ...
Page 200: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 186 ...