Re: [PATCH] Changed java-example to use java.so directly to start example Hello application

[Waldek Kozaczuk]

Tomasz,

You can ignore this patch. I create new issue #800 and send corresponding 
patch that addresses the problem in a better way.

I will be sending another patch that cleans the apps later.

Waldek

On Thursday, September 22, 2016 at 11:44:59 AM UTC-4, Tomasz Grabiec wrote:
>
> On Wed, Sep 21, 2016 at 6:44 PM, Waldek Kozaczuk  > wrote: 
> > But in order to run multiple java modules/apps it need MultiJarLoader 
> which 
> > would not work on compact profile JRE. On other hand it is just an 
> example. 
> > 
> > My motivation for this patch was to get rid of 3 extra 
> java_compact*_example 
> > apps. But maybe instead of changing java_example I can simply reduce 
> > java_compact*_example to something like java_singleapp_example that 
> would 
> > use java.so. Thoughts? 
>
> Perhaps java module linking should detect if compact-profile runtime 
> is used and fall back to not using isolation framework, and complain 
> during build if more than one JVM application is being compiled into 
> the image. 
>
> This way all java modules could keep using run_java() and be generic. 
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PATCH] Support building and running Java apps in non-isolated mode

[Waldemar Kozaczuk]

Added new java-non-isolated module and refactored
 scripts/module.py to provide isolated_jvm and non_isolated_jvm as a way to
 build and run java apps in isolated (old default) and non-isolated mode.

The non-isolated mode gets enabled by module.py that detects if selected 
 java module (provides = ['java']) has following attribute set to true like so:

non_isolated_jvm = True

Example to build an image with isolated JVM (default):
./scripts/build image=java,java-example

Example to build an image with non-isolated JVM:
./scripts/build image=java-non-isolated,java-example

Fixes #800

Signed-off-by: Waldemar Kozaczuk 
---
 modules/java-non-isolated/Makefile | 10 ++
 modules/java-non-isolated/module.py| 28 
 modules/java-non-isolated/usr.manifest | 21 +
 scripts/module.py  | 25 ++---
 4 files changed, 81 insertions(+), 3 deletions(-)
 create mode 100644 modules/java-non-isolated/Makefile
 create mode 100644 modules/java-non-isolated/module.py
 create mode 100644 modules/java-non-isolated/usr.manifest

