Mailing List Archive

driver domains broken?
Has anyone tried driver domains with all the new Xen-API code? It
seems unhappy parsing the PCI device. I get something like this in
xend.log using current xen-unstable.hg:

[2006-11-14 15:31:01 xend.XendDomainInfo 6903] DEBUG (__init__:1072) XendDomainInfo.create(['vm', ['name', 'debianDD'], ['memory', 2048], ['vcpus', 2], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['image', ['linux', ['kernel', '/boot/xenlinuz'], ['root', '/dev/hda1 ro'], ['args', 'console=tty1']]], ['device', ['vbd', ['uname', 'phy:/dev/VBDs/debianDD'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['pci', ['dev', ['domain', '0x0000'], ['bus', '0x01'], ['slot', '0x02'], ['func', '0x1']]]]])
[2006-11-14 15:31:01 xend 6903] DEBUG (__init__:1072) XendConfig: reading device: {'uname': 'phy:/dev/VBDs/debianDD', 'mode': 'w', 'dev': 'hda1'}
[2006-11-14 15:31:01 xend 6903] ERROR (__init__:1072) too many values to unpack
Traceback (most recent call last):
File "//usr/lib/python/xen/util/xmlrpclib2.py", line 179, in _marshaled_dispatch
response = self._dispatch(method, params)
File "SimpleXMLRPCServer.py", line 406, in _dispatch
return func(*params)
File "//usr/lib/python/xen/xend/server/XMLRPCServer.py", line 64, in domain_create
info = XendDomain.instance().domain_create(config)
File "//usr/lib/python/xen/xend/XendDomain.py", line 802, in domain_create
dominfo = XendDomainInfo.create(config)
File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 148, in create
vm = XendDomainInfo(XendConfig(sxp = config))
File "//usr/lib/python/xen/xend/XendConfig.py", line 285, in __init__
cfg = self._populate_from_sxp(sxp)
File "//usr/lib/python/xen/xend/XendConfig.py", line 455, in _populate_from_sxp
for opt, val in config[1:]:
ValueError: too many values to unpack

Sorry if I missed a change in specifying driver domains. Thanks,

Alex


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: driver domains broken? [ In reply to ]
On Tue, Nov 14, 2006 at 09:37:27PM -0700, Alex Williamson wrote:

>
> Has anyone tried driver domains with all the new Xen-API code? It
> seems unhappy parsing the PCI device. I get something like this in
> xend.log using current xen-unstable.hg:
>
> [2006-11-14 15:31:01 xend.XendDomainInfo 6903] DEBUG (__init__:1072) XendDomainInfo.create(['vm', ['name', 'debianDD'], ['memory', 2048], ['vcpus', 2], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['image', ['linux', ['kernel', '/boot/xenlinuz'], ['root', '/dev/hda1 ro'], ['args', 'console=tty1']]], ['device', ['vbd', ['uname', 'phy:/dev/VBDs/debianDD'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['pci', ['dev', ['domain', '0x0000'], ['bus', '0x01'], ['slot', '0x02'], ['func', '0x1']]]]])
> [2006-11-14 15:31:01 xend 6903] DEBUG (__init__:1072) XendConfig: reading device: {'uname': 'phy:/dev/VBDs/debianDD', 'mode': 'w', 'dev': 'hda1'}
> [2006-11-14 15:31:01 xend 6903] ERROR (__init__:1072) too many values to unpack
> Traceback (most recent call last):
> File "//usr/lib/python/xen/util/xmlrpclib2.py", line 179, in _marshaled_dispatch
> response = self._dispatch(method, params)
> File "SimpleXMLRPCServer.py", line 406, in _dispatch
> return func(*params)
> File "//usr/lib/python/xen/xend/server/XMLRPCServer.py", line 64, in domain_create
> info = XendDomain.instance().domain_create(config)
> File "//usr/lib/python/xen/xend/XendDomain.py", line 802, in domain_create
> dominfo = XendDomainInfo.create(config)
> File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 148, in create
> vm = XendDomainInfo(XendConfig(sxp = config))
> File "//usr/lib/python/xen/xend/XendConfig.py", line 285, in __init__
> cfg = self._populate_from_sxp(sxp)
> File "//usr/lib/python/xen/xend/XendConfig.py", line 455, in _populate_from_sxp
> for opt, val in config[1:]:
> ValueError: too many values to unpack
>
> Sorry if I missed a change in specifying driver domains. Thanks,

No change -- this is a recent breakage. Patch appreciated, otherwise it'll
get fixed on Thursday probably.

Ewan.

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