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
123
124
125
126
|
peripherals: 0.945
permissions: 0.945
graphic: 0.937
TCG: 0.933
semantic: 0.916
vnc: 0.910
register: 0.910
assembly: 0.897
device: 0.879
arm: 0.867
ppc: 0.863
debug: 0.862
PID: 0.859
user-level: 0.857
hypervisor: 0.851
VMM: 0.850
mistranslation: 0.847
virtual: 0.840
socket: 0.833
boot: 0.820
network: 0.817
risc-v: 0.815
architecture: 0.803
performance: 0.795
files: 0.790
x86: 0.780
KVM: 0.774
kernel: 0.666
i386: 0.646
Cisco NX-OSv 9k crashes during boot with qemu 2.10.1(Debian 1:2.10.0+dfsg-2) and ovmf 0~20161202.7bbe0b3e-1
Ubuntu 17.04
qemu 2.10.1(Debian 1:2.10.0+dfsg-2)
gns3 2.0.3
NX-OSv 9k 7.0.3.I6.1
- No such issue with previous qemu 2.8.x
- the issue does not seem to come from the debian packaging
- the issue does not seem to come from GNS3 either, as confirmed by Jeremy Grossmann at https://github.com/GNS3/gns3-server/issues/1193#issuecomment-344240460
Either some parameters usage have changed (for instance -bios) (which would make qemu not backwards compatible) or there is an issue with qemu itself.
The configuration parameters are:
```
"compute_id": "local",
"console": 2010,
"console_type": "telnet",
"first_port_name": "mgmt0",
"height": 48,
"label": {
"rotation": 0,
"style": "font-family: TypeWriter;font-size: 10.0;font-weight: bold;fill: #000000;fill-opacity: 1.0;",
"text": "NX_OSv_9k_Spine_31",
"x": -54,
"y": -25
},
"name": "NX_OSv_9k_Spine_31",
"node_id": "8d01119a-0adc-41bc-950b-c5639db7708c",
"node_type": "qemu",
"port_name_format": "Ethernet1/{port1}",
"port_segment_size": 0,
"properties": {
"acpi_shutdown": false,
"adapter_type": "e1000",
"adapters": 10,
"bios_image": "",
"bios_image_md5sum": null,
"boot_priority": "c",
"cdrom_image": "",
"cdrom_image_md5sum": null,
"cpu_throttling": 0,
"cpus": 2,
"hda_disk_image": "NX-OSv-9k-7.0.3.I6.1.free.qcow2",
"hda_disk_image_md5sum": "18bb991b814a508d1190575f99deed99",
"hda_disk_interface": "ide",
"hdb_disk_image": "",
"hdb_disk_image_md5sum": null,
"hdb_disk_interface": "ide",
"hdc_disk_image": "",
"hdc_disk_image_md5sum": null,
"hdc_disk_interface": "ide",
"hdd_disk_image": "",
"hdd_disk_image_md5sum": null,
"hdd_disk_interface": "ide",
"initrd": "",
"initrd_md5sum": null,
"kernel_command_line": "",
"kernel_image": "",
"kernel_image_md5sum": null,
"legacy_networking": false,
"mac_address": "00:07:00:03:16:01",
"options": "-nographic -enable-kvm -cpu host -machine q35 -smp cpus=2 -bios /usr/share/ovmf/OVMF.fd",
"platform": "x86_64",
"process_priority": "normal",
"qemu_path": "/usr/bin/qemu-system-x86_64",
"ram": 6144,
"usage": ""
```
The logs are:
- [execution log](https://github.com/GNS3/gns3-server/files/1381651/qemu.log.txt)
- [terminal log](https://github.com/GNS3/gns3-server/files/1381660/terminal.log.txt)
With the latest qemu, I can boot:
- Cisco IOSv 15.6(2)T
- Cisco IOSv-L2 15.2(20170321:233949)
- Cisco CSR 1000v 16.5.1b
- Cisco ASAv 9.6(2)
The major difference with NX-OSv 9k is the bios parameter: ```-bios /usr/share/ovmf/OVMF.fd```:
```
ll /usr/share/ovmf/OVMF.fd
-rw-r--r-- 1 root root 2097152 Dec 9 2016 /usr/share/ovmf/OVMF.fd
```
A normal boot log with qemu 2.8.1 is available [here](https://github.com/GNS3/gns3-server/files/1381729/terminal.log.2.8.txt)
Highlighting the differences: qemu 2.8.1 on the left, qemu 2.10.1 on the right hand side with the same boot parameters
Actually, this issue is solved with a fresher ovmf package than the one shipped by default with Ubuntu 17.04 (0~20161202.7bbe0b3e-1).
This issue should be closed.
Closing, according to the previous comment.
|