Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will rep
I'm forwarding this to upstream, such enhancements, in my opinion,
should not be done inside a single distribution, and since I don't
use (and don't even know how to use) the mentioned features I can't
further comment on this, and don't really want to become a broken
phone.
Thank you for the good
On Sat, Mar 01, 2014 at 03:46:22PM +0100, Paolo Bonzini wrote:
> Il 28/02/2014 20:14, Gabriel L. Somlo ha scritto:
> >Some guests (e.g. 0S X) insist on a minimum lapic version of 0x14.
> >This patch bumps the emulated lapic version to 0x14 to accomodate that.
> >
> >Signed-off-by: Gabriel L. Somlo
Il 01/03/2014 13:30, Alexey Kardashevskiy ha scritto:
>
> Corrupted DMA buffer is 0x e0 -- 0x7f15c313f000.
> The e1000 packet is at 0x12ffac2 -- 0x7f15c313eac2.
>
> (0x7f15c313f000 - 0x7f15c313eac2) = 0x53e which is less than 0x5aa and
> (0x5aa - 0x53e) = 0x6c bytes get corrupted.
>
> I see
On 26 February 2014 19:47, Rob Herring wrote:
> Tagged addresses would probably be broken in other places as well as I
> don't think we handle all of the BranchTo() pseudocode. I'm not sure
> anything is using tagged addresses ATM.
Yeah, I agree we would need to fix other places too at some point
Hi
Please, send any topic that you are interested in covering.
Agenda:
* [Qemu-devel] [PATCH V17 00/11] Add support for binding guest numa
nodes
Any news about this? (Vinod)
* Should we change anything to get more people to sign for the call?
There hasn't been a call in quite a long time
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory allocation).
The related test:
- Environments (for qemu-devel):
- Host is under fedora17 desktop wit
'ctx->fs_root' + 'path'/'fullname.data' may be larger than PATH_MAX, so
need use snprintf() instead of sprintf() just like another area have done in
9pfs.
Signed-off-by: Chen Gang
---
hw/9pfs/virtio-9p-local.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/hw/9pfs/vi
When "goto err_out", 'v9fs_string' already was allocated, so still need
free 'v9fs_string' before return.
Signed-off-by: Chen Gang
---
hw/9pfs/virtio-9p-local.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/9pfs/virtio-9p-local.c b/hw/9pfs/virtio-9p-local.c
index fc93e9e
Patch 1/3: move v9fs_string_free() to below "err_out:"
Patch 2/3: use snprintf() instead of sprintf()
(which will be replaced of by Path 3/3)
Patch 3/3: use g_strdup_printf() instead of PATH_MAX limitation
Signed-off-by: Chen Gang
---
hw/9pfs/cofs.c | 15 ++-
hw/9p
Il 28/02/2014 20:14, Gabriel L. Somlo ha scritto:
Some guests (e.g. 0S X) insist on a minimum lapic version of 0x14.
This patch bumps the emulated lapic version to 0x14 to accomodate that.
Signed-off-by: Gabriel L. Somlo
---
Along with the TCG ioapic polarity fix, this allows me to boot OS X
w
Il 28/02/2014 23:08, Eric Blake ha scritto:
Use the fact that we are calling the next release "2.0" to actually kill
qemu disk encryption as a horribly botched feature, on the grounds that
we are doing users a favor by not letting them use broken encryption?
Only for qemu, of course---qemu-img
On 03/01/2014 12:40 AM, Markus Armbruster wrote:
> Visitors get passed a pointer to the visited object. The generated
> visitors try to cope with this pointer being null in some places, for
> instance like this:
>
> visit_start_optional(m, obj ? &(*obj)->has_name : NULL, "name", &err);
>
> v
On 02/24/2014 03:20 PM, Alexey Kardashevskiy wrote:
> On 02/16/2014 03:29 PM, Hoyer, David wrote:
>
>> We are using Qemu-1.7.0 with Xen-4.3.0 and Debian jessie. We are
>> noticing that when we transfer large files from our network to the
>> guestOS via the e1000 virtual network device that we ex
On 1 March 2014 04:36, Chalamarla, Tirumalesh
wrote:
> Hi Peter,
>
> Thanks for the reply, yes i am interested in (2). i will follow up on
> the suggested mailing list.
>
> Just in case if you know, does the gicv3 support available in QEMU, or
> there is a plan.
QEMU doesn't implement
Luiz Capitulino writes:
> On Tue, 11 Feb 2014 14:00:14 +0100
> Lluís Vilanova wrote:
>
>> Adds the "include(...)" primitive to the syntax of QAPI schema files,
>> allowing
>> these to be modularized into multiple per-topic files in the future.
>
> Markus, Eric, you commented/reviewed v2 of this
Lluís Vilanova writes:
> Adds the "include(...)" primitive to the syntax of QAPI schema files.
>
> Signed-off-by: Lluís Vilanova
> ---
> docs/qapi-code-gen.txt |8
> scripts/qapi.py| 36 ++--
> 2 files changed, 42 insertions(+), 2 deletions
Lluís Vilanova writes:
> Use an explicit input file on the command-line instead of reading from
> standard input
>
> Signed-off-by: Lluís Vilanova
> ---
> Makefile | 24 ++--
> docs/qapi-code-gen.txt|4 ++--
18 matches
Mail list logo
