--- Begin Message ---
On Sunday, May 17, 2020 11:35 AM, leesteken--- via pve-user
wrote:
> On Sunday, May 17, 2020 10:49 AM, prox...@elchaka.de wrote:
>
> > I am not sure if this is working with lxc...
> > In Addition die you set hotplug enabled for CPU under options throu
--- Begin Message ---
On Sunday, May 17, 2020 10:49 AM, wrote:
> I am not sure if this is working with lxc...
> In Addition die you set hotplug enabled for CPU under options through the
> webgui for you container? I See this for all of my kvm...
>
I don't see any hotplug options for LXC, only
--- Begin Message ---
Apologies for replying to myself, but I have a litte more information.
‐‐‐ Original Message ‐‐‐
On Tuesday, May 12, 2020 1:12 PM, wrote:
> Hi PVE-users,
>
> Lately, on a no-subscription Proxmox (that I update regularly since release
> 6.0), I get the following
--- Begin Message ---
Hi PVE-users,
Lately, on a no-subscription Proxmox (that I update regularly since release
6.0), I get the following error when changing the CPU limit of any
(unpriviliged) container:
Parameter verification failed. (400)
cpulimit: unable to hotplug cpulimit: unable to
um=email_source=link_campaign=sig-email_content=webmail)
>
> #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
>
> El mar., 7 abr. 2020 a las 16:12, leesteken--- via pve-user
> () escribió:
>
>> -- Forwarded message --
>> From: leeste...@pm.me
>> To: PVE User List
&
--- Begin Message ---
‐‐‐ Original Message ‐‐‐
On Tuesday, April 7, 2020 8:58 PM, Leandro Roggerone
wrote:
> Hi guys , Im running windows server 2012.
> After doing process described here:
> http://www.kieranlane.com/2013/09/18/resetting-administrator-password-windows-2012/
> for
--- Begin Message ---
‐‐‐ Original Message ‐‐‐
On Friday, April 3, 2020 8:19 PM, System Administrator via pve-user
wrote:
> Hello,
>
> I have installed the latest Proxmox VE 6.1-2 and when modifying network
Maybe upgrading to the latest (non-subscription) version 6.1-8 using apt-get
--- Begin Message ---
‐‐‐ Original Message ‐‐‐
On Friday, March 20, 2020 12:46 PM, Mark Adams via pve-user
wrote:
> Hi All,
>
> I am having the issue that is detailed in this forum post:
>
> https://forum.proxmox.com/threads/vm-start-timeout-with-pci-gpu.45843/
>
> I thought I
--- Begin Message ---
Removing the ExecStart (and ExecStop) lines that contain --allow=ovs indeed
fixed the issue.
I don't have any OVS packages installed, which is probably why it triggered on
my setup.
I'll revert the changes, use 'systemctl reset-failed networking.service' as a
work-around
--- Begin Message ---
Dear Proxmox user list,
My network and internet connections work fine but I'm getting a "State:
degraded" from systemctl status,
since an apt-get dist-upgrade yesterday. That Proxmox (6.1-7) update did
rewrite my /etc/network/interface
configuration file, but it looked
--- Begin Message ---
‐‐‐ Original Message ‐‐‐
On Friday, February 28, 2020 1:36 PM, Thomas Naumann wrote:
> unfortunatly there is no independent third location
Are you physically located in one of the two datacenters? Then run it there.
Otherwise, run a QDevic at the same location
--- Begin Message ---
‐‐‐ Original Message ‐‐‐
On Monday, February 10, 2020 4:49 PM, Gerald Brandt wrote:
> Hi,
>
> I have a small cluster of 4 servers. One server in the cluster seems to
> be having an issue. For the last two weeks, one or two of the VMs seem
> to psuedo lock up over
--- Begin Message ---
On Monday, February 3, 2020 12:42 PM, Marco Gaiarin wrote:
>
> I've done a fresh installation of PVE6 (6.1) on an old HP ProLiant ML110
> G6 (CPU Intel(R) Xeon(R) CPU X3430@2.40GHz), and following:
>
> https://pve.proxmox.com/wiki/PCI(e)_Passthrough
>
> I've tried to enable
13 matches
Mail list logo
