[Qemu-devel] [Bug 1736042] Re: qemu-system-x86_64 does not boot image reliably

Please always use the latest version of QEMU (currently v2.10, soon v2.11) when reporting bugs to the upstream QEMU project - we don't support old versions like v2.5 any more. So I guess you wanted to report a bug agains v2.5 in Ubuntu instead and I changed the target of this bug accordingly. **

Re: [Qemu-devel] [PATCH 1/2] colo: compare the packet based on the tcp sequence number

On Mon, Dec 4, 2017 at 3:32 AM, Mao Zhongyi wrote: > > > On 12/04/2017 09:41 AM, Zhang Chen wrote: > >> >> >> On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi > > wrote: >> >> The primary and secondary

[Qemu-devel] Guest Reboot After Plug HDMI

Hello, Everybody. I encounter a problem when i using my guest.I booting my guest without HDMI primarily, Then i add it, but my guest is be rebooted.To know what cause it, i do it again, especially i check my guest is running normal or not with "ping" before plugging, that's well.What i was

Re: [Qemu-devel] [PATCH v1] spapr.c: Update qemu's maxcpus for pseries machine.

Thanks David for the explanation. I thought the changes been into upstream code for pseries to limit maxcpus to 240 instead of 1024. On 12/01/2017 06:07 PM, David Gibson wrote: On Fri, Dec 01, 2017 at 04:54:09PM +0530, Seeteena Thoufeek wrote: Need to adjust the max cpus supported number

Re: [Qemu-devel] [PATCH v3 3/3] nvdimm: add 'unarmed' option

On 12/01/17 10:44 +, Stefan Hajnoczi wrote: > On Mon, Nov 27, 2017 at 12:35:17PM +0800, Haozhong Zhang wrote: > > @@ -312,6 +315,10 @@ nvdimm_build_structure_memdev(GArray *structures, > > DeviceState *dev) > > > > /* Only one interleave for PMEM. */ > >

