search for: veewee

Displaying 7 results from an estimated 7 matches for "veewee".

2013 Jul 30
2
Vagrant Puppet Provision VM
Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └── VBoxGuestAdditions_4.2.12.iso ├──...
2015 Dec 08
2
Re: Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied
Thanks Kashyap for replying. QEMU has permissions to the directory which is having images. I will look into the AppArmor issue and find out more about this. Also as per suggestion from the link i have uncommented the user and group from the qemu.conf file - https://github.com/jedi4ever/veewee/issues/996 By checking more on the AppArmor and sVirt issue , i have modified the qemu.conf for security_driver="none". The result for this is no permission error but another error which can be related to QEMU 2.3.0 virsh # blockcommit vm-01 vda --verbose --pivot --active Block Commit:...
2015 Dec 09
2
Re: Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied
...> wrote: Thanks Kashyap for replying. QEMU has permissions to the directory which is having images. I will look into the AppArmor issue and find out more about this. Also as per suggestion from the link i have uncommented the user and group from the qemu.conf file - https://github.com/jedi4ever/veewee/issues/996 By checking more on the AppArmor and sVirt issue , i have modified the qemu.conf for security_driver="none". The result for this is no permission error but another error which can be related to QEMU 2.3.0 virsh # blockcommit vm-01 vda --verbose --pivot --active Block Commit:...
2015 Dec 08
0
Re: Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied
...ap for replying. > > QEMU has permissions to the directory which is having images. I will look > into the AppArmor issue and find out more about this. > Also as per suggestion from the link i have uncommented the user and group > from the qemu.conf file - https://github.com/jedi4ever/veewee/issues/996 > > By checking more on the AppArmor and sVirt issue , i have modified the > qemu.conf for security_driver="none". The result for this is no permission > error but another error which can be related to QEMU 2.3.0 > > virsh # blockcommit vm-01 vda --verbose --...
2016 Jan 05
0
Re: Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied
.... > > > > QEMU has permissions to the directory which is having images. I will look > into the AppArmor issue and find out more about this. > > Also as per suggestion from the link i have uncommented the user and group > from the qemu.conf file - https://github.com/jedi4ever/veewee/issues/996 > > > > By checking more on the AppArmor and sVirt issue , i have modified the > qemu.conf for security_driver="none". The result for this is no permission > error but another error which can be related to QEMU 2.3.0 > > > > virsh # blockcommit vm...
2015 Dec 07
3
Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied
Hi , Working on the simple POC : Advanced snapshot using libvirt and qemu . Following are the exact steps which are followed . 1. Created as base VM - Ubuntu 15.10 with following libvirt and qemu versions Using library: libvirt 1.2.16 Using API: QEMU 1.2.16 Running hypervisor: QEMU 2.3.0 QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9.1), Copyright (c) 2003-2008 Fabrice
2013 Jan 07
16
stdlib take almost 14 minutes to sync on CentOS Vagrant VM
Hi, I have a fresh CentOS 5.8 Vagrant VM that I''m using to emulate a customer''s server. During the first Puppet run, it takes 13 minutes and 48 seconds to sync the Puppet Labs stdlib module. On a similar Ubuntu 12.04.1 Vagrant VM, Puppet starts up, and almost instantly goes from plugin sync to facter load. Is this load time for stdlib on a RHEL variant normal?