summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/device/613529
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/gemma3:12b/device/613529')
-rw-r--r--results/classifier/gemma3:12b/device/61352914
1 files changed, 14 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/613529 b/results/classifier/gemma3:12b/device/613529
new file mode 100644
index 000000000..d6c2b8162
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/613529
@@ -0,0 +1,14 @@
+
+qemu does not accept regular disk geometry
+
+Hi, 
+
+I am currently hunting a strange bug in qemu/kvm:
+
+I am using an lvm logical volume as a virtual hard disk for a virtual machine. 
+
+I use fdisk or parted to create a partition table and partitions, kpartx to generate the device entries for the partitions, then install linux on ext3/ext4 with grub or msdos filesystem with syslinux. 
+
+But then, in most cases even the boot process fails or behaves strangely, sometimes even mounting the file system in the virtual machine fails. It seems as if there is a problem with the virtual disk geometry. The problem does not seem to occur if I reboot the host system after creating the partition table on the logical volume. I guess the linux kernel needs to learn the disk geometry by reboot. A blkdev --rereadpt does not work on lvm volumes. 
+
+The first approach to test/fix the problem would be to pass the disk geometry to qemu/lvm with the -drive option. Unfortunately, qemu/kvm does not accept the default geometry with 255 heads and 63 sectors. Seems to limit the number of heads to 16, thus limiting the disk size.
\ No newline at end of file