Re: [Qemu-devel] [PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled

On 12/01/2017 11:49 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote: The guest free pages should not be discarded by the live migration thread when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because skipping the transfer of such poisoned

Re: [Qemu-devel] [for-2.12 3/7] pci: Fold pci_bus.h into pci.h

On Fri, Dec 01, 2017 at 06:29:39PM +0200, Michael S. Tsirkin wrote: > On Thu, Nov 30, 2017 at 03:02:48PM +1100, David Gibson wrote: > > On Wed, Nov 29, 2017 at 12:38:00PM +0200, Marcel Apfelbaum wrote: > > > On 29/11/2017 10:46, David Gibson wrote: > > > > include/hw/pci/pci_bus.h is now very

Re: [Qemu-devel] [PATCH v4 31/32] migration, qmp: new command "migrate-pause"

On Fri, Dec 01, 2017 at 04:53:28PM +, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > It is used to manually trigger the postcopy pause state. It works just > > like when we found the migration stream failed during postcopy, but > > provide an explicit way for user

Re: [Qemu-devel] [PATCH v4 30/32] migration: delay the postcopy-active state switch

On Fri, Dec 01, 2017 at 12:34:32PM +, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > Switch the state until we try to start the VM on destination side. The > > problem is that without doing this we may have a very small window that > > we'll be in such a state: > >

Re: [Qemu-devel] [for-2.12 3/7] pci: Fold pci_bus.h into pci.h

On Sun, Dec 03, 2017 at 07:07:36AM +0200, Michael S. Tsirkin wrote: > On Sat, Dec 02, 2017 at 11:59:20AM +1100, David Gibson wrote: > > On Fri, Dec 01, 2017 at 06:29:39PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Nov 30, 2017 at 03:02:48PM +1100, David Gibson wrote: > > > > On Wed, Nov 29,

Re: [Qemu-devel] [PATCH v1 2/2] intel-iommu: Extend address width to 48 bits

On Fri, Dec 01, 2017 at 09:02:30AM -0800, Prasad Singamsetty wrote: [...] > > > > > And... you may also need to create that PC_COMPAT_2_11 macro after > > 2.11 is released. For that you can refer to a6fd5b0e050a. > > > > Anyway, I think this "set default" work can be postponed after recent >

[Qemu-devel] [PULL 3/3] spapr: Include "pre-plugged" DIMMS in ram size calculation at reset

At guest reset time, we allocate a hash page table (HPT) for the guest based on the guest's RAM size. If dynamic HPT resizing is not available we use the maximum RAM size, if it is we use the current RAM size. But the "current RAM size" calculation is incorrect - we just use the "base" ram_size

[Qemu-devel] [PULL 1/3] pseries: fix TCG migration

From: Laurent Vivier Migration of pseries is broken with TCG because QEMU tries to restore KVM MMU state unconditionally. The result is a SIGSEGV in kvm_vm_ioctl(): #0 kvm_vm_ioctl (s=0x0, type=-2146390353) at qemu/accel/kvm/kvm-all.c:2032 #1 0x0001003e3e2c

[Qemu-devel] [PULL 2/3] target-ppc: Don't invalidate non-supported msr bits

From: Kurban Mallachiev The msr invalidation code (commits 993eb and 2360b) inverts all bits except MSR_TGPR and MSR_HVB. On non PowerPC 601 processors this leads to incorrect change of excp_prefix in hreg_store_msr() function. The problem is that new msr value get

[Qemu-devel] [PULL 0/3] ppc-for-2.11 queue 20171204

The following changes since commit c11d61271b9e6e7a1f0479ef1ca8fb55fa457a62: Update version for v2.11.0-rc3 release (2017-11-29 17:59:34 +) are available in the Git repository at: git://github.com/dgibson/qemu.git tags/ppc-for-2.11-20171204 for you to fetch changes up to

Re: [Qemu-devel] [PATCH v18 07/10] virtio-balloon: VIRTIO_BALLOON_F_SG

On 12/01/2017 11:38 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:23PM +0800, Wei Wang wrote: +static void send_one_desc(struct virtio_balloon *vb, + struct virtqueue *vq, + uint64_t addr, + uint32_t len, +

Re: [Qemu-devel] [PATCH 2/2] colo: add trace for the tcp packet comparison

On 12/04/2017 09:53 AM, Zhang Chen wrote: On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi > wrote: Cc: Zhang Chen > Cc: Li Zhijian

Re: [Qemu-devel] [PATCH 1/2] colo: compare the packet based on the tcp sequence number

On 12/04/2017 09:41 AM, Zhang Chen wrote: On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi > wrote: The primary and secondary guest has the same TCP stream, but the the packet sizes are different due to the different

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: > On 12/01/2017 05:14 AM, David Gibson wrote: > > On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: > >> On 11/30/2017 05:55 AM, David Gibson wrote: > >>> On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater

Re: [Qemu-devel] [PATCH 1/1] main loop: remove useless code

Hi Peter Maydell: Got it, thank you very much! 2017-12-02 19:52 GMT+08:00 Peter Maydell : > On 2 December 2017 at 07:41, FelixYao wrote: > > hi Paolo Bonzini: > > > > Those codes seem useless, Could it be removed? > > > > Signed-off-by: FelixYao

Re: [Qemu-devel] [PATCH 13/25] spapr: introduce the XIVE Event Queues

On Fri, Dec 01, 2017 at 05:36:39PM +0100, Cédric Le Goater wrote: > On 12/01/2017 12:35 AM, David Gibson wrote: > > On Thu, Nov 30, 2017 at 02:06:27PM +, Cédric Le Goater wrote: > >> On 11/30/2017 04:38 AM, David Gibson wrote: > >>> On Thu, Nov 23, 2017 at 02:29:43PM +0100, Cédric Le Goater

Re: [Qemu-devel] [PATCH 14/25] spapr: push the XIVE EQ data in OS event queue

On Sat, Dec 02, 2017 at 08:46:19AM -0600, Benjamin Herrenschmidt wrote: > On Sat, 2017-12-02 at 08:45 -0600, Benjamin Herrenschmidt wrote: > > On Fri, 2017-12-01 at 15:10 +1100, David Gibson wrote: > > > > > > Hm, ok. Guest endian (or at least, not definitively host-endian) data > > > in a plain

Re: [Qemu-devel] [PATCH 2/2] colo: add trace for the tcp packet comparison

On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi wrote: > Cc: Zhang Chen > Cc: Li Zhijian > Cc: Jason Wang > > Signed-off-by: Mao Zhongyi > --- > net/colo-compare.c | 16

Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] target/ppc: Fix system lockups caused by interrupt_request state corruption

On Mon, Dec 04, 2017 at 12:00:40PM +1100, David Gibson wrote: > On Fri, Dec 01, 2017 at 03:49:07PM +, Richard Purdie wrote: > > Occasionally in Linux guests on x86_64 we're seeing logs like: > > > > ppc_set_irq: 0x55b4e0d562f0 n_IRQ 8 level 1 => pending 0100req 0004 > > > > when they

Re: [Qemu-devel] [PATCH 15/25] spapr: notify the CPU when the XIVE interrupt priority is more privileged

On Sat, Dec 02, 2017 at 08:40:58AM -0600, Benjamin Herrenschmidt wrote: > On Thu, 2017-11-30 at 16:00 +1100, David Gibson wrote: > > > > > static uint64_t spapr_xive_icp_accept(sPAPRXiveICP *icp) > > > { > > > -return 0; > > > +uint8_t nsr = icp->tima_os[TM_NSR]; > > > + > > > +

Re: [Qemu-devel] [PATCH 1/2] colo: compare the packet based on the tcp sequence number

On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi wrote: > The primary and secondary guest has the same TCP stream, but the > the packet sizes are different due to the different fragmentation. > > In the current impletation, compare the packet with the size of >

Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] target/ppc: Fix system lockups caused by interrupt_request state corruption

On Fri, Dec 01, 2017 at 03:49:07PM +, Richard Purdie wrote: > Occasionally in Linux guests on x86_64 we're seeing logs like: > > ppc_set_irq: 0x55b4e0d562f0 n_IRQ 8 level 1 => pending 0100req 0004 > > when they should read: > > ppc_set_irq: 0x55b4e0d562f0 n_IRQ 8 level 1 => pending

Re: [Qemu-devel] [Qemu-ppc] [PATCH 3/3] maint: Fix macros with broken 'do/while(0); ' usage

On Thu, Nov 30, 2017 at 07:41:59AM -0600, Eric Blake wrote: > The point of writing a macro embedded in a 'do { ... } while (0)' > loop is so that the macro can be used as a drop-in statement with > the caller supplying the trailing ';'. Although our coding style > frowns on brace-less 'if': >

[Qemu-devel] [Bug 1736042] [NEW] qemu-system-x86_64 does not boot image reliably

Public bug reported: Booting image as root user with following command works randomly. ./qemu-system-x86_64 -enable-kvm -curses -smp cpus=4 -m 8192 /root/ructfe2917_g.qcow2 Most of the time it ends up on "800x600 Graphic mode"(been stuck there even for 4 hours before killed), but 1 out of ~20

[Qemu-devel] [Bug 1715715] Re: [qemu-ppc] Segfault when booting from HD after MacOS9 install

I just tried the latest git and it actually boots fine with your command... so I guess whatever issue I was having (the null dereference in the timer code I pasted above) must have been fixed... however I've noticed another issue with a different command that causes the bootup to hang:

[Qemu-devel] [Bug 1715715] Re: [qemu-ppc] Segfault when booting from HD after MacOS9 install

I've just tested MacOS 9.2.1 as part of my QEMU pre-release testing and it works fine for me with latest QEMU git and the following command line: qemu-system-ppc -M mac99 -m 256 -drive file=os921.qcow2,format=qcow2,media=disk -net nic,model=rtl8139 -net user Note that the QEMU mac99 machine now

Re: [Qemu-devel] [PATCH 05/17] timer: generalize Dallas/Maxim RTC i2c devices

On 11/29/2017 11:13 PM, David Gibson wrote: > On Sun, Nov 26, 2017 at 03:59:03PM -0600, Michael Davidsaver wrote: >> Support for: ds1307, ds1337, ds1338, ds1339, >> ds1340, ds1375, ds1388, and ds3231. >> >> Tested with ds1338 and ds1375. >> >> Signed-off-by: Michael Davidsaver

[Qemu-devel] R: Re: [PATCH] qemu-pr-helper: miscellaneous fixes

- Dr. David Alan Gilbert ha scritto: > * Paolo Bonzini (pbonz...@redhat.com) wrote: > > 1) Return a generic sense if TEST UNIT READY does not provide one; > > > > 2) Fix two mistakes in copying from the spec. > > > > Reported-by: Dr. David Alan Gilbert

