Split out read and write functions.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 53 +++--
block/trace-events | 4 ++--
2 files changed, 41 insertions(+), 16 deletions(-)
diff --git a/block/backup.c b/block/backup.c
in
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/iotests.py | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/iotests.py b/tests/qemu-iotests/iotests.py
index bec8eb4..a5ef9c3 100644
--- a/tests/qemu-iotests/iotests.py
+++ b/tests/qemu-
Merge top/full/incremental modes backup into one backup_loop.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 41 +
1 file changed, 9 insertions(+), 32 deletions(-)
diff --git a/block/backup.c b/block/backup.c
index e2b944a..2afd1b6 10064
We should not copy non-dirty clusters in write notifiers. So,
initialize copy_bitmap from sync_bitmap.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 32 +++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/block/backup.c b/block/backup
Hi everyone,
I am pleased to announce that the QEMU v2.7.1 stable release is now
available:
http://wiki.qemu.org/download/qemu-2.7.1.tar.bz2
v2.7.1 is now tagged in the official qemu.git repository,
and the stable-2.7 branch has been updated accordingly:
http://git.qemu.org/?p=qemu.git;a=sh
TOP backup mode skips not allocated clusters. This patch mark skipped
clusters in copy_bitmap to prevent their writing in write notifier
(however, they may be written before skipping, but that is not
critical).
Also, update job->common.offset appropriately, to come eventually to
job->common.len.
We can use copy_bitmap instead of sync_bitmap. copy_bitmap is
initialized from sync_bitmap and it is more informative: we will not try
to process data, that is already in progress (by write notifier).
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 58 +++
Set fake progress for non-dirty clusters in copy_bitmap initialization,
to:
1. set progress in the same place where corresponding clusters are
consumed from copy_bitmap (or not initialized, as here)
2. earlier progress information for user
3. simplify the code
Signed-off-by: Vladimir Sementsov-Ogi
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Pavel Butsykin
---
include/qemu/bitmap.h | 4
util/bitmap.c | 27 +++
2 files changed, 31 insertions(+)
diff --git a/include/qemu/bitmap.h b/include/qemu/bitmap.h
index 63ea2d0..3bfc33e 100644
--- a/i
Add this function only for HBitmap's with greanularity = 0.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Pavel Butsykin
---
include/qemu/hbitmap.h | 2 ++
util/hbitmap.c | 9 +
2 files changed, 11 insertions(+)
diff --git a/include/qemu/hbitmap.h b/include/qemu/hbit
To simplify things make all reads not serializing, not only from
notifiers. This is needed because after the following patch, there would
not be strong division between reads from notifiers or not - they all
would be called from one place.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/ba
On 23/12/2016 16:12, Michal Suchanek wrote:
> This copies the timer hack from ui/console.c kbd_send_chars to ui/gtk.c
> gd_vc_in.
>
> There is no fd-like object to peek repatedly so the paste data is saved
> in a free-floating buffer only submitted to gtk_timeout_add. Multiple
> pastes can poten
New async scheme: all copying is done by worker coroutines. Main
block-job coroutine serves initial skipping of unallocated clusters, and
also all pauses, error handling, throttling.
Notifiers just mark clusters as awaited (by adding NotifierRequest to
the list) and wait for some time (5 sec) for
Make dirty iter resistant to resetting bits in corresponding HBitmap.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/qemu/hbitmap.h | 24 ++--
util/hbitmap.c | 23 ++-
2 files changed, 24 insertions(+), 23 deletions(-)
diff --git a/includ
Use HBitmap copy_bitmap instead of done_bitmap. This is needed to unify
backup loop for full/incremental modes in future patches.
We reset bit of the copy_bitmap immediately after checking it in
backup_do_cow(). It is safe, because all other intersecting requests
will wait for our request finish a
Public bug reported:
Trying to boot a Cirros (minimal Linux) VM with qemu 2.6.0 and libvirt
2.0.0 in TCG mode fails for me. The VM gets stuck in "Starting up ..."
and never moves on. The command line used to boot the VM was:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUD
The Cirros image has a 3.2.0 kernel, in case it helps.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1652333
Title:
TCG mode fails to boot Linux kernel with qemu 2.6.0 and libvirt 2.0.0
Status in
This copies the timer hack from ui/console.c kbd_send_chars to ui/gtk.c
gd_vc_in.
There is no fd-like object to peek repatedly so the paste data is saved
in a free-floating buffer only submitted to gtk_timeout_add. Multiple
pastes can potentially interleave if qemu blocks for long or the user
past
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 30 ++
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/block/backup.c b/block/backup.c
index 900bbd3..b79a481 100644
--- a/block/backup.c
+++ b/block/backup.c
@@ -383,19 +383,24 @@ static
Call backup_copy_cluster directly from backup_worker_co. Move io buffer
allocation to backup_worker_co (and do not reallocate it for each
cluster).
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 28 +---
block/trace-events | 6 ++
2 files change
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20161223151253.21338-1-msucha...@suse.de
Subject: [Qemu-devel] [RFC PATCH] Fix pasting into serial console in GTK ui
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
tota
This copies the timer hack from ui/console.c kbd_send_chars to ui/gtk.c
gd_vc_in.
There is no fd-like object to peek repatedly so the paste data is saved
in a free-floating buffer only submitted to gtk_timeout_add. Multiple
pastes can potentially interleave if qemu blocks for long or the user
past
On 3.4.0 or later, send GDK_SCROLL_SMOOTH event, instead of
GDK_SCROLL_UP/DOWN.
This fixes it by converting any smooth scroll to up/down.
(I.e. without smooth support)
Signed-off-by: OGAWA Hirofumi
---
ui/gtk.c | 10 ++
1 file changed, 10 insertions(+)
diff -puN ui/gtk.c~mouse-wheel
Considering that Easter is on April 16th, we'd probably want to have the
release before that date even in case of a slip.
On the other hand, the Christmas / New Year break here means that we'll
have to make the development time 1-2 week shorter in practice.
2016-02-21 2.9 soft freeze
2016-03-
From: Corey Minyard
Macro parameters should almost always have () around them when used.
llvm reported an error on this.
Remove redundant parenthesis and put parenthesis around the entire
macros with assignments in case they are used in an expression.
Remove some unused macros.
Reported in htt
With "ps2: use QEMU qcodes instead of scancodes", key handling was
changed to qcode base. But all scancodes are not converted to new one.
This adds some missing qcodes what I found in using.
Signed-off-by: OGAWA Hirofumi
---
hw/input/ps2.c|3 +++
qapi-schema.json |3 ++-
ui/input
On Fri, Dec 23, 2016 at 11:25:18AM +0100, Thomas Huth wrote:
> On 23.12.2016 10:20, Kashyap Chamarthy wrote:
[...]
> > Yes, I can confirm that I have downloaded the ISO from the
> > official website -- it's a nightly build of their
> > SVN revision 6766.
>
> OK, as far as I can see, the issue
On 23 December 2016 at 12:12, Paolo Bonzini wrote:
> On 23/12/2016 12:15, Peter Maydell wrote:
>> Applied, thanks. (Nice to see that git is smart enough to
>> be able to merge this on top of the earlier target-* rename.)
>
> Actually I did the rebase myself.
Oops, so you did; I was confused, clea
On 23/12/2016 12:15, Peter Maydell wrote:
>> * core support for MemoryRegionCache from myself
>> * rules.mak speedup and cleanups from myself and Marc-Adnré
>> * multiboot command line fix from Vlad
>> * SCSI fixes from myself
>> * small qemu-timer speedup from myself
>> * x86 debugging improveme
Public bug reported:
I noticed when I ran 'man qemu' for version 2.8.0 I am getting this back
at the terminal;
:1674: warning [p 1, 188.5i, div `an-div', 0.2i]: can't break
line
:1677: warning [p 1, 188.8i, div `an-div', 0.2i]: can't break
line
** Affects: qemu
Importance: Undecided
LOL TYPO here;
https://bugs.launchpad.net/qemu/+bug/1649040
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1649042
Title:
Ubuntu 16.04.1 LightDM Resolution Not Correct
Status in QEMU:
New
Bug d
Hi I'll just post to here for both issues;
https://bugs.launchpad.net/qemu/+bug/1649042
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1649042
Title:
Ubuntu 16.04.1 LightDM Resolution Not Correct
On 22 December 2016 at 09:42, Peter Xu wrote:
> Hello,
>
> Since this is a general topic, I picked it out from the VT-d
> discussion and put it here, just want to be more clear of it.
>
> The issue is, whether we have exposed too much address spaces for
> emulated PCI devices?
>
> Now for each PCI
I switched to boot scsi and when I start it, the screen is just blank...
qemu-system-x86_64 -drive
if=none,id=hd,cache=none,aio=threads,format=raw,file=ubuntu.img,index=0 \
-object iothread,id=iothread0 \
-machine type=q35,accel=kvm,kernel_irqchip=on \
-device virtio-scsi-pci,iothread=iothread0,
On 22 December 2016 at 15:22, Paolo Bonzini wrote:
> The following changes since commit d1e8e8ecc3d2a1a72504912d671f1cbbac1b06e5:
>
> Merge remote-tracking branch 'remotes/huth/tags/target-dirs-20161220' into
> staging (2016-12-21 21:11:48 +)
>
> are available in the git repository at:
>
>
It's the same in 2.8.0 but I will test it again when I get some time for
vmware.
I used vmware because it offers better resolution.
After posting this issue I have learned a little about virtio and for a
few times I was able to boot it with -vag virtio and this was really
nice. I was able to resi
On 23.12.2016 10:20, Kashyap Chamarthy wrote:
> [...]
>
>> On 22.12.2016 18:37, vilca...@gmail.com wrote:
>>> Hi, just letting you know that Avira found some crypto-locker virus in
>>> ColibriOS iso that you featured in QEMU Advent Calendar 2016. Maybe you
>>> should look into that. I am not sure
Marc-André Lureau writes:
> Add a qapi2texi script to generate the documentation from the qapi
> schemas.
>
> The SQUASHED patch in this series is a squashed version of the
> documentation move from qmp-commands.txt to the schemas. The whole
> version (not sent on the ML to avoid spamming) is in
[...]
> On 22.12.2016 18:37, vilca...@gmail.com wrote:
> > Hi, just letting you know that Avira found some crypto-locker virus in
> > ColibriOS iso that you featured in QEMU Advent Calendar 2016. Maybe you
> > should look into that. I am not sure if it’s a false positive or not.. You
> > can check
- Original Message -
> From: "Markus Armbruster"
> To: "Paolo Bonzini"
> Cc: "Eduardo Habkost" , "Peter Maydell"
> , "Fam Zheng"
> , "QEMU Developers"
> Sent: Friday, December 23, 2016 10:02:33 AM
> Subject: Re: [Qemu-devel] [RFC PATCH 00/11] Stubs cleanup
>
> Paolo Bonzini writes:
Paolo Bonzini writes:
> On 22/12/2016 18:42, Eduardo Habkost wrote:
>> On Thu, Dec 22, 2016 at 06:32:24PM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 22/12/2016 18:30, Peter Maydell wrote:
On 22 December 2016 at 15:59, Paolo Bonzini wrote:
> This moves out of libqemustub.a those function
On 22.12.2016 18:37, vilca...@gmail.com wrote:
> Hi, just letting you know that Avira found some crypto-locker virus in
> ColibriOS iso that you featured in QEMU Advent Calendar 2016. Maybe you
> should look into that. I am not sure if it’s a false positive or not.. You
> can check the attachmen
Please do not report distribution specific bugs (since you're using
qemu-kvm 2.0.0+dfsg-2ubuntu1.27) against the QEMU project bugtracker -
use the distribution's bugtracker instead.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
101 - 143 of 143 matches
Mail list logo
