[Bug 245392] bhyve: PCI passthru built-in rtl8168 to OpenBSD no packets (AMD Ryzen 3 1200)

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392

Kubilay Kocak  changed:

   What|Removed |Added

 Blocks||246647


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647
[Bug 246647] Request Errata Notice (EN) for bug 229852 and bug 245392 in
releng/12.1
-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246647] Request Errata Notice (EN) for bug 229852 and bug 245392 in releng/12.1

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647

Kubilay Kocak  changed:

   What|Removed |Added

 Depends on||245392
   Assignee|ko...@freebsd.org   |r...@freebsd.org
  Flags||maintainer-feedback?(re@Fre
   ||eBSD.org),
   ||maintainer-feedback?(scottl
   ||@FreeBSD.org)
 CC||r...@freebsd.org,
   ||sco...@freebsd.org
Summary|Fix for #229852 still not   |Request Errata Notice (EN)
   |MFCed in 12.1R-P5   |for bug 229852 and bug
   ||245392 in releng/12.1


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392
[Bug 245392] bhyve: PCI passthru built-in rtl8168 to OpenBSD no packets (AMD
Ryzen 3 1200)
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647

Anatoli  changed:

   What|Removed |Added

 Status|Closed  |Open
 Resolution|Not A Bug   |---

--- Comment #3 from Anatoli  ---
I'm reopening this bug report as suggested by Kubilay Kocak as I believe this
bug (together with the #245392) is a show-stopper for production use of bhyve
with pci passthru in some environments (this one on Intel CPUs, the other one
with OpenBSD/NetBSD guests). #245392 was blocking PCI passthru use with other
BSDs for years.

In my particular case I'm deploying an infrastructure with 2 enterprise-grade
servers as bhyve hosts serving dozens of OpenBSD guests and we can't use STABLE
nor can we wait for 6 months more for these fixes to be included in 12.2R (we
already got a considerable delay because of these bugs).

Though maybe it makes sense to combine both bugs in a single EN, when #245392
gets closed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647

Kubilay Kocak  changed:

   What|Removed |Added

   Assignee|virtualizat...@freebsd.org  |ko...@freebsd.org
 Resolution|DUPLICATE   |Not A Bug
 Depends on||229852
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2298
   ||52
 CC||virtualizat...@freebsd.org

--- Comment #2 from Kubilay Kocak  ---
Thank you for the report Anatoli

The commit in base r349184 was indeed merged (MFC'd) to stable/12 in base
r355440 (see bug 229852)

Merges to *stable* branches are scheduled for inclusion in *future* minor
releases.

Only Errata Notices (EN's) and Security Fixes (SA's) are pushed to 
releng" branches, that is to say, included in "current" minor releases  (*.*-pX
releases)

If you would like to request that the resolution for bug 229852 be considered
an EN (Errata Notice), please re-open that issue.

Having said that, given the date of the original fix/merge (over 6 months ago),
and the schedule for future 12.x releases, an EN request is unlikely to be
accepted (in my opinion, I may be wrong).


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852
[Bug 229852] [PATCH] bhyve: IOMMU (Intel VTd) PCI passthrough attempt locks up
some systems
-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 229852] [PATCH] bhyve: IOMMU (Intel VTd) PCI passthrough attempt locks up some systems

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852

Kubilay Kocak  changed:

   What|Removed |Added

   Assignee|virtualizat...@freebsd.org  |sco...@freebsd.org

--- Comment #23 from Kubilay Kocak  ---
^Triage: Assign to committer that resolved

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 229852] [PATCH] bhyve: IOMMU (Intel VTd) PCI passthrough attempt locks up some systems

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852

Kubilay Kocak  changed:

   What|Removed |Added

 Blocks||246647
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2466
   ||47


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647
[Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 245392] bhyve: PCI passthru built-in rtl8168 to OpenBSD no packets (AMD Ryzen 3 1200)

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392

--- Comment #11 from Anatoli  ---
Created attachment 214741
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214741=edit
The patch fixing the problem

The bug can be fixed by applying the attached patch and rebuilding user-space
bhyve.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 245392] bhyve: PCI passthru built-in rtl8168 to OpenBSD no packets (AMD Ryzen 3 1200)

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392

--- Comment #10 from Anatoli  ---
After a lot of triage, Peter Grehan identified the source of the problem and
prepared a patch (attached).

His description of the cause: the problem was that OpenBSD issues 4-byte PCI
configuration-space register reads/writes to consecutive 2-byte fields. In
general this is benign, but it exposed 2 bugs in the bhyve PCI emulation where
this wasn't being handled correctly.

This can be fixed by applying the attached patch and rebuilding user-space
bhyve.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 229852] [PATCH] bhyve: IOMMU (Intel VTd) PCI passthrough attempt locks up some systems

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852

Kubilay Kocak  changed:

   What|Removed |Added

 CC||m...@anatoli.ws

--- Comment #22 from Kubilay Kocak  ---
*** Bug 246647 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |DUPLICATE

--- Comment #1 from Kubilay Kocak  ---


*** This bug has been marked as a duplicate of bug 229852 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647

Bug ID: 246647
   Summary: Fix for #229852 still not MFCed in 12.1R-P5
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bhyve
  Assignee: virtualizat...@freebsd.org
  Reporter: m...@anatoli.ws

A fix for the bug #229852 (bhyve: IOMMU (Intel VTd) PCI passthrough attempt
locks up some systems) was stated as MFCed 6 months ago
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852#c21 and
https://svnweb.freebsd.org/base?view=revision=355440) but it's still
not included in 12.1R-P5.

