maybe this is just this issue?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795857
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823152
Title:
QEMU not able to boot ubuntu 18.04 as a gues
** Attachment added: "qemu-cmdline"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240132/+files/qemu-cmdline
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs
** Attachment added: "debug-nonworking.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240134/+files/debug-nonworking.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Titl
** Attachment added: "qemu-cmdline"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240133/+files/qemu-cmdline
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs
** Attachment added: "debug-working-222G.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240135/+files/debug-working-222G.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
** Attachment added: "debug-working-novirtio-net.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240137/+files/debug-working-novirtio-net.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
** Attachment added: "debug-working-2.6.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240136/+files/debug-working-2.6.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Ti
i see,
but is there a good reason why it did work with an older qemu version/machine
type (<= 2.6)
also my cpuinfo says physical bits 39 but i cannot use more maxmem than 222G
i attached the cpuinfo, cmdline, and debug logs for a nonworking invocation and
one for each working, with 222G, with ma
i forgot:
it also works with
-machine pc-i440fx-2.6
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs at efi with virtio-net memory hotplug
Status in QEMU:
New
Bug descr
Public bug reported:
with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled
and it has a virtio-net devices
the ovmf images where compiled from https://github.com/tianocore/edk2
(current master)
reproducer:
qemu-system-x86_64 -drive
'if=pflash,unit=0,format=raw,readonly,file=./O
Public bug reported:
there is an inconsistency in how qemu creates qcow2 files, which causes
an error in the gluster (and possibly other block drivers)
the problem is that the gluster backend expects the filesize to be 512
byte aligned, which is not the case anymore since 2.7.0 when using the
fil
11 matches
Mail list logo
