[Bug 820873] New: The "long" option doesn't work with "xl list" on opensuse 12.3
https://bugzilla.novell.com/show_bug.cgi?id=820873 https://bugzilla.novell.com/show_bug.cgi?id=820873#c0 Summary: The "long" option doesn't work with "xl list" on opensuse 12.3 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: rschaffner@novell.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- The "long" option for displaying VM details doesn't work with "xl list" on opensuse 12.3 homevhst01:~ # xl list smt Name ID Mem VCPUs State Time(s) smt 1 512 1 -b---- 861.4 homevhst01:~ # xl list -l smt Domain name must be specified. homevhst01:~ # xl list smt -l Usage: xl [-v] list [options] [Domain] List information about all/some domains. Options: -l, --long Output all VM details -v, --verbose Prints out UUIDs and security context -Z, --context Prints out security context homevhst01:~ # which xl /usr/sbin/xl homevhst01:~ # rpm -qf /usr/sbin/xl xen-tools-4.2.1_12-1.8.1.x86_64 homevhst01:~ # -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c2
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c3
--- Comment #3 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c4
--- Comment #4 from James Fehlig
What version of xen-tools are you running?
Currently the system has xen-tools-4.3.0_03-248.1.x86_64 from the Virtualization project in OBS. But I also tried with the latest xen-tools package from the updates (http://download.opensuse.org/update/12.3/x86_64/xen-tools-4.2.1_12-1.8.1.x86...) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c5
--- Comment #5 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c6
--- Comment #6 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c7
--- Comment #7 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c8
--- Comment #8 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c9
--- Comment #9 from James Fehlig
Actually I use virsh for starting my VMs and the long list option doesn't work with any of them.
There are no guarantees libvirt and xl will play nicely together. These are two different libxl applications, neither of which is aware that the other exits. libxl supports the notion of "user data", where applications can store private data related to a domain. xl stores its data with userid "xl". libvirt stores its data with userid "libvirt-xml". The bug you are seeing is xl unable to find its user data. (In reply to comment #7)
Ok, it looks like the problem is in the libvirtd libxl driver. "xl list -l" only works if the VM is started by xl.
No problem in the libvirt libxl driver. IMO, the bug here is that xl could report a better error message, e.g. "No xl user data found. Is this domain managed by another libxl application?". (In reply to comment #8)
Of course, if I start them with xl then libvirt doesn't see them.
That's correct. libvirt will only know about domains started by libvirt, similar to the qemu driver where domains started with e.g. 'qemu-kvm ...' are unknown to libvirt. Again, I think the bug here is an unclear error message from xl. Do you agree? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c10
James Fehlig
Created an attachment (id=543896) --> (http://bugzilla.novell.com/attachment.cgi?id=543896) [details] Xen xm formatted config file
Actually I use virsh for starting my VMs and the long list option doesn't work with any of them.
After upgrading my homevhst to os12.3, I took my xm formatted config files and converted them to libvirt formatted xml using "virsh domxml-from-native". I then used "virsh define" to add them to libvirt.
I can do most things through virsh and libvirt but some things are not yet supported (ex. "virsh console" does not work) which means I need to use xl.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c11
--- Comment #11 from bamvor jian zhang
I would assume that xl is pulling the information from xenstore and not from a config file so I would assume it doesn't matter but maybe I'm wrong.
I've attached the original xm formatted config file.
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c14
--- Comment #14 from Ralph Schaffner
the virsh console command is upstreamed right now. do u have anyother command must use xl cli with the details from "xl list -l"? the details of vm could get from virsh dumpxml domain_name or xenstore-ls. is it enough for you?
I'm sure there are other ways to get the same information but I was looking for some consistency. Prior to upgrading to opensuse 12.3, I didn't use virsh or libvirt. I could use virt-manager and vm-install to create VMs and manage them with xm. After upgrading to opensuse 12.3, virt-manager and vm-install use libvirt. 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. 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. I suspect I will end up migrating everything to virsh and libvirtd but until the upstream code for "virsh console" makes it's way into opensuse, I will continue to have to use a mix of commands. But as James said, useful/informative error messages are always preferred. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c15
--- Comment #15 from Ralph Schaffner
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c16
--- Comment #16 from James Fehlig
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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c17
--- Comment #17 from James Fehlig
This may actually be a feature request but if xl is suppose to be a generic tool for working with libxl
I don't think that is the purpose of xl - it is simply an "in-tree" libxl app AFAIK. But that would need to be verified with the upstream Xen community. But I think the problem here is with the notion "user data" that libxl supports. Apps can store domain-specific private data with libxl, and I suspect xl is choking on the user data provided by libvirt. It should ignore this data IMO, and print a message that the domain is unknown or foreign to xl. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c18
--- Comment #18 from Ralph Schaffner
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.
Well, since the point of the bug is that I can't do a long list using xl on VMs created using vm-install which is something I could do with with xm, I'd say that is a fairly specific issue preventing me from maintaining the same workflow. ;) Prior to opensuse 12.3, I used to use virt-manager and vm-install for creating VMs and then managed them using xm. I can't just swap out xl for xm and keep doing that. Before 12.3, I didn't use virsh. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c19
--- Comment #19 from James Fehlig
Well, since the point of the bug is that I can't do a long list using xl on VMs created using vm-install which is something I could do with with xm, I'd say that is a fairly specific issue preventing me from maintaining the same workflow. ;)
Hehe, touche. But really the problem here is with the workflow. You shouldn't mix and match toolstacks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c20
bamvor jian zhang
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c
bamvor jian zhang
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c21
--- Comment #21 from Chunyan Liu
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c22
--- Comment #22 from Chunyan Liu
https://bugzilla.novell.com/show_bug.cgi?id=820873
https://bugzilla.novell.com/show_bug.cgi?id=820873#c23
Chunyan Liu
http://bugzilla.novell.com/show_bug.cgi?id=820873
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
--- Comment #25 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
--- Comment #26 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=820873
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com