I guess possibly the cause is from my environment, and post my
observation here in case anyone sees same (then that would be
a potential bug).
For RuntimeError: (28, 'No space left on device'), it seems that
xenstore database is corrupted. After removing old file, then that
error never occurs again. A similar bug is reported at:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=487
For " Error: Device 769 (vbd) could not be connected. Hotplug
Scripts not working.", things become complex.
- With latest tip, that error occurs if I use following line in
config file:
"disk = [ 'file:/var/images/domU.img,hda1,w' ]"
However it works if I setup loop device manually with:
"disk = [ 'phy:loop0,hda1,w' ]"
- With latest p2m tree, either way works for me
Since that diversity seems not easily explained by difference
between two trees, So I'm inclined to consider it as environmental
issue...
Thanks,
Kevin
>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>Tian, Kevin
>Sent: 2006年4月20日 13:44
>To: Alex Williamson
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] Can anybody succeed with the tip?
>
>>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>>Sent: 2006年4月20日 13:39
>>
>>On Thu, 2006-04-20 at 13:13 +0800, Tian, Kevin wrote:
>>> I just failed at creation:
>>>
>>> # xm create -c
>>> Using config file "/etc/xen/xmdefconfig".
>>> Error: (2, 'No such file or directory')
>>>
>>> However it works if I simply copied tools from an old Rev (9510)...
>>
>> That sounds like the error I get when I forget to run 'xend start':
>>
>># xm create -c
>>Using config file "/etc/xen/xmdefconfig".
>>Error: (2, 'No such file or directory')
>># xend start
>># xm create -c
>>Using config file "/etc/xen/xmdefconfig".
>>### domain f00000000411e5a8: rid=80000-c0000 mp_rid=2000
>>...
>>
>>Tip is working for me, please let me know if you determine it has a
>>problem. Thanks,
>>
>> Alex
>>
>
>I did run "xend start". By checking xend.log, it shows:
>RuntimeError: (28, 'No space left on device')
>
>Then I suspected issue from xenstore. After removing
>/var/lib/xenstored/tdb, then I observed a different behavior:
>Error: Device 769 (vbd) could not be connected. Hotplug scripts
>not working.
>
>The new error is easy to be seen long time ago, for several
>different reasons. But it disappears long for now.
>
>I'll re-build and re-check the environment, to see whether anything
>gets messed.
>
>BTW, Xiantao said he can also work on the latest tip...
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|