[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654271
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654271
Title:
host machine freezes
To manage notifications about this bug go to:
Hi, that stepping shouldn't be important but thanks for checking.
I tried to find a few avx/fma test programs, but I only found super
small ones and none triggered anything like your freeze.
Since you have currently the only setup to trigger this, if you can you
could try the far newer
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654271
Title:
host machine freezes
To manage notifications about this bug go to:
The difference between host-passthrough and host-model (Haswell) was confirmed
by Linux CPUinfo, but there was a difference.
Cpu family and model are the same, stepping is 3-> 1, flag is arch_perfmon,
tsc_adjust is not host-model.
AV2 and FMA are also valid in the CPU model of host-passthrough
So as far as I understand, when you take avx2/fma away from the guest
things work, but if you keep them enabled (via cpu model) it fails?
Generally those features should be supported, to most of it they are
just processor features and passed through.
By Default I think avx2 is passed but fma is
Moving this to the Ubuntu-qemu bug tracker since you're apparently using
Ubuntu's QEMU, not the upstream QEMU.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
