https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable10+,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #42 from Andriy Gapon ---
*** Bug 215377 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #41 from Adam Jimerson ---
Sorry didn't realize this was still only on the STABLE branch. As my host is
currently on RELEASE branch I probably won't get the patch until 11.2.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Anish Gupta changed:
What|Removed |Added
CC||an...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Adam Jimerson changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Andriy Gapon changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #38 from commit-h...@freebsd.org ---
A commit references this bug:
Author: avg
Date: Thu Feb 15 17:10:42 UTC 2018
New revision: 329321
URL: https://svnweb.freebsd.org/changeset/base/329321
Log:
MFC r328622: vmm/svm: post
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #37 from commit-h...@freebsd.org ---
A commit references this bug:
Author: avg
Date: Thu Feb 15 17:09:48 UTC 2018
New revision: 329320
URL: https://svnweb.freebsd.org/changeset/base/329320
Log:
MFC r328622: vmm/svm: post
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #36 from Nils Beyer ---
(In reply to Nils Beyer from comment #35)
sorry guys; please forget my last comment. Didn't see that MFC note...
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #35 from Nils Beyer ---
thank you very much. Any chance to get that in 11-STABLE as well?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Andriy Gapon changed:
What|Removed |Added
Status|Open|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #33 from commit-h...@freebsd.org ---
A commit references this bug:
Author: avg
Date: Wed Jan 31 11:14:26 UTC 2018
New revision: 328622
URL: https://svnweb.freebsd.org/changeset/base/328622
Log:
vmm/svm: post LAPIC interrupts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #32 from Nils Beyer ---
(In reply to Andriy Gapon from comment #30)
well, performance-wise I did a Cinebench R15 (RC184115DEMO) benchmark (CPU)
under Windows 10 (latest release) with both patch variants - here
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #31 from Peter Grehan ---
Please check in D13780 - I much prefer that one unless the later version can be
shown to have better performance.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #30 from Andriy Gapon ---
(In reply to Nils Beyer from comment #29)
I still cannot decide between D13780 and D13828.
I have given some light testing to both, both seem to work.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #29 from Nils Beyer ---
(In reply to Andriy Gapon from comment #27)
thanks, with that patch (D13780), I also am able to use multiple vCPUs at every
stage of Windows pleasure.
When will it go upstream?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #28 from Andriy Gapon ---
And an alternative proposal: https://reviews.freebsd.org/D13828
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Andriy Gapon changed:
What|Removed |Added
Status|New |Open
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #26 from Andriy Gapon ---
Created attachment 189559
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189559=edit
ktr capture of the problem
I am able to reproduce the problem with a FreeBSD guest on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #25 from mik...@georgsen.dk ---
(In reply to Peter Grehan from comment #24)
OPNsense-17.7.5-OpenSSL-dvd-amd64.iso
pfSense-CE-2.4.2-RELEASE-amd64.iso
Latest FreeNAS 11.1
2,4,8 vCPU
4,8 vRAM
Threadripper 1950X
MSI X399 GAMING
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #24 from Peter Grehan ---
Yes, much easier with a FreeBSD (-based) guest. Some config questions - what
version of pfsense/Opnsense, how many guest vCPUs, and what's the AMD h/w setup
?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
mik...@georgsen.dk changed:
What|Removed |Added
CC||mik...@georgsen.dk
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
domhau...@gmail.com changed:
What|Removed |Added
CC||domhau...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #21 from Peter Grehan ---
(In reply to dgilbert from comment #20)
Sorry, didn't know that was you.
There are 2 other things to try here:
- when the guest is hung, on the host issue
bhyvectl --get-rip
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #20 from dgilb...@eicat.ca ---
(In reply to Peter Grehan from comment #19)
You asked me this in email on the list. I replied that this didn't seem to have
any effect... Ie: it still hung.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #19 from Peter Grehan ---
(In reply to dgilbert from comment #18)
Would you be able to try your same test, but with the guest vCPUs pinned ? e.g.
add the following bhyve parameters
-p 0:1 -p 1:2 -p 2:3 -p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
dgilb...@eicat.ca changed:
What|Removed |Added
CC||dgilb...@eicat.ca
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #17 from Nils Beyer ---
(In reply to Peter Grehan from comment #16)
cool, thanks...
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #16 from Peter Grehan ---
I've been working with Anish to narrow down the problem seen on the Ryzen with
a FreeBSD guest. We are making (slow) progress on this.
>AMD SVM is not production-ready, yet, is it?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #15 from Nils Beyer ---
(In reply to Peter Grehan from comment #11)
Peter, do you have any news regarding that issue? The guest freezes still
happen on 11.1-RELEASE. Sometimes the Windows 10 guest boots, I can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #14 from Peter Grehan ---
>bhyve_net_type e1000
The lockup you are seeing is unrelated to the AMD one, and is a known one with
the e1000 under Windows.
I've created 218715 to track
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
jes...@monsted.dk changed:
What|Removed |Added
CC||jes...@monsted.dk
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #12 from Nils Beyer ---
I had this vCPU lock-up behaviour on a "Phenom II X6 1055T", too. So it seems
that the desktop lines of AMD CPUs are generally unsupported in bhyve's SVM
implementation.
Ok, while
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #11 from Peter Grehan ---
It's ddb from within the guest. The signature is:
1 vCPU will panic with a lock-spin timeout:
CPU 11, panic spin lock 0x81ea0480 (smp rendezvous) held by
0xf800079da000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #10 from Nils Beyer ---
Peter Grehan wrote in comment #9:
> However, I can repro this doing a FreeBSD buildworld with >= 12 vCPUs. It
> takes
> a lot longer (~20 mins) but seems to be reliable. Backtraces in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #9 from Peter Grehan ---
Insta-repro for me on a Ryzen 1700. Happens almost immediately on install with
>= 2 vCPUs, and the more configured, the faster the freeze. Single vCPU install
is reliable, and I've
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #7 from ajsc...@hotmail.com ---
(In reply to Peter Grehan from comment #6)
I did it almost the same way only Virtio driver and tried 2 and 4 cpu's
Also added hw.vmm.topology.cores_per_package="4" to /boot/loader.conf
I have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #6 from Peter Grehan ---
I didn't add the virtio driver - maybe that was what did it. Also, I'm
installing on an Opteron 6320.
The process was, with 1 vCPU
install
- reboot
2nd phase
- reboot
final phase
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #5 from ajsc...@hotmail.com ---
(In reply to Peter Grehan from comment #4)
I did that.
1 cpu:
- Install
Reboot
- Setup Windows
Reboot
-Install Virtio driver
Reboot
When everything was setup booted with 2 vcpu's
But then the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #4 from Peter Grehan ---
You have to wait until the install is complete (i.e. the 3rd reboot, where you
enter username etc). At that point, you should be able to power off and then
restart with > 1 vCPU.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
--- Comment #3 from ajsc...@hotmail.com ---
(In reply to Peter Grehan from comment #2)
I tried after install to start with 2 cpu's but it hangs in start screen of
windows 10 x64
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Peter Grehan changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-standards@FreeBSD.o
44 matches
Mail list logo