similar to: Re: Read-only iscsi disk? Or hot-plug?

Peter Krempa <pkrempa@redhat.com> writes: > On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS will not accept the hot plugged memory and will complain with >> messages

On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote: > Op 27-04-2020 om 09:02 schreef Peter Krempa: > > On Sat, Apr 25, 2020 at 16:40:35 +0200, Paul van der Vlis wrote: > >> Op 25-04-2020 om 16:00 schreef Paul van der Vlis: > >>> Hello, > >>> > >>> I have a qcow2 disk what needs to become increased. > >>> >

Commit aa9e0057b19e29f76c9a81f9aebeeb1cb5bf1fdb made the libvirt backend use <shareable/> for the disk of the appliance, since at that time all the instances were using the disk directly. OTOH, commit 3ad44c866042919374e2d840502e53da2ed8aef0 switched to overlays for read-only disks, including the appliance, so effectively protecting the appliance. Because of this, the libvirt backend does

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000 The start address above is also reported within <memory> element of the hot

Peter Krempa <pkrempa@redhat.com> writes: > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote: >> Hi, when working on hot unplugs of various devices, I've found out that >> hot unplugging <lease> device doesn't generate >> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an >> alias, so it wouldn't be

We wan't to setup two Oracle instance and make RAC work on them. Both VM are setup based on libvirt + KVM, we use a lvm lun which formated in qcow2 format and set the shareable properties in the disk driver like this: <disk type='block' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source

Op 27-04-2020 om 10:41 schreef Peter Krempa: > On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote: >> A point is that I have to create disk(s) on the other side with >> qemu-img, I did not found a way to do that automatically. My question > > We are able to pre-create the storage given that a full copy is > requested (copy-storage-all, not copy-storage-inc)

hi everybody I've looked it up on the net but info is scarce. Could please someone explain how to use loopback and what is purpose? many thanks

On 08/08/2013 03:54 AM, Timon Wang wrote: > Anybody have idea on it? > > I tried to set the disk as raw format, and retried the setup process, > but still can't get through. Caveat: I know nothing in particular about Oracle RAC, but... Assuming that RAC uses something like SCSI reservations in order to share the disk, I would guess it doesn't like the disk being on the IDE

Hello, I use libvirt on machines without shared storage. My VM's have all one qcow2-disk, with the same name as the VM. When I want to migrate a VM, I check if there is an qcow2 image on the other host with that name. When that's not the case, I copy the image using rsync first. If the image excist, I don't do that, and I think that "--copy-storage-inc" will do it. But I

Anybody have idea on it? I tried to set the disk as raw format, and retried the setup process, but still can't get through. On Fri, Aug 2, 2013 at 1:58 PM, Timon Wang <timonwst@gmail.com> wrote: > We wan't to setup two Oracle instance and make RAC work on them. > Both VM are setup based on libvirt + KVM, we use a lvm lun which > formated in qcow2 format and set the

I have tryied change the disk bus to SCSI, add a SCSI controller whose model is virtio-scsi, still can't setup the RAC instance. I tried to use windows 2008 Failover Cluster feature to setup a a Failover Cluster instead, and I can't find any cluster disk to share between two nodes. So when Failover Cluster is setup, I can't add any Cluster disk to the Failover Cluster. Have I missed

DV suggested that we document some libvirt setups using shared storage. I'm not a fan of NFS, so I wrote some blog posts on how to use iSCSI in the context of libvirt + KVM. There is of course more than one way todo things, so I've outlined a couple of different options. One completely manual command line approach using tgtadm on the iSCSI server:

hi, I have two private packages, the first (`pkc') depending on the second one (`roiutils'). The source code and DESCRIPTION files describes the dependency as it should be ('Imports', `require'), at least I think so. now, running R CMD CHECK pkc yields the following output in which I have inserted my questions (lines starting with -->): * checking for working latex ...

I tried two times to get some help for this from the help list but to no avail. I hope, it's OK to post this here (once...). if not, please ignore (the rest of) this mail: for one of my private packages R CMD CHECK {package} givves me annoying warnings due to 'missing links' in the manpages for functions from another private package mentioned in the manpages. specifically, I have two

On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote: > Peter Krempa <pkrempa@redhat.com> writes: > > > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote: > >> Hi, when working on hot unplugs of various devices, I've found out that > >> hot unplugging <lease> device doesn't generate > >> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED

Hello, I'm trying to plug and unplug cpus with a host CentOS 7 on a guest machine with CentOS too. I have created the guest with virt-install command, modified my domxml to have maximum 4 vcpus and updated the current cpu to 2. After that I open the virsh console, and used command setvcpus to add/remove cpus. I was able to increase the vcpu count until 4 but can't increase it after 4 as

Hi, when working on hot unplugs of various devices, I've found out that hot unplugging <lease> device doesn't generate VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an alias, so it wouldn't be identifiable in the corresponding callback. Is this difference from other hotpluggable devices intentional? If yes, is there any better way of checking

On Sun, Feb 10, 2019 at 12:11:42 +0100, Paul van der Vlis wrote: > Hello, > > I use libvirt on machines without shared storage. My VM's have all one > qcow2-disk, with the same name as the VM. > > When I want to migrate a VM, I check if there is an qcow2 image on the > other host with that name. When that's not the case, I copy the image > using rsync first. If

I'm running libvirt 0.10.2 and qemu-kvm-1.2.0, both compiled from source, on CentOS 6. I've got a working blkio cgroup hierarchy which I'm attaching guests to using the following XML guest configs: VM1 (foreground): <cputune> <shares>2048</shares> </cputune> <blkiotune> <weight>1000</weight> </blkiotune>