[Qemu-devel] [PATCH v8 07/16] spapr_rtas: add ibm, configure-connector RTAS interface

This interface is used to fetch an OF device-tree nodes that describes a newly-attached device to guest. It is called multiple times to walk the device-tree node and fetch individual properties into a 'workarea'/buffer provided by the guest. The device-tree is generated by QEMU and passed to an sP

[Qemu-devel] [PATCH v8 06/16] spapr: add rtas_st_buffer_direct() helper

This is similar to the existing rtas_st_buffer(), but for cases where the guest is not expecting a length-encoded byte array. Namely, for calls where a "work area" buffer is used to pass around arbitrary fields/data. Signed-off-by: Michael Roth Reviewed-by: David Gibson --- include/hw/ppc/spapr

[Qemu-devel] [PATCH v8 05/16] spapr_rtas: add get-sensor-state RTAS interface

From: Mike Day This interface allows a guest to read various platform/device sensors. initially, we only implement support necessary to support hotplug: reading of the dr-entity-sense sensor, which communicates the state of a hotplugged resource/device to the guest (EMPTY/PRESENT/UNUSABLE). See

[Qemu-devel] [PATCH v8 04/16] spapr_rtas: add set-indicator RTAS interface

From: Mike Day This interface allows a guest to control various platform/device sensors. Initially, we only implement support necessary to control sensors that are required for hotplug: DR connector indicators/LEDs, resource allocation state, and resource isolation state. See docs/specs/ppc-spap

[Qemu-devel] [PATCH v8 02/16] spapr_drc: initial implementation of sPAPRDRConnector device

This device emulates a firmware abstraction used by pSeries guests to manage hotplug/dynamic-reconfiguration of host-bridges, PCI devices, memory, and CPUs. It is conceptually similar to an SHPC device, complete with LED indicators to identify individual slots to physical physical users and indicat

[Qemu-devel] [PATCH v8 01/16] docs: add sPAPR hotplug/dynamic-reconfiguration documentation

This adds a general overview of hotplug/dynamic-reconfiguration for sPAPR/pSeries guest. As specified in PAPR+ v2.7. Signed-off-by: Michael Roth Reviewed-by: David Gibson --- docs/specs/ppc-spapr-hotplug.txt | 287 +++ 1 file changed, 287 insertions(+) crea

[Qemu-devel] [PATCH v8 08/16] spapr_events: re-use EPOW event infrastructure for hotplug events

From: Nathan Fontenot This extends the data structures currently used to report EPOW events to guests via the check-exception RTAS interfaces to also include event types for hotplug/unplug events. This is currently undocumented and being finalized for inclusion in PAPR specification, but we impl

[Qemu-devel] [PATCH v8 15/16] spapr_pci: enable basic hotplug operations

This enables hotplug of PCI devices to a PHB. Upon hotplug we generate the OF-nodes required by PAPR specification and IEEE 1275-1994 "PCI Bus Binding to Open Firmware" for the device. We associate the corresponding FDT for these nodes with the DRC corresponding to the slot, which will be fetched

[Qemu-devel] [PATCH v8 14/16] pci: make pci_bar useable outside pci.c

We need to work with PCI BARs to generate OF properties during PCI hotplug for sPAPR guests. Signed-off-by: Michael Roth Reviewed-by: David Gibson Cc: m...@redhat.com --- hw/pci/pci.c | 2 +- include/hw/pci/pci.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/hw/pc

[Qemu-devel] [PATCH v8 16/16] spapr_pci: emit hotplug add/remove events during hotplug

From: Tyrel Datwyler This uses extension of existing EPOW interrupt/event mechanism to notify userspace tools like librtas/drmgr to handle in-guest configuration/cleanup operations in response to device_add/device_del. Userspace tools that don't implement this extension will need to be run manua

[Qemu-devel] [PATCH v8 12/16] spapr_pci: add dynamic-reconfiguration option for spapr-pci-host-bridge

This option enables/disables PCI hotplug for a particular PHB. Also add machine compatibility code to disable it by default for machine types prior to pseries-2.4. Signed-off-by: Michael Roth Reviewed-by: David Gibson --- hw/ppc/spapr.c | 15 ++- hw/ppc/spapr_pci.c

[Qemu-devel] [PATCH v8 11/16] spapr: add pseries-2.4 machine type

Initially this is identifical to pseries-2.3. Subsequent patches will use it to mask new 2.4 features by default. Signed-off-by: Michael Roth --- hw/ppc/spapr.c | 19 ++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c index c1e7281..

[Qemu-devel] [PATCH v8 13/16] spapr_pci: create DRConnectors for each PCI slot during PHB realize

These will be used to support hotplug/unplug of PCI devices to the PCI bus associated with a particular PHB. We also set up device-tree properties in each PHBs initial FDT to describe the DRCs associated with them. This advertises to guests that each PHB is DR-capable device with physical hotplugg

