Xen users - Jul 2011 - Re: Re: XAPI on debian - sr-create issue

You''re right scout the last line. Out looks like xapi is waiting on
tapdisk to plug a key into xenstore. Perhaps a udev rule problem? Perhaps
someone who knows more about tapdisk than I well be able to diagnose this
tomorrow.

Mike

Sent from Samsung tablet

Sébastien RICCIO <sr@swisscenter.com> wrote:


Of course, here it is attached.

Last line seems interesting. However tapdisk2 is started and the device
is attached to the dom0.
As it''s a box for my experimentations I can give you shell access if
you
want to see things on the beast :)

Sébastien


On 07/20/2011 10:30 PM, Mike McClurg wrote:
> Can you provide the tail of xensource.log? It''s usually /var/log -
hopefully it gets put in the same place when run on Debian...
>
> Mike

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

On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
> You''re right scout the last line. Out looks like xapi is waiting
on tapdisk to plug a key into xenstore. Perhaps a udev rule problem? Perhaps
someone who knows more about tapdisk than I well be able to diagnose this
tomorrow.
Can you resent the attachment? Thx. :)

Daniel
> Mike
> 
> Sent from Samsung tablet
> 
> Sébastien RICCIO <sr@swisscenter.com> wrote:
> 
> 
> Of course, here it is attached.
> 
> Last line seems interesting. However tapdisk2 is started and the device
> is attached to the dom0.
> As it''s a box for my experimentations I can give you shell access
if you
> want to see things on the beast :)
> 
> Sébastien
> 
> 
> On 07/20/2011 10:30 PM, Mike McClurg wrote:
> > Can you provide the tail of xensource.log? It''s usually
/var/log - hopefully it gets put in the same place when run on Debian...
> >
> > Mike
> 


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

attachement sent again :)


On 07/20/2011 10:53 PM, Daniel Stodden wrote:
> On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
>> You''re right scout the last line. Out looks like xapi is
waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem?
Perhaps someone who knows more about tapdisk than I well be able to diagnose
this tomorrow.
> Can you resent the attachment? Thx. :)
>
> Daniel
>
>> Mike
>>
>> Sent from Samsung tablet
>>
>> Sébastien RICCIO<sr@swisscenter.com>  wrote:
>>
>>
>> Of course, here it is attached.
>>
>> Last line seems interesting. However tapdisk2 is started and the device
>> is attached to the dom0.
>> As it''s a box for my experimentations I can give you shell
access if you
>> want to see things on the beast :)
>>
>> Sébastien
>>
>>
>> On 07/20/2011 10:30 PM, Mike McClurg wrote:
>>> Can you provide the tail of xensource.log? It''s usually
/var/log - hopefully it gets put in the same place when run on Debian...
>>>
>>> Mike
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


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

On Wed, 2011-07-20 at 16:58 -0400, Sébastien RICCIO
wrote:
> attachement sent again :)
Looks wedged...right?

Then next xenstore-access.log please.

Thanks again :)

Daniel
> On 07/20/2011 10:53 PM, Daniel Stodden wrote:
> > On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
> >> You''re right scout the last line. Out looks like xapi is
waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem?
Perhaps someone who knows more about tapdisk than I well be able to diagnose
this tomorrow.
> > Can you resent the attachment? Thx. :)
> >
> > Daniel
> >
> >> Mike
> >>
> >> Sent from Samsung tablet
> >>
> >> Sébastien RICCIO<sr@swisscenter.com>  wrote:
> >>
> >>
> >> Of course, here it is attached.
> >>
> >> Last line seems interesting. However tapdisk2 is started and the
device
> >> is attached to the dom0.
> >> As it''s a box for my experimentations I can give you
shell access if you
> >> want to see things on the beast :)
> >>
> >> Sébastien
> >>
> >>
> >> On 07/20/2011 10:30 PM, Mike McClurg wrote:
> >>> Can you provide the tail of xensource.log? It''s
usually /var/log - hopefully it gets put in the same place when run on Debian...
> >>>
> >>> Mike
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> 


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

On Wed, 2011-07-20 at 17:08 -0400, Daniel Stodden wrote:
> On Wed, 2011-07-20 at 16:58 -0400, Sébastien RICCIO wrote:
> > attachement sent again :)
> 
> Looks wedged...right?
> 
> Then next xenstore-access.log please.
> 
> Thanks again :)
Coming to think of it -- Did we debianify XCP''s xen-bugtool already?

We obviously shall :)

