qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.l.williamson@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1826422] Re: Regression: QEMU 4.0 hangs the host (*bisect included*)
Date: Fri, 26 Apr 2019 13:11:49 -0000	[thread overview]
Message-ID: <155628430918.13556.6374404531618745107.malone@gac.canonical.com> (raw)
In-Reply-To: 155620554968.6380.13610580395862407350.malonedeb@chaenomeles.canonical.com

The change in QEMU 4.0 is only a change in defaults of the machine type,
it can be entirely reverted in the VM config with kernel_irqchip=on or
<ioapic driver='kvm'/> with libvirt.  Using a machine type prior to the
q35 4.0 machine type would also avoid it.  There are no performance
issues with these configurations that would favor using 3.1 over 4.0.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1826422

Title:
  Regression: QEMU 4.0 hangs the host (*bisect included*)

Status in QEMU:
  New

Bug description:
  The commit b2fc91db84470a78f8e93f5b5f913c17188792c8 seemingly
  introduced a regression on my system.

  When I start QEMU, the guest and the host hang (I need a hard reset to
  get back to a working system), before anything shows on the guest.

  I use QEMU with GPU passthrough (which worked perfectly until the
  commit above). This is the command I use:

  ```
  /path/to/qemu-system-x86_64
    -drive if=pflash,format=raw,readonly,file=/path/to/OVMF_CODE.fd
    -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd.tmp
    -enable-kvm
    -machine q35,accel=kvm,mem-merge=off
    -cpu host,kvm=off,hv_vendor_id=vgaptrocks,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time
    -smp 4,cores=4,sockets=1,threads=1
    -m 10240
    -vga none
    -rtc base=localtime
    -serial none
    -parallel none
    -usb
    -device usb-tablet
    -device vfio-pci,host=01:00.0,multifunction=on
    -device vfio-pci,host=01:00.1
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device usb-host,vendorid=<vid>,productid=<pid>
    -device virtio-scsi-pci,id=scsi
    -drive file=/path/to/guest.img,id=hdd1,format=qcow2,if=none,cache=writeback
    -device scsi-hd,drive=hdd1
    -net nic,model=virtio
    -net user,smb=/path/to/shared
  ```

  If I run QEMU without GPU passthrough, it runs fine.

  Some details about my system:

  - O/S: Mint 19.1 x86-64 (it's based on Ubuntu 18.04)
  - Kernel: 4.15
  - `configure` options: `--target-list=x86_64-softmmu --enable-gtk --enable-spice --audio-drv-list=pa`
  - EDK2 version: 1a734ed85fda71630c795832e6d24ea560caf739 (20/Apr/2019)
  - CPU: i7-6700k
  - Motherboard: ASRock Z170 Gaming-ITX/ac
  - VGA: Gigabyte GTX 960 Mini-ITX

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1826422/+subscriptions

  parent reply	other threads:[~2019-04-26 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 15:19 [Qemu-devel] [Bug 1826422] [NEW] Regression: QEMU 4.0 hangs the host (*bisect included*) Saverio Miroddi
2019-04-25 15:19 ` Saverio Miroddi
2019-04-25 16:33 ` [Qemu-devel] [Bug 1826422] " Alex Williamson
2019-04-25 16:33   ` Alex Williamson
2019-04-25 20:11 ` Saverio Miroddi
2019-04-25 20:11   ` Saverio Miroddi
2019-04-26  2:08 ` Alex Williamson
2019-04-26  2:08   ` Alex Williamson
2019-04-26  4:05 ` Alex Williamson
2019-04-26  4:05   ` Alex Williamson
2019-04-26  7:08 ` Saverio Miroddi
2019-04-26  7:08   ` Saverio Miroddi
2019-04-26 13:11 ` Alex Williamson [this message]
2019-04-26 13:11   ` Alex Williamson
2019-04-29 15:59 ` Saverio Miroddi
2019-04-29 15:59   ` Saverio Miroddi
2019-05-22 18:49 ` Alex Williamson
2019-08-16  4:55 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=155628430918.13556.6374404531618745107.malone@gac.canonical.com \
    --to=alex.l.williamson@gmail.com \
    --cc=1826422@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).