could some one give me detail about the needed packages and all steps to "upgrade" a fresh osol 2009.06 with the stuff from one of the gates? The provide build instructions are not really complete. (http://opensolaris.org/os/project/xen-gate/BuildInstructions/) I''d like to try this to figure out if the server reboot problem we have (http://defect.opensolaris.org/bz/show_bug.cgi?id=9216) is solved with the new xvm stuff. florian
2009/6/24 Florian Manschwetus <florianmanschwetus@gmx.de>:> could some one give me detail about the needed packages and all steps to > "upgrade" a fresh osol 2009.06 with the stuff from one of the gates? > The provide build instructions are not really complete. > (http://opensolaris.org/os/project/xen-gate/BuildInstructions/)The build instructions assume that you''re on SX:CE, and have the studio12 compiler installed: http://opensolaris.org/os/community/tools/sun_studio_tools/ Building the xen bits should be no problem using the above mentioned build instructions. For the dom0 kernel you have to do a "ON" compilation, which I described here: http://www.opensolaris.org/jive/thread.jspa?messageID=382068#382068 With opensolaris 2009.06 things are a bit different. The following page contains some hints what needs to be installed on opensolaris for an "ON" compilation: http://opensolaris.org/os/project/indiana/building_on/
libvirt fails to build here: Undefined first referenced symbol in file virNodeDeviceWaitForDevices ../src/.libs/libvirt_driver_storage.a(storage_backend.o) ld: fatal: symbol referencing errors. No output written to .libs/libvirtd gmake[2]: *** [libvirtd] Error 1 gmake[1]: *** [install] Error 2 gmake: *** [install-recursive] Error 1 could some one helo here? Florian Am 24.06.2009 10:12, schrieb Juergen Keil:> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >> could some one give me detail about the needed packages and all steps to >> "upgrade" a fresh osol 2009.06 with the stuff from one of the gates? >> The provide build instructions are not really complete. >> (http://opensolaris.org/os/project/xen-gate/BuildInstructions/) > > The build instructions assume that you''re on SX:CE, and have > the studio12 compiler installed: > > http://opensolaris.org/os/community/tools/sun_studio_tools/ > > > Building the xen bits should be no problem using the > above mentioned build instructions. > > For the dom0 kernel you have to do a "ON" compilation, which > I described here: > > http://www.opensolaris.org/jive/thread.jspa?messageID=382068#382068 > > > With opensolaris 2009.06 things are a bit different. > The following page contains some hints what needs to be > installed on opensolaris for an "ON" compilation: > > http://opensolaris.org/os/project/indiana/building_on/ >
Am 24.06.2009 11:42, schrieb Florian Manschwetus:> libvirt fails to build here: > Undefined first referenced > symbol in file > virNodeDeviceWaitForDevices > ../src/.libs/libvirt_driver_storage.a(storage_backend.o) > ld: fatal: symbol referencing errors. No output written to .libs/libvirtd > gmake[2]: *** [libvirtd] Error 1 > gmake[1]: *** [install] Error 2 > gmake: *** [install-recursive] Error 1 > > could some one helo here? > > FlorianOk, we have found a patch in a newsgroup libvirt builds now. But the package build step fails... Florian> > Am 24.06.2009 10:12, schrieb Juergen Keil: >> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>> could some one give me detail about the needed packages and all steps to >>> "upgrade" a fresh osol 2009.06 with the stuff from one of the gates? >>> The provide build instructions are not really complete. >>> (http://opensolaris.org/os/project/xen-gate/BuildInstructions/) >> >> The build instructions assume that you''re on SX:CE, and have >> the studio12 compiler installed: >> >> http://opensolaris.org/os/community/tools/sun_studio_tools/ >> >> >> Building the xen bits should be no problem using the >> above mentioned build instructions. >> >> For the dom0 kernel you have to do a "ON" compilation, which >> I described here: >> >> http://www.opensolaris.org/jive/thread.jspa?messageID=382068#382068 >> >> >> With opensolaris 2009.06 things are a bit different. >> The following page contains some hints what needs to be >> installed on opensolaris for an "ON" compilation: >> >> http://opensolaris.org/os/project/indiana/building_on/ >> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Am 24.06.2009 12:39, schrieb Florian Manschwetus:> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >> libvirt fails to build here: >> Undefined first referenced >> symbol in file >> virNodeDeviceWaitForDevices >> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >> ld: fatal: symbol referencing errors. No output written to .libs/libvirtd >> gmake[2]: *** [libvirtd] Error 1 >> gmake[1]: *** [install] Error 2 >> gmake: *** [install-recursive] Error 1 >> >> could some one helo here? >> >> Florian > > Ok, we have found a patch in a newsgroup libvirt builds now. > But the package build step fails... > > Florian==> log/packages.err <=make[2]: *** No rule to make target `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', needed by `i.manifest''. Stop. make[1]: *** [SUNWxvmr] Error 2 make: *** [pkgdefs] Error 2 ==> log/packages.out <=mkdir -p /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/ for f in xenstore-snoop; do \ cp cmd/$f /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/; \ done /export/home/tkadmin/xvm-3.4/sunos.hg/src/svc make[1]: Entering directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' make[1]: Nothing to be done for `all''. make[1]: Leaving directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs make[1]: Entering directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr make[2]: Entering directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' make[2]: Leaving directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' make[1]: Leaving directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' These are the details I have... Florian
Hi Florian, Yeah, it looks like something is missing in your build environment? I''ll build up a system to figure out why it''s failing for you. (My build system is still nevada since OpenSolaris is trailing a bit behind the current build at the moment) MRJ Florian Manschwetus wrote:> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >>> libvirt fails to build here: >>> Undefined first referenced >>> symbol in file >>> virNodeDeviceWaitForDevices >>> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >>> ld: fatal: symbol referencing errors. No output written to >>> .libs/libvirtd >>> gmake[2]: *** [libvirtd] Error 1 >>> gmake[1]: *** [install] Error 2 >>> gmake: *** [install-recursive] Error 1 >>> >>> could some one helo here? >>> >>> Florian >> >> Ok, we have found a patch in a newsgroup libvirt builds now. >> But the package build step fails... >> >> Florian > ==> log/packages.err <=> make[2]: *** No rule to make target > `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', > needed by `i.manifest''. Stop. > make[1]: *** [SUNWxvmr] Error 2 > make: *** [pkgdefs] Error 2 > > ==> log/packages.out <=> mkdir -p /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/ > for f in xenstore-snoop; do \ > cp cmd/$f > /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/; \ > done > /export/home/tkadmin/xvm-3.4/sunos.hg/src/svc > make[1]: Entering directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' > make[1]: Nothing to be done for `all''. > make[1]: Leaving directory `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' > /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs > make[1]: Entering directory > `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' > /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr > make[2]: Entering directory > `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' > make[2]: Leaving directory > `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' > make[1]: Leaving directory > `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' > > These are the details I have... > Florian > > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Am 24.06.2009 15:38, schrieb Mark Johnson:> > Hi Florian, > > > Yeah, it looks like something is missing in your > build environment?Uhm, is somewhere a list what should be in my build environment? Florian> > I''ll build up a system to figure out why it''s > failing for you. (My build system is still nevada > since OpenSolaris is trailing a bit behind the current > build at the moment) > > > > MRJ > > > > > Florian Manschwetus wrote: >> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >>>> libvirt fails to build here: >>>> Undefined first referenced >>>> symbol in file >>>> virNodeDeviceWaitForDevices >>>> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >>>> ld: fatal: symbol referencing errors. No output written to >>>> .libs/libvirtd >>>> gmake[2]: *** [libvirtd] Error 1 >>>> gmake[1]: *** [install] Error 2 >>>> gmake: *** [install-recursive] Error 1 >>>> >>>> could some one helo here? >>>> >>>> Florian >>> >>> Ok, we have found a patch in a newsgroup libvirt builds now. >>> But the package build step fails... >>> >>> Florian >> ==> log/packages.err <=>> make[2]: *** No rule to make target >> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >> needed by `i.manifest''. Stop. >> make[1]: *** [SUNWxvmr] Error 2 >> make: *** [pkgdefs] Error 2 >> >> ==> log/packages.out <=>> mkdir -p /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/ >> for f in xenstore-snoop; do \ >> cp cmd/$f >> /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/; \ >> done >> /export/home/tkadmin/xvm-3.4/sunos.hg/src/svc >> make[1]: Entering directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' >> make[1]: Nothing to be done for `all''. >> make[1]: Leaving directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' >> /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs >> make[1]: Entering directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' >> /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr >> make[2]: Entering directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' >> make[2]: Leaving directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' >> make[1]: Leaving directory >> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' >> >> These are the details I have... >> Florian >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >
Florian Manschwetus wrote:> Am 24.06.2009 15:38, schrieb Mark Johnson: >> >> Hi Florian, >> >> >> Yeah, it looks like something is missing in your >> build environment? > Uhm, is somewhere a list what should be in my build environment?No. That''s what I''m going to come up with :-) MRJ> Florian >> >> I''ll build up a system to figure out why it''s >> failing for you. (My build system is still nevada >> since OpenSolaris is trailing a bit behind the current >> build at the moment) >> >> >> >> MRJ >> >> >> >> >> Florian Manschwetus wrote: >>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >>>>> libvirt fails to build here: >>>>> Undefined first referenced >>>>> symbol in file >>>>> virNodeDeviceWaitForDevices >>>>> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >>>>> ld: fatal: symbol referencing errors. No output written to >>>>> .libs/libvirtd >>>>> gmake[2]: *** [libvirtd] Error 1 >>>>> gmake[1]: *** [install] Error 2 >>>>> gmake: *** [install-recursive] Error 1 >>>>> >>>>> could some one helo here? >>>>> >>>>> Florian >>>> >>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>> But the package build step fails... >>>> >>>> Florian >>> ==> log/packages.err <=>>> make[2]: *** No rule to make target >>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>> needed by `i.manifest''. Stop. >>> make[1]: *** [SUNWxvmr] Error 2 >>> make: *** [pkgdefs] Error 2 >>> >>> ==> log/packages.out <=>>> mkdir -p /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/ >>> for f in xenstore-snoop; do \ >>> cp cmd/$f >>> /export/home/tkadmin/xvm-3.4//proto/install//usr/lib/xen/bin/; \ >>> done >>> /export/home/tkadmin/xvm-3.4/sunos.hg/src/svc >>> make[1]: Entering directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' >>> make[1]: Nothing to be done for `all''. >>> make[1]: Leaving directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/svc'' >>> /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs >>> make[1]: Entering directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' >>> /export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr >>> make[2]: Entering directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' >>> make[2]: Leaving directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs/SUNWxvmr'' >>> make[1]: Leaving directory >>> `/export/home/tkadmin/xvm-3.4/sunos.hg/src/pkgdefs'' >>> >>> These are the details I have... >>> Florian >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >> > >
2009/6/24 Florian Manschwetus <florianmanschwetus@gmx.de>:> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >> >> libvirt fails to build here: >> Undefined first referenced >> symbol in file >> virNodeDeviceWaitForDevices >> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >> ld: fatal: symbol referencing errors. No output written to .libs/libvirtd >> gmake[2]: *** [libvirtd] Error 1 >> gmake[1]: *** [install] Error 2 >> gmake: *** [install-recursive] Error 1 >> >> could some one helo here? >> >> Florian > > Ok, we have found a patch in a newsgroup libvirt builds now. > But the package build step fails...What exactly did you have to patch? On SX:CE this does build just fine, without patching anything... On OpenSolaris 2009.06 I had to pkg install SUNWbcc, and make sure that /opt/SUNWspro points to the Studio12 compiler. But I started from an OpenSolaris 2009.06 that already had a few more packages installed in the past...
Am 24.06.2009 16:21, schrieb Juergen Keil:> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >> Am 24.06.2009 11:42, schrieb Florian Manschwetus: >>> libvirt fails to build here: >>> Undefined first referenced >>> symbol in file >>> virNodeDeviceWaitForDevices >>> ../src/.libs/libvirt_driver_storage.a(storage_backend.o) >>> ld: fatal: symbol referencing errors. No output written to .libs/libvirtd >>> gmake[2]: *** [libvirtd] Error 1 >>> gmake[1]: *** [install] Error 2 >>> gmake: *** [install-recursive] Error 1 >>> >>> could some one helo here? >>> >>> Florian >> Ok, we have found a patch in a newsgroup libvirt builds now. >> But the package build step fails... > > > What exactly did you have to patch?I needed to patch in the xvm-3.4 gate the libvirt with this patch to make it compile (the error mentioned above)(patch attached) Florian> > On SX:CE this does build just fine, without patching anything... > > On OpenSolaris 2009.06 I had to pkg install SUNWbcc, > and make sure that /opt/SUNWspro points to the Studio12 > compiler. But I started from an OpenSolaris 2009.06 that > already had a few more packages installed in the past... >
2009/6/24 Florian Manschwetus <florianmanschwetus@gmx.de>:> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >> Ok, we have found a patch in a newsgroup libvirt builds now. >> But the package build step fails... >> >> Florian > > ==> log/packages.err <=> make[2]: *** No rule to make target > `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', needed > by `i.manifest''. Stop. > make[1]: *** [SUNWxvmr] Error 2 > make: *** [pkgdefs] Error 2package build fails for me, too, on OpenSolaris 2009.06. But on my box the problem is that the script bld_awk_pkginfo aborts with a usage message: ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ 11.1 usage: blk_awk_pkginfo -p <provider> -m <mach> -o <awk_script> [-v <version>] I think this a gmake vs Sun make problem, you probably have to make sure /usr/bin is in the $PATH before /usr/gnu/bin.
Am 24.06.2009 16:30, schrieb Juergen Keil:> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>> Ok, we have found a patch in a newsgroup libvirt builds now. >>> But the package build step fails... >>> >>> Florian >> ==> log/packages.err<=>> make[2]: *** No rule to make target >> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', needed >> by `i.manifest''. Stop. >> make[1]: *** [SUNWxvmr] Error 2 >> make: *** [pkgdefs] Error 2 > > package build fails for me, too, on OpenSolaris 2009.06. > > But on my box the problem is that the script bld_awk_pkginfo > aborts with a usage message: > > ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ > 11.1 > usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> [-v<version>] > > > I think this a gmake vs Sun make problem, you probably have to make sure > /usr/bin is in the $PATH before /usr/gnu/bin. >Indeed this was the issue now package building is fine, let me revert the libvirt to see if this is also a PATH problem. Florian
Am 24.06.2009 16:56, schrieb Florian Manschwetus:> Am 24.06.2009 16:30, schrieb Juergen Keil: >> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>> But the package build step fails... >>>> >>>> Florian >>> ==> log/packages.err<=>>> make[2]: *** No rule to make target >>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>> needed >>> by `i.manifest''. Stop. >>> make[1]: *** [SUNWxvmr] Error 2 >>> make: *** [pkgdefs] Error 2 >> >> package build fails for me, too, on OpenSolaris 2009.06. >> >> But on my box the problem is that the script bld_awk_pkginfo >> aborts with a usage message: >> >> ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ >> 11.1 >> usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> [-v<version>] >> >> >> I think this a gmake vs Sun make problem, you probably have to make sure >> /usr/bin is in the $PATH before /usr/gnu/bin. >> > Indeed this was the issue now package building is fine, let me revert > the libvirt to see if this is also a PATH problem.No libvirt still needs the mentioned patch> > Florian > > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Am 24.06.2009 17:06, schrieb Florian Manschwetus:> Am 24.06.2009 16:56, schrieb Florian Manschwetus: >> Am 24.06.2009 16:30, schrieb Juergen Keil: >>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>>> But the package build step fails... >>>>> >>>>> Florian >>>> ==> log/packages.err<=>>>> make[2]: *** No rule to make target >>>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>>> needed >>>> by `i.manifest''. Stop. >>>> make[1]: *** [SUNWxvmr] Error 2 >>>> make: *** [pkgdefs] Error 2 >>> >>> package build fails for me, too, on OpenSolaris 2009.06. >>> >>> But on my box the problem is that the script bld_awk_pkginfo >>> aborts with a usage message: >>> >>> ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ >>> 11.1 >>> usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> >>> [-v<version>] >>> >>> >>> I think this a gmake vs Sun make problem, you probably have to make sure >>> /usr/bin is in the $PATH before /usr/gnu/bin. >>> >> Indeed this was the issue now package building is fine, let me revert >> the libvirt to see if this is also a PATH problem. > No libvirt still needs the mentioned patch >> >> FlorianOk, well so far, next step is the xen-gate/onnv-3.4 do I need a complete nightly? And could I install it in a different BE, so that the current system stays unchanged (some detail on needed steps or a hint to a nice howto would be helpful)? thx, Florian
Florian Manschwetus wrote:> Am 24.06.2009 16:56, schrieb Florian Manschwetus: >> Am 24.06.2009 16:30, schrieb Juergen Keil: >>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>>> But the package build step fails... >>>>> >>>>> Florian >>>> ==> log/packages.err<=>>>> make[2]: *** No rule to make target >>>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>>> needed >>>> by `i.manifest''. Stop. >>>> make[1]: *** [SUNWxvmr] Error 2 >>>> make: *** [pkgdefs] Error 2 >>> >>> package build fails for me, too, on OpenSolaris 2009.06. >>> >>> But on my box the problem is that the script bld_awk_pkginfo >>> aborts with a usage message: >>> >>> ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ >>> 11.1 >>> usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> >>> [-v<version>] >>> >>> >>> I think this a gmake vs Sun make problem, you probably have to make sure >>> /usr/bin is in the $PATH before /usr/gnu/bin. >>> >> Indeed this was the issue now package building is fine, let me revert >> the libvirt to see if this is also a PATH problem. > No libvirt still needs the mentioned patchAre you sync''d up to the latest 3.4 bits? : asus-a8n[1]; cd libvirt.hg : asus-a8n[1]; hg qpop -a : asus-a8n[1]; hg log src/node_device.c | head changeset: 2541:4f27afbdbf31 user: berrange date: Wed Jun 03 11:24:21 2009 +0000 summary: Fix HAL driver restart thread safety MRJ
Am 24.06.2009 17:47, schrieb Mark Johnson:> > > Florian Manschwetus wrote: >> Am 24.06.2009 16:56, schrieb Florian Manschwetus: >>> Am 24.06.2009 16:30, schrieb Juergen Keil: >>>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>>>> But the package build step fails... >>>>>> >>>>>> Florian >>>>> ==> log/packages.err<=>>>>> make[2]: *** No rule to make target >>>>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>>>> needed >>>>> by `i.manifest''. Stop. >>>>> make[1]: *** [SUNWxvmr] Error 2 >>>>> make: *** [pkgdefs] Error 2 >>>> >>>> package build fails for me, too, on OpenSolaris 2009.06. >>>> >>>> But on my box the problem is that the script bld_awk_pkginfo >>>> aborts with a usage message: >>>> >>>> ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ >>>> 11.1 >>>> usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> >>>> [-v<version>] >>>> >>>> >>>> I think this a gmake vs Sun make problem, you probably have to make >>>> sure >>>> /usr/bin is in the $PATH before /usr/gnu/bin. >>>> >>> Indeed this was the issue now package building is fine, let me revert >>> the libvirt to see if this is also a PATH problem. >> No libvirt still needs the mentioned patch > > Are you sync''d up to the latest 3.4 bits? > > : asus-a8n[1]; cd libvirt.hg > : asus-a8n[1]; hg qpop -a > : asus-a8n[1]; hg log src/node_device.c | head > changeset: 2541:4f27afbdbf31 > user: berrange > date: Wed Jun 03 11:24:21 2009 +0000 > summary: Fix HAL driver restart thread safety >tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a abort: local changes found, refresh first tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg log src/node_device.c | head changeset: 2541:4f27afbdbf31 user: berrange date: Wed Jun 03 11:24:21 2009 +0000 summary: Fix HAL driver restart thread safety changeset: 2537:14cd0a9a1f8c user: veillard date: Tue Jun 02 15:12:53 2009 +0000 summary: NPIV implementation for node device create and destroy> > > > > MRJ > >
Florian Manschwetus wrote:> Am 24.06.2009 17:47, schrieb Mark Johnson: >> >> >> Florian Manschwetus wrote: >>> Am 24.06.2009 16:56, schrieb Florian Manschwetus: >>>> Am 24.06.2009 16:30, schrieb Juergen Keil: >>>>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>>>> Am 24.06.2009 12:39, schrieb Florian Manschwetus: >>>>>>> Ok, we have found a patch in a newsgroup libvirt builds now. >>>>>>> But the package build step fails... >>>>>>> >>>>>>> Florian >>>>>> ==> log/packages.err<=>>>>>> make[2]: *** No rule to make target >>>>>> `/export/home/tkadmin/xvm-3.4//sunos.hg/src/pkgdefs/common_files/$@'', >>>>>> needed >>>>>> by `i.manifest''. Stop. >>>>>> make[1]: *** [SUNWxvmr] Error 2 >>>>>> make: *** [pkgdefs] Error 2 >>>>> >>>>> package build fails for me, too, on OpenSolaris 2009.06. >>>>> >>>>> But on my box the problem is that the script bld_awk_pkginfo >>>>> aborts with a usage message: >>>>> >>>>> ./bld_awk_pkginfo -m -p "5.11/SunOS Development" -o awk_pkginfo -v \ >>>>> 11.1 >>>>> usage: blk_awk_pkginfo -p<provider> -m<mach> -o<awk_script> >>>>> [-v<version>] >>>>> >>>>> >>>>> I think this a gmake vs Sun make problem, you probably have to make >>>>> sure >>>>> /usr/bin is in the $PATH before /usr/gnu/bin. >>>>> >>>> Indeed this was the issue now package building is fine, let me revert >>>> the libvirt to see if this is also a PATH problem. >>> No libvirt still needs the mentioned patch >> >> Are you sync''d up to the latest 3.4 bits? >> >> : asus-a8n[1]; cd libvirt.hg >> : asus-a8n[1]; hg qpop -a >> : asus-a8n[1]; hg log src/node_device.c | head >> changeset: 2541:4f27afbdbf31 >> user: berrange >> date: Wed Jun 03 11:24:21 2009 +0000 >> summary: Fix HAL driver restart thread safety >> > tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a > abort: local changes found, refresh firstOh, that''s strange... hg status hg qseries -v Thanks, MRJ> tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg log src/node_device.c | head > changeset: 2541:4f27afbdbf31 > user: berrange > date: Wed Jun 03 11:24:21 2009 +0000 > summary: Fix HAL driver restart thread safety > > changeset: 2537:14cd0a9a1f8c > user: veillard > date: Tue Jun 02 15:12:53 2009 +0000 > summary: NPIV implementation for node device create and destroy > >> >> >> >> >> MRJ >> >> > >
Mark Johnson wrote:> > Florian Manschwetus wrote: >> Am 24.06.2009 17:47, schrieb Mark Johnson: >>> Are you sync''d up to the latest 3.4 bits? >>> >>> : asus-a8n[1]; cd libvirt.hg >>> : asus-a8n[1]; hg qpop -a >>> : asus-a8n[1]; hg log src/node_device.c | head >>> changeset: 2541:4f27afbdbf31 >>> user: berrange >>> date: Wed Jun 03 11:24:21 2009 +0000 >>> summary: Fix HAL driver restart thread safety >>> >> tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a >> abort: local changes found, refresh first > > Oh, that''s strange... > > hg status > hg qseries -v >ah, you patched the file... in libvirt.hg, can you hg diff > /tmp/mydiff hg revert --all hg qpop -a hg pull -uv hg qpush -a Thanks, MRJ
2009/6/24 Florian Manschwetus <florianmanschwetus@gmx.de>:> Ok, well so far, next step is the xen-gate/onnv-3.4 > do I need a complete nightly?Yes.> And could I install it in a different BE, so that the current system stays > unchangedSure. Note that once you bfu-upgraded a boot environment to the onnv-3.4 bits, you should not use the opensolaris pkg tools to upgrade / install new package bits into that boot environment.>(some detail on needed steps or a hint to a nice howto would be helpful)?On OpenSolaris, start with these step to prepare the system: http://www.opensolaris.org/os/project/indiana/building_on/ The build procedure for SX:CE can be found here: http://www.opensolaris.org/jive/thread.jspa?messageID=382068#382068
Am 24.06.2009 18:03, schrieb Mark Johnson:> > > Mark Johnson wrote: >> >> Florian Manschwetus wrote: >>> Am 24.06.2009 17:47, schrieb Mark Johnson: >>>> Are you sync''d up to the latest 3.4 bits? >>>> >>>> : asus-a8n[1]; cd libvirt.hg >>>> : asus-a8n[1]; hg qpop -a >>>> : asus-a8n[1]; hg log src/node_device.c | head >>>> changeset: 2541:4f27afbdbf31 >>>> user: berrange >>>> date: Wed Jun 03 11:24:21 2009 +0000 >>>> summary: Fix HAL driver restart thread safety >>>> >>> tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a >>> abort: local changes found, refresh first >> >> Oh, that''s strange... >> >> hg status >> hg qseries -v >> > > ah, you patched the file... > > in libvirt.hg, can you > > hg diff > /tmp/mydiff > hg revert --all > hg qpop -a > hg pull -uv > hg qpush -aDone, error stays... (The guy who found the patch, told me that he has found it on a newsgroup/mailing-list, maybe there is some more info available) Florian> > > Thanks, > > > MRJ > >
Am 24.06.2009 21:25, schrieb Florian Manschwetus:> Am 24.06.2009 18:03, schrieb Mark Johnson: >> >> >> Mark Johnson wrote: >>> >>> Florian Manschwetus wrote: >>>> Am 24.06.2009 17:47, schrieb Mark Johnson: >>>>> Are you sync''d up to the latest 3.4 bits? >>>>> >>>>> : asus-a8n[1]; cd libvirt.hg >>>>> : asus-a8n[1]; hg qpop -a >>>>> : asus-a8n[1]; hg log src/node_device.c | head >>>>> changeset: 2541:4f27afbdbf31 >>>>> user: berrange >>>>> date: Wed Jun 03 11:24:21 2009 +0000 >>>>> summary: Fix HAL driver restart thread safety >>>>> >>>> tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a >>>> abort: local changes found, refresh first >>> >>> Oh, that''s strange... >>> >>> hg status >>> hg qseries -v >>> >> >> ah, you patched the file... >> >> in libvirt.hg, can you >> >> hg diff > /tmp/mydiff >> hg revert --all >> hg qpop -a >> hg pull -uv >> hg qpush -a > > Done, error stays... > > (The guy who found the patch, told me that he has found it on a > newsgroup/mailing-list, maybe there is some more info available)This looks promising and could bring some explanation: http://www.mail-archive.com/libvir-list@redhat.com/msg13970.html Florian> > Florian >> >> >> Thanks, >> >> >> MRJ >> >> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Florian Manschwetus wrote:> Am 24.06.2009 21:25, schrieb Florian Manschwetus: >> Am 24.06.2009 18:03, schrieb Mark Johnson: >>> >>> >>> Mark Johnson wrote: >>>> >>>> Florian Manschwetus wrote: >>>>> Am 24.06.2009 17:47, schrieb Mark Johnson: >>>>>> Are you sync''d up to the latest 3.4 bits? >>>>>> >>>>>> : asus-a8n[1]; cd libvirt.hg >>>>>> : asus-a8n[1]; hg qpop -a >>>>>> : asus-a8n[1]; hg log src/node_device.c | head >>>>>> changeset: 2541:4f27afbdbf31 >>>>>> user: berrange >>>>>> date: Wed Jun 03 11:24:21 2009 +0000 >>>>>> summary: Fix HAL driver restart thread safety >>>>>> >>>>> tkadmin@jupiter:~/xvm-3.4/libvirt.hg$ hg qpop -a >>>>> abort: local changes found, refresh first >>>> >>>> Oh, that''s strange... >>>> >>>> hg status >>>> hg qseries -v >>>> >>> >>> ah, you patched the file... >>> >>> in libvirt.hg, can you >>> >>> hg diff > /tmp/mydiff >>> hg revert --all >>> hg qpop -a >>> hg pull -uv >>> hg qpush -a >> >> Done, error stays... >> >> (The guy who found the patch, told me that he has found it on a >> newsgroup/mailing-list, maybe there is some more info available) > > This looks promising and could bring some explanation: > http://www.mail-archive.com/libvir-list@redhat.com/msg13970.htmlAh, yep.. "If neither hal nor devkit is installed, compiling libvirt yields an undefined symbol error for virNodeDeviceWaitForDevices" Looks like the fix was pushed last week.. I''ll sync up with the latest libvirt bits for you. MRJ> Florian > >> >> Florian >>> >>> >>> Thanks, >>> >>> >>> MRJ >>> >>> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org > >
Am 24.06.2009 18:56, schrieb Juergen Keil:> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >> Ok, well so far, next step is the xen-gate/onnv-3.4 >> do I need a complete nightly? > > Yes. > >> And could I install it in a different BE, so that the current system stays >> unchanged > > Sure. > > Note that once you bfu-upgraded a boot environment to the onnv-3.4 > bits, you should not use the opensolaris pkg tools to upgrade / install > new package bits into that boot environment.What should I use instead? Uhm for bfu there should be an archive but there isn''t? Nightly said it was successful but then there should be an archieve right? Florian> > >> (some detail on needed steps or a hint to a nice howto would be helpful)? > > On OpenSolaris, start with these step to prepare the system: > > http://www.opensolaris.org/os/project/indiana/building_on/ > > > The build procedure for SX:CE can be found here: > > http://www.opensolaris.org/jive/thread.jspa?messageID=382068#382068 >
2009/6/25 Florian Manschwetus <florianmanschwetus@gmx.de>:> Am 24.06.2009 18:56, schrieb Juergen Keil: >> >> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>> >>> Ok, well so far, next step is the xen-gate/onnv-3.4 >>> do I need a complete nightly? >> >> Yes. >> >>> And could I install it in a different BE, so that the current system >>> stays >>> unchanged >> >> Sure. >> >> Note that once you bfu-upgraded a boot environment to the onnv-3.4 >> bits, you should not use the opensolaris pkg tools to upgrade / install >> new package bits into that boot environment. > > What should I use instead?bfu. (e.g. if you have compiled updated nightly archives) pkgadd might be ok, too, iff the installable package does not overlap with bits delivered by onnv. E.g. a pkgadd of a java jdk or acrobat reader should be ok; but installing a package that installs an onnv kernel module, or system header files, or system library files would not be ok.> Uhm for bfu there should be an archive but there isn''t? > Nightly said it was successful but then there should be an archieve right?The bfu archives can be found in archives/i386/nightly-nd (if you compiled release bits) or archives/i386/nightly (debug bits)
Am 25.06.2009 09:18, schrieb Juergen Keil:> 2009/6/25 Florian Manschwetus<florianmanschwetus@gmx.de>: >> Am 24.06.2009 18:56, schrieb Juergen Keil: >>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>> Ok, well so far, next step is the xen-gate/onnv-3.4 >>>> do I need a complete nightly? >>> Yes. >>> >>>> And could I install it in a different BE, so that the current system >>>> stays >>>> unchanged >>> Sure. >>> >>> Note that once you bfu-upgraded a boot environment to the onnv-3.4 >>> bits, you should not use the opensolaris pkg tools to upgrade / install >>> new package bits into that boot environment. >> What should I use instead? > > bfu. (e.g. if you have compiled updated nightly archives) > > pkgadd might be ok, too, iff the installable package > does not overlap with bits delivered by onnv. E.g. a > pkgadd of a java jdk or acrobat reader should be ok; > but installing a package that installs an onnv kernel > module, or system header files, or system library files > would not be ok. > > > >> Uhm for bfu there should be an archive but there isn''t? >> Nightly said it was successful but then there should be an archieve right? > > The bfu archives can be found in archives/i386/nightly-nd (if you > compiled release bits) or archives/i386/nightly (debug bits) >Ok there is no archives folder so again something went wrong. I''ll have a look for some useful hints, uhm also for the nightly I should prefer /usr/bin over /usr/gnu/bin? Florian
2009/6/25 Florian Manschwetus <florianmanschwetus@gmx.de>:> Am 25.06.2009 09:18, schrieb Juergen Keil: >> >> 2009/6/25 Florian Manschwetus<florianmanschwetus@gmx.de>: >>> >>> Am 24.06.2009 18:56, schrieb Juergen Keil: >>>> >>>> 2009/6/24 Florian Manschwetus<florianmanschwetus@gmx.de>: >>>>> >>>>> Ok, well so far, next step is the xen-gate/onnv-3.4 >>>>> do I need a complete nightly? >>>> >>>> Yes. >>>> >>>>> And could I install it in a different BE, so that the current system >>>>> stays >>>>> unchanged >>>> >>>> Sure. >>>> >>>> Note that once you bfu-upgraded a boot environment to the onnv-3.4 >>>> bits, you should not use the opensolaris pkg tools to upgrade / install >>>> new package bits into that boot environment. >>> >>> What should I use instead? >> >> bfu. (e.g. if you have compiled updated nightly archives) >> >> pkgadd might be ok, too, iff the installable package >> does not overlap with bits delivered by onnv. E.g. a >> pkgadd of a java jdk or acrobat reader should be ok; >> but installing a package that installs an onnv kernel >> module, or system header files, or system library files >> would not be ok. >> >> >> >>> Uhm for bfu there should be an archive but there isn''t? >>> Nightly said it was successful but then there should be an archieve >>> right? >> >> The bfu archives can be found in archives/i386/nightly-nd (if you >> compiled release bits) or archives/i386/nightly (debug bits) >> > Ok there is no archives folder so again something went wrong. > I''ll have a look for some useful hints,Build logs can be found in the directory log (during the build) and log/log.YYYY-MM-DD.hh:mm (that is, log + current timestamp at the time the build finished). The mail_msg file contains the short summary that is send via email to the $STAFFER user when the nightly build completed. And the nightly.log file contains the full log of the build commands.> uhm also for the nightly I should > prefer /usr/bin over /usr/gnu/bin?Yes, probably (but I haven''t tested it on opensolaris with /usr/gnu/bin at the front of $PATH, maybe it works?) /usr/bin before /usr/gnu/bin is the default setting of the path on SX:CE. I have /opt/onbld/bin /opt/SUNWspro/bin /usr/bin at the start of $PATH.