Paolo Bonzini writes:
> On 31/10/19 11:58, John Snow wrote:
>> It's an old compatibility shim that just delegates to ide-cd or ide-hd.
>> I'd like to refactor these some day, and getting rid of the super-object
>> will make that easier.
>>
>> Either way, we don't need this.
>
> Good idea. I
"Dr. David Alan Gilbert" writes:
> * Han Han (h...@redhat.com) wrote:
>> However, another important question is: how can we avoid such undocumented
>> incompatibility appears again?
>
> The reboot-timeout one was accidental - it was a documented qemu
> feature; just no one noticed it when the
Hi,
I like to find to find out if you have a working qemu on solaris 10 or 11.
I have tried the qemu-sun4vniagara but without networking. Is the
networking support for niagara version available?
Regards
Zai
Regarding the presentation I gave at the kvm forum
on pagefaults.
Two points:
1. pagefaults are important not just for migration.
They are important for performance features such as
autonuma and huge pages, since this relies on moving
pages around.
Migration can maybe be solved by switch to
From: Zhang Chen
This patch load pulse_timer and timeout_timer in the new iothread.
The pulse timer will send pulse info to awd_node, and the timeout timer
will check the reply pulse from awd_node. If timeout occur, it will send
opt_script's data to the notification_node.
Signed-off-by: Zhang
From: Zhang Chen
This patch introduce a new module named Advanced Watch Dog,
and defined the input and output parameter. AWD use standard chardev
as the way of communicationg with the outside world.
If you want to use it, please add "--enable-awd" when configure qemu.
Demo command:
-object
From: Zhang Chen
Because Advanced Watch Dog module needs chardev socket
to initialize properly before.
Signed-off-by: Zhang Chen
---
vl.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/vl.c b/vl.c
index 6a65a64bfd..048fe458b9 100644
--- a/vl.c
+++ b/vl.c
@@ -2689,6 +2689,13 @@
From: Zhang Chen
Find and check the chardev awd_node and notification_node,
The awd_node used for keep connect with outside(like VM client/other
host/Remote server), and the notification_node used for do some
operation when disconnect event occur.
Signed-off-by: Zhang Chen
---
net/awd.c | 37
From: Zhang Chen
Advanced Watch Dog is an universal monitoring module on VMM side, it can be
used to detect network down(VMM to guest, VMM to VMM, VMM to another remote
server) and do previously set operation. Current AWD patch just accept any
input as the signal to refresh the watchdog
Patchew URL:
https://patchew.org/QEMU/20191101014528.14505-1-richardw.y...@linux.intel.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [PATCH] target/i386: return directly from hyperv_init_vcpu() if hyperv
not enabled
Type:
If hyperv is not enabled, related features are not set or enabled.
No extra work to do, return directly.
---
First time touch hyperv, hope my understanding is correct.
Signed-off-by: Wei Yang
---
target/i386/kvm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/i386/kvm.c
Hi Jones,
Thanks for your patch.
I have tested the v7 patch.
All the test is passed.
Please add
Tested-by: Zhang Lei
My test environment is below.
*QEMU
base + v7 pathc
base is
58560ad254 (origin/master, origin/HEAD, master) Merge remote-tracking branch
Also happens on Ubuntu 19.10
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1799792
Title:
Broken scaling with gtk,gl=on on a hidpi display
Status in QEMU:
New
Bug description:
Tested on QEMU
On 10/31/19 11:03 AM, Laurent Vivier wrote:
Linux kernel 5.4 will introduce a new memory map for SWIM device.
(aee6bff1c325 ("m68k: mac: Revisit floppy disc controller base addresses"))
Until this release all MMIO are mapped between 0x50f0 and 0x50f4,
but it appears that for real
If the vhost-user-scsi backend supports the VHOST_USER_F_RESET_DEVICE
protocol feature, then the device can be reset when requested.
If this feature is not supported, do not try a reset as this will send
a VHOST_USER_RESET_OWNER that the backend is not expecting,
potentially putting into an
I have updated patches [1] sent by David Vrabel last year:
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg05077.html
This change adds a new ???reset device??? feature to the vhost-user protocol
and a corresponding VHOST_USER_RESET_DEVICE message to notify vhost-user
backends when a
Add a VHOST_USER_RESET_DEVICE message which will reset the vhost user
backend. Disabling all rings, and resetting all internal state, ready
for the backend to be reinitialized.
A backend has to report it supports this features with the
VHOST_USER_PROTOCOL_F_RESET_DEVICE protocol feature bit. If
On 29/10/19 19:21, Peter Maydell wrote:
> On Tue, 29 Oct 2019 at 16:22, Paolo Bonzini wrote:
>>
>> Hello,
>>
>> this is an attempt at including kernel-doc, with small tweaks (see patch
>> 2) to support QEMU's doc comment format, in the Sphinx documentation
>> pipeline.
>>
>> The ugly part is
On 10/18/19 5:06 PM, Damien Hedde wrote:
Replace deprecated qdev_reset_all by resettable_cold_reset_fn for
the ipl registration in the main reset handlers.
This does not impact the behavior for the following reasons:
+ at this point resettable just call the old reset methods of devices
and
On 10/18/19 5:06 PM, Damien Hedde wrote:
Deprecate device_legacy_reset(), qdev_reset_all() and
qbus_reset_all() to be replaced by new functions
device_cold_reset() and bus_cold_reset() which uses resettable API.
Also introduce resettable_cold_reset_fn() which may be used as a
replacement for
On 10/18/19 5:06 PM, Damien Hedde wrote:
Adds trace events to reset procedure and when updating the parent
bus of a device.
Signed-off-by: Damien Hedde
---
hw/core/qdev.c | 27 ---
hw/core/trace-events | 9 +
2 files changed, 33 insertions(+), 3
On 31/10/19 11:58, John Snow wrote:
> It's an old compatibility shim that just delegates to ide-cd or ide-hd.
> I'd like to refactor these some day, and getting rid of the super-object
> will make that easier.
>
> Either way, we don't need this.
Good idea. I will prepare a similar patch for
We hit an issue when trying to change the log file from the monitor
console. The root of the issue here is that the qemu_logfile handle
is not thread safe. So when we try to close the file, we end up with
a seg fault. The full analysis is below along with some possible
solutions.
Will plan to
So it's been a little while and I've been trying some different
approaches. I think the problem I am having is because I don't have the
required kernel modules loaded. When I run lsmod I only see the following
two modules loaded:
Module Size Used by
nfsd
Yes, I tried running as root. I also tried it on a different computer
that is running Mac OS 10.13, and it gave the same errors.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1850570
Title:
On 10/31/19 5:08 AM, Edgar E. Iglesias wrote:
> Rebuild hflags when modifying CPUState at boot.
>
> Fixes: e979972a6a
> Signed-off-by: Edgar E. Iglesias
Reviewed-by: Luc Michel
> ---
> hw/arm/boot.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
>
On Thu, Oct 17, 2019 at 2:35 PM Basil Salman wrote:
>
> From: Basil Salman
>
> Memory block commands are only supported for linux with sysfs,
> "guest-get-memory-block-info" was not in blacklist for other
> cases.
>
> Reported on:
> https://bugzilla.redhat.com/show_bug.cgi?id=1751431
>
>
Hi,
Following Dima's presentation on virtio device fuzzing[1] and
Alexander's "[PATCH v4 00/20] Add virtual device fuzzing support"[2]
series on the mailing list, it's time discuss the roadmap for QEMU
device fuzzing in qemu.git.
We will meet at 13:45 CET on Fri 1st of November in the Forum 1/2/3
On Thu, 31 Oct 2019 at 15:57, John Snow wrote:
>
> The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-tcg-plugins-281019-4' into staging (2019-10-30
> 14:10:32 +)
>
> are available in the Git
Patchew URL: https://patchew.org/QEMU/20191031155636.18589-1-js...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [libvirt] [PULL v2 0/9] Ide patches
Type: series
Message-id: 20191031155636.18589-1-js...@redhat.com
===
From: Sam Eiderman
Add QTest tests to check the logical geometry override option.
The tests in hd-geo-test are out of date - they only test IDE and do not
test interesting MBRs.
Creating qcow2 disks with specific size and MBR layout is currently
unused - we only use a default empty MBR.
From: Sam Eiderman
Move device name construction to a separate function.
We will reuse this function in the following commit to pass logical CHS
parameters through fw_cfg much like we currently pass bootindex.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe
Hello,
Jordi Pujol, le jeu. 31 oct. 2019 14:33:00 +0100, a ecrit:
> The smbd daemon takes additional command line options
> from environment variable SMBDOPTIONS.
> Set the environment variable SMBDOPTIONS before executing qemu.
>
> Example:
>
> export SMBDOPTIONS="--option='server min
From: Sam Eiderman
Add an interface to provide direct logical CHS values for boot devices.
We will use this interface in the next commits.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Reviewed-by: Philippe Mathieu-Daudé
>
> Message: 9
> Date: Wed, 30 Oct 2019 01:46:54 -
> From: John Canada <1850...@bugs.launchpad.net>
> To: qemu-devel@nongnu.org
> Subject: [Bug 1850570] [NEW] Cannot use usb-host on Mac OS
> Message-ID:
> <
> 157240001496.28481.10507378472210680134.malone...@chaenomeles.canonical.com
>
From: Sam Eiderman
Add logical geometry variables to BlockConf.
A user can now supply "lcyls", "lheads" & "lsecs" for any HD device
that supports CHS ("cyls", "heads", "secs").
These devices include:
* ide-hd
* scsi-hd
* virtio-blk-pci
In future commits we will use the provided
From: Sam Eiderman
Using fw_cfg, supply logical CHS values directly from QEMU to the BIOS.
Non-standard logical geometries break under QEMU.
A virtual disk which contains an operating system which depends on
logical geometries (consistent values being reported from BIOS INT13
AH=08) will most
From: Sam Eiderman
Fixing tabbing in block related macros.
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: John Snow
---
include/hw/block/block.h | 16
It's an old compatibility shim that just delegates to ide-cd or ide-hd.
I'd like to refactor these some day, and getting rid of the super-object
will make that easier.
Either way, we don't need this.
Signed-off-by: John Snow
Reviewed-by: Thomas Huth
Reviewed-by: Markus Armbruster
ACKed-by:
The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-tcg-plugins-281019-4'
into staging (2019-10-30 14:10:32 +)
are available in the Git repository at:
https://github.com/jnsnow/qemu.git
From: Sam Eiderman
Relevant devices are:
* ide-hd (and ide-cd, ide-drive)
* scsi-hd (and scsi-cd, scsi-disk, scsi-block)
* virtio-blk-pci
We do not call del_boot_device_lchs() for ide-* since we don't need to -
IDE block devices do not support unplugging.
Reviewed-by: Karl Heubaum
On 10/31/19 11:02 AM, Peter Maydell wrote:
> On Thu, 31 Oct 2019 at 10:59, John Snow wrote:
>>
>> The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
>>
>> Merge remote-tracking branch
>> 'remotes/stsquad/tags/pull-tcg-plugins-281019-4' into staging (2019-10-30
>>
From: Sam Eiderman
We will need to add LCHS removal logic to scsi-hd's unrealize() in the
next commit.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Tested-by: Philippe Mathieu-Daudé
On Thu, Oct 31, 2019 at 09:39:23AM +, misono.tomoh...@fujitsu.com wrote:
[..]
> > > > Hi Misono,
> > > >
> > > > Have you tried running pjdfstests. Looks like with the patch applied
> > > > I see following tests failing which were passing without the patch.
> > > > Can you please have a look.
* ge...@hostfission.com (ge...@hostfission.com) wrote:
>
>
> On 2019-11-01 01:52, Peter Maydell wrote:
> > On Thu, 31 Oct 2019 at 14:26, wrote:
> > > As the author of Looking Glass, I also have to consider the
> > > maintenance
> > > and the complexity of implementing the vhost protocol into
On Wed, Oct 23, 2019 at 09:25:23PM +0900, Misono Tomohiro wrote:
> When writeback mode is enabled (-o writeback), O_APPEND handling is
> done in kernel. Therefore virtiofsd clears O_APPEND flag when open.
> Otherwise O_APPEND flag takes precedence over pwrite() and write
> data may corrupt.
>
>
On 10/31/19 11:02 AM, Peter Maydell wrote:
> On Thu, 31 Oct 2019 at 10:59, John Snow wrote:
>>
>> The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
>>
>> Merge remote-tracking branch
>> 'remotes/stsquad/tags/pull-tcg-plugins-281019-4' into staging (2019-10-30
>>
Philippe Mathieu-Daudé writes:
> The kernel packaged was fetched from an unstable repository.
> Use the stable snapshot archive instead.
>
> Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Alex Bennée
Tested-by: Alex Bennée
> ---
> tests/acceptance/boot_linux_console.py | 3 ++-
> 1
Patchew URL: https://patchew.org/QEMU/20191031142734.8590-1-drjo...@redhat.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
On 2019-11-01 01:52, Peter Maydell wrote:
On Thu, 31 Oct 2019 at 14:26, wrote:
As the author of Looking Glass, I also have to consider the
maintenance
and the complexity of implementing the vhost protocol into the
project.
At this time a complete Porthole client can be implemented in 150
Edgar E. Iglesias writes:
> Rebuild hflags when modifying CPUState at boot.
>
> Fixes: e979972a6a
> Signed-off-by: Edgar E. Iglesias
> ---
> hw/arm/boot.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index c264864c11..ef6724960c 100644
> ---
On Thu, 31 Oct 2019 at 10:59, John Snow wrote:
>
> The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-tcg-plugins-281019-4' into staging (2019-10-30
> 14:10:32 +)
>
> are available in the Git
On Thu, 31 Oct 2019 at 14:26, wrote:
> As the author of Looking Glass, I also have to consider the maintenance
> and the complexity of implementing the vhost protocol into the project.
> At this time a complete Porthole client can be implemented in 150 lines
> of C without external dependencies,
These are the SVE equivalents to kvm_arch_get/put_fpsimd. Note, the
swabbing is different than it is for fpsmid because the vector format
is a little-endian stream of words.
Signed-off-by: Andrew Jones
Reviewed-by: Richard Henderson
Reviewed-by: Eric Auger
Tested-by: Masayoshi Mizuma
---
Allow cpu 'host' to enable SVE when it's available, unless the
user chooses to disable it with the added 'sve=off' cpu property.
Also give the user the ability to select vector lengths with the
sve properties. We don't adopt 'max' cpu's other sve property,
sve-max-vq, because that property is
Since 97a28b0eeac14 ("target/arm: Allow VFP and Neon to be disabled via
a CPU property") we can disable the 'max' cpu model's VFP and neon
features, but there's no way to disable SVE. Add the 'sve=on|off'
property to give it that flexibility. We also rename
cpu_max_get/set_sve_vq to
kvm_arm_create_scratch_host_vcpu() takes a struct kvm_vcpu_init
parameter. Rather than just using it as an output parameter to
pass back the preferred target, use it also as an input parameter,
allowing a caller to pass a selected target if they wish and to
also pass cpu features. If the caller
Enable SVE in the KVM guest when the 'max' cpu type is configured
and KVM supports it. KVM SVE requires use of the new finalize
vcpu ioctl, so we add that now too. For starters SVE can only be
turned on or off, getting all vector lengths the host CPU supports
when on. We'll add the other SVE CPU
Add support for the query-cpu-model-expansion QMP command to Arm. We
do this selectively, only exposing CPU properties which represent
optional CPU features which the user may want to enable/disable.
Additionally we restrict the list of queryable cpu models to 'max',
'host', or the current type
Extend the SVE vq map initialization and validation with KVM's
supported vector lengths when KVM is enabled. In order to determine
and select supported lengths we add two new KVM functions for getting
and setting the KVM_REG_ARM64_SVE_VLS pseudo-register.
This patch has been co-authored with
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates
Since Linux kernel v5.2-rc1 KVM has support for enabling SVE in guests.
This series provides the QEMU bits for that enablement. First, we
select existing CPU properties representing features we want to
advertise in addition to the SVE vector lengths and prepare
them for a qmp query. Then we
Now that Arm CPUs have advertised features lets add tests to ensure
we maintain their expected availability with and without KVM.
Signed-off-by: Andrew Jones
Reviewed-by: Eric Auger
---
tests/Makefile.include | 5 +-
tests/arm-cpu-features.c | 253 +++
2
Hello,
Many thanks Laurent,
This is the version 2 of this patch, has been modified according to
the qemu guidelines.
**
From: Jordi Pujol Palomer
Date: Thu, 31 Oct 2019 14:31:14 +0200
Subject: [PATCH v2] QEMU samba daemon: additional command line
On 2019-11-01 00:24, Dr. David Alan Gilbert wrote:
* ge...@hostfission.com (ge...@hostfission.com) wrote:
Hi Dave,
On 2019-10-31 05:52, Dr. David Alan Gilbert wrote:
> * ge...@hostfission.com (ge...@hostfission.com) wrote:
> > Hi All,
> >
> > Over the past week, I have been working to come
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Thursday, October 31, 2019 5:33 AM
> Subject: Re: [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to
> VM
>
>
> On 2019/10/25 下午6:12, Tian, Kevin wrote:
> >> From: Jason Wang [mailto:jasow...@redhat.com]
> >> Sent: Friday,
On 10/31/19 5:08 AM, Edgar E. Iglesias wrote:
Rebuild hflags when modifying CPUState at boot.
Fixes: e979972a6a
Signed-off-by: Edgar E. Iglesias
---
hw/arm/boot.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index c264864c11..ef6724960c 100644
---
On 10/31/19 9:53 AM, Gerd Hoffmann wrote:
Signed-off-by: Gerd Hoffmann
---
tests/vm/netbsd | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/vm/netbsd b/tests/vm/netbsd
index d1bfd0..33779402dd 100755
--- a/tests/vm/netbsd
+++ b/tests/vm/netbsd
@@ -22,7 +22,7 @@
On 10/31/19 9:53 AM, Gerd Hoffmann wrote:
Use new helper to read all pending console output,
not just a single char. Unblocks installer boot.
Signed-off-by: Gerd Hoffmann
---
tests/vm/netbsd | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/vm/netbsd
The kernel packaged was fetched from an unstable repository.
Use the stable snapshot archive instead.
Signed-off-by: Philippe Mathieu-Daudé
---
tests/acceptance/boot_linux_console.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/acceptance/boot_linux_console.py
On 10/31/19 9:53 AM, Gerd Hoffmann wrote:
Helper function to read all console output.
Signed-off-by: Gerd Hoffmann
---
tests/vm/basevm.py | 19 +++
1 file changed, 19 insertions(+)
diff --git a/tests/vm/basevm.py b/tests/vm/basevm.py
index 2929de23aa..086bfb2c66 100755
---
Patchew URL: https://patchew.org/QEMU/20191031105904.12194-1-js...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [libvirt] [PULL 0/9] Ide patches
Type: series
Message-id: 20191031105904.12194-1-js...@redhat.com
=== TEST
Sorry for the delay,I was busy doing my job the last two weeks.
I use XFS V5 on both main host (5.3.7-arch1-2-ARCH) and backup host
(5.3.5-arch1-1-ARCH).
It seems I ran in the first bug that has been fixed upstream.
With git master (git clone at 18.10.) I could not reproduce the failure on my
* Han Han (h...@redhat.com) wrote:
> However, another important question is: how can we avoid such undocumented
> incompatibility appears again?
The reboot-timeout one was accidental - it was a documented qemu
feature; just no one noticed it when the input check was added.
Officially if we
* ge...@hostfission.com (ge...@hostfission.com) wrote:
> Hi Dave,
>
> On 2019-10-31 05:52, Dr. David Alan Gilbert wrote:
> > * ge...@hostfission.com (ge...@hostfission.com) wrote:
> > > Hi All,
> > >
> > > Over the past week, I have been working to come up with a solution
> > > to the
> > >
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Wed, Oct 30, 2019 at 10:47:00AM +, Dr. David Alan Gilbert wrote:
> > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > On Mon, Oct 21, 2019 at 11:58:02AM +0100, Dr. David Alan Gilbert (git)
> > > wrote:
> > > > From: "Dr. David Alan
PING
On Thu, Oct 17, 2019 at 3:34 PM Basil Salman wrote:
> From: Basil Salman
>
> "guest-get-memory-block-info" is enabled according to "get-info" output,
> while the command is only supported for linux with sysfs.
>
> "guest-get-memory-block-info" command was added to blacklist.
>
> Basil
30.10.2019 14:46, Tuguoyi wrote:
> There are two issues in In check_constraints_on_bitmap(),
> 1) The sanity check on the granularity will cause uint64_t
> integer left-shift overflow when cluster_size is 2M and the
> granularity is BIGGER than 32K.
> 2) The way to calculate image size that the
On Tue, 29 Oct 2019 at 14:05, Max Reitz wrote:
>
> On 18.10.19 18:10, Thomas Huth wrote:
> > Peter hit a "Could not open 'TEST_DIR/t.IMGFMT': Failed to get shared
> > 'write' lock - Is another process using the image [TEST_DIR/t.IMGFMT]?"
> > error with 130 already twice. Looks like this test is
Hi,
On 30/10/2019 08:55, Jordi Pujol wrote:
> Hello,
>
> The new version 4 of Samba disables version 1 SMB protocols, now to
> run old Win clients we must modify the temporary configuration of the
> samba daemon to enable protocols before starting the samba client.
> This patch gets the value of
On Thu, 31 Oct 2019 at 02:56, wrote:
> If you still believe that vhost-user should be used, I will do what I
> can to
> implement it, but for such a simple device I honestly believe it is
> overkill.
While not making a statement on whether vhost-user is technically
suitable in this case, I would
Another update to this that adds support for unmap notification. The
device
has also been renamed to `porthole` and now resides here:
https://github.com/gnif/qemu/blob/master/hw/misc/porthole.c
And here is the updated Linux test client.
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.
-- PMM
On Thu, 31 Oct 2019 at 10:02, Alex Bennée wrote:
>
> The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
>
> Merge remote-tracking branch
>
From: Sam Eiderman
Using fw_cfg, supply logical CHS values directly from QEMU to the BIOS.
Non-standard logical geometries break under QEMU.
A virtual disk which contains an operating system which depends on
logical geometries (consistent values being reported from BIOS INT13
AH=08) will most
From: Sam Eiderman
Add QTest tests to check the logical geometry override option.
The tests in hd-geo-test are out of date - they only test IDE and do not
test interesting MBRs.
Creating qcow2 disks with specific size and MBR layout is currently
unused - we only use a default empty MBR.
From: Sam Eiderman
We will need to add LCHS removal logic to scsi-hd's unrealize() in the
next commit.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Tested-by: Philippe Mathieu-Daudé
From: Sam Eiderman
Move device name construction to a separate function.
We will reuse this function in the following commit to pass logical CHS
parameters through fw_cfg much like we currently pass bootindex.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe
From: Sam Eiderman
Add an interface to provide direct logical CHS values for boot devices.
We will use this interface in the next commits.
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Reviewed-by: Philippe Mathieu-Daudé
From: Sam Eiderman
Fixing tabbing in block related macros.
Signed-off-by: Sam Eiderman
Signed-off-by: Sam Eiderman
Reviewed-by: Karl Heubaum
Reviewed-by: Arbel Moshe
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: John Snow
---
include/hw/block/block.h | 16
From: Sam Eiderman
Relevant devices are:
* ide-hd (and ide-cd, ide-drive)
* scsi-hd (and scsi-cd, scsi-disk, scsi-block)
* virtio-blk-pci
We do not call del_boot_device_lchs() for ide-* since we don't need to -
IDE block devices do not support unplugging.
Reviewed-by: Karl Heubaum
From: Sam Eiderman
Add logical geometry variables to BlockConf.
A user can now supply "lcyls", "lheads" & "lsecs" for any HD device
that supports CHS ("cyls", "heads", "secs").
These devices include:
* ide-hd
* scsi-hd
* virtio-blk-pci
In future commits we will use the provided
The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-tcg-plugins-281019-4'
into staging (2019-10-30 14:10:32 +)
are available in the Git repository at:
https://github.com/jnsnow/qemu.git
It's an old compatibility shim that just delegates to ide-cd or ide-hd.
I'd like to refactor these some day, and getting rid of the super-object
will make that easier.
Either way, we don't need this.
Signed-off-by: John Snow
Reviewed-by: Thomas Huth
Reviewed-by: Markus Armbruster
ACKed-by:
Thank you for this work. I hope it will be fine now.
On 31.10.2019 09:53, Gerd Hoffmann wrote:
> Use new helper to read all pending console output,
> not just a single char. Unblocks installer boot.
>
> Signed-off-by: Gerd Hoffmann
> ---
> tests/vm/netbsd | 2 +-
> 1 file changed, 1
On Thu, Oct 31, 2019 at 09:15:56AM +0100, Greg Kurz wrote:
> On Wed, 30 Oct 2019 17:32:43 +0100
> David Gibson wrote:
>
> > We have to set the default model of all machine classes, not just for the
> > active one. Otherwise, "query-machines" will indicate the wrong CPU model
> >
On Wed, Oct 30, 2019 at 06:32:28PM +0100, David Hildenbrand wrote:
> On 30.10.19 17:32, David Gibson wrote:
> > We have to set the default model of all machine classes, not just for the
> > active one. Otherwise, "query-machines" will indicate the wrong CPU model
> > ("qemu-s390x-cpu" instead of
Linux kernel 5.4 will introduce a new memory map for SWIM device.
(aee6bff1c325 ("m68k: mac: Revisit floppy disc controller base addresses"))
Until this release all MMIO are mapped between 0x50f0 and 0x50f4,
but it appears that for real hardware 0x50f0 is not the base address:
the
From: Cleber Rosa
There's an updated version of the Debian package containing the m68k
Kernel.
Now, if the package gets updated again, the test won't fail, but will
be canceled. A more permanent solution is certainly needed.
Signed-off-by: Cleber Rosa
Reviewed-by: Alex Bennée
Tested-by:
The following changes since commit 68d8ef4ec540682c3538d4963e836e43a211dd17:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-tcg-plugins-281019-4'
into staging (2019-10-30 14:10:32 +)
are available in the Git repository at:
https://github.com/stsquad/qemu.git
On Wed, 30 Oct 2019 at 18:09, Richard Henderson
wrote:
>
> Just one easy patch that made the cutoff.
>
>
> r~
>
>
> The following changes since commit 16884391c750d0c5e863f55ad7146fc5181e:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2019-10-29'
> into staging
1 - 100 of 121 matches
Mail list logo
