Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

How to refresh lvm-backed virtual disk in libvirt

+1
−0

How can I grow a libvirtd VM's LVM-backed virtual disk online, without rebooting the vm.

My host has an LVM VG for VMs. Each VM disk is an LV to the host.

It's easy to grow the VG by adding a PV and extending the LV. But the VM doesn't "see" the new space without rebooting.

How can I get the VM to see the larger space without rebooting the VM?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+1
−0

virsh blockresize vmname diskname --size 123b

vmname is the name of the "domain" in libvirt parlance. diskname is the name inside /dev int the vm. vda or vdb for instance. 123 should be the exact number of bytes of the newly expanded block device that hosts this virtual disk.

First, obtain the size of that device with blockdev --getsize64 /dev/vg_somehting/lv_vm_something

That will give you an integer in bytes

Then run the virsh command with that byte number and the suffix b.

As of 2023-02, there is no way arround having to tell virsh blockresize the new size yourself. Historically the reason it had a --size argument is that it actually performed the resize of a virtual disk file or qcow file to the size you specified.

It will not modify the size of an lvm lv. But you still have to tell it the size.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »