Creating vm error

● vdi-agent.service - KZVM-VDI agent
   Loaded: loaded (/etc/systemd/system/vdi-agent.service; enabled)
   Active: active (running) since Thu 2016-09-15 11:59:32 CEST; 2min 18s ago
 Main PID: 603 (python)
   CGroup: /system.slice/vdi-agent.service
           └─603 python /usr/local/VDI/vdi-agent

Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: Exception in thread Thread-1:
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: Traceback (most recent call last):
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: self.run()
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/lib/python2.7/threading.py", line 763, in run
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: self.__target(*self.__args, **self.__kwargs)
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/local/VDI/vdi-agent", line 96, in vm_routine
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: thread.exit()
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: NameError: global name 'thread' is not defined

Any idea ?

Looks like threading isn't pulled into the namespace correctly but works
fine for him on debian and me on rhel but we are both running older Python
versions.  Are you running Python 3.3?
Developer will need to look at this one and modify import line to
accommodate your platform I think.  Guessing though.
On Sep 15, 2016 7:03 AM, "Nickeloerus"<EMAIL_ADDRESS>wrote:

● vdi-agent.service - KZVM-VDI agent
Loaded: loaded (/etc/systemd/system/vdi-agent.service; enabled)
Active: active (running) since Thu 2016-09-15 11:59:32 CEST; 2min 18s ago
Main PID: 603 (python)
CGroup: /system.slice/vdi-agent.service
└─603 python /usr/local/VDI/vdi-agent
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: Exception in thread Thread-1:
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: Traceback (most recent call last):
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: self.run()
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/lib/python2.7/threading.py", line 763, in run
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: self.__target(*self.__args, **self.__kwargs)
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: File "/usr/local/VDI/vdi-agent", line 96, in vm_routine
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: thread.exit()
Sep 15 12:01:47 pica-hvm-01 vdi-agent[603]: NameError: global name 'thread' is not defined
Any idea ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59, or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX-ojK4jHXo5-eLD0WMCQp3f0ETVgks5qqRf5gaJpZM4J9sg6
.

This should fix  issue.

root@pica-hvm-01:~# systemctl status vdi-agent -l
● vdi-agent.service - KZVM-VDI agent
   Loaded: loaded (/etc/systemd/system/vdi-agent.service; enabled)
   Active: active (running) since Thu 2016-09-15 13:08:42 CEST; 2min 35s ago
 Main PID: 603 (python)
   CGroup: /system.slice/vdi-agent.service
           └─603 python /usr/local/VDI/vdi-agent

Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: no element found at line 2, column 0, byte 1:
Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: ^
Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: failed to get domain 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: Domain not found: no domain with matching name 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: failed to get domain 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: Domain not found: no domain with matching name 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: no element found at line 2, column 0, byte 1:
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: ^
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.

it fixed the thread issue, but have another now

Are you using fqdn for the domain you're joining?  How many machines in the
domain?
On Sep 15, 2016 8:12 AM, "Nickeloerus"<EMAIL_ADDRESS>wrote:

root@pica-hvm-01:~# systemctl status vdi-agent -l
● vdi-agent.service - KZVM-VDI agent
Loaded: loaded (/etc/systemd/system/vdi-agent.service; enabled)
Active: active (running) since Thu 2016-09-15 13:08:42 CEST; 2min 35s ago
Main PID: 603 (python)
CGroup: /system.slice/vdi-agent.service
└─603 python /usr/local/VDI/vdi-agent
Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: no element found at line 2, column 0, byte 1:
Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: ^
Sep 15 13:10:40 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: failed to get domain 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: Domain not found: no domain with matching name 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: failed to get domain 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: error: Domain not found: no domain with matching name 'Win10'
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: no element found at line 2, column 0, byte 1:
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: ^
Sep 15 13:11:12 pica-hvm-01 vdi-agent[603]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
it fixed the thread issue, but have another now
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-247300331,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX8Y_jySumQl44qMqEapwVKWanq8Nks5qqSgogaJpZM4J9sg6
.

This is different kind of domain - this is what they call VMs in libvirt/qemu.
Do you have xpath installed? which xpath

yes have xpath installed
libxml-xpath-perl is already the newest version.
what am i doing wrong?
could be me but i find it hard too even get it running

What about vms? Do they exist? virsh list --all

root@pica-hvm-01:~# virsh list --all
 Id    Name                           State
----------------------------------------------------

root@pica-hvm-01:~#

no they dont

So vm creation failed. You can delete entry in dashboard and try creating vm again.

If it fails again, enable debug in your dashboard and look at web server log files.

Thread-1 2016-09-15 14:19:11,767 root         INFO     Starting machine Win10
Thread-1 2016-09-15 14:19:11,868 root         DEBUG    Opening socket []
Thread-1 2016-09-15 14:19:11,868 root         WARNING  Virtio socket failure for VM: Win10
Thread-1 2016-09-15 14:19:11,868 root         DEBUG    Closing vm Win10, login thread

This is self explanatory. VM "Win10" does not have kvm-vdi socket created. This usually happens when VM was created using different tool, than KVM-VDI dashboard. To solve this, run /usr/local/VDI//vdi-xmledit -name Win10 on hypervisor.

