[PATCH V3 0/5] Reintroduce OVMF support

[PATCH V3 0/5] Reintroduce OVMF support

[Wei Liu]

OVMF (open virtual machine firmware) is used to provide UEFI support for
virtual machines. It was first introduced about a year ago but was disabled due
to compilation problem. Now that the compilation problem is resolved we can
reintorduce it.

OVMF tree can be pulled from
  git://xenbits.xen.org/people/liuw/ovmf.git for-xenbits

Wei.

Change from V2:
* update Config.mk before enabling OVMF build

Ian Campbell (3):
  tools: clone ovmf to ovmf-dir directory
  tools: support system supplied ovmf binary
  tools: Enable OVMF build by default

Wei Liu (2):
  libxl: bump LIBXL_MAXMEM_CONSTANT to 2048
  Config.mk: update OVMF changeset

 Config.mk                         |    2 +-
 Makefile                          |    4 ++++
 config/Tools.mk.in                |    1 +
 tools/configure                   |   20 +++++++++++++++-----
 tools/configure.ac                |   13 ++++++++++++-
 tools/firmware/Makefile           |   31 ++++++++++++-------------------
 tools/firmware/hvmloader/Makefile |    8 ++++++--
 tools/libxl/libxl_internal.h      |    2 +-
 8 files changed, 52 insertions(+), 29 deletions(-)

-- 
1.7.10.4

[PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Wei Liu]

When using OVMF we need to have 1MiB of memory in place for firmware.
Without this change we have:

(XEN) HVM128: Loading OVMF ...
(XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
(XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)

This is not a fatal error as hvmloader will instead use low memory to
load OVMF, but it's better to eliminate such error.

Changing this constant doesn't necessary increase the total amount of
memory a guest uses because it's just a limit.

Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
---
 tools/libxl/libxl_internal.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
index 165dc00..908af20 100644
--- a/tools/libxl/libxl_internal.h
+++ b/tools/libxl/libxl_internal.h
@@ -87,7 +87,7 @@
 #define LIBXL_QEMU_BODGE_TIMEOUT 2
 #define LIBXL_XENCONSOLE_LIMIT 1048576
 #define LIBXL_XENCONSOLE_PROTOCOL "vt100"
-#define LIBXL_MAXMEM_CONSTANT 1024
+#define LIBXL_MAXMEM_CONSTANT 2048
 #define LIBXL_PV_EXTRA_MEMORY 1024
 #define LIBXL_HVM_EXTRA_MEMORY 2048
 #define LIBXL_MIN_DOM0_MEM (128*1024)
-- 
1.7.10.4

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[George Dunlap]

On Tue, Oct 29, 2013 at 11:39 AM, Wei Liu <wei.liu2@citrix.com> wrote:
> When using OVMF we need to have 1MiB of memory in place for firmware.
> Without this change we have:
>
> (XEN) HVM128: Loading OVMF ...
> (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
>
> This is not a fatal error as hvmloader will instead use low memory to
> load OVMF, but it's better to eliminate such error.
>
> Changing this constant doesn't necessary increase the total amount of
> memory a guest uses because it's just a limit.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>

Acked-by: George Dunlap <george.dunlap@eu.citrix.com>

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Ian Campbell]

On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> When using OVMF we need to have 1MiB of memory in place for firmware.
> Without this change we have:
> 
> (XEN) HVM128: Loading OVMF ...
> (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> 
> This is not a fatal error as hvmloader will instead use low memory to
> load OVMF, but it's better to eliminate such error.
> 
> Changing this constant doesn't necessary increase the total amount of
> memory a guest uses because it's just a limit.

It will allow a guest to try and use up to 1MB more though, and it
allows this for PV guests as well as HVM guests not using OVMF.

There's only a small number of place which use this constant, can we
refactor them into a helper function, which can then be expanded to
include a per-BIOS overhead in addition to this one? The BIOS selection
is stored in xenstore, so that work even for calls which don't have the
domain configuration to hand.

(does anyone remember what the existing 1MB is actually for?)

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Wei Liu]

On Fri, Nov 01, 2013 at 04:02:17PM +0000, Ian Campbell wrote:
> On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> > When using OVMF we need to have 1MiB of memory in place for firmware.
> > Without this change we have:
> > 
> > (XEN) HVM128: Loading OVMF ...
> > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> > 
> > This is not a fatal error as hvmloader will instead use low memory to
> > load OVMF, but it's better to eliminate such error.
> > 
> > Changing this constant doesn't necessary increase the total amount of
> > memory a guest uses because it's just a limit.
> 
> It will allow a guest to try and use up to 1MB more though, and it
> allows this for PV guests as well as HVM guests not using OVMF.
> 
> There's only a small number of place which use this constant, can we
> refactor them into a helper function, which can then be expanded to
> include a per-BIOS overhead in addition to this one? The BIOS selection
> is stored in xenstore, so that work even for calls which don't have the
> domain configuration to hand.
> 
> (does anyone remember what the existing 1MB is actually for?)
> 

Happened to come across this when I was looking at other problem.

http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html

It looks like that constant was never intended to use in the way it is
now. Hah.

Wei.

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Ian Campbell]

On Fri, 2013-11-01 at 16:10 +0000, Wei Liu wrote:
> On Fri, Nov 01, 2013 at 04:02:17PM +0000, Ian Campbell wrote:
> > On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> > > When using OVMF we need to have 1MiB of memory in place for firmware.
> > > Without this change we have:
> > > 
> > > (XEN) HVM128: Loading OVMF ...
> > > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> > > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> > > 
> > > This is not a fatal error as hvmloader will instead use low memory to
> > > load OVMF, but it's better to eliminate such error.
> > > 
> > > Changing this constant doesn't necessary increase the total amount of
> > > memory a guest uses because it's just a limit.
> > 
> > It will allow a guest to try and use up to 1MB more though, and it
> > allows this for PV guests as well as HVM guests not using OVMF.
> > 
> > There's only a small number of place which use this constant, can we
> > refactor them into a helper function, which can then be expanded to
> > include a per-BIOS overhead in addition to this one? The BIOS selection
> > is stored in xenstore, so that work even for calls which don't have the
> > domain configuration to hand.
> > 
> > (does anyone remember what the existing 1MB is actually for?)
> > 
> 
> Happened to come across this when I was looking at other problem.
> 
> http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html
> 
> It looks like that constant was never intended to use in the way it is
> now. Hah.

Indeed not.

I vaguely recall that the xapi folks add a bit of slack to the domain
size while they are doing the calculation to see if it fit will on the
host, but not actually when they build the domain. (note that this
therefore only matters for the domain being built, and not cumulatively
for all domains, which makes a difference to the overall overheads on
the system). We could try switching to a model like that and see what
breaks I guess?

I've CC'd a couple of xapi folks so they can correct my no doubt faulty
memory ;-)
Ian.

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Wei Liu]

On Fri, Nov 01, 2013 at 04:23:04PM +0000, Ian Campbell wrote:
> On Fri, 2013-11-01 at 16:10 +0000, Wei Liu wrote:
> > On Fri, Nov 01, 2013 at 04:02:17PM +0000, Ian Campbell wrote:
> > > On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> > > > When using OVMF we need to have 1MiB of memory in place for firmware.
> > > > Without this change we have:
> > > > 
> > > > (XEN) HVM128: Loading OVMF ...
> > > > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> > > > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> > > > 
> > > > This is not a fatal error as hvmloader will instead use low memory to
> > > > load OVMF, but it's better to eliminate such error.
> > > > 
> > > > Changing this constant doesn't necessary increase the total amount of
> > > > memory a guest uses because it's just a limit.
> > > 
> > > It will allow a guest to try and use up to 1MB more though, and it
> > > allows this for PV guests as well as HVM guests not using OVMF.
> > > 
> > > There's only a small number of place which use this constant, can we
> > > refactor them into a helper function, which can then be expanded to
> > > include a per-BIOS overhead in addition to this one? The BIOS selection
> > > is stored in xenstore, so that work even for calls which don't have the
> > > domain configuration to hand.
> > > 
> > > (does anyone remember what the existing 1MB is actually for?)
> > > 
> > 
> > Happened to come across this when I was looking at other problem.
> > 
> > http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html
> > 
> > It looks like that constant was never intended to use in the way it is
> > now. Hah.
> 
> Indeed not.
> 
> I vaguely recall that the xapi folks add a bit of slack to the domain
> size while they are doing the calculation to see if it fit will on the
> host, but not actually when they build the domain. (note that this
> therefore only matters for the domain being built, and not cumulatively
> for all domains, which makes a difference to the overall overheads on
> the system). We could try switching to a model like that and see what
> breaks I guess?
> 
> I've CC'd a couple of xapi folks so they can correct my no doubt faulty
> memory ;-)
> Ian.

Xapi experts, any thought?

Wei.

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Ian Campbell]

On Wed, 2013-11-06 at 10:32 +0000, Wei Liu wrote:
> On Fri, Nov 01, 2013 at 04:23:04PM +0000, Ian Campbell wrote:
> > On Fri, 2013-11-01 at 16:10 +0000, Wei Liu wrote:
> > > On Fri, Nov 01, 2013 at 04:02:17PM +0000, Ian Campbell wrote:
> > > > On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> > > > > When using OVMF we need to have 1MiB of memory in place for firmware.
> > > > > Without this change we have:
> > > > > 
> > > > > (XEN) HVM128: Loading OVMF ...
> > > > > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> > > > > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> > > > > 
> > > > > This is not a fatal error as hvmloader will instead use low memory to
> > > > > load OVMF, but it's better to eliminate such error.
> > > > > 
> > > > > Changing this constant doesn't necessary increase the total amount of
> > > > > memory a guest uses because it's just a limit.
> > > > 
> > > > It will allow a guest to try and use up to 1MB more though, and it
> > > > allows this for PV guests as well as HVM guests not using OVMF.
> > > > 
> > > > There's only a small number of place which use this constant, can we
> > > > refactor them into a helper function, which can then be expanded to
> > > > include a per-BIOS overhead in addition to this one? The BIOS selection
> > > > is stored in xenstore, so that work even for calls which don't have the
> > > > domain configuration to hand.
> > > > 
> > > > (does anyone remember what the existing 1MB is actually for?)
> > > > 
> > > 
> > > Happened to come across this when I was looking at other problem.
> > > 
> > > http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html
> > > 
> > > It looks like that constant was never intended to use in the way it is
> > > now. Hah.
> > 
> > Indeed not.
> > 
> > I vaguely recall that the xapi folks add a bit of slack to the domain
> > size while they are doing the calculation to see if it fit will on the
> > host, but not actually when they build the domain. (note that this
> > therefore only matters for the domain being built, and not cumulatively
> > for all domains, which makes a difference to the overall overheads on
> > the system). We could try switching to a model like that and see what
> > breaks I guess?
> > 
> > I've CC'd a couple of xapi folks so they can correct my no doubt faulty
> > memory ;-)
> > Ian.
> 
> Xapi experts, any thought?

Andy Cooper told me on IRC
        Xapi adds the slack when building the domain.

Apparently not doing so cause unspecified fallout. Which isn't to say
that's xapi specific and xl would be fine.

Ian.

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Stefano Stabellini]

On Wed, 6 Nov 2013, Ian Campbell wrote:
> On Wed, 2013-11-06 at 10:32 +0000, Wei Liu wrote:
> > On Fri, Nov 01, 2013 at 04:23:04PM +0000, Ian Campbell wrote:
> > > On Fri, 2013-11-01 at 16:10 +0000, Wei Liu wrote:
> > > > On Fri, Nov 01, 2013 at 04:02:17PM +0000, Ian Campbell wrote:
> > > > > On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> > > > > > When using OVMF we need to have 1MiB of memory in place for firmware.
> > > > > > Without this change we have:
> > > > > > 
> > > > > > (XEN) HVM128: Loading OVMF ...
> > > > > > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> > > > > > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> > > > > > 
> > > > > > This is not a fatal error as hvmloader will instead use low memory to
> > > > > > load OVMF, but it's better to eliminate such error.
> > > > > > 
> > > > > > Changing this constant doesn't necessary increase the total amount of
> > > > > > memory a guest uses because it's just a limit.
> > > > > 
> > > > > It will allow a guest to try and use up to 1MB more though, and it
> > > > > allows this for PV guests as well as HVM guests not using OVMF.
> > > > > 
> > > > > There's only a small number of place which use this constant, can we
> > > > > refactor them into a helper function, which can then be expanded to
> > > > > include a per-BIOS overhead in addition to this one? The BIOS selection
> > > > > is stored in xenstore, so that work even for calls which don't have the
> > > > > domain configuration to hand.
> > > > > 
> > > > > (does anyone remember what the existing 1MB is actually for?)
> > > > > 
> > > > 
> > > > Happened to come across this when I was looking at other problem.
> > > > 
> > > > http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html
> > > > 
> > > > It looks like that constant was never intended to use in the way it is
> > > > now. Hah.
> > > 
> > > Indeed not.
> > > 
> > > I vaguely recall that the xapi folks add a bit of slack to the domain
> > > size while they are doing the calculation to see if it fit will on the
> > > host, but not actually when they build the domain. (note that this
> > > therefore only matters for the domain being built, and not cumulatively
> > > for all domains, which makes a difference to the overall overheads on
> > > the system). We could try switching to a model like that and see what
> > > breaks I guess?
> > > 
> > > I've CC'd a couple of xapi folks so they can correct my no doubt faulty
> > > memory ;-)
> > > Ian.
> > 
> > Xapi experts, any thought?
> 
> Andy Cooper told me on IRC
>         Xapi adds the slack when building the domain.
> 
> Apparently not doing so cause unspecified fallout. Which isn't to say
> that's xapi specific and xl would be fine.

Yeah.. theoretically I think that we shouldn't have that constat at all.
In practice it could cause stability issues, maybe difficult to narrow
down. Maybe we should remember to remove it at the beginning of the next
development cycle and see what breaks? Keeping in mind that OSSTests is
really unlikely to find any of these issues, we should probably try to
get the community more involved with the testing.

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Ian Campbell]

create !
title it Remove arbitrary LIBXL_MAXMEM_CONSTANT from libxl, see what breaks
thanks

On Wed, 2013-11-06 at 18:04 +0000, Stefano Stabellini wrote:
> > > > > Happened to come across this when I was looking at other problem.
> > > > > 
> > > > > http://lists.xen.org/archives/html/xen-devel/2009-12/msg00401.html
> > > > > 
> > > > > It looks like that constant was never intended to use in the way it is
> > > > > now. Hah.
> > > > 
> > > > Indeed not.
> > > > 
> > > > I vaguely recall that the xapi folks add a bit of slack to the domain
> > > > size while they are doing the calculation to see if it fit will on the
> > > > host, but not actually when they build the domain. (note that this
> > > > therefore only matters for the domain being built, and not cumulatively
> > > > for all domains, which makes a difference to the overall overheads on
> > > > the system). We could try switching to a model like that and see what
> > > > breaks I guess?
> > > > 
> > > > I've CC'd a couple of xapi folks so they can correct my no doubt faulty
> > > > memory ;-)
> > > > Ian.
> > > 
> > > Xapi experts, any thought?
> > 
> > Andy Cooper told me on IRC
> >         Xapi adds the slack when building the domain.
> > 
> > Apparently not doing so cause unspecified fallout. Which isn't to say
> > that's xapi specific and xl would be fine.
> 
> Yeah.. theoretically I think that we shouldn't have that constat at all.
> In practice it could cause stability issues, maybe difficult to narrow
> down. Maybe we should remember to remove it at the beginning of the next
> development cycle and see what breaks? Keeping in mind that OSSTests is
> really unlikely to find any of these issues, we should probably try to
> get the community more involved with the testing.

The reasons for keeping it are based mostly on folklore rather than an
actual understanding of the issues, which may not even be real, and it's
wasting (cumulatively) a fair bit of RAM.

But waiting until early in the 4.5 cycle is probably a good idea.

I've created a bug (with this mail) to remind us to do this.

Ian.

Processed: Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[xen]

Processing commands for xen@bugs.xenproject.org:

> create !
Created new bug #23 rooted at `<1383822208.26213.173.camel@kazak.uk.xensource.com>'
Title: `Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048'
> title it Remove arbitrary LIBXL_MAXMEM_CONSTANT from libxl, see what breaks
Set title for #23 to `Remove arbitrary LIBXL_MAXMEM_CONSTANT from libxl, see what breaks'
> thanks
Finished processing.

Modified/created Bugs:
 - 23: http://bugs.xenproject.org/xen/bug/23 (new)

