On 2015/3/17 14:29, Stefan Weil wrote:
> Confirmed for Debian Jessie, too. The package mesa-common-dev includes
> /usr/include/GL/glx.h, but only a
> /usr/lib/x86_64-linux-gnu/pkgconfig/dri.pc. There is no glx.pc for Debian.
>
Does this patch fix ?
https://lists.gnu.org/archive/html/qemu-devel/2
On 13.03.15 12:56, Bharata B Rao wrote:
> From: Bharata B Rao
>
> Currently CPUState.cpu_index is monotonically increasing and a newly
> created CPU always gets the next higher index. The next available
> index is calculated by counting the existing number of CPUs. This is
> fine as long as we
Hi,
Le 16/03/2015 22:48, John Snow a écrit :
On 03/14/2015 12:50 PM, Hervé Poussineau wrote:
They were introduced in 6f7e9aec5eb5bdfa57a9e458e391b785c283a007 and
82407d1a4035e5bfefb53ffdcb270872f813b34c and lots of bug fixes were done after
that.
This fixes (at least) the detection of the flo
Confirmed for Debian Jessie, too. The package mesa-common-dev includes
/usr/include/GL/glx.h, but only a
/usr/lib/x86_64-linux-gnu/pkgconfig/dri.pc. There is no glx.pc for Debian.
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member
address_space_translate_internal will clamp the *plen length argument
based on the size of the memory region being queried. The iommu walker
logic in addresss_space_translate was ignoring this by discarding the
post fn call value of *plen. Fix by just always using *plen as the
length argument throu
On 03/16/2015 10:35 PM, Michael S. Tsirkin wrote:
On Mon, Mar 16, 2015 at 05:39:44PM +0800, Zhu Guihua wrote:
Add a new API named acpi_send_gpe_event() to send hotplug SCI.
This API can be used by pci, cpu and memory hotplug.
Signed-off-by: Zhu Guihua
Good cleanup, but needs to fix up the co
On Fri, Mar 13, 2015 at 11:30 AM, Gonglei wrote:
> On 2015/3/13 0:43, Andreas Färber wrote:
>> Hello,
>>
>> The main patch of this series is an HMP command "info qom-tree",
>> which displays the machine composition tree. This names all objects,
>> including those missing in "info qtree" for lack o
Sorry but I am new to this. Is it too late to talk to some mentor for Google
summer?
Sorry for being late
Quoting David Gibson (2015-03-12 00:52:10)
> On Thu, Mar 05, 2015 at 08:12:58AM -0600, Michael Roth wrote:
> > Quoting David Gibson (2015-03-04 22:30:40)
> > > On Wed, Mar 04, 2015 at 07:37:08AM -0600, Michael Roth wrote:
> > > > Quoting Michael Roth (2015-03-03 23:50:34)
> > > > > Quoting David Gi
Hi Juan
This patch will make my work more difficult, as we discussed before, after
modification,
I have to use a lock before I can reuse the function save_block_hdr in my
compression threads,
this will lead to low efficiency. Could help to revert this patch?
Liang
> -Original Message
"Michael S. Tsirkin" writes:
> On Mon, Mar 09, 2015 at 05:43:19PM +1030, Rusty Russell wrote:
>> > I think it's a good idea to merge these patches (maybe except the
>> > !TASK_RUNNING thing) sooner rather than later, to make sure people have
>> > the time to test the fixes properly. Would you lik
On Fri, 03/13 17:56, Peter Maydell wrote:
> On 13 March 2015 at 17:50, Patchew Tool wrote:
> >
> > This series passed Patchew automatic testing, but there are some warnings.
> >
> > Find the log fragments below, or open the following URL to see the full log:
> >
> > http://qemu.patchew.org/testing
On Mon, Mar 16, 2015 at 22:23:24 +, Peter Maydell wrote:
> On 16 March 2015 at 20:08, Emilio G. Cota wrote:
> > I fail to see why calling tlb_fill() from the helper causes
> > trouble. What I thought would happen is that the exception
> > (if any) is started from the helper, gets serviced, an
On Tue, Mar 17, 2015 at 9:35 AM, Andreas Färber wrote:
> Am 17.03.2015 um 00:19 schrieb Alistair Francis:
>> On Sat, Feb 28, 2015 at 6:52 PM, Alistair Francis
>> wrote:
>>> On Sat, Feb 28, 2015 at 3:59 AM, Andreas Färber wrote:
Am 27.02.2015 um 02:48 schrieb Alistair Francis:
> Use the
On 3/17/15, 2:21 AM, "Paolo Bonzini" wrote:
>
>On 16/03/2015 16:59, Chris Takemura wrote:
>> Hi everyone,
>>
>> We're using qemu as a device model for xen 4.4. Lately we've been
>> having qemu crashes with this output:
>>
>> lsi_scsi: error: Unhandled writeb 0xff = 0x0
>>
>> lsi_scsi: error:
Am 17.03.2015 um 00:19 schrieb Alistair Francis:
> On Sat, Feb 28, 2015 at 6:52 PM, Alistair Francis
> wrote:
>> On Sat, Feb 28, 2015 at 3:59 AM, Andreas Färber wrote:
>>> Am 27.02.2015 um 02:48 schrieb Alistair Francis:
Use the DeviceClass realize() and init() instead of
the deprecated
Test non-default -smp core and thread counts and a non-default CPU model
on all PC machines except for isapc. Note that not all historic versions
actually supported this particular configuration, ignored for simplicity.
For machines pc-*-1.5+ test QMP cpu-add with monotonically increasing ID,
and
Hello,
As prerequisite for upcoming changes to CPU initialization and hot-plug code,
I would like to merge these two patches from my x86 CPU branch.
For now the coverage is limited to one test case per PC machine and is testing
both a non-default sockets/cores/hyperthreads combination, a non-defa
This avoids cluttering GTester output with irrelevant warnings.
Cc: Eduardo Habkost
Signed-off-by: Andreas Färber
---
hw/i386/pc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index c756404..4b46c29 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.
This is done by adding a new machine property vmware-port-ring3 that
needs to be enabled to have any effect. It only effects accel=tcg
mode. It is needed if you want to use VMware tools in accel=tcg
mode.
Signed-off-by: Don Slutz
(cherry picked from commit 6d99c91fc9ae27b476e89a8cc880b4a46e2375
The support included is enough to allow VMware tools to install in a
guest and provide guestinfo support. guestinfo support is provided
by what is known as VMware RPC support.
If the guest is running VMware tools, then the "build version" of
the tools is also available via the property build-numb
Signed-off-by: Don Slutz
---
hw/misc/vmport_rpc.c | 250 +++
trace-events | 8 +-
2 files changed, 255 insertions(+), 3 deletions(-)
diff --git a/hw/misc/vmport_rpc.c b/hw/misc/vmport_rpc.c
index 0ba3319..a147561 100644
--- a/hw/misc/vmpo
This adds one new inject command:
inject-vmport-action
And three guest info commands:
vmport-guestinfo-set
vmport-guestinfo-get
query-vmport-guestinfo
More details in qmp-commands.hx
Signed-off-by: Don Slutz
---
hw/misc/vmport_rpc.c | 269 +++
Based on
https://sites.google.com/site/chitchatvmback/backdoor
and testing on ESXi, this should be in MB not bytes.
Signed-off-by: Don Slutz
---
hw/misc/vmport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/misc/vmport.c b/hw/misc/vmport.c
index 7fcc00d..6b350ce 10064
Signed-off-by: Don Slutz
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d7e9ba2..8672e00 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -754,6 +754,13 @@ S: Maintained
F: hw/net/vmxnet*
F: hw/scsi/vmw_pvscsi*
+VMware port
+M: Don Slut
This is the 1st part of "Add limited support of VMware's hyper-call
rpc".
This patch uses existing infrastructure used by vmmouse.c (provided
by vmport.c) to handle the VMware backdoor command 30.
One of the better on-line references is:
https://sites.google.com/site/chitchatvmback/backdoor
Mor
On Sat, Feb 28, 2015 at 6:52 PM, Alistair Francis
wrote:
> On Sat, Feb 28, 2015 at 3:59 AM, Andreas Färber wrote:
>> Am 27.02.2015 um 02:48 schrieb Alistair Francis:
>>> Use the DeviceClass realize() and init() instead of
>>> the deprecated SysBusDevice init().
>>>
>>> Signed-off-by: Alistair Fra
Changes v1 to v2:
Added live migration code.
Adjust data structures for migration.
Switch to GHashTable.
Eric Blake
s/spawened/spawned/
Done
s/traceing/tracing/
Done
Change "error_set(errp, ERROR_CLASS_GENERIC_ERROR, " to
"error_setg(errp, "
Done
W
On 03/16/2015 09:40 PM, Andreas Färber wrote:
Am 16.03.2015 um 05:58 schrieb Alexey Kardashevskiy:
On 03/06/2015 12:17 AM, Alexander Graf wrote:
On 05.03.15 02:56, Alexey Kardashevskiy wrote:
At the moment when running in KVM mode, QEMU registers "host" class to
match the current CPU PVR value
On 16 March 2015 at 20:08, Emilio G. Cota wrote:
> Removing the call to tlb_fill() on a TLB miss solves the problem.
> But of course this also means the helper doesn't work as intended.
>
> I fail to see why calling tlb_fill() from the helper causes
> trouble. What I thought would happen is that
Public bug reported:
When passing --enable-opengl to ./configure qemu now looks for a glx.pc
but this doesn't exist on Gentoo or apparently Fedora 21 according to
the mailing list reports.
On my amd64 funtoo box these are the *glx.pc files found
/usr/lib32/pkgconfig/xcb-glx.pc
/usr/lib32/pkgconfi
On 16.03.2015 19:49, Cole Robinson wrote:
Since 2.3 rc0 should be out tomorrow, I'll just wait for that to be released
and build it for rawhide/f22 and virt-preview
Shouldn't we have a 2.2.1 version, too?
A reference point between 2.1 and the not yet released version 2.3
version would be fin
Am 16.03.2015 um 22:48 schrieb Alexander Graf:
On 14.03.15 11:29, Stefan Weil wrote:
This fixes potential runtime crashes and two warnings from Coverity.
The new error message does not add a prefix "qemu:" because that is
already done in function hw_error. It also starts with an uppercase
let
On 03/14/2015 12:50 PM, Hervé Poussineau wrote:
They were introduced in 6f7e9aec5eb5bdfa57a9e458e391b785c283a007 and
82407d1a4035e5bfefb53ffdcb270872f813b34c and lots of bug fixes were done after
that.
This fixes (at least) the detection of the floppy controller on Debian
4.0r9/SPARC,
and SS
On 14.03.15 11:29, Stefan Weil wrote:
> This fixes potential runtime crashes and two warnings from Coverity.
>
> The new error message does not add a prefix "qemu:" because that is
> already done in function hw_error. It also starts with an uppercase
> letter because that seems to be the mostly
On 03/16/2015 04:57 PM, Max Reitz wrote:
On 2015-03-13 at 14:30, John Snow wrote:
Add bdrv_clear_dirty_bitmap and a matching QMP command,
qmp_block_dirty_bitmap_clear that enables a user to reset
the bitmap attached to a drive.
This allows us to reset a bitmap in the event of a full
drive bac
On 2015-03-13 at 14:30, John Snow wrote:
Add the "frozen" status booleans, to inform clients
when a bitmap is occupied doing a task.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c | 1 +
qapi/block-core.json | 5 -
2 files changed, 5 insertions(+), 1 deletio
On 2015-03-13 at 14:30, John Snow wrote:
Add bdrv_clear_dirty_bitmap and a matching QMP command,
qmp_block_dirty_bitmap_clear that enables a user to reset
the bitmap attached to a drive.
This allows us to reset a bitmap in the event of a full
drive backup.
Signed-off-by: John Snow
---
block.
On 2015-03-13 at 14:30, John Snow wrote:
We add a bitmap merge operation to assist in error cases
where we wish to combine two bitmaps together.
This is algorithmically O(bits) provided HBITMAP_LEVELS remains
constant. For a full bitmap on a 64bit machine:
sum(bits/64^k, k, 0, HBITMAP_LEVELS) ~=
On 2015-03-16 at 16:53, John Snow wrote:
On 03/16/2015 04:44 PM, Max Reitz wrote:
On 2015-03-13 at 14:30, John Snow wrote:
The new command pair is added to manage a user created dirty bitmap.
The
dirty bitmap's name is mandatory and must be unique for the same
device,
but different devices
On 2015-03-13 at 14:30, John Snow wrote:
As a convenience: between incremental backups, bitmap migrations
and bitmap persistence we seem to need to recalculate these a lot.
Because the lengths are a little bit-twiddly, let's just solidly
cache them and be done with it.
Signed-off-by: John Snow
On 03/16/2015 04:44 PM, Max Reitz wrote:
On 2015-03-13 at 14:30, John Snow wrote:
The new command pair is added to manage a user created dirty bitmap. The
dirty bitmap's name is mandatory and must be unique for the same device,
but different devices can have bitmaps with the same names.
The g
On 2015-03-13 at 14:30, John Snow wrote:
The new command pair is added to manage a user created dirty bitmap. The
dirty bitmap's name is mandatory and must be unique for the same device,
but different devices can have bitmaps with the same names.
The granularity is an optional field. If it is no
On 2015-03-13 at 14:30, John Snow wrote:
Signed-off-by: John Snow
---
docs/bitmaps.md | 311
1 file changed, 311 insertions(+)
create mode 100644 docs/bitmaps.md
Reviewed-by: Max Reitz
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
This patch adds the core code for virtio gpu emulation,
covering 2d support.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
hw/display/Makefile.objs | 2 +
hw/display/virtio-gpu.c
On Sun, Mar 15, 2015 at 20:42:31 -0400, Emilio G. Cota wrote:
> On Sun, Mar 15, 2015 at 16:10:21 -0700, Richard Henderson wrote:
> > It goes into softmmu_template.h. Which then tests a victim tlb, and finally
> > calls tlb_fill. You'll probably need to do the same.
>
> I've defined this vaddr->p
On Mon, Mar 16, 2015 at 3:49 PM, Bandan Das wrote:
> jacob jacob writes:
>
>> On Mon, Mar 16, 2015 at 2:12 PM, Bandan Das wrote:
>>> jacob jacob writes:
>>>
I also see the following in dmesg in the VM.
[0.095758] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff])
[
jacob jacob writes:
> On Mon, Mar 16, 2015 at 2:12 PM, Bandan Das wrote:
>> jacob jacob writes:
>>
>>> I also see the following in dmesg in the VM.
>>>
>>> [0.095758] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff])
>>> [0.096006] acpi PNP0A03:00: ACPI _OSC support notification fa
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
Add seavgabios configuration for virtio-vga,
hook up the new vgabios in the makefiles.
Signed-off-by: Gerd Hoffmann
---
Makefile | 2 +-
roms/Makefile | 2 +-
roms/config.vga-virtio | 6 ++
3 files changed, 8 insertion
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
Add prebuilt vgabios-virtio.bin binary.
Signed-off-by: Gerd Hoffmann
---
pc-bios/vgabios-virtio.bin | Bin 0 -> 37376 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 pc-bios/vgabios-virtio.bin
Well, I can't really revi
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
Some convinience fluff: Add support for '-vga virtio', also add
virtio-vga to the list of vga cards so '-device virtio-vga' will
turn off the default vga.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoff
On 03/16/15 15:15, Gabriel L. Somlo wrote:
> Currently, when fw_cfg_add_file_callback() is invoked with a
> duplicate file name, it gets to insert the data blob at the
> next available selector, but exit (signalling the error via
> a call to the trace_fw_cfg_add_file_dupe() function) before
> incre
eing it with the new ROM that went in today?
( remotes/kraxel/tags/pull-seabios-1.8.1-20150316-1 ) and it doesn't
trigger with my one line script?
Dave
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
t;
> https://github.com/bkoppelmann/qemu-tricore-upstream.git
> tags/pull-tricore-20150316
>
> for you to fetch changes up to b724b012a4ea9877c5ddad254df63735a945618c:
>
> target-tricore: Add instructions of SYS opcode format (2015-03-16 15:53:08
> +)
>
> --
For now, it looks like bug have a mixed Murphy-Heisenberg nature, as
it appearance is very rare (compared to the number of actual launches)
and most probably bounded to the physical characteristics of my
production nodes. As soon as I reach any reproducible path for a
regular workstation environmen
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
This patch adds a virtio-vga device. It is simliar to virtio-gpu-pci,
but it also adds in vga compatibility, so guests without native
virtio-gpu support can drive the device in vga mode.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave
On 03/16/15 15:15, Gabriel L. Somlo wrote:
> Currently, fw_cfg_add_bytes_read_callback() does not deal with
> the possibility that the data pointer at the requested key position
> has previously been set, and assumes it will be called exactly once
> for each key value.
>
> This patch introduces an
On 03/13/2015 08:07 PM, Kashyap Chamarthy wrote:
> On Fri, Mar 13, 2015 at 10:18:39PM +0100, Gerhard Wiesinger wrote:
>> Hello,
>>
>> Any updates for the
>> http://fedorapeople.org/groups/virt/virt-preview/fedora-virt-preview.repo
>> repo to qemu 2.2.1 planned?
>
> The above is maintained by Fedor
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
This patch adds virtio-gpu-pci, which is the pci proxy for the virtio
gpu device. With this patch in place virtio-gpu is functional. You
need a linux guest with a virtio-gpu driver though, and output will
appear pretty late in boot, once the kernel i
On Mon, Mar 16, 2015 at 06:02:45PM +0100, Laszlo Ersek wrote:
> On 03/16/15 15:15, Gabriel L. Somlo wrote:
> > The fw_cfg device allowed guest-side data writes to overwrite the
> > selected entry in place, without allowing modification to the size
> > of the entry, and with the ability to invoke a
#x27;remotes/pmaydell/tags/pull-target-arm-20150316' into staging (2015-03-16
> 13:56:10 +)
>
> are available in the git repository at:
>
> git://github.com/rth7680/qemu.git tags/tcg-pull-20150316
>
> for you to fetch changes up to 2374c4b8375072da1f401c6daccc68ae76c
On 2015-03-13 at 05:47, Gerd Hoffmann wrote:
This patch adds the core code for virtio gpu emulation,
covering 2d support.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
hw/display/Makefile.objs | 2 +
hw/display/virtio-gpu.c
On Mon, Mar 16, 2015 at 2:12 PM, Bandan Das wrote:
> jacob jacob writes:
>
>> I also see the following in dmesg in the VM.
>>
>> [0.095758] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff])
>> [0.096006] acpi PNP0A03:00: ACPI _OSC support notification failed,
>> disabling PCIe ASPM
>
Jan Kiszka writes:
> Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
>> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
>>> Hi,
>>>
>>> apparently since the latest QEMU updates I'm getting this once in a
>>> while:
>>
>> http://www.seabios.org/pipermail/seabios/2015-March/008897.html
>
> OK...
On Mon, Mar 16, 2015 at 06:33:52PM +0100, Markus Armbruster wrote:
> Doesn't work since commit 31bed55 changed qdev_device_help() to reject
> abstract devices and devices that have
> cannot_instantiate_with_device_add_yet set.
>
> The former makes sense: abstract devices are purely internal, and t
jacob jacob writes:
> I also see the following in dmesg in the VM.
>
> [0.095758] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff])
> [0.096006] acpi PNP0A03:00: ACPI _OSC support notification failed,
> disabling PCIe ASPM
> [0.096915] acpi PNP0A03:00: Unable to request _OSC cont
On 16/03/2015 18:33, Markus Armbruster wrote:
> Doesn't work since commit 31bed55 changed qdev_device_help() to reject
> abstract devices and devices that have
> cannot_instantiate_with_device_add_yet set.
>
> The former makes sense: abstract devices are purely internal, and the
> implementation
Doesn't work since commit 31bed55 changed qdev_device_help() to reject
abstract devices and devices that have
cannot_instantiate_with_device_add_yet set.
The former makes sense: abstract devices are purely internal, and the
implementation of the help feature can't cope with them.
The latter makes
Make the CPU iotlb a structure rather than a plain hwaddr;
this will allow us to add transaction attributes to it.
Signed-off-by: Peter Maydell
---
cputlb.c| 4 ++--
include/exec/cpu-defs.h | 13 +++--
softmmu_template.h | 32 +---
3 file
On 16 March 2015 at 13:41, Juan Quintela wrote:
> The following changes since commit 2dfe7d07e2f40adb18a0b0cd286f3d327692d0fc:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20150316' into
> staging (2015-03-16 11:44:55 +)
>
> are available in the
This is an RFC patchset aimed at getting comment on
some memory API changes to support "transaction attributes",
ie sideband information that goes along with a memory read
or write access to define things like ARM secure/nonsecure,
CPU/transaction master ID, privileged/nonprivileged.
(See also pre
On 16/03/2015 16:59, Chris Takemura wrote:
> Hi everyone,
>
> We're using qemu as a device model for xen 4.4. Lately we've been
> having qemu crashes with this output:
>
> lsi_scsi: error: Unhandled writeb 0xff = 0x0
>
> lsi_scsi: error: Unhandled writeb 0x100 = 0x0
>
> lsi_scsi: error: Unha
Define an API so that devices can register MemoryRegionOps whose read
and write callback functions are passed an arbitrary pointer to some
transaction attributes and can return a success-or-failure status code.
This will allow us to model devices which:
* behave differently for ARM Secure/NonSecur
Honour the NS bit in ARM page tables:
* when adding entries to the TLB, include the Secure/NonSecure
transaction attribute
* set the NS bit in the PAR when doing ATS operations
Note that we don't yet correctly use the NSTable bit to
cause the page table walk itself to use the right attributes
Add a MemTxAttrs field to the IOTLB, and allow target-specific
code to set it via a new tlb_set_page_with_attrs() function;
pass the attributes through to the device when making IO accesses.
Signed-off-by: Peter Maydell
---
cputlb.c| 18 +++---
include/exec/cpu-defs.h
Add a MemTxAttrs argument to the io_mem_read() and io_mem_write()
functions. In this commit this is simply pushing the ability to
specify attributes out one level of the callstack, and all the
callers currently pass MEMTXATTRS_UNSPECIFIED.
Signed-off-by: Peter Maydell
---
exec.c
On 16/03/2015 17:52, Jeremy White wrote:
> It seemed as though the convention was that all non static functions
> went into the .syms file; I may have misunderstood.
I suspect that the .syms file was introduced as a way to hide utility
functions from libqemuutil.a. Now that libqemuutil is not u
On 13/03/2015 10:47, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann
> ---
> tests/Makefile | 3 +++
> tests/display-vga-test.c | 18 ++
> 2 files changed, 21 insertions(+)
>
> diff --git a/tests/Makefile b/tests/Makefile
> index 588f438..55ad89f 100644
> --- a/t
From: Peter Lieven
The code to check the bitmap for the allocation status of each sector
has been "disabled by reason" ever since the vpc driver existed.
The reason might be that we might end up reading sector by sector
in vpc_read if we really used it. This would be a performance desaster.
The
The CHS calculation as done per the VHD spec imposes a maximum image
size of ~127 GB. Real VHD images exist that are larger than that.
Apparently there are two separate non-standard ways to achieve this:
You could use more heads than the spec does - this is the option that
qemu-img create chooses.
From: Fam Zheng
Signed-off-by: Fam Zheng
Message-id: 1425296209-1476-4-git-send-email-f...@redhat.com
Reviewed-by: Max Reitz
Signed-off-by: Max Reitz
---
blockdev.c | 92 --
1 file changed, 59 insertions(+), 33 deletions(-)
diff --g
From: Peter Lieven
The VHD spec [1] allows for total_sectors of 65535 x 16 x 255 (~127GB)
represented by a CHS geometry. If total_sectors is greater
than 65535 x 16 x 255 this geometry is set as a maximum.
Qemu, Hyper-V and disk2vhd use this special geometry as an indicator
to use the image curr
From: Fam Zheng
Signed-off-by: Fam Zheng
Message-id: 1425296209-1476-2-git-send-email-f...@redhat.com
Reviewed-by: Max Reitz
Signed-off-by: Max Reitz
---
monitor.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/monitor.c b/monitor.c
index c86a89e..8b703f9 100644
On 03/16/15 15:15, Gabriel L. Somlo wrote:
> The fw_cfg device allowed guest-side data writes to overwrite the
> selected entry in place, without allowing modification to the size
> of the entry, and with the ability to invoke a callback each time
> the entry was overwritten completely.
>
> To dat
From: Max Reitz
It is easy to create only self-referential refblocks, but there are
cases where that is impossible. This adds a test for two of those cases
(combined in a single test case).
Suggested-by: Eric Blake
Signed-off-by: Max Reitz
Message-id: 1417798412-15330-1-git-send-email-mre...@r
From: Fam Zheng
All callers are converted, so drop it.
Signed-off-by: Fam Zheng
Message-id: 1425296209-1476-5-git-send-email-f...@redhat.com
Reviewed-by: Max Reitz
Signed-off-by: Max Reitz
---
block.c | 9 -
include/block/block.h | 1 -
2 files changed, 10 deletions(-)
From: Fam Zheng
Signed-off-by: Fam Zheng
Message-id: 1425296209-1476-3-git-send-email-f...@redhat.com
Reviewed-by: Max Reitz
Signed-off-by: Max Reitz
---
migration/block.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/migration/block.c b/migration/block.c
index 0c
From: Peter Lieven
*pnum can't be greater than s->block_size / BDRV_SECTOR_SIZE for allocated
sectors since there is always a bitmap in between.
Signed-off-by: Peter Lieven
Reviewed-by: Max Reitz
Message-id: 1425379316-19639-2-git-send-email...@kamp.de
Signed-off-by: Max Reitz
---
block/vpc.
From: Markus Armbruster
qerror_report_err() is a transitional interface to help with
converting existing monitor commands to QMP. It should not be used
elsewhere. Replace by error_report_err().
Commit 6936f29 cleaned that up in qemu-img.c, but two calls have crept
in since. Take care of them
From: Max Reitz
Signed-off-by: Max Reitz
Message-id: 1423598552-24301-3-git-send-email-mre...@redhat.com
Reviewed-by: Eric Blake
Reviewed-by: Kevin Wolf
Signed-off-by: Max Reitz
---
tests/qemu-iotests/121 | 102 +
tests/qemu-iotests/121.out |
From: Max Reitz
When choosing a new place for the refcount table, alloc_refcount_block()
tries to infer the number of clusters used so far from its argument
cluster_index (which comes from the idea that if any cluster with an
index greater than cluster_index was in use, the refcount table would
h
From: Peter Lieven
the field is named current size in the spec. Name it accordingly.
Signed-off-by: Peter Lieven
Reviewed-by: Max Reitz
Message-id: 1425379316-19639-5-git-send-email...@kamp.de
Signed-off-by: Max Reitz
---
block/vpc.c | 9 +
1 file changed, 5 insertions(+), 4 deletion
From: Markus Armbruster
Message quality regressed in commit dc523cd.
Signed-off-by: Markus Armbruster
Signed-off-by: Kevin Wolf
---
qemu-img.c | 6 ++
tests/qemu-iotests/061.out | 1 -
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
i
From: Markus Armbruster
Error classes are a leftover from the days of "rich" error objects.
New code should always use ERROR_CLASS_GENERIC_ERROR. Commit e246211
added a use of ERROR_CLASS_DEVICE_NOT_FOUND. Replace it.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
Signed-off-by: Ke
From: Markus Armbruster
We've steered users away from QCOW/QCOW2 encryption for a while,
because it's a flawed design (commit 136cd19 Describe flaws in
qcow/qcow2 encryption in the docs).
In addition to flawed crypto, we have comically bad usability, and
plain old bugs. Let me show you.
= Exam
From: Markus Armbruster
Commit c4bacaf improved error reporting, but neglected to update
051.out. Commit 2726958 tried to redress, but didn't get it quite
right (punctuation difference), and shortly after commit
ae071cc..master improved error reporting some more, neglecting 051.out
some more. S
The following changes since commit dcf848c478dd8765bd4f746fc4e80eaad44cf87d:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20150316'
into staging (2015-03-16 13:56:10 +)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/fo
CP0.BadVAddr is supposed to capture the most recent virtual address that caused
the exception. Currently this does not work correctly for unaligned instruction
fetch as translation is not stopped and CP0.BadVAddr is updated with subsequent
addresses.
Signed-off-by: Leon Alrae
---
v2:
* descriptio
Hey Marc-André,
Thanks for the review.
On 03/16/2015 11:22 AM, Marc-André Lureau wrote:
> Hi Jeremy
>
> I have checked no regression for spice, but not the new pcsc backend.
> Do you have a spice-gtk branch or are you using vscclient only?
I'm using spice-gtk with this patch:
http://lists.fre
On 14.03.15 11:29, Stefan Weil wrote:
> This fixes potential runtime crashes and two warnings from Coverity.
>
> The new error message does not add a prefix "qemu:" because that is
> already done in function hw_error. It also starts with an uppercase
> letter because that seems to be the mostly
1 - 100 of 323 matches
Mail list logo
