Rao Shoaib wrote:
>>
>> Are you doing an hvm or pv install?  If hvm, I'd suspect
>> you should be seeing a menu presented to you since it
>> emulates a PXE boot, but I'm not actually 100% sure
>> the presentation of the grub menu piece of this is
>> supported though.
> I have tried both (virt-install with and without 'v') and in both 
> cases I only get a text console. PV install progresses further than 
> HVM install. HVM install fails with libvirt error (see below). BTW 
> this is with the mictoroot of osol-0906-ai-x86.microroot. With VB I 
> get a GRUB GUI which lists the commands and than shows dots on the 
> screen as it downloads the archives.
>
> HVM install:
>
> Starting install...
> Retrieving file unix...   100% |=========================| 1.4 MB    
> 00:00    WARNING: No install_service set via --autocf arguments, using 
> default installation service, if configured.
> Retrieving file x86.micro 100% |=========================|  57 MB    
> 00:01    Creating 
> domain...                                                 0 B 00:01
> libvir: error : Unknown failure
> libvir: error : Unknown failure
> Couldn't find domain "55".
>
> Domain installation does not appear to have been
> successful.  If it was, you can restart your domain
> by running 'virsh start myguest'; otherwise, please
> restart your installation.

I'd post this error out to matrix-eng for more clues.

>
>
>>
>> For pv installs, the dom0 boots the domU directly given
>> the known kernel binaries, so from what I recall, you
>> don't get a menu choice here.
> Yes. The following happens with PV:
>
> PV Install:
>
> Starting install...
> Retrieving file unix...   100% |=========================| 1.4 MB    
> 00:00    WARNING: No install_service set via --autocf arguments, using 
> default installation service, if configured.
> Retrieving file x86.micro 100% |=========================|  57 MB    
> 00:01    Creating 
> domain...                                                 0 B 00:03
> Connected to domain 54
> Escape character is '^]'
> v3.3.2-rc1-xvm-debu chgset 'Thu Jun 11 01:08:29 2009 -0700 
> 18432:56a9508086df'
> SunOS Release 5.11 Version snv_111b 32-bit
> Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
> Use is subject to license terms.
> Hostname: dhcp-10-1-232-80
> Remounting root read/write
> Probing for device nodes ...
> Preparing automated install image for use
> Downloading solaris.zlib archive
> --11:55:51--  http://10.1.235.154/mnt_iso/solaris.zlib
>           => `/tmp/solaris.zlib'
> Connecting to 10.1.235.154:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 588,066,304 (561M) [text/plain]
>
> 100%[====================================>] 588,066,304   15.63M/s    
> ETA 00:00
>
> 11:56:26 (16.10 MB/s) - `/tmp/solaris.zlib' saved [588066304/588066304]
>
> Downloading solarismisc.zlib archive
> --11:56:26--  http://10.1.235.154/mnt_iso/solarismisc.zlib
>           => `/tmp/solarismisc.zlib'
> Connecting to 10.1.235.154:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 29,468,672 (28M) [text/plain]
>
> 100%[====================================>] 29,468,672    
> 14.93M/s           
> 11:56:28 (14.92 MB/s) - `/tmp/solarismisc.zlib' saved [29468672/29468672]
>
> --11:56:28--  http://10.1.235.154/mnt_iso/.image_info
>           => `/tmp/.image_info'
> Connecting to 10.1.235.154:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 50 [text/plain]
>
> 100%[====================================>] 50            
> --.--K/s           
> 11:56:28 (4.00 MB/s) - `/tmp/.image_info' saved [50/50]
>
> Done mounting automated install image
> Configuring devices.
> Reading ZFS config: done.
>
> dhcp-10-1-232-80 console login: Couldn't find Auto Installer Service 
> Discovery Engine
> Jun 19 11:56:46 dhcp-10-1-232-80 svc.startd[7]: 
> application/auto-installer:default failed fatally: transitioned to 
> maintenance (see 'svcs -xv' for details)

Are you sure this error comes from when you are using the AI ISO
as well?  From the output it looks like it unarchived the /usr dir
just fine (the solaris.zlib archive), but the error simply means that
it wasn't able to find the /usr/bin/ai_sd binary.  So my first guess
would be that it got the wrong solaris.zlib archive, i.e. sucking bits
from a non-AI ISO.


thanks,
-ethan


Reply via email to