Has this bug been fixed in 3.13.0-44.73?
I recently upgraded some of our precise compute nodes(Dell C6145 AMD Opteron(tm) Processor 6376) to trusty, with the latest kernel 3.13.0-45-generic #74-Ubuntu, but still seeing this kernel panic in vm's console log.
Using libvirt_cpu_mode=host-model can fix it, but good to know if this bug still in the latest kernel?
Has this bug been fixed in 3.13.0-44.73?
I recently upgraded some of our precise compute nodes(Dell C6145 AMD Opteron(tm) Processor 6376) to trusty, with the latest kernel 3.13.0-45-generic #74-Ubuntu, but still seeing this kernel panic in vm's console log.
Using libvirt_ cpu_mode= host-model can fix it, but good to know if this bug still in the latest kernel?
Thanks,