diff --git a/modules/java-non-isolated/Makefile 
b/modules/java-non-isolated/Makefile
new file mode 100644
index 000..d5d916e
--- /dev/null
+++ b/modules/java-non-isolated/Makefile
@@ -0,0 +1,10 @@
+# TODO: need to move compilation of $(java-targets) from the main makefile
+# to here. Unfortunately, compiling with OSv header files is a big mess,
+# and much easier to do it in the main OSv makefile :-(
+SRC = $(shell readlink -f ../..)
+module:
+   cd $(SRC)/java && mvn package -DskipTests=true
+
+clean:
+   cd $(SRC)/java && mvn clean
+   -rm -f dependency-reduced-pom.xml
diff --git a/modules/java-non-isolated/module.py 
b/modules/java-non-isolated/module.py
new file mode 100644
index 000..1f5b401
--- /dev/null
+++ b/modules/java-non-isolated/module.py
@@ -0,0 +1,28 @@
+from osv.modules.filemap import FileMap
+from osv.modules import api
+import os, os.path
+
+usr_files = FileMap()
+
+provides = ['java']
+
+non_isolated_jvm = True
+
+api.require('fonts')
+api.require('ca-certificates')
+api.require('libz')
+api.require('josvsym')
+api.require('httpserver-jolokia-plugin')
+api.require('httpserver-jvm-plugin')
+
+jdkdir = os.path.basename(os.path.expandvars('${jdkbase}'))
+
+usr_files.add('${jdkbase}').to('/usr/lib/jvm/java') \
+.include('lib/**') \
+.include('jre/**') \
+.exclude('jre/lib/security/cacerts') \
+.exclude('jre/lib/audio/**')
+
+usr_files.link('/usr/lib/jvm/' + jdkdir).to('java')
+usr_files.link('/usr/lib/jvm/jre').to('java/jre')
+usr_files.link('/usr/lib/jvm/java/jre/lib/security/cacerts').to('/etc/pki/java/cacerts')
diff --git a/modules/java-non-isolated/usr.manifest 
b/modules/java-non-isolated/usr.manifest
new file mode 100644
index 000..63b11bc
--- /dev/null
+++ b/modules/java-non-isolated/usr.manifest
@@ -0,0 +1,21 @@
+#
+# Copyright (C) 2013-2014 Cloudius Systems, Ltd.
+#
+# This work is open source software, licensed under the terms of the
+# BSD license as described in the LICENSE file in the top-level directory.
+#
+
+[manifest]
+/usr/lib/&/libexpat.so.1: %(miscbase)s/usr/lib64/&
+/usr/lib/&/libjpeg.so.62: %(miscbase)s/usr/lib64/&
+/usr/lib/jni/balloon.so: java/jni/balloon.so
+/usr/lib/jni/monitor.so: java/jni/monitor.so
+/usr/lib/&/jni/elf-loader.so: java/&
+/usr/lib/&/jni/networking.so: java/&
+/usr/lib/&/jni/stty.so: java/&
+/usr/lib/&/jni/tracepoint.so: java/&
+/usr/lib/&/jni/power.so: java/&
+/java.so: java/jvm/java_non_isolated.so
+/usr/lib/libosv.so: libosv.so
+/usr/lib/jvm/java/jre/lib/ext/runjava.jar: 
${OSV_BASE}/java/runjava/target/runjava.jar
+/java/cloudius.jar: ${OSV_BASE}/java/cloudius/target/cloudius.jar
diff --git a/scripts/module.py b/scripts/module.py
index aede2cf..19c39b5 100755
--- a/scripts/module.py
+++ b/scripts/module.py
@@ -8,7 +8,7 @@ import argparse
 from functools import reduce
 from osv.modules import api, resolve, filemap
 
-class jvm(api.basic_app):
+class isolated_jvm(api.basic_app):
 multimain_manifest = '/etc/javamains'
 apps = []
 
@@ -33,6 +33,21 @@ class jvm(api.basic_app):
 def add(self, app):
 self.apps.append(app)
 
+def has_any_app(self):
+return self.apps
+
+class non_isolated_jvm(api.basic_app):
+app = None
+
+def get_launcher_args(self):
+return ['java.so'] + self.app.get_jvm_args() + 
self.app.get_multimain_lines()
+
+def add(self, app):
+self.app = app
+
+def has_any_app(self):
+return self.app
+
 def expand(text, variables):
 def resolve(m):
 name = m.group('name')
@@ -117,7 +132,11 @@ def flatten_list(elememnts):
 
 def get_basic_apps(apps):
 basic_apps = []
-_jvm = jvm()
+java = resolve.require('java')
+if hasattr(java,'non_isolated_jvm') and java.non_isolated_jvm:
+_jvm = non_isolated_jvm()
+else:
+_jvm = isolated_jvm()
 
 for app in 

Re: Guideline for MPTCP support in OSv

[GanesH AvacharE]

Hello Benoit,

It's really awesome thing and level of awesomeness is same as MPTCP.

I understood the concept ;but I never made my hand dirty on kernel code.

I am not able to analyse how to start and amount time it will take.

I think I have to add some sort of data structure like circular buffer in
socket system call. Am i right?

Can you guide me on the same line?

Thanks!

On Friday 14 October 2016, Benoît Canet  wrote:

