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
|
other: 0.884
permissions: 0.881
semantic: 0.838
debug: 0.814
performance: 0.775
vnc: 0.760
network: 0.749
graphic: 0.747
socket: 0.746
KVM: 0.744
device: 0.716
boot: 0.702
PID: 0.689
files: 0.663
kvm crash when writing on disk
When running the following command:
/usr/bin/kvm -S -M pc-1.0 -cpu qemu32 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name winxp -uuid f86ef88f-b90e-699a-74b8-9675063fc26e -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device lsi,id=scsi0,bus=pci.0,addr=0x4 -drive file=/home/master/xpnew.iso,if=none,media=cdrom,id=drive-ide0-0-0,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/var/lib/zentyal/machines/winxp/winxp.img,if=none,id=drive-scsi0-0-0,format=qcow2 -device scsi-disk,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0 -netdev tap,fd=18,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=b3:b8:a9:49:a2:f8,bus=pci.0,addr=0x3 -usb -device usb-mouse,id=input0 -vnc 0.0.0.0:0,password -k de -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
running a windows installation (for instance, it has crashed with other OS), when the guest OS installer has reached 60% of the copying files process, the following errors can be found, and KVM gets Force Closed (i am recollecting errors from different times I have tried to references to memory positions may vary)
syslog:
Nov 26 19:46:59 mikeboxx kernel: [2254718.689953] kvm6983 general protection ip:7fc451d4be08 sp:7fc44991ab80 error:0 in libc-2.15.so[7fc451ccd000+1b5000]
/var/log/libvirt/libvirtd.log:
2012-11-21 10:01:26.464+0000: 16050: error : qemuMonitorIO:603 : internal error End of file from monitor
/var/log/libvirt/qemu/winxp-ajur.log
**enclosed as it has a long size due to the core dump
The linux kernel running is this one:
3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Libvirtd versions are these:
root@mikeboxx:/home/ebox-remote-support# dpkg -l | grep libvirt
ii libvirt-bin 0.9.8-2ubuntu17.4 programs for the libvirt library
ii libvirt0 0.9.8-2ubuntu17.4 library for interfacing with different virtualization systems
and KVM - QEMU versions are these ones:
root@mikeboxx:/home/ebox-remote-support# dpkg -l | grep qemu
ii qemu-common 1.0+noroms-0ubuntu14.3 qemu common functionality (bios, documentation, etc)
ii qemu-kvm 1.0+noroms-0ubuntu14.3 Full virtualization on i386 and amd64 hardware
ii qemu-utils 1.0+noroms-0ubuntu14.3 qemu utilities
I have checked bug #1022901 in https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1022901 due to the similarity of the error "internal error End of file from monitor", but the sintoms are not the same as long as the partition where the img file resides has plenty of space and so does the img itself:
root@mikeboxx:/home/ebox-remote-support# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 226G 3.4G 211G 2% /
root@mikeboxx:/home/ebox-remote-support# qemu-img info /var/lib/zentyal/machines/winxp/winxp.img
image: /var/lib/zentyal/machines/winxp/winxp.img
file format: qcow2
virtual size: 11G (11559501824 bytes)
disk size: 384M
cluster_size: 65536
Can you help us to solve this? Case you needed any information else, please do not hesitate to ask for it
On Wed, Dec 12, 2012 at 10:19:06AM -0000, xavy wrote:
> Public bug reported:
>
> When running the following command:
>
> /usr/bin/kvm -S -M pc-1.0 -cpu qemu32 -enable-kvm -m 1024 -smp
> 1,sockets=1,cores=1,threads=1 -name winxp -uuid f86ef88f-b90e-699a-
> 74b8-9675063fc26e -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-
> shutdown -device lsi,id=scsi0,bus=pci.0,addr=0x4 -drive
I'm afraid the emulated LSI SCSI adapter has known issues and doesn't
seem to be under active development.
Use IDE for compatibility or virtio-blk if you're willing to install the
virtio-win guest drivers. There is also SATA (AHCI) and MegaSAS SCSI
support if you don't want to use IDE/virtio-blk.
Stefan
Running it with ide solved the FC.
Thanks for the comments Stefan ;)
Closing according to comment #2 and #3
|