TCMapes
-
Posts
47 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TCMapes
-
-
I just read the command information wrong. Seems i had the pinning right for my gaming vm then.
-
Just wanted to post this here. But from the following console commands the CPU lay seems to have CCD 0 on CPU 0 through 15 and CCD 1 on CPU 16 through 31. From the below information it looks like I should do CPU isolation on 16 thru 31. Then pin those to my gaming VM. Am I missing something here?
----------------lstopo command--------------------------------------------------------
Machine (126GB total)
Package L#0
NUMANode L#0 (P#0 126GB)
L3 L#0 (32MB)
L2 L#0 (512KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
PU L#0 (P#0)
PU L#1 (P#16)
L2 L#1 (512KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
PU L#2 (P#1)
PU L#3 (P#17)
L2 L#2 (512KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
PU L#4 (P#2)
PU L#5 (P#18)
L2 L#3 (512KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
PU L#6 (P#3)
PU L#7 (P#19)
L2 L#4 (512KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
PU L#8 (P#4)
PU L#9 (P#20)
L2 L#5 (512KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
PU L#10 (P#5)
PU L#11 (P#21)
L2 L#6 (512KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
PU L#12 (P#6)
PU L#13 (P#22)
L2 L#7 (512KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
PU L#14 (P#7)
PU L#15 (P#23)
L3 L#1 (32MB)
L2 L#8 (512KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
PU L#16 (P#8)
PU L#17 (P#24)
L2 L#9 (512KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
PU L#18 (P#9)
PU L#19 (P#25)
L2 L#10 (512KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
PU L#20 (P#10)
PU L#21 (P#26)
L2 L#11 (512KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
PU L#22 (P#11)
PU L#23 (P#27)
L2 L#12 (512KB) + L1d L#12 (32KB) + L1i L#12 (32KB) + Core L#12
PU L#24 (P#12)
PU L#25 (P#28)
L2 L#13 (512KB) + L1d L#13 (32KB) + L1i L#13 (32KB) + Core L#13
PU L#26 (P#13)
PU L#27 (P#29)
L2 L#14 (512KB) + L1d L#14 (32KB) + L1i L#14 (32KB) + Core L#14
PU L#28 (P#14)
PU L#29 (P#30)
L2 L#15 (512KB) + L1d L#15 (32KB) + L1i L#15 (32KB) + Core L#15
PU L#30 (P#15)
PU L#31 (P#31)
------------------lscpu -e--------------------------------------------------------
CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE MAXMHZ MINMHZ MHZ
0 0 0 0 0:0:0:0 yes 5083.3979 2200.0000 3696.7129
1 0 0 1 1:1:1:0 yes 5083.3979 2200.0000 3838.7380
2 0 0 2 2:2:2:0 yes 5083.3979 2200.0000 4712.8442
3 0 0 3 3:3:3:0 yes 5083.3979 2200.0000 4323.0791
4 0 0 4 4:4:4:0 yes 5083.3979 2200.0000 4716.0020
5 0 0 5 5:5:5:0 yes 5083.3979 2200.0000 4095.6111
6 0 0 6 6:6:6:0 yes 5083.3979 2200.0000 4717.2632
7 0 0 7 7:7:7:0 yes 5083.3979 2200.0000 4715.3799
8 0 0 8 8:8:8:1 yes 5083.3979 2200.0000 3594.2419
9 0 0 9 9:9:9:1 yes 5083.3979 2200.0000 3400.0000
10 0 0 10 10:10:10:1 yes 5083.3979 2200.0000 3581.8450
11 0 0 11 11:11:11:1 yes 5083.3979 2200.0000 3400.0000
12 0 0 12 12:12:12:1 yes 5083.3979 2200.0000 3400.0000
13 0 0 13 13:13:13:1 yes 5083.3979 2200.0000 3746.9951
14 0 0 14 14:14:14:1 yes 5083.3979 2200.0000 3400.0000
15 0 0 15 15:15:15:1 yes 5083.3979 2200.0000 3400.0000
16 0 0 0 0:0:0:0 yes 5083.3979 2200.0000 3787.1699
17 0 0 1 1:1:1:0 yes 5083.3979 2200.0000 4684.5049
18 0 0 2 2:2:2:0 yes 5083.3979 2200.0000 4675.6758
19 0 0 3 3:3:3:0 yes 5083.3979 2200.0000 4415.8789
20 0 0 4 4:4:4:0 yes 5083.3979 2200.0000 4704.3140
21 0 0 5 5:5:5:0 yes 5083.3979 2200.0000 4511.8540
22 0 0 6 6:6:6:0 yes 5083.3979 2200.0000 4669.6411
23 0 0 7 7:7:7:0 yes 5083.3979 2200.0000 4663.3330
24 0 0 8 8:8:8:1 yes 5083.3979 2200.0000 3400.0000
25 0 0 9 9:9:9:1 yes 5083.3979 2200.0000 3400.0000
26 0 0 10 10:10:10:1 yes 5083.3979 2200.0000 3400.0000
27 0 0 11 11:11:11:1 yes 5083.3979 2200.0000 3400.0000
28 0 0 12 12:12:12:1 yes 5083.3979 2200.0000 3400.0000
29 0 0 13 13:13:13:1 yes 5083.3979 2200.0000 3400.0000
30 0 0 14 14:14:14:1 yes 5083.3979 2200.0000 3593.3479
31 0 0 15 15:15:15:1 yes 5083.3979 2200.0000 3400.0000 -
`virsh start "Windows 11"
error: Failed to start domain 'Windows 11'
error: internal error: qemu unexpectedly closed the monitor: 2023-09-24T00:26:35.415430Z qemu-system-x86_64: -device {"driver":"virtio-blk-pci","bus":"pci.3","addr":"0x0","drive":"libvirt-3-format","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}: Failed to get "write" lock
Is another process using the image [/mnt/ssd_cache/domains/Windows_11/vdisk1.img]?`Any ideas on how i can kill the lock without rebooting entire system?
-
2 minutes ago, TCMapes said:
Could the ZFS Pools and Array becausing my high CPU spikes and the hard reboots?
I notice every time my unraid system spikes my system reboots. Usually when I am downloading a game on my VM. In this case Baldurs Gate 3.
Is there something I should do? I feel like my system is rebooting to protect itself just don't know why.
Forgot to add I am not overclocking anything system speeds are default. I have all DIMMS populated with a total RAM give 128GB.
-
Could the ZFS Pools and Array becausing my high CPU spikes and the hard reboots?
I notice every time my unraid system spikes my system reboots. Usually when I am downloading a game on my VM. In this case Baldurs Gate 3.
Is there something I should do? I feel like my system is rebooting to protect itself just don't know why.
-
Thanks for the information. I changed the share to most-free and now all my zfs disks are growing evenly.
-
Is this normal to have a share set to high water mark and files never being written to it.
As you can see Disk 5 is not touched.
Share Settings.
I would expect all disks growing evenly. Any thoughts on what the array is doing.
-
Hardlinks not working. Am I missing something for my docker setup. Do I even need the /media path?
When I check to see if hardlinks are using for my share /data it is showing it is not used.
All my dockers use the data share I setup using the TRaSH guide for hardlinks.
-
Dont think the script works anymore for newer cards. I always get a small bios file. Even after I removing the binding and or leave the binding.
-
Glad to see this plugin is being tweaked to work with the latest unraid OS build
-
Attached are my recent diagnostics logs after a hard reboot to bring unraid back.
-
i am having the same issue. Unraiid system crashes when I leave my WIN11 VM running over night. I come to my office and have to hard cycle the entire unraid system. At first I thought it was sleep/hibernation in the vm doing it but that was the first thing I turned off. I am running the latest stable release of unraid. I am thinking I need to roll back to the previous stable until they fix this bug. Never happened until the unraid OS upgrade.
-
oh one more thing. What is the process to destroy and redeploy a Macinabox VM. Seems when select remove VM and Disk it just spins.
-
Has anyone got Macinabox Monterey working?
NOTE: This is the first time I have ever used Machinabox docker from @SpaceInvaderOne
-
On 2/10/2023 at 5:11 AM, aymanibousi said:
isnt it suppose to be 15gigs?
When i start the VM, it starts as the apple logo, loads half way then it reboots itself, like in a loop!eDit: it loads up to option menu where it shows macos base system, uefi and reset nvram. I press on macos base system, it loads a quarter way then errors out and resets to the option menu again!
Edit2: logs of VM shows 2023-02-10T10:14:53.445182Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
I am getting this same experience with AMD Ryzen 9 5950X 16-Core @ 4100 MHz system. So far I think Big Sur is working though it has not finished installing.
-
Got it and it is running as expected. Thanks again!
-
Would love to see the next version composed from binhex.
-
I have a weird issue with my VM. It was working fine forever until recent patch tuesday in July. Now it will not display anything black screen. I will also have to force stop it which can lead it other hardware health issues on my unraid server. Some times if I start my VM with passthru GPU my entire unraid server reboots. Any help would be appreciated.
VM Config Start
__________________________________________________________________________________________________________________
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='5'>
<name>Windows 11</name>
<uuid>8964a397-0e4a-73b1-26cb-eda07c167439</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/>
</metadata>
<memory unit='KiB'>16777216</memory>
<currentMemory unit='KiB'>16777216</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='12'/>
<vcpupin vcpu='1' cpuset='28'/>
<vcpupin vcpu='2' cpuset='13'/>
<vcpupin vcpu='3' cpuset='29'/>
<vcpupin vcpu='4' cpuset='14'/>
<vcpupin vcpu='5' cpuset='30'/>
<vcpupin vcpu='6' cpuset='15'/>
<vcpupin vcpu='7' cpuset='31'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/8964a397-0e4a-73b1-26cb-eda07c167439_VARS-pure-efi-tpm.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-passthrough' check='none' migratable='on'>
<topology sockets='1' dies='1' cores='4' threads='2'/>
<cache mode='passthrough'/>
<feature policy='require' name='topoext'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/sbin/qemu</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='writeback'/>
<source file='/mnt/user/domains/Windows 11/vdisk1.img' index='3'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/en-us_windows_11_consumer_editions_version_21h2_updated_july_2022_x64_dvd_a9ae6b6a.iso' index='2'/>
<backingStore/>
<target dev='hda' bus='sata'/>
<readonly/>
<boot order='2'/>
<alias name='sata0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/virtio-win-0.1.221-1.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='sata'/>
<readonly/>
<alias name='sata0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='sata' index='0'>
<alias name='sata0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='usb' index='0' model='qemu-xhci' ports='15'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:72:31:8c'/>
<source bridge='br0'/>
<target dev='vnet4'/>
<model type='virtio-net'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/1'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-Windows 11/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='3'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0' persistent_state='yes'/>
<alias name='tpm0'/>
</tpm>
<audio id='1' type='none'/>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<rom file='/mnt/user/domains/vbios/RTX3090ti.rom'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0ecb'/>
<product id='0x203e'/>
<address bus='3' device='4'/>
</source>
<alias name='hostdev3'/>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x8087'/>
<product id='0x0029'/>
<address bus='1' device='3'/>
</source>
<alias name='hostdev4'/>
<address type='usb' bus='0' port='2'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain>
-
No idea how to diagnose the issue here. I attached the latest diagnostics to this post.
Thanks in advance for the assistance.
-
7 minutes ago, TCMapes said:
So not game parameters but the two json files. Wont they get over written when updates occur?
vrising\VRisingServer_Data\StreamingAssets\Settings that the proper path. Cause i updated the json and restarted docker and password still not applied
-
8 minutes ago, ich777 said:
These setting are supposed to go into the game/server settings files not the game parameters.
So not game parameters but the two json files. Wont they get over written when updates occur?
-
13 minutes ago, TCMapes said:
So like this then?
Did not work for Server Password or Clan Size.
-
So like this then?
-
What is the proper syntax for putting parameters into dedicated vRising Server?
For example is below the correct process
Password = "aPassword"
ClanSize = "10"
ListOnMasterServer = "False"
Thanks again Ich777 for another fantastic docker.
-
1
-
Performance Improvements in VMs by adjusting CPU pinning and assignment
in VM Engine (KVM)
Posted
If you are curious to see how your CPU is handle in unraid the following two commands can show you dies layout for CPU isolation. For the chiplet designs coming out is best to put your workhorse vm on a single chiplet intead across multiple. Hope this helps.
lscpu -e and lstopo
lstopo
Machine (126GB total)
Package L#0
NUMANode L#0 (P#0 126GB)
L3 L#0 (32MB)
L2 L#0 (512KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
PU L#0 (P#0)
PU L#1 (P#16)
L2 L#1 (512KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
PU L#2 (P#1)
PU L#3 (P#17)
L2 L#2 (512KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
PU L#4 (P#2)
PU L#5 (P#18)
L2 L#3 (512KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
PU L#6 (P#3)
PU L#7 (P#19)
L2 L#4 (512KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
PU L#8 (P#4)
PU L#9 (P#20)
L2 L#5 (512KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
PU L#10 (P#5)
PU L#11 (P#21)
L2 L#6 (512KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
PU L#12 (P#6)
PU L#13 (P#22)
L2 L#7 (512KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
PU L#14 (P#7)
PU L#15 (P#23)
L3 L#1 (32MB)
L2 L#8 (512KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
PU L#16 (P#8)
PU L#17 (P#24)
L2 L#9 (512KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
PU L#18 (P#9)
PU L#19 (P#25)
L2 L#10 (512KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
PU L#20 (P#10)
PU L#21 (P#26)
L2 L#11 (512KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
PU L#22 (P#11)
PU L#23 (P#27)
L2 L#12 (512KB) + L1d L#12 (32KB) + L1i L#12 (32KB) + Core L#12
PU L#24 (P#12)
PU L#25 (P#28)
L2 L#13 (512KB) + L1d L#13 (32KB) + L1i L#13 (32KB) + Core L#13
PU L#26 (P#13)
PU L#27 (P#29)
L2 L#14 (512KB) + L1d L#14 (32KB) + L1i L#14 (32KB) + Core L#14
PU L#28 (P#14)
PU L#29 (P#30)
L2 L#15 (512KB) + L1d L#15 (32KB) + L1i L#15 (32KB) + Core L#15
PU L#30 (P#15)
PU L#31 (P#31)
lscpu -e
CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE MAXMHZ MINMHZ MHZ
0 0 0 0 0:0:0:0 yes 5083.3979 2200.0000 3696.7129
1 0 0 1 1:1:1:0 yes 5083.3979 2200.0000 3838.7380
2 0 0 2 2:2:2:0 yes 5083.3979 2200.0000 4712.8442
3 0 0 3 3:3:3:0 yes 5083.3979 2200.0000 4323.0791
4 0 0 4 4:4:4:0 yes 5083.3979 2200.0000 4716.0020
5 0 0 5 5:5:5:0 yes 5083.3979 2200.0000 4095.6111
6 0 0 6 6:6:6:0 yes 5083.3979 2200.0000 4717.2632
7 0 0 7 7:7:7:0 yes 5083.3979 2200.0000 4715.3799
8 0 0 8 8:8:8:1 yes 5083.3979 2200.0000 3594.2419
9 0 0 9 9:9:9:1 yes 5083.3979 2200.0000 3400.0000
10 0 0 10 10:10:10:1 yes 5083.3979 2200.0000 3581.8450
11 0 0 11 11:11:11:1 yes 5083.3979 2200.0000 3400.0000
12 0 0 12 12:12:12:1 yes 5083.3979 2200.0000 3400.0000
13 0 0 13 13:13:13:1 yes 5083.3979 2200.0000 3746.9951
14 0 0 14 14:14:14:1 yes 5083.3979 2200.0000 3400.0000
15 0 0 15 15:15:15:1 yes 5083.3979 2200.0000 3400.0000
16 0 0 0 0:0:0:0 yes 5083.3979 2200.0000 3787.1699
17 0 0 1 1:1:1:0 yes 5083.3979 2200.0000 4684.5049
18 0 0 2 2:2:2:0 yes 5083.3979 2200.0000 4675.6758
19 0 0 3 3:3:3:0 yes 5083.3979 2200.0000 4415.8789
20 0 0 4 4:4:4:0 yes 5083.3979 2200.0000 4704.3140
21 0 0 5 5:5:5:0 yes 5083.3979 2200.0000 4511.8540
22 0 0 6 6:6:6:0 yes 5083.3979 2200.0000 4669.6411
23 0 0 7 7:7:7:0 yes 5083.3979 2200.0000 4663.3330
24 0 0 8 8:8:8:1 yes 5083.3979 2200.0000 3400.0000
25 0 0 9 9:9:9:1 yes 5083.3979 2200.0000 3400.0000
26 0 0 10 10:10:10:1 yes 5083.3979 2200.0000 3400.0000
27 0 0 11 11:11:11:1 yes 5083.3979 2200.0000 3400.0000
28 0 0 12 12:12:12:1 yes 5083.3979 2200.0000 3400.0000
29 0 0 13 13:13:13:1 yes 5083.3979 2200.0000 3400.0000
30 0 0 14 14:14:14:1 yes 5083.3979 2200.0000 3593.3479
31 0 0 15 15:15:15:1 yes 5083.3979 2200.0000 3400.0000