The vm is created in the KVM-VDI dashboard..
here is syslog
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Starting Session 29 of user VDI.
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Started Session 29 of user VDI.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Starting Paths.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Reached target Paths.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Starting Timers.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Reached target Timers.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Starting Sockets.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Reached target Sockets.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Starting Basic System.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Reached target Basic System.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Starting Default.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Reached target Default.
Sep 16 09:29:19 pica-hvm-01 systemd[1391]: Startup finished in 5ms.
Sep 16 09:29:19 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopping Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopped target Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopping Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopped target Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopping Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopped target Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopping Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopped target Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopping Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Stopped target Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Starting Shutdown.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Reached target Shutdown.
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Starting Exit the Session...
Sep 16 09:29:20 pica-hvm-01 systemd[1391]: Received SIGRTMIN+24 from PID 1403 (kill).
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Starting Session 30 of user VDI.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Started Session 30 of user VDI.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Startup finished in 5ms.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopping Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopped target Default.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopping Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopped target Basic System.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopping Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopped target Paths.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopping Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopped target Timers.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopping Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Stopped target Sockets.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Shutdown.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Reached target Shutdown.
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Starting Exit the Session...
Sep 16 09:29:20 pica-hvm-01 systemd[1410]: Received SIGRTMIN+24 from PID 1422 (kill).
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:29:20 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Starting Session 31 of user VDI.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Started Session 31 of user VDI.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Paths.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Paths.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Timers.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Timers.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Sockets.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Sockets.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Basic System.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Basic System.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Default.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Default.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Startup finished in 5ms.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopping Default.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopped target Default.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopping Basic System.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopped target Basic System.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopping Paths.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopped target Paths.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopping Timers.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopped target Timers.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopping Sockets.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Stopped target Sockets.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Shutdown.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Reached target Shutdown.
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Starting Exit the Session...
Sep 16 09:29:34 pica-hvm-01 systemd[1429]: Received SIGRTMIN+24 from PID 1438 (kill).
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:29:34 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:30:37 pica-hvm-01 systemd[1]: Starting Session 32 of user root.
Sep 16 09:30:37 pica-hvm-01 systemd[1]: Started Session 32 of user root.
Sep 16 09:33:22 pica-hvm-01 systemd[1]: Starting Session 33 of user root.
Sep 16 09:33:22 pica-hvm-01 systemd[1]: Started Session 33 of user root.
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Starting Session 34 of user VDI.
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Started Session 34 of user VDI.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Starting Paths.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Reached target Paths.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Starting Timers.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Reached target Timers.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Starting Sockets.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Reached target Sockets.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Starting Basic System.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Reached target Basic System.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Starting Default.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Reached target Default.
Sep 16 09:38:09 pica-hvm-01 systemd[1458]: Startup finished in 5ms.
Sep 16 09:38:09 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:38:10 pica-hvm-01 kernel: [72860.882525] tun: Universal TUN/TAP device driver, 1.6
Sep 16 09:38:10 pica-hvm-01 kernel: [72860.882528] tun: (C) 1999-2004 Max Krasnyansky<EMAIL_ADDRESS>Sep 16 09:38:10 pica-hvm-01 libvirtd[639]: libvirt version: 1.2.9, package: 9+deb8u3 (buildd 2016-07-01-18:17:10 x86-grnet-01)
Sep 16 09:38:10 pica-hvm-01 libvirtd[639]: Cannot get interface MTU on 'br0': No such device
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopping Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopped target Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopping Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopped target Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopping Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopped target Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopping Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopped target Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopping Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Stopped target Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Starting Shutdown.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Reached target Shutdown.
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Starting Exit the Session...
Sep 16 09:38:10 pica-hvm-01 systemd[1458]: Received SIGRTMIN+24 from PID 1488 (kill).
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Starting Session 35 of user VDI.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Started Session 35 of user VDI.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Startup finished in 4ms.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopping Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopped target Default.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopping Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopped target Basic System.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopping Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopped target Paths.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopping Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopped target Timers.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopping Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Stopped target Sockets.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Shutdown.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Reached target Shutdown.
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Starting Exit the Session...
Sep 16 09:38:10 pica-hvm-01 systemd[1495]: Received SIGRTMIN+24 from PID 1507 (kill).
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:38:10 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Starting Session 36 of user VDI.
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Started Session 36 of user VDI.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Starting Paths.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Reached target Paths.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Starting Timers.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Reached target Timers.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Starting Sockets.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Reached target Sockets.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Starting Basic System.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Reached target Basic System.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Starting Default.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Reached target Default.
Sep 16 09:38:30 pica-hvm-01 systemd[1517]: Startup finished in 5ms.
Sep 16 09:38:30 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: error: failed to get domain 'test2'
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: error: Domain not found: no domain with matching name 'test2'
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: error: failed to get domain 'test2'
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: error: Domain not found: no domain with matching name 'test2'
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: no element found at line 2, column 0, byte 1:
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: ^
Sep 16 09:38:30 pica-hvm-01 vdi-agent[604]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopping Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopped target Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopping Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopped target Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopping Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopped target Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopping Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopped target Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopping Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Stopped target Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Starting Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Reached target Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Starting Exit the Session...
Sep 16 09:38:31 pica-hvm-01 systemd[1517]: Received SIGRTMIN+24 from PID 1535 (kill).
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting Session 37 of user VDI.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Started Session 37 of user VDI.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Startup finished in 4ms.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopping Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopped target Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopping Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopped target Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopping Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopped target Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopping Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopped target Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopping Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Stopped target Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Reached target Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Starting Exit the Session...
Sep 16 09:38:31 pica-hvm-01 systemd[1541]: Received SIGRTMIN+24 from PID 1553 (kill).
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Created slice user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting User Manager for UID 1001...
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Starting Session 38 of user VDI.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Started Session 38 of user VDI.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Startup finished in 5ms.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Started User Manager for UID 1001.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping User Manager for UID 1001...
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopping Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopped target Default.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopping Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopped target Basic System.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopping Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopped target Paths.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopping Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopped target Timers.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopping Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Stopped target Sockets.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Reached target Shutdown.
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Starting Exit the Session...
Sep 16 09:38:31 pica-hvm-01 systemd[1559]: Received SIGRTMIN+24 from PID 1571 (kill).
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopped User Manager for UID 1001.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Stopping user-1001.slice.
Sep 16 09:38:31 pica-hvm-01 systemd[1]: Removed slice user-1001.slice.

What does
cat /etc/libvirt/qemu/Win10.xml | grep kvm-vdi give you?

root@pica-hvm-01:~# cat /etc/libvirt/qemu/Win10.xml | grep kvm-vdi
cat: /etc/libvirt/qemu/Win10.xml: No such file or directory

There is no delete button for simple machine in dashboard is that correct ?

Are you sure you have VM in your hypervisor?
virsh list --all |grep Win10
Delete button for infrastructure VMs (so called simple machines) is removed on purpose.

VM will not even show up in virsh when created or started.
root@pica-hvm-01:~# virsh list --all
 Id    Name                           State
----------------------------------------------------

agent status keeps giving me
vdi-agent.service - KZVM-VDI agent
   Loaded: loaded (/etc/systemd/system/vdi-agent.service; enabled)
   Active: active (running) since Fri 2016-09-16 09:48:03 CEST; 3min 25s ago
 Main PID: 604 (python)
   CGroup: /system.slice/vdi-agent.service
           └─604 python /usr/local/VDI/vdi-agent

Sep 16 09:48:03 pica-hvm-01 systemd[1]: Starting KZVM-VDI agent...
Sep 16 09:48:03 pica-hvm-01 systemd[1]: Started KZVM-VDI agent.
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: error: failed to get domain 'test4'
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: error: Domain not found: no domain with matching name 'test4'
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: error: failed to get domain 'test4'
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: error: Domain not found: no domain with matching name 'test4'
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: no element found at line 2, column 0, byte 1:
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: ^
Sep 16 09:49:35 pica-hvm-01 vdi-agent[604]: at /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
root@pica-hvm-01:~#

and vdi-agent.log
Thread-1 2016-09-16 09:49:35,839 root         INFO     Starting machine test4
Thread-1 2016-09-16 09:49:35,944 root         DEBUG    Opening socket []
Thread-1 2016-09-16 09:49:35,944 root         WARNING  Virtio socket failure for VM: test4
Thread-1 2016-09-16 09:49:35,944 root         DEBUG    Closing vm test4, login thread

do i need too give user VDI extra rights beside DATA or something?

Empty list from virsh list -all means that dashboard failed to create VM. You can delete non existing VMs from dashboard.
To get more information, what happens when you create VM, you should enable debug log in config php: $write_debug_log=true;
Then try creating new VM. Then look at your webserver error.log. You should see debug output there.
Sudo rights provided in hypervisors/sudoers file should be enough for VDI user.

i have a quick comment here if it helps you... make sure selinux/apparmor is turned off and that you are not trying to run any of the components from /home because there is a bug in centos that causes selinux to trigger despite being set in permissive mode.  it needs to be disabled completely.

As i've mentioned before, it seems, that KVM-VDI fails to create vm. You should look at your www server error.log file. perhaps this is sudo isue, or maybe your server cant create vms at all for some reasons. All thise reasons should be displayed in error.log

so the next step here also is to try using virsh commands to see what happens when you create and start a domain manually.  all the dashboard is doing is running the right virsh command to do your bidding.
first thing to do is enable debug logging in functions/config.php, that should log to httpd_error_log
(if you still see nothing useful try enabling real debug logging next using the following method)
http://wiki.libvirt.org/page/DebugLogs
run virsh start (if you have a domain to start -- if not run virsh create then do the start)
if you get any errors during this process, that is likely what the apache instance is doing also.
If you can create/start a VM using the command line then try this
sudo apache --shell=/bin/bash (on centos) so you can test the same commands as the apache user
Hope this helps... let me know how you make out and we can help you get it going.

