SimonF

Community Developer
  • Posts

    4024
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by SimonF

  1. they are normally update in major version Currently is 8.1.x for qemu and 10.x for libvirt
  2. should be ttys0 to 4 for physical s0 is com1 s3 is com4
  3. ls /dev/tty* https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/ screen can be download from nerdtools plugin I think.
  4. if detected would show as ttysx device where x is a number Do you have enabled in bios?
  5. License is tied to the usb flash boot drive. So you can clear config and move to a different machine.
  6. Have you hidden the panel. Click on padlock to unlock spanner should appear on the system panel. Click and check panels selected.
  7. Can you elaborate on the above statement? more details on which type of vgpu support, i.e. GVT-g, sr-vio or something else?
  8. Yes the docker needs to use the host based drivers. As soon as you bind to vfio the host cannot no longer use the card and hence the docker does see the card. You either need to have two cards or gpus that support splitting up(GVT/sr-vio), but this would not support output to a screen for the VM. Just would provide gpu accelaration.
  9. So the USB device is remove from the VM in the template? How do you re-add the device to the xml. You could try using my USB Manager and see if that fixes you issue. Not sure why the template option does not work. If you can provide screen shots before and after, also a new syslog just after you start the VM. Example settings below for a USB Bluetooth device. If you use this method you dont need to have in VM template.
  10. As ich777 said you need to install the gpu stats plugin + the corresponding driver package which you already have installed.
  11. Maybe because you are using the older version of GPU Stats that is not 100% compatible with 6.12+ You need to be using my version from CA.
  12. If you are not using PCI passthru you can either leave blank or remove. Changes where made to stop autostart if vfio binding fails as could indicate PCI numbers have chaged due to hardware removal/additions etc. If the VM autostarts and now as the wrong device is allocated to the VM due to PCI number changes it could lookup or crash the host. Before 07:00.0 VGA Card(Passthru to VM) 08:00.0 Disk Controller(Unraid) After 07:00.0 DIsk Controller(Unraid) If the VM autostarts the diskcontroller would be allocated to the VM and all the Unraid disks would not been seen on the host as a simple example.
  13. Not sure if it is related, but you seem to be getting lots of connect errors in the logs. But you dont seem to have it installed. I cannot see any issues so far in the logs for the USB/Vm issue. It may be work disabling bluetooth on the host.
  14. I thought I had implemented but will look over the weekend. Normally when a usb device disconnects it is automatically removed from the guest.
  15. Looks like you had a 2060 bound to vfio on 1:00.x which is no longer there. and a device at 09:00.0 if you don't need them delete the vfio file and next reboot you should be ok.
  16. 1024Gb is 1Tb? But it will start as a sparse file so the vdisk on the physical disk will be smaller until data is put into it.
  17. Unraid uses the php api. I can look at managed save as a option which is hibernate to disk libvirt_domain_suspend libvirt_domain_suspend($res) [Since version 0.4.1(-1)] Function is used to suspend the domain identified by it's resource. @res [resource]:libvirt domain resource, e.g. from libvirt_domain_lookup_by_*() Returns:: TRUE for success, FALSE on error libvirt_domain_managedsave libvirt_domain_managedsave($res) [Since version 0.4.1(-1)] Function is used to managed save the domain (domain was unloaded from memory and it state saved to disk) identified by it's resource. @res [resource]:libvirt domain resource, e.g. from libvirt_domain_lookup_by_*() Returns:: TRUE for success, FALSE on error
  18. Change in settings from yes to know on the VM Manager settings. if status is running still this means that Libvirt is still running, But will sort after next reboot. Or you can just change to Yes and then no and apply.
  19. Service needs to be disabled to stop libvirt and remote the VMS opions.
  20. I am lookingto see how this can be implemented, the rust version in the next released is stored in /usr/bin and we have a symlink from /usr/libexec to the new binary. So we could change the symlink to a wrapper to do the additional processing. I have also asked libvirt team if they have a time scale to implement in XML. Looking at the old args we should be able to build new args as follows. Old --fd=45 -o source=/mnt/cache,cache=always,sandbox=chroot,xattr /usr/libexec/virtiofsd \ --fd="$FD" \ # From fd= --shared-dir="/mnt/user/Music" \ # From source= --xattr \ # From sandbox --cache="never" \ #From cache= --sandbox="chroot" \ #From sandbox --inode-file-handles="mandatory" \ # Add as default --announce-submounts #Add as default. @jchIs there a reason for cache = "never" ?