On Mon, Jul 29, 2019 at 04:43:11PM +0200, Fabian Grünbichler wrote:
> On Mon, Jul 29, 2019 at 10:59:09AM +0200, Wolfgang Bumiller wrote:
> > By default lxc-attach will try to find the user's shell via
> > getpwuid_r(), and if this fails will run `getent passwd
> > $uid`.
> >
> > The first part is
Add a mention to 'pve-efiboot-tool refresh' in places where
'update-initramfs' is mentioned.
Signed-off-by: Stefan Reiter
---
local-zfs.adoc | 5 -
qm-pci-passthrough.adoc | 18 +++---
system-booting.adoc | 6 +++---
3 files changed, 18 insertions(+), 11 deletions(
On Thu, Aug 01, 2019 at 10:36:35AM +0200, Wolfgang Bumiller wrote:
> On Mon, Jul 29, 2019 at 04:43:11PM +0200, Fabian Grünbichler wrote:
> > On Mon, Jul 29, 2019 at 10:59:09AM +0200, Wolfgang Bumiller wrote:
> > > By default lxc-attach will try to find the user's shell via
> > > getpwuid_r(), and i
Upgrading from PVE 5 to 6 works only with the Gluster packages from the
Debian repository. At least Gluster versions 5.8 to 6.4-1 have conflicts
with our packages.
Signed-off-by: Dominic Jäger
---
Tested on one VM with PVE 5.4 and upstream Gluster (6.4-1) and one
with PVE 5.4 and the Debian Glust
As explained in [0], we can add a hook script that will be called after
update-initramfs did its job (and thus, a new initrd has been created).
We can use this to automatically sync the ESPs using 'pve-efiboot-tool
refresh', if update-initramfs was called manually (on kernel upgrade we
already hav
Mostly to avoid calling hooks directly in other scripts, future-proofing.
Signed-off-by: Stefan Reiter
---
bin/pve-efiboot-tool | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/bin/pve-efiboot-tool b/bin/pve-efiboot-tool
index a2ff4e1..d9bb829 1
Signed-off-by: Peter Keresztes Schmidt
---
PVE/QemuServer.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 8c519b5..106d2ae 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -178,7 +178,8 @@ my @supported_cpu_flags = (
As asked by multiple users in [0]
this allows to specify the aes flag separatly from the chosen cpu type.
Patch for pve-manager will follow.
[0]:
https://forum.proxmox.com/threads/proxmox-cpu-model-kvm64-with-pcid-and-aes-flags.39249/
Peter Keresztes Schmidt (1):
CPU flags: Add aes flag
PVE
Add the aes flag to the CPU flags list.
The corresponding qemu-server patch was submitted earlier.
Peter Keresztes Schmidt (1):
CPU flags: Add aes flag
www/manager6/form/VMCPUFlagSelector.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.21.0
_
Signed-off-by: Peter Keresztes Schmidt
---
www/manager6/form/VMCPUFlagSelector.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/www/manager6/form/VMCPUFlagSelector.js
b/www/manager6/form/VMCPUFlagSelector.js
index 2612be11..dec9de54 100644
--- a/www/manager6/form/VMCPUFla
10 matches
Mail list logo