If this is plain debian installation, this should work out of the box.
There may be several issues, that I could think of:

sudo problems. Just edit your sudoers file and change VDI user permissions to:
VDI ALL=(ALL) NOPASSWD:ALL
No kvm enabled. Please check if your kvm module is enabled:
lsmod |grep kvm
Check that all paths in your config.php are ok. Also, check, that all paths on hypervisor side in config file are existing.

Hi Seitanas,
I'm getting the same errors as henickr. I did the install on Ubuntu 14.04. I followed the instructions (to the tee) and feel that I'm very close to getting this working. I installed the KVM-VDI application on a server that houses 1 KVM guest. The KVM-VDI application pulled this guest into the web dashboard and I can manipulate this VM, as I should.

However, I cannot create new VM's. For example,
I have my original VM in the interface. Here is what happens when I try to make a new VM (let's say Linux2):

The VM is created in the dashboard.

However, when I try to start it, I get some issues.
First issue, is this:

I'm not a programmer, so I'm unsure of this. To me, it looks like the VM is not creating a XML file for KVM to reference. I checked /etc/libvirt/qemu and found only my original VM's XML file:

Second thing I found was that the VM is creating a volume (within /dev/data). Here is a screenshot of the QCOW2 it fabricates:

That looks good, however, the VM is small in size (193K). I specified 10GB in the dashboard.
I checked the paths, however, that doesn't mean I got them all. If I made a mistake or this error is something to do with a path, please let me know.
The other thing I checked was doing a virsh list when I started the VM. When I did, all I saw was my original VM. I didn't see Linux2. On the host I'm working on, we use Linux KVM with a LVM structure. We create the base image and export it to a .IMG. Then, we dd the IMG to a logical volume that the XML file in KVM references (just a little background).
We're trying to get a KVM VDI to work and I just want to say, THANKS!
This program is definitely what I'm looking for! :)
If you can, please get back to me. I would love to get this working (hopefully, in a production environment).

Hello, first of all, you should not use /dev fs to create VM images in. This is pseudo file system for Linux devices. You should create some directory in your disk drive (eg /data) and then specify path to that directory when you are creating new VM.
To debug this, first, delete VM from dashboard list (the one that failed to create), then enable debug logging: change $write_debug_log=false; in your config.php to $write_debug_log=true;
Then try to create machine, and paste lines from your /var/log/apache2/error.log
As for disk image being smaller (193K instead of 10G) - this is normal. qcow2 images are thin provisioned, and they will grow when data is written to them.

Hi Seitanas,
I am getting similar issues when try to create VM on Dashboard.  when I created new 'Source Machine'. Below is error.log.
[Mon Oct 17 18:12:45.815038 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] command: sudo virt-install --name='ubuntu1404' --disk path='/data/ubuntu1404-5805770dc6f84.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=sSrUqDP3nFG52 --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --pxe --noautoconsole, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:45.815223 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] Executing: sudo qemu-img create -f qcow2 -o size='10'G '/data/ubuntu1404-5805770dc6f84.qcow2', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:46.016020 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] Formatting '/data/ubuntu1404-5805770dc6f84.qcow2', fmt=qcow2 size=10737418240 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:46.016085 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] Executing: sudo virt-install --name='ubuntu1404' --disk path='/data/ubuntu1404-5805770dc6f84.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=sSrUqDP3nFG52 --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --pxe --noautoconsole, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:47.235225 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] Executing: sudo /usr/local/VDI//vdi-xmledit -name 'ubuntu1404', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:47.372273 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730]   File "/usr/local/VDI/vdi-xmledit", line 39\n    image_path = disk.find('source')\n                                   ^\nTabError: inconsistent use of tabs and spaces in indentation\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:47.372367 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] \nStarting install...\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Mon Oct 17 18:12:47.458442 2016] [:error] [pid 1485] [client <IP_ADDRESS>:58730] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
Pl let me know how can I fix the above error. Appreciate your help
Thanks
KD

After updating files, below is the error.
root@hypervisor:/usr/local/VDI# ./vdi-xmledit -name ubuntu1404                                    Traceback (most recent call last):
File "./vdi-xmledit", line 24, in
tree = ET.parse('/etc/libvirt/qemu/' + vmname+'.xml')
File "/usr/lib/python3.5/xml/etree/ElementTree.py", line 1184, in parse
tree.parse(source, parser)
File "/usr/lib/python3.5/xml/etree/ElementTree.py", line 585, in parse
source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory: '/etc/libvirt/qemu/ubuntu1404.xml'

This means that VM "ubuntu1404" does not exist. ls /etc/libvirt/qemu/

I deleted the old VM and recreate 'Source Machine'  and getting error, below is error.log.
Do I need update all the files under "root@hypervisor:/usr/local/VDI"
I have only updated this file "vdi-xmledit"
Pl see the attached image, after updating above file it is showing all this folders/names in dashboard.

[Tue Oct 18 09:52:52.757433 2016] [:error] [pid 1483] [client <IP_ADDRESS>:51524]                       Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', r                      eferer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:52:53.510898 2016] [:error] [pid 1483] [client <IP_ADDRESS>:51524]                       Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', r                      eferer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:52:56.952664 2016] [:error] [pid 1483] [client <IP_ADDRESS>:51524]                       Executing: sudo ls /var/lib/libvirt/images|grep -i .iso, referer: http://10.11.2                      54.140/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:30.976670 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       command: sudo virt-install --name='ubuntu1404Desk' --disk path='/data/ubuntu1404                      Desk-5806538aee6f6.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vc                      pus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio -                      -os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,pass                      word=4CJm86RZ1yal5 --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0                       --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.is                      o', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:30.976760 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Executing: sudo qemu-img create -f qcow2 -o size='10'G '/data/ubuntu1404Desk-580                      6538aee6f6.qcow2', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:31.176367 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Formatting '/data/ubuntu1404Desk-5806538aee6f6.qcow2', fmt=qcow2 size=1073741824                      0 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16\n, refer                      er: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:31.176504 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Executing: sudo virt-install --name='ubuntu1404Desk' --disk path='/data/ubuntu14                      04Desk-5806538aee6f6.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --                      vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio                       --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,pa                      ssword=4CJm86RZ1yal5 --redirdev usb,type=spicevmc --video qxl --noreboot --wait=                      0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.                      iso', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:32.580566 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Executing: sudo /usr/local/VDI//vdi-xmledit -name 'ubuntu1404Desk', referer: htt                      p://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:32.728753 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Traceback (most recent call last):\n  File "/usr/local/VDI/vdi-xmledit", line 24                      , in \n    tree = ET.parse('/etc/libvirt/qemu/' + vmname+'.xml')\n  File                       "/usr/lib/python3.5/xml/etree/ElementTree.py", line 1184, in parse\n    tree.pa                      rse(source, parser)\n  File "/usr/lib/python3.5/xml/etree/ElementTree.py", line                       585, in parse\n    source = open(source, "rb")\nFileNotFoundError: [Errno 2] No                       such file or directory: '/etc/libvirt/qemu/ubuntu1404Desk.xml'\n, referer: http:                      //<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:32.728813 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       \nStarting install...\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 09:53:33.388500 2016] [:error] [pid 1301] [client <IP_ADDRESS>:51540]                       Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', r                      eferer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php

Something is wrong with your /etc/sudoers file on line  32.
Missing empty line on the end perhaps?

