similar to: [CentOS] VirtIO disk 'leakage' across guests?

We are in the process of migrating several stand-alone server hosts onto a CentOS-6 kvm virtual host. We also use Webmin to administer our hosts. All of the guests, without exception, have been cloned brom a prototype guest using virt-manager. All of the additional VirtIO disks assigned to some of the guests have been added through virt-manager as well. Recently I have encountered a situation

We are in the process of migrating several stand-alone server hosts onto a CentOS-6 kvm virtual host. We also use Webmin to administer our hosts. All of the guests, without exception, have been cloned brom a prototype guest using virt-manager. All of the additional VirtIO disks assigned to some of the guests have been added through virt-manager as well. Recently I have encountered a situation

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

On Wed, 2006-12-06 at 23:51 -0700, asterisk-users-request@lists.digium.com wrote: > Date: Wed, 06 Dec 2006 22:37:01 -0500 > From: Steve Prior <sprior@geekster.com> > Subject: Re: [asterisk-users] Is there any Asterisk controllable > thermostat? > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users@lists.digium.com> >

I mistyped the storage allocation for an additional virtio drive for one of our vm guests and now I cannot get rid of the thing. I have discovered that this is probably, indeed almost certainly, related to udev but the few work arounds I have found all seem to fail for me. Does anyone here know how to remove these things? When I try this: # for i in {1..200}; do udevadm control

CentOS-6.2 I created a new VirtIO disk for one of my virtual machines. Previous experience has taught me that I need to partition it before attempting to add the new storage to the physical volume set of the intended guest. Up to now I have simply accepted the defaults given by fdisk after telling it that I want a new partition. The defaults always exclude the first 2048 sectors. Disk

Hi One of our customers has a Filemaker database which needs to be accessed for some data. Using the Web Companion, I can query the database for an XML version of the data. I need to be able to push this data into an array of hashes, so I can access it in a more convenient way. Filemaker is able to provide me with 2 XML formats (DSO-XML and FMP-XML): *********** DSO-XML ***********

I am trying to migrate a VMware guest to KVM. I have the .vmdk file which I convert to qcow2 format using qemu-img convert. The next step is to import the new img file. If I use virt-install --import <guest config options> it all works fine. But when I try the same think using the libvirt API I get the "no boot disk found" message when starting the vm. When importing the VM

Hi all, I'm playing with virsh, and I succeed to mange easily some KVM nodes. But I have issues to size RAM of openvz guests. virsh set by default the the memory to 256M on each guest instead of that I specify in the XML I have to modify by end the variable PHYSPAGES on each /etc/vz/conf/id_of_my_vz.conf Please follow the XML dump and the steps that I did. Cheers,Aurelien Log ---- 1)

On 17.12.2015 13:06, Andrei Perietanu wrote: > I am trying to migrate a VMware guest to KVM. I have the .vmdk file which I > convert to qcow2 format using qemu-img convert. > > The next step is to import the new img file. > > If I use virt-install --import <guest config options> it all works fine. > But when I try the same think using the libvirt API I get the "no

I''m creating a new domU using ''virsh create <xmlfile>'' without specifying the MAC address within the XML file, under the assumption that the dom0 or hypervisor generates the MAC address for me. Next I''d like to get the MAC address that was assigned to this new domU, and I don''t see a way to get that information from the command line via virsh