summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/debug/1736042
blob: 655d989060b2e6328518a3cd7c0cbdaebcf6345f (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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
debug: 0.899
x86: 0.856
user-level: 0.818
graphic: 0.809
performance: 0.794
semantic: 0.715
mistranslation: 0.678
KVM: 0.655
architecture: 0.591
boot: 0.516
device: 0.508
ppc: 0.501
files: 0.498
register: 0.371
permissions: 0.349
hypervisor: 0.335
kernel: 0.334
network: 0.329
i386: 0.315
socket: 0.280
PID: 0.262
virtual: 0.256
risc-v: 0.234
VMM: 0.232
peripherals: 0.220
vnc: 0.213
TCG: 0.205
arm: 0.180
assembly: 0.149

qemu-system-x86_64 does not boot image reliably

Booting image as root user with following command works randomly.

./qemu-system-x86_64 -enable-kvm -curses -smp cpus=4 -m 8192 /root/ructfe2917_g.qcow2

Most of the time it ends up on "800x600 Graphic mode"(been stuck there even for 4 hours before killed), but 1 out of ~20 it boots image correctly(and instantly).

This is visible in v2.5.0 build from sources, v2.5.0 from Ubuntu Xenial and v2.1.2 from Debian Jessie.

The image in question was converted from vmdk using:

qemu-img convert -O qcow2 file.vmdk file.qcow2

The image contains Ubuntu with grub.

I can provide debug logs, but will need guidance how to enable them(and what logs are necessary).

As a side note, it seems that booting is more certain after connecting(or mounting) partition using qemu-nbd/mount.

Please always use the latest version of QEMU (currently v2.10, soon v2.11) when reporting bugs to the upstream QEMU project - we don't support old versions like v2.5 any more. So I guess you wanted to report a bug agains v2.5 in Ubuntu instead and I changed the target of this bug accordingly.

I want a fix ;) and I do expect qemu to get it faster then Ubuntu.
So I set up Ubuntu Zesty(to fullfill dependencies) and build qemu:
QEMU emulator version 2.10.1 (v2.10.1-dirty)
and... it's still there.

Can you tell me how and what logs to provide?

And it still happens on:

QEMU emulator version 2.10.93 (v2.11.0-rc3-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

This looks not a QEMU bug to me. You may drop "-curses" first, and run again. Once get inside, change grub file(/etc/default/grub) by uncomment GRUB_TERMINAL=console. It should work then. If still not, then blacklist vga16fb and add "fbcon=map:99 text" in grub command line. Remember to run update-grub after change configure file.

Have you ever tried the suggestions from Liang Yan ?

[Expired for QEMU because there has been no activity for 60 days.]