Could this affect virtio-scsi? I'm not so sure since it's not perfectly
reliable to reproduce, but v2.12.0 was hanging for me for a few minutes
at a time with virtio-scsi cache=writeback showing 100% disk util%. I
never had issues booting up, and didn't try SATA. v2.11.1 was fine.
My first attempt
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1488363
Title:
qemu 2.4.0 hangs using vfio for pci passthrough of graphics card
Status in QEMU:
It works. :) Thanks a bunch.
I tested linux it originally crashed with, plus the memtest86+ (still
auto rebooted though), and no sign of a problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/15916
FYI I tried my grsec kernel (which also has some =m changed to =y so
maybe I only forgot a modprobe command before) without
acs_override=downstream which works with the revert build, and hangs
without.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subs
It's an AMD FX(tm)-8150 with a GA-990FXA-UD5 board bios version F11. I
also tested without the usb controllers, such as with your suggested
commands. And again below.
root@peter:~ # uname -a
Linux peter 4.6.2-1-MANJARO #1 SMP PREEMPT Wed Jun 8 11:00:08 UTC 2016 x86_64
GNU/Linux
root@peter:~ # ca
** Attachment added: "disk image that reproduces problem"
https://bugs.launchpad.net/qemu/+bug/1591628/+attachment/4684474/+files/qemutest2.img.xz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/159
Attached is a 4.7 MB xz image of a 20 MB disk image that triggers the
problem. It contains a grub2 (2.02~beta2) bootloader, /boot with
memtest86+, and no rootfs.
If I load that as is, it hangs.
If I comment out the "load_video" line, it works. (memtest doesn't run
properly, but auto-reboots, but
** Attachment added: "screenshot fail while booting memtest86+"
https://bugs.launchpad.net/qemu/+bug/1591628/+attachment/4683121/+files/IMG_9592_qemu_fail_memtest.JPG
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
** Attachment added: "screenshot fail while booting linux grsec 4.1.6"
https://bugs.launchpad.net/qemu/+bug/1591628/+attachment/4683120/+files/IMG_9591_qemu_fail_linux.JPG
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bu
** Attachment added: "grub.cfg with only memtest86+ entry remaining and set as
default"
https://bugs.launchpad.net/qemu/+bug/1591628/+attachment/4683122/+files/grub.cfg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
(changed your command with a different iso, and without the usb-host,
and with a pci passthrough of a usb controller, and with a vgarom for my
gpu otherwise I find it hangs if I repeatedly reboot a VM)
If I try with your command with an iso it works. If I replace the iso
with the VM's disk, it fai
FYI I had a similar issue years ago until I figured out that adding the
vgarom file fixes it, eg.:
-device vfio-
pci,host=04:00.0,bus=root.1,multifunction=on,x-vga=on,addr=0.0,romfile=Sapphire.R7260X.1024.131106.rom
For radeon, you can look in /sys. eg. we see
/sys/devices/pci:00/:00
And here's the qemu command (missing \ at the end of the lines)
qemu-system-x86_64
-enable-kvm
-M q35
-m 3584
-cpu host
-boot c
-smp 8,sockets=1,cores=8,threads=1
-vga none
-device ioh3420,bus=pcie.0,addr=1c.0,port=1,chassis=1,id=root.1
-device
vfio-pci,host=0
Public bug reported:
Not a duplicate of my old bug 1488363
qemu version 2.5.1 works fine
qemu version 2.6.0 fails
seabios 1.9.2-1
using kernel 4.5.5 with grsecurity
I built using the arch packaging tools, but commented out all the patch
code, so it should be vanilla.
The problem is just that
With seabios 1.9.1-1 and qemu 2.5.0-1 manjaro packages (which as far as
I know have no patches), it seems to work now.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1488363
Title:
qemu 2.4.0 hangs
I ran a bisect, and here's the result:
b8eb5512fd8a115f164edbbe897cdf8884920ccb is the first bad commit
commit b8eb5512fd8a115f164edbbe897cdf8884920ccb
Author: Nadav Amit
Date: Mon Apr 13 02:32:08 2015 +0300
target-i386: disable LINT0 after reset
Due to old Seabios bug, QEMU reen
Public bug reported:
2.3.0 (manjaro distro package) works fine. 2.4.0 (manjaro or the arch
vanilla one) hangs on the SeaBIOS screen when saying "Press F12 for boot
menu". All tested with the same hardware, OS, command and configuration.
It also starts without the GPU passed through, even with the
17 matches
Mail list logo
