--00221597476e64a939049e70c40d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
The previous mail contains the intel N/W adapters and I did not find the
paravirtualized adapter and the MAC address.
So, I thought this may be the problem.
2011/3/14 St=E9phanie Ouillon <stephanie@minet.net>
> Well, I had already checked the settings.
> I'll try the latest version of VirtualBox 4.0.4, hoping that the bug for
> VirtualBox 4.0.2 has been fixed and that the vm will boot.
>
> Le 14/03/11 02:58, Pratyush Kshirsagar a =E9crit :
>
> I think this are the N/W adapters that your VMM / Hypervisor has or
> attached to.
> But if you are using Virtual Box you need to Click the Advanced tab in N=
/W
> settings and select the adapter type to
> Paravirtualized Network (virtio-net)
> I am using bridge networking with this N/W adapter.
> Please check the settings and try to run it.
> Hope it solves the problem.
>
> - Pratyush.
>
> 2011/3/13 St=E9phanie Ouillon <stephanie@minet.net>
>
>> Hello,
>>
>> I run 10 days ago the code you sent to me in your mail, but I had to rea=
d
>> more about virtio driver to be able to understand a bit more the
>> architecture of the code.
>>
>> Well, I used a DragonFly 2.9-development on Virtualbox (not the latest
>> version of VBox because there is a reported bug for DragonFly BSD machin=
es,
>> so I use the 3.12) and I used a PCnet-PCI II emulated network card (NAT
>> mode).
>>
>> I build the code to load the modules and I did what you mentionned :
>>
>> #kldload -v ./virtio.ko
>> virtio_probe 51966virtio_probe 9237virtio_probe 28947Loaded ./virtio.ko,
>> id=3D5
>>
>> #kldload -v ./virtio_net.ko
>> Loaded ./virtio-net.ko, id=3D6
>>
>> #dmesg
>> virtio_probe 51966virtio_probe 9237virtio_probe 28947
>>
>>
>> I checked the numbers, they match the following devices :
>> 51966 : Virtual Guest Service
>> 9237 : "0x8086","0x2415","Intel Corporation","Intel 82801DBM SM/BUS
>> Controller 24C3","Aureal (AD1881 SOUNDMAX) Placa M=E3e Asaki P3-141"
>> 28947: "0x8086","0x7113","Intel Corporation","82371AB/EB/MB","PIIX4/4E/4=
M
>> Power Management Controller"
>>
>>
>> However, I see no message from the virtio_attach() fonction nor
>> virtio_net_probe() or virtio_net_attach() and I don't understand why ( i=
f it
>> is normal, or not ? ).
>> I tried to launch Virtualbox with virtio-net for the network configurati=
on
>> to see what would happen, if I could go further and have more informatio=
n
>> but I had an error message at the very beginning :
>>
>> Configuration error: Failed to get the "MAC" value
>> (VERR_CFGM_VALUE_NOT_FOUND).
>> Unknown error creating VM (VERR_CFGM_VALUE_NOT_FOUND).
>>
>> So the vm couldn't be launched, even when configured with no network
>> connection.
>>
>>
>>
>> St=E9phanie Ouillon
>>
>>
>> Le 28/02/11 02:34, Pratyush Kshirsagar a =E9crit :
>>
>> Yes, you are right but I did some work porting virtio network driver fro=
m
>> NetBSD before we moved forward to port it from FreeBSD.
>> Attached is the partly done code.
>> The other basic calls needed for block and network drivers are kept sam=
e
>> by Tim and me so that we don't do lot of cleaning and book keeping stuff=
..
>>
>> The working code is in "net" directory and not the nbsd_code.
>> you need to make the outer dir and then the do make in net.
>> use kldload -v ./virtio.ko followed by kldload -v ./virtio_net.ko
>> Thus when you use dmesg it will show the messages during the netword
>> device probe and attach() with the network device number/id.
>>
>> You can mail me for further information.
>>
>> - Pratyush Kshirsagar.
>>
>> 2011/2/27 St=E9phanie Ouillon <stephanie@minet.net>
>>
>>> Hello,
>>>
>>> I've read the posts on the DragonFly BSD Digest site about virtio, but =
I
>>> have some questions about it.
>>>
>>> A virtual network driver was ported from NetBSD, using some FreeBSD cod=
e
>>> that wasn't supposed to be public under a BSD license. So for the momen=
t,
>>> the code that is published on gitorious (
>>> http://gitorious.org/virtio-drivers/virtio-drivers/trees/master) can't
>>> be used at all ? Can somebody tell me more about that ?
>>> Thanks !
>>>
>>>
>>> Regards,
>>>
>>> St=E9phanie
>>>
>>
>>
>>
>
>
--00221597476e64a939049e70c40d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
The previous mail contains the intel N/W adapters and I did not find the pa=
ravirtualized adapter and the MAC address.<br>So, I thought this may be the=
problem.<br><br><div class=3D"gmail_quote">2011/3/14 St=E9phanie Ouillon <=
span dir=3D"ltr"><<a href=3D"mailto:stephanie@minet.net">stephanie@minet=
..net</a>></span><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
=20
=20
=20
<div bgcolor=3D"#ffffff" text=3D"#000000">
Well, I had already checked the settings. <br>
I'll try the latest version of VirtualBox 4.0.4, hoping that the bu=
g
for VirtualBox 4.0.2 has been fixed and that the vm will boot. <br>
<br>
Le 14/03/11 02:58, Pratyush Kshirsagar a =E9crit=A0:
<blockquote type=3D"cite">I think this are the N/W adapters that your V=
MM /
Hypervisor has or attached to.
<div>But if you are using Virtual Box =A0you need to Click the
Advanced tab in N/W settings and select the adapter type to=A0</div=
>
<div>Paravirtualized Network (virtio-net)</div>
<div>I am using bridge networking with this N/W adapter.</div>
<div>Please check the settings and try to run it.</div>
<div>Hope it solves the problem.</div>
<div><br>
</div>
<div>- Pratyush.<br>
<br>
<div class=3D"gmail_quote"><div class=3D"im">2011/3/13 St=E9phanie =
Ouillon <span dir=3D"ltr"><<a href=3D"mailto:stephanie@minet.net" target=
=3D"_blank">stephanie@minet.net</a>></span><br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt =
0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor=3D"#ffffff" text=3D"#000000"> Hello, <br>
<br>
I run 10 days ago the code you sent to me in your mail,
but I had to read more about virtio driver to be able to
understand a bit more the architecture of the code.<br>
<br>
Well, I used a DragonFly 2.9-development on Virtualbox
(not the latest version of VBox because there is a
reported bug for DragonFly BSD machines, so I use the
3.12) and I used a PCnet-PCI II emulated network card (NAT
mode).<br>
<br>
I build the code to load the modules and I did what you
mentionned :<br>
<br>
<font face=3D"Courier New, Courier, monospace">#kldload -v
./virtio.ko<br>
virtio_probe 51966virtio_probe 9237virtio_probe
28947Loaded ./virtio.ko, id=3D5<br>
<br>
#kldload -v ./virtio_net.ko<br>
Loaded ./virtio-net.ko, id=3D6</font><br>
<font face=3D"Courier New, Courier, monospace"><br>
#dmesg <br>
virtio_probe 51966virtio_probe 9237virtio_probe 28947</font=
><br>
<br>
<br>
I checked the numbers, they match the following devices :
<br>
51966 : Virtual Guest Service<br>
9237 : "0x8086","0x2415","Intel Corp=
oration","Intel
82801DBM SM/BUS Controller 24C3","Aureal (AD1881 SO=
UNDMAX)
Placa M=E3e Asaki P3-141"<br>
28947: "0x8086","0x7113","Intel
Corporation","82371AB/EB/MB","PIIX4/4E/4M=
Power Management
Controller"<br>
<br>
<br>
However, I see no message from the virtio_attach()
fonction nor virtio_net_probe() or virtio_net_attach() and
I don't understand why ( if it is normal, or not ? ).<br>
I tried to launch Virtualbox with virtio-net for the
network configuration to see what would happen, if I could
go further and have more information but I had an error
message at the very beginning :<br>
<br>
<font face=3D"Times New Roman, Times, serif">Configuration
error: Failed to get the "MAC" value
(VERR_CFGM_VALUE_NOT_FOUND).<br>
Unknown error creating VM (VERR_CFGM_VALUE_NOT_FOUND).</fon=
t><br>
<br>
So the vm couldn't be launched, even when configured with
no network connection.<br>
<br>
<br>
<br>
St=E9phanie Ouillon<br>
<br>
<br>
Le 28/02/11 02:34, Pratyush Kshirsagar a =E9crit=A0:
<div><div></div><div class=3D"h5"><blockquote type=3D"cite">Y=
es, you are right but I did some
work porting virtio network driver from NetBSD before we
moved forward to port it from FreeBSD.
<div>Attached is the partly done code.</div>
<div> The other basic calls needed for block and network
drivers are kept same by Tim and me so that we don't
do lot of cleaning and book keeping stuff.<br>
</div>
<div><br>
</div>
<div>The working code is in "net" directory and n=
ot the
nbsd_code.</div>
<div>you need to make the outer dir and then the do make
in net.</div>
<div>use kldload -v ./virtio.ko followed by kldload -v
./virtio_net.ko=A0</div>
<div>Thus when you use dmesg it will show the messages
during the netword device probe and attach() with the
network device number/id.</div>
<div><br>
</div>
<div>You can mail me for further information.</div>
<div><br>
</div>
<div>- Pratyush Kshirsagar.</div>
<div><br>
<div class=3D"gmail_quote">2011/2/27 St=E9phanie Ouillon =
<span dir=3D"ltr"><<a href=3D"mailto:stephanie@minet.net" target=3D"_bla=
nk">stephanie@minet.net</a>></span><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt =
0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex=
;"> Hello,<br>
<br>
I've read the posts on the DragonFly BSD Digest
site about virtio, but I have some questions about
it.<br>
<br>
A virtual network driver was ported from NetBSD,
using some FreeBSD code that wasn't supposed to b=
e
public under a BSD license. So for the moment, the
code that is published on gitorious (<a href=3D"http:=
//gitorious.org/virtio-drivers/virtio-drivers/trees/master" target=3D"_blan=
k">http://gitorious.org/virtio-drivers/virtio-drivers/trees/master</a>)
can't be used at all ? Can somebody tell me more
about that ?<br>
Thanks !<br>
<br>
<br>
Regards,<br>
<font color=3D"#888888"> <br>
St=E9phanie<br>
</font></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</blockquote></div><br>
--00221597476e64a939049e70c40d--