Hi Jan,
When booting inmate Linux, I have ivshmem-net configured. In root cell it shows
as eth2.
I monitor system network, and see eth2 is assigned a random address.
[ADDR]4: eth2 inet 169.254.232.89/16 brd 169.254.255.255 scope global eth2
valid_lft forever preferred_lft forever
[ROUTE]local 169.254.232.89 dev eth2 table local proto kernel scope host src
169.254.232.89
[ROUTE]broadcast 169.254.255.255 dev eth2 table local proto kernel scope link
src 169.254.232.89
[ROUTE]169.254.0.0/16 dev eth2 proto kernel scope link src 169.254.232.89
[ROUTE]broadcast 169.254.0.0 dev eth2 table local proto kernel scope link src
169.254.232.89
[ROUTE]default dev eth2 scope link
And also in route table, it added two entries going through eth2, I not
understand why
it will add one entry that default use eth2 with gateway 0.0.0.0
#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 eth2
default _gateway 0.0.0.0 UG 0 0 0 eth1
10.193.102.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
It added the eth2 route table and will break nfsroot if we using 10.193.108.x
for nfsroot server,
because it will match the 1st entry.
This is not jailhouse hypervisor issue, I just not sure the eth2 behavior, it
is systemd does that
route change or we need look into ivshmem-net to avoid update route table when
creating
eth2?
Thanks,
Peng.
--
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/DB6PR0402MB2760C0BAFC4117D229FDD5E888BB0%40DB6PR0402MB2760.eurprd04.prod.outlook.com.
