Install Qubes in Odroid H2,
111 views
Skip to first unread message
elo...@gmail.com
Mar 28, 2020, 5:40:03 PM3/28/20
to qubes-users
I install Ubuntu mate 18.04.4LTS Bionic in x86_64bits, in mate 1.20.1 in Personal computer Odroid H2, my computer have a CPU J4105 Intel celeron. I install the libraries for the virtualization of the QEMU virtual machine manager, creating a KVM, QEMU supports Xen type hypervisors.
The creation of the virtual machine has the following configuration.
Considering that my personal computer has 8 GB of RAM and 4 TB of disk space, I have allocated 2 CPUs, 4 GB of ram and 100 gigabytes of storage space, the iso image that I downloaded from the official website is Qubes 4.0.3 x86_64 bits.iso, is loaded from the hard disk to start virtualization. The virtual network interface is assigned to the device model of the network card, but I can also choose, virtio.
The installation has no failures, except the warning that my hardware does not support supports IOMMU / VT-d / AMD-Vi.
When I start Qubes, the last line fails.
Failed to start Qubes VM sys-net. But the system loads equally, I start Qubes manager.
When I try to start whonix -ws, the warning becomes apparent, / usr / bin / qvm-start, sys-firewall failed: stdout:
stderr: failed to start and HVM qube with PCI devices assigned-hardware does not support IOMMU / VT-d / AMD-Vi
I try to configure the devices, adding network cards, but I get the same results. In the Bios I have the VT-d display enabled, I don't know what else to do, in which I have the PVH mode enabled by default, and I have also tried the HVM mode.
and tried to update sys-whonix, in terminal, and it shows me the same Qube HVM boot failure message.
Other collateral errors are, Start failed: invalid argument: could not find capabilities for arch = x86_64, see /var/log/libvirt/libxl/libx-driver.log for details.
The sys-firewall qube is network connected to sys-net, which does not support firewall.
You may edit the sys-firewall qube firewall rules, but these will not take any effect until you connect it to a working firewall qube.
Other comments like PVH, mode is hidden since it doesn't support PCI passthrough.
I just need to know how to make the HVM mode work, and know how I can transfer files from my USB, since the recognition of USB devices also fails, everything else works perfectly. I have noticed that my Qubes is something different, I give an example.
In the following video https://www.youtube.com/watch?v=yrDo0q9qSXs&t=937s, at minute 37:54, in the option Domain: anon-whonix many options appear, while I only see one. Only Qube settings.
Thanks, and for the culture, I must not stop trying.
The creation of the virtual machine has the following configuration.
Considering that my personal computer has 8 GB of RAM and 4 TB of disk space, I have allocated 2 CPUs, 4 GB of ram and 100 gigabytes of storage space, the iso image that I downloaded from the official website is Qubes 4.0.3 x86_64 bits.iso, is loaded from the hard disk to start virtualization. The virtual network interface is assigned to the device model of the network card, but I can also choose, virtio.
The installation has no failures, except the warning that my hardware does not support supports IOMMU / VT-d / AMD-Vi.
When I start Qubes, the last line fails.
Failed to start Qubes VM sys-net. But the system loads equally, I start Qubes manager.
When I try to start whonix -ws, the warning becomes apparent, / usr / bin / qvm-start, sys-firewall failed: stdout:
stderr: failed to start and HVM qube with PCI devices assigned-hardware does not support IOMMU / VT-d / AMD-Vi
I try to configure the devices, adding network cards, but I get the same results. In the Bios I have the VT-d display enabled, I don't know what else to do, in which I have the PVH mode enabled by default, and I have also tried the HVM mode.
and tried to update sys-whonix, in terminal, and it shows me the same Qube HVM boot failure message.
Other collateral errors are, Start failed: invalid argument: could not find capabilities for arch = x86_64, see /var/log/libvirt/libxl/libx-driver.log for details.
The sys-firewall qube is network connected to sys-net, which does not support firewall.
You may edit the sys-firewall qube firewall rules, but these will not take any effect until you connect it to a working firewall qube.
Other comments like PVH, mode is hidden since it doesn't support PCI passthrough.
I just need to know how to make the HVM mode work, and know how I can transfer files from my USB, since the recognition of USB devices also fails, everything else works perfectly. I have noticed that my Qubes is something different, I give an example.
In the following video https://www.youtube.com/watch?v=yrDo0q9qSXs&t=937s, at minute 37:54, in the option Domain: anon-whonix many options appear, while I only see one. Only Qube settings.
Thanks, and for the culture, I must not stop trying.
Catacombs
Mar 28, 2020, 6:56:09 PM3/28/20
to qubes-users
Qubes must be installed “bare metal”. Nothing underneath it. I have not done so, I. believe Ubuntu could be a guest OS.
Those error messages presume Qubes was installed first. Beware Qubes can want to take over the entirety of drives on computer. Might not be mandatory with the latest Qubes. As you can guess. Security mandates not having any thing else on computer.
Those error messages presume Qubes was installed first. Beware Qubes can want to take over the entirety of drives on computer. Might not be mandatory with the latest Qubes. As you can guess. Security mandates not having any thing else on computer.
Yethal
Mar 31, 2020, 9:29:50 AM3/31/20
to qubes-users
In order for Qubes to work inside KVM your CPU would need to support nested virtualization. Either switch your hardware or install baremetal
elo...@gmail.com
Apr 1, 2020, 7:16:28 AM4/1/20
to qubes-users
Where can I download baremetal?Yethal
Apr 2, 2020, 8:02:50 AM4/2/20
to qubes-users
Download the Qubes ISO and install it like a regular operating system.
elo...@gmail.com
Apr 2, 2020, 5:29:16 PM4/2/20
to qubes-users
Es lo que hecho, pero el .iso lo cargo con KVM.
Me has nombrado baremetal, no he encontrado nada al respecto, parecen ser servidores de IBM.
Foppe de Haan
Apr 3, 2020, 1:48:28 AM4/3/20
to qubes-users
what he means is install Qubes the same way you installed Ubuntu Mate, on its own drive.
That said, did you check in the bios if IOMMU and VT-X and VT-D support were all enabled?
elo...@gmail.com
Apr 8, 2020, 6:27:59 AM4/8/20
to qubes-users
I've tried, it's all here
https://forum.odroid.com/viewtopic.php?f=168&t=38036&sid=5d8803576236ab981175dab28b5c9791
https://forum.odroid.com/viewtopic.php?f=168&t=37933&sid=5d8803576236ab981175dab28b5c9791
Infinite loop in this bootable usb OS video.
Eloy Beltran
Apr 8, 2020, 6:31:25 AM4/8/20
to qubes-users
Qubes cannot be started without a virtual machine, and the virtual machine cannot be installed if there is not previously an Operating System, I have installed it in a QEMU based KVM. If I had loaded the .iso image to USB, the message would have been as follows.
Dom0 mode: Relaxed
Interrupt remapping enabled
Enabled directed EOI with ioapic_ack_old on!
ENABLING IO-APIC IRQs
-> Using old ACK method
..MP-BIOS bug:8254 timer not conected to IO-APIC
CPU0: No irq handler for vector e7 (IRQ -8)
IRQ7 a=0001[0001,000] v=60[ffff......
You can see all in
https://forum.odroid.com/viewtopic.php?f=168&t=37933
https://forum.odroid.com/viewtopic.php?f=168&t=38036Reply all
Reply to author
Forward
0 new messages