Hi Emmanuel,
El 02/02/17 a las 17:09, Emmanuel Kasper escribió:
It seem's Proxmox will fail to start a VM of Windows 10/2016 type and
more than 2 GB RAM?
I recall something about this in the mailing list, and have changed the
type to Windows 8 and it works, but I was surprised this is not yet
Hello,
in case you're experiencing very bad synchronised disk I/O
performance (like when updating/installing debian packages) in
QEMU guests, and you're using qcow2 disk images stored on ZFS
file systems, you may want to watch this thread on the QEMU
devel mailing list:
Hi Eneko,
> It seem's Proxmox will fail to start a VM of Windows 10/2016 type and
> more than 2 GB RAM?
> I recall something about this in the mailing list, and have changed the
> type to Windows 8 and it works, but I was surprised this is not yet
> fixed in non-subscription repo :)
>
Which
On Thu, Feb 02, 2017 at 10:55:25AM +0100, Florent B wrote:
> Hi everyone,
>
> On a testing cluster, I have a problem when I destroy some VM, sometimes
> the task is "OK" but VM disk is not removed on RBD.
this is https://bugzilla.proxmox.com/show_bug.cgi?id=1063 , for which I
sent a v1 patch set
Would make sense to have TASK WARN maybe - that would certainly make
you check backup the output. Or perhaps try to delete the disk first,
if that fails then do nothing else in the task.
Are you using KRBD? Its usually the RBD being mounted with the kernel
module on a different box than the one
Hi,
just answering the additional question, the rest may get better answered
by our community.
On 02/02/2017 10:22 AM, Uwe Sauter wrote:
Hi all,
I would like to hear recommendations regarding the network setup of a Proxmox
cluster. The situation is the following:
* Proxmox hosts have
Hi all,
I would like to hear recommendations regarding the network setup of a Proxmox
cluster. The situation is the following:
* Proxmox hosts have several ethernet links
* multiple VLANs are used in our datacenter
* I cannot guarantee that the VLANs are on the same interface for each host
In my PVE installation (2 clusters, now one standalone) when backup
start i got:
Jan 26 15:16:37 magneto pvestatd[2120]: got timeout
Jan 26 15:16:47 magneto pvestatd[2120]: got timeout
Jan 26 15:19:21 magneto pvestatd[2120]: got timeout
Jan 26 15:50:53 magneto pvestatd[2120]: storage
