What makes you so sure, that it is possible at all ? Standard actions $ pfexec pkg install xvm-gui $ pfexec svcadm enable milestone/xvm $ pfexec reboot
i believe expect gnome desktop installed (1) It's not Linux, where any step is clear understandable and doesn't require X Server up and running. Libvirtd service is usually dependent on packages libvirt,libvirt-python, python-virtinst ( or kind of this packages). Xen Host might be installed on linux without Libvirt and it's dependent packages, but i hardly believe that it's possible on OSOL. --- On Wed, 3/31/10, Florian Manschwetus <[email protected]> wrote: From: Florian Manschwetus <[email protected]> Subject: Re: [xen-discuss] xvm problems on snv_134 To: "Ralph Böhme" <[email protected]> Cc: [email protected] Date: Wednesday, March 31, 2010, 8:36 AM Could some one explain clearly, what todo on a fresh installed b134 (genunix text install image) to get xvm running? Florian Am 22.03.2010 15:21, schrieb Ralph Böhme: > I received the following response via PM, to which I replied via PM too as > I'm not subscriben to the mailing list: > >>> Any ideas? Thanks! >> >> >> # beadm create osx131;beadm activate osx131;reboot >> # pkg install SUNWxvm SUNWlibvirt SUNWvirtinst >> # svcadm enable milestone/xvm >> # reboot > > Okay, thanks, I'll try that. But according to > > <http://hub.opensolaris.org/bin/view/Community+Group+xen/2008_11_dom0> > > the steps for recenct snv should be: > $ pfexec pkg install xvm-gui > $ pfexec svcadm enable milestone/xvm > $ pfexec reboot > > Note that I'm on snv_134. From digging around in the xvm-gui IPS package, it > does in fact contain all the packages you list. Also what makes me wonder is > that you're referring to the old-style IPS names before the big rename. -----Inline Attachment Follows----- _______________________________________________ xen-discuss mailing list [email protected]
_______________________________________________ xen-discuss mailing list [email protected]