>
>
> Hello Ganesh,
>
> I think OSv implement this: https://lwn.net/Articles/169961/
>
> Nadav's email is n...@scylladb.com
> .
>
> No idea right now.
>
> Best regards
>
> Benoît
>
> On Fri, Oct 14, 2016 at 4:13 PM, GanesH AvacharE <
> ganeshavachare...@gmail.com
> > wrote:
>
>> Hello Benoit,
>>
>> Thanks for your prompt reply.
>>
>> I will wait for Nadav.
>> Can you provide me the email of Van-Jacobson and Nadav the maintainer of
>> OSv?
>>
>> As you mentioned it is big project.
>> Is there any another project which I can take it as final year B.Tech
>> project and which can be finished within 4-5 months ?
>>
>> Thanks!
>>
>>
>> On Friday 14 October 2016, Benoît Canet > > wrote:
>>
>>>
>>> Hi Ganesh,
>>>
>>> This sound like a big project given that the OSv tcp stack is heavyly
>>> optimised. (Van-Jacobson)
>>>
>>> Maybe you should wait for Nadav the OSv maintainer to come back from
>>> vacation in two week and discuss
>>> that with him.
>>>
>>> Best regards
>>>
>>> Benoît
>>>
>>> On Fri, Oct 14, 2016 at 6:01 AM, GanesH AvacharE <
>>> ganeshavachare...@gmail.com> wrote:
>>>
 Hello all,

 I want to develop MPTCP(Multipath TCP) support in OSv as Final year
 B.Tech project ;but I have time limitation of 4-5 months.

 Is it possible to develop MPTCP in OSv within 4-5 months?

 If it is not possible,

 Can you suggest me any feature which can be implemented in OSv within
 4-5 months?

 Thanks!

 Regards,
 Ganesh

 --
 You received this message because you are subscribed to the Google
 Groups "OSv Development" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to osv-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>
>> --
>>
>> *Regards,*
>> *Ganesh*
>>
>>
>

-- 

*Regards,*
*Ganesh*

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble with /dev/urandom

[Benoît Canet]

Thanks I will dig this.

On Fri, Oct 14, 2016 at 4:29 PM, Tomasz Grabiec 
wrote:

>
>
> On Fri, Oct 14, 2016 at 4:14 PM, Benoît Canet  > wrote:
>
>>
>> QEMU on ubuntu 16.04.
>>
>> benoit@alfred:~/osv$ cat /proc/sys/kernel/random/entropy_avail
>>
>> 58
>>
>>
> That's not a lot.  Try watching it during your test.
>
>
>> Some go debugging interleaved.
>>
>> OSv v0.24-199-g733d26f
>> 4 CPUs detected
>> Firmware vendor: SeaBIOS
>> bsd: initializing - done
>> VFS: mounting ramfs at /
>> VFS: mounting devfs at /dev
>> net: initializing - done
>> vga: Add VGA device instance
>> eth0: ethernet address: 52:54:00:12:34:56
>> virtio-blk: Add blk device instances 0 as vblk0, devsize=10737418240
>> random: virtio-rng registered as a source.
>> random: intel drng, rdrand registered as a source.
>>
>>
> Looks like we have both virtio-rng and drng registered as entropy sources.
>
> There is a thread which polls them 10 times a second. See random_kthread()
> from random_harvestq.cc. It feeds entropy into the system via
> random_process_event() from yarrow.cc. Maybe we're not replenishing entropy
> fast enough. Check if and which live sources provide entropy. Try
> increasing the rate.
>
> random:  initialized
>> VFS: unmounting /dev
>> VFS: mounting zfs at /zfs
>> zfs: mounting osv/zfs from device /dev/vblk0.1
>> VFS: mounting devfs at /dev
>> VFS: mounting procfs at /proc
>> program zpool.so returned 1
>> BSD shrinker: event handler list found: 0xa1e6ca80
>> BSD shrinker found: 1
>> BSD shrinker: unlocked, running
>> [I/42 dhcp]: Waiting for IP...
>> [I/252 dhcp]: Server acknowledged IP for interface eth0
>> eth0: 192.168.122.15
>> [I/252 dhcp]: Configuring eth0: ip 192.168.122.15 subnet mask 255.255.255.0 
>> gateway 192.168.122.1 MTU 1500
>> args
>> 0
>> 1.5
>> 4.0
>> 6.0
>> 6.5
>> 6.0
>> 6.2
>> 6.1
>> typ != _STT_FUNC %i
>> true 0 bind != _STB_GLOBAL && bind != _STB_WEAK %i
>> falsesym.st_shndx == _SHN_UNDEF %ifalse6.5
>> 6.0
>> 6.5
>> 7
>> osinit
>> schedinit enter
>> schedinit 1
>> schedinit 2
>> schedinit 3
>> schedinit 4
>> schedinit 5
>> schedinit 6
>> schedinit 7
>> schedinit 8
>> alginit 1
>> alginit 2
>> alginit 3
>> getRandomData 1
>> getRandomData 3
>> getRandomData 4
>> random: blocking on read.
>> random: device unblocked.
>> getRandomData 5
>> getRandomData 6
>> getRandomData 7
>> alginit 4
>> schedinit 9
>> schedinit 10
>> schedinit 11
>> schedinit 12
>> schedinit 13
>> schedinit 14
>> schedinit 15
>> schedinit 16
>> schedinit 17
>> schedinit 18
>> schedinit 19
>> schedinit 21
>> schedinit 25
>> schedinit 27
>> schedinit exit
>> newproc enter
>> newproc exit
>> mstart enter
>> sigaltstack() stubbed
>> mstart enter
>> mstart enter
>> newproc enter
>> blub
>>
>> [backtrace]
>> 0x00202525 
>> 0x0032a97a 
>> 0x00388b98 
>> 0x00387a36 
>> 0x1147e0d2 
>> 0x1147f15b 
>> 0x1147c7db 
>> 0x1147c6cc 
>> 0x114cf232 
>> 0x2055ff3f 
>>
>>
>
>
>
>>
>>
>> On Fri, Oct 14, 2016 at 3:57 PM, Tomasz Grabiec 
>> wrote:
>>
>>>
>>>
>>> On Fri, Oct 14, 2016 at 3:39 PM, Benoît Canet <
>>> ben...@cloudius-systems.com> wrote:
>>>

 Hello list,

 In the process of porting go to OSv I noticed that the Go runtime
 initialization stall half the time waiting in a read for /dev/urandom.

 The message OSv output is "random: blocking on read.".

 It then sometime proceeed to unblock itself a couple dozen of seconds
 later.

 Does it ring a bell ? Is it expected behavior from /dev/urandom ?

