Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Gilberto Nunes 
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 right??
> >
>
> I did this a lot, just prepare the VM before and just don't power it on,
> poweroff on the 4.3 then just click start on the 4.2. I usually have less
> than 20 seconds of downtime doing it this way, no one never noticed.
> Depends on how much time your VM needs to boot of course, we only have
> Linux.
>
> --
> Kevin Lemonnier
> PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>


-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread 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 right??
> 

I did this a lot, just prepare the VM before and just don't power it on,
poweroff on the 4.3 then just click start on the 4.2. I usually have less
than 20 seconds of downtime doing it this way, no one never noticed.
Depends on how much time your VM needs to boot of course, we only have Linux.

-- 
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111


signature.asc
Description: Digital signature
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] VM CPU randomly pegged at 100%, clock goes bonkers

2016-11-08 Thread Philippe Andersson 
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, its CPU usage would reach 100% (the host itself and the other
VM are unaffected).

- login on the console is sometimes still possible with a lot of
patience, but in most cases it no longer responds

- NFS mount requests fail, but the VM still answers ping requests

- named dies with the following error message:

---
Nov 28 12:06:37 wopr kernel: [1267439601.897597] Clocksource tsc
unstable (delta = -161077616 ns)
Nov 28 12:06:37 wopr named[2338]: timer.c:708: fatal error:
Nov 28 12:06:37 wopr named[2338]: RUNTIME_CHECK(isc_time_now(()) ==
0) failed
Nov 28 12:06:37 wopr named[2338]: exiting (due to fatal error in library)
---

- the internal clock of the server becomes completely wrong (possibly by
tens of years)

There's usually nothing else to do but power off the VM and restart it.

PVE is version 4.1 on a HP Proliant DL380 Gen6.

The OS inside the VM is OpenSuSE 11.2 32bit (kernel 2.6.31.14-0.8-desktop).

I've started investigating this on the assumption that the message
"Clocksource tsc unstable" was the cause rather than a symptom. I've
implemented a workaround for it, but I don't know yet whether this alone
will resolve the issue.

Any idea as to what could cause this? Or other avenues that should be
explored? If you need more info about the setup, just ask.

Thanks in advance.

Best regards,

Ph. A.

-- 

*Philippe Andersson*
Unix System Administrator
IBA Particle Therapy |
Tel: +32-10-475.983
Fax: +32-10-487.707
eMail: p...@iba-group.com



___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Gilberto Nunes 
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 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 don't power
> on the vm running on host B).
>
> So, you can have a really short downtime.
>
> This is what i have done migrating vms from a 3.4 to a 4.0 running cluster.
>
> Regards, Fabrizio
>
>
> - Il 8-nov-16, alle 17:43, Gilberto Nunes gilberto.nune...@gmail.com
> ha scritto:
>
> > 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:
> >>
> >> > 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 running VM from PVE 4.3 to
> PVE
> >> > 4.2.
> >> >
> >> AFAIK this is not possible since pve 4.2 uses an older version of qemu.
> >>
> >> --
> >> Hilsen/Regards
> >> Michael Rasmussen
> >>
> >> Get my public GnuPG keys:
> >> michael  rasmussen  cc
> >> http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
> >> mir  datanom  net
> >> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
> >> mir  miras  org
> >> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
> >> --
> >> /usr/games/fortune -es says:
> >> I can resist anything but temptation.
> >>
> >> ___
> >> pve-user mailing list
> >> pve-user@pve.proxmox.com
> >> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >>
> >>
> >
> >
> > --
> >
> > Gilberto Ferreira
> > +55 (47) 9676-7530
> > Skype: gilberto.nunes36
> > ___
> > pve-user mailing list
> > pve-user@pve.proxmox.com
> > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> --
> ---
> Fabrizio Cuseo - mailto:f.cu...@panservice.it
> Direzione Generale - Panservice InterNetWorking
> Servizi Professionali per Internet ed il Networking
> Panservice e' associata AIIP - RIPE Local Registry
> Phone: +39 0773 410020 - Fax: +39 0773 470219
> http://www.panservice.it  mailto:i...@panservice.it
> Numero verde nazionale: 800 901492
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>



-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Fabrizio Cuseo 
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 don't power on 
the vm running on host B).

So, you can have a really short downtime.

This is what i have done migrating vms from a 3.4 to a 4.0 running cluster.

