mirror of
https://github.com/retspen/webvirtmgr.git
synced 2026-04-25 23:55:57 +03:00
[GH-ISSUE #632] create new instance not working #479
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alv000h on GitHub (Feb 23, 2017).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/632
Hi,
When I try to create a new instance it does not work.
I click on "new instance", after Action -> create (mini instance). After that I fill the form "create virtual machine" and click on "create".
It does nothing, no error is raised in screen and the VM is not created.
I dont see nothing in libvirt/supervisor logs, Is there any way to activate debug, to see what is (not) happening??
I am using local socket connection to libvirt (with virt-manager all works fine) and all seems be ok, it show VM, storage pool and network previously created by virt-manager.
webvirtmgr commit is
79c8a8b5@hiddenicon commented on GitHub (Mar 27, 2017):
I am seeing the same exact issue. All other items can be created from GUI, can't create instance. Does nothing. I checked all logs that I know of, don't see any entries. I see access to /create/1/ in access logs, but nothing else.
@sndl commented on GitHub (Mar 29, 2017):
Same here. I can create an instance if I first create a storage and then create custom instance. This is likely a bug, because I used older version on the same libvirt setup an there were no issues.
@Thom-Ernst commented on GitHub (May 6, 2017):
Getting the same problem still...
@sndl commented on GitHub (May 8, 2017):
There is a pull request, that resolves this issue, so you can just pull it from there https://github.com/retspen/webvirtmgr/pull/625
@alv000h commented on GitHub (May 8, 2017):
@retspen @sndl, is there an estimated date to merge it to master?
@ghost commented on GitHub (Jul 29, 2017):
@retspen This is probably worth merging with master and would curb any potential issues being opened for the same thing.