Comments (10)
You can try to define the pool with:
# virsh pool-define /dev/stdin <<EOF
<pool type='dir'>
<name>default</name>
<target>
<path>/var/lib/libvirt/images</path>
</target>
</pool>
EOF
virsh pool-start default
virsh pool-autostart default
from virt-deploy.
Hi,
I've met similar issue. I have minimal installation and I've installed virt-deploy and it seems that "default" pool is not defined.
It is caused also by missing dependency, what is not directly needed but this dependency create this pool.
it is package "virt-manager"
after installation of that package and reboot machine, pool is aviable.
So I'm not sure what is better solution, install dependendend virt-manager or create default pool + default network in own setup as workaround.
From this point of view I cannot decide what is better.
it is connected with another issue:
#10
So my point of view is, that it would be nice, to not use default pool and default network but be able to config own pool for disc and net.
Regards
Honza
from virt-deploy.
@screeley44 what version are you using? (virt-deploy --version)
Latest version on copr is 0.1.6.
Can you check that you have the default pool defined in libvirt:
# virsh pool-list
Name State Autostart
-------------------------------------------
default active yes
Thanks
from virt-deploy.
that worked!! Thanks!!
Name State Autostart
default active yes
from virt-deploy.
Marking this as enhancement/help-wanted because adding the default storage pool when missing will improve user experience.
from virt-deploy.
My mentioned solution should also solve another issue:
I'm running virt-deploy under normal user ( not root) and I've added policy to
/etc/polkit-1/localauthority/50-local.d/50-org.example-libvirt-remote-access.pkla
to allow some group work with virsh qemu:///system
All virsh qemu:///system comands works then well, but qemu-img command does not have access to /var/lib/libvirt/images (default pool location), so in case virt-deploy under normal user create this pool in some other dir where user/group has access it will be better. (/var/lib/libvirt/images/_fedora-21-x86_64.qcow2: qemu-img exited with error status 1.)
from virt-deploy.
Hi,
otherwise I found, that this default pool is created after command virt-manager is called (probably virt-manager do some init of "default" pool)
installation of virt-manager is not enouht
Honza
from virt-deploy.
error: Failed to define pool default
error: operation failed: Storage source conflict with pool: 'images'
SOLVED:
virsh pool-list
Name State Autostart
images active yes
$ virsh pool-destroy images
Pool images destroyed
$ virsh pool-undefine images
Pool images has been undefined
Then restart the deployment
from virt-deploy.
a reference to vagrant-libvirt README
storage_pool_name - Libvirt storage pool name, where box image and instance snapshots will be stored.
My Solution
Example: install boxe centos/7
- init Vagrant
vagrant init centos/7
- edit
Vagrantfile
config, inprovider
secition add config like follow:
Vagrant.configure("2") do |config|
...
config.vm.provider :libvirt do |libvirt|
libvirt.storage_pool_name = "images"
end
...
end
- then, start install
vagrant up --provider libvirt
- (Option) if you like, you can add follow environment config to /etc/profile to make
libvirt
as default provider, then you not need--provider libvirt
as vagrant parameter.
export VAGRANT_DEFAULT_PROVIDER=libvirt
from virt-deploy.
Related Issues (17)
- Add support for specifying ssh commands to execute on an instance HOT 4
- RFE: create new instance with option to modify used network HOT 3
- virt-deploy should require new enough libguestfs-tools-c version HOT 1
- virt-deploy should depend on python-lxml HOT 3
- better handle table _IMAGE_OS_TABLE
- RFE: tree installation abilities HOT 3
- CentOS 7.2 not supported
- fedora-23 template: virt-resize: error: unknown/unavailable method for expanding the xfs filesystem on /dev/sda3 HOT 3
- storage pool in /var/lib/libvirt/images without sudo
- Support cloud-init to configure instances HOT 1
- So the default storage pool must exist? Why?
- traceback when using same name (DNS) -> no info about created machine displayed HOT 4
- RFE: add new option to wait for guest is ready to communicate (ping, ssh, ...) HOT 1
- error when deleting created instance (more snapshots) HOT 1
- support creation machines for user (qemu:///session) HOT 3
- error: failed to mkdir on virt-deploy create <instance> <image> HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from virt-deploy.