Le 2/09/22 à 14:54, Fiona Ebner a écrit :
> Hi,
>
> Am 31.08.22 um 11:40 schrieb DERUMIER, Alexandre:
>> Hi,
>>
>> Any news to apply this patch serie ? Now that qemu 7.0 is pushed in repo.
>>
>
> While the series looks fine to me, I'd feel better if a member of the
> release team could take a lo
Hi,
Am 31.08.22 um 11:40 schrieb DERUMIER, Alexandre:
> Hi,
>
> Any news to apply this patch serie ? Now that qemu 7.0 is pushed in repo.
>
While the series looks fine to me, I'd feel better if a member of the
release team could take a look for sanity-checking as well, especially
the config-re
The following issue reported on the community forum [0] is likely
fixed by this.
In my case, loading a VM snapshot that originally was taken on an
Intel CPU on my AMD-based host often caused problems in other VMs. In
particular, it often led to CPU stalls, and sometimes clock jumps far
into the fu
--- Begin Message ---
Hi,
El 2/9/22 a las 9:59, Eneko Lacunza escribió:
Hi,
El 2/9/22 a las 9:47, Fiona Ebner escribió:
Am 02.09.22 um 09:22 schrieb Eneko Lacunza:
Hi Fiona,
Does this patch correspond to kernels linked in this forum thread?
https://forum.proxmox.com/threads/proxmox-7-2-3-ce
A few suggestions I would have found helpful when first reading this
documentation, inline:
On 6/10/22 12:53, Markus Frank wrote:
> added AMD SEV documentation for "[PATCH qemu-server] QEMU AMD SEV
> enable"
>
> Signed-off-by: Markus Frank
> ---
> v2:
> * added check if sev is enabled
> * added
This reverts commit c3442aa5546b029a524928d10c7ecabe0024c137.
Nowadays, relying on 'readlink /sys/block/nvmeXnY/device' won't always
lead to the correct device, as reported in the community forum[0],
where it results in '../../nvme-subsys0' and there's no matching entry
under '/dev/'.
Since Linux
The SEV memory encryption works without problems.
Parameters for 'cbitpos' and 'reduced-phys-bits' were successfully and
automatically applied, when not supplied in the config.
I could run up to 15 SEV-enabled VMs concurrently, which is in line with
the expected maximum capabilities of a 1st gen Ep
On 8/27/22 18:09, DERUMIER, Alexandre wrote:
Le 26/08/22 à 08:39, Dominik Csapak a écrit :
On 8/25/22 16:53, DERUMIER, Alexandre wrote:
> root@pve2:~# qm start 101
> ignoring mediated device with multifunction device
ok, it's simply that indeed I have specify a multifunction path
":0
--- Begin Message ---
Hi,
El 2/9/22 a las 9:47, Fiona Ebner escribió:
Am 02.09.22 um 09:22 schrieb Eneko Lacunza:
Hi Fiona,
Does this patch correspond to kernels linked in this forum thread?
https://forum.proxmox.com/threads/proxmox-7-2-3-ceph-16-2-7-migrating-vms-hangs-them-kernel-panic-on-l
Hi,
Am 02.09.22 um 09:22 schrieb Eneko Lacunza:
> Hi Fiona,
>
> Does this patch correspond to kernels linked in this forum thread?
>
> https://forum.proxmox.com/threads/proxmox-7-2-3-ceph-16-2-7-migrating-vms-hangs-them-kernel-panic-on-linux-freeze-on-windows.109645/page-2#post-488479
>
No, th
In preparation to increase the timeout for workers. Both existing
callers of librados_connect() don't currently use the parameter.
Signed-off-by: Fiona Ebner
---
No changes from v1.
PVE/Storage/RBDPlugin.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/Storage/RBDPlug
The default timeout in PVE/RADOS.pm is 5 seconds, but this is not
always enough for external clusters under load. Workers can and should
take their time to not fail here too quickly.
Signed-off-by: Fiona Ebner
---
Changes from v1:
* Add missing use statement. Was transitively used via e.g.
--- Begin Message ---
Hi Fiona,
Does this patch correspond to kernels linked in this forum thread?
https://forum.proxmox.com/threads/proxmox-7-2-3-ceph-16-2-7-migrating-vms-hangs-them-kernel-panic-on-linux-freeze-on-windows.109645/page-2#post-488479
If so I can test them and see if that helps w
13 matches
Mail list logo
