Hi Liam,
I did what you have said...but.
1st - ldm add device order changed. zvol is added first then ISO:
Boot device: cdrom File and args:
Bad magic number in disk label
ERROR: /virtual-devices at 100/channel-devices at 200/disk at 0: Can't open
disk label package
ERROR: boot-read fail
Evaluating:
Can't open boot device
2nd not trying to boot from slice f:
{0} ok boot cdrom:f
Boot device: /virtual-devices at 100/channel-devices at 200/disk at 1 File and
args:
Bad magic number in disk label
ERROR: /virtual-devices at 100/channel-devices at 200/disk at 0: Can't open
disk label package
ERROR: boot-read fail
Can't open boot device
{0} ok devalias
cdrom /virtual-devices at 100/channel-devices at 200/disk at
1
vdisk1 /virtual-devices at 100/channel-devices at 200/disk at 0
vnet0 /virtual-devices at 100/channel-devices at 200/network
at 0
net /virtual-devices at 100/channel-devices at 200/network
at 0
disk /virtual-devices at 100/channel-devices at 200/disk at 0
virtual-console /virtual-devices/console at 1
name aliases
{0} ok boot /virtual-devices at 100/channel-devices at 200/disk at 1:f
Boot device: /virtual-devices at 100/channel-devices at 200/disk at 1:f File
and args:
WARNING: /virtual-devices at 100/channel-devices at 200/disk at 1: Timeout
receiving packet from LDC ... retrying
WARNING: /virtual-devices at 100/channel-devices at 200/disk at 1: Timeout
receiving packet from LDC ... retrying
WARNING: /virtual-devices at 100/channel-devices at 200/disk at 1:
Communication error with Virtual Disk Server!
ERROR: boot-read fail
Can't open boot device
> Hi Roman,
>
> Roman Ivanov wrote:
> > Hello ALL,
> >
> > I am trying to boot guest domain from ISO image of
> Solaris 10 U5, but failing.
> > iso file exists and readable.
>
>
> You need to boot from slice f like a regular CD
>
> e.g. boot
> /virtual-devices at 100/channel-devices at 200/disk at 0:f
>
> Try this instead.
> ldm set-variable boot-device="cdrom:f" ldg1
>
> Also, I'd suggest adding vdisk1 before the ISO image
> so that
> the root disk is disk at 0 and the ISO is disk at 1 (then
> if you later
> remove the ISO image it's disk at 1 which disappears).
>
> HTH
>
> -- Liam
>
>
> > LDoms have version 1.0.3.
> >
> > Domain created as follows:
> > ldm add-domain ldg1
> > ldm add-vcpu 14 ldg1
> > ldm add-memory 1984M ldg1
> > ldm add-vnet vnet0 primary-vsw0 ldg1
> > ldm add-vdsdev
> /distr/distr/Solaris10/sparc_U5/solarisdvd.iso
> cdrom at primary-vds0
> > ldm add-vdisk cdrom cdrom at primary-vds0 ldg1
> > ldm set-variable boot-device=cdrom ldg1
> > ldm add-vdiskserverdevice
> /dev/zvol/dsk/distr/demo/ldg1 volldg1 at primary-vds0
> > ldm add-vdisk vdisk1 volldg1 at primary-vds0 ldg1
> > ldm bind-domain ldg1
> > ldm start ldg1
> >
> > Boot device: cdrom File and args:
> > WARNING:
> /virtual-devices at 100/channel-devices at 200/disk at 0:
> Timeout receiving packet from LDC ... retrying
> >
> > WARNING:
> /virtual-devices at 100/channel-devices at 200/disk at 0:
> Timeout receiving packet from LDC ... retrying
> >
> > WARNING:
> /virtual-devices at 100/channel-devices at 200/disk at 0:
> Communication error with Virtual Disk Server!
> >
> > ERROR: boot-read fail
> >
> > Evaluating:
> >
> > Can't open boot device
> >
> > Any thoughts?
> _______________________________________________
> ldoms-discuss mailing list
> ldoms-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ldoms-dis
> cuss
--
This message was posted from opensolaris.org
