Ram Pai schrieb:
> Copying the qemu-devel mailing list too.
>
> On Wed, 2009-06-24 at 09:58 -0700, Ram Pai wrote:
>> Problem: It is impossible to feed filenames with the character colon because
>> qemu interprets such names as a protocol. For example a filename scsi:0,
>> is interpreted as a pro
Ram Pai schrieb:
> On Thu, 2009-06-25 at 11:14 +0200, Kevin Wolf wrote:
>> Ram Pai schrieb:
>>> Copying the qemu-devel mailing list too.
>>>
>>> On Wed, 2009-06-24 at 09:58 -0700, Ram Pai wrote:
>>>> Problem: It is impossible to feed filenames w
Ram Pai schrieb:
> Problem: It is impossible to feed filenames with the character colon because
> qemu interprets such names as a protocol. For example a filename scsi:0, is
> interpreted as a protocol by name "scsi".
>
> This patch allows user to espace colon characters. For example the above
> f
Avi Kivity schrieb:
> The qcow block driver format is no longer maintained and likely contains
> serious data corruptors. Urge users to stay away for it, and advertise
> the new and improved replacement.
>
> Signed-off-by: Avi Kivity
vvfat is using qcow internally, so the warning will appear th
Amit Shah schrieb:
> On (Mon) Jun 29 2009 [17:04:49], Avi Kivity wrote:
>> The qcow block driver format is no longer maintained and likely contains
>> serious data corruptors. Urge users to stay away for it, and advertise
>> the new and improved replacement.
>
> Does this also print the message a
Anthony Liguori schrieb:
> Kevin Wolf wrote:
>> Avi Kivity schrieb:
>>
>>> The qcow block driver format is no longer maintained and likely contains
>>> serious data corruptors. Urge users to stay away for it, and advertise
>>> the new and improved repl
Michael S. Tsirkin schrieb:
> This fixes segfault reported by Kevin Wolf,
> and simplifies the code in msix_save.
>
> Reported-by: Kevin Wolf
> Signed-off-by: Michael S. Tsirkin
I can confirm that this fixes the segfault for me.
Kevin
--
To unsubscribe from this list
Andreas Färber schrieb:
> I'm confused now. Only recently someone stepped up, saying that qcow2
> was broken and that qcow should be used instead for safety reasons.
> Now all of a sudden, it's the exact opposite, you're even considering
> replacing qcow with qcow2 for vvfat and dropping qcow
Ram Pai schrieb:
> Problem: It is impossible to feed filenames with the character colon because
> qemu interprets such names as a protocol. For example filename scsi:0, is
> interpreted as a protocol by name "scsi".
>
> This patch allows user to escape colon characters. For example the above
> fil
Anthony Liguori schrieb:
> Kevin Wolf wrote:
>> Ram Pai schrieb:
>>
>>> Problem: It is impossible to feed filenames with the character colon because
>>> qemu interprets such names as a protocol. For example filename scsi:0, is
>>> interpreted as a p
Avi Kivity schrieb:
> If you're using an old image, it's worthwhile to regenerate it using
> 'qemu-img convert' to clear any hidden corruption.
Be careful with that. qemu-img convert doesn't retain snapshots, so
you're only converting whatever the guest currently sees. But at least
checking old i
Anthony Liguori schrieb:
> Jan Kiszka wrote:
>> Hmm, I must have missed this: Where is your staging tree hosted?
>>
>
> Right now it's at http://repo.or.cz/w/qemu/aliguori-queue.git but I plan
> to move it to git.qemu.org in the next few days.
If I'm not mistaken, the patch "qemu-io: Implemen
Anthony Liguori schrieb:
> Kevin Wolf wrote:
>> Anthony Liguori schrieb:
>>
>>> Jan Kiszka wrote:
>>>
>>>> Hmm, I must have missed this: Where is your staging tree hosted?
>>>>
>>>>
>>> Right now it&
Christoph Hellwig schrieb:
> On Fri, Jul 10, 2009 at 11:59:25AM -0500, Anthony Liguori wrote:
>>> If I'm not mistaken, the patch "qemu-io: Implement
>>> bdrv_get_buffer/bdrv_put_buffer" is missing from the queue.
>>>
>> I just did a pull a few hours ago from Christoph's qemu-io tree. I'm
>> exp
Anthony Liguori schrieb:
> Blue Swirl wrote:
>> I bet this won't compile on win32.
>>
>> Instead of this (IMHO doomed) escape approach, maybe the filename
>> parameter could be specified as the next argument, for example:
>> -hda format=qcow2,blah,blah,filename_is_next_arg -hda "filename with
>> fu
Anthony Liguori schrieb:
> Blue Swirl wrote:
>> Then how about something like:
>> -drive name=hda,if=ide,cache=off,file_is_arg -filearg foo.img
>> -drive name=vda,if=virtio,cache=writeback,file_comes_next -patharg foo.img
>> -drive name=sdb,if=scsi,unit=1,fnarg -fnarg boo.img
>>
>
> The ex
Ram Pai schrieb:
> On Wed, 2009-07-15 at 22:04 +0100, Jamie Lokier wrote:
>> What an unhelpful error message... There isn't even a way to find out
>> the backing file path which the tool is looking for.
>
> Ok. i have introduced a message towards the effect, in the next revision
> of the patch.
Ram Pai schrieb:
> On Wed, 2009-07-15 at 18:04 +0300, Blue Swirl wrote:
>> On 7/15/09, Ram Pai wrote:
>>> Problem: It is impossible to feed filenames with the character colon because
>>> qemu interprets such names as a protocol. For example filename scsi:0, is
>>> interpreted as a protocol by na
Jamie Lokier schrieb:
> Kevin Wolf wrote:
>> Can we at least allow \, instead of ,, in parameter parsing, so that the
>> backslash has the practical benefit of being a single universal escape
>> character?
>
> Is there a good reason why we cannot simply use \ to escape
Ram Pai schrieb:
> Problem: It is impossible to feed filenames with the character colon because
> qemu interprets such names as a protocol. For example filename scsi:0, is
> interpreted as a protocol by name "scsi".
>
> This patch allows user to espace colon characters. For example the above
> fil
Am 16.06.2011 16:43, schrieb Kevin Wolf:
> Am 16.06.2011 16:28, schrieb Christoph Hellwig:
>> On Wed, Jun 15, 2011 at 09:46:10AM -0400, Federico Simoncelli wrote:
>>> qemu-img currently writes disk images using writeback and filling
>>> up the cache buffers which are
Am 28.06.2011 21:41, schrieb Marcelo Tosatti:
> On Tue, Jun 28, 2011 at 02:38:15PM +0100, Stefan Hajnoczi wrote:
>> On Mon, Jun 27, 2011 at 3:32 PM, Juan Quintela wrote:
>>> Please send in any agenda items you are interested in covering.
>>
>> Live block copy and image streaming:
>> * The differe
Am 20.06.2011 18:48, schrieb Federico Simoncelli:
> qemu-img currently writes disk images using writeback and filling
> up the cache buffers which are then flushed by the kernel preventing
> other processes from accessing the storage.
> This is particularly bad in cluster environments where time-ba
Am 29.06.2011 15:36, schrieb Johannes Stezenbach:
> On Linux x86_64 host with 32bit userspace, running
> qemu or even just "qemu-img create -f qcow2 some.img 1G"
> causes a kernel warning:
>
> ioctl32(qemu-img:5296): Unknown cmd fd(3) cmd(5326){t:'S';sz:0}
> arg(7fff) on some.img
> ioctl3
Am 29.06.2011 16:25, schrieb Johannes Stezenbach:
> On Linux x86_64 host with 32bit userspace, running
> qemu or even just "qemu-img create -f qcow2 some.img 1G"
> causes a kernel warning:
>
> ioctl32(qemu-img:5296): Unknown cmd fd(3) cmd(5326){t:'S';sz:0}
> arg(7fff) on some.img
> ioctl3
Am 30.06.2011 13:48, schrieb Stefan Hajnoczi:
> On Wed, Jun 29, 2011 at 4:41 PM, Marcelo Tosatti wrote:
>> On Wed, Jun 29, 2011 at 11:08:23AM +0100, Stefan Hajnoczi wrote:
>>> In the future we could add a 'base' argument to block_stream. If base
>>> is specified then data contained in the base im
Am 30.06.2011 16:36, schrieb Marcelo Tosatti:
>> 4. Live block copy API and high-level control - the main code that
>> adds the live block copy feature. Existing patches by Marcelo, can be
>> restructured to use common core by Marcelo.
>
> Can use your proposed block_stream interface, with a "blo
Am 05.07.2011 16:32, schrieb Marcelo Tosatti:
> On Tue, Jul 05, 2011 at 04:39:06PM +0300, Dor Laor wrote:
>> On 07/05/2011 03:58 PM, Marcelo Tosatti wrote:
>>> On Tue, Jul 05, 2011 at 01:40:08PM +0100, Stefan Hajnoczi wrote:
On Tue, Jul 5, 2011 at 9:01 AM, Dor Laor wrote:
> I tried to re-
Am 05.07.2011 20:18, schrieb Marcelo Tosatti:
> On Tue, Jul 05, 2011 at 04:37:08PM +0100, Stefan Hajnoczi wrote:
>> On Tue, Jul 5, 2011 at 3:32 PM, Marcelo Tosatti wrote:
>>> On Tue, Jul 05, 2011 at 04:39:06PM +0300, Dor Laor wrote:
On 07/05/2011 03:58 PM, Marcelo Tosatti wrote:
> On Tue,
Am 06.07.2011 12:39, schrieb Stefan Hajnoczi:
> On Wed, Jul 6, 2011 at 10:15 AM, Kaushal Shriyan
> wrote:
>> Is there a way to resize the Hard Disk of VM ?
>
> You can use qemu-img resize on a disk image that is currently not in use:
> qemu-img resize +10G
For running VMs, there is the 'block_r
Am 10.07.2011 20:08, schrieb Pekka Enberg:
> Hi Ingo,
>
> * Pekka Enberg wrote:
>>> This series fixes QCOW locking issues and implements delayed metadata
>>> writeout.
>>> This improves performance of writeout to QCOW2 images that don't have
>>> clusters
>>> and L2 tables allocated on-disk.
>>>
Am 11.07.2011 11:41, schrieb Pekka Enberg:
> Hi Kevin,
>
> On Mon, Jul 11, 2011 at 12:31 PM, Kevin Wolf wrote:
>> I would love to try out your code occasionally myself, but so far I have
>> been to lazy to build a guest kernel only to be able to test it. Having
>> t
Am 11.07.2011 15:34, schrieb Stefan Hajnoczi:
> On Mon, Jul 11, 2011 at 2:02 PM, Hannes Reinecke wrote:
>> Hi all,
>>
>> these are some fixes I found during debugging my megasas HBA emulation.
>> This time I've sent them as a separate patchset for inclusion.
>> All of them have been acked, so plea
Am 11.07.2011 15:02, schrieb Hannes Reinecke:
> Hi all,
>
> these are some fixes I found during debugging my megasas HBA emulation.
> This time I've sent them as a separate patchset for inclusion.
> All of them have been acked, so please apply.
>
> Hannes Reinecke (4):
> iov: Update parameter u
Am 19.07.2011 08:31, schrieb Hannes Reinecke:
> On 07/12/2011 03:37 PM, Kevin Wolf wrote:
>> Am 11.07.2011 15:02, schrieb Hannes Reinecke:
>>> Hi all,
>>>
>>> these are some fixes I found during debugging my megasas HBA emulation.
>>> This time I'
: Pekka Enberg
> CommitDate: Wed, 20 Jul 2011 16:28:31 +0300
>
> kvm tools, qcow: Fix copy-on-write image corruption
>
> We don't handle refcount table properly so make sure we only write to clusters
> that have the "copied" flag set.
>
> Cc: Kevin Wolf
> Cc
Am 22.07.2011 10:21, schrieb Pekka Enberg:
> On Thu, 21 Jul 2011, Kevin Wolf wrote:
>> Hm, I must have missed this patch on the KVM mailing list...
>
> It wasn't on the list, sorry.
>
>> You should also error out before creating a new L2 table as its refcount
>>
#x27; no longer complains about referenced
> clusters with zero reference count after
>
> dd if=/dev/zero of=/mnt/tmp
>
> where '/mnt' is freshly generated QCOW2 image.
>
> Cc: Asias He
> Cc: Cyrill Gorcunov
> Cc: Ingo Molnar
> Cc: Kevin Wolf
>
Am 25.07.2011 12:06, schrieb Stefan Hajnoczi:
> On Mon, Jul 25, 2011 at 9:51 AM, Avi Kivity wrote:
>> qemu_malloc() is type-unsafe as it returns a void pointer. Introduce
>> QEMU_NEW() (and QEMU_NEWZ()), which return the correct type.
>>
>> Signed-off-by: Avi Kivity
>> ---
>>
>> This is part of
Am 25.07.2011 10:30, schrieb Pekka Enberg:
> Hi Alexander,
>
> On Mon, Jul 25, 2011 at 11:14 AM, Alexander Graf wrote:
>>> So i wanted to have a lightweight tool that allows me to test KVM and
>>> tools/kvm/ does that very nicely: i type './kvm run' and i can test a
>>> native bzImage (which has
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
> Not every command is support for any device type. This patch adds
> a check for rejecting unsupported commands.
>
> Signed-off-by: Hannes Reinecke
> ---
> hw/scsi-disk.c | 104
> +++-
> 1 files
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
> Not every command is support for any device type. This patch adds
> a check for rejecting unsupported commands.
>
> Signed-off-by: Hannes Reinecke
We do emulate SEEK (6), but it's not in your scsi_cmd_table at all.
> ---
> hw/scsi-disk.c | 104
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
> Markus Armbruster pointed out that not every SCSI command is supported
> for a given device type. Based on his patch and suggestiongs this series
> cleans up the SCSI device type and adds a check for supported commands.
>
> Hannes Reinecke (6):
> s
Am 04.08.2011 16:20, schrieb Philipp Hahn:
> Hello,
>
> it seems like I have discovered a bug in qemu-0.14.1 which corrupts Qcow2
> image files when using internal snapshots.
> I tied this both on an amd64 host running our Debian bases UCS distribution
> (using pure qemu-kvm_0.14 and pure qemu-k
Am 08.08.2011 15:00, schrieb Anthony Liguori:
> On 08/08/2011 07:56 AM, Avi Kivity wrote:
>> QEMU deals with a lot of fixed width integer types; their names
>> (uint64_t etc) are clumsy to use and take up a lot of space.
>>
>> Following Linux, introduce shorter names, for example U64 for
>> uint64_
Am 14.08.2011 06:04, schrieb Avi Kivity:
> In certain circumstances, posix-aio-compat can incur a lot of latency:
> - threads are created by vcpu threads, so if vcpu affinity is set,
>aio threads inherit vcpu affinity. This can cause many aio threads
>to compete for one cpu.
> - we can c
Am 16.07.2012 16:25, schrieb Paolo Bonzini:
> Linux will not use these, but a very similar mechanism will be used to
> report the condition via virtio-scsi events.
>
> Signed-off-by: Paolo Bonzini
> ---
> hw/scsi-bus.c |5 +
> hw/scsi-disk.c | 15 +++
> hw/scsi.h |
Am 01.08.2012 17:52, schrieb Paolo Bonzini:
> Il 23/07/2012 18:32, Paolo Bonzini ha scritto:
>> Il 03/07/2012 15:20, Paolo Bonzini ha scritto:
These patches let virtio-blk use the new support for toggling the cache
mode between writethrough and writeback.
The first patch introdu
Am 31.08.2011 09:40, schrieb Jan Kiszka:
> On 2011-08-31 02:03, Chris Friesen wrote:
>> Hi,
>>
>> I've run into another problem. I configured qemu-kvm-0.15.0 as:
>>
>> ./configure --target-list="i386-softmmu,x86_64-softmmu" --disable-sdl
>> --disable-vnc --disable-curses
>>
>>
>> Building it, I g
should help pulling upstream into qemu-kvm when "block: avoid
> SIGUSR2" is merged. And will help merging further cleanups of this code
> I'm working on.
Acked-by: Kevin Wolf
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a
Am 08.09.2011 12:11, schrieb Zhi Yong Wu:
> Signed-off-by: Zhi Yong Wu
> ---
> Makefile.objs |2 +-
> block/blk-queue.c | 201
> +
> block/blk-queue.h | 59
> block_int.h | 27 +++
> 4 files changed, 288
Am 08.09.2011 12:11, schrieb Zhi Yong Wu:
> Signed-off-by: Zhi Yong Wu
> ---
> block.c | 59
> +++
> block.h |5
> block_int.h |3 ++
> blockdev.c | 29 +++
> qemu-config.c |
Am 08.09.2011 12:11, schrieb Zhi Yong Wu:
> Note:
> 1.) When bps/iops limits are specified to a small value such as 511
> bytes/s, this VM will hang up. We are considering how to handle this senario.
> 2.) When "dd" command is issued in guest, if its option bs is set to a
> large value
Am 17.10.2011 11:17, schrieb Vadim Rozenfeld:
> with the following series of patches we are starting to implement
> some basic Microsoft Hyper-V Enlightenment functionality, like relaxed
> timing, spinlock, and virtual apic support.
>
> For more Hyper-V related information please see:
> "Hyperviso
Am 26.09.2011 10:01, schrieb Zhi Yong Wu:
> On Fri, Sep 23, 2011 at 11:32 PM, Kevin Wolf wrote:
>> Am 08.09.2011 12:11, schrieb Zhi Yong Wu:
>>> Signed-off-by: Zhi Yong Wu
>>> ---
>>> Makefile.objs |
Am 26.09.2011 08:15, schrieb Zhi Yong Wu:
> On Fri, Sep 23, 2011 at 11:54 PM, Kevin Wolf wrote:
>>> +}
>>> +
>>> +static void bdrv_block_timer(void *opaque)
>>> +{
>>> +BlockDriverState *bs = opaque;
>>> +BlockQueue *queue= bs-
Am 26.09.2011 09:24, schrieb Zhi Yong Wu:
> On Sat, Sep 24, 2011 at 12:19 AM, Kevin Wolf wrote:
>> Am 08.09.2011 12:11, schrieb Zhi Yong Wu:
>>> Note:
>>> 1.) When bps/iops limits are specified to a small value such as 511
>>> bytes/s, this VM will hang
Am 18.10.2011 10:07, schrieb Zhi Yong Wu:
> On Mon, Oct 17, 2011 at 6:17 PM, Kevin Wolf wrote:
>>>>> +
>>>>> +typedef struct BlockQueueAIOCB BlockQueueAIOCB;
>>>>> +
>>>>> +struct BlockQueue {
>>>>> +QTAILQ_HEAD(re
Am 18.10.2011 11:29, schrieb Zhi Yong Wu:
>>> +void qemu_del_block_queue(BlockQueue *queue)
>>> +{
>>> +BlockQueueAIOCB *request, *next;
>>> +
>>> +QTAILQ_FOREACH_SAFE(request, &queue->requests, entry, next) {
>>> +QTAILQ_REMOVE(&queue->requests, request, ent
Am 24.10.2011 12:00, schrieb Chris Webb:
> I have a qemu-kvm guest (apparently a Ubuntu 11.04 x86-64 install) which has
> stopped and refuses to continue:
>
> (qemu) info status
> VM status: paused
> (qemu) cont
> (qemu) info status
> VM status: paused
>
> The host is running linux 2.6.
Am 24.10.2011 12:58, schrieb Chris Webb:
> Kevin Wolf writes:
>
>> Am 24.10.2011 12:00, schrieb Chris Webb:
>>> I have qemu monitor access and can even strace the relevant qemu process if
>>> necessary: is it possible to use this to diagnose what's caus
Am 24.10.2011 13:29, schrieb Chris Webb:
> Kevin Wolf writes:
>
>> In qemu 1.0 we'll have an extended 'info status' that includes the stop
>> reason, but 0.14 doesn't have this yet (was committed to git master only
>> recently).
>
> Right, ok
Am 24.10.2011 13:35, schrieb Paolo Bonzini:
> On 10/24/2011 01:04 PM, Juan Quintela wrote:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> - What's left to merge for 1.0.
I would still like to cache the default cache mode (probably to
cache=writeback). We don't
Am 25.10.2011 15:05, schrieb Anthony Liguori:
> On 10/25/2011 07:35 AM, Kevin Wolf wrote:
>> Am 24.10.2011 13:35, schrieb Paolo Bonzini:
>>> On 10/24/2011 01:04 PM, Juan Quintela wrote:
>>>>
>>>> Hi
>>>>
>>>> Please send in any age
Am 25.10.2011 16:06, schrieb Anthony Liguori:
> On 10/25/2011 08:56 AM, Kevin Wolf wrote:
>> Am 25.10.2011 15:05, schrieb Anthony Liguori:
>>> On 10/25/2011 07:35 AM, Kevin Wolf wrote:
>>>> Am 24.10.2011 13:35, schrieb Paolo Bonzini:
>>>>>
Am 25.10.2011 16:06, schrieb Anthony Liguori:
> On 10/25/2011 08:56 AM, Kevin Wolf wrote:
>> Am 25.10.2011 15:05, schrieb Anthony Liguori:
>>> I'd be much more open to changing the default mode to cache=none FWIW since
>>> the
>>> risk of data loss there
Am 26.10.2011 11:57, schrieb Daniel P. Berrange:
> On Wed, Oct 26, 2011 at 10:48:12AM +0200, Markus Armbruster wrote:
>> Kevin Wolf writes:
>>
>>> Am 25.10.2011 16:06, schrieb Anthony Liguori:
>>>> On 10/25/2011 08:56 AM, Kevin Wolf wrote:
>>>&g
Am 26.10.2011 13:39, schrieb Daniel P. Berrange:
> On Wed, Oct 26, 2011 at 01:23:05PM +0200, Kevin Wolf wrote:
>> Am 26.10.2011 11:57, schrieb Daniel P. Berrange:
>>> On Wed, Oct 26, 2011 at 10:48:12AM +0200, Markus Armbruster wrote:
>>>> Kevin Wolf writes:
>>&
Am 26.10.2011 16:41, schrieb Lucas Meneghel Rodrigues:
> Hi folks:
>
> We've captured a regression with floppy disk on recent qemu (and
> qemu-kvm, after a code merge). We bisected it to be caused by:
>
> commit 212ec7baa28cc9d819234fed1541fc1423cfe3d8
> Author: Richard Henderson
> Date: Mon
Am 04.11.2011 17:40, schrieb Lucas Meneghel Rodrigues:
> 2) The floppy regression problem which was reported some days ago on
> this mailing list still happens, Kevin did post a patch that resolves it
>
> [...]
>
> But still wasn't integrated upstream. As I understand, there are doubts
> whethe
Am 05.11.2011 03:16, schrieb Lucas Meneghel Rodrigues:
> Hi folks,
>
> qemu-kvm is segfaulting when executing migration with blkdebug files.
>
> 19:50:02 DEBUG| Git repo qemu_kvm uri: git://github.com/avikivity/qemu.git
> 19:50:02 DEBUG| Git repo qemu_kvm branch: master
> 19:50:30 INFO | Commit h
Am 06.11.2011 19:31, schrieb Ted Ts'o:
> On Sun, Nov 06, 2011 at 11:08:10AM -0600, Anthony Liguori wrote:
>> I'm quite happy with KVM tool and hope they continue working on it.
>> My only real wish is that they wouldn't copy QEMU so much and would
>> try bolder things that are fundamentally differe
Am 07.11.2011 12:38, schrieb Pekka Enberg:
> On Mon, 7 Nov 2011, Kevin Wolf wrote:
>> Makes it a lot less hackable for me unless you want to restrict the set
>> of potential developers to Linux kernel developers...
>
> We're not restricting potential developers to
Am 09.11.2011 22:01, schrieb Anthony Liguori:
> On 11/09/2011 03:00 PM, Michael S. Tsirkin wrote:
>> On Wed, Nov 09, 2011 at 02:22:02PM -0600, Anthony Liguori wrote:
>>> On 11/09/2011 02:18 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 11:35:54AM -0600, Anthony Liguori wrote:
> On
Am 10.11.2011 22:30, schrieb Anthony Liguori:
> Live migration with qcow2 or any other image format is just not going to work
> right now even with proper clustered storage. I think doing a block level
> flush
> cache interface and letting block devices decide how to do it is the best
> approa
Am 11.11.2011 15:03, schrieb Anthony Liguori:
> On 11/11/2011 04:15 AM, Kevin Wolf wrote:
>> Am 10.11.2011 22:30, schrieb Anthony Liguori:
>>> Live migration with qcow2 or any other image format is just not going to
>>> work
>>> right now even with proper clust
Am 11.11.2011 15:35, schrieb Anthony Liguori:
> On 11/11/2011 08:29 AM, Kevin Wolf wrote:
>> Am 11.11.2011 15:03, schrieb Anthony Liguori:
>>> On 11/11/2011 04:15 AM, Kevin Wolf wrote:
>>>> Am 10.11.2011 22:30, schrieb Anthony Liguori:
>>>>> Live migr
Am 12.11.2011 11:25, schrieb Avi Kivity:
> On 11/11/2011 12:15 PM, Kevin Wolf wrote:
>> Am 10.11.2011 22:30, schrieb Anthony Liguori:
>>> Live migration with qcow2 or any other image format is just not going to
>>> work
>>> right now even with proper clust
Am 14.11.2011 12:08, schrieb Daniel P. Berrange:
> On Mon, Nov 14, 2011 at 12:24:22PM +0200, Michael S. Tsirkin wrote:
>> On Mon, Nov 14, 2011 at 10:16:10AM +, Daniel P. Berrange wrote:
>>> On Sat, Nov 12, 2011 at 12:25:34PM +0200, Avi Kivity wrote:
>>>> On 1
Am 18.11.2011 09:47, schrieb Lan Tianyu:
> When meeting request to write the cluster without copied flag,
> allocate a new cluster and write original data with modification
> to the new cluster. This also adds support for the writing operation
> of the qcow2 compressed image. After testing, image f
Am 20.11.2011 11:59, schrieb Pekka Enberg:
> On Sun, 2011-11-20 at 14:14 +0800, Lan, Tianyu wrote:
>>> OK. Thx.
>>> But fsync is too slow. I try to find a way to sync a range of file.
>>> Are there any solutions to meet my purpose?
>
> On Sun, 2011-11-20 at 08:23 +0200, Sasha Levin wrote:
>> fdat
Am 21.11.2011 08:12, schrieb Lan Tianyu:
> When meeting request to write the cluster without copied flag,
> allocate a new cluster and write original data with modification
> to the new cluster. This also adds support for the writing operation
> of the qcow2 compressed image. After testing, image f
Am 14.01.2011 06:28, schrieb Amos Kong:
> - Original Message -
>> From: Amos Kong
>>
>> KVM guest always pauses on NOSPACE error, this test
>> just repeatedly extend guest disk space and resume guest
>> from paused status.
>>
>> Changes from v2:
>> - Oops! Forgot to update tests_base.cfg.s
Am 19.01.2011 06:44, schrieb Yoshiaki Tamura:
> event-tap function is called only when it is on, and requests sent
> from device emulators.
>
> Signed-off-by: Yoshiaki Tamura
> ---
> block.c | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/block.c b/block
Am 19.01.2011 06:44, schrieb Yoshiaki Tamura:
> event-tap controls when to start FT transaction, and provides proxy
> functions to called from net/block devices. While FT transaction, it
> queues up net/block requests, and flush them when the transaction gets
> completed.
>
> Signed-off-by: Yoshi
Am 19.01.2011 06:44, schrieb Yoshiaki Tamura:
> event-tap function is called only when it is on, and requests sent
> from device emulators.
>
> Signed-off-by: Yoshiaki Tamura
> ---
> block.c | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/block.c b/block
Am 19.01.2011 14:04, schrieb Yoshiaki Tamura:
>>> +static void event_tap_blk_flush(EventTapBlkReq *blk_req)
>>> +{
>>> +BlockDriverState *bs;
>>> +
>>> +bs = bdrv_find(blk_req->device_name);
>>
>> Please store the BlockDriverState in blk_req. This code loops over all
>> block devices and do
Am 19.01.2011 14:16, schrieb Yoshiaki Tamura:
> 2011/1/19 Kevin Wolf :
>> Am 19.01.2011 06:44, schrieb Yoshiaki Tamura:
>>> event-tap function is called only when it is on, and requests sent
>>> from device emulators.
>>>
>>> Signed-off-by:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
> +return;
> +}
> +
> +bdrv_aio_writev(bs, blk_req->reqs[0].sector, blk_req->reqs[0].qiov,
> +blk_req->reqs[0].nb_sectors, blk_req->reqs[0].cb,
> +blk_req->reqs[0].opaque);
Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
> 2011/1/20 Kevin Wolf :
>> Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
>>>>>>> +return;
>>>>>>> +}
>>>>>>> +
>>>>>>> +bdrv_aio_writev(bs,
Am 20.01.2011 14:50, schrieb Yoshiaki Tamura:
> 2011/1/20 Kevin Wolf :
>> Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
>>> 2011/1/20 Kevin Wolf :
>>>> Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
>>>>>>>>> +return;
>>>&g
Am 25.01.2011 15:11, schrieb Aurelien Jarno:
> Luiz Capitulino a écrit :
>> On Mon, 24 Jan 2011 16:06:34 -0600
>> Anthony Liguori wrote:
>>
>>> On 01/24/2011 07:25 AM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
>>> - coroutines for the block l
Am 28.01.2011 08:21, schrieb Yoshiaki Tamura:
> event-tap function is called only when it is on, and requests were
> sent from device emulators.
>
> Signed-off-by: Yoshiaki Tamura
Acked-by: Kevin Wolf
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
th
Am 27.01.2011 17:33, schrieb MORITA Kazutaka:
> This patch parses the input filename in sd_create(), and enables us
> specifying a target server to create sheepdog images.
>
> Signed-off-by: MORITA Kazutaka
Thanks, applied to the block branch.
Kevin
--
To unsubscribe from this list: send the li
Am 08.03.2011 16:50, schrieb Chris Wright:
> QAPI merge plans
> - should be 100% back compat
> - qmp moved over
> - hmp moved over
> - 1st pass, core infrastructure (includes test framework)
> - 2nd pass, command conversion
> - 3rd pass, more controversial bits
> - adds dependencies: glib and pytho
Am 06.12.2011 19:21, schrieb Jan Kiszka:
> On 2011-12-06 19:13, Michael Tokarev wrote:
>> On 06.12.2011 20:57, Michael Tokarev wrote:
>>> On 06.12.2011 20:38, Jan Kiszka wrote:
On 2011-12-06 17:29, Michael Tokarev wrote:
>>> []
> It appears there are two issues here, one is fixed by
>
Am 12.12.2011 03:03, schrieb Lan Tianyu:
> This patch enables allocating new refcount blocks and so then kvm tools
> could expand qcow2 image much larger.
>
> Signed-off-by: Lan Tianyu
> ---
> tools/kvm/disk/qcow.c | 105 +---
> 1 files changed, 89 in
Am 12.12.2011 11:58, schrieb Pekka Enberg:
> On Mon, 12 Dec 2011, Kevin Wolf wrote:
>>> @@ -667,14 +722,11 @@ static struct qcow_refcount_block
>>> *qcow_read_refcount_block(struct qcow *q, u64
>>>
>>> rft_idx = clust_idx >> (header->cluster_bi
Am 12.12.2011 12:15, schrieb Kevin Wolf:
> Am 12.12.2011 11:58, schrieb Pekka Enberg:
>> On Mon, 12 Dec 2011, Kevin Wolf wrote:
>>>> @@ -667,14 +722,11 @@ static struct qcow_refcount_block
>>>> *qcow_read_refcount_block(struct qcow *q, u64
>>>>
>>
Am 13.12.2011 04:41, schrieb lan,Tianyu:
> On 一, 2011-12-12 at 19:15 +0800, Kevin Wolf wrote:
>> Am 12.12.2011 11:58, schrieb Pekka Enberg:
>>> On Mon, 12 Dec 2011, Kevin Wolf wrote:
>>>>> @@ -667,14 +722,11 @@ static struct qcow_refcount_block
>>>>&g
1 - 100 of 310 matches
Mail list logo
