I''m trying to figure out what the CURRENT requirements are for configuring the xVM domains to start at boot-time and stop on shutdown. The closest to current I''ve seen is http://opensolaris.org/os/community/xen/docs/xVM_lowres.pdf which does not address the problem, and http://opensolaris.org/os/community/xen/docs/xvm-ktde-20070917.pdf which states: * svc:/system/xvm/domains:default - Automatically creates and destroys guest domains at service start/stop time (typically system boot/shutdown) which appears not to be the case. The next older documentation refers to ''virsh autostart'', which no longer exists. There is also a reference somewhere to "we have moved all this to the smf(5) system under xvm/domains", but with no details. And older documentation refers to the configuration files that have been relegated to smf. This is intended for a production system, and I don''t want to have to wake up and start them manually if this isn''t needed. Yes, I know that this is all beta or alpha and changing as we speak - part of the intention is to make it work despite that, to showcase some of the new features. ;-) Background: I started this round of installs with the OpenSolaris 2008.11 CD ROM until I realized that the CD ROM only has the minimal stuff needed to bring it up and make it work. [After downloading the CD, I also accidentally ordered two copies of the physical CD ROM before realizing that there JUST IS NO PAGE saying that you have successfully completed the order.] I got Solaris Express Community Edition (SXCE) build 107, put it on a DVD, and installed it with no problems. I used the ''bootadm'' tool to change the default boot option to Solaris xVM. I booted and got the xVM hypervisor with the OpenSolaris/SXCE Dom0 running over it. I tried to use virt-install to create a DomU. It of course failed. After some debugging, I put all of the variables in the shell script /usr/lib/xen/scripts/vbd-check - except for the one in the ''for'' loop - in double-quotes. I was then able to install HVM domains containing SXCE-107, Fedora 10, and Ubuntu Server 8.10. [XEN DEVELOPERS - IT''S BASIC PROGRAMMING SAFETY TO ENCLOSE ALL VARIABLES IN DOUBLE-QUOTES UNLESS YOU''RE DELIBERATELY DOING SOMETHING LIKE THE ''for'' LOOP - SO HOW DID THIS HAPPEN??? Only half the variables were in double-quotes!!!] Re-booting the entire system, I noticed that the three virtual domains did NOT come up - I had to ''virsh start'' them all. I''ve now re-reviewed all the documentation I can find, plus everything on this mailing list since 2008.11 came out, and - nothing. Please help. Thanks! Two other problems I noticed - (1) The Fedora 10 GUI is abnormally slow. I have not tested to see whether that is the kernel, the console I/O, or the graphics I/O. Has anybody else observed this and been able to make any determinations on cause and fix? (2) When I start the OpenSolaris/SXCE-107 domain and open a ''vncviewer'' window on it immediately, I see the ''hald'' daemon fail on the keyboard, and then the X server subsequently fail as well. When I re-boot the domain, even though I have to re-start the ''vncviewer'' window and seem to catch it in the same place, ''hald'' succeeds and the X server comes up with the normal login window. Any ideas why this might be? I''ve heard it said that one definition of insanity is repeating the same action and expecting the results to be different - but that sure seems to work with a lot of software! [Then again, who says we''re sane?] Thanks again! -- /*********************************************************************\ ** ** Joe Yao jsdy@tux.org - Joseph S. D. Yao ** \*********************************************************************/
Joseph S D Yao wrote:> I''m trying to figure out what the CURRENT requirements are for > configuring the xVM domains to start at boot-time and stop on shutdown. > The closest to current I''ve seen is > http://opensolaris.org/os/community/xen/docs/xVM_lowres.pdf > which does not address the problem, and > http://opensolaris.org/os/community/xen/docs/xvm-ktde-20070917.pdf > which states: > * svc:/system/xvm/domains:default > - Automatically creates and destroys guest domains at > service start/stop time (typically system boot/shutdown) > which appears not to be the case. The next older documentation refers > to ''virsh autostart'', which no longer exists. There is also a reference > somewhere to "we have moved all this to the smf(5) system under > xvm/domains", but with no details. And older documentation refers to > the configuration files that have been relegated to smf. > > This is intended for a production system, and I don''t want to have to > wake up and start them manually if this isn''t needed. Yes, I know that > this is all beta or alpha and changing as we speak - part of the > intention is to make it work despite that, to showcase some of the new > features. ;-)There isn''t a "good" way to do this today.. I imagine virsh autostart will be the way in the future.. I think there is an RFE filed for it. To enable it today (with the guest shutdown), xm list -l <guest> > /tmp/myguest.sxp In myguest.sxp, change on_xend_start from ignore to start. Then do a xm new -F /tmp/myguest When the xvm/domains service starts, the guests with on_xend_start set will start.> Background: > > I started this round of installs with the OpenSolaris 2008.11 CD ROM > until I realized that the CD ROM only has the minimal stuff needed to > bring it up and make it work. [After downloading the CD, I also > accidentally ordered two copies of the physical CD ROM before realizing > that there JUST IS NO PAGE saying that you have successfully completed > the order.] > > I got Solaris Express Community Edition (SXCE) build 107, put it on a > DVD, and installed it with no problems. I used the ''bootadm'' tool to > change the default boot option to Solaris xVM. I booted and got the xVM > hypervisor with the OpenSolaris/SXCE Dom0 running over it. > > I tried to use virt-install to create a DomU. It of course failed. > > After some debugging, I put all of the variables in the shell script > /usr/lib/xen/scripts/vbd-check - except for the one in the ''for'' loop - > in double-quotes. I was then able to install HVM domains containing > SXCE-107, Fedora 10, and Ubuntu Server 8.10. [XEN DEVELOPERS - IT''S > BASIC PROGRAMMING SAFETY TO ENCLOSE ALL VARIABLES IN DOUBLE-QUOTES > UNLESS YOU''RE DELIBERATELY DOING SOMETHING LIKE THE ''for'' LOOP - SO HOW > DID THIS HAPPEN??? Only half the variables were in double-quotes!!!]Bug was introduced in b107 and fixed in b108 :-) http://bugs.opensolaris.org/view_bug.do?bug_id=6796508> Re-booting the entire system, I noticed that the three virtual domains > did NOT come up - I had to ''virsh start'' them all. > > I''ve now re-reviewed all the documentation I can find, plus everything > on this mailing list since 2008.11 came out, and - nothing. Please > help. Thanks! > > Two other problems I noticed - > > (1) The Fedora 10 GUI is abnormally slow. I have not tested to see > whether that is the kernel, the console I/O, or the graphics I/O. Has > anybody else observed this and been able to make any determinations on > cause and fix?I have not run this guest. I usually run my linux guests in PV though.> (2) When I start the OpenSolaris/SXCE-107 domain and open a ''vncviewer'' > window on it immediately, I see the ''hald'' daemon fail on the keyboard, > and then the X server subsequently fail as well. When I re-boot the > domain, even though I have to re-start the ''vncviewer'' window and seem > to catch it in the same place, ''hald'' succeeds and the X server comes up > with the normal login window. Any ideas why this might be? I''ve heard > it said that one definition of insanity is repeating the same action and > expecting the results to be different - but that sure seems to work with > a lot of software! [Then again, who says we''re sane?]Known bug (although I don''t know the bug number).. You will only see that the first time you boot after an install. There some post install stuff that runs the first time which you need to let finish.. Then it should be fine. Any reason your not running the guests as PV? MRJ> Thanks again! > >
Mark Johnson wrote:>> This is intended for a production system, and I don''t want to have to >> wake up and start them manually if this isn''t needed. Yes, I know that >> this is all beta or alpha and changing as we speak - part of the >> intention is to make it work despite that, to showcase some of the new >> features. ;-) > > There isn''t a "good" way to do this today.. I imagine virsh autostart > will be the way in the future.. I think there is an RFE filed for it.Yep, and it''s already fix in our 3.3 gate.. So virsh autostart will be available once we putback. http://bugs.opensolaris.org/view_bug.do?bug_id=6795210 MRJ
On Thu, Mar 12, 2009 at 06:11:31PM -0400, Mark Johnson wrote: ...> There isn''t a "good" way to do this today.. I imagine virsh autostart > will be the way in the future.. I think there is an RFE filed for it.... OK. I''d got the impression that ''virsh autostart'' used to work but didn''t any more. Obviously I got it backwards. I''m like that with time. ;-S ...> To enable it today (with the guest shutdown), > xm list -l <guest> > /tmp/myguest.sxp > In myguest.sxp, change on_xend_start from ignore to start. Then do a > xm new -F /tmp/myguest > > When the xvm/domains service starts, the guests with on_xend_start > set will start.... OK, so it IS still the configuration file bit; you just have to be trickier with where the configuration file is. Thanks!!! ...> Bug was introduced in b107 and fixed in b108 :-) > http://bugs.opensolaris.org/view_bug.do?bug_id=6796508... So I noticed, but by that time I didn''t want to go back and re-install b108. We''ll see whether a future build changes my mind. ;-) But my point was - this is one of the, OK not first, but second or third things people programming with shell variables are supposed to learn. So how come half the variables were unquoted??? ;-( ...> I have not run this guest. I usually run my linux guests in PV though.The examples in the docs showed SXCE in PV mode. I guess I wanted HVM mode to completely isolate the Linuces from the SXCE Dom0. And, yes, I''m thinking that was likely why the Fedora 10 VM was so slow. ...> Known bug (although I don''t know the bug number).. You will only see that > the first time you boot after an install. There some post install stuff that > runs the first time which you need to let finish.. Then it should be fine.... Nope - every time I''ve re-booted the hardware, it''s there. I''ll look for post-install stuff: I saw some somewhere and maybe that''s it. Yes, my memory is of the documented post-install stuff asking for a keyboard language/type, now that you mention it. But my memory is not photographic, so I''ll have to find it again.> Any reason your not running the guests as PV?As I said, to isolate the Linuces from the underlying SXCE. And to show that it worked. -- /*********************************************************************\ ** ** Joe Yao jsdy@tux.org - Joseph S. D. Yao ** \*********************************************************************/
On Thu, Mar 12, 2009 at 07:19:30PM -0400, Mark Johnson wrote:> Mark Johnson wrote:...> > There isn''t a "good" way to do this today.. I imagine virsh autostart > > will be the way in the future.. I think there is an RFE filed for it. > > Yep, and it''s already fix in our 3.3 gate.. So virsh autostart > will be available once we putback. > > http://bugs.opensolaris.org/view_bug.do?bug_id=6795210... Mought be a reason to upgrade. Will that put it in build 110? Thanks again! -- /*********************************************************************\ ** ** Joe Yao jsdy@tux.org - Joseph S. D. Yao ** \*********************************************************************/
On Fri, Mar 13, 2009 at 7:28 AM, Joseph S D Yao <jsdy@tux.org> wrote:>> To enable it today (with the guest shutdown), >> xm list -l <guest> > /tmp/myguest.sxp >> In myguest.sxp, change on_xend_start from ignore to start. Then do a >> xm new -F /tmp/myguest >> >> When the xvm/domains service starts, the guests with on_xend_start >> set will start. > ... > > > OK, so it IS still the configuration file bit; you just have to be > trickier with where the configuration file is.Sort of. Once you do "xm new", you can safely delete the file /tmp/myguest.sxp because xend no longer needs it.
On Thu, Mar 12, 2009 at 06:11:31PM -0400, Mark Johnson wrote:> There isn''t a "good" way to do this today.. I imagine virsh autostart > will be the way in the future.. I think there is an RFE filed for it.Yes, this will become available with the new Xen 3.3 bits. regards john