Folks, New releases in the 3.3 and 3.4 stable branches are now tagged and released. You can pick up the source repositories here: http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) Or you can pick up tarballs from the following webpages: 3.3.2: http://www.xen.org/download/index_3.3.2.html 3.4.1: http://www.xen.org/download/ -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Aug 7, 2009 at 7:35 AM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:> Folks, > > New releases in the 3.3 and 3.4 stable branches are now tagged and released. > > You can pick up the source repositories here: > http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) > http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) > > Or you can pick up tarballs from the following webpages: > 3.3.2: http://www.xen.org/download/index_3.3.2.html > 3.4.1: http://www.xen.org/download/Should we have a high-level ChangeLog every time we release a new version? I am sure even some core developers are not aware of all the significant changes, let alone normal users. Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thiago Camargo Martins Cordeiro
2009-Aug-07 02:28 UTC
Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
Mmm... upgrades!!Thanks a LOT for this two great releases!!!! [?] - Thiago 2009/8/6 Jun Koi <junkoi2004@gmail.com>> On Fri, Aug 7, 2009 at 7:35 AM, Keir Fraser<keir.fraser@eu.citrix.com> > wrote: > > Folks, > > > > New releases in the 3.3 and 3.4 stable branches are now tagged and > released. > > > > You can pick up the source repositories here: > > http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) > > http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) > > > > Or you can pick up tarballs from the following webpages: > > 3.3.2: http://www.xen.org/download/index_3.3.2.html > > 3.4.1: http://www.xen.org/download/ > > > Should we have a high-level ChangeLog every time we release a new version? > > I am sure even some core developers are not aware of all the > significant changes, let alone normal users. > > Thanks, > J > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 07/08/2009 02:49, "Jun Koi" <junkoi2004@gmail.com> wrote:>> Or you can pick up tarballs from the following webpages: >> 3.3.2: http://www.xen.org/download/index_3.3.2.html >> 3.4.1: http://www.xen.org/download/ > > > Should we have a high-level ChangeLog every time we release a new version? > > I am sure even some core developers are not aware of all the > significant changes, let alone normal users.There are many ''low-grade'' bug fixes. I suppose calling out a few big ones might be good. But someone would have to remember to do that as we go, or trawl the changeset log before release. These releases are considerably bigger than the average Linux stable 2.6.x.y sub-point release for example, so a similar summary would be much larger. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2009-Aug-09 14:54 UTC
Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
On Thu, Aug 06, 2009 at 11:35:08PM +0100, Keir Fraser wrote:> Folks, > > New releases in the 3.3 and 3.4 stable branches are now tagged and released. > > You can pick up the source repositories here: > http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) > http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) > > Or you can pick up tarballs from the following webpages: > 3.3.2: http://www.xen.org/download/index_3.3.2.html > 3.4.1: http://www.xen.org/download/ >>From that url:Linux 2.6.18 with Xen 3.4.x support source tarball: http://bits.xensource.com/oss-xen/release/3.4.0/linux-2.6.18-xen-3.4.0.tar.gz Any plans to update that kernel tarball to contain the fixes from linux-2.6.18-xen.hg that were made after Xen 3.4.0 release? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 09/08/2009 15:54, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:> From that url: > > Linux 2.6.18 with Xen 3.4.x support source tarball: > http://bits.xensource.com/oss-xen/release/3.4.0/linux-2.6.18-xen-3.4.0.tar.gz > > Any plans to update that kernel tarball to contain the fixes from > linux-2.6.18-xen.hg that were made after Xen 3.4.0 release?I can''t say as we were planning that. I suppose we could stick in a 3.4.1 tag and re-roll the tarball. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser writes ("Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1
released"):> On 09/08/2009 15:54, "Pasi Kärkkäinen" <pasik@iki.fi>
wrote:
> > Any plans to update that kernel tarball to contain the fixes from
> > linux-2.6.18-xen.hg that were made after Xen 3.4.0 release?
>
> I can''t say as we were planning that. I suppose we could stick in
a 3.4.1
> tag and re-roll the tarball.
That sounds like a reasonable plan to me.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Andrew Lyon
2009-Aug-10 10:11 UTC
[Xen-users] Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
On Thu, Aug 6, 2009 at 11:35 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:> Folks, > > New releases in the 3.3 and 3.4 stable branches are now tagged and released. > > You can pick up the source repositories here: > http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) > http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) > > Or you can pick up tarballs from the following webpages: > 3.3.2: http://www.xen.org/download/index_3.3.2.html > 3.4.1: http://www.xen.org/download/ > > -- Keir > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >Sorry to report this on the final 3.4.1 but I never had time to test any of the rc''s, it appears that the fix for using videoram config setting was not applied to 3.4.1, when I try to start a domain with stdvga=1 and videoram=16 it fails: [2009-08-10 11:01:06 9632] WARNING (image:493) domain windows7: device model failure: pid 15316: exited with nonzero status 255; see /var/log cat /xen/qemu-dm-windows7.log domid: 9 qemu: the number of cpus is 8 config qemu network with xen bridge for tap9.0 xenbr0 Machine `xenfv'' requires 17104896 bytes of memory The attached patch fixes this problem but apparently it caused problems on ia64 and another change was suggested, please see original thread http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00890.html, I guess this really needs to be tested on both ia32 and ia64 Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/08/2009 11:11, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:> Sorry to report this on the final 3.4.1 but I never had time to test > any of the rc''s, it appears that the fix for using videoram config > setting was not applied to 3.4.1, when I try to start a domain with > stdvga=1 and videoram=16 it fails:Cc''ing Ian Jackson. He looks after the qemu tree. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 10/08/2009 11:11, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:> Sorry to report this on the final 3.4.1 but I never had time to test > any of the rc''s, it appears that the fix for using videoram config > setting was not applied to 3.4.1, when I try to start a domain with > stdvga=1 and videoram=16 it fails:Do you mean this: commit e0bb6b8df60863bca0163a1688baf4854e931e55 Author: Ian Jackson <ian.jackson@eu.citrix.com> Date: Mon Jun 8 17:45:42 2009 +0100 stdvga + videoram config option Without this patch, guests cannot be created on ia64 because of qemu-dm''s error. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> That appears to remove this assignment ram_size = vga_ram_size; from an ia64-specific fragment in vl.c which doesn''t appear in the 3.4 branch. If that''s not what you meant, what did you mean ? :-) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Aug 10, 2009 at 12:26 PM, Ian Jackson<Ian.Jackson@eu.citrix.com> wrote:> On 10/08/2009 11:11, "Andrew Lyon" <andrew.lyon@gmail.com> wrote: >> Sorry to report this on the final 3.4.1 but I never had time to test >> any of the rc''s, it appears that the fix for using videoram config >> setting was not applied to 3.4.1, when I try to start a domain with >> stdvga=1 and videoram=16 it fails: > > Do you mean this: > > commit e0bb6b8df60863bca0163a1688baf4854e931e55 > Author: Ian Jackson <ian.jackson@eu.citrix.com> > Date: Mon Jun 8 17:45:42 2009 +0100 > > stdvga + videoram config option > > Without this patch, guests cannot be created on ia64 because of > qemu-dm''s error. > > Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> > > That appears to remove this assignment > ram_size = vga_ram_size; > from an ia64-specific fragment in vl.c which doesn''t appear in the 3.4 > branch. > > If that''s not what you meant, what did you mean ? :-) > > Ian. >Yes that is the correct pair of patches, I have tested on x86_64 and I am able to create hvm with increased video ram, I do not see much value in applying a patch which does not work and then fixing it if both are not currently in 3.4 so here is a single patch instead, perhaps KUWAMURA Shin''ya can add a signed-off-by to this too. Signed-off-by: Andrew Lyon <andrew.lyon@gmail.com> --- diff --git tools/ioemu-qemu-xen/vl.c tools/ioemu-qemu-xen/vl.c index b5bb5cb..3506977 100644 --- tools/ioemu-qemu-xen/vl.c +++ tools/ioemu-qemu-xen/vl.c @@ -4801,7 +4801,6 @@ int main(int argc, char **argv, char **envp) machine = first_machine; cpu_model = NULL; initrd_filename = NULL; - ram_size = VGA_RAM_SIZE; #ifdef CONFIG_GDBSTUB use_gdbstub = 0; gdbstub_port = DEFAULT_GDBSTUB_PORT; @@ -5654,13 +5653,6 @@ int main(int argc, char **argv, char **envp) } #endif -#if defined (__ia64__) - if (ram_size > VGA_IO_START) - ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ - if (ram_size > MMIO_START) - ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ -#endif - /* init the bluetooth world */ for (i = 0; i < nb_bt_opts; i++) if (bt_parse(bt_opts[i])) @@ -5677,6 +5669,13 @@ int main(int argc, char **argv, char **envp) phys_ram_size = (machine->ram_require + vga_ram_size) & ~RAMSIZE_FIXED; +#if defined (__ia64__) + if (ram_size > VGA_IO_START) + ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ + if (ram_size > MMIO_START) + ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ +#endif + if (machine->ram_require & RAMSIZE_FIXED) { if (ram_size > 0) { if (ram_size < phys_ram_size) { Andy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2009-Aug-11 08:29 UTC
Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
On Mon, Aug 10, 2009 at 01:46:30PM +0100, Andrew Lyon wrote:> On Mon, Aug 10, 2009 at 12:26 PM, Ian Jackson<Ian.Jackson@eu.citrix.com> wrote: > > On 10/08/2009 11:11, "Andrew Lyon" <andrew.lyon@gmail.com> wrote: > >> Sorry to report this on the final 3.4.1 but I never had time to test > >> any of the rc''s, it appears that the fix for using videoram config > >> setting was not applied to 3.4.1, when I try to start a domain with > >> stdvga=1 and videoram=16 it fails: > > > > Do you mean this: > > > > commit e0bb6b8df60863bca0163a1688baf4854e931e55 > > Author: Ian Jackson <ian.jackson@eu.citrix.com> > > Date: Mon Jun 8 17:45:42 2009 +0100 > > > > stdvga + videoram config option > > > > Without this patch, guests cannot be created on ia64 because of > > qemu-dm''s error. > > > > Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> > > > > That appears to remove this assignment > > ram_size = vga_ram_size; > > from an ia64-specific fragment in vl.c which doesn''t appear in the 3.4 > > branch. > > > > If that''s not what you meant, what did you mean ? :-) > > > > Ian. > > > > Yes that is the correct pair of patches, I have tested on x86_64 and I > am able to create hvm with increased video ram, I do not see much > value in applying a patch which does not work and then fixing it if > both are not currently in 3.4 so here is a single patch instead, > perhaps KUWAMURA Shin''ya can add a signed-off-by to this too. > > Signed-off-by: Andrew Lyon <andrew.lyon@gmail.com> >Btw is there some web based method of seeing shortlogs/logs of xen qemu git repositories? http://xenbits.xensource.com/git-http/qemu-xen-3.4-testing.git/ I didn''t figure out the way to see the logs from the web interface.. was just wondering if this fix was already merged into qemu-xen-3.4-testing. -- Pasi> > --- > > diff --git tools/ioemu-qemu-xen/vl.c tools/ioemu-qemu-xen/vl.c > index b5bb5cb..3506977 100644 > --- tools/ioemu-qemu-xen/vl.c > +++ tools/ioemu-qemu-xen/vl.c > @@ -4801,7 +4801,6 @@ int main(int argc, char **argv, char **envp) > machine = first_machine; > cpu_model = NULL; > initrd_filename = NULL; > - ram_size = VGA_RAM_SIZE; > #ifdef CONFIG_GDBSTUB > use_gdbstub = 0; > gdbstub_port = DEFAULT_GDBSTUB_PORT; > @@ -5654,13 +5653,6 @@ int main(int argc, char **argv, char **envp) > } > #endif > > -#if defined (__ia64__) > - if (ram_size > VGA_IO_START) > - ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ > - if (ram_size > MMIO_START) > - ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ > -#endif > - > /* init the bluetooth world */ > for (i = 0; i < nb_bt_opts; i++) > if (bt_parse(bt_opts[i])) > @@ -5677,6 +5669,13 @@ int main(int argc, char **argv, char **envp) > > phys_ram_size = (machine->ram_require + vga_ram_size) & ~RAMSIZE_FIXED; > > +#if defined (__ia64__) > + if (ram_size > VGA_IO_START) > + ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ > + if (ram_size > MMIO_START) > + ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ > +#endif > + > if (machine->ram_require & RAMSIZE_FIXED) { > if (ram_size > 0) { > if (ram_size < phys_ram_size) { > > > Andy > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2009-Aug-14 14:35 UTC
Re: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
On Tue, Aug 11, 2009 at 11:29:21AM +0300, Pasi Kärkkäinen wrote:> On Mon, Aug 10, 2009 at 01:46:30PM +0100, Andrew Lyon wrote: > > On Mon, Aug 10, 2009 at 12:26 PM, Ian Jackson<Ian.Jackson@eu.citrix.com> wrote: > > > On 10/08/2009 11:11, "Andrew Lyon" <andrew.lyon@gmail.com> wrote: > > >> Sorry to report this on the final 3.4.1 but I never had time to test > > >> any of the rc''s, it appears that the fix for using videoram config > > >> setting was not applied to 3.4.1, when I try to start a domain with > > >> stdvga=1 and videoram=16 it fails: > > > > > > Do you mean this: > > > > > > commit e0bb6b8df60863bca0163a1688baf4854e931e55 > > > Author: Ian Jackson <ian.jackson@eu.citrix.com> > > > Date: Mon Jun 8 17:45:42 2009 +0100 > > > > > > stdvga + videoram config option > > > > > > Without this patch, guests cannot be created on ia64 because of > > > qemu-dm''s error. > > > > > > Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> > > > > > > That appears to remove this assignment > > > ram_size = vga_ram_size; > > > from an ia64-specific fragment in vl.c which doesn''t appear in the 3.4 > > > branch. > > > > > > If that''s not what you meant, what did you mean ? :-) > > > > > > Ian. > > > > > > > Yes that is the correct pair of patches, I have tested on x86_64 and I > > am able to create hvm with increased video ram, I do not see much > > value in applying a patch which does not work and then fixing it if > > both are not currently in 3.4 so here is a single patch instead, > > perhaps KUWAMURA Shin''ya can add a signed-off-by to this too. > > > > Signed-off-by: Andrew Lyon <andrew.lyon@gmail.com> > > > > Btw is there some web based method of seeing shortlogs/logs of xen qemu git > repositories? > > http://xenbits.xensource.com/git-http/qemu-xen-3.4-testing.git/ > > I didn''t figure out the way to see the logs from the web interface.. > was just wondering if this fix was already merged into qemu-xen-3.4-testing. >Was this patch merged? -- Pasi> > > > > --- > > > > diff --git tools/ioemu-qemu-xen/vl.c tools/ioemu-qemu-xen/vl.c > > index b5bb5cb..3506977 100644 > > --- tools/ioemu-qemu-xen/vl.c > > +++ tools/ioemu-qemu-xen/vl.c > > @@ -4801,7 +4801,6 @@ int main(int argc, char **argv, char **envp) > > machine = first_machine; > > cpu_model = NULL; > > initrd_filename = NULL; > > - ram_size = VGA_RAM_SIZE; > > #ifdef CONFIG_GDBSTUB > > use_gdbstub = 0; > > gdbstub_port = DEFAULT_GDBSTUB_PORT; > > @@ -5654,13 +5653,6 @@ int main(int argc, char **argv, char **envp) > > } > > #endif > > > > -#if defined (__ia64__) > > - if (ram_size > VGA_IO_START) > > - ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ > > - if (ram_size > MMIO_START) > > - ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ > > -#endif > > - > > /* init the bluetooth world */ > > for (i = 0; i < nb_bt_opts; i++) > > if (bt_parse(bt_opts[i])) > > @@ -5677,6 +5669,13 @@ int main(int argc, char **argv, char **envp) > > > > phys_ram_size = (machine->ram_require + vga_ram_size) & ~RAMSIZE_FIXED; > > > > +#if defined (__ia64__) > > + if (ram_size > VGA_IO_START) > > + ram_size += VGA_IO_SIZE; /* skip VGA I/O hole */ > > + if (ram_size > MMIO_START) > > + ram_size += 1 * MEM_G; /* skip 3G-4G MMIO, LEGACY_IO_SPACE etc. */ > > +#endif > > + > > if (machine->ram_require & RAMSIZE_FIXED) { > > if (ram_size > 0) { > > if (ram_size < phys_ram_size) { > > > > > > Andy > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel