Created CLOUDSTACK-6225 and pushed a patch to verify libvirt version
and format before adding the allocate flag.
The bug also mentions the outstanding Ubuntu 12.04 issue.
On Tue, Mar 11, 2014 at 10:50 AM, Nux! wrote:
> On 11.03.2014 16:46, Marcus wrote:
>>
>> so it looks like preallocation only
On 11.03.2014 16:46, Marcus wrote:
so it looks like preallocation only works 1) on raw volumes, and 2) on
certain libvirt versions. I'll see if I can add those checks in,
assuming we really want to keep that flag.
That is true. Preallocation seems only for raw types.
This is what I see with lib
so it looks like preallocation only works 1) on raw volumes, and 2) on
certain libvirt versions. I'll see if I can add those checks in,
assuming we really want to keep that flag.
On Tue, Mar 11, 2014 at 10:36 AM, Marcus wrote:
> I see that the Ubuntu Cloud Archive revolves around providing
> Open
I see that the Ubuntu Cloud Archive revolves around providing
OpenStack packages. In fact, visiting the page
"https://wiki.ubuntu.com/ServerTeam/CloudArchive"; doesn't really give
me any indication of what to do if I just want to upgrade libvirt, it
wants me to choose a version of OpenStack. Are we
Now that I think about it a bit more, I'm not really interested in
hobbling ourselves until 2017 to support libvirt 0.9.8 on ubuntu
12.04. It's a bit easier with the RHEL/CentOS model, where they
deprecate their point releases and increment software versions on each
point release, so you're more of
The hard part is that there are so many libvirt versions and support
for very fundamental elements varies wildly. I'd like the community to
weigh in on it, I've felt for awhile that we should target a minimum
libvirt version in addition to the specific platforms. In a sense we
have, as in the past
On 03/09/2014 01:19 AM, Marcus wrote:
I imagine the new LTS will have it, but I'm not sure what our OS support
policy is.
Well, I think we should also keep supporting 12.04 since it's not EOL
until 2017.
But we can always say that we require the Ubuntu Cloud Archive to be used?
wido
On
I imagine the new LTS will have it, but I'm not sure what our OS support
policy is.
On Mar 8, 2014 11:59 AM, "Wido den Hollander" wrote:
>
>
> On 03/08/2014 12:32 AM, Marcus wrote:
>
>> On Fri, Mar 7, 2014 at 4:30 PM, Marcus wrote:
>>
>>> Hrm... sent instead of pasted. Commit
>>>
>>> commit 3989
On 08.03.2014 18:58, Wido den Hollander wrote:
On 03/08/2014 12:32 AM, Marcus wrote:
On Fri, Mar 7, 2014 at 4:30 PM, Marcus wrote:
Hrm... sent instead of pasted. Commit
commit 3989d6c48118f31464c87c71b6279a11eb13eb35
Author: Wido den Hollander
Date: Mon Feb 3 17:04:11 2014 +0100
kvm:
On 03/08/2014 12:32 AM, Marcus wrote:
On Fri, Mar 7, 2014 at 4:30 PM, Marcus wrote:
Hrm... sent instead of pasted. Commit
commit 3989d6c48118f31464c87c71b6279a11eb13eb35
Author: Wido den Hollander
Date: Mon Feb 3 17:04:11 2014 +0100
kvm: Resize volumes using libvirt
virsh blockresi
On Fri, Mar 7, 2014 at 4:30 PM, Marcus wrote:
> Hrm... sent instead of pasted. Commit
>
> commit 3989d6c48118f31464c87c71b6279a11eb13eb35
> Author: Wido den Hollander
> Date: Mon Feb 3 17:04:11 2014 +0100
>
> kvm: Resize volumes using libvirt
>
> virsh blockresize works on this system, so I
11 matches
Mail list logo
