Mark, could you also make a short info howto update, a system I build just yesterday, when the patch is inplace. The older Machine I would have to re-bfu due to changed userspace, but the machine installed yesterday should be fixed with rebuilding and reinstalling xvm packages?
Btw, could you sync-up the onnv-3.4 with b124? It is difficult to build b123 with b124, due to missing, with b124 obsolete, headerfiles. Florian Am 07.10.2009 17:46, schrieb Mark Johnson: > > > Florian Manschwetus wrote: >> Today a hvm guest on my xvm-3.4 testserver crashed. >> It is a win2003R2 x64 (no PV-Drivers) running an exchange 2007 >> The domain is viridian enabled. >> >> the corresponding qemu-dm process was around 11G Ram according to top. > > I believe you are running into the bug the following patch fixed... > Ian just pushed a bunch of fixes to qemu-xen-unstable... I pinged him to > see if he plans on pushing them to 3.4 too? If so, I'll sync up and > push.. > > If not, I should be able to get the fixes backported this week. > > > MRJ > > > commit 9c58cf9321f746b223bdd778c49c31ff756b6b1b > Author: Ian Jackson <[email protected]> > Date: Fri Sep 4 16:12:28 2009 +0100 > > fix qemu memory leak in block interface > > the qemu block interface leaks memory every time a read or write > request > is issued, this patch fixes it. > This is also the bug that is causing stubdomains to crash under high > disk IO. > > Signed-off-by: Stefano Stabellini <[email protected]> > > > > >
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ xen-discuss mailing list [email protected]