I have recopied the line from hypervisor/sudoers, still .xml file is not getting generated. below is the error.log
[Tue Oct 18 10:28:57.712130 2016] [:error] [pid 1599] [client <IP_ADDRESS>:52275]          Executing: sudo ls /var/lib/libvirt/images|grep -i .iso, referer: http://10.11.2         54.140/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:28.792336 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          command: sudo virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk         -58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus=         '1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-         type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password         =2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --no         autoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso',          referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:28.792492 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Executing: sudo qemu-img create -f qcow2 -o size='11'G '/data/ubuntu14desk-58065         bf8c16df.qcow2', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:29.008808 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Formatting '/data/ubuntu14desk-58065bf8c16df.qcow2', fmt=qcow2 size=11811160064          encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16\n, referer         : http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:29.008924 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Executing: sudo virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14de         sk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpu         s='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --o         s-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,passwo         rd=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --         noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'         , referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:30.507141 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Executing: sudo /usr/local/VDI//vdi-xmledit -name 'ubuntu14desk', referer: http:         //<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:30.663977 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Traceback (most recent call last):\n  File "/usr/local/VDI/vdi-xmledit", line 24         , in \n    tree = ET.parse('/etc/libvirt/qemu/' + vmname+'.xml')\n  File          "/usr/lib/python3.5/xml/etree/ElementTree.py", line 1184, in parse\n    tree.pa         rse(source, parser)\n  File "/usr/lib/python3.5/xml/etree/ElementTree.py", line          585, in parse\n    source = open(source, "rb")\nFileNotFoundError: [Errno 2] No          such file or directory: '/etc/libvirt/qemu/ubuntu14desk.xml'\n, referer: http://         <IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:30.664086 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          \nStarting install...\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 10:29:30.817652 2016] [:error] [pid 1619] [client <IP_ADDRESS>:52284]          Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', r         eferer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php

Try running this command on hypervisor side:
virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpu s='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'

root@hypervisor:/data# virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpu s='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'
WARNING  KVM acceleration not available, using 'qemu'
ERROR    Unknown options ['s']
root@hypervisor:/data#

Somehow your debug logs contain random spaces in them.
here's corrected version:
virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'

root@hypervisor:/data# virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'
WARNING  KVM acceleration not available, using 'qemu'
Starting install...
ERROR    Cannot get interface MTU on 'br0': No such device
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start ubuntu14desk
otherwise, please restart your installation.
root@hypervisor:/data#

Here you go. Your hypervisor misses bridge interface.

Bridge interface is active.  It is virtual bridge interface created by libvirt and used to provide basic NAT to vms.
For KVM-VDI you should create normal bridge interface out of your physical one.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces_network-bridge.html

You can use virbr0 on RHEL if you want but you will need to source nat the
traffic if you don't create your own 'real' bridge as suggested previously.
Otherwise your guests won't have internet access.  virbr0 does work though
if you do that.
On Tue, Oct 18, 2016 at 2:55 PM, Tadas Ustinavičius <
<EMAIL_ADDRESS>wrote:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterp
rise_Linux/6/html/Deployment_Guide/s2-networkscripts-
interfaces_network-bridge.html
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-254587266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZXxqSPhWGvUXPLuattQx0rBw1LXOhks5q1Qf-gaJpZM4J9sg6
.

Prefect!! Thanks a lot. I configured BR0 interface, since my all install is on ubuntu16 it is little different then RHEL to configure BR0. Here is the link, if someone need help. http://www.cyberciti.biz/faq/how-to-create-bridge-interface-ubuntu-linux/
I hope now I can use Dashboard to create VM's? OR do I have to use manual process?
Any ideas how to get rid of all the names / folder from the Dashboard?

root@hypervisor:~# virt-install --name='ubuntu14desk' --disk path='/data/ubuntu14desk-58065bf8c16df.qcow2',format=qcow2,bus=virtio,cache=none --soundhw=ac97 --vcpus='1',cores='1',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='ubuntusaucy' --graphics spice,listen=<IP_ADDRESS>,password=2fgFs8LCz4tiD --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 --noautoconsole --cdrom '/var/lib/libvirt/images/ubuntu-14.04.5-desktop-amd64.iso'
WARNING  KVM acceleration not available, using 'qemu'
Starting install...
Creating domain...                                                                                |    0 B  00:00:00
Domain installation still in progress. You can reconnect to
the console to complete the installation process.

Just delete those trash names with delete button.
Now you should be able create VMs via dashboard, - there seem to be no errors in debug log.

Just had this issue. That fixed the problem. Below is my new /etc/network/interfaces file:
root@VDI-Host:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens160
iface ens160 inet dhcp

auto br0
iface br0 inet dhcp
        bridge_ports ens192

Then just ifup br0. Make sure that you aren't putting your management interface in the bridge or you will lose your connection.

Some how my HTML5 console does not show anything, it is blank screen. But I am able to use SPICE console using Remote-viewer. Any idea?
Dustinaevans: Correct, I bridged with ens160 and lost the connection, had to reboot the system and it came-up fine. Below is interface file.
The loopback network interface
auto lo
iface lo inet loopback
The primary network interface
#auto ens160
#iface ens160 inet dhcp
auto br0
iface br0 inet dhcp
bridge_ports ens160
bridge_stp off
bridge_fd 0
bridge_maxwait 0

do you have websockify server running on your dashboard server?

if you're getting a black screen on the spice console, make sure your
dashboard node can get through to the vnc port on the hypervisor node and
that the outside world (wherever you're accessing the dashboard from) can
access http and port 5959.
On Tue, Oct 18, 2016 at 3:45 PM, kdand<EMAIL_ADDRESS>wrote:

Some how my HTML5 console does not show anything, it is blank screen. But
I am able to use SPICE console using Remote-viewer. Any idea?
Dustinaevans: Correct, I bridged with ens160 and lost the connection, had
to reboot the system and it came-up fine. Below is interface file.
The loopback network interface
auto lo
iface lo inet loopback
The primary network interface
#auto ens160
#iface ens160 inet dhcp
auto br0
iface br0 inet dhcp
bridge_ports ens160
bridge_stp off
bridge_fd 0
bridge_maxwait 0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-254601647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX6Pf71IakWwhHNkV_Wp6uKAIucJlks5q1RPLgaJpZM4J9sg6
.

Yes, websockify server is running. I am able to use SPICE remote-viewer to access console. But not HTML5.
root@Dashboard:/var/www/html/websockify# ./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959 --daemon
WARNING: no 'numpy' module, HyBi protocol will be slower
WebSocket server settings:

Listen on :5959
Flash security policy server
No SSL/TLS support (no cert file)
Backgrounding (daemon)
Traceback (most recent call last):
File "./run", line 5, in
websockify.websocketproxy.websockify_init()
File "/var/www/html/websockify/websockify/websocketproxy.py", line 535, in websockify_init
server.start_server()
File "/var/www/html/websockify/websockify/websocket.py", line 976, in start_server
tcp_keepintvl=self.tcp_keepintvl)
File "/var/www/html/websockify/websockify/websocket.py", line 744, in socket
sock.bind(addrs[0][4])
OSError: [Errno 98] Address already in use

Address already in use
Have an ifconfig?

