From: Federico Simoncelli
Signed-off-by: Federico Simoncelli
Signed-off-by: Paolo Bonzini
---
blockdev.c | 63 ++
hmp-commands.hx | 16 +
hmp.c| 11 +
hmp.h|1 +
qapi-schema.json |
On 03/06/12 08:56, Alon Levy wrote:
> On Tue, Mar 06, 2012 at 08:36:34AM +0100, Gerd Hoffmann wrote:
>> Hi,
>>
How would the parallel execution facility be opaque to the implementer?
screendump returns, screendump_async needs to pass a closure. You can
automatically generate any am
Il 06/03/2012 08:16, Mark Wu ha scritto:
> It seems we need a name for the union to reference its member.
What version is your compiler?
> So I
> modified the scripts as the following patch. I also updated blockdev.c
> accordingly. After that I can compile it without error. Actually, I
> don't kn
On 03/05/12 18:22, Marc-André Lureau wrote:
> This allows a Spice client to identify a VM
Patch added to spice patch queue.
thanks,
Gerd
Anthony Liguori writes:
> On 03/05/2012 04:53 PM, Stefano Stabellini wrote:
>> On Mon, 5 Mar 2012, Anthony Liguori wrote:
>>> On 02/28/2012 05:46 AM, Julien Grall wrote:
Hello,
In the current model, only one instance of qemu is running for each
running HVM
domain.
>
Il 06/03/2012 09:19, Mark Wu ha scritto:
> gcc -v
> Using built-in specs.
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info
> --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap
> --enable-shared --enable
QSIMPLEQ_FOREACH will use the states pointer after the loop has freed it.
Signed-off-by: Paolo Bonzini
---
Found while (re)reviewing Jeff's patches.
blockdev.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index 1fb2a17..9480dbb 1006
Il 05/03/2012 18:35, Avi Kivity ha scritto:
>>> > > The I/O handlers would still use the qemu mutex, no? we'd just protect
>>> > > the select() (taking the mutex from before releasing the global lock,
>>> > > and reacquiring it afterwards).
>> >
>> > Yes, that could work, but it is _really_ ugly.
On Tue, Mar 06, 2012 at 09:10:00AM +0100, Gerd Hoffmann wrote:
> On 03/06/12 08:56, Alon Levy wrote:
> > On Tue, Mar 06, 2012 at 08:36:34AM +0100, Gerd Hoffmann wrote:
> >> Hi,
> >>
> How would the parallel execution facility be opaque to the implementer?
> screendump returns, screendum
> I got the following error when I tried to compile it:
> blockdev.c: In function ‘qmp_blockdev_snapshot_sync’:
> blockdev.c:664: error: unknown field ‘blockdev_snapshot_sync’
> specified in initializer
> cc1: warnings being treated as errors
> blockdev.c:664: error: missing braces around initializ
On Sat, Mar 03, 2012 at 05:43:48PM +1100, ronnie sahlberg wrote:
> Yes,
>
> Very unfortuante since libiscsi is such a nice name for a
> multiplatform library what even works on win32 :-(
>
> I have so renamed it to libiscsiclient and sent a patch to qemu to
> this list to use -liscsiclient inste
On Sat, Mar 03, 2012 at 03:54:19PM +0400, Michael Tokarev wrote:
> On 03.03.2012 15:15, Andreas Färber wrote:
> > Am 03.03.2012 07:43, schrieb ronnie sahlberg:
> >> Yes,
> >>
> >> Very unfortuante since libiscsi is such a nice name for a
> >> multiplatform library what even works on win32 :-(
> >>
On 2012-03-06 08:49, Liu, Jinsong wrote:
> Jan,
>
> Any comments? I feel some confused about your point 'disable cpuid feature
> for older machine types by default': are you planning a common approach for
> this common issue, or, you just ask me a specific solution for the tsc
> deadline timer
Am 05.03.2012 19:10, schrieb Stefan Hajnoczi:
> Monitor operations that manipulate image files must not execute while a
> background job (like image streaming) is in progress. This prevents
> corruptions from happening when two pieces of code are manipulating the
> image file without knowledge of
On 06.03.2012 14:07, Daniel P. Berrange wrote:
> On Sat, Mar 03, 2012 at 03:54:19PM +0400, Michael Tokarev wrote:
>> It looks like iscsi-initiator-utils package in fedora is built using
>> shared libiscsi which appears to be package-specific, e.g.
>
> Yes, it is the iscsi-initiator-utils package
>
Sorry about this.
First, libiscsi is a really good name for a general purpose
multiplatform library, like libiscsi.
Second, a generic name like this is a horribly poor idea for a single
distribution/ single use / obscure private library.
I want to solve a problem to make it available on all pl
On Tue, Mar 06, 2012 at 10:06:38PM +1100, ronnie sahlberg wrote:
> Sorry about this.
>
> First, libiscsi is a really good name for a general purpose
> multiplatform library, like libiscsi.
> Second, a generic name like this is a horribly poor idea for a single
> distribution/ single use / obscure
The last memory core series completely clobbered -vga std, which has
been annoying people, especially those that have it as the default
adapter. This patchset fixes the problem.
Please pull from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/urgent
On 03/06/2012 01:18 PM, Avi Kivity wrote:
> The last memory core series completely clobbered -vga std, which has
> been annoying people, especially those that have it as the default
> adapter. This patchset fixes the problem.
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/virt/kvm/qemu-k
On Mon, 05 Mar 2012 20:44:39 +0100
Paolo Bonzini wrote:
> Il 05/03/2012 19:55, Eric Blake ha scritto:
> > Right now, libvirt has an API virDomainSnapshotCreateXML with a flag
> > VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT, which should map to this new mode
> > operand. Am I guaranteed that if I pass a
qemu-img resize has some limitations with qcow2, but the user is only
told that "this image format does not support resize". Quite confusing,
so add some more detailed error_report() calls and change "this image
format" into "this image".
Signed-off-by: Kevin Wolf
---
block/qcow2.c |3 +++
q
On 03/06/2012 12:06 PM, ronnie sahlberg wrote:
> Sorry about this.
>
> First, libiscsi is a really good name for a general purpose
> multiplatform library, like libiscsi.
> Second, a generic name like this is a horribly poor idea for a single
> distribution/ single use / obscure private library.
virtio_load checks features that are enabled by the guest and
blocks migration if they are not available in the destination
host. However, in some cases we can let features through because
we know that guests will be able to proceed even without it.
The patch is on top of Orit's at
http://permali
The guest must already be prepared to see SG_IO support
disappear from under its feet, for example if migration
refers to a block device on the source and file-based
storage on the destination; or more likely, if the source
kernel allows (gasp) SG_IO on a partition and the destination
does not. So
It is not a problem if the destination does not have
VIRTIO_BALLOON_F_MUST_TELL_HOST. In that case, the guest
will simply do useless virtqueue traffic, but the destination
does not have a problem.
(In fact, it _is_ a problem if the destination has
VIRTIO_BALLOON_F_MUST_TELL_HOST but the source do
virtio_load checks features that are enabled by the guest and
blocks migration if they are not available in the destination
host. However, in some cases we can let features through because
we know that guests will be able to proceed even without it.
Signed-off-by: Paolo Bonzini
---
hw/virtio-ba
This was a long pending bug, now revealed by the assert in
phys_page_find that stumbled over the large page index returned by
cpu_get_phys_page_debug for NX-marked pages.
Signed-off-by: Jan Kiszka
---
Was easily triggerable by attaching gdb to the guest and doing some
backtraces that reached int
On Tue, 06 Mar 2012 08:36:34 +0100
Gerd Hoffmann wrote:
> Hi,
>
> >> How would the parallel execution facility be opaque to the implementer?
> >> screendump returns, screendump_async needs to pass a closure. You can
> >> automatically generate any amount of code, but you can only have a
> >> s
On Mon, 5 Mar 2012, Evgeny Voevodin wrote:
>
> As I understand, your approach removes linking back to the previous allocated
> chunk to avoid usage of already allocated and used memory again. Also you
> added g_free() to tcg_pool_reset(). Wouldn't it slow down emulation?
No, it would not. I a
On 03/06/2012 02:23 PM, Jan Kiszka wrote:
> This was a long pending bug, now revealed by the assert in
> phys_page_find that stumbled over the large page index returned by
> cpu_get_phys_page_debug for NX-marked pages.
>
> Signed-off-by: Jan Kiszka
> ---
>
> Was easily triggerable by attaching gdb
On Mon, Mar 5, 2012 at 4:44 PM, Martin Mailand wrote:
> Am 05.03.2012 17:35, schrieb Stefan Hajnoczi:
>
>>> 1. Test on i7 Laptop with Cpu governor "ondemand".
>>> >
>>> > v0.14.1
>>> > bw=63492KB/s iops=15873
>>> > bw=63221KB/s iops=15805
>>> >
>>> > v1.0
>>> > bw=36696KB/s iops=9173
>>> > b
On 03/06/2012 02:56 PM, Avi Kivity wrote:
> > diff --git a/target-i386/helper.c b/target-i386/helper.c
> > index af6bba2..40fe407 100644
> > --- a/target-i386/helper.c
> > +++ b/target-i386/helper.c
> > @@ -947,7 +947,7 @@ target_phys_addr_t cpu_get_phys_page_debug(CPUState
> > *env, target_ulong
Fixed by
http://git.qemu.org/?p=qemu.git;a=commit;h=5ca2358ac895139e624881c5b3bf3095d3cc4515
usb-desc: fix user trigerrable segfaults (!config)
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subs
On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> On Tue, 06 Mar 2012 08:36:34 +0100
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > >> How would the parallel execution facility be opaque to the implementer?
> > >> screendump returns, screendump_async needs to pass a closure. You can
On Fri, Mar 02, 2012 at 04:49:44PM +0100, Hans de Goede wrote:
Ack. Anthony, this breaks build for libcacard, caused by my last commit
to the same file as Brad noted:
commit 0082f4336e128a17d5f34e01de0fd29930e99b0d
Author: Alon Levy
Date: Sun Feb 26 17:09:24 2012 +0100
lib
On Tue, Mar 06, 2012 at 01:22:05PM +0100, Paolo Bonzini wrote:
> virtio_load checks features that are enabled by the guest and
> blocks migration if they are not available in the destination
> host. However, in some cases we can let features through because
> we know that guests will be able to pr
On Tue, Mar 6, 2012 at 11:48 AM, Kevin Wolf wrote:
> qemu-img resize has some limitations with qcow2, but the user is only
> told that "this image format does not support resize". Quite confusing,
> so add some more detailed error_report() calls and change "this image
> format" into "this image".
On Mon, Mar 05, 2012 at 06:34:51PM +, Blue Swirl wrote:
> On Sun, Mar 4, 2012 at 22:29, Michael S. Tsirkin wrote:
> > On Sun, Mar 04, 2012 at 09:54:02PM +, Blue Swirl wrote:
> >> >> 19.3.1.10 tells that the header type is 0, as you noted too. Still,
> >> >> the register layout matches brid
On 03/06/2012 07:16 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
On Tue, 06 Mar 2012 08:36:34 +0100
Gerd Hoffmann wrote:
Hi,
How would the parallel execution facility be opaque to the implementer?
screendump returns, screendump_async needs to pass
On Tue, 06 Mar 2012 07:51:29 -0600
Anthony Liguori wrote:
> On 03/06/2012 07:16 AM, Alon Levy wrote:
> > On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> >> On Tue, 06 Mar 2012 08:36:34 +0100
> >> Gerd Hoffmann wrote:
> >>
> >>>Hi,
> >>>
> > How would the parallel execu
Il 06/03/2012 14:33, Michael S. Tsirkin ha scritto:
>> > virtio_load checks features that are enabled by the guest and
>> > blocks migration if they are not available in the destination
>> > host. However, in some cases we can let features through because
>> > we know that guests will be able to p
06.03.2012 15:15, Daniel P. Berrange wrote:
On Tue, Mar 06, 2012 at 10:06:38PM +1100, ronnie sahlberg wrote:
Sorry about this.
First, libiscsi is a really good name for a general purpose
multiplatform library, like libiscsi.
Second, a generic name like this is a horribly poor idea for a single
Anthony: do you plan to apply this soon?
Andre: can you help to review the Opteron_G4 model?
Donald, Xiantao: can you help to review the SandyBridge model?
On Mon, Feb 27, 2012 at 04:33:11PM -0300, Eduardo Habkost wrote:
> This series add two new CPU models to Qemu: Intel SandyBridge and AMD
>
This was a long pending bug, now revealed by the assert in
phys_page_find that stumbled over the large page index returned by
cpu_get_phys_page_debug for NX-marked pages: We need to mask out NX and
all user-definable bits 52..62 from PDEs and the final PTE to avoid
corrupting physical addresses.
S
On 03/06/2012 03:57 PM, Paolo Bonzini wrote:
> Il 06/03/2012 14:33, Michael S. Tsirkin ha scritto:
virtio_load checks features that are enabled by the guest and
blocks migration if they are not available in the destination
host. However, in some cases we can let features through bec
On Tue, Mar 06, 2012 at 10:53:42AM -0300, Luiz Capitulino wrote:
> On Tue, 06 Mar 2012 07:51:29 -0600
> Anthony Liguori wrote:
>
> > On 03/06/2012 07:16 AM, Alon Levy wrote:
> > > On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> > >> On Tue, 06 Mar 2012 08:36:34 +0100
> > >> Ger
Hi Martin,
On 05.03.2012 17:13, Martin Mailand wrote:
> Am 10.02.2012 15:36, schrieb Dongsu Park:
> >Recently I observed performance regression regarding virtio-blk,
> >especially different IO bandwidths between qemu-kvm 0.14.1 and 1.0.
> >So I want to share the benchmark results, and ask you what
On 03/06/2012 04:22 PM, Jan Kiszka wrote:
> This was a long pending bug, now revealed by the assert in
> phys_page_find that stumbled over the large page index returned by
> cpu_get_phys_page_debug for NX-marked pages: We need to mask out NX and
> all user-definable bits 52..62 from PDEs and the fi
Juan Quintela wrote:
> Hi
>
> Please send in any agenda items you are interested in covering.
As there are any topic, tomorow call gets cancelled.
Happy hacking, Juan.
On Tue, Mar 06, 2012 at 01:22:07PM +0100, Paolo Bonzini wrote:
> The guest must already be prepared to see SG_IO support
> disappear from under its feet, for example if migration
> refers to a block device on the source and file-based
> storage on the destination; or more likely, if the source
> ke
On Tue, Mar 06, 2012 at 01:22:06PM +0100, Paolo Bonzini wrote:
> It is not a problem if the destination does not have
> VIRTIO_BALLOON_F_MUST_TELL_HOST. In that case, the guest
> will simply do useless virtqueue traffic, but the destination
> does not have a problem.
> (In fact, it _is_ a problem
Il 06/03/2012 15:55, Michael S. Tsirkin ha scritto:
> > It is not a problem if the destination does not have
> > VIRTIO_BALLOON_F_MUST_TELL_HOST. In that case, the guest
> > will simply do useless virtqueue traffic, but the destination
> > does not have a problem.
> > (In fact, it _is_ a problem i
On 03/06/2012 08:23 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 10:53:42AM -0300, Luiz Capitulino wrote:
So cutting off a part of the email is a good way to win arguments? cool
trick.
It doesn't work as well if you acknowledge that was the motivation ;-) (j/k)
I agree a reproducer is a good
On Tue, Mar 06, 2012 at 03:59:53PM +0100, Paolo Bonzini wrote:
> Il 06/03/2012 15:55, Michael S. Tsirkin ha scritto:
> > > It is not a problem if the destination does not have
> > > VIRTIO_BALLOON_F_MUST_TELL_HOST. In that case, the guest
> > > will simply do useless virtqueue traffic, but the des
On 03/06/2012 02:22 AM, Markus Armbruster wrote:
Anthony Liguori writes:
My concern is that this moves the Xen use case pretty far from what
the typical QEMU use case would be (running one emulator per guest).
If it was done in a non-invasive way, maybe it would be acceptable but
at a high le
Il 06/03/2012 16:08, Michael S. Tsirkin ha scritto:
> > > Can't we just add a flag to control this feature?
> >
> > I think the sane thing here would be to remove it from the spec.
>
> I guess we could but what does it buy us?
Not having a broken spec. :)
The pedantically correct thing to do wo
On 29.02.2012 17:02, Michal Privoznik wrote:
> This command returns an array of:
>
> [ifname, hwaddr, [ipaddr, ipaddr_family, prefix] ]
>
> for each interface in the system.
> Currently, only IPv4 and IPv6 are supported.
>
> Signed-off-by: Michal Privoznik
> ---
> diff to v5:
> -another change
Hello dear developers,
I want to use the CPU emulation component of QEMU (user mode) and I'm
running into a bit of a problem that I hope you can help me with or point
me to the right list.
On my x86 Linux VM, I have configured QEMU with:
'--target-list=i386-linux-user' '--cc=/bin/arm-none-linux-
On 03/06/2012 01:33 AM, Paolo Bonzini wrote:
Reviewed-by: Luiz Capitulino
Signed-off-by: Paolo Bonzini
---
qapi-schema-test.json | 10 ++
scripts/qapi-types.py |5 +
scripts/qapi-visit.py | 31 ++-
test-qmp-input-visitor.c | 18 +
In module.c
typedef struct ModuleEntry
{
module_init_type type;
void (*init)(void);
QTAILQ_ENTRY(ModuleEntry) node;
} ModuleEntry;
The field `type` is not set in `register_module_init`. As different types of
modules use their own list, I guess this field is
Hi, I find that in module.c
typedef struct ModuleEntry
{
module_init_type type;
void (*init)(void);
QTAILQ_ENTRY(ModuleEntry) node;
} ModuleEntry;
The field `type` in `ModuleEntry` is not set in
`register_module_init`. As different types of modules use their o
On 03/06/2012 04:31 PM, Paolo Bonzini wrote:
Il 06/03/2012 09:19, Mark Wu ha scritto:
gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-
> I read pci code in qemu about i440fx, pci.c and so on. I think if guest
> os whose mainboard is based on x86, it will use IO instructions to
> access PCI configuration space.If not use passthrough, qemu should
> emulate these operations.I find a function called kvm_handle_io who will
On March 5, 2012 at 11:22 AM Erik Rull wrote:
>
>
>
> On March 2, 2012 at 3:15 PM Gerd Hoffmann wrote:
>
> > > But: This + the latest GIT master causes again my problems with the
> >
> > With or without this one:
> >
> > commit 5ca2358ac895139e624881c5b3bf3095d3cc4515
> > Date: Wed Feb 29 0
On Tue, Mar 06, 2012 at 04:28:20PM +0100, Michal Privoznik wrote:
> On 29.02.2012 17:02, Michal Privoznik wrote:
> > This command returns an array of:
> >
> > [ifname, hwaddr, [ipaddr, ipaddr_family, prefix] ]
> >
> > for each interface in the system.
> > Currently, only IPv4 and IPv6 are suppor
The kvmvapic code remaps a section of ROM as RAM to allow the guest to
maintain state there. It is careful to align the section size to a page
boundary, to avoid creating subpages, but neglects to do the same for
the start address. These leads to an assert later on when the memory
core tries to c
On 03/06/2012 04:14 PM, Paolo Bonzini wrote:
Il 06/03/2012 08:16, Mark Wu ha scritto:
It seems we need a name for the union to reference its member.
What version is your compiler?
So I
modified the scripts as the following patch. I also updated blockdev.c
accordingly. After that I can compile
On 6 March 2012 05:11, Roger Tagged wrote:
> I want to use the CPU emulation component of QEMU (user mode) and I'm
> running into a bit of a problem that I hope you can help me with or point me
> to the right list.
Which version of QEMU are you using?
> On my x86 Linux VM, I have configured QEMU
On Tue, Mar 06, 2012 at 07:51:29AM -0600, Anthony Liguori wrote:
> On 03/06/2012 07:16 AM, Alon Levy wrote:
> >On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> >>On Tue, 06 Mar 2012 08:36:34 +0100
> >>Gerd Hoffmann wrote:
> >>
> >>> Hi,
> >>>
> >How would the parallel execu
Il 06/03/2012 15:53, Michael S. Tsirkin ha scritto:
> > The guest must already be prepared to see SG_IO support
> > disappear from under its feet, for example if migration
> > refers to a block device on the source and file-based
> > storage on the destination; or more likely, if the source
> > ker
On 2012-03-06 16:50, Avi Kivity wrote:
> The kvmvapic code remaps a section of ROM as RAM to allow the guest to
> maintain state there. It is careful to align the section size to a page
> boundary, to avoid creating subpages, but neglects to do the same for
> the start address. These leads to an
On Tue, Mar 06, 2012 at 05:56:49PM +0200, Alon Levy wrote:
> On Tue, Mar 06, 2012 at 07:51:29AM -0600, Anthony Liguori wrote:
> > On 03/06/2012 07:16 AM, Alon Levy wrote:
> > >On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> > >>On Tue, 06 Mar 2012 08:36:34 +0100
> > >>Gerd Hoffma
I'm using the QEMU sources from 0.15.1.
I will try the --cross-prefix option. I have a feeling this will do it. I
know that the prologue is being initialized with the i386 target backend
because the debugger shows me the name of the file and it is
tcg/i386/tcg-target.c. Further more, the cod
it seems that g_main_context_default creates a semaphore which is added
into rfds passed to glib_select_fill function, that's why select fails.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/916720
Ti
On 6 March 2012 16:09, Roger wrote:
> I will try the --cross-prefix option. I have a feeling this
> will do it. I know that the prologue is being initialized with
> the i386 target backend
> I'll also try the --cpu option recommended by the previous poster.
Yes, this should force the host CPU
On 03/06/2012 09:56 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 07:51:29AM -0600, Anthony Liguori wrote:
On 03/06/2012 07:16 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
On Tue, 06 Mar 2012 08:36:34 +0100
Gerd Hoffmann wrote:
Hi,
How would the
On Tue, Mar 06, 2012 at 10:16:42AM -0600, Anthony Liguori wrote:
> On 03/06/2012 09:56 AM, Alon Levy wrote:
> >On Tue, Mar 06, 2012 at 07:51:29AM -0600, Anthony Liguori wrote:
> >>On 03/06/2012 07:16 AM, Alon Levy wrote:
> >>>On Tue, Mar 06, 2012 at 09:24:27AM -0300, Luiz Capitulino wrote:
> On
On 03/06/2012 10:26 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 10:16:42AM -0600, Anthony Liguori wrote:
On 03/06/2012 09:56 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 07:51:29AM -0600, Anthony Liguori wrote:
On 03/06/2012 07:16 AM, Alon Levy wrote:
On Tue, Mar 06, 2012 at 09:24:27AM -0300
On Thu, Mar 1, 2012 at 2:56 AM, Dong Xu Wang wrote:
> diff --git a/block/add-cow-cache.c b/block/add-cow-cache.c
> new file mode 100644
> index 000..6be02ff
> --- /dev/null
> +++ b/block/add-cow-cache.c
> @@ -0,0 +1,171 @@
> +/*
> + * Cache For QEMU ADD-COW Disk Format
> + *
> + * Copyright IB
On 03/06/2012 06:22 AM, Paolo Bonzini wrote:
The guest must already be prepared to see SG_IO support
disappear from under its feet, for example if migration
refers to a block device on the source and file-based
storage on the destination; or more likely, if the source
kernel allows (gasp) SG_IO o
Il 06/03/2012 18:03, Anthony Liguori ha scritto:
> I don't know how comfortable I feel about this.
>
> You can't just remove a feature in flight. The guest is going to behave
> differently in such a way that the host isn't expecting. Yes, it should
> fail gracefully, but nonetheless it will fail
Hello,
I'm reacting a bit later but I have a trouble with an old DOS OS from Digital
Research called Concurrent DOS.
It worked fine till Qemu v0.11.1.
I tried it with a lot of versions from 0.12.0 to 1.0.1 and it boot correctly.
But after a key pressed, I can't use the keyboard any more. The sys
On 03/06/2012 11:12 AM, Paolo Bonzini wrote:
Il 06/03/2012 18:03, Anthony Liguori ha scritto:
I don't know how comfortable I feel about this.
You can't just remove a feature in flight. The guest is going to behave
differently in such a way that the host isn't expecting. Yes, it should
fail gr
On Mon, Feb 27, 2012 at 04:33:13PM -0300, Eduardo Habkost wrote:
> - ffxsr: untested, so not enabled
[...]
> extfeature_edx:
> Opteron_G3: lm rdtscp fxsr mmxnx pse36 pat cmov mca
> pge mtrr syscall apic cx8 mce pae msr tsc pse de fpu
> full: lm rdtscp pdpe1gb ff
..and why we got to this situation.
(per Anthony's request, and if you'll excuse the puny attempt to write
biblically, a new beginning)
In the begining there was screendump. It was a synchronous monitor
command. Libvirt said: I want a screendump. And qemu waited for the vga
device to produce it.
>From original patch with Patchwork-id: 31110 by
Stefan Hajnoczi
"Add a flag to indicate that incoming migration is pending and care needs
to be taken for data consistency. Block drivers should not modify the
image file before incoming migration is complete since the migration
source host is sti
This function will help to inform the block layer that an incoming
live migration is coming in order to make proper usage of the
BDRV_O_INCOMING flag.
Signed-off-by: Benoit Canet
---
block.c |8
block.h |2 ++
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/block
Open images with BDRV_O_INCOMING in order to inform block drivers
that an incoming live migration is coming.
Signed-off-by: Benoit Canet
---
block.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/block.c b/block.c
index b0f0288..78287df 100644
--- a/block.c
+++ b/blo
Reviewed-by: Luiz Capitulino
Signed-off-by: Paolo Bonzini
---
qapi-schema-test.json | 10 ++
scripts/qapi-types.py |6 ++
scripts/qapi-visit.py | 31 ++-
test-qmp-input-visitor.c | 18 ++
test-qmp-output-visitor.c |
>From original commit is Patchwork-id: 31108 by
Stefan Hajnoczi
"The QED image format includes a file header bit to mark images dirty.
QED normally checks dirty images on open and fixes inconsistent
metadata. This is undesirable during live migration since the dirty bit
may be set if the source
From: Federico Simoncelli
Signed-off-by: Federico Simoncelli
Signed-off-by: Paolo Bonzini
---
blockdev.c | 63 ++
hmp-commands.hx | 16 +
hmp.c| 11 +
hmp.h|1 +
qapi-schema.json |
Signed-off-by: Eduardo Habkost
---
target-i386/cpuid.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/target-i386/cpuid.c b/target-i386/cpuid.c
index c2edb64..465ea15 100644
--- a/target-i386/cpuid.c
+++ b/target-i386/cpuid.c
@@ -50,7 +50,7 @@ static const char *ext_fea
This patches add the definition of a SandyBridge CPU model.
Summary of differences:
Flags present on actual hardware, but not on the added model definition:
- pbe, tm, ht, ss, acpi, vme, xTPR, tm2, eist, smx: host-specific
features, not exposed to guest.
- ds, ds-cpl, dtes64, pdcm: emulation n
Too many VM kittens were killed since 7d03f82f81. Another one just died
under my fat fingers.
When you quit a kgdb session, does the Linux kernel power off? Or when
you terminate gdb attached to a hardware debugger, does your board
vanish in space? No.
So let's stop terminating QEMU when the gdbs
This patch will allow to do a post incoming live migration check
on QED images and keep invalidating caches on qcow2 images.
Signed-off-by: Benoit Canet
---
block.c | 10 +-
block.h |8 +---
block/qcow2.c |7 ++-
block_int.h |4 ++--
migration.c |
v4 includes Federico's drive-reopen (patch 10) command, fixes another
small bug in Jeff's code (patch 2), and tweaks the union handling for
older compilers.
v3 tested with the following scenarios, v4 only d/e:
a) mirror only
1) create base.qcow2 and starat QEMU with it
2) Execute the following
Hi all,
I've been looking at trying to fix some outstanding OpenBIOS bug reports
and come across a serious performance regression with regard to VGA/VNC
updates on qemu-system-ppc. In particular, I've been looking at Any
ideas gratefully received.Any ideas gratefully received.trying to create
On 2 March 2012 11:35, Igor Mitsyanko wrote:
> Create 9 exynos4210 i2c interfaces.
>
> Signed-off-by: Igor Mitsyanko
> +#define EXYNOS4_I2C(obj) \
> +OBJECT_CHECK(Exynos4210I2CState, (obj), TYPE_EXYNOS4_I2C)
> +#define EXYNOS4_I2C_SLAVE(obj) \
> +OBJECT_CHECK(Exynos42
Current code depends on variables defined in config-host.mak before it is
actually included.
Signed-off-by: Lluís Vilanova
Cc: Anthony Liguori
Cc: Paul Brook
---
Makefile | 15 ---
1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/Makefile b/Makefile
index 49c775b..4
On 2 March 2012 11:35, Igor Mitsyanko wrote:
> Function name type_class_init() gave us a wrong impression of separation
> of type's "class" and "object" entities initialization. Name type_initialize()
> is more appropriate for type_class_init() function (considering what
> operations
> it perform
1 - 100 of 171 matches
Mail list logo
