rmk

It's only on install but I had to downgrade libvirt to 1.2.6 to get network functionality within virt-manager or webvirtmgr. Otherwise you would see an error that it wasn't supported. I opened up a thread in the defect forum hoping they will include network support in their version. Edit: I don't really like the idea of restarting it cause when I added your repo the other night i forgot and was watching tv and it rebooted my mythbuntu vm. I think maybe I should make a separate libvirt plugin to install 1.2.6, include the scripts to symlink libvirt and start and stop with the array and enable tcp listen. I posted some scripts in a separate thread a few days ago to manage Libvirt. I agree with having the this all part of a separate package. My scripts are intended to bring all domains up once the array is online and bring them down gracefully prior to stopping the array. While writing them, I discovered the slackware Libvirt scripts always stop all instances when Libvirt is stopped, which is a terrible assumption. I ended up killing libvirtd directly and removing the pid file in my script.

What's the reason for restarting libvirtd within the plugin? https://github.com/dmacias72/webvirtmgr_unRAID_6/blob/master/webvirtmgr.plg#L1033-L1035

Forward whatever the websocket ports are for your domains. Your browser is making a direct websocket connection to the domain via novnc (it's all client side).

To get VNC going, make sure you have a VNC graphics device with websockets enabled, like so: <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' passwd='somethingcomplexrandom'> <listen type='address' address='0.0.0.0'/> </graphics> The reason -1 is used for ports is to let libvirt figure out a port and dynamically assign one. If you prefer, you can statically assign unique ports of your choosing. You will not need to know the ports or the password (use something complex/random) when using WebVirtMgr. The password is important (not that it represents real security) because there's no actual proxy being used here, so VNC ports will be exposed to the entire network. To be clear, you do not need websockify at all when using the aforementioned approach. Websockify exists to convert a TCP socket into a web socket. QEMU has supported directly exposing VNC as a websocket for some time now, which is all we're enabling here.

No problem. I'll help get vnc going tomorrow. It's the same approach as what is used with OpenStack Nova, so it shouldn't be too difficult.

I just submitted a patch to WebVirtMgr which should make setup significantly easier. https://github.com/rmk40/webvirtmgr https://github.com/rmk40/webvirtmgr/commit/65973c914455e82627f8e96176ae4da7dcf19ca1 It'll allow for using a local socket to connect to Libvirt and will eliminate the need to specify a hostname or login credentials. The patch is pending a pull request so hopefully it'll be upstream soon but this plugin is welcome to pull directly from my repo in the meantime.

Unvirt is a set of scripts to be used with Libvirt for properly starting and stopping domains (virtual machines). The scripts are designed to bring your instances online when your array is brought up and shut them down prior to stopping the array. Installation: [*]Download this package: https://dl.dropboxusercontent.com/u/15034469/unraid/unvirt-1.0.0-noarch-unRAID.tgz [*]Place a copy of the package in /boot/extra [*]Either reboot unRAID or run 'installpkg /boot/extra/unvirt-1.0.0-noarch-unRAID.tgz' via SSH/Telnet Usage: Unvirt expects are particular directory structure and naming schema. [*]Create a directory in /mnt/user called 'virtual_machines' [*]Each domain (VM) needs to be in a separate directory. For example, create a new directory: /mnt/user/test_vm. This directory must contain test_vm.xml to define your domain. [*]Start your array, all the domains will be started. [*]Stop your array, the domains will be given 60 seconds each to shutdown gracefully before they are hard terminated You can control both the location of the virtual machines directory and shutdown timeout by creating a config file. /boot/config/plugins/libvirt/libvirt.cfg: # Timeout value in seconds to wait for graceful VM shutdown TIMEOUT=60 # Top level directory for your domains. Must contain sub directories # for each domain with a .xml file of the same name of the directory # present. VM_ROOT_DIR=/mnt/user/virtual_machines Suggestions and feedback is welcome.