Regards, Fabrizio 


- Il 8-nov-16, alle 17:43, Gilberto Nunes gilberto.nune...@gmail.com ha 
scritto:

> 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:
>>
>> > 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 running VM from PVE 4.3 to PVE
>> > 4.2.
>> >
>> AFAIK this is not possible since pve 4.2 uses an older version of qemu.
>>
>> --
>> Hilsen/Regards
>> Michael Rasmussen
>>
>> Get my public GnuPG keys:
>> michael  rasmussen  cc
>> http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
>> mir  datanom  net
>> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
>> mir  miras  org
>> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
>> --
>> /usr/games/fortune -es says:
>> I can resist anything but temptation.
>>
>> ___
>> pve-user mailing list
>> pve-user@pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>>
> 
> 
> --
> 
> Gilberto Ferreira
> +55 (47) 9676-7530
> Skype: gilberto.nunes36
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-- 
---
Fabrizio Cuseo - mailto:f.cu...@panservice.it
Direzione Generale - Panservice InterNetWorking
Servizi Professionali per Internet ed il Networking
Panservice e' associata AIIP - RIPE Local Registry
Phone: +39 0773 410020 - Fax: +39 0773 470219
http://www.panservice.it  mailto:i...@panservice.it
Numero verde nazionale: 800 901492
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Chance Ellis 
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 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:
>
> > 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 running VM from PVE 4.3 to PVE
> > 4.2.
> >
> AFAIK this is not possible since pve 4.2 uses an older version of qemu.
>
> --
> Hilsen/Regards
> Michael Rasmussen
>
> Get my public GnuPG keys:
> michael  rasmussen  cc
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
> mir  datanom  net
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
> mir  miras  org
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
> --
> /usr/games/fortune -es says:
> I can resist anything but temptation.
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>


-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user



___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Gilberto Nunes 
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:
>
> > 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 running VM from PVE 4.3 to PVE
> > 4.2.
> >
> AFAIK this is not possible since pve 4.2 uses an older version of qemu.
>
> --
> Hilsen/Regards
> Michael Rasmussen
>
> Get my public GnuPG keys:
> michael  rasmussen  cc
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
> mir  datanom  net
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
> mir  miras  org
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
> --
> /usr/games/fortune -es says:
> I can resist anything but temptation.
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>


-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Michael Rasmussen 
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 running VM from PVE 4.3 to PVE
> 4.2.
> 
AFAIK this is not possible since pve 4.2 uses an older version of qemu.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
I can resist anything but temptation.


pgp3RvFQ_L2re.pgp
Description: OpenPGP digital signature
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Luis G. Coralle 
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 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 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 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 running VM from PVE 4.3 to PVE
> > 4.2.
> >
> > Do I need a cluster with this two servers???
> >
> > If I make a cluster I will able to safe remove PVE 4.2 from formed
> > cluster??
> >
> > I just wanna to be sure, çause I do not wanna mess up everthing!
> >
> > Thanks for any help
> >
> > --
> >
> > Gilberto Ferreira
> > +55 (47) 9676-7530
> > Skype: gilberto.nunes36
> >
> >
>
>
> --
>
> Gilberto Ferreira
> +55 (47) 9676-7530
> Skype: gilberto.nunes36
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>



-- 
Luis G. Coralle
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Safe remove node from cluster...

2016-11-08 Thread Gilberto Nunes 
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 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 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 running VM from PVE 4.3 to PVE
> 4.2.
>
> Do I need a cluster with this two servers???
>
> If I make a cluster I will able to safe remove PVE 4.2 from formed
> cluster??
>
> I just wanna to be sure, çause I do not wanna mess up everthing!
>
> Thanks for any help
>
> --
>
> Gilberto Ferreira
> +55 (47) 9676-7530
> Skype: gilberto.nunes36
>
>


-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] Safe remove node from cluster...

2016-11-08 Thread 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 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 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 running VM from PVE 4.3 to PVE
4.2.

Do I need a cluster with this two servers???

If I make a cluster I will able to safe remove PVE 4.2 from formed cluster??

I just wanna to be sure, çause I do not wanna mess up everthing!

Thanks for any help

-- 

Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

2016-11-08 Thread lists 


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
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Hierarchical pools

2016-11-08 Thread Angel Docampo 

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 permissions of the father into the child, like this:
   /---> root, where 
