From 739e98479cd4ce590fa99c2fefa03c852cbbd9e4 Mon Sep 17 00:00:00 2001 From: Todd Malsbary Date: Wed, 2 Mar 2022 14:11:28 -0800 Subject: [PATCH] Add vagrant destroy note to troubleshooting Signed-off-by: Todd Malsbary Change-Id: I675e35a13cec6b5ee6ebf383e7c43cce9df43936 --- doc/troubleshooting.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index dbc089b..1981186 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -123,3 +123,14 @@ process is. A description of the BareMetalHost states can be found in the [Bare Metal Operator documentation](https://github.com/metal3-io/baremetal-operator/blob/main/docs/baremetalhost-states.md). + +## Vagrant destroy fails with `cannot undefine domain with nvram` + +The fix is to destroy each machine individually. For the default ICN +virtual machine deployment: + + vagrant destroy -f jump + virsh -c qemu:///system destroy vm-machine-1 + virsh -c qemu:///system undefine --nvram --remove-all-storage vm-machine-1 + virsh -c qemu:///system destroy vm-machine-2 + virsh -c qemu:///system undefine --nvram --remove-all-storage vm-machine-2 -- 2.16.6