Disabling qubes-netvm
Matthias Brumm
I try to get QubesOS running on a MacBook Pro. I am referring to this https://www.qubes-os.org/doc/macbook-troubleshooting/#macbook-pro-retina-15-inch-mid-2015-macbookpro-115 number 7. I use refind as a bootloader and do not have a visible grub to pass options to.
How can I disable netvm from starting?
Matthias
Matthias Brumm
> I try to get QubesOS running on a MacBook Pro. I am referring to this https://www.qubes-os.org/doc/macbook-troubleshooting/#macbook-pro-retina-15-inch-mid-2015-macbookpro-115 number 7.
I was able to start the rescue system with this: https://www.qubes-os.org/doc/uefi-troubleshooting/#accessing-installer-rescue-mode-on-uefi
But there is a tmux session with some panes. How to use the rescue system? How to mount the partition with Qubes OS on it?
Matthias
awokd
procedures/documentation will apply. Check out
https://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/s1-rescuemode-boot.html.
I can't verify, because UEFI is too broken on my systems.
Matthias Brumm
> The Qubes installer is a modified version of Fedora's, so often the same
> procedures/documentation will apply. Check out
> https://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/s1-rescuemode-boot.html.
> I can't verify, because UEFI is too broken on my systems.
OK, I have managed to get to the rescue system, but there seems not to be a qubes-netvm to disable or the disabling of machines has changed.
The system boots up, shows a black screen with mouse cursor and is rebooting a short while after.
Matthias
awokd
somewhere of /var/lib/qubes/qubes.xml and edit it. If sys-net is
crashing, set its autostart to no. It might still attempt to start due
to dependencies, but you can then also remove attached devices.
Matthias Brumm
Could you please show me the relevant part? I do not find this. I am beginning to suspect, that this VM was not created, but then there has to be some other reason of the crash.
Matthias
awokd
name="name">sys-net</property>.
Another way to work around sys-net install issues like that is to
temporarily disable network devices in UEFI config, or physically remove.
Matthias Brumm
> Look for the section of XML that contains <property
> name="name">sys-net</property>.
>
> Another way to work around sys-net install issues like that is to
> temporarily disable network devices in UEFI config, or physically remove.
This is my workplace, so these options are not possible.
Matthias
awokd
>> Look for the section of XML that contains <property
>> name="name">sys-net</property>.
>>
> Thank you for your help. I disabled all three autostart vms to hopefully get the system to start, but no luck. I think I surrender for now to get this installed on a Macbook.
assigned to sys-net in that same section of XML. Look for lines like
<device backend-domain="dom0" id="09_00.0"/> and delete them. If
that still doesn't let you boot Qubes, it's some other issue besides
sys-net.
>> Another way to work around sys-net install issues like that is to
>> temporarily disable network devices in UEFI config, or physically remove.
>
> This is my workplace, so these options are not possible.
Matthias Brumm
> Matthias Brumm:
> > Am Dienstag, 2. Juli 2019 16:14:52 UTC+2 schrieb awokd:
> >> Look for the section of XML that contains <property
> >> name="name">sys-net</property>.
> >>
> > Thank you for your help. I disabled all three autostart vms to hopefully get the system to start, but no luck. I think I surrender for now to get this installed on a Macbook.
>
> Didn't think of it earlier, but you could also remove the devices
> assigned to sys-net in that same section of XML. Look for lines like
> <device backend-domain="dom0" id="09_00.0"/> and delete them. If
> that still doesn't let you boot Qubes, it's some other issue besides
> sys-net.
>
When I am done, I try to make a short section for the macbook troubleshooting information.
Matthias
Matthias Brumm
> That was a very good idea. After editing the xml file I got to the stage 2 and I think Qubes had to do some last steps. Then Qubes OS booted. When I have the time, I can now look into enabling network etc.
>
> When I am done, I try to make a short section for the macbook troubleshooting information.
I don't know, if Qubes is possible on a modern Macbook. I have tried several ways to attach the Broadcom wifi to sys-net, but either it is not shown in the machine or the system freezes.
And this struggles before trying to get the keyboard and touchpad running (still using USB keyboard and mouse.
Apple seems to do a great work in locking their system up.
Perhaps I can get a new laptop for my work in some months or so.
Matthias
awokd
unfriendliness. What's the model #? It's possible someone else figured
out how to get it working, or I suppose it's possible there's no fix.
I was going to suggest using Ethernet, but then I remembered you said "a
modern Macbook"...
Matthias Brumm
> That's too bad; Broadcom wifi adapters are notorious for Linux
> unfriendliness. What's the model #? It's possible someone else figured
> out how to get it working, or I suppose it's possible there's no fix.
> I was going to suggest using Ethernet, but then I remembered you said "a
> modern Macbook"...
Yes. Actualy I just hope to get compiz working as I am dependant onb a good working screen zoom as on OSX. Then I am sure to use it as a daily driver, when getting some Lenovo gear.
Matthias