Jiri Denemark 98b7c37d37 cpu: Avoid adding <vendor> to custom CPUs
Guest CPU definitions with mode='custom' and missing <vendor> are
expected to run on a host CPU from any vendor as long as the required
CPU model can be used as a guest CPU on the host. But even though no CPU
vendor was explicitly requested we would sometimes force it due to a bug
in virCPUUpdate and virCPUTranslate.

The bug would effectively forbid cross vendor migrations even if they
were previously working just fine.

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-11-15 15:49:16 +01:00
..
2016-03-18 17:29:53 +01:00
2016-09-14 13:18:07 +02:00
2016-03-18 17:29:53 +01:00
2016-05-14 09:19:51 +02:00
2016-05-02 07:18:25 +02:00
2016-06-14 08:25:25 +02:00
2016-05-20 17:16:21 +02:00
2016-05-20 17:16:21 +02:00
2016-05-20 17:16:21 +02:00
2016-09-14 13:18:07 +02:00
2016-08-24 17:43:29 +02:00
2016-05-02 07:18:25 +02:00