Hi,
Paolo Bonzini wrote:
> Il 14/02/2013 07:10, Tomoki Sekiyama ha scritto:
> > diff --git a/qga/vss-win32-provider/qga-provider.idl
> b/qga/vss-win32-provider/qga-provider.idl
> > new file mode 100644
> > index 000..17abca0
> > --- /dev/null
> > +++ b/qga/vss-win32-provider/qga-provider.idl
在 2012-12-18二的 13:41 +0100，Vasilis Liaskovitis写道：
> Each hotplug-able memory slot is a DimmDevice. All DimmDevices are attached
> to a new bus called DimmBus. This bus is introduced so that we no longer
> depend on hotplug-capability of main system bus (the main bus does not allow
> hotplugging). T
On 03/25/2013 08:24:44 PM, Richard Henderson wrote:
On 2013-03-25 17:52, Rob Landley wrote:
Can the virtio things (serial, network, block, virtfs) be used on
arbitrary
targets yet? I.E. Can I use a virtio network device on arm, mips,
powerpc,
sparc... (And can the virtio serial console hook u
Signed-off-by: Hu Tao
---
docs/specs/pvpanic.txt | 35 +++
1 file changed, 35 insertions(+)
create mode 100644 docs/specs/pvpanic.txt
diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
new file mode 100644
index 000..1f14063
--- /dev/null
+++ b/docs
When I using tcg with coroutine backend = gthread,
x86_64-softmmu/qemu-system-x86_64 will hung. Any one
working on it?
System: RH6.3
gdb:
Reading symbols from
/home/xiawenc/Workdir/Src/qemu/build/master/x86_64-softmmu/qemu-system-x86_64...done.
(gdb) r
Starting program:
/home/xiawenc/Workdir/Sr
Gcc report "hw/vmxnet3.c:972: error: ‘rx_ridx’ may be used
uninitialized in this function", so fix it.
Signed-off-by: Wenchao Xia
---
hw/vmxnet3.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/vmxnet3.c b/hw/vmxnet3.c
index 925be80..bdd256e 100644
--- a/hw/vmxnet
On Fri, Mar 22, 2013 at 09:48:18AM +0200, Gleb Natapov wrote:
> On Thu, Mar 21, 2013 at 05:17:11PM +0800, Hu Tao wrote:
> > On Thu, Mar 21, 2013 at 10:11:54AM +0100, Paolo Bonzini wrote:
> > > Il 21/03/2013 10:08, Hu Tao ha scritto:
> > > > Signed-off-by: Hu Tao
> > > > ---
> > > > src/acpi-dsdt-
On 2013-03-25 17:52, Rob Landley wrote:
Can the virtio things (serial, network, block, virtfs) be used on arbitrary
targets yet? I.E. Can I use a virtio network device on arm, mips, powerpc,
sparc... (And can the virtio serial console hook up to qemu's stdin/stdout in
-nographic mode yet?)
I ask
On 03/25/2013 08:17:44 AM, Juan Quintela wrote:
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
If Google summer of code is still open:
http://qemu-project.org/Google_Summer_of_Code_2013
Last I checked, the older targets haven't had a lot of love. QEMU still
doe
Can the virtio things (serial, network, block, virtfs) be used on
arbitrary targets yet? I.E. Can I use a virtio network device on arm,
mips, powerpc, sparc... (And can the virtio serial console hook up to
qemu's stdin/stdout in -nographic mode yet?)
I asked this in 2010 and the answer at t
** For discussion / early review only, still not complete **
This is the second version of the ssh block device patch, previously
posted and discussed here:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg161996.html
There are multiple changes since last time, but the main one is that
thi
From: "Richard W.M. Jones"
qemu-system-x86_64 -drive file=ssh://hostname/some/image
QEMU will ssh into 'hostname' and open '/some/image' which is made
available as a standard block device.
You can specify a username (ssh://user@host/...) and/or a port number
(ssh://host:port/...).
Current li
On Mon, 25 Mar 2013, Gerd Hoffmann wrote:
No, it is not, and yes, this is where the inconsistency comes from. We
read wred+wgreen+wblue directly from the surface whereas depth is cached
in the vmware vga state struct. Patch attached. Not fully tested yet.
Tried that before and it didn't work
The code to load the high 64 bits assumed that the insn used to
load the low 64 bits zero-extended. Enforce that.
Cc: Alexander Graf
Signed-off-by: Richard Henderson
---
tcg/s390/tcg-target.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tcg/s390/tcg-target.c b/tcg/s390/t
On 2013-03-25 06:19, Alexander Graf wrote:
This is because lgfi leaves the register negative, but iihl doesn't replace the
upper 16 bits, only [48..32].
The patch below fixes it for me, but I'm sure you can come up with something
cleaner, better and working on non-ext-imm machines :).
Oops,
The functions CPSGetCurrentProcess and CPSEnableForegroundOperation
are deprecated in newer versions of MacOSX and cause warning messages
to be logged to the system log. Instead, use the new preferred method
of promoting our console process up to a graphical app with menubar
and Dock icon, which is
In MacOSX 10.6 and above the NSOpenPanel beginSheetForDirectory
method is deprecated. Use the preferred replacements instead.
We retain the original code for use on earlier MacOSX versions
because the replacement methods don't exist before 10.6.
Signed-off-by: Peter Maydell
---
ui/cocoa.m | 16 +
Avoid the NSOpenPanel filename method (deprecated in MacOSX 10.6)
in favour of using the URL method and extracting the path from the
resulting NSUrl object.
Signed-off-by: Peter Maydell
---
ui/cocoa.m | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ui/cocoa.m b/ui/cocoa.m
ind
On MacOSX 10.8 QEMU provokes system log messages:
11/03/2013 17:03:29.998 qemu-system-arm[42586]: objc[42586]: Object
0x7ffbf9c2f3b0 of class NSScreen autoreleased with no pool in place - just
leaking - break on objc_autoreleaseNoPool() to debug
11/03/2013 17:03:29.999 qemu-system-arm[42586]: objc
These patches fix various compiler and runtime warnings QEMU provokes
on MacOSX 10.8. The first two fix a leak and some deprecated functions
which cause warnings in the system log when QEMU runs. The second
two avoid some functions which cause compile time warnings about
use of functions deprecated
On 03/25/2013 06:05 PM, Anthony Liguori wrote:
Stefan Berger writes:
[argh, just posted this to qemu-trivial -- it's not trivial]
Hello!
I am posting this message to revive the previous discussions about the
design of vNVRAM / blobstore cc'ing (at least) those that participated
in this disc
These commands return the maximum number of CPUs supported by the
currently running emulator instance, as defined in its QEMUMachine
struct.
Signed-off-by: Michal Novotny
---
hmp-commands.hx | 14 ++
hmp.c| 15 +++
hmp.h| 1 +
qapi-schema.json |
These commands return the maximum number of CPUs supported by the
currently running emulator instance, as defined in its QEMUMachine
struct.
Signed-off-by: Michal Novotny
---
hmp-commands.hx | 14 ++
hmp.c| 8
hmp.h| 1 +
qapi-schema.json | 11
Stefan Berger writes:
> [argh, just posted this to qemu-trivial -- it's not trivial]
>
>
> Hello!
>
> I am posting this message to revive the previous discussions about the
> design of vNVRAM / blobstore cc'ing (at least) those that participated
> in this discussion 'back then'.
>
> The first g
Enable PCIe devices to negotiate links.
Signed-off-by: Alex Williamson
---
v2:
- Stick with the capabilities of the hardware we're emulating for
ioh3420 & xio3130 bandwidth (and pre-enable more)
- Use qemu_fls
- Fixes for multifunction devices
- Use device current link settings as targets
On Mon, 25 Mar 2013 22:07:36 +0100
Paolo Bonzini wrote:
> Il 25/03/2013 20:40, Luiz Capitulino ha scritto:
> > Commit f628926bb423fa8a7e0b114511400ea9df38b76a changed monitor_flush()
> > to retry on qemu_chr_fe_write() errors. However, the Monitor's output
> > buffer can keep growing while the re
[argh, just posted this to qemu-trivial -- it's not trivial]
Hello!
I am posting this message to revive the previous discussions about the
design of vNVRAM / blobstore cc'ing (at least) those that participated
in this discussion 'back then'.
The first goal of the implementation is to provid
Am 25.03.2013 um 15:34 schrieb Paolo Bonzini :
> Il 25/03/2013 14:32, Peter Lieven ha scritto:
>>
>> Am 25.03.2013 um 14:23 schrieb Peter Lieven :
>>
>>>
>>> Am 25.03.2013 um 14:02 schrieb Paolo Bonzini :
>>>
> Maybe I should have explained the output more detailed. The percentages
>
> By default, custom names should not be allowed. Perhaps the
> qemu-bridge-helper configuration file needs an option to specify a
> glob pattern, e.g. vm*.
>
> This way the host system administrator can restrict network interface
> names while still allowing humand-friendly names.
Ok, lets go t
Il 25/03/2013 20:40, Luiz Capitulino ha scritto:
> Commit f628926bb423fa8a7e0b114511400ea9df38b76a changed monitor_flush()
> to retry on qemu_chr_fe_write() errors. However, the Monitor's output
> buffer can keep growing while the retry is not issued and this can
> cause the buffer to overflow.
>
Result of git bisect:
commit 837d1f978224f7e7b020c71ffb10b291952cc596
Merge: a6fc23e 2b35e93
Author: Blue Swirl
Date: Sat Jan 12 12:46:57 2013 +
Merge branch 's390-reorg' of git://repo.or.cz/qemu/rth
* 's390-reorg' of git://repo.or.cz/qemu/rth: (149 commits)
target-s390:
** Attachment added: "GDB log to match strace log"
https://bugs.launchpad.net/qemu/+bug/1158912/+attachment/3596881/+files/debug-qemu-20130325-1050.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
On 03/25/2013 01:56 PM, Eduardo Habkost wrote:
>
>>
>> It needs to be possible to fix bugs
>
> It is possible to fix them today: just write a compat function or add a
> global variable that is handled by cpu_x86_init(), and call it from the
> pc-1.3 machine-type init function. See disable_kvm
On Mon, Mar 25, 2013 at 01:45:47PM -0700, H. Peter Anvin wrote:
> On 03/25/2013 12:05 PM, Eduardo Habkost wrote:
> > On Mon, Mar 25, 2013 at 11:44:30AM -0700, H. Peter Anvin wrote:
> >> On 03/25/2013 08:15 AM, Igor Mammedov wrote:
>
> Such changes have been rejected in the past (e.g., n27
Now, all this said... if the only objection is the change of model
number for "486" then I suggest just dropping that.
-hpa
On 03/25/2013 12:05 PM, Eduardo Habkost wrote:
> On Mon, Mar 25, 2013 at 11:44:30AM -0700, H. Peter Anvin wrote:
>> On 03/25/2013 08:15 AM, Igor Mammedov wrote:
Such changes have been rejected in the past (e.g., n270 Atom).
I personally wouldn't object to 486 changes, but I guess it
On Mon, 25 Mar 2013 16:35:11 +0100
Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov
> ---
> v2:
> * s/cpu_set/cpu-set/
> * qmp doc style fix
> * use bool type instead of opencodding online/offline string
> suggested-by: Eric Blake
> changes are on WIP branch: https://github.com/
On Fri, Mar 01, 2013 at 11:56:00PM +0100, Jiri Denemark wrote:
[...]
> > > > = Getting information about CPU models =
> > > >
> > > > Requirement: libvirt uses the predefined CPU models from QEMU, but it
> > > > needs to
> > > > be able to query for CPU model details, to find out how it can creat
On 03/25/13 14:56, Igor Mitsyanko wrote:
> On 03/25/2013 02:37 PM, Gerd Hoffmann wrote:
>>
>>>Hi,
>>>
>>> [5425.580115] displaysurface_create_from surface=0x7ff315d3df40,
800x600, bpp 16, bswap 0 [5425.580257] displaysurface_free
surface=0x7ff3158c33b0
>>>
>>> This is vga=0x314
On 03/25/2013 02:09 PM, Luiz Capitulino wrote:
> On Mon, 25 Mar 2013 16:35:11 +0100
> Igor Mammedov wrote:
>
>> +void qmp_cpu_set(int64_t id, const bool online, Error **errp)
>> +{
>> +if (online) {
>> +do_cpu_hot_add(id, errp);
>> +} else {
>> +error_setg(errp, "Unplug i
Applied. Thanks.
Regards,
Anthony Liguori
Applied. Thanks.
Regards,
Anthony Liguori
Hi,
>>> The previous version of monitor_flush() ignores errors, and everything
>>> works, so doing the same thing here fixes the problem :)
>>
>> No, ignoring errors breaks qmp because the output isn't valid json any
>> more when you cut off something ...
>
> What you mean "when you cut off"? W
Am 25.03.2013 um 18:30 hat Kevin Wolf geschrieben:
> This gets rid of the nb_clusters and keep_clusters and the associated
> complicated calculations. Just advance the number of bytes that have
> been processed and everything is fine.
>
> This patch advances the variables even after the last opera
Commit f628926bb423fa8a7e0b114511400ea9df38b76a changed monitor_flush()
to retry on qemu_chr_fe_write() errors. However, the Monitor's output
buffer can keep growing while the retry is not issued and this can
cause the buffer to overflow.
To reproduce this issue, just start qemu and type on the Mo
Long overdue.
Signed-off-by: Luiz Capitulino
---
include/qapi/qmp/qstring.h | 1 +
qobject/qstring.c | 8
2 files changed, 9 insertions(+)
diff --git a/include/qapi/qmp/qstring.h b/include/qapi/qmp/qstring.h
index 0e690f4..1bc3666 100644
--- a/include/qapi/qmp/qstring.h
+++ b/
Hi,
This series fixes an easy to reproduce assertion in the Monitor code. The
second patch contains all the relevant details.
Gerd, I'd like a reviewed-by from you before merging this.
Luiz Capitulino (2):
qstring: add qobject_get_length()
Monitor: Make output buffer dynamic
include/qapi/q
On 03/25/2013 11:30 AM, Kevin Wolf wrote:
> The old code detected an overlapping allocation even when the
> allocations didn't actually overlap, but were only adjacent.
>
> Signed-off-by: Kevin Wolf
> ---
> block/qcow2-cluster.c | 2 +-
> tests/qemu-iotests/038.out | 10 +-
> 2 fil
On Mon, Mar 25, 2013 at 11:44:30AM -0700, H. Peter Anvin wrote:
> On 03/25/2013 08:15 AM, Igor Mammedov wrote:
> >>
> >> Such changes have been rejected in the past (e.g., n270 Atom).
> >> I personally wouldn't object to 486 changes, but I guess it should
> >> rather be handled via Igor's CPU stati
On 03/25/2013 11:30 AM, Kevin Wolf wrote:
> The unlock wakes up the next coroutine, but the currently running
> coroutine will lock it again before it yields, so this doesn't make a
> lot of sense.
>
> Signed-off-by: Kevin Wolf
> ---
> block/qcow2.c | 2 --
> 1 file changed, 2 deletions(-)
Code
On Mon, Mar 25, 2013 at 04:15:15PM +0100, Igor Mammedov wrote:
> On Mon, 25 Mar 2013 10:39:36 +0100
> Andreas Färber wrote:
>
> > Am 28.02.2013 03:12, schrieb H. Peter Anvin:
> > > From: "H. Peter Anvin"
> > >
> > > Add models for 486SX, and pre-CPUID versions of the 486 (DX & SX).
> > > Change
On 03/25/2013 11:30 AM, Kevin Wolf wrote:
> This should be based on the virtual disk size, not on the size of the
> image.
>
> Interesting observation: With some VM state stored in the image file,
> percentages higher than 100% are possible, even though snapshots
> themselves are ignored. This is
Am 25.03.2013 um 18:30 hat Kevin Wolf geschrieben:
> Instead of just checking once in exactly this order if there are
> dependendies, non-COW clusters and new allocation, this starts looping
> around these. This way we can, for example, gather non-COW clusters after
> new allocations as long as the
On 03/25/2013 08:15 AM, Igor Mammedov wrote:
>>
>> Such changes have been rejected in the past (e.g., n270 Atom).
>> I personally wouldn't object to 486 changes, but I guess it should
>> rather be handled via Igor's CPU static properties that I have in my
>> review queue: The .model value would be
On Mon, 25 Mar 2013 17:31:33 +0100
Michal Novotny wrote:
> These commands return the maximum number of CPUs supported by the
> currently running emulator instance, as defined in its QEMUMachine
> struct.
I've applied this patch to the QMP tree, but with one change (see below).
>
> Signed-off-b
On Mar 25, 2013 5:40 PM, "Peter Maydell" wrote:
>
> Now we have error_setg() we can improve the error message emitted if
> you attempt to set a property of a device after the device is realized
> (the previous message was "permission denied" which was not very
> informative).
>
> Signed-off-by: Pe
On 03/23/2013 06:24:49 AM, Peter Maydell wrote:
On 22 March 2013 22:05, Scott Wood wrote:
> On 03/22/2013 08:08:57 AM, Peter Maydell wrote:
>> The memory API flattens the tree of memory regions down into a flat
>> view of the address space. These callbacks get called for the
>> final flattened v
handle_alloc() is now called with the offset at which the actual new
allocation starts instead of the offset at which the whole write request
starts, part of which may already be processed.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 44 +++-
blo
This is a more precise description of what really constitutes a
dependency. The behaviour doesn't change at this point because the COW
area of the old request is still aligned to cluster boundaries and
therefore an overlap is detected wheneven the requests touch any part of
the same cluster.
Signe
On Sun, 2013-03-24 at 11:14 +0200, Michael S. Tsirkin wrote:
> On Fri, Mar 22, 2013 at 09:25:13AM -0600, Alex Williamson wrote:
> > On Thu, 2013-03-21 at 18:56 +0200, Michael S. Tsirkin wrote:
> > > On Tue, Mar 19, 2013 at 04:24:47PM -0600, Alex Williamson wrote:
> > > > Enable PCIe devices to nego
Instead of just checking once in exactly this order if there are
dependendies, non-COW clusters and new allocation, this starts looping
around these. This way we can, for example, gather non-COW clusters after
new allocations as long as the host cluster offsets stay contiguous.
Once handle_depende
This patch is mainly to separate the indentation change from the
semantic changes. All that really changes here is that everything moves
into a while loop, all 'goto done' become 'break' and at the end of the
loop a new 'break is inserted.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 13
Look only for clusters that start at a given physical offset.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 28
1 file changed, 20 insertions(+), 8 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index c36b1e7..3588773 100644
--- a/bl
Now *bytes is used to return the length of the area that can be written
to without performing an allocation or COW.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 23 +--
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 133 +++---
trace-events | 1 +
2 files changed, 94 insertions(+), 40 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index 2047468..4be43c3 100644
--- a/block/qco
This gets rid of the nb_clusters and keep_clusters and the associated
complicated calculations. Just advance the number of bytes that have
been processed and everything is fine.
This patch advances the variables even after the last operation even
though they aren't used any more afterwards to make
We already communicate the same information in *bytes.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index 454a30c..009f62a 100644
--- a/block/qcow2-cluste
The interface works completely on a byte granularity now and duplicated
parameters are removed.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 29 -
block/qcow2.h | 5 +
2 files changed, 21 insertions(+), 13 deletions(-)
diff --git a/block/qcow2-c
Instead of expecting a single l2meta, have a list of them. This allows
to still have a single I/O request for the guest data, even though
multiple l2meta may be needed in order to describe both a COW overwrite
and a new cluster allocation (typical sequential write case).
Signed-off-by: Kevin Wolf
handle_copied() uses its bytes parameter now to determine how many
clusters it should try to find.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 240 +++---
trace-events | 1 +
2 files changed, 152 insertions(+), 89 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index 9550927..454a30c 100644
--- a/block/qc
Things can be simplified a bit now. No semantic changes.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 110 --
1 file changed, 53 insertions(+), 57 deletions(-)
diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
index 457f162..2047
Handling overlapping allocations isn't just a detail of cluster
allocation. It is rather one of three ways to get the host cluster
offset for a write request:
1. If a request overlaps an in-flight allocations, the cluster offset
can be taken from there (this is what handle_dependencies will evo
This should be based on the virtual disk size, not on the size of the
image.
Interesting observation: With some VM state stored in the image file,
percentages higher than 100% are possible, even though snapshots
themselves are ignored. This is a qcow2 bug to be fixed another day: The
VM state shou
This moves some code that prepares the allocation of new clusters to
where the actual allocation happens. This is the minimum required to be
able to move it to a separate function in the next patch.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 35 ---
1 f
The unlock wakes up the next coroutine, but the currently running
coroutine will lock it again before it yields, so this doesn't make a
lot of sense.
Signed-off-by: Kevin Wolf
---
block/qcow2.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 8ea696a..3f7e
The old code detected an overlapping allocation even when the
allocations didn't actually overlap, but were only adjacent.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 2 +-
tests/qemu-iotests/038.out | 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/
This is the start of the latest Delayed COW series. As there seem to be serious
problems with the actual Delayed COW (which in fact exist today, but would
become a bit easier to hit) and I don't have the time to complete this at the
moment, here is another series with preparatory patches, for which
Version 3 sent to both you and list.
Michal
On 03/25/2013 05:27 PM, Luiz Capitulino wrote:
> On Mon, 25 Mar 2013 17:24:02 +0100
> Michal Novotny wrote:
>
+void hmp_query_cpu_max(Monitor *mon, const QDict *qdict)
+{
+int cpu_max;
+Error *errp = NULL;
+
+c
On Mon, 25 Mar 2013 17:24:02 +0100
Michal Novotny wrote:
> >> +void hmp_query_cpu_max(Monitor *mon, const QDict *qdict)
> >> +{
> >> +int cpu_max;
> >> +Error *errp = NULL;
> >> +
> >> +cpu_max = qmp_query_cpu_max(&errp);
> >> +if (errp) {
> >> +monitor_printf(mon, "%s\n",
On 03/25/2013 05:13 PM, Luiz Capitulino wrote:
> On Mon, 25 Mar 2013 16:58:50 +0100
> Michal Novotny wrote:
>
>> These commands return the maximum number of CPUs supported by the
> /These commands/This command
I meant both of them - both QMP (query-cpu-max) one HMP (cpu_max) one.
>
>> current
On Fri, Mar 22, 2013 at 04:31:07PM -0400, Luiz Capitulino wrote:
> Today we reset fd_counter if it wraps, but it's better to abort()
> instead, as fd_counter should never reach INT64_MAX.
>
> Signed-off-by: Luiz Capitulino
Thanks, applied to qga branch with s/resonable/reasonable/ typo fix.
> -
> Right, the header's not used - but, are we certain that
> put_buffer_copy() will *always* be used for RAM in the future?
I think you should not make any assumption and proceed as if this
series didn't exist.
Paolo
On Fri, Mar 15, 2013 at 07:07:49PM +0100, Laszlo Ersek wrote:
> Laszlo Ersek (2):
> qga schema: mark optional GuestLogicalProcessor.can-offline with
> #optional
> qga schema: document generic QERR_UNSUPPORTED
>
> qga/qapi-schema.json | 18 +++---
> 1 files changed, 15 insert
On Fri, Mar 15, 2013 at 05:29:03PM +0800, Lei Li wrote:
> This patch series attempts to add Windows implementation
> for qemu-ga commands guest-get-time and guest-set-time.
Thanks, applied to qga branch.
>
> The previous thread about the interfaces introduced and
> the POSIX-specific command im
On Mon, 25 Mar 2013 16:58:50 +0100
Michal Novotny wrote:
> These commands return the maximum number of CPUs supported by the
/These commands/This command
> currently running emulator instance, as defined in its QEMUMachine
> struct.
>
> Signed-off-by: Michal Novotny
> ---
> hmp-commands.hx
Peter Maydell writes:
On 25 March 2013 14:06, Torbjorn Granlund wrote:
> Still qemu-system-mips64, qemu-system-mips64el, and qemu-system-arm
> give spurious errors.
If you can provide a reasonably sized test case for
qemu-system-arm I can investigate that one.
I don't know how to
Resent now. it went to my inbox (added from SOB) so hopefully it went to
you and list too (however list is too slow to verify now).
Michal
On 03/25/2013 04:52 PM, Luiz Capitulino wrote:
> On Mon, 25 Mar 2013 13:06:27 +0100
> Michal Novotny wrote:
>
>> On 03/21/2013 01:51 PM, Luiz Capitulino wrot
On Mon, 25 Mar 2013 13:06:27 +0100
Michal Novotny wrote:
>
> On 03/21/2013 01:51 PM, Luiz Capitulino wrote:
> > On Tue, 12 Mar 2013 17:03:31 +0100
> > Michal Novotny wrote:
> >
> >> This is the patch to introduce the query-cpu-max QMP command to get
> >> the maximum number of CPUs supported by
> On 03/25/2013 02:05 AM, Paolo Bonzini wrote:
> > Interesting, do you have SeaBIOS and/or OVMF patches for this?
>
> Not at this point.
I guess you could repost 1 and 2 without the RFC tag, then.
Paolo
On 03/25/2013 02:05 AM, Paolo Bonzini wrote:
>
> Interesting, do you have SeaBIOS and/or OVMF patches for this?
>
Not at this point.
-hpa
On 25 March 2013 15:24, Anthony Liguori wrote:
> Signed-off-by: Anthony Liguori
> +#if !GLIB_CHECK_VERSION(2, 14, 0)
> +static inline guint g_timeout_add_seconds(guint interval, GSourceFunc
> function,
> + gpointer data)
> +{
> +return g_timeout_add(i
On Thu, 21 Mar 2013 20:46:57 -0600
Eric Blake wrote:
> On 03/21/2013 08:28 AM, Igor Mammedov wrote:
> > ... via do_cpu_hot_add() hook called by cpu_set QMP command,
> > for x86 target.
> >
> > * add extra check that APIC ID is in allowed range
>
> > +if (x86_cpu_is_cpu_exist(qdev_get_machin
Signed-off-by: Anthony Liguori
---
include/glib-compat.h | 27 +++
include/qemu-common.h | 2 +-
2 files changed, 28 insertions(+), 1 deletion(-)
create mode 100644 include/glib-compat.h
diff --git a/include/glib-compat.h b/include/glib-compat.h
new file mode 100644
ind
On Mon, Mar 25, 2013 at 4:03 PM, Richard Henderson wrote:
> On 03/24/2013 03:59 AM, Peter Maydell wrote:
>> PC is FF600400 so either we've messed it up already or this
>> is just "64 bit address space doesn't fit in a 32 bit one".
>
> This is probably the fallback vdso address.
Yes, it lo
Signed-off-by: Igor Mammedov
---
v2:
* s/cpu_set/cpu-set/
* qmp doc style fix
* use bool type instead of opencodding online/offline string
suggested-by: Eric Blake
changes are on WIP branch: https://github.com/imammedo/qemu/tree/cpu_set.WIP
---
include/sysemu/sysemu.h |2 ++
qa
Right, the header's not used - but, are we certain that
put_buffer_copy() will *always* be used for RAM in the future?
- Michael
On 03/25/2013 09:05 AM, Paolo Bonzini wrote:
- Messaggio originale -
Da: "Michael R. Hines"
A: "Orit Wasserman"
Cc: qemu-devel@nongnu.org, pbonz...@redha
On Mon, 25 Mar 2013 15:48:46 +0100
Igor Mammedov wrote:
> qmp-shell converts only integer arguments and the rest
> is assumed to be strings which are faithfully sent as
> quoted strings by json. But QEMU refuses to accept qmp
> command with boolean argument whose value is escaped
> as string.
>
On Mon, 25 Mar 2013 10:39:36 +0100
Andreas Färber wrote:
> Am 28.02.2013 03:12, schrieb H. Peter Anvin:
> > From: "H. Peter Anvin"
> >
> > Add models for 486SX, and pre-CPUID versions of the 486 (DX & SX).
> > Change the model number for the standard 486DX to a model which
> > actually had CPUI
On Mon, Mar 25, 2013 at 03:36:22PM +0100, Kevin Wolf wrote:
> You don't have a bdrv_co_flush_to_disk, what does this mean? Is every
> write immediately flushed to the disk, is the driver unsafe by design,
> or is this just a missing implementation detail?
Initially there is no .bdrv_co_flush_to_di
1 - 100 of 240 matches
Mail list logo
