Which command line parameters are passed to QEMU? Is your system able to
use KVM (e.g. did you enable virtualization support in your BIOS)?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
On Fri, Feb 16, 2018 at 02:46:35PM -0600, Eric Blake wrote:
> On 02/15/2018 07:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> >Simple way to have auto generated filenames with auto clenup. Like
>
> s/clenup/cleanup/
>
> >FilePath but without using 'with' statement and without additional
> >indentat
> On Feb 19, 2018, at 5:11 AM, Tomáš Golembiovský wrote:
>
> On Wed, 14 Feb 2018 00:07:53 +0200
> "Michael S. Tsirkin" wrote:
>
>> On Tue, Feb 13, 2018 at 12:29:39PM -0800, Jonathan Helman wrote:
>>>
>>>
>>> On 02/05/2018 04:08 AM, Tomáš Golembiovský wrote:
ping
On Tue, 5
> On Feb 19, 2018, at 4:43 AM, Tomáš Golembiovský wrote:
>
> Document statistics added in commits
>
>commit a0d06486b445985b8d128df172daefbae205bffd
>Author: Denis V. Lunev
>Date: Wed Feb 24 10:50:48 2016 +0300
>
>virtio-balloon: add 'available' counter
>
> and
>
>
On Tue, Feb 20, 2018 at 04:18:01AM +, Mark Cave-Ayland wrote:
> On 20/02/18 03:28, David Gibson wrote:
>
> > On Mon, Feb 19, 2018 at 06:19:14PM +, Mark Cave-Ayland wrote:
> > > Signed-off-by: Mark Cave-Ayland
> > > ---
> > > hw/intc/heathrow_pic.c | 126
> > > ++
On Mon, Feb 19, 2018 at 06:19:17PM +, Mark Cave-Ayland wrote:
> Signed-off-by: Mark Cave-Ayland
Reviewed-by: David Gibson
> ---
> hw/misc/macio/macio.c | 43 +
> hw/ppc/mac.h | 3 --
> hw/ppc/mac_newworld.c | 1 +
> hw/ppc/mac_oldw
On Mon, Feb 19, 2018 at 06:19:18PM +, Mark Cave-Ayland wrote:
> Also switch macio_oldworld_realize() over to use it rather than using the
> pic_mem
> memory region directly.
>
> Signed-off-by: Mark Cave-Ayland
Reviewed-by: David Gibson
> ---
> hw/misc/macio/macio.c | 14 +
On 20/02/18 04:20, David Gibson wrote:
On Mon, Feb 19, 2018 at 06:19:15PM +, Mark Cave-Ayland wrote:
Signed-off-by: Mark Cave-Ayland
---
hw/intc/heathrow_pic.c | 31 ---
hw/intc/trace-events | 5 +
include/hw/intc/heathrow_pic.h | 1 +
On Mon, Feb 19, 2018 at 06:19:15PM +, Mark Cave-Ayland wrote:
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/intc/heathrow_pic.c | 31 ---
> hw/intc/trace-events | 5 +
> include/hw/intc/heathrow_pic.h | 1 +
> 3 files changed, 18 insertions(+
On Mon, Feb 19, 2018 at 06:19:16PM +, Mark Cave-Ayland wrote:
> This enables the device to be made available during the setup of the Old World
> machine. In order to pass back the previous set of IRQs we temporarily
> introduce
> a new pic_irqs parameter until it can be removed.
>
> An additi
On 20/02/18 03:28, David Gibson wrote:
On Mon, Feb 19, 2018 at 06:19:14PM +, Mark Cave-Ayland wrote:
Signed-off-by: Mark Cave-Ayland
---
hw/intc/heathrow_pic.c | 126 +++--
include/hw/intc/heathrow_pic.h | 49
2 files change
On Mon, Feb 19, 2018 at 06:19:12PM +, Mark Cave-Ayland wrote:
> The current recommendation is to embed subdevices directly within their
> container
> device, so do this for the DBDMA device.
>
> Signed-off-by: Mark Cave-Ayland
Applied, thanks.
> ---
> hw/misc/macio/macio.c | 13 +++---
On Mon, Feb 19, 2018 at 06:19:14PM +, Mark Cave-Ayland wrote:
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/intc/heathrow_pic.c | 126
> +++--
> include/hw/intc/heathrow_pic.h | 49
> 2 files changed, 119 insertions(+), 56 deletion
On Mon, Feb 19, 2018 at 06:19:13PM +, Mark Cave-Ayland wrote:
> Now that the ESCC device is instantiated directly via qdev, move it to within
> the macio device and wire up the IRQs and memory regions using the sysbus API.
>
> This enables to remove the now-obsolete escc_mem parameter to the m
On Mon, Feb 19, 2018 at 11:34:25AM +0100, BALATON Zoltan wrote:
1;5002;0c> Add emulation of aCube Sam460ex board based on AMCC 460EX embedded
SoC.
> This is not a complete implementation yet with a lot of components
> still missing but enough for the U-Boot firmware to start and to boot
> a Linux
Any news or fixes?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1734810
Title:
Windows guest virtual PC running abnormally slow
Status in Boxes:
New
Status in KVM:
New
Status in libvirt:
Ne
Signed-off-by: Emilio G. Cota
---
accel/tcg/translator.c | 21 ++---
include/exec/translator.h | 6 +++---
target/alpha/translate.c | 6 ++
target/arm/translate-a64.c | 8 +++-
target/arm/translate.c | 9 +++--
target/hppa/translate.c| 7 ++-
ta
Changes since v1:
- Instead of passing max_insns to tb_start, merge max_insns into base,
as suggested by Richard.
Note that I'm using an int, which is what all the callers were using
and is what the "bound" variables use too.
- Added rth's R-b tag to patch 2
I left out the suggestion of ha
This was fairly straightforward since it had already been converted
to DisasContextBase; just had to add TARGET_TOO_MANY to the switch
in tb_stop.
Reviewed-by: Richard Henderson
Signed-off-by: Emilio G. Cota
---
target/sh4/translate.c | 171 +
1 f
On Mon, 19 Feb 2018 12:14:51 +0100
Gerd Hoffmann wrote:
> This series adds support for a vgpu display to the qemu vfio code.
> For now only regions are supported, dmabufs will follow later.
>
> This version adds a patch to allow devices disable hotplugging, which
> will be used by vfio display s
On Mon, Feb 19, 2018 at 11:34:52 -0800, Richard Henderson wrote:
> On 02/19/2018 11:31 AM, Richard Henderson wrote:
> > On 02/15/2018 07:18 PM, Emilio G. Cota wrote:
> >> sh4 will need it.
> >>
> >> Signed-off-by: Emilio G. Cota
> >> ---
> >> accel/tcg/translator.c | 2 +-
> >> include/exec/t
On 02/19/2018 10:52 AM, Viktor Mihajlovski wrote:
On 16.02.2018 23:07, Collin L. Walling wrote:
[...]
diff --git a/hw/s390x/ipl.h b/hw/s390x/ipl.h
index 74469b1..f632c59 100644
--- a/hw/s390x/ipl.h
+++ b/hw/s390x/ipl.h
@@ -60,6 +60,9 @@ typedef struct IplBlockQemuScsi IplBlockQemuScsi;
#defin
It's been marked as deprecated since a very long time already, and
the parameter is not doing anything useful anymore except for printing
a warning, so it's now time to finally get rid of this option.
Signed-off-by: Thomas Huth
---
qemu-doc.texi | 7 ---
vl.c | 3 ---
2 files change
On 19 February 2018 at 17:10, Laurent Vivier wrote:
> The following changes since commit f0fa81767555fe2c4b5f8c9e0725a80eac1d7f56:
>
> cuda.h: Fix multiple typedef (2018-02-16 18:38:21 +)
>
> are available in the Git repository at:
>
> git://github.com/vivier/qemu.git tags/linux-user-for-2
Quoting Markus Armbruster (2018-02-11 03:35:42)
> Rename the variable holding the QAPISchemaGenFOOVisitor from gen to
> vis, to avoid confusion in the next commit.
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Michael Roth
> ---
> scripts/qapi-commands.py | 8
> scripts/qapi-ev
Quoting Markus Armbruster (2018-02-11 03:35:48)
> A massive number of objects depends on QAPI-generated headers. In my
> "build everything" tree, it's roughly 4800 out of 5100. This is
> particularly annoying when only some of the generated files change,
> say for a doc fix.
>
> Improve qapi-gen
Quoting Markus Armbruster (2018-02-11 03:35:46)
> Whenever qapi-schema.json changes, we run six programs eleven times to
> update eleven files. Similar for qga/qapi-schema.json. This is
> silly. Replace the six programs by a single program that spits out
> all eleven files.
>
> The programs bec
Quoting Markus Armbruster (2018-02-11 03:35:49)
> Error messages print absolute file names of included files even if the
> user gave a relative one on the command line:
>
> $ PYTHONPATH=scripts python -B tests/qapi-schema/test-qapi.py
> tests/qapi-schema/include-cycle.json
> In file inclu
Quoting Markus Armbruster (2018-02-11 03:35:44)
> In preparation of the next commit, which will turn the generators into
> modules. These global variables will become local to main() then.
>
> Signed-off-by: Markus Armbruster
> Reviewed-by: Eric Blake
> Reviewed-by: Marc-André Lureau
Reviewed
Quoting Markus Armbruster (2018-02-11 03:35:45)
> The next commit will introduce a common driver program for all
> generators. The generators need to be modules for that. qapi2texi.py
> already is. Make the other generators follow suit.
>
> The changes are actually trivial. Obvious in the diff
Quoting Markus Armbruster (2018-02-11 03:35:43)
> These classes encapsulate accumulating and writing output.
>
> Convert C code generation to QAPIGenC and QAPIGenH. The conversion is
> rather shallow: most of the output accumulation is not converted.
> Left for later.
>
> The indentation machine
Quoting Markus Armbruster (2018-02-11 03:36:03)
> With modular code generation, putting stuff right into
> qapi-schema.json is a bad idea. Update writing-qmp-commands.txt
> accordingly.
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Michael Roth
> ---
> docs/devel/writing-qmp-commands.txt
Quoting Markus Armbruster (2018-02-11 03:35:54)
> The generators' conversion to visitors (merge commit 9e72681d16)
> changed the processing order of entities from source order to
> alphabetical order. The next commit needs source order, so change it
> back.
>
> Signed-off-by: Markus Armbruster
>
Quoting Markus Armbruster (2018-02-11 03:35:56)
> All generated .c are named like their .h, except for qmp-marshal.c and
> qmp-commands.h. To add to the confusion, tests-qmp-commands.c falsely
> matches generated test-qmp-commands.h.
>
> Get rid of this unnecessary complication.
>
> Signed-off-b
Quoting Markus Armbruster (2018-02-11 03:35:47)
> argparse is nicer to use than getopt, and gives us --help almost for
> free.
>
> Signed-off-by: Markus Armbruster
> ---
> scripts/qapi-gen.py| 48 ++--
> scripts/qapi/common.py | 43
Quoting Markus Armbruster (2018-02-11 03:36:05)
> Move qapi-schema.json to qapi/, so it's next to its modules, and all
> files get generated to qapi/, not just the ones generated for modules.
>
> Consistently name the generated files qapi-MODULE.EXT:
> qmp-commands.[ch] become qapi-commands.[ch],
Quoting Markus Armbruster (2018-02-11 03:35:51)
> Signed-off-by: Markus Armbruster
> Reviewed-by: Marc-André Lureau
Reviewed-by: Michael Roth
> ---
> scripts/qapi-gen.py| 8 ++--
> scripts/qapi/common.py | 23 +--
> tests/qapi-schema/test-qapi.py |
Quoting Markus Armbruster (2018-02-11 03:36:07)
> We used to generate first test and later QGA QAPI code into
> qapi-generated/. Commit b93b63f574 moved the test code to tests/.
> Commit 54c2e50205 moved the QGA code to qga/qapi-generated/. The
> directory has been unused since.
>
> Signed-off-b
Quoting Markus Armbruster (2018-02-11 03:35:59)
> guardname() fails to return a valid C identifier for arguments
> containing anything but [A-Za-z0-9_.-']. Fix that. Don't bother
> protecting ticklish identifiers; header guards are all-caps, and no
> ticklish identifiers are.
>
> Signed-off-by:
Quoting Markus Armbruster (2018-02-11 03:35:50)
> Signed-off-by: Markus Armbruster
> Reviewed-by: Eric Blake
> Reviewed-by: Marc-André Lureau
Reviewed-by: Michael Roth
> ---
> scripts/qapi/common.py | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/qap
Quoting Markus Armbruster (2018-02-11 03:36:06)
> Fix up the reference to qmp-commands.hx in qmp.c. Missed in commit
> 5032a16d1d.
>
> Fix up the reference to qmp-commands.txt in
> docs/xen-save-devices-state.txt. Missed in commit 4d8bb958fa.
>
> Signed-off-by: Markus Armbruster
Reviewed-by:
Quoting Markus Armbruster (2018-02-11 03:35:58)
> Linking code from multiple separate QAPI schemata into the same
> program is possible, but involves some weirdness around built-in
> types:
>
> * We generate code for built-in types into .c only with option
> --builtins. The user is responsible
Quoting Markus Armbruster (2018-02-11 03:35:57)
> The use of QAPIGen is rather shallow so far: most of the output
> accumulation is not converted. Take the next step: convert output
> accumulation in the code-generating visitor classes. Helper functions
> outside these classes are not converted.
Quoting Markus Armbruster (2018-02-11 03:35:52)
> Signed-off-by: Markus Armbruster
> Reviewed-by: Marc-André Lureau
> ---
> scripts/qapi/common.py | 15 +--
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/qapi/common.py b/scripts/qapi/common.py
> index dce
Quoting Markus Armbruster (2018-02-11 03:36:04)
> * Fix guidance on error classes
>
> * Point to generated documentation
>
> * Drop plea for documentation, because the QAPI code generator
> enforces it since commit 3313b6124b
>
> * Minor tweaks here and there
>
> Signed-off-by: Markus Armbrus
Quoting Markus Armbruster (2018-02-11 03:35:53)
> The parse tree is a list of expressions. Except include expressions
> currently get replaced by the included file's parse tree.
>
> Instead of throwing away the include expression, keep it with the file
> name expanded so you don't have to track t
Quoting Markus Armbruster (2018-02-11 03:35:41)
> Each generator carries a copyright notice for the generator itself,
> and another one for the files it generates. Only the former have been
> updated along the way, the latter have not, and are all out of date.
>
> Fix by copying the generator's c
On 02/14/2018 07:05 PM, Emilio G. Cota wrote:
> Signed-off-by: Emilio G. Cota
> ---
> target/hppa/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/hppa/translate.c b/target/hppa/translate.c
> index 6499b39..b4b74a8 100644
> --- a/target/hppa/translate.c
On 02/19/2018 11:31 AM, Richard Henderson wrote:
> On 02/15/2018 07:18 PM, Emilio G. Cota wrote:
>> sh4 will need it.
>>
>> Signed-off-by: Emilio G. Cota
>> ---
>> accel/tcg/translator.c | 2 +-
>> include/exec/translator.h | 3 ++-
>> target/alpha/translate.c | 3 ++-
>> target/arm/transl
On 02/15/2018 07:18 PM, Emilio G. Cota wrote:
> This was fairly straightforward since it had already been converted
> to DisasContextBase; just had to add TARGET_TOO_MANY to the switch
> in tb_stop.
>
> Signed-off-by: Emilio G. Cota
> ---
> target/sh4/translate.c | 175
> +++
On 02/15/2018 07:18 PM, Emilio G. Cota wrote:
> sh4 will need it.
>
> Signed-off-by: Emilio G. Cota
> ---
> accel/tcg/translator.c | 2 +-
> include/exec/translator.h | 3 ++-
> target/alpha/translate.c | 3 ++-
> target/arm/translate-a64.c | 4 +++-
> target/arm/translate.c | 4 +++-
On 02/19/2018 10:24 AM, James Barrett wrote:
> I keep getting these warnings with a message to send email to
> qemu-devel@nongnu.org
>
> here is the command I am using:
>
> qemu-system-i386 -hda bbs.hd -fda bbs.fd -hdb fat:rw:dist
>
>
> Host OS is Ubunti 17.10, guest OS is MS-DOS 6.22
>
Wha
On 02/19/2018 12:26 PM, Alberto Garcia wrote:
+ - The L2 cache entry size has the same restrictions as the cluster
+ size (power of two, at least 512 bytes).
Worth mentioning the upper limit of the cluster size?
I thought it would be unnecessary since the that's already mentioned
several t
>>Heh. I have stopped pushing my patches (and scratched a few itches with
>>patchew instead) because I'm still a bit burned out from recent KVM
>>stuff, but this may be the injection of enthusiasm that I needed. :)
Thanks Paolo for your great work on multiqueue, that's a lot of work since the
l
By the way, one thing that makes me nervous is that we lack an
explicit "request queue" or "per-queue" concept. State can either be
per-BlockDriverState (shared state) or per-request, but not per-queue.
So far there hasn't been a need for per-queue state but there may be
opportunities to eliminat
On 19 February 2018 at 16:19, Stefan Hajnoczi wrote:
> The following changes since commit e5ecc287a7bd24a1364e23e263cb60cfc8d21eb5:
>
> Merge remote-tracking branch 'remotes/dgilbert/tags/pull-hmp-20180216' into
> staging (2018-02-16 18:39:05 +)
>
> are available in the Git repository at:
>
On Mon, Feb 19, 2018 at 6:03 PM, Paolo Bonzini wrote:
> On 18/02/2018 19:20, Stefan Hajnoczi wrote:
>> Paolo's patches have been getting us closer to multiqueue block layer
>> support but there is a final set of changes required that has become
>> clearer to me just recently. I'm curious if this
Move the remaining comment into macio.c for reference, then remove the
macio_init() function and instantiate the macio devices for both Old World
and New World machines via qdev_init_nofail() directly.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 11 +++
hw/ppc/mac_newworl
This removes the last of the functionality from macio_init() in preparation
for its subsequent removal.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/hw/misc/macio/macio.c b/hw/misc/macio/macio.c
index e5288f1
On Mon 19 Feb 2018 05:44:23 PM CET, Eric Blake wrote:
> On 02/19/2018 08:54 AM, Alberto Garcia wrote:
>> This patch updates docs/qcow2-cache.txt explaining how to use the new
>> l2-cache-entry-size parameter.
>>
>> Here's a more detailed technical description of this feature:
>>
>> https://l
Also switch macio_newworld_realize() over to use it rather than using the
pic_mem
memory region directly.
Now that both Old World and New World macio devices no longer make use of the
pic_mem memory region directly, we can remove it.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c
Signed-off-by: Mark Cave-Ayland
---
hw/intc/heathrow_pic.c | 31 ---
hw/intc/trace-events | 5 +
include/hw/intc/heathrow_pic.h | 1 +
3 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/hw/intc/heathrow_pic.c b/hw/intc/heathrow_pic
This is to faciliate access to OpenPICState when wiring up the PIC to the macio
controller.
Signed-off-by: Mark Cave-Ayland
---
hw/intc/openpic.c| 157 --
include/hw/ppc/openpic.h | 160 ++-
2 files c
This patchset eliminates the legacy macio_init() function used to setup the
ESCC and PIC memory regions and instead allows the macio device to be
instantiated directly via qdev, wiring up the ESCC internally using sysbus MMIO
memory regions and the PIC via QOM object links.
The biggest surprise in
Now that the ESCC device is instantiated directly via qdev, move it to within
the macio device and wire up the IRQs and memory regions using the sysbus API.
This enables to remove the now-obsolete escc_mem parameter to the macio_init()
function.
(Note this patch also contains small touch-ups to t
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 43 +
hw/ppc/mac.h | 3 --
hw/ppc/mac_newworld.c | 1 +
hw/ppc/mac_oldworld.c | 1 +
include/hw/misc/macio/macio.h | 75 +++
5 fi
Also switch macio_oldworld_realize() over to use it rather than using the
pic_mem
memory region directly.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 14 ++
hw/ppc/mac_oldworld.c | 8 +---
include/hw/misc/macio/macio.h | 2 ++
3 files changed, 1
Signed-off-by: Mark Cave-Ayland
---
hw/intc/heathrow_pic.c | 126 +++--
include/hw/intc/heathrow_pic.h | 49
2 files changed, 119 insertions(+), 56 deletions(-)
create mode 100644 include/hw/intc/heathrow_pic.h
diff --git a/hw/intc/h
The current recommendation is to embed subdevices directly within their
container
device, so do this for the DBDMA device.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/hw/misc/macio/macio.c b/hw/misc/
This enables the device to be made available during the setup of the Old World
machine. In order to pass back the previous set of IRQs we temporarily introduce
a new pic_irqs parameter until it can be removed.
An additional benefit of this change is that it is also possible to remove the
pic_mem p
On Sat, 17 Feb 2018 10:07:38 +0100
Jan Kiszka wrote:
[...]
> > Seems like no one is doing guest debugging with kvm on x86 except
> > me, and I'm only doing it too infrequently now: This one broke that
> > use case for SMP guests long ago. How was it tested?
> >
> > To reproduce the bug: set up
On 19.02.2018 18:17, Collin L. Walling wrote:
> On 02/19/2018 11:19 AM, Collin L. Walling wrote:
>> On 02/19/2018 11:00 AM, Thomas Huth wrote:
>>> On 19.02.2018 16:40, Collin L. Walling wrote:
On 02/17/2018 02:48 AM, Thomas Huth wrote:
> On 16.02.2018 23:07, Collin L. Walling wrote:
>
On 18/02/2018 19:20, Stefan Hajnoczi wrote:
> Paolo's patches have been getting us closer to multiqueue block layer
> support but there is a final set of changes required that has become
> clearer to me just recently. I'm curious if this matches Paolo's
> vision and whether anyone else has comment
On 02/19/2018 11:17 AM, Collin L. Walling wrote:
How is this for a compromise?
- start num_idx at 1, provide comment as for why
- change while loop comment to explain we are "counting the
_indices_ _of_ _num_"
- str[num_idx] is assigned \0, and we also decrement num_idx in one
>From an architecture point of view, nothing can be mapped into the address
space on s390x. All there is is memory. Therefore there is also not really
an interface to communicate such information to the guest. All we can do is
specify the maximum ram address and guests can probe in that range if
me
On 19/02/2018 18:31, Kashyap Chamarthy wrote:
> PCIe features are available only via the 'q35' machine type for x86 and
> the 'virt' machine type for AArch64 architecture.
>
> Mention that explicitly.
Thanks for the improvement
Reviewed-by: Marcel Apfelbaum
Thanks,
Marcel
>
> Thanks: Daniel
On 02/19/2018 03:15 AM, Thomas Huth wrote:
Other options like "-chardev" or "-device" feature a nice help text
with the available devices when being called with "help" or "?".
Since it is quite useful, especially if you want to see which network
backends have been compiled into the QEMU binary, l
On 02/19/2018 11:19 AM, Collin L. Walling wrote:
On 02/19/2018 11:00 AM, Thomas Huth wrote:
On 19.02.2018 16:40, Collin L. Walling wrote:
On 02/17/2018 02:48 AM, Thomas Huth wrote:
On 16.02.2018 23:07, Collin L. Walling wrote:
[...]
+/**
+ * uitoa:
+ * @num: an integer (base 10) to be convert
On 02/19/2018 03:15 AM, Thomas Huth wrote:
"-net dump" has been marked as deprecated since QEMU v2.10, since it
only works with the deprecated 'vlan' parameter. Network dumping should
be done with "-object filter-dump" nowadays instead. Since nobody
complained so far about the deprecation message
Instead of a sequence of "#if ... #endif" move the
selection to a function in linux-user/*/target_elf.h
We can't add them in linux-user/*/target_cpu.h
because we will need to include "elf.h" to
use ELF flags with eflags, and including
"elf.h" in "target_cpu.h" introduces some
conflicts in elfload.
From: Andreas Schwab
With glibc 2.27 the openpty function prefers the TIOCGPTPEER ioctl.
Signed-off-by: Andreas Schwab
Reviewed-by: Laurent Vivier
Message-Id:
Signed-off-by: Laurent Vivier
---
linux-user/aarch64/termbits.h| 2 ++
linux-user/alpha/termbits.h | 1 +
linux-user/arm/te
>> As migration support is not working, this change cannot really break
>> migration. As the memory hotplug device was always created, we can
>> simply continue faking support for SCLP_FC_ASSIGN_ATTACH_READ_STOR and
>> expose the same information just as if no maxmem and slots parameter was
>> giv
From: YunQiang Su
So here we need to detect the version of binaries and set
cpu_model for it.
Signed-off-by: YunQiang Su
[lv: original patch modified to move code into cpu_get_model()]
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
Message-Id: <20180124211301.10095-5-laur...@viv
From: Guido Günther
This unbreaks the testcase from
http://lists.nongnu.org/archive/html/qemu-arm/2018-01/msg00514.html
Thanks to Laurent Vivier for spotting the 7th one.
Signed-off-by: Guido Günther
Tested-by: Philippe Mathieu-Daudé
Suggested-by: Laurent Vivier
Reviewed-by: Philippe Ma
From: YunQiang Su
Add a function to return ELF e_flags and use it
to select the CPU model.
Signed-off-by: YunQiang Su
[lv: split the patch and some cleanup in get_elf_eflags()]
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
Message-Id: <20180124211301.10095-3-laur...@vivier.eu>
From: Peter Maydell
Back when we used to support compiling either with or without
NPTL threading library support, we used a macro THREAD which would
expand either to nothing (no thread support) or to __thread (threads
supported). For a long time now we have required thread support,
so remove the
From: Samuel Thibault
We properly computed the capped mask size to be put to the application
buffer, but didn't actually used it. Also, we need to return the capped mask
size instead of 0 on success.
Signed-off-by: Samuel Thibault
Reviewed-by: Laurent Vivier
Message-Id: <20180211174704.27441-1
M680x0 doesn't support the same set of instructions
as ColdFire, so we can't use "any" CPU type to execute
m68020 instructions.
We select CPU type ("m68040" or "any" for ColdFire)
according to the ELF header. If we can't, we
use by default the value used until now: "any".
Signed-off-by: Laurent Vi
The following changes since commit f0fa81767555fe2c4b5f8c9e0725a80eac1d7f56:
cuda.h: Fix multiple typedef (2018-02-16 18:38:21 +)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-for-2.12-pull-request
for you to fetch changes up to f352a021329f73d
On 02/16/2018 03:40 PM, Emilio G. Cota wrote:
> The only non-trivial modification is the use of DISAS_TOO_MANY
> in the same way is used by the generic translation loop.
>
> Signed-off-by: Emilio G. Cota
> ---
> target/s390x/translate.c | 1267
> +++---
>
On Mon, 19 Feb 2018 15:33:41 +0100
David Hildenbrand wrote:
> From an architecture point of view, nothing can be mapped into the address
> space on s390x. All there is is memory. Therefore there is also not really
> an interface to communicate such information to the guest. All we can do is
> spe
On 02/16/2018 10:08 AM, Viktor Mihajlovski wrote:
Changing the implementation of hmp_info_cpus() to call
qmp_query_cpus_fast() instead of qmp_query_cpus. This has the
following consequences:
o No further code change required for qmp_query_cpus deprecation
o HMP profits from the less disru
On 02/16/2018 10:08 AM, Viktor Mihajlovski wrote:
From: Luiz Capitulino
The query-cpus command has an extremely serious side effect:
it always interrupts all running vCPUs so that they can run
ioctl calls. This can cause a huge performance degradation for
some workloads. And most of the informa
On 02/19/2018 08:54 AM, Alberto Garcia wrote:
This patch updates docs/qcow2-cache.txt explaining how to use the new
l2-cache-entry-size parameter.
Here's a more detailed technical description of this feature:
https://lists.gnu.org/archive/html/qemu-block/2017-09/msg00635.html
And here are
On 19 February 2018 at 11:43, Marcel Apfelbaum wrote:
> Hi Peter,
>
> Changes from V1:
> * split the rdma patch into several patches.
> * fixed license issues.
> * moved Linux headers to standard-headers and fixed the used types.
> * R-B tags on all code files (patch 4/10 doesn't have an R-B t
On 19.02.2018 17:20, Paolo Bonzini wrote:
> On 19/02/2018 10:15, Thomas Huth wrote:
>> The legacy "-net" option can be quite confusing for the users since most
>> people do not expect to get a "vlan" hub between their emulated guest
>> hardware and the host backend. But so far, we are also not able
On Mon, Feb 19, 2018 at 05:31:31PM +0100, Kashyap Chamarthy wrote:
> PCIe features are available only via the 'q35' machine type for x86 and
> the 'virt' machine type for AArch64 architecture.
>
> Mention that explicitly.
>
> Thanks: Daniel Berrangé
>
> Signed-off-by: Kashyap Chamarthy
> ---
>
PCIe features are available only via the 'q35' machine type for x86 and
the 'virt' machine type for AArch64 architecture.
Mention that explicitly.
Thanks: Daniel Berrangé
Signed-off-by: Kashyap Chamarthy
---
docs/pcie.txt | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --g
On 19/02/2018 10:15, Thomas Huth wrote:
> The legacy "-net" option can be quite confusing for the users since most
> people do not expect to get a "vlan" hub between their emulated guest
> hardware and the host backend. But so far, we are also not able to get
> rid of "-net" completely, since it is
I keep getting these warnings with a message to send email to
qemu-devel@nongnu.org
here is the command I am using:
qemu-system-i386 -hda bbs.hd -fda bbs.fd -hdb fat:rw:dist
Host OS is Ubunti 17.10, guest OS is MS-DOS 6.22
WARNING: Image format was not specified for 'bbs.hd' and probing gues
1 - 100 of 208 matches
Mail list logo
