search for: vdb

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 1.2.8 [root@localhost scripts]# virsh domblklist centos_nfs Target Source ------------------------------------------------ vda /var/lib/libvirt...

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 some...

...ual 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 this one vm, which has two disks as two separete qcow2 files: vda and vdb. Vdb contains my nexcloud data, resides on a btrfs subvolume, and a daily snapshot of this subvolume is taken by a cronjob by the host machine. Therefore, I do not want to include it in the snapshot taken by virsh, and therefore I did not include vdb as a separate --diskspec item, and used the same...

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for hotplug response -- sometimes a ti...

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for hotplug response -- sometimes a ti...

...rowser (e.g. http://127.0.0.1:30410/doc/html/Search?results=1). Another example is help.search("tm") with jsonlite installed. TROUBLESHOOTING: This occurs because utils:::merge_vignette_index() uses: base[, "Name"] <- sub("\\.[^.]*$", "", basename(vDB$File)) base[, "Topic"] <- base[, "Name"] which assumes that the 'Name' (and hence the 'Topic') can be inferred from the basename of the vignette source file by dropping the filename extension. This assumption was valid in R (< 3.0.0), but with the int...

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-2 Severity: important When I try to start a domU with more than 6 vdb it crash. The first time the vm does not launch and aparently wait for the loop device creation (some scripts/block add, udev --daemon and sleep 1 process running). And nothing happen until I Ctrl+C the xm create. My loop module is loaded with 64 loops. After this first attempt the devices are c...

...virtual server, but for some reason it refuses to honor the <address> I have tried the following 3: <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/nbd2'/> <target dev='vdb' bus='virtio'/> <serial>my-fake-serial</serial> <address type='drive' controller='0' bus='1' target='3' unit='2'/> </disk> <disk type='block' device='disk'> <driver na...

...mages. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name "snapshotname" --description "snapshot description" --disk-only --atomic --no-metadata --diskspec "vda" I run this command for each block device (e.g vda, vdb, etc). However, after running the above command (to only backup vda), I see that a snapshot has also been created for vdb. I tried running it with --print-xml, which gives this output: <domainsnapshot> <name>05-22-14_17-09-25</name> <description>05-22-14_17-09-25</des...

...k with spdk I enable debug of systemd-udevd by changing guest's /etc/udev/udev.conf to this: udev_log="debug" and regenerate initramfs. Then, we can get more message about this issue. I select some useful messages from /run/initramfs/rdsosreport.txt: systemd-udevd[199] probe /dev/vdb raid offset=8 systemd-udevd[199] no db file to read /run/udev/data/+virtio:virtio1: No such systemd-udevd[199] handling device node '/dev/vdb', devnum=b253:16, mode=0660, systemd-udevd[199] set permissions /dev/vdb, 060660, uid=0, gid=6 systemd-udevd[199] creating symlink '/dev...

...You can drop --atomic if you use a qemu released in at least last 5 > years as the snapshot is always atomic if the qemu supports the > 'transaction' command. > > > > > The only exception is this one vm, which has two disks as two separete > > qcow2 files: vda and vdb. Vdb contains my nexcloud data, resides on a > > btrfs subvolume, and a daily snapshot of this subvolume is taken by a > > cronjob > > by the host machine. Therefore, I do not want to include it in the > > snapshot taken by virsh, and therefore I did not include vdb as a &gt...

I''ve had a go at determining exactly what happens when you create a filesystem without enough devices to meet the requested replication strategy: # mkfs.btrfs -m raid1 -d raid1 /dev/vdb # mount /dev/vdb /mnt # btrfs fi df /mnt Data: total=8.00MB, used=0.00 System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=153.56MB, used=24.00KB Metadata: total=8.00MB, used=0.00 The data section is single-copy-only; system and metadata are DUP. This is...

...f the two devices and it still boots. These are the commands in its log: : Running... ['/sbin/grub-install', '--just-copy'] : Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] : grub> device (hd0) /dev/vdb : grub> root (hd0,1) : grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,1) /grub/stage2 p (hd0,1)/grub/grub.conf : Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] : grub> root (hd0,1) : grub>...

