thr3ads.net - Xen users - [Xen-users] Test [May 2005]

If this information is useful, please help other people find it:
Share via:

Jean-Michel Caricand

2005-May-26 21:37 UTC

[Xen-users] Test

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

Jean-Michel Caricand

2005-May-27 06:48 UTC

head link

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support

Mark Williamson a écrit :
>[off list]
>
>*ping!*
>
>Are you sure the kernel you''re using has ACL support compiled in?
>
>Did you format in dom0?  Is dom0 ACL aware?
>
>Cheers,
>Mark
>
>On Thursday 26 May 2005 22:37, Jean-Michel Caricand wrote:
>  
>
>>_______________________________________________
>>Xen-users mailing list
>>Xen-users@lists.xensource.com
>>http://lists.xensource.com/xen-users
>>    
>>
>
>  
>I use binary tarball xen-2.0.6-install.tgz and vmlinuz-2.6.11.10-xenU 
for my virtual machine.
mount with acl option in fstab work fine.

# mount
...
/dev/sdb3 on / type ext3 (rw,acl)
...

# setfacl -m u:ludo:rwx /home/
setfacl: /home: Opération non supportée


Other problem.  I want to  build my kernel to  ACL  support  myself :


amande:/home/jm/xen-2.0# make world

... lines ...

make[3]: Leaving directory `/home/jm/xen-2.0/tools/python''
make[3]: Entering directory `/home/jm/xen-2.0/tools/xfrd''
gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I 
../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xfrd.o.d 
-I/usr/include -c -o xfrd.o xfrd.c
gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I 
../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xen_domain.o.d 
-I/usr/include -c -o xen_domain.o xen_domain.c
xen_domain.c:179: error: erreur d''analyse syntaxique before
"curl_infotype"
xen_domain.c: Dans la fonction « curldebug »:
xen_domain.c:181: error: `data'' undeclared (first use in this function)
xen_domain.c:181: error: (Each undeclared identifier is reported only once
xen_domain.c:181: error: for each function it appears in.)
xen_domain.c:181: error: `buf_n'' undeclared (first use in this
function)
xen_domain.c: Dans la fonction « xen_domain_configure »:
xen_domain.c:317: error: `CURLFORMcode'' undeclared (first use in this 
function)
xen_domain.c:317: error: erreur d''analyse syntaxique before
"formcode"
xen_domain.c:327: error: `formcode'' undeclared (first use in this
function)
xen_domain.c:329: error: `CURLFORM_BUFFER'' undeclared (first use in
this
function)
xen_domain.c:330: error: `CURLFORM_BUFFERPTR'' undeclared (first use in 
this function)
xen_domain.c:331: error: `CURLFORM_BUFFERLENGTH'' undeclared (first use 
in this function)
xen_domain.c:333: attention : passage de l''argument n°1 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:333: attention : passage de l''argument n°2 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:342: attention : passage de l''argument n°1 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:342: attention : passage de l''argument n°2 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:353: attention : passage de l''argument n°1 de « 
curl_formfree » d''un type pointeur incompatible
xen_domain.c: Dans la fonction « xen_domain_unpause »:
xen_domain.c:370: error: `CURLFORMcode'' undeclared (first use in this 
function)
xen_domain.c:370: error: erreur d''analyse syntaxique before
"formcode"
xen_domain.c:378: error: `formcode'' undeclared (first use in this
function)
xen_domain.c:381: attention : passage de l''argument n°1 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:381: attention : passage de l''argument n°2 de « 
curl_formadd » d''un type pointeur incompatible
xen_domain.c:392: attention : passage de l''argument n°1 de « 
curl_formfree » d''un type pointeur incompatible
make[3]: *** [xen_domain.o] Erreur 1
make[3]: Leaving directory `/home/jm/xen-2.0/tools/xfrd''
make[2]: *** [install] Erreur 2
make[2]: Leaving directory `/home/jm/xen-2.0/tools''
make[1]: *** [tools] Erreur 2
make[1]: Leaving directory `/home/jm/xen-2.0''
make: *** [world] Erreur 2
amande:/home/jm/xen-2.0#   

I''m under Debian sarge. Any idea ?        

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

Mark Williamson

2005-May-27 09:45 UTC

head link

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support

You need the curl-devel package (header files etc).

Take a look on the FAQ at wiki.xensource.com - it has a list of the debian 
package names you''ll need to build Xen.

I''m not sure the fact that mount works with acl in the fstab
necessarily means
it is working - if the kernel doesn''t have support then it might just
be
ignoring it.

Cheers,
Mark

