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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
|
risc-v: 0.892
register: 0.882
user-level: 0.877
virtual: 0.875
x86: 0.874
hypervisor: 0.872
boot: 0.870
mistranslation: 0.866
debug: 0.851
device: 0.850
KVM: 0.847
peripherals: 0.847
arm: 0.839
graphic: 0.838
architecture: 0.836
PID: 0.835
assembly: 0.832
performance: 0.831
network: 0.828
semantic: 0.828
TCG: 0.822
vnc: 0.812
socket: 0.810
ppc: 0.809
kernel: 0.808
VMM: 0.803
permissions: 0.792
i386: 0.777
files: 0.754
Qemu scrambles order of eth devices in vm
HV = 12.04 LTS plus libvirt 1.0x
VM = 12.04 LTS
On the HV there are 12 eth interfaces which we make available to the VM. We have 4 10G virtual function interfaces, and 8 1G conventionally bridged interfaces. No matter what order we present the interfaces in the xml file, they come up in eth0-eth11 order on the VM as follows: ( the interfcaes do work, once you figure out which is which)
eth0-eth7 not in order as compoared to the bridges on the HV (interfaces file) or compared to the xml file for the VM, or compared to the bus numbers. MAC addresses are random.
eth8-eth11 show up in the VM in order of PCU bus numbers just as you'd expect, always after the bridged interfaces.
Consulting the libvirt mailing list, the developer says they present the list in bus order to qemu, but qemu scrambles that order. That appears to me too, to be the case.
There is really no such concept as "NIC order" at the hardware level in QEMU. NIC naming order is something that operating systems invent according to some policy they have. As far as libvirt & QEMU are concerned, you only have control over the PCI device slot numbering. The operating system may choose to number NICs based on their PCI device slot number, or something else entirely. Further after an OS has been booted once, they often record the original mapping of MAC <-> NIC names, so even if you change the PCI slot ordering on later boots, the naming won't change.
Thank you Daniel.
I understand what you say and agree. However when presented with a mapping and an order by libvirt, shouldn't the order be preserved by default? If the OS scrambles it, then fine, not your problem...
Are we on the right track here, is there some way to control the order as presented by Qemu when the VM's OS boots?
If its at all helpful to understand the issue, here is our current proposed workaround:
=start 32 fresh VMs, each with 8 bridged connections and 4 82599 virtual connections=
take one generic xml file
qemu-img one default disk image
examine the HV's lspci output to find out bus numbering for the 82599 virtuals
add correct bus numbering in xml file
virsh create the xml to get randomized MAC addresses ( better ways to do this...)
save xml again
shutdown VM
> heres where the workaround occurs <
mount VM
write to /etc/udev/rules.d file to capture MAC vs PCI numbering in order of presentation for booting
etc etc
For the benefit of 1) others and 2) me when I forget how this works-
I did find a solution in formatting the xml file.
If you leave the vnets out completely, see file below, the generic xml file will cooperate with libvirt and qemu and
order the VM's eth devices as they are ordered on the hypervisor.
(note: the macvtap entries seen below may also not be needed, sound and usb not tested)
## sample xml file for libvirt 1.0.0 showing some bridges and some SRIOV ports too ##
<domain type='kvm' id='1'>
<name>sample</name>
<hostname>sample</hostname>
<memory unit='KiB'>524288</memory>
<currentMemory unit='KiB'>524288</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='x86_64' machine='pc-1.0'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/libvirt/images/oa4-vm-sample-cli.qcow2'/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
<controller type='usb' index='0'>
<alias name='usb0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<interface type='bridge'>
<source bridge='br4'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br5'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br6'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br7'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br8'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br9'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br10'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br11'/>
<model type='virtio'/>
</interface>
<interface type='bridge'>
<source bridge='br250'/>
<model type='virtio'/>
</interface>
<interface type='hostdev'>
<source dev='eth0' mode='vepa'>
<address type='pci' domain='0x0000' bus='0x02' slot='0x10' function='0x0'/>
</source>
<target dev='macvtap1'/>
<model type='virtio'/>
</interface>
<interface type='hostdev'>
<source dev='eth1' mode='vepa'>
<address type='pci' domain='0x0000' bus='0x02' slot='0x10' function='0x1'/>
</source>
<target dev='macvtap1'/>
<model type='virtio'/>
</interface>
<interface type='hostdev'>
<source dev='eth2' mode='vepa'>
<address type='pci' domain='0x0000' bus='0x16' slot='0x10' function='0x0'/>
</source>
<target dev='macvtap0'/>
</interface>
<interface type='hostdev'>
<source dev='eth3' mode='vepa'>
<address type='pci' domain='0x0000' bus='0x16' slot='0x10' function='0x1'/>
</source>
<target dev='macvtap0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/1'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<sound model='ich6'>
<alias name='sound0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</sound>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</memballoon>
</devices>
<seclabel type='none'/>
</domain>
On 12/12/2012 11:59 AM, john fisher wrote:
>
> Are we on the right track here, is there some way to control the order
> as presented by Qemu when the VM's OS boots?
>
--
John Fisher
Is there still something left to do here, or could we close this bug nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|