http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c1 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com Assignee|virt-bugs@suse.de |aginies@suse.com --- Comment #1 from James Fehlig --- I chatted with Antoine about this and there appears to be a logic bug in the patterns spec file wrt SLE vs openSUSE. Antoine said he would fix it... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c3 --- Comment #3 from James Fehlig --- (In reply to Antoine Ginies from comment #2)

i don't think there is a patterns-server-kvm_tools and patterns-server-xen_tools in openSUSE, and in these patterns there is a requires for libvirt-daemon-config-network, so we don't have the issue on SLE. The split was made on purpose to be able to install only the basement of KVM and XEN hypervisor. So maybe it could be a good idea to get this patterns available in openSUSE and use them.

The distinction doesn't make sense to me. Does openSUSE prefer a limited number of patterns? If the goal is a "base" KVM or Xen setup then the SLE {kvm,xen}_server pattern is the way to go. This gives you the most basic components required to run a KVM or Xen VM. If you want all the basic tools to create and manage VMs as well, then go with the {kvm,xen}_tools. IMO openSUSE should provide the same patterns as SLE. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c6 Antoine Ginies changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|aginies@suse.com |carnold@suse.com --- Comment #6 from Antoine Ginies --- Charles could you fix yast2-vm and install the new pattern under openSUSE. Now we have the same patterns as SLES, but the name differ a bit. so we need a deps on: patterns-server-kvm_tools patterns-server-xen_tools -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c9 --- Comment #9 from Charles Arnold --- (In reply to Guillaume GARDET from comment #8)

(In reply to Charles Arnold from comment #7)

...

I have issued a pull request for this change. It is pending a review.

Charles, do you have an SR number to share, please?

No, the pull request is still waiting review. Once accepted it will automatically be sent to Factory and on to a Tumbleweed release. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c11 --- Comment #11 from Guillaume GARDET --- (In reply to Richard Brown from comment #10)

(In reply to Charles Arnold from comment #9)

...

(In reply to Guillaume GARDET from comment #8)

...

(In reply to Charles Arnold from comment #7)

...

I have issued a pull request for this change. It is pending a review.

Charles, do you have an SR number to share, please?

No, the pull request is still waiting review. Once accepted it will automatically be sent to Factory and on to a Tumbleweed release.

Can we have a link to the pull request then please? Who is the review waiting on?

Seems to be https://github.com/yast/yast-vm/pull/36 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c13 --- Comment #13 from Guillaume GARDET --- (In reply to Guillaume GARDET from comment #12)

@Charles, your PR has been reviewed. Could you update it accordingly, please?

Charles updated the PR, which is now merged on github. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c15 --- Comment #15 from Antoine Ginies --- It would be nice to get the full log of the libvirtd starting. # journalctl -u libvirtd > libvirtd.log Sounds like there is an issue with starting the network. Please check: # virsh net-list default network should be available # virsh netinfo default to get info on this network if not started you should do it by hand: # virsh net-autostart default # virsh net-start default -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c17 --- Comment #17 from Richard Brown --- (In reply to Antoine Ginies from comment #16)

Any update?

Happy New Year....any update? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 Max Lin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlin@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c20 --- Comment #20 from Max Lin --- Created attachment 794145 --> http://bugzilla.opensuse.org/attachment.cgi?id=794145&action=edit journal journal log. The interesting part can be, Jan 10 09:59:13 susetest systemd[1]: Starting Virtualization daemon... Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.355+0000: 24917: info : libvirt version: 4.10.0 Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.355+0000: 24917: info : hostname: susetest Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.355+0000: 24917: warning : virGetHostnameImpl:714 : getaddrinfo failed for 'susetest': Name or service not known Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.387+0000: 24917: info : libvirt version: 4.10.0 Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.387+0000: 24917: info : hostname: susetest Jan 10 09:59:13 susetest libvirtd[24917]: 2019-01-10 14:59:13.387+0000: 24917: warning : netcfIfaceRegister:1275 : Failed to intialize libnetcontrol. Management of interface devices is disabled -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c22 --- Comment #22 from James Fehlig --- (In reply to Max Lin from comment #19)

...

# virsh net-list

The list is empty.

'virsh net-list' only shows active networks. You would see the network named 'default' if you added the --all option.

...

default network should be available

# virsh netinfo default

as the attached image.

Note that default network is not active. You can activate it with 'virsh net-start default'. To activate it at boot, set the autostart property. E.g. 'virsh net-autostart default'. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c24 --- Comment #24 from Max Lin --- Yes, it was NetworkManager there, make this clear, the topic here is started from https://progress.opensuse.org/issues/41093 , NetworkManager is now the default management tool for desktop environment, not per workstation or laptop anymore, therefore we're looking for an technical solution to have virtualization thingy works with NetworkManager on openQA, then should works on user's machine as well. So the question still remained is: Why does libvirt network 'default' get activated when wicked is the default network stack, but not with NM? It's a little bit far from this bugreport though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c26 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mlin@suse.com) --- Comment #26 from James Fehlig --- (In reply to Max Lin from comment #24)

So the question still remained is: Why does libvirt network 'default' get activated when wicked is the default network stack, but not with NM?

Are you encountering problems activating the default network when using NM? Does 'virsh net-start default' fail? As I already wrote, you can't use libvirt to manage *interface* devices when using NM, but there should be no problems managing virtual networks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1109832 http://bugzilla.opensuse.org/show_bug.cgi?id=1109832#c27 Alexander Graul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |agraul@suse.com Resolution|--- |FIXED --- Comment #27 from Alexander Graul --- Verified manually on Tumbleweed Snapshot 20190125 that libvirt-daemon-config-network is installed when yast2 virtualzation is used to install the virtualization stack. -- You are receiving this mail because: You are on the CC list for the bug.