blob: ef0581525e6a84d3caac1b32c7d47bc38c746b00 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
virtual: 0.937
device: 0.786
user-level: 0.714
boot: 0.712
mistranslation: 0.706
architecture: 0.681
performance: 0.666
semantic: 0.661
graphic: 0.647
files: 0.646
PID: 0.640
register: 0.631
socket: 0.585
permissions: 0.562
vnc: 0.557
kernel: 0.536
risc-v: 0.516
ppc: 0.513
VMM: 0.471
network: 0.460
i386: 0.424
x86: 0.402
hypervisor: 0.394
peripherals: 0.328
TCG: 0.326
arm: 0.322
assembly: 0.311
KVM: 0.307
debug: 0.141
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.
Seems to be the same issue as in
http://qemu-forum.ipi.fi/viewtopic.php?f=4&t=5218
has been (orally) confirmed by other users.
It is effectively impossible to reliably install a system on an lvm logical device and run it under kvm/qemu
Which version of QEMU have you been using for your tests? Can you still reproduce this problem with the latest version of QEMU?
[Expired for QEMU because there has been no activity for 60 days.]
|