Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upWith no eth0 in dom0, VM launches fail? #1364
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
Sorry for insufficient research and misleading header. Looking at full journal log, I saw this:
# grep -i netvm -C 3 journalctl.full.log
Oct 29 04:44:10 dom0 systemd[1]: Started Qubes memory management daemon.
Oct 29 04:44:10 dom0 systemd[1]: Starting Qubes memory information reporter...
Oct 29 04:44:10 dom0 systemd[1]: Started Qubes memory information reporter.
Oct 29 04:44:10 dom0 systemd[1]: Starting Qubes NetVM startup...
Oct 29 04:44:10 dom0 systemd[1]: qubes-netvm.service: main process exited, code=exited, status=1/FAILURE
Oct 29 04:44:10 dom0 systemd[1]: Failed to start Qubes NetVM startup.
Oct 29 04:44:10 dom0 systemd[1]: Unit qubes-netvm.service entered failed state.
Oct 29 04:44:10 dom0 systemd[1]: Starting Multi-User System.
Oct 29 04:44:10 dom0 systemd[1]: Reached target Multi-User System.
Oct 29 04:47:14 dom0 systemd[1]: Time has been changed
--
Oct 29 04:51:12 dom0 kernel: loop0: p1 p2
Oct 29 04:51:12 dom0 sudo[2457]: pam_unix(sudo:session): session closed for user root
Oct 29 04:51:13 dom0 su[2431]: pam_unix(su-l:session): session closed for user me
Oct 29 04:51:14 dom0 systemd[1]: Starting Qubes NetVM startup...
Oct 29 04:51:15 dom0 kernel: loop0: p1 p2
Oct 29 04:51:16 dom0 libvirtd[653]: internal error: Active 0000:04:00.1 devices on bus with 0000:04:00.0, not doing bus reset
Oct 29 04:51:16 dom0 libvirtd[653]: internal error: Unable to reset PCI device 0000:04:00.0: internal error: Active 0000:04:00.1 devices on bus with 0000:04:00.0, not doing bus reset
--
Oct 29 04:51:16 dom0 sh[2629]: xid = vm.start(verbose=options.verbose, preparing_dvm=options.preparing_dvm, start_guid=not options.noguid, notify_function=tray_notify_generic if options.tray else None)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/qubes/modules/006QubesProxyVm.py", line 82, in start
Oct 29 04:51:16 dom0 sh[2629]: retcode = super(QubesProxyVm, self).start(**kwargs)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", line 121, in start
Oct 29 04:51:16 dom0 sh[2629]: xid=super(QubesNetVm, self).start(**kwargs)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1733, in start
Oct 29 04:51:16 dom0 sh[2629]: self.netvm.start(verbose = verbose, start_guid = start_guid, notify_function = notify_function)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", line 121, in start
Oct 29 04:51:16 dom0 sh[2629]: xid=super(QubesNetVm, self).start(**kwargs)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1773, in start
Oct 29 04:51:16 dom0 sh[2629]: self.libvirt_domain.createWithFlags(libvirt.VIR_DOMAIN_START_PAUSED)
Oct 29 04:51:16 dom0 sh[2629]: File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1037, in createWithFlags
Oct 29 04:51:16 dom0 sh[2629]: if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
Oct 29 04:51:16 dom0 sh[2629]: libvirt.libvirtError: internal error: Unable to reset PCI device 0000:04:00.0: internal error: Active 0000:04:00.1 devices on bus with 0000:04:00.0, not doing bus reset
Oct 29 04:51:16 dom0 libvirtd[653]: End of file while reading data: Input/output error
Oct 29 04:51:16 dom0 systemd[1]: qubes-netvm.service: main process exited, code=exited, status=1/FAILURE
Oct 29 04:51:16 dom0 systemd[1]: Failed to start Qubes NetVM startup.
Oct 29 04:51:16 dom0 systemd[1]: Unit qubes-netvm.service entered failed state.
Oct 29 04:51:16 dom0 su[2726]: (to me) root on none
Oct 29 04:51:16 dom0 systemd[1]: Starting Session c5 of user me.
Oct 29 04:51:16 dom0 systemd[1]: Started Session c5 of user me.
--
Oct 29 05:11:47 dom0 systemd[1]: Started Qubes memory management daemon.
Oct 29 05:11:47 dom0 systemd[1]: Starting Qubes memory information reporter...
Oct 29 05:11:47 dom0 systemd[1]: Started Qubes memory information reporter.
Oct 29 05:11:47 dom0 systemd[1]: Starting Qubes NetVM startup...
Oct 29 05:11:47 dom0 sh[886]: ERROR: Cannot start Dom0 fake domain!
Oct 29 05:11:48 dom0 systemd[1]: qubes-netvm.service: main process exited, code=exited, status=1/FAILURE
Oct 29 05:11:48 dom0 systemd[1]: Failed to start Qubes NetVM startup.
Oct 29 05:11:48 dom0 systemd[1]: Unit qubes-netvm.service entered failed state.
Oct 29 05:11:48 dom0 systemd[1]: Starting Terminate Plymouth Boot Screen...
Oct 29 05:11:48 dom0 systemd[1]: Received SIGRTMIN+21 from PID 176 (plymouthd).
Oct 29 05:11:48 dom0 systemd[1]: Started Wait for Plymouth Boot Screen to Quit.
krieger-od
commented
Oct 30, 2015
|
Sorry for insufficient research and misleading header. Looking at full journal log, I saw this: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
# lspci
...
04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10)
04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10)
krieger-od
commented
Oct 30, 2015
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 30, 2015
Member
On Thu, Oct 29, 2015 at 06:54:33PM -0700, Andrey Utkin wrote:
04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10) 04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10)
Interesting, it looks like you have one device which is both network
card and card reader. Assign the later one to your netvm (in VM
properties, devices tab) and it should work then.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Thu, Oct 29, 2015 at 06:54:33PM -0700, Andrey Utkin wrote:
Interesting, it looks like you have one device which is both network Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
@marmarek thanks for quick reply!
Could you please give instructions for stupid one, how to do that?
Either in runtime, or from other Linux system, I can do it in any way.
Thanks.
krieger-od
commented
Oct 30, 2015
|
@marmarek thanks for quick reply! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 30, 2015
Member
Open Qubes Manager, select sys-net VM, click VM settings button (in
the toolbar, or context menu). Then go to Devices tab, search for
04:00.1 (your SD card reader) in Available column and move it to
Selected. Accept the change.
Then you should be able to start sys-net (or any other VM) normally.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Open Qubes Manager, select Then you should be able to start Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
I have selected 04:00.1 and 04:00.0 for sys-net VM, but after this, and after a reboot, other VMs still don't start. sys-net VM also doesn't start at boot, this seems to be relevant error in journal:
Oct 30 08:35:52 dom0 systemd[1]: Starting Qubes NetVM startup...
Oct 30 08:35:53 dom0 sh[856]: ERROR: Cannot start Dom0 fake domain!
Oct 30 08:35:53 dom0 systemd[1]: qubes-netvm.service: main process exited, code=exited, status=1/FAILURE
Oct 30 08:35:53 dom0 systemd[1]: Failed to start Qubes NetVM startup.
krieger-od
commented
Oct 30, 2015
|
I have selected 04:00.1 and 04:00.0 for sys-net VM, but after this, and after a reboot, other VMs still don't start. sys-net VM also doesn't start at boot, this seems to be relevant error in journal: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
I guess my netbook doesn't have such features like vt-x and vt-d, but I've read that these features are not required. Maybe I need to edit some config setting to make it work?
krieger-od
commented
Oct 30, 2015
|
I guess my netbook doesn't have such features like vt-x and vt-d, but I've read that these features are not required. Maybe I need to edit some config setting to make it work? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 30, 2015
Member
Try to start sys-net from command line: Open terminal in dom0 and call
qvm-start sys-net. If you'll get an error about missing FLR, PM reset
or bus reset, take a look here:
#1144 (and linked
posts/documentation entries).
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Try to start Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
Thanks, will check. Just in case - my last boot journal, grepped for error|fail, is https://gist.github.com/krieger-od/9d0d6466ad4d1c6dfe12
krieger-od
commented
Oct 30, 2015
|
Thanks, will check. Just in case - my last boot journal, grepped for error|fail, is https://gist.github.com/krieger-od/9d0d6466ad4d1c6dfe12 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
sys-net and sys-firewall get started if i start them manually from VM manager. Others don't start.
krieger-od
commented
Oct 30, 2015
|
sys-net and sys-firewall get started if i start them manually from VM manager. Others don't start. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 30, 2015
Member
What error do you get?
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
What error do you get? Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
Oct 30 08:50:11 dom0 logger[2606]: /etc/xen/scripts/vif-route-qubes: Writing backend/vif/4/0/hotplug-error /etc/xen/scripts/vif-route-qubes failed; error detected. backend/vif/4/0/hotplug-status error to xenstore.
Oct 30 08:50:11 dom0 logger[2608]: /etc/xen/scripts/vif-route-qubes: /etc/xen/scripts/vif-route-qubes failed; error detected.
Oct 30 08:50:11 dom0 logger[2667]: /etc/xen/scripts/block-snapshot: remove XENBUS_PATH=backend/vbd/4/51712
Oct 30 08:50:11 dom0 logger[2673]: /etc/xen/scripts/vif-route-qubes: offline type_if=vif XENBUS_PATH=backend/vif/4/0
Oct 30 08:50:11 dom0 logger[2721]: /etc/xen/scripts/block-snapshot: Device /dev/mapper/snapshot-811:394854-811:396599 still in use - not removing
Oct 30 08:50:11 dom0 logger[2733]: /etc/xen/scripts/vif-route-qubes: ifdown vif4.0 failed
Oct 30 08:50:11 dom0 logger[2739]: /etc/xen/scripts/vif-route-qubes: ip route del 10.137.0.8 dev vif4.0 metric 32748 failed
Oct 30 08:50:11 dom0 logger[2741]: /etc/xen/scripts/vif-route-qubes: iptables -t raw -D PREROUTING -i vif4.0 ! -s 10.137.0.8 -j DROP failed
Oct 30 08:50:11 dom0 logger[2747]: /etc/xen/scripts/vif-route-qubes: ip addr del 10.137.0.1/32 dev vif4.0 failed
Oct 30 08:50:11 dom0 logger[2748]: /etc/xen/scripts/vif-route-qubes: Successful vif-route-qubes offline for vif4.0.
Oct 30 08:50:11 dom0 libvirtd[640]: internal error: libxenlight failed to create new domain 'work'
krieger-od
commented
Oct 30, 2015
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 30, 2015
Member
Why it tries to connect any network to dom0? Did you set that somehow?
In that case, undo that change, set default netvm back to "sys-firewall".
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Why it tries to connect any network to dom0? Did you set that somehow? Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
krieger-od
Oct 30, 2015
I must have set dom0 as default net vm during my random actions :)
Thanks for help very much, now VMs started to work.
krieger-od
commented
Oct 30, 2015
|
I must have set dom0 as default net vm during my random actions :) |
krieger-od commentedOct 30, 2015
Hi, I am excited about Qubes OS, want to try it, but on both laptops available to me, dom0 doesn't recognize ethernet interfacee, so that there's only "lo" loopback interface in output of "ip link".
I have tried both latest Live USB and 3.0 installation.
So when I launch anything in any VM, this shows up in system journal:
According to https://www.qubes-os.org/doc/qubes-net/ , eth0 presence is not required. But then I have no idea what is wrong.
Any help is highly appreciated.
Thanks to QubesOS team for your great work.