Summary Files Commits Branches @commit @diff @stats
path: root / src / blog / virt-manager-freeze-on-browse / index.du
diff options
context:
space:
mode:
1 files changed, 3 insertions, 3 deletions
-rw-r--r--src/blog/virt-manager-freeze-on-browse/index.du6
diff --git a/src/blog/virt-manager-freeze-on-browse/index.du b/src/blog/virt-manager-freeze-on-browse/index.du
index a5646cf..ff6bdfc 100644
--- a/src/blog/virt-manager-freeze-on-browse/index.du
+++ b/src/blog/virt-manager-freeze-on-browse/index.du
@@ -9,9 +9,7 @@ The title explains what the problem is.
You might've also noticed that it spikes a CPU core's utilization to 100%.
Furthermore everything works if you enter a file location manually in the corresponding input field, it's just that darn button.
-'footnote storage-pools The storage pool is just a folder with files that store what locations can be used by virtual machines (more info {url here;https://libvirt.org/storage.html}). In the case of virt-manager, pretty much every time you select any folder or file, a folder entry gets added there.
-
-This issue is caused by some sort of problem with the storage pools{storage-pools} when it tries to load them.
+This issue is caused by some sort of problem with the storage pools{fn The storage pool is just a folder with files that store what locations can be used by virtual machines (more info {url here;https://libvirt.org/storage.html}). In the case of virt-manager, pretty much every time you select any folder or file, a folder entry gets added there.} when it tries to load them.
I was able to fix it by pretty much deleting that folder, but you really should just rename it:
```sh
@@ -21,3 +19,5 @@ libvirt automagically regenerates the original folder, so you might need to rest
```sh
sudo systemctl restart libvirtd
+
+{footnotes}