Bernhard:
By default network cards are assigned to sys-net and are not visible
in dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned
to it. So you need to run lsusb or lspci from within sys-net, not
dom0. You
I installed Kali Linux (as a non template vm) and in the qubes setting for
this Kali it says:
default dispvm template has a different networking setting than this qube,
unexpected network access may occur
what should I do in Kali for it to work?
--
You received this message because you are
When I compared your logs to what I have, it came to my mind that some
years ago I had similar problems - because of processor microcode which was
too old. I had to update that to get hvms working.
I couldn't find which microcode version you have, it is somehow not shown
in the cpu log you
!!!
I have some, hopefully, great news.
I was messing around searching some help online and I got an idea to try
installing Win7 StandaloneVM following the
https://www.qubes-os.org/doc/windows-tools/ guide.
I kid you not, it worked on first try! HVM mode, even got the Windows Tools
working.
Lenovo Thinkpad X230, let me know if you need serial number or such.
Error message on install attempt: Unsupported hardware detected
Relevant: VT-d, Interrupt Remapping (Intel i5-3320M processor, not AMD) is
not enabled, without these features blah blah blah.
UEFI BIOS version: G2ET97WW (2.57)
So I got myself into a corner:
* Usually I attach the entire USB controller to my app-dev (debian 9) qube. But
in that case this qube can only have 2048 MB of memory (for some reason that's
the limit when the USB controller is attached; any more and things crash ...
same with Windows qube and
On Thu, Dec 05, 2019 at 04:35:57PM -0600, Sven Semmler wrote:
> So ... now what? Where does Qubes keep a record of this. What can I do to
> 'detach' this and the other USB devices from app-dev?
qvm-clone app-dev app-dev2
qvm-remove app-dev
qvm-clone app-dev2 app-dev
qvm-remove app-dev2
... did
I'm looking for the best laptop I can install Qubes on. Please help me
choose.
I've looked into it, and I think this looks good.
https://ryf.fsf.org/categories/laptops
https://www.qubes-os.org/news/2019/07/18/insurgo-privacybeast-qubes-certification/
https://puri.sm/products/librem-13/
Hi @tukaisute,
On 12/6/19 7:32 AM, tukais...@cock.li wrote:
> I'm looking for the best laptop I can install Qubes on. Please help me
> choose.
> I've looked into it, and I think this looks good.
>
> https://ryf.fsf.org/categories/laptops
>
Hi everyone,
Thank you for all your help and discussion. I posted the HCL for the device
I'm troubleshooting -- the latest Lenovo Flex 14 with the i5-10210U. You
can find it here:
https://groups.google.com/forum/#!topic/qubes-users/kamMImlGMNQ
I'm guessing the plan is to set up networking,
It seems like this was a graphics error and not related to iSCSI. Adding
the following boot arguments to [qubes] section in BOOTX64.cfg fixed the
problem:
*mapbs=1 noexitboot=1 modprobe.blacklist=nouveau
rd.driver.blacklist=nouveau*
As suggested here:
11 matches
Mail list logo