|
List Info
Thread: 4gb seg fixup, process on FC6 domU
|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 14:37:41 |
|
On 12/20/06, Daniel P. Berrange < berrange redhat.com">berrangeredhat.com> wrote:
On Wed, Dec 20, 2006 at 07:19:06PM +0500, Asrai khn wrote:
>; Hi Dan,
>
>
> Both of those are redundant/wrong for FC6.
> >
> >First, there is no separate /lib/tls anymore - FC6 ditched old pthreads
> >implementation, and the new NPTL is the default in /lib. So renaming the
> >empty /lib/tls directory is irrelevant.
> >
> >Second, the 'hwcap 0 nosegneg' stuff is automatically installed by the
> >Xen kernel RPM, eg
> >
> > $ rpm -qf /etc/ld.so.conf.d/kernelcap-2.6.18-1.2868.fc6.conf
>; > kernel-xen-2.6.18-1.2868.fc6
>
>
> When i do this on host machine gives me...
>;
> rpm -qf /etc/ld.so.conf.d/kernelcap-2.6.18-1.2849.fc6.conf
>; kernel-xen-2.6.18-1.2849.fc6
>;
> but gives nothing on guest, i don't have /etc/ld.so.conf.d/kernelcap-
>; 2.6.18-1.2849.fc6.conf
on guests
So, have you actually got a kernel-xen installed in your guest ? It
sounds very much like you dont....
yes we don't have xen kernel on guest ; coz we are not using pygrub.
> I'm launching guest using xm create vms.cfg
>
> and vms.cfg is as under
>;
> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen"
> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen-domU.img"
The fact that you are explicitly listing kernels from Dom0 instead of
using the regular pygrub bootloader, also suggests to me you've not
got kernel-xen installed in your guest image
True, no pygrub
> memory = 128
> name = "xxxx"
> #vif = [ 'mac=00:16:3e:11:69:85, bridge=xenbr0' ]
> vif = [ 'ip=66.xxx.xxx.xxx' ]
> disk = ['tap:aio:/var/uml/vm3/root,sda1,w',
> 'tap:aio:/var/uml/vm3/var,sda2,w', 'tap:aio:/var/uml/vm3/swap,sda3,w']
> root = "/dev/sda1 ro"
> on_reboot = 'restart'
>; on_crash = 'restart'
>;
> So the kernel running on guest ... and i have also copied the xen kernel
>; modules /lib/modules/ on guest disk image by mounting it.
If you're not using pygrub, then you'll at least need to make sure the
correct 'kernelcap' file is installed in the guest, with file name
matching the kernel version.
What do you mean by install 'kernelcap' file on guest?
you want me to create this file manually in the specific path and then echo 'something' to it?
Thanks. Askar
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- ; Perl modules: http://search.cpan.org/~danberr/ ; -=|
|=- ; Projects: http://freshmeat.net/~danielpb/
; -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
|
| Deadline Extension: Call for tutorials
ESWC 2007 |
|
2006-12-21 09:58:13 |
Please note that the deadline for tutorial proposals has
been extended
until 10 January 2007.
best regards,
Stijn
[Apologies if you receive multiple copies]
============================================================
======
CALL FOR TUTORIALS
4th European Semantic Web Conference (ESWC 2007)
3-7 June 2007
Innsbruck, Austria
DESCRIPTION The vision of the Semantic Web is to enhance
today’s web via the
exploitation of machine-processable meta data. The explicit
representation of
the semantics of data, enriched with domain theories
(Ontologies), will enable
a web that provides a qualitatively new level of service. It
will weave
together a large network of human knowledge and makes this
knowledge
machine-processable. Various automated services will help
the users to achieve
their goals by accessing and processing information in
machine-understandable
form. This network of knowledge systems will ultimately lead
to truly
intelligent systems, which will be employed for various
specialized reasoning
subsystems to accomplish complex tasks. Many technologies
and methodologies are
being developed within Artificial Intelligence, Natural
Language Processing,
Machine Learning, Databases, Multimedia Systems, Distributed
Systems, Software
Engineering and Information Systems that can contribute
towards the realization
of this vision.
The 4th Annual European Semantic Web Conference (ESWC 2007)
will present the
latest results in research and application of Semantic Web
technologies,
including knowledge mark-up languages, Semantic Web
services, and ontology
management. More details can be found on the ESWC 2007
homepage.
In addition to the regular research and workshop programme,
ESWC 2007 invites
tutorials on relevant topics of interest. A tutorial should
present the state
of the art of a semantic web area enabling attendees to
fully appreciate the
current issues, main schools of thought and possible
application areas.
Proposals for tutorials are welcome for the ESWC 2007 topics
of interest (see
bottom); tutorial proposals are requested to follow the
submission process
defined below.
TUTORIAL PROPOSALS
ESWC 2007 tutorials may be either for a full day or for a
half day. Unless
there is a clear rationale we will give preference to half
day tutorials over
full day tutorials.
Tutorials proposed for the ESWC 2007 should cover one topic
in appropriate
depth (see ESWC 2007 topics below), and present this in a
appropriate manner
which enables attendees to fully comprehend and apply
emerging Semantic Web
technologies. Although tutorials may focus entirely on
theoretical aspects, we
strongly encourage hands-on sessions where appropriate.
Tutorial proposals should not exceed 5 pages in DIN A4
format and should
contain the following information:
* abstract (200 words maximum; to be published on the
ESWC 2007 website)
* tutorial description (aims, content, presentation
style, technical requirements)
* relevance of the tutorial to ESWC 2007
* outline of the tutorial content and schedule
* information on presenters (name, affiliation,
expertise, experiences in teaching and in tutorial
presentation)
Tutorial proposals are to be submitted to Joerg Diederich,
email: diederich at l3s dot de www: http://www.l3s.de/~diede
rich
Submitted proposals that follow the above guidelines will be
reviewed by the
ESWC 2007 organizing committee with respect to the relevance
of the topic, the
content, and the presentation style.
Important Dates:
* submission deadline for tutorial proposals: 10 January
2007
* notification of acceptance: 18 January 2007
* tutorial hand-outs due: 31 March 2007
* tutorial presentation date: 3 June 2007
For accepted tutorials, the presenters will need to submit
the material for
hand-outs (the slide sets and / or additional information;
software
installation and usage guides for practical hands-on
sessions) to the
organization committee for preprinting and placement on the
ESWC 2007 website.
For each accepted tutorial, we offer one discount of 180 EUR
on the
registration fee for ESWC 2007 (50% of the Early-Bird
registration fee).
TOPIC LIST The topics of interest for tutorials include, but
are not limited to
the following:
* Ontology Management (creation, evolution, evaluation,
etc.)
* Ontology Alignment (mapping, matching, merging,
mediation and reconciliation)
* Ontology Learning and Metadata Generation (e.g. HLT
and ML approaches)
* Multimedia and Semantic Web
* Semantic Annotation of Data
* Semantic Web Trust, Privacy, Security and Intellectual
Property Rights
* Semantic Web Rules and Query Languages
* Logics for the Semantic Web
* Reasoning on the Semantic Web
* Behavior in the Semantic Web
* Searching, Querying, Visualizing, Navigating and
Browsing the Semantic Web
* Personalization and User Modelling
* User Interfaces and Semantic Web
* Semantic Grid and Middleware
* Semantic Web Services (description, discovery,
invocation, composition, choreography, etc.)
* Semantic Web-based Knowledge Management (e.g. Semantic
Desktop, Knowledge Portals)
* Semantic Web for e-Business, e-Culture, e-Government,
e-Health, e-Learning, e-Science
* Database Technologies for the Semantic Web
* Data Semantics and Web Semantics
* Semantic Interoperability
* Semantic Workflows
* Semantic Web Mining
TUTORIAL CHAIR Joerg Diederich (L3S Research Center),
diederich at l3s dot de, http://www.l3s.de/~diede
rich
|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 14:44:10 |
On Wed, Dec 20, 2006 at 07:37:41PM +0500, Asrai khn wrote:
> On 12/20/06, Daniel P. Berrange <berrangeredhat.com> wrote:
> >On Wed, Dec 20, 2006 at 07:19:06PM +0500, Asrai khn
wrote:
> >
> >If you're not using pygrub, then you'll at least
need to make sure the
> >correct 'kernelcap' file is installed in the guest,
with file name
> >matching the kernel version.
>
>
> What do you mean by install 'kernelcap' file on guest?
> you want me to create this file manually in the
specific path and then echo
> 'something' to it?
Actually i've realized its not the name of the config name
which matters.
The issue is you need to run 'ldconfig' after creating the
config file so
that it updates its library cache
echo "hwcap 0 nosegneg" >
/etc/ld.conf.so.d/nosegneg.conf
ldconfig
Once you've done that, you can verify the linker knows about
Xen variant
by looking for libc mapping. eg before I add the hwcap stuff
it shows:
# ldconfig -v -p 2>&1 | grep libc.so
libc.so.6 (libc6, OS ABI: Linux 2.6.9) =>
/lib/libc.so.6
Once I create the hwcap setting & re-run ldconfig it
shows
# ldconfig -v -p 2>&1 | grep libc.so
libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI:
Linux 2.6.9) => /lib/i686/nosegneg/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 2.6.9) =>
/lib/libc.so.6
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1
978 392 2496 -=|
|=- Perl modules: http://search.cpan.o
rg/~danberr/ -=|
|=- Projects: http://freshmeat.net/
~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF
F742 7D3B 9505 -=|
--
Fedora-xen mailing list
Fedora-xenredhat.com
ht
tps://www.redhat.com/mailman/listinfo/fedora-xen
|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 14:58:46 |
|
On 12/20/06, Daniel P. Berrange < berrangeredhat.com">berrangeredhat.com> wrote:
On Wed, Dec 20, 2006 at 07:37:41PM +0500, Asrai khn wrote:
>; On 12/20/06, Daniel P. Berrange < berrangeredhat.com">berrangeredhat.com> wrote:
>; >On Wed, Dec 20, 2006 at 07:19:06PM +0500, Asrai khn wrote:
> >
> >If you're not using pygrub, then you'll at least need to make sure the
> >correct 'kernelcap' file is installed in the guest, with file name
> >matching the kernel version.
>
>
> What do you mean by install 'kernelcap' file on guest?
>; you want me to create this file manually in the specific path and then echo
> 'something' to it?
Actually i've realized its not the name of the config name which matters.
The issue is you need to run 'ldconfig' after creating the config file so
that it updates its library cache
echo "hwcap 0 nosegneg" > /etc/ld.conf.so.d/nosegneg.conf
;ldconfig
Right, I did this and run 'ldconfig' afterward but its /etc/ld.so.conf.d/nosegneg.conf not /etc/ld.conf.so.d/nosegneg.conf , may be typo
Once you've done that, you can verify the linker knows about Xen variant
by looking for libc mapping. eg before I add the hwcap stuff it shows:
# ldconfig -v -p 2>&1 | grep libc.so
; libc.so.6
(libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6
I get this before echo thing...
ldconfig -v -p 2>&1 | grep libc.so
; libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6
Once I create the hwcap setting & re-run ldconfig it shows
# ldconfig -v -p 2>&1 | grep
libc.so
; libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => /lib/i686/nosegneg/libc.so.6
;libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6
After hwcap I get ..
ldconfig -v -p 2>&1 | grep libc.so
; libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => /lib/i686/nosegneg/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6
But still getting those ; '4gb seg fixup, process9; errors
ldconfig is enough not need to reboot the guest right?
Thanks. Askar
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- ; Perl modules: http://search.cpan.org/~danberr/ ; -=|
|=- ; ; Projects: http://freshmeat.net/~danielpb/ ; ; -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 15:02:54 |
On Wed, Dec 20, 2006 at 07:58:46PM +0500, Asrai khn wrote:
> On 12/20/06, Daniel P. Berrange <berrangeredhat.com> wrote:
> >
> >On Wed, Dec 20, 2006 at 07:37:41PM +0500, Asrai khn
wrote:
> >> On 12/20/06, Daniel P. Berrange
<berrangeredhat.com> wrote:
> >> >On Wed, Dec 20, 2006 at 07:19:06PM +0500,
Asrai khn wrote:
> >> >
> >> >If you're not using pygrub, then you'll at
least need to make sure the
> >> >correct 'kernelcap' file is installed in
the guest, with file name
> >> >matching the kernel version.
> >>
> >>
> >> What do you mean by install 'kernelcap' file
on guest?
> >> you want me to create this file manually in
the specific path and then
> >echo
> >> 'something' to it?
> >
> >Actually i've realized its not the name of the
config name which matters.
> >The issue is you need to run 'ldconfig' after
creating the config file so
> >that it updates its library cache
> >
> > echo "hwcap 0 nosegneg" >
/etc/ld.conf.so.d/nosegneg.conf
> > ldconfig
>
>
> Right, I did this and run 'ldconfig' afterward but its
> /etc/ld.so.conf.d/nosegneg.conf not
/etc/ld.conf.so.d/nosegneg.conf , may be
> typo
>
> Once you've done that, you can verify the linker knows
about Xen variant
> >by looking for libc mapping. eg before I add the
hwcap stuff it shows:
> >
> > # ldconfig -v -p 2>&1 | grep libc.so
> > libc.so.6 (libc6, OS ABI: Linux 2.6.9)
=> /lib/libc.so.6
>
>
> I get this before echo thing...
>
> ldconfig -v -p 2>&1 | grep libc.so
> libc.so.6 (libc6, OS ABI: Linux 2.6.9) =>
/lib/libc.so.6
>
>
> Once I create the hwcap setting & re-run ldconfig
it shows
> >
> > # ldconfig -v -p 2>&1 | grep libc.so
> > libc.so.6 (libc6, hwcap:
0x0018000000000000, OS ABI: Linux 2.6.9)
> >=> /lib/i686/nosegneg/libc.so.6
> > libc.so.6 (libc6, OS ABI: Linux 2.6.9)
=> /lib/libc.so.6
>
>
> After hwcap I get ..
>
> ldconfig -v -p 2>&1 | grep libc.so
> libc.so.6 (libc6, hwcap: 0x0018000000000000, OS
ABI: Linux 2.6.9) =>
> /lib/i686/nosegneg/libc.so.6
> libc.so.6 (libc6, OS ABI: Linux 2.6.9) =>
/lib/libc.so.6
>
> But still getting those '4gb seg fixup, process'
errors
>
> ldconfig is enough not need to reboot the guest right?
Nope. All you've done is update the linker cache. This means
any new processes
you've spawned will use the correct libc. Any old processes
will still have
the old (Xen unfriendly) libc mapped into memory. A reboot
is the only way
to get everything using the new settings I'm afraid.
NB, even with this change you'll see the 4gb fixup messages
if you run any
mono processes - eg beagle or tomboy - this is a bug in the
Mono VM for
which there isn't any fix yet.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1
978 392 2496 -=|
|=- Perl modules: http://search.cpan.o
rg/~danberr/ -=|
|=- Projects: http://freshmeat.net/
~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF
F742 7D3B 9505 -=|
--
Fedora-xen mailing list
Fedora-xenredhat.com
ht
tps://www.redhat.com/mailman/listinfo/fedora-xen
|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 15:16:37 |
|
Hi Dan,
Nope. All you've done is update the linker cache. This means any new processes
you've spawned will use the correct libc. ; Any old processes will still have
the old (Xen unfriendly) libc mapped into memory. A reboot is the only way
to get everything using the new settings I'm afraid. Cool after reboot i'm am getting those errors not in logs neither when connect to guest via console 
So the solution
echo "hwcap 0 nosegneg" > /etc/ld.conf.so.d/nosegneg.conf
work for us.
NB, even with this change you'll see the 4gb fixup messages if you run any
mono processes - eg beagle or tomboy - this is a bug in the Mono VM for
which there isn't any fix yet. We don't use mono process beagle or tomboy.
I very much appreciate your help
Thanks. Askar
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- ; Perl modules: http://search.cpan.org/~danberr/ ; -=|
|=- ; Projects:
http://freshmeat.net/~danielpb/ ; ; -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 16:15:53 |
Hi,
On 12/20/06, Asrai khn <asraikhngmail.com> wrote:
> So the solution
>
> echo "hwcap 0 nosegneg" >
/etc/ld.conf.so.d/nosegneg.conf
>
> work for us.
don't forget the ldconfig. people searching the list archive
might
wonder why it doesn't work for them because they just follow
this mail
here...
> > NB, even with this change you'll see the 4gb fixup
messages if you run any
> > mono processes - eg beagle or tomboy - this is a
bug in the Mono VM for
> > which there isn't any fix yet.
>
> We don't use mono process beagle or tomboy.
I also had this annoying problem but also on Domain 0. When
reading
the "fine print" I saw the hint on mono causing
theses things.
removed beagle and everything works fine.
thanks,
Henning
--
Fedora-xen mailing list
Fedora-xenredhat.com
ht
tps://www.redhat.com/mailman/listinfo/fedora-xen
|
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-20 21:35:57 |
|
Hi,
Let me clear the type which we are doing from the very start of this thread
on FC6 instead of
echo "hwcap 0 nosegneg" > /etc/ld.conf.so.d/nosegneg.conf <--- type in the directory name
do this ...
echo hwcap 0 nosegneg" > /etc/ld.so.conf.d/nosegneg.conf
and then
ldconfig
Thanks. Askar
On 12/20/06,
Henning Sprang < henning_spranggmx.de">henning_spranggmx.de>; wrote:
Hi,
On 12/20/06, Asrai khn < asraikhngmail.com">asraikhngmail.com> wrote:
>; So the solution
>
> echo "hwcap 0 nosegneg" > /etc/ld.conf.so.d/nosegneg.conf
>
> work for us.
don't forget the ldconfig. people searching the list archive might
wonder why it doesn't work for them because they just follow this mail
here...
> > NB, even with this change you'll see the 4gb fixup messages if you run any
> > mono processes - eg beagle or tomboy - this is a bug in the Mono VM for
> > which there isn't any fix yet.
>
> We don't use mono process beagle or tomboy.
I also had this annoying problem but also on Domain 0. When reading
the "fine print"; I saw the hint on mono causing theses things.
removed beagle and everything works fine.
thanks,
Henning
--
Fedora-xen mailing list
Fedora-xenredhat.com">
Fedora-xenredhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
|
| 4gb seg fixup, process on FC6 domU |
|
2006-12-21 14:09:09 |
On 12/20/06, Asrai khn <asraikhngmail.com> wrote:
> do this ...
>
> echo hwcap 0 nosegneg" >
/etc/ld.so.conf.d/nosegneg.conf
or better
echo "hwcap 0 nosegneg" >
/etc/ld.so.conf.d/nosegneg.conf
>
> and then
>
> ldconfig
Yep.
And remove beagle when you want to get rid of all
warnings...
Henning
--
Fedora-xen mailing list
Fedora-xenredhat.com
ht
tps://www.redhat.com/mailman/listinfo/fedora-xen
|
|
[1-9]
|
|