search for: vdc

...in meta sn1 --diskspec vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only --atomic --no-metadata Then I successfully blockcommitted 2 disks: virsh blockcommit meta vda --active --verbose --pivot virsh blockcommit meta vdb --active --verbose --pivot But when doing virsh blockcommit meta vdc --active --verbose --pivot I got: Block commit: [100 %]error: failed to pivot job for disk vdc error: block copy still active: disk 'vdc' not ready for pivot yet Domain snapshot sn1 created And now it looks like this: virsh domblklist meta Target Source --------------------------------...

...belled > > "xyz"". > > > > So nothing related to filesystem but gpt labels & disks. > > > > > For comparison - option "label" - GPT Partition name selection, > working as expected > > SeaBIOS / SYSLINUX > > # gdisk -l /dev/vdc > ... > Partition table scan: > MBR: protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > Disk /dev/vdc: ... > ... > Number Start (sector) End (sector) Size Code Name > 1...

Hello everyone, I'm unable to read temperature Gigabyte H77-DH3H motherboard. Is that motherboard supported or am I doing it incorrectly? When trying to access hw.acpi.thermal everything appears to be ok, but it is not, the system always returns 27,8C and 29,8C which fooled me initially - the values never change. Here is output: [chinatsu]:/root# sysctl hw.acpi.thermal

Nerijus Baliunas <nerijus@...> writes: > How do I make vdc to be the initial disk, not the snapshot one? I powered off the VM, with "virsh edit meta" changed vdc source file from meta-pgsql.sn1 to meta-pgsql.qcow2 and started VM. Is it possible to achieve this without powering off VM? Thanks, Nerijus

