Jump to content

vanstinator

Members
  • Posts

    71
  • Joined

  • Last visited

Posts posted by vanstinator

  1. 16 hours ago, saarg said:

    What a shitshow unifi is regarding software... I can't believe they sell hardware that needs beta software.

    To be totally fair it's also beta hardware. So I get the requirement. At any rate I cloned the repo and manually built the image I needed for now. I'll hop back over when it ships to stable

  2. On 7/17/2019 at 5:12 PM, DayspringGaming said:

    Yup. I have all the XML pasted in correctly, have all the vdisks set as SATA with #1 as the Clover Qcow2 file, #2 as the High Sierra .IMG file and #3 is the 50gb install disk. 

    Pretty much followed the video to the letter - just not getting an icon to install anything.

     

    I've done the same. Created 3 disks. #1 clover.qcow2 (from the zip file in the video), #2 mojave.img (created myself) #3 vdisk3. The system boots to clover just fine. But there's not an install option for the OS. Just a row of clover options. If anyone else has run into this and has any suggestions that I can try I'd really appreciate it!

     

    My XML is as follows: 

     

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
      <name>Mojave</name>
      <uuid>0ef26eff-b13d-925f-ed4c-db47768e784e</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/>
      </metadata>
      <memory unit='KiB'>8388608</memory>
      <currentMemory unit='KiB'>8388608</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>8</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
        <vcpupin vcpu='1' cpuset='4'/>
        <vcpupin vcpu='2' cpuset='1'/>
        <vcpupin vcpu='3' cpuset='5'/>
        <vcpupin vcpu='4' cpuset='2'/>
        <vcpupin vcpu='5' cpuset='6'/>
        <vcpupin vcpu='6' cpuset='3'/>
        <vcpupin vcpu='7' cpuset='7'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/0ef26eff-b13d-925f-ed4c-db47768e784e_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' cores='4' threads='2'/>
      </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>
        <disk type='file' device='disk'>
          <driver name='qemu' type='qcow2' cache='writeback'/>
          <source file='/mnt/user/domains/Mojave/clover.qcow2'/>
          <target dev='hdc' bus='sata'/>
          <boot order='1'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/Mojave/mojave.img'/>
          <target dev='hdd' bus='sata'/>
          <address type='drive' controller='0' bus='0' target='0' unit='3'/>
        </disk>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/Mojave/vdisk3.img'/>
          <target dev='hde' bus='sata'/>
          <address type='drive' controller='0' bus='0' target='0' unit='4'/>
        </disk>
        <controller type='pci' index='0' model='pcie-root'/>
        <controller type='pci' index='1' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='1' port='0x10'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
        </controller>
        <controller type='pci' index='2' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='2' port='0x11'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
        </controller>
        <controller type='pci' index='3' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='3' port='0x12'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
        </controller>
        <controller type='pci' index='4' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='4' port='0x13'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
        </controller>
        <controller type='sata' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
        </controller>
        <controller type='usb' index='0' model='ich9-ehci1'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci1'>
          <master startport='0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci2'>
          <master startport='2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci3'>
          <master startport='4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:df:22:62'/>
          <source bridge='br0'/>
          <model type='vmxnet3'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </interface>
        <serial type='pty'>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
        <channel type='unix'>
          <target type='virtio' name='org.qemu.guest_agent.0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <address type='usb' bus='0' port='1'/>
        </input>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </memballoon>
      </devices>
      <qemu:commandline>
        <qemu:arg value='-usb'/>
        <qemu:arg value='-device'/>
        <qemu:arg value='usb-mouse,bus=usb-bus.0'/>
        <qemu:arg value='-device'/>
        <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
        <qemu:arg value='-device'/>
        <qemu:arg value='isa-applesmc,osk=somekey'/>
        <qemu:arg value='-smbios'/>
        <qemu:arg value='type=2'/>
        <qemu:arg value='-cpu'/>
        <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,vmware-cpuid-freq=on,'/>
      </qemu:commandline>
    </domain>

     

     

  3. Can someone ELI5 what Enable Copy-On-Write: in the add-share screen does? I saw it get added to 6.X and I only partially understood what was going on. I for the life of me can't find those patch notes to read over it again. I'm adding a new share, first since this feature was added, and I'm not sure what to set it to...

  4. HDSentinel is a great program. I use it in all 10 of my computers. There is a Pro Windows version, an Enterprise version (server), a Linux version, a Linux daemon version, a home version, and a free trial version that never expires (it just lacks some of the higher order functions). The guy who runs the company and develops the program, Janos, is a gem of a human being. He is as valuable as the product itself. Finding nice, helpful technical experts who will actually talk with you, is just refreshing. Even back when I was only using the trial version, Janos was more than happy to help me problem solve. He is why I went so strongly with HDS, that and the program itself and it's capabilities. And there are others here who feel the same way. As JudyZ's comments will attest -- I liked Janos' HDS program so much that I installed it on my Linux computers too. But Installation and use was strictly manual, command-line stuff in Linux. And it overwrites the report each time you run it, unless you manually rename the old report before you run HDS again. So I wrote a couple simple scripts, to help automate the installation, put launchers in a couple logical places, and give you an automated way to run the program, generate a new report, and save it automatically, with the date/time in the filename, thereby building a library of searchable reports.  HDSentinel is a gem, it does a great many basic tasks really well. Plus it helps you avoid catastrophic failures, premature retirements of drives, and gives you options for reclaiming or salvaging a disk with issues.

     

    http://www.hdsentinel.com/  -- general info and links

    http://www.hdsentinel.com/add-on-linux-installers.php -- the program bundled with my installers and scripts

     

    Now Janos, Judy and I are working on a way to include the HDS Daemon on an unRAID USB drive, have it run  automatically at startup, and have its output be monitored by the Enterprise (server) version of HDS either in Docker or remotely.

     

    So this is old, but wondering if there was any traction on this? I'm actually looking for just a solution. While I love the unraid SMART if I could add those drives to a dashboard like HDSentinel that would be awesome.

  5. Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

     

    Along with my earlier question how do I turn off https forcing? I'm working on getting this setup behind my entire public facing reverse proxy with an actual signed cert I have, so I don't want nginx/owncloud creating and forcing https at this layer.

  6. Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

×
×
  • Create New...