I had ran the command twice "./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959 --daemon"
Below is the ifconfig
ens160    Link encap:Ethernet  HWaddr 00:0c:29:74:f0:f7
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::20c:29ff:fe74:f0f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:9279 errors:0 dropped:0 overruns:0 frame:0
TX packets:5102 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13393152 (13.3 MB)  TX bytes:2809115 (2.8 MB)
lo        Link encap:Local Loopback
inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:13640 (13.6 KB)  TX bytes:13640 (13.6 KB)

Just run command withour --daemon and paste output from it when you try to connect

Address already in use means it's already running.  You can (as root) run
lsof -i:5959 to check.  Both the http port and websockify need to be
accessible from the client location for it to work.  Not just running.

Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-254606217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX7E2tbTFUmcrKReloLygcoWtXWL0ks5q1RekgaJpZM4J9sg6
.

Yes, I can access both ports HTTP and 5959 from client side. All I see the blank screen with hamburger icon in left top corner. I have attached both screen shots.

Below is the out put lsof -i:5959 and command running without --daemon
root@Dashboard:/var/www/html/websockify# lsof -i:5959
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python  1747 root    3u  IPv4  17281      0t0  TCP *:5959 (LISTEN)
root@Dashboard:/var/www/html/websockify#  ./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959
WARNING: no 'numpy' module, HyBi protocol will be slower
WebSocket server settings:

Listen on :5959
Flash security policy server
No SSL/TLS support (no cert file)
Traceback (most recent call last):
File "./run", line 5, in
websockify.websocketproxy.websockify_init()
File "/var/www/html/websockify/websockify/websocketproxy.py", line 535, in websockify_init
server.start_server()
File "/var/www/html/websockify/websockify/websocket.py", line 976, in start_server
tcp_keepintvl=self.tcp_keepintvl)
File "/var/www/html/websockify/websockify/websocket.py", line 744, in socket
sock.bind(addrs[0][4])
OSError: [Errno 98] Address already in use

Just stop all currently running websockify services. Run new instance:
 ./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959 then try to connect via html5 and paste the output from websockify.

root@Dashboard:/var/www/html/websockify# ./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959
WARNING: no 'numpy' module, HyBi protocol will be slower
WebSocket server settings:

Listen on :5959
Flash security policy server
No SSL/TLS support (no cert file)
proxying from :5959 to targets generated by TokenFile
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found
<IP_ADDRESS>: SSL connection but '/var/www/html/websockify/self.pem' not found

Once 'Source Machine' is shutdown (force) VM, I cannot power-on?
Also, how we dismount ISO image? After OS installation, when I reboot the 'Source Machine' VM it is stuck on installation disk removal.

Oh if you're using HTTPS on dashboard you can use --key and --cert to point
to the certificates or combine them in the websockify directory as self.pem
I had difficulty using self signed but a real cert works quickly.
On Oct 18, 2016 6:25 PM, "kdand"<EMAIL_ADDRESS>wrote:

Once 'Source Machine' is shutdown (force) VM, I cannot power-on?
Also, how we dismount ISO image? After OS installation, when I reboot the
'Source Machine' VM it is stuck on installation disk removal.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-254643989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX7GhBx5DaReXIcphB1zK2lBcGiC0ks5q1Tk4gaJpZM4J9sg6
.

If you forced a shutdown it is possible you corrupted the file.  I'm
usually very careful with my initial or source images to shut them down
from inside the OS.
There is a command to mount/unmount disks but I need to dig it up...
virsh --attach-disk I think.
You need it when using a Windows image that can't find its disk drivers so
you can flip in and out the virtio driver iso.
On Oct 18, 2016 6:25 PM, "kdand"<EMAIL_ADDRESS>wrote:

Once 'Source Machine' is shutdown (force) VM, I cannot power-on?
Also, how we dismount ISO image? After OS installation, when I reboot the
'Source Machine' VM it is stuck on installation disk removal.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-254643989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX7GhBx5DaReXIcphB1zK2lBcGiC0ks5q1Tk4gaJpZM4J9sg6
.

To keep things simple, I have not configured HTTPS, I knew I will run into more issue if I where to configure SSL & cert configuration. Is there a way to use HTML5 without configured SSL & CERT?

Once I force shutdown the 'source machine' I cannot power-on from dashboard.
Use the 'virsh' command to start the VM's manually from hypervisor.
root@hypervisor:/data# virsh start ubuntu14desk
Domain ubuntu14desk started
root@hypervisor:/data# virsh list --all
Id    Name                           State
4     ubuntu14desk                   running

Win8-1Pro                      shut off

root@hypervisor:/data# virsh start Win8-1Pro
Domain Win8-1Pro started
Is anyone have issues installing Windows8.1 Pro 'Source Machine', VM keeps automatically shutdown after it boots from ISO file?

I created 'Initial Machine' from 'Source Machine' did 'Copy disk from source' but cannot power on initial machine from Dashboard. From Hypervisor system I manual started initial machine by virsh start initialVMname. but does not find disk to boot the OS.
It seems from Dashboard I cannot start any VM's once it is shudown.
Below is the error.log.
[Tue Oct 18 17:46:09.223859 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] \nStarting install...\n\rCreating domain...                                          |    0 B  00:00     \nDomain creation completed.\nYou can restart your domain by running:\n  virsh --connect qemu:///system start ubuntu1404\n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:09.223910 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] Executing: sudo /usr/local/VDI//vdi-xmledit -name 'ubuntu1404', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:09.657996 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] \n, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:09.936161 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] Executing: sudo virsh domblklist ubuntu14desk|grep vda| awk '{print $2}' , referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:10.164745 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] Executing: sudo virsh domblklist ubuntu1404|grep vda| awk '{print $2}' , referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:10.274489 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] Executing: sudo /usr/local/VDI/copy-file /data/ubuntu14desk-58065bf8c16df.qcow2 /data/ubuntu1404-5806c24fc503c.qcow2 32, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:46:10.539969 2016] [:error] [pid 4747] [client <IP_ADDRESS>:64884] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:47:10.480610 2016] [:error] [pid 4645] [client <IP_ADDRESS>:64906] PHP Notice:  Undefined index: hypervisor in /var/www/html/kvm-vdi/snapshot.php on line 10, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:47:11.386978 2016] [:error] [pid 4645] [client <IP_ADDRESS>:64906] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:47:13.307082 2016] [:error] [pid 4645] [client <IP_ADDRESS>:64906] PHP Notice:  Undefined index: hypervisor in /var/www/html/kvm-vdi/snapshot.php on line 10, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:47:14.123077 2016] [:error] [pid 4645] [client <IP_ADDRESS>:64906] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:48:38.257114 2016] [:error] [pid 4749] [client <IP_ADDRESS>:64940] Executing: sudo virsh domblklist ubuntu14desk|grep vda| awk '{print $2}' , referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:48:38.460224 2016] [:error] [pid 4749] [client <IP_ADDRESS>:64940] Executing: sudo virsh domblklist ubuntu1404|grep vda| awk '{print $2}' , referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:48:38.568981 2016] [:error] [pid 4749] [client <IP_ADDRESS>:64940] Executing: sudo /usr/local/VDI/copy-file /data/ubuntu14desk-58065bf8c16df.qcow2 /data/ubuntu1404-5806c24fc503c.qcow2 32, referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php
[Tue Oct 18 17:48:39.341092 2016] [:error] [pid 4749] [client <IP_ADDRESS>:64940] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://<IP_ADDRESS>/kvm-vdi/dashboard.php