---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues

Re: [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Wei Liu]

On Tue, Oct 29, 2013 at 11:39:47AM +0000, Wei Liu wrote:
> When using OVMF we need to have 1MiB of memory in place for firmware.
> Without this change we have:
> 
> (XEN) HVM128: Loading OVMF ...
> (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024
> (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1)
> 
> This is not a fatal error as hvmloader will instead use low memory to
> load OVMF, but it's better to eliminate such error.
> 
> Changing this constant doesn't necessary increase the total amount of
> memory a guest uses because it's just a limit.
> 
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> ---
>  tools/libxl/libxl_internal.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
> index 165dc00..908af20 100644
> --- a/tools/libxl/libxl_internal.h
> +++ b/tools/libxl/libxl_internal.h
> @@ -87,7 +87,7 @@
>  #define LIBXL_QEMU_BODGE_TIMEOUT 2
>  #define LIBXL_XENCONSOLE_LIMIT 1048576
>  #define LIBXL_XENCONSOLE_PROTOCOL "vt100"
> -#define LIBXL_MAXMEM_CONSTANT 1024
> +#define LIBXL_MAXMEM_CONSTANT 2048
>  #define LIBXL_PV_EXTRA_MEMORY 1024
>  #define LIBXL_HVM_EXTRA_MEMORY 2048
>  #define LIBXL_MIN_DOM0_MEM (128*1024)
> -- 

Actually those messages are debug only, so this patch is not necessary.

Please drop this one.


Wei.

> 1.7.10.4

[PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
 Config.mk |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Config.mk b/Config.mk
index 1879454..dad2dc4 100644
--- a/Config.mk
+++ b/Config.mk
@@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
 QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
 SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
 endif
-OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
+OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
 QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
 SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
 # Fri Aug 2 14:12:09 2013 -0400
-- 
1.7.10.4

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 29/10/2013 12:39, Wei Liu ha scritto:
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> ---
>   Config.mk |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Config.mk b/Config.mk
> index 1879454..dad2dc4 100644
> --- a/Config.mk
> +++ b/Config.mk
> @@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
>   QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
>   SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
>   endif
> -OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> +OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
>   QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
>   SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
>   # Fri Aug 2 14:12:09 2013 -0400

This patch update only the ovmf changeset but not the repository, now 
git://xenbits.xen.org/ovmf.git is not updated, so you have to update it 
or change also repository to git://xenbits.xen.org/people/liuw/ovmf.git.
All other things look good to me, now I test this series of patches.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Tue, Oct 29, 2013 at 03:16:17PM +0100, Fabio Fantoni wrote:
> Il 29/10/2013 12:39, Wei Liu ha scritto:
> >Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> >---
> >  Config.mk |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/Config.mk b/Config.mk
> >index 1879454..dad2dc4 100644
> >--- a/Config.mk
> >+++ b/Config.mk
> >@@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
> >  QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
> >  SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> >  endif
> >-OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> >+OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
> >  QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
> >  SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
> >  # Fri Aug 2 14:12:09 2013 -0400
> 
> This patch update only the ovmf changeset but not the repository,
> now git://xenbits.xen.org/ovmf.git is not updated, so you have to
> update it or change also repository to
> git://xenbits.xen.org/people/liuw/ovmf.git.
> All other things look good to me, now I test this series of patches.

I don't have the permission to push to that repository so I need to
defer this to maintainers.

Again, you can probably wait until this series go through push gate
before conducting any test.

Wei.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 29/10/2013 15:21, Wei Liu ha scritto:
> On Tue, Oct 29, 2013 at 03:16:17PM +0100, Fabio Fantoni wrote:
>> Il 29/10/2013 12:39, Wei Liu ha scritto:
>>> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
>>> ---
>>>   Config.mk |    2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/Config.mk b/Config.mk
>>> index 1879454..dad2dc4 100644
>>> --- a/Config.mk
>>> +++ b/Config.mk
>>> @@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
>>>   QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
>>>   SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
>>>   endif
>>> -OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
>>> +OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
>>>   QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
>>>   SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
>>>   # Fri Aug 2 14:12:09 2013 -0400
>> This patch update only the ovmf changeset but not the repository,
>> now git://xenbits.xen.org/ovmf.git is not updated, so you have to
>> update it or change also repository to
>> git://xenbits.xen.org/people/liuw/ovmf.git.
>> All other things look good to me, now I test this series of patches.
> I don't have the permission to push to that repository so I need to
> defer this to maintainers.
>
> Again, you can probably wait until this series go through push gate
> before conducting any test.
>
> Wei.


For this patches serie:
Tested-by: Fabio Fantoni <fabio.fantoni@m2r.biz>

About ovmf:
I don't have uefi domUs ready, so I did a fast test with windows 7 pro 
64 bit dvd and starts, spice it works.
The problem found for now is very bad general performance and at the end 
of windows installer loading the domU reboots.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Tue, Oct 29, 2013 at 05:15:49PM +0100, Fabio Fantoni wrote:
> Il 29/10/2013 15:21, Wei Liu ha scritto:
> >On Tue, Oct 29, 2013 at 03:16:17PM +0100, Fabio Fantoni wrote:
> >>Il 29/10/2013 12:39, Wei Liu ha scritto:
> >>>Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> >>>---
> >>>  Config.mk |    2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>>diff --git a/Config.mk b/Config.mk
> >>>index 1879454..dad2dc4 100644
> >>>--- a/Config.mk
> >>>+++ b/Config.mk
> >>>@@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
> >>>  QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
> >>>  SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> >>>  endif
> >>>-OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> >>>+OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
> >>>  QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
> >>>  SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
> >>>  # Fri Aug 2 14:12:09 2013 -0400
> >>This patch update only the ovmf changeset but not the repository,
> >>now git://xenbits.xen.org/ovmf.git is not updated, so you have to
> >>update it or change also repository to
> >>git://xenbits.xen.org/people/liuw/ovmf.git.
> >>All other things look good to me, now I test this series of patches.
> >I don't have the permission to push to that repository so I need to
> >defer this to maintainers.
> >
> >Again, you can probably wait until this series go through push gate
> >before conducting any test.
> >
> >Wei.
> 
> 
> For this patches serie:
> Tested-by: Fabio Fantoni <fabio.fantoni@m2r.biz>
> 
> About ovmf:
> I don't have uefi domUs ready, so I did a fast test with windows 7
> pro 64 bit dvd and starts, spice it works.
> The problem found for now is very bad general performance and at the
> end of windows installer loading the domU reboots.

Oh Windows... :-P

It would be useful to have at least some hypervisor / QEMU logs.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

[-- Attachment #1: Type: text/plain, Size: 3889 bytes --]

Il 29/10/2013 17:34, Wei Liu ha scritto:
> On Tue, Oct 29, 2013 at 05:15:49PM +0100, Fabio Fantoni wrote:
>> Il 29/10/2013 15:21, Wei Liu ha scritto:
>>> On Tue, Oct 29, 2013 at 03:16:17PM +0100, Fabio Fantoni wrote:
>>>> Il 29/10/2013 12:39, Wei Liu ha scritto:
>>>>> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
>>>>> ---
>>>>>   Config.mk |    2 +-
>>>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/Config.mk b/Config.mk
>>>>> index 1879454..dad2dc4 100644
>>>>> --- a/Config.mk
>>>>> +++ b/Config.mk
>>>>> @@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
>>>>>   QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
>>>>>   SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
>>>>>   endif
>>>>> -OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
>>>>> +OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
>>>>>   QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
>>>>>   SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
>>>>>   # Fri Aug 2 14:12:09 2013 -0400
>>>> This patch update only the ovmf changeset but not the repository,
>>>> now git://xenbits.xen.org/ovmf.git is not updated, so you have to
>>>> update it or change also repository to
>>>> git://xenbits.xen.org/people/liuw/ovmf.git.
>>>> All other things look good to me, now I test this series of patches.
>>> I don't have the permission to push to that repository so I need to
>>> defer this to maintainers.
>>>
>>> Again, you can probably wait until this series go through push gate
>>> before conducting any test.
>>>
>>> Wei.
>>
>> For this patches serie:
>> Tested-by: Fabio Fantoni <fabio.fantoni@m2r.biz>
>>
>> About ovmf:
>> I don't have uefi domUs ready, so I did a fast test with windows 7
>> pro 64 bit dvd and starts, spice it works.
>> The problem found for now is very bad general performance and at the
>> end of windows installer loading the domU reboots.
> Oh Windows... :-P

I know that quality, efficiency, stability and security do not exist in 
the Microsoft vocabulary...
Unfortunately almost all users for desktop/workstation use windows (for 
now) and even at the time I still use it for work due to some programs 
that only run on windows (and often are made very badly) :(

>
> It would be useful to have at least some hypervisor / QEMU logs.

I found this error on xl dmesg:
> (XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
I see a recently posted patch about pfn:
http://lists.xen.org/archives/html/xen-devel/2013-10/msg02028.html
Can this serie solve the problem and I have to try it or has nothing to 
do with this?

And this is the error that cause reboot of domU:
> (XEN) hvm.c:1274:d4 Triple fault on VCPU0 - invoking HVM shutdown 
> action 1.

I not found any other error or relevant information on logs but I attach 
them if you want see.

I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same 
performance problem (some minutes only for arrive to grub-efi of dvd) 
and after other 10-15 minutes without complete the boot I did a destroy.
Also for that logs on attachments.

Despite windows is bad, it seems that problems persist even in the test 
linux except the shutdown with vcpu issue.

The dom0 used have the installation of this:
http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
Except the git branch used (here the hvm-improve.t6) and the qemu:
QEMU_UPSTREAM_URL ?= 
git://xenbits.xen.org/staging/qemu-upstream-unstable.git
QEMU_UPSTREAM_REVISION ?= master

If you need more informations and/or tests tell me and I'll do/post them.

About legacy bios support that I mentioned days ago I found this 
document about:
http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
Seem that need ovmf change (and probably also on hvmloader) that are not 
able to do.

Thank for any reply and sorry for my bad english.

[-- Attachment #2: W7logs.7z --]
[-- Type: application/octet-stream, Size: 4280 bytes --]

[-- Attachment #3: PRECISElogs.7z --]
[-- Type: application/octet-stream, Size: 2303 bytes --]

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Wed, Oct 30, 2013 at 12:33:50PM +0100, Fabio Fantoni wrote:
[...]
> >>For this patches serie:
> >>Tested-by: Fabio Fantoni <fabio.fantoni@m2r.biz>
> >>
> >>About ovmf:
> >>I don't have uefi domUs ready, so I did a fast test with windows 7
> >>pro 64 bit dvd and starts, spice it works.
> >>The problem found for now is very bad general performance and at the
> >>end of windows installer loading the domU reboots.
> >Oh Windows... :-P
> 
> I know that quality, efficiency, stability and security do not exist
> in the Microsoft vocabulary...
> Unfortunately almost all users for desktop/workstation use windows
> (for now) and even at the time I still use it for work due to some
> programs that only run on windows (and often are made very badly) :(
> 

Don't get me wrong. I'm just saying debugging Windows with no source
code available is beyond my ability. :-)

> >
> >It would be useful to have at least some hypervisor / QEMU logs.
> 
> I found this error on xl dmesg:
> >(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
> I see a recently posted patch about pfn:
> http://lists.xen.org/archives/html/xen-devel/2013-10/msg02028.html
> Can this serie solve the problem and I have to try it or has nothing
> to do with this?

I don't think that patch is useful to fix this at first glance.

AFAICT this is a limitation of Xen's physmap implementation.  I'm still
investigating a proper fix for this -- unfortunately that might
involving modifying Xen's most complicated part so don't hold your
breath.

> 
> And this is the error that cause reboot of domU:
> >(XEN) hvm.c:1274:d4 Triple fault on VCPU0 - invoking HVM shutdown
> >action 1.
> 

Windows, right? Could you try Linux?

> I not found any other error or relevant information on logs but I
> attach them if you want see.
> 
> I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same
> performance problem (some minutes only for arrive to grub-efi of
> dvd) and after other 10-15 minutes without complete the boot I did a
> destroy.
> Also for that logs on attachments.
> 

Is QMEU busy-looping?

> Despite windows is bad, it seems that problems persist even in the
> test linux except the shutdown with vcpu issue.
> 
> The dom0 used have the installation of this:
> http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
> Except the git branch used (here the hvm-improve.t6) and the qemu:
> QEMU_UPSTREAM_URL ?=
> git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> QEMU_UPSTREAM_REVISION ?= master
> 

Oh please don't use staging QEMU. That introduces a new variable which
makes it very hard to identify the genuine problem.

Wei.

> If you need more informations and/or tests tell me and I'll do/post them.
> 
> About legacy bios support that I mentioned days ago I found this
> document about:
> http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
> Seem that need ovmf change (and probably also on hvmloader) that are
> not able to do.
> 
> Thank for any reply and sorry for my bad english.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 30/10/2013 12:50, Wei Liu ha scritto:
> On Wed, Oct 30, 2013 at 12:33:50PM +0100, Fabio Fantoni wrote:
> [...]
>>>> For this patches serie:
>>>> Tested-by: Fabio Fantoni <fabio.fantoni@m2r.biz>
>>>>
>>>> About ovmf:
>>>> I don't have uefi domUs ready, so I did a fast test with windows 7
>>>> pro 64 bit dvd and starts, spice it works.
>>>> The problem found for now is very bad general performance and at the
>>>> end of windows installer loading the domU reboots.
>>> Oh Windows... :-P
>> I know that quality, efficiency, stability and security do not exist
>> in the Microsoft vocabulary...
>> Unfortunately almost all users for desktop/workstation use windows
>> (for now) and even at the time I still use it for work due to some
>> programs that only run on windows (and often are made very badly) :(
>>
> Don't get me wrong. I'm just saying debugging Windows with no source
> code available is beyond my ability. :-)
>
>>> It would be useful to have at least some hypervisor / QEMU logs.
>> I found this error on xl dmesg:
>>> (XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
>> I see a recently posted patch about pfn:
>> http://lists.xen.org/archives/html/xen-devel/2013-10/msg02028.html
>> Can this serie solve the problem and I have to try it or has nothing
>> to do with this?
> I don't think that patch is useful to fix this at first glance.
>
> AFAICT this is a limitation of Xen's physmap implementation.  I'm still
> investigating a proper fix for this -- unfortunately that might
> involving modifying Xen's most complicated part so don't hold your
> breath.
>
>> And this is the error that cause reboot of domU:
>>> (XEN) hvm.c:1274:d4 Triple fault on VCPU0 - invoking HVM shutdown
>>> action 1.
> Windows, right? Could you try Linux?
>
>> I not found any other error or relevant information on logs but I
>> attach them if you want see.
>>
>> I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same
>> performance problem (some minutes only for arrive to grub-efi of
>> dvd) and after other 10-15 minutes without complete the boot I did a
>> destroy.
>> Also for that logs on attachments.
>>
> Is QMEU busy-looping?

I probably not understand exactly what you mean, the domU seems continue 
to boot apparently but in very slow motion.
Qemu is always active and with low load (on average 5% cpu).

>
>> Despite windows is bad, it seems that problems persist even in the
>> test linux except the shutdown with vcpu issue.
>>
>> The dom0 used have the installation of this:
>> http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
>> Except the git branch used (here the hvm-improve.t6) and the qemu:
>> QEMU_UPSTREAM_URL ?=
>> git://xenbits.xen.org/staging/qemu-upstream-unstable.git
>> QEMU_UPSTREAM_REVISION ?= master
>>
> Oh please don't use staging QEMU. That introduces a new variable which
> makes it very hard to identify the genuine problem.
>
> Wei.

Is based on latest qemu stable (1.6.1).
I tested 1.6 fora long time without see regression and seems more good 
than 1.3 on something.
Are there specific reasons to use an older version instead?
If there were it would not be a problem for me to recompile/re-test with 
a qemu previous.

>
>> If you need more informations and/or tests tell me and I'll do/post them.
>>
>> About legacy bios support that I mentioned days ago I found this
>> document about:
>> http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
>> Seem that need ovmf change (and probably also on hvmloader) that are
>> not able to do.
>>
>> Thank for any reply and sorry for my bad english.
>
>

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Wed, Oct 30, 2013 at 01:57:40PM +0100, Fabio Fantoni wrote:
[...]
> >>I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same
> >>performance problem (some minutes only for arrive to grub-efi of
> >>dvd) and after other 10-15 minutes without complete the boot I did a
> >>destroy.
> >>Also for that logs on attachments.
> >>
> >Is QMEU busy-looping?
> 
> I probably not understand exactly what you mean, the domU seems
> continue to boot apparently but in very slow motion.
> Qemu is always active and with low load (on average 5% cpu).
> 

OK. I get it. 5% CPU is OK and expected at this stage.

To get an idea what your guest is doing you probably need to setup
serial console.

> >
> >>Despite windows is bad, it seems that problems persist even in the
> >>test linux except the shutdown with vcpu issue.
> >>
> >>The dom0 used have the installation of this:
> >>http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
> >>Except the git branch used (here the hvm-improve.t6) and the qemu:
> >>QEMU_UPSTREAM_URL ?=
> >>git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> >>QEMU_UPSTREAM_REVISION ?= master
> >>
> >Oh please don't use staging QEMU. That introduces a new variable which
> >makes it very hard to identify the genuine problem.
> >
> >Wei.
> 
> Is based on latest qemu stable (1.6.1).
> I tested 1.6 fora long time without see regression and seems more
> good than 1.3 on something.
> Are there specific reasons to use an older version instead?
> If there were it would not be a problem for me to recompile/re-test
> with a qemu previous.
> 

If it is working fine for you then it is OK.

But IMHO it is generally better to wait for specific changeset to go
through push gate before conducting your test because that reduces the
variables which might cause regressions.

Wei.

> >
> >>If you need more informations and/or tests tell me and I'll do/post them.
> >>
> >>About legacy bios support that I mentioned days ago I found this
> >>document about:
> >>http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
> >>Seem that need ovmf change (and probably also on hvmloader) that are
> >>not able to do.
> >>
> >>Thank for any reply and sorry for my bad english.
> >
> >

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 30/10/2013 15:05, Wei Liu ha scritto:
> On Wed, Oct 30, 2013 at 01:57:40PM +0100, Fabio Fantoni wrote:
> [...]
>>>> I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same
>>>> performance problem (some minutes only for arrive to grub-efi of
>>>> dvd) and after other 10-15 minutes without complete the boot I did a
>>>> destroy.
>>>> Also for that logs on attachments.
>>>>
>>> Is QMEU busy-looping?
>> I probably not understand exactly what you mean, the domU seems
>> continue to boot apparently but in very slow motion.
>> Qemu is always active and with low load (on average 5% cpu).
>>
> OK. I get it. 5% CPU is OK and expected at this stage.
>
> To get an idea what your guest is doing you probably need to setup
> serial console.
>
>>>> Despite windows is bad, it seems that problems persist even in the
>>>> test linux except the shutdown with vcpu issue.
>>>>
>>>> The dom0 used have the installation of this:
>>>> http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
>>>> Except the git branch used (here the hvm-improve.t6) and the qemu:
>>>> QEMU_UPSTREAM_URL ?=
>>>> git://xenbits.xen.org/staging/qemu-upstream-unstable.git
>>>> QEMU_UPSTREAM_REVISION ?= master
>>>>
>>> Oh please don't use staging QEMU. That introduces a new variable which
>>> makes it very hard to identify the genuine problem.
>>>
>>> Wei.
>> Is based on latest qemu stable (1.6.1).
>> I tested 1.6 fora long time without see regression and seems more
>> good than 1.3 on something.
>> Are there specific reasons to use an older version instead?
>> If there were it would not be a problem for me to recompile/re-test
>> with a qemu previous.
>>
> If it is working fine for you then it is OK.
>
> But IMHO it is generally better to wait for specific changeset to go
> through push gate before conducting your test because that reduces the
> variables which might cause regressions.
>
> Wei.

I also tried another build without change qemu repo and changet but same 
result.
Do you have domUs working on ovmf? If yes what are differences from my 
test system?

I tried to change also domU parameters:
- removing audio, vdagent and usb redirection it changes nothing.
- switch from stdvga to cirrus vga solves the performance problem, but 
with Precise it shows always a black screen after start of grub-efi 
entry, and black screen also with windows 7 installer.

What domU vga you used on your tests?

I'm trying to setup ovmf serial console, but I have no idea on where to 
start from. Do you have some suggestions?

Thanks for any reply.

>
>>>> If you need more informations and/or tests tell me and I'll do/post them.
>>>>
>>>> About legacy bios support that I mentioned days ago I found this
>>>> document about:
>>>> http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
>>>> Seem that need ovmf change (and probably also on hvmloader) that are
>>>> not able to do.
>>>>
>>>> Thank for any reply and sorry for my bad english.
>>>

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Wed, Oct 30, 2013 at 04:52:52PM +0100, Fabio Fantoni wrote:
[...]
> 
> I also tried another build without change qemu repo and changet but
> same result.
> Do you have domUs working on ovmf? If yes what are differences from
> my test system?
> 
> I tried to change also domU parameters:
> - removing audio, vdagent and usb redirection it changes nothing.
> - switch from stdvga to cirrus vga solves the performance problem,
> but with Precise it shows always a black screen after start of
> grub-efi entry, and black screen also with windows 7 installer.
> 
> What domU vga you used on your tests?
> 

Cirrus, because there's cirrus driver in OVMF. I don't know whether
there is driver for stdvga.

Black screen is expected because there's probably something wrong with
OVMF / Xen. I need to check real hardware behavior to identify the
problem.

> I'm trying to setup ovmf serial console, but I have no idea on where
> to start from. Do you have some suggestions?
> 

Add serial='pty' in you HVM guest config file. I believe you can get a
tutorial on wiki.xen.org

Wei.

> Thanks for any reply.
> 
> >
> >>>>If you need more informations and/or tests tell me and I'll do/post them.
> >>>>
> >>>>About legacy bios support that I mentioned days ago I found this
> >>>>document about:
> >>>>http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
> >>>>Seem that need ovmf change (and probably also on hvmloader) that are
> >>>>not able to do.
> >>>>
> >>>>Thank for any reply and sorry for my bad english.
> >>>

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Il 30/10/2013 16:58, Wei Liu ha scritto:
> On Wed, Oct 30, 2013 at 04:52:52PM +0100, Fabio Fantoni wrote:
> [...]
>> I also tried another build without change qemu repo and changet but
>> same result.
>> Do you have domUs working on ovmf? If yes what are differences from
>> my test system?
>>
>> I tried to change also domU parameters:
>> - removing audio, vdagent and usb redirection it changes nothing.
>> - switch from stdvga to cirrus vga solves the performance problem,
>> but with Precise it shows always a black screen after start of
>> grub-efi entry, and black screen also with windows 7 installer.
>>
>> What domU vga you used on your tests?
>>
> Cirrus, because there's cirrus driver in OVMF. I don't know whether
> there is driver for stdvga.
>
> Black screen is expected because there's probably something wrong with
> OVMF / Xen. I need to check real hardware behavior to identify the
> problem.
>
>> I'm trying to setup ovmf serial console, but I have no idea on where
>> to start from. Do you have some suggestions?
>>
> Add serial='pty' in you HVM guest config file. I believe you can get a
> tutorial on wiki.xen.org
>
> Wei.

Thanks and sorry for the stupid question.
Precise's boot stops with calltrace, log on attachment.
I'll try also with latest ubuntu version (Saucy) with newer kernel 
(3.11) and with latest stable qemu version (1.6.1).

>> Thanks for any reply.
>>
>>>>>> If you need more informations and/or tests tell me and I'll do/post them.
>>>>>>
>>>>>> About legacy bios support that I mentioned days ago I found this
>>>>>> document about:
>>>>>> http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
>>>>>> Seem that need ovmf change (and probably also on hvmloader) that are
>>>>>> not able to do.
>>>>>>
>>>>>> Thank for any reply and sorry for my bad english.

This idea could be enable legacy bios and vgabioses support on ovmf... 
Is that really stupid question to not deserve an aswer?
Thanks for any reply.

[-- Attachment #2: ovmf-precise-serial.log --]
[-- Type: text/plain, Size: 58485 bytes --]

cat /dev/pts/1
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu   
[    0.000000] Linux version 3.8.0-29-generic (buildd@panlong) (gcc version 4.6
.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23
 UTC 2013 (Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5)                       
[    0.000000] Command line: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed
/ubuntu.seed boot=casper console=hvc0 console=ttyS0,38400n8 --                 
[    0.000000] KERNEL supported cpus:                         
[    0.000000]   Intel GenuineIntel  
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003d96ffff] usable
[    0.000000] BIOS-e820: [mem 0x000000003d970000-0x000000003d981fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000003d982000-0x000000003d9affff] reserved 
[    0.000000] BIOS-e820: [mem 0x000000003d9b0000-0x000000003f16ffff] usable  
[    0.000000] BIOS-e820: [mem 0x000000003f170000-0x000000003f1c7fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000003f1c8000-0x000000003f1cffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000003f1d0000-0x000000003f1d3fff] ACPI NVS 
[    0.000000] BIOS-e820: [mem 0x000000003f1d4000-0x000000003f7cefff] usable  
[    0.000000] BIOS-e820: [mem 0x000000003f7cf000-0x000000003f7fefff] reserved
[    0.000000] BIOS-e820: [mem 0x000000003f7ff000-0x000000003f7fffff] usable
[    0.000000] NX (Execute Disable) protection: active                         
[    0.000000] efi: EFI v2.31 by EDK II                                        
[    0.000000] efi:  SMBIOS=0x3f1c7000  ACPI=0x3f1cf000  ACPI 2.0=0x3f1cf014   
[    0.000000] efi: mem00: type=7, attr=0xf, range=[0x0000000000000000-0x000000
00000a0000) (0MB)                                                              
[    0.000000] efi: mem01: type=2, attr=0xf, range=[0x0000000000100000-0x000000
000062a000) (5MB)                                                              
[    0.000000] efi: mem02: type=7, attr=0xf, range=[0x000000000062a000-0x000000
0000800000) (1MB)                                                              
[    0.000000] efi: mem03: type=4, attr=0xf, range=[0x0000000000800000-0x000000
0001000000) (8MB)                                                              
[    0.000000] efi: mem04: type=7, attr=0xf, range=[0x0000000001000000-0x000000
002c555000) (693MB)                                                            
[    0.000000] efi: mem05: type=2, attr=0xf, range=[0x000000002c555000-0x000000
003b800000) (242MB)                                                            
[    0.000000] efi: mem06: type=4, attr=0xf, range=[0x000000003b800000-0x000000
003b820000) (0MB)                                                              
[    0.000000] efi: mem07: type=7, attr=0xf, range=[0x000000003b820000-0x000000
003d34f000) (27MB)                                                             
[    0.000000] efi: mem08: type=2, attr=0xf, range=[0x000000003d34f000-0x000000
003d41a000) (0MB)                                                              
[    0.000000] efi: mem09: type=1, attr=0xf, range=[0x000000003d41a000-0x000000
003d54e000) (1MB)                                                              
[    0.000000] efi: mem10: type=7, attr=0xf, range=[0x000000003d54e000-0x000000
003d5cd000) (0MB)                                                              
[    0.000000] efi: mem11: type=2, attr=0xf, range=[0x000000003d5cd000-0x000000
003d69a000) (0MB)                                                              
[    0.000000] efi: mem12: type=4, attr=0xf, range=[0x000000003d69a000-0x000000
003d73f000) (0MB)                                                              
[    0.000000] efi: mem13: type=3, attr=0xf, range=[0x000000003d73f000-0x000000
003d970000) (2MB)                                                              
[    0.000000] efi: mem14: type=9, attr=0xf, range=[0x000000003d970000-0x000000
003d982000) (0MB)                                                              
[    0.000000] efi: mem15: type=6, attr=0x800000000000000f, range=[0x000000003d
982000-0x000000003d984000) (0MB)                                               
[    0.000000] efi: mem16: type=5, attr=0x800000000000000f, range=[0x000000003d
984000-0x000000003d99b000) (0MB)                                               
[    0.000000] efi: mem17: type=6, attr=0x800000000000000f, range=[0x000000003d
99b000-0x000000003d9b0000) (0MB)                                               
[    0.000000] efi: mem18: type=4, attr=0xf, range=[0x000000003d9b0000-0x000000
003eff0000) (22MB)                                                             
[    0.000000] efi: mem19: type=2, attr=0xf, range=[0x000000003eff0000-0x000000
003eff4000) (0MB)                                                              
[    0.000000] efi: mem20: type=3, attr=0xf, range=[0x000000003eff4000-0x000000
003f170000) (1MB)                                                              
[    0.000000] efi: mem21: type=5, attr=0x800000000000000f, range=[0x000000003f
170000-0x000000003f1a0000) (0MB)                                               
[    0.000000] efi: mem22: type=6, attr=0x800000000000000f, range=[0x000000003f
1a0000-0x000000003f1c4000) (0MB)                                               
[    0.000000] efi: mem23: type=0, attr=0xf, range=[0x000000003f1c4000-0x000000
003f1c8000) (0MB)                                                              
[    0.000000] efi: mem24: type=9, attr=0xf, range=[0x000000003f1c8000-0x000000
003f1d0000) (0MB)                                                              
[    0.000000] efi: mem25: type=10, attr=0xf, range=[0x000000003f1d0000-0x00000
0003f1d4000) (0MB)                                                             
[    0.000000] efi: mem26: type=4, attr=0xf, range=[0x000000003f1d4000-0x000000
003f7cf000) (5MB)                                                              
[    0.000000] efi: mem27: type=6, attr=0x800000000000000f, range=[0x000000003f
7cf000-0x000000003f7ff000) (0MB)                                               
[    0.000000] efi: mem28: type=4, attr=0xf, range=[0x000000003f7ff000-0x000000
003f800000) (0MB)                                                              
[    0.000000] SMBIOS 2.7 present.                                             
[    0.000000] Hypervisor detected: Xen HVM                                    
[    0.000000] Xen version 4.4.                                                
[    0.000000] Netfront and the Xen platform PCI driver have been compiled for 
this kernel: unplug emulated NICs.                                             
[    0.000000] Blkfront and the Xen platform PCI driver have been compiled for 
this kernel: unplug emulated disks.                                            
[    0.000000] You might have to change the root device                        
[    0.000000] from /dev/hd[a-d] to /dev/xvd[a-d]                              
[    0.000000] in your root= kernel command line option                        
[    0.000000] No AGP bridge found                                             
[    0.000000] e820: last_pfn = 0x3f800 max_arch_pfn = 0x400000000             
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] init_memory_mapping: [mem 0x00000000-0x3f7fffff]                
[    0.000000] RAMDISK: [mem 0x2f994000-0x309abfff]                            
[    0.000000] ACPI: RSDP 000000003f1cf014 00024 (v02    Xen)                  
[    0.000000] ACPI: XSDT 000000003f1ce0e8 00054 (v01    Xen      HVM 00000000 
     01000013)                                                                 
[    0.000000] ACPI: FACP 000000003f1cd000 000F4 (v04    Xen      HVM 00000000 
HVML 00000000)                                                                 
[    0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tab
les! (20121018/tbfadt-394)                                                     
[    0.000000] ACPI BIOS Bug: Warning: 32/64X FACS address mismatch in FADT - 0
x3F1D3000/0x00000000FC001000, using 32 (20121018/tbfadt-521)                   
[    0.000000] ACPI: DSDT 000000003d970000 1138D (v02    Xen      HVM 00000000 
INTL 20100528)                                                                 
[    0.000000] ACPI: FACS 000000003f1d3000 00040                               
[    0.000000] ACPI: APIC 000000003f1cc000 00460 (v02    Xen      HVM 00000000 
HVML 00000000)                                                                 
[    0.000000] ACPI: HPET 000000003f1cb000 00038 (v01    Xen      HVM 00000000 
HVML 00000000)                                                                 
[    0.000000] ACPI: WAET 000000003f1ca000 00028 (v01    Xen      HVM 00000000 
HVML 00000000)                                                                 
[    0.000000] ACPI: SSDT 000000003f1c9000 00031 (v02    Xen      HVM 00000000 
INTL 20100528)                                                                 
[    0.000000] ACPI: SSDT 000000003f1c8000 00031 (v02    Xen      HVM 00000000 
INTL 20100528)                                                                 
[    0.000000] No NUMA configuration found                                     
[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000003f7fffff]    
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x3f7fffff]                
[    0.000000]   NODE_DATA [mem 0x3d695000-0x3d699fff]                         
[    0.000000] Zone ranges:                                                    
[    0.000000]   DMA      [mem 0x00010000-0x00ffffff]                          
[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]                          
[    0.000000]   Normal   empty                                                
[    0.000000] Movable zone start for each node                                
[    0.000000] Early memory node ranges                                        
[    0.000000]   node   0: [mem 0x00010000-0x0009ffff]                         
[    0.000000]   node   0: [mem 0x00100000-0x3d96ffff]                         
[    0.000000]   node   0: [mem 0x3d9b0000-0x3f16ffff]                         
[    0.000000]   node   0: [mem 0x3f1d4000-0x3f7cefff]                         
[    0.000000]   node   0: [mem 0x3f7ff000-0x3f7fffff]                         
[    0.000000] ACPI: PM-Timer IO Port: 0xb008                                  
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)              
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)              
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x1e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x22] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x24] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x26] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x28] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x2a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x2c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x2e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x32] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x34] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x36] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x38] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x21] lapic_id[0x42] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x22] lapic_id[0x44] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x23] lapic_id[0x46] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x24] lapic_id[0x48] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x25] lapic_id[0x4a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x26] lapic_id[0x4c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x27] lapic_id[0x4e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x28] lapic_id[0x50] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x29] lapic_id[0x52] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2a] lapic_id[0x54] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2b] lapic_id[0x56] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2c] lapic_id[0x58] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2d] lapic_id[0x5a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2e] lapic_id[0x5c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x2f] lapic_id[0x5e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x31] lapic_id[0x62] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x32] lapic_id[0x64] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x33] lapic_id[0x66] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x34] lapic_id[0x68] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x35] lapic_id[0x6a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x36] lapic_id[0x6c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x37] lapic_id[0x6e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x38] lapic_id[0x70] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x39] lapic_id[0x72] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3a] lapic_id[0x74] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3b] lapic_id[0x76] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3c] lapic_id[0x78] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3d] lapic_id[0x7a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3e] lapic_id[0x7c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x3f] lapic_id[0x7e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x40] lapic_id[0x80] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x41] lapic_id[0x82] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x42] lapic_id[0x84] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x43] lapic_id[0x86] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x44] lapic_id[0x88] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x45] lapic_id[0x8a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x46] lapic_id[0x8c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x47] lapic_id[0x8e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x48] lapic_id[0x90] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x49] lapic_id[0x92] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4a] lapic_id[0x94] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4b] lapic_id[0x96] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4c] lapic_id[0x98] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4d] lapic_id[0x9a] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4e] lapic_id[0x9c] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x4f] lapic_id[0x9e] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x50] lapic_id[0xa0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x51] lapic_id[0xa2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x52] lapic_id[0xa4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x53] lapic_id[0xa6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x54] lapic_id[0xa8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x55] lapic_id[0xaa] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x56] lapic_id[0xac] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x57] lapic_id[0xae] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x58] lapic_id[0xb0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x59] lapic_id[0xb2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5a] lapic_id[0xb4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5b] lapic_id[0xb6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5c] lapic_id[0xb8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5d] lapic_id[0xba] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5e] lapic_id[0xbc] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x5f] lapic_id[0xbe] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x60] lapic_id[0xc0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x61] lapic_id[0xc2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x62] lapic_id[0xc4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x63] lapic_id[0xc6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x64] lapic_id[0xc8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x65] lapic_id[0xca] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x66] lapic_id[0xcc] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x67] lapic_id[0xce] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x68] lapic_id[0xd0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x69] lapic_id[0xd2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6a] lapic_id[0xd4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6b] lapic_id[0xd6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6c] lapic_id[0xd8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6d] lapic_id[0xda] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6e] lapic_id[0xdc] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x6f] lapic_id[0xde] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x70] lapic_id[0xe0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x71] lapic_id[0xe2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x72] lapic_id[0xe4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x73] lapic_id[0xe6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x74] lapic_id[0xe8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x75] lapic_id[0xea] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x76] lapic_id[0xec] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x77] lapic_id[0xee] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x78] lapic_id[0xf0] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x79] lapic_id[0xf2] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7a] lapic_id[0xf4] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7b] lapic_id[0xf6] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7c] lapic_id[0xf8] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7d] lapic_id[0xfa] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7e] lapic_id[0xfc] disabled)             
[    0.000000] ACPI: LAPIC (acpi_id[0x7f] lapic_id[0xfe] disabled)             
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])         
[    0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47  
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)        
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)      
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)    
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)    
[    0.000000] Using ACPI (MADT) for SMP configuration information             
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000                      
[    0.000000] smpboot: Allowing 128 CPUs, 126 hotplug CPUs                    
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 000000000010000
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003d970000 - 000000003d98200
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003d982000 - 000000003d9b000
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003f170000 - 000000003f1c800
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003f1c8000 - 000000003f1d000
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003f1d0000 - 000000003f1d400
0                                                                              
[    0.000000] PM: Registered nosave memory: 000000003f7cf000 - 000000003f7ff00
0                                                                              
[    0.000000] e820: [mem 0x3f800000-0xffffffff] available for PCI devices     
[    0.000000] Booting paravirtualized kernel on Xen HVM                       
[    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:128 nr_
node_ids:1                                                                     
[    0.000000] PERCPU: Embedded 28 pages/cpu @ffff88003a800000 s85056 r8192 d21
440 u131072                                                                    
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pa
ges: 255701                                                                    
[    0.000000] Policy zone: DMA32                                              
[    0.000000] Kernel command line: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/
preseed/ubuntu.seed boot=casper console=hvc0 console=ttyS0,38400n8 --          
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)            
[    0.000000] __ex_table already sorted, skipping sort                        
[    0.000000] Checking aperture...                                            
[    0.000000] No AGP bridge found                                             
[    0.000000] Memory: 942584k/1040384k available (7170k kernel code, 1296k abs
ent, 96504k reserved, 6073k data, 1012k init)                                  
[    0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=128
, Nodes=1                                                                      
[    0.000000] Hierarchical RCU implementation.                                
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.         
[    0.000000]  RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=128.       
[    0.000000] NR_IRQS:16640 nr_irqs:2112 16                                   
[    0.000000] Xen HVM callback vector for event delivery is enabled           
[    0.000000] Console: colour dummy device 80x25                              
[    0.000000] console [hvc0] enabled                                          
[    0.000000] console [ttyS0] enabled                                         
[    0.000000] allocated 4194304 bytes of page_cgroup                          
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memo
ry cgroups                                                                     
[    0.000000] tsc: Detected 2661.216 MHz processor                            
[    0.008000] Calibrating delay loop (skipped), value calculated using timer f
requency.. 5322.43 BogoMIPS (lpj=10644864)                                     
[    0.012006] pid_max: default: 131072 minimum: 1024                          
[    0.016767] Security Framework initialized                                  
[    0.020013] AppArmor: AppArmor initialized                                  
[    0.024005] Yama: becoming mindful.                                         
[    0.026940] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes
)                                                                              
[    0.032625] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)  
[    0.036380] Mount-cache hash table entries: 256                             
[    0.044211] Initializing cgroup subsys cpuacct                              
[    0.047735] Initializing cgroup subsys memory                               
[    0.048024] Initializing cgroup subsys devices                              
[    0.052007] Initializing cgroup subsys freezer                              
[    0.056007] Initializing cgroup subsys blkio                                
[    0.060005] Initializing cgroup subsys perf_event                           
[    0.064011] Initializing cgroup subsys hugetlb                              
[    0.068121] CPU: Physical Processor ID: 0                                   
[    0.072005] CPU: Processor Core ID: 0                                       
[    0.074919] mce: CPU supports 2 MCE banks                                   
[    0.076034] Last level iTLB entries: 4KB 512, 2MB 7, 4MB 7                  
[    0.076034] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32                
[    0.076034] tlb_flushall_shift: 6                                           
[    0.088242] Freeing SMP alternatives: 24k freed                             
[    0.100823] ACPI: Core revision 20121018                                    
[    0.112612] ftrace: allocating 29358 entries in 115 pages                   
[    0.170234] Switched APIC routing to physical flat.                         
[    0.178393] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0              
[    0.223485] smpboot: CPU0: Intel(R) Xeon(R) CPU           X3450  @ 2.67GHz (
fam: 06, model: 1e, stepping: 05)                                              
[    0.230661] installing Xen timer for CPU 0                                  
[    0.232268] cpu 0 spinlock event irq 70                                     
[    0.236029] Performance Events: unsupported p6 CPU model 30 no PMU driver, s
oftware events only.                                                           
[    0.248018] NMI watchdog: disabled (cpu0): hardware events not enabled      
[    0.252453] cpu 1 spinlock event irq 71                                     
[    0.256013] installing Xen timer for CPU 1                                  
[    0.260117] smpboot: Booting Node   0, Processors  #1                       
[    0.278231] Brought up 2 CPUs                                               
[    0.280014] smpboot: Total of 2 processors activated (10644.86 BogoMIPS)    
[    0.285008] devtmpfs: initialized                                           
[    0.288938] EVM: security.selinux                                           
[    0.292012] EVM: security.SMACK64                                           
[    0.296011] EVM: security.capability                                        
[    0.299984] PM: Registering ACPI NVS region [mem 0x3f1d0000-0x3f1d3fff] (163
84 bytes)                                                                      
[    0.300976] regulator-dummy: no parameters                                  
[    0.304219] NET: Registered protocol family 16                              
[    0.308291] ACPI: bus type pci registered                                   
[    0.312534] PCI: Using configuration type 1 for base access                 
[    0.316854] bio: create slab <bio-0> at 0                                   
[    0.320145] ACPI: Added _OSI(Module Device)                                 
[    0.323497] ACPI: Added _OSI(Processor Device)                              
[    0.324009] ACPI: Added _OSI(3.0 _SCP Extensions)                           
[    0.327652] ACPI: Added _OSI(Processor Aggregator Device)                   
[    0.338058] ACPI: Interpreter enabled                                       
[    0.340009] ACPI: (supports S0 S3 S4 S5)                                    
[    0.343370] ACPI: Using IOAPIC for interrupt routing                        
[    0.414048] ACPI: No dock devices found.                                    
[    0.416010] PCI: Using host bridge windows from ACPI; if necessary, use "pci
=nocrs" and report a bug                                                       
[    0.420071] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])          
[    0.424388] pci_root PNP0A03:00: fail to add MMCONFIG information, can't acc
ess extended PCI configuration space under this bridge.                        
[    0.428038] PCI host bridge to bus 0000:00                                  
[    0.431055] pci_bus 0000:00: root bus resource [bus 00-ff]                  
[    0.432009] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]          
[    0.436008] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]          
[    0.440008] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]  
[    0.444008] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfbffffff]  
[    0.482629] pci 0000:00:01.3: quirk: [io  0xb000-0xb03f] claimed by PIIX4 AC
PI                                                                             
[    0.484061] pci 0000:00:01.3: quirk: [io  0xb100-0xb10f] claimed by PIIX4 SM
B                                                                              
[    0.573597]  pci0000:00: ACPI _OSC support notification failed, disabling PC
Ie ASPM                                                                        
[    0.576008]  pci0000:00: Unable to request _OSC control (_OSC support mask: 
0x08)                                                                          
[    0.580341] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 10 *11)                 
[    0.585390] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 10 *11)                 
[    0.589595] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 *10 11)                 
[    0.593580] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 *10 11)                 
[    0.597491] xen/balloon: Initialising balloon driver.                       
[    0.600049] xen-balloon: Initialising balloon driver.                       
[    0.604099] vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+me
m,locks=none                                                                   
[    0.608010] vgaarb: loaded                                                  
[    0.610168] vgaarb: bridge control possible 0000:00:03.0                    
[    0.612231] SCSI subsystem initialized                                      
[    0.615102] ACPI: bus type scsi registered                                  
[    0.616066] ACPI: bus type usb registered                                   
[    0.620011] usbcore: registered new interface driver usbfs                  
[    0.624016] usbcore: registered new interface driver hub                    
[    0.628060] usbcore: registered new device driver usb                       
[    0.632081] PCI: Using ACPI for IRQ routing                                 
[    0.635503] pci 0000:00:02.0: no compatible bridge window for [mem 0x8200000
0-0x82ffffff pref]                                                             
[    0.636062] pci 0000:00:03.0: no compatible bridge window for [mem 0x8000000
0-0x81ffffff pref]                                                             
[    0.640011] pci 0000:00:03.0: no compatible bridge window for [mem 0x8300100
0-0x83001fff]                                                                  
[    0.644429] NetLabel: Initializing                                          
[    0.647132] NetLabel:  domain hash size = 128                               
[    0.648007] NetLabel:  protocols = UNLABELED CIPSOv4                        
[    0.651903] NetLabel:  unlabeled traffic allowed by default                 
[    0.652065] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[    0.656025] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0                         
[    0.660824] hpet0: 3 comparators, 64-bit 62.500000 MHz counter              
[    0.666061] Switching to clocksource xen                                    
[    0.677675] AppArmor: AppArmor Filesystem Enabled                           
[    0.681282] pnp: PnP ACPI init                                              
[    0.683613] ACPI: bus type pnp registered                                   
[    0.687470] pnp 00:00: disabling [mem 0x00000000-0x0009ffff] because it over
laps 0000:00:02.0 BAR 1 [mem 0x00000000-0x00ffffff pref]                       
[    0.696341] pnp 00:00: disabling [mem 0x00000000-0x0009ffff disabled] becaus
e it overlaps 0000:00:03.0 BAR 0 [mem 0x00000000-0x01ffffff pref]              
[    0.706318] system 00:02: [io  0x08a0-0x08a3] has been reserved             
[    0.710732] system 00:02: [io  0x0cc0-0x0ccf] has been reserved             
[    0.715116] system 00:02: [io  0x04d0-0x04d1] has been reserved             
[    0.720790] system 00:0a: [io  0x10c0-0x1141] has been reserved             
[    0.737670] system 00:0a: [io  0xb044-0xb047] has been reserved             
[    0.767085] pnp: PnP ACPI: found 11 devices                                 
[    0.770339] ACPI: ACPI bus type pnp unregistered                            
[    0.783766] pci 0000:00:03.0: no compatible bridge window for [mem 0xffff000
0-0xffffffff pref]                                                             
[    0.790100] pci 0000:00:03.0: BAR 0: assigned [mem 0xf0000000-0xf1ffffff pre
f]                                                                             
[    0.799664] pci 0000:00:02.0: BAR 1: assigned [mem 0xf2000000-0xf2ffffff pre
f]                                                                             
[    0.809107] pci 0000:00:03.0: BAR 6: assigned [mem 0xf3000000-0xf300ffff pre
f]                                                                             
[    0.814687] pci 0000:00:03.0: BAR 1: assigned [mem 0xf3010000-0xf3010fff]   
[    0.823809] NET: Registered protocol family 2                               
[    0.827411] TCP established hash table entries: 8192 (order: 5, 131072 bytes
)                                                                              
[    0.832904] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)      
[    0.837846] TCP: Hash tables configured (established 8192 bind 8192)        
[    0.842998] TCP: reno registered                                            
[    0.845605] UDP hash table entries: 512 (order: 2, 16384 bytes)             
[    0.850273] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)        
[    0.855324] NET: Registered protocol family 1                               
[    0.858684] pci 0000:00:00.0: Limiting direct PCI/PCI transfers             
[    0.863164] pci 0000:00:01.0: PIIX3: Enabling Passive Release               
[    0.867527] pci 0000:00:01.0: Activating ISA DMA hang workarounds           
[    0.872662] Trying to unpack rootfs image as initramfs...                   
[    4.364839] Freeing initrd memory: 16480k freed                             
[    4.371559] Initialise module verification                                  
[    4.374919] audit: initializing netlink socket (disabled)                   
[    4.379301] type=2000 audit(1383214761.634:1): initialized                  
[    4.409354] HugeTLB registered 2 MB page size, pre-allocated 0 pages        
[    4.415836] VFS: Disk quotas dquot_6.5.2                                    
[    4.418986] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)       
[    4.424628] fuse init (API version 7.20)                                    
[    4.427853] msgmni has been set to 1938                                     
[    4.431554] Key type asymmetric registered                                  
[    4.434656] Asymmetric key parser 'x509' registered                         
[    4.438553] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
252)                                                                           
[    4.444494] io scheduler noop registered                                    
[    4.447621] io scheduler deadline registered (default)                      
[    4.451533] io scheduler cfq registered                                     
[    4.454590] pci_hotplug: PCI Hot Plug PCI Core version: 0.5                 
[    4.458941] pciehp: PCI Express Hot Plug Controller Driver version: 0.4     
[    4.464010] efifb: probing for efifb                                        
[    4.466804] efifb: framebuffer at 0x80000000, mapped to 0xffffc90000280000, 
using 1408k, total 1408k                                                       
[    4.473951] efifb: mode is 800x600x24, linelength=2400, pages=1             
[    4.478634] efifb: scrolling: redraw                                        
[    4.481422] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0                  
[    4.488248] Console: switching to colour frame buffer device 100x37         
[    4.494617] fb0: EFI VGA frame buffer device                                
[    4.497924] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/in
put0                                                                           
[    4.503747] ACPI: Power Button [PWRF]                                       
[    4.506712] input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/in
put1                                                                           
[    4.512512] ACPI: Sleep Button [SLPF]                                       
[    4.568653] GHES: HEST is not enabled!                                      
[    4.571947] Grant tables using version 1 layout.                            
[    4.575642] Grant table initialized
[    4.579173] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    4.615437] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    4.622547] Linux agpgart interface v0.103
[    4.628216] brd: module loaded
[    4.632035] loop: module loaded
[    4.653733] vbd vbd-832: 19 xenbus_dev_probe on device/vbd/832
[    4.662583] blkfront: xvda: flush diskcache: enabled using persistent grants
[    4.662649] vbd vbd-832: failed to write error node for device/vbd/832 (19 x
enbus_dev_probe on device/vbd/832)
[    4.672244] scsi0 : ata_piix
[    4.686446] scsi1 : ata_piix
[    4.688807] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc200 irq 14
[    4.694122] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc208 irq 15
[    4.700849] libphy: Fixed MDIO Bus: probed
[    4.705127] tun: Universal TUN/TAP device driver, 1.6
[    4.709071] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    4.713938] PPP generic driver version 2.4.2
[    4.717262]  xvda: unknown partition table
[    4.720433] Initialising Xen virtual ethernet driver.
[    4.724486] Setting capacity to 24576000
[    4.727655] xvda: detected capacity change from 0 to 12582912000
[    4.732960] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.737865] ehci-pci: EHCI PCI platform driver
[    4.741268] ehci-platform: EHCI generic platform driver
[    4.745425] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.750069] uhci_hcd: USB Universal Host Controller Interface driver
[    4.755956] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,
0x64 irq 1,12
[    4.764541] serio: i8042 KBD port at 0x60,0x64 irq 1
[    4.768231] serio: i8042 AUX port at 0x60,0x64 irq 12
[    4.772815] mousedev: PS/2 mouse device common for all mice
[    4.778390] input: AT Translated Set 2 keyboard as /devices/platform/i8042/s
erio0/input/input2
[    4.785931] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[    4.791546] rtc0: alarms up to one day, 114 bytes nvram, hpet irqs
[    4.796486] device-mapper: uevent: version 1.0.3
[    4.800193] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: dm-
devel@redhat.com
[    4.806803] cpuidle: using governor ladder
[    4.811547] cpuidle: using governor menu
[    4.815224] ledtrig-cpu: registered to indicate activity on CPUs
[    4.819808] EFI Variables Facility v0.08 2004-May-17
[    4.824289] ashmem: initialized
[    4.826835] TCP: cubic registered
[    4.829485] NET: Registered protocol family 10
[    4.833466] NET: Registered protocol family 17
[    4.837064] Key type dns_resolver registered
[    4.840783] Loading module verification certificates
[    4.845495] MODSIGN: Loaded cert 'Magrathea: Glacier signing key: 38550890b1
fce75cc801d8fb942703db919b9386'
[    4.852650] registered taskstats version 1
[    4.858151] ata1.01: ATAPI: QEMU DVD-ROM, 1.3.1, max UDMA/100
[    4.864255] ata1.01: configured for MWDMA2
[    4.867886] Key type trusted registered
[    4.871439] scsi 0:0:1:0: CD-ROM            QEMU     QEMU DVD-ROM     1.3. P
Q: 0 ANSI: 5
[    4.875101] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[    4.875102] cdrom: Uniform CD-ROM driver Revision: 3.20
[    4.875236] sr 0:0:1:0: Attached scsi generic sg0 type 5
[    4.895888] Key type encrypted registered
[    4.901431] XENBUS: Device with no driver: device/vbd/832
[    4.905750] XENBUS: Device with no driver: device/vkbd/0
[    4.910109] rtc_cmos 00:04: setting system clock to 2013-10-31 10:19:22 UTC 
(1383214762)
[    4.916145] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    4.920595] EDD information not available.
[    4.926227] Freeing unused kernel memory: 1012k freed
[    4.930357] Write protecting the kernel read-only data: 12288k
[    4.937773] Freeing unused kernel memory: 1012k freed
[    4.944600] Freeing unused kernel memory: 1008k freed
[    4.969420] udevd[108]: starting version 175
[    5.041850] Disabling lock debugging due to kernel taint
[    5.063689] [drm] Initialized drm 1.1.0 20060810
[    5.098714] [TTM] Zone  kernel: Available graphics memory: 497792 kiB
[    5.103911] [TTM] Initializing pool allocator
[    5.131896] [TTM] Initializing DMA pool allocator
[    5.157569] [drm] fb mappable at 0x0
[    5.160333] [drm] vram aper at 0x0
[    5.162936] [drm] size 0
[    5.165130] [drm] fb depth is 24
[    5.167649] [drm]    pitch is 3840
[    5.180891] fbcon: cirrusdrmfb (fb1) is primary device
[    5.180892] fbcon: Remapping primary device, fb1, to tty 1-63
[    5.256009] FDC 0 is a S82078B
[    5.368199] tsc: Refined TSC clocksource calibration: 2661.107 MHz
[   22.302244] cirrus 0000:00:03.0: fb1: cirrusdrmfb frame buffer device
[   22.307471] cirrus 0000:00:03.0: registered panic notifier
[   22.311868] [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:03.0 on mino
r 0
Begin: Loading essential drivers ... [   22.670015] Btrfs loaded
[   22.677408] xor: automatically using best checksumming function:
[   22.720061]    generic_sse:  2224.000 MB/sec
[   22.724037] device-mapper: dm-raid45: initialized v0.2594b
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... [   22.822949] squashfs: version 4.0 (2009
/01/31) Phillip Lougher
Begin: Running /scripts/casper-premount ... done.
done.
done.
Begin: Creating debconf-communicate fifo mechanism ... done.
Begin: Running /scripts/casper-bottom ... Begin: Moving mount points... ... don
e.
Begin: Configuring fstab... ... done.
Begin: Setting up swap... ... done.
Begin: Setting up locales... ... Generating locales...
  en_US.UTF-8... done
Generation complete.
done.
Begin: Setting up automatic login... ... done.
Begin: Setting hostname... ... done.
Begin: Setting up console keyboard... ... done.
Begin: Configuring gnome-panel-data... ... done.
Begin: Configuring screensaver... ... done.
Begin: Regenerating SSL certificate... ... done.
Begin: Preconfiguring /etc/modules... ... done.
Begin: Preconfiguring networking... ... done.
Begin: Loading preseed file... ... done.
Begin: Adding live session user... ... pwconv: failed to change the mode of /et
c/passwd- to 0600
done.
Begin: Setting up init... ... done.
Begin: Disabling user menu... ... done.
Begin: Configuring accessibility options... ... done.
Begin: Disabling update-notifier... ... done.
Begin: Configuring power management... ... done.
Begin: Enabling detection of crashes... ... done.
Begin: Disabling unnecessary KDE services... ... done.
Begin: Fixing language selector... ... /usr/lib/python2.7/dist-packages/Languag
eSelector/LocaleInfo.py:256: UserWarning: Failed to connect to socket /var/run/
dbus/system_bus_socket: No such file or directory
  warnings.warn(msg.args[0].encode('UTF-8'))
done.
Begin: Disabling trackerd... ... done.
Begin: Adding APT-CDROM source... ... Using CD-ROM mount point /cdrom/
Identifying.. [efbc1451e61c03989abcac77ba0be12d-2]
Scanning disc for index files..
Found 4 package indexes, 0 source indexes, 0 translation indexes and 1 signatur
es
Found label 'Ubuntu 12.04.3 LTS _Precise Pangolin_ - Release amd64 (20130820.1)
'
This disc is called: 
'Ubuntu 12.04.3 LTS _Precise Pangolin_ - Release amd64 (20130820.1)'
Copying package lists...gpgv: Signature made Tue Aug 20 18:08:18 2013 UTC using
 DSA key ID FBB75451
gpgv: Good signature from "Ubuntu CD Image Automatic Signing Key <cdimage@ubunt
u.com>"
Reading Package Indexes... Done
Writing new source list
Source list entries for this disc are:
deb cdrom:[Ubuntu 12.04.3 LTS _Precise Pangolin_ - Release amd64 (20130820.1)]/
 dists/precise/main/binary-i386/
deb cdrom:[Ubuntu 12.04.3 LTS _Precise Pangolin_ - Release amd64 (20130820.1)]/
 dists/precise/restricted/binary-i386/
deb cdrom:[Ubuntu 12.04.3 LTS _Precise Pangolin_ - Release amd64 (20130820.1)]/
 precise main restricted
Repeat this process for the rest of the CDs in your set.
W: Skipping nonexistent file /cdrom/dists/precise/main/binary-amd64/Packages
W: Skipping nonexistent file /cdrom/dists/precise/main/binary-i386/Packages
W: Skipping nonexistent file /cdrom/dists/precise/restricted/binary-amd64/Packa
ges
W: Skipping nonexistent file /cdrom/dists/precise/restricted/binary-i386/Packag
es
done.
Begin: Possibly disabling update-initramfs (useless on a live CD)... ... done.
Begin: Grant administrative PolicyKit privileges to default user... ... done.
Begin: Configuring jackd2... ... done.
Adding 'diversion of /usr/bin/bluetooth-applet to /usr/bin/bluetooth-applet.ori
g by casper'
done.
done.
Begin: Running /scripts/init-bottom ... done.
 * Starting mDNS/DNS-SD daemon                                           [ OK ]
 * Starting bluetooth daemon                                             [ OK ]
 * Starting load fallback graphics devices                               [ OK ]
 * Stopping load fallback graphics devices                               [ OK ]
[   29.189556] piix4_smbus 0000:00:01.3: Host SMBus controller not enabled!
 * Starting configure network device security                            [ OK ]
 * Starting Uncomplicated firewall                                       [ OK ]
 * Starting configure network device                                     [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting Mount network filesystems                                    [ OK ]
 * Starting Failsafe Boot Delay                                          [ OK ]
 * Stopping Mount network filesystems                                    [ OK ]
 * Starting Bridge socket events into upstart                            [ OK ]
 * Starting configure network device                                     [ OK ]
 * Stopping Failsafe Boot Delay                                          [ OK ]
 * Starting System V initialisation compatibility                        [ OK ]
 * Starting modem connection manager                                     [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting CUPS printing spooler/server                                 [ OK ]
 * Starting network connection manager                                   [ OK ]
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * Stopping cold plug devices                                            [ OK ]
saned disabled; edit /etc/default/saned
 * Stopping System V initialisation compatibility                        [ OK ]
 * Starting System V runlevel compatibility                              [ OK ]
 * Starting automatic crash report generation                            [ OK ]
 * Starting LightDM Display Manager                                      [ OK ]
 * Starting ACPI daemon                                                  [ OK ]
 * Starting save kernel messages                                         [ OK ]
 * Stopping log initial device creation                                  [ OK ]
 * Starting crash report submission daemon                               [ OK ]
 * Starting regular background program processing daemon                 [ OK ]
 * Starting deferred execution scheduler                                 [ OK ]
 * Stopping Send an event to indicate plymouth is up                     [ OK ]
 * Stopping save kernel messages                                         [ OK ]
 * Starting CPU interrupts balancing daemon                              [ OK ]
 * Starting configure network device security                            [ OK ]
[   61.489475] BUG: unable to handle kernel NULL pointer dereference at 0000000
000000260
[   61.492090] IP: [<ffffffff81365be4>] iowrite32_rep+0x54/0x70
[   61.492090] PGD 0 
[   61.492090] Oops: 0002 [#1] SMP 
[   61.492090] Modules linked in: dm_crypt(F) joydev(F) xen_kbdfront(F) dm_mult
ipath(F) scsi_dh(F) microcode(F) psmouse(F) serio_raw(F) i2c_piix4(F) mac_hid(F
) parport_pc(F) bnep(F) rfcomm(F) ppdev(F) bluetooth(F) lp(F) parport(F) squash
fs(F) overlayfs(F) nls_utf8(F) isofs(F) dm_raid45(F) xor(F) dm_mirror(F) dm_reg
ion_hash(F) dm_log(F) btrfs(F) zlib_deflate(F) libcrc32c(F) floppy(F) cirrus(F)
 ttm(F) drm_kms_helper(F) drm(F) sysimgblt(F) sysfillrect(F) syscopyarea(F)
[   61.492090] CPU 1 
[   61.492090] Pid: 27, comm: kworker/1:1 Tainted: GF            3.8.0-29-gener
ic #42~precise1-Ubuntu Xen HVM domU
[   61.492090] RIP: 0010:[<ffffffff81365be4>]  [<ffffffff81365be4>] iowrite32_r
ep+0x54/0x70
[   61.492090] RSP: 0000:ffff88003eb27cc8  EFLAGS: 00000006
[   61.492090] RAX: ffff88003e138000 RBX: 000000000000000c RCX: 000000000000000
3
[   61.492090] RDX: 00000000000001f0 RSI: ffff88003e138188 RDI: 00000000000001f
0
[   61.492090] RBP: ffff88003eb27cc8 R08: ffff88003eb26000 R09: 000000000000000
2
[   61.492090] R10: 0000000000000001 R11: 0000000000000002 R12: ffff88003e13818
8
[   61.492090] R13: 00000000000101f0 R14: 0000000000000001 R15: 000000000000000
1
[   61.492090] FS:  0000000000000000(0000) GS:ffff88003a820000(0000) knlGS:0000
000000000000
[   61.492090] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   61.492090] CR2: 0000000000000260 CR3: 0000000035912000 CR4: 00000000000006e
0
[   61.492090] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000000000
0
[   61.492090] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 000000000000040
0
[   61.492090] Process kworker/1:1 (pid: 27, threadinfo ffff88003eb26000, task 
ffff88003ea2c5c0)
[   61.492090] Stack:
[   61.492090]  ffff88003eb27d18 ffffffff814df3b7 0000000000000009 000000000eba
e7fa
[   61.492090]  ffff88003eb27cf8 ffff88003e138150 ffff88003e138000 000000000000
0286
[   61.492090]  0000000000000001 ffff88003e139f18 ffff88003eb27d38 ffffffff814d
f8f9
[   61.492090] Call Trace:
[   61.492090]  [<ffffffff814df3b7>] ata_sff_data_xfer32+0x57/0x140
[   61.492090]  [<ffffffff814df8f9>] atapi_send_cdb+0x39/0xe0
[   61.492090]  [<ffffffff814e0513>] ata_sff_hsm_move+0x183/0x4e0
[   61.492090]  [<ffffffff814e0920>] ata_sff_pio_task+0xb0/0x180
[   61.492090]  [<ffffffff81078ce1>] process_one_work+0x141/0x490
[   61.492090]  [<ffffffff81079ca8>] worker_thread+0x168/0x400
[   61.492090]  [<ffffffff81079b40>] ? manage_workers+0x120/0x120
[   61.492090]  [<ffffffff8107f1b0>] kthread+0xc0/0xd0
[   61.492090]  [<ffffffff8107f0f0>] ? flush_kthread_worker+0xb0/0xb0
[   61.492090]  [<ffffffff816fc82c>] ret_from_fork+0x7c/0xb0
[   61.492090]  [<ffffffff8107f0f0>] ? flush_kthread_worker+0xb0/0xb0
[   61.492090] Code: 83 c0 04 8b 16 89 17 48 39 c8 48 89 c6 75 f0 5d c3 66 0f 1
f 44 00 00 48 81 ff 00 00 01 00 76 17 81 e7 ff ff 00 00 48 89 d1 89 fa <f3> 6f 
5d c3 0f 1f 84 00 00 00 00 00 48 c7 c6 7d 00 a6 81 e8 24 
[   61.492090] RIP  [<ffffffff81365be4>] iowrite32_rep+0x54/0x70
[   61.492090]  RSP <ffff88003eb27cc8>
[   61.492090] CR2: 0000000000000260
[   61.492090] ---[ end trace 026264c933e33df4 ]---
[   61.772162] BUG: unable to handle kernel paging request at ffffffffffffffd8
[   61.776067] IP: [<ffffffff8107f5e0>] kthread_data+0x10/0x20
[   61.776067] PGD 1c0f067 PUD 1c10067 PMD 0 
[   61.776067] Oops: 0000 [#2] SMP 
[   61.776067] Modules linked in: dm_crypt(F) joydev(F) xen_kbdfront(F) dm_mult
ipath(F) scsi_dh(F) microcode(F) psmouse(F) serio_raw(F) i2c_piix4(F) mac_hid(F
) parport_pc(F) bnep(F) rfcomm(F) ppdev(F) bluetooth(F) lp(F) parport(F) squash
fs(F) overlayfs(F) nls_utf8(F) isofs(F) dm_raid45(F) xor(F) dm_mirror(F) dm_reg
ion_hash(F) dm_log(F) btrfs(F) zlib_deflate(F) libcrc32c(F) floppy(F) cirrus(F)
 ttm(F) drm_kms_helper(F) drm(F) sysimgblt(F) sysfillrect(F) syscopyarea(F)
[   61.776067] CPU 1 
[   61.776067] Pid: 27, comm: kworker/1:1 Tainted: GF     D      3.8.0-29-gener
ic #42~precise1-Ubuntu Xen HVM domU
[   61.776067] RIP: 0010:[<ffffffff8107f5e0>]  [<ffffffff8107f5e0>] kthread_dat
a+0x10/0x20
[   61.776067] RSP: 0000:ffff88003eb278e8  EFLAGS: 00010092
[   61.776067] RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff81e544e
0
[   61.776067] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88003ea2c5c
0
[   61.776067] RBP: ffff88003eb278e8 R08: 0000000000000001 R09: ffff88003ea30e3
0
[   61.776067] R10: 0000000000000000 R11: ffff88003ea30e20 R12: 000000000000000
1
[   61.776067] R13: ffff88003ea2c9b0 R14: 0000000000000001 R15: 000000000000004
6
[   61.776067] FS:  0000000000000000(0000) GS:ffff88003a820000(0000) knlGS:0000
000000000000
[   61.776067] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   61.776067] CR2: ffffffffffffffd8 CR3: 0000000035912000 CR4: 00000000000006e
0
[   61.776067] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000000000
0
[   61.776067] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 000000000000040
0
[   61.776067] Process kworker/1:1 (pid: 27, threadinfo ffff88003eb26000, task 
ffff88003ea2c5c0)
[   61.776067] Stack:
[   61.776067]  ffff88003eb27908 ffffffff8107a895 ffff88003eb27908 ffff88003a83
3f40
[   61.776067]  ffff88003eb27988 ffffffff816f275f ffff88003eb27938 000000000000
0000
[   61.776067]  ffff88003eb27fd8 ffff88003eb27fd8 ffff88003eb27fd8 000000000001
3f40
[   61.776067] Call Trace:
[   61.776067]  [<ffffffff8107a895>] wq_worker_sleeping+0x15/0xc0
[   61.776067]  [<ffffffff816f275f>] __schedule+0x5cf/0x6b0
[   61.776067]  [<ffffffff816f2b59>] schedule+0x29/0x70
[   61.776067]  [<ffffffff8105ff4b>] do_exit+0x2bb/0x480
[   61.776067]  [<ffffffff816f4f20>] oops_end+0xb0/0xf0
[   61.776067]  [<ffffffff816da829>] no_context+0x1ab/0x1ba
[   61.776067]  [<ffffffff816daa0b>] __bad_area_nosemaphore+0x1d3/0x1f2
[   61.776067]  [<ffffffff8109b063>] ? update_group_power+0xf3/0x100
[   61.776067]  [<ffffffff816daa3d>] bad_area_nosemaphore+0x13/0x15
[   61.776067]  [<ffffffff816f7de2>] __do_page_fault+0x3c2/0x560
[   61.776067]  [<ffffffff816f7f8e>] do_page_fault+0xe/0x10
[   61.776067]  [<ffffffff816f4358>] page_fault+0x28/0x30
[   61.776067]  [<ffffffff81365be4>] ? iowrite32_rep+0x54/0x70
[   61.776067]  [<ffffffff814df3b7>] ata_sff_data_xfer32+0x57/0x140
[   61.776067]  [<ffffffff814df8f9>] atapi_send_cdb+0x39/0xe0
[   61.776067]  [<ffffffff814e0513>] ata_sff_hsm_move+0x183/0x4e0
[   61.776067]  [<ffffffff814e0920>] ata_sff_pio_task+0xb0/0x180
[   61.776067]  [<ffffffff81078ce1>] process_one_work+0x141/0x490
[   61.776067]  [<ffffffff81079ca8>] worker_thread+0x168/0x400
[   61.776067]  [<ffffffff81079b40>] ? manage_workers+0x120/0x120
[   61.776067]  [<ffffffff8107f1b0>] kthread+0xc0/0xd0
[   61.776067]  [<ffffffff8107f0f0>] ? flush_kthread_worker+0xb0/0xb0
[   61.776067]  [<ffffffff816fc82c>] ret_from_fork+0x7c/0xb0
[   61.776067]  [<ffffffff8107f0f0>] ? flush_kthread_worker+0xb0/0xb0
[   61.776067] Code: 00 48 89 e5 5d 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 2e 0
f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 98 03 00 00 55 48 89 e5 <48> 8b 
40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 
[   61.776067] RIP  [<ffffffff8107f5e0>] kthread_data+0x10/0x20
[   61.776067]  RSP <ffff88003eb278e8>
[   61.776067] CR2: ffffffffffffffd8
[   61.776067] ---[ end trace 026264c933e33df5 ]---

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Thu, Oct 31, 2013 at 10:47:24AM +0100, Fabio Fantoni wrote:
> Il 30/10/2013 16:58, Wei Liu ha scritto:
> >On Wed, Oct 30, 2013 at 04:52:52PM +0100, Fabio Fantoni wrote:
> >[...]
> >>I also tried another build without change qemu repo and changet but
> >>same result.
> >>Do you have domUs working on ovmf? If yes what are differences from
> >>my test system?
> >>
> >>I tried to change also domU parameters:
> >>- removing audio, vdagent and usb redirection it changes nothing.
> >>- switch from stdvga to cirrus vga solves the performance problem,
> >>but with Precise it shows always a black screen after start of
> >>grub-efi entry, and black screen also with windows 7 installer.
> >>
> >>What domU vga you used on your tests?
> >>
> >Cirrus, because there's cirrus driver in OVMF. I don't know whether
> >there is driver for stdvga.
> >
> >Black screen is expected because there's probably something wrong with
> >OVMF / Xen. I need to check real hardware behavior to identify the
> >problem.
> >
> >>I'm trying to setup ovmf serial console, but I have no idea on where
> >>to start from. Do you have some suggestions?
> >>
> >Add serial='pty' in you HVM guest config file. I believe you can get a
> >tutorial on wiki.xen.org
> >
> >Wei.
> 
> Thanks and sorry for the stupid question.
> Precise's boot stops with calltrace, log on attachment.
> I'll try also with latest ubuntu version (Saucy) with newer kernel
> (3.11) and with latest stable qemu version (1.6.1).
> 
> >>Thanks for any reply.
> >>
> >>>>>>If you need more informations and/or tests tell me and I'll do/post them.
> >>>>>>
> >>>>>>About legacy bios support that I mentioned days ago I found this
> >>>>>>document about:
> >>>>>>http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
> >>>>>>Seem that need ovmf change (and probably also on hvmloader) that are
> >>>>>>not able to do.
> >>>>>>
> >>>>>>Thank for any reply and sorry for my bad english.
> 
> This idea could be enable legacy bios and vgabioses support on
> ovmf... Is that really stupid question to not deserve an aswer?
> Thanks for any reply.

I think we need to wait until this happens in upstream.

As for the guest log, I don't have a clear idea whether it is caused by
OVMF at this stage. Null pointer deference looks just like a normal bug
but I'm not sure whether it is caused by OVMF setting up the wrong thing
very far ahead...

Wei.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 31/10/2013 11:03, Wei Liu ha scritto:
> On Thu, Oct 31, 2013 at 10:47:24AM +0100, Fabio Fantoni wrote:
>> Il 30/10/2013 16:58, Wei Liu ha scritto:
>>> On Wed, Oct 30, 2013 at 04:52:52PM +0100, Fabio Fantoni wrote:
>>> [...]
>>>> I also tried another build without change qemu repo and changet but
>>>> same result.
>>>> Do you have domUs working on ovmf? If yes what are differences from
>>>> my test system?
>>>>
>>>> I tried to change also domU parameters:
>>>> - removing audio, vdagent and usb redirection it changes nothing.
>>>> - switch from stdvga to cirrus vga solves the performance problem,
>>>> but with Precise it shows always a black screen after start of
>>>> grub-efi entry, and black screen also with windows 7 installer.
>>>>
>>>> What domU vga you used on your tests?
>>>>
>>> Cirrus, because there's cirrus driver in OVMF. I don't know whether
>>> there is driver for stdvga.
>>>
>>> Black screen is expected because there's probably something wrong with
>>> OVMF / Xen. I need to check real hardware behavior to identify the
>>> problem.
>>>
>>>> I'm trying to setup ovmf serial console, but I have no idea on where
>>>> to start from. Do you have some suggestions?
>>>>
>>> Add serial='pty' in you HVM guest config file. I believe you can get a
>>> tutorial on wiki.xen.org
>>>
>>> Wei.
>> Thanks and sorry for the stupid question.
>> Precise's boot stops with calltrace, log on attachment.
>> I'll try also with latest ubuntu version (Saucy) with newer kernel
>> (3.11) and with latest stable qemu version (1.6.1).
>>
>>>> Thanks for any reply.
>>>>
>>>>>>>> If you need more informations and/or tests tell me and I'll do/post them.
>>>>>>>>
>>>>>>>> About legacy bios support that I mentioned days ago I found this
>>>>>>>> document about:
>>>>>>>> http://code.coreboot.org/p/seabios/source/tree/master/README.CSM
>>>>>>>> Seem that need ovmf change (and probably also on hvmloader) that are
>>>>>>>> not able to do.
>>>>>>>>
>>>>>>>> Thank for any reply and sorry for my bad english.
>> This idea could be enable legacy bios and vgabioses support on
>> ovmf... Is that really stupid question to not deserve an aswer?
>> Thanks for any reply.
> I think we need to wait until this happens in upstream.
>
> As for the guest log, I don't have a clear idea whether it is caused by
> OVMF at this stage. Null pointer deference looks just like a normal bug
> but I'm not sure whether it is caused by OVMF setting up the wrong thing
> very far ahead...
>
> Wei.

I tried with saucy and it boot but has graphic performance issue and no 
mouse.
About windows problem it is probably due to a missed cirrus driver on 
windows 7.
The only other option that I found should be try with stdvga but seem it 
needs legacy vgabios from csm.
What if I try to add ovmf patches for legacybios (that seems to have 
also memory patch) from this git?
http://git.infradead.org/users/dwmw2/edk2.git
Does it make sense without modification to hvmloader?
Thanks for any reply.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

On Thu, Oct 31, 2013 at 12:22:32PM +0100, Fabio Fantoni wrote:
[...]
> 
> I tried with saucy and it boot but has graphic performance issue and
> no mouse.
> About windows problem it is probably due to a missed cirrus driver
> on windows 7.
> The only other option that I found should be try with stdvga but
> seem it needs legacy vgabios from csm.
> What if I try to add ovmf patches for legacybios (that seems to have
> also memory patch) from this git?
> http://git.infradead.org/users/dwmw2/edk2.git
> Does it make sense without modification to hvmloader?
> Thanks for any reply.

It's really hard to tell whether these out-of-tree patches will be of
any help for the cuurent situation.

Wei.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

Il 31/10/2013 15:40, Wei Liu ha scritto:
> On Thu, Oct 31, 2013 at 12:22:32PM +0100, Fabio Fantoni wrote:
> [...]
>> I tried with saucy and it boot but has graphic performance issue and
>> no mouse.
>> About windows problem it is probably due to a missed cirrus driver
>> on windows 7.
>> The only other option that I found should be try with stdvga but
>> seem it needs legacy vgabios from csm.
>> What if I try to add ovmf patches for legacybios (that seems to have
>> also memory patch) from this git?
>> http://git.infradead.org/users/dwmw2/edk2.git
>> Does it make sense without modification to hvmloader?
>> Thanks for any reply.
> It's really hard to tell whether these out-of-tree patches will be of
> any help for the cuurent situation.
>
> Wei.

Sorry, I try to better explain what i meant:
In my earlier mail, what I was asking is:
since the patch to OVMF to prevent it from marking the region from 
0xC0000-0xFFFFF as read-only before invoking Legacy16Boot method is 
already present on the git I've linked, I was asking if such a patch 
should works without any further modification xen-side.
On the other hand, if you think the patch will never work without xen 
modifications, I'll not test csm now but I'll wait xen change.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Wei Liu]

Just notice you also attached log files...

You can just inline them in mail or attach them one by one instead of
making zip / tarball -- this will be much easier for people to look at
them.

Wei.

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Fabio Fantoni]

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Il 30/10/2013 13:09, Wei Liu ha scritto:
> Just notice you also attached log files...
>
> You can just inline them in mail or attach them one by one instead of
> making zip / tarball -- this will be much easier for people to look at
> them.
>
> Wei.

Done and also reported below some part about of previous mail...



I found this error on xl dmesg:
> (XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
I see a recently posted patch about pfn:
http://lists.xen.org/archives/html/xen-devel/2013-10/msg02028.html
Can this serie solve the problem and I have to try it or has nothing to 
do with this?

And this is the error that cause reboot of domU:
> (XEN) hvm.c:1274:d4 Triple fault on VCPU0 - invoking HVM shutdown 
> action 1.

I not found any other error or relevant information on logs but I attach 
them if you want see.

I also tried with Ubuntu 12.04.3, same pfn error on xl dmesg, same 
performance problem (some minutes only for arrive to grub-efi of dvd) 
and after other 10-15 minutes without complete the boot I did a destroy.
Also for that logs on attachments.

Despite windows is bad, it seems that problems persist even in the test 
linux except the shutdown with vcpu issue.

The dom0 used have the installation of this:
http://lists.xen.org/archives/html/xen-devel/2013-10/msg01111.html
Except the git branch used (here the hvm-improve.t6) and the qemu:
QEMU_UPSTREAM_URL ?= 
git://xenbits.xen.org/staging/qemu-upstream-unstable.git
QEMU_UPSTREAM_REVISION ?= master

[-- Attachment #2: qemu-dm-W7UEFI.log.1 --]
[-- Type: text/plain, Size: 1113 bytes --]

xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
(/usr/sbin/xl:7067): SpiceWorker-Warning **: red_worker.c:11464:dev_destroy_primary_surface: double destroy of primary surface
(/usr/sbin/xl:7067): SpiceWorker-Warning **: red_worker.c:9650:red_create_surface: condition `surface->context.canvas' reached
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 43.405000 ms, bitrate 656410256 bps (626.001602 Mbps)
inputs_connect: inputs channel client create
red_dispatcher_set_cursor_peer: 
qemu: terminating on signal 1 from pid 7174
red_channel_client_disconnect: 0x7fd1f698e110 (channel 0x7fd1f68600b0 type 5 id 0)
snd_channel_put: sound channel freed
red_channel_client_disconnect: 0x7fd1f69dbd60 (channel 0x7fd1f6860230 type 6 id 0)
snd_channel_put: sound channel freed

[-- Attachment #3: W7UEFI.cfg --]
[-- Type: text/plain, Size: 839 bytes --]

name='W7UEFI'
builder="hvm"
#device_model_override="/usr/bin/qemu-system-x86_64"
bios="ovmf"
memory=2048
vcpus=2
nestedhvm=1
#vif=['model=e1000,bridge=xenbr0']
vif=['bridge=xenbr0,mac=00:16:3e:42:ab:6f']
#vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap=it']
disk=['/mnt/vm/disks/W7UEFI.disk1.xm,raw,hda,rw','/mnt/vm/iso/W7PRO64SP1.iso,raw,hdb,ro,cdrom']
boot='dc'
device_model_version="qemu-xen"
xen_platform_pci=1
viridian=1
vnc=0
#vncunused=1
#vnclisten="0.0.0.0"
#keymap="it"
#on_poweroff="destroy"
#on_reboot="restart"
on_crash="destroy"
vga="stdvga"
#videoram=16
spice=1
spicehost='0.0.0.0'
spiceport=6002
spicedisable_ticketing=1
spicevdagent=1
spice_clipboard_sharing=0
spiceusbredirection=4
soundhw="hda"
localtime=1
#usb=1
#usbversion=2
#spicepasswd="prova"

#device_model_args=["-trace","events=/etc/xen/qemu-trace-options"]


[-- Attachment #4: xldmesg-PRECISE.txt --]
[-- Type: text/plain, Size: 2988 bytes --]

(d6) HVM Loader
(d6) Detected Xen v4.4-unstable
(d6) Xenbus rings @0xfeffc000, event channel 4
(d6) System requested OVMF
(d6) CPU speed is 2661 MHz
(d6) Relocating guest memory for lowmem MMIO space disabled
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(d6) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(d6) PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(d6) PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(d6) PCI-ISA link 3 routed to IRQ5
(d6) pci dev 01:3 INTA->IRQ10
(d6) pci dev 02:0 INTA->IRQ11
(d6) pci dev 03:0 INTA->IRQ5
(d6) pci dev 04:0 INTA->IRQ5
(d6) pci dev 06:0 INTA->IRQ11
(d6) No RAM in high memory; setting high_mem resource base to 100000000
(d6) pci dev 02:0 bar 14 size 001000000: 0f0000008
(d6) pci dev 05:0 bar 10 size 001000000: 0f1000008
(d6) pci dev 06:0 bar 30 size 000040000: 0f2000000
(d6) pci dev 05:0 bar 30 size 000010000: 0f2040000
(d6) pci dev 03:0 bar 10 size 000004000: 0f2050000
(d6) pci dev 04:0 bar 14 size 000001000: 0f2054000
(d6) pci dev 05:0 bar 18 size 000001000: 0f2055000
(d6) pci dev 02:0 bar 10 size 000000100: 00000c001
(d6) pci dev 06:0 bar 10 size 000000100: 00000c101
(d6) pci dev 06:0 bar 14 size 000000100: 0f2056000
(d6) pci dev 04:0 bar 10 size 000000020: 00000c201
(d6) pci dev 01:1 bar 20 size 000000010: 00000c221
(d6) Multiprocessor initialisation:
(d6)  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(d6)  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(d6) Testing HVM environment:
(d6)  - REP INSB across page boundaries ... passed
(d6)  - GS base MSRs and SWAPGS ... passed
(d6) Passed 2 of 2 tests
(d6) Writing SMBIOS tables ...
(d6) Loading OVMF ...
(d6) Loading ACPI ...
(d6) vm86 TSS at fc012c00
(d6) BIOS map:
(d6)  00000-fffff: Main BIOS
(d6) Invoking OVMF ...
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) irq.c:270: Dom6 PCI link 0 changed 5 -> 11
(XEN) irq.c:270: Dom6 PCI link 1 changed 10 -> 11
(XEN) irq.c:270: Dom6 PCI link 2 changed 11 -> 10
(XEN) irq.c:270: Dom6 PCI link 3 changed 5 -> 10
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) irq.c:375: Dom6 callback via changed to Direct Vector 0xf3
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) irq.c:270: Dom6 PCI link 0 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 1 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 2 changed 10 -> 0
(XEN) irq.c:270: Dom6 PCI link 3 changed 10 -> 0

[-- Attachment #5: xldmesg-W7.txt --]
[-- Type: text/plain, Size: 2607 bytes --]

(d4) HVM Loader
(d4) Detected Xen v4.4-unstable
(d4) Xenbus rings @0xfeffc000, event channel 4
(d4) System requested OVMF
(d4) CPU speed is 2661 MHz
(d4) Relocating guest memory for lowmem MMIO space disabled
(XEN) irq.c:270: Dom4 PCI link 0 changed 0 -> 5
(d4) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom4 PCI link 1 changed 0 -> 10
(d4) PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom4 PCI link 2 changed 0 -> 11
(d4) PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom4 PCI link 3 changed 0 -> 5
(d4) PCI-ISA link 3 routed to IRQ5
(d4) pci dev 01:3 INTA->IRQ10
(d4) pci dev 02:0 INTA->IRQ11
(d4) pci dev 03:0 INTA->IRQ5
(d4) pci dev 04:0 INTA->IRQ5
(d4) pci dev 06:0 INTA->IRQ11
(d4) pci dev 1d:0 INTA->IRQ10
(d4) pci dev 1d:1 INTB->IRQ11
(d4) pci dev 1d:2 INTC->IRQ5
(d4) pci dev 1d:7 INTD->IRQ5
(d4) No RAM in high memory; setting high_mem resource base to 100000000
(d4) pci dev 02:0 bar 14 size 001000000: 0f0000008
(d4) pci dev 05:0 bar 10 size 001000000: 0f1000008
(d4) pci dev 06:0 bar 30 size 000040000: 0f2000000
(d4) pci dev 05:0 bar 30 size 000010000: 0f2040000
(d4) pci dev 03:0 bar 10 size 000004000: 0f2050000
(d4) pci dev 04:0 bar 14 size 000001000: 0f2054000
(d4) pci dev 05:0 bar 18 size 000001000: 0f2055000
(d4) pci dev 1d:7 bar 10 size 000001000: 0f2056000
(d4) pci dev 02:0 bar 10 size 000000100: 00000c001
(d4) pci dev 06:0 bar 10 size 000000100: 00000c101
(d4) pci dev 06:0 bar 14 size 000000100: 0f2057000
(d4) pci dev 04:0 bar 10 size 000000020: 00000c201
(d4) pci dev 1d:0 bar 20 size 000000020: 00000c221
(d4) pci dev 1d:1 bar 20 size 000000020: 00000c241
(d4) pci dev 1d:2 bar 20 size 000000020: 00000c261
(d4) pci dev 01:1 bar 20 size 000000010: 00000c281
(d4) Multiprocessor initialisation:
(d4)  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(d4)  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(d4) Testing HVM environment:
(d4)  - REP INSB across page boundaries ... passed
(d4)  - GS base MSRs and SWAPGS ... passed
(d4) Passed 2 of 2 tests
(d4) Writing SMBIOS tables ...
(d4) Loading OVMF ...
(d4) Loading ACPI ...
(d4) vm86 TSS at fc012c00
(d4) BIOS map:
(d4)  00000-fffff: Main BIOS
(d4) Invoking OVMF ...
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) mm.c:620:d0 Could not get page ref for pfn ffffffffffffffff
(XEN) irq.c:270: Dom4 PCI link 0 changed 5 -> 11
(XEN) irq.c:270: Dom4 PCI link 1 changed 10 -> 11
(XEN) irq.c:270: Dom4 PCI link 2 changed 11 -> 10
(XEN) irq.c:270: Dom4 PCI link 3 changed 5 -> 10
(XEN) hvm.c:1274:d4 Triple fault on VCPU0 - invoking HVM shutdown action 1.

[-- Attachment #6: xl-PRECISEUEFI.log --]
[-- Type: text/plain, Size: 2870 bytes --]

Waiting for domain PRECISEUEFI (domid 6) to die [pid 7866]
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0x1dc0380 wpath=@releaseDomain token=3/0: register slotnum=3
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: register slotnum=2
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0380 wpath=@releaseDomain token=3/0: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0x1dbe8e0:6] from domid=6 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0x1dbe8e0:6]   got=domaininfos[0] got->domain=6
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff0002
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: event epath=/local/domain/6/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: event epath=/local/domain/6/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: event epath=/local/domain/6/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: event epath=/local/domain/6/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1dc0380 wpath=@releaseDomain token=3/0: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0x1dbe8e0:6] from domid=6 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0x1dbe8e0:6]   got=domaininfos[0] got->domain=6
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff000b
libxl: debug: libxl.c:961:domain_death_occurred: dying
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
Domain 6 has been destroyed.
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0x1dc0380 wpath=@releaseDomain token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0x1dc0050 wpath=/local/domain/6/device/vbd/832/eject token=2/1: deregister slotnum=2
xc: debug: hypercall buffer: total allocations:4 total releases:4
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:2 misses:2 toobig:0

[-- Attachment #7: xl-W7UEFI.log --]
[-- Type: text/plain, Size: 17384 bytes --]

Waiting for domain W7UEFI (domid 4) to die [pid 7174]
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc4fb20 wpath=@releaseDomain token=3/0: register slotnum=3
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc50200 wpath=/local/domain/4/device/vbd/832/eject token=2/1: register slotnum=2
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc4fb20 wpath=@releaseDomain token=3/0: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0xc55b90:4] from domid=4 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0xc55b90:4]   got=domaininfos[0] got->domain=4
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff0002
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc50200 wpath=/local/domain/4/device/vbd/832/eject token=2/1: event epath=/local/domain/4/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc4fb20 wpath=@releaseDomain token=3/0: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0xc55b90:4] from domid=4 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0xc55b90:4]   got=domaininfos[0] got->domain=4
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=10006
libxl: debug: libxl.c:1055:domain_death_xswatch_callback:  shutdown reporting
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
Domain 4 has shut down, reason code 1 0x1
Action for shutdown reason code 1 is restart
Domain 4 needs to be cleaned up: destroying the domain
libxl: debug: libxl.c:1257:libxl_domain_destroy: ao 0xc504e0: create: how=(nil) callback=(nil) poller=0xc500d0
libxl: debug: libxl_dm.c:1383:libxl__destroy_device_model: Device Model signaled
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc50ec8 wpath=/local/domain/0/backend/vif/4/0/state token=1/2: register slotnum=1
libxl: debug: libxl.c:1266:libxl_domain_destroy: ao 0xc504e0: inprogress: poller=0xc500d0, flags=i
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc50ec8 wpath=/local/domain/0/backend/vif/4/0/state token=1/2: event epath=/local/domain/0/backend/vif/4/0/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend /local/domain/0/backend/vif/4/0/state wanted state 6 still waiting state 5
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc50ec8 wpath=/local/domain/0/backend/vif/4/0/state token=1/2: event epath=/local/domain/0/backend/vif/4/0/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend /local/domain/0/backend/vif/4/0/state wanted state 6 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc50ec8 wpath=/local/domain/0/backend/vif/4/0/state token=1/2: deregister slotnum=1
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0xc50ec8: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge offline
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge remove
libxl: debug: libxl_event.c:1570:libxl__ao_complete: ao 0xc504e0: complete, rc=0
libxl: debug: libxl_event.c:1542:libxl__ao__destroy: ao 0xc504e0: destroy
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc4fb20 wpath=@releaseDomain token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc50200 wpath=/local/domain/4/device/vbd/832/eject token=2/1: deregister slotnum=2
Done. Rebooting now
libxl: debug: libxl_create.c:1307:do_domain_create: ao 0xc56ce0: create: how=(nil) callback=(nil) poller=0xc500d0
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=hda, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=hda, using backend qdisk
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=unknown
libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=hdb, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=hdb, using backend qdisk
libxl: debug: libxl_create.c:751:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV domain, skipping bootloader
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0xc52208: deregister unregistered
libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=8, nr_vcpus=10, free_memkb=10064
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement candidate with 1 nodes, 8 cpus and 10064 KB free selected
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x19f128
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x29f128
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000029f128
  Modules:       0000000000000000->0000000000000000
  TOTAL:         0000000000000000->000000007f000000
  ENTRY ADDRESS: 0000000000100000
xc: detail: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003f7
  1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x7facea04e000 -> 0x7facea1e3fad
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=qdisk
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=qdisk
libxl: debug: libxl_dm.c:1280:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-system-i386
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -xen-domid
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   5
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-5,server,nowait
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -mon
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -nodefaults
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -name
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   W7UEFI
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -spice
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   port=6002,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on,disable-copy-paste
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   virtio-serial
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   spicevmc,id=vdagent,name=vdagent
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   virtserialport,chardev=vdagent,name=com.redhat.spice.0
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   VGA
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -boot
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   order=dc
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   ich9-usb-ehci1,id=usb,addr=0x1d.0x7,multifunction=on
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   ich9-usb-uhci1,masterbus=usb.0,firstport=0,addr=0x1d.0,multifunction=on
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   ich9-usb-uhci2,masterbus=usb.0,firstport=2,addr=0x1d.0x1,multifunction=on
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   ich9-usb-uhci3,masterbus=usb.0,firstport=4,addr=0x1d.0x2,multifunction=on
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   spicevmc,name=usbredir,id=usbrc1
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   usb-redir,chardev=usbrc1,id=usbrc1
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   spicevmc,name=usbredir,id=usbrc2
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   usb-redir,chardev=usbrc2,id=usbrc2
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   spicevmc,name=usbredir,id=usbrc3
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   usb-redir,chardev=usbrc3,id=usbrc3
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -chardev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   spicevmc,name=usbredir,id=usbrc4
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   usb-redir,chardev=usbrc4,id=usbrc4
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -soundhw
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   hda
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -smp
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   2,maxcpus=2
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -device
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   rtl8139,id=nic0,netdev=net0,mac=00:16:3e:42:ab:6f
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -netdev
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   type=tap,id=net0,ifname=vif5.0-emu,script=no,downscript=no
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -M
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   xenfv
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -m
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   2032
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -drive
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   file=/mnt/vm/disks/W7UEFI.disk1.xm,if=ide,index=0,media=disk,format=raw,cache=writeback
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   -drive
libxl: debug: libxl_dm.c:1282:libxl__spawn_local_dm:   file=/mnt/vm/iso/W7PRO64SP1.iso,if=ide,index=1,media=cdrom,format=raw,cache=writeback,id=ide-832
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc52440 wpath=/local/domain/0/device-model/5/state token=2/3: register slotnum=2
libxl: debug: libxl_create.c:1321:do_domain_create: ao 0xc56ce0: inprogress: poller=0xc500d0, flags=i
libxl: debug: libxl_event.c:478:watchfd_callback: watch w=0xc52440 epath=/local/domain/4/device/vbd/832/eject token=2/1: counter != 3
libxl: debug: libxl_event.c:478:watchfd_callback: watch w=0xc52440 epath=/local/domain/4/device/vbd/832/eject token=2/1: counter != 3
libxl: debug: libxl_event.c:478:watchfd_callback: watch w=0xc52440 epath=/local/domain/4/device/vbd/832/eject token=2/1: counter != 3
libxl: debug: libxl_event.c:472:watchfd_callback: watch epath=@releaseDomain token=3/0: empty slot
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc52440 wpath=/local/domain/0/device-model/5/state token=2/3: event epath=/local/domain/0/device-model/5/state
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc52440 wpath=/local/domain/0/device-model/5/state token=2/3: event epath=/local/domain/0/device-model/5/state
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc52440 wpath=/local/domain/0/device-model/5/state token=2/3: deregister slotnum=2
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0xc52440: deregister unregistered
libxl: debug: libxl_qmp.c:708:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-5
libxl: debug: libxl_qmp.c:300:qmp_handle_response: message type: qmp
libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{
    "execute": "qmp_capabilities",
    "id": 1
}
'
libxl: debug: libxl_qmp.c:300:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{
    "execute": "query-chardev",
    "id": 2
}
'
libxl: debug: libxl_qmp.c:300:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{
    "execute": "query-vnc",
    "id": 3
}
'
libxl: debug: libxl_qmp.c:300:qmp_handle_response: message type: return
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc57878 wpath=/local/domain/0/backend/vif/5/0/state token=2/4: register slotnum=2
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc57878 wpath=/local/domain/0/backend/vif/5/0/state token=2/4: event epath=/local/domain/0/backend/vif/5/0/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc57878 wpath=/local/domain/0/backend/vif/5/0/state token=2/4: event epath=/local/domain/0/backend/vif/5/0/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc57878 wpath=/local/domain/0/backend/vif/5/0/state token=2/4: deregister slotnum=2
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0xc57878: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge add
libxl: debug: libxl_event.c:1738:libxl__ao_progress_report: ao 0xc56ce0: progress report: ignored
libxl: debug: libxl_event.c:1570:libxl__ao_complete: ao 0xc56ce0: complete, rc=0
libxl: debug: libxl_event.c:1542:libxl__ao__destroy: ao 0xc56ce0: destroy
Waiting for domain W7UEFI (domid 5) to die [pid 7174]
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc4fb20 wpath=@releaseDomain token=2/5: register slotnum=2
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc4fb20 wpath=@releaseDomain token=2/5: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0xc4f950:5] from domid=5 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0xc4f950:5]   got=domaininfos[0] got->domain=5
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff0002
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: event epath=/local/domain/5/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: event epath=/local/domain/5/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: event epath=/local/domain/5/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: event epath=/local/domain/5/device/vbd/832/eject
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xc4fb20 wpath=@releaseDomain token=2/5: event epath=@releaseDomain
libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0xc4f950:5] from domid=5 nentries=1 rc=1
libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0xc4f950:5]   got=domaininfos[0] got->domain=5
libxl: debug: libxl.c:1043:domain_death_xswatch_callback:  exists shutdown_reported=0 dominf.flags=ffff000b
libxl: debug: libxl.c:961:domain_death_occurred: dying
libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported
libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done
Domain 5 has been destroyed.
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc4fb20 wpath=@releaseDomain token=2/5: deregister slotnum=2
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xc56940 wpath=/local/domain/5/device/vbd/832/eject token=3/6: deregister slotnum=3
xc: debug: hypercall buffer: total allocations:981 total releases:981
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:973 misses:4 toobig:4

[-- Attachment #8: PRECISEUEFI.cfg --]
[-- Type: text/plain, Size: 615 bytes --]

name='PRECISEUEFI'
builder="hvm"
bios="ovmf"
memory=1024
vcpus=2
vif=['bridge=xenbr0']
#vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap="it"']
disk=['/mnt/vm/disks/PRECISEUEFI.disk1.xm,raw,hda,rw', '/mnt/vm/iso/PRECISE3.iso,raw,hdb,ro,cdrom']
#disk=['/mnt/vm/disks/PRECISEHVM.disk1.xm,raw,hda,rw']
boot='c'
#xen_platform_pci=1
device_model_version='qemu-xen'
vnc=0
#vncunused=1
#vnclisten="0.0.0.0"
keymap="it"
vga="stdvga"
#videoram=16

spice=1
spicehost='0.0.0.0'
spiceport=6002
spicedisable_ticketing=1
spicevdagent=1
#spiceusbredirection=1
soundhw="hda"
localtime=1
#usb=1
#usbversion=2
#spicepasswd="prova"

[-- Attachment #9: qemu-dm-PRECISEUEFI.log --]
[-- Type: text/plain, Size: 1113 bytes --]

xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
(/usr/sbin/xl:7759): SpiceWorker-Warning **: red_worker.c:11464:dev_destroy_primary_surface: double destroy of primary surface
(/usr/sbin/xl:7759): SpiceWorker-Warning **: red_worker.c:9650:red_create_surface: condition `surface->context.canvas' reached
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 49.223000 ms, bitrate 629960012 bps (600.776684 Mbps)
inputs_connect: inputs channel client create
red_dispatcher_set_cursor_peer: 
qemu: terminating on signal 1 from pid 7948
red_channel_client_disconnect: 0x7fa07b161d90 (channel 0x7fa07b1218c0 type 5 id 0)
snd_channel_put: sound channel freed
red_channel_client_disconnect: 0x7fa07b1f69a0 (channel 0x7fa07b11ba40 type 6 id 0)
snd_channel_put: sound channel freed

[-- Attachment #10: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [PATCH V3 2/5] Config.mk: update OVMF changeset

[Ian Campbell]

On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>

Along with a reminder to self to pull
git://xenbits.xen.org/people/liuw/ovmf.git for-xenbits
and push
ssh://xenbits.xen.org/home/xen/git/ovmf.git FETCH_HEAD:master

while committing...

> ---
>  Config.mk |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Config.mk b/Config.mk
> index 1879454..dad2dc4 100644
> --- a/Config.mk
> +++ b/Config.mk
> @@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
>  QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
>  SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
>  endif
> -OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> +OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
>  QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
>  SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
>  # Fri Aug 2 14:12:09 2013 -0400

[PATCH V3 3/5] tools: clone ovmf to ovmf-dir directory

[Wei Liu]

From: Ian Campbell <ian.campbell@citrix.com>

for consistency with other foo-dir e.g. qemu, seabios.

Remove obsolete ovmf-find target.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
 Makefile                          |    4 ++++
 tools/firmware/Makefile           |   29 ++++++++++-------------------
 tools/firmware/hvmloader/Makefile |    2 +-
 3 files changed, 15 insertions(+), 20 deletions(-)

diff --git a/Makefile b/Makefile
index d915660..4e48457 100644
--- a/Makefile
+++ b/Makefile
@@ -110,6 +110,10 @@ endif
 tools/firmware/seabios-dir-force-update:
 	$(MAKE) -C tools/firmware seabios-dir-force-update
 
+.PHONY: tools/firmware/ovmf-dir-force-update
+tools/firmware/ovmf-dir-force-update:
+	$(MAKE) -C tools/firmware ovmf-dir-force-update
+
 .PHONY: install-docs
 install-docs:
 	$(MAKE) -C docs install
diff --git a/tools/firmware/Makefile b/tools/firmware/Makefile
index f064765..8633748 100644
--- a/tools/firmware/Makefile
+++ b/tools/firmware/Makefile
@@ -6,7 +6,7 @@ TARGET      := hvmloader/hvmloader
 INST_DIR := $(DESTDIR)$(XENFIRMWAREDIR)
 
 SUBDIRS-y :=
-SUBDIRS-$(CONFIG_OVMF) += ovmf
+SUBDIRS-$(CONFIG_OVMF) += ovmf-dir
 ifeq ($(SEABIOS_PATH),)
 SUBDIRS-$(CONFIG_SEABIOS) += seabios-dir
 endif
@@ -15,9 +15,9 @@ SUBDIRS-$(CONFIG_ROMBIOS) += vgabios
 SUBDIRS-$(CONFIG_ROMBIOS) += etherboot
 SUBDIRS-y += hvmloader
 
-ovmf:
-	GIT=$(GIT) $(XEN_ROOT)/scripts/git-checkout.sh $(OVMF_UPSTREAM_URL) $(OVMF_UPSTREAM_REVISION) ovmf
-	cp ovmf-makefile ovmf/Makefile;
+ovmf-dir:
+	GIT=$(GIT) $(XEN_ROOT)/scripts/git-checkout.sh $(OVMF_UPSTREAM_URL) $(OVMF_UPSTREAM_REVISION) ovmf-dir
+	cp ovmf-makefile ovmf-dir/Makefile;
 
 seabios-dir:
 	GIT=$(GIT) $(XEN_ROOT)/scripts/git-checkout.sh $(SEABIOS_UPSTREAM_URL) $(SEABIOS_UPSTREAM_TAG) seabios-dir
@@ -52,32 +52,23 @@ subdir-distclean-etherboot: .phony
 	$(MAKE) -C etherboot distclean
 
 subdir-distclean-ovmf: .phony
-	rm -rf ovmf ovmf-remote
+	rm -rf ovmf-dir ovmf-dir-remote
 
 subdir-distclean-seabios-dir: .phony
 	rm -rf seabios-dir seabios-dir-remote
 
-.PHONY: ovmf-find
-ovmf-find:
-	if test -d $(OVMF_UPSTREAM_URL) ; then \
-	               mkdir -p ovmf; \
-        else \
-                export GIT=$(GIT); \
-                $(XEN_ROOT)/scripts/git-checkout.sh $(OVMF_UPSTREAM_URL) $(OVMF_UPSTREAM_REVISION) ovmf ; \
-        fi
-
-.PHONY: ovmf-force-update
-ovmf-force-update:
+.PHONY: ovmf-dir-force-update
+ovmf-dir-force-update:
 	set -ex; \
 	if [ "$(OVMF_UPSTREAM_REVISION)" ]; then \
-		cd ovmf-remote; \
+		cd ovmf-dir-remote; \
 		$(GIT) fetch origin; \
 		$(GIT) reset --hard $(OVMF_UPSTREAM_REVISION); \
 	fi
 
 subdir-clean-ovmf:
-	set -e; if test -d ovmf/.; then \
-		$(MAKE) -C ovmf clean; \
+	set -e; if test -d ovmf-dir/.; then \
+		$(MAKE) -C ovmf-dir clean; \
 	fi
 
 .PHONY: seabios-dir-force-update
diff --git a/tools/firmware/hvmloader/Makefile b/tools/firmware/hvmloader/Makefile
index 8ab1429..e27e457 100644
--- a/tools/firmware/hvmloader/Makefile
+++ b/tools/firmware/hvmloader/Makefile
@@ -37,7 +37,7 @@ endif
 
 CIRRUSVGA_DEBUG ?= n
 
-OVMF_DIR := ../ovmf
+OVMF_DIR := ../ovmf-dir
 ROMBIOS_DIR := ../rombios
 SEABIOS_DIR := ../seabios-dir
 
-- 
1.7.10.4

[PATCH V3 4/5] tools: support system supplied ovmf binary

[Wei Liu]

From: Ian Campbell <ian.campbell@citrix.com>

Debian Jessie at least contains an ovmf package that includes
/usr/share/ovmf/OVMF.fd. It's also possible that user may want to supply
his/her own ovmf binary.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
 config/Tools.mk.in                |    1 +
 tools/configure                   |   16 +++++++++++++---
 tools/configure.ac                |   11 +++++++++++
 tools/firmware/Makefile           |    2 ++
 tools/firmware/hvmloader/Makefile |    6 +++++-
 5 files changed, 32 insertions(+), 4 deletions(-)

diff --git a/config/Tools.mk.in b/config/Tools.mk.in
index 67f5782..d9d3239 100644
--- a/config/Tools.mk.in
+++ b/config/Tools.mk.in
@@ -24,6 +24,7 @@ BCC                 := @BCC@
 IASL                := @IASL@
 FETCHER             := @FETCHER@
 SEABIOS_PATH        := @seabios_path@
+OVMF_PATH           := @ovmf_path@
 
 # Extra folder for libs/includes
 PREPEND_INCLUDES    := @PREPEND_INCLUDES@
diff --git a/tools/configure b/tools/configure
index 1da8652..22e74a7 100755
--- a/tools/configure
+++ b/tools/configure
@@ -682,6 +682,7 @@ APPEND_LIB
 APPEND_INCLUDES
 PREPEND_LIB
 PREPEND_INCLUDES
+ovmf_path
 seabios_path
 qemu_xen
 qemu_traditional
@@ -768,6 +769,7 @@ enable_blktap1
 enable_qemu_traditional
 with_system_qemu
 with_system_seabios
+with_system_ovmf
 '
       ac_precious_vars='build_alias
 host_alias
@@ -1440,6 +1442,9 @@ Optional Packages:
   --with-system-seabios[=PATH]
                           Use system supplied seabios PATH instead of building
                           and installing our own version
+  --with-system-ovmf[=PATH]
+                          Use system supplied OVMF PATH instead of building
+                          and installing our own version
 
 Some influential environment variables:
   CC          C compiler command
@@ -3771,9 +3776,14 @@ fi
 
 
 
-
-
-
+# Check whether --with-system-ovmf was given.
+if test "${with_system_ovmf+set}" = set; then :
+  withval=$with_system_ovmf;
+    case $withval in
+        no) ovmf_path= ;;
+        *)  ovmf_path=$withval ;;
+    esac
+fi
 
 
 for cppflag in $PREPEND_INCLUDES
diff --git a/tools/configure.ac b/tools/configure.ac
index 4f3c33a..b2941a4 100644
--- a/tools/configure.ac
+++ b/tools/configure.ac
@@ -108,6 +108,17 @@ AC_ARG_WITH([system-seabios],
 ],[])
 AC_SUBST(seabios_path)
 
+AC_ARG_WITH([system-ovmf],
+    AS_HELP_STRING([--with-system-ovmf@<:@=PATH@:>@],
+       [Use system supplied OVMF PATH instead of building and installing
+        our own version]),[
+    case $withval in
+        no) ovmf_path= ;;
+        *)  ovmf_path=$withval ;;
+    esac
+],[])
+AC_SUBST(ovmf_path)
+
 AC_ARG_VAR([PREPEND_INCLUDES],
     [List of include folders to prepend to CFLAGS (without -I)])
 AC_ARG_VAR([PREPEND_LIB],
diff --git a/tools/firmware/Makefile b/tools/firmware/Makefile
index 8633748..cb13212 100644
--- a/tools/firmware/Makefile
+++ b/tools/firmware/Makefile
@@ -6,7 +6,9 @@ TARGET      := hvmloader/hvmloader
 INST_DIR := $(DESTDIR)$(XENFIRMWAREDIR)
 
 SUBDIRS-y :=
+ifeq ($(OVMF_PATH),)
 SUBDIRS-$(CONFIG_OVMF) += ovmf-dir
+endif
 ifeq ($(SEABIOS_PATH),)
 SUBDIRS-$(CONFIG_SEABIOS) += seabios-dir
 endif
diff --git a/tools/firmware/hvmloader/Makefile b/tools/firmware/hvmloader/Makefile
index e27e457..00ee952 100644
--- a/tools/firmware/hvmloader/Makefile
+++ b/tools/firmware/hvmloader/Makefile
@@ -56,7 +56,11 @@ ROMS :=
 ifeq ($(CONFIG_OVMF),y)
 OBJS += ovmf.o
 CFLAGS += -DENABLE_OVMF
-OVMF_ROM := $(OVMF_DIR)/ovmf.bin
+ifeq ($(OVMF_PATH),)
+	OVMF_ROM := $(OVMF_DIR)/ovmf.bin
+else
+	OVMF_ROM := $(OVMF_PATH)
+endif
 ROMS += $(OVMF_ROM)
 endif
 
-- 
1.7.10.4

[PATCH V3 5/5] tools: Enable OVMF build by default

[Wei Liu]

From: Ian Campbell <ian.campbell@citrix.com>

The issues with non-GCC4.4 builds seem to have been resolved.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 tools/configure    |    4 ++--
 tools/configure.ac |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/tools/configure b/tools/configure
index 22e74a7..eb58bcd 100755
--- a/tools/configure
+++ b/tools/configure
@@ -1422,7 +1422,7 @@ Optional Features:
   --enable-xenapi         Enable Xen API Bindings (default is DISABLED)
   --disable-ocamltools    Disable Ocaml tools (default is ENABLED)
   --disable-xsmpolicy     Disable XSM policy compilation (default is ENABLED)
-  --enable-ovmf           Enable OVMF (default is DISABLED)
+  --disable-ovmf          Enable OVMF (default is ENABLED)
   --disable-rombios       Disable ROM BIOS (default is ENABLED)
   --disable-seabios       Disable SeaBIOS (default is ENABLED)
   --disable-debug         Disable debug build of tools (default is ENABLED)
@@ -3584,7 +3584,7 @@ elif test "x$enable_ovmf" = "xyes"; then :
 
 elif test -z $ax_cv_ovmf; then :
 
-    ax_cv_ovmf="n"
+    ax_cv_ovmf="y"
 
 fi
 ovmf=$ax_cv_ovmf
diff --git a/tools/configure.ac b/tools/configure.ac
index b2941a4..86fcb28 100644
--- a/tools/configure.ac
+++ b/tools/configure.ac
@@ -53,7 +53,7 @@ AX_ARG_DEFAULT_ENABLE([monitors], [Disable xenstat and xentop monitoring tools])
 AX_ARG_DEFAULT_DISABLE([xenapi], [Enable Xen API Bindings])
 AX_ARG_DEFAULT_ENABLE([ocamltools], [Disable Ocaml tools])
 AX_ARG_DEFAULT_ENABLE([xsmpolicy], [Disable XSM policy compilation])
-AX_ARG_DEFAULT_DISABLE([ovmf], [Enable OVMF])
+AX_ARG_DEFAULT_ENABLE([ovmf], [Enable OVMF])
 AX_ARG_DEFAULT_ENABLE([rombios], [Disable ROM BIOS])
 AX_ARG_DEFAULT_ENABLE([seabios], [Disable SeaBIOS])
 AX_ARG_DEFAULT_ENABLE([debug], [Disable debug build of tools])
-- 
1.7.10.4

Re: [PATCH V3 0/5] Reintroduce OVMF support

[Ian Campbell]

On Tue, 2013-10-29 at 11:39 +0000, Wei Liu wrote:
> OVMF (open virtual machine firmware) is used to provide UEFI support for
> virtual machines. It was first introduced about a year ago but was disabled due
> to compilation problem. Now that the compilation problem is resolved we can
> reintorduce it.
> 
> OVMF tree can be pulled from
>   git://xenbits.xen.org/people/liuw/ovmf.git for-xenbits
> 
> Wei.
> 
> Change from V2:
> * update Config.mk before enabling OVMF build
> 
> Ian Campbell (3):
>   tools: clone ovmf to ovmf-dir directory
>   tools: support system supplied ovmf binary

I have pushed these.

>   tools: Enable OVMF build by default

Wei told me that more work was needed to make OVMF usable, so on his
recommendation I have held off on this one.

> Wei Liu (2):
>   libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

This one was previously ruled out.

>   Config.mk: update OVMF changeset

I have applied this one.

Thanks Wei.

Ian