AW: [qubes-users] 4.0-rc2 install error

49 views
Skip to first unread message

[799]

unread,
Nov 9, 2017, 12:21:34 AM11/9/17
to ke7...@gmail.com, qubes...@googlegroups.com
-------- Original-Nachricht --------
An 9. Nov. 2017, 01:07, just_testing schrieb:

I'm fairly new to Linux, but I managed to get 3.2 to run and like it. But, I get this message during a 4.0-rc2 install with the same hardware: [Dom0] error ["/usr/bin/qvm-start", "sys-firewall"] failed: stdout:"" stderr: "Start failed:internal error:libxenlight failed to create new domain "sys-firewall" ".

Lenovo T410 with intel centrino 6300 wireless card. So any hope? Maybe fixed in the official 4.0 release? Something I can try? Incompatible hardware?

ANSWER:
I run into the same problem with my Lenovo X230 and invested several hours reinstalling and trying different Grub settings (IOMMU) on boot.
Nothing made it work, thereof I suggest waiting until the final Release of Qubes 4 comes out and don't invest any time here.
If you are new to Qubes be assured that Qubes 3.2 is perfectly fine to be used for daily production use until Q4 has been released as stable version.

In my case I am unsure if running Coreboot adds additional complexity and thereof will try to reinstall Qubes 4 after I've reflashed the original BIOS.

What would be great is a list of devices which are known to be able to run Qubes 4.

[799]

Sergio Matta

unread,
Nov 9, 2017, 8:12:51 PM11/9/17
to qubes-users
I have this problem with my unsupported iommu motherboard. My solution was change my vms to pv in a dom0 terminal with qvm-prefs vm-name (sys-net,sys-firewall,personal,work) virt_mod pv
and insert ip commands in rw-config-rc.local (sorry but this mac has no slash)

In sys-net edit rw-config-rc.local
ip link set vif2.0 up
ip addr add 10.137.0.4/255.255.255.255 dev vif2.0
ip route add 10.137.0.6/255..255.255.255 dev vif2.0

then save it and change it with chmod +x

do the same In sys-firewall too and change the vif# to the one created to connect to work or personal - run ifconfig -a

change the ip. the first is the vm you are editing and the other is the vm will connects thru it.

Mos of the times it runs ok, but if you has no network, you should manually run rc.local with sudo

Reply all
Reply to author
Forward
0 new messages