Pl check if there is any issue with hypervisors/copy-file? From Dashboard 'copy disks from source' did not work. Tried to run manually on hypervisor and getting below error.
root@hypervisor:~# /usr/local/VDI/copy-file /data/ubuntu14desk-58065bf8c16df.qcow2 /data/ubuntu1404-5806fa3b1496a.qcow2
File "/usr/local/VDI/copy-file", line 24
bytes_copied=bytes_copied+1024*10480
^
TabError: inconsistent use of tabs and spaces in indentation

Okay, i see that there may be some problems with newer python. Will remake python part.

After updating hypervisors/copy-file. Tried to run manually.
root@hypervisor:/usr/local/VDI# /usr/local/VDI/copy-file /data/ubuntu14desk-58065bf8c16df.qcow2 /data/ubuntu1404-58084eda55ce1.qcow2
Traceback (most recent call last):
File "/usr/local/VDI/copy-file", line 2, in
from ConfigParser import ConfigParser
ImportError: No module named 'ConfigParser'

Could you try using python 2 instead of 3?

Below is the out put with python2.7
root@hypervisor:/usr/local/VDI# python
Python 2.7.12 (default, Jul  1 2016, 15:12:24)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

root@hypervisor:/usr/local/VDI# /usr/local/VDI/copy-file /data/ubuntu14desk-58065bf8c16df.qcow2 /data/ubuntu1404-58084eda55ce1.qcow2
Traceback (most recent call last):
File "/usr/local/VDI/copy-file", line 13, in
vm=str(sys.argv[3])
IndexError: list index out of range

This is normal behavior, because you are using incorrect syntax.
copy-file source_path dest_path vmid

Thanks!!
It worked now.
Any idea why windows 8.1 and 10 have issue creating 'source machine' It boots fine from ISO, once I click on install windows, it crash and VM shutdown completely.

All VMs are created with virtio devices. Windows do not contain drivers for those devices inside installation iso. So you have to create windows install iso with drivers included (note, that windows 8.1/10 needs virtio DOD drivers), or mount virtio driver iso file before starting installation and preload vide/network and storage drivers. KVM-VDi does not support iso remount, so you need to use external tool, like Virtual Machine Manager, or just plain virsh

Okay, I will try to build iso and check.
HTML5 worked for few times and then it stopped with below errors.
root@Dashboard:/var/www/html/websockify# ./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959
WARNING: no 'numpy' module, HyBi protocol will be slower
WebSocket server settings:

