https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Andriy Gapon changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #19 from mainl...@apeiron.net ---
I've attached a patch that fixes this regression in bug #213155.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Mateusz Piotrowski changed:
What|Removed |Added
CC||mpp...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #17 from Cameron ---
I've managed to work around this.
There's 2 issues here:
1. Rather than using an Opteron_* model in kvm for the CPU, etc. Use kvm64.
Others may work as well. I believe this alone will Just Work if you have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
mainl...@apeiron.net changed:
What|Removed |Added
CC||mainl...@apeiron.net
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #15 from Abi ---
Affecting me too. Started since pfsense 2.4 uses FreeBSD 11
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
fbsdbug...@omni.poc.net changed:
What|Removed |Added
CC||fbsdbug...@omni.poc.net
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
tsuroer...@gmail.com changed:
What|Removed |Added
CC||tsuroer...@gmail.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #12 from Lex van Roon ---
I am also experiencing these issues with a non-UEFI based system. Motherboard:
Asus M5A99X EVO, CPU: AMD FX-8120
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #11 from Cameron ---
I have a non-UEFI BIOS with a Supermicro H8DG6-F motherboard and dual 6348
CPU's. This issue doesn't appear to be UEFI related.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #10 from Miguel Castellanos ---
I tried directly on the hardware as requested.
FreeBSD-11.RELEASE booted correctly under the physical hardware, but fails to
boot as guest on a qemu virtual machine under KVM (Centos 7.2) on the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Luciano Mannucci changed:
What|Removed |Added
CC||luci...@vespaperitivo.it
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #8 from Cameron ---
Can anyone try booting FreeBSD 11.0 directly on the hardware? Unfortunately,
I'm unable to. This may not be KVM related.
I also tried 11-STABLE around a week back, the issue is still present there.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Miguel Castellanos changed:
What|Removed |Added
CC||miguelcastellanos@hotmail.e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #6 from Cameron ---
To clarify my comment, using Opteron_G5 or Opteron_G4 causes boot to hang with
FreeBSD 11.0-p6. Using Opteron_G3 works.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Cameron changed:
What|Removed |Added
CC||c...@neo-zeon.de
--- Comment #5 from Cam
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #4 from Lex van Roon ---
I can confirm that by switching the hypervisor to Opteron_G3 I've got a working
FreeBSD 11.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #3 from Andrew Keling ---
Should note that this corrected my issue upgrading my servers from 10.3 to 11.
I was also seeing issue with the install cd locking up too.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
--- Comment #2 from Andrew Keling ---
Found a work around. Seems to be an issue with copying the the host CPU
topology and with the Opteron_G4 CPU arch too.
Switching to Opteron_G3 or selecting Hypervisor_Default seems to mitigate this
iss
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Andrew Keling changed:
What|Removed |Added
CC||akell...@gmail.com
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Mark Linimon changed:
What|Removed |Added
CC|freebsd-am...@freebsd.org |
Assignee|freebsd-b...@fr
22 matches
Mail list logo
