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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
risc-v: 0.766
VMM: 0.710
user-level: 0.709
virtual: 0.668
x86: 0.664
vnc: 0.653
debug: 0.646
hypervisor: 0.643
TCG: 0.643
KVM: 0.637
register: 0.630
arm: 0.630
permissions: 0.621
boot: 0.620
performance: 0.620
i386: 0.617
device: 0.617
files: 0.611
semantic: 0.606
assembly: 0.602
ppc: 0.600
peripherals: 0.597
architecture: 0.597
socket: 0.595
PID: 0.591
kernel: 0.582
graphic: 0.574
network: 0.564
mistranslation: 0.551
random IO errors / data corruption in VMs (created and executed via virt-manager)
I have recurring problems with VM installation and usage - data on VM disk gets corrupted at some point and it causes all sorts of problems - sometimes I cannot even install base system, other times some .so files are corrupt after isntallation, etc - totally random.
I use virt-manager to create and run VMs. I have also tried creating VMs via virt-install, result is identical.
If I use VirtualBox I have no such problems.
My OS is Fedora 20 upgraded to 21, qemu and libvirt are installed from Fedora official repos.
Here's an example qemu command-line:
/usr/bin/qemu-system-x86_64
-machine accel=kvm
-name fuel
-S
-machine pc-i440fx-2.1,accel=kvm,usb=off
-cpu SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+movbe,+pcid,+pdcm,+xtpr,+fma,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
-m 3142
-realtime mlock=off
-smp 2,sockets=2,cores=1,threads=1
-uuid 27693a46-7a50-4a3c-bcaf-bf061ba469ed
-no-user-config
-nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/fuel.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control
-rtc base=utc,driftfix=slew
-global kvm-pit.lost_tick_policy=discard
-no-hpet
-no-shutdown
-boot menu=on,strict=on
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2
-device lsi,id=scsi0,bus=pci.0,addr=0xa
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7
-drive file=/home/virtual-disks/fuel.vdi,if=none,id=drive-virtio-disk0,format=vdi
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive file=/home/dsutyagin/Downloads/iso/MirantisOpenStack-6.0.iso,if=none,id=drive-scsi0-0-0,readonly=on,format=raw
-device scsi-cd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=2
-netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:0d:42:2d,bus=pci.0,addr=0x3
-netdev tap,fd=25,id=hostnet1,vhost=on,vhostfd=26
-device virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:a4:8c:ef,bus=pci.0,addr=0x4
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/fuel.org.qemu.guest_agent.0,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel1,name=vdagent
-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0
-device usb-tablet,id=input0
-spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,bus=pci.0,addr=0x5 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0
-chardev spicevmc,id=charredir0,name=usbredir
-device usb-redir,chardev=charredir0,id=redir0
-chardev spicevmc,id=charredir1,name=usbredir
-device usb-redir,chardev=charredir1,id=redir1
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9
-msg timestamp=on
If this is not a bug, I'd be happy if you help me fix this problem. I am sorry if this is not the proper place to post such a problem.
qemu-system-x86_64 --version
QEMU emulator version 2.1.3 (qemu-2.1.3-2.fc21), Copyright (c) 2003-2008 Fabrice Bellard
qemu-kvm --version
QEMU emulator version 2.1.3 (qemu-2.1.3-2.fc21), Copyright (c) 2003-2008 Fabrice Bellard
Can you please retry with current qemu.git master? I suspect that this is a duplicate of https://bugs.launchpad.net/qemu/+bug/1422307 and fixed in commit f0ab6f10 (a bug in the code handling VirtualBox's VDI image format).
In general, running VMs with image formats of other hypervisors is not recommended, both for reliability and performance reasons. You may want to consider using qcow2 or raw instead.
I have tried using qcow2 and the problem does not appear anymore. I guess it was a bug with VDI implementation indeed. Please close the ticket. Thank you very much for your help!
On Fri, Mar 06, 2015 at 06:50:30AM -0000, Dmitry Sutyagin wrote:
> I have recurring problems with VM installation and usage - data on VM disk gets corrupted at some point and it causes all sorts of problems - sometimes I cannot even install base system, other times some .so files are corrupt after isntallation, etc - totally random.
...
> -drive file=/home/virtual-disks/fuel.vdi,if=none,id=drive-virtio-disk0,format=vdi
Hi Dmitry,
A bug that can lead to corruption was recently discovered in the vdi
image format code in QEMU.
The vdi image format code is only designed to work for
importing/exporting image files in qemu-img convert. It is not suitable
for running guests and achieving good I/O performance.
I recommend using raw or qcow2 image files instead.
Stefan
Closing according to comment #2.
|