Listen on :5959
Flash security policy server
No SSL/TLS support (no cert file)
proxying from :5959 to targets generated by TokenFile
<IP_ADDRESS> - - [20/Oct/2016 00:10:35] <IP_ADDRESS>: Plain non-SSL (ws://) WebSocket connection
<IP_ADDRESS> - - [20/Oct/2016 00:10:35] <IP_ADDRESS>: Version hybi-13, base64: 'False'
<IP_ADDRESS> - - [20/Oct/2016 00:10:35] <IP_ADDRESS>: Path: '/?password=&token=ubuntu14-1'
<IP_ADDRESS> - - [20/Oct/2016 00:10:35] connecting to: <IP_ADDRESS>:5900
<IP_ADDRESS> - - [20/Oct/2016 00:10:38] code 400, message Bad request version ('2jà\x01')
<IP_ADDRESS> - - [20/Oct/2016 00:11:11] <IP_ADDRESS>: Plain non-SSL (ws://) WebSocket connection
<IP_ADDRESS> - - [20/Oct/2016 00:11:11] <IP_ADDRESS>: Version hybi-13, base64: 'False'
<IP_ADDRESS> - - [20/Oct/2016 00:11:11] <IP_ADDRESS>: Path: '/?password=&token=ubuntu14-1'
<IP_ADDRESS> - - [20/Oct/2016 00:11:11] connecting to: <IP_ADDRESS>:5900
<IP_ADDRESS> - - [20/Oct/2016 00:11:11] code 400, message Bad HTTP/0.9 request type ('\x88\x80å')

I see password item missing here. Something is wrong with vdi-wrapper script.

Quick comment about the bad request messages.  Most are benign.  I get them
regularly on a working setup.  Chrome canary (and new chromium dev builds)
properly close websockify connections but other browsers have a bug where
sometimes the thread remains open and causes an error.  It can be ignored.
My suggestion here is to create a new vm if it consistently doesn't work as
once you get a good golden image to push it should work properly.
On Oct 20, 2016 4:30 AM, "Tadas Ustinavičius"<EMAIL_ADDRESS>wrote:

I see password item missing here. Something is wrong with vdi-wrapper
script.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-255030166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX9s7gxHBki4ZrErSuUzY3yBK5LvSks5q1xiPgaJpZM4J9sg6
.

And I had an issue on RHEL with Windows blue screens that required a
specific version of qemu but I don't think that applies to you on debian.
RHEL users should use qemu-system-ev package.  My only comment here is when
you begin your windows install, allow it to progress to the place where it
doesn't see your HDD then on the hypervisor issue your virsh --attach-disk
command before you click next then after you see the virtio disk in the
combo box reissue another --attach-disk to put the windows iso back in the
drive before selecting it or windows will blue screen.
HTH
On Oct 20, 2016 5:34 AM, "Raymond Henick"<EMAIL_ADDRESS>wrote:

Quick comment about the bad request messages.  Most are benign.  I get
them regularly on a working setup.  Chrome canary (and new chromium dev
builds) properly close websockify connections but other browsers have a bug
where sometimes the thread remains open and causes an error.  It can be
ignored.
My suggestion here is to create a new vm if it consistently doesn't work
as once you get a good golden image to push it should work properly.
On Oct 20, 2016 4:30 AM, "Tadas Ustinavičius"<EMAIL_ADDRESS>wrote:

I see password item missing here. Something is wrong with vdi-wrapper
script.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-255030166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX9s7gxHBki4ZrErSuUzY3yBK5LvSks5q1xiPgaJpZM4J9sg6
.

Oh sorry... My comment implies you do not have/want to build a custom iso.
That is how you handle a regular iso.  Obviously much easier going forward
if you build one with the drivers included.
On Oct 20, 2016 5:42 AM, "Raymond Henick"<EMAIL_ADDRESS>wrote:

And I had an issue on RHEL with Windows blue screens that required a
specific version of qemu but I don't think that applies to you on debian.
RHEL users should use qemu-system-ev package.  My only comment here is when
you begin your windows install, allow it to progress to the place where it
doesn't see your HDD then on the hypervisor issue your virsh --attach-disk
command before you click next then after you see the virtio disk in the
combo box reissue another --attach-disk to put the windows iso back in the
drive before selecting it or windows will blue screen.
HTH
On Oct 20, 2016 5:34 AM, "Raymond Henick"<EMAIL_ADDRESS>wrote:

Quick comment about the bad request messages.  Most are benign.  I get
them regularly on a working setup.  Chrome canary (and new chromium dev
builds) properly close websockify connections but other browsers have a bug
where sometimes the thread remains open and causes an error.  It can be
ignored.
My suggestion here is to create a new vm if it consistently doesn't work
as once you get a good golden image to push it should work properly.
On Oct 20, 2016 4:30 AM, "Tadas Ustinavičius"<EMAIL_ADDRESS>wrote:

I see password item missing here. Something is wrong with vdi-wrapper
script.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Seitanas/kvm-vdi/issues/59#issuecomment-255030166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxZX9s7gxHBki4ZrErSuUzY3yBK5LvSks5q1xiPgaJpZM4J9sg6
.

If I create windows VM in virtual box and then convert it to KVM format. Will this windows VM work in KVM-VDI as 'source machine'?

No, VirtualBox uses different type of devices than KVM. You will have to reinstall drivers of your VM to fit virtio ones. Having said that this is complicated and you probably will end up with several blue screens


Tusharsaxena3112

changing some styling Have a look!

hi @Tusharsaxena3112
Good Effort.
But For merging your request in our production you should follow the contribution guidelines.
if you want any change you have to create a new button in the existing type or in your own type

Okay, @mjmaurya will take care of that! Thanks!


coleman-update-partners

I added two logos and uploaded them

LGTM 🚢

@micahalcorn is gonna take this and fix up css to center logos.

Also files in the wrong folder, but otherwise, not bad @coleman415


chore: open coverage result with live-server

https://github.com/skku-npc/skku-coding-platform/pull/293#discussion_r796739709
Backend test 후 coverage의 결과인 HTML 파일을 live-server로 열도록 구현했습니다.

Docker Desktop for Windows: Inside the container, any mounted files/folders will appear as if they are owned by root but the user you specify will still be able to read/write them and all files will be executable. Locally, all filesystem operations will use the permissions of your local user instead. This is because there is fundamentally no way to directly map Windows-style file permissions to Linux.

https://code.visualstudio.com/remote/advancedcontainers/add-nonroot-user
Windows Docker에서는 local user의 권한이 devcontainer 내 user의 권한과 분리되는 issue가 있는 것 같네요. PR 따로 만들어두겠습니다.


hardwareBackButton not working

Hi
hardwareBackButton mentioned at https://ionicframework.com/docs/react/config is not working. When we move from one route to another then clicking on android back button must navigate to the previous route, but its not working. Although it is working on ionic-dev-app but not on the capacitor app.

Hi
Any updates over this?

fix released in 4.11.4

not working either
`
const App: React.FC = () => {
setupConfig({
hardwareBackButton: true
});
return();
}
`


No setup information found for ghc-7.8.3 on your platform

Hello all.
My platform is:
C>ver
Microsoft Windows [Version 10.0.19042.985]

C>stack   upgrade
Current Stack version: 2.7.1, available download version: 2.7.1
Skipping binary upgrade, you are already running the most recent version

Now, I did stack new hello-world and selected from https://www.stackage.org the oldest known resolver lts-0.7 for the project just for some research purposes. But then the following happened:
C>stack build
No setup information found for ghc-7.8.3 on your platform.
This probably means a GHC bindist has not yet been added for OS key 'windows64'.
Supported versions: ghc-7.8.4, ghc-7.10.1, ghc-7.10.2, ..., ghc-9.0.1

I do not understand what this means or what I can do to overcome it. Only found some similar issues reported, including on this list.
Then I switched to the second oldest resolver lts-2.22. But this was  not any good, either, and it produced:
C>stack  build
Stack no longer supports Cabal versions below 1.19.2,
but version <IP_ADDRESS> was found.
This invocation will most likely fail.
To fix this, either use an older version of Stack or a newer resolver
Acceptable resolvers: lts-3.0/nightly-2015-05-05 or later
...

Ok, next try is with lts-3.22. Now it actually WORKS. Other LTS snapshots were not checked.
But shouldn't they all "work"? -Kind of smoothly?
Now, this is my real problem:
I want to research several legacy Haskell projects on Github, some of which were abandoned 5 or 7 years ago. The original authors left no documentation, which versions of Cabal or Ghc were used to build the projects. So I do need very early snapshots.
Any helpful ideas would be greatly welcome.
Thanks.
Hubert

@H1h8 I think the root of the problem here is the introduction of Stack 2 which had some breaking changes. Unfortunately I couldn't find blog post describing concrete details but the idea is that you should try the last release of Stack-1 (which should be 1.9.3) if you want to use such old LTS versions.

From the 2.1.1 release notes (changelog):

No longer supports Cabal versions older than 1.19.2. This means projects using snapshots earlier than lts-3.0 or nightly-2015-05-05 will no longer build.

@juhp and @qrilka, thanks for your cumulative explanation.
Good advice - read the changelog.
:-)
Indeed, I was not aware that there was a breaking change of behavior, although I did read the entire user guide.
Maybe v1.9.3 will help me.


Controlling the level of logs in NimBLE for ArduinoIDE 1.8.16

Hello,
After many tests, I can't get the NimBLE library logs to have the level I want.
In the serial output I always have "I NimBLEScan" and "D NimBLEScan" logs every time a BLE device is detected:
I NimBLEScan: "New advertiser: 7a: 0a: 85: 19: a4: 74"
D NimBLEScan: "erase device: 7a: 0a: 85: 19: a4: 74"
I NimBLEScan: "New advertiser: 46: 82: a0: 34: 74: a0"
D NimBLEScan: "erase device: 46: 82: a0: 34: 74: a0"
.
.
..........
With the function "Serial.printf (" Level log NimBLEScan =% d \ n ", esp_log_level_get (" NimBLEScan "));" I always get "Level log NimBLEScan = 1"
In my last tests I have the following configuration:
#define CONFIG_LOG_MAXIMUM_LEVEL ESP_LOG_NONE
#define LOG_LOCAL_LEVEL ESP_LOG_NONE
#define CONFIG_BT_NIMBLE_LOG_LEVEL 5
But I keep getting prints of all the BLE devices in my environment which are many:
None of the options I have tried have worked for me
Please, how should I set the log levels for NimBLE correctly?
Thanks in advance
My development data is:
OS = Windows10
ArduinoIDE: 1.8.16
ESP32 SDK: 2.0.1
NimBLE: 1.3.3

Hi @jaggil the current release uses the Arduino core debug level set in the Arduino IDE menu. This has been changed in the master branch to set a more appropriate macro setting in nimconfig.h NIMBLE_CPP_DEBUG_LEVEL. If you'd rather continue using the current release you can take a look at https://github.com/h2zero/NimBLE-Arduino/blob/1.3.3/src/NimBLELog.h and make the changes you'd like there.

Glad the master branch solution is working for you.
I will be making a release of this branch at some point in the future as a 2.x version due to planned breaking changes, which the log change is one of.
I don't have a timeline for this to be complete as there is still a long list of todo items and testing and my time is more limited lately.


Include Enable-CsOnlineSessionForReconnection to mitigate PS session timeout issue

By default, the PS session times out after an hour, and you have to close and launch a new PS session to reconnect.
There is a new function in the Skype Online PowerShell module called Enable-CsOnlineSessionForReconnection that can be used to mitigate the timeout issue.  The PS session will reconnect and authenticate, allowing it to be reused without having to launch a new instance to reconnect.
We published the newest version of the Skype Online Powershell module (below) for administering Skype for Business Online as well as Skype for Business Server for hybrid administration.
Skype for Business Online, Windows PowerShell Module (2046.123 - Published 10/2/2019)
https://www.microsoft.com/en-us/download/details.aspx?id=39366
Can we get this incorporated into this document?  It may also make sense to add it to the PowerShell repo as well.
https://github.com/MicrosoftDocs/office-docs-powershell
Let me know if you have any questions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 332f86e2-a5d4-e2fd-3001-73ba9cb7e591
Version Independent ID: c03f7691-b2d9-b68a-dc96-bf91c16362bb
Content: Diagnose connection problems with the Skype for Business Online Connector
Content Source: Skype/SfbOnline/set-up-your-computer-for-windows-powershell/diagnose-problems-with-the-skype-for-business-online-connector.md
Service: skype-for-business-online
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@ndambrosio Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @ndambrosio
I've added the important note in PR #3234
Please create the new issue on the Powershell Repository as well.
@scanum Please help me follow up this to do the transition to the Powershell Gallery smoothy

@ndambrosio Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Need a better packaging path for Linux

This issue is manly a reminder for myself of issues I've run into writing the setup.py file for RikerBot.
Riker is a weird project, it is supremely ill-suited for building with distutils and I have very little interest in supporting that workflow. This is fine for Windows where we can just distribute a binary wheel and be done with it, and that's the workflow that setup.py currently supports. But in the Linux world people want it both ways, they would like to install with PyPi and compile things locally, which means distutils.
I'm currently partial to the idea, that if you want Riker on Linux just build it yourself. Maybe in the future we can look into a Pkgbuild or something and install straight to site-packages, Python be damned. Or maybe someone will come along and make the build project work with distutils and I won't have to think about it.

setting up github action to provide builds on pypi might be interesting
have a look at https://github.com/kyamagu/faiss-wheels which does something nice (in c++/python/swig too)

I'm closing this since pip can now build Rikerbot, which means the typical build path for Python modules on Linux works


fix: moves the finalizer to guest creation.

This PR changes the first guest being created in the pool to allow leverage its finalizer. It also uses the middleware's log.
cc @juliens @ttys3

LGTM


Window width vs element width

There's an issue with lines 89 & 90 that relates to iOS. As the calculations are based off the window dimensions, this is not always ideal as when you scroll down on iOS, the Mobile Safari url bar shrinks in height, which affects the window dimensions, thus causing the image to adjust accordingly.
Simply removing the conditionals on those two lines resolves the issue, however I'm not sure how this may affect usage of this plugin under other circumstances for others.
var containerW = settings.container.clientWidth,
  containerH = settings.container.clientHeight,

@matthojo Any thoughts on the above, or should I close this issue for now? Thanks.

@niallobrien We could close for now, thank you. I've not touched this project is too long! It probably needs a fairly decent refactor.


Haskell: patch regex-tdfa-text to fix build (required to build Leksah) + minor fixes

cc @cstrahan

cc @peti

@obadz, would you mind rebasing this PR relative to the current master branch so that it can be merged without conflicts?

@peti, done


pip-compile --extra doesn't take into account already pinned versions

I'm trying to move away from *.in files and manage everything from pyproject.toml, but I'm facing a problem where pip-compile --extra doesn't take into account the already pinned versions from pip-compile (without --extra).
Environment Versions

OS Type: Arch Linux
Python version: 3.11.3
pip version: pip 23.1.2 from /usr/lib/python3.11/site-packages/pip (python 3.11)
pip-tools version: 6.13.0

Steps to replicate

Create the following pyproject.toml:

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "foobar"
version = "1"
dependencies = ["django==4.1.7"]

[project.optional-dependencies]
dev = ["pytest"]

Execute pip-compile --no-header --no-annotate --resolver backtracking to obtain:

asgiref==3.7.2
django==4.1.7
sqlparse==0.4.4

Remove the restriction from the django dependency from the pyproject.toml, and verify that pip-compile doesn't update any package.
Execute pip-compile --no-header --no-annotate --resolver backtracking --extra dev -o dev-requirements.txt, and see that the django dependency has been updated in the dev-requirements.txt:

asgiref==3.7.2
django==4.2.2
iniconfig==2.0.0
packaging==23.1
pluggy==1.2.0
pytest==7.4.0
sqlparse==0.4.4

I also tried to pass --pip-args "-c requirements.txt", but nothing changed.
Expected result
Actually, I would expect a way to pin only the dev dependencies, since the main dependencies were already pinned. Some workflow similar to the Workflow for layered requirements but with pyproject.toml instead of *.in files.

Is it correct that you're pinning versions in requirements.txt, then compiling dev-requirements.txt, and want the pinned items from the former to inform the latter?
Currently pip-compile only reads from the same output file being generated for the "preferred constraints" behavior.
If I understand right, then at least a workaround would be to cp requirements.txt dev-requirements.txt before compiling dev-requirements.txt.
If you were using dev-requirements.in you could include -c requirements.txt, but using only pyproject.toml as input I really don't know how constraints support is (either in standards or individual backends).

Related: #1364

Is it correct that you're pinning versions in requirements.txt, then compiling dev-requirements.txt, and want the pinned items from the former to inform the latter?

Yes. Essentially, I was trying to achieve the same "Layered workflow" available with *.in files, but using the pyproject.toml. I also don't understand why --pip-args "-c requirements.txt" doesn't work.

Digging into the issue I found that pip parses requirements from -c requirements using get_requirements() method. pip-tools doesn't use this method. It loads requirements in its own way which is why --pip-args "-c requirements.txt" doesn't work properly.
I suppose this can be fixed by calling get_requirements() and extending the existing pins after parsing source and lock files.

@ianliu could you please try this PR (https://github.com/jazzband/pip-tools/pull/1936)? I've added support for pip-compile -c requirements.txt, which I believe should resolve the issue


SkeletalDetectorSample_UWP Can not find any bodies in GPU mode

The SkeletalDetectorSample_UWP can not find any bodies in GPU mode, but it runs correct in CPU mode. The ObjectDetectorSample_UWP runs correct both.
Environment:
Lonovo Y7000
Windows 10 Insider Preview Build 18965.rs_prerelease.190803
CPU: i7-9750H
RAM:16GB
GPU: Nvidia RTX 2060
IDE: Visual Studio 2019 community

Thank you, we are aware of a discrepancy in results when running on CPU compared to GPU with this skill and are investigating the root cause. I will update this thread once we provide a fix.

Yes, It has been fixed. Thanks!


ENV EMODnet Ingestion 78221 - RLABO

For the Ingestion dataset on C13 and N15 isotopes, we need RLABO codes for:
the La Rochelle University, Littoral Environment and Societies (LIENSS) (EDMO code 1879) https://edmo.seadatanet.org/report/1879
the Ifremer, Scientific Information Systems for the sea (SISMER) (EDMO code 486) https://edmo.seadatanet.org/report/486

new RLABOs RLES and SISM


Drag and Drop

Need a drag and drop component in the JSX folder

I'd be keen on figuring out the drag and drop feature.

Awesome! I'm messaging you on slack right now!


Trains are not centered on stations correctly

The trains were coming quite slowly.

Just wanted to let know that I'm working on this. Its already fixed for the simple case, more complex cases I'm still figuring out with track iterators and centering two carts.

I have fixed this centering issue after many hours of debugging why offsets kept occurring one way or another. In any case, it appears to work now in all the following test cases:

Single minecarts/odd size trains above sign, even size trains center in the middle of two carts
Centers correctly when the train drives up onto the station to stop
Centers correctly when the train drives up to launch in the opposite direction
Centers correctly when minecarts are added to a station-waiting train

https://github.com/bergerhealer/TrainCarts/commit/bed191d4608658fe92430032612bccd1956dfc40
Please have a test before I close it @MinePlayer64
https://ci.mg-dev.eu/job/TrainCarts/35/
Your other issue (launch speed not being linear) is not yet fixed, I'm working on that.

Seems to work really well, I couldn't find any problem with it (even at speed 5).


Fresh ToDo List Web App Showcase

https://fresh-todo-list.deno.dev/

@MrSaeedNasiri I made a PR at the project repo! Just some minor fixes/improvements for you to consider 😁