[Bug 223850] New: XEN tool xm shows no info
https://bugzilla.novell.com/show_bug.cgi?id=223850 Summary: XEN tool xm shows no info Product: openSUSE 10.2 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: mistinie@novell.com QAContact: qa@suse.de after updating a RC1 to RC2 i booted the xen kernel. I restored a previously saved VM, which worked fine (a SLES10 VM): e56:/home/micha # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 474 2 r----- 62.4 vm2 1 512 1 -b---- 0.0 I logged into the VM and rebooted the VM. Afterwords I started the Yast XEN module, and wondered about the showed garbage in the VM list. A manual start of "xm list" showed the same: e56:/home/micha # xm list Error: Boot loader didn't return any data! Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 ------- Comment #1 from mistinie@novell.com 2006-11-27 05:05 MST ------- Created an attachment (id=107009) --> (https://bugzilla.novell.com/attachment.cgi?id=107009&action=view) screenshot of yast xen module -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 ------- Comment #2 from mistinie@novell.com 2006-11-27 05:06 MST ------- Created an attachment (id=107010) --> (https://bugzilla.novell.com/attachment.cgi?id=107010&action=view) yast log -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 ------- Comment #3 from mistinie@novell.com 2006-11-27 05:06 MST ------- Created an attachment (id=107011) --> (https://bugzilla.novell.com/attachment.cgi?id=107011&action=view) xend.log -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 ------- Comment #4 from mistinie@novell.com 2006-11-27 05:07 MST ------- Created an attachment (id=107012) --> (https://bugzilla.novell.com/attachment.cgi?id=107012&action=view) xend-debug.log -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 jdouglas@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223850 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #6 from ccoffing@novell.com 2006-11-27 19:08 MST ------- Good catch, thanks. The key to reproducing this is to get a VM running without xend knowing what the kernel is (such as doing a restore), and then issue a command that requests the VM's state. This will cause the bootloader to be called, but it is called with mangled disk state. This problem was introduced when we went from 3.0.2 to 3.0.3. Fixed. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com