sounds good!
thanks
2016-11-08 15:20 GMT-02:00 Kevin Lemonnier :
> On Tue, Nov 08, 2016 at 02:43:05PM -0200, Gilberto Nunes wrote:
> > HUm... I see So the safe procedure is move the disk and make dowtime,
> > make new VM in PVE 4.2, using the disk previously moved
On Tue, Nov 08, 2016 at 02:43:05PM -0200, Gilberto Nunes wrote:
> HUm... I see So the safe procedure is move the disk and make dowtime,
> make new VM in PVE 4.2, using the disk previously moved right??
>
I did this a lot, just prepare the VM before and just don't power it on,
poweroff on the
Hello list,
I migrated my home server to a VM last week (I used MondoRescue images
for the P2V process). Initially, everything seemed to work well. But for
the last few days, the VM has started to show a strange behaviour:
- sometimes right after boot, sometimes after several hours of
operation,
hum... that's a nice workaround but this is not my case... The structure is
different on both servers...
thanks anyway
2016-11-08 14:48 GMT-02:00 Fabrizio Cuseo :
> If you have exactly the same name schema for ethernet and storage, and you
> have the same storage shared
If you have exactly the same name schema for ethernet and storage, and you have
the same storage shared from both hosts, you can:
- power off the VM running on Host A
- copy the .conf file from host A to host B
- power on the VM on host B
- rename (safe) the .conf file on host A (to be sure that
You could always copy the /etc/pve/qemu-server/VMID.conf file from 4.3 to 4.2.
You would just need to update the location of the disk.
On 11/8/16, 11:43 AM, "pve-user on behalf of Gilberto Nunes"
wrote:
HUm... I
HUm... I see So the safe procedure is move the disk and make dowtime,
make new VM in PVE 4.2, using the disk previously moved right??
2016-11-08 14:41 GMT-02:00 Michael Rasmussen :
> On Tue, 8 Nov 2016 14:18:58 -0200
> Gilberto Nunes wrote:
>
> >
On Tue, 8 Nov 2016 14:18:58 -0200
Gilberto Nunes wrote:
> I need migrate one single VM to Promox 4.2.
> Proxmox 4.2 already has a GlusterFS storage.
> I already set this storage to Proxmox 4.3 and I am able to move disk from
> PVE 4.3 to PVE4.2, but I need migrate the
It could make the glusterfs storage accessible to the proxmox 4.3 node and
then move the disk or define a nfs server common to the two nodes and move
the disk.
2016-11-08 13:20 GMT-03:00 Gilberto Nunes :
> Oh I almost forget: I have about 30 VM's running now on
Oh I almost forget: I have about 30 VM's running now on Proxmox 4.3, so I
cannot stop this server, for any reason!
2016-11-08 14:18 GMT-02:00 Gilberto Nunes :
> Hi list
>
> I know that can de always discuss here but I need to be sure what I am
> intend to do.
> I have
Hi list
I know that can de always discuss here but I need to be sure what I am
intend to do.
I have a Proxmox 4.3 running and other server with Proxmox 4.2.
There is not any cluster between this servers
I need migrate one single VM to Promox 4.2.
Proxmox 4.2 already has a GlusterFS storage.
I
On 8-11-2016 13:20, Alexandre DERUMIER wrote:
Or would your patch become included in the regular proxmox..?
Yes. I have sent a patch this morning on the pve-devel mailing list.
Waiting for review.
Thanks!
___
pve-user mailing list
On 08/11/16 10:12, Dominik Csapak wrote:
if i understand you correctly, you want to achieve something like this:
vms:
Pool System:
vm 100 - 105
Pool Development:
vm 106 - 110
Pool Lab:
vm 111 - 115
Not exactly, what I want is to nest a pool inside another pool in order
to inherit the
>>Or would your patch become included in the regular proxmox..?
Yes. I have sent a patch this morning on the pve-devel mailing list.
Waiting for review.
- Mail original -
De: "lists"
À: "proxmoxve"
Envoyé: Mardi 8 Novembre 2016 10:44:07
Hi Daniel,
On 11/07/2016 09:01 PM, Daniel wrote:
> Hi there,
>
> i just tried to migrate a dedicated Host to a LXC container by simple rsync
> with —numeric-ids to keet it as it is.
>
> The VM it selfs starts and can be accessed by Console via Proxmox but no
> process is started.
> Anyone has
Hi Alexandre,
That would be super, i guess! (although you'd have to tell me also how
to apply the patch to our proxmox)
Or would your patch become included in the regular proxmox..?
The latter seems appropriate, since from what I understand, this is
something that also virt-manager does
On 11/08/2016 10:01 AM, Angel Docampo wrote:
Hello,
I would like to suggest a feature, or to know how do you do to (if you
do it), when want to add the VMs to more than a pool.
As an example, if I have several pools of VMs, say "Development",
"Systems" and "Lab", I would like to let some
Hello,
I would like to suggest a feature, or to know how do you do to (if you do it),
when want to add the VMs to more than a pool.
As an example, if I have several pools of VMs, say "Development", "Systems" and "Lab", I
would like to let some users/groups both from developer and system
On Mon, Nov 07, 2016 at 11:53:20AM +, Guy Plunkett wrote:
>> On 7 Nov 2016, at 11:50, Kevin Lemonnier wrote:
>>
>>> moving the /etc/pve/nodes/pve11/qemu-server/*.conf files to another node
>>> worked well. I didn't have to restart any services.
>>
>> Still, that seems
19 matches
Mail list logo