qemu side patch to support xen HVM direct kernel boot:
if -kernel exists, calls xen_load_linux(), which will read kernel/initrd
and add a linuxboot.bin or multiboot.bin option rom. The
linuxboot.bin/multiboot.bin will load kernel/initrd and jump to execute
kernel directly. It's working when xen use
xen side patch to support xen HVM direct kernel boot:
support 'kernel', 'ramdisk', 'cmdline' (and 'root', 'extra' as well
which would be deprecated later) in HVM config file, parse config file,
pass -kernel, -initrd, -append parameters to qemu.
It's working with qemu-xen when using the default BIO
Updated current patch series for working with qemu-xen and default
BIOS (seabios), to make it in good shape. Stubdom support will be
continued.
xen side patch: pass kernel/initrd/append parameters to qemu-dm
qemu side patch: reuse load_linux() for xen hvm direct kernel boot.
Different from p
Hi,
> -if (depth == 32 || ((depth == 16 || depth == 15) && !byteswap)) {
> + if (depth == 32 || depth == 24 ||
> + ((depth == 16 || depth == 15) && !byteswap)) {
Doesn't apply. depth == 15 isn't upstream. Guess you have some more
local changes? Also the whitespace looks
On Thu, Jun 26, 2014 at 11:01:32PM +0200, Damjan Marion wrote:
> Old code was affected by memory gaps which resulted in buffer pointers
> pointing to address outside of the mapped regions.
>
> Here we are introducing following changes:
> - new function qemu_get_ram_block_host_ptr() returns host p
On Mon, Jun 30, 2014 at 05:40:16PM -0600, Eric Blake wrote:
> On 06/30/2014 05:16 PM, Eric Blake wrote:
> > I'm trying to track down a core dump with the QMP drive-mirror command.
>
> Looks like the bug is related to a base image that is not a multiple of
> a cluster size.
>
> >
> > # in one ter
On Mon, Jun 30, 2014 at 07:03:37PM +0100, Peter Maydell wrote:
> Commit 25814e8987 introduced an error-exit code path which does
> a "goto exit" before the cow_bs variable is initialized, meaning
> we would call bdrv_unref() on an uninitialized variable and
> likely segfault. Fix this by moving the
On Mon, Jun 30, 2014 at 05:05:41PM +0200, Benoît Canet wrote:
> fe069d9d had aligned code and documentation while dropping the s from the
> actual JSON output. Fix that.
>
> This also fix test/qemu-iotest/081 since the missing s was causing a
> permutation.
>
> Signed-off-by: Benoit Canet
> ---
On Mon, Jun 30, 2014 at 04:25:47PM +0200, Benoît Canet wrote:
> The Monday 30 Jun 2014 à 16:09:57 (+0200), Stefan Hajnoczi wrote :
> > On Fri, Jun 27, 2014 at 10:17:16PM +0200, Benoît Canet wrote:
> > I think this patch can be boiled down to 2 lines:
> >
> > if __name__ == '__main__':
> > +if
The existing test whether "-lm" needs to be included or not is
insufficient as it reports false negative on Fedora20/ppc64.
This happens because sin(0.0) is a constant value which compiler
can safely throw away and therefore there is no need to add "-lm".
As the result, qemu-nbd/qemu-io/qemu-img to
On Mon, Jun 30, 2014 at 01:33:39PM +0200, Kevin Wolf wrote:
> Am 07.06.2014 um 20:51 hat Max Reitz geschrieben:
> > bdrv_make_empty() is currently only called if the current image
> > represents an external snapshot that has been committed to its base
> > image; it is therefore unlikely to have int
Hi Le,
On 2014-07-01 04:34, Le Tan wrote:
> Hi Jan,
> I use pci_setup_iommu() to setup a PCIIOMMUFunc for the q35 pci bus.
> In the iommu_fn, I print out the devfn parameter and find out that it
> sometimes will be -1. So what does it mean?
> The detail code is here:
>
> In mch_init() function, I
Il 01/07/2014 09:30, Alexey Kardashevskiy ha scritto:
The existing test whether "-lm" needs to be included or not is
insufficient as it reports false negative on Fedora20/ppc64.
This happens because sin(0.0) is a constant value which compiler
can safely throw away and therefore there is no need t
On 07/01/2014 05:41 PM, Paolo Bonzini wrote:
> Il 01/07/2014 09:30, Alexey Kardashevskiy ha scritto:
>> The existing test whether "-lm" needs to be included or not is
>> insufficient as it reports false negative on Fedora20/ppc64.
>> This happens because sin(0.0) is a constant value which compiler
On 30/06/2014 15:59, Sebastian Tanase wrote:
Show in 'info jit' the current delay between the host clock
and the guest clock. In addition, print the maximum advance
and delay of the guest compared to the host.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
---
cpu-exec.c
From: Jeff Cody
This allows a user to make a live change to the backing file recorded in
an open image.
The image file to modify can be specified 2 ways:
1) image filename
2) image node-name
Note: this does not cause the backing file itself to be reopened; it
merely changes the backing filenam
Hi,
The commit 580b6b2aa2(dataplane: use the QEMU block layer for I/O)
introduces ~40% throughput regression on virtio-blk dataplane, and
one of causes is that submitting I/O at batch is removed.
This patchset trys to introduce this mechanism on block, at least,
linux-aio can benefit from that.
This patch introduces these two APIs so that following
patches can support queuing I/O requests and submitting them
at batch for improving I/O performance.
Reviewed-by: Paolo Bonzini
Signed-off-by: Ming Lei
---
block.c | 21 +
include/block/block.h |
This patch implements .bdrv_io_plug and .bdrv_io_unplug
callbacks for linux-aio Block Drivers, so that submitting
I/O at batch can be supported on linux-aio.
Signed-off-by: Ming Lei
---
block/linux-aio.c | 86 +++--
block/raw-aio.h |2 ++
b
Before commit 580b6b2aa2(dataplane: use the Qemu block
layer for I/O), dataplane for virtio-blk submits block
I/O at batch.
This commit 580b6b2aa2 replaces the custom linux AIO
implementation(including I/O batch) with Qemu block
layer, but this commit causes ~40% throughput regression
on virtio-bl
Il 01/07/2014 09:47, Alexey Kardashevskiy ha scritto:
On 07/01/2014 05:41 PM, Paolo Bonzini wrote:
Il 01/07/2014 09:30, Alexey Kardashevskiy ha scritto:
The existing test whether "-lm" needs to be included or not is
insufficient as it reports false negative on Fedora20/ppc64.
This happens becau
Hi,
Qemu compiles failed.
./configure --enable-debug --target-list=x86_64-softmmu
make -j
net/l2tpv3.c: In function ‘net_l2tpv3_process_queue’:
net/l2tpv3.c:368: error: invalid use of undefined type ‘struct mmsghdr’
net/l2tpv3.c:369: error: dereferencing pointer to incomplete type
net/l2tpv3.c:
Am 30.06.2014 um 16:09 hat Stefan Hajnoczi geschrieben:
> On Fri, Jun 27, 2014 at 10:17:16PM +0200, Benoît Canet wrote:
> I think this patch can be boiled down to 2 lines:
>
> if __name__ == '__main__':
> +if 'quorum' not in iotests.qemu_img('--help'):
> +iotests.notrun('not built wit
On Mon, Jun 30, 2014 at 06:09:02PM -0500, greg.bell...@linaro.org wrote:
> From: Fabian Aggeler
>
> Define a new ARM CP register info list for the ARMv7 Security Extension
> feature. Register that list only for ARM cores with Security Extension/EL3
> support. Moving Aarch32 SCR into Security Exte
Il 01/07/2014 10:00, ChenLiang ha scritto:
./configure --enable-debug --target-list=x86_64-softmmu
make -j
net/l2tpv3.c: In function ‘net_l2tpv3_process_queue’:
net/l2tpv3.c:368: error: invalid use of undefined type ‘struct mmsghdr’
net/l2tpv3.c:369: error: dereferencing pointer to incomplete t
On Mon, Jun 30, 2014 at 06:09:04PM -0500, greg.bell...@linaro.org wrote:
> From: Fabian Aggeler
>
> arm_is_secure() function allows to determine CPU security state
> if the CPU implements Security Extensions/EL3.
> arm_is_secure_below_el3() returns true if CPU is in secure state
> below EL3.
>
>
On 1 July 2014 07:52, Paolo Bonzini wrote:
> Il 01/07/2014 07:42, Alexey Kardashevskiy ha scritto:
>
>> This is wrong actually. The problem here that compiler knows how to
>> optimize constants. sin(0.0) is the one while log(0.0) is not (it is
>> supposed to throw error or something as it the resu
On Mon, Jun 30, 2014 at 06:09:07PM -0500, greg.bell...@linaro.org wrote:
> From: Sergey Fedorov
>
> This patch is based on idea found in patch at
> git://github.com/jowinter/qemu-trustzone.git
> f3d955c6c0ed8c46bc0eb10b634201032a651dd2 by
> Johannes Winter .
>
> This flag prevents QEMU from exec
Am 01.07.2014 um 09:52 hat Stefan Hajnoczi geschrieben:
> From: Jeff Cody
>
> This allows a user to make a live change to the backing file recorded in
> an open image.
>
> The image file to modify can be specified 2 ways:
>
> 1) image filename
> 2) image node-name
>
> Note: this does not cause
On Mo, 2014-06-30 at 22:32 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2014-06-30 at 13:14 +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > From what I can tell, we only ever call the cursor drawing callback on
> > > non-shared surfaces. Should I deduce that the HW cursor emulation simply
> > >
The following changes since commit ec9fe956d5c728da770db5ec9bc429080ccb5043:
Merge remote-tracking branch 'remotes/bonzini/small-fixes' into staging
(2014-06-30 15:56:00 +0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to fetch changes up
From: Alexey Kardashevskiy
The existing test whether "-lm" needs to be included or not is
insufficient as it reports false negative on Fedora20/ppc64.
This happens because sin(0.0) is a constant value which compiler
can safely throw away and therefore there is no need to add "-lm".
As the result,
From: Cédric Le Goater
Virtio SCSI Events need to be byteswapped before being pushed
when host and guest have a different endianness. Not doing so
breaks hotplug of virtio scsi disks, with the following error
message being printed in the guest console:
virtio_scsi: Unsupport virtio scsi event 10
On Tue, Jul 1, 2014 at 10:17 AM, Paolo Bonzini wrote:
> Il 01/07/2014 10:00, ChenLiang ha scritto:
>
>> ./configure --enable-debug --target-list=x86_64-softmmu
>> make -j
>>
>> net/l2tpv3.c: In function ‘net_l2tpv3_process_queue’:
>> net/l2tpv3.c:368: error: invalid use of undefined type ‘struct
From: Greg Kurz
Hotplug of a virtio scsi disk is currently broken: no disk appears in the
guest (verified with a fedora 20 host running a fedora 20 guest with KVM).
Bisect leeds to Paolo's patches to support any_layout, especially this
commit:
commit 36b15c79aa1bef5fe7543f9f2629b6413720bbfb
Auth
On Tue, Jul 01, 2014 at 04:00:52PM +0800, ChenLiang wrote:
> Qemu compiles failed.
What is your kernel version?
I guess you're running an old kernel without recvmmsg(). So the kernel
headers are missing the mmsghdr struct.
If you would like to contribute a patch to fix this, please introduce a
On Mon, Jun 30, 2014 at 06:09:09PM -0500, greg.bell...@linaro.org wrote:
> From: Fabian Aggeler
>
> This patch extends arm_excp_unmasked() according to ARM ARMv7 and
> ARM ARMv8 (all EL running in Aarch32) and adds comments.
>
> Signed-off-by: Fabian Aggeler
> Signed-off-by: Greg Bellows
> ---
Il 01/07/2014 10:19, Peter Maydell ha scritto:
> I think something like "double x; int f(void) {return isnan(sin(x));}"
> should be bullet proof.
This is a compile_prog test, though -- the compiler could spot
that x and f are both unused, since it has the entire program
in hand. My suggestion wo
On 1 July 2014 09:22, Paolo Bonzini wrote:
> From: Alexey Kardashevskiy
>
> The existing test whether "-lm" needs to be included or not is
> insufficient as it reports false negative on Fedora20/ppc64.
> This happens because sin(0.0) is a constant value which compiler
> can safely throw away and
On 2014/7/1 16:17, Paolo Bonzini wrote:
> Il 01/07/2014 10:00, ChenLiang ha scritto:
>> ./configure --enable-debug --target-list=x86_64-softmmu
>> make -j
>>
>> net/l2tpv3.c: In function ‘net_l2tpv3_process_queue’:
>> net/l2tpv3.c:368: error: invalid use of undefined type ‘struct mmsghdr’
>> net/
Il 01/07/2014 10:26, Alexander Graf ha scritto:
Right. A quick fix would be to add a flag to force always using a shadow
surface and set it in cirrus ... I'm not sure anybody will notice the
performance difference.
I suspect we can rip out hw cursor emulation and nobody will notice the
differe
From: Stefan Hajnoczi
Sometimes an object needs to present a property which is actually on
another object, or it needs to provide an alias name for an existing
property.
Examples:
a.foo -> b.foo
a.old_name -> a.new_name
The new object_property_add_alias() API allows objects to alias a
prope
The following changes since commit 53a259da5697ec8a82463161e2e32ff942a08bc2:
Merge remote-tracking branch
'remotes/awilliam/tags/vfio-pci-for-qemu-20140630.0' into staging (2014-06-30
18:31:07 +0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git memory
for you
From: Marcelo Tosatti
Add a link to rtc under /machine providing a stable
location for management apps to query the value of the
time. The link should be added by any object that sends
RTC_TIME_CHANGE events.
{"execute":"qom-get","arguments":{"path":"/machine","property":"rtc-time"} }
Suggeste
This will be added (after QOMification) as the QOM parent.
Reviewed-by: Peter Crosthwaite
Signed-off-by: Paolo Bonzini
---
memory.c | 2 +-
vl.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/memory.c b/memory.c
index b91a60a..7eaa1e9 100644
--- a/memory.c
+++ b/mem
Child properties must be unique. Fix this problem by
turning their aliases into links.
The resolve function that forwards to the target property
does not have any knowledge of the target property's type,
so it works fine.
Reviewed-by: Peter Crosthwaite
Signed-off-by: Paolo Bonzini
---
qom/obj
From: Peter Crosthwaite
Certain parts of the QOM framework test this pointer to determine if
an object is parented. Nuke it when the object is unparented to allow
for reuse of an object after unparenting.
Signed-off-by: Peter Crosthwaite
Signed-off-by: Paolo Bonzini
---
qom/object.c | 1 +
1
The two are now the same.
Reviewed-by: Peter Crosthwaite
Signed-off-by: Paolo Bonzini
---
include/exec/memory.h | 1 -
memory.c | 35 +--
2 files changed, 25 insertions(+), 11 deletions(-)
diff --git a/include/exec/memory.h b/include/exec/memory.h
It may be desirable to have custom link<> properties that do more
than just store an object. Even the addition of a "check"
function is not enough if setting the link has side effects
or if a non-standard reference counting is preferrable.
Avoid the assumption that the opaque field of a link<> is
libqtest is using g_strdup_printf to format QMP commands, but
this does not work if the argument strings need to be escaped.
Instead, use the fancy %-formatting functionality of QObject.
The only change required in tests is that strings have to be
formatted as %s, not '%s' or \"%s\". Luckily this
There is no need to have them visible under /machine.
Signed-off-by: Paolo Bonzini
---
exec.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/exec.c b/exec.c
index df4a080..5a2a25e 100644
--- a/exec.c
+++ b/exec.c
@@ -1801,13 +1801,13 @@ MemoryRegion *iotlb_to_region(
From: Peter Crosthwaite
To allow devices to dynamically resize the device. The motivation is
to allow devices with variable size to init their memory_region
without size early and then correctly populate size at realize() time.
Signed-off-by: Peter Crosthwaite
Signed-off-by: Paolo Bonzini
---
When a device is unparented (i.e. made completely hidden from management)
we want to send a DEVICE_DELETED event only if the device actually was
realized. This avoids raising DEVICE_DELETED events when device_add
fails.
However, this does not work right for recursively-deleted
devices: the whole
Public bug reported:
In case of multiple errors, it leads to a crash.
Typical back trace:
#0 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 in __GI_abort () at abort.c:90
#2 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry= "*** Error in `%s': %
On Tue, Jul 1, 2014 at 10:10 AM, Kevin Wolf wrote:
> Am 30.06.2014 um 16:09 hat Stefan Hajnoczi geschrieben:
>> On Fri, Jun 27, 2014 at 10:17:16PM +0200, Benoît Canet wrote:
>> I think this patch can be boiled down to 2 lines:
>>
>> if __name__ == '__main__':
>> +if 'quorum' not in iotests.qe
The following changes since commit 53a259da5697ec8a82463161e2e32ff942a08bc2:
Merge remote-tracking branch
'remotes/awilliam/tags/vfio-pci-for-qemu-20140630.0' into staging (2014-06-30
18:31:07 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/block-pul
It becomes unwiedly to duplicate all virtio-blk qdev property
definitions due to an #ifdef. The C preprocessor syntax makes it a
little hard to resolve this cleanly but we can extract the #ifdef and
call a macro it defines later.
Avoiding duplication is important since it will only get worse when
object_initialize() leaves the object with a refcount of 1.
object_property_add_child() adds its own reference which is dropped
again when the property is deleted.
The upshot of this is that we always have a refcount >= 1. Upon hot
unplug the virtio-blk child is not finalized!
Drop our reference
Move the x-data-plane property. Originally it was outside since not
every transport may wish to support dataplane. But that makes little
sense when we have a dedicated CONFIG_VIRTIO_BLK_DATA_PLANE ifdef
already.
This move makes it easier to switch to property aliases in the next
patch.
Signed-o
The qdev_alias_all_properties() function creates QOM alias properties
for each qdev property on a DeviceState. This is useful for parent
objects that wish to forward property accesses to their children.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Peter Crosthwaite
---
hw/core/qdev.c
Sometimes an object needs to present a property which is actually on
another object, or it needs to provide an alias name for an existing
property.
Examples:
a.foo -> b.foo
a.old_name -> a.new_name
The new object_property_add_alias() API allows objects to alias a
property on the same object o
The x-data-plane=on|off option is no longer useful because the
iothread= option conveys the same information plus which
IOThread to use.
Do not delete x-data-plane=on|off yet as a convenience to people using
this legacy experimental option. We will drop it in QEMU 2.2.
Instead, turn on data-plan
virtio-blk-pci, virtio-blk-s390, and virtio-blk-ccw all duplicate the
qdev properties of their VirtIOBlock child. This approach does not work
well with string or pointer properties since we must be careful about
leaking or double-freeing them.
Use the QOM alias property to forward property access
There is no need to make DEFINE_VIRTIO_BLK_PROPERTIES() public. Inline
it into virtio-blk.c so it cannot be used by mistake from other source
files.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Peter Crosthwaite
---
hw/block/virtio-blk.c | 12 +++-
include/hw/virtio/virtio-blk.
This function is no longer used since parent objects now use child
aliases to set the VirtIOBlkConf directly.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Peter Crosthwaite
---
hw/block/virtio-blk.c | 6 --
include/hw/virtio/virtio-blk.h | 2 --
2 files changed, 8 deletions(-)
diff
From: Cornelia Huck
If the virtio transport does not support notifiers (like s390-virtio),
we can't use dataplane. Bail out early and let the user know what is
wrong.
Signed-off-by: Cornelia Huck
Reviewed-by: Stefan Hajnoczi
Signed-off-by: Stefan Hajnoczi
---
hw/block/dataplane/virtio-blk.c
From: Max Reitz
As of the "iotests: Allow out-of-tree run" series, the qemu-iotests may
(and should) be run directly in the build tree and will then guess the
binary paths themselves. Therefore, qemu-iotests-quick.sh does not need
to (and should not) enter the source path anymore; also, it does n
The iothread property type is no longer used and can be removed.
Signed-off-by: Stefan Hajnoczi
---
hw/core/qdev-properties-system.c | 50
include/hw/qdev-properties.h | 3 ---
2 files changed, 53 deletions(-)
diff --git a/hw/core/qdev-properties-sy
From: Max Reitz
Now that qemu-iotests-quick.sh supports tests using the qemu binary, we
are free to add such tests to the quick group.
Signed-off-by: Max Reitz
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/group | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
Up until now -device virtio-blk-pci,x-iothread= was used to assign
an IOThread. This was a temporary solution while we cleaned up QOM link
properties.
This patch switches over to a QOM link property since it is now possible
to restrict the setter to unrealized instances and automatically unref
th
From: Chunyan Liu
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. On
From: Jeff Cody
Now that active layer block-commit is supported, the 'top' argument
no longer needs to be mandatory.
Change it to optional, with the default being the active layer in the
device chain.
[kwolf: Rebased and resolved conflict in tests/qemu-iotests/040]
Reviewed-by: Eric Blake
Rev
From: Jeff Cody
This is a small helper function, to determine if 'base' is in the
chain of BlockDriverState 'top'. It returns true if it is in the chain,
and false otherwise.
If either argument is NULL, it will also return false.
Reviewed-by: Benoit Canet
Reviewed-by: Eric Blake
Signed-off-b
From: Jeff Cody
This allows a user to make a live change to the backing file recorded in
an open image.
The image file to modify can be specified 2 ways:
1) image filename
2) image node-name
Note: this does not cause the backing file itself to be reopened; it
merely changes the backing filenam
From: Benoît Canet
fe069d9d had aligned code and documentation while dropping the s from the
actual JSON output. Fix that.
This also fix test/qemu-iotest/081 since the missing s was causing a
permutation.
Signed-off-by: Benoit Canet
Reviewed-by: Eric Blake
Signed-off-by: Stefan Hajnoczi
---
On 01.07.14 10:20, Gerd Hoffmann wrote:
On Mo, 2014-06-30 at 22:32 +1000, Benjamin Herrenschmidt wrote:
On Mon, 2014-06-30 at 13:14 +0200, Gerd Hoffmann wrote:
Hi,
From what I can tell, we only ever call the cursor drawing callback on
non-shared surfaces. Should I deduce that the HW curs
From: Max Reitz
While at it, add some more tests to the quick group (those that run with
-nocache in under three seconds on my HDD).
Signed-off-by: Max Reitz
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/group | 38 +++---
1 file changed, 19 insertions(
On 30/06/2014 15:59, Sebastian Tanase wrote:
Make icount parameter use QemuOpts style options in order
to easily add other suboptions.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
---
cpus.c| 10 +-
include/qemu-common.h | 3 ++-
qemu-options.hx |
From: Jeff Cody
On some image chains, QEMU may not always be able to resolve the
filenames properly, when updating the backing file of an image
after a block commit.
For instance, certain relative pathnames may fail, or drives may
have been specified originally by file descriptor (e.g. /dev/fd/?
Please consider for 2.1. It needs git-am -3 by now; if you need a
respin, let me know.
Markus Armbruster writes:
> When a device model's I/O operation fails, we execute the error
> action. This lets layers above QEMU implement thin provisioning, or
> attempt to correct errors before they reach
From: Jeff Cody
On some image chains, QEMU may not always be able to resolve the
filenames properly, when updating the backing file of an image
after a block job.
For instance, certain relative pathnames may fail, or drives may
have been specified originally by file descriptor (e.g. /dev/fd/???)
The following changes since commit 53a259da5697ec8a82463161e2e32ff942a08bc2:
Merge remote-tracking branch
'remotes/awilliam/tags/vfio-pci-for-qemu-20140630.0' into staging (2014-06-30
18:31:07 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/tracing-p
From: Yang Zhiyong
We have the experience that the guest doesn't stop successfully
though it was instructed to shut down.
The root cause may be not in QEMU mostly. However, QEMU is often
suspected at the beginning just because the issue occurred in
virtualization environment.
Therefore, we nee
On Di, 2014-07-01 at 10:26 +0200, Alexander Graf wrote:
> On 01.07.14 10:20, Gerd Hoffmann wrote:
> > On Mo, 2014-06-30 at 22:32 +1000, Benjamin Herrenschmidt wrote:
> >> On Mon, 2014-06-30 at 13:14 +0200, Gerd Hoffmann wrote:
> >>>Hi,
> >>>
> From what I can tell, we only ever call the c
On Di, 2014-07-01 at 10:31 +0200, Paolo Bonzini wrote:
> Il 01/07/2014 10:26, Alexander Graf ha scritto:
> >>
> >>> Right. A quick fix would be to add a flag to force always using a shadow
> >>> surface and set it in cirrus ... I'm not sure anybody will notice the
> >>> performance difference.
> >>
On Tue, Jul 01, 2014 at 10:40:42AM +0800, Chen, Tiejun wrote:
> On 2014/6/30 19:28, Michael S. Tsirkin wrote:
> >On Mon, Jun 30, 2014 at 06:20:22PM +0800, Chen, Tiejun wrote:
> >>On 2014/6/30 17:55, Michael S. Tsirkin wrote:
> >>>On Mon, Jun 30, 2014 at 05:38:21PM +0800, Chen, Tiejun wrote:
> O
Il 01/07/2014 11:07, Gerd Hoffmann ha scritto:
On Di, 2014-07-01 at 10:31 +0200, Paolo Bonzini wrote:
Il 01/07/2014 10:26, Alexander Graf ha scritto:
Right. A quick fix would be to add a flag to force always using a shadow
surface and set it in cirrus ... I'm not sure anybody will notice the
The following changes since commit ec9fe956d5c728da770db5ec9bc429080ccb5043:
Merge remote-tracking branch 'remotes/bonzini/small-fixes' into staging
(2014-06-30 15:56:00 +0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to fetch changes up
On Tue, 2014-07-01 at 09:09 +0200, Gerd Hoffmann wrote:
> Hi,
>
> > -if (depth == 32 || ((depth == 16 || depth == 15) && !byteswap)) {
> > + if (depth == 32 || depth == 24 ||
> > + ((depth == 16 || depth == 15) && !byteswap)) {
>
> Doesn't apply.
> depth == 15 isn't upstr
On Tue, 2014-07-01 at 10:20 +0200, Gerd Hoffmann wrote:
> > Right. A quick fix would be to add a flag to force always using a shadow
> > surface and set it in cirrus ... I'm not sure anybody will notice the
> > performance difference.
>
> I suspect we can rip out hw cursor emulation and nobody wil
On Tue, 2014-07-01 at 10:26 +0200, Alexander Graf wrote:
>
> Windows NT 4 might use it. I remember that I had issues running NT4 with
> Cirrus emulation a while back.
Any location where one can find images legally ?
> >> Right. A quick fix would be to add a flag to force always using a shadow
>
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Tuesday, July 01, 2014 4:23 PM
> To: chenliang (T)
> Cc: qemu-devel@nongnu.org; peter.mayd...@linaro.org; Paolo Bonzini;
> Gonglei (Arei); Anton Ivanov
> Subject: Re: [Qemu-devel] The master branch qemu compile
Markus Armbruster writes:
> This series is on top of Kevin's "block: Handle failure for
> potentially large allocations".
>
> PATCH 1+2 convert some allocations. While preparing them, I stumbled
> over some useless casts, which led to PATCH 3.
Fell through the cracks despite Max's R-by, and now
On 2014/7/1 17:12, Michael S. Tsirkin wrote:
On Tue, Jul 01, 2014 at 10:40:42AM +0800, Chen, Tiejun wrote:
On 2014/6/30 19:28, Michael S. Tsirkin wrote:
On Mon, Jun 30, 2014 at 06:20:22PM +0800, Chen, Tiejun wrote:
On 2014/6/30 17:55, Michael S. Tsirkin wrote:
On Mon, Jun 30, 2014 at 05:38:21
On 2014/7/1 13:47, Michael S. Tsirkin wrote:
On Mon, Jun 30, 2014 at 08:34:46PM +0100, Stefano Stabellini wrote:
On Fri, 27 Jun 2014, Chen, Tiejun wrote:
On 2014/6/25 17:58, Chen, Tiejun wrote:
On 2014/6/25 17:44, Michael S. Tsirkin wrote:
On Wed, Jun 25, 2014 at 05:28:48PM +0800, Chen, Tieju
From: Peter Maydell
Commit 25814e8987 introduced an error-exit code path which does
a "goto exit" before the cow_bs variable is initialized, meaning
we would call bdrv_unref() on an uninitialized variable and
likely segfault. Fix this by moving the NULL-initialization
to the top of the function a
From: Alexey Kardashevskiy
The existing test whether "-lm" needs to be included or not is
insufficient as it reports false negative on Fedora20/ppc64.
This happens because sin(0.0) is a constant value which compiler
can safely throw away and therefore there is no need to add "-lm".
As the result,
On 1 July 2014 09:39, Paolo Bonzini wrote:
> The following changes since commit ec9fe956d5c728da770db5ec9bc429080ccb5043:
>
> Merge remote-tracking branch 'remotes/bonzini/small-fixes' into staging
> (2014-06-30 15:56:00 +0100)
>
> are available in the git repository at:
>
>
> git://github.co
From: Peter Crosthwaite
Expose the already existing .parent and .addr fields as QOM properties.
.parent (i.e. the field describing the memory region that contains this
one in Memory hierachy) is renamed "container". This is to avoid
confusion with the QOM parent.
Signed-off-by: Peter Crosthwaite
From: Peter Crosthwaite
QOM propertyify the .may-overlap and .priority fields. The setters
will re-add the memory as a subregion if needed (i.e. the values change
when the memory region is already contained).
Signed-off-by: Peter Crosthwaite
[Remove setters. - Paolo]
Signed-off-by: Paolo Bonzin
1 - 100 of 307 matches
Mail list logo
