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
|
boot: 0.878
network: 0.863
PID: 0.764
graphic: 0.739
architecture: 0.704
device: 0.698
socket: 0.670
permissions: 0.665
peripherals: 0.664
mistranslation: 0.652
files: 0.646
virtual: 0.643
user-level: 0.628
debug: 0.603
semantic: 0.599
arm: 0.581
hypervisor: 0.575
performance: 0.546
risc-v: 0.518
kernel: 0.509
ppc: 0.507
vnc: 0.482
register: 0.479
VMM: 0.442
assembly: 0.429
TCG: 0.389
i386: 0.382
x86: 0.377
KVM: 0.274
Using qemu-system-sparc64 no network interface seems to exist
Using boot command:
qemu-system-sparc64 -M niagara -L /home/chrisp/sparc/S10image/ -nographic -m 256 -drive if=pflash,readonly=on,file=/home/chrisp/sparc/S10image/disk.s10hw2
After I log into solaris system I see no network devices other than the loopback device.
All the docs I can see suggest it should come up with a default network device that allows communication via the hosts network. Host is ubuntu 64bit.
root@giant:/home/chrisp/sparc# qemu-system-sparc64 -version
QEMU emulator version 5.0.0
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
dladm show-link
ifconfig -a
ok boot
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Sun-Fire-T2000/ufsboot
Loading: /platform/sun4v/ufsboot
SunOS Release 5.10 Version Generic_118822-23 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: unknown
unknown console login: root
Last login: Wed Feb 8 09:01:28 on console
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
# dladm show-link
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
Unfortunately it's been a while and no one has added the proper support to qemu yet, see comments at:
http://tyom.blogspot.com/2016/10/qemu-sun4vniagara-target-went-public.html
Apparently the niagara PCI adapter has to be implemented and the firmware recompiled to enable it.
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" within the next 60 days (otherwise it will get
closed as "Expired"). We will then eventually migrate the ticket auto-
matically to the new system.
Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|