Lines Matching full:have

7 When we do migration, we have two QEMU processes: the source and the
12 There are two things that are different, but they have very similar
36 I am going to list the number of combinations that we can have.  Let's
43   This have to work, and if it doesn't work it is a bug.
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
62   both sides are the same QEMU and both sides have exactly the same
72 because we have the limitation than qemu-5.1 doesn't know pc-5.2.  So
94 we have a problem when we try to migrate between different QEMU
120 hw_compat_X_Y is an array of registers that have the format:
134 queues to a device that have only one queue, we don't know where to
140 has 4, and we have 3 queues that are not properly initialized and
163 And now the other interesting case, case 3.  In this case we have:
167     Here we have the same QEMU in both sides.  So it doesn't matter a
168     lot if we have set the number of queues to 1 or not, because
211 machine types to have the right value::
224 just to make the things easier.  But we have a device that has
227 devices have different features, whatever.
230 "theoretically" easy.  You have to get the features that the device
252 Let's say that we have:
276 When both hosts have different cpu features this is guaranteed to
283 B have the following features:
308 Other devices have worse control about individual features.  If they
312 In this section we have considered that we are using the same QEMU
314 versions process, then we need to have into account all other
317 How to mitigate when we have a backward compatibility error
322 it.  The problem is what happens when we detect after we have done a
511 In the second migration, the source is not qemu-8.0, but we still have
512 that "problem" and have that property enabled.  Notice that we need to
513 continue having this mark/property until we have this machine