>>>
>>> It looks like entropy pool was depleted. Maybe no hardware entropy
>>> sources were detected and we were using only slow interrupt entropy
>>> harvesting.
>>>
>>> Another option is that you are using virtio-rng and entropy was depleted
>>> on your host. Check with `cat /proc/sys/kernel/random/entropy_avail`
>>>
>>> Which hypervisor are you running on?
>>>
>>> Can you show your debug console output?
>>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble with /dev/urandom

[Tomasz Grabiec]

On Fri, Oct 14, 2016 at 4:14 PM, Benoît Canet 
wrote:

>
> QEMU on ubuntu 16.04.
>
> benoit@alfred:~/osv$ cat /proc/sys/kernel/random/entropy_avail
>
> 58
>
>
That's not a lot.  Try watching it during your test.


> Some go debugging interleaved.
>
> OSv v0.24-199-g733d26f
> 4 CPUs detected
> Firmware vendor: SeaBIOS
> bsd: initializing - done
> VFS: mounting ramfs at /
> VFS: mounting devfs at /dev
> net: initializing - done
> vga: Add VGA device instance
> eth0: ethernet address: 52:54:00:12:34:56
> virtio-blk: Add blk device instances 0 as vblk0, devsize=10737418240
> random: virtio-rng registered as a source.
> random: intel drng, rdrand registered as a source.
>
>
Looks like we have both virtio-rng and drng registered as entropy sources.

There is a thread which polls them 10 times a second. See random_kthread()
from random_harvestq.cc. It feeds entropy into the system via
random_process_event() from yarrow.cc. Maybe we're not replenishing entropy
fast enough. Check if and which live sources provide entropy. Try
increasing the rate.

