tonci at suma-informatika.hr
Tue Feb 18 22:27:44 CET 2014
Hello to everybody
I still haven't figured out how to install (upgrade to) 3.2 beta
proxmoxm host ?
PLease help ... putting pvetest in sources.lst does not help at all
Can it be installed from scratch ?
thank you very much in advance
/srdačan pozdrav / best regards/
On 09.02.2014. 12:00, pve-user-request at pve.proxmox.com wrote:
> Send pve-user mailing list submissions to
> pve-user at pve.proxmox.com
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> pve-user-request at pve.proxmox.com
> You can reach the person managing the list at
> pve-user-owner at pve.proxmox.com
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pve-user digest..."
> Today's Topics:
> 1. Re: problems with 3.2-beta (Adam Thompson)
> Message: 1
> Date: Sat, 08 Feb 2014 12:43:50 -0600
> From: Adam Thompson <athompso at athompso.net>
> To: "pve-user at pve.proxmox.com" <pve-user at pve.proxmox.com>
> Subject: Re: [PVE-User] problems with 3.2-beta
> Message-ID: <52F67AE6.5020208 at athompso.net>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> On 14-02-02 12:00 PM, Adam Thompson wrote:
>> Overall, the Ceph GUI is great. I actually got Ceph up and running
>> (and working) this time! Syncing ceph.conf through corosync is such
>> an obvious way to simplify things... for small clusters, anyway.
>> I am seeing some problems, however, and I'm not sure if they're just
>> me, or if I should be opening bugs:
>> 1. I have one node that's up and running just fine, pvecm claims
>> everything's fine, but I can't migrate VMs that started somewhere else
>> to it - migration always fails, claiming the node is dead. Nothing
>> unusual appears in any logfile that I can see... or at least nothing
>> that looks bad to me. I can create a new VM there, migrate it
>> (online) to another node and migrate it back (online, again), but VMs
>> that were started on another node won't migrate.
>> 5. Stopping VMs with HA enabled is now an *extremely* slow process...
>> If I disable HA for a particular VM, I now notice that Stopping also
>> produces a Shutdown task, and it takes longer than previously, but not
>> unreasonably slow. I don't understand why Stop isn't instantaneous,
>> though. I notice that typing "stop" into a qm monitor also is slow...
>> the only way I have to rapidly stop a VM is to kill the KVM process
>> running it.
> FYI: Completely shutting down all four nodes (note: the last two refused
> to shutdown cleanly, I had to remove power) and rebooting them seems to
> have solved both these problems.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pve-user