Administrator has all the permissions.
   /pool/Development   ---> root of the "Development" pool, 
where root and selected people/groups can access with custom permissions
   /pool/Development/Lab---> "Lab" subpool, where inherited 
permissions from "Development" pool can access, and add some others like 
group "System"
   /pool/Systems   ---> root of "Systems" pool, 
where root and selected people/groups can access with custom permissions



In this way, we can inherit permissions from the parent pool without the 
need of specify permissions in each and every pool, simplifying the 
management of pools greatly.
Furthermore, on Datacenter --> Permissions --> Add, I can see a checkbox 
called "propagate", which seems to mean that we can avoid to inherit the 
permissions on the subpools, but we can only create pools on the first 
level... which IMO seems that proxmox is ready to inherit permissions on 
pools and nest pools but is not yet implemented (in fact, we can 
actually create a permission on Datacenter --> Permissions --> Add, and 
specify the path /pool/Develepment/Lab, but it does not appear as a 
pool, and it cannot be deleted! :S )


Hope I have explained better now. What do you think?

Best,

--


*Angel Docampo
*
*Datalab Tecnologia, s.a.*
Castillejos, 352 - 08025 Barcelona
Tel. 93 476 69 14 - Ext: 114
Mob. 670.299.381

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

2016-11-08 Thread Alexandre DERUMIER 
>>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
Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

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 automatically. 
(https://github.com/virt-manager/virt-manager/commit/cbba1c4dd381) 

Anyway: much appreciated, thanks! 

MJ 

On 8-11-2016 0:42, Alexandre DERUMIER wrote: 
> I can make a patch for this. 
> 
> 
> - Mail original - 
> De: "lists"  
> À: "proxmoxve"  
> Envoyé: Lundi 7 Novembre 2016 20:36:35 
> Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM 
> 
> Just to add to my own question: 
> 
> To disable HyperV enlightments you have to make sure that these options 
> are NOT set: 
> 
> "hv_time,hv_relaxed,hv_spinlocks=0x2000" 
> 
> Can anyone tell me how to do / where to check that in proxmox? 
> 
> MJ 
> 
> On 7-11-2016 18:50, lists wrote: 
>> Hi, 
>> 
>> We are trying to migrate a win7 uefi machine into proxmox, and so far 
>> we're failing. Done a lot of reading, and what seems to be the problem: 
>> 
>> https://bugs.launchpad.net/qemu/+bug/1593605 
>> 
>> My conclusion ius that we should be able to run win7/uefi on qemu, but 
>> we need to disable the disable HyperV enlightments. 
>> 
>> And this is where we're stuck now, google tells me numerous to ENABLE 
>> them, for example: 
>> 
>>> virt-xml $VMNAME --edit --features 
>>> hyperv_relaxed=on,hyperv_vapic=on,hyperv_spinlocks=on,hyperv_spinlocks_retries=8191
>>>  
>>> 
>> 
>> But proxmox does not know virt-xml, and we need to DISABLE them, using 
>> (what we understand) cpu flags. 
>> 
>> Could someone help us in the right direction? 
>> 
>> MJ 
>> ___ 
>> pve-user mailing list 
>> pve-user@pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> ___ 
> pve-user mailing list 
> pve-user@pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> 
> ___ 
> pve-user mailing list 
> pve-user@pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> 
___ 
pve-user mailing list 
pve-user@pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Migrate dedicates host to LXC container

2016-11-08 Thread Alwin Antreich 
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 an idea what can happen? Folders like proc and dev still exists on 
> the container.

Try this article, the conversion worked for me on a openSuSe.
https://www.snikt.net/blog/2014/03/22/convert-kvm-image-to-lxc-container/

> 
> Cheers
> 
> Daniel
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> 

-- 
Cheers,
Alwin
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

2016-11-08 Thread lists 

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 automatically.

(https://github.com/virt-manager/virt-manager/commit/cbba1c4dd381)

Anyway: much appreciated, thanks!

MJ

On 8-11-2016 0:42, Alexandre DERUMIER wrote:

I can make a patch for this.


- Mail original -
De: "lists" 
À: "proxmoxve" 
Envoyé: Lundi 7 Novembre 2016 20:36:35
Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

Just to add to my own question:

To disable HyperV enlightments you have to make sure that these options
are NOT set:

"hv_time,hv_relaxed,hv_spinlocks=0x2000"

Can anyone tell me how to do / where to check that in proxmox?

MJ

On 7-11-2016 18:50, lists wrote:

Hi,

We are trying to migrate a win7 uefi machine into proxmox, and so far
we're failing. Done a lot of reading, and what seems to be the problem:

https://bugs.launchpad.net/qemu/+bug/1593605

My conclusion ius that we should be able to run win7/uefi on qemu, but
we need to disable the disable HyperV enlightments.

And this is where we're stuck now, google tells me numerous to ENABLE
them, for example:


virt-xml $VMNAME --edit --features
hyperv_relaxed=on,hyperv_vapic=on,hyperv_spinlocks=on,hyperv_spinlocks_retries=8191



But proxmox does not know virt-xml, and we need to DISABLE them, using
(what we understand) cpu flags.

Could someone help us in the right direction?

MJ
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Hierarchical pools

2016-11-08 Thread Dominik Csapak 

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 users/groups both from
developer and system groups to control the VMs from pool "Lab" with some
elevated privileges like poweroff, CDROM, etc to install and configure
the VM before entering production.

I cannot see how to acomplish this, because one reource (VM/storage) can
belong only to one Pool. As far as I can see, there are two options, let
the pools be hierarchical or let the resources belong to more than one
pool.


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


Users:

user  1 - 10 : access to system
user 11 - 20: access to development
user 21 - 30: access to lab


now you want user 5 and 15 grant access to "lab" machines?

i would do it like this:

create for each pool a user group (under datacenter -> Permissions -> 
groups)


grant each group the right permissions (under datacenter -> permissions)

and now add the group for system to user 1 -10 and so on
but also add the lab group to user 5 and 15

is this what you wanted?

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] Hierarchical pools

2016-11-08 Thread Angel Docampo 

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 groups to control the VMs from pool "Lab" 
with some elevated privileges like poweroff, CDROM, etc to install and configure the VM before entering production.

I cannot see how to acomplish this, because one reource (VM/storage) can belong 
only to one Pool. As far as I can see, there are two options, let the pools be 
hierarchical or let the resources belong to more than one pool.

Can this feature be useful enough to suggest it to the Proxmox team? Anyone 
achieve this with some workaround I didn't thought?

Best,

--
[cid:part1.74F14D67.C6327600@dltec.net]

Angel Docampo
Datalab Tecnologia, s.a.
Castillejos, 352 - 08025 Barcelona
Tel. 93 476 69 14 - Ext: 114
Mob. 670.299.381


Nota Legal
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] How to move VM from dead node?