[Qemu-devel] [PATCH v8 03/16] spapr_rtas: add get/set-power-level RTAS interfaces

From: Nathan Fontenot These interfaces manage the power domains that guest devices are assigned to and are used to power on/off devices. Currently we only utilize 1 power domain, the 'live-insertion' domain, which automates power management of plugged/unplugged devices, essentially making these c

[Qemu-devel] [PATCH v8 10/16] spapr_drc: add spapr_drc_populate_dt()

This function handles generation of ibm,drc-* array device tree properties to describe DRC topology to guests. This will by used by the guest to direct RTAS calls to manage any dynamic resources we associate with a particular DR Connector as part of hotplug/unplug. Since general management of boot

[Qemu-devel] [PATCH v8 00/16] spapr: add support for pci hotplug

These patches are based on spapr-next, and can also be obtained from: https://github.com/mdroth/qemu/commits/spapr-hotplug-pci-v8 v8: * rebased on https://github.com/dgibson/qemu/commits/spapr-next * added sPAPR 2.4 machine-type, updated compat code from 2.3 -> 2.4 * added small helper to lookup

[Qemu-devel] [PATCH v8 09/16] spapr_events: event-scan RTAS interface

From: Tyrel Datwyler We don't actually rely on this interface to surface hotplug events, and instead rely on the similar-but-interrupt-driven check-exception RTAS interface used for EPOW events. However, the existence of this interface is needed to ensure guest kernels initialize the event-report

Re: [Qemu-devel] [PATCH] hda-codec: use smaller dynamic range for input amplifier

Hi, > > The "right" solution for this problem would be to implement > > proper dB scaling in QEMU and the audio backends (such as spice). Can we try this please? > > While this clean solution is not available, I suggest to decrease > > the dynamic range for the the emulated Amps in the QEMU hd

Re: [Qemu-devel] [PATCH] acpi: add a missing backslash to the \_SB scope.

On Tue, 21 Apr 2015 14:53:54 +0200 "Michael S. Tsirkin" wrote: > On Tue, Apr 21, 2015 at 12:33:36PM +0100, Peter Maydell wrote: > > On 21 April 2015 at 11:09, Michael S. Tsirkin wrote: > > > On Tue, Apr 21, 2015 at 11:26:12AM +0300, Gal Hammer wrote: > > >> A predefined scope in the ACPI specs i

Re: [Qemu-devel] [PATCH 5/6] [wip] tseg, part1, not (yet) tested

Hi, > A "unified" patchset (not necessarily posted, just pushed somewhere) > would be helpful down the road -- IIRC this one was claimed unapplicable > to current master. (Which is also why I didn't try the "info mtree" > command, see elsewhere in the thread -- I didn't try to build the series.)

Re: [Qemu-devel] [libvirt] [RFC 0/7] Live Migration with Pass-through Devices proposal

Hi Laine, Thanks for your review for my patches. and do you know that solarflare's patches have made some update version since https://www.redhat.com/archives/libvir-list/2012-November/msg01324.html ? if not, I hope to go on to complete this work. ;) Thanks, Chen On 04/20/2015 06:29 AM, La

[Qemu-devel] [PATCH] target-arm: Adjust id_aa64pfr0 when has_el3 CPU property disabled

