On Mon, Feb 1, 2010 at 9:26 PM, Anthony Liguori wrote:
> Hi,
>
> The new qemu.org wiki is now live. I've transferred all of the content from
> the old website and have now switched www.qemu.org to redirect to
> wiki.qemu.org.
Hi Anthony...
Right now, February 2nd, 1:02 PM GMT+7 (Indonesian time
Notice: If you are receiving this email is because you are registered
in the QEMU mailing list or you posted an entry in the Official OS
Support List.
Dear developers, testers and users.
Stuart Brady and I are proud to present you the new QEMU's Official OS
Support List 3.0.
This list is
Please send in any agenda items you are interested in covering.
2010/2/2 Luiz Capitulino :
> On Tue, 2 Feb 2010 00:26:53 +0800
> Roy Tam wrote:
>
>> 2010/2/2 Luiz Capitulino :
>>
>> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
>> > is the last qemu's function I see in the logs.
>> >
>> > From now on I only see msvcrt functions...
>>
On 02/01/2010 04:44 PM, Ian Molton wrote:
Anthony Liguori wrote:
I went back and looked at the last series and found my feedback. I had
suggested that instead of automatically reconnecting, a mechanism should
be added for a user to initiate a reconnect.
This sounds useful
Addi
Anthony Liguori wrote:
>> +DEFINE_RNG_PROPERTIES(VirtIOPCIProxy, rng),
>>
>
> I don't see any reason to use a define here.
Consistency with the other virtio code (at the time I wrote it)
> Coding style is off here (newline between ) and { ).
Fixed.
> Can't call gettimeofday di
Anthony Liguori wrote:
> I went back and looked at the last series and found my feedback. I had
> suggested that instead of automatically reconnecting, a mechanism should
> be added for a user to initiate a reconnect.
This sounds useful
> Additionally, we should emit events upon disconnect thro
Gerd Hoffmann wrote:
> Hi,
>
>>> + PCI_VENDOR_ID_REDHAT_QUMRANET,
>>> + PCI_DEVICE_ID_VIRTIO_RNG,
>>
>> Gerd (or the right person at Red Hat) needs to Ack the assignment of
>> this PCI device id.
>
> Using the first unused one should be ok, I'll double check that though.
> pci-ids.txt must be u
On Mon, 01 Feb 2010 20:37:41 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Mon, 01 Feb 2010 18:08:27 +0100
> > Markus Armbruster wrote:
> >
> >> Luiz Capitulino writes:
> >>
> >> > Feature negotiation allows clients to enable new QMP capabilities they
> >> > support and
Luiz Capitulino writes:
> On Mon, 01 Feb 2010 18:08:27 +0100
> Markus Armbruster wrote:
>
>> Luiz Capitulino writes:
>>
>> > Feature negotiation allows clients to enable new QMP capabilities they
>> > support and thus allows QMP to envolve in a compatible way.
>> >
>> > A capability is a new
[target-x86_64.conf was unintentionally omitted from the earlier patch]
This is a reimplementation of prior versions which adds
the ability to define cpu models for contemporary processors.
The added models are likewise selected via -cpu ,
and are intended to displace the existing convention
of "-
On Tue, 2 Feb 2010 00:26:53 +0800
Roy Tam wrote:
> 2010/2/2 Luiz Capitulino :
>
> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> > is the last qemu's function I see in the logs.
> >
> > From now on I only see msvcrt functions...
> >
> > Maybe, you can type run on gdb
On Mon, 01 Feb 2010 18:08:27 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > Feature negotiation allows clients to enable new QMP capabilities they
> > support and thus allows QMP to envolve in a compatible way.
> >
> > A capability is a new QMP feature and/or protocol change w
On Mon, 01 Feb 2010 18:04:04 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > It will be used to switch between "handshake" and "operational"
> > modes. Currently it doesn't have any practical effect, as
> > mode-oriented support is not enforced yet.
> >
> > Usage example:
> >
> >
It's emitted when a disk write or read fails, some device information
is provided. We can also provide error details in the future.
Example:
{ "event": "DISK_ERROR",
"data": { "device": "ide0-hd1",
"operation": "write",
"action": "stop" }
"timestamp": { "second
It's really drive_get_on_error()'s current body. This is needed
so that the disk error event code can also use the returned action.
Signed-off-by: Luiz Capitulino
---
vl.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/vl.c b/vl.c
index 6f1e1ab..57c439d 100644
--
Hi there,
I've been requested by libvirt guys to add a QMP event for disk I/O errors,
this is what this series is about.
It's a RFC because I need feedback on the following:
1. drive_get_on_error() is called on all disk errors, right?
2. I've tested only ENOSPC errors, is there a way to test
Luiz Capitulino writes:
> In order to have feature negotiation in QMP, the Monitor
> has to be modified to support different modes of operation.
>
> We need two modes:
>
> o Handshake: where features are negotiated, only commands
> which deal with protocol configuration are allowed
>
> o Operatio
Luiz Capitulino writes:
> Feature negotiation allows clients to enable new QMP capabilities they
> support and thus allows QMP to envolve in a compatible way.
>
> A capability is a new QMP feature and/or protocol change which is not part of
> the core protocol as defined in the QMP spec.
Well,
Hi all,
I am new to QEMU and need some help from you guys. Below are few questions of
mine. I'll highly appreciate if someone can answer these questions:
I've build a demo application of Nucleus PLUS for ARM integrator CP. This
application uses framebuffer and displays some data on LCD. Can yo
Luiz Capitulino writes:
> It will be used to switch between "handshake" and "operational"
> modes. Currently it doesn't have any practical effect, as
> mode-oriented support is not enforced yet.
>
> Usage example:
>
> { "execute": "qmp_switch_mode", "arguments": { "mode": "operational" } }
>
> Si
Luiz Capitulino writes:
> On Thu, 28 Jan 2010 16:49:00 -0600
> Anthony Liguori wrote:
>
>> On 01/28/2010 07:42 AM, Luiz Capitulino wrote:
>> > Two new errors:
>> >
>> > - QERR_QMP_INVALID_MODE_NAME
>> > - QERR_QMP_INVALID_MODE_TRANSITION
>> >
>> > Signed-off-by: Luiz Capitulino
>> > ---
>> > q
On 02/01/2010 10:03 AM, Gerd Hoffmann wrote:
Hi,
+ PCI_VENDOR_ID_REDHAT_QUMRANET,
+ PCI_DEVICE_ID_VIRTIO_RNG,
Gerd (or the right person at Red Hat) needs to Ack the assignment of
this PCI device id.
Using the first unused one should be ok, I'll double check that though.
pci-ids.txt must b
On 02/01/2010 10:12 AM, Luiz Capitulino wrote:
On Mon, 01 Feb 2010 09:25:27 -0600
Anthony Liguori wrote:
On 02/01/2010 07:34 AM, Ian Molton wrote:
Add a reconnect option that allows sockets to reconnect (after a
specified delay) to the specified server. This makes the virtio
On Monday 01 February 2010 08:26:54 Anthony Liguori wrote:
> Hi,
>
> The new qemu.org wiki is now live. I've transferred all of the content
> from the old website and have now switched www.qemu.org to redirect to
> wiki.qemu.org.
>
> My hope is with the new wiki format, qemu.org can be a central
2010/2/2 Luiz Capitulino :
>
> Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> is the last qemu's function I see in the logs.
>
> From now on I only see msvcrt functions...
>
> Maybe, you can type run on gdb, run system_reset on the
> Monitor and then switch back to gdb an
2010/2/2 Luiz Capitulino :
> Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> is the last qemu's function I see in the logs.
>
> From now on I only see msvcrt functions...
>
> Maybe, you can type run on gdb, run system_reset on the
> Monitor and then switch back to gdb and
On Mon, Feb 01, 2010 at 01:19:50PM -0200, Luiz Capitulino wrote:
> On Mon, 1 Feb 2010 17:12:11 +0200
> "Michael S. Tsirkin" wrote:
>
> > info pci returns a bus object, not a qdict, which leads to a crash in
> > monitor which wants a qdict. Not sure what the right fix is: this patch
> > just chec
On Mon, 01 Feb 2010 09:25:27 -0600
Anthony Liguori wrote:
> On 02/01/2010 07:34 AM, Ian Molton wrote:
> > Add a reconnect option that allows sockets to reconnect (after a
> > specified delay) to the specified server. This makes the virtio-rng driver
> > useful in production environments where
Hi,
+ PCI_VENDOR_ID_REDHAT_QUMRANET,
+ PCI_DEVICE_ID_VIRTIO_RNG,
Gerd (or the right person at Red Hat) needs to Ack the assignment of
this PCI device id.
Using the first unused one should be ok, I'll double check that though.
pci-ids.txt must be updated too.
cheers,
Gerd
On Mon, 1 Feb 2010 21:42:37 +0800
Roy Tam wrote:
> 2010/2/1 Luiz Capitulino :
> > On Mon, 1 Feb 2010 20:36:22 +0800
> > Roy Tam wrote:
> >
> >> 2010/2/1 Luiz Capitulino :
> >> > On Sun, 31 Jan 2010 16:28:42 +0800
> >> > Roy Tam wrote:
> >> >
> >> >> Dear all,
> >> >>
> >> >> In latest git revis
On 02/01/2010 07:34 AM, Ian Molton wrote:
This patch adds support for virtio-rng. Data is read from a chardev and
can be either raw entropy or received via the EGD protocol.
Signed-off-by: Ian Molton
---
Makefile.target |2 +-
hw/pci.h|1 +
hw/virtio-pci.c | 27
On 02/01/2010 07:34 AM, Ian Molton wrote:
Add a reconnect option that allows sockets to reconnect (after a
specified delay) to the specified server. This makes the virtio-rng driver
useful in production environments where the EGD server may need to be restarted.
Signed-off-by: Ian Molton
On Mon, 1 Feb 2010 17:12:11 +0200
"Michael S. Tsirkin" wrote:
> info pci returns a bus object, not a qdict, which leads to a crash in
> monitor which wants a qdict. Not sure what the right fix is: this patch
> just checks and handles non-disct command as synchronous. OTOH if we
> definitely nee
info pci returns a bus object, not a qdict, which leads to a crash in
monitor which wants a qdict. Not sure what the right fix is: this patch
just checks and handles non-disct command as synchronous. OTOH if we
definitely need all commands to return a dict, we should change return
type appropriat
Hi Stefan,
2010/2/1 Stefan Weil :
> Dirk Ullrich schrieb:
>> Hi,
>>
>> I have patched QEMU's "configure" script and its main makefile: Now
>> QEMU's documentation is also created in PDF format (using "texi2pdf"),
>> and the targets "install-all-doc" / "install-all" install
>> documentation in INFO
Hi,
The new qemu.org wiki is now live. I've transferred all of the content
from the old website and have now switched www.qemu.org to redirect to
wiki.qemu.org.
My hope is with the new wiki format, qemu.org can be a centralized
location to connect all of the information available about QEMU
2010/2/1 Luiz Capitulino :
> On Mon, 1 Feb 2010 20:36:22 +0800
> Roy Tam wrote:
>
>> 2010/2/1 Luiz Capitulino :
>> > On Sun, 31 Jan 2010 16:28:42 +0800
>> > Roy Tam wrote:
>> >
>> >> Dear all,
>> >>
>> >> In latest git revision, when guest OS restarts or system_reset command
>> >> issues from mon
Add a reconnect option that allows sockets to reconnect (after a
specified delay) to the specified server. This makes the virtio-rng driver
useful in production environments where the EGD server may need to be restarted.
Signed-off-by: Ian Molton
---
qemu-char.c | 159
This patch addresses a build issue due to a missing include in
fpu/softfloat-native.c
Signed-off-by: Ian Molton
---
fpu/softfloat-native.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fpu/softfloat-native.c b/fpu/softfloat-native.c
index 8d64f4e..702950e 10064
This patch adds support for virtio-rng. Data is read from a chardev and
can be either raw entropy or received via the EGD protocol.
Signed-off-by: Ian Molton
---
Makefile.target |2 +-
hw/pci.h|1 +
hw/virtio-pci.c | 27 +++
hw/virtio-rng.c | 202 ++
This patch adds a 'SIZE' type property to those available to qdevs.
It is the analogue of the OPT_SIZE property for options.
Signed-off-by: Ian Molton
---
hw/qdev-properties.c | 34 ++
hw/qdev.h|4
parse_common.h | 40
This patch rationalises the declaration of inet_listen_opts such that
it matches the other inet_{listen,connect}_opts functions.
This change is needed for a patch adding socket reconection support.
Signed-off-by: Ian Molton
---
qemu-sockets.c |9 +++--
qemu_socket.h |2 +-
The following patches are an update of my virtio-rng patchset.
Patches 1-3 implement needed infrastructure fpr virtio-rng to be used
effectively, patch 4 implements the device.
Patch 5 is a build fix I needed in order to compile -git qemu.
Please apply :)
qemu-sockets.c |9 +-
qem
On Mon, 1 Feb 2010 20:36:22 +0800
Roy Tam wrote:
> 2010/2/1 Luiz Capitulino :
> > On Sun, 31 Jan 2010 16:28:42 +0800
> > Roy Tam wrote:
> >
> >> Dear all,
> >>
> >> In latest git revision, when guest OS restarts or system_reset command
> >> issues from monitor console, it asserts failed:
> >> As
2010/2/1 Luiz Capitulino :
> On Sun, 31 Jan 2010 16:28:42 +0800
> Roy Tam wrote:
>
>> Dear all,
>>
>> In latest git revision, when guest OS restarts or system_reset command
>> issues from monitor console, it asserts failed:
>> Assertion failed: obj != NULL, file C:/msys/home/User/qemu/monitor.c, l
Christoph Hellwig wrote:
> On Mon, Feb 01, 2010 at 10:25:52AM +0100, Alexander Graf wrote:
> > We don't know beforehand if a user will use the commit comnand during
> > tje runtime of the vm.
> >
> > IMHO it'd be best to always open backing files read only and try to
> > open them for write ac
On Sun, 31 Jan 2010 16:28:42 +0800
Roy Tam wrote:
> Dear all,
>
> In latest git revision, when guest OS restarts or system_reset command
> issues from monitor console, it asserts failed:
> Assertion failed: obj != NULL, file C:/msys/home/User/qemu/monitor.c, line 338
Hm, I can't reproduce this
Dirk Ullrich schrieb:
> Hi,
>
> I have patched QEMU's "configure" script and its main makefile: Now
> QEMU's documentation is also created in PDF format (using "texi2pdf"),
> and the targets "install-all-doc" / "install-all" install
> documentation in INFO and PDF format, too. May be others find th
Christoph Hellwig wrote:
> On Mon, Feb 01, 2010 at 10:25:52AM +0100, Alexander Graf wrote:
>
>> We don't know beforehand if a user will use the commit comnand during
>> tje runtime of the vm.
>>
>> IMHO it'd be best to always open backing files read only and try to
>> open them for write acc
On Mon, Feb 01, 2010 at 10:25:52AM +0100, Alexander Graf wrote:
> We don't know beforehand if a user will use the commit comnand during
> tje runtime of the vm.
>
> IMHO it'd be best to always open backing files read only and try to
> open them for write access on the commit command. That comm
Am 01.02.2010 um 10:06 schrieb Christoph Hellwig :
On Mon, Feb 01, 2010 at 09:46:00AM +0100, Kevin Wolf wrote:
Is it better to always open the backing file with read-only mode ?
this will be more consistent/predictable ?
I would love to open them read-only unconditionally, but we can't. It
Export all topology information in the block config structure,
guarded by a new VIRTIO_BLK_F_TOPOLOGY config flag.
Note that there is no savevm support for the new information yet,
as it would be a pain without the table driven savevm format.
Juan has promised to send out a new version of the tabl
On Mon, Feb 01, 2010 at 09:46:00AM +0100, Kevin Wolf wrote:
> > Is it better to always open the backing file with read-only mode ? this
> > will be more consistent/predictable ?
>
> I would love to open them read-only unconditionally, but we can't. It
> would break the commit monitor command. I t
Am 31.01.2010 17:49, schrieb Naphtali Sprei:
> There's a problem when trying to use an image file based on a read-only image
> file.
> Before this patch, qemu fails to open the base image and stop.
> With this patch, qemu tries to open the backing file with same permissions as
> the "top" file,
>
On Tue, Jan 26, 2010 at 06:07:45PM -0600, Anthony Liguori wrote:
> On 01/26/2010 07:49 AM, Christoph Hellwig wrote:
> >If we go over the maximum number of iovecs support by syscall we get
> >back EINVAL from the kernel which translate to I/O errors for the guest.
> >
> >Add a MAX_IOV defintion for
56 matches
Mail list logo
