Recent content by hanoon

in my case - I did shutdown, detach disk and reattach it back as Virtio then bootdisk size reported correctly on boot.

I can confirm the issue still exists Change password failed: user 'xxxx' does not exist (500) - while user exists Word around - on the node - shell useradd xxxx passwd xxxx

for anyone having this issue - make sure your VM settings have Spide as the display instead of Default - At least that was it in my case Hope that helps!

in my case - I had Ceph installed but not used (partially installed) so I didn't update the apt source list for it - I disabled the Proxmox repo - updated the Ceph list - ran the update - and then dist-upgrade - it worked fine - then I enabled the Proxmox repo and another dist-upgrade ran...

Hello, Thanks for your ongoing contributions and valuable input - This comment stopped me - I looked at those units DX60 S2, I see them available - What software do you use with them, or do you use factory OS? Do you need a license to use factory OS? Are you able to offer ISCSI / NFS from these...

Do we know which update KB causing the issue so we can remove and resolve the issue?

One socket - same number of cores - works

I just tested and It has the same BSOD after downgrading the Virtio driver - The issue is actually started after the Proxmox update not the Virtio driver update.

No - I tried different variations - this just happened to be the one when I sent configs. let me know if It should be something else Case 1 NUMA on Memory HP on CPU HP off = BSOD Case 2 NUMA on Memory HP off CPU HP on = BSOD Case 3 NUMA on Memory HP off CPU HP off = BSOD Case 4 NUMA off...

@fiona @fweber also tried changing cpu type to host not helping Any assistance would be appreciated

I tried and still same results - here are the configurations after the change in case something is missing agent: 1 args: -machine type=q35,kernel_irqchip=on balloon: 0 bios: seabios boot: order=virtio0;net0;ide0 cores: 48 cpu: kvm64 cpuunits: 2048 hotplug: disk,network,usb,memory,cpu ide0...

Another update - I also tested updating windows OS to latest version (after disabling NUMA and hotplug for CPU/Memory) still BSOD

I changed it and stop the VM completely then start it - Didn't make any difference

Hi - Yes it's 0.1.229 - is the one we installed. Tried i440fx back without luck

In Windows 2022 template we have CPU/Memory hotplug enabled with NUMA to support it on the processor - Recently all 2022 have been getting BSOD with an error I did search the forum and multiple threads however the workaround to get the VM to boot is to disable NUMA and CPU/Memory hotplug - then...