The last bios indeed helped. It knows runs under 200ms.
Do you anticipate doing minor release of 3.1.0 with updated bios to address
this issue? Or users are expected to upgrade to QEMU 4.0.0?
Regards,
Waldek
On Thu, May 2, 2019 at 4:05 AM Stefano Garzarella <
1826...@bugs.launchpad.net> wrote:
I tried with the bios
https://github.com/qemu/qemu/blob/v4.0.0/pc-bios/bios-256k.bin and it failed
like so:
```
qemu: could not load PC BIOS 'bios-256k.bin'
qemu failed.
```
Have not had chance to try with QEMU 4 yet.
--
You received this bug notification because you are a member of qemu-
Public bug reported:
Yesterday I have upgraded my laptop from Ubuntu 18.10 to 19.04 and that
way got newer QEMU 3.1.0 along vs QEMU 2.12.0 before. I have noticed
that everytime I start QEMU to run OSv, QEMU seems to hand noticably
longer (~1 second) before showing SeaBIOS output. I have tried all
Bingo! Adding '-S 0' makes convert work. But it is not perfect as the
end result is fully allocated image.
So with qcow2 like this:
image: mysql-example.qemu
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 50M
cluster_size: 65536
Format specific information:
compat: 1.1
I am not familiar with QEMU source code but I might have some cycles to
look into it. Where would I look -
https://github.com/qemu/qemu/blob/master/qemu-img.c? Or somewhere else?
Any suggestions would be appreciated.
--
You received this bug notification because you are a member of qemu-
I have done more tests based on your suggestion and I think it is the
opposite. The problem happens is the source is APFS.
Following failed:
APFS -> ExFAT
APFS -> Fat32
Following worked:
ExFAT -> APFS
FAT32 -> APFS
So for now my workaround is to use USB stick formatted with FAT32 or
ExFAT, copy
Have I provided all necessary data and other details?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1776920
Title:
qemu-img convert on Mac OSX creates corrupt images
Status in QEMU:
New
Bug
Raw image created by dd in steps 1 and 2.
** Attachment added: "image.img"
https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5152722/+files/image.img
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Source file 1
** Attachment added: "lzloader.elf"
https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5152720/+files/lzloader.elf
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1776920
Also if I use the same image.qemu file and convert to vmdk format I get
even smaller file which for sure is wrong as well:
qemu-img convert image.qemu -O vmdk image2.vbox
ll image*
-rw-r--r-- 1 *** *** 6684672 Jun 14 17:17 image.img
-rw-r--r-- 1 *** *** 7012352 Jun 14 17:40 image.qemu
The corrupt qcow2 image created by converting image.qemu in step 4.
** Attachment added: "image2.qemu"
https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5152724/+files/image2.qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Source file 2
** Attachment added: "boot.bin"
https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5152721/+files/boot.bin
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1776920
Title:
Original qcow2 image converted from raw image in step 3.
** Attachment added: "image.qemu"
https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5152723/+files/image.qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I believe I have distilled entire process to few repeatable steps that
can be fully reproduced on my Mac. The binary source files - - boot.bin
and lzloader.elf - were created on my Linux VM running in VirtualBox on
same Mac but I do not think it matters as the execution completely
happens on Mac.
I will provide all necessary info. Unfortunately the smallest image I can
provide is around 10M.
What is M1/M2/M3 L1/L2/L3 file?
Waldek
On Thu, Jun 14, 2018 at 10:46 AM, Christian Ehrhardt <
1776...@bugs.launchpad.net> wrote:
> Can this be done with like a 1M example file that you could
Public bug reported:
An image created by qemu-img create, then modified by another program is
converted to bad/corrupt image when using convert sub command on Mac
OSX. The same convert works on Linux. The version of qemu-img is 2.12.
** Affects: qemu
Importance: Undecided
Status:
16 matches
Mail list logo
