Re: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

I don't know exactly, but I'm thinking that OpenSolaris requires Xen 3.1 or higher.  Could be wrong, but it seems that success with pre-3.1 versions is pretty hit-or-miss.

 

-Nick

>>> On 2008/05/31 at 12:21, Daniel Bareiro <daniel-listas@xxxxxxx> wrote:

Hi all!

I am trying to install OpenSolaris 2008.05 PV domU on Debian GNU/Linux
dom0 follow this [1] steps. Xen version is 3.0.3-1 from Debian packages.

But I got this messages during boot:

Configuring devices.
Mounting local partitions/cdroms
May 31 11:04:29 svc.startd[7]: svc:/system/coreadm:default: Method
"/lib/svc/method/svc-coreadm start" failed due to signal KILL.
Reading ZFS config: done.
May 31 11:05:36 svc.startd[7]: svc:/system/coreadm:default: Method or
service exit timed out.  Killing contract 31.
May 31 11:07:12 svc.startd[7]: svc:/network/routing/route:default:
Method or service exit timed out.  Killing contract 33.
May 31 11:07:16 svc.startd[7]: svc:/network/rpc/bind:default: Couldn't
fork to execute method /lib/svc/method/rpc-bind start: Resource
temporarily unavailable
May 31 11:07:39 svc.startd[7]: svc:/network/routing/route:default:
Method or service exit timed out.  Killing contract 33.
May 31 11:07:42 svc.startd[7]: svc:/system/coreadm:default: Method
"/lib/svc/method/svc-coreadm refresh" failed with exit status 96.
May 31 11:07:44 svc.startd[7]: svc:/network/routing/route:default:
Method "/lib/svc/method/svc-route" failed due to signal KILL.
May 31 11:07:44 svc.startd[7]: svc:/system/dbus:default: Method or
service exit timed out.  Killing contract 34.
May 31 11:07:46 svc.startd[7]: svc:/system/dbus:default: Method
"/lib/svc/method/svc-dbus start" failed with exit status 95.
May 31 11:07:52 svc.startd[7]: system/coreadm:default misconfigured:
transitioned to maintenance (see 'svcs -xv' for details)
May 31 11:08:00 svc.startd[7]: system/dbus:default failed fatally:
transitioned to maintenance (see 'svcs -xv' for details)
May 31 11:08:15 svc.startd[7]: svc:/network/inetd-upgrade:default:
Method or service exit timed out.  Killing contract 35.
May 31 11:08:25 svc.startd[7]: svc:/network/inetd-upgrade:default:
Method or service exit timed out.  Killing contract 35.
May 31 11:08:28 svc.startd[7]: svc:/network/inetd-upgrade:default:
Method "/lib/svc/method/inetd-upgrade start" failed due to signal KILL.
May 31 11:12:05 svc.startd[7]:
svc:/application/opengl/ogl-select:default: Method or service exit timed
out.  Killing contract 47.
May 31 11:13:03 svc.startd[7]:
svc:/application/opengl/ogl-select:default: Method or service exit timed
out.  Killing contract 47.
May 31 11:15:53 svc.startd[7]:
svc:/application/opengl/ogl-select:default: Method
"/lib/svc/method/ogl-select start" failed due to signal KILL.
May 31 11:15:55 svc.startd[7]: svc:/network/inetd-upgrade:default:
Method "/lib/svc/method/inetd-upgrade start" failed due to signal KILL.
May 31 11:15:55 svc.startd[7]: svc:/network/routing/route:default:
Method or service exit timed out.  Killing contract 51.
May 31 11:16:01 svc.startd[7]: svc:/network/routing/route:default:
Method "/lib/svc/method/svc-route" failed due to signal KILL.

And I do not reach to obtain login. Some idea than can be happening?

Thanks in advance.

Regards,
Daniel

[1] http://www.mobilnews.cz/blog/?p=42
--
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598

---

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users