|
 |
9119d9 |
From 22e3737a8ba5750ecbd5d96f2679b11ef6f125af Mon Sep 17 00:00:00 2001
|
|
|
9119d9 |
Message-Id: <22e3737a8ba5750ecbd5d96f2679b11ef6f125af@dist-git>
|
|
|
9119d9 |
From: Michal Privoznik <mprivozn@redhat.com>
|
|
|
9119d9 |
Date: Wed, 19 Nov 2014 09:37:02 +0100
|
|
|
9119d9 |
Subject: [PATCH] docs: Document NVRAM behavior on transient domains
|
|
|
9119d9 |
|
|
|
9119d9 |
https://bugzilla.redhat.com/show_bug.cgi?id=1026772
|
|
|
9119d9 |
|
|
|
9119d9 |
Since 1.2.8 it's possible to use OVMF on domains. Moreover, it's
|
|
|
9119d9 |
possible to have libvirt create NVRAM file per domain. Later,
|
|
|
9119d9 |
when domain is undefined, the file is removed too. However,
|
|
|
9119d9 |
things are a bit complicated when domain's transient. There's no
|
|
|
9119d9 |
undefine to transient domains. There are two options: 1) leave
|
|
|
9119d9 |
the file behind and let mgmt app remove it. 2) remove it
|
|
|
9119d9 |
automatically as domain dies.
|
|
|
9119d9 |
But, in some scenarios mgmt app may want to preserve the file,
|
|
|
9119d9 |
copy it somewhere safe, and then copy it back when the domain is
|
|
|
9119d9 |
starting again. And this wouldn't be possible with case 2). So,
|
|
|
9119d9 |
even though case 1) leaves some files behind (possibly undeleted
|
|
|
9119d9 |
for a long time), the files themselves are small (128K each). And
|
|
|
9119d9 |
data loss is worse than full disk, isn't it?
|
|
|
9119d9 |
|
|
|
9119d9 |
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
|
|
|
9119d9 |
(cherry picked from commit 401702d92eb28faffbb7a8b63baca67ef7d9a5b5)
|
|
|
9119d9 |
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
|
|
|
9119d9 |
---
|
|
|
9119d9 |
docs/formatdomain.html.in | 5 ++++-
|
|
|
9119d9 |
1 file changed, 4 insertions(+), 1 deletion(-)
|
|
|
9119d9 |
|
|
|
9119d9 |
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
|
|
|
9119d9 |
index 80af7fa..138b5e1 100644
|
|
|
9119d9 |
--- a/docs/formatdomain.html.in
|
|
|
9119d9 |
+++ b/docs/formatdomain.html.in
|
|
|
9119d9 |
@@ -147,7 +147,10 @@
|
|
|
9119d9 |
started up libvirt copies so called master NVRAM store file defined
|
|
|
9119d9 |
in qemu.conf. If needed, the template
|
|
|
9119d9 |
attribute can be used to per domain override map of master NVRAM stores
|
|
|
9119d9 |
- from the config file. Since 1.2.8
|
|
|
9119d9 |
+ from the config file. Note, that for transient domains if the NVRAM file
|
|
|
9119d9 |
+ has been created by libvirt it is left behind and it is management
|
|
|
9119d9 |
+ application's responsibility to save and remove file (if needed to be
|
|
|
9119d9 |
+ persistent). Since 1.2.8
|
|
|
9119d9 |
boot
|
|
|
9119d9 |
The dev attribute takes one of the values "fd", "hd",
|
|
|
9119d9 |
"cdrom" or "network" and is used to specify the next boot device
|
|
|
9119d9 |
--
|
|
|
9119d9 |
2.1.3
|
|
|
9119d9 |
|