> Can I ask why you want to do this?
> Why dont you just call notify-send in the qube?
First some introduction:
- I have 'storage' vm. It takes storage devices (few HDDs) on startup and
exposes them via NFS & Samba to other VMs and physical machines. Each VM can
access just what is exported
> >> Wondering how to log packets blocked and accepted by qubes firewall
> >> for specific vm or all vms if thats the only option? Couldn't find
> >> anything in website or google or qvm-firewall
> > Unfortunately, Qubes firewall was not designed for such use case.
> >
> > If you are familiar
Hi all,
I struggle to get something that's working in Q3.2 also in Qubes4:
- I need to display message from AppVm on the screen (via notify-send in dom0)
and do it via qubes-rpc executed in AppVm "storage". rpc procedure is named
'storage.log'
- allow policy in dom0:
> cat
Hi all,
I tried test install of Qubes4 to test migration from 3.2 and I was surpised
that sys-new,sys-fw and all appvm share same network 10.137.0.*
This is in contrast to 3.2, where appVMs are in 10.137.2.*, firewalls in
10.137.1.*, and just sys-net in 10.137.0.*
(like drawn in
Great, thank you both!
1. 'dnf mark install qubes-vm-recommended'
2. 'dnf remove thunderbird-qubes' (on which above metapackage depends). This
way it removes removes also the recommended meta-package, but leaves its other
dependencies
Let's mark this as completed
--
You received this
Hi guys,
I installed Q4.0.1 on USB HDD to see changes from 3.2.
As I've decided to use fedora-29 for system-related VMs, I wanted to remove
large apps like Firefox and Thunderbird from it.
But running 'dnf remove thunderbird' on f29 template resulted in removal of 67
other packages, which
Suggestion: Instead of having "VMs that boot 'cleanly'" I'd propose to add
following option:
- configuration data that lives in /rw/config (usrlocal) and is cleaned by this
scripts/services to be fetched from Dom0 (or dedicated VM) based on VM's name.
This should be done after cleanup service
So, after Marek's fix here, https://github.com/QubesOS/qubes-issues/issues/1659
is it true that I can expect this from it:
- HVM passthrough working using stub domain via xl ?
(following your guide above, exlcuding 'qemu-xen-traditional')
And not:
- HVM passthrough working via VM created with
> If we shutdown a VM that has a USB storage device attached, the VM still
> indicates the device being attached to the VM. But when you restart the VM,
> the device is not accessible and can no longer be disconnected.
As far as I remember this should fix it: "sudo udevadm trigger
Hi Marcus,
I'm bit confused with this
> Edit /etc/default/grub and add following options (change the pci address if
> needed)
Which version of Qubes is this? Aint 3.1 EFI-only?
And EFI version of kernel args are to be passed via /boot/efi/EFI/qubes
(kernel=)?
regards,
Tom
--
You received
etc/init.d/rc.local (not sure if necessary qubes stuff will be already
available)
- something else
thanks,
Tomhet
P.S. An alternative could be event listeners for qubes events
'onVmStartComplete'/'beforeVmShutdown', if such exist & I knew python.
--
You received this message because you
ices to be attached to storage -
this is 2nd column of table output by qvm-block command.
After devices are assigned to storageVM, auto-mount is executed in the VM.
I have similar script that unmounts and detaches devices from the storageVM.
Currently I have to find suitable place and time to run th
12 matches
Mail list logo
