<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello to everybody <br>
<br>
I still haven't figured out how to install (upgrade to) 3.2 beta
proxmoxm host ?<br>
<br>
PLease help ... putting pvetest in sources.lst does not help at
all <br>
<br>
Can it be installed from scratch ?<br>
<br>
thank you very much in advance <br>
<br>
and <br>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<title></title>
<br>
<small><i><span style="font-family: Helvetica, sans-serif; "><br>
</span></i></small>
<div><small><i><span style="font-family: Helvetica, sans-serif;
">srdačan pozdrav / best regards</span></i></small><br>
<div class="moz-signature">
<div class="moz-signature"><br>
<div class="moz-signature">
<div class="moz-signature">
<div class="moz-signature"><font face="Helvetica,
Arial, sans-serif">Tonči Stipičević</font><br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
On 09.02.2014. 12:00, <a class="moz-txt-link-abbreviated" href="mailto:pve-user-request@pve.proxmox.com">pve-user-request@pve.proxmox.com</a> wrote:<br>
</div>
<blockquote
cite="mid:mailman.3.1391943601.336.pve-user@pve.proxmox.com"
type="cite">
<pre wrap="">Send pve-user mailing list submissions to
<a class="moz-txt-link-abbreviated" href="mailto:pve-user@pve.proxmox.com">pve-user@pve.proxmox.com</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="moz-txt-link-freetext" href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user</a>
or, via email, send a message with subject or body 'help' to
<a class="moz-txt-link-abbreviated" href="mailto:pve-user-request@pve.proxmox.com">pve-user-request@pve.proxmox.com</a>
You can reach the person managing the list at
<a class="moz-txt-link-abbreviated" href="mailto:pve-user-owner@pve.proxmox.com">pve-user-owner@pve.proxmox.com</a>
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 <a class="moz-txt-link-rfc2396E" href="mailto:athompso@athompso.net"><athompso@athompso.net></a>
To: <a class="moz-txt-link-rfc2396E" href="mailto:pve-user@pve.proxmox.com">"pve-user@pve.proxmox.com"</a> <a class="moz-txt-link-rfc2396E" href="mailto:pve-user@pve.proxmox.com"><pve-user@pve.proxmox.com></a>
Subject: Re: [PVE-User] problems with 3.2-beta
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:52F67AE6.5020208@athompso.net"><52F67AE6.5020208@athompso.net></a>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 14-02-02 12:00 PM, Adam Thompson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">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.
</pre>
</blockquote>
<br>
</body>
</html>