random:  initialized
> VFS: unmounting /dev
> VFS: mounting zfs at /zfs
> zfs: mounting osv/zfs from device /dev/vblk0.1
> VFS: mounting devfs at /dev
> VFS: mounting procfs at /proc
> program zpool.so returned 1
> BSD shrinker: event handler list found: 0xa1e6ca80
> BSD shrinker found: 1
> BSD shrinker: unlocked, running
> [I/42 dhcp]: Waiting for IP...
> [I/252 dhcp]: Server acknowledged IP for interface eth0
> eth0: 192.168.122.15
> [I/252 dhcp]: Configuring eth0: ip 192.168.122.15 subnet mask 255.255.255.0 
> gateway 192.168.122.1 MTU 1500
> args
> 0
> 1.5
> 4.0
> 6.0
> 6.5
> 6.0
> 6.2
> 6.1
> typ != _STT_FUNC %i
> true 0 bind != _STB_GLOBAL && bind != _STB_WEAK %i
> falsesym.st_shndx == _SHN_UNDEF %ifalse6.5
> 6.0
> 6.5
> 7
> osinit
> schedinit enter
> schedinit 1
> schedinit 2
> schedinit 3
> schedinit 4
> schedinit 5
> schedinit 6
> schedinit 7
> schedinit 8
> alginit 1
> alginit 2
> alginit 3
> getRandomData 1
> getRandomData 3
> getRandomData 4
> random: blocking on read.
> random: device unblocked.
> getRandomData 5
> getRandomData 6
> getRandomData 7
> alginit 4
> schedinit 9
> schedinit 10
> schedinit 11
> schedinit 12
> schedinit 13
> schedinit 14
> schedinit 15
> schedinit 16
> schedinit 17
> schedinit 18
> schedinit 19
> schedinit 21
> schedinit 25
> schedinit 27
> schedinit exit
> newproc enter
> newproc exit
> mstart enter
> sigaltstack() stubbed
> mstart enter
> mstart enter
> newproc enter
> blub
>
> [backtrace]
> 0x00202525 
> 0x0032a97a 
> 0x00388b98 
> 0x00387a36 
> 0x1147e0d2 
> 0x1147f15b 
> 0x1147c7db 
> 0x1147c6cc 
> 0x114cf232 
> 0x2055ff3f 
>
>



>
>
> On Fri, Oct 14, 2016 at 3:57 PM, Tomasz Grabiec 
> wrote:
>
>>
>>
>> On Fri, Oct 14, 2016 at 3:39 PM, Benoît Canet <
>> ben...@cloudius-systems.com> wrote:
>>
>>>
>>> Hello list,
>>>
>>> In the process of porting go to OSv I noticed that the Go runtime
>>> initialization stall half the time waiting in a read for /dev/urandom.
>>>
>>> The message OSv output is "random: blocking on read.".
>>>
>>> It then sometime proceeed to unblock itself a couple dozen of seconds
>>> later.
>>>
>>> Does it ring a bell ? Is it expected behavior from /dev/urandom ?
>>>
>>
>> It looks like entropy pool was depleted. Maybe no hardware entropy
>> sources were detected and we were using only slow interrupt entropy
>> harvesting.
>>
>> Another option is that you are using virtio-rng and entropy was depleted
>> on your host. Check with `cat /proc/sys/kernel/random/entropy_avail`
>>
>> Which hypervisor are you running on?
>>
>> Can you show your debug console output?
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble with /dev/urandom

[Benoît Canet]

In the code I don't understand on what the wakeup operate nor on what the
blocking operate.

randomdev_unblock(void)
{
if (!random_context.seeded) {
#ifndef __OSV__
selwakeuppri(_context.rsel, PUSER);
#endif
wakeup(_context);


random_context does not look like a wait condition it look strange.


On Fri, Oct 14, 2016 at 3:57 PM, Tomasz Grabiec 
wrote:

>
>
> On Fri, Oct 14, 2016 at 3:39 PM, Benoît Canet  > wrote:
>
>>
>> Hello list,
>>
>> In the process of porting go to OSv I noticed that the Go runtime
>> initialization stall half the time waiting in a read for /dev/urandom.
>>
>> The message OSv output is "random: blocking on read.".
>>
>> It then sometime proceeed to unblock itself a couple dozen of seconds
>> later.
>>
>> Does it ring a bell ? Is it expected behavior from /dev/urandom ?
>>
>
> It looks like entropy pool was depleted. Maybe no hardware entropy sources
> were detected and we were using only slow interrupt entropy harvesting.
>
> Another option is that you are using virtio-rng and entropy was depleted
> on your host. Check with `cat /proc/sys/kernel/random/entropy_avail`
>
> Which hypervisor are you running on?
>
> Can you show your debug console output?
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Guideline for MPTCP support in OSv

[Benoît Canet]

Hello Ganesh,

I think OSv implement this: https://lwn.net/Articles/169961/

Nadav's email is n...@scylladb.com.

No idea right now.

Best regards

Benoît

On Fri, Oct 14, 2016 at 4:13 PM, GanesH AvacharE <
ganeshavachare...@gmail.com> wrote:

> Hello Benoit,
>
> Thanks for your prompt reply.
>
> I will wait for Nadav.
> Can you provide me the email of Van-Jacobson and Nadav the maintainer of
> OSv?
>
> As you mentioned it is big project.
> Is there any another project which I can take it as final year B.Tech
> project and which can be finished within 4-5 months ?
>
> Thanks!
>
>
> On Friday 14 October 2016, Benoît Canet 
> wrote:
>
>>
>> Hi Ganesh,
>>
>> This sound like a big project given that the OSv tcp stack is heavyly
>> optimised. (Van-Jacobson)
>>
>> Maybe you should wait for Nadav the OSv maintainer to come back from
>> vacation in two week and discuss
>> that with him.
>>
>> Best regards
>>
>> Benoît
>>
>> On Fri, Oct 14, 2016 at 6:01 AM, GanesH AvacharE <
>> ganeshavachare...@gmail.com> wrote:
>>
>>> Hello all,
>>>
>>> I want to develop MPTCP(Multipath TCP) support in OSv as Final year
>>> B.Tech project ;but I have time limitation of 4-5 months.
>>>
>>> Is it possible to develop MPTCP in OSv within 4-5 months?
>>>
>>> If it is not possible,
>>>
>>> Can you suggest me any feature which can be implemented in OSv within
>>> 4-5 months?
>>>
>>> Thanks!
>>>
>>> Regards,
>>> Ganesh
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "OSv Development" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to osv-dev+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>
> --
>
> *Regards,*
> *Ganesh*
>
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Guideline for MPTCP support in OSv

[Benoît Canet]

Hi Ganesh,

This sound like a big project given that the OSv tcp stack is heavyly
optimised. (Van-Jacobson)

Maybe you should wait for Nadav the OSv maintainer to come back from
vacation in two week and discuss
that with him.

Best regards

Benoît

On Fri, Oct 14, 2016 at 6:01 AM, GanesH AvacharE <
ganeshavachare...@gmail.com> wrote:

> Hello all,
>
> I want to develop MPTCP(Multipath TCP) support in OSv as Final year B.Tech
> project ;but I have time limitation of 4-5 months.
>
> Is it possible to develop MPTCP in OSv within 4-5 months?
>
> If it is not possible,
>
> Can you suggest me any feature which can be implemented in OSv within 4-5
> months?
>
> Thanks!
>
> Regards,
> Ganesh
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble with /dev/urandom

[Benoît Canet]

QEMU on ubuntu 16.04.

benoit@alfred:~/osv$ cat /proc/sys/kernel/random/entropy_avail
58

Some go debugging interleaved.

OSv v0.24-199-g733d26f
4 CPUs detected
Firmware vendor: SeaBIOS
bsd: initializing - done
VFS: mounting ramfs at /
VFS: mounting devfs at /dev
net: initializing - done
vga: Add VGA device instance
eth0: ethernet address: 52:54:00:12:34:56
virtio-blk: Add blk device instances 0 as vblk0, devsize=10737418240
random: virtio-rng registered as a source.
random: intel drng, rdrand registered as a source.
random:  initialized
VFS: unmounting /dev
VFS: mounting zfs at /zfs
zfs: mounting osv/zfs from device /dev/vblk0.1
VFS: mounting devfs at /dev
VFS: mounting procfs at /proc
program zpool.so returned 1
BSD shrinker: event handler list found: 0xa1e6ca80
BSD shrinker found: 1
BSD shrinker: unlocked, running
[I/42 dhcp]: Waiting for IP...
[I/252 dhcp]: Server acknowledged IP for interface eth0
eth0: 192.168.122.15
[I/252 dhcp]: Configuring eth0: ip 192.168.122.15 subnet mask
255.255.255.0 gateway 192.168.122.1 MTU 1500
args
0
1.5
4.0
6.0
6.5
6.0
6.2
6.1
typ != _STT_FUNC %i
true 0 bind != _STB_GLOBAL && bind != _STB_WEAK %i
falsesym.st_shndx == _SHN_UNDEF %ifalse6.5
6.0
6.5
7
osinit
schedinit enter
schedinit 1
schedinit 2
schedinit 3
schedinit 4
schedinit 5
schedinit 6
schedinit 7
schedinit 8
alginit 1
alginit 2
alginit 3
getRandomData 1
getRandomData 3
getRandomData 4
random: blocking on read.
random: device unblocked.
getRandomData 5
getRandomData 6
getRandomData 7
alginit 4
schedinit 9
schedinit 10
schedinit 11
schedinit 12
schedinit 13
schedinit 14
schedinit 15
schedinit 16
schedinit 17
schedinit 18
schedinit 19
schedinit 21
schedinit 25
schedinit 27
schedinit exit
newproc enter
newproc exit
mstart enter
sigaltstack() stubbed
mstart enter
mstart enter
newproc enter
blub

[backtrace]
0x00202525 
0x0032a97a 
0x00388b98 
0x00387a36 
0x1147e0d2 
0x1147f15b 
0x1147c7db 
0x1147c6cc 
0x114cf232 
0x2055ff3f 



On Fri, Oct 14, 2016 at 3:57 PM, Tomasz Grabiec 
wrote:

>
>
> On Fri, Oct 14, 2016 at 3:39 PM, Benoît Canet  > wrote:
>
>>
>> Hello list,
>>
>> In the process of porting go to OSv I noticed that the Go runtime
>> initialization stall half the time waiting in a read for /dev/urandom.
>>
>> The message OSv output is "random: blocking on read.".
>>
>> It then sometime proceeed to unblock itself a couple dozen of seconds
>> later.
>>
>> Does it ring a bell ? Is it expected behavior from /dev/urandom ?
>>
>
> It looks like entropy pool was depleted. Maybe no hardware entropy sources
> were detected and we were using only slow interrupt entropy harvesting.
>
> Another option is that you are using virtio-rng and entropy was depleted
> on your host. Check with `cat /proc/sys/kernel/random/entropy_avail`
>
> Which hypervisor are you running on?
>
> Can you show your debug console output?
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Guideline for MPTCP support in OSv

[GanesH AvacharE]

Hello Benoit,

Thanks for your prompt reply.

I will wait for Nadav.
Can you provide me the email of Van-Jacobson and Nadav the maintainer of
OSv?

As you mentioned it is big project.
Is there any another project which I can take it as final year B.Tech
project and which can be finished within 4-5 months ?

Thanks!

On Friday 14 October 2016, Benoît Canet  wrote:

>
> Hi Ganesh,
>
> This sound like a big project given that the OSv tcp stack is heavyly
> optimised. (Van-Jacobson)
>
> Maybe you should wait for Nadav the OSv maintainer to come back from
> vacation in two week and discuss
> that with him.
>
> Best regards
>
> Benoît
>
> On Fri, Oct 14, 2016 at 6:01 AM, GanesH AvacharE <
> ganeshavachare...@gmail.com
> > wrote:
>
>> Hello all,
>>
>> I want to develop MPTCP(Multipath TCP) support in OSv as Final year
>> B.Tech project ;but I have time limitation of 4-5 months.
>>
>> Is it possible to develop MPTCP in OSv within 4-5 months?
>>
>> If it is not possible,
>>
>> Can you suggest me any feature which can be implemented in OSv within 4-5
>> months?
>>
>> Thanks!
>>
>> Regards,
>> Ganesh
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "OSv Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to osv-dev+unsubscr...@googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

*Regards,*
*Ganesh*

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Trouble with /dev/urandom

[Benoît Canet]

Hello list,

In the process of porting go to OSv I noticed that the Go runtime
initialization stall half the time waiting in a read for /dev/urandom.

The message OSv output is "random: blocking on read.".

It then sometime proceeed to unblock itself a couple dozen of seconds later.

Does it ring a bell ? Is it expected behavior from /dev/urandom ?

Best regards

Benoît

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.