similar to: Re: [Qemu-devel] [PATCH, v2] qemu/xendisk: properly update stats in ioreq_release()

While for the "normal" case (called from blk_send_response_all()) decrementing requests_finished is correct, doing so in the parse error case is wrong; requests_inflight needs to be decremented instead. Change in v2: Adjust coding style. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/hw/xen_disk.c +++ b/hw/xen_disk.c @@ -154,7 +154,7 @@ static void ioreq_finish(struct

Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/xen/drivers/passthrough/vtd/ia64/vtd.c +++ b/xen/drivers/passthrough/vtd/ia64/vtd.c @@ -27,6 +27,7 @@ #include <asm/sal.h> #include "../iommu.h" #include "../dmar.h" +#include "../extern.h" #include "../vtd.h" --- a/xen/drivers/passthrough/vtd/quirks.c +++

At 09:49 +0100 on 08 May (1336470591), Tim Deegan wrote: > Ccing xen-devel. Actually this time. > At 11:29 -0700 on 07 May (1336390171), Christian Limpach wrote: > > > The current version of Xen allocates the shared page directly > > > in vm memory with other pages (like XenStore page) called > > > special pages. I just begin to hack Xen, so I used the same >

Keir, The patch moves ACPI timer to HV, which is the last platform timer in Qemu. We found Vista polls ACPI timer very frequently (about 15 times averagely) when handling timer (RTC @ 64HZ) interrupt routine. Though the exact reason is known, it should be related to system time adjustment. When it''s in Qemu, the overhead is big. After moving, Vista''s idle overhead decreases

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called as introduced with the patch "x86-64: detect processors subject to AMD erratum #121 and

Hi! In struct ioreq are the "addr", "size", "count" and "data" 64bit fields. So handle 64bit operations in stdvga instead of throwing away the upper 32bits (see attached patch). This fixes some noisy xen messages like "invalid io size: 8". Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany

These functions don''t seem to be used outside of i386-dm/helper2.c Signed-off-by: Simon Horman <horms@verge.net.au> --- i386-dm/helper2.c | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) Index: ioemu-remote/i386-dm/helper2.c =================================================================== --- ioemu-remote.orig/i386-dm/helper2.c 2009-03-02

This patch implements a new mechanism to buffer the MMIO_WRITE and PIO_WRITE packet in a queue, and then submit them to qemu-dm in batch. This could save a lot of domain switch time. We implement this as a generic one to do ioreq in batch. However, we only use it to batch the MMIO_WIRTE request for stdvga(0xA0000-0xC0000) in order to solve the win2k boot issue for hvm domain. Without this patch,

Hey, I just started noticing it today - with qemu-xen (tip is commit b97307ecaad98360f41ea36cd9674ef810c4f8cf xen_disk: mark ioreq as mapped before unmapping in error case) when I try to pass in a PCI device at bootup it blows up with: char device redirected to /dev/pts/2 (label serial0) qemu: hardware error: xen: failed to populate ram at 40050000 CPU #0: EAX=00000000 EBX=00000000

The following two fixes by Jürgen Keil have been in qemu for a year now. They are still missing in ioemu. [Qemu-devel] PATCH: qcow2 image corruption http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00773.html [Qemu-devel] [PATCH] qcow2: release refcount table clusters of the old table, after growing the refcount table http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00043.html

xs_printf writes the terminating null byte of the passed string to Xenstore. When reading, the null byte is returned in the following form which confuses tools: sector-size = "512\000" This patch removes the null byte from the data to write. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list

With my qcow2 patch to blktap I contributed a bit to the mess, so here an attempt to clean up and remove at least some of the code duplication in the functions dealing with aio operations. This patch is mostly just moving code. Apart from renaming to get common names and such things, only very few changes are needed as big parts of the code were completely identical and obviously created by

Any call to inflate() must be followed by inflateEnd(), otherwise the internal zlib state is leaked. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

When a domain wants to use a tap:ioemu disk but has no device model, start a tapdisk-ioemu instance as provider. Also, move the creation and removal of communication pipes to xend so that qemu-dm doesn''t need the unwanted SIGHUP handler anymore. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list

qemu-xen: Fix open_disk for blktap disks If blktap drives are registered properly, qemu code is much less likely to get confused by them. Use bdrv_new(), assign a device name and create an entry in drives_table for them. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

пн, 10 лют. 2020 о 15:48 Kevin Wolf <kwolf@redhat.com> пише: > > Am 10.02.2020 um 12:43 hat Richard W.M. Jones geschrieben: > > On Sat, Feb 08, 2020 at 01:25:28AM +0200, Mykola Ivanets wrote: > > > From: Nikolay Ivanets <stenavin@gmail.com> > > > > > > I faced with situation where libguestfs cannot recognize partitions on a > > > disk

On Tue, Apr 10, 2018 at 4:48 PM Kevin Wolf <kwolf@redhat.com> wrote: > Am 10.04.2018 um 15:03 hat Nir Soffer geschrieben: > > On Tue, Apr 10, 2018 at 1:44 PM Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > We now have true zeroing support in oVirt imageio, thanks for that. > > > > > > However a problem is that ‘qemu-img

Hi On Tue, Mar 17, 2020 at 12:55 PM Markus Armbruster <armbru@redhat.com> wrote: > > This series extends QMP introspection to cover deprecation. > Additionally, new option -compat lets you configure what to do when > deprecated interfaces get used. This is intended for testing users of > the management interfaces. It is experimental. > > -compat

branch xen-unstable xen branch xen-unstable job test-amd64-i386-rhel6hvm-amd test redhat-install Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg *** Found and reproduced problem

The previous order of relinquish resource is: relinquish_domain_resources() -> vcpu_destroy() -> nvmx_vcpu_destroy(). However some L1 resources like nv_vvmcx and io_bitmaps are free in nvmx_vcpu_destroy(), therefore the relinquish_domain_resources() will not reduce the refcnt of the domain to 0, therefore the latter vcpu release functions will not be called. To fix this issue, we need to