Hello, rebase on upstream?
On Thu, Nov 7, 2013 at 2:23 PM, Laszlo Ersek wrote:
> ... upwards through the following call chain:
>
> pc_init1() | pc_q35_init()
> pc_memory_init()
> pc_system_firmware_init()
> pc_system_flash_init()
>
> Signed-off-by: Laszlo Ersek
> ---
> include/hw/i386/pc.h | 6 --
Hi Anthony,
Please pull my current target-xtensa patch queue.
There are two fixes: one adds missing features for dc233c xtensa core,
another fixes qemu abort caused by gdb (generic breakpoint_invalidate,
reviewed by Paolo).
The following changes since commit 964668b03d26f0b5baa5e5aff0c966f4fcb76e
From: Alexey Kardashevskiy
In order to get devices appear in output of
"./qemu-system-ppc64 -device ?",
they must be assigned to one of DEVICE_CATEGORY_.
This puts VIO devices classes to corresponding categories.
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: Alexander Graf
---
hw/ch
Hi Blue / Aurelien / Anthony,
This is my current patch queue for ppc. Please pull.
Alex
The following changes since commit 964668b03d26f0b5baa5e5aff0c966f4fcb76e9e:
Update version for 1.7.0-rc0 release (2013-11-06 21:49:39 -0800)
are available in the git repository at:
git://github.com/
The SPAPR specification says that the RMA starts at the LPAR's logical
address 0 and is the first logical memory block reported in
the LPAR’s device tree.
So SLOF only maps the first block and that block needs to span
the full RMA.
This makes sure that the RMA area is where SLOF expects it.
Cc:
If backing file doesn't exist, the error message is confusing and
misleading:
$ qemu /tmp/a.qcow2
qemu: could not open disk image /tmp/a.qcow2: Could not open file: No
such file or directory
But...
$ ls /tmp/a.qcow2
/tmp/a.qcow2
$ qemu-img info /tmp/a.qcow2
image: /t
On 11.10.2013, at 12:53, Mark Cave-Ayland wrote:
> OpenBIOS prior to SVN r1225 had a horrible bug when accessing PCI
> configuration space for PPC Mac architectures - instead of writing the PCI
> configuration data value to the data register address, it would instead write
> it to the data regis
On 10/09/2013 01:19 PM, Fam Zheng wrote:
Previously live commit of active block device is not supported, this series
implements it and updates corresponding qemu-iotests cases.
This series is based on BlockJobType enum QAPI series.
v5: Address comments from Eric and Paolo:
Add mirror_start
于 2013/11/8 2:47, Max Reitz 写道:
> If the NewImageMode is "absolute-paths" but no backing file is available
> (e.g., when mirroring a device with an unbacked image), the target image
> will not be backed either. This patch updates the documentation in
> qapi-schema.json accordingly.
>
> Signed-off-
So far POWER7+ was a part of POWER7 family. However it has a different
PVR base value so in order to support PVR masks, it needs a separate
family class.
Another reason to make a POWER7+ family is that its name in the device
tree (/proc/device-tree/cpus/cpu*) should be "Power7+" but not "Power7"
a
On Thu, Nov 07, 2013 at 04:24:59PM +0100, Igor Mammedov wrote:
> On Wed, 6 Nov 2013 19:31:19 -0200
> Marcelo Tosatti wrote:
>
> >
> > v2: condition enablement of new mapping to new machine types (Paolo)
> > v3: fix changelog
> > v4: rebase
> >
> > -
> >
> >
> > Align guest physical addres
It is currently possible to specify things like:
-device e1000,netdev=foo,vlan=1
With this usage, whichever argument was specified last (vlan or netdev)
overwrites what was previousely set and results in a non-working
configuration. Even worse, when used with multiqueue devices,
it causes
>> I read below words on the report of > forecast (May 29, 2013)>, We were going to remove the old
>> block-migration code Then people fixed it
>> Good: it works now
>> Bad: We have to maintain both
>> It uses the same port than migration
>> You need to migrate all/none of block devices
>>
>> The
On 14.10.2013, at 16:58, Michael S. Tsirkin wrote:
> Support ROM blobs not mapped into guest memory:
> same as ROM files really but use caller's buffer.
>
> Support invoking callback on access and
> return memory pointer making it easier
> for caller to update memory if necessary.
>
> Reviewed
On 11/07/2013 06:31 AM, Tom Musta wrote:
> The single-precision scalar arithmetic instructions all interpret the most
> significant 64 bits of a VSR as a single precision floating point number
> stored in double precision format (similar to the standard PowerPC floating
> point single precision ins
On 11/08/2013 09:30 AM, Richard Henderson wrote:
> On 11/08/2013 09:28 AM, Richard Henderson wrote:
>> On 11/07/2013 06:31 AM, Tom Musta wrote:
>>> }
>>>\
>>> +
On 11/08/2013 09:28 AM, Richard Henderson wrote:
> On 11/07/2013 06:31 AM, Tom Musta wrote:
>> }
>> \
>> +
>> \
>> +if (r2sp) {
On 11/07/2013 06:31 AM, Tom Musta wrote:
> }
> \
> +
> \
> +if (r2sp) {
> \
Am 07.11.2013 um 21:28 schrieb "Gabriel L. Somlo" :
> Some guest operating systems' drivers (particularly Mac OS X)
> expect the link state to be pre-initialized by an earlier
> component such as a proprietary BIOS. This patch injects
> additional LSC events upon PHY reset, allowing the OS X dri
Signed-off-by: Laszlo Ersek
---
hw/i386/pc_piix.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index 6e2c027..9bda20a 100644
--- a/hw/i386/pc_piix.c
+++ b/hw/i386/pc_piix.c
@@ -152,7 +152,7 @@ static void pc_init1(QEMUMachineInitArgs *a
On 11/07/13 22:24, Marcel Apfelbaum wrote:
> Why pci-hole and system.flash collide? IMHO we should not play with
> priorities here, better solve the collision.
What about this "beautiful" series? It produces
memory
-000f (prio 0, RW): system
[...]
6000
... upwards through the following call chain:
pc_init1() | pc_q35_init()
pc_memory_init()
pc_system_firmware_init()
pc_system_flash_init()
Signed-off-by: Laszlo Ersek
---
include/hw/i386/pc.h | 6 --
hw/i386/pc.c | 5 +++--
hw/i386/pc_piix.c| 3 ++-
hw/i38
On Thu, 2013-11-07 at 22:31 +0100, Paolo Bonzini wrote:
> Il 07/11/2013 22:24, Marcel Apfelbaum ha scritto:
> > Thank you Laszlo for the detailed info!
> > I think the problem is right above. Why pci-hole and system.flash collide?
> > IMHO we should not play with priorities here, better solve the c
On Thu, 2013-11-07 at 22:48 +0100, Laszlo Ersek wrote:
> On 11/07/13 22:24, Marcel Apfelbaum wrote:
> > On Thu, 2013-11-07 at 22:12 +0100, Laszlo Ersek wrote:
>
> >> adding subregion 'pci-hole' to region 'system' at offset 6000
> >> warning: subregion collision 6000/a000 (pci-hole)
On Thu, 2013-11-07 at 21:51 +, Peter Maydell wrote:
> On 7 November 2013 21:38, Marcel Apfelbaum wrote:
> > Thanks Paolo,
> > Let me just point out what I know (or I think I know):
> > 1. Not all architectures have the behavior: "Address space that is not
> > RAM(and friends) is for sure PCI"
On 7 November 2013 21:38, Marcel Apfelbaum wrote:
> Thanks Paolo,
> Let me just point out what I know (or I think I know):
> 1. Not all architectures have the behavior: "Address space that is not
> RAM(and friends) is for sure PCI".
>Only x86 behaves like this (I think).
More specifically, t
On 11/07/13 22:24, Marcel Apfelbaum wrote:
> On Thu, 2013-11-07 at 22:12 +0100, Laszlo Ersek wrote:
>> adding subregion 'pci-hole' to region 'system' at offset 6000
>> warning: subregion collision 6000/a000 (pci-hole) vs
>> ffe0/20 (system.flash)
> Thank you Laszlo for the
*** This bug is a duplicate of bug 921208 ***
https://bugs.launchpad.net/bugs/921208
** This bug has been marked a duplicate of bug 921208
win7/x64 installer hangs on startup with 0x005d.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
On Wed, Nov 06, 2013 at 11:34:25AM -0500,
"Michael R. Hines" wrote:
> On 10/23/2013 07:00 AM, Isaku Yamahata wrote:
> >Since more integer parameters would come in the future, so how about
> >set_migrate_parameter similar to set_migrate_capability?
> >It sets integer value, while set_migrate_capab
Public bug reported:
I need to utilize 1G hugepages on my guest system. But this is not
possible as long as there is no pdpe1gb support in guest system. The
latest source code contains pdpe1gb support for AMD but not for Intel.
Are there any obstacles that does not allow to implement it for mod
Looks like we need to adjust OpenStack code for the change in RHEL6.5. I
see there is a bug reported here
https://bugs.launchpad.net/nova/+bug/1242819 to clear up some
unnecessary steps for snapshot.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
On 11/07/2013 09:33 AM, Alex Williamson wrote:
On Thu, 2013-11-07 at 12:26 +0200, Michael S. Tsirkin wrote:
On Thu, Nov 07, 2013 at 03:32:29PM +0800, Amos Kong wrote:
On Thu, Nov 07, 2013 at 08:59:22AM +0200, Michael S. Tsirkin wrote:
On Tue, Nov 05, 2013 at 07:17:18PM +0800, Amos Kong wrote:
On 11/07/2013 10:27 AM, Michael S. Tsirkin wrote:
On Thu, Nov 07, 2013 at 07:33:57AM -0700, Alex Williamson wrote:
On Thu, 2013-11-07 at 12:26 +0200, Michael S. Tsirkin wrote:
On Thu, Nov 07, 2013 at 03:32:29PM +0800, Amos Kong wrote:
On Thu, Nov 07, 2013 at 08:59:22AM +0200, Michael S. Tsirki
Il 07/11/2013 22:24, Marcel Apfelbaum ha scritto:
> Thank you Laszlo for the detailed info!
> I think the problem is right above. Why pci-hole and system.flash collide?
> IMHO we should not play with priorities here, better solve the collision.
We need to audit all the other boards that support PC
On 11/07/13 22:21, Paolo Bonzini wrote:
> Il 07/11/2013 22:12, Laszlo Ersek ha scritto:
>> -7ffe (prio 0, RW): system
>> [...]
>> 6000- (prio 0, RW): alias pci-hole @pci
>> 6000-
>> [...]
>> ffe
On Thu, 2013-11-07 at 22:12 +0100, Laszlo Ersek wrote:
> This is a QEMU bug report, only disguised as an edk2-devel followup.
>
> The problem in a nutshell is that the OVMF binary, placed into pflash
> (read-only KVM memslot) used to run in qemu-1.6, but it fails to start
> in qemu-1.7. The OVMF r
Il 07/11/2013 22:12, Laszlo Ersek ha scritto:
> -7ffe (prio 0, RW): system
> [...]
> 6000- (prio 0, RW): alias pci-hole @pci
> 6000-
> [...]
> ffe0- (prio 0, R-): system.flash
>
Le Thursday 07 Nov 2013 à 15:54:09 (-0500), Jeff Cody a écrit :
> On Thu, Nov 07, 2013 at 04:01:42PM +0100, Benoît Canet wrote:
> > Add the minimum of code to prepare the followings patches.
> >
> > If no node_name is provided to bdrv_new the bs->node_name is set to
> > "undefined".
> > This will
This is a QEMU bug report, only disguised as an edk2-devel followup.
The problem in a nutshell is that the OVMF binary, placed into pflash
(read-only KVM memslot) used to run in qemu-1.6, but it fails to start
in qemu-1.7. The OVMF reset vector reads as 0xFF bytes.
(Jordan and myself started writ
Le Thursday 07 Nov 2013 à 13:23:43 (-0700), Eric Blake a écrit :
> On 11/07/2013 08:01 AM, Benoît Canet wrote:
> > Add the minimum of code to prepare the followings patches.
> >
> > If no node_name is provided to bdrv_new the bs->node_name is set to
> > "undefined".
> > This will allow to have so
On Thu, Nov 07, 2013 at 04:01:42PM +0100, Benoît Canet wrote:
> Add the minimum of code to prepare the followings patches.
>
> If no node_name is provided to bdrv_new the bs->node_name is set to
> "undefined".
> This will allow to have some default string to communicate in QMP and HMP.
> This als
On Thu, 2013-11-07 at 12:27 -0800, Jordan Justen wrote:
> On Sun, Nov 3, 2013 at 12:48 PM, Marcel Apfelbaum wrote:
> > The commit:
> >
> > Commit: a53ae8e934cd54686875b5bcfc2f434244ee55d6
> > Author: Marcel Apfelbaum
> > Date: Mon Sep 16 11:21:16 2013 +0300
> >
> > hw/pci: partially handle
On 11/07/2013 08:01 AM, Benoît Canet wrote:
> As node-name is a separate name space as device-name we can enable it's
s/space as/space from/
s/it's/its/
> definition right now: nobody will use it so no harm involved.
>
> Signed-off-by: Benoit Canet
> ---
> block.c | 6 --
> 1 file changed,
On 11/07/2013 08:53 PM, Alex Bennée wrote:
>
> r...@twiddle.net writes:
>
>> All references to cpu_T are done with a constant index. It aids
>> readability to decompose the array into two scalar variables.
>
>
> I'm not necessarily disagreeing with the readability argument but does
> this make
On 11/07/2013 08:01 AM, Benoît Canet wrote:
> The following series introduce a new file.node-name property in order to be
> able to give a name to each BlockDriverState of the graph.
>
> It also define "undefined" as a special value for node-name; a value that
> will be
> used to indicate to the
Some guest operating systems' drivers (particularly Mac OS X)
expect the link state to be pre-initialized by an earlier
component such as a proprietary BIOS. This patch injects
additional LSC events upon PHY reset, allowing the OS X driver
to successfully complete initial link negotiation. This is
On Sun, Nov 3, 2013 at 12:48 PM, Marcel Apfelbaum wrote:
> The commit:
>
> Commit: a53ae8e934cd54686875b5bcfc2f434244ee55d6
> Author: Marcel Apfelbaum
> Date: Mon Sep 16 11:21:16 2013 +0300
>
> hw/pci: partially handle pci master abort
>
> introduced a regression on make check:
Laszlo poin
On 11/07/2013 08:01 AM, Benoît Canet wrote:
> Add the minimum of code to prepare the followings patches.
>
> If no node_name is provided to bdrv_new the bs->node_name is set to
> "undefined".
> This will allow to have some default string to communicate in QMP and HMP.
> This also make "undefined"
On 11/07/2013 12:10 PM, Max Reitz wrote:
> There may be calls to error_setg() and especially error_setg_errno()
> which blindly (and until now wrongly) assume these functions not to
> clobber errno (e.g., they pass errno to error_setg_errno() and return
> -errno afterwards). Instead of trying to fi
On 11/07/2013 11:47 AM, Max Reitz wrote:
> If the NewImageMode is "absolute-paths" but no backing file is available
> (e.g., when mirroring a device with an unbacked image), the target image
> will not be backed either. This patch updates the documentation in
> qapi-schema.json accordingly.
>
> Si
I know there are patches for seabios
Il 07/11/2013 19:04, Gabriel L. Somlo ha scritto:
> Some guest operating systems' drivers (particularly Mac OS X)
> expect the link state to be pre-initialized by an earlier
> component such as a proprietary BIOS. This patch injects an
> additional LSC event upon PHY reset, allowing the OS X driver
Le Thursday 07 Nov 2013 à 20:10:29 (+0100), Max Reitz a écrit :
> There may be calls to error_setg() and especially error_setg_errno()
> which blindly (and until now wrongly) assume these functions not to
> clobber errno (e.g., they pass errno to error_setg_errno() and return
> -errno afterwards).
Hi all,
when starting qemu (with or without kvm active) I get the following error
code after having a few minutes a blue windows logo on a black background:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x005C
Parameters:
0x0110
0xFFD09BC8
0x0019
0xC0
Il 07/11/2013 19:54, Michael S. Tsirkin ha scritto:
> On Thu, Nov 07, 2013 at 06:29:40PM +0100, Paolo Bonzini wrote:
>> Il 07/11/2013 17:47, Michael S. Tsirkin ha scritto:
>>> That's on kvm with 52 bit address.
>>> But where I would be concerned is systems with e.g. 36 bit address
>>> space where w
There may be calls to error_setg() and especially error_setg_errno()
which blindly (and until now wrongly) assume these functions not to
clobber errno (e.g., they pass errno to error_setg_errno() and return
-errno afterwards). Instead of trying to find and fix all of these
constructs, just make sur
Le Thursday 07 Nov 2013 à 19:47:48 (+0100), Max Reitz a écrit :
> If the NewImageMode is "absolute-paths" but no backing file is available
> (e.g., when mirroring a device with an unbacked image), the target image
> will not be backed either. This patch updates the documentation in
> qapi-schema.js
On Thu, Nov 07, 2013 at 06:29:40PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 17:47, Michael S. Tsirkin ha scritto:
> > That's on kvm with 52 bit address.
> > But where I would be concerned is systems with e.g. 36 bit address
> > space where we are doubling the cost of the lookup.
> > E.g. try i38
Le Monday 04 Nov 2013 à 19:33:21 (+0800), Fam Zheng a écrit :
>
> On 11/04/2013 07:06 PM, Kevin Wolf wrote:
> >Am 04.11.2013 um 10:48 hat Fam Zheng geschrieben:
> >>On 11/04/2013 05:31 PM, Stefan Hajnoczi wrote:
> >>>On Wed, Oct 30, 2013 at 02:49:32PM +0100, Markus Armbruster wrote:
> The firs
If the NewImageMode is "absolute-paths" but no backing file is available
(e.g., when mirroring a device with an unbacked image), the target image
will not be backed either. This patch updates the documentation in
qapi-schema.json accordingly.
Signed-off-by: Max Reitz
---
Follow-up to:
- block/dr
Some guest operating systems' drivers (particularly Mac OS X)
expect the link state to be pre-initialized by an earlier
component such as a proprietary BIOS. This patch injects an
additional LSC event upon PHY reset, allowing the OS X driver
to successfully complete initial link negotiation. This i
Il 07/11/2013 17:47, Michael S. Tsirkin ha scritto:
> That's on kvm with 52 bit address.
> But where I would be concerned is systems with e.g. 36 bit address
> space where we are doubling the cost of the lookup.
> E.g. try i386 and not x86_64.
Tried now...
P_L2_LEVELS pre-patch
On Thu, Nov 07, 2013 at 05:29:15PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 17:21, Michael S. Tsirkin ha scritto:
> >> > This fixes the problems with the misalignment of the master abort region.
> >> > See patch 2 for details, patch 1 is just a preparatory search-and-replace
> >> > patch.
> >> >
Il 07/11/2013 17:21, Michael S. Tsirkin ha scritto:
>> > This fixes the problems with the misalignment of the master abort region.
>> > See patch 2 for details, patch 1 is just a preparatory search-and-replace
>> > patch.
>> >
>> > Paolo Bonzini (2):
>> > split definitions for exec.c and transla
On Thu, Nov 07, 2013 at 05:14:35PM +0100, Paolo Bonzini wrote:
> This fixes the problems with the misalignment of the master abort region.
> See patch 2 for details, patch 1 is just a preparatory search-and-replace
> patch.
>
> Paolo Bonzini (2):
> split definitions for exec.c and translate-all.
As an alternative to commit 818f86b (exec: limit system memory
size, 2013-11-04) let's just make all address spaces 64-bit wide.
This eliminates problems with phys_page_find ignoring bits above
TARGET_PHYS_ADDR_SPACE_BITS and address_space_translate_internal
consequently messing up the computations
The exec.c and translate-all.c radix trees are quite different, and
the exec.c one in particular is not limited to the CPU---it can be
used also by devices that do DMA, and in that case the address space
is not limited to TARGET_PHYS_ADDR_SPACE_BITS bits.
We want to make exec.c's radix trees 64-bi
This fixes the problems with the misalignment of the master abort region.
See patch 2 for details, patch 1 is just a preparatory search-and-replace
patch.
Paolo Bonzini (2):
split definitions for exec.c and translate-all.c radix trees
exec: make address spaces 64-bit wide
exec.c | 2
On Thu, Oct 31, 2013 at 11:47:12AM +0800, Nancy wrote:
> Hi,
>
> Does QEMU support MIPS smp 2 malta board?
>
> $ qemu-system-mipsel -M malta -kernel vmlinux -initrd ramfs.cpio.gz \
> -append "console=ttyS0 root=/dev/ram0 maxcpus=2" -nographic -s \
> -smp 2
>
>
>
> There's no problem whi
On 11/7/2013 8:46 AM, Gerd Hoffmann wrote:
Hi,
As far as the EDID is concerned, there can only be one EDID for a
display+hw pair, or the guest won't know what to do. In my use-case, I
simply pass real EDIDs through, and create a full-screen window for each
real monitor.
Ok, makes sense.
I
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1248427
Title:
whether qemu-img convert will support "-s" option in the newer version
Status
Il 07/11/2013 16:25, Stefano Stabellini ha scritto:
On Thu, 7 Nov 2013, Fabio Fantoni wrote:
Il 06/11/2013 18:16, Stefano Stabellini ha scritto:
On Tue, 5 Nov 2013, Fabio Fantoni wrote:
Il 30/09/2013 16:56, Fabio Fantoni ha scritto:
I'm trying to implement basic spice support on xen pv domUs.
On Thu, Nov 07, 2013 at 02:49:06PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 13:04, Michael S. Tsirkin ha scritto:
> >> > (it follows from this that using the #define anywhere
> >> > except in a memory_region_init() call is probably a bug)
> >> >
> >> > -- PMM
> >
> > BTW how about we change th
Add the minimum of code to prepare the followings patches.
If no node_name is provided to bdrv_new the bs->node_name is set to "undefined".
This will allow to have some default string to communicate in QMP and HMP.
This also make "undefined" a reserved string for bs->node_name.
Signed-off-by: Ben
On Wed, 30 Oct 2013 21:44:12 -0200
Marcelo Tosatti wrote:
> On Wed, Oct 30, 2013 at 08:56:17PM +0100, Igor Mammedov wrote:
> > On Wed, 30 Oct 2013 16:51:29 -0200
> > Marcelo Tosatti wrote:
> >
[...]
>
> > btw: now if QEMU can't allocate hugepages for whole guest size it will
> > fallback
> >
On Thu, 7 Nov 2013, Fabio Fantoni wrote:
> Il 06/11/2013 18:16, Stefano Stabellini ha scritto:
> > On Tue, 5 Nov 2013, Fabio Fantoni wrote:
> > > Il 30/09/2013 16:56, Fabio Fantoni ha scritto:
> > > > I'm trying to implement basic spice support on xen pv domUs.
> > > >
> > > > Test seems ok on Ubu
On Wed, 6 Nov 2013 19:31:19 -0200
Marcelo Tosatti wrote:
>
> v2: condition enablement of new mapping to new machine types (Paolo)
> v3: fix changelog
> v4: rebase
>
> -
>
>
> Align guest physical address and host physical address
> beyond guest 4GB on a 1GB boundary.
>
> Otherwise 1GB TL
On Thu, Nov 07, 2013 at 04:07:34PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 16:05, Michael S. Tsirkin ha scritto:
> >> > So, ack for patch 5-7-8, which should also be enough to fix the problem
> >> > that Luiz reported.
> > Not at all. As long as exec.c ignores high bits, any access
> > there wi
On Thu, Nov 07, 2013 at 07:33:57AM -0700, Alex Williamson wrote:
> On Thu, 2013-11-07 at 12:26 +0200, Michael S. Tsirkin wrote:
> > On Thu, Nov 07, 2013 at 03:32:29PM +0800, Amos Kong wrote:
> > > On Thu, Nov 07, 2013 at 08:59:22AM +0200, Michael S. Tsirkin wrote:
> > > > On Tue, Nov 05, 2013 at 07
Il 06/11/2013 18:16, Stefano Stabellini ha scritto:
On Tue, 5 Nov 2013, Fabio Fantoni wrote:
Il 30/09/2013 16:56, Fabio Fantoni ha scritto:
I'm trying to implement basic spice support on xen pv domUs.
Test seems ok on Ubuntu 12.04 pv domU except mouse which is not visible.
I also tried agent-m
Il 07/11/2013 16:05, Michael S. Tsirkin ha scritto:
>> > So, ack for patch 5-7-8, which should also be enough to fix the problem
>> > that Luiz reported.
> Not at all. As long as exec.c ignores high bits, any access
> there will end up in the wrong region.
... unless it happens to be the correct r
On Thu, Nov 07, 2013 at 03:08:35PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 11:41, Marcel Apfelbaum ha scritto:
> > A bug reported by Luiz Capitulino let us to find
> > several bugs in memory address space setup.
> >
> > One issue is that gdb stub can give us arbitrary addresses
> > and we'll t
As node-name is a separate name space as device-name we can enable it's
definition right now: nobody will use it so no harm involved.
Signed-off-by: Benoit Canet
---
block.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/block.c b/block.c
index 230e71a..132981f 100644
The following series introduce a new file.node-name property in order to be
able to give a name to each BlockDriverState of the graph.
It also define "undefined" as a special value for node-name; a value that will
be
used to indicate to the management that it can not manipulate a node because it
On Wed, Nov 06, 2013 at 10:34:24AM +0100, Stefan Hajnoczi wrote:
> On Tue, Nov 05, 2013 at 08:46:07AM -0700, Eric Blake wrote:
> > On 11/05/2013 07:37 AM, Stefan Hajnoczi wrote:
> >
> > >> +
> > >> +copy = strtol(n1, NULL, 10);
> > >> +if (copy > SD_MAX_COPIES) {
> > >> +return -EI
Sheepdog support two kinds of redundancy, full replication and erasure coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 <= x <= SD_MAX_COPIES)
# create a erasure coded vdi with x data strips and y parity strips
-o redundancy=x:y (x must be one of {2,4,8,16} and 1 <= y <
v6:
- update comment typo
- remove is_number()
v5:
- use pstrcpy instead of strncpy
- fix a segfalt for 'null' string option string
v4:
- fix do_sd_create that forgot to pass nr_copies
- fix parse_redundancy dealing with replicated vdi
v3:
- rework is_numeric
v2:
- fix a typo in comment
We can actually use BDRVSheepdogState *s to pass most of the parameters.
Cc: Kevin Wolf
Cc: Stefan Hajnoczi
Signed-off-by: Liu Yuan
---
block/sheepdog.c | 37 +++--
1 file changed, 15 insertions(+), 22 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepd
On Thu, 2013-11-07 at 12:26 +0200, Michael S. Tsirkin wrote:
> On Thu, Nov 07, 2013 at 03:32:29PM +0800, Amos Kong wrote:
> > On Thu, Nov 07, 2013 at 08:59:22AM +0200, Michael S. Tsirkin wrote:
> > > On Tue, Nov 05, 2013 at 07:17:18PM +0800, Amos Kong wrote:
> > > > We currently just update the HMP
From: "Aneesh Kumar K.V"
With kvm enabled, we store the hash page table information in the hypervisor.
Use ioctl to read the htab contents. Without this we get the below error when
trying to read the guest address
(gdb) x/10 do_fork
0xc0098660 : Cannot access memory at address
0xc00
From: "Aneesh Kumar K.V"
Correctly update the htab_mask using the return value of
KVM_PPC_ALLOCATE_HTAB ioctl. Also we don't update sdr1
on GET_SREGS for HV. So don't update htab_mask if sdr1
is found to be zero. Fix the pte index calculation to be
same as that found in the kernel
Signed-off-by:
From: "Aneesh Kumar K.V"
We will use this in later patches to make sure we use the right load
functions when copying hpte entries.
Signed-off-by: Aneesh Kumar K.V
---
hw/ppc/spapr.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
index 004184d..22f2a8
From: Jeff Cody
This removes the IMGFMT_GENERIC blocker for read-only, so existing
iotests run read/write tests for vhdx images created by qemu-img (e.g.
tests 001, 002, 003).
In addition, this updates the sample image test for the Hyper-V
created image, to verify we can write it as well.
Signe
From: "Aneesh Kumar K.V"
Targets like ppc64 support different typed of KVM, one which use
hypervisor mode and the other which doesn't. Add a new machine
property kvm_type that helps in selecting the respective ones
We also add a new QEMUMachine callback get_vm_type that helps
in mapping the strin
The following should work:
(qemu) drive_add if=none,id=drive0
(qemu) drive_del drive0
(qemu) drive_add if=none,id=drive0
Previous versions of QEMU produced a duplicate ID error because
drive_add leaked the options.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Eric Blake
---
tests/Makefil
From: Jeff Cody
The non-global option output is suppresed in _make_test_img() for
output verification in the 0?? tests. This adds suppression for
the vhdx-unique options as well. This allows check -vhdx to run
successfully.
Signed-off-by: Jeff Cody
Signed-off-by: Stefan Hajnoczi
---
tests/q
Add a qtest qmp() function that returns the response object. This
allows test cases to verify the result or to check for error responses.
It also allows waiting for QMP events.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Eric Blake
Reviewed-by: Andreas Färber
---
tests/libqtest.c | 66 +++
From: Jeff Cody
In preparation for VHDX log support, move these structures to the
header.
Signed-off-by: Jeff Cody
Signed-off-by: Stefan Hajnoczi
---
block/vhdx.c | 52
block/vhdx.h | 48
2 f
On 11/07/2013 12:34 AM, Fam Zheng wrote:
> If backing file doesn't exist, the error message is confusing and
> misleading:
>
>
> This is not intuitive. It's better to have the missing file's name in
> the error message. With this patch:
>
> $ qemu-io -c 'read 0 512' /tmp/a.qcow2
> qemu-
1 - 100 of 193 matches
Mail list logo
