similar to: added second virtio-disk: disk order detected wrong

Thank you for your help! 1, i used vda as install disk and vdb as target disk, because i boot from the first. After setup boot order flag i was able change install disk to vdb and target disk to vda. With this configuration when i boot from vdb i can install OS with grub and after it redefine XML without vdb without problem. Thanks a lot. 2, maybe i have something wrong, but still not working:

Hi, I'm trying to create a snapshot on a specific disk by using diskspec option. However, libvirt/virsh seems to ignore it and takes a snapshot of all disks. Am I using this option incorrectly? In below examples, I'm trying to snapshot only vdb. However even vda is getting snapshotted regardless of diskspec. Is this a known issue? I'm on CentOS 7.1, libvirtd (libvirt) 1.2.8, virsh

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

Dear all, Please let me start by indicating that I am not from a technical background, so please be gentle and patient with me. I am trying to get a snapshot from my virtual machines (vm) and the following command works for all of them bar one: # virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state --diskspec vda,file=overlay.qcow2 --disk-only --atomic The only exception is

Hello, I am working on a script to automatically create live snapshots of running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has multiple disks, I'd like to back them up individually with separate calls to snapshot-create-as, so I can more easily manage the disk images. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name

Hi, dear friend. My guest has two disks, vda and vdb. both are qcow2 local file. When guest running state. I want to take the vda snapshot of guest(just vda, no include vdb). but I met libvirt do snapshot for all disks of guest. About methods for follow: 1、 ``` bash virsh snapshot-create-as 8x0lbzvS --name sys_disk3 --disk-only --diskspec "vda,snapshot=external" ``` ``` result

Let's say I have a vm, vm1, which has a lv as its hard drive: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/dev/mapper/kvmtest_vm1_rootvg'/> <target dev='vda' bus='virtio'/> <address type='pci'

Hello, I want to do a snapshot which the VM has volumes. But I want to skip the volume check when I do the snapshot. (Which means I want to do a snapshot without detaching the volume) So I try to write a snapshot XML refer by http://libvirt.org/formatsnapshot.html as following: vda is my VM basic disk (qcow2) vdb is a volume (raw) ================ t1.xml =============== <domainsnapshot>

Hi, >> Yes, here's the layout from the vm: >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> devtmpfs 7.9G 0 7.9G 0% /dev >> tmpfs 7.9G 0 7.9G 0% /dev/shm >> tmpfs 7.9G 643M 7.3G 9% /run >> tmpfs 7.9G 0 7.9G 0%

I never thought I'd say this, but I think it's easier to do this with GRUB 2. Anyway I did an installation to raid1's in CentOS 6's installer, which still uses GRUB legacy. I tested removing each of the two devices and it still boots. These are the commands in its log: : Running... ['/sbin/grub-install', '--just-copy'] : Running... ['/sbin/grub',

Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist --------------------------------------------------------------------- The two disks are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: - --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist -

Hi all, i created a script in PHP for create a virtual server with two QCOW2 discs … one is our system for installation and second is target system. After successfully instalation (create a blank Debian system, prepare all files and grub partitions) i need a restart virtual without a installation disk. If i use Virsh: detach-disk --domain debian-test2 --persistent --target vda reset

On Thu, Dec 05, 2013 at 01:28:07PM +0200, Alexandr Gluzskiy wrote: > Alexandr писал 2013-12-02 09:36: > >Good day to all. i have problems with cdrom hot adding code. currently > >i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, > >this code works for machine with one ide hdd and one ide cdrom, but > >this not work for machine with only one ide hdd,

Hello Thanks heaps for your suggestions. responses inline. On 10 Apr 2014, at 10:34 pm, Eric Blake <eblake@rehost1hat.com> wrote: > > [ … ] > [Can you convince your mailer to wrap long lines? It makes it easier > for other readers] I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. >> >> Using RHEL 6.4 and libvirt version

The boot order issue http://osdir.com/ml/libvir-list/2009-08/msg00398.html resolved with the code changes specified by http://www.redhat.com/archives/libvir-list/2009-August/msg00340.html seems to suggest that hard disks, cdroms, floppy devices (since they are all disks) are ordered primarily by virtual bus type as encountered in the domain xml. This indicates that there can exist a

Any idea what 'virt-customize' script I should use to convert from virtio-blk (vda, vdb...) to virtio-scsi (sda, sdb...) ? I've tried naively to convince libvirt to use virtio-scsi and still present it to the guest as 'vd*' - that didn't work ( <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/>

On 05/22/2014 04:31 PM, Andrew Martin wrote: > Hello, > [Can you convince your mailer to wrap long lines?] > I am working on a script to automatically create live snapshots of > running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has Any reason you aren't upgrading to newer versions? Although these seem sufficient for what you are trying. > multiple disks, I'd

Hello. What it the difference in external snapshot configuration with and without <domainsnapshot> ? What is the difference between vda and vdb in the following example? (From https://libvirt.org/formatsnapshot.html) <domainsnapshot> ... <memory snapshot='no'/> <disks> <disk name='vda' snapshot='external'> <driver