similar to: Live migration with 2 nodes and no SAN

On Thu, Sep 29, 2011 at 9:35 PM, Lucian <lucian at lastdot.org> wrote: > On Fri, Sep 30, 2011 at 2:22 AM, Trey Dockendorf <treydock at gmail.com> > wrote: > > I had a recent request to improve security on my web servers by having > each > > website use a different user to run the hosting service. So > > example1.comhas it's own Apache instance running

I'm setting up a chroot environment on a shared web server to allow users to modify their web roots within a secure chroot, but am having a problem. Right now when I log in with test accounts I get this... Last login: Thu Jul 14 09:04:14 2011 from .... id: cannot find name for group ID 507 id: cannot find name for user ID 506 [I have no name!@webserver ~]$ I've verified that the UID /

I am unable to get the #includedir function to work with sudo. This works just fine on all my CentOS 5.6 servers, but on 6 it is being ignored. I have this line in the file /etc/sudoers.d/zabbix-puppet zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet However sudo still requires a password. If I put that same line into /etc/sudoers file , there is no password prompt. At the end of my

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'

I had a recent request to improve security on my web servers by having each website use a different user to run the hosting service. So example1.comhas it's own Apache instance running as apache1 and then example2.com has its own instance of Apache as apache2. Is this even possible or realistic? I understand the idea of how that would be secure, much like creating a virtual machine to

I have an oVirt engine node that currently runs the system on a qcow2 based virtual disk, and an NFS export volume on RAW. I'd like to take a snapshot before a somewhat risky upgrade of oVirt and can't with the raw image attached. Looking at the documentation for the snapshot XML, I created this XML file for the snapshot <domainsnapshot> <name>20120802</name>

I have decided to migrate my latest KVM server to CentOS 6.0 and am beginning to get a little frustrated with some issues that worked perfectly in 5.6. Right now I've given up on getting virbr0 and NAT to work, but now I need networking bridging to work, but nothing seems to fix the issue. I have not had much experience with troubleshooting KVM so could really use some pointers on resolving

Sorry, ctrl entered. I'm hoping someone here can help me figure out what's going on here. I've got two CentOS 7 hosts with shared storage that I'm trying to do live migrations between and I'm running into an error with VMs that were originally created on a CentOS 6 host and then moved the CentOS 7 hosts. The CentOS 6 VM runs fine on the host, and can do non-live

hi there, I'm following these documentations to add a file-based disk volume to a KVM guest under Centos 6.0 : http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/chap-Virtualization-Storage_Volumes.html as instructed, I created a "pool" then a "volume", file-based, e.g : mkdir /mnt/raid/kvm_pool1 virsh # pool-define-as pool1 dir - - - -

System: CentOS Linux release 6.0 (final) Kernel: 2.6.32-71.23.1.el6.x86_64 KVM: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2) Libvirt: ibvirtd (libvirt) 0.8.1 Hi everyone, I only recently subscribed to this list and hope you can shed some light on the following error. I created a VM on my Centos 6 KVM machine, used a qcow2 image and wanted to create a snapshot via 'virsh

On Tue, Apr 04, 2017 at 12:04:42PM +0200, Daniel Kučera wrote: >Hi all, > Hi, I caught your mail in my Spam folder for some reason, maybe the same happened for others. I don't have that deep knowledge of the snapshots, but I'm replying so that if someone else has it in Spam and they have more insight, they can reply. >I'm using ZFS on Linux block volumes as my VM storage

Hi Martin, in the meantime, I've found a solution which I consider at least acceptable: 1. create zfs snapshot of domain disk (/dev/zstore/test-volume) 2. save original XML domain definition 3. create snapshot in libvirt like this: virsh snapshot-create --xmlfile snap.xml --disk-only --no-metadata test-domain snap.xml: <domainsnapshot> <disks> <disk

Hi all, I'm using ZFS on Linux block volumes as my VM storage and want to do live migrations between hypervisors. If I create ZFS snapshot of used volume on source host, send it do destination host (zfs send/recv) and then run live migration with VIR_MIGRATE_NON_SHARED_DISK flag, the migration works OK. But this procedure copies the whole disk twice which is a huge downside. The best

On 02/12/2015 07:41 PM, Edward Young wrote: > Hi all, > > > When I live migrate a vm using > > "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system > tcp://192.168.1.3" > > > I got the following error > > > WARNING: Image format was not specified for > 'nbd://node2:49155/drive-virtio-disk0' and

On Thu, Feb 12, 2015 at 08:41:31PM -0600, Edward Young wrote: > Hi all, > > > When I live migrate a vm using > > "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system > tcp://192.168.1.3" > > > I got the following error > > > WARNING: Image format was not specified for >

On Thu, Jun 11, 2020 at 05:45:46PM +0200, Paul van der Vlis wrote: > Hello, > > I am looking for a way to migrate a VM live to another location. > > The qcow2 images are now on /data , but I want to move some of them to a > volume mounted on /data2 what's faster. > > Is this possible without downtime? Yes, you don't need to use live migration for this even. The

On 02/13/2015 03:15 AM, Kashyap Chamarthy wrote: > On Thu, Feb 12, 2015 at 08:41:31PM -0600, Edward Young wrote: >> Hi all, >> >> >> When I live migrate a vm using >> >> "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system >> tcp://192.168.1.3" >> >> >> I got the following error >> >> >>

I recently began getting periodic emails from SEalert that SELinux is preventing /usr/libexec/qemu-kvm "getattr" access from the directory I store all my virtual machines for KVM. All VMs are stored under /vmstore , which is it's own mount point, and every file and folder under /vmstore currently has the correct context that was set by doing the following: semanage fcontext -a -t

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'

I'm setting up a shared web server running Apache. Each web root will belong to a department, which has a corresponding Active Directory group to give access. So far I've got samba working and such, but am having some trouble wrapping my head around the necessary permissions to make all this work, especially securely. So far I've found that both the POSIX and the ACL permissions