Lines Matching full:it
43 This have to work, and if it doesn't work it is a bug.
60 It needs to use the definition of pc-5.1 and the devices as they
70 Now it comes the interesting ones, when both QEMU processes are
80 qemu-5.1 to understand whatever qemu-5.2 decides to change, so it is
98 pc-5.1, it needs to **not** use the feature, to be able to migrate to
102 qemu-5.2 has to expect that it is not going to get data for the new
103 feature, because qemu-5.1 doesn't know about it.
110 that array to see what value it needs to get for that feature. And
115 macros that exist. With it, we set the default value for that
116 property, and that is what it is going to get in the latest released
129 change that is not backward compatible. In qemu-5.1 it has one
130 queue. In qemu-5.2 it has the same number of queues as the number of
144 that when it is running pc-5.1, it needs to set the number of queues
167 Here we have the same QEMU in both sides. So it doesn't matter a
186 care because we haven't started the guest in qemu-5.2, it came
190 Now, how was this done in reality? The following commit shows how it
210 It changes the default value of num_queues. But it fishes it for old
241 That said, actually doing it is complicated. Almost all devices are
262 If we try to migrate without any care from host A to host B, it will
264 destination, it will find that the hardware is not there.
278 has less features than host B, sometimes it works. Important word of
300 And you would be able to migrate between them. It is responsibility
305 Notice that we don't recommend to use -cpu host for migration. It is
306 used in this example because it makes the example simpler.
310 the device needs a way to configure which ones it is going to use.
322 it. The problem is what happens when we detect after we have done a
325 Let see how it worked with one example.
409 of breakage happens, but in this case it is quite simple::
435 I.e. If the property bit is enabled, we configure it as we did for
436 qemu-8.0. If the property bit is not set, we configure it as it was in 7.2.
490 So, if we start a pc-7.2 machine in qemu-8.0 we can't migrate it to
505 property for pc-7.2. Notice that we need to remember, it is not
514 rebooted. But it is not a normal reboot (that don't reload QEMU) we