Minisforum MS-01 PCIe Card and RAM Compatibility Thread
- Thread starter Patrick
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Tried also without SFP+, getting the same error.
I'm able to reproduce the error (even if the errors are different, really strange), 2-3 seconds after starting a Windows 11 VM, here is the log:
Test1 - Using onboard ethernet port
Code:
eb 20 17:44:16 nicoska2 pvedaemon[14727]: start VM 107: UPID:nicoska2:00003987:00007C2C:65D4D6E0:qmstart:107:root@pam:
Feb 20 17:44:16 nicoska2 pvedaemon[1948]: <root@pam> starting task UPID:nicoska2:00003987:00007C2C:65D4D6E0:qmstart:107:root@pam:
Feb 20 17:44:16 nicoska2 systemd[1]: Created slice qemu.slice - Slice /qemu.
Feb 20 17:44:16 nicoska2 systemd[1]: Started 107.scope.
Feb 20 17:44:17 nicoska2 kernel: tap107i0: entered promiscuous mode
Feb 20 17:44:17 nicoska2 kernel: vmbr0: port 17(fwpr107p0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: vmbr0: port 17(fwpr107p0) entered disabled state
Feb 20 17:44:17 nicoska2 kernel: fwpr107p0: entered allmulticast mode
Feb 20 17:44:17 nicoska2 kernel: fwpr107p0: entered promiscuous mode
Feb 20 17:44:17 nicoska2 kernel: vmbr0: port 17(fwpr107p0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: vmbr0: port 17(fwpr107p0) entered forwarding state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 1(fwln107i0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 1(fwln107i0) entered disabled state
Feb 20 17:44:17 nicoska2 kernel: fwln107i0: entered allmulticast mode
Feb 20 17:44:17 nicoska2 kernel: fwln107i0: entered promiscuous mode
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 1(fwln107i0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 1(fwln107i0) entered forwarding state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 2(tap107i0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 2(tap107i0) entered disabled state
Feb 20 17:44:17 nicoska2 kernel: tap107i0: entered allmulticast mode
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 2(tap107i0) entered blocking state
Feb 20 17:44:17 nicoska2 kernel: fwbr107i0: port 2(tap107i0) entered forwarding state
Feb 20 17:44:17 nicoska2 pvedaemon[1948]: <root@pam> end task UPID:nicoska2:00003987:00007C2C:65D4D6E0:qmstart:107:root@pam: OK
-- Reboot --
Code:
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 6/KVM/11954 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 2/KVM/11950 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 1/KVM/11949 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 15/KVM/11963 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 3/KVM/11951 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 17/KVM/11965 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 4/KVM/11952 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 8/KVM/11956 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:54 nicoska2 kernel: x86/split lock detection: #AC: CPU 9/KVM/11957 took a split_lock trap at address: 0x7ee1c050
Feb 20 17:01:56 nicoska2 pvedaemon[1948]: <root@pam> starting task UPID:nicoska2:00002F1C:00002A4A:65D4CCF4:vncproxy:107:root@pam:
Feb 20 17:01:56 nicoska2 pvedaemon[12060]: starting vnc proxy UPID:nicoska2:00002F1C:00002A4A:65D4CCF4:vncproxy:107:root@pam:
Feb 20 17:01:58 nicoska2 pvedaemon[1947]: VM 107 qmp command failed - VM 107 qmp command 'guest-ping' failed - got timeout
Feb 20 17:02:17 nicoska2 pvedaemon[1948]: VM 107 qmp command failed - VM 107 qmp command 'guest-ping' failed - got timeout
Feb 20 17:02:41 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 20 17:02:41 nicoska2 kernel: mce: CMCI storm detected: switching to poll mode
Feb 20 17:02:41 nicoska2 kernel: mce: [Hardware Error]: Machine check events loggedIt's starting to become a little bit frustrating :/
I've also tried do disable (in BIOS):
- C-State
- SpeedShift
but it doesn't help
@wadup I'm also having trouble getting vPro working. I can connect via a browser on port 16993 but can't get MeshCommander (using mesh-mini) to connect. It just times out. I'm using IP:16693 for hostname and
Digest / TLS for Auth. Any ideas? The vPro page in the browser doesn't show Remote Control.TLP configs on my Debian system are in
/etc/tlp.d with defaults at /etc/tlpd.confI had a similar lockup under load issue on a 1355U and that TLP setting + larger PSU brick made it happy.
You will want to read some docs about TLP because it has other fun things in it that you may not want. Also, since MS-01 has no battery you probably want to tell TLP to run in A/C mode:
tlp ac You can alternatively setup some udev rules to accomplish the same thing TLP does.I would try Linux >6.6 if you can:
I don't have those file in my system. Is this something I need to install via apt-get ?
I'm really worried to screw up my entire Proxmox host. At the moment 6.5.11-8-pve is the latest release availableI would try Linux >6.6 if you can:
Have you tried Proxmox VE 7.4-17?? this should install kernel 5.15.143.1. I am not running PVE version 8 yet.
Yup,
tlp is the package you'll probably want.I would recommend
restic or something similar to take backups if you're uneasy about breaking things.The PSU shipped is definitely underpowered when you hit that magic moment where everything is drawing max power:
13900h max tdp = 115w
XE 7 max tdp = 28w
PCIE slot spec = 75w
That's 218w without any ssd/hdd/memory draw on a 180w psu. Did you try power limiting the CPU? Kneecap that thing, and if it behaves then you'll need something like a SlimQ 240w or Dell 240w and hope the DC ATX PSU can handle the additional watts.
Yeah guys, please advice for a good PSU for the machine to be sure we dont have power troubles.
Just to be clear, I don't have any PCIE card and the system reboot itself also without using SFP+ cage.
Anyway, if we assume the TDP is the problem here, maybe if I reduce cores and RAM from the Windows VM it should run, correct?
Another question, are there any options (BIOS wise) to limit the CPU power consumption?
Thank you
Nico
At least for me on the 12900h the limits can be set in the BIOS under:
Advanced --> CPU Configuration
Standard without changes is :
PL1: 55W
PL2: 80W
But keep in mind they list it in milliwatts. So 55000 for PL1 and 80000 for PL2.
Installing Proxmox 7.4 is not possible.Installer don't even boot up. I believe the issue is with iGPU
This is the VM:
It crashes right after startup screen
Last edited:
Mine standard was:
PL1: 60000
PL2: 80000
I changed to:
PL1: 40000
PL2: 60000
Windows VM is configure as below:
Nothing to do, it crashed again right after startup screen:
I'm really worried that I got a bad CPU unit :/
Code:
Feb 20 22:40:24 nicoska2 pvedaemon[1943]: <root@pam> end task UPID:nicoska2:00003AC3:00009039:65D51C47:qmstart:107:root@pam: OK
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 2/KVM/15145 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 7/KVM/15150 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 5/KVM/15148 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 1/KVM/15144 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 4/KVM/15147 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 6/KVM/15149 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 3/KVM/15146 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 9/KVM/15152 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:24 nicoska2 kernel: x86/split lock detection: #AC: CPU 8/KVM/15151 took a split_lock trap at address: 0x7eebd050
Feb 20 22:40:32 nicoska2 pvedaemon[15287]: starting vnc proxy UPID:nicoska2:00003BB7:000093BD:65D51C50:vncproxy:107:root@pam:
Feb 20 22:40:32 nicoska2 pvedaemon[1944]: <root@pam> starting task UPID:nicoska2:00003BB7:000093BD:65D51C50:vncproxy:107:root@pam:
Feb 20 22:40:33 nicoska2 pvedaemon[1945]: VM 107 qmp command failed - VM 107 qmp command 'guest-ping' failed - got timeout
Feb 20 22:40:37 nicoska2 pveproxy[1960]: detected empty handle
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 4: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 5: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 9: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 8: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 2: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 6: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 1: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 3: requested 19791 ns lapic timer period limited to 200000 ns
Feb 20 22:40:48 nicoska2 kernel: kvm: vcpu 7: requested 19791 ns lapic timer period limited to 200000 ns
-- Reboot --i have installed it with some tweaks.... did you see this error: Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices ?
were you not able to see the GUI where you provide the IP and all that?