[opensuse-virtual] Xen hypervisor developement conforming to openSUSE
We are forward porting our secure hypervisor variant of Xen and tried openSUSE as an alternative to our previous platform. We like openSUSE so much that we'd like to make our hypervisor work conform to the openSUSE process. We are not working on dom0 or other guests, but the hypervisor code itself. We have installed the xen-3.3.1-testing-src rpm. At that point, we could just "make world" and continue as we have in the past, but it does not look like that would conform to the way YaST and friends are installing Xen. Is there a written description of what we should do differently than "make world" or "make install-xen", to make our prototype "YaST" conforming? Sincerely, John ---- What is the formal meaning of the one-line program #include "/dev/tty" -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
hi, On Fri, Feb 27, 2009 at 12:07 PM, John McDermott (U.S. Navy Employee) <john.mcdermott@nrl.navy.mil> wrote:
Is there a written description of what we should do differently than "make world" or "make install-xen", to make our prototype "YaST" conforming?
don't know if that helps at all ... in my experience, the way-of-nonstandard-xen-on-suse is not well documented at all. that said, the opemSUSE's distro-released xen, rpm -qa | grep -i ^xen xen-doc-html-3.3.1_18494_03-1.8 xen-doc-pdf-3.3.1_18494_03-1.8 xen-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 xen-libs-3.3.1_18494_03-1.8 runs well, and we're happy with the openSUSE-based 'alternatives' to, e.g., networking & bridging setup using the upstream-xen scripts. as for released- or customized source, much of the openSUSE-friendliness is embodied in the rmp spec file zypper si xen cat /usr/src/packages/SPECS/xen.spec ... &, of course, a "prep'd" build env can be had with, rpmbuild -bp /usr/src/packages/SPECS/xen.spec one changes are _correctly_ made to that src tree, rpmbuild ... continues on with the build/install. we've tried & failed to crowbar/full-replace prior versions of 'vanilla' upstream src into the suse build/install process, and have a correctly sync'd kernel-xen, and never got past problems. ultimately we settled on starting with and mod'ing distro's xen src _because_ it's close-to-most-recent xen code, and interoperable with a 'modern' kernel (atm, 2.6.27.19-3.2-xen). and, it works like a champ! of course, _we_ will be very interested to hear knowledgeable responses from the *suse folks to your question. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Fri, Feb 27, 2009 at 1:52 PM, PGNet <pgnet.trash+osvm@gmail.com> wrote:
hi,
On Fri, Feb 27, 2009 at 12:07 PM, John McDermott (U.S. Navy Employee) <john.mcdermott@nrl.navy.mil> wrote:
Is there a written description of what we should do differently than "make world" or "make install-xen", to make our prototype "YaST" conforming?
don't know if that helps at all ...
in my experience, the way-of-nonstandard-xen-on-suse is not well documented at all.
that said, the opemSUSE's distro-released xen,
rpm -qa | grep -i ^xen xen-doc-html-3.3.1_18494_03-1.8 xen-doc-pdf-3.3.1_18494_03-1.8 xen-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 xen-libs-3.3.1_18494_03-1.8
runs well, and we're happy with the openSUSE-based 'alternatives' to, e.g., networking & bridging setup using the upstream-xen scripts.
as for released- or customized source, much of the openSUSE-friendliness is embodied in the rmp spec file
zypper si xen cat /usr/src/packages/SPECS/xen.spec ...
&, of course, a "prep'd" build env can be had with,
rpmbuild -bp /usr/src/packages/SPECS/xen.spec
one changes are _correctly_ made to that src tree, rpmbuild ... continues on with the build/install.
we've tried & failed to crowbar/full-replace prior versions of 'vanilla' upstream src into the suse build/install process, and have a correctly sync'd kernel-xen, and never got past problems. ultimately we settled on starting with and mod'ing distro's xen src _because_ it's close-to-most-recent xen code, and interoperable with a 'modern' kernel (atm, 2.6.27.19-3.2-xen).
and, it works like a champ!
of course, _we_ will be very interested to hear knowledgeable responses from the *suse folks to your question.
Something to look into is build.opensuse.org (OBS - build service). You can link to the packages, apply your patch, and then it will build it on the fly in a completely clean/new jail. I use it for my stuff (non xen). There is also the osc command where you can do a lot of it from the command line. Stephen -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
participants (3)
-
John McDermott (U.S. Navy Employee) -
PGNet -
Stephen Shaw