Daniel
> Daniel
> 
> > On 07/20/2011 10:53 PM, Daniel Stodden wrote:
> > > On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
> > >> You''re right scout the last line. Out looks like
xapi is waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule
problem? Perhaps someone who knows more about tapdisk than I well be able to
diagnose this tomorrow.
> > > Can you resent the attachment? Thx. :)
> > >
> > > Daniel
> > >
> > >> Mike
> > >>
> > >> Sent from Samsung tablet
> > >>
> > >> Sébastien RICCIO<sr@swisscenter.com>  wrote:
> > >>
> > >>
> > >> Of course, here it is attached.
> > >>
> > >> Last line seems interesting. However tapdisk2 is started and
the device
> > >> is attached to the dom0.
> > >> As it''s a box for my experimentations I can give you
shell access if you
> > >> want to see things on the beast :)
> > >>
> > >> Sébastien
> > >>
> > >>
> > >> On 07/20/2011 10:30 PM, Mike McClurg wrote:
> > >>> Can you provide the tail of xensource.log? It''s
usually /var/log - hopefully it gets put in the same place when run on Debian...
> > >>>
> > >>> Mike
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > >
> > 
> 
> 


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

Looks wedged indeed :)

root@xen-blade13:/var/log# updatedb
root@xen-blade13:/var/log# locate xenstore-access.log
root@xen-blade13:/var/log#

No luck with this one :(


On 07/20/2011 11:08 PM, Daniel Stodden wrote:
> On Wed, 2011-07-20 at 16:58 -0400, Sébastien RICCIO wrote:
>> attachement sent again :)
> Looks wedged...right?
>
> Then next xenstore-access.log please.
>
> Thanks again :)
>
> Daniel
>

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

On Wed, 2011-07-20 at 17:17 -0400, Sébastien RICCIO
wrote:
> Looks wedged indeed :)
> 
> root@xen-blade13:/var/log# updatedb
> root@xen-blade13:/var/log# locate xenstore-access.log
> root@xen-blade13:/var/log#
> 
> No luck with this one :(
I''m not on top of things with the state of the debian port, so I
don''t
know what''s ported and what not.

Do you have a dedicated blkback build running or is this vanilla 2.6.39?

I also made a typo, should be sth like (note the *d)

dns@vantst16:/var/log$ ls -l /var/log/xenstored-access.log 
-rw-r--r-- 1 root root 332848 Jul 19 21:02 /var/log/xenstored-access.log

Do you find /var/log -name ''*xenstore*'' anything resembling
that?

Xen.org has some different name/format for the same thing, iirc. 

Do you have sth like this?

---
# cat /etc/xensource/xenstored.conf 
# default xenstored config

# Where the pid file is stored
pid-file = /var/run/xenstored.pid

# Activate transaction merge support
merge-activate = true

# Activate node permission system
perms-activate = true

# Activate quota
quota-activate = true
quota-maxentity = 1000
quota-maxsize = 2048
quota-maxwatch = 100
quota-transaction = 10

# Activate filed base backend
persistant = false

# Xenstored logs
# xenstored-log-file = /var/log/xenstored.log
# xenstored-log-level = null
# xenstored-log-nb-files = 10

# Xenstored access logs
# access-log-file = /var/log/xenstored-access.log
# access-log-nb-lines = 13215
# acesss-log-nb-chars = 180
access-log-special-ops = true
---

Daniel
> On 07/20/2011 11:08 PM, Daniel Stodden wrote:
> > On Wed, 2011-07-20 at 16:58 -0400, Sébastien RICCIO wrote:
> >> attachement sent again :)
> > Looks wedged...right?
> >
> > Then next xenstore-access.log please.
> >
> > Thanks again :)
> >
> > Daniel
> >
> 


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

OK, it''s nothing to do with tapdisk.

The frontend hotplug script needs a couple of changes that I had forgotten
about. I''ll post a fix asap.

Jon


On 20 Jul 2011, at 21:53, Daniel Stodden wrote:
> On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
>> You''re right scout the last line. Out looks like xapi is
waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem?
Perhaps someone who knows more about tapdisk than I well be able to diagnose
this tomorrow.
> 
> Can you resent the attachment? Thx. :)
> 
> Daniel
> 
>> Mike
>> 
>> Sent from Samsung tablet
>> 
>> Sébastien RICCIO <sr@swisscenter.com> wrote:
>> 
>> 
>> Of course, here it is attached.
>> 
>> Last line seems interesting. However tapdisk2 is started and the device
>> is attached to the dom0.
>> As it''s a box for my experimentations I can give you shell
access if you
>> want to see things on the beast :)
>> 
>> Sébastien
>> 
>> 
>> On 07/20/2011 10:30 PM, Mike McClurg wrote:
>>> Can you provide the tail of xensource.log? It''s usually
/var/log - hopefully it gets put in the same place when run on Debian...
>>> 
>>> Mike
>> 
> 
> 

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

