bastl
-
Posts
1267 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bastl
-
-
@SonWon As said thousand's of times before. DON'T USE UNRAIDS GUI for managing VMs. Use the web interface as it supposed to. The GUI mode is only for second choice "emergency use cases". Are you running your Windows machine in "Safe Mode" all the time? If so, you doin something wrong.
Video is running fine for me either using a VNC client from within a VM connecting to another VM, or from another machine. Same for RDP, AnyDesk or Teamviewer. Again, the Unraid OS is meant to be running "headless" without any desktop environment. What do you think 99,99% of the internet server infrastructure runninng on? On desktop operation systems or headless??? Sorry for that posting, but I tried to explain this a couple of times. 99,99% of the people here in the forum running Unraid connecting via the webinterface from another machine to manage their servers or from within a VM as it's supposed to be. The 0.01% having a monitor connected maybe using it every 3-4 months for trouble shooting or testing stuff.
-
19 minutes ago, SonWon said:
I don't need VNC when running KVM on top of a host OS so no performance hit.
You are wrong. No matter what host OS you're using there is always a "virtual" GPU involved in KVM if you get a window that shows you the guest desktop. With other words, no GPU no display output
Always think of a real PC. What shows on your monitor if the PC has no GPU? NOTHING!!!
I remember using virtmanager in Fedora to create my KVM VMs and there you had spice as option for a virtual GPU with similar performance to QXL. As I said before, there are tons of options to connect to your VM that has no real GPU. RDP for windows is kinda the best option, VNC or Anydesk, Teamviewer, NoMachine for Linux. And the difference between the spice client and vnc is marginal.
34 minutes ago, SonWon said:test running VMs without VNC or pass through if they are interested.
I guess you still not really understand how virtualisation works.
-
NO NO NO. QXL is a virtual GPU type. QXL basically works for every VM in Unraid. If you have 2 graphics cards, you can have 2 VMs using it. If you can put 3 or 4 in your system you can have 3 or 4 VMs with it's own high performance GPUs. Let's say you buy 4 1080ti's you can have up to 4 VMs running at the same time each with it's own 1080ti. I guess you don't really know what "passthrough" means. It means you handing over the real hardware to the VM. QXL is a "virtual" emulated GPU. You can have as much VMs with "virtual" GPUs as you like. You can't connect a real monitor to a "virtual" GPU so you need a piece of software to give you the picture this GPU produces. VNC, RDP, Teamviewer whatever. QXL has nothing to do with the graphics card you plug in your system. It's emulated by software! For basic office stuff, web browsing and media consumption a virtual GPU is fine. If you wanna play games or render videos or have some sort of 3D CAD simulation program you need a dedicated graphics card.
-
@SonWon You don't really get it 😂
If you don't want to run any application in the host system, why you want a desktop environment??? If you're using Arch or RedHat with an desktop environment YOU HAVE TO HAVE A GPU for that. Both distros could be run headless without a GPU as well. VMs you create from there is similar to Unraid
1. Option: virtual GPU (spice, QXL whatever)
- accessible via Spice Client, VNC or any other remote software from whatever device you like
- no GPU hardware acceleration
- worse performance as a real GPU
2. Option: passed through physical existing GPU
- access via directly connected monitor
- 3D acceleration for rendering, games to use your actual hardware
- better graphics performance
- GPU in use by a VM can't be used by another VM
Unraid, the host system is more like a "headless" virtualisation platform like XenServer, XCP-NG or VMware vSphere, not like a software solution like Virtualbox or VMware player where you need a host OS with it's own desktop environment. There is no need for an GPU to run Unraid. Same as for example FreeNas. YOU DON'T NEED A GPU. Unraid is more special and provides you the ability to boot in an desktop environment (GUI) but in this case YOU NEED A GPU. But it's kinda waste to use a GPU for starting or stoping your VMs if you work inside a VM anyway. Give the GPU to the VM you wanna use as a daily system and use it's 3D acceleration inside the VM and manage your server via the webui. But be aware you can't have 2 VMs running at the same time using that GPU. Otherwise you can have as much VMs as you like or better say, as your system can handle running in parallel with "virtual CPUs" and "virtual GPUs" as you like.
You have different choices for defining the virtual GPU (QXL, Cirrus, vmvga) in the VM settings. QXL mostly performs the best and the rest is more for compatibility reasons. You can access the VM via the webVNC client build into unraid or use a standalone client inside your main VM (the one with the GPU power) to access these VMs. You can also install whatever remote software you want inside each VM to access it and control it. RDP, AnyDesk, NoMachine or Teamviewer. It's up on you. You don't need to use the build in webVNC, only for first install of the VMs OS and the initial setup the webVNC is needed.
-
Aside from the GUI not working, you only need 2 GPUs for your needs. Same as I, setup your a webbrowsing, mail, media VM with a GPU and a Gaming VM with a second GPU. As I said before, there is no need for using Unraids GUI if you can manage it from within a VM anyways. Unraid will work without a GPU without any issues
-
No one said you require your Win10 VM to access Unraid. I gave you 4 other Options to manage your server without using a Windows VM or using the Unraid GUI. Now explain me, why are you not using one of your Linux VMs if you don't trust MS? You posted above you have 2 VMs using the 1030.
Maybe I don't really get your point. You're starting your server without any VMs and than decide everytime what you wanna do and manual start the specific VM? Are you controlling all your VMs except from the gaming VM via WebVNC from the GUI only? Is this the case, why not using a dedicated VM you already have for this purpose?
-
9 minutes ago, SonWon said:
How when the I cannot get to the VMs because the Unraid gui didn't start? Even with them auto starting they are not accessible without the gui running.
You don't need the gui to access a VM with a GPU passed through. Thats the main purpose to have a dedicated GPU inside a VM. Plug a Monitor into that GPU and if everything is setup correctly, you should see the Desktop of your VM. Sure you need an keyboard and a mouse attached to the VM to controll it, but isn't that what you're already doin with your gaming VM?
Example from my usecase. A linux VM for managing Unraid and light web browsing and office stuff with it's own GPU and mouse, BT dongle for keyboard passed through. And I have a second VM with Windows installed for gaming with it's own GPU and mouse and an USB keyboard. Both connected to the same monitor (HDMI, DisplayPort) to switch between the VMs I have to press a button on the monitor to switch the input source and a hotkey on the keyboard to switch between Bluetooth or USB connection.
If you struggle to get the GUI working and only want wo start or stop a VM you can use a SSH client on your phone or tablet, connect to your server and type
virsh start VMNAME or virsh stop VMNAME -
Use one of your "two Linux VMs running on the GeForce GT 1030" instead.
Edit:
You can also use a SSH connection to the server to control your VMs if you like and in case you don't trust any HTTPS traffic to your server.
-
Set the VMs to Autostart or at least the one you have a GPU passthrough and use that to access the webui. You can also access the webui via a phone or a tablet to start and stop your VMs if you wanna do it manual all the time. Or another option is to use the ControlR app on your phone to start stop dockers or VMs.
-
Short question, why you wanna use the Unraid Gui at all? Use the webui like everyone else. The GUI isn't really for day to day use. See it as more like a fallback option if you have no network for example. I remember someone in the forum posted something about his dad has some issues with the Unraid GUI browsing the web. A horrible idea to use the Unraid GUI as a daily driver.
-
I had it once on the first day testing the RC4. Same behaviour, webterminal stopped responding, no log entry and a reboot fixed it. Last thing I did before it happenned was using a btrfs command to list my snapshots on an unassigned device and it froze. Sorry no diags.
-
Same happened to me right now on 6.7.0 RC3.
1: Created a new Win10 VM succesful
2: Edit that VM and add a USB Device for example or a GPU or change the name, doesn't matter
3: hit the Update button and it will never finish updating
Picture below shows the current settings. 2 USB devices i had to add manualy cause the initial config couldn't been changed. Nothing else has been placed or changed in the xml after the first creation.
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='38'> <name>W10_4</name> <uuid>b7b73747-6358-d959-c4e5-563197f607e9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='21'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='22'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <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/b7b73747-6358-d959-c4e5-563197f607e9_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='raw' cache='writeback'/> <source file='/mnt/user/VMs/W10_test/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='nec-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c5:e3:5e'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-38-W10_4/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc517'/> <address bus='1' device='4'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x0aa7'/> <address bus='1' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04fc'/> <product id='0x0003'/> <address bus='3' device='4'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
-
Looks like on 6.7.0 RC3 it's fixed for me now.
-
I guess the issue is there are no different branches for the plugins. Always keep in mind mostly one guy is maintaining a specific addon and i guess mostly in their spare time for FREE. Maintaining the addons and maybe make them backwards compatible for lets say 5 years all in their own branches, i don't know. That might be something you overlook. I more like to have a up to date software than an perfect balanced design. Maybe we will see some sort of additional icon packs in the future. Who knows. Maybe you're able to code something like that and maintain it for the community. 😁
-
As with every design change some people will complain they don't like it. Understandable and ok in my opinion. If it's a new series of cars trying to push a new design language, the packaging of your favorite fast food or some sort of software. In my opinion i always liked the more cleaner design and i think limetech did a great job
-
-
If it crashes your OC isn't stable
You know what to do, right?
-
Ah ok. Now i get your point. Maybe a good idea to post your diagnostics for the devs to have a deeper look into it. I never tried to use Unraid on a platform that hasn't virtualisation support neither do i have some hardware laying around to test with. I guess that virtualisation without HW support would work but extremly slow. I don't really know how it's implemented, but on a standard Linux distro if there is no support KVM modules aren't used and in this case only Qemu is used for virtualisating an guest OS. It's basically a software virtualisation in this case similar to Virtualbox but way slower.
-
Enable virtualisation support (Intel-VT-x or AMD-V) in your BIOS depends on what CPU u are using.
-
Weird. It happened again on 6.7.0 RC2 same as yesterday over night the message comes back up. I have no idea whats causing it. I have a BTRFS snapshot script for my VMs which is running every morning at 6am and a second script starting one VM every morning at 7:30am. Running them by hand don't show this effect. Any ideas?
-
I did the same thing as yesterday. Changed the permisson for one of my users for one share and it disappeared.
last log entries:
Jan 25 10:35:49 UNRAID emhttpd: req (6): shareName=VMs&userAccess.0=no-access&userAccess.1=read-only&userAccess.2=no-access&changeShareAccess=Apply&csrf_token=**************** Jan 25 10:35:49 UNRAID emhttpd: Starting services... Jan 25 10:35:49 UNRAID emhttpd: shcmd (97): /etc/rc.d/rc.samba restart Jan 25 10:35:51 UNRAID root: Starting Samba: /usr/sbin/nmbd -D Jan 25 10:35:51 UNRAID root: /usr/sbin/smbd -D Jan 25 10:35:51 UNRAID root: /usr/sbin/winbindd -D Jan 25 10:35:51 UNRAID emhttpd: shcmd (106): smbcontrol smbd close-share 'VMs' -
Before i went to bed yesterday i checked and "services starting" wasn't there. And now it's back again.
-
If you decrease the width of the browser on your desktop you see 2 columns at some point. The page dynamically adjusts the columns from 2 to 3
-
Maybe some helpful informations. My array drives are XFS formated and I only have the cache drive and some unassigned devices using BTRFS. Reading/writing to this drives for me doesn't show these errors. Looks like only the array is affected.
Always think of a real PC. What shows on your monitor if the PC has no GPU? NOTHING!!!
Unraid OS version 6.7.0-rc6 available
-
-
-
-
-
in Prereleases
Posted
I had the exact same happen yesterday. The fix common problems plugin reported exactly the same. @limetech I usual only have 1 physical nic in use with the standard br0 and virbr0. A couple days ago I had set up a bridge on a second ethernet port without a cable connected and an fixed ip 192.168.0.6/24 No issues on RC5. Dockers worked as usual and no errors in FCP. I only used that new bridge on one single VM for testing but reverted back to br0. I forgot to remove the br2 again. On RC6 yesterday I tried to ping 1.1.1.1 from the console and the the target couldn't be reached. Unraid tried to connect to the internet via that second port I had configured. "192.168.0.1 no answer" I removed the bridge and all went back to normal.