Changed the name via hostname but in the Datacenter
i see the already existent VM mapped on the oldnode
and the new mapped on the new renamed node.
I think that this information will be stored on /etc/pve/.members
but it/s unchangeable...
Tx, Diaolin
Yeah, seen before writing here.
This mean that i should change the method or simply add the quorum disk to the existing
proxmoxve2.0 config?
Tx, DIaolin
My opinion is only that if i am in a tree i have the property from the point assigned to me
but i cannot destroy that point because this is a property of the container and not of the
point itself.
But this is only my opinion.
Diaolin
Too simple!
It-s like removing a file in a directory, if i don-t have write permission in the dir but
complete write permission on the file i cannot remove it.
But, as you say, a user should not do that!
:-)
Diaolin
Just for fun:
i created a user
and in the left pane clicked on a VM
added Administrator permission to that user for the VM
Logged on as user and removed the permission...
I think that this is correct but seeing this from a Unix perspective the
Administrator access to a particular server...
Ok, but only next week...
when done i'll post the result?
In your test system did you have success with the venet?
Another question on this problem: do you thin that there can be a problem with networking?
I've found the machine on the other node but it was not started it was in stopped state...
Two machines with a central nfs on another machine...
the template il debian6.0 from your site...
the kvm migration is ok and i use always the same nfs.
Just for understanding: i migrate openvz online and the machine stops... after migration and doesn't resume.
Only starting manually....
Tx
Tested with a shared nfs but the online option does not work.
Migrating the openvz machine is all ok but not the Online option The transferred machine stays down...
Diaolin
In many cases happens that, during backup, vzdump using snapshot exits with error 5...
and the the snapshot partition will not be umounted due to it-s busy state.
Locate (updatedb) is the guilty program!
It happens that if updatedb is running the mount point can be busy and despite
the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.