Re: [Libvirt-announce] [libvirt] Release candidate 2 of 1.0.3 is available
by Daniel Veillard
On Wed, Feb 27, 2013 at 03:26:24PM +0100, Michal Privoznik wrote:
> On 27.02.2013 12:20, Daniel Veillard wrote:
> > I have just tagged git and pushed the tarball. The rpms for F17
> > are at the usual place too:
> > ftp://libvirt.org/libvirt/
> >
> > I gave a try to the set of rpms and this seems to work fine for
> > relatively simple tests.
> > Please give it more testing and let's keep change to git to
> > bug fixes to minimize risks for 1.0.3.
> > If everything goes well I will push 1.0.3 on Friday,
> >
> > thanks !
> >
> > Daniel
> >
>
> Maybe we want to postpone the release a bit; I was trying to find out how drop of qemu driver lock speeds up parallel startup of multiple domains, however - it is not working.
>
> I've created small test program - test4.c and run it against current HEAD. It takes arguments - domain names - which it spawns a separate thread per each domain and repeatedly starts and destroys domains. See code for more.
>
> Then, I've created 20 copies of diskless domain (attached as well): test1..test20 and run my test4 program over them:
>
> ./test4 $(for ((i=1; i<21; i++)); do echo -n "test$i "; done)
>
> I had to tweak max_client_requests=20 to really run those 20 requests in parallel.
>
> However, what I am getting instead of nice measuring of speedup is:
>
> [9722] Starting test1 (round 20) ...[9725] Starting test4 (round 20) ...[9724] Starting test3 (round 20) ...[9723] Starting test2 (round 20) ...[9726] Starting test5 (round 20) ...[9727] Starting test6 (round 20) ...[9728] Starting test7 (round 20) ...[9729] Starting test8 (round 20) ...[9730] Starting test9 (round 20) ...[9731] Starting test10 (round 20) ...[9732] Starting test11 (round 20) ...[9733] Starting test12 (round 20) ...[9734] Starting test13 (round 20) ...[9735] Starting test14 (round 20) ...[9736] Starting test15 (round 20) ...[9737] Starting test16 (round 20) ...[9738] Starting test17 (round 20) ...[9741] Starting test20 (round 20) ...[9739] Starting test18 (round 20) ...[9740] Starting test19 (round 20) ...libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test12libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test14libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test7libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test1libvir: QEMU Driver error : Requested operation is not valid: domain is not running
> Unable to destroy domain test12[9733] Destroying test12 ...[9728] Destroying test7 ...[9735] Destroying test14 ...[9733] Starting test12 (round 19) ...libvir: QEMU Driver error : Requested operation is not valid: domain is not running
> Unable to destroy domain test7[9728] Starting test7 (round 19) ...libvir: QEMU Driver error : Requested operation is not valid: domain is not running
> Unable to destroy domain test14[9735] Starting test14 (round 19) ...libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test18libvir: QEMU Driver error : Requested operation is not valid: domain is not running
> Unable to destroy domain test1[9722] Destroying test1 ...[9722] Starting test1 (round 19) ...libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test8libvir: error : An error occurred, but the cause is unknown
> Unable to start domain test15[9725] Done
>
>
> etc.
>
> Unfortunately, I caught this after freeze.
No problem, freeze is there to find bugs, you found a serious bug,
let's fix it before the release.
[...]
> //sleep(20);
> sleep(1);
does sleep(20); there avoid the problem ? There is a failure in guest
start but we don't get a proper description
There is no urging deadline, except well for the pending patches
waiting for the end of the freeze, if we can fix this by Monday, then
that would be IMHO just fine. If on Monday we still don't have a
solution let's discuss the status of the analysis,
okay ?
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
11 years, 2 months
[Libvirt-announce] Entering freeze for libvirt-1.0.3
by Daniel Veillard
I have just tagged git and pushed the tarball. The rpms for F17
are following too at the usual place:
ftp://libvirt.org/libvirt/
I gave a try to the set of rpms and this seems to work fine for
relatively simple tests, but of course more testing and checking on
other architectures is needed !
If everything goes fine, I will make an rc2 in a couple of days
and then we can decide if a final release on Friday is fine or if
we need to postpone to next week,
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
11 years, 2 months
Re: [Libvirt-announce] [libvirt] Entering freeze for libvirt-1.0.3
by Daniel Veillard
On Tue, Feb 26, 2013 at 01:03:17PM +0800, Li Zhang wrote:
> On 2013年02月26日 12:51, Daniel Veillard wrote:
> >On Tue, Feb 26, 2013 at 11:10:35AM +0800, Li Zhang wrote:
> >>On 2013年02月25日 19:52, Daniel Veillard wrote:
> >>> I have just tagged git and pushed the tarball. The rpms for F17
> >>>are following too at the usual place:
> >>> ftp://libvirt.org/libvirt/
> >>>
> >>> I gave a try to the set of rpms and this seems to work fine for
> >>>relatively simple tests, but of course more testing and checking on
> >>>other architectures is needed !
> >>> If everything goes fine, I will make an rc2 in a couple of days
> >>>and then we can decide if a final release on Friday is fine or if
> >>>we need to postpone to next week,
> >>There are too few changes in this release for pp64.
> > By "too few" do you mean that we are missing anything important ?
> I have sent out 2 patches which are not accepted for this release.
>
> One patch is to fix one bug for ppc64 which is:
> [PATCHv2 1/1] Optimize machine option to set more options with it.
> Without this patch, USB controllers doesn't work well with VGA
> enabled for ppc64.
> And testing with VDSM, it will always report errors when using VGA.
Hum, i just read your patch but i don't have enough knowledge of
qemu parameters to know if there is large side effect to your patch.
Also you remove code which is about core and replace it with something
completely different.
As is and with the amount of details you provided I can't make any
jugement of how bad or good those changes are. One thing is sure,
bug fixes can go in, they are fine during freeze !
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
11 years, 2 months
Re: [Libvirt-announce] [libvirt] Entering freeze for libvirt-1.0.3
by Daniel Veillard
On Tue, Feb 26, 2013 at 11:10:35AM +0800, Li Zhang wrote:
> On 2013年02月25日 19:52, Daniel Veillard wrote:
> > I have just tagged git and pushed the tarball. The rpms for F17
> >are following too at the usual place:
> > ftp://libvirt.org/libvirt/
> >
> > I gave a try to the set of rpms and this seems to work fine for
> >relatively simple tests, but of course more testing and checking on
> >other architectures is needed !
> > If everything goes fine, I will make an rc2 in a couple of days
> >and then we can decide if a final release on Friday is fine or if
> >we need to postpone to next week,
>
> There are too few changes in this release for pp64.
By "too few" do you mean that we are missing anything important ?
> Testing it by building source for ppc64, it works well.
Cool, thanks for testing :-)
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
11 years, 2 months
