From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: GPLPV questions Date: Wed, 13 Feb 2013 15:32:39 -0500 Message-ID: <20130213203239.GC24566@phenom.dumpdata.com> References: <511BA0D7.8070809@tiscali.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <511BA0D7.8070809@tiscali.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Fabio Fantoni Cc: xen-devel , James Harper List-Id: xen-devel@lists.xenproject.org On Wed, Feb 13, 2013 at 03:19:03PM +0100, Fabio Fantoni wrote: > I have tried to build gplpv from source with makedist.bat but it > gave me some errors about files not found. > I saw that latest commits were big. Is there something incomplete > and must I wait other commits before build it? It would probably help if you pasted what those errors were. > > I would like to see if new build fix network not working after > restore on windows domUs using upstream qemu. > Dom0 is wheezy with xen-unstable from source. > Tested with Windows 7 pro 64 bit with gplpv 0.11.0.357, I not found > error on xen for now, probably is problem of gplpv with qemu > upstream. > Linux hvm domUs seem not have that problem, tested with quantal > (ubuntu 12.10) and network works also after restore. > If you need more details and tests tell me and I'll post it. > > Another problem present on both traditional/upstream qemu with > older/new xen and older/new gplpv is domU's time not correctly > updated after restore (it remains the time at the save operation), > this is a big problem with windows domUs (DC and client) in a > windows domain where the time source is DC by default. > > Thanks for any reply. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel