Re: call for testing: xen 4.1 packages

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

On 31.03.11 23:50, Manuel Bouyer wrote:
> On Thu, Mar 31, 2011 at 11:38:42PM +0200, Christoph Egger wrote:
>>> With the latest version, xenkernel41 boots fine with a 5.1_STABLE dom0 
>>> kernel.
>>> xentools41 builds fine exept blktap2. Do we have a blktap2 driver for
>>> NetBSD dom0 ? If not, maybe we should just disable blktap2 on NetBSD for 
>>> now ?
>>
>> Wouldn't it be better to implement the functionality with rump?
> 
> Maybe, I don't know if rump would be the right way to do it.
> What is the blktap2 driver supposed to do ?

It adds support for different virtual disk types such as qcow, qcow2,
vhd, vmdk, etc.

pooka@ pointed me to pud(4) when I talked to him last time.

>>
>>> can't open gnttab device
>>> xen be core: xen be core: can't open gnttab device
>>> can't open gnttab device
>>> xen be core: xen be core: can't open gnttab device
>>> can't open gnttab device
>>
>> Those messages go away once we have gnttab support in our dom0 kernel.
>> This is required to get PCI passthrough support for HVM guests, btw.
> 
> OK
> 
>>
>>> I used the same xen config file as xen33; is there something that needs to
>>> be changed ?
>>>
>>
>> No. xl is supposed to be a replacement for xm.
>>
>>>>
>>>> xm is marked as supported but deprecated in Xen 4.1.
>>>> Future versions of Xen no longer support xm (it will be removed).
>>>
>>> xm more or less works for info, list and top. create fails with:
>>> borneo:/var/log/xen#xm create -c nb1
>>> Using config file "/usr/pkg/etc/xen/nb1".
>>> Error: need more than 1 value to unpack
>>
>> /var/log/xen/xend.log or /var/log/xen/xend-debug.log should contain
>> a python backtrace where the error happened.
> 
> Nothing shows up in xend-debug.log. In xend.log I see:
> [2011-03-31 23:45:51 12525] ERROR (xmlrpclib2:181) Internal error handling 
> xend.domain.create
> Traceback (most recent call last):
>   File "/usr/pkg/lib/python2.6/site-packages/xen/util/xmlrpclib2.py", line 
> 134, in _marshaled_dispatch
>     response = self._dispatch(method, params)
>   File "/usr/pkg/lib/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch
>     return func(*params)
>   File 
> "/usr/pkg/lib/python2.6/site-packages/xen/xend/server/XMLRPCServer.py", line 
> 80, in domain_create
>     info = XendDomain.instance().domain_create(config)
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/XendDomain.py", line 
> 1001, in domain_create
>     dominfo = XendDomainInfo.create(config)
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/XendDomainInfo.py", 
> line 106, in create
>     vm.start()
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/XendDomainInfo.py", 
> line 473, in start
>     XendTask.log_progress(0, 30, self._constructDomain)
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/XendTask.py", line 209, 
> in log_progress
>     retval = func(*args, **kwds)
>     balloon.free(16*1024, self) # 16MB should be plenty
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/balloon.py", line 117, 
> in free
>     dom0_alloc = get_dom0_current_alloc()
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/balloon.py", line 59, 
> in get_dom0_current_alloc   
>     kb = _get_proc_balloon('current')
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/balloon.py", line 54, 
> in _get_proc_balloon
>     return osdep.lookup_balloon_stat(label)
>   File "/usr/pkg/lib/python2.6/site-packages/xen/xend/osdep.py", line 97, in 
> _netbsd_balloon_stat
>     (name, value) = sysctloutput.split('=')
> ValueError: need more than 1 value to unpack
> 

If you are on NetBSD-5 then pull up  dom0 balloon support from -current
then the error goes away.

Christoph