>>Certainly restart (shutting down qemu and restarting it, not a reset) >>works, I thought you wanted online resize. You can resize an lvm volume online without restarting the guest. just use lvextend to extend you lvm volume then use qmp block_resize command with the same size. (so the guest will see the new size) I have implemented this in the proxmox kvm distribution, and it's working fine. (tested with virtio-blk and virtio-scsi) ----- Mail original ----- De: "Avi Kivity" <avi@xxxxxxxxxx> À: "Ross Boylan" <ross@xxxxxxxxxxxxxxxx> Cc: kvm@xxxxxxxxxxxxxxx Envoyé: Mercredi 5 Septembre 2012 09:25:26 Objet: Re: expanding virtual disk based on lvm On 09/04/2012 09:58 PM, Ross Boylan wrote: > On Tue, 2012-09-04 at 15:53 +0300, Avi Kivity wrote: >> On 08/28/2012 11:26 PM, Ross Boylan wrote: >> > My vm launches with -hda /dev/turtle/VD0 -hdb /dev/turtle/VD1, where VD0 >> > and VD1 are lvm logical volumes. I used lvextend to expand them, but >> > the VM, started after the expansion, does not seem to see the extra >> > space. >> > >> > What do I need to so that the space will be recognized? >> >> IDE (-hda) does not support rechecking the size. Try booting with >> virtio-blk. Additionally, you may need to request the guest to rescan >> the drive (no idea how to do that). Nor am I sure whether qemu will >> emulate the request correctly. >> > Thank you for the suggestion. > > I think the "physical" recognition of the new virtual disk size was > accomplished when I restarted the VM, without any other steps. I've had > plenty of other problems, but I think at the VM level things are good. Certainly restart (shutting down qemu and restarting it, not a reset) works, I thought you wanted online resize. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