Signed-off-by: Sergey Fedorov --- target-arm/cpu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/target-arm/cpu.c b/target-arm/cpu.c index 986f04c..327b1e5 100644 --- a/target-arm/cpu.c +++ b/target-arm/cpu.c @@ -524,9 +524,10 @@ static void arm_cpu_realizefn(DeviceState *

[Qemu-devel] [PATCH 4/5] scripts: qmp-shell: add transaction subshell

Add a special processing mode to craft transactions. By entering "transaction(" the shell will enter a special mode where each subsequent command will be saved as a transaction instead of executed as an individual command. The transaction can be submitted by entering ")" on a line by itself. Exa

[Qemu-devel] [PATCH 5/5] scripts: qmp-shell: Add verbose flag

Add a verbose flag that shows the QMP command that was constructed, to allow for later copy/pasting, reference, debugging, etc. Signed-off-by: John Snow --- scripts/qmp/qmp-shell | 21 - 1 file changed, 16 insertions(+), 5 deletions(-) diff --git a/scripts/qmp/qmp-shell b/sc

[Qemu-devel] [PATCH 2/5] scripts: qmp-shell: add support for [] expressions

qmp-shell currently allows you to describe values as JSON expressions: key={"key":{"key2":"val"}} But it does not currently support arrays, which are needed for serializing and deserializing transactions: key=[{"type":"drive-backup","data":{...}}] Add support for arrays. CAVEAT: The parser is

[Qemu-devel] [PATCH 1/5] scripts: qmp-shell: refactor helpers

Refactor the qmp-shell command line processing function into two components. This will be used to allow sub-expressions, which will assist us in adding transactional support to qmp-shell. Signed-off-by: John Snow --- scripts/qmp/qmp-shell | 24 +--- 1 file changed, 13 inserti

[Qemu-devel] [PATCH 3/5] scripts: qmp-shell: allow single-quotes in JSON expressions

As a convenience for the user, replace any single quotes given with double quotes so that the data will deserialize correctly via json.loads(). Signed-off-by: John Snow --- scripts/qmp/qmp-shell | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/qmp/qmp-shell b/scripts/q

[Qemu-devel] [PATCH 0/5] scripts: qmp-shell: add transaction support

The qmp-shell is a little rudimentary, but it can be hacked to give us some transactional support without too much difficulty. (1) Prep. (2) Add support for serializing json arrays (3) Allow users to use 'single quotes' instead of "double quotes" (4) Add a special transaction( ... ) syntax that le

Re: [Qemu-devel] [RFC 3/3] qemu-agent: add notify for qemu-ga boot

On 04/17/2015 02:53 AM, Chen Fan wrote: > Signed-off-by: Chen Fan > --- > qga/main.c | 13 + > 1 file changed, 13 insertions(+) I'm not sure that qga should be sending asynchronous messages (so far, it only every replies synchronously). As it is, we already wired up a qemu event tha

[Qemu-devel] [PATCH 1/2] x86: Add 2.4 pc machine versions

This patch adds all the boilerplate required to handle a 2.4 machine type and compatibility options required on older machines. Signed-off-by: Alexander Graf --- hw/i386/pc_piix.c| 37 + hw/i386/pc_q35.c | 34 +++--- include

[Qemu-devel] [PATCH 2/2] x86: Fix Opteron xlevels

The AMD Opteron family has different xlevel levels depending on the generation. I looked up Gen1, Gen2 and Gen3 hardware and adapted the levels according to real silicon. The reason this came up is that there is a sanity check in KVM making sure that SVM is only used when xlevel is high enough. Us

Re: [Qemu-devel] [[PATCH] 2/7] target-arm: Extend helpers to route exceptions

On Thu, Apr 16, 2015 at 12:51 PM, Peter Maydell wrote: > On 27 March 2015 at 19:10, Greg Bellows wrote: > > Updated the various helper routines to set the target EL as needed. > > > > Signed-off-by: Greg Bellows > > --- > > target-arm/op_helper.c | 5 + > > 1 file changed, 5 insertions(+)

[Qemu-devel] [ANNOUNCE] QEMU 2.3.0-rc4 is now available

Hello, On behalf of the QEMU Team, I'd like to announce the availability of the fifth release candidate for the QEMU 2.3 release. This release is meant for testing purposes and should not be used in a production environment. http://wiki.qemu.org/download/qemu-2.3.0-rc4.tar.bz2 This is a minor

Re: [Qemu-devel] [PATCH 12/12 v9] target-tilegx: Generate tcg instructions to execute to 1st system call

On 21 April 2015 at 22:23, Chen Gang wrote: > On 4/22/15 05:15, Peter Maydell wrote: >> will work in place of both of the above (and does this CPU >> really only have two kinds of compare-immediate? Some of the >> case labels suggest not, so it would be better to just implement >> all the compare-

Re: [Qemu-devel] [PATCH 12/12 v9] target-tilegx: Generate tcg instructions to execute to 1st system call

On 4/22/15 05:15, Peter Maydell wrote: > On 21 April 2015 at 22:01, Chen Gang wrote: >> On 4/11/15 05:28, Chen Gang wrote: >>> On 4/10/15 06:19, Peter Maydell wrote: On 27 March 2015 at 11:07, Chen Gang wrote: > +} > + > +static void gen_cmpltui(struct DisasContext *dc, > +

Re: [Qemu-devel] [PATCH 12/12 v9] target-tilegx: Generate tcg instructions to execute to 1st system call

On 21 April 2015 at 22:01, Chen Gang wrote: > On 4/11/15 05:28, Chen Gang wrote: >> On 4/10/15 06:19, Peter Maydell wrote: >>> On 27 March 2015 at 11:07, Chen Gang wrote: +} + +static void gen_cmpltui(struct DisasContext *dc, +uint8_t rdst, uint8_t rsrc

Re: [Qemu-devel] [PATCH 12/12 v9] target-tilegx: Generate tcg instructions to execute to 1st system call

On 4/11/15 05:28, Chen Gang wrote: > On 4/10/15 06:19, Peter Maydell wrote: >> On 27 March 2015 at 11:07, Chen Gang wrote: >>> +} >>> + >>> +static void gen_cmpltui(struct DisasContext *dc, >>> +uint8_t rdst, uint8_t rsrc, int8_t imm8) >>> +{ >>> +qemu_log_mask(CPU_LOG_

Re: [Qemu-devel] implementing EFI_SMM_CONTROL2_PROTOCOL.Trigger()

On 21/04/2015 22:31, Laszlo Ersek wrote: > typedef enum { > EfiLockUninitialized = 0, > EfiLockReleased = 1, > EfiLockAcquired = 2 > } EFI_LOCK_STATE; > > typedef struct { > EFI_TPL Tpl; > EFI_TPL OwnerTpl; > EFI_LOCK_STATE Lock; > } EFI_LOCK; > > VOID > E

Re: [Qemu-devel] [PATCH qemu v6 03/15] spapr_pci: Make find_phb()/find_dev() public

Quoting Alexey Kardashevskiy (2015-04-10 10:24:32) > This makes find_phb()/find_dev() public and changed its names > to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to > be used from other parts of QEMU such as VFIO DDW (dynamic DMA window) > or VFIO PCI error injection or VFIO EEH h

Re: [Qemu-devel] [PATCH v2.5 00/10] block: incremental backup transactions

On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote: [. . .] > And, invoking `drive-backup` *without* pre-creating the target image > (i.e. 'incremental.o.img'): > > { 'execute': 'drive-backup', > 'arguments': { > 'device': 'ide0-0-0', > 'bitmap': 'bitmap0

[Qemu-devel] implementing EFI_SMM_CONTROL2_PROTOCOL.Trigger() (was: [PATCH 6/6] [wip] tseg, part2, not (yet) tested)

adding edk2-devel On 04/21/15 17:21, Paolo Bonzini wrote: > > > On 21/04/2015 17:05, Laszlo Ersek wrote: >> >> Yet another question -- as far as I understand, I should have enough >> info (with my pending questions of course) for EFI_SMM_ACCESS2_PROTOCOL. >> I've now reviewed EFI_SMM_CONTROL2_PR

Re: [Qemu-devel] [PATCH] vhost-user: Add ability to know vhost-user backend disconnection

On Tue, Apr 21, 2015 at 9:36 AM, Tetsuya Mukawa wrote: > Current QEMU cannot detect vhost-user backend disconnection. The > patch adds ability to know it. > To know disconnection, add watcher to detect G_IO_HUP event. When > G_IO_HUP event is detected, the disconnected socket will be read > to cau

Re: [Qemu-devel] [PATCH 09/10] s390x/mmu: Use ioctl for reading and writing from/to guest memory

Am 21.04.2015 um 21:36 schrieb Alexander Graf: > On 04/21/2015 09:34 PM, Christian Borntraeger wrote: >> Am 21.04.2015 um 21:12 schrieb Alexander Graf: >>> On 04/20/2015 04:55 PM, Christian Borntraeger wrote: Am 09.04.2015 um 10:51 schrieb Cornelia Huck: > From: Thomas Huth > > Ad

Re: [Qemu-devel] [PATCH 09/10] s390x/mmu: Use ioctl for reading and writing from/to guest memory

On 04/21/2015 09:34 PM, Christian Borntraeger wrote: Am 21.04.2015 um 21:12 schrieb Alexander Graf: On 04/20/2015 04:55 PM, Christian Borntraeger wrote: Am 09.04.2015 um 10:51 schrieb Cornelia Huck: From: Thomas Huth Add code to make use of the new ioctl for reading from / writing to virtual

Re: [Qemu-devel] [PATCH 09/10] s390x/mmu: Use ioctl for reading and writing from/to guest memory

Am 21.04.2015 um 21:12 schrieb Alexander Graf: > On 04/20/2015 04:55 PM, Christian Borntraeger wrote: >> Am 09.04.2015 um 10:51 schrieb Cornelia Huck: >>> From: Thomas Huth >>> >>> Add code to make use of the new ioctl for reading from / writing to >>> virtual guest memory. By using the ioctl, the

Re: [Qemu-devel] [PATCH 2/2] pci: GPEX: Add support to route legacy interrupts

On 04/17/2015 10:55 AM, Pranavkumar Sawargaonkar wrote: This patch adds routine to route legacy interrupts to VM. Signed-off-by: Pranavkumar Sawargaonkar Signed-off-by: Tushar Jagad I don't think the device model should have awareness of any global irq number spaces. Can you move this into

Re: [Qemu-devel] [PATCH 09/10] s390x/mmu: Use ioctl for reading and writing from/to guest memory

On 04/20/2015 04:55 PM, Christian Borntraeger wrote: Am 09.04.2015 um 10:51 schrieb Cornelia Huck: From: Thomas Huth Add code to make use of the new ioctl for reading from / writing to virtual guest memory. By using the ioctl, the memory accesses are now protected with the so-called ipte-lock

Re: [Qemu-devel] [PATCH 3/6] s390/kvm: diag288 instruction interception and handling

On 04/17/2015 09:52 AM, Cornelia Huck wrote: From: Xu Wang Intercept the diag288 requests from kvm guests, and hand the requested command to the diag288 watchdog device for further handling. Signed-off-by: Xu Wang Reviewed-by: David Hildenbrand Signed-off-by: Cornelia Huck We're getting a

Re: [Qemu-devel] [PATCH 1/6] s390x/virtio-ccw: enable has_dynamic_sysbus

On 04/17/2015 09:52 AM, Cornelia Huck wrote: From: Xu Wang We have to enable this flag to support dynamically adding devices to the sysbus. This change is needed for the the upcoming diag288 watchdog. s390 doesn't have a "sysbus" per se. Please create a new bus type. Alex Signed-off-by:

Re: [Qemu-devel] [PATCH 5/6] [wip] tseg, part1, not (yet) tested

On 04/21/15 17:04, Gerd Hoffmann wrote: >>> +static const MemoryRegionOps tseg_blackhole_ops = { >>> +.read = tseg_blackhole_read, >>> +.write = tseg_blackhole_write, >>> +.endianness = DEVICE_NATIVE_ENDIAN, >>> +.valid.min_access_size = 1, >>> +.valid.max_access_size = 4, >>> +

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

> On 21 Apr 2015, at 16:34, Leon Alrae wrote: > > I'll resend the patch with dropped "RFC" as I would really like to go > forward and finally close this issue. perhaps you should first take a closer look at the patch I submitted, since it covers not only parsing the arguments, but also groupin

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 21 April 2015 at 17:51, Liviu Ionescu wrote: > could you also suggest a solution for a .BAT script when running on windows? I don't do windows, so you're on your own there, I'm afraid, though a little googling suggests windows bat syntax does have sufficient power (eg string-replacement functi

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

> On 21 Apr 2015, at 19:54, Peter Maydell wrote: > > Incidentally if you have a better idea for achieving the > desired goal than this messing around with comma-escaping > I would really like to know. I don't like either of the > current two proposals very much :-( please keep in mind that the

[Qemu-devel] [Bug 1440843] Re: Guest WinXP crashes when trying to use a USB spectrometer

Please check that the devices get added to the EHCI bus and not to the UHCI. As far as I know the -usb* commands are deprecated. The functions behind the -device usb* and -usb* should behave the same. -- You received this bug notification because you are a member of qemu- devel-ml, which is subs

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 04/21/2015 10:54 AM, Peter Maydell wrote: > On 21 April 2015 at 17:48, Eric Blake wrote: >> On 04/21/2015 09:55 AM, Peter Maydell wrote: >>> If you want pure POSIX shell then it is slightly >>> uglier as we have to invoke sed: >>> >>> argstr="" >>> for arg in "$@"; do >>> o=$(printf '%s.\n

Re: [Qemu-devel] [PATCH] hda-codec: use smaller dynamic range for input amplifier

Hi - Original Message - > This patch addresses the following problem: > > Moving the input volume slider 0% to 1% in a Win7 guest causes the > the "gain" values in the emulated HDA codec HW to jump from 0 to 40. > This makes it impossible to control sound volume in the low-gain > range us

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 21 April 2015 at 17:48, Eric Blake wrote: > On 04/21/2015 09:55 AM, Peter Maydell wrote: >> If you want pure POSIX shell then it is slightly >> uglier as we have to invoke sed: >> >> argstr="" >> for arg in "$@"; do >> o=$(printf '%s.\n' "$arg" | sed s/,/,,/g) >> argstr=${argstr:+$arg

Re: [Qemu-devel] about [SeaBIOS PATCH] Try to hard-reboot on rerun of post even on emulators.

On 04/21/15 17:06, Kevin O'Connor wrote: > On Tue, Apr 21, 2015 at 10:37:49AM +0200, Laszlo Ersek wrote: >> As to how you can fix >> (which is the >> motivation for this entire discussion): >> >> - You need to identify *what variable exactly* st

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

> On 21 Apr 2015, at 19:23, Peter Maydell wrote: > >> do these scripts properly handle args containing spaces or embedded >> apostrophes/quotes? > > Yes. Also arguments containing newlines. super! could you also suggest a solution for a .BAT script when running on windows? in my opinion bot

[Qemu-devel] [PATCH] hda-codec: use smaller dynamic range for input amplifier

This patch addresses the following problem: Moving the input volume slider 0% to 1% in a Win7 guest causes the the "gain" values in the emulated HDA codec HW to jump from 0 to 40. This makes it impossible to control sound volume in the low-gain range using the windows guest. This is related to how

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 04/21/2015 09:55 AM, Peter Maydell wrote: > If you want pure POSIX shell then it is slightly > uglier as we have to invoke sed: > > argstr="" > for arg in "$@"; do > o=$(printf '%s.\n' "$arg" | sed s/,/,,/g) > argstr=${argstr:+$argstr,}arg=${o%.} > done It's possible to use IFS= and

[Qemu-devel] APIC handling causing kernel panic with kernel-3.12.38 and qemu-1.2

Hello Fellows, We are experiencing some kernel panics, probably caused by APIC handling, in our host servers when using kernel-3.12.38 and qemu-1.2. The issues (most of them similar) happen when executing VMs with CentOS-6, Ubuntu-14.* and Windows 2012 Server as guest's OS and different workloads.

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 21 April 2015 at 17:21, Liviu Ionescu wrote: > >> On 21 Apr 2015, at 18:55, Peter Maydell wrote: >> >> On 21 April 2015 at 16:14, Liviu Ionescu wrote: >>> if you insist on the arg= solution, could you be so kind and >>> provide a bash script wrapper that passes all arguments ($@) >>> using yo

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

> On 21 Apr 2015, at 18:55, Peter Maydell wrote: > > On 21 April 2015 at 16:14, Liviu Ionescu wrote: >> if you insist on the arg= solution, could you be so kind and >> provide a bash script wrapper that passes all arguments ($@) >> using your syntax? > > > ... bashisms ... pure POSIX shell d

Re: [Qemu-devel] While testing `drive-backup` with 'dirty-bitmap' syc mode via QMP. . .

On Tue, Apr 21, 2015 at 11:34:07AM -0400, John Snow wrote: > Kashyap Chamarthy sent me a question asking for some clarifications on > testing my incremental backup series. I responded off-list but he has asked > me to reproduce my answer for the archives :) Thanks for the detailed response on both

Re: [Qemu-devel] [PATCH RFC 0/3] iothread: release iothread around aio_poll

On 21/04/2015 17:40, Stefan Hajnoczi wrote: >> > >> > Stefan, can you put this on track for 2.4 or do you need a repost? > This series causes qemu-iotests -qcow2 091 to fail: > > 9f83aea22314d928bb272153ff37d2d7f5adbf06 is the first bad commit > commit 9f83aea22314d928bb272153ff37d2d7f5adbf06 >

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

On 21 April 2015 at 16:14, Liviu Ionescu wrote: > if you insist on the arg= solution, could you be so kind and > provide a bash script wrapper that passes all arguments ($@) > using your syntax? If you're willing to accept bashisms, then: argstr="" for arg in "$@"; do argstr=${argstr:+$args

[Qemu-devel] [PATCH] vhost-user: Add ability to know vhost-user backend disconnection

Current QEMU cannot detect vhost-user backend disconnection. The patch adds ability to know it. To know disconnection, add watcher to detect G_IO_HUP event. When G_IO_HUP event is detected, the disconnected socket will be read to cause a CHR_EVENT_CLOSED. Signed-off-by: Tetsuya Mukawa --- net/vh

[Qemu-devel] using scsi megasas causes Windows 8 bluescreen

I'm trying to install Windows 8 on megasas scsi device with master qemu branch. At the end of the installation I consistently get a blue screen and the image doesn't boot after that. I tried to bisect to older qemu versions, the oldest one that made Windows to recognize the disk was origin/stable-2

[Qemu-devel] [Bug 1446726] [NEW] qemu stable 2.0 crashes during loadvm

Public bug reported: Qemu output: 2015-03-06 01:06:54.255+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name instance-462a -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Westmere,+erms,+sm

Re: [Qemu-devel] [PATCH RFC 0/3] iothread: release iothread around aio_poll

On Tue, Mar 31, 2015 at 11:35 AM, Paolo Bonzini wrote: > On 20/02/2015 17:26, Paolo Bonzini wrote: >> Right now, iothreads are relying on a "contention callback" to release >> the AioContext (e.g. for block device operations or to do bdrv_drain_all). >> This is necessary because aio_poll needs to

Re: [Qemu-devel] [PATCH] target-arm: rename c1_coproc to cpacr_el1

On 21.04.2015 06:49, Peter Maydell wrote: > On 17 March 2015 at 16:23, Peter Maydell wrote: >> On 17 March 2015 at 15:33, Sergey Fedorov wrote: >>> Rename the field holding CPACR_EL1 system register state in AArch64 >>> naming style. >>> >>> Signed-off-by: Sergey Fedorov >> Reviewed-by: Peter Ma

Re: [Qemu-devel] [RFC v3] monitor: add memory search commands s, sp

On Tue, 21 Apr 2015 16:25:12 +0200 Claudio Fontana wrote: > Hello Luiz, > > On 21.04.2015 00:01, Luiz Capitulino wrote: > > On Fri, 27 Mar 2015 17:19:30 +0100 > > Claudio Fontana wrote: > > > >> Just a respectful ping on this one.. > >> Luiz do you think you can integrate this into the monitor

Re: [Qemu-devel] While testing `drive-backup` with 'dirty-bitmap' syc mode via QMP. . .

Kashyap Chamarthy sent me a question asking for some clarifications on testing my incremental backup series. I responded off-list but he has asked me to reproduce my answer for the archives :) On 04/21/2015 08:35 AM, Kashyap Chamarthy wrote: Hi John, I would have asked this question on #qemu

Re: [Qemu-devel] [Qemu-block] [PATCH COLO v3 01/14] docs: block replication's description

On 21/04/2015 03:25, Wen Congyang wrote: >> > Please do not introduce "+colo" block drivers. This approach is >> > invasive and makes block replication specific to only a few block >> > drivers, e.g. NBD or qcow2. > NBD is used to connect to secondary qemu, so it must be used. But the primary >

[Qemu-devel] [PATCH] qcow2: do lazy allocation of the L2 cache

Large disk images need large L2 caches in order to maximize their I/O performance. However setting a correct size for the cache is not necessarily easy since apart from the image size, it also depends on other factors like its usage patterns or whether it's part of a backing chain. In order to be

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

On 21/04/2015 17:05, Laszlo Ersek wrote: > > Yet another question -- as far as I understand, I should have enough > info (with my pending questions of course) for EFI_SMM_ACCESS2_PROTOCOL. > I've now reviewed EFI_SMM_CONTROL2_PROTOCOL too, and AFAICS the only > thing I need to know for it is "ho

Re: [Qemu-devel] [PATCH 5/6] [wip] tseg, part1, not (yet) tested

On Di, 2015-04-21 at 17:08 +0200, Paolo Bonzini wrote: > > On 21/04/2015 17:04, Gerd Hoffmann wrote: > > Hmm. I think if we merge all the smm / smram / tseg patches in one go > > this should work. Without patches reading the ESMRAMC register returns > > zero. With the patches the three cache-di

Re: [Qemu-devel] [RFC PATCH] vl.c: add -semihosting-config "arg" sub-argument

> On 21 Apr 2015, at 16:34, Leon Alrae wrote: > > (PS: --semihosting-cmdline $@ is probably the most convenient from GUI / > wrapper point of view, but I don't have an opinion whether this is > enough to justify adding a top level QEMU command line option with such > a unique syntax) nope, the

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

> > tseg_blackhole is added on top of address_space_memory to hide TSEG; > > tseg_window is included in /machine/smram and TCG adds it to the private > > per-CPU address space when it enters system management mode. > > Hm, I must have missed this (or not seen it at all) -- should I have > noticed

[Qemu-devel] [PATCH v2] hw/ppc/spapr_iommu: Fix the check for invalid upper bits in liobn

The check "liobn & 0xULL" in spapr_tce_find_by_liobn() is completely useless since liobn is only declared as an uint32_t parameter. Fix this by using target_ulong instead (this is what most of the callers of this function are using, too). Signed-off-by: Thomas Huth --- v2: - Do no

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

Hi, > > I'm thinking, the last 1 / 2 / 8 megabytes should behave as RAM in all > > of the following cases: > > - no SMRAM programmed (tseg size = 0) > > - SMRAM programmed (tseg size > 0), and it is open > > - SMRAM programmed (tseg size > 0) and closed, but CPU in SMM > > Correct. Almost. I

Re: [Qemu-devel] [PATCH 5/6] [wip] tseg, part1, not (yet) tested

> > +static const MemoryRegionOps tseg_blackhole_ops = { > > +.read = tseg_blackhole_read, > > +.write = tseg_blackhole_write, > > +.endianness = DEVICE_NATIVE_ENDIAN, > > +.valid.min_access_size = 1, > > +.valid.max_access_size = 4, > > +.impl.min_access_size = 4, > > +

Re: [Qemu-devel] [RFC v3] monitor: add memory search commands s, sp

On 21.04.2015 16:28, Paolo Bonzini wrote: > > > On 21/04/2015 16:25, Claudio Fontana wrote: >> I seem not to get this warning with the compiler version I am currently >> using, >> and after checking the code I could not find out why with some compilers >> would emit such a warning. >> >> It is

Re: [Qemu-devel] [PATCH 5/6] [wip] tseg, part1, not (yet) tested

On 21/04/2015 17:04, Gerd Hoffmann wrote: > Hmm. I think if we merge all the smm / smram / tseg patches in one go > this should work. Without patches reading the ESMRAMC register returns > zero. With the patches the three cache-disable bits are hardcoded to > '1'. This should work for detecti

[Qemu-devel] [PATCH v2 1/2] target-mips: move group of functions above gen_load_fpr32()

Move the "Tests" group of functions so that gen_load_fpr32() and gen_store_fpr32() can use generate_exception(). Signed-off-by: Leon Alrae --- target-mips/translate.c | 118 1 file changed, 58 insertions(+), 60 deletions(-) diff --git a/target-mi

[Qemu-devel] [PATCH v2 2/2] target-mips: add Config5.FRE support allowing Status.FR=0 emulation

This relatively small architectural feature adds the following: FIR.FREP: Read-only. If FREP=1, then Config5.FRE and Config5.UFE are available. Config5.FRE: When enabled all single-precision FP arithmetic instructions, LWC1/LWXC1/MTC1, SWC1/SWXC1/MFC1 cause a Reserved Instr

[Qemu-devel] [PATCH v2 0/2] target-mips: add Config5.FRE support

MIPS architectural feature allowing emulation of Status.FR=0 on a CPU with Status.FR hardwired to 1. v2: * move functions and drop prototypes (James) * fix declaration after code (James) Leon Alrae (2): target-mips: move group of functions above gen_load_fpr32() target-mips: add Config5.FRE s

Re: [Qemu-devel] about [SeaBIOS PATCH] Try to hard-reboot on rerun of post even on emulators.

On Tue, Apr 21, 2015 at 10:37:49AM +0200, Laszlo Ersek wrote: > As to how you can fix > (which is the > motivation for this entire discussion): > > - You need to identify *what variable exactly* stores the list of > bootable devices. Is that

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

On 04/21/15 16:38, Paolo Bonzini wrote: > > > On 21/04/2015 16:30, Laszlo Ersek wrote: -MemoryRegion tseg_blackhole; +MemoryRegion tseg_blackhole, tseg_window; PcPciInfo pci_info; ram_addr_t below_4g_mem_size; ram_addr_t above_4g_mem_size; >> W

Re: [Qemu-devel] [PATCH v2.5 00/10] block: incremental backup transactions

On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote: [. . .] > And, invoking `drive-backup` *without* pre-creating the target image > (i.e. 'incremental.o.img'): > > { 'execute': 'drive-backup', > 'arguments': { > 'device': 'ide0-0-0', Small typo (in this email,

Re: [Qemu-devel] [RFC v3] monitor: add memory search commands s, sp

On 21/04/2015 16:35, Luiz Capitulino wrote: > > gladly, I am definitely looking for Review, first I wanted to check if the > > idea itself was acceptable. > > I honestly don't have an opinion on this, which means I'm willing > to apply if there are no objections. > > On the other hand, isn't i

Re: [Qemu-devel] [PATCH 3/3] target-arm: Add the GICv2m to the virt board

On 8 April 2015 at 22:21, Christoffer Dall wrote: > Adding the GICv2m to the virt board should allow us to enable MSIs on > the generic PCI host controller, in theory. > So is this commit message just saying "I haven't tested this patchset" :-), or are we still missing some functionality to get

Re: [Qemu-devel] [PATCH 2/3] arm_gicv2m: Add GICv2m widget to support MSIs

On 8 April 2015 at 22:20, Christoffer Dall wrote: > The ARM GICv2m widget is a little device that handle MSI interrupt > "handles" > writes to a trigger register and ties them to a range of interrupt lines > wires to the GIC. It has a few status/id registers and the interrupt > wires, > and t

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

On 21/04/2015 16:30, Laszlo Ersek wrote: >> > -MemoryRegion tseg_blackhole; >> > +MemoryRegion tseg_blackhole, tseg_window; >> > PcPciInfo pci_info; >> > ram_addr_t below_4g_mem_size; >> > ram_addr_t above_4g_mem_size; >> > > Why is this necessary? If you disable the black

[Qemu-devel] [PATCH RFC 0/2] virtio-ccw realization/plugged handling

Turns out that reworking the realization/plugging sequence for virtio-ccw to make it more similar to virtio-pci (as discussed in https://marc.info/?l=qemu-devel&m=142954827813046&w=2) was easier than expected. At least I have something that seems to look sane, produces working virtio-ccw devices an

[Qemu-devel] [PATCH RFC 2/2] virtio-ccw: implement ->device_plugged

Let's move operations that are only valid after the backend has been realized to a ->device_plugged callback, just as virtio-pci does. Also reorder setting up the host feature bits to the sequence used by virtio-pci. While we're at it, also add a ->device_unplugged callback to stop ioeventfd, just

[Qemu-devel] [PATCH RFC 1/2] virtio-ccw: change realization sequence

virtio-ccw has an odd sequence of realizing devices: first the device-specific relization (net, block, ...), then the generic realization. It feels less odd to have the generic realization callback trigger the device-specific realization instead (and this also matches what virtio-pci does). One th

Re: [Qemu-devel] [PATCH 6/6] [wip] tseg, part2, not (yet) tested

On 04/20/15 11:19, Gerd Hoffmann wrote: > add tseg window to smram region, so cpus can access it in smm mode. > > Signed-off-by: Gerd Hoffmann > --- > hw/pci-host/q35.c | 13 + > include/hw/pci-host/q35.h | 2 +- > 2 files changed, 14 insertions(+), 1 deletion(-) > > diff -

Re: [Qemu-devel] [RFC v3] monitor: add memory search commands s, sp

On 21/04/2015 16:25, Claudio Fontana wrote: > I seem not to get this warning with the compiler version I am currently using, > and after checking the code I could not find out why with some compilers > would emit such a warning. > > It is difficult for me to debug this issue since I do not get

  1   2   >