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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2008-Jun-01 10:47 UTC
Re: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0
Would address it to xen-discuss forum@opensolaris.org.
--- On Sat, 5/31/08, Daniel Bareiro <daniel-listas@gmx.net> wrote:
From: Daniel Bareiro <daniel-listas@gmx.net>
Subject: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0
To: "Xen-Users" <xen-users@lists.xensource.com>
Date: Saturday, May 31, 2008, 2:21 PM
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_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Nick Couchman
2008-Jun-01 13:29 UTC
Re: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0
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@gmx.net> 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@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2008-Jun-01 13:53 UTC
Re: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0
Works at Xen 3.0.3 Debian Dom0
http://www.mobilnews.cz/blog/?p=42
Works at Xen 3.2.1 CentOS 5.1 Dom0
http://lxer.com/module/newswire/view/102728/index.html
Works at Xen 3.2 Ubuntu 8.04 Desktop(Server) Dom0
http://lxer.com/module/newswire/view/103407/index.html
Works at Xen 3.1 F8 Dom0, Xen 3.1 CentOS 5.1 Dom0,
Xen 3.1 Ubuntu 7.10 Dom0. Just doesn''t require kernel
patch (vs Xen 3.2 Linux Dom0).
--- On Sun, 6/1/08, Nick Couchman <Nick.Couchman@seakr.com> wrote:
From: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] OpenSolaris 2008.05 domU on Debian dom0
To: dbareiro@gmx.net, "Xen-Users"
<xen-users@lists.xensource.com>
Date: Sunday, June 1, 2008, 9:29 AM
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@gmx.net> 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@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Looking at
http://strugglers.net/~andy/blog/2008/01/20/red-hat-based-linux-under-xen-from-debian-etch/
I found following statement.
Quote:-
Andy Says:
March 29th, 2008 at 2:42 am
Hi,
The broken pygrub is not a security bug so not going to be fixed at least until
the next stable release I suppose.
Do you have the details of the pygrub exploit? I thought I saw it fixed, which
is what I would expect as a security issue.
If you’re just here to bash Debian then I’m not really interested however.My
concern is failure to manage with "xm" CentOS 5.1 DomU at
Xen 3.2.1 F8 Dom0 after successful DomU creating by virt-install obtained as a
result of "yum install python_libvirt" on xen-disabled F8 instance
(64-bit)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boris Derzhavets
2008-Jun-01 17:57 UTC
Re: [Xen-users] What is pygrub status in Xen 3.2.1 ? (just a minor fix is required)
Ok. I got it done due to :-
http://lists.xensource.com/archives/html/xen-bugs/2008-04/msg00051.html
1. Install F8 xen disabled
2.yum install python_libvirt
3.Install Xen 3.2.1 from source on F8 instance.
4. Perform virt-install PV CentOS 5.1 DomU
The way i did ( just the first try)
DomU hanged at reboot
# xm destroy <Domain>
# xm delete <Domain>
5. Fixed /usr/bin/pygrub.
6. Cretated RHLPV:-
[root@dhcppc0 xen]# cat RHELPV
name = "RHELPV"
maxmem = 1024
memory = 1024
vcpus = 1
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
# vfb = [ ]
disk = [ "phy:/dev/sdb12,xvda,w" ]
vif = [ "bridge=eth2" ]
7. Started up DomU:-
# xm create -c RHLPV
Domain started fine.
Now , I believe there wouldn''t be any need destroy and delete
Domain.
It should work with fixed pygrub through :-
xm start/shutdown/reboot <Domain>
--- On Sun, 6/1/08, Boris Derzhavets <bderzhavets@yahoo.com>
wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-users] What is pygrub status in Xen 3.2.1 ?
To: xen-users@lists.xensource.com
Date: Sunday, June 1, 2008, 1:23 PM
Looking at
http://strugglers.net/~andy/blog/2008/01/20/red-hat-based-linux-under-xen-from-debian-etch/
I found following statement.
Quote:-
Andy Says:
March 29th, 2008 at 2:42 am
Hi,
The broken pygrub is not a security bug so not going to be fixed at least until
the next stable release I suppose.
Do you have the details of the pygrub exploit? I thought I saw it fixed, which
is what I would expect as a security issue.
If you’re just here to bash Debian then I’m not really interested however.My
concern is failure to manage with "xm" CentOS 5.1 DomU at
Xen 3.2.1 F8 Dom0 after successful DomU creating by virt-install obtained as a
result of "yum install python_libvirt" on xen-disabled F8 instance
(64-bit)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users