Re: [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

Hi Max, On 12/01/2017 06:13 PM, Max Reitz wrote: On 2017-11-16 23:35, Daniel Henrique Barboza wrote: This patch implements a test case for the scenario that was failing prior to the patch "migration/ram.c: do not set 'postcopy_running' in POSTCOPY_INCOMING_END". This new test file 198 was

Re: [Qemu-devel] [PULL 3/8] nbd-client: Refuse read-only client with BDRV_O_RDWR

On Thu, Nov 09, 2017 at 10:59:34AM -0600, Eric Blake wrote: > The NBD spec says that clients should not try to write/trim to > an export advertised as read-only by the server. But we failed > to check that, and would allow the block layer to use NBD with > BDRV_O_RDWR even when the server is

Re: [Qemu-devel] [PATCH 7/7] target/arm: Implement TT instruction

On 12/01/2017 10:44 AM, Peter Maydell wrote: > Implement the TT instruction which queries the security > state and access permissions of a memory location. > > Signed-off-by: Peter Maydell > --- > target/arm/helper.h| 2 + > target/arm/helper.c| 108 >

Re: [Qemu-devel] [Bug 1735384] Re: OpenJDK JVM segfaults on qemu-sh4 (regression)

On 01.12.2017 00:25, John Paul Adrian Glaubitz wrote: > The offending commit is: > > d25f2a72272b9ffe0d06710d6217d1169bc2cc7d is the first bad commit > commit d25f2a72272b9ffe0d06710d6217d1169bc2cc7d > Author: Alex Bennée > Date: Mon Nov 13 13:55:27 2017 + > >

Re: [Qemu-devel] [PATCH 6/7] target/arm: Factor MPU lookup code out of get_phys_addr_pmsav8()

On 12/01/2017 10:44 AM, Peter Maydell wrote: > For the TT instruction we're going to need to do an MPU lookup that > also tells us which MPU region the access hit. This requires us > to do the MPU lookup without first doing the SAU security access > check, so pull the MPU lookup parts of

Re: [Qemu-devel] [PATCH 5/7] target/arm: Create new arm_v7m_mmu_idx_for_secstate_and_priv()

On 12/01/2017 10:44 AM, Peter Maydell wrote: > The TT instruction is going to need to look up the MMU index > for a specified security and privilege state. Refactor the > existing arm_v7m_mmu_idx_for_secstate() into a version that > lets you specify the privilege state and one that uses the >

Re: [Qemu-devel] [PATCH 4/7] target/arm: Split M profile MNegPri mmu index into user and priv

On 12/01/2017 10:44 AM, Peter Maydell wrote: > For M profile, we currently have an mmu index MNegPri for > "requested execution priority negative". This fails to > distinguish "requested execution priority negative, privileged" > from "requested execution priority negative, usermode", but > the

Re: [Qemu-devel] [PATCH 3/7] target/arm: Add missing M profile case to regime_is_user()

On 12/01/2017 10:44 AM, Peter Maydell wrote: > When we added the ARMMMUIdx_MSUser MMU index we forgot to > add it to the case statement in regime_is_user(), so we > weren't treating it as unprivileged when doing MPU lookups. > Correct the omission. > > Signed-off-by: Peter Maydell

Re: [Qemu-devel] [PATCH 2/7] target/arm: Allow explicit writes to CONTROL.SPSEL in Handler mode

On 12/01/2017 10:44 AM, Peter Maydell wrote: > In ARMv7M the CPU ignores explicit writes to CONTROL.SPSEL > in Handler mode. In v8M the behaviour is slightly different: > writes to the bit are permitted but will have no effect. > > We've already done the hard work to handle the value in >

Re: [Qemu-devel] [PATCH 1/7] target/arm: Handle SPSEL and current stack being out of sync in MSP/PSP reads

On 12/01/2017 10:44 AM, Peter Maydell wrote: > For v8M it is possible for the CONTROL.SPSEL bit value and the > current stack to be out of sync. This means we need to update > the checks used in reads and writes of the PSP and MSP special > registers to use v7m_using_psp() rather than directly

Re: [Qemu-devel] [PATCH v2 4/7] chardev: Clean up previous patch indentation

On Sat, Dec 2, 2017 at 12:24 AM, Eric Blake wrote: > The previous patch left in an extra scope layer for ease of > review; time to remove it. No semantic change. > > Signed-off-by: Eric Blake > Reviewed-by: Marc-André Lureau

Re: [Qemu-devel] [PATCH v2 3/7] chardev: Use goto/label instead of do/break/while(0)

On Sat, Dec 2, 2017 at 12:24 AM, Eric Blake wrote: > Use of a do/while(0) control flow in order to permit an early break > is an unusual paradigm, and triggers a false positive with a planned > future syntax check against 'while (0);'. Rewrite the code to use a > goto instead.

Re: [Qemu-devel] [PATCH] spapr: fix LSI interrupt specifiers in the device tree

On Sat, Dec 02, 2017 at 08:30:11PM +0100, Greg Kurz wrote: > PAPR 2.7 C.6.9.1.2 describes the "#interrupt-cells" property of the > PowerPC External Interrupt Source Controller node as follows: > > “#interrupt-cells” > > Standard property name to define the number of cells in an interrupt- >