[Qemu-devel] [Bug 1456819] Re: OVMF, Hyper-V, virtio, Win7 incompatibility

Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1185253 especially note (2) under "Additional info" in Comment #0. "Hyper-V extensions + UEFI guest firmware + Win7 guest + guest is multi- VCPU" is not a supported configuration, even in Microsoft's own stack. Virt-manager has been mo

[Qemu-devel] [Bug 1533848] Re: A workaround for Windows 7 ACPI SLIC table behavior when used with OVMF

Fixed in 37ad223^..ae12374. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1533848 Title: A workaround for Windows 7 ACPI SLIC table behavior

[Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

http://thread.gmane.org/gmane.comp.emulators.qemu/390272/focus=391042 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1536487 Title: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU

[Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

sent a patch: http://thread.gmane.org/gmane.comp.emulators.qemu/395014 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1536487 Title: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU

[Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

** Changed in: qemu Status: New => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1536487 Title: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1 Status

[Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

Fix committed in e6915b5f3a874a467a9a65f7ec1d6ef8d251a51a. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1536487 Title: Unable to mi

[Qemu-devel] [Bug 1191606] Re: qemu crashes with iscsi initiator (libiscsi) when using virtio

http://lists.nongnu.org/archive/html/qemu-devel/2013-06/msg03987.html ** Changed in: qemu Status: New => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1191606 Title: qemu crashe

Re: [Qemu-devel] [Bug 1224444] [NEW] virtio-serial loses writes when used over virtio-mmio

On 09/12/13 14:04, Richard Jones wrote: > + -chardev socket,path=/home/rjones/d/libguestfs/tmp/libguestfsLa9dE2/guestfsd.sock,id=channel0 \ Is this a socket that libguestfs pre-creates on the host-side? > the socket is never added to any poll/ppoll syscall, so it's no > wonder that qemu neve

Re: [Qemu-devel] [Bug 1224444] Re: virtio-serial loses writes when used over virtio-mmio

On 09/16/13 16:39, Richard Jones wrote: >> Is this a socket that libguestfs pre-creates on the host-side? > > Yes it is: > https://github.com/libguestfs/libguestfs/blob/master/src/launch-direct.c#L208 > > You mention a scenario that might cause this. But that appears to be > when the socket is o

Re: [Qemu-devel] [Bug 1224444] Re: virtio-serial loses writes when used over virtio-mmio

On 09/17/13 10:09, Peter Maydell wrote: > On 16 September 2013 17:13, Laszlo Ersek wrote: >> H. Normally (as in, virtio-pci), when a VCPU thread (running KVM) >> executes guest code that sends data to the host via virtio, KVM kicks >> the "host notifier" eventfd. > > What happens in the virti

Re: [Qemu-devel] [Bug 1224444] Re: virtio-serial loses writes when used over virtio-mmio

On 09/17/13 11:51, Richard Jones wrote: >> There's at least three cases here I guess (KVM + eventfd, KVM without >> eventfd (enforceable eg. with the "ioeventfd" property for virtio >> devices), and TCG). We're probably talking about the third case. > > To clarify on this point: I have reproduced

Re: [Qemu-devel] [Bug 1529449] Re: serial is required for -device nvme

On 04/28/16 20:07, Tom Yan wrote: > Instead of requiring a serial of arbitrary length/format, I think a > WWN/EUI-64 is more useful/important, WWN/EUI-64 is not "more important". Section "7.9 Unique Identifier" in the NVMe spec (Revision 1.2a, October 23, 2015) says that the serial number is manda

[Qemu-devel] [Bug 1558175] Re: virtio: vm killed (Guest moved used index)

(Bugfix for a similar SeaBIOS bug: 5f2d17d35b23.) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1558175 Title: virtio: vm killed (Guest moved used index) Status in QEMU: New Bug description:

Re: [Qemu-devel] [Bug 1558175] Re: virtio: vm killed (Guest moved used index)

On 03/18/16 10:45, Stefan Hajnoczi wrote: > However, it's still a guest code bug because a driver must not abandon > an active device. Depending on the contents of the rings it could cause > spurious I/O leading to data corruption. > > So this needs to be fixed in DPDK or the application. I agr

[Qemu-devel] [Bug 1558175] Re: virtio: vm killed (Guest moved used index)

Stefan, I too had the same immediate idea upon seeing this bug report. But, after I skimmed the DPDK code briefly, I think it does reset the virtio-net device correctly, before it tries to use it. Instead, at least based on the extensive log that Julien pasted, I believe the following happens: whe

[Qemu-devel] [Bug 1558175] Re: virtio: vm killed (Guest moved used index)

(The iPXE commit in question is 755d2b8f6be6.) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1558175 Title: virtio: vm killed (Guest moved used index) Status in QEMU: New Bug description: Hel

[Qemu-devel] [Bug 1591724] Re: Windows 7 installation DVD can't boot in qemu 2.6.0/OVMF

The following combination: - OVMF without the SeaBIOS CSM ("pure EFI" in Gerd's RPMs) - Cirrus video card - Windows 7 installer in the guest has never been supported. The VBE Shim in OVMF works on stdvga and QXL only. This is documented; please refer to OvmfPkg/README, section "UEFI Windows 7 & W

[Qemu-devel] [Bug 1592315] Re: Windows 10 continuous screen refresh if resize guest to match window size is selected with QXL

Please refer to the following tickets: https://bugs.freedesktop.org/show_bug.cgi?id=94950 https://bugzilla.redhat.com/show_bug.cgi?id=1266484 https://bugzilla.redhat.com/show_bug.cgi?id=1342489 I can't deduce from the above whether it is a host side problem (spice- gtk) or a problem with the VDAg

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

The OVMF build you use (SVN r15214) is from Feb 2014 -- it is completely obsolete. I suggest you use the packages from https://www.kraxel.org/repos/ . I'm marking this as "invalid" because supporting 2+ year old OVMF builds is unthinkable. ** Changed in: qemu Status: New => Invalid -- Yo

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Denis, thanks a lot for the reminder and the analysis here. I knew about this issue at one point -- see https://bugzilla.redhat.com/show_bug.cgi?id=1185253 -- but by now I've completely forgotten that HyperV enlightenments and UEFI SMP Win7 don't mix. Also, for your analysis in comment #7 -- thank

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

... In addition to what I said above in comment #9 (which stands), the technical problem with turning the memory allocation in question into AcpiNVS type is that it would prevent *all* OSes from reusing the area. It would prevent the Windows 7 memory manager from deallocating page #0 (thereby savi

[Qemu-devel] [Bug 1585008] Re: Windows 7 guests hang on bootup when qxl video is used

This is a dupe of LP#1581936 and LP#1591724. The issue is fixed by upstream QEMU commit 94ef4f337fb6. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585008 Title: Windows 7 guests hang on bootup wh

[Qemu-devel] [Bug 1821884] Re: Extend uefi-test-tools to report SMBIOS location

Posted [PULL 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures 20190503093118.15700-1-lersek@redhat.com">http://mid.mail-archive.com/20190503093118.15700-1-lersek@redhat.com -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Qemu-devel] [Bug 1821884] Re: Extend uefi-test-tools to report SMBIOS location

Fixed in commit range 8482ff2eb3bb..24496b8d27d9. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1821884 Title: Extend uefi-test-tool

[Qemu-devel] [Bug 1831477] Re: update edk2 submodule & binaries to edk2-stable201905

Posted [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905 20190606133110.13754-1-lersek@redhat.com">http://mid.mail-archive.com/20190606133110.13754-1-lersek@redhat.com ** Changed in: qemu Status: New => In Progress -- You received this bug notification because you are a m

[Qemu-devel] [Bug 1831477] Re: update edk2 submodule & binaries to edk2-stable201905

[PULL 0/6] update edk2 submodule & binaries to edk2-stable201905 20190614202333.19355-1-lersek@redhat.com">http://mid.mail-archive.com/20190614202333.19355-1-lersek@redhat.com -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bu

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

I haven't done any sort of "narrowing down", but recent QEMUs (built from the master branch, post-v4.1) have corrupted at least two VM disk images (qcow2) for me as well. I had to reinstall both VMs. I didn't make any noise because I was sure that, if I wasn't seeing ghosts, then others must have

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

After reading the message of commit 69f47505ee66 ("block: avoid recursive block_status call if possible", 2019-06-04), I'm none the wiser. But, I can at least confirm that all my qcow2 images are pre-allocated, as a norm. I create them with the following command: qemu-img create \ -f qcow2 \ -

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

(See also / possible duplicate: .) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1846427 Title: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle St

[Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install

Hi Max, from my : I've seen corruption on ext4. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1847793 Title: qemu 4.1.0 - Corrupt guest file

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

In reply to Kevin's comment#13: > I find Laszlo's case with a preallocated image particularly surprising > because the behaviour isn't supposed to have changed at all for > preallocated images, at least if the heuristics still detects them as > such. But isn't that "if" at the core of this proble

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

In reply to : > Is it possible that we're talking about some kind of miscompilation > here, maybe because gcc-9.2.0 is just that tiny bit too spanking > current? I'm riding the trailing edge here (gcc-4.8 in RHEL7) :) [...] -- You recei

[Bug 1852196] Re: update edk2 submodule & binaries to edk2-stable201911

Yes, I do have a reason for delaying this LP until after 4.2.0 is out. When I filed this ticket (on 2019-Nov-12), QEMU had already entered the 4.2.0 soft feature freeze (on 2019-Oct-29). Despite possible appearances, this LP is actually a feature addition -- that's why I also set "Tags: feature-re

[Qemu-devel] [Bug 1838703] Re: Makefile BUG in edk2 firmware install 4.1.0-rc3

The same issue was reported and patched on qemu-devel by Olaf Hering two months ago. The patch received three Reviewed-by tags, but nobody bothered to queue it. [Qemu-devel] [PATCH v1] Makefile: remove DESTDIR from firmware file cont The thread is split over two months, hence two links below, int

[Qemu-devel] [Bug 1838703] Re: Makefile BUG in edk2 firmware install 4.1.0-rc3

Fixed in commit 177cd674d620 ("Makefile: remove DESTDIR from firmware file content", 2019-08-03), part of v4.1.0-rc4. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. htt

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Can you post the host dmesg that is written at the time of the guest crash? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash Status in QEMU: New Bug descriptio

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

(I should have given the pattern /sys/module/kvm_intel/parameters/*, but the result is the same.) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash Status in QEMU:

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Please add the output of the following command too: tail /sys/module/kvm/holders/kvm_intel/parameters/* Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

We could also try changing upstream iPXE so that the FXSAVE trick is not active for CONFIG=qemu. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash Status in QEMU:

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Gerd, do you think we should rebuild the iPXE binaries bundled with QEMU with the offending iPXE commit (71560d185475) reverted, at least until KVM gets FXSAVE emulation in big real mode? I think this would be reasonable, as that iPXE commit works around a bug in the IBM Tivoli Provisioning Manager

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

(--> the rebuilt binaries should go into v2.7.1, if we agree) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash Status in QEMU: New Bug description: I am runn

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

(In other news, Launchpad continues to suck incredibly. Did you see how it broke up "unrestricted_guest" in my previous comment?) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

BTW, this bug can be easily reproduced on hosts that do feature unrestricted_guest, just reload the kvm_intel module with unrestricted_guest=N. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 T

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Some more reports on ipxe-devel: http://lists.ipxe.org/pipermail/ipxe-devel/2016-October/005203.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-October/005210.html Radim just posted the KVM feature patches: [PATCH 0/2] KVM: x86: emulate fxsave and fxrstor https://www.spinics.net/lists/kerne

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Thanks. It's indeed the same issue, you have unrestricted_guest=N and emulate_invalid_guest_state=Y. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623276 Title: qemu 2.7 / iPXE crash Status in QE

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

The iPXE patches are now upstream (a big "thank you" to the iPXE maintainer!); QEMU 2.8 -- with Gerd willing -- should bundle iPXE binaries containing that fix. http://lists.ipxe.org/pipermail/ipxe-devel/2016-November/005244.html ** Changed in: qemu Status: New => Confirmed ** Changed in:

[Qemu-devel] [Bug 1623276] Re: qemu 2.7 / iPXE crash

Fixed in: commit 423f7cf233fe262c777db7f87db3e9fac29e02d1 Author: Gerd Hoffmann Date: Wed Nov 9 09:48:44 2016 +0100 ipxe: update to 20161108 snapshot ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu-

[Qemu-devel] [Bug 1629282] Re: QEMU (still) hangs on Windows 7 install

I'll assume "OVMF_15214.fd" is from . It's an ancient build of OVMF (older than two and half years). The binary packaged in that ZIP file isn't even a split one, it's a unified binary that is unsuitable for the command line that you've given above. Please either gra

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

@alex3kov -- I think you mean the question as """ Since this behaviour will not change in future versions of Windows 7 / Windows Server 2008 R2, ... """ because, again, the problem is not in OVMF but in the Windows guest. QEMU cannot be expected to recognize (guest OS, guest firmware, hw config

[Qemu-devel] [Bug 1635695] Re: ovmf + smp + hyper-v + windows 7: doesn't work

*** This bug is a duplicate of bug 1593605 *** https://bugs.launchpad.net/bugs/1593605 Sigh, the Windows bug that keeps on giving. And, users avoiding libvirt and sticking with the QEMU command line, despite the fact that using libvirt & its tools would save them from this bug. Anyway, this r

[Qemu-devel] [Bug 1606899] Re: virtio-vga does not let guest poweroff properly

Does the issue persist if you remove the intel-hda device (id=sound0) and the dependent hda-duplex device (id=sound0-codec0)? Asking because of . If it persists, then please capture a stack dump with gdb, when QEMU is hung. (

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

Fixed in commit f58b39d2d5b6dea1a757e1dc7d67a44eac1c4f9c. ** Changed in: qemu Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1594239 Title: After adding mo

[Qemu-devel] [Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

(1) What phase of the guest do you get invalid video output in? Do you see the TianoCore splash screen? Does the grub2 menu appear? (2) I cannot reproduce the issue (with a different guest OS anyway); I just tried QEMU (at d1c82f7cc344) and OVMF (built from edk2 at 7cf59c854f35), with stdvga; this

[Qemu-devel] [Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

Added Marc-André and Gerd to the CC list. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1658634 Title: Can't get correct display with latest QEMU and OVMF BIOS Status in QEMU: Confirmed Bug des

[Qemu-devel] [Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

For reference, this is my script: ISO=ubuntu-16.04.1-desktop-amd64.iso CODE=OVMF_CODE.fd TMPL=OVMF_VARS.fd cp $TMPL vars.fd qemu-system-x86_64 \ -m 1024 \ -M pc,accel=kvm \ -device VGA \ -drive if=pflash,readonly,format=raw,file=$CODE \ -drive if=pflash,format=raw,file=vars.fd \ -dri

[Qemu-devel] [Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

I downloaded "ubuntu-16.04.1-desktop-amd64.iso" (MD5: 17643c29e3c4609818f26becf76d29a3), and I can reproduce the issue -- the grub2 display is corrupt. (I didn't even look further than that.) I also confirm that it works fine with the same firmware, but using QEMU 2.7. Here's the result of the bis

Re: [Qemu-devel] [Bug 1658634] [PATCH] console: fix console resize

On 01/24/17 11:37, elmarco wrote: > Hi > > On Tue, Jan 24, 2017 at 2:31 PM Gerd Hoffmann <1658...@bugs.launchpad.net> > wrote: > >> Only skip surface reallocation in case the old surface was created using >> qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we >> might end up wit

[Qemu-devel] [Bug 1721221] Re: PCI-E passthrough of Nvidia GTX GFX card to Win 10 guest fails with "kvm_set_phys_mem: error registering slot: Invalid argument"

There's another bug report / discussion thread on qemu-devel about the same commit: 1505913885.24609.8.camel@redhat.com">http://mid.mail-archive.com/1505913885.24609.8.camel@redhat.com I'll add a note to that thread about this LP report too. -- You received this bug notification because you are

Re: [Qemu-devel] [Bug 1723927] [NEW] Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

On 10/16/17 13:26, chan wrote: > Public bug reported: > > Hi, > > I started windows server 2012 DC or redhat7.0, but boot failed by UEFI, and > start process stop on > "TianoCore" image by looking at VNCviewer. > > VM using the command:(redhat7.0) > /usr/bin/kvm -name guest=ytest,debug-threads=

[Qemu-devel] [Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

Sigh, in bullet (1) of comment #10, I obviously didn't mean to link this same LP entry. Instead I meant . Sorry. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpa

[Qemu-devel] [Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

(1) See also . (2) One idea is (a) letting Windows use VirtioGpuDxe's GOP (blt only) until it calls ExitBootServices() -- which I have already confirmed to work with an ARM64 Windows Server variant that I was legally given access to --, and (b) once av

[Qemu-devel] [Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

@Andrew: are you implying that you successfully rebuilt the virtio guest drivers for ARM64 Windows? If that's the case, could you please share specifics about the build setup? I'm not the one working on the virtio GPU driver for Windows, but I assume your aarch64 build steps would apply to that dri

[Qemu-devel] [Bug 1778350] Re: Android-x86 4.4-r5 won't boot on QEMU since v2.11.0-rc2

@navicrej -- can you please apply the series [Qemu-devel] [PATCH 0/2] hw/pci-host/x86: extend the 64-bit PCI hole relative to the fw-assigned base https://patchew.org/QEMU/20180924221346.16733-1-ler...@redhat.com/ on your end, and see if it makes a difference? (I don't expect it to, for the rea

[Qemu-devel] [Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

"-bios /usr/share/qemu-kvm/OVMF_CODE.fd" is *never* a correct option to boot OVMF. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by uefi on CPU of

[Qemu-devel] [Bug 1714331] Re: Virtual machines not working anymore on 2.10

See also LP#1725560. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1714331 Title: Virtual machines not working anymore on 2.10 Status in QEMU: New Bug description: Using 2.10, my virtual mach

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

See also LP#1725560. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715700 Title: Windows 7 guest won't boot on qemu 2.10 (works on 2.9) Status in QEMU: Fix Committed Bug description: Qemu ve

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

Thanks, Gerd, for the CC -- I agree, this commit (208fa0e43645) almost certainly breaks the VBE Shim. Displaying the patch with a bit larger context, > diff --git a/hw/i386/pc.c b/hw/i386/pc.c > index 22e16031b03b..59435390ba62 100644 > --- a/hw/i386/pc.c > +++ b/hw/i386/pc.c > @@ -1442,8 +1442,11

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

I'm not sure if I mentioned this before, but launchpad is an *abomination*. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715700 Title: Windows 7 guest won't boot on qemu 2.10 (works on 2.9) Stat

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

I'd also like to mention that, when we originally worked on the VBE Shim, I tried to put it elsewhere. Obviously it has to be pointed-to by a real mode interrupt vector, which limits quite a bit where it can go at all; the point is that I tried to put it into low *RAM* (under 640KB). It didn't wor

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

What I mentioned earlier was not that SeaBIOS would break. Instead, I said that building OVMF, with the SeaBIOS CSM (Compatibility Support Module) embedded into it, would break, exactly the same way as the VBE Shim. Quoting the CSM Spec from Intel: "The CSM provides compatibility support between

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

Re: comment 14, "is there a way to fix vbeshim instead of reverting RO limitation that commit introduced?": I don't think so; please see my earlier comments 15 and 17. To elaborate: If a user wants to boot Windows 7 on OVMF, they have *three* options: (1) Build the SeaBIOS CSM (CONFIG_CSM=y), an

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

Indeed the CSM platform support had the same error one and half years ago, see: https://github.com/tianocore/edk2/commit/db27e9f3d8f0 Thank you, Gerd, for the hint! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launch

Re: [Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

On 09/19/17 13:49, Gerd Hoffmann wrote: > ovmf seems to not touch pam configuration, so rom remains mapped. I don't understand; the code that I quoted above -- and that LaunchPad messed up -- explicitly changes the PAM registers: // // Put the shim in place first. // Pam1Address = PCI_LIB

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

Ahh, wait, now I remember something -- the PAM registers are at a different location on Q35!!! If that's what's wrong, then it is indeed an OVMF bug. Let me see if I can write a patch. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

Re: [Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

On 09/19/17 14:38, Gerd Hoffmann wrote: >> (2) Build the SeaBIOS CSM (CONFIG_CSM=y), and embed it into OVMF, >> like described above. Then, boot Windows 7 in *UEFI Mode*. > >> Option #1 and option #2 no longer work because the CSM infrastructure >> in edk2 needs to be able to write 0xc. > > W

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

Posted: [edk2] [PATCH 0/3] OvmfPkg/QemuVideoDxe/VbeShim: handle PAM1 register on Q35 correctly https://lists.01.org/pipermail/edk2-devel/2017-September/014898.html I CC'd Aleksei on the series, but testing is welcome from anyone. (The cover letter at the link contains a git fetch URL.) -- You

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

edk2 commit range: b68c793144e8..947f3737abf6. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715700 Title: Windows 7 guest won't boot on qe

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

The issue is that virtio-mmio devices don't distinguish themselves on the sysbus level. Using the small reproducer from Cole, and setting a breakpoint on virtio_bus_get_dev_path(), for the second virtio-scsi-device we get: ... qdev_get_dev_path() virtio_bus_get_dev_path()

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

I don't think this difference is intentional. I think we're seeing an interplay between the following two commits: * http://git.qemu.org/?p=qemu.git;a=commitdiff;h=4d2ffa08b601b * http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7685ee6abcb93 Referring to the message of the second commit above, the

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

I'll try to come up with a patch, if for nothing more than illustration. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1594239 Title: After adding more scsi disks for Aarch64 virtual machine, start

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

Posted a patch: http://lists.nongnu.org/archive/html/qemu- devel/2016-07/msg01119.html -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1594239 Title: After adding more scsi disks for Aarch64 virtual

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

A virtio-mmio "bus" is a single-device transport. It has a fixed base address that is set at board creation time. The MMIO area is 0x200 bytes in size, and hosts the virtio registers for one device that can sit on this transport. Transports can be unused. The "virt" machtype creates 32 transports

[Bug 1888971] Re: SMI trigger causes hang with multiple cores

Does coreboot do anything to set up an SMI handler? Does it relocate SMBASE for all processors? Misbehavior upon raising an SMI is fully expected, unless the guest (usually the guest firmware) sets up SMI handling properly. The bug report currently includes only two bits of information about gues

[Bug 1888971] Re: SMI trigger causes hang with multiple cores

> I guess fundamentally th issue is writing 0xXX in IO port 0xB2 should > trigger SMI handler in all possible core but instead it triggers SMI > only in Core#0. For that, the guest needs to negotiate the "broadcast SMI" feature with QEMU. See commit range 57bb40c9db40..b8bab8eb6934. -- You recei

[Bug 1886602] Re: Windows 10 very slow with OVMF

Inactive for more than a month, significant amount of info was not provided. Closing. ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1886602 Title

[Bug 1888971] Re: SMI trigger causes hang with multiple cores

Inactive for ~two weeks, closing. ** Changed in: qemu Status: New => Incomplete ** Changed in: qemu Status: Incomplete => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1888971

[Bug 1858814] Re: 'make -C roms efi' does not update edk2 submodules

Symptom persists as of v5.1.0, but I don't think it really matters. We should close the ticket as wontfix. ** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net

[Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install

Can we close this ticket 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/1847793 Title: qemu 4.1.0 - Corrupt guest filesystem after new vm install Status in QEMU: New Bug description: When

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

Commit 5e9785505210 was released in v4.2.0; closing this ticket. ** Changed in: qemu Status: Fix Committed => 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/1846427 Title: 4.1.0

[Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

No need to keep this open any longer (no activity for 19 months). Please follow the links captured above to the past discussions. There's nothing new to add wrt. the situation. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qem

[Bug 1826200] Re: RFE: populate "OEM Strings" (type 11) SMBIOS table strings from regular files

We'll probably never have resources for this -- nice to have feature, but has not become critical in ~1.5 years. LP doesn't allow me to close the ticket as "Won't Fix", so I'll have to go with "Invalid". (The report is not invalid at all, but the ticket status should *somehow* reflect that we have

[Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

Fixed in commit 3ef0c573d37b ("console: fix console resize", 2017-01-31), released in v2.9.0. ** Changed in: qemu Status: Confirmed => 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/bu

[Bug 1886602] Re: Windows 10 very slow with OVMF

** Changed in: qemu Status: Incomplete => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1886602 Title: Windows 10 very slow with OVMF Status in QEMU: Invalid Bug description: D

[Bug 893208] Re: qemu on ARM hosts can't boot i386 image

The qemu-linaro project seems to have been discontinued; the wiki and git repo links at don't work, and the latest release seems to be "qemu-linaro-1.7.0-2014.01.tar.gz". Marking this ticket as "invalid" for the qemu-linaro project. ** Changed in: qemu-linaro

[Bug 1529449] Re: serial is required for -device nvme

No new developments for 4+ years, closing as invalid (I'd prefer "wontfix due to lack of resources", but I'm unable to pick that resolution). ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Bug 1217339] Re: SIGQUIT to send ACPI-shutdown to Guest

The discussion noted in comment#4 petered out in March 2017. Closing this ticket as "Invalid" (only because LP does not let me use the "Won't Fix" resolution -- the report / feature request may very well have had merit, but apparently a good enough design could not be found). ** Changed in: qemu

[Bug 1778350] Re: Android-x86 4.4-r5 won't boot on QEMU since v2.11.0-rc2

No feedback for almost two years, closing. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1778350 Title: Android-x86 4.4-r5 won't boot on QEMU sinc

[Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

Closing due to almost 3 years of inactivity. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by ue

[Bug 1813165] Re: KVM internal error. Suberror: 1 emulation failure

According to comment #12, the bug underlying this LP ticket was fixed in Linux kernel commit ad7dc69aeb23 ("x86/kvm/mmu: fix switch between root and guest MMUs", 2019-02-22), released in v5.0. ** Project changed: qemu => linux ** Changed in: linux Status: New => Fix Released -- You recei

[Bug 1918917] Re: synchronous abort on accessing unused I/O ports on aarch64

** Summary changed: - synchronous about on accessing unused I/O ports on aarch64 + synchronous abort on accessing unused I/O ports on aarch64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1918917 Ti

  1   2   >