On Wed, Oct 10, 2012 at 2:09 PM, Kashyap Chamarthy wrote:
> On Wed, Oct 10, 2012 at 1:31 AM, Jeff Cody wrote:
>> On 10/09/2012 04:54 AM, Kashyap Chamarthy wrote:
>>> Hi (Jeff?)
>>>
>>> I was testing blockcommit operations qemu-git, as of Oct-6th (which
>
On Fri, Oct 12, 2012 at 7:39 PM, Stefan Hajnoczi wrote:
> The qemu-img info --backing-chain option enumerates the backing file
> chain. For example, for base.qcow2 <- snap1.qcow2 <- snap2.qcow2 the
> output becomes:
>
> $ qemu-img info --backing-chain snap2.qcow2
> image: snap2.qcow2
> file
On Sat, Oct 13, 2012 at 12:46 AM, Kashyap Chamarthy
wrote:
> On Fri, Oct 12, 2012 at 7:39 PM, Stefan Hajnoczi wrote:
>> The qemu-img info --backing-chain option enumerates the backing file
>> chain. For example, for base.qcow2 <- snap1.qcow2 <- snap2.qcow2 the
>> out
On Sat, Oct 13, 2012 at 2:01 AM, Eric Blake wrote:
> On 10/12/2012 02:19 PM, Kashyap Chamarthy wrote:
>
>>
>> From eb4c4bc92c035c42c23c30c5e7ee73b54f9cf3a8 Mon Sep 17 00:00:00 2001
>> From: Kashyap Chamarthy
>> Date: Sat, 13 Oct 2012 01:30:37 +0530
>> Subject:
>From a6233277e17338f571dda27cd9192d764f824b18 Mon Sep 17 00:00:00 2001
From: Kashyap Chamarthy
Date: Sun, 14 Oct 2012 09:51:18 +0530
Subject: [PATCH v2] qemu-img: document 'info --backing-chain'
Signed-off-by: Kashyap Chamarthy
---
qemu-img-cmds.hx | 4 ++--
qemu-img
On Sun, Oct 14, 2012 at 3:06 AM, Eric Blake wrote:
> On 10/13/2012 09:50 AM, Kashyap Chamarthy wrote:
>
>>
>> [PS: I haven't used 'git-send-email' for this trivial patch. Should I
>> have used that, instead of attaching it? I was wondering if
>> attach
Sorry, forgot to add [PATCH] in the subject.
/kashyap
On Sun, Oct 14, 2012 at 11:00 AM, Kashyap Chamarthy
wrote:
> From a6233277e17338f571dda27cd9192d764f824b18 Mon Sep 17 00:00:00 2001
> From: Kashyap Chamarthy
> Date: Sun, 14 Oct 2012 09:51:18 +0530
> Subject: [PATCH v2] qemu-i
On Tue, Oct 16, 2012 at 2:37 AM, Eric Blake wrote:
> On 10/13/2012 11:30 PM, Kashyap Chamarthy wrote:
> >>From a6233277e17338f571dda27cd9192d764f824b18 Mon Sep 17 00:00:00 2001
> > From: Kashyap Chamarthy
> > Date: Sun, 14 Oct 2012 09:51:18 +0530
> > Subject: [PATC
Signed-off-by: Kashyap Chamarthy
---
qemu-img-cmds.hx | 4 ++--
qemu-img.texi| 21 -
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index
0ef82e9ac7a89d607e1f2c8e38461cee5b438dba
Hi (Jeff?)
I was testing blockcommit operations qemu-git, as of Oct-6th (which
has your blockcommit code pulled in). And also w/ libvirt-git which
has Eric's libvirt blockcommit patches applied.
with the goal of :
actual state: [base] <-- [snap-1] <-- [snap-2] <-- [snap3] <-- [active-layer]
de
On Wed, Oct 10, 2012 at 1:31 AM, Jeff Cody wrote:
> On 10/09/2012 04:54 AM, Kashyap Chamarthy wrote:
>> Hi (Jeff?)
>>
>> I was testing blockcommit operations qemu-git, as of Oct-6th (which
>> has your blockcommit code pulled in). And also w/ libvirt-git which
>&g
Heya,
After building qemu, I tried to invoke QMP by via telnet:
Build:
==
#./configure --target-list=x86_64-softmmu --disable-werror
--enable-debug ; make -j5
==
Invoke QMP:
==
kashyap@qemu$ ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -smp 2
-m 2048 /export/images/e
On Sat, Mar 9, 2013 at 4:18 PM, Kashyap Chamarthy wrote:
> Heya,
>
> After building qemu, I tried to invoke QMP by via telnet:
>
> Build:
> ==
> #./configure --target-list=x86_64-softmmu --disable-werror
> --enable-debug ; make -j5
> ==
>
> Invoke
On Mon, Mar 11, 2013 at 2:51 PM, Markus Armbruster wrote:
> Kashyap Chamarthy writes:
>
>> Heya,
>>
>> After building qemu, I tried to invoke QMP by via telnet:
>
> Exact version, please. Commit hash if you build from git.
>
>> Build:
>> ==
On Sun, Jun 08, 2014 at 05:48:58PM +0530, Kashyap Chamarthy wrote:
> Heya,
>
> I built QEMU from this commit:
>
> $ git log | head -2
> commit 50809c8b9288a9bfe1fdec926b7ef985608a7ea6
> Merge: 4e627ae ae74bbe
>
>
> And, attempted to boot a Fedora gues
On Tue, Jun 10, 2014 at 10:55:13AM +0200, Paolo Bonzini wrote:
> Il 08/06/2014 14:18, Kashyap Chamarthy ha scritto:
[. . .]
>
> QEMU's "make install" should have installed the firmware blobs in
> /usr/share/local/qemu, including bios-256k.bin. Did it?
Yes it did. I
Heya,
Laszlo pointed out OVMF packages for Fedora from here[1]. I tried a
simple test using this[2] by installing Fedora onto a USB stick.
Once Fedora is installed on the USB stick (/dev/sdb), and I attempt to
boot into the USB device as below, I get the Fedora serial console login
prompt just fi
On Tue, Jun 10, 2014 at 05:18:21PM +0200, Laszlo Ersek wrote:
> On 06/10/14 15:04, Kashyap Chamarthy wrote:
> > Heya,
> >
> > Laszlo pointed out OVMF packages for Fedora from here[1]. I tried a
> > simple test using this[2] by installing Fedora onto a USB stick.
> >
On Tue, Jun 10, 2014 at 06:26:50PM +0200, Laszlo Ersek wrote:
> On 06/10/14 18:10, Kashyap Chamarthy wrote:
[. . .]
> > The USB stick is created with Fedora Rawhide image using this
> > script: http://people.freedesktop.org/~kay/installer/installer.sh
> >
> > $ s
On Tue, Jun 10, 2014 at 07:30:58PM +0200, Laszlo Ersek wrote:
> On 06/10/14 19:16, Kashyap Chamarthy wrote:
[. . .]
> >
> > Yes, I can, but will have to wait till tomorrow -- the contents of the
> > script came down to 1.6G after trying to make an ISO as below.
> >
create -f qcow2 -o backing_file=fedora-rawhide.qcow2 \
> overlay.qcow2
>
> And I tested with "overlay.qcow2" (rather than /dev/sdb), always
> recreating it from scratch before a test.
>
> On 06/10/14 15:04, Kashyap Chamarthy wrote:
> > Heya,
> >
> > Laszlo pointe
vin Wwolf mentioned on IRC that preallocation is the
best that can be done to extract near raw performance out of QCOW2.
Can someone please give insight as to what kind of 'metadata' is
this? Trying to understand this, before I try to apply this in my
test lab.
Thanks,
Kashyap Chamarthy
On 05/23/2013 05:53 PM, Richard W.M. Jones wrote:
> I'm pleased to announce the next stable release of libguestfs (1.22).
Great work!
==
$ ./autogen.sh && make -j 7 && \
time make -k check LIBGUESTFS_DEBUG=1 \
LIBGUESTFS_TRACE=1 |& tee \
/var/tmp/make-check-libugestfs-24-may.log
=
On Tue, Mar 18, 2014 at 07:56:16AM +0800, Le Tan wrote:
> Hi, I am diving into the source code of qemu. I see the word
> "coroutine" appears in so many places. I can't figure out what it
> means. So, please, can anyone help me, telling me the mechanism or
> semantic of "coroutine"? Thanks!
This mi
On Fri, Feb 20, 2015 at 11:09:20AM +, Stefan Hajnoczi wrote:
> On Fri, Feb 13, 2015 at 05:08:41PM -0500, John Snow wrote:
> > This series requires: [PATCH v3] blkdebug: fix "once" rule
> >
> > Welcome to the "incremental backup" newsletter, where we discuss
> > exciting developments in non-red
On Wed, Jan 21, 2015 at 11:39:44AM +0100, Paolo Bonzini wrote:
>
>
> On 21/01/2015 11:32, Zhang Haoyu wrote:
> > Hi,
> >
> > Does drive_mirror support incremental backup a running vm?
> > Or other mechanism does?
> >
> > incremental backup a running vm requirements:
> > First time backup, all o
On Wed, Jan 21, 2015 at 11:39:44AM +0100, Paolo Bonzini wrote:
>
>
> On 21/01/2015 11:32, Zhang Haoyu wrote:
> > Hi,
> >
> > Does drive_mirror support incremental backup a running vm?
> > Or other mechanism does?
> >
> > incremental backup a running vm requirements:
> > First time backup, all o
A simple reproducer below.
Export a disk image over NBD (I realize port 10809 is default, thought
I'd explicitly mention anyhow):
$ qemu-nbd --f qcow2 -p10809 \
/var/lib/libvirt/images/cirros-0.3.3-x86_64-disk.img -t
Create an overlay with backing file exported via NBD:
$ qemu-img
On Thu, Jan 29, 2015 at 04:47:23PM +, Richard W.M. Jones wrote:
> On Thu, Jan 29, 2015 at 05:25:09PM +0100, Kashyap Chamarthy wrote:
> > A simple reproducer below.
> >
> > Export a disk image over NBD (I realize port 10809 is default, thought
> > I&
On Thu, Jan 29, 2015 at 06:22:22PM +0100, Kashyap Chamarthy wrote:
> On Thu, Jan 29, 2015 at 04:47:23PM +, Richard W.M. Jones wrote:
> > On Thu, Jan 29, 2015 at 05:25:09PM +0100, Kashyap Chamarthy wrote:
[. . .]
> > > On the shell where `qemu-nbd` is runn
On Fri, Jan 30, 2015 at 06:15:21PM +0100, Kevin Wolf wrote:
> Am 29.01.2015 um 17:25 hat Kashyap Chamarthy geschrieben:
> > $ qemu-system-x86_64 \
> > -nographic \
> > -nodefconfig\
On Fri, Jan 30, 2015 at 02:32:25PM -0500, Max Reitz wrote:
> On 2015-01-30 at 13:41, Kashyap Chamarthy wrote:
> >On Fri, Jan 30, 2015 at 06:15:21PM +0100, Kevin Wolf wrote:
> >>Am 29.01.2015 um 17:25 hat Kashyap Chamarthy geschrieben:
[. . .]
> >>Copying Stefan bec
On Thu, Jan 08, 2015 at 01:44:58PM -0600, Gary R Hook wrote:
> On 12/24/14 4:42 AM, Kashyap Chamarthy wrote:
> >On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote:
> >
> >[. . .]
> >
> >In my case, the block device is a QCOW2 disk image file. If I boot
>
On Thu, Jan 08, 2015 at 06:04:20PM -0600, Gary R Hook wrote:
> On 1/8/15 2:21 PM, Kashyap Chamarthy wrote:
>
> >>qemu-img create -f qcow2 /tmp/dsk.test.qcow2
> >
> >A typo? You also need to provide a size here:
> >
> > $ qemu-img create -f qcow2 /tmp
On Wed, Nov 19, 2014 at 11:13:27AM -0700, Eric Blake wrote:
> On 11/19/2014 10:32 AM, Prof. Dr. Michael Schefczyk wrote:
[. . .]
> > virsh snapshot-create-as vm XXX --disk-only qemu-img convert -f
> > qcow2 -s XXX -O qcow2 XXX.img /backup/YYY.img virsh snapshot-delete
> > vm XXX
>
> Yes, virsh i
On Mon, Dec 01, 2014 at 04:51:58PM +, Stefan Hajnoczi wrote:
> Today is the first day of QEMU Advent Calendar 2014, where an
> interesting and fun QEMU disk image is published every day.
>
> http://www.qemu-advent-calendar.org/
>
> I won't spam the mailing list every day but I wanted to let y
Booting a minimal KVM guest throws the below error on Cubietruck:
"kvm_init_vcpu failed: Invalid argument"
More context and an easy reproducer in this QEMU bug[1] for Fedora.
Context quoting Rich Jones from comment #2:
"For some reason I thought this had been fixed upstream, but
now t
On Tue, Dec 09, 2014 at 11:27:02AM +, Richard W.M. Jones wrote:
> On Tue, Dec 09, 2014 at 10:53:41AM +, Peter Maydell wrote:
> > On 9 December 2014 at 10:50, Kashyap Chamarthy wrote:
> > > Booting a minimal KVM guest throws the below error on Cubietruck:
> >
On Tue, Dec 09, 2014 at 11:27:02AM +, Richard W.M. Jones wrote:
> On Tue, Dec 09, 2014 at 10:53:41AM +, Peter Maydell wrote:
> > On 9 December 2014 at 10:50, Kashyap Chamarthy wrote:
> > > Booting a minimal KVM guest throws the below error on Cubietruck:
> >
Tested this locally, w/ similar test as yours:
$ ./x86_64-softmmu/qemu-system-x86_64 -qmp stdio -nodefaults
{"QMP": {"version": {"qemu": {"micro": 93, "minor": 2, "major": 2},
"package": ""}, "capabiliti
On Fri, Apr 17, 2015 at 09:01:10PM -0400, John Snow wrote:
> I am not prepared to send a v3 on this, primarily because I am still
> waffling on whether or not to do the code motion patch that is present in
> patch #8 of v2 of this series.
>
> However, for the purposes of testing, reviewers may fin
On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote:
[. . .]
> And, invoking `drive-backup` *without* pre-creating the target image
> (i.e. 'incremental.o.img'):
>
> { 'execute': 'drive-backup',
> 'arguments': {
>
On Tue, Apr 21, 2015 at 11:34:07AM -0400, John Snow wrote:
> Kashyap Chamarthy sent me a question asking for some clarifications on
> testing my incremental backup series. I responded off-list but he has asked
> me to reproduce my answer for the archives :)
Thanks for the detailed re
On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote:
[. . .]
> And, invoking `drive-backup` *without* pre-creating the target image
> (i.e. 'incremental.o.img'):
>
> { 'execute': 'drive-backup',
> 'arguments
ml/qemu-devel/2015-04/msg02161.html
Signed-off-by: Kashyap Chamarthy
---
qmp-commands.hx | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/qmp-commands.hx b/qmp-commands.hx
index
3a42ad0bffeb23778f877410f6e2038943da46c0..df2ab50daf2689328ed622d42f5ff129ce27cdef
100
On Thu, Apr 23, 2015 at 10:34:57AM -0400, John Snow wrote:
> The qmp-shell is a little rudimentary, but it can be hacked
> to give us some transactional support without too much difficulty.
>
> (1) Prep.
> (2) Add support for serializing json arrays
> (3) Allow users to use 'single quotes' instead
On Thu, Apr 23, 2015 at 05:07:44PM -0600, Eric Blake wrote:
> On 04/23/2015 06:46 AM, Kashyap Chamarthy wrote:
> > Although the canonical source of reference for QMP commands is
> > qapi-schema.json, for consistency's sake, update qmp-commands.hx to
> > state the list of
ml/qemu-devel/2015-04/msg02161.html
Signed-off-by: Kashyap Chamarthy
Reviewed-by: Eric Blake
---
>From v1 -> v2:
- Update the "NB" part of the commit message by removing the duplicate
command entry and add the missing one ('block-dirty-bitmap-clear')
- Fix g
On Fri, Apr 24, 2015 at 11:52:00AM -0400, John Snow wrote:
>
> On 04/24/2015 04:32 AM, Kashyap Chamarthy wrote:
[. . .]
> These:
>
> > block-dirty-bitmap-add
> > block-dirty-bitmap-clear
> >
>
> Aren't merged yet, so it might be a little con
On Fri, Apr 24, 2015 at 02:51:59PM -0600, Eric Blake wrote:
> On 04/24/2015 10:20 AM, Kashyap Chamarthy wrote:
> > On Fri, Apr 24, 2015 at 11:52:00AM -0400, John Snow wrote:
> >>
> >> On 04/24/2015 04:32 AM, Kashyap Chamarthy wrote:
> >
> > [. . .]
>
On Thu, Apr 23, 2015 at 06:23:31PM +0200, Kashyap Chamarthy wrote:
> On Thu, Apr 23, 2015 at 10:34:57AM -0400, John Snow wrote:
> > The qmp-shell is a little rudimentary, but it can be hacked
> > to give us some transactional support without too much difficulty.
> >
>
On Tue, Apr 28, 2015 at 06:17:32PM +0200, Kashyap Chamarthy wrote:
[. . .]
> > Seems like a regression from your v2.
> >
> > It fails here, even for a non-transaction command, with your patch series
> > applied:
> >
> > (QEMU) blockdev-snapshot-internal-
;: {"node": "drive-ide0-0-0", "name":
"bitmap1"}, "type": "block-dirty-bitmap-add"}, {"data": {"node":
"drive-ide0-0-0", "name": "bitmap0"}, "type": "block-dirty-bitmap-clear"},
{"data": {"target": "./incremental.0.img", "format": "qcow2", "sync":
"dirty-bitmap", "bitmap": "bitmap1", "mode": "existing", "device":
"drive-ide0-0-0"}, "type": "drive-backup"}]}}
{"return": {}}
(QEMU)
And a quick negative test: don't pre-create the target image when
running the `drive-backup` command, appropriate error is thrown.
So, FWIW:
Tested-by: Kashyap Chamarthy
--
/kashyap
On Mon, May 18, 2015 at 06:22:22PM +0200, Max Reitz wrote:
> On 12.05.2015 01:04, John Snow wrote:
> >From: Kashyap Chamarthy
> >
> >Although the canonical source of reference for QMP commands is
> >qapi-schema.json, for consistency's sake, update qmp-commands.hx t
On Tue, May 19, 2015 at 11:37:32AM -0400, John Snow wrote:
> > On Mon, May 18, 2015 at 06:22:22PM +0200, Max Reitz wrote:
> >> On 12.05.2015 01:04, John Snow wrote:
[. . .]
> >>> diff --git a/qmp-commands.hx b/qmp-commands.hx
> >>> index 7506774..363126a 100644
> >>> --- a/qmp-commands.hx
> >>> +
On Wed, Mar 04, 2015 at 11:15:02PM -0500, John Snow wrote:
> Reviewed-by: Max Reitz
> Signed-off-by: John Snow
> ---
> tests/qemu-iotests/124 | 49
> ++
> tests/qemu-iotests/124.out | 4 ++--
> 2 files changed, 51 insertions(+), 2 deletions(-)
T
On Wed, Mar 11, 2015 at 10:25:13AM -0400, John Snow wrote:
>
>
> On 03/11/2015 08:11 AM, Kashyap Chamarthy wrote:
[. . .]
> >To test, I applied these two series to yesterday's QEMU git master:
> >
> > [PATCH 00/11] block: incremental backup transaction
On Fri, Mar 13, 2015 at 10:18:39PM +0100, Gerhard Wiesinger wrote:
> Hello,
>
> Any updates for the
> http://fedorapeople.org/groups/virt/virt-preview/fedora-virt-preview.repo
> repo to qemu 2.2.1 planned?
The above is maintained by Fedora Virtualization maintainers. I added
Cole Robinson, who ma
Heya,
I built QEMU from this commit:
$ git log | head -2
commit 50809c8b9288a9bfe1fdec926b7ef985608a7ea6
Merge: 4e627ae ae74bbe
And, attempted to boot a Fedora guest via this QEMU CLI results as
below:
$ /usr/local/sbin/qemu-system-x86_64 -s -S -nographic \
-nodefconfig -
On Wed, Sep 30, 2015 at 02:56:14PM -0400, John Snow wrote:
>
>
> On 09/21/2015 10:46 PM, Fam Zheng wrote:
> > From: Kashyap Chamarthy
> >
> > Although the canonical source of reference for QMP commands is
> > qapi-schema.json, for consistency's sake, u
dirty-bitmap-add
block-dirty-bitmap-clear
Also update the possible values for the "type" action array.
Signed-off-by: Kashyap Chamarthy
Reviewed-by: Eric Blake
---
In v8 ("v8" because Fam included this as part of a series that is
in its "v7" edition):
- Update the
On Fri, Oct 02, 2015 at 06:40:28AM -0600, Eric Blake wrote:
> On 10/02/2015 06:12 AM, Kashyap Chamarthy wrote:
> > Although the canonical source of reference for QMP commands is
> > qapi-schema.json, for consistency's sake, update qmp-commands.hx to
> > state the list of
[Sorry, I noticed your question only just now, as I was briefly away
from this list.]
On Fri, Oct 02, 2015 at 07:59:48PM +0200, Max Reitz wrote:
> On 02.10.2015 14:12, Kashyap Chamarthy wrote:
> > Although the canonical source of reference for QMP commands is
> > qapi-s
On Wed, Feb 10, 2016 at 06:40:58PM +, Daniel P. Berrange wrote:
[...]
I've applied all the series in this patches, to yesterday's Git master,
so I'm here:
$ git describe
pull-qcrypto-next-2016-02-02-1-378-gf9375d2
> Starting a QEMU system emulator built-in NBD server
>
> $ qemu-s
On Fri, Feb 12, 2016 at 03:00:32PM +, Daniel P. Berrange wrote:
> On Fri, Feb 12, 2016 at 02:28:33PM +0100, Kashyap Chamarthy wrote:
> > On Wed, Feb 10, 2016 at 06:40:58PM +, Daniel P. Berrange wrote:
> >
> > [...]
> >
> > I've applied all the seri
On Fri, Feb 12, 2016 at 05:03:07PM +0100, Kashyap Chamarthy wrote:
[...]
> So, 'qmp-shell' invocation works for me too:
>
> $ ./qmp-shell ./qmp-sock
> [...]
> (QEMU) nbd-server-start
> addr={"type":"inet","data":{"
On Mon, Feb 15, 2016 at 10:26:17AM +0100, Paolo Bonzini wrote:
>
>
> On 15/02/2016 10:12, Kevin Wolf wrote:
> > Am 14.02.2016 um 17:12 hat Paolo Bonzini geschrieben:
> >> On 14/02/2016 16:52, Paolo Bonzini wrote:
> >>> Reproducer:
> >>>
> >>> x86_64-softmmu/qemu-system-x86_64 \
> >>>-incoming
rrently no support for multiplexing in the other direction
> +(where a single QEMU front end takes input and output from multiple
> chardevs).
>
> Every backend supports the @option{logfile} option, which supplies the path
> to a file to record all data transmitted via the backend. The
> @option{logappend}
Reviewed-by: Kashyap Chamarthy
--
/kashyap
rt and the QEMU monitor,
> +and @option{-nographic} also multiplexes the console and the monitor to
> +stdio.
> +
> +There is currently no support for multiplexing in the other direction
> +(where a single QEMU front end takes input and output from multiple
> chardevs).
>
> Every backend supports the @option{logfile} option, which supplies the path
> to a file to record all data transmitted via the backend. The
> @option{logappend}
Nice. Reads a whole lot clearer (contextual description, followed by a
practical example and related additional information) than before. And
as a user of QEMU, I could follow if I pay attention carefully. :-)
Thanks!
FWIW:
Reviewed-by: Kashyap Chamarthy
--
/kashyap
"/export/tests//cirros-0.3.3.img",
"backing-filename-format": "qcow2",
"filename": "./ext-snap1.qcow2",
"dirty-flag": false,
"virtual-size": 41126400,
"backing-filename": "/export/tests//cirros-0.3.3.img",
"format-specific": {
"data": {
"compat": "1.1",
"refcount-bits": 16,
"corrupt": false,
"lazy-refcounts": false
},
"type": "qcow2"
},
"actual-size": 200704
},
[...]
> Signed-off-by: Daniel P. Berrange
> ---
> scripts/qmp/qmp-shell | 23 ++-
> 1 file changed, 10 insertions(+), 13 deletions(-)
FWIW:
Tested-by: Kashyap Chamarthy
[...]
--
/kashyap
On Tue, Feb 16, 2016 at 02:02:58PM +, Stefan Hajnoczi wrote:
> Hi,
> There are several ongoing efforts to implement incremental
> backup-related features.
>
> Let's have a voice/video conference to get everyone on the same page,
> avoid duplicated work, and get patches merged faster.
>
> Agen
Can you please provide some more information here.
e.g.
- qemu command-line used
- how did you trigger it - libvirt/or direct qemu-kvm binary
- segentation fault/tracedetails
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QE
Short: I can't reproduce here with L1 guest having has host-passthrough
for CPU.
Long:
=
Version Info:
-
On Physical host:
~
$ uname -r; rpm -q libvirt-daemon-kvm qemu
3.10.0-0.rc2.git1.2.fc20.x86_64
qemu-1.4.2-3.fc19.x86_64
libvirt-daemon-kvm-1.0.5.2-1.fc19.x86_6
On Thu, Oct 15, 2015 at 10:30:21AM +0300, Denis V. Lunev wrote:
> The following is done:
> - QMP/HMP events are now logged
I applied this patch series locally, and tried to test it the below way:
Launch a minimal QEMU instance:
$ /home/kashyapc/build/build-qemu-upstream/x86_64-softmmu/qemu-sys
On Thu, Oct 15, 2015 at 06:18:31PM +0300, Pavel Butsykin wrote:
>
> On 15.10.2015 17:49, Kashyap Chamarthy wrote:
> >On Thu, Oct 15, 2015 at 10:30:21AM +0300, Denis V. Lunev wrote:
> >>The following is done:
> >>- QMP/HMP events are now logged
> >
> >I ap
[1] when you wrote these improvements to
qmp-shell, the change looks good, FWIW:
Reviewed-By: Kashyap Chamarthy
[1]
https://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg04201.html
> diff --git a/scripts/qmp/qmp-shell b/scripts/qmp/qmp-shell
> index 65280d2..fa39bf0 100755
>
On Wed, Jul 29, 2015 at 09:46:53AM +0100, Stefan Hajnoczi wrote:
> On Wed, Jul 29, 2015 at 12:57:30AM +0900, Manjong Han wrote:
> > I was facing a weird behavior when I used the one disk image file on 2
> > virtual machines at the same time.
> >
> > I made the instance of a virtual machine, using
Upstream QEMU recommends to use '-display none' as opposed to
'-nographic' -- which is a "legacy option that does a whole bunch of
confusing stuff" (thanks Peter Maydell).
Upstream libguestfs already made the switch [1] in DEC-2013.
[1] https://github.com/libguestfs/libguestfs/commit/7a41f5c1 --
On Fri, Mar 11, 2016 at 11:01:28AM +0100, Paolo Bonzini wrote:
>
>
> On 11/03/2016 08:38, Gerd Hoffmann wrote:
> > This patches makes input-linux use -object instead a new command line
Nit: s/instead a/instead of a/
[If you want to fix up when you apply.]
> > switch. So, instead of the switch
Meta-comment: You might want to first try sending the patch series to
yourself before sending to the list -- to see if subsequent patches to
the cover letter are submitted as part of the _same_ e-mail thread.
[...]
--
/kashyap
On Wed, May 25, 2016 at 11:13:24PM -0600, Chris Friesen wrote:
[...]
> However, if I explicitly specify a custom CPU model of "qemu64" the
> instance refuses to boot and I get a log saying:
[Not a direct answer to the exact issue you're facing, but a related
issue that is being investigated pres
quot;configure" being executed.
>
> The content of "pkgversion" is not changed when "--with-pkgversion" is
> used on the command line.
>
> Cc: "Daniel P. Berrange"
> Cc: Kashyap Chamarthy
> Signed-off-by: Laszlo Ersek
> ---
> c
Seems like supplying "qcow2" file BlockdevDriver option to QMP
`blockdev-add` results in a SIGSEGV:
[...]
Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault.
0x55a0121f in visit_type_BlockdevRef ()
[...]
Reproducer
--
Tested with: qemu-
On Wed, Jun 15, 2016 at 11:58:31AM +0200, Kashyap Chamarthy wrote:
> Seems like supplying "qcow2" file BlockdevDriver option to QMP
> `blockdev-add` results in a SIGSEGV:
>
> [...]
> Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation
it_start_struct(v, name, NULL, 0, &err);
> |@@ -2459,10 +2462,13 @@ void visit_type_BlockdevRef(Visitor *v,
> | case QTYPE_QSTRING:
> | visit_type_str(v, name, &(*obj)->u.reference, &err);
> | break;
> |+case QTYPE_NONE:
> |+abort();
>
On Fri, Apr 17, 2015 at 03:22:37PM +0100, Daniel P. Berrange wrote:
> This integrates support for QIOChannelTLS object in the TCP
> chardev backend. If the 'tls-cred=NAME' option is passed with
> the '-chardev tcp' argument, then it will setup the chardev
> such that the client is required to estab
On Tue, May 05, 2015 at 02:49:51PM +0100, Daniel P. Berrange wrote:
> On Mon, May 04, 2015 at 10:07:15PM +0200, Kashyap Chamarthy wrote:
> > On Fri, Apr 17, 2015 at 03:22:37PM +0100, Daniel P. Berrange wrote:
> > > This integrates support for QIOChannelTLS object in the TCP
>
On Tue, May 05, 2015 at 04:54:44PM +0200, Kashyap Chamarthy wrote:
[. . .]
> While running QEMU as TLS server, the TLS handshake completes
> successfully when connected via `gnutls-cli`.
>
> However, when using QEMU as client to connect to an existing GnuTLS
> server, I notice
On Wed, May 06, 2015 at 11:18:23AM +0100, Daniel P. Berrange wrote:
> On Wed, May 06, 2015 at 10:34:06AM +0200, Kashyap Chamarthy wrote:
> > On Tue, May 05, 2015 at 04:54:44PM +0200, Kashyap Chamarthy wrote:
> >
> > [. . .]
> >
> > > While running QEMU as TLS
(Cc also: libvirt upstream maling list)
Gentle reminder ...
tl;dr: please submit the proposals by *10th Dec 2022*
On Tue, Nov 08, 2022 at 10:45:33AM -0500, Stefan Hajnoczi wrote:
> Hi,
> The yearly FOSDEM open source conference is now accepting talk
> proposals. FOSDEM '23 will be held in Brusse
[Reviving this old thread as I don't think we came to a conclusion on
this.]
On Fri, Sep 21, 2018 at 05:43:23PM +0200, Kashyap Chamarthy wrote:
> Hi folks,
>
> As Markus pointed out in this 'qemu-devel' thread[1],
> backends/rng-random.c uses '/dev/random'
tps://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg02724.html
-- "[RFC] Virtio RNG: Consider changing the default entropy source to
/dev/urandom"
Signed-off-by: Kashyap Chamarthy
---
backends/rng-random.c | 2 +-
qemu-options.hx | 2 +-
2 files changed, 2 inserti
tps://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg02724.html
-- "[RFC] Virtio RNG: Consider changing the default entropy source to
/dev/urandom"
Signed-off-by: Kashyap Chamarthy
---
backends/rng-random.c | 2 +-
qemu-options.hx | 2 +-
2 files changed, 2 inserti
On Fri, May 03, 2019 at 04:49:05PM +0100, Daniel P. Berrangé wrote:
> On Fri, May 03, 2019 at 05:46:13PM +0200, Kashyap Chamarthy wrote:
> > When QEMU exposes a VirtIO-RNG device to the guest, that device needs a
> > source of entropy, and that source needs to be "non-block
On Thu, May 09, 2019 at 02:53:20PM +0100, Stefan Hajnoczi wrote:
> On Fri, May 03, 2019 at 05:46:12PM +0200, Kashyap Chamarthy wrote:
> > When QEMU exposes a VirtIO-RNG device to the guest, that device needs a
> > source of entropy, and that source needs to be "non-block
-- "[RFC] Virtio RNG: Consider changing the default entropy source to
/dev/urandom"
Signed-off-by: Kashyap Chamarthy
---
v2:
- Update commit message to mention justification for preferring
`/dev/urandom` over `/dev/random` [stefanha]
---
backends/rng-random.c | 2 +-
qemu
On Fri, May 10, 2019 at 10:15:25AM +0200, Kashyap Chamarthy wrote:
[...]
> Signed-off-by: Kashyap Chamarthy
I didn't intentionally retain Dan and Rich's "Reviewed-by" tags. Maybe
I should have, because I only updated the commit message.
> ---
> v2:
> -
On Thu, May 09, 2019 at 04:23:42PM +0200, Laurent Vivier wrote:
> Add a new RNG backend using QEMU builtin getrandom function.
>
> It can be created with "-object rng-builtin".
Can you please specify a full, working example in the commit message?
It would be useful for later reference.
> This pa
On Mon, May 13, 2019 at 08:36:23AM +0200, Laurent Vivier wrote:
> On 12/05/2019 20:21, Michael S. Tsirkin wrote:
[...]
> > > Kashyap Chamarthy (1):
> > >VirtIO-RNG: Update default entropy source to `/dev/urandom`
> > >
> > > Laurent Vivier (2):
> &
Hi folks,
Today I learnt about some obscure PCIe-related properties, in context of
the adding PCIe root ports to a guest, namely:
io-reserve
mem-reserve
bus-reserve
pref32-reserve
pref64-reserve
Unfortunately, the commit[*] that added them provided no documentation
whatsover.
1 - 100 of 538 matches
Mail list logo