.../ + /* virtio_add_feature(&features, VIRTIO_F_VERSION_1); */ + return features; +} + static void virtio_blk_set_status(VirtIODevice *vdev, uint8_t status) { VirtIOBlock *s = VIRTIO_BLK(vdev); @@ -821,6 +839,7 @@ static void virtio_blk_class_init(ObjectClass *klass, void *data) vdc->get_config = virtio_blk_update_config; vdc->set_config = virtio_blk_set_config; vdc->get_features = virtio_blk_get_features; + vdc->get_features_rev = virtio_blk_get_features_rev; vdc->set_status = virtio_blk_set_status; vdc->reset = virtio_blk_reset;...

.../ + /* virtio_add_feature(&features, VIRTIO_F_VERSION_1); */ + return features; +} + static void virtio_blk_set_status(VirtIODevice *vdev, uint8_t status) { VirtIOBlock *s = VIRTIO_BLK(vdev); @@ -821,6 +839,7 @@ static void virtio_blk_class_init(ObjectClass *klass, void *data) vdc->get_config = virtio_blk_update_config; vdc->set_config = virtio_blk_set_config; vdc->get_features = virtio_blk_get_features; + vdc->get_features_rev = virtio_blk_get_features_rev; vdc->set_status = virtio_blk_set_status; vdc->reset = virtio_blk_reset;...

The idea is to boot a disk in an mbr fashion while using the GPT (not filesystem) label to detect the disk. That is useful when you use grub2 & gpt. I was in case where my nodes (100s) have 8 disks each and no guarantee of which disk is "bootable" in the disk. This way I can tell "please boot the disk that have one partition labelled "xyz"". So nothing related

...es, VIRTIO_F_VERSION_1); */ > + return features; > +} > + > static void virtio_blk_set_status(VirtIODevice *vdev, uint8_t status) > { > VirtIOBlock *s = VIRTIO_BLK(vdev); > @@ -821,6 +839,7 @@ static void virtio_blk_class_init(ObjectClass *klass, void *data) > vdc->get_config = virtio_blk_update_config; > vdc->set_config = virtio_blk_set_config; > vdc->get_features = virtio_blk_get_features; > + vdc->get_features_rev = virtio_blk_get_features_rev; > vdc->set_status = virtio_blk_set_status; > vdc->reset...

...es, VIRTIO_F_VERSION_1); */ > + return features; > +} > + > static void virtio_blk_set_status(VirtIODevice *vdev, uint8_t status) > { > VirtIOBlock *s = VIRTIO_BLK(vdev); > @@ -821,6 +839,7 @@ static void virtio_blk_class_init(ObjectClass *klass, void *data) > vdc->get_config = virtio_blk_update_config; > vdc->set_config = virtio_blk_set_config; > vdc->get_features = virtio_blk_get_features; > + vdc->get_features_rev = virtio_blk_get_features_rev; > vdc->set_status = virtio_blk_set_status; > vdc->reset...

..."please boot the disk that have one partition labelled > "xyz"". > > So nothing related to filesystem but gpt labels & disks. > For comparison - option "label" - GPT Partition name selection, working as expected SeaBIOS / SYSLINUX # gdisk -l /dev/vdc ... Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/vdc: ... ... Number Start (sector) End (sector) Size Code Name 1 2048 6143 2.0 MiB EF02 BIOS_Boot...

> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/> > <boot order='4'/> > ... > ... > > > # gdisk -l /dev/vdc > ... > Partiti...

...> > >> > So nothing related to filesystem but gpt labels & disks. >> > >> >> >> For comparison - option "label" - GPT Partition name selection, >> working as expected >> >> SeaBIOS / SYSLINUX >> >> # gdisk -l /dev/vdc >> ... >> Partition table scan: >> MBR: protective >> BSD: not present >> APM: not present >> GPT: present >> >> Found valid GPT with protective MBR; using GPT. >> Disk /dev/vdc: ... >> ... >> Number Start (sector) End (s...

...t # btrfs fi df /mnt Data: total=315.19MB, used=250.58MB System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=153.56MB, used=364.00KB Metadata: total=8.00MB, used=0.00 Again, much as expected. Now, add in a second device, and balance: # btrfs dev add /dev/vdc /mnt # btrfs fi bal /mnt # btrfs fi df /mnt Data, RAID0: total=1.20GB, used=250.58MB System, RAID1: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=128.00MB, used=308.00KB This is bad, though. Data has reverted to RAID-0. Now, just to check, what happens whe...

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

Hello, it happened with another VM: # virsh snapshot-create-as --domain rasa sn1 --diskspec vda,file=/var/lib/libvirt/images/rasa-sn1.qcow2 --disk-only --atomic --no-metadata # virsh blockcommit rasa vda --active --verbose --pivot Block commit: [100 %]error: failed to pivot job for disk vda error: block copy still active: disk 'vda' not ready for pivot yet # virsh domblklist rasa

Nerijus Baliunas <nerijus@...> writes: > But trying to virsh blockcommit rasa vda --active --verbose --pivot once more: > error: block copy still active: disk 'vda' already in active block job > > How do I make rasa.qcow2 the only active vda? "virsh blockjob rasa vda --abort" aborts the blockcommit and then I can try to blockcommit again: # virsh blockjob

...ne Help department. Thanks for shopping at Amazon.com! Sincerely, Amazon.com Customer Service http://www.amazon.com P.S. You received this message because Amazon.com received the following message: >From r-help at lists.r-project.org Wed Sep 22 17:03:56 2004 Received: from mail-border-1001.vdc.amazon.com (mail-border-1001.vdc.amazon.com [10.139.9.251]) by mail-admin-1.amazon.com (8.12.7/) with ESMTP id i8N03jsQ016597 for <account-update-autoresponse at mail-admin-1.amazon.com>; Wed, 22 Sep 2004 17:03:46 -0700 Received: from service-5-internal.amazon.com by mail-border-1001.vdc.am...

...milliseconds validflag: value of 0 indicates a valid track and a periodic signal, and a value less than 0 indicates either a lost track, a bad video signal, or a non periodic signal ttlin: is the bit value indicating the status of a sensed TTL signal. Possible values include 1 (+5 VDC) and 0 (0 VDC). mark: specifies the sample when the phase value is closest to 0 or PI (180 degrees) . Possible values include Z (0 phase), P (PI phase), "" (null string), and - (neither 0 nor PI phase) ttl_out: is the bit value indicating the status of an output TTL signal....

...16 17:21, Ady Ady via Syslinux wrote: >> >> As opposed to "label", >> "dlabel" ... >> https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf >> >> SeaBIOS / GRUB2 >> >> ... >> ... >> <target dev='vdc' bus='virtio'/> >> <boot order='3'/> >> ... >> ... >> <target dev='vdd' bus='virtio'/> >> <boot order='4'/> >> ... >> ... >> >> >> # g...

...for ghigo: Path: /mnt/btrfs1 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,RAID...