> >Not sure how you ended up assigning that IP (i do not look at 
> >screenshots). But i guess your network setup is that you have one 
> >physical NIC which still belongs to the root cell. And you have a 
> >virtual network with two jailhouse shmem network adapters going between 
> >your non-root and root-cell. 
>
I assigned IP through command line. I have one physical NIC, yes you are 
right, but the I do not know how to access the virtual network. 

>
> >An i further guess that the non-root cell got its IP via its kernel 
> >cmdline. To hook that up to the root-cell, the root-cell will need an 
> >IP from the same subnet. And that additional subnet should not overlap 
> >with the subnet your root-cell is already using on the physical NIC. 

 
For instance, if the root cell has an IP of 192.168.0.100, I give the IP to 
the non-root cell of 192.168.0.101 

> >That way you should eventually be able to "ping" and "ssh" between root 
> >and non-root. What you might want to do later would be to create a 
> >bridge on the root-cell, where you would attach the physical NIC and 
> >the jailhouse-NIC ... that would connect you non-root cell to your LAN 
> >and allow for DHCP and external communication. 
>

> >Nothing jailhouse specific really, simple Linux networking stuff. The 
> >only thing really needed is the jailhouse NIC driver on the root cell, 
> >i assume a new NIC appeared after your "jailhouse enable" ... 
>
> I think I am missing something in this part, the command "ifconfig" 
returns the same NIC drivers [eth0-wlan0-lo] before and after jailhouse 
enable. May I ask where can I find information about Jailhouse NIC and how 
to embed it in the root cell. 

Best regards, 
Moustafa Noufale

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/8dce9427-624f-4d62-b803-3ef00552e283n%40googlegroups.com.

Reply via email to