diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/hypervisor/2102 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/2102')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/2102 | 41 |
1 files changed, 0 insertions, 41 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/2102 b/results/classifier/deepseek-2-tmp/output/hypervisor/2102 deleted file mode 100644 index 417c8d0a..00000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/2102 +++ /dev/null @@ -1,41 +0,0 @@ - -"qemu-img resize -f qcow2" produces broken disk images -Description of problem: -The documentation of `qemu-img` at -<https://www.qemu.org/docs/master/tools/qemu-img.html> -makes it sound like `qemu-img resize` supports various image formats -(raw, qcow2, etc.) in the same way. - -But it doesn't. While `qemu-img resize -f raw` works as expected, -`qemu-img resize -f qcow2` produces broken disk images. -Steps to reproduce: -``` -$ wget http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz -$ gunzip arm64.img -``` - -First resize, then convert: -``` -$ cp arm64.img arm64-rc.img -$ qemu-img resize -f raw arm64-rc.img 10G -$ qemu-img convert -f raw -O qcow2 arm64-rc.img arm64-rc.qcow2 -$ rm -f arm64-rc.img -``` - -First convert, then resize: -``` -$ qemu-img convert -f raw -O qcow2 arm64.img arm64-cr.qcow2 -$ qemu-img resize -f qcow2 arm64-cr.qcow2 10G -``` - -Attach to a VM in VirtualBox (as an additional SATA disk) and start that VM. - -arm64-rc.qcow2 => -`# fdisk /dev/sdb` => it has two partitions. - -arm64-cr.qcow2 => -`# fdisk /dev/sdb` => it has no partitions! -And the VM cannot be cleanly shut down. I had to manually kill the VirtualBoxVM -process. -Additional information: - |