This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1436245 - [RFE] Add support for taking external snapshots of PFLASH nvram image
Summary: [RFE] Add support for taking external snapshots of PFLASH nvram image
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: beta
: ---
Assignee: Peter Krempa
QA Contact: Meina Li
URL:
Whiteboard:
: 2128504 (view as bug list)
Depends On: 760547 1624009
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 13:45 UTC by Peter Krempa
Modified: 2023-09-22 12:22 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 12:22:34 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7049 0 None Migrated None 2023-09-22 12:22:27 UTC

Description Peter Krempa 2017-03-27 13:45:49 UTC 
Description of problem:
Currently it's not possible to snaphsot the <nvram> backing image while taking an external snapshots. Add the support so that all files are properly versioned.
Comment 1 Xuesong Zhang 2017-03-29 08:16:57 UTC 
hi, Peter,

From the libvirt.org[1], <mvram> is one specific device for PPC arch. So, I'd like to update the arch of this BZ from "Unspecified" to "ppc64le" for better tracking. Is it ok for you? Please correct me if any of my thoughts is wrong.

[1] nvram device: http://libvirt.org/formatdomain.html#elementsNVRAM
Comment 2 Peter Krempa 2017-03-29 08:23:24 UTC 
No, <nvram> is also used for OVMF, which maps to a second pflash drive. So it certainly  is not ppc64 relevant at all. The ppc64 nvram probably won't be snapshottable, but I did not investiagte further.
Comment 3 Xuesong Zhang 2017-03-29 10:03:31 UTC 
(In reply to Peter Krempa from comment #2)
> No, <nvram> is also used for OVMF, which maps to a second pflash drive. So
> it certainly  is not ppc64 relevant at all. The ppc64 nvram probably won't
> be snapshottable, but I did not investiagte further.

OK, it seesm the <nvram> in this BZ is the following settings in <os>, not the specific device for PPC.

<os>
  ......
  <nvram template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/nvram/guest_VARS.fd</nvram>
  ......
</os>
Comment 6 Jaroslav Suchanek 2018-04-12 07:08:37 UTC 
Comment 5 should include answers from comment 4.
Comment 9 Jaroslav Suchanek 2019-04-24 12:26:36 UTC 
This bug is going to be addressed in next major release.
Comment 12 RHEL Program Management 2021-01-15 07:33:20 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 19 RHEL Program Management 2022-01-31 07:27:08 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 22 RHEL Program Management 2022-07-31 07:27:19 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 23 Meina Li 2022-08-01 01:47:37 UTC 
Reopen this bug according to the comment 13.
Comment 25 Jaroslav Suchanek 2022-09-21 08:38:30 UTC 
*** Bug 2128504 has been marked as a duplicate of this bug. ***
Comment 29 RHEL Program Management 2023-09-22 12:19:51 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 30 RHEL Program Management 2023-09-22 12:22:34 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.
Note You need to log in before you can comment on or make changes to this bug.