The next-cube.h file is missing the usual copyright-and-license
header; add it (same as the next-cube.c one).
Signed-off-by: Peter Maydell
---
include/hw/m68k/next-cube.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/hw/m68k/next-cube.h b/include/hw/m68k/next-cube.h
Move the rtc into the NeXTPC struct. Since this is the last
use of the 'backdoor' NextState pointer we can now remove that.
Probably the RTC should be its own device at some point: in hardware
there is a separate MCS1850 RTC chip connected to the Peripheral
Controller via a 1-bit serial
Add the vmstate for the new NeXTPC devic; this is in theory
a migration compatibility break, but this machine doesn't have
working migration currently anyway.
Signed-off-by: Peter Maydell
---
hw/m68k/next-cube.c | 34 +-
1 file changed, 33 insertions(+), 1
Make the next_irq function take a NeXTPC* as its opaque rather than
the M68kCPU*. This will make it simpler to turn the next_irq
function into a gpio input line of the NeXTPC device in the next
commit.
For this to work we have to pass the CPU to the NeXTPC device via a
link property, in the same
All the code which accesses int_status and int_mask is now doing
so via the NeXTPC->NeXTState indirection, so we can move these
fields into the NeXTPC struct where they belong.
Signed-off-by: Peter Maydell
---
hw/m68k/next-cube.c | 33 -
1 file changed, 16
Make the next_irq function be GPIO inputs to the NEXT_PC
device, rather than a freestanding set of qemu_irq lines.
This fixes a minor Coverity issue where it correctly points
out the trivial memory leak of the memory allocated in the
call to qemu_allocate_irqs().
Fixes: CID 1421962
Currently the next-cube board code open-codes a lot of handling of
interrupts and some miscellaneous registers. Move this into a proper
QOM device.
In the real hardware this functionality seems to be the
responsibility of the Peripheral Controller (PC) chip, so name the
device that.
There are
Move the registers handled by the mmio_ops struct into the NeXTPC
device. This allows us to also move the scr1 and scr2 data fields.
Signed-off-by: Peter Maydell
---
hw/m68k/next-cube.c | 80 +
1 file changed, 44 insertions(+), 36 deletions(-)
diff
The fields scsi_irq, scsi_dma, scsi_reset and fd_irq in
NeXTState are all unused, except in commented out
"this should do something like this" code. Remove the
unused fields. As and when the functionality that might
use them is added, we can put in the correct kind of
wiring (which might or might
Currently the next-cube board code open-codes a lot of handling of
interrupts and some miscellaneous registers. This series refactors
that to move most of it into a proper QOM device. (The main motivation
here is to fix the Coverity issue CID 1421962 which is a trivial
memory leak of the memory
The next_irq() function is global, but isn't actually used anywhere
outside next-cube.c. Make it static.
Signed-off-by: Peter Maydell
---
include/hw/m68k/next-cube.h | 2 --
hw/m68k/next-cube.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git
Move the registers handled by the scr_ops struct into the NeXTPC
device.
Signed-off-by: Peter Maydell
---
hw/m68k/next-cube.c | 50 ++---
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/hw/m68k/next-cube.c b/hw/m68k/next-cube.c
index
in the Git repository at:
>
> git://git.kraxel.org/qemu tags/ui-20210115-pull-request
>
> for you to fetch changes up to 763deea7e906321f8ba048c359f168f60d51c14e:
>
> vnc: add support for extended desktop resize (2021-01-15 11:22:43 +0100)
>
>
On 1/15/21 1:40 PM, Stefan Berger wrote:
On 1/15/21 11:06 AM, Philippe Mathieu-Daudé wrote:
On 1/15/21 4:53 PM, Stefan Berger wrote:
On 1/15/21 10:52 AM, Philippe Mathieu-Daudé wrote:
Subject is incorrect, this is not a removal of the tests, but
removal of their execution. The tests are still
On 1/15/21 7:11 AM, Cupertino Miranda wrote:
> As you know, we reused the code from binutils to implement the decoder.
> In that sense, we kindly request to allow us to do it through binutils
> development flow later on. We will change the tables in binutils
> and those changes will also be
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> Instead of checking iotests.py only, check all Python files in the
> qemu-iotests/ directory. Of course, most of them do not pass, so there
> is an extensive skip list for now. (The only files that do pass are
> 209, 254, 283, and
Add pvpanic PCI device support details in docs/specs/pvpanic.txt.
Signed-off-by: Mihai Carabas
---
docs/specs/pvpanic.txt | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
index a90fbca..974aafd 100644
---
To ease the PCI device addition in next patches, split the code as follows:
- generic code (read/write/setup) is being kept in pvpanic.c
- ISA dependent code moved to pvpanic-isa.c
Also, rename:
- ISA_PVPANIC_DEVICE -> PVPANIC_ISA_DEVICE.
- TYPE_PVPANIC -> TYPE_PVPANIC_ISA.
- MemoryRegion io ->
Add PCI interface support for PVPANIC device. Create a new file pvpanic-pci.c
where the PCI specific routines reside and update the build system with the new
files and config structure.
Signed-off-by: Mihai Carabas
---
docs/specs/pci-ids.txt| 1 +
hw/misc/Kconfig | 6 +++
Add a test case for pvpanic-pci device. The scenario is the same as pvpapnic
ISA device, but is using the PCI bus.
Signed-off-by: Mihai Carabas
---
tests/qtest/meson.build| 1 +
tests/qtest/pvpanic-pci-test.c | 62 ++
2 files changed, 63
This patchset adds support for pvpanic pci device.
v3 applied feedback:
- patch 1: made pvpanic isa device available only for PC, compile pvpanic-test
only when isa device is present
- patch 2: fixed device id to 0x0011, used OBJECT_DECLARE_TYPE,
PVPANIC_PCI_DEVICE, added
On Wed, Jan 13, 2021 at 09:06:29AM +0100, Cornelia Huck wrote:
> On Tue, 12 Jan 2021 10:55:11 -0800
> Ram Pai wrote:
>
> > On Tue, Jan 12, 2021 at 09:19:43AM +0100, Cornelia Huck wrote:
> > > On Mon, 11 Jan 2021 11:58:30 -0800
> > > Ram Pai wrote:
> > >
> > > > On Mon, Jan 11, 2021 at
On 1/14/21 10:02 AM, Daniel P. Berrangé wrote:
librados-dev is not required by QEMU directly, only librbd-dev.
glusterfs-common is not directly needed by QEMU.
QEMU uses ncursesw only on non-Windows hosts.
The clang package is clang 10.
flex and bison are not required by QEMU.
Standardize
On 15/01/21 18:51, Philippe Mathieu-Daudé wrote:
It is pointless to install ROM blobs for user emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
RFC because I think it would be better to make the 'blobs'
option a 'feature' instead of a boolean so we can set it
as 'auto' and then in that
On 1/15/21 2:22 PM, Greg Kurz wrote:
On Thu, 14 Jan 2021 15:06:28 -0300
Daniel Henrique Barboza wrote:
The only restriction we have when unplugging CPUs is to forbid unplug of
the boot cpu core. spapr_core_unplug_possible() does not contemplate the
I'll look into it.
I can't remember
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> There are a couple of environment variables that we fetch with
> os.environ.get() without supplying a default. Clearly they are required
> and expected to be set by the ./check script (as evidenced by
> execute_setup_common(), which checks for
On 1/15/21 11:06 AM, Philippe Mathieu-Daudé wrote:
On 1/15/21 4:53 PM, Stefan Berger wrote:
On 1/15/21 10:52 AM, Philippe Mathieu-Daudé wrote:
Subject is incorrect, this is not a removal of the tests, but
removal of their execution. The tests are still in the repository.
This is more of a
On 1/14/21 10:02 AM, Daniel P. Berrangé wrote:
llvm is not required by QEMU, just clang.
libblockdev-mpath-devel is not used by QEMU, rather it wants
device-mapper-multipath-devel.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Daniel P. Berrangé
---
On 21-01-15 18:47:20, Klaus Jensen wrote:
> On Jan 15 09:35, Keith Busch wrote:
> > On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
> > >
> > > As you already mentioned, the problem I see with this approach is that
> > > we have separate namespaces attached to separate controllers.
> On 11/11/20 10:17 AM, cupertinomira...@gmail.com wrote:
>> +/*
>> + * The macro to add boiler plate code for conditional execution.
>> + * It will add tcg_gen codes only if there is a condition to
>> + * be checked (ctx->insn.cc != 0). This macro assumes that there
>> + * is a "ctx" variable of
On 1/14/21 10:02 AM, Daniel P. Berrangé wrote:
dbus-daemon doesn't exist in centos7, it is part of dbus.
snappy is used by QEMU, not csnappy.
mesa-libEGL-devel is not used in QEMU at all, but mesa-libgbm-devel is.
vte291-devel is required for GTK3, not vte-devel.
spice-glib-devel is not
>> +void QEMU_NORETURN helper_halt(CPUARCState *env, uint32_t npc)
>> +{
>> +CPUState *cs = env_cpu(env);
>> +if (env->stat.Uf) {
>> +cs->exception_index = EXCP_PRIVILEGEV;
>> +env->causecode = 0;
>> +env->param = 0;
>> + /* Restore PC such that we point at
>> +
>> +assert(ctx->insn.limm_p == 0 && !in_delay_slot);
>> +
>> +if (ctx->insn.limm_p == 0 && !in_delay_slot) {
>> +in_delay_slot = true;
>> +uint32_t cpc = ctx->cpc;
>> +uint32_t pcl = ctx->pcl;
>> +insn_t insn = ctx->insn;
>> +
>> +ctx->cpc =
Hi Richard,
Sorry to take so long to get through the changes after your review.
I am still going through the improving process and waiting for some
internal company approval to publish the generator of the TCG
instruction definitions, as we have discussed.
Nevertheless, there are some
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> Reviewed-by: Vladimir Sementsov-Ogievskiy
> ---
> tests/qemu-iotests/124| 8 +---
> tests/qemu-iotests/iotests.py | 11 +++
> 2 files changed, 8 insertions(+), 11
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> @busy is false when the job is paused, which happens all the time
> because that is how jobs yield (e.g. for mirror at least since commit
> 565ac01f8d3).
>
> Back when 129 was added (2015), perhaps there was no better way of
> checking whether
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> Throttling on the BB has not affected block jobs in a while, so it is
> possible that one of the jobs in 129 finishes before the VM is stopped.
> We can fix that by running the job from a throttle node.
>
> Signed-off-by: Max Reitz
>
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> Before this patch, test_block_commit() performs an active commit, which
> under the hood is a mirror job. If we want to test various different
> block jobs, we should perhaps run an actual commit job instead.
>
> Doing so requires adding an
On Fri, Jan 15, 2021 at 2:43 PM Max Reitz wrote:
>
> And consequentially drop it from 297's skip list.
>
> Signed-off-by: Max Reitz
> Reviewed-by: Vladimir Sementsov-Ogievskiy
> ---
> tests/qemu-iotests/297 | 2 +-
> tests/qemu-iotests/300 | 18 +++---
> 2 files changed, 16
On Thu, Jan 14, 2021 at 10:36:43AM +, Dr. David Alan Gilbert wrote:
> * Christian Borntraeger (borntrae...@de.ibm.com) wrote:
> >
> >
> > On 13.01.21 13:42, Dr. David Alan Gilbert wrote:
> > > * Cornelia Huck (coh...@redhat.com) wrote:
> > >> On Tue, 5 Jan 2021 12:41:25 -0800
> > >> Ram Pai
> On Jan 15, 2021, at 4:20 AM, Stefan Hajnoczi wrote:
>
> On Thu, Jan 14, 2021 at 01:24:37PM -0500, Jag Raman wrote:
>>
>>
>>> On Jan 14, 2021, at 1:00 PM, Daniel P. Berrangé wrote:
>>>
>>> On Thu, Jan 14, 2021 at 12:55:58PM -0500, Jag Raman wrote:
> On Jan 14, 2021, at
On Thu, Jan 14, 2021 at 07:33:32PM +0530, P J P wrote:
> Hello,
>
> * We have received quite a few subscription requests for the 'qemu-security'
> list in the last few weeks. Majority of them are rejected because we could
> not identify the user from merely their email-id.
>
> * I have
On 1/14/21 10:02 AM, Daniel P. Berrangé wrote:
This will make diffs in later patches clearer.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Daniel P. Berrangé
---
tests/docker/dockerfiles/centos7.docker | 4 ++--
tests/docker/dockerfiles/fedora.docker| 4 ++--
On 1/15/21 4:34 PM, Stefan Weil wrote:
> Am 15.01.21 um 15:01 schrieb Peter Maydell:
>
>> I was just trying to see what updates the qemu.nsi file needed for
>> the merge-all-the-manuals-into-one-place change, and I discovered
>> that it's been broken since October when we removed the Changelog
It is pointless to install ROM blobs for user emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
RFC because I think it would be better to make the 'blobs'
option a 'feature' instead of a boolean so we can set it
as 'auto' and then in that case we could do something
blobs = have_system
Issuing 'stop' on the VM drains all nodes. If the mirror job has many
large requests in flight, this may lead to significant I/O that looks a
bit like 'stop' would make the job try to complete (which is what 129
should verify not to happen).
We can limit the I/O in flight by limiting the buffer
On Fri, Jan 15, 2021 at 06:47:20PM +0100, Klaus Jensen wrote:
> Cool!
I thought so too :)
> Question: NSIDs must be the same on each controller for shared
> namespaces, but can private namespaces "share" nsid across controllers
> in the subsystem? I don't think the spec is clear on that point.
@busy is false when the job is paused, which happens all the time
because that is how jobs yield (e.g. for mirror at least since commit
565ac01f8d3).
Back when 129 was added (2015), perhaps there was no better way of
checking whether the job was still actually running. Now we have the
@status
On Jan 15 09:35, Keith Busch wrote:
> On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
> >
> > As you already mentioned, the problem I see with this approach is that
> > we have separate namespaces attached to separate controllers. So we are
> > faking it to the max and if I/O starts
Signed-off-by: Max Reitz
Reviewed-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/124| 8 +---
tests/qemu-iotests/iotests.py | 11 +++
2 files changed, 8 insertions(+), 11 deletions(-)
diff --git a/tests/qemu-iotests/124
And consequentially drop it from 297's skip list.
Signed-off-by: Max Reitz
Reviewed-by: Willian Rampazzo
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/129 | 4 ++--
tests/qemu-iotests/297 | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
Signed-off-by: Max Reitz
Reviewed-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Eric Blake
Reviewed-by: Willian Rampazzo
---
tests/qemu-iotests/129 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/qemu-iotests/129 b/tests/qemu-iotests/129
index 0e13244d85..2fc65ada6a 100755
---
Before this patch, test_block_commit() performs an active commit, which
under the hood is a mirror job. If we want to test various different
block jobs, we should perhaps run an actual commit job instead.
Doing so requires adding an overlay above the source node before the
commit is done (and
And consequentially drop it from 297's skip list.
Signed-off-by: Max Reitz
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/297 | 2 +-
tests/qemu-iotests/300 | 18 +++---
2 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/tests/qemu-iotests/297
Throttling on the BB has not affected block jobs in a while, so it is
possible that one of the jobs in 129 finishes before the VM is stopped.
We can fix that by running the job from a throttle node.
Signed-off-by: Max Reitz
Reviewed-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
Instead of checking iotests.py only, check all Python files in the
qemu-iotests/ directory. Of course, most of them do not pass, so there
is an extensive skip list for now. (The only files that do pass are
209, 254, 283, and iotests.py.)
(Alternatively, we could have the opposite, i.e. an
Cover letters:
v1: https://lists.nongnu.org/archive/html/qemu-block/2021-01/msg00254.html
v2: https://lists.nongnu.org/archive/html/qemu-block/2021-01/msg00296.html
v3: https://lists.nongnu.org/archive/html/qemu-block/2021-01/msg00371.html
git:
https://github.com/XanClic/qemu.git fix-129-2-v4
There are a couple of environment variables that we fetch with
os.environ.get() without supplying a default. Clearly they are required
and expected to be set by the ./check script (as evidenced by
execute_setup_common(), which checks for test_dir and
qemu_default_machine to be set, and aborts if
On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
>
> As you already mentioned, the problem I see with this approach is that
> we have separate namespaces attached to separate controllers. So we are
> faking it to the max and if I/O starts going through the other
> controller we end
On 15/01/21 16:57, Peter Maydell wrote:
On Fri, 15 Jan 2021 at 15:52, Stefan Weil wrote:
I forgot to mention that some of the problems with the Meson build also
occur on macOS with Homebrew: they always happen when a software package
requires special compiler flags to find its include files or
On Fri, 15 Jan 2021 14:01:28 +0530
Bharata B Rao wrote:
> On Wed, Jan 13, 2021 at 05:22:56PM +0100, Greg Kurz wrote:
> > Hi Bharata,
> >
> > On Wed, 6 Jan 2021 14:29:10 +0530
> > Bharata B Rao wrote:
> >
> > > If KVM_CAP_RPT_INVALIDATE KVM capability is enabled, then
> > >
> > > - indicate
On Fri, Jan 15, 2021 at 9:17 AM Havard Skinnemoen
wrote:
> +Hao Wu
>
> On Fri, Jan 15, 2021 at 1:15 AM Philippe Mathieu-Daudé
> wrote:
> >
> > On 1/15/21 8:56 AM, Gan Qixin wrote:
> > > The pwm_qom_get function didn't free "response", which caused an
> indirect
> > > memory leak. So use
On Thu, 14 Jan 2021 15:06:28 -0300
Daniel Henrique Barboza wrote:
> The only restriction we have when unplugging CPUs is to forbid unplug of
> the boot cpu core. spapr_core_unplug_possible() does not contemplate the
I can't remember why this restriction was introduced in the first place...
This
On Tue, Jan 12, 2021 at 1:45 PM Thomas Huth wrote:
>
> The "And a hippo new year" image from the QEMU advent calendar 2020
> can be used to test the virtex-ml507 ppc machine.
>
> Signed-off-by: Thomas Huth
> ---
> tests/acceptance/machine_ppc.py | 18 ++
> 1 file changed, 18
On Tue, Jan 12, 2021 at 1:44 PM Thomas Huth wrote:
>
> We can use the "Stupid creek" image to test the mpc8544ds ppc machine.
>
> Signed-off-by: Thomas Huth
> ---
> tests/acceptance/machine_ppc.py | 17 +
> 1 file changed, 17 insertions(+)
Reviewed-by: Willian Rampazzo
+Hao Wu
On Fri, Jan 15, 2021 at 1:15 AM Philippe Mathieu-Daudé wrote:
>
> On 1/15/21 8:56 AM, Gan Qixin wrote:
> > The pwm_qom_get function didn't free "response", which caused an indirect
> > memory leak. So use qobject_unref() to fix it.
> >
> > ASAN shows memory leak stack:
> >
> > Indirect
On 1/14/21 9:56 PM, Gan Qixin wrote:
> When compiling qemu-fuzz-i386 on aarch64 host, clang reported the following
> error:
>
> ../util/cacheflush.c:38:44: error: value size does not match register size
> specified by the constraint and modifier [-Werror,-Wasm-operand-widths]
> asm
On Thu, 14 Jan 2021 10:58:11 +1100
David Gibson wrote:
> At least some s390 cpu models support "Protected Virtualization" (PV),
> a mechanism to protect guests from eavesdropping by a compromised
> hypervisor.
>
> This is similar in function to other mechanisms like AMD's SEV and
> POWER's PEF,
On Thu, Jan 14, 2021 at 11:36:23AM -0500, John Snow wrote:
> On 1/14/21 7:29 AM, Markus Armbruster wrote:
[...]
> So I see two possible options for "not inventing a language":
>
> 1. Raw QMP
> 2. The existing qmp-shell syntax, warts and all.
>
> I don't see a tremendous problem with doing
On Fri, 15 Jan 2021 at 09:05, Greg Kurz wrote:
>
> The following changes since commit 7c79721606be11b5bc556449e5bcbc331ef6867d:
>
> Merge remote-tracking branch 'remotes/rth-gitlab/tags/pull-tcg-20210113'
> into staging (2021-01-14 09:54:29 +)
>
> are available in the Git repository at:
>
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1906693
Title:
Assertion Failure in bdrv_co_write_req_prepare through megasas
Status in QEMU:
New
Bug description:
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1904652
Title:
Assertion failure in usb-ohci
Status in QEMU:
New
Bug description:
Hello,
Using hypervisor fuzzer,
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1901532
Title:
Assertion failure `mr != NULL' failed through usb-ehci
Status in QEMU:
Confirmed
Bug description:
Hello,
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1909247
Title:
QEMU: use after free vulnerability in esp_do_dma() in hw/scsi/esp.c
Status in QEMU:
New
Bug description:
A
Fix now in master as commit 6d3ef04893bde -- will be in next QEMU
release.
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907817
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1905444
Title:
[OSS-Fuzz] Issue 27796 in oss-fuzz: qemu:qemu-fuzz-i386-target-
generic-fuzz-xhci: Stack-overflow in
Fix now in master: commit e7e29fdbbe07f.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1904954
Title:
lan9118 bug peeked received
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907909
Title:
assertion failure in am53c974
Status in QEMU:
New
Bug description:
Hello,
Using hypervisor fuzzer,
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907497
Title:
[OSS-Fuzz] Issue 28435 qemu:qemu-fuzz-i386-target-generic-fuzz-intel-
hda: Stack-overflow in ldl_le_dma
Status
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907938
Title:
[OSS-Fuzz] Issue 28524 virtio-blk: ASSERT: !s->dataplane_started
Status in QEMU:
New
Bug description:
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908062
Title:
qemu-system-i386 virtio-vga: Assertion in address_space_stw_le_cached
failed again
Status in QEMU:
New
Bug
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908515
Title:
assertion failure in lsi53c810 emulator
Status in QEMU:
New
Bug description:
Hello,
Using hypervisor
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908513
Title:
assertion failure in mptsas1068 emulator
Status in QEMU:
New
Bug description:
Using hypervisor fuzzer,
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910603
Title:
[OSS-Fuzz] Issue 29174 sb16: Abrt in audio_bug
Status in QEMU:
New
Bug description:
=== Reproducer ===
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910826
Title:
[OSS-Fuzz] Issue 29224 rtl8139: Stack-overflow in
rtlNUMBER_transmit_one
Status in QEMU:
New
Bug
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1909261
Title:
[OSS-Fuzz] Issue 28929 xhci: ASSERT: xfer->packet.status !=
USB_RET_NAK
Status in QEMU:
New
Bug
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910941
Title:
Assertion `addr < cache->len && 2 <= cache->len - addr' in virtio-blk
Status in QEMU:
New
Bug description:
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1911075
Title:
[OSS-Fuzz] ahci: stack overflow in ahci_cond_start_engines
Status in QEMU:
Confirmed
Bug description:
===
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1911839
Title:
[OSS-Fuzz] Issue 29586 e1000e: Memcpy-param-overlap in
flatview_write_continue
Status in QEMU:
New
Bug
On 1/15/21 5:06 PM, Philippe Mathieu-Daudé wrote:
> On 1/15/21 4:53 PM, Stefan Berger wrote:
>> On 1/15/21 10:52 AM, Philippe Mathieu-Daudé wrote:
>>> Subject is incorrect, this is not a removal of the tests, but
>>> removal of their execution. The tests are still in the repository.
>>> This is
On Fri, 15 Jan 2021 09:07:47 +
"Zhang, Chen" wrote:
> > -Original Message-
> > From: Lukas Straub
> > Sent: Thursday, January 14, 2021 9:45 PM
> > To: Zhang, Chen
> > Cc: Jason Wang ; qemu-dev > de...@nongnu.org>; Eric Blake ; Dr. David Alan
> > Gilbert ; Markus Armbruster ;
> >
On 1/15/21 4:53 PM, Stefan Berger wrote:
> On 1/15/21 10:52 AM, Philippe Mathieu-Daudé wrote:
>> Subject is incorrect, this is not a removal of the tests, but
>> removal of their execution. The tests are still in the repository.
>> This is more of a disablement.
>
> How do you compile / run them
On Fri, 15 Jan 2021 at 15:52, Stefan Weil wrote:
> I forgot to mention that some of the problems with the Meson build also
> occur on macOS with Homebrew: they always happen when a software package
> requires special compiler flags to find its include files or libraries,
> but the Meson build
On 1/15/21 10:52 AM, Philippe Mathieu-Daudé wrote:
Subject is incorrect, this is not a removal of the tests, but
removal of their execution. The tests are still in the repository.
This is more of a disablement.
How do you compile / run them to have the LeakSanitizer checks?
Am 15.01.21 um 16:19 schrieb Peter Maydell:
On Fri, 15 Jan 2021 at 14:01, Peter Maydell wrote:
I was just trying to see what updates the qemu.nsi file needed for
the merge-all-the-manuals-into-one-place change, and I discovered
that it's been broken since October when we removed the Changelog
Subject is incorrect, this is not a removal of the tests, but
removal of their execution. The tests are still in the repository.
This is more of a disablement.
On 1/15/21 4:09 PM, Philippe Mathieu-Daudé wrote:
> The TPM tests are failing, and no further tests are run,
> making the rest of the
On Fri, 15 Jan 2021 at 15:45, Markus Armbruster wrote:
>
> The .realize() method realizes the child at (1). It should use
> qdev_realize() like we do everywhere else, since commit ce189ab230
> "qdev: Convert bus-less devices to qdev_realize() with Coccinelle".
>
> It sets a link property from
On Fri, 15 Jan 2021 at 15:34, Stefan Weil wrote:
> although I have some local fixes (available for example in
> https://github.com/stweil/qemu/) I am still struggling with 5.2.0.
>
> One problem which was recently discussed on the list is the directory
> structure of the installation (especially
Am 15.01.21 um 16:27 schrieb Jason Dillaman:
> On Thu, Jan 14, 2021 at 2:59 PM Peter Lieven wrote:
>> Am 14.01.21 um 20:19 schrieb Jason Dillaman:
>>> On Sun, Dec 27, 2020 at 11:42 AM Peter Lieven wrote:
since we implement byte interfaces and librbd supports aio on byte
granularity we
On 210115 1351, Christian Schoenebeck wrote:
> On Freitag, 15. Januar 2021 13:23:08 CET Greg Kurz wrote:
> > On Thu, 14 Jan 2021 17:17:48 -0500
> >
> > Alexander Bulekov wrote:
> > > Signed-off-by: Alexander Bulekov
> > > ---
> >
> > No changelog at all ?
>
> Yeah, that's indeed quite short.
101 - 200 of 415 matches
Mail list logo
