PeteAsking

Members
  • Posts

    442
  • Joined

  • Last visited

Everything posted by PeteAsking

  1. Not sure if anyne needs to know this but monterey gave me some trouble and I had to edit the XML to change the processor type. My parts I edited before the disk section are: <domain type='kvm' id='24' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Elendil Macinabox Monterey</name> <uuid>8a8e5ae8-9cce-49e5-b883-e447e7ad0fa4</uuid> <description>MacOS Monterey</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="Monterey.png" os="osx"/> </metadata> <memory unit='KiB'>25165824</memory> <currentMemory unit='KiB'>25165824</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/mnt/user/system/custom_ovmf/Macinabox_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>IvyBridge</model> <feature policy='disable' name='pclmuldq'/> <feature policy='require' name='fma'/> <feature policy='disable' name='pcid'/> <feature policy='disable' name='tsc-deadline'/> <feature policy='disable' name='f16c'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='fsgsbase'/> <feature policy='require' name='bmi1'/> <feature policy='require' name='avx2'/> <feature policy='disable' name='smep'/> <feature policy='require' name='bmi2'/> <feature policy='disable' name='erms'/> <feature policy='require' name='xsaveopt'/> <feature policy='disable' name='rdtscp'/> <feature policy='disable' name='fma4'/> <feature policy='require' name='invtsc'/> </cpu> <clock offset='utc'> <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> Parts of interest are the <vcpu> and the <cpu_mode> sections. The reason for the edits is I would just get stuck with the progress bar on boot mot moving at all athe the CPU just consuming 1 core on my unraid box and nothing would happen (just stuck on the apple logo with no progress bar movement essentially). Unsure if anyone else has this issue but that is how I fixed it. This is editing the XML from the VM's page. The thing that fixed it for me was: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>IvyBridge</model> and also <vcpu placement='static'>4</vcpu> Both which are defined differently in the template. You can also try <model fallback='forbid'>SandyBridge</model> if you like. Edit: Another thing I forgot to say I did was add to the bootom of the xml a change to mem balloon and some qemu arguments: </video> <memballoon model="none"/> </devices> <qemu:commandline> <qemu:arg value="-device"/> <qemu:arg value="************************"/> <qemu:arg value="-smbios"/> <qemu:arg value="type=2"/> <qemu:arg value="-cpu"/> <qemu:arg value="Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check"/> </qemu:commandline> </domain> Also near the top I changed pc-q35-6.2 to: type arch="x86_64" machine="pc-q35-4.2">hvm</type> This also alleviated some crashes I had/ and or stuck on the black apple.
  2. To convert a raw disk you just use the qemu-img command on a linux box eg: qemu-img convert -p -c -O qcow2 originaldisk.qcow2 newdisk.qcow2 Resulting newdisk.qcow2 is in qcow format. You can check with qemu-img info newdisk.qcow2
  3. Very minor, its only change from 65 was: > Improve application stability when using mobile apps. You need to stop the docker container and make a copy of it somewhere so that you can roll back if need be. Then change your tag to unifi-controller:version-7.1.66 and pray it upgrades. It can take like 10 minutes.
  4. Just upgraded to 7.1.66, as with the previous version there is pretty much no risk to upgrade if you are already on the 7 series.
  5. 7.1.65 has just minor bug changes so anyone on 7.1.61 should immediately just upgrade (take a copy of your docker obviously first)as there is an almost zero chance of anything going wrong.
  6. All of the 7 series have had no issues whatsoever for me so any of the version 7 versions are totally fine. Only thing I am unsure of is upgrading from an old version if you need to go via certain revisions or if you can just go from say 6.2.26 straight to the latest one.
  7. Changed my tag to lscr.io/linuxserver/unifi-controller:version-7.1.61 and verified everything is working perfectly.
  8. The error indicates mongodb is not running so must be some issue with your setup. Either wrong port or something blocking it etc. You would need to look into that.
  9. The correct syntax is: --memory=2G not --memory="2g" which is a syntax you have made up and not appropriate.
  10. I mean, you are going to have to provide a lot more information about your particular setup before anyone can help. Collectively the community might know more than any individual about how things should work, but you alone are in possession on how your particular setup is configured so unless you tell us we will have no idea what to suggest.
  11. Did you set a memory limit as has been suggested many times in this thread? Also while on reading the thread did you set a version tag (eg: /unifi-controller:version-7.0.25) so your docker does not auto update past a revision without your knowledge, as has been suggested many times in this thread? Both these things are very important when using the unifi docker. Reason being the tag means you could have taken a manual backup before updating so you can always roll back to a prior version if you have a problem later on with anything, such as DB issue or any other issue.
  12. 7.0.25 has few changes and just a few bugfixes. Updating to it from 7.0.23 is very seamless.
  13. That is great, I would also agree with 7.0.23 being excellent and zero problems my side and nobody here moaning and reddit is quiet also on this version so probably everyone should try it and check they are happy. If nobody is complaining in a month or so about 7.0.23 we should just recommend that to anyone who asks. Its kind of easy when everyone has a stable version to then recommend how to upgrade from it to a later version (ie the exact steps) and also then everyone kind of knows how it works and what to expect etc. Plus this supports all their hardware currently so seems like a good place to me anyway.
  14. So I take it everyone loves 7.0.23 then? Looks like no complaints from anyone (other than the actual process of getting to 7.0.23 having a few kinks during upgrade, but once there all good right?).
  15. It was nothing major for me at least. Just the things like minimum speed the clients can connect at got set to auto (ie any speed they want) and non impact settings like that.
  16. I updated to 7.0.23 an everything appears to work but it changed some of my settings and I had to go through everything on the controller and check they were all correct again on every page.
  17. Hello, Would anyone know if it is possible to sleep a docker when no players are connected? A blog post here describes a method they used but I dont think we can use knockd... Would appreciate anyone who knew the answer to this: https://daniel.im/blog/2020-04-04_sleep-minecraft/
  18. If you block apples domains it interferes with their functioning of those features.
  19. My networking is such that I have a vlan (vlan 7) where the docker resides and my firewall has rules to allow this out to the internet and between vlans as required. This is not required unless you have vlans also. If you do then you would need to ensure your firewall rules apply correctly to allow traffic from the various ip's etc
  20. Just fyi I noticed a mistake in my config, the ServerIP further down which seths the hostname record etc should be 192.168.7.5, and I incorrectly listed it in my ss above as 192.168.2.22. I corrected that now. It doesnt change much or stop the docker working but in case you are confused I have something on that IP and was obviously not paying too much attention when typing in that field when I redid it.
  21. No problem, my config is on a vlan so bear in mind you wont be doing that presumably and thus the networking is simpler in your case:
  22. Just an update on this I took a backup removed the docker, renamed the folder in appdata, reinstalled and found even then it does not show as 'installed' when searching the app dockers so seems impossible to do this.
  23. Must be your setup because I just reinstalled as a test and the template works perfectly and updates lists etc no issue.
  24. Interesting. Is there a way to migrate to a new identical docker since now in the apps my when I search unifi it doesnt know its installed even if it is identical as it thinks the docker I have installed is different.