This is a severe bug crashing the entire system (12.1R) when starting bhyve
with pci passthru.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Low Cost Payroll Service for Charlie's Choice

2020-05-21 Thread Helen Collins

Hi,


My name is Helen and I am with PayrollServices, a service that keeps
small business owners up-to-date on the best names and deals of
nationwide payroll companies.
On average, 40% of the administrative wor of a small business deals
with payroll processing.
Even if you’re already outsourcing Charlie's Choice’s payroll,
it’s always good to know how much you should really be paying.

Please reply to this email with your payroll needs to enjoy our free
quote comparison service.


Best regards,
Helen Collins
Online Payroll Specialist
Helen@PayrollServices.website


Unsubscribe by reply back "REMOVE".
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


[Bug 246121] [bhyve][PATCH] Append Keyboard Layout specified option for using VNC.

2020-05-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246121

Koine Yuusuke  changed:

   What|Removed |Added

 Attachment #214027|0   |1
is obsolete||
 Attachment #214725|text/x-uuencode |text/plain
  mime type||

--- Comment #5 from Koine Yuusuke  ---
Created attachment 214725
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214725=edit
[bhyve][PATCH] Append Keyboard Layout specified option for using VNC.

Thank you for the various ideas!

As a result of thinking, I think that the method that has the keyboard-layout
setting file is better.
However, I tried to automatically generate the keyboard-layout setting file for
each language from the file existing /usr/share/vt/kbdmap for vt, so update the
generated keyboard-layout patch files for each language.
Now that I can enter the following keys on the keyboards of all languages
supported by vt, what about?

A. How to apply the patch --
  1. cd /usr/src/usr.sbin
  2. patch -u < bhyve_kbdlayout_fbsd13c.patch
  3. sh bhyve_kbdlayout.shar   (*Updated the bhyve_kbdlayou.shar file
in this time.)
  4. cd /usr/src/usr.sbin/bhyve
  5. make
  6. make install

  * If you use the FreeBSD 12.1-RELEASE, please replace the "fbsd13c" of the
above No.2 to the "fbsd121r".

B. Supoorting Keyboard map -
  You can use the following keyboard language layout.
   (Indicates the string that can be specified in the bhyve -k option.)
  am / be / be_acc / bg_bds / bg_phonetic / br / br_noacc / by
  ca / ca-fr / centraleuropean / centraleuropean_qwerty
  ch / ch_acc / ch-fr / ch-fr_acc / ch_macbook_acc / colemak_acc
  cz / de / de_acc / de_noacc / dk / dk_acc / dk_macbook
  ee / es / es_acc / es_dvorak / fi
  fr / fr_acc / fr_dvorak / fr_dvorak_acc / fr_macbook
  gr / gr_101_acc / gr_elot_acc / hr / hu_101 / hu_102
  il / is / is_acc / it / kz_io / kz_kst / lt
  latinamerican / latinamerican_acc / nl / no / no_dvorak / nordic_asus-eee
  pl / pl_dvorak / pt / pt_acc / ru / ru_shift / ru_win / se / si / sk
  tr / tr_f / ua / ua_shift_alt / uk / uk_capsctrl / uk_dvorak / uk_macbook
  us / us_acc / us_ctrl / us_emacs / us_macbook / us_unix
  us_dvorak / us_dvorakl / us_dvorakp / us_dvorakr / us_dvorakx
  jp / jp_capsctrl

C. Supporting Key with the above Keyboard-Layout file. 
  Alphabetical Key ( [a-zA-Z] )
  Numeric Key  ( [0-9] )
  Sign mark Key( !"#$%&'()+-*/=^~\|@`[]{};:,.<>?_ )
  Enter / Escape / Tab / Shift(L/R) / Ctrl.(L/R) / Alt(L/R) / Home / End / Ins.
/ BackSpace / Delete
  Up Arrow / Down Arrow / Left Arrow / Right Arrow / PgUp / PgDown
  F1-12 / WinKey(L/R)

* jp / jp_capsctl supports Japanese keyboard specific keys.

D. Thoghts on the ideas you taught 
 1. The workaround by executing "setxkbmap us" on the VNC client side.
   This method allows the guest OS to enter the correct key input, but there is
a problem that the key cannot be input correctly on the client side(HyberVisor)
terminal.
   Therefore, it is not possible to use the FreeBSD terminal on which bhyve
runs and the guest OS as the same time.
   I knew it was also introduced as a workaround on other sites, but I patched
this thread because of the above issue.

 2. The use of QEMU Extended Key Event Message
   I understand that this method is a drastic measure to avoid using the
keyboard-layout files, and I would like to make the patch with it if possible
...
   However, in the current VNC clients that exist the FreeBSD ports, tigerVNC
doesn't support this message because it is an old version, and it seems that
tightVNC & ssvnc doesn't support this message in the first place.
   If the VNC clients that exist the FreeBSd ports supprots this message, I
would like to try to support this message, but I can not support it because
there is no VNCclient currently. And as far as I can see the bhyve source tree,
I think the difficulty level of the modification is high.

 3. This proposal
   When we aim to make it easy to use any language using the current VNCclient
on FreeBSD ports, I think that it is unavoidable to use the keyboard-layout
setting file.
   However, it is difficult to create the keyboard-layout files for each
launguage from the beginning, so the minimum keys such as alphabets, numbers,
and symbols were automatically generated.
   I would like to ask if this method is acceptable, test the generating
keyboard-layout setting file for each language, and add a unique key definition
for each language.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list