Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I have configured an HVM guest as so: name = "visorflow-guest-linux" memory = 2048 vcpus = 1 builder = "hvm" altp2mhvm = 1 vif = [ "model=e1000,script=vif-route,ip=10.0.0.2/32,gatewaydev=wlp3s0" ] disk = [ "tap2:tapdisk:aio:/path/disk.img,xvda,w" ] serial = "pty" sdl = 1 It seems in the case of a HVM guest, the vif-route script does not function properly, and as a result "xl create visorflow-guest-linux" prints the error message below. Version-Release number of selected component (if applicable): xen-runtime-4.7.1-6.fc25.x86_64 xen-licenses-4.7.1-6.fc25.x86_64 xen-libs-4.7.1-6.fc25.x86_64 xen-4.7.1-6.fc25.x86_64 xen-hypervisor-4.7.1-6.fc25.x86_64 xen-devel-4.7.1-6.fc25.x86_64 How reproducible: Every time Steps to Reproduce: 1. Configure a Xen guest as noted above 2. Load the guest using "xl create ..." Actual results: Parsing config from visorflow-guest-linux.cfg libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route add [8241] exited with error status 1 libxl: error: libxl_device.c:1219:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected. libxl: error: libxl_create.c:1462:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route remove [8400] exited with error status 1 libxl: error: libxl_device.c:1219:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected. libxl: error: libxl.c:1583:libxl__destroy_domid: non-existant domain 13 libxl: error: libxl.c:1542:domain_destroy_callback: unable to destroy guest with domid 13 libxl: error: libxl.c:1471:domain_destroy_cb: destruction of domain 13 failed Expected results: The guest should load with networking configured appropriately. Additional info: I added some echos to the vif-route script, and I found: The script runs twice, once with: command=online dev=vif15.0 and once with: command=add dev=vif15.0-emu with the TAP device, vif15.0-emu, the command is "add" and not "online" as noted. This means that neither the "online" nor the "offline" block will fire in vif-route's case statement. Thus "ipcmd" does not get set, and the "ip route" command fails. The following kludge seems to fix vif-route. Replace: if [ "${ip}" ] ; then with: if [ "${ip}" -a $command = online ] ; then It is not yet clear to me how the vif15.0-emu device should be configured.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.