2016-11-08 Thread Fabian Grünbichler 
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 like a fairly usual operation that the GUI could
>> very well support, I think.
>> Would it be possible to add that in the future ?
>it would also be nice for the GUI not to lose the details of the VMs if the 
>node is down, and indeed allow the transfer of the VM to an active node.
>
>I know this can be done today with the HA but it would be nice to also do this 
>for non HA VMs

the problem is that PVE has a notion of nodes being owners of their
respective ressources (like containers or VMs). the technical background
is that we only allow changes to their configuration in processes
holding a node-local lock, to prevent race conditions and conflicts.
cluster-wide locking is very expensive, and is thus only used when
absolutely needed (like allocating/freeing disk images on shared
storage).

a consequence of this architectural design is that node A cannot "steal"
a VM/container (or rather, its configuration file) from another node B,
because there is no way for a process on node A to lock this file (only
node B is able and allowed to locally lock and modify it). the only
exception to this is for HA-managed ressources, because our HA stack
has a system of cluster-wide locking and watchdogs to ensure that it
only steals ressources from actually dead nodes (and in a conflict-free
manner).

so there are only three options:
- use HA for automatic migration on node failure
- move the configuration files manually as root when a node has died,
  and take the blame if you moved from a node that was not actually dead
  (in which case you violated one of the basic assumptions of PVE and
  "anything" might happen)
- change this architectural design (not likely, as it is one of the
  basic principles of PVE's clustering ;))

I hope this makes it clear why this case is handled like it is, and that
it's not some arbitrary unwillingness to add this functionality to the
API/GUI ;)

p.s. top-posting makes email threads rather hard to follow, please
consider switching to in-line replies or bottom-posting

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user