Hi,
When we tested xm commands, the xm commands occurred the Traceback.
The following are the examples.
# xm sched-sedf domUtemp -s xx
Unexpected error: exceptions.ValueError
Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
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 1169, in main
rc = cmd(args)
File "//usr/lib/python/xen/xm/main.py", line 701, in xm_sched_sedf
opts['slice'] = ms_to_ns(v)
File "//usr/lib/python/xen/xm/main.py", line 665, in ms_to_ns
return (float(val) / 0.000001)
ValueError: invalid literal for float(): xx
# xm vcpu-pin domUtemp x 1
Unexpected error: exceptions.ValueError
Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
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 1173, in main
rc = cmd(args)
File "//usr/lib/python/xen/xm/main.py", line 600, in xm_vcpu_pin
vcpu = int(args[1])
ValueError: invalid literal for int(): x
The cause of the Traceback are entering wrong xm commands.
We suggest this patch so that the Traceback does not occur.
Signed-off-by: Hiroyuki Yamamoto <yamamoto.hiroyu@xxxxxxxxxxxxxx>
Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Best regards,
Kan
xm.patch
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home