On 07/20/2011 11:31 PM, Daniel Stodden wrote:
> On Wed, 2011-07-20 at 17:17 -0400, Sébastien RICCIO wrote:
>> Looks wedged indeed :)
>>
>> root@xen-blade13:/var/log# updatedb
>> root@xen-blade13:/var/log# locate xenstore-access.log
>> root@xen-blade13:/var/log#
>>
>> No luck with this one :(
> I''m not on top of things with the state of the debian port, so I
don''t
> know what''s ported and what not.
>
> Do you have a dedicated blkback build running or is this vanilla 2.6.39?
It''s the 3.0.0-rc6-686-pae from debian sid  that
i''verecompiled with a
patch to fix vga issue when used as dom0 for xen.

> I also made a typo, should be sth like (note the *d)
>
> dns@vantst16:/var/log$ ls -l /var/log/xenstored-access.log
> -rw-r--r-- 1 root root 332848 Jul 19 21:02 /var/log/xenstored-access.log
>
> Do you find /var/log -name ''*xenstore*'' anything
resembling that?
>
> Xen.org has some different name/format for the same thing, iirc.
>
> Do you have sth like this?
No, nothing that looks like this. I''m trying to figure out where it 
could be stored.
Neither I can''t find xenstored.conf. It looks like the debian packages 
for the 4.1 doesn''t provide the the same
configuration files as if it was installed from the sources.

After looking at the init.d script that starts xenstore, it seems to use 
/etc/defaults/xend as config file that contains:

XENCONSOLED_ARGSXENSTORED_ARGS
So I guess no logs are enabled by default for the xenstore daemon.


I''m reading now that Jon found the bug, I''ll wait for his fix,
try again
and let you know.

Thanks,
Sébastien

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

Good news! I will try it when posted.

Thanks a lot,

Sébastien

On 07/20/2011 11:58 PM, Jonathan Ludlam wrote:
> OK, it''s nothing to do with tapdisk.
>
> The frontend hotplug script needs a couple of changes that I had forgotten
about. I''ll post a fix asap.
>
> Jon
>
>
> On 20 Jul 2011, at 21:53, Daniel Stodden wrote:
>
>> On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
>>> You''re right scout the last line. Out looks like xapi is
waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem?
Perhaps someone who knows more about tapdisk than I well be able to diagnose
this tomorrow.
>> Can you resent the attachment? Thx. :)
>>
>> Daniel
>>
>>> Mike
>>>
>>> Sent from Samsung tablet
>>>
>>> Sébastien RICCIO<sr@swisscenter.com>  wrote:
>>>
>>>
>>> Of course, here it is attached.
>>>
>>> Last line seems interesting. However tapdisk2 is started and the
device
>>> is attached to the dom0.
>>> As it''s a box for my experimentations I can give you shell
access if you
>>> want to see things on the beast :)
>>>
>>> Sébastien
>>>
>>>
>>> On 07/20/2011 10:30 PM, Mike McClurg wrote:
>>>> Can you provide the tail of xensource.log? It''s
usually /var/log - hopefully it gets put in the same place when run on Debian...
>>>>
>>>> Mike
>>

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

I''ve uploaded a new deb, which Works For Me. Give it a spin and see how
it goes!

Jon

On 20 Jul 2011, at 23:03, Sébastien RICCIO wrote:
> Good news! I will try it when posted.
> 
> Thanks a lot,
> 
> Sébastien
> 
> On 07/20/2011 11:58 PM, Jonathan Ludlam wrote:
>> OK, it''s nothing to do with tapdisk.
>> 
>> The frontend hotplug script needs a couple of changes that I had
forgotten about. I''ll post a fix asap.
>> 
>> Jon
>> 
>> 
>> On 20 Jul 2011, at 21:53, Daniel Stodden wrote:
>> 
>>> On Wed, 2011-07-20 at 16:47 -0400, Mike McClurg wrote:
>>>> You''re right scout the last line. Out looks like xapi
is waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem?
Perhaps someone who knows more about tapdisk than I well be able to diagnose
this tomorrow.
>>> Can you resent the attachment? Thx. :)
>>> 
>>> Daniel
>>> 
>>>> Mike
>>>> 
>>>> Sent from Samsung tablet
>>>> 
>>>> Sébastien RICCIO<sr@swisscenter.com>  wrote:
>>>> 
>>>> 
>>>> Of course, here it is attached.
>>>> 
>>>> Last line seems interesting. However tapdisk2 is started and
the device
>>>> is attached to the dom0.
>>>> As it''s a box for my experimentations I can give you
shell access if you
>>>> want to see things on the beast :)
>>>> 
>>>> Sébastien
>>>> 
>>>> 
>>>> On 07/20/2011 10:30 PM, Mike McClurg wrote:
>>>>> Can you provide the tail of xensource.log? It''s
usually /var/log - hopefully it gets put in the same place when run on Debian...
>>>>> 
>>>>> Mike
>>> 
> 

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

