You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During my experiments, I realized that the qcow2 images for the virtual machines are always put into a directory with the name /var/lib/libvirt-xxx where xxx is a string.
This is problematic in that we are assuming that the user has his storage configured with enough storage available to the /var/lib directory (either through mount on /, /var or /var/lib depending on the user's configuration).
If this is not already the case, the user will need to expand the storage available to /var/lib which may be a mild irritation or a problematic one depending on the users storage configuration.
If the user has not used a storage configuration that is easily expandable, then they will have to risk data on /var/lib to give this additional storage.
It might make more sense to parameterize the location where these images will be stored.
Maybe we can even create a subdir with the xxx expansion and store the qcow2 images there or just use the provided location directory or figure out some other way to parameterize this
The text was updated successfully, but these errors were encountered:
mohammedzee1000
changed the title
qcow2 images of the zkvm virtual machines is set to /var/lib/libvirt-*
qcow2 images of the zkvm virtual machines is created in /var/lib/libvirt-*
Sep 23, 2023
During my experiments, I realized that the qcow2 images for the virtual machines are always put into a directory with the name
/var/lib/libvirt-xxx
where xxx is a string.This is problematic in that we are assuming that the user has his storage configured with enough storage available to the
/var/lib
directory (either through mount on/
,/var
or/var/lib
depending on the user's configuration).If this is not already the case, the user will need to expand the storage available to
/var/lib
which may be a mild irritation or a problematic one depending on the users storage configuration.If the user has not used a storage configuration that is easily expandable, then they will have to risk data on
/var/lib
to give this additional storage.It might make more sense to parameterize the location where these images will be stored.
Maybe we can even create a subdir with the
xxx
expansion and store the qcow2 images there or just use the provided location directory or figure out some other way to parameterize thisThe text was updated successfully, but these errors were encountered: