[qubes-users] Re: Setting up automated appvm backups using cron?

2018-11-26 Thread gdrub51
Le dimanche 25 novembre 2018 22:33:18 UTC+1, Stumpy a écrit : > I was wanting to back up some of my more important appvms, like vault, > on a regular basis. I am lazy so was thinking that cron might be an > option? Its been awhile since I used cron but I assume I could make a > job with a line

[qubes-users] Get help with HNS VM installation error

2018-11-10 Thread gdrub51
Hi, I'm trying to install a VM in HVM mode called HNS (hybrid network simulation). Based on Debian, HNS seems to run on KVM/QEMU. I followed the step-by-step installation instructions : https://www.hynesim.org/installation-pas-a-pas/ Edit /etc/hynesim/hynesim-node.ini Add support for

[qubes-users] Qubes OS 4.0, full screen and HVM domain

2018-11-09 Thread gdrub51
Hi, I'm trying to enable full screen mode two standalone VM(s). The following modus operandi does not work : https://www.qubes-os.org/doc/full-screen-mode/ No error displayed and no change right-clicking on a window’s title bar and selecting "Fullscreen". How can I fix it ? Any help and

[qubes-users] The log entries in sys-net are filled with a bunch of messages

2018-10-01 Thread gdrub51
Hi, I created a new sys-net (sys-net2) as network VM to use a wireless USB adapter. The sys-net2 dmesg logs (guest-sys-net2.log) are filled with a bunch of messages (4878 lines) like the following: ---%<-- First lines ---%<-- [0.00] Linux version 4.14.57-2.pvops.qubes.x86_64

[qubes-users] BT adapter with Qubes OS 4.0

2018-09-19 Thread gdrub51
Hi, I'm trying to look for a USB bluetooth adapter. Why qvm-usb doesn't list available USB devices ? [user@dom0 ~]$ qvm-usb BACKEND:DEVID DESCRIPTION USED BY [user@dom0 ~]$ %<--- [user@dom0 ~]$ lsusb Bus 002 Device 002: ID 0bc2:61b6 Seagate RSS LLC Bus 002 Device

Re: [qubes-users] suspend to ram, r8169, networking in sys-net not working after resume

2018-09-10 Thread gdrub51
Le lundi 23 avril 2018 00:30:40 UTC+2, cooloutac a écrit : > On Sunday, April 22, 2018 at 1:44:18 PM UTC-4, Mike Keehan wrote: > > On Sat, 21 Apr 2018 14:20:02 +0200 (CEST) > > wrote: > > > > > >> My issue: > > > >> > > > >> On qubes version r4.0 after resuming from suspend networking isn't > >

[qubes-users] Qubes-R4.0, Qubes VM Manager and VMs state

2018-09-07 Thread gdrub51
Hi, Why do I have to click on "Refresh" button in Qubes VM Manager for viewing/verifying the VMs state ('Started' or 'Stopped') ? On Qubes OS version 3.2, it was automatic, in real time. How can I fix it ? Thank you so much for your help. Best regards. -- You received this message because

[qubes-users] Importing a VM from R3.2 and shortcuts

2018-08-30 Thread gdrub51
Hi, Qubes OS version: Qubes-R4.0 After restoring VM from a backup (R3.2), all applications have been automatically included in the list of available apps. They appear in the VM’s submenu ("start menu" in dom0). When I click on shortcut, the assigned application is not running in its AppVM. I

[qubes-users] Qubes-R4.0 : missing argument to qvm-create

2018-08-30 Thread gdrub51
Hi, I'm trying to run the following command: $ qemu-img convert -O raw *.vmdk win10.raw $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > /home/user/win10-root.img $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from /home/user/win10-root.img qvm-create:

[qubes-users] Re: Unable to reset PCI device 0000:00:1f.6 (Qubes-R4.0 / fresh install) : no network

2018-08-29 Thread gdrub51
Finally, I followed the advice of awokd : $ qvm-pci attach --persistent --option permissive=true --option no-strict-reset=true sys-net dom0:00_XXX Everything works perfectly yet (for how long? :-) ). -- You received this message because you are subscribed to the Google Groups "qubes-users"

[qubes-users] Re: Unable to reset PCI device 0000:00:1f.6 (Qubes-R4.0 / fresh install) : no network

2018-08-29 Thread gdrub51
Le mercredi 22 août 2018 10:01:49 UTC+2, gdr...@gmail.com a écrit : > Hi, > > " [DOM0] Error starting Qube ! > ERROR : Start failed : internal error: Unable to reset PCI device > :00:1f.6 no FLR, PM reset or bus reset available, see > /var/log/libirt/libxl/libxl-driver.log for details" > >

[qubes-users] Unable to reset PCI device 0000:00:1f.6 (Qubes-R4.0 / fresh install) : no network

2018-08-22 Thread gdrub51
Hi, " [DOM0] Error starting Qube ! ERROR : Start failed : internal error: Unable to reset PCI device :00:1f.6 no FLR, PM reset or bus reset available, see /var/log/libirt/libxl/libxl-driver.log for details" Device :00:1f.6 is an assigned Ethernet controller : Intel Corporation

[qubes-users] Re: No ARP response

2017-05-29 Thread gdrub51
Thx Alex. The problem is not related to this post (enable proxy arp on Linux) : https://groups.google.com/forum/#!msg/qubes-users/lA2SgPcV9fU/PjMj_UE8CAAJ ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and

[qubes-users] No ARP response

2017-05-29 Thread gdrub51
Hi, I created a Kali Linux HVM from a bootable ISO image. So far, all is fine. sys-net2 is the VM that controls network and the HVM is connected to the network via the default sys-firewall2. $ ping 192.168.XX.XX PING 192.168.XX.XX (192.168.XX.XX) 56(84) bytes of data. 64 bytes from