qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL v2 00/88] virtio: features,fixes


From: Thomas Huth
Subject: Re: [PULL v2 00/88] virtio: features,fixes
Date: Wed, 3 Jul 2024 20:46:38 +0200
User-agent: Mozilla Thunderbird

On 03/07/2024 19.01, Richard Henderson wrote:
On 7/3/24 09:51, Michael S. Tsirkin wrote:
On Wed, Jul 03, 2024 at 09:31:45AM -0700, Richard Henderson wrote:
On 7/2/24 13:15, Michael S. Tsirkin wrote:
The following changes since commit 1152a0414944f03231f3177207d379d58125890e:

    Merge tag 'pull-xen-20240701' ofhttps://xenbits.xen.org/git-http/people/aperard/qemu-dm  into staging (2024-07-01 09:06:25 -0700)

are available in the Git repository at:

    https://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git  tags/for_upstream

for you to fetch changes up to 29e45afd8d6abf7a67dab5db0ab1cfbc388daefe:

    hw/pci: Replace -1 with UINT32_MAX for romsize (2024-07-02 11:27:19 -0400)

----------------------------------------------------------------
virtio: features,fixes

A bunch of improvements:
- vhost dirty log is now only scanned once, not once per device
- virtio and vhost now support VIRTIO_F_NOTIFICATION_DATA
- cxl gained DCD emulation support
- pvpanic gained shutdown support
- beginning of patchset for Generic Port Affinity Structure
- s3 support
- friendlier error messages when boot fails on some illegal configs
- for vhost-user, VHOST_USER_SET_LOG_BASE is now only sent once
- vhost-user now works on any POSIX system
- sr-iov VF setup code has been reworked significantly
- new tests, particularly for risc-v ACPI
- bugfixes

Signed-off-by: Michael S. Tsirkin<mst@redhat.com>

Fails testing:

https://gitlab.com/qemu-project/qemu/-/jobs/7257337667

Could you give me a hint how to trigger this in CI pls?
All tests seem to pass when I push it to gitlab.
Any special variables to set?

In CI, FreeBSD uses travis; I'm not sure what's involved.

s/travis/cirrus-ci/

See .gitlab-ci.d/cirrus/README.rst for information how to enable it in your private gitlab repo.

I replicated it locally within a FreeBSD VM.

It should be reproducible with 'make vm-build-freebsd', but I think that's more difficult to debug after the fact than a full vm.

Just use "make vm-build-freebsd DEBUG=1" and you should get a shell prompt for interactive debugging, so that's likely the best way to tackle such issues.

 HTH,
  Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]