...gested patch should be OK for ARM in that it will produce ids in > the format > platform-a003e00.virtio_mmio[-partn] Ok, my guest has 4 disks - sda - virtio-scsi, over virtio-pci transport - sdb - virtio-scsi, over virtio-mmio transport - vda - virtio-scsi, over virtio-pci transport - vdb - virtio-scsi, over virtio-mmio transport with systemd 231 I get these links platform-3f000000.pcie-pci-0000:00:01.1-virtio-pci-0000:02:00.0-scsi-0:0:0:0 -> ../../sda platform-3f000000.pcie-pci-0000:00:01.3-virtio-pci-0000:04:00.0 -> ../../vda virtio-pci-a003c00.virtio_mmio -> ../....

...gested patch should be OK for ARM in that it will produce ids in > the format > platform-a003e00.virtio_mmio[-partn] Ok, my guest has 4 disks - sda - virtio-scsi, over virtio-pci transport - sdb - virtio-scsi, over virtio-mmio transport - vda - virtio-scsi, over virtio-pci transport - vdb - virtio-scsi, over virtio-mmio transport with systemd 231 I get these links platform-3f000000.pcie-pci-0000:00:01.1-virtio-pci-0000:02:00.0-scsi-0:0:0:0 -> ../../sda platform-3f000000.pcie-pci-0000:00:01.3-virtio-pci-0000:04:00.0 -> ../../vda virtio-pci-a003c00.virtio_mmio -> ../....

...e“ way: 1, complicated: libvirt_domain_destroy($domain); libvirt_domain_undefine($domain); $xml = domain_create_xml($name,$uuid,$memory,$cpu,$vnc,$mac); $domain = libvirt_domain_define_xml($server->conn, $xml); libvirt_domain_disk_add($domain, "/users/".$name.".img", "vdb", "virtio", "qcow2", NULL); libvirt_domain_create($domain); (or instead libvirt_domain_disk_add i can define disk directly in XML) But in this case, the server will not boot (GRUB error) 2, simple: libvirt_domain_disk_remove($domain,“vda“); libvirt_domain_reboot($domain...

...I have now is essentially as follows: > virsh snapshot-create-as --domain "vmname" --name "snapshotname" --description "snapshot description" --disk-only --atomic --no-metadata --diskspec "vda" > > I run this command for each block device (e.g vda, vdb, etc). However, after running the above command (to only backup vda), I see that a snapshot has also been created for vdb. I tried running it with --print-xml, which gives this output: > <domainsnapshot> > <name>05-22-14_17-09-25</name> > <description>05-22-14_1...

...fs -O > no_netdev". > > > I have other same type servers. And on other servers with same /etc/fstsb, > file system is correct. > There's no difference between normal server's rc.sysinit and this problem > server's rc.sysinit too. It's not apparent how /dev/vdb (the whole filesystem) came to be mounted on both /mnt/extradiskA and /home. Let's see the output from "lsblk" and "mount". Did you look in /mnt/extradiskA/home and verify that just the expected user directories are there (no "/mnt/extradiskA/home/home")? It mi...

...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> <disks> <disk name='vda' snapshot='internal'> <source file='/var/lib/libvirt/VM1/disk' /> </disk> <disk name='vdb' snapshot='no' /> </disks> &...

...rfs1 Summary: Disk_size: 9.00GB Disk_allocated: 1.83GB Disk_unallocated: 7.17GB Used: 284.00KB Free_(Estimated): 6.76GB (Max: 8.54GB, min: 4.96GB) Data_to_disk_ratio: 75 % Allocated_area: Data,RAID0: Size:921.75MB, Used:256.00KB /dev/vdc 307.25MB /dev/vdb 307.25MB /dev/vdd 307.25MB Data,Single: Size:8.00MB, Used:0.00 /dev/vdb 8.00MB System,RAID1: Size:8.00MB, Used:4.00KB /dev/vdd 8.00MB /dev/vdc 8.00MB System,Single: Size:4.00MB, Used:0.00 /dev/vdb 4.00MB Metadata,RAID1: Size:460.94MB, Used:24...