http://bugzilla.opensuse.org/show_bug.cgi?id=1017189 http://bugzilla.opensuse.org/show_bug.cgi?id=1017189#c2 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com --- Comment #2 from James Fehlig --- (In reply to Matwey Kornilov from comment #0)

The reason is that initially virtualbox 4 has been supplied with 13.2 and libvirt 1.2.9 only supports vbox 4.3 API In other words, virtualbox 5.0.20 update is inconsistent with provided libvirt.

That's a good reason for not doing such major version updates in a released product. A 4.x to 4.y update is reasonable, 4 to 5 is not.

Commit d0bef6433408745e4fffb9f16a146cbde9510f3b ("Add support for VirtualBox 5") has to be backported to libvirt 1.2.9

Where? Have you backported it to a home project branch of libvirt? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017189 http://bugzilla.opensuse.org/show_bug.cgi?id=1017189#c8 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matwey.kornilov@gmail.com Flags| |needinfo?(matwey.kornilov@g | |mail.com) --- Comment #8 from James Fehlig --- (In reply to Matwey Kornilov from comment #7)

I am facing the similar issue at openSUSE Leap 42.2 with

virtualbox-5.1.22-19.15.2.x86_64 (from OSS updates)

and

libvirt 2.0.0

IMO you should have opened a new bug, but I'm fine using this one for now.

virtualbox 5.1 API is supported only starting libvirt 2.5.x.

See commit 15209649bdaa5fc995983708e47d4bd84791b228 ("vbox: add vbox 5.1 C API header file.")

I added that commit to a branch in my home project. Can you give it a try? http://download.opensuse.org/repositories/home:/jfehlig:/branches:/openSUSE:... FYI, SLE12 SP2 and 42.2 share the same libvirt package. vbox is not supported on SLE, in fact the driver is not even built for SLE. But all maintenance of libvirt flows through SLE. After passing QA, libvirt updates are released to the SLE update repos. A bot is configured to submit those to openSUSE:Leap:42.2:Update automatically. Long story short: the fix will have to wait for a future SLE12 SP2 update before appearing in openSUSE:Leap:42.2:Update. -- You are receiving this mail because: You are on the CC list for the bug.