Hi everybody,
Allow me to remind you that Xen Test Day is today, so come and join us
on #xentest on freenode!
We will be testing Xen 4.3 RC2 (released yesterday). For more info, see:
- on Xen Test Days:
http://wiki.xen.org/wiki/Xen_Test_Days
- on getting and testing RC2:
http://wiki.xen.org/wiki/Xen_4.3_RC2_test_instructions
- for generic testing information:
http://wiki.xen.org/wiki/Testing_Xen
If you''re using Fedora 18, there is even an RPM available already
(thanks Michael Young for the great work!) here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5407161
See you all on freenode, channel #xentest.
Regards
Lars
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Am Mittwoch 22 Mai 2013, 09:35:59 schrieb Dario Faggioli:> Hi everybody, > > Allow me to remind you that Xen Test Day is today, so come and join us > on #xentest on freenode! > > We will be testing Xen 4.3 RC2 (released yesterday).On opensSuSE-12.3 I have another linking problem: ... AR i386-dm/libqemu.a LINK i386-dm/qemu-dm /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: vl.o: undefined reference to symbol ''timer_settime@@GLIBC_2.3.3'' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: note: ''timer_settime@@GLIBC_2.3.3'' is defined in DSO /lib64/librt.so.1 so try adding it to the linker command line /lib64/librt.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[4]: *** [qemu-dm] Error 1 make[4]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools/qemu-xen-traditional-dir-remote/i386-dm'' make[3]: *** [subdir-i386-dm] Error 2 make[3]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools/qemu-xen-traditional-dir-remote'' make[2]: *** [subdir-install-qemu-xen-traditional-dir] Error 2 make[2]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools'' make[1]: *** [subdirs-install] Error 2 make[1]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools'' make: *** [install-tools] Error 2 And the linker is kindly enough to give the correct hint ;-) After adding "LDFLAGS += -lrt" all went fine. # man timer_settime tells among others: Link with -lrt. Maybe I should mention that openSuSE-12.3 uses libc-2.17 and # ld -v GNU ld (GNU Binutils; openSUSE 12.3) 2.23.1 Thanks. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html
On Wed, 2013-05-22 at 11:17 +0200, Dietmar Hahn wrote:> Am Mittwoch 22 Mai 2013, 09:35:59 schrieb Dario Faggioli: > > Hi everybody, > > > > Allow me to remind you that Xen Test Day is today, so come and join us > > on #xentest on freenode! > > > > We will be testing Xen 4.3 RC2 (released yesterday). > > On opensSuSE-12.3 I have another linking problem: > > ... > AR i386-dm/libqemu.a > LINK i386-dm/qemu-dm > /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: vl.o: undefined reference to symbol ''timer_settime@@GLIBC_2.3.3'' > /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: note: ''timer_settime@@GLIBC_2.3.3'' is defined in DSO /lib64/librt.so.1 so try adding it to the linker command line > /lib64/librt.so.1: could not read symbols: Invalid operation > collect2: error: ld returned 1 exit status > make[4]: *** [qemu-dm] Error 1 > make[4]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools/qemu-xen-traditional-dir-remote/i386-dm'' > make[3]: *** [subdir-i386-dm] Error 2 > make[3]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools/qemu-xen-traditional-dir-remote'' > make[2]: *** [subdir-install-qemu-xen-traditional-dir] Error 2 > make[2]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools'' > make[1]: *** [subdirs-install] Error 2 > make[1]: Leaving directory `/home/hahn/Src/Xen/RC2/xen/tools'' > make: *** [install-tools] Error 2 > > And the linker is kindly enough to give the correct hint ;-) > After adding "LDFLAGS += -lrt" all went fine.I think 70992304dc8c5fc67d876e0f8e3dfaa82be955a1 in the qemu-xen-trad tree should fix this. But it didn''t make it into the 4.3.0-rc2 tag. Ian
> I think 70992304dc8c5fc67d876e0f8e3dfaa82be955a1 in the qemu-xen-trad > tree should fix this. But it didn''t make it into the 4.3.0-rc2 tag.Where can I find this tree? -- Company details: http://ts.fujitsu.com/imprint.html
On Wed, 2013-05-22 at 11:58 +0200, Dietmar Hahn wrote:> > I think 70992304dc8c5fc67d876e0f8e3dfaa82be955a1 in the qemu-xen-trad > > tree should fix this. But it didn''t make it into the 4.3.0-rc2 tag. > > Where can I find this tree?It''s auto cloned into tools/qemu-xen-traditional from http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.git
Am Mittwoch 22 Mai 2013, 11:26:08 schrieb Ian Campbell:> On Wed, 2013-05-22 at 11:58 +0200, Dietmar Hahn wrote: > > > I think 70992304dc8c5fc67d876e0f8e3dfaa82be955a1 in the qemu-xen-trad > > > tree should fix this. But it didn''t make it into the 4.3.0-rc2 tag. > > > > Where can I find this tree? > > It''s auto cloned into tools/qemu-xen-traditional from > http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.gitThanks, now the linking works! Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html
Hi everybody,
Allow me to remind you that the 4th Xen Test Day is happening today, so
come and join us on #xentest on freenode!
We will be testing Xen 4.3 RC4, released yesterday and, probably, *the*
*last* release candidate! For more info, see:
- on Xen Test Days:
http://wiki.xen.org/wiki/Xen_Test_Days
- on getting and testing RC4:
http://wiki.xen.org/wiki/Xen_4.3_RC4_test_instructions
- for generic testing information:
http://wiki.xen.org/wiki/Testing_Xen
See you all on freenode, channel #xentest.
Regards
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Il 12/06/2013 09:01, Dario Faggioli ha scritto:> Hi everybody, > > Allow me to remind you that the 4th Xen Test Day is happening today, so > come and join us on #xentest on freenode! > > We will be testing Xen 4.3 RC4, released yesterday and, probably, *the* > *last* release candidate! For more info, see: > > - on Xen Test Days: > http://wiki.xen.org/wiki/Xen_Test_Days > > - on getting and testing RC4: > http://wiki.xen.org/wiki/Xen_4.3_RC4_test_instructions > > - for generic testing information: > http://wiki.xen.org/wiki/Testing_Xen > > See you all on freenode, channel #xentest. > > Regards > Dario > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develI saw that qemu upstrem tag is not updated (on Config.mk QEMU_UPSTREAM_REVISION ?= qemu-xen-4.3.0-rc1) but on git there are new patches, why? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On mer, 2013-06-12 at 09:44 +0200, Fabio Fantoni wrote:> > > I saw that qemu upstrem tag is not updated (on Config.mk > QEMU_UPSTREAM_REVISION ?= qemu-xen-4.3.0-rc1) but on git there are new > patches, why? >I honestly don''t know, although I remember Ian Jackson and Stefano mentioning it yesterday... Stefano, Ian, any clues? Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Dario Faggioli writes ("Re: [Xen-devel] Xen Test Day is
today!"):> On mer, 2013-06-12 at 09:44 +0200, Fabio Fantoni wrote:
> > I saw that qemu upstrem tag is not updated (on Config.mk
> > QEMU_UPSTREAM_REVISION ?= qemu-xen-4.3.0-rc1) but on git there are new
> > patches, why?
> >
> I honestly don''t know, although I remember Ian Jackson and Stefano
> mentioning it yesterday... Stefano, Ian, any clues?
On IRC yesterday I wrote:
11:57 <Diziet> stefano_s: You have updated the qemu-upstream-unstable
tree but the fixed version in xen.git#staging''s
Config.mk remains at qemu-xen-4.3.0-rc1.
11:58 <Diziet> I''m going to make the RC tarball with what you get
if
you check out xen.git master, not what you get if you
were to fiddle with Config.mk (or pull by hand or
whatever).
I think we should update Config.mk - indeed, we should probably have
done so before. But that''s subject to prompting from Stefano (who
knows when the qemu upstream tree has been updated) at and the moment
confirmation George as release manager.
Ian.
On Wed, 2013-06-12 at 12:34 +0100, Ian Jackson wrote:> Dario Faggioli writes ("Re: [Xen-devel] Xen Test Day is today!"): > > On mer, 2013-06-12 at 09:44 +0200, Fabio Fantoni wrote: > > > I saw that qemu upstrem tag is not updated (on Config.mk > > > QEMU_UPSTREAM_REVISION ?= qemu-xen-4.3.0-rc1) but on git there are new > > > patches, why? > > > > > I honestly don''t know, although I remember Ian Jackson and Stefano > > mentioning it yesterday... Stefano, Ian, any clues? > > On IRC yesterday I wrote: > > 11:57 <Diziet> stefano_s: You have updated the qemu-upstream-unstable > tree but the fixed version in xen.git#staging''s > Config.mk remains at qemu-xen-4.3.0-rc1. > 11:58 <Diziet> I''m going to make the RC tarball with what you get if > you check out xen.git master, not what you get if you > were to fiddle with Config.mk (or pull by hand or > whatever). > > I think we should update Config.mk - indeed, we should probably have > done so before. But that''s subject to prompting from Stefano (who > knows when the qemu upstream tree has been updated) at and the moment > confirmation George as release manager.Presumably we are going to put real commit numbers here instead of tag names, otherwise we need to have a test pass in the midst of the release process to propagate the change of tag name. We can still tag the qemu repo post-hoc as we do for xen.git. Ian.
Ian Campbell writes ("Re: [Xen-devel] qemu upstream version in Xen 4.3.0
RC4"):> Presumably we are going to put real commit numbers here instead of tag
> names, otherwise we need to have a test pass in the midst of the release
> process to propagate the change of tag name. We can still tag the qemu
> repo post-hoc as we do for xen.git.
For the RCs I''ve not being doing anything to Config.mk.
For the release we have other practical options. We can leave in the
commit number. We could decree in advance what versions of qemu are
going to be in 4.3.0 release and tag them well in advance. We could
force push a change to Config.mk (which would be possible because
presumably no other changes are going to be made right before a
release so at that time staging and master will be identical).
Ian.