From: Wenchao Xia
These patches introduce libqblock API, make libqblock.la and make
check-libqblock could build this library.
Functionalities:
1 create a new image.
2 sync access of an image.
3 basic image information retrieving such as backing file.
4 detect if a sector is allocated in an
From: Wenchao Xia
In this example, first it will create some qcow2 images, then try get
information including backing file relationship, then it will do sync IO on
the image.
Signed-off-by: Wenchao Xia
---
tests/libqblock/libqblock-qcow2.c | 390 -
1 file
From: Wenchao Xia
Libqblock was placed in new directory ./libqblock, libtool will build
dynamic library there, source files of block layer remains in ./block.
So block related source code will generate 3 sets of binary, first is old
ones used in qemu, second and third are non PIC and PIC ones i
From: Wenchao Xia
This patch contains the major APIs in the library. For ABI some reserved
members were used.
Important APIs:
1 QBlockContext. This structure was used to retrieve errors, every thread
must create one first.
2 QBlockState. It stands for an block image object.
3 QBlockStatic
From: Wenchao Xia
This patch contains type and macro defines used in APIs, one file for public
usage, one for libqblock internal usage.
Signed-off-by: Wenchao Xia
---
libqblock/libqblock-internal.h | 75
libqblock/libqblock-types.h| 252 +++
On Fri, Oct 12, 2012 at 11:29:47AM +0200, Jan Kiszka wrote:
> On 2012-10-08 20:52, Anthony Liguori wrote:
> > Jan Kiszka writes:
> >
> >> On 2012-09-11 17:53, Jan Kiszka wrote:
> >>> Our one and only BIOS depends on a writable shadowed BIOS in the ISA
> >>> range. As we have no interface to contr
Reviewed-by: Anthony Liguori
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
scripts/qapi_visit.py | 157 +
1 file changed, 81 insertions(+), 76 deletions(-)
diff --git a/scripts/qapi_visit.py b/scripts/qapi_visit.py
index a360de7..f9
Signed-off-by: Michael Roth
---
qapi/qmp-output-visitor.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/qapi/qmp-output-visitor.c b/qapi/qmp-output-visitor.c
index 2bce9d5..83cf0dc 100644
--- a/qapi/qmp-output-visitor.c
+++ b/qapi/qmp-output-visitor.c
@@ -181,6 +181,
Reviewed-by: Anthony Liguori
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
module.h |2 ++
vl.c |1 +
2 files changed, 3 insertions(+)
diff --git a/module.h b/module.h
index c4ccd57..cb81aa2 100644
--- a/module.h
+++ b/module.h
@@ -25,6 +25,7 @@ typedef enum {
MOD
Reviewed-by: Anthony Liguori
Signed-off-by: Michael Roth
---
scripts/qapi_visit.py |9 +
1 file changed, 9 insertions(+)
diff --git a/scripts/qapi_visit.py b/scripts/qapi_visit.py
index 856df5e..c531a5a 100644
--- a/scripts/qapi_visit.py
+++ b/scripts/qapi_visit.py
@@ -145,6 +145,15
If we're given a pointer that has already be initialized to a non-NULL
value, don't attempt to allocate memory for the object as we'll likely
clobber something we weren't supposed to.
Also, fix up a check in the unit test that may fail as a result of this
change do to it not initializing the objec
Add support for arrays in the code generators.
Complex field descriptions can now be used to provide additional
information to the visitor generators, such as the max size of an array,
or the field within a struct to use to determine how many elements are
present in the array to avoid serializing
Generally these will be serialized into lists, but the
representation can be of any form so long as it can
be deserialized into a single-dimension C array.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
qapi/qapi-visit-core.c | 25 +
qapi/qapi-visit-core.h
visit_type_size() was added for use-cases currently only encountered by
OptsVisitor users, which implements a specific handler for
visit_type_size(). For Visitor implementations that don't implement the
handler, we fallback to using v->type_uint64().
However, some visitor implementations, such as
This allows OrderedDict() instances to be [pretty-]printed to
QAPI-compatible JSON structures with field ordering preserved. This is
useful for QIDL, which generates schemas programatically and exposes
them to users in various ways.
Signed-off-by: Michael Roth
---
scripts/ordereddict.py | 51 +
Python doesn't allow "-" in module names, so we need to rename the file
so we can re-use bits of the codegen
Reviewed-by: Anthony Liguori
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
Makefile |8
scripts/{qapi-visit.py => qapi_visit.py
Signed-off-by: Michael Roth
---
Makefile |2 +
configure |1 +
rules.mak | 25 ++-
tests/Makefile |8 +-
tests/test-qidl-included.h | 31
tests/test-qidl-linked.c | 93 +++
tests/test-qidl-linked.h
Python doesn't allow "-" in module names, so we need to rename the file
so we can re-use bits of the codegen.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
Makefile |8
scripts/{qapi-commands.py => qapi_commands.py} |0
tests/M
On 10/09/2012 11:56 PM, Jeff Cody wrote:
> Currently, bdrv_find_backing_image compares bs->backing_file with
> what is passed in as a backing_file name. Mismatches may occur,
> however, when bs->backing_file and backing_file are both not
> absolute or relative.
>
> Use path_combine() to make sure
This introduces the QIDL parser to process QIDL annotations in C files.
This code is mostly a straight import from qc.git, with some reworking
to handle the declaration/annotation format and lexer we're using for
QEMU.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
scripts/qidl_pars
It is used nowhere else, and the corresponding MAX_CODE_GEN_BUFFER_SIZE
also lives there.
Signed-off-by: Richard Henderson
---
exec-all.h | 2 --
exec.c | 4
2 files changed, 4 insertions(+), 2 deletions(-)
Dang it, I knew there was something else I was intending to include
in the patc
On Fri, Oct 05, 2012 at 10:24:30AM +0200, Paolo Bonzini wrote:
> Il 04/10/2012 19:33, Michael Roth ha scritto:
> > +
> > +%.qidl.c: %.c $(SRC_PATH)/qidl.h $(addprefix $(SRC_PATH)/scripts/,lexer.py
> > qidl.py qidl_parser.py qapi.py qapi_visit.py)
> > + $(call rm -f $(*D)/qidl-generated/$(*F).qid
Hi Valerio/Clemens,
in my case, Windows 7 alone runs great!
I face this issue after installing PointSec to encrypt the (emulated)
disk from the Windows 7 itself.
Playing with above suggested parameters:
1) "-cpu kvm64,+nx -no-kvm" the BSOD:
0x005D
(0x78BFBF9,0x0
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
docs/qidl.txt | 347 +
1 file changed, 347 insertions(+)
create mode 100644 docs/qidl.txt
diff --git a/docs/qidl.txt b/docs/qidl.txt
new file mode 100644
index 000..7d17cdc
-
Adds an abstract Lexer class to handle tokenizer via a
peek/pop/peekline/popline interface, along with an implementation for C
based on the lexer from qc.git
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
scripts/lexer.py | 306 ++
For ARM we cap the buffer size to 16MB. Do not allocate 32MB in that case.
Signed-off-by: Richard Henderson
---
exec.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/exec.c b/exec.c
index db735dd..386cc08 100644
--- a/exec.c
+++ b/exec.c
@@ -529,7 +529,11 @@ bool memor
We had a hack for arm and sparc, allocating code_gen_prologue to a
special section. Which, honestly does no good under certain cases.
We've already got limits on code_gen_buffer_size to ensure that all
TBs can use direct branches between themselves; reuse this limit to
ensure the prologue is also
It now consists of:
A macro definition of MAX_CODE_GEN_BUFFER_SIZE with host-specific values,
A function size_code_gen_buffer that applies most of the reasoning for
choosing a buffer size,
Three variations of a function alloc_code_gen_buffer that contain all
of the logic for allocating executabl
The hard-coded addresses inside alloc_code_gen_buffer only make sense
if we're building an executable that will actually run at the address
we've put into the linker scripts.
When we're building with -fpie, the executable will run at some
random location chosen by the kernel. We get better placem
This revision of the patch set takes Blue's suggestion to split up
code_gen_alloc into several pieces. It does seem to clean things
up a bit.
The first patch is cleanup, doing the split. The third patch does
in one line what I was trying to accomplish with the first revision
of this patch. The
Signed-off-by: Michael Roth
---
qidl.h | 105
1 file changed, 105 insertions(+)
create mode 100644 qidl.h
diff --git a/qidl.h b/qidl.h
new file mode 100644
index 000..b4c9b02
--- /dev/null
+++ b/qidl.h
@@ -0,0 +1,105 @@
+/*
This takes the declarations generated by the QIDL parser and converts
them to QAPI schemas to generate the visitor routines and other
supporting code for QIDL.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
scripts/qidl.py | 290 +
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
hw/qdev-properties.h | 151 ++
hw/qdev.h| 126 +
2 files changed, 152 insertions(+), 125 deletions(-)
create mode 100644 hw/qdev-prope
Signed-off-by: Michael Roth
---
docs/qapi-code-gen.txt | 251 +---
1 file changed, 237 insertions(+), 14 deletions(-)
diff --git a/docs/qapi-code-gen.txt b/docs/qapi-code-gen.txt
index cccb11e..d3ca74a 100644
--- a/docs/qapi-code-gen.txt
+++ b/docs/q
We currently hard-code property size at 4096 for the purposes of
getattr()/stat()/etc. For 'state' properties we can exceed this easily,
leading to truncated responses.
Instead, for a particular property, make it
max(4096, most_recent_property_size * 2). This allows some
head-room for properties t
Currently the QAPI JSON parser expects a very particular style of code
indentation, the major one being that terminating curly/square brackets are
not on placed on a seperate line. This is incompatible with most
pretty-print formats, so make it a little more robust by supporting
these cases.
Also
python-fuse defaults to multi-threaded handling of filesystem calls.
In the case of QOM this can lead to threads reading QMP responses to
requests executed by other threads, causing all sorts of strangeness
when interacting with QOM mounts. For instance:
mdroth@loki:~/w/qom$ ls -l machine | grep
Reviewed-by: Anthony Liguori
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
qapi/Makefile.objs |1 +
qapi/misc-qapi-visit.c | 14 ++
qapi/qapi-visit-core.h |3 +++
3 files changed, 18 insertions(+)
create mode 100644 qapi/misc-qapi-visit.c
diff --git a/qa
qidl embeds visitor code into object files rather than linking against
seperate files, so allow for static declarations when we're using
qapi_visit.py as a library as we do with qidl.py
Reviewed-by: Anthony Liguori
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
scripts/qapi_visit.p
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
qapi/qmp-input-visitor.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/qapi/qmp-input-visitor.c b/qapi/qmp-input-visitor.c
index 107d8d3..635106e 100644
--- a/qapi/qmp-input-visitor.c
+++ b/qapi/qm
Python doesn't allow "-" in module names, so we need to rename the file
so we can re-use bits of the codegen
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael Roth
---
Makefile |8
scripts/{qapi-types.py => qapi_types.py} |0
tests/Makefile
These patches are based are origin/master, and can also be obtained from:
git://github.com/mdroth/qemu.git qidl-base-v4
Changes since v3:
- Added documentation for array_capacity/array_size/embedded QAPI
directives and improved existing docs. (Paolo)
> qapi: Improve existing docs and do
Am 12.10.2012 19:59, schrieb Peter Maydell:
> Commit 4be403c accidentally defined the target_phys_addr_t type when
> building user-mode emulators. Since the type doesn't really make
> any sense except for system emulators, avoid defining it when building
> in user mode.
>
> Signed-off-by: Peter Ma
On 10/12/2012 11:24 AM, riku.voi...@linaro.org wrote:
> From: Riku Voipio
>
> Currently linux-user handles system calls with a 3000+ line switch/case
> construct
> in do_syscall(). Some syscalls are implemented inline in the switch/case,
> others
> as separate functions, and the rest as mix of
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as kvm festures or Hypervisor vendor-neutral interface
identification.
This is the EAX value for 0x4001.
QEMU knows this is KVM_CPUID_FEATURES (0x4001) in some builds.
This is based on:
Microsoft Hypervisor CPUID Leaves:
Part of "target-i386: Add way to expose VMWare CPUID"
Also adds some other known names (kvm, hyperv) to Hypervisor vendor.
This allows "hypervisor-vendor=vmware3" instead of
"hypervisor-vendor=VMwareVMware,hypervisor-level=2,hypervisor-features=0".
And "hypervisor-vendor=vmware" instead of
"hype
Part of "target-i386: Add way to expose VMWare CPUID"
At this stage it is used to set the cpu object's hypervisor features
to the default for Microsoft's Hypervisor ("Hv#1").
Also known as kvm festures or Hypervisor vendor-neutral interface
identification.
This is the EAX value for 0x4001.
On 10/12/2012 02:19 PM, Kashyap Chamarthy wrote:
>
> From eb4c4bc92c035c42c23c30c5e7ee73b54f9cf3a8 Mon Sep 17 00:00:00 2001
> From: Kashyap Chamarthy
> Date: Sat, 13 Oct 2012 01:30:37 +0530
> Subject: [PATCH] Add documentation for 'qemu-img info --backing-chain'
>
> Signed-off-by: Kashyap Chama
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization level or maximim cpuid function present in
this leaf.
This is the EAX value for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http:/
On Sat, Oct 13, 2012 at 12:46 AM, Kashyap Chamarthy
wrote:
> On Fri, Oct 12, 2012 at 7:39 PM, Stefan Hajnoczi wrote:
>> The qemu-img info --backing-chain option enumerates the backing file
>> chain. For example, for base.qcow2 <- snap1.qcow2 <- snap2.qcow2 the
>> output becomes:
>>
>> $ qemu-i
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization vendor.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization vendor.
This is EBX, ECX, and EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
If hypervisor vendor is set then add kvm's
signature at KVM_CPUID_SIGNATURE_NEXT (0x4100).
Signe
Part of "target-i386: Add way to expose VMWare CPUID"
This is EAX and EBX data for 0x4010.
Add new #define CPUID_HV_TIMING_INFO for this.
The best documentation I have found is:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/22643
And a test under ESXi 4.0 shows that VMware is s
Part of "target-i386: Add way to expose VMWare CPUID"
QEMU knows this as KVM_CPUID_FEATURES (0x4001) in some builds.
If hypervisor features are set, then pass adjusted
cpuid_kvm_features as EAX in 0x4101.
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/
Part of "target-i386: Add way to expose VMWare CPUID"
This is EAX and EBX data for 0x4010.
Add new #define CPUID_HV_TIMING_INFO for this.
The best documentation I have found is:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/22643
And a test under ESXi 4.0 shows that VMware is s
Part of "target-i386: Add way to expose VMWare CPUID"
At this stage it is used to set the cpu object's hypervisor vendor
to the default for Microsoft's Hypervisor ("Microsoft Hv").
Also known as Paravirtualization vendor.
This is EBX, ECX, EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SI
Part of "target-i386: Add way to expose VMWare CPUID"
At this stage it is used to set the cpu object's hypervisor level to
the default for Microsoft's Hypervisor.
Also known as Paravirtualization level or maximim cpuid function
present in this leaf. This is the EAX value for 0x4000.
This is
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as kvm festures or Hypervisor vendor-neutral interface
identification.
This is just the EAX value for 0x4001.
QEMU knows this is KVM_CPUID_FEATURES (0x4001) in some builds.
When exposing VMWare CPUID this needs to be set t
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization level.
QEMU knows this as KVM_CPUID_SIGNATURE (0x4000) in kvm on linux.
This does not provide vendor support in tcg yet.
>From http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html
kvm has this
Part of "target-i386: Add way to expose VMWare CPUID"
These are modeled after x86_cpuid_set_vendor and x86_cpuid_get_vendor.
Since kvm's vendor is shorter, the test for correct size is removed and zero
padding is added.
See http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html for
d
Part of "target-i386: Add way to expose VMWare CPUID"
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 29 +
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/t
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization level.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
Signed-off-by: Don Slutz
---
target-i386/kvm.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/target-i386/kvm.c b/
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization vendor.
This is EBX, ECX, and EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/wind
Also known as Paravirtualization CPUIDs.
This is primarily done so that the guest will think it is running
under vmware when hypervisor-vendor=vmware is specified as a
property of a cpu.
Patches 1 to 3 define new cpu properties.
Patches 4 to 6 Add QOM access to the new properties.
Patches 7 to 9
This was part of [PATCH v6 00/16] Allow changing of Hypervisor CPUIDs.
Since it is no longer in use by any of the patches in v7, I have split it off.
Don Slutz (1):
target-i386: Add missing kvm bits.
target-i386/cpu.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
Currently "-cpu host,-kvmclock,-kvm_nopiodelay,-kvm_mmu" does not
turn off all bits in CPUID 0x4001 EAX.
The missing ones are KVM_FEATURE_STEAL_TIME and
KVM_FEATURE_CLOCKSOURCE_STABLE_BIT.
This adds the names kvm_steal_time and kvm_clock_stable for these
bits.
Signed-off-by: Don Slutz
---
Stefan Hajnoczi writes:
> The following changes since commit b4ae3cfa57b8c1bdbbd7b7d420971e9171203ade:
>
> ssi: Add slave autoconnect helper (2012-10-10 11:13:32 +1000)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git trivial-patches
Pulled. Thanks.
Regards
Peter Maydell writes:
> Hi; this is a pullreq for the arm-devs queue. Contains my fix for
> the various DS1338 bugs plus some other minor patches from various
> people; please pull.
Pulled. Thanks.
Regards,
Anthony Liguori
>
> thanks
> -- PMM
>
> The following changes since commit b4ae3cfa57b
On Fri, Oct 12, 2012 at 7:39 PM, Stefan Hajnoczi wrote:
> The qemu-img info --backing-chain option enumerates the backing file
> chain. For example, for base.qcow2 <- snap1.qcow2 <- snap2.qcow2 the
> output becomes:
>
> $ qemu-img info --backing-chain snap2.qcow2
> image: snap2.qcow2
> file
One more follow up. Using the standard startup.c with just a while(1)
{} loop yields the same problem.
Has anyone got a regression test for the -M lm3s811evb that I can run?
I might be able to see what's different with the TI code that is causing
the SIGUSR1.
Oliver
--
You received this bug n
To follow up, I think this bug might be a problem with the stellaris
branch of the code. I compiled the very simple gpio_led example, and
this crashes with the SIGUSR1 as well.
Oliver
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
This was part of [PATCH v6 00/16] Allow changing of Hypervisor CPUIDs.
Since it is no longer in use by any of the patches in v7, I have split it off.
Don Slutz (1):
target-i386: Add missing kvm bits.
target-i386/cpu.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
From: Riku Voipio
In preparations for for refactoring the main switch/case out
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 92 ++
1 file changed, 48 insertions(+), 44 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscal
From: Riku Voipio
Currently linux-user handles system calls with a 3000+ line switch/case
construct
in do_syscall(). Some syscalls are implemented inline in the switch/case, others
as separate functions, and the rest as mix of both.
As the first step of the cleanup, I'd like to move implementat
From: Riku Voipio
In preparations for for refactoring the main switch/case out
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 32 ++--
1 file changed, 18 insertions(+), 14 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index a9bfe8c.
From: Riku Voipio
In preparations for for refactoring the main switch/case out
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index eebf219..61030f2 100
From: Riku Voipio
In preparations for for refactoring the main switch/case out
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 0b077e7..497cae5
From: Riku Voipio
In preparations for for refactoring the main switch/case out
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 497cae5..a9bfe8c 100644
--
Commit 33ebc29 fixed the bugs in the implementation of VQRSHL,
but forgot to remove the FIXME comment...
Signed-off-by: Peter Maydell
---
target-arm/neon_helper.c |1 -
1 file changed, 1 deletion(-)
diff --git a/target-arm/neon_helper.c b/target-arm/neon_helper.c
index 8bb5129..9aa920d 1006
On 10/12/2012 02:32 AM, Michael Tokarev wrote:
On 12.10.2012 10:49, Mike Lovell wrote:
/* request a tap device, disable PI, and add vnet header support if
- * requested and it's available. */
-prep_ifreq(&ifr, "tap%d");
+ * requested and it's available. use ifname if provided f
Commit 4be403c accidentally defined the target_phys_addr_t type when
building user-mode emulators. Since the type doesn't really make
any sense except for system emulators, avoid defining it when building
in user mode.
Signed-off-by: Peter Maydell
---
cf brief discussion earlier:
http://lists.gnu
Juan Quintela writes:
> Is the only way of knowing the RAM size.
>
> Signed-off-by: Juan Quintela
>
> Reviewed-by: Paolo Bonzini
> ---
> cpu-all.h | 2 ++
> exec.c| 2 +-
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/cpu-all.h b/cpu-all.h
> index 74d3681..5408782 10064
Public bug reported:
I've noticed a significant network performance regression when using
vde_switch, starting about one week ago (10/05/2012); before that date,
I used to get about 1.5 Gbits host to guest, but now I can only get
about 320 Mbits; I didn't find any modification in net/vde.*, just i
Il 12/10/2012 18:54, Paolo Bonzini ha scritto:
> Il 12/10/2012 14:39, Gerd Hoffmann ha scritto:
>> +chr = qemu_chr_new_from_opts(opts, NULL);
>> +if (chr == NULL) {
>> +qemu_opts_del(opts);
>> +error_setg(&err, "Creating chardev failed\n");
>> +goto exit_err;
>> +
On 26 September 2012 19:48, Peter Maydell wrote:
> These patches implement movcond_i32 for the ARM TCG backend; we
> emit "mov dst, v2; cmp c1, c2; movcc dst, v1". We could have
> done this with a pair of conditional movs, but (a) this is not
> actually any shorter (b) it means we don't get the co
Il 12/10/2012 14:31, Kevin Wolf ha scritto:
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/041 | 78
>
> tests/qemu-iotests/041.out | 15
> tests/qemu-iotests/group |1 +
> 3 files changed, 94 insertions(+), 0 deletions(
Il 12/10/2012 14:31, Kevin Wolf ha scritto:
> Signed-off-by: Kevin Wolf
> ---
> qemu-img.c | 23 +++
> 1 files changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index f17f187..849eb41 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -674,
Il 12/10/2012 18:26, Richard Henderson ha scritto:
> Older glibc (RHEL 5.x, Debian 5.x) does not have the _sigev_un._tid
> member in its structure definition, while the accompanying kernel
> headers do define SIGEV_THREAD_ID. We need configure to check for
> both before using it.
>
> Cc: Paolo Bo
Il 12/10/2012 14:39, Gerd Hoffmann ha scritto:
> +chr = qemu_chr_new_from_opts(opts, NULL);
> +if (chr == NULL) {
> +qemu_opts_del(opts);
> +error_setg(&err, "Creating chardev failed\n");
> +goto exit_err;
> +}
> +return 0;
> +
Since you have to do a v3, ple
Older glibc (RHEL 5.x, Debian 5.x) does not have the _sigev_un._tid
member in its structure definition, while the accompanying kernel
headers do define SIGEV_THREAD_ID. We need configure to check for
both before using it.
Cc: Paolo Bonzini
Cc: Anthony Liguori
Signed-off-by: Richard Henderson
-
Gerd Hoffmann writes:
> Hi,
>
> Here comes the spice patch queue. It raises the minimal required
> spice-server version to 0.12 and the qxl device revision to 4.
> It also brings a collection of bugfixes.
>
> please pull,
> Gerd
>
Pulled. Thanks.
Regards,
Anthony Liguori
> The following
Stefan Hajnoczi writes:
> The following changes since commit 4bb26682f70a5f626cad3e0ac82bf4b6252ea7a4:
>
> Merge branch 'master' of git.qemu.org:/pub/git/qemu (2012-10-07 18:42:18
> +)
>
> are available in the git repository at:
>
>
> git://github.com/stefanha/qemu.git net
>
> for you to
Alex Williamson writes:
> Anthony,
>
> The following changes since commit 4bb26682f70a5f626cad3e0ac82bf4b6252ea7a4:
>
> Merge branch 'master' of git.qemu.org:/pub/git/qemu (2012-10-07 18:42:18
> +)
>
> are available in the git repository at:
>
>
> git://github.com/awilliam/qemu-vfio.git
Gerd Hoffmann writes:
> Hi,
>
> Pretty small this time with just a few bugfixes.
>
> please pull,
> Gerd
>
Pulled. Thanks.
Regards,
Anthony Liguori
> The following changes since commit b4ae3cfa57b8c1bdbbd7b7d420971e9171203ade:
>
> ssi: Add slave autoconnect helper (2012-10-10 11:13:32 +
Jan Kiszka writes:
> On 2012-10-12 15:41, Anthony Liguori wrote:
>> Jan Kiszka writes:
>>
>>> On 2012-10-08 20:52, Anthony Liguori wrote:
Jan Kiszka writes:
> On 2012-09-11 17:53, Jan Kiszka wrote:
>> Our one and only BIOS depends on a writable shadowed BIOS in the ISA
>>
On Fri, Oct 12, 2012 at 12:06:44PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> >>> I just tried out getting rid of the bridges by default.
> >>
> >> That clearly raises the question which devices should be created
> >> automatically by -M q35. I think the devices which are part of the ich9
> >> chips
On 2012-10-12 15:41, Anthony Liguori wrote:
> Jan Kiszka writes:
>
>> On 2012-10-08 20:52, Anthony Liguori wrote:
>>> Jan Kiszka writes:
>>>
On 2012-09-11 17:53, Jan Kiszka wrote:
> Our one and only BIOS depends on a writable shadowed BIOS in the ISA
> range. As we have no interface
Am 12.06.2012 15:44, schrieb Kevin Wolf:
> Am 12.06.2012 15:33, schrieb Andreas Färber:
>> Am 14.05.2012 14:20, schrieb Kevin Wolf:
>>> Am 13.05.2012 10:03, schrieb Zhouyi Zhou:
hi all
sometimes, qemu/kvm-0.1x will hang in endless loop in
qcow2_alloc_cluster_offset.
On Thu, Oct 11, 2012 at 10:40:04PM +0200, Michael S. Tsirkin wrote:
> > Windows and Linux guests seem fine with either layout. Slots 1-2 are
> > specific to my setup. So this is a pretty minimal set.
>
> I guess we can remove the PCI bridge too?
>
maybe. Perhaps, we can have a very basic set of
The qemu-img info --backing-chain option enumerates the backing file
chain. For example, for base.qcow2 <- snap1.qcow2 <- snap2.qcow2 the
output becomes:
$ qemu-img info --backing-chain snap2.qcow2
image: snap2.qcow2
file format: qcow2
virtual size: 100M (104857600 bytes)
disk size: 196
1 - 100 of 183 matches
Mail list logo