On Friday 27 May 2005 07:48, Jean-Michel Caricand wrote:> Mark Williamson a écrit :
> >[off list]
> >
> >*ping!*
> >
> >Are you sure the kernel you''re using has ACL support compiled
in?
> >
> >Did you format in dom0?  Is dom0 ACL aware?
> >
> >Cheers,
> >Mark
> >
> >On Thursday 26 May 2005 22:37, Jean-Michel Caricand wrote:
> >>_______________________________________________
> >>Xen-users mailing list
> >>Xen-users@lists.xensource.com
> >>http://lists.xensource.com/xen-users
>
> I use binary tarball xen-2.0.6-install.tgz and vmlinuz-2.6.11.10-xenU
> for my virtual machine.
> mount with acl option in fstab work fine.
>
> # mount
> ...
> /dev/sdb3 on / type ext3 (rw,acl)
> ...
>
> # setfacl -m u:ludo:rwx /home/
> setfacl: /home: Opération non supportée
>
>
> Other problem.  I want to  build my kernel to  ACL  support  myself :
>
>
> amande:/home/jm/xen-2.0# make world
>
> ... lines ...
>
> make[3]: Leaving directory `/home/jm/xen-2.0/tools/python''
> make[3]: Entering directory `/home/jm/xen-2.0/tools/xfrd''
> gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
> ../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xfrd.o.d
> -I/usr/include -c -o xfrd.o xfrd.c
> gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
> ../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xen_domain.o.d
> -I/usr/include -c -o xen_domain.o xen_domain.c
> xen_domain.c:179: error: erreur d''analyse syntaxique before
"curl_infotype"
> xen_domain.c: Dans la fonction « curldebug »:
> xen_domain.c:181: error: `data'' undeclared (first use in this
function)
> xen_domain.c:181: error: (Each undeclared identifier is reported only once
> xen_domain.c:181: error: for each function it appears in.)
> xen_domain.c:181: error: `buf_n'' undeclared (first use in this
function)
> xen_domain.c: Dans la fonction « xen_domain_configure »:
> xen_domain.c:317: error: `CURLFORMcode'' undeclared (first use in
this
> function)
> xen_domain.c:317: error: erreur d''analyse syntaxique before
"formcode"
> xen_domain.c:327: error: `formcode'' undeclared (first use in this
function)
> xen_domain.c:329: error: `CURLFORM_BUFFER'' undeclared (first use
in this
> function)
> xen_domain.c:330: error: `CURLFORM_BUFFERPTR'' undeclared (first
use in
> this function)
> xen_domain.c:331: error: `CURLFORM_BUFFERLENGTH'' undeclared (first
use
> in this function)
> xen_domain.c:333: attention : passage de l''argument n°1 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:333: attention : passage de l''argument n°2 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:342: attention : passage de l''argument n°1 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:342: attention : passage de l''argument n°2 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:353: attention : passage de l''argument n°1 de «
> curl_formfree » d''un type pointeur incompatible
> xen_domain.c: Dans la fonction « xen_domain_unpause »:
> xen_domain.c:370: error: `CURLFORMcode'' undeclared (first use in
this
> function)
> xen_domain.c:370: error: erreur d''analyse syntaxique before
"formcode"
> xen_domain.c:378: error: `formcode'' undeclared (first use in this
function)
> xen_domain.c:381: attention : passage de l''argument n°1 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:381: attention : passage de l''argument n°2 de «
> curl_formadd » d''un type pointeur incompatible
> xen_domain.c:392: attention : passage de l''argument n°1 de «
> curl_formfree » d''un type pointeur incompatible
> make[3]: *** [xen_domain.o] Erreur 1
> make[3]: Leaving directory `/home/jm/xen-2.0/tools/xfrd''
> make[2]: *** [install] Erreur 2
> make[2]: Leaving directory `/home/jm/xen-2.0/tools''
> make[1]: *** [tools] Erreur 2
> make[1]: Leaving directory `/home/jm/xen-2.0''
> make: *** [world] Erreur 2
> amande:/home/jm/xen-2.0#
>
> I''m under Debian sarge. Any idea ?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Jean-Michel Caricand

2005-May-27 12:46 UTC

head link

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support

