Posted By: xcoryakx on October 22, 2016, 8:13 am |
ticket number is for the 1st ticket is (Ticket #263000) and for the 2nd ticket is (Ticket #556536) please help asap |
Posted By: asim_shaikh on October 25, 2016, 6:25 am | Post: 1 |
Quote ticket number is for the 1st ticket is (Ticket #263000) and for the 2nd ticket is (Ticket #556536) please help asap
Hi, We have replied to your tickets. ----------------------- Regards, Virtualizor Team http://www.virtualizor.com |
Posted By: xcoryakx on October 28, 2016, 3:58 am | Post: 2 |
I have a new ticket open, still having the same issue with the xen server would you look in to it.
402209 |
Posted By: asim_shaikh on October 29, 2016, 12:45 pm | Post: 3 |
Quote I have a new ticket open, still having the same issue with the xen server would you look in to it.
402209 Hi, We are awaiting your response since your last reply was Quote Hetzner is doing hardware test, I'll let you know when it's up ----------------------- Regards, Virtualizor Team http://www.virtualizor.com |
Posted By: asim_shaikh on November 3, 2016, 6:16 am | Post: 5 |
Quote The VPS failed to start
error: Failed to reconnect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory The following errors were found : There was an error while starting the new VPS error: Failed to reconnect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Hi, These errors are usually displayed when you have freshly installed KVM and didnt reboot the node. It should be fixed when you reboot the node once. Also now we have updated your ticket for the natbr error as there is no NAT bridge created on your server. ----------------------- Regards, Virtualizor Team http://www.virtualizor.com |