Lines Matching full:but

12 There are two things that are different, but they have very similar
34 device feature exposure.  But that is not relevant for this section.
47   Exactly the same case than the previous one, but for 5.1.
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
55 the latest machine type for that version (pc-5.2) but one of an older
61   were configured on 5.1, but this should be easy in the sense that
90 compatibility problems.  But the reason that we create qemu-5.2 is to
117 version.  But if we want a different value for a previous version, we
139 to qemu-5.2, we only sent information for one queue, but destination
185     migration B -> C is case 3, so we don't care.  But actually we
210 It changes the default value of num_queues.  But it fishes it for old
224 just to make the things easier.  But we have a device that has
321 development.  But as soon as we find that there is a problem, we fix
375 The patch changes how we configure PCI space for AER.  But QEMU fails
409 of breakage happens, but in this case it is quite simple::
484 But now we found that qemu-8.0 neither can migrate to qemu-7.2 not
511 In the second migration, the source is not qemu-8.0, but we still have
514 rebooted.  But it is not a normal reboot (that don't reload QEMU) we