From: Fabio Fantoni <fabio.fantoni@heliman.it>
To: George Dunlap <dunlapg@umich.edu>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Qemu upstream bugs with xen
Date: Wed, 30 Jan 2013 12:28:47 +0100 [thread overview]
Message-ID: <510903EF.5020004@heliman.it> (raw)
In-Reply-To: <CAFLBxZaV9VbVvMUwp_QWEfvJUA78qtbceKiD-ayES78j5tmivA@mail.gmail.com>
I done other test with qemu upstream, on restore of Windows 7 pro 64 bit
domU with latest gplpv give these lines on logs:
xen_ram_alloc: do not alloc 7f800000 bytes of ram at 0 when runstate is
INMIGRATE
xen_ram_alloc: do not alloc 800000 bytes of ram at 7f800000 when
runstate is INMIGRATE
xen_ram_alloc: do not alloc 10000 bytes of ram at 80000000 when runstate
is INMIGRATE
xen_ram_alloc: do not alloc 10000 bytes of ram at 80010000 when runstate
is INMIGRATE
All seem working except network (seem more gplpv problem already
reported on other post), about this ram logs (first is very strange).
Is it normal or maybe some bugs around?
Dom0 is Wheezy updated with xen-unstable from source (changeset:
26396:b6195e277da5) and qemu 1.3.0 from experimental debian git, rebuilt
for wheezy.
If you need more tests and details tell me and I'll post them.
next prev parent reply other threads:[~2013-01-30 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 9:47 Qemu upstream bugs with xen Fabio Fantoni
2013-01-18 13:00 ` Stefano Stabellini
2013-01-18 14:44 ` Fabio Fantoni
2013-01-18 15:51 ` Stefano Stabellini
2013-02-04 13:14 ` Fabio Fantoni
2013-02-04 13:20 ` Ian Campbell
2013-02-04 13:48 ` Fabio Fantoni
2013-02-04 13:56 ` Ian Campbell
2013-01-21 12:16 ` George Dunlap
2013-01-30 11:28 ` Fabio Fantoni [this message]
2013-02-08 16:21 ` Stefano Stabellini
2013-03-11 11:55 ` Frediano Ziglio
2013-03-11 13:32 ` Fabio Fantoni
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=510903EF.5020004@heliman.it \
--to=fabio.fantoni@heliman.it \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dunlapg@umich.edu \
--cc=stefano.stabellini@eu.citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).