Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2209153

Summary:	[RFE] Add use case and configuration for using passt with libvirt/VMs
Product:	Red Hat Enterprise Linux 9	Reporter:	Germano Veit Michel <gveitmic>
Component:	Documentation	Assignee:	Jiri Herrmann <jherrman>
Documentation sub component:	default	QA Contact:	RHEL DPM <rhel-docs>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	high
Priority:	high	CC:	germano, leiyang, radrao, rharcari, rhel-docs, sbrivio, yalzhang
Version:	9.2	Keywords:	Documentation, FutureFeature, MigratedToJIRA
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2209429 (view as bug list)		Environment:
Last Closed:	2023-09-27 17:16:12 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2209429

Description Germano Veit Michel 2023-05-22 21:35:10 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.2_release_notes/new-features#new-features-virtualization

Section Number and Name: 

Chapter 4 - New Features
 -> 4.17. Virtualization
  -> New package: passt

Describe the issue:

The last sentence:
"For more information on using passt, see the libvirt upstream documentation."

Customers should be referred to detailed RHEL documentation, not upstream libvirt.


Suggestions for improvement: 

1. Remove that sentence refering the customer to upstream
2. Add proper documentation under Virtual Machine under Chaper 16 (Configuring virtual machine network connections) describing:
   * Use case and recommendations on when to use it or not
   * How to configure
   * Any limitations or other considerations

So the customer does not need to consult upstream documentation for a GA feature.

Comment 20 yalzhang@redhat.com 2023-09-21 03:32:54 UTC

* "When using passt while in non-privileged user mode, your VM uses network address translation (NAT) connection more effectively."
It may cause some misunderstanging that passt did use NAT. (But I don't know how to describe it's performance benefits without mention slirp) How about:
"In non-privileged user mode, passt backend user interface is very efficient. In addition, passt improves the general stability and security of network connection in non-root VM sessions."

* The xml example in step 2 of the procedure it taken from the libvirt.org. It's a kind of a full xml and it's very complecated. How about using a simple one, like:
<devices>
  [...]
  <interface type='user'>
    <backend type='passt'>
    <mac address="52:54:00:98:d8:b7"/>
    <source dev='eth0'/>
    <ip family='ipv4' address='172.17.2.4' prefix='24'/>
    <ip family='ipv6' address='fd12:3456:789a:bcde::1'/>
  </interface>
</devices>

This example configuration sets up a passt connection with the following parameters:

The VM obtains the network routes for forwarding traffic from the eth0 host interface.
VM will get the ipv4 address as 172.17.2.4/24 and ipv6 address as fd12:3456:789a:bcde::1/64

In this xml, I deleted the optional portforwarding sections to make it simple; updated the mac address to be a random one; updated the ipv6 address to be a private ipv6 address.
(The ip setction can also be deleted, then you will get a minimal xml, but it may cause some confusing that VM will share the ip address of the host's, so I keep it.)

Stefano, what do you think?

Comment 21 yalzhang@redhat.com 2023-09-21 03:43:20 UTC

The "/" missed after "<backend type='passt'>", should be "<backend type='passt'/>"

Comment 26 RHEL Program Management 2023-09-27 17:15:56 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 27 RHEL Program Management 2023-09-27 17:16:12 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.