From: Fabio Fantoni <fantonifabio@tiscali.it>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: GPLPV questions
Date: Wed, 27 Feb 2013 12:15:21 +0100 [thread overview]
Message-ID: <512DEAC9.2040002@tiscali.it> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35671CE8@BITCOM1.int.sbss.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 2027 bytes --]
Il 13/02/2013 23:26, James Harper ha scritto:
>> 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's possible I missed a commit but I can't see any missing files.
>
> Can you post the output of makedist?
>
> But yes the latest commits involve a pretty major change and I haven't tested save/restore yet so that is probably more broken than before.
>
>> 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.
Are there news about this problem? This is the last critical problem
remained with upstream qemu on my tests and only present with windows domU.
I saw another related post days ago with probably same problem you can't
reproduce.
http://lists.xen.org/archives/html/xen-users/2013-02/msg00278.html
Do you need more details about my dom0 and domU xl cfg?
>>
>> 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.
> I noticed that recently. I can't think how it could be a GPLPV bug though.
>
>
> James
>
>
> -----
> Nessun virus nel messaggio.
> Controllato da AVG - www.avg.com
> Versione: 2013.0.2899 / Database dei virus: 2639/6101 - Data di rilascio: 13/02/2013
>
>
>
[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-02-27 11:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 14:19 GPLPV questions Fabio Fantoni
2013-02-13 20:32 ` Konrad Rzeszutek Wilk
2013-02-13 22:26 ` James Harper
2013-02-14 11:13 ` Fabio Fantoni
2013-02-14 11:16 ` James Harper
2013-02-14 11:31 ` Fabio Fantoni
2013-02-20 10:57 ` Fabio Fantoni
2013-02-20 11:03 ` James Harper
2013-02-20 11:23 ` Fabio Fantoni
2013-02-20 12:04 ` James Harper
2013-02-20 13:14 ` Fabio Fantoni
2013-02-27 11:15 ` Fabio Fantoni [this message]
2013-03-15 14:34 ` Stefan.Hausotte
2013-03-16 0:44 ` James Harper
2013-12-27 13:52 ` Fabio Fantoni
2013-12-27 22:52 ` James Harper
2013-12-28 8:33 ` Fabio Fantoni
2013-12-28 9:49 ` James Harper
2013-12-28 11:56 ` Andrew Cooper
2014-01-03 18:16 ` Pasi Kärkkäinen
2013-02-13 22:53 ` James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=512DEAC9.2040002@tiscali.it \
--to=fantonifabio@tiscali.it \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.