david279

Members
 View Profile  See their activity

  • Posts

    827

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Report Comments posted by david279

    Unraid OS version 6.9.0-beta22 available

    in Prereleases

    Posted

    4 minutes ago, J89eu said:

    Yes I am

    Add this to the end of your VMs xml before the last domain line.

    Its a QEMU 5.0 bug that effects windows VM. 

    <qemu:commandline>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/>
  </qemu:commandline>

     

    • Like 1

    Unraid OS version 6.9.0-beta22 available

    in Prereleases

    Posted

    1 minute ago, ich777 said:

    I use 'br0' for all my VM's and half of my Docker Containers.

    I mean the model type for the ethernet bridge

      

    <interface type='bridge'>
      <mac address='52:54:00:36:3e:6d'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

    I should look like that.

    • Thanks 2

    Unraid OS version 6.9.0-beta22 available

    in Prereleases

    Posted

    42 minutes ago, alturismo said:

    ok, seems i was too fast, i guess its another issue why this happens

     

    when i read changelog again ;)

     

    webgui: VMs: change default network model to virtio-net

     

    this virtio-net does not exist here, i only have those

     

    image.thumb.png.b7a2a8181e228cd44ad392ed3701229b.png

     

    so i have chosen the virbr0 which is 192.168.122.0/24, whatever this is about cause i never added it.

     

    so, how can i add this virtio-net to unraid ?

     

    as note, when i add a new vm i also dont have the option, its still default to br0 and i can choose from br0, br1 or virbr0 only.

    Just go into the xml for the vm find the network section and edit virtio to virtio-net. 

    Unraid OS version 6.9.0-beta1 available

    in Prereleases

    Posted

    3 minutes ago, mikeyosm said:

    Just read this....

     

    https://blog.christophersmart.com/2019/12/18/kvm-guests-with-emulated-ssd-and-nvme-drives/

     

    Anyone tried this and measured performance compared with passthrough nvme?

    I tried this recently with a widows VM. Read performance was way higher than virtio blk/scsi but the write performance was about the same. I just setup a basic windows VM so i didnt test gaming or anything like that. 

    Unraid OS version 6.8.0-rc7 available

    in Prereleases

    Posted

    1 minute ago, Can0nfan said:

    Hi @limetech great work team 

     

    I didn’t seen anything about the missing VM’s issue from RC6 I’m still running RC5 because of that any word if this is resolved in RC7??

    Revert libvirt from 5.9.0 to 5.8.0 because 5.9.0 has bug where 'libvirt_list_domains()' returns an empty string when all

     

    In the notes above. I think this is the fix.

    • Like 2

    6.8.0 RC1+RC4 corrupted QCOW2 vdisks on XFS! warning "unraid qcow2_free_clusters failed: Invalid argument" propably due compressed QCOW2 files

    in Prereleases

    Posted

    13 minutes ago, darthcircuit said:

    Is there any way of manually updating qemu to 4.1 in RC5 or upcoming builds? I won't be using qcow2, especially compressed. I just pass through the whole controller for my windows 10 vm. Since 4.0.1 doesnt allow me to use the previous patch:

      

    
<qemu:commandline>
<qemu:arg value='-global'/>
<qemu:arg value='pcie-root-port.speed=8'/>
<qemu:arg value='-global'/>
<qemu:arg value='pcie-root-port.width=16'/>
</qemu:commandline>


    Which means my pcie lanes are only running at 1x speed. That will be a problem.

     

     

    image.png

    Are you using a AMD GPU? if not you could switch the machine type back to i440fx and that would give you the correct speeds. 

    [6.7.0-rc1] System Hard Lock

    in Prereleases

    Posted

    Im using the same motherboard as the OP and i haven't had a ryzen crash in a very long time. First this bug is pretty much on the first gen ryzen chip and setting the typical current option in the bios should solve it. I had a 1600x and was booted for months without a problem. I have a 2700x now still using the same motherboard and still no crashes. Im also on the newest F25 bios that i flashed friday, I was on F24 before that with no issues.