WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 308] New: Most xm commands fail

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=308

           Summary: Most xm commands fail
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: danms@xxxxxxxxxx


Recently (I think it was changeset
7273:32f9300618d607a486d7efccccc57d8a08b9deae), lots of xm commands fail with a
stack trace like this:

[dom0] Running `xm block-attach 01_block_attach_device_pos-1128974279 phy:ram0
sdb1 w'
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/usr/lib/python/xen/xm/main.py", line 706, in main
    handle_xend_error(argv[1], args[0], ex)
  File "/usr/lib/python/xen/xm/main.py", line 174, in handle_xend_error
    raise ex
xen.xend.XendProtocol.XendError: Exception: Missing parameter: dev_config

Running xm-test on a recent pull makes this painfully obvious.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 308] New: Most xm commands fail, bugzilla-daemon <=