Hi,
I've been running Qubes for a few years now and I'd like to give
Spectrum a try, as I've been having some hardware and performance
problems with Qubes. Is there some up-to-date guide I can follow? I
found https://alyssa.is/using-virtio-wl/#demo and was able to see the
weston terminal. I also tried updating to the latest commit and was
able to get a nested wayfire window with:
nix-build . -A spectrumPackages && ./result-3/bin/spectrum-vm
(I'm fairly new to Nix, so not sure if this is the right way to do things)
I managed to change the keyboard layout, mount a tmpfs for home, and
increase the memory enough to start firefox, but I haven't managed to
get much further. Things I tried so far:
- I tried replacing wayfire with weston-terminal, to avoid the nested
session. But sommelier segfaults when I do that.
- I tried adding `--shared-dir /tmp/ff:ff:type=9p` to share a host
directory. Then `mount -t 9p -o trans=virtio,version=9p2000.L ff /tmp`
in the VM seemed to work, but `ls /tmp` crashed the VM.
- I tried using `-d /dev/mapper/disk` to share an LVM partition, but
`mount -t ext4 /dev/vdb /tmp` refused to mount it.
- I tried enabling networking with `--host_ip 10.0.0.1`, etc, but it
said it couldn't create a tap device. I guess it needs more
privileges.
Ideally, I'd like to run a VM with each of my old Qubes filesystems,
to get back to where I was with my Qubes setup, before investigating
new spectrum stuff (e.g. one app per VM). Do you have any advice on
this? I see these lists are a bit quiet - I hope someone is still
working on this because it sounds great :-)
Thanks!
--
talex5 (GitHub/Twitter) http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D 6A51 7513 3C8F 94F6 E0CC
Hi all,
Good news is that the work on aarch64 support has progressed to the point where
the Spectrum host can be built natively and run on aarch64 HW.
It's still a bunch of patches in various stages of WIP or review to
spectrum or further
up the stream.
In short, to "nixpkgs-spectrum":
0001-Allow-static-building-of-dtc.patch
0002-Workaround-ld-script-segmentation-fault.patch /* may be not needed */
0003-Add-imx8-specific-kernel.patch
and to "spectrum":
0001-Add-imx8-kernel.patch
Should anyone want to reproduce, please let me know and I'll try to
find a solution
to share them. Probably worth waiting for cross-compilation support unless you
have powerful aarch64 at your disposal.
In the meanwhile, we try to establish a mechanism to collaborate in branches of
required upstream repos. It's fairly impractical to fork
"nixpkgs-spectrum"-repo due to
its' size, over 2GB,
Which takes me to the discussion point - what's the workflow proposal
on multiple people
working on the same functionality in the same branch? If I'm not
mistaken the email workflow
creates a new branch for each author? Then someone would have to
cherry-pick them to the
same branch to integrate them in dev time hydra builds.
Best,
-Ville
