Created attachment 633005 [details] syslog of F18b TC6, it reaches anaconda ok. Description of problem: There is a pause, then anaconda is able to start despite of this error. Version-Release number of selected component (if applicable): F18b TC6 How reproducible: always (same guest) Steps to Reproduce: 1. boot guest Expected results: no error Actual results: call trace
Created attachment 633006 [details] screenshot
Created attachment 633011 [details] kvm guest xml file
Avi, any ideas on this one?
Looks like the guest is trying to use AVX2 instructions, while these are not available. Can you post guest and host /proc/cpuid? Most likely the host exposes AVX2 even though it is not actually available.
Created attachment 653749 [details] cpuinfo HOST (AMD FX6100)
Created attachment 653750 [details] cpuinfo GUEST
Created attachment 653754 [details] cpuinfo GUEST (but FORCED opteronG3) I forced the cpu to OpteronG3 and the issue is gone on F18b. Solaris will issue some cpu errors but it will still boot. It seems that copy_host_cpu and opteronG4 does not work ok. In this guest i had to change the cpu settings from default due to it being to slooow for solaris.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days