12:22 a.m.
Hi, well I made sure that not only the old instances were stopped, but I
also went in there an undefined them.
so virsh list -all is blank
# virsh list --all
Id Name State
---------------------------------------------------
So none of those networks are 'in use'
Yet the kimchi interface still has the 'default' network greyed out
(probably because it *is* the default and thus still in use).
Obviously not a stop issue, as it would be unusual to need to turn off
the default network, but it something to be aware.
yes, a warning would be nicer.
I'll let you know if anything else comes up with the new version. So far
so good.
On 4/3/2017 2:07 PM, Aline Manera wrote:
Hi Bill,
The Kimchi UI blocks user to stop/edit/undefine an Network in use by
Templates or Guests. That should be the cause of the 'issue' you are
seeing.
I plan to remove that from Kimchi UI and only show a warning message
to user and let she/he decide on what to do.
Regards,
Aline Manera
On 04/03/2017 05:48 PM, WK wrote:
> more info.
>
> if you net-destroy, net-dumpxml, net-undefine and then turn around
> and net-define, net-start the network, it is still stuck (i.e. all
> greyed out)
>
> You must create either 'create' the network in the kimchi UI (instead
> of net-define)
>
> OR
>
> the Network must have a different name. Clearly something in the UI
> is holding onto the Network Name.
>
> I tried just changing the UUID, but its the Network Name that is
> significant
>
> -bill
>
>
> On 4/3/2017 12:08 PM, WK wrote:
>>
>> Just migrated off a number of VMs from a U16.4 LTS host running
>> kim.2.3.1
>>
>> then did an in place upgrade using dpkg -i and apt-get -f (to get a
>> few deps).
>>
>> rebooted and system came right up.
>>
>> The only issue I have encounter is that in the Network section. I
>> had 3 networks set up. The default and two additional (one vTap and
>> a LAN bridge).
>>
>> I wanted to remove one of them and move it to another port. In the
>> UI, all options are greyed out (i.e Stop, Edit, Delete).
>>
>> This occurs both on FireFox and on Edge on a Windows 10 desktop
>>
>> I have cleared cache etc and still have the issue.
>>
>> From the command line I had no problem using virsh net-destroy NET1
>> and virsh net-undefine NET1
>>
>> Back on the UI, of course kimchi showed that it was gone. I then
>> used the kimchi UI to recreate the Network with no problem and all
>> the normal UI options are available for the newly recreated Network.
>>
>> The remaining networks are still stuck.
>>
>> I guess I go ahead and undefine and then redefine them as well, but
>> I am curious if anyone else ran into this issue.
>>
>>
>> Sincerely,
>>
>> William Kern
>>
>>
>> _______________________________________________
>> Kimchi-devel mailing list
>> Kimchi-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>
> _______________________________________________
> Kimchi-devel mailing list
> Kimchi-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>