Am 31.05.23 um 16:34 schrieb DERUMIER, Alexandre:
> Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
>> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
>>> In addition to theses model, I have enabled aes too.
>>> I think it's really important, because a lot of users use default
>>> val
Le jeudi 01 juin 2023 à 10:34 +0200, Fiona Ebner a écrit :
> Am 31.05.23 um 16:34 schrieb DERUMIER, Alexandre:
> > Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
> > > Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
> > > > In addition to theses model, I have enabled aes too.
> > > >
Am 31.05.23 um 17:08 schrieb DERUMIER, Alexandre:
>>>
>>> +my $builtin_models = {
>>> + 'x86-64-v1' => {
>>> + 'reported-model' => 'Opteron_G1',
>>
>> It's unfortunate that we'll report this model and hence also AMD as
>> vendor even on Intel hosts and vice versa for the other models. We
Am 22.05.23 um 12:25 schrieb Alexandre Derumier:> Nahelemn is a 2008
cpu, so I think it's ok, we are in 2013 ;)
> (and user can disable aes flag in gui too)
>
> That mean than the minimum compatible cpu for v2 is Intel Westmere (2010)
> and Amd Bulldozer (2011).
>
Unfortunately, it doesn't seem t
Le jeudi 01 juin 2023 à 11:17 +0200, Fiona Ebner a écrit :
> Am 31.05.23 um 17:08 schrieb DERUMIER, Alexandre:
> > > >
> > > > +my $builtin_models = {
> > > > + 'x86-64-v1' => {
> > > > + 'reported-model' => 'Opteron_G1',
> > >
> > > It's unfortunate that we'll report this model and hen
Le jeudi 01 juin 2023 à 11:34 +0200, Fiona Ebner a écrit :
> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:> Nahelemn is a 2008
> cpu, so I think it's ok, we are in 2013 ;)
> > (and user can disable aes flag in gui too)
> >
> > That mean than the minimum compatible cpu for v2 is Intel Westmere
>
--- Begin Message ---
Hi,
We have Ryzen 1700, 2600X, 3700 and 5950X machines here, I can test on
them if that helps (please detail tests to perform).
Thanks
El 1/6/23 a las 13:37, DERUMIER, Alexandre escribió:
Le jeudi 01 juin 2023 à 11:34 +0200, Fiona Ebner a écrit :
Am 22.05.23 um 12:25
This patch series changes the behavior during guest migrations:
Don't scan all storages for potential images belonging to the guest.
Only migrate images referenced in the config.
This made it necessary to handle pending changes explicitly which had
been covered by the storage scan.
We also added
Aliased volids can lead to unexpected behavior in a migration.
An aliased volid can happen if we have two storage configurations,
pointing to the same place. The resulting 'path' for a disk image
will be the same.
Therefore, stop the migration in such a case.
The check works by comparing the path
> >
> > What AMD CPUs did you try it on?
> >
> epyc v2/v3 with last microcodes
>
>
> does it work with x86-64-v3 ? (because the other patch of the series
> could autofind the best new model if it's working)
Looking at linux kernel code, they have some quirks based on cpu model
number && vendo
Signed-off-by: Aaron Lauterer
---
I am happy for suggestions on how to improve the phrasing if it is not
clear enough.
pvesm.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/pvesm.adoc b/pvesm.adoc
index 6ade1a4..7e91c50 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -174,6 +174,9 @@ zfs
Signed-off-by: Aaron Lauterer
---
changes since v2:
removed autovivified 'snapshots => {}'
test/run_qemu_migrate_tests.pl | 64 ++
1 file changed, 64 insertions(+)
diff --git a/test/run_qemu_migrate_tests.pl b/test/run_qemu_migrate_tests.pl
index fedbc32..3d5eb8d
Signed-off-by: Aaron Lauterer
---
changes since v2:
- changed mock storages and disk images, now there is 'alias-zfs' and
'alias-zfs-2' with the same disk image present to mimick an aliased
storage config.
test/run_qemu_migrate_tests.pl | 81 --
1 file changed, 78
When scanning all configured storages for disk images belonging to the
VM, the migration could easily fail if a storage is not available, but
enabled. That storage might not even be used by the VM at all.
By not doing that and only looking at the disk images referenced in the
VM config, we can avo
Aliased volumes (referencing the same volume multiple times) can lead to
unexpected behavior in a migration.
Therefore, stop the migration in such a case.
The check works by comparing the path returned by the storage plugin.
This means that we should be able to catch the common situations where
i
When scanning all configured storages for volumes belonging to the
container, the migration could easily fail if a storage is not
available, but enabled. That storage might not even be used by the
container at all.
By not doing that and only looking at the disk images referenced in the
config, we
Used wrong tag, this is for manager, not widget-toolkit...
Am 06/04/2023 um 13:38 schrieb Noel Ullreich:
> Since some languages translate byte units like 'GiB' or write them in their
> own script, this patch wraps units in the `gettext` function.
>
> While most occurrences of byte strings can be
Am 06/04/2023 um 13:38 schrieb Noel Ullreich:
> Some languages translate byte units like 'GiB' or write them in their
> own script.
>
> By `gettext`ing the units in the `format_size` function, we can
> translate the units for (almost) all of the web interface.
>
> Signed-off-by: Noel Ullreich
>
Am 19/04/2023 um 12:34 schrieb Aaron Lauterer:
> Signed-off-by: Aaron Lauterer
> ---
>
> AFAIK we do not have negative sizes anywhere, and if, it is an
> indication that something is wrong.
above belongs in the commit message, additionaly some background for why doing
this now (i.e., did you run
Don't we reuse that on PBS/PMG too, and if is it working there?
The commit message isn't excactly telling... ;-)
Am 13/04/2023 um 17:10 schrieb Aaron Lauterer:
> Signed-off-by: Aaron Lauterer
> ---
> src/node/NetworkEdit.js | 16
> 1 file changed, 16 insertions(+)
>
> diff --
Am 01.06.23 um 15:53 schrieb DERUMIER, Alexandre:
>>>
>>> What AMD CPUs did you try it on?
>>>
>> epyc v2/v3 with last microcodes
>>
>>
>> does it work with x86-64-v3 ? (because the other patch of the series
>> could autofind the best new model if it's working)
>
> Looking at linux kernel code, t
Am 01.06.23 um 14:02 schrieb Eneko Lacunza:
> Hi,
>
> We have Ryzen 1700, 2600X, 3700 and 5950X machines here, I can test on
> them if that helps (please detail tests to perform).
>
> Thanks
>
Hi,
thank you for the offer. It would be interesting to see if you have any
issues with the following:
The old 'main' component stays valid, pointing to no-subscription,
which means the is_referenced_repository() check needs a special case
for it. It will eventually go away, together with the handles for
Quincy.
Alternatively, the standard repository's info() could've been changed
to return multipl
Signed-off-by: Fiona Ebner
---
proxmox-apt/tests/repositories.rs | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/proxmox-apt/tests/repositories.rs
b/proxmox-apt/tests/repositories.rs
index 4b3c9de..710e2f7 100644
--- a/proxmox-apt/tests/repositories.rs
+++ b/proxmox-apt/te
On Proxmox VE 8, only Quincy and newer will be supported.
Signed-off-by: Fiona Ebner
---
proxmox-apt/src/repositories/mod.rs | 4 --
proxmox-apt/src/repositories/standard.rs | 58
proxmox-apt/tests/repositories.rs| 4 --
3 files changed, 66 deletions(-)
d
Signed-off-by: Fiona Ebner
---
proxmox-apt/tests/repositories.rs | 30 +++
.../ceph-quincy-bookworm.list | 6
.../ceph-quincy-nosub-bookworm.list | 2 ++
.../sources.list.d/ceph-quincy-bookworm.list | 4 +++
.../ceph-quincy-nosub-book
Hi,
I found an interesting thread on the forum about kvm_pv_unhalt
https://forum.proxmox.com/threads/live-migration-between-intel-xeon-and-amd-epyc2-linux-guests.68663/
Sounds good. Please also take a look at the default flag
"kvm_pv_unhalt". As I mentioned, it would cause a kernel crash in
para
27 matches
Mail list logo
