Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: call for testing: xen 4.1 packages

On 31.03.11 23:16, Manuel Bouyer wrote:
> On Thu, Mar 31, 2011 at 01:10:43PM -0500, Toby Karyadi wrote:
>> On 3/31/2011, "Manuel Bouyer" <bouyer%antioche.eu.org@localhost> wrote:
>>> I forgot to mention the URL to my updated package:
>>> ftp://ftp-asim.lip6.fr/outgoing/bouyer/xentools41.tar.gz
>>> this also has some PLIST fixes, and patches for things like man pages
>>> installed in the wrong directory.
>>> --
>>> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>>>     NetBSD: 26 ans d'experience feront toujours la difference
>>> --
>> I found that 'xm create' works fine for both PV and HVM DomU even with
>> the xentools41 prior to version above. With xl, I encountered similar
>> problems with my PV DomU, such as connecting to the console during
>> create and essentially the domain just didn't start. Once the domain is
>> running (i.e. using xm) I was able to use xl console just fine.
> for me, 'xm create' complains with:
> borneo:/usr/pkg/share/examples/xen#xm create nb1
> Using config file "/usr/pkg/etc/xen/nb1".
> Error: need more than 1 value to unpack
> looks like a python error, maybe something in the domU config file,
> but I don't even know at what to look. no domU is started.
>> One unusual thing that I noticed in /var/log/xen is that when I used xl
>> create for my PV DomU, a log with the name
>> 'qemu-dm-<pv_domu_name>.log' is created. That is not the case when I
>> used xm create (for a PV DomU) . What does qemu-dm have anything to do
>> for a PV DomU? 
> As i understood it, backend drivers have moved to userland (in qemu-dm)
> even for PV guests.

That's right. There are conflict situations causing the problems,
particularly with xm.


Home | Main Index | Thread Index | Old Index