Public bug reported:
Reading /proc/self/maps a user doesn't get a stack record. Not all
programs relies on the maps file but some do.
The bug found by running 32-bits binaries with address sanitizer (Asan)
instrumentations under 64-bit qemu.
$ echo int main() { return 0; } /tmp/test.c
$ gcc
upstream-20140722-v1.0.json
Section xio3130-downstream Description xio3130-express-downstream-port:
version error: 2 0
Section xio3130-downstream: Description PCIDevice missing, got PCIEDevice
instead; skipping
Section usb-ccid, Description usb-ccid: expected field
abProtocolDataStructure, got
This way the tests run without sound hardware being present
on the build machine. Even with sound hardware it IMO isn't
very useful to use it in regression testing. Once the sound
card tests are advanced enougth that they try to actually
play sound we probably want the guests sound output
Reason: we don't want commit to that interface yet. Possibly
the implementation will be switched over to use fsdev.
Suggested-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/dev-mtp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Public bug reported:
Qemu internal memory areas are not suppressed in the output and are visible to
a guest via /proc/self/maps.
$ echo int main() { return 0; } /tmp/test.c
$ gcc -m32 -fsanitize=address -fno-common -Wall -g -fPIC -o /tmp/test
/tmp/test.c
$ qemu-i386-static -R 0 /tmp/test
Il 22/07/2014 09:34, Gerd Hoffmann ha scritto:
Reason: we don't want commit to that interface yet. Possibly
the implementation will be switched over to use fsdev.
Suggested-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/dev-mtp.c | 2 +-
On Mo, 2014-07-21 at 17:06 +0200, Paolo Bonzini wrote:
Devices that use address_space_rw to write large areas to memory
(as opposed to address_space_map/unmap) were broken with respect
to migration since fe680d0 (exec: Limit translation limiting in
address_space_translate to xen, 2014-05-07).
I think the ifdefs are just accident of history and we can safely remove
them.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1346769
Title:
/proc/self/maps content returned to 32-bits guest under
-M pc-1.0 gives a few errors:
$ ./scripts/vmstate-static-checker.py -s v1.0-1.0.json -d
upstream-20140722-v1.0.json
Section xio3130-downstream Description xio3130-express-downstream-port:
version error: 2 0
Section xio3130-downstream: Description PCIDevice missing, got
PCIEDevice
Il 22/07/2014 11:50, Amit Shah ha scritto:
These are the ones that remain after fixing up the rest:
Section xio3130-downstream Description xio3130-express-downstream-port:
version error: 2 0
Section usb-host Section usb-host Description usb-host: minimum version
error: 0 1
Section
- Mail original -
De: Paolo Bonzini pbonz...@redhat.com
À: Sebastian Tanase sebastian.tan...@openwide.fr, qemu-devel@nongnu.org
Cc: aligu...@amazon.com, afaer...@suse.de, r...@twiddle.net, peter maydell
peter.mayd...@linaro.org,
mich...@walle.cc, a...@alex.org.uk,
Il 22/07/2014 11:58, Sebastian Tanase ha scritto:
-timers_state.cpu_clock_offset contains the offset between the real and
virtual clocks.
However, when using the value of the virtual clock
(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL)),
qemu_icount_bias already includes this offset because, on
On (Tue) 22 Jul 2014 [11:55:29], Paolo Bonzini wrote:
Il 22/07/2014 11:50, Amit Shah ha scritto:
These are the ones that remain after fixing up the rest:
Section xio3130-downstream Description xio3130-express-downstream-port:
version error: 2 0
Section usb-host Section usb-host
On 22 Jul 2014, at 11:22, Amit Shah wrote:
Also interesting is qemu 1.0 - qemu-kvm-1.0:
Section isa-pit, Description i8254: expected field channels, got
flags; skipping rest
This one, together with the PIIX4 one (which for some reason doesn't
show up) where the two I hit, after manually
From: Chen Gang gang.chen.5...@gmail.com
If kvm_arch_remove_sw_breakpoint() in CPU_FOREACH() always be fail, it
will let 'cpu' NULL. And the next kvm_arch_remove_sw_breakpoint() in
QTAILQ_FOREACH_SAFE() will get NULL parameter for 'cpu'.
And kvm_arch_remove_sw_breakpoint() can assumes 'cpu' must
The following changes since commit fa666c10f2f3e15685ff88abd3bc433ddce012d6:
Revert kvmclock: Ensure time in migration never goes backward (2014-07-18
15:28:03 +0200)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to
Devices that use address_space_rw to write large areas to memory
(as opposed to address_space_map/unmap) were broken with respect
to migration since fe680d0 (exec: Limit translation limiting in
address_space_translate to xen, 2014-05-07). Such devices include
IDE CD-ROMs.
The reason is that
2014-07-22 0:49 GMT+04:00 Samuel Thibault samuel.thiba...@gnu.org:
Alternatively, you can track the parameters branch, which I don't
regenerate.
Thanks. Now all works fine.
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination clearer.
It avoids the abort(), which in the
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination clearer.
There is an underlying insufficiency
Gerd Hoffmann kra...@redhat.com writes:
This way the tests run without sound hardware being present
on the build machine. Even with sound hardware it IMO isn't
very useful to use it in regression testing. Once the sound
card tests are advanced enougth that they try to actually
play sound
On 22 Jul 2014, at 11:54, Amit Shah amit.s...@redhat.com wrote:
This one, together with the PIIX4 one (which for some reason doesn't
show up) where the two I hit, after manually fixing the rom sizes
stuff on the command line.
Apparently flags and channels are pseudonyms.
No, they're
Amit Shah amit.s...@redhat.com writes:
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination
Amit Shah amit.s...@redhat.com writes:
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination
Comparing json outputs from qemu-1.0 with qemu-2.1 turned up a few
description name changes; whitelist them here.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
scripts/vmstate-static-checker.py | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
Hi,
This patchset updates the whitelist and adds handling for 'unused'
fields. These were found when comparing qemu-1.0 json output with
qemu-2.1 -M pc-1.0.
Amit Shah (2):
vmstate static checker: whitelist additions
checker: ignore fields marked unused
scripts/vmstate-static-checker.py |
On (Tue) 22 Jul 2014 [13:41:43], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a
On (Tue) 22 Jul 2014 [12:38:14], Alex Bligh wrote:
On 22 Jul 2014, at 11:54, Amit Shah amit.s...@redhat.com wrote:
This one, together with the PIIX4 one (which for some reason doesn't
show up) where the two I hit, after manually fixing the rom sizes
stuff on the command line.
The following changes since commit 35858955e6c6f9ef41c199d15457c13426ac6434:
Merge remote-tracking branch 'remotes/afaerber/tags/qom-devices-for-2.1' into
staging (2014-07-21 18:06:12 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-rng.git
From: John Snow js...@redhat.com
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch replaces the
abort with a simple error message to make the reason for the termination
clearer. This also ensures device-hotplug with
Il 22/07/2014 13:54, Amit Shah ha scritto:
a) because I'm using qemu-kvm-1.0, not qemu-1.0. You looked at qemu-1.0
in the previous message; that's not directly relevant for what I'm
looking at as my source is qemu-kvm-1.0 (qemu vs qemu-kvm).
Sigh; please read both my replies.
The
On 22 July 2014 11:51, Paolo Bonzini pbonz...@redhat.com wrote:
The following changes since commit fa666c10f2f3e15685ff88abd3bc433ddce012d6:
Revert kvmclock: Ensure time in migration never goes backward (2014-07-18
15:28:03 +0200)
are available in the git repository at:
On 22 Jul 2014, at 12:54, Amit Shah amit.s...@redhat.com wrote:
Sigh; please read both my replies.
The only difference between qemu-kvm-1.0 and qemu-1.0 is the presence
of the pci-assign section in qemu-kvm-1.0. All other output from
qemu-1.0 - qemu-2.1 is equally applicable to
On 22 Jul 2014, at 13:12, Paolo Bonzini pbonz...@redhat.com wrote:
There's something similar going on with PIIX4_PM but I don't remember
the details.
From memory:
* qemu-1.0 uses the v2 format
* qemu-kvm-1.0 uses the v3 format but advertises itself as v2
* qemu-2.1 uses the v3 format
I
On Tue, 22 Jul 2014, Roger Pau Monné wrote:
On 27/05/14 15:29, Stefan Hajnoczi wrote:
On Fri, May 23, 2014 at 05:57:48PM +0200, Roger Pau Monne wrote:
The current behaviour of tap_open for BSD systems differ greatly from
it's Linux counterpart. Since FreeBSD supports interface renaming and
On Fri, Jun 27, 2014 at 11:24:08AM +0300, Chrysostomos Nanakos wrote:
+xseg_set_req_data(s-xseg, req, reqdata);
+if (op == ARCHIP_OP_WRITE) {
+data = xseg_get_data(s-xseg, req);
+if (!data) {
+archipelagolog(Cannot get XSEG data\n);
+goto
On Thu, Jul 10, 2014 at 01:04:54PM +0300, Chrysostomos Nanakos wrote:
On 07/10/2014 03:23 AM, Jeff Cody wrote:
On Fri, Jun 27, 2014 at 11:24:08AM +0300, Chrysostomos Nanakos wrote:
+err_exit:
+__sync_add_and_fetch(segreq-failed, 1);
+if (segments_nr == 1) {
+if
On (Tue) 22 Jul 2014 [14:12:00], Paolo Bonzini wrote:
Il 22/07/2014 13:54, Amit Shah ha scritto:
a) because I'm using qemu-kvm-1.0, not qemu-1.0. You looked at qemu-1.0
in the previous message; that's not directly relevant for what I'm
looking at as my source is qemu-kvm-1.0 (qemu
On (Tue) 22 Jul 2014 [13:15:41], Alex Bligh wrote:
On 22 Jul 2014, at 12:54, Amit Shah amit.s...@redhat.com wrote:
Sigh; please read both my replies.
The only difference between qemu-kvm-1.0 and qemu-1.0 is the presence
of the pci-assign section in qemu-kvm-1.0. All other output
On (Tue) 22 Jul 2014 [13:19:43], Alex Bligh wrote:
On 22 Jul 2014, at 13:12, Paolo Bonzini pbonz...@redhat.com wrote:
There's something similar going on with PIIX4_PM but I don't remember
the details.
From memory:
* qemu-1.0 uses the v2 format
* qemu-kvm-1.0 uses the v3 format but
Paolo Bonzini pbonz...@redhat.com wrote:
Devices that use address_space_rw to write large areas to memory
(as opposed to address_space_map/unmap) were broken with respect
to migration since fe680d0 (exec: Limit translation limiting in
address_space_translate to xen, 2014-05-07). Such devices
Juan Quintela quint...@redhat.com wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Call details:
15:00 CEST
13:00 UTC
09:00 EDT
Every two weeks
If you need phone number details, contact me privately
No topis, no call.
See you in 2 weeks.
and rework error path a bit. There is no difference at the moment, but
the code will be definitely shorter when additional processing will
be required for WithouFreSpacExt
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
Parallels has released in the recent updates of Parallels Server 5/6
new addition to his image format. Images with signature WithouFreSpacExt
have offsets in the catalog coded not as offsets in sectors (multiple
of 512 bytes) but offsets coded in blocks (i.e. header-tracks * 512)
In this case to
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
block/parallels.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/block/parallels.c b/block/parallels.c
index c44df87..8f9ec8a 100644
---
Parallels image format has several additional fields inside:
- nb_sectors is actually 64 bit wide. Upper 32bits are not used for
images with signature WithoutFreeSpace and must be explicitely
zeroed according to Parallels. They will be used for images with
signature WithouFreSpacExt
- inuse
- Mail original -
De: Paolo Bonzini pbonz...@redhat.com
À: Sebastian Tanase sebastian.tan...@openwide.fr
Cc: aligu...@amazon.com, afaer...@suse.de, r...@twiddle.net, peter maydell
peter.mayd...@linaro.org,
mich...@walle.cc, a...@alex.org.uk, stefa...@redhat.com,
Parallels has released in the recent updates of Parallels Server 5/6
new addition to his image format. Images with signature WithouFreSpacExt
have offsets in the catalog coded not as offsets in sectors (multiple
of 512 bytes) but offsets coded in blocks (i.e. header-tracks * 512)
In this case all
- Mail original -
De: Paolo Bonzini pbonz...@redhat.com
À: Sebastian Tanase sebastian.tan...@openwide.fr, qemu-devel@nongnu.org
Cc: aligu...@amazon.com, afaer...@suse.de, r...@twiddle.net, peter maydell
peter.mayd...@linaro.org,
mich...@walle.cc, a...@alex.org.uk,
Il 22/07/2014 16:02, Sebastian Tanase ha scritto:
Yes, QEMU_CLOCK_VIRTUAL counts up from qemu_clock_get_ns(QEMU_CLOCK_REALTIME)
on ARM (I have only tested with the versatilepb and vexpress boards).
That's a bug to fix indeed, then---it should count up from 0 without
icount, and icount shouldn't
- Mail original -
De: Paolo Bonzini pbonz...@redhat.com
À: Sebastian Tanase sebastian.tan...@openwide.fr
Cc: aligu...@amazon.com, afaer...@suse.de, r...@twiddle.net, peter maydell
peter.mayd...@linaro.org,
mich...@walle.cc, a...@alex.org.uk, stefa...@redhat.com,
- Mail original -
De: Paolo Bonzini pbonz...@redhat.com
À: Sebastian Tanase sebastian.tan...@openwide.fr
Cc: aligu...@amazon.com, afaer...@suse.de, r...@twiddle.net, peter maydell
peter.mayd...@linaro.org,
mich...@walle.cc, a...@alex.org.uk, stefa...@redhat.com,
Il 22/07/2014 17:17, Sebastian Tanase ha scritto:
That's a bug to fix indeed, then---it should count up from 0 without
icount, and icount shouldn't affect this. Thanks for investigating
it.
Just to be sure I don't missunderstand, when you say without icount
you refer to qemu_icount_bias
vmstate_xhci_event was introduced in commit 37352df3 (xhci: add live
migration support), and first released in v1.6.0. The field list in this
VMSD is not terminated with the VMSTATE_END_OF_LIST() macro.
During normal use (ie. migration), the issue is practically invisible,
because the
On (Tue) 22 Jul 2014 [17:26:41], Laszlo Ersek wrote:
vmstate_xhci_event was introduced in commit 37352df3 (xhci: add live
migration support), and first released in v1.6.0. The field list in this
VMSD is not terminated with the VMSTATE_END_OF_LIST() macro.
During normal use (ie. migration),
From: Hu Tao hu...@cn.fujitsu.com
commit e938ba0c tried to enable -mem-path for ppc but breaked some ppc
boards.
The problems are:
1. it fails when allocating memory for rom, sram whose sizes are less
than huge page size:
./ppc-softmmu/qemu-system-ppc -m 512 -mem-path /hugepages/ \
On 07/22/2014 07:48 AM, Amit Shah wrote:
On (Tue) 22 Jul 2014 [13:41:43], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
On (Mon) 21 Jul 2014 [17:44:37], John Snow wrote:
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves
Hi Peter,
This is my current patch queue for ppc. Please pull.
Alex
The following changes since commit 35858955e6c6f9ef41c199d15457c13426ac6434:
Merge remote-tracking branch 'remotes/afaerber/tags/qom-devices-for-2.1' into
staging (2014-07-21 18:06:12 +0100)
are available in the git
Il 22/07/2014 17:26, Laszlo Ersek ha scritto:
vmstate_xhci_event was introduced in commit 37352df3 (xhci: add live
migration support), and first released in v1.6.0. The field list in this
VMSD is not terminated with the VMSTATE_END_OF_LIST() macro.
During normal use (ie. migration), the
Il 22/07/2014 17:28, Sebastian Tanase ha scritto:
When not using -icount everything is fine because QEMU_CLOCK_VIRTUAL
is based on the real clock and the offset; qemu_icount_bias
doesn't come into play. So the vm_clock_warp_start fix is only for the case
where we use -icount.
I meant that
On 07/22/14 17:42, Paolo Bonzini wrote:
Il 22/07/2014 17:26, Laszlo Ersek ha scritto:
vmstate_xhci_event was introduced in commit 37352df3 (xhci: add live
migration support), and first released in v1.6.0. The field list in this
VMSD is not terminated with the VMSTATE_END_OF_LIST() macro.
Expose Intel IOMMU to the BIOS. If object of TYPE_INTEL_IOMMU_DEVICE exists,
add DMAR table to ACPI RSDT table. For now the DMAR table indicates that there
is only one hardware unit without INTR_REMAP capability on the platform.
Signed-off-by: Le Tan tamlokv...@gmail.com
---
hw/i386/acpi-build.c
Add support for emulating Intel IOMMU according to the VT-d specification for
the q35 chipset machine. Implement the logic for DMAR (DMA remapping) without
PASID support. Use register-based invalidation for context-cache invalidation
and IOTLB invalidation.
Basic fault reporting and caching are
Hi,
These patches are intended to introduce Intel IOMMU (VT-d) emulation to q35
chipset. The major job in these patches is to add support for emulating Intel
IOMMU according to the VT-d specification, including basic responses to CSRs
accesses, the logic of DMAR (DMA remapping) and DMA memory
Add Intel IOMMU emulation to q35 chipset and expose it to the guest.
1. Add a machine option. Users can use -machine vtd=on|off in the command
line to enable/disable Intel IOMMU. The default is off.
2. Accroding to the machine option, q35 will initialize the Intel IOMMU and
use pci_setup_iommu()
On (Tue) 22 Jul 2014 [11:30:28], John Snow wrote:
On 07/22/2014 07:48 AM, Amit Shah wrote:
-assert(vrng-conf.max_bytes = INT64_MAX);
+/* Workaround: Property parsing does not enforce unsigned integers,
+ * So this is a hack to reject such numbers. */
+if
On 22 July 2014 16:48, Laszlo Ersek ler...@redhat.com wrote:
On 07/22/14 17:42, Paolo Bonzini wrote:
Cc: qemu-sta...@nongnu.org
As far as I can see, this address was present in my original To: list.
:) (Admittedly, not with CC.)
Including the line in the commit message means it can get
The VMStateDescription for the imx_ccm device was missing its
terminator. Found by static search of the codebase using
a regex based on one suggested by Ian Jackson:
pcregrep -rMi '(?s)VMStateField(?:(?!END_OF_LIST).)*?;' $(git grep -l
'VMStateField\[\]')
Signed-off-by: Peter Maydell
On 22 July 2014 16:38, Alexander Graf ag...@suse.de wrote:
Hi Peter,
This is my current patch queue for ppc. Please pull.
Alex
The following changes since commit 35858955e6c6f9ef41c199d15457c13426ac6434:
Merge remote-tracking branch 'remotes/afaerber/tags/qom-devices-for-2.1'
into
Add a machine type pc-1.0-qemu-kvm for live migrate compatibility
with qemu-kvm version 1.0.
Signed-off-by: Alex Bligh a...@alex.org.uk
---
hw/acpi/piix4.c | 49 --
hw/i386/pc_piix.c| 31 +
On 07/21/2014 10:37 AM, Peter Maydell wrote:
It's trying to measure clock cycles required to perform the startup
relocations.
That's a neat trick, given that the generic timers are not cycle
counters! They're a fixed frequency counter which is generally
unrelated and rather slower than the
On Tue, Jul 22, 2014 at 03:55:38PM -0400, Stefan Berger wrote:
From: Stefan Berger stef...@linux.vnet.ibm.com
Add an SSDT ACPI table for the TPM device.
Add a TCPA table for BIOS logging area when a TPM is being used.
The latter follows this spec here:
On Mon, Jul 21, 2014 at 12:04:22AM +0200, Jan Kiszka wrote:
On 2014-07-20 23:03, Michael S. Tsirkin wrote:
On Sun, Jul 20, 2014 at 11:45:10PM +0200, Jan Kiszka wrote:
On 2014-07-20 21:48, Michael S. Tsirkin wrote:
On Sat, Jul 19, 2014 at 06:55:48PM +0200, Jan Kiszka wrote:
From: Jan
On 21.07.2014 17:52, Eric Blake wrote:
On 07/19/2014 02:35 PM, Max Reitz wrote:
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and mainly clutters
host cache memory. Though this is generally no concern as cache memory
is
On 21.07.2014 17:57, Eric Blake wrote:
On 07/19/2014 02:35 PM, Max Reitz wrote:
qemu-img amend may extensively modify the target image, depending on the
options to be amended (e.g. conversion to qcow2 compat level 0.10 from
1.1 for an image with many unallocated zero clusters). Therefore it
On 21.07.2014 21:52, Jeff Cody wrote:
Use the block layer to create, and write to, the image file in the
VDI .bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW are not needed in the image format driver, and
the underlying
On Tue, Jul 22, 2014 at 10:14:58PM +0200, Max Reitz wrote:
On 21.07.2014 21:52, Jeff Cody wrote:
Use the block layer to create, and write to, the image file in the
VDI .bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW
On 22.07.2014 22:19, Jeff Cody wrote:
On Tue, Jul 22, 2014 at 10:14:58PM +0200, Max Reitz wrote:
On 21.07.2014 21:52, Jeff Cody wrote:
Use the block layer to create, and write to, the image file in the
VDI .bdrv_create() operation.
This has a couple of benefits: Images can now be created over
On Tue, Jul 22, 2014 at 10:21:48PM +0200, Max Reitz wrote:
On 21.07.2014 21:52, Jeff Cody wrote:
This updates the VDI corruption test to also test static VDI image
creation, as well as the default dynamic image creation.
Signed-off-by: Jeff Cody jc...@redhat.com
---
On Tue, Jul 22, 2014 at 04:13:01PM -0400, Stefan Berger wrote:
On 07/22/2014 03:05 PM, Michael S. Tsirkin wrote:
On Tue, Jul 22, 2014 at 03:55:38PM -0400, Stefan Berger wrote:
From: Stefan Berger stef...@linux.vnet.ibm.com
Add an SSDT ACPI table for the TPM device.
Add a TCPA table for BIOS
On 07/22/2014 03:05 PM, Michael S. Tsirkin wrote:
On Tue, Jul 22, 2014 at 03:55:38PM -0400, Stefan Berger wrote:
From: Stefan Berger stef...@linux.vnet.ibm.com
Add an SSDT ACPI table for the TPM device.
Add a TCPA table for BIOS logging area when a TPM is being used.
The latter follows this
qemu-img amend may extensively modify the target image, depending on the
options to be amended (e.g. conversion to qcow2 compat level 0.10 from
1.1 for an image with many unallocated zero clusters). Therefore it
makes sense to allow the user to specify the cache mode to be used.
Signed-off-by:
Currently, qemu-img does not allow setting the cache mode for source
images. However, it reads images generally only once, therefore a full
writeback cache unnecessarily clutters the host cache. In case the user
finds this undesirable, there has to be a way of disabling that cache.
This series
On Tue, Jul 22, 2014 at 11:47:48PM +0800, Le Tan wrote:
Add support for emulating Intel IOMMU according to the VT-d specification for
the q35 chipset machine. Implement the logic for DMAR (DMA remapping) without
PASID support. Use register-based invalidation for context-cache invalidation
and
On 07/22/2014 02:58 PM, Max Reitz wrote:
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and mainly clutters
host cache memory. Though this is generally no concern as cache memory
is freely available and can be scaled by
From: Stefan Berger stef...@linux.vnet.ibm.com
Add an SSDT ACPI table for the TPM device.
Add a TCPA table for BIOS logging area when a TPM is being used.
The latter follows this spec here:
qemu-img should use QMP commands whenever possible in order to ensure
feature completeness of both online and offline image operations. For
the commit command, this is relatively easy, so implement it first
(in the hope that indeed others will follow).
As qemu-img does not have access to QMP (due
Normally, discarded sectors should read back as zero. However, there are
cases in which a sector (or rather cluster) should be discarded as if
they were never written in the first place, that is, reading them should
fall through to the backing file again.
Signed-off-by: Max Reitz
When a block job signals readiness, this is currently reported only
through QMP. If qemu wants to use block jobs for internal tasks, there
needs to be another way to correctly detect when a block job may be
completed.
For this reason, introduce a bool ready which is set when the block
job may be
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 internal snapshots. In this
case, bdrv_make_empty() can be greatly sped up by creating an empty L1
table and dropping all data
Implement this function by making all clusters in the image file fall
through to the backing file (by using the recently extended discard).
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
Reviewed-by: Kevin Wolf kw...@redhat.com
---
block/qcow2.c | 27
Implement progress output for the commit command by querying the
progress of the block job.
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
---
qemu-img-cmds.hx | 4 ++--
qemu-img.c | 24 ++--
qemu-img.texi| 2 +-
3 files
Implement block_job_complete_sync() by doing the exact same thing as
block_job_cancel_sync() does, only with calling block_job_complete()
instead of block_job_cancel().
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Kevin Wolf kw...@redhat.com
---
blockjob.c | 39
Instead of taking the total length of the block device as the block
job's length, use the number of dirty sectors. The progress is now the
number of sectors mirrored to the target block device. Note that this
may result in the job's length increasing during operation, which is
however in fact
Introduce a new parameter for qemu-img commit which may be used to
explicitly specify the backing file into which an image should be
committed if the backing chain has more than a single layer.
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
---
After the top image has been committed, it should be emptied unless
specified otherwise.
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
---
qemu-img-cmds.hx | 4 ++--
qemu-img.c | 34 +++---
qemu-img.texi| 6 +-
3
qemu-img should use QMP commands whenever possible in order to ensure
feature completeness of both online and offline image operations. As
qemu-img itself has no access to QMP (since this would basically require
just everything being linked into qemu-img), imitate QMP's
implementation of
As different image formats most probably map guest addresses to
different host addresses, add a filter to filter the host addresses out;
also, the image filename should be filtered.
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
---
Add a test for qemu-img commit on backing chains with more than two
images. This test also checks whether the top image is emptied (unless
this is prevented by specifying either -d or -b) and does therefore not
work for qed and vmdk which requires it to be separate from 020.
Signed-off-by: Max
Add a test for qcow2's fast bdrv_make_empty implementation on images
without internal snapshots.
Signed-off-by: Max Reitz mre...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
---
tests/qemu-iotests/098 | 75 ++
tests/qemu-iotests/098.out |
1 - 100 of 107 matches
Mail list logo