Mark Williamson a écrit :
>You need the curl-devel package (header files etc).
>
>Take a look on the FAQ at wiki.xensource.com - it has a list of the debian 
>package names you''ll need to build Xen.
>
>I''m not sure the fact that mount works with acl in the fstab
necessarily means
>it is working - if the kernel doesn''t have support then it might
just be
>ignoring it.
>
>Cheers,
>Mark
>
>On Friday 27 May 2005 07:48, Jean-Michel Caricand wrote:
>  
>
>>Mark Williamson a écrit :
>>    
>>
>>>[off list]
>>>
>>>*ping!*
>>>
>>>Are you sure the kernel you''re using has ACL support
compiled in?
>>>
>>>Did you format in dom0?  Is dom0 ACL aware?
>>>
>>>Cheers,
>>>Mark
>>>
>>>On Thursday 26 May 2005 22:37, Jean-Michel Caricand wrote:
>>>      
>>>
>>>>_______________________________________________
>>>>Xen-users mailing list
>>>>Xen-users@lists.xensource.com
>>>>http://lists.xensource.com/xen-users
>>>>        
>>>>
>>I use binary tarball xen-2.0.6-install.tgz and vmlinuz-2.6.11.10-xenU
>>for my virtual machine.
>>mount with acl option in fstab work fine.
>>
>># mount
>>...
>>/dev/sdb3 on / type ext3 (rw,acl)
>>...
>>
>># setfacl -m u:ludo:rwx /home/
>>setfacl: /home: Opération non supportée
>>
>>
>>Other problem.  I want to  build my kernel to  ACL  support  myself :
>>
>>
>>amande:/home/jm/xen-2.0# make world
>>
>>... lines ...
>>
>>make[3]: Leaving directory `/home/jm/xen-2.0/tools/python''
>>make[3]: Entering directory `/home/jm/xen-2.0/tools/xfrd''
>>gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
>>../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xfrd.o.d
>>-I/usr/include -c -o xfrd.o xfrd.c
>>gcc  -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
>>../../tools/libxc -I ../../tools/libxutil -Wp,-MD,.xen_domain.o.d
>>-I/usr/include -c -o xen_domain.o xen_domain.c
>>xen_domain.c:179: error: erreur d''analyse syntaxique before
"curl_infotype"
>>xen_domain.c: Dans la fonction « curldebug »:
>>xen_domain.c:181: error: `data'' undeclared (first use in this
function)
>>xen_domain.c:181: error: (Each undeclared identifier is reported only
once
>>xen_domain.c:181: error: for each function it appears in.)
>>xen_domain.c:181: error: `buf_n'' undeclared (first use in this
function)
>>xen_domain.c: Dans la fonction « xen_domain_configure »:
>>xen_domain.c:317: error: `CURLFORMcode'' undeclared (first use
in this
>>function)
>>xen_domain.c:317: error: erreur d''analyse syntaxique before
"formcode"
>>xen_domain.c:327: error: `formcode'' undeclared (first use in
this function)
>>xen_domain.c:329: error: `CURLFORM_BUFFER'' undeclared (first
use in this
>>function)
>>xen_domain.c:330: error: `CURLFORM_BUFFERPTR'' undeclared (first
use in
>>this function)
>>xen_domain.c:331: error: `CURLFORM_BUFFERLENGTH'' undeclared
(first use
>>in this function)
>>xen_domain.c:333: attention : passage de l''argument n°1 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:333: attention : passage de l''argument n°2 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:342: attention : passage de l''argument n°1 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:342: attention : passage de l''argument n°2 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:353: attention : passage de l''argument n°1 de «
>>curl_formfree » d''un type pointeur incompatible
>>xen_domain.c: Dans la fonction « xen_domain_unpause »:
>>xen_domain.c:370: error: `CURLFORMcode'' undeclared (first use
in this
>>function)
>>xen_domain.c:370: error: erreur d''analyse syntaxique before
"formcode"
>>xen_domain.c:378: error: `formcode'' undeclared (first use in
this function)
>>xen_domain.c:381: attention : passage de l''argument n°1 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:381: attention : passage de l''argument n°2 de «
>>curl_formadd » d''un type pointeur incompatible
>>xen_domain.c:392: attention : passage de l''argument n°1 de «
>>curl_formfree » d''un type pointeur incompatible
>>make[3]: *** [xen_domain.o] Erreur 1
>>make[3]: Leaving directory `/home/jm/xen-2.0/tools/xfrd''
>>make[2]: *** [install] Erreur 2
>>make[2]: Leaving directory `/home/jm/xen-2.0/tools''
>>make[1]: *** [tools] Erreur 2
>>make[1]: Leaving directory `/home/jm/xen-2.0''
>>make: *** [world] Erreur 2
>>amande:/home/jm/xen-2.0#
>>
>>I''m under Debian sarge. Any idea ?
>>    
>>
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users
>
>  
>Hi Mark,

You are right !!!

I have to install libcurl3-dev in the place of libcurl-dev and the
kernel vmlinuz-2.6.11-xenU does not have option ACL for Ext3 file system.

While trying to build Xen 2.0, I have this error:

# make ARCH=xen menuconfig
I add ACL for ext3 fs

# make

...

  CC      drivers/video/console/vgacon.o
  LD      drivers/video/console/built-in.o
  LD      drivers/video/built-in.o
  CC      drivers/xen/balloon/balloon.o
drivers/xen/balloon/balloon.c: Dans la fonction « balloon_process »:
drivers/xen/balloon/balloon.c:218: error: `phys_to_machine_mapping'' 
undeclared (first use in this function)
drivers/xen/balloon/balloon.c:218: error: (Each undeclared identifier is 
reported only once
drivers/xen/balloon/balloon.c:218: error: for each function it appears in.)
drivers/xen/balloon/balloon.c:218: error: `INVALID_P2M_ENTRY''
undeclared
(first use in this function)
drivers/xen/balloon/balloon.c:261: attention : implicit declaration of 
function `scrub_pages''
drivers/xen/balloon/balloon.c:283: attention : implicit declaration of 
function `mfn_to_pfn''
make[3]: *** [drivers/xen/balloon/balloon.o] Erreur 1
make[2]: *** [drivers/xen/balloon] Erreur 2
make[1]: *** [drivers/xen] Erreur 2
make: *** [drivers] Erreur 2
amande:/home/jm/xen-2.0/linux-2.6.11-xen0#

Have I forget anything ?

Thanks. 



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

Xen users - May 2005 - Test

[Xen-users] Test

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support

Re: [Xen-users] Test - Xen 2.0 compilation - ACL support