On 05/19/2015 03:29 PM, Mathew Moon wrote:
> Hi,
>
> Sorry about top-posting, didn't know it was a nuisance. As for
It's okay - we were all new once.
> developing,
> I wish I could but I have never spent any time coding in c, c++, etc. I
> am a systems guy, not a developer, so I only wor
Hi,
Sorry about top-posting, didn't know it was a nuisance. As for
developing,
I wish I could but I have never spent any time coding in c, c++, etc. I
am a systems guy, not a developer, so I only work with scripting languages.
I would love to have the tech chops to contribute though. If I
On 05/19/2015 02:41 PM, Mathew Moon wrote:
> Hi Eric,
[please don't top-post on technical lists]
>
> Thanks for the info. I see the value in this, but it isn't quite what I was
> looking for. Basically what I want to do is to switch between snapshots
> quickly. For instance, I am currently worki
On 05/19/2015 03:06 PM, Mathew Moon wrote:
> It seems that my version of libvirt does not support the flags that yours
> does either. I have the latest version from the Ubuntu repos and am running
> 14.04. What version are you running and do you know if these features
> depend on libvirt, or qemu-i
It seems that my version of libvirt does not support the flags that yours
does either. I have the latest version from the Ubuntu repos and am running
14.04. What version are you running and do you know if these features
depend on libvirt, or qemu-img to be upgraded?
===
Hi Eric,
Thanks for the info. I see the value in this, but it isn't quite what I was
looking for. Basically what I want to do is to switch between snapshots
quickly. For instance, I am currently working on designing a HA SQL
implementation with failover. So right now I have 5 VM's running postgres
On 05/19/2015 12:52 PM, Mathew Moon wrote:
> Hi,
>
> Is it possible to "pivot" to a new image without doing blockcopy or
> blockpull?
No. Qemu does not support arbitrary reopening of a backing chain yet
(even with the 'change-backing-file' QMP command, that is just rewriting
contents of the qcow2
Hi,
Is it possible to "pivot" to a new image without doing blockcopy or
blockpull? I know how to use snapshots and blockpull to create a new image
and pivot to using it live, but what I would like to do is to have a VM
switch from using imageA.qcow2 to image2.qcow2 while running. I don't see
why t
I wrote:
1. Let's say I assign 4GB of RAM to each guest and that the network
has 20 running guests at any given time, should the server have at
least 80GB (20 by 4) of RAM or can I "oversell" a bit and bet on the
fact that only few guests will actually use 4GB?
I've found the answer to this q