Re: [qubes-users] Any way to attach a USB drive to a VM by label?
On Saturday, May 19, 2018 at 4:23:09 AM UTC-4, David Hobach wrote: > On 05/19/2018 01:04 AM, Qubes Guy wrote: > > On Friday, May 18, 2018 at 5:59:09 PM UTC-4, David Hobach wrote: > >> On 05/18/2018 08:19 PM, Marek Marczykowski-Górecki wrote: > >>> -BEGIN PGP SIGNED MESSAGE- > >>> Hash: SHA256 > >>> > >>> On Thu, May 17, 2018 at 05:57:09PM -0700, Qubes Guy wrote: > >>>> I've successfully used qvm-block (in Dom0) to attach USB drives to > >>>> different VMs (persistently), but I've noticed that Qubes (or Linux) > >>>> sometimes gives them to different devices over time. In other words, on > >>>> Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned > >>>> to /dev/sdj when I boot up on Wednesday. This is throwing off my > >>>> VeraCrypt / FreeFileSync backup routine. (Another way of saying this is > >>>> if I say "qvm-block attach MyVM sys-usb:sda --persistent" when one of > >>>> the three drives I use for MyVM is currently attached to that, this will > >>>> fail if Qubes moves that drive to a different device-name (during boot) > >>>> that isn't one of the three I previously attached (when I go to start up > >>>> that VM). > >>>> > >>>> I thought about persistently attaching all 10 of my USB drives to the VM > >>>> (some HDs, some flash, one SSD - I never use all of them at once - don't > >>>> ask!) because that would certainly fix this problem, but I get the > >>>> following error when I try to start the VM: "ERROR: Start failed: XML > >>>> error: target 'xvdi' duplicated for disk sources '/dev/sdc' and > >>>> '/dev/sde', see /var/log/libvirt/libxl/libxl-driver.log for details". > >>>> > >>>> Note that I did all the persistent attachment commands while the VM was > >>>> not running. If I detach all those, start the VM, do the persistent > >>>> attachments, shut down the VM and then restart it, I get an error along > >>>> the lines of "qrexec process failed to respond in 60 seconds". > >>>> > >>>> So, I guess I'm asking if there's a way to just persistently attach 2 or > >>>> 3 external USB drives and have them consistently available on the same > >>>> device names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt > >>>> ultimately doesn't care what device a drive is attached to (it could be > >>>> sda - sdj on my system) because it shows the attached drive as > >>>> "/media/user/BIG_TOSHIBA, but if a drive isn't where it's supposed to > >>>> be, that'll fail. > >>>> > >>>> In case you're curious, the error messages in > >>>> /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if > >>>> you want me to post it, I can. > >>>> > >>>> Any help you guys can give me would be greatly appreciated! Thanks... > >>> > >>> It isn't available yet, related issue: > >>> https://github.com/QubesOS/qubes-issues/issues/3437 > >> > >> As a workaround you could mount the device via uuid or file system label > >> in sys-usb, create a loop device from the container you want to pass to > >> another VM and use qvm-block on that loop device (for which you can > >> define the name yourself). > >> > >> Of course that's only convenient if you script it... > > > > Thanks, but how do you do create a loop device? I'm (mostly) a Linux newbie > > (and, as of 5 weeks ago, I was a Qubes newbie) - I'm your worst nightmare > > :) I tried the UUID mount thing described in the article I mentioned > > above, but it just prevents sys-net from starting, but maybe with this loop > > thing you mention? Can you give me the actual commands required, or direct > > me to an article showing this? I'm not even sure what to search for. Thanks > > much! > > Honestly you'll probably be off better by waiting for the feature to be > implemented then. > > Anyway for reference I was talking about something like > > in your sys-usb: > 1. mount -U [uuid] [mount point] > 2. losetup -f --show [your veracrypt file on the mounted file system] > > in dom0: > 3. qvm-block a [target VM] "sys-usb:[output of 2]" > 4. Open the veracrypt block device now attached to [target VM]. (luks > supports that, not sure about veracrypt) > > You
Re: [qubes-users] Any way to attach a USB drive to a VM by label?
On Friday, May 18, 2018 at 5:59:09 PM UTC-4, David Hobach wrote: > On 05/18/2018 08:19 PM, Marek Marczykowski-Górecki wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Thu, May 17, 2018 at 05:57:09PM -0700, Qubes Guy wrote: > >> I've successfully used qvm-block (in Dom0) to attach USB drives to > >> different VMs (persistently), but I've noticed that Qubes (or Linux) > >> sometimes gives them to different devices over time. In other words, on > >> Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to > >> /dev/sdj when I boot up on Wednesday. This is throwing off my VeraCrypt / > >> FreeFileSync backup routine. (Another way of saying this is if I say > >> "qvm-block attach MyVM sys-usb:sda --persistent" when one of the three > >> drives I use for MyVM is currently attached to that, this will fail if > >> Qubes moves that drive to a different device-name (during boot) that isn't > >> one of the three I previously attached (when I go to start up that VM). > >> > >> I thought about persistently attaching all 10 of my USB drives to the VM > >> (some HDs, some flash, one SSD - I never use all of them at once - don't > >> ask!) because that would certainly fix this problem, but I get the > >> following error when I try to start the VM: "ERROR: Start failed: XML > >> error: target 'xvdi' duplicated for disk sources '/dev/sdc' and > >> '/dev/sde', see /var/log/libvirt/libxl/libxl-driver.log for details". > >> > >> Note that I did all the persistent attachment commands while the VM was > >> not running. If I detach all those, start the VM, do the persistent > >> attachments, shut down the VM and then restart it, I get an error along > >> the lines of "qrexec process failed to respond in 60 seconds". > >> > >> So, I guess I'm asking if there's a way to just persistently attach 2 or 3 > >> external USB drives and have them consistently available on the same > >> device names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt > >> ultimately doesn't care what device a drive is attached to (it could be > >> sda - sdj on my system) because it shows the attached drive as > >> "/media/user/BIG_TOSHIBA, but if a drive isn't where it's supposed to be, > >> that'll fail. > >> > >> In case you're curious, the error messages in > >> /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you > >> want me to post it, I can. > >> > >> Any help you guys can give me would be greatly appreciated! Thanks... > > > > It isn't available yet, related issue: > > https://github.com/QubesOS/qubes-issues/issues/3437 > > As a workaround you could mount the device via uuid or file system label > in sys-usb, create a loop device from the container you want to pass to > another VM and use qvm-block on that loop device (for which you can > define the name yourself). > > Of course that's only convenient if you script it... Thanks, but how do you do create a loop device? I'm (mostly) a Linux newbie (and, as of 5 weeks ago, I was a Qubes newbie) - I'm your worst nightmare :) I tried the UUID mount thing described in the article I mentioned above, but it just prevents sys-net from starting, but maybe with this loop thing you mention? Can you give me the actual commands required, or direct me to an article showing this? I'm not even sure what to search for. Thanks much! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6c66eee4-1ce8-4fbe-89b1-c758ccbc3ac2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Any way to attach a USB drive to a VM by label?
On Friday, May 18, 2018 at 2:19:09 PM UTC-4, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, May 17, 2018 at 05:57:09PM -0700, Qubes Guy wrote: > > I've successfully used qvm-block (in Dom0) to attach USB drives to > > different VMs (persistently), but I've noticed that Qubes (or Linux) > > sometimes gives them to different devices over time. In other words, on > > Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to > > /dev/sdj when I boot up on Wednesday. This is throwing off my VeraCrypt / > > FreeFileSync backup routine. (Another way of saying this is if I say > > "qvm-block attach MyVM sys-usb:sda --persistent" when one of the three > > drives I use for MyVM is currently attached to that, this will fail if > > Qubes moves that drive to a different device-name (during boot) that isn't > > one of the three I previously attached (when I go to start up that VM). > > > > I thought about persistently attaching all 10 of my USB drives to the VM > > (some HDs, some flash, one SSD - I never use all of them at once - don't > > ask!) because that would certainly fix this problem, but I get the > > following error when I try to start the VM: "ERROR: Start failed: XML > > error: target 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > Note that I did all the persistent attachment commands while the VM was not > > running. If I detach all those, start the VM, do the persistent > > attachments, shut down the VM and then restart it, I get an error along the > > lines of "qrexec process failed to respond in 60 seconds". > > > > So, I guess I'm asking if there's a way to just persistently attach 2 or 3 > > external USB drives and have them consistently available on the same device > > names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt ultimately > > doesn't care what device a drive is attached to (it could be sda - sdj on > > my system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, > > but if a drive isn't where it's supposed to be, that'll fail. > > > > In case you're curious, the error messages in > > /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you > > want me to post it, I can. > > > > Any help you guys can give me would be greatly appreciated! Thanks... > > It isn't available yet, related issue: > https://github.com/QubesOS/qubes-issues/issues/3437 > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlr/GRUACgkQ24/THMrX > 1yzuqAf7Bw2L6SpZhPlLrhX20eFvagLuPpKbuMl/yVLMDhRBZqK86kIonC3Zvm1b > eR6cTQ540PNHJiqL0uescJIHS7sHJDnnqC7Y0x12GIlEKWU+1pobRDZIwfErMiD/ > 2FzJisSgk8tiLIwmyhcrWyUyVxuk6e1TpG5sVdUMb3lTqjiqPPChZBRlLFsYmraK > PvBvY9DCeL6unSIUJqadxBtfeh5KDmSXauLS7T/vxVfEWbsNxI+ZrgGWPALkniZK > MaXGp6hYrmnycl6o8xi74CWoGvwruhUrFOVxAn8hrFR0OA5PmeWVQjtRJ4j0okmL > qXHoFWHbMVltipYLNvBYZANXcIc3bw== > =BsRg > -END PGP SIGNATURE- Oops, forgot the link: https://gist.github.com/etes/aa76a6e9c80579872e5f -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9f3aba53-b1ee-473a-aa3c-a9cec5fd91df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Any way to attach a USB drive to a VM by label?
On Friday, May 18, 2018 at 2:19:09 PM UTC-4, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, May 17, 2018 at 05:57:09PM -0700, Qubes Guy wrote: > > I've successfully used qvm-block (in Dom0) to attach USB drives to > > different VMs (persistently), but I've noticed that Qubes (or Linux) > > sometimes gives them to different devices over time. In other words, on > > Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to > > /dev/sdj when I boot up on Wednesday. This is throwing off my VeraCrypt / > > FreeFileSync backup routine. (Another way of saying this is if I say > > "qvm-block attach MyVM sys-usb:sda --persistent" when one of the three > > drives I use for MyVM is currently attached to that, this will fail if > > Qubes moves that drive to a different device-name (during boot) that isn't > > one of the three I previously attached (when I go to start up that VM). > > > > I thought about persistently attaching all 10 of my USB drives to the VM > > (some HDs, some flash, one SSD - I never use all of them at once - don't > > ask!) because that would certainly fix this problem, but I get the > > following error when I try to start the VM: "ERROR: Start failed: XML > > error: target 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > Note that I did all the persistent attachment commands while the VM was not > > running. If I detach all those, start the VM, do the persistent > > attachments, shut down the VM and then restart it, I get an error along the > > lines of "qrexec process failed to respond in 60 seconds". > > > > So, I guess I'm asking if there's a way to just persistently attach 2 or 3 > > external USB drives and have them consistently available on the same device > > names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt ultimately > > doesn't care what device a drive is attached to (it could be sda - sdj on > > my system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, > > but if a drive isn't where it's supposed to be, that'll fail. > > > > In case you're curious, the error messages in > > /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you > > want me to post it, I can. > > > > Any help you guys can give me would be greatly appreciated! Thanks... > > It isn't available yet, related issue: > https://github.com/QubesOS/qubes-issues/issues/3437 > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlr/GRUACgkQ24/THMrX > 1yzuqAf7Bw2L6SpZhPlLrhX20eFvagLuPpKbuMl/yVLMDhRBZqK86kIonC3Zvm1b > eR6cTQ540PNHJiqL0uescJIHS7sHJDnnqC7Y0x12GIlEKWU+1pobRDZIwfErMiD/ > 2FzJisSgk8tiLIwmyhcrWyUyVxuk6e1TpG5sVdUMb3lTqjiqPPChZBRlLFsYmraK > PvBvY9DCeL6unSIUJqadxBtfeh5KDmSXauLS7T/vxVfEWbsNxI+ZrgGWPALkniZK > MaXGp6hYrmnycl6o8xi74CWoGvwruhUrFOVxAn8hrFR0OA5PmeWVQjtRJ4j0okmL > qXHoFWHbMVltipYLNvBYZANXcIc3bw== > =BsRg > -END PGP SIGNATURE- So, the fix for this is coming? (Sorry, I can't speak the "Github" language too well yet.) I'm trying the method below, but running into the same kind of problems (so far) - qrexec non-responsiveness, sys-net no longer starting, etc -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b86911a1-0f43-4da3-a850-c16dc0566509%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Any way to attach a USB drive to a VM by label?
On Friday, May 18, 2018 at 3:14:57 AM UTC-4, awokd wrote: > On Fri, May 18, 2018 1:00 am, Qubes Guy wrote: > > On Thursday, May 17, 2018 at 8:57:09 PM UTC-4, Qubes Guy wrote: > > >> So, I guess I'm asking if there's a way to just persistently attach 2 or > >> 3 external USB drives and have them consistently available on the same > >> device names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt > >> ultimately doesn't care what device a drive is attached to (it could be > >> sda - sdj on my system) because it shows the attached drive as > >> "/media/user/BIG_TOSHIBA, but if a drive isn't where it's supposed to > >> be, that'll fail. > > > By the way, I'm running version 4.0 of Qubes on a fairly recent laptop > > with 8GB of RAM... > > Can you make sys-usb's /etc/fstab persistent, then specify /dev names > there by drive UUID? I'm not sure what you mean by either of those things. Are you saying I should put entries in the fstab file in sys-usb to permanently mount those drives? If so, what would the commands look like? (As a side note, I tried to persistently mount a NAS share using the fstab file in my Debian template (and various other things) and couldn't get that to work, but I do know about the fstab file. I'm gonna try to use NFS instead...) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/74405d5e-a364-4c6d-8c56-b122662e2fe5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Any way to attach a USB drive to a VM by label?
On Thursday, May 17, 2018 at 8:57:09 PM UTC-4, Qubes Guy wrote: > I've successfully used qvm-block (in Dom0) to attach USB drives to different > VMs (persistently), but I've noticed that Qubes (or Linux) sometimes gives > them to different devices over time. In other words, on Monday, my > BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when > I boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync > backup routine. (Another way of saying this is if I say "qvm-block attach > MyVM sys-usb:sda --persistent" when one of the three drives I use for MyVM is > currently attached to that, this will fail if Qubes moves that drive to a > different device-name (during boot) that isn't one of the three I previously > attached (when I go to start up that VM). > > I thought about persistently attaching all 10 of my USB drives to the VM > (some HDs, some flash, one SSD - I never use all of them at once - don't > ask!) because that would certainly fix this problem, but I get the following > error when I try to start the VM: "ERROR: Start failed: XML error: target > 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', see > /var/log/libvirt/libxl/libxl-driver.log for details". > > Note that I did all the persistent attachment commands while the VM was not > running. If I detach all those, start the VM, do the persistent attachments, > shut down the VM and then restart it, I get an error along the lines of > "qrexec process failed to respond in 60 seconds". > > So, I guess I'm asking if there's a way to just persistently attach 2 or 3 > external USB drives and have them consistently available on the same device > names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt ultimately > doesn't care what device a drive is attached to (it could be sda - sdj on my > system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, but > if a drive isn't where it's supposed to be, that'll fail. > > In case you're curious, the error messages in > /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you > want me to post it, I can. > > Any help you guys can give me would be greatly appreciated! Thanks... By the way, I'm running version 4.0 of Qubes on a fairly recent laptop with 8GB of RAM... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/592ec7f7-d1c5-4bf6-871a-3863fec8ff0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Any way to attach a USB drive to a VM by label?
I've successfully used qvm-block (in Dom0) to attach USB drives to different VMs (persistently), but I've noticed that Qubes (or Linux) sometimes gives them to different devices over time. In other words, on Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when I boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync backup routine. (Another way of saying this is if I say "qvm-block attach MyVM sys-usb:sda --persistent" when one of the three drives I use for MyVM is currently attached to that, this will fail if Qubes moves that drive to a different device-name (during boot) that isn't one of the three I previously attached (when I go to start up that VM). I thought about persistently attaching all 10 of my USB drives to the VM (some HDs, some flash, one SSD - I never use all of them at once - don't ask!) because that would certainly fix this problem, but I get the following error when I try to start the VM: "ERROR: Start failed: XML error: target 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', see /var/log/libvirt/libxl/libxl-driver.log for details". Note that I did all the persistent attachment commands while the VM was not running. If I detach all those, start the VM, do the persistent attachments, shut down the VM and then restart it, I get an error along the lines of "qrexec process failed to respond in 60 seconds". So, I guess I'm asking if there's a way to just persistently attach 2 or 3 external USB drives and have them consistently available on the same device names when I start the VM so VeraCrypt doesn't balk? (VeraCrypt ultimately doesn't care what device a drive is attached to (it could be sda - sdj on my system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, but if a drive isn't where it's supposed to be, that'll fail. In case you're curious, the error messages in /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you want me to post it, I can. Any help you guys can give me would be greatly appreciated! Thanks... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f0434929-c5e2-446e-8835-045f7203906b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Any way to attach a USB drive to a PVH by label?
I've successfully used qvm-block (in Dom0) to attach USB drives to different VMs (even persistently), but I've noticed that Qubes (or Linux?) sometimes gives them to different devices over time. In other words, on Monday, my BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when I boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync backup routine. Is there a way to make this stick? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f09ce2f0-cce3-4099-ad10-09a57bd046eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Tuesday, May 15, 2018 at 12:11:50 AM UTC-4, john wrote: > On 05/12/18 19:46, Qubes Guy wrote: > > On Saturday, May 12, 2018 at 4:28:56 AM UTC-4, > > niepo...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > >> On Friday, May 11, 2018 at 3:17:05 PM UTC-4, Qubes Guy wrote: > >>> On Friday, May 11, 2018 at 1:17:24 PM UTC, > >>> niepo...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > >>>> Fresh install of Qubes R4.0 and there is no internet connection in appVM > >>>> - firefox just not load websites. > >>>> > >>>> Internet connection actually is ok as I'm able to make update for > >>>> template VM. > >>>> > >>>> What can be reason of this not working internet in app VM and how > >>>> resolve this? > >>> > >>> Is this still a problem? Did you give your AppVM access to the net VM > >>> (set "Networking" to sys-firewall (preferably) or sys-net in the settings > >>> dialog for the AppVM)? > >> > >> Yes, problem still exist. > >> > >> There was sys-firewall connected to appVM as well sys-net and no > >> connection. > >> I have also tried changing template from fedora to debian -internet not > >> working. > >> I have also install chromium browser and connection not working. > >> > >> Very frustrating situation... > > > > One thing I forgot to mention: Do NOT set the "Networking" setting in your > > template VMs (set it to "None"). Giving network access to your templates is > > considered a major security threat (since all AppVMs you base on them > > inherit any malware/corruption). If you put "qubes-updates-proxy" in the > > services tab of sys-net, you won't need to do this. If you absolutely need > > to do this anyway, turn it off as soon as possible... > > > > When I look at the qubes settings -> services in sys-net I see nothing > , would adding qubes-updates-proxy allow me to install manually > software I want to be AppVM-wide , in the Fedora Template? > > or exactly how is one Supposed to ever add software to a Template if > there is no networking except for updates ? > > Or lets say I add the qubes-updates-proxy to sys-net , then in the > Template can I just sudo dnf installor there more to it ? I couldn't get any template VMs to update (or be able to install software in them) until I put qubes-updates-proxy in sys-net. Apparently, that's how template VMs gain network access securely. The documentation implies says that this is already enabled by default (meaning I shouldn't have had to add it myself), but that wasn't the case, at least for me. The minute I put it in, the floodgates opened and I've been able to use Qubes ever since. The only downside to this is that this doesn't work for Firefox unless you install it through the standard repository. I couldn't get Quantum that way, so I had to manually install it in the template. And every time Firefox auto-updates itself, it's in the AppVM and the update disappears every time I restart the AppVM. So I'm currently enabling network access in the template VM only long enough to allow Firefox to update itself. I shouldn't, but I am. I understand that Mozilla is now calling Quantum "Firefox ESR" now (Extended Support Release). ESR version 52 was the only version in the Debian repository at the time, so I didn't want it. But if the Debian folks put Quantum in the repository, I'll switch over. If you can get Quantum from Fedora's repository (or however), then just ignore all that :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9a829f9e-0746-4908-b63a-d484b0c84192%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Monday, May 14, 2018 at 12:55:51 PM UTC-4, niepo...@gmail.com wrote: > On Sunday, May 13, 2018 at 11:59:16 AM UTC-4, awokd wrote: > > On Sat, May 12, 2018 7:08 pm, wrote: > > > netVM has ok ping to google.com > > > firewallVM has no pings > > > appVM has also no pings > > > > > > Maybe it's worth to mention: update template VM was done with success > > > (which is a bit odd as update actually was done with success as firewallVM > > > has no pings). > > > > Are you using the default templates and AppVMs, or ones you've restored? > > Try doing a reinstall and testing with the default ones only. > > appVM's are not restored. All is default except I changed to pv mode netVM > and firewallVM (in hvm and pvh do not started). > > Looks like i will back to R3.2 as R4.0 is useless for me with no internet in > appVM's. I don't know if this is helpful, but I get Internet via a USB-to-Ethernet adapter. I have that (and all of my other USB devices) connected to a single internal USB controller connected to the sys-usb VM. sys-usb is an HVM (with network-manager in the Services tab). sys-net is connected to sys-usb, and it's a PVH (with meminfo-writer, clocksync and qubes-updates-proxy in its Services tab). sys-firewall is connected to sys-net, and it's also a PVH (with no services in the Services tab). Of course, sys-usb was flagged as providing networks services when it was created. Hope that helps... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e6b70863-d701-4480-ba56-9edd5dbe6ce3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Saturday, May 12, 2018 at 4:28:56 AM UTC-4, niepo...@gmail.com wrote: > On Friday, May 11, 2018 at 3:17:05 PM UTC-4, Qubes Guy wrote: > > On Friday, May 11, 2018 at 1:17:24 PM UTC, niepo...@gmail.com wrote: > > > Fresh install of Qubes R4.0 and there is no internet connection in appVM > > > - firefox just not load websites. > > > > > > Internet connection actually is ok as I'm able to make update for > > > template VM. > > > > > > What can be reason of this not working internet in app VM and how resolve > > > this? > > > > Is this still a problem? Did you give your AppVM access to the net VM (set > > "Networking" to sys-firewall (preferably) or sys-net in the settings dialog > > for the AppVM)? > > Yes, problem still exist. > > There was sys-firewall connected to appVM as well sys-net and no connection. > I have also tried changing template from fedora to debian -internet not > working. > I have also install chromium browser and connection not working. > > Very frustrating situation... One thing I forgot to mention: Do NOT set the "Networking" setting in your template VMs (set it to "None"). Giving network access to your templates is considered a major security threat (since all AppVMs you base on them inherit any malware/corruption). If you put "qubes-updates-proxy" in the services tab of sys-net, you won't need to do this. If you absolutely need to do this anyway, turn it off as soon as possible... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dfa187be-0914-4f56-b2e0-7e541712e629%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Saturday, May 12, 2018 at 4:28:56 AM UTC-4, niepo...@gmail.com wrote: > On Friday, May 11, 2018 at 3:17:05 PM UTC-4, Qubes Guy wrote: > > On Friday, May 11, 2018 at 1:17:24 PM UTC, niepo...@gmail.com wrote: > > > Fresh install of Qubes R4.0 and there is no internet connection in appVM > > > - firefox just not load websites. > > > > > > Internet connection actually is ok as I'm able to make update for > > > template VM. > > > > > > What can be reason of this not working internet in app VM and how resolve > > > this? > > > > Is this still a problem? Did you give your AppVM access to the net VM (set > > "Networking" to sys-firewall (preferably) or sys-net in the settings dialog > > for the AppVM)? > > Yes, problem still exist. > > There was sys-firewall connected to appVM as well sys-net and no connection. > I have also tried changing template from fedora to debian -internet not > working. > I have also install chromium browser and connection not working. > > Very frustrating situation... Set the "Networking" setting in your AppVM settings dialog to point to sys-firewall, set the "Networking" setting in sys-firewall to point to sys-net, and if your network connection is coming via an Ethernet-to-USB adapter, set the "Networking" setting in sys-net to point to sys-usb. (A sidenote regarding the latter: If you don't already have a separate VM to handle USB services, you really should create it, even if you're not using an Ethernet-to-USB adapter. Note that only one VM should be responsible for providing network services (which would either be sys-net or sys-usb, depending on the card/adapter you're using to provide Internet. If you *do* have an Ethernet-to-USB adapter, you'll want to set the "Provides network services" checkbox when you go to create the sys-usb VM.) You also need to add "qubes-updates-proxy" (without quotes) to the list of services in the sys-net settings dialog. After you do all this, you should be able to use "sudo apt-get update" in a terminal in your template VM to install or update packages (which AppVMs inherit, of course). One thing I've discovered is that you often need to restart VMs to get them to recognize changes you've made, so if you don't get what you expect, restart the VM in question. Let me know what happens... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/855af1af-870b-475c-94c8-af0f01a4f8b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Saturday, May 12, 2018 at 4:28:56 AM UTC-4, niepo...@gmail.com wrote: > On Friday, May 11, 2018 at 3:17:05 PM UTC-4, Qubes Guy wrote: > > On Friday, May 11, 2018 at 1:17:24 PM UTC, niepo...@gmail.com wrote: > > > Fresh install of Qubes R4.0 and there is no internet connection in appVM > > > - firefox just not load websites. > > > > > > Internet connection actually is ok as I'm able to make update for > > > template VM. > > > > > > What can be reason of this not working internet in app VM and how resolve > > > this? > > > > Is this still a problem? Did you give your AppVM access to the net VM (set > > "Networking" to sys-firewall (preferably) or sys-net in the settings dialog > > for the AppVM)? > > Yes, problem still exist. > > There was sys-firewall connected to appVM as well sys-net and no connection. > I have also tried changing template from fedora to debian -internet not > working. > I have also install chromium browser and connection not working. > > Very frustrating situation... And, of course, I meant "www.google.com". Try that. If you don't get a response, let me know how you're getting your Internet (Wireless or Ethernet) and the name and model of the network card/controller -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dea20035-28d1-4aed-9709-9c441d41de6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Saturday, May 12, 2018 at 4:28:56 AM UTC-4, niepo...@gmail.com wrote: > On Friday, May 11, 2018 at 3:17:05 PM UTC-4, Qubes Guy wrote: > > On Friday, May 11, 2018 at 1:17:24 PM UTC, niepo...@gmail.com wrote: > > > Fresh install of Qubes R4.0 and there is no internet connection in appVM > > > - firefox just not load websites. > > > > > > Internet connection actually is ok as I'm able to make update for > > > template VM. > > > > > > What can be reason of this not working internet in app VM and how resolve > > > this? > > > > Is this still a problem? Did you give your AppVM access to the net VM (set > > "Networking" to sys-firewall (preferably) or sys-net in the settings dialog > > for the AppVM)? > > Yes, problem still exist. > > There was sys-firewall connected to appVM as well sys-net and no connection. > I have also tried changing template from fedora to debian -internet not > working. > I have also install chromium browser and connection not working. > > Very frustrating situation... Open a terminal in your sys-net VM and type "ping .google.com" (without quotes). If you get no response, you need to figure out why you have no network connectivity in that VM. (It should say something like "64 bytes from time=18.5ms" or something like that.) Let me know if you have network access there. I'm hitting the road for a little while. I'll respond as soon as I can... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8294ac3f-7284-4a81-80a9-87091c2fd93a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R4.0 - no internet working in appVM
On Friday, May 11, 2018 at 1:17:24 PM UTC, niepo...@gmail.com wrote: > Fresh install of Qubes R4.0 and there is no internet connection in appVM - > firefox just not load websites. > > Internet connection actually is ok as I'm able to make update for template VM. > > What can be reason of this not working internet in app VM and how resolve > this? Is this still a problem? Did you give your AppVM access to the net VM (set "Networking" to sys-firewall (preferably) or sys-net in the settings dialog for the AppVM)? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d3dfa6f5-e8d7-463b-b45b-ff9462c5a41d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