Hi Jon,

Nice one. I can confirm it works at my side too, successfulyl 
plugged/unpluged vbd to dom0,
including the ones on my ocfs2 storage.


-- Plugging a vbd from local storage

root@xen-blade13:~# xe vbd-plug uuid=92a3b3bc-8b48-b13d-a53c-891c10fba1b9

[dmesg result]

[  272.585209] block tda: sector-size: 512/512+0 capacity: 62914560 
discard: 0+0 flush: 0x0
[  272.656198] xen-blkback:ring-ref 9, event-channel 90, protocol 1 
(x86_32-abi)
[  272.664439] blkfront: xvda: barrier or flush: disabled
[  272.666350]  xvda: xvda1

[trying to write to it]

root@xen-blade13:~# dd if=/dev/zero of=/dev/xvda bs=4096k count=1000 
oflag=direct
202+0 records out
847249408 bytes (847 MB) copied, 11.5655 s, 73.3 MB/s



-- Plugging a vbd from ocfs2 storage (only gigabit link atm, will be 
10gig soon)

root@xen-blade13:~# xe vbd-plug uuid=a0629baa-60d7-0c8a-f7b2-69b1ed27985c

[dmesg result]

[  396.784280] block tdb: sector-size: 512/512+0 capacity: 41943040 
discard: 0+0 flush: 0x0
[  396.858781] xen-blkback:ring-ref 10, event-channel 92, protocol 1 
(x86_32-abi)
[  396.864828] blkfront: xvdb: barrier or flush: disabled
[  396.866592]  xvdb: unknown partition table

[trying to write to it]

root@xen-blade13:~# dd if=/dev/zero of=/dev/xvdb bs=4096k count=1000 
oflag=direct
232+0 records out
973078528 bytes (973 MB) copied, 13.2006 s, 73.7 MB/s


Unplugging also works, but leave this entry in the dmesg:

[ 1072.380954] WARNING: g.e. still in use!
[ 1072.381029] WARNING: leaking g.e. and page still in use!

I don''t know if this is relevant to something bad. Anyone knows what it
means ? Should it be ignored ?

Thanks a lot for your work.
I''m now going to test the network things. Talking about this, does it 
makes sense to use standard bridged
networking when openvswitch is available ? Looks to me like in XCP and 
XenCenter beta (project boston)
  it has been replaced by openvswitch.

The openvswitch version provided by the debian sid repository contains a 
kernel module that does not
recompile compile against a 3.0.0 kernel, it has checks that looks for a 
"2.6" in kernel version.

So I have built the latest openvswitch version from the git repo as 
debian packages and vswitch is up
and running on my sandbox.

Any lead on how to use openvswitch layer with xapi on debian ?

The file 
/usr/src/openvswitch.last/xenserver/opt_xensource_libexec_InterfaceReconfigureVswitch.py
exists, but how to tell xapi to use this instead of bridge ?

I''m maybe going a bit too fast about this, but I''m ready to
test it :)

Cheers,
Sébastien


On 07/21/2011 02:10 AM, Jonathan Ludlam wrote:
> I''ve uploaded a new deb, which Works For Me. Give it a spin and
see how it goes!
>
> Jon
>
> On 20 Jul 2011, at 23:03, Sébastien RICCIO wrote:
>

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

Hi,

I think that if they are planned for XAPI on Debian, these init.d 
scripts are already
on your todo list, but in case they''re not, I just would like to report
that xapissl
(the stunnel for 443) and xapi-domains are missing from the deb packages.

Is there a todo list accessible somewhere, so that maybe I can check what is
already planned and avoid submitting unecessary reports ?

Thanks a lot.

Sébastien

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