On Wed, August 8, 2018 5:53 pm, Andreas Moreiro wrote: > > Qubes dev said in his last post here, that it can not be done in 2014. > https://groups.google.com/d/topic/qubes-users/RFXoZ3zt-PE > > > I tried it for myself, and I can assign the PCI device, and get an eth0 > interface, however I can't assign the virtual interface vif+ to the HVM. > > I tried attaching in Dom0 with: > xl network-attach whonix-gw-clone-1 script=/etc/xen/scripts/vif-route-qubes > ip=... backend=firewallVM and got an error: libx: > error:libx.c:2044device_addrm_aocomplete: unable to add device > > > > Tried to start the firewallvm, with the HVM as its netVM, and got these > errors in the log: > > libxl_device.c:1081:device_backend_callback: unable to add device with > path libxl_device.c:1512:device_attach_devices: unable to add nic devices > libxl_device.c:1081:device_backend_callback: unable to remove device with > path libxl.c:1669:devices_destroy_cb: libxl_devices_destroy failed > > > i used some parts of this tutorial for inspiration: > https://garlicgambit.wordpress.com/2016/04/22/how-to-run-tails-from-a-qub > es-live-cd/ > > Thanks for reading. Any suggestions?
Sys-net is already an HVM. Are you trying to make a custom template? You shouldn't have to manually assign interfaces. Did you check the "provides network" box when creating your custom sys-net? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7fc023164d6dc45068ff1d625c0b0da0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
