Hi Kirk and all,
I managed to resolve the problem, I am now able to resize the volume
provided that I follow below steps:
- stop the VM;
- detach the volume from the VM;
- resize the volume;
- re-attach the volume;
- restart the VM.
Both upgrade and downgrade work fine now. Many thanks for your
Dear Marcus, Kirk and all,
Any further recommendations on how can I troubleshoot on this matter to
pinpoint the cause of the inability to resize the disk, and to find the
solution to the problem?
Looking forward to your reply, thank you.
Cheers.
On Fri, Oct 4, 2013 at 3:30 PM, Indra Pramana
Hi Marcus and Kirk,
Good day to you, and thank you for your email replies.
We are using Ceph RBD primary storage. I can't find any error information
on agent.log, and I have set the logging to verbose (DEBUG) for all.
Since I am using RBD, am I still able to run the qemu-img info command?
I che
What primary storage are you using? Any errors in agent log?
On Oct 3, 2013 3:16 PM, "Indra Pramana" wrote:
> Hi Marcus,
>
> Good day to you, and thank you for your e-mail.
>
> I have tried restarting the VM and even stop and start the VM, but after
> logging in to the VM, I still see the hard dr
Hi Marcus,
Good day to you, and thank you for your e-mail.
I have tried restarting the VM and even stop and start the VM, but after
logging in to the VM, I still see the hard drive's size as 20 GB instead of
60 GB.
I tried to check /var/log/libvirt/libvirtd.log file on the KVM host where
the VM
I just tested local storage qcow2 and CLVM resize on 4.2, they both worked.
Resize works like this:
1. Do sanity checks
2. Send resize command to the agent
3. Resize the disk/lun/file
4. Inform the VM instance that the disk has changed by making a
libvirt volBlockResize call (this is not fatal, s
