Am 08.03.22 um 17:19 schrieb Mark Schouten:
> Hi,
>
> So should I try and find someone who is able to reproduce this with a
> test-machine and is able to give you remote access to debug? Would that help?
>
It would certainly increase the likelihood of finding the issue. Since
it only happens on
On 3/8/22 19:10, Thomas Lamprecht wrote:
On 08.03.22 15:41, Dominik Csapak wrote:
When writing into the file, explicitly utf8 encode it, and then try to
utf8 decode it on read.
If the notes are not valid utf8, we assume it was an iso-8859 comment
and return is at is was.
Technically this is a
On 08.03.22 15:41, Dominik Csapak wrote:
> When writing into the file, explicitly utf8 encode it, and then try to
> utf8 decode it on read.
>
> If the notes are not valid utf8, we assume it was an iso-8859 comment
> and return is at is was.
>
> Technically this is a breaking change, since there a
--- Begin Message ---
Hi,
So should I try and find someone who is able to reproduce this with a
test-machine and is able to give you remote access to debug? Would that help?
—
Mark Schouten, CTO
Tuxis B.V.
m...@tuxis.nl
> On 8 Mar 2022, at 10:12, Fabian Ebner wrote:
>
> Am 07.03.22 um 15:5
When writing into the file, explicitly utf8 encode it, and then try to
utf8 decode it on read.
If the notes are not valid utf8, we assume it was an iso-8859 comment
and return is at is was.
Technically this is a breaking change, since there are iso-8859 comments
that would sucessfully decode as u
On 07.03.22 14:20, Oguz Bektas wrote:
> 'force-cpu' parameter was introduced to allow live-migration of VMs with
> custom CPU models; it does not need to be allowed for general use on
> vm_start for regular users, since they would be able to set arbitrary
> cpu types or cpuid parameters that aren't
update ja.po for proxmox-ve 7.1-10
---
--- /tmp/ja.po 2022-03-08 18:19:34.0 +0900
+++ jan.po 2022-03-07 11:04:44.763767160 +0900
@@ -8,7 +8,7 @@
"Project-Id-Version: proxmox translations\n"
"Report-Msgid-Bugs-T
Am 07.03.22 um 15:51 schrieb Mark Schouten:
> Hi,
>
> Sorry for getting back on this thread after a few months, but is the
> Windows-case mentioned here the case that is discussed in this forum-thread:
> https://forum.proxmox.com/threads/windows-vms-stuck-on-boot-after-proxmox-upgrade-to-7-0.1007
