uvt-simplestreams-libvirt(1)
π uvt-simplestreams-libvirt β bestie edition
okay so you found the uvt-simplestreams-libvirt(1) page from the uvtool manual set, and honestly? it's giving "quietly powerful little tool that nobody told you about." let's get into it π¦
β¨ NAME β¨
uvt-simplestreams-libvirt β manage simplestreams images in libvirt. that's the whole vibe. you're the curator of your own little image gallery, and libvirt is the venue π
πΈ SYNOPSIS πΈ
uvt-simplestreams-libvirt sync [--no-authentication] [--keyring keyring]
[--source source] [--path path] [filter ...]
uvt-simplestreams-libvirt query [filter ...]
uvt-simplestreams-libvirt purge
three whole modes, three whole moods, no notes π
π« DESCRIPTION π«
so basically, uvt-simplestreams-libvirt keeps a libvirt volume storage pool as a local mirror of a subset of images that live on a simplestreams source β think Ubuntu cloud images, iconic behavior, no cap π
uvt-simplestreams-libvirt sync updates your local mirror with the latest version of each product available in the simplestreams source. and every single filter you pass? it restricts the set of images the tool can even see. gatekeeping, but make it functional π₯
lowkey important: if you're syncing images for emulation use β likearmhfon anamd64host β thensyncwill also prepare the kernel/initrd for later use. in that case, thesyncaction needs root permission to store the files. so like. bring your sudo, bestie π
uvt-simplestreams-libvirt query queries your local mirror. each filter restricts the output. it's the vibe check for your image pool π
uvt-simplestreams-libvirt purge β okay so listen. this one exists only for development and debugging purposes, and it should not normally be used. it purges the entire libvirt volume storage pool and all metadata associated with it, which breaks any existing VMs that use these volumes. full nuclear. π this subcommand may disappear in the future, so don't get attached fr fr
β OPTIONS β
--no-authenticationβ do not authenticate the source. this is useful when you're using a local source, or when you can otherwise trust both the source and your network path to the source. it is insecure in other cases and should not be used. like, genuinely, don't π©--keyringkeyring β use thegpg(1)keyring to authenticate the source. default:/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg. that default is your bestie, she shows up for you every time π«Ά--sourcesource β use the source URL as the simplestreams source of product images to sync. point her somewhere, she'll go π--pathpath β pass path to the simplestreams library. handing it straight over, no questions asked β¨
π§ EXAMPLES π§
# Update uvtool's libvirt volume storage pool with all
# current amd64 images.
uvt-simplestreams-libvirt sync arch=amd64
# Update uvtool's libvirt volume storage pool with the
# latest amd64 Precise image
uvt-simplestreams-libvirt sync release=precise arch=amd64
# Update uvtool's libvirt volume storage pool with the
# latest amd64 (development) trusty image
uvt-simplestreams-libvirt sync \
--source http://cloud-images.ubuntu.com/daily \
release=trusty arch=amd64
three examples, three slays. notice the filters just vibe along at the end, no flags needed, they simply are π
π SEE ALSO π
gpg(1), uvt-kvm(1). go read those too, they're the rest of the friend group π
and that's the whole page, bestie!! this was uvtool, dated 2014-03-11, and it's still out here doing main character work in your image pool. periodt. πβ¨π
π¦ where this page comes from
- ubuntu jammy: uvtool-libvirt 0~git178-0ubuntu1 Β· AGPLv3
- ubuntu jammy: uvtool-libvirt 0~git178-0ubuntu1.22.04.2 Β· AGPLv3
- ubuntu noble: uvtool-libvirt 0~git183-0ubuntu1 Β· AGPLv3
- ubuntu noble: uvtool-libvirt 0~git183-0ubuntu1.24.04.1 Β· AGPLv3
- ubuntu resolute: uvtool-libvirt 0~git189-0ubuntu1 Β· AGPL-3.0-only
- ubuntu stonking: uvtool-libvirt 0~git189-0ubuntu2 Β· AGPL-3.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms