Hi all, In the older format using Xen 3.0.3 (domains created via xm), I simply created a sym link from /etc/xen/domU config file to /etc/xen/auto. I am now using virt-install (Xen 3.4.1) which creates the domU config in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. So I sym link this to a file in /etc/xen/auto/hostname_of_domU and noticed that no auto starting of the domU happens. I''ve looked in both my Xen books and only find that /etc/xen/auto is the place to auto start domUs. Any ideas on how to auto start gracefully while not writing a script in /etc/rc3.d every time a new domU comes on line? And why are xm create and virt-install so diff in how they approach domU configs? This is confusing. - aurf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, In the older format using Xen 3.0.3 (domains created via xm), I simply created a sym link from /etc/xen/domU config file to /etc/xen/auto. I am now using virt-install (Xen 3.4.1) which creates the domU config in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. So I sym link this to a file in /etc/xen/auto/hostname_of_domU and noticed that no auto starting of the domU happens. I''ve looked in both my Xen books and only find that /etc/xen/auto is the place to auto start domUs. Any ideas on how to auto start gracefully while not writing a script in /etc/rc3.d every time a new domU comes on line? And why are xm create and virt-install so diff in how they approach domU configs? This is confusing. - Brian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Oct 8, 2009 at 11:37 AM, Brian Krusic <brian@krusic.com> wrote:> Hi all, > > In the older format using Xen 3.0.3 (domains created via xm), I simply > created a sym link from /etc/xen/domU config file to /etc/xen/auto. > > I am now using virt-install (Xen 3.4.1) which creates the domU config in > /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and noticed > that no auto starting of the domU happens. > > I''ve looked in both my Xen books and only find that /etc/xen/auto is the > place to auto start domUs. > > Any ideas on how to auto start gracefully while not writing a script in > /etc/rc3.d every time a new domU comes on line? > > And why are xm create and virt-install so diff in how they approach domU > configs? This is confusing. > > - Brian > >I just updated to 3.4.1 and autostart stopped working. I copied the xen domU file into /etc/xen/auto and it started working again. Xendomains kept complaining that my domU file was not valid. Start there. Grant McWilliams _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seems like /etc/xen/auto doesn''t like sxp format. I''m a bit of a tard in that I like using virt-install to create my domUs, a no brainer in that I don''t have to know much to create a config. I''d rather just tweak it after words. In 3.4.1, virt-install creates domUs in the sxp format. Would you happen to know how I can force the new version of virt-install to create in the old format? - Brian On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote:> > On Thu, Oct 8, 2009 at 11:37 AM, Brian Krusic <brian@krusic.com> > wrote: > Hi all, > > In the older format using Xen 3.0.3 (domains created via xm), I > simply created a sym link from /etc/xen/domU config file to /etc/xen/ > auto. > > I am now using virt-install (Xen 3.4.1) which creates the domU > config in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and > noticed that no auto starting of the domU happens. > > I''ve looked in both my Xen books and only find that /etc/xen/auto is > the place to auto start domUs. > > Any ideas on how to auto start gracefully while not writing a script > in /etc/rc3.d every time a new domU comes on line? > > And why are xm create and virt-install so diff in how they approach > domU configs? This is confusing. > > - Brian > > > I just updated to 3.4.1 and autostart stopped working. I copied the > xen domU file into /etc/xen/auto and it started working again. > Xendomains kept complaining that my domU file was not valid. Start > there. > > Grant McWilliams > _______________________________________________ > 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
I just found that if you look at the sxp file, specifically; on_xend_start ignore on_xend_stop ignore change ignore to start and stop accordingly. I found some tidits on converting the simpler domU config to the newer SXP style... I think. May be I am reading this wrong but my Running Xen book states on page 183, paragraph 1, that most users will not need this type of functionality. What are your thoughts? - Brian On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote:> > On Thu, Oct 8, 2009 at 11:37 AM, Brian Krusic <brian@krusic.com> > wrote: > Hi all, > > In the older format using Xen 3.0.3 (domains created via xm), I > simply created a sym link from /etc/xen/domU config file to /etc/xen/ > auto. > > I am now using virt-install (Xen 3.4.1) which creates the domU > config in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and > noticed that no auto starting of the domU happens. > > I''ve looked in both my Xen books and only find that /etc/xen/auto is > the place to auto start domUs. > > Any ideas on how to auto start gracefully while not writing a script > in /etc/rc3.d every time a new domU comes on line? > > And why are xm create and virt-install so diff in how they approach > domU configs? This is confusing. > > - Brian > > > I just updated to 3.4.1 and autostart stopped working. I copied the > xen domU file into /etc/xen/auto and it started working again. > Xendomains kept complaining that my domU file was not valid. Start > there. > > Grant McWilliams > _______________________________________________ > 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
> > > > I found some tidits on converting the simpler domU config to the newer SXP > style... I think. > > May be I am reading this wrong but my Running Xen book states on page 183, > paragraph 1, that most users will not need this type of functionality. > > What are your thoughts? > > - Brian > > On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote: >Brian, I know that I only use the older style Xen config files in /etc/xen/ and they work fine. They''re really not that touch to put together since there''s only about 5 lines in them. Grant McWilliams _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I will opt to follow suite and do the older format. Regarding the SXP format, page 184, paragraph 3; Creating a guest can be complicated because there are so many variables to set up... Yea, you got that right! - Brian On Oct 8, 2009, at 12:53 PM, Grant McWilliams wrote:> > > I found some tidits on converting the simpler domU config to the > newer SXP style... I think. > > May be I am reading this wrong but my Running Xen book states on > page 183, paragraph 1, that most users will not need this type of > functionality. > > What are your thoughts? > > - Brian > > On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote: > > Brian, > I know that I only use the older style Xen config files in /etc/ > xen/ and they work fine. They''re really not that touch to put > together since there''s only about 5 lines in them. > > Grant McWilliams > _______________________________________________ > 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
One big problem I see is consistency. Wether GUI or CLI, in 3.4.1, SXP is the default. And I personally have to assume others will need to manage this Xen infrastructure I''ve sold management on and have created. So I must conform to the way of SXP unfortunately. It does make things more complicated at first glance. Just my thoughts. - Brian On Oct 8, 2009, at 12:53 PM, Grant McWilliams wrote:> > > I found some tidits on converting the simpler domU config to the > newer SXP style... I think. > > May be I am reading this wrong but my Running Xen book states on > page 183, paragraph 1, that most users will not need this type of > functionality. > > What are your thoughts? > > - Brian > > On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote: > > Brian, > I know that I only use the older style Xen config files in /etc/ > xen/ and they work fine. They''re really not that touch to put > together since there''s only about 5 lines in them. > > Grant McWilliams > _______________________________________________ > 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
On Fri, Oct 9, 2009 at 3:29 AM, Brian Krusic <brian@krusic.com> wrote:> One big problem I see is consistency. > Wether GUI or CLI, in 3.4.1, SXP is the default.Last time I check virt-install is not part of Xen. It''s a separate project by Redhat.> And I personally have to assume others will need to manage this Xen > infrastructure I''ve sold management on and have created.I do it the old-fashioned way : create old-style config files and symlinks manually :D> So I must conform to the way of SXP unfortunately. > It does make things more > complicated at first glance. > Just my thoughts.Ask Redhat to have "on_xend_start/stop" parameter configurable when creating new guests? Also ask Xen developers to have a new "xm" command that can change the value of "on_xend_start/stop" without having to delete - edit - recreate domU? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Yes, its the same script and they call the same thing which is diff on each system. So my conventional Centos 5 system has virt-manager 0.5.3-10 and libvirt 0.3.3-1, found at the Centos repos. Where as my Gitco-ized Centos 5 system has virt-manager 0.7.0-1 and libvirt 0.7.0-6. These packages were updated using the Gitco 3.4.1 repo so I know they are in the Xensource domain. I think Xensource fundamentally changed domU config methodology and I can see the advantages of setting startup behavior within a domU config file because sym links are too easy to blow away. Its too bad the SXP format is like pig latin and looks more like code. - Brian On Oct 8, 2009, at 3:26 PM, Fajar A. Nugraha wrote:> On Fri, Oct 9, 2009 at 3:29 AM, Brian Krusic <brian@krusic.com> wrote: >> One big problem I see is consistency. >> Wether GUI or CLI, in 3.4.1, SXP is the default. > > Last time I check virt-install is not part of Xen. It''s a separate > project by Redhat. > >> And I personally have to assume others will need to manage this Xen >> infrastructure I''ve sold management on and have created. > > I do it the old-fashioned way : create old-style config files and > symlinks manually :D > >> So I must conform to the way of SXP unfortunately. >> It does make things more >> complicated at first glance. >> Just my thoughts. > > Ask Redhat to have "on_xend_start/stop" parameter configurable when > creating new guests? > Also ask Xen developers to have a new "xm" command that can change the > value of "on_xend_start/stop" without having to delete - edit - > recreate domU? > > -- > Fajar > > _______________________________________________ > 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
Hi, I just noticed something diff between the 2 systems, the plain Centos 5 system that is completely up to date and the Centos 5 system having the Gitco repo. The virt-install on the Centos system is 566 lines and the Gitco one is 937. Since they both have RHEL as the author I assume they both came from Redhat but why is the Gitco system diff? I did an update on my plain Centos system and it didn''t suck down a newer version of the script. Any ideas? Am I looking at this completely wrong? - Brian On Oct 8, 2009, at 3:26 PM, Fajar A. Nugraha wrote:> On Fri, Oct 9, 2009 at 3:29 AM, Brian Krusic <brian@krusic.com> wrote: >> One big problem I see is consistency. >> Wether GUI or CLI, in 3.4.1, SXP is the default. > > Last time I check virt-install is not part of Xen. It''s a separate > project by Redhat. > >> And I personally have to assume others will need to manage this Xen >> infrastructure I''ve sold management on and have created. > > I do it the old-fashioned way : create old-style config files and > symlinks manually :D > >> So I must conform to the way of SXP unfortunately. >> It does make things more >> complicated at first glance. >> Just my thoughts. > > Ask Redhat to have "on_xend_start/stop" parameter configurable when > creating new guests? > Also ask Xen developers to have a new "xm" command that can change the > value of "on_xend_start/stop" without having to delete - edit - > recreate domU? > > -- > Fajar > > _______________________________________________ > 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
On Thu, 2009-10-08 at 11:37 -0700, Brian Krusic wrote:> Hi all, > > In the older format using Xen 3.0.3 (domains created via xm), I simply > created a sym link from /etc/xen/domU config file to /etc/xen/auto. > > I am now using virt-install (Xen 3.4.1) which creates the domU config > in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and > noticed that no auto starting of the domU happens. > > I''ve looked in both my Xen books and only find that /etc/xen/auto is > the place to auto start domUs. > > Any ideas on how to auto start gracefully while not writing a script > in /etc/rc3.d every time a new domU comes on line? > > And why are xm create and virt-install so diff in how they approach > domU configs? This is confusing. > > - BrianI''ve read through this thread. Is there a consensus here? When I first started on xen it used the files in /etc/xen/vm for configs, and to autostart on boot you would put a softlink under /etc/xen/auto. With newer versions (I''m on 3.2.x) I''m using xenstore, but I don''t like the process. 1) I create a new domU with virt-manager 2) I then shutdown the domU 3) save a conf of the domU: xm list -l [domU name] > [domU name].conf 4) edit this conf file for the start and stop lines 5) remove the domU from virt-manager 6) reinstall it with: xm new -F [domU name].conf I really don''t like this process at all and it doesn''t work 100% of the time for setting a domU to auto start. Plus, with it set this way I can''t restart xend without hosing the running domUs. I think if I change the stop to ignore it would help. Drawback is I''d have to manually shutdown all the domU''s before restarting the server. Right now I have memory issues on two of my servers. I need to reboot both servers, which affects roughly 20 domU''s, both linux pv''s and windows hvm''s. I don''t know for sure, but it seems that restarting xend might fix the problem for me. It was much nicer when it was a simple soft link in auto to the config in vm. From this thread it sounds like you can still do this? Does that mean no more virt-manager? Should I be doing this a different way? Thanks, James ps- sorry this got so long.... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Oct 9, 2009 at 12:22 PM, James Pifer <jep@obrien-pifer.com> wrote:> On Thu, 2009-10-08 at 11:37 -0700, Brian Krusic wrote: > > Hi all, > > > > In the older format using Xen 3.0.3 (domains created via xm), I simply > > created a sym link from /etc/xen/domU config file to /etc/xen/auto. > > > > I am now using virt-install (Xen 3.4.1) which creates the domU config > > in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and > > noticed that no auto starting of the domU happens. > > > > I''ve looked in both my Xen books and only find that /etc/xen/auto is > > the place to auto start domUs. > > > > Any ideas on how to auto start gracefully while not writing a script > > in /etc/rc3.d every time a new domU comes on line? > > > > And why are xm create and virt-install so diff in how they approach > > domU configs? This is confusing. > > > > - Brian > > I''ve read through this thread. Is there a consensus here? When I first > started on xen it used the files in /etc/xen/vm for configs, and to > autostart on boot you would put a softlink under /etc/xen/auto. > > > Should I be doing this a different way? > > Thanks, > James > ps- sorry this got so long.... > >You know I could be wrong on this but I think the config.sxp way has to do with libvirt. Virt-install and virsh manage libvirt domains I believe. The first thing I do to a Xen Dom0 is shutdown libvirtd or delete the bridge that it creates so I can manage everything I do myself. This also means I create /etc/xen/config files from template. Grant _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Cool post James, glad I''m not the only one. Eagerly awaiting feedback. - Brian On Oct 9, 2009, at 12:22 PM, James Pifer wrote:> On Thu, 2009-10-08 at 11:37 -0700, Brian Krusic wrote: >> Hi all, >> >> In the older format using Xen 3.0.3 (domains created via xm), I >> simply >> created a sym link from /etc/xen/domU config file to /etc/xen/auto. >> >> I am now using virt-install (Xen 3.4.1) which creates the domU config >> in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. >> >> So I sym link this to a file in /etc/xen/auto/hostname_of_domU and >> noticed that no auto starting of the domU happens. >> >> I''ve looked in both my Xen books and only find that /etc/xen/auto is >> the place to auto start domUs. >> >> Any ideas on how to auto start gracefully while not writing a script >> in /etc/rc3.d every time a new domU comes on line? >> >> And why are xm create and virt-install so diff in how they approach >> domU configs? This is confusing. >> >> - Brian > > I''ve read through this thread. Is there a consensus here? When I first > started on xen it used the files in /etc/xen/vm for configs, and to > autostart on boot you would put a softlink under /etc/xen/auto. > > With newer versions (I''m on 3.2.x) I''m using xenstore, but I don''t > like > the process. > > 1) I create a new domU with virt-manager > 2) I then shutdown the domU > 3) save a conf of the domU: xm list -l [domU name] > [domU name].conf > 4) edit this conf file for the start and stop lines > 5) remove the domU from virt-manager > 6) reinstall it with: xm new -F [domU name].conf > > I really don''t like this process at all and it doesn''t work 100% of > the > time for setting a domU to auto start. Plus, with it set this way I > can''t restart xend without hosing the running domUs. I think if I > change > the stop to ignore it would help. Drawback is I''d have to manually > shutdown all the domU''s before restarting the server. > > Right now I have memory issues on two of my servers. I need to reboot > both servers, which affects roughly 20 domU''s, both linux pv''s and > windows hvm''s. I don''t know for sure, but it seems that restarting > xend > might fix the problem for me. > > It was much nicer when it was a simple soft link in auto to the config > in vm. From this thread it sounds like you can still do this? Does > that > mean no more virt-manager? > > Should I be doing this a different way? > > Thanks, > James > ps- sorry this got so long.... > > > _______________________________________________ > 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
Wow, thats a great idea. I never even thought of shutting that stuff down. Do you keep libvirt off and remove the bridge permanently? You mind posting some example configs? I realize they are only a few lines long and I have a few to base others on but I am curious. This seems like a cool way of doing it. - Brian On Oct 9, 2009, at 12:33 PM, Grant McWilliams wrote:> > On Fri, Oct 9, 2009 at 12:22 PM, James Pifer <jep@obrien-pifer.com> > wrote: > On Thu, 2009-10-08 at 11:37 -0700, Brian Krusic wrote: > > Hi all, > > > > In the older format using Xen 3.0.3 (domains created via xm), I > simply > > created a sym link from /etc/xen/domU config file to /etc/xen/auto. > > > > I am now using virt-install (Xen 3.4.1) which creates the domU > config > > in /var/lib/xend/domains/UUID_#_of_domU/config.sxp. > > > > So I sym link this to a file in /etc/xen/auto/hostname_of_domU and > > noticed that no auto starting of the domU happens. > > > > I''ve looked in both my Xen books and only find that /etc/xen/auto is > > the place to auto start domUs. > > > > Any ideas on how to auto start gracefully while not writing a script > > in /etc/rc3.d every time a new domU comes on line? > > > > And why are xm create and virt-install so diff in how they approach > > domU configs? This is confusing. > > > > - Brian > > I''ve read through this thread. Is there a consensus here? When I first > started on xen it used the files in /etc/xen/vm for configs, and to > autostart on boot you would put a softlink under /etc/xen/auto. > > > Should I be doing this a different way? > > Thanks, > James > ps- sorry this got so long.... > > > You know I could be wrong on this but I think the config.sxp way has > to do with > libvirt. Virt-install and virsh manage libvirt domains I believe. > The first thing I do > to a Xen Dom0 is shutdown libvirtd or delete the bridge that it > creates so I can manage > everything I do myself. This also means I create /etc/xen/config > files from template. > > Grant > _______________________________________________ > 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
On Fri, Oct 9, 2009 at 12:50 PM, Brian Krusic <brian@krusic.com> wrote:> Wow, thats a great idea. > I never even thought of shutting that stuff down. > > Do you keep libvirt off and remove the bridge permanently? > > You mind posting some example configs? > > I realize they are only a few lines long and I have a few to base others on > but I am curious. > > This seems like a cool way of doing it. > > - Brian > > On Oct 9, 2009, at 12:33 PM, Grant McWilliams wrote: >Brian, You have a couple of choices if you don''t want to use the libvirtd bridge. You can edit /etc/libvirt/qemu/networks/autostart/default.xml file to get rid of (or change the name of) the bridge that''s started by libvirt. You can just delete the default.xml file form autostart and it won''t create it at all. If xen is the only reason you have libvirtd (probably unless you use more than one virtualizer which isn''t likely) then you can just shut the service down altogether. I usually just go for deleting the default.xml file. I started doing this when I noticed that xen would create a bridge and libvirt would create a bridge and they weren''t the same bridge. The line in xend-config.sxp that specifies my bridge is here (network-script ''network-virtual bridge="classnet0" bridgeip=" 192.168.1.254/24" brnet="192.168.1.0/24"'') Standard /etc/xen/config file. name = "classserver" memory = "1024" disk = [ ''tap:aio:/srv/xen/classserver-os.img,sda,w'',''tap:aio:/srv/xen/classserver-data.img,sdb,w'',] vif = [ ''mac=aa:cc:00:00:00:01'' ] bootloader="/usr/bin/pygrub" on_reboot = ''restart'' on_crash = ''restart'' on_xend_start = ''start'' on_xend_stop = ''shutdown'' Notice that I''m setting the mac address to the DomU but nothing else? With CentOS you can''t specify IP addresses in the vif line without recompiling the kernel but you can specify mac addresses. I specify the mac address and then inside the classnet0 network I have a dnsmasq server that gives out IPs based on mac address. That way I can specify IPs inside the CentOS domUs without recompiling. Grant McWilliams Some people, when confronted with a problem, think "I know, I''ll use Windows." Now they have two problems. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
wow again, very very cool approach. yoda mang! thanks very much for the info. - Brian On Oct 9, 2009, at 1:33 PM, Grant McWilliams wrote:> > > > > On Fri, Oct 9, 2009 at 12:50 PM, Brian Krusic <brian@krusic.com> > wrote: > Wow, thats a great idea. > > I never even thought of shutting that stuff down. > > Do you keep libvirt off and remove the bridge permanently? > > You mind posting some example configs? > > I realize they are only a few lines long and I have a few to base > others on but I am curious. > > This seems like a cool way of doing it. > > - Brian > > On Oct 9, 2009, at 12:33 PM, Grant McWilliams wrote: > > Brian, > > You have a couple of choices if you don''t want to use the libvirtd > bridge. You can edit /etc/libvirt/qemu/networks/autostart/default.xml > file to get rid of (or change the name of) the bridge that''s started > by libvirt. You can just delete the default.xml file form autostart > and it won''t create it at all. If xen is the only reason you have > libvirtd (probably unless you use more than one virtualizer which > isn''t likely) then you can just shut the service down altogether. I > usually just go for deleting the default.xml file. I started doing > this when I noticed that xen would create a bridge and libvirt would > create a bridge and they weren''t the same bridge. > > The line in xend-config.sxp that specifies my bridge is here > > (network-script ''network-virtual bridge="classnet0" > bridgeip="192.168.1.254/24" brnet="192.168.1.0/24"'') > > Standard /etc/xen/config file. > > name = "classserver" > memory = "1024" > disk = [ ''tap:aio:/srv/xen/classserver-os.img,sda,w'',''tap:aio:/srv/ > xen/classserver-data.img,sdb,w'',] > vif = [ ''mac=aa:cc:00:00:00:01'' ] > bootloader="/usr/bin/pygrub" > on_reboot = ''restart'' > on_crash = ''restart'' > on_xend_start = ''start'' > on_xend_stop = ''shutdown'' > > Notice that I''m setting the mac address to the DomU but nothing > else? With CentOS you can''t specify IP addresses in the vif line > without recompiling the kernel but you can specify mac addresses. I > specify the mac address and then inside the classnet0 network I have > a dnsmasq server that gives out IPs based on mac address. That way I > can specify IPs inside the CentOS domUs without recompiling. > > > Grant McWilliams > > Some people, when confronted with a problem, think "I know, I''ll use > Windows." > Now they have two problems. > _______________________________________________ > 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
Hi Grant, I moved one of my domUs from an older system having the /etc/xen/domU config format onto the newer system which uses the config.sxp format and I can''t see the domU. I restarted xend, etc... to no avail. No strange errors in the xen logs either. Were you able to get older domUs into Xen3.4.1? - Brian On Oct 9, 2009, at 1:33 PM, Grant McWilliams wrote:> > > > > On Fri, Oct 9, 2009 at 12:50 PM, Brian Krusic <brian@krusic.com> > wrote: > Wow, thats a great idea. > > I never even thought of shutting that stuff down. > > Do you keep libvirt off and remove the bridge permanently? > > You mind posting some example configs? > > I realize they are only a few lines long and I have a few to base > others on but I am curious. > > This seems like a cool way of doing it. > > - Brian > > On Oct 9, 2009, at 12:33 PM, Grant McWilliams wrote: > > Brian, > > You have a couple of choices if you don''t want to use the libvirtd > bridge. You can edit /etc/libvirt/qemu/networks/autostart/default.xml > file to get rid of (or change the name of) the bridge that''s started > by libvirt. You can just delete the default.xml file form autostart > and it won''t create it at all. If xen is the only reason you have > libvirtd (probably unless you use more than one virtualizer which > isn''t likely) then you can just shut the service down altogether. I > usually just go for deleting the default.xml file. I started doing > this when I noticed that xen would create a bridge and libvirt would > create a bridge and they weren''t the same bridge. > > The line in xend-config.sxp that specifies my bridge is here > > (network-script ''network-virtual bridge="classnet0" > bridgeip="192.168.1.254/24" brnet="192.168.1.0/24"'') > > Standard /etc/xen/config file. > > name = "classserver" > memory = "1024" > disk = [ ''tap:aio:/srv/xen/classserver-os.img,sda,w'',''tap:aio:/srv/ > xen/classserver-data.img,sdb,w'',] > vif = [ ''mac=aa:cc:00:00:00:01'' ] > bootloader="/usr/bin/pygrub" > on_reboot = ''restart'' > on_crash = ''restart'' > on_xend_start = ''start'' > on_xend_stop = ''shutdown'' > > Notice that I''m setting the mac address to the DomU but nothing > else? With CentOS you can''t specify IP addresses in the vif line > without recompiling the kernel but you can specify mac addresses. I > specify the mac address and then inside the classnet0 network I have > a dnsmasq server that gives out IPs based on mac address. That way I > can specify IPs inside the CentOS domUs without recompiling. > > > Grant McWilliams > > Some people, when confronted with a problem, think "I know, I''ll use > Windows." > Now they have two problems. > _______________________________________________ > 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
On Mon, Oct 12, 2009 at 11:10 AM, Brian Krusic <brian@krusic.com> wrote:> Hi Grant, > I moved one of my domUs from an older system having the /etc/xen/domU > config format onto the newer system which uses the config.sxp format and I > can''t see the domU. > > I restarted xend, etc... to no avail. No strange errors in the xen logs > either. > > Were you able to get older domUs into Xen3.4.1? > > - Brian > > On Oct 9, 2009, at 1:33 PM, Grant McWilliams wrote: >Yes, I use the old style exclusively with Xen 3.4.1. What do you mean you can''t see the DomU? If you do an xm create DomU does it start? Or is it just not auto starting? Make sure the xendomains service is running. Grant McWilliams Some people, when confronted with a problem, think "I know, I''ll use Windows." Now they have two problems. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ah, I see, they no don''t show in the virtual machine manager. Kind of strange. - Brian On Oct 12, 2009, at 11:21 AM, Grant McWilliams wrote:> > On Mon, Oct 12, 2009 at 11:10 AM, Brian Krusic <brian@krusic.com> > wrote: > Hi Grant, > > I moved one of my domUs from an older system having the /etc/xen/ > domU config format onto the newer system which uses the config.sxp > format and I can''t see the domU. > > I restarted xend, etc... to no avail. No strange errors in the xen > logs either. > > Were you able to get older domUs into Xen3.4.1? > > - Brian > > On Oct 9, 2009, at 1:33 PM, Grant McWilliams wrote: > > Yes, I use the old style exclusively with Xen 3.4.1. What do you > mean you can''t see the DomU? If you do an xm create DomU does it > start? Or is it just not auto starting? Make sure the xendomains > service is running. > > > Grant McWilliams > > Some people, when confronted with a problem, think "I know, I''ll use > Windows." > Now they have two problems. > > > _______________________________________________ > 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
On Mon, Oct 12, 2009 at 11:34 AM, Brian Krusic <brian@krusic.com> wrote:> Ah, I see, they no don''t show in the virtual machine manager. > Kind of strange. > > - Brian > > On Oct 12, 2009, at 11:21 AM, Grant McWilliams wrote: >I believe the Virtual Machine manager only manages libvirt domains so they won''t show. Try xm list and see if they show up. I''m sure they will if you started them with xm create. Grant McWilliams Some people, when confronted with a problem, think "I know, I''ll use Windows." Now they have two problems. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users