Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem with networking on Xen #124

Open
bchalios opened this issue Aug 9, 2018 · 1 comment
Open

problem with networking on Xen #124

bchalios opened this issue Aug 9, 2018 · 1 comment

Comments

@bchalios
Copy link

bchalios commented Aug 9, 2018

I am trying to run the apache server from rumprun-packages.

I have built it and baked it according to the README but when trying to launch the unikernel on Xen I get the following error:

root@local:/home/bchalios/rumprun-packages/apache2# rumprun xen -i -I xen0,xenif -W xen0,inet,static,10.0.120.120/24 -b images/data.iso,/data bin/httpd_xen_pv.bin -k start -DONE_PROCESS

!!!
!!! NOTE: rumprun is experimental. syntax may change in the future
!!!

Parsing config from /tmp/rumprun.ONbwkksb/xr.conf
unrecognized argument `xenif'
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge online [30018] exited with error status 1
libxl: error: libxl_device.c:1286:device_hotplug_child_death_cb: script: Could not find bridge device xenbr0
libxl: error: libxl_create.c:1519:domcreate_attach_devices: Domain 138:unable to add vif devices
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge offline [30080] exited with error status 1
libxl: error: libxl_device.c:1286:device_hotplug_child_death_cb: script: Could not find bridge device xenbr0
libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 138:Non-existant domain
libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 138:Unable to destroy guest
libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 138:Destruction of domain failed
rumprun: error: xl create failed

@speas038
Copy link

speas038 commented Sep 18, 2018

This seems to be caused by you not having your xen bridge device enabled, your /etc/network/interfaces file should look something like this for xen guests to have networking enabled

iface eth0 inet manual

iface xenbr0 inet dhcp
	bridge_ports eth0

reference: https://wiki.xenproject.org/wiki/Network_Configuration_Examples_(Xen_4.1%2B)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants