https://bugzilla.novell.com/show_bug.cgi?id=820873 https://bugzilla.novell.com/show_bug.cgi?id=820873#c16 --- Comment #16 from James Fehlig <jfehlig@suse.com> 2013-10-17 18:55:13 UTC --- (In reply to comment #14)
After upgrading to opensuse 12.3, virt-manager and vm-install use libvirt.
virt-manager and vm-install have always used libvirt. What did change in 12.3 is moving the libvirt xen driver from libvirt-client to libvirtd. So libvirtd is now required on xen hosts even when using the legacy xend driver. It has always been required when using the libxl stack.
This is currently pushing me towards libvirtd and virsh but I still have VMs that were created prior to my upgrade and exist outside libvirtd control.
xl is supposed to be compatible with xm, so your existing tooling/scripts should still work. That said, I'd suggesting using libvirt anyhow since it will provide a stable interface even when upstream Xen swaps one toolstack for another.
I was hoping I could still maintain the same workflow and simply replace xm with xl but I guess that isn't going to be possible.
Are there specific issues preventing this? As mentioned above, upstream Xen strives for xl compatibility with xm.
until the upstream code for "virsh console" makes it's way into opensuse
Will be included in 13.1. FYI, if you live on the bleeding edge, the OBS Virtualization project always contains the latest, SUSE-packaged libvirt, which e.g. contains Bamvor's console patches https://build.opensuse.org/package/show/Virtualization/libvirt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.