On Wed, 2 Mar 2011 15:09:21 -0600, Brandon Gooch wrote:
> On Wed, Mar 2, 2011 at 2:52 PM, Bernhard Froehlich wrote:
>> On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote:
>>> On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote:
On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich
On Thu, 17 Mar 2011 15:01:17 +0100 Bernhard Froehlich wrote:
BF> Thanks to everyone involved! I have committed it now to our blueports
BF> repository and the patch will come together with the next major
BF> VirtualBox update to 4.0.x.
BF> http://svn.bluelife.at/index.cgi/blueports/revision/?
On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote:
> On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote:
>> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich
>> wrote:
>>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote:
On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Fro
On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote:
> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich
> wrote:
>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote:
>>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote:
>>>
>>> BF> Sounds like it's my turn now. Which FreeB
On Wed, Mar 2, 2011 at 2:52 PM, Bernhard Froehlich wrote:
> On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote:
>> On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote:
>>> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich
>>> wrote:
On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj
On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich wrote:
> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote:
>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote:
>>
>> BF> Sounds like it's my turn now. Which FreeBSD version is required to be
>> BF> able to use it?
>>
>> As Bj
Hi,
Since we're going to see VIMAGE (partly) committed into HEAD anytime
now, perhaps it would be a good time to make available some clear
developer documentation on how to cope with VIMAGE in the kernel (at
kernel build time or building a module separately). 3rd party driver
vendors will be mos
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
On Thu, Feb 3, 2011 at 12:18 PM, Bjoern A. Zeeb
wrote:
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
On Thu, Feb 3, 2011 at 11:59 AM, Bjoern A. Zeeb
wrote:
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
I don't understand why you saw a CRE
On 2/3/11 2:59 AM, Bjoern A. Zeeb wrote:
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
I don't understand why you saw a CRED_TO_VNET of 0
I was under the impression that every process/thread in the
system would
be
on vnet0
in a vimage kernel.
This is how my printf looks like:
struct thread
On Thu, Feb 3, 2011 at 12:18 PM, Bjoern A. Zeeb
wrote:
> On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
>
>> On Thu, Feb 3, 2011 at 11:59 AM, Bjoern A. Zeeb
>> wrote:
>>>
>>> On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
>>>
>>> I don't understand why you saw a CRED_TO_VNET of 0
>>> I wa
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
On Thu, Feb 3, 2011 at 11:59 AM, Bjoern A. Zeeb
wrote:
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
I don't understand why you saw a CRED_TO_VNET of 0
I was under the impression that every process/thread in the system
would
be
on vnet0
in a vi
On Thu, Feb 3, 2011 at 11:59 AM, Bjoern A. Zeeb
wrote:
> On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
>
> I don't understand why you saw a CRED_TO_VNET of 0
> I was under the impression that every process/thread in the system
> would
> be
> on vnet0
> in a vimage kernel.
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
I don't understand why you saw a CRED_TO_VNET of 0
I was under the impression that every process/thread in the system would
be
on vnet0
in a vimage kernel.
This is how my printf looks like:
struct thread *td = curthread;
struct vnet *v = TD_TO_VNE
On Thu, Feb 3, 2011 at 10:55 AM, Bjoern A. Zeeb
wrote:
> On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
>
>> On Wed, Feb 2, 2011 at 8:06 PM, Julian Elischer
>> wrote:
>>>
>>> On 2/2/11 10:05 AM, Monthadar Al Jaberi wrote:
I just tried something that seems to work, but please dont hit me
On Thu, 3 Feb 2011, Monthadar Al Jaberi wrote:
On Wed, Feb 2, 2011 at 8:06 PM, Julian Elischer wrote:
On 2/2/11 10:05 AM, Monthadar Al Jaberi wrote:
I just tried something that seems to work, but please dont hit me ^^;;;
in wtap_ioctl I assigned curthread->td_vnet myself to point to a VNET
On Wed, Feb 2, 2011 at 8:06 PM, Julian Elischer wrote:
> On 2/2/11 10:05 AM, Monthadar Al Jaberi wrote:
>>
>> I just tried something that seems to work, but please dont hit me ^^;;;
>>
>> in wtap_ioctl I assigned curthread->td_vnet myself to point to a VNET
>> (saved it when the module first loade
On 2/2/11 10:05 AM, Monthadar Al Jaberi wrote:
I just tried something that seems to work, but please dont hit me ^^;;;
in wtap_ioctl I assigned curthread->td_vnet myself to point to a VNET
(saved it when the module first loaded) (I have not created any jails
yet)... and it works... I didnt put a
I just tried something that seems to work, but please dont hit me ^^;;;
in wtap_ioctl I assigned curthread->td_vnet myself to point to a VNET
(saved it when the module first loaded) (I have not created any jails
yet)... and it works... I didnt put any CURVNET macros...
my assumption is that if at
On 2/2/11 9:12 AM, Bjoern A. Zeeb wrote:
On Wed, 2 Feb 2011, Monthadar Al Jaberi wrote:
Hi,
Thanx makes more sense, but I have noticed something weired if you can
shade some light on.
I added printfs one when the module is first loaded (static int
event_handler(module_t module, int event, voi
On Wed, 2 Feb 2011, Monthadar Al Jaberi wrote:
Hi,
Thanx makes more sense, but I have noticed something weired if you can
shade some light on.
I added printfs one when the module is first loaded (static int
event_handler(module_t module, int event, void *arg)):
curthread=0xc3f95870
curthread->
On 2/2/11 8:42 AM, Julian Elischer wrote:
On 2/2/11 7:06 AM, Monthadar Al Jaberi wrote:
Thanx makes more sense, but I have noticed something weired if you can
shade some light on.
I added printfs one when the module is first loaded (static int
event_handler(module_t module, int event, void *arg
On 2/2/11 7:06 AM, Monthadar Al Jaberi wrote:
Thanx makes more sense, but I have noticed something weired if you can
shade some light on.
I added printfs one when the module is first loaded (static int
event_handler(module_t module, int event, void *arg)):
curthread=0xc3f95870
curthread->td_vnet
Thanx makes more sense, but I have noticed something weired if you can
shade some light on.
I added printfs one when the module is first loaded (static int
event_handler(module_t module, int event, void *arg)):
curthread=0xc3f95870
curthread->td_vnet=0xc3170e00
curthread->td_ucred=0xc3185d00
TD_TO
ok here's how it works..
any place you access a V_xxx variable you need to have the current
vnet set.
so somewhere in your code path to get to that point you have to have done
CURVNET_SET() and after you have finised on the way out you should do
CURVNET_RESTORE().
you can get the vnet from sev
On 2/1/11 11:04 AM, Monthadar Al Jaberi wrote:
On Tue, Feb 1, 2011 at 6:25 PM, Julian Elischer wrote:
On 2/1/11 8:40 AM, Monthadar Al Jaberi wrote:
Hi,
I hope I am on the write place, second try...
I have written a module that loads fake wifi devices (wtap?) and
distributes packets between t
On Tue, Feb 1, 2011 at 6:25 PM, Julian Elischer wrote:
> On 2/1/11 8:40 AM, Monthadar Al Jaberi wrote:
>>
>> Hi,
>>
>> I hope I am on the write place, second try...
>>
>> I have written a module that loads fake wifi devices (wtap?) and
>> distributes packets between them. For now I use route comma
On 2/1/11 8:40 AM, Monthadar Al Jaberi wrote:
Hi,
I hope I am on the write place, second try...
I have written a module that loads fake wifi devices (wtap?) and
distributes packets between them. For now I use route command to route
packets between them from upper layers (TCP,...).
I want to tak
Hi,
I hope I am on the write place, second try...
I have written a module that loads fake wifi devices (wtap?) and
distributes packets between them. For now I use route command to route
packets between them from upper layers (TCP,...).
I want to take it to next step and create jails with VNET. I
On Thu, 27 Jan 2011 00:19:57 +0100 Bernhard Froehlich wrote:
BF> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff
BF> I've integrated it a bit better into the VirtualBox build system, added
BF> the ports stuff and updated the patch for VirtualBox 4.0.2.
Thanks!
BF> It
On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote:
> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote:
>
> BF> Sounds like it's my turn now. Which FreeBSD version is required to be
> BF> able to use it?
>
> As Bjoern noted it is for __FreeBSD_version >= 800500.
>
> BF> Is VIM
On Wed, 26 Jan 2011, Mikolaj Golub wrote:
On Wed, 26 Jan 2011 14:18:03 + (UTC) Bjoern A. Zeeb wrote:
BAZ> On Wed, 26 Jan 2011, Mikolaj Golub wrote:
>>
>> On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote:
>>
>> BAZ> I think you should wrap the CURVNET changes in __FreeBSD_vers
On Wed, 26 Jan 2011 14:18:03 + (UTC) Bjoern A. Zeeb wrote:
BAZ> On Wed, 26 Jan 2011, Mikolaj Golub wrote:
>>
>> On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote:
>>
>> BAZ> I think you should wrap the CURVNET changes in __FreeBSD_version
>> BAZ> checks so that the port, sh
On Wed, 26 Jan 2011, Brandon Gooch wrote:
On Wed, Jan 26, 2011 at 8:25 AM, Mikolaj Golub wrote:
[SNIP]
I suppose we should have an option in ports, something:
.if ${OSVERSION} < 800500
OPTIONS+= VIMAGE "Build for VIMAGE kernel" off
.endif
and if it is on set VIMAGE make environment
On Wed, Jan 26, 2011 at 8:25 AM, Mikolaj Golub wrote:
[SNIP]
> I suppose we should have an option in ports, something:
>
> .if ${OSVERSION} < 800500
> OPTIONS+= VIMAGE "Build for VIMAGE kernel" off
> .endif
>
> and if it is on set VIMAGE make environment variable. Or may be you have
> a b
On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote:
BF> Sounds like it's my turn now. Which FreeBSD version is required to be
BF> able to use it?
As Bjoern noted it is for __FreeBSD_version >= 800500.
BF> Is VIMAGE enabled per default and what happens if VIMAGE is disabled -
BF> do
On Wed, 26 Jan 2011, Mikolaj Golub wrote:
On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote:
BAZ> I think you should wrap the CURVNET changes in __FreeBSD_version
BAZ> checks so that the port, should it run elsewhere or on older FreeBSDs
BAZ> (if it runs there) not trouble people h
On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote:
BAZ> I think you should wrap the CURVNET changes in __FreeBSD_version
BAZ> checks so that the port, should it run elsewhere or on older FreeBSDs
BAZ> (if it runs there) not trouble people having to patch it away.
BAZ> #if defined
On Tue, 25 Jan 2011 18:13:43 -0800, Julian Elischer wrote:
> On 1/25/11 1:06 PM, Mikolaj Golub wrote:
>> On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
>>
>> JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>>
>> >> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem"
>> fu
On Tue, 25 Jan 2011, Mikolaj Golub wrote:
On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem" functions
>> CURVNET_SET_QUIET(vnet0) macro, which sets td->td_vnet to default vn
On 01/26/2011 03:13 AM, Julian Elischer wrote:
On 1/25/11 1:06 PM, Mikolaj Golub wrote:
On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem"
functions
>> CURVNET_SET_QUIET(vnet0
On 1/25/11 1:06 PM, Mikolaj Golub wrote:
On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem" functions
>> CURVNET_SET_QUIET(vnet0) macro, which sets td->td_vnet to defa
On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem" functions
>> CURVNET_SET_QUIET(vnet0) macro, which sets td->td_vnet to default vnet (see
>> the
>> attached patch). This
On 1/23/11 6:33 AM, Mikolaj Golub wrote:
Hi,
Sorry for cross posting, but this question concerns both VirtualBox and VIMAGE
:-).
I would like to be able to run VirtualBox on my desktop, with kernel compilled
with VIMAGE, so I would use light vnet jails for FreeBSD VMs and VirtualBox
for other
Hi,
Sorry for cross posting, but this question concerns both VirtualBox and VIMAGE
:-).
I would like to be able to run VirtualBox on my desktop, with kernel compilled
with VIMAGE, so I would use light vnet jails for FreeBSD VMs and VirtualBox
for other OSes.
Currently the system will crash if y
44 matches
Mail list logo
