GreeffJl

Members
  • Posts

    21
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

GreeffJl's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi I have installed this plugin and it works well mounting my xfs filesystems, but i caanot mout my external usb drive which is NTFS? Any help would be appropriated Regards J
  2. Just tried that and got the same symptoms! I guess you might have found a bug in the current beta. It certainly USED to work. You can bypass the GUI and edit the file on the USB stick by editing /boot/config/ident.cfg (or flash/config/ident.cfg if done via the network). If you do it via the network then make sure you use an editor that understands Linux end-of-line characters. Thanks for the update, will change it as suggested for now. Regards I'd suggest doing when the array is stopped and then rebooting aftewards.
  3. Will do and reply back with results.
  4. Thats the problem, when I go to Identification, Change the name from Tower to Enigma adn apply, it just defaults back to Tower?
  5. This might sound stupid but I cannot change the server name from Tower to "Whatever". its just grayout. I have done this on previously builds? Running on the latest 64 bit build. Regards Jacques
  6. Ahh not to worry, I have figured it out. Just edit the xml and apply this in the docker apps. Thanks to myself :-)
  7. Hi I have binhex-sabnzbd docker installed and the the default weui url is https://<host>:8080 - I would like to change this to port 8090. How can I do this after the fact without rebuilding/downloading the docker. Many Thanks
  8. Hi Any help installing Slackware on KVM would be appricated. I have mastered some docker files, but would like to run a unifi controller on the VM Many Thanks
  9. I got the VM and running the install part, But there is no install disk? <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>windows_8.1</name> <uuid>cc411d70-4463-4db7-bf36-d364c0cdaa9d</uuid> <memory unit='GB'>4</memory> <currentMemory unit='GB'>4</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='q35'>hvm</type> <boot dev='cdrom'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/VM/Win81/win81.iso'/> <target dev='sdc' bus='sata'/> <readonly/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/VM/Win81/virtio-win-0.1-81.iso'/> <target dev='sdd' bus='sata'/> <readonly/> </disk> <disk type="file" device="disk"> <driver name="qemu" type="qcow2" /> <source file="/mnt/cache/VM/Win81/Win81.qcow2" /> <target dev="vda" bus="virtio" /> </disk> <controller type='sata' index='0'> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> </controller> <controller type='pci' index='2' model='pci-bridge'> </controller> <controller type='usb' index='0' model='none'> </controller> <interface type='bridge'> <source bridge='docker0'/> <model type='virtio'/> </interface> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <input type='mouse' bus='ps2'/> <memballoon model='virtio'/> </devices> </domain>
  10. All working, but my mouse is not working in the vnc console, any ideas?
  11. get the following error when i start the VN [code/ Error while starting domain: Cannot get interface MTU on 'br0': No such device Any idea?
  12. Hi, getting the following error on instances - webvirtmgr Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory any idea perhaps?
  13. This is what I get Tunables Report from unRAID Tunables Tester v2.2 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --------------------------------------------------------------------------- 1 | 1280 | 768 | 384 | 0.0 MB/s 2 | 1408 | 768 | 512 | 0.0 MB/s 3 | 1536 | 768 | 640 | 0.0 MB/s 4 | 1664 | 768 | 768 | 0.0 MB/s 5 | 1920 | 896 | 896 | 0.0 MB/s 6 | 2176 | 1024 | 1024 | 0.0 MB/s 7 | 2560 | 1152 | 1152 | 0.0 MB/s 8 | 2816 | 1280 | 1280 | 0.0 MB/s 9 | 3072 | 1408 | 1408 | 0.0 MB/s 10 | 3328 | 1536 | 1536 | 0.0 MB/s 11 | 3584 | 1664 | 1664 | 0.0 MB/s 12 | 3968 | 1792 | 1792 | 0.0 MB/s 13 | 4224 | 1920 | 1920 | 0.0 MB/s 14 | 4480 | 2048 | 2048 | 0.0 MB/s Completed: 0 Hrs 0 Min 58 Sec. Best Bang for the Buck: Test 0 with a speed of 1 MB/s Tunable (md_num_stripes): 0 Tunable (md_write_limit): 0 Tunable (md_sync_window): 0 These settings will consume 0MB of RAM on your hardware. Unthrottled values for your server came from Test 0 with a speed of MB/s Tunable (md_num_stripes): 0 Tunable (md_write_limit): 0 Tunable (md_sync_window): 0 These settings will consume 0MB of RAM on your hardware. This is -115MB less than your current utilization of 115MB. NOTE: Adding additional drives will increase memory consumption. Not sure why?