Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote: > On Fri, 18 Jan 2019 07:17:00 -0800 (PST) > scott wrote: > > > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > > Thanks but unfortunately I don't know that issue helps, as those > > > > who were able to resolve it did so by updating which I cannot do > > > > since sys-net fails to start. > > > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , > > > > seems to cover that problem but nothing's mentioned about net & > > > > firewall failing to start. > > > > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > > scott wrote: > > > > > > > > > > > Hello, I apologize in advance if this has already been > > > > > > addressed but searching for "sys-net" & "libxl" give many > > > > > > confusing results, I don't see any that match both not > > > > > > working, and I'm completely new to Qubes. My problem is that > > > > > > after 2 different installs of the same version, 4.01, I keep > > > > > > getting the same problems: When I get into Qubes I cannot > > > > > > update dom0, and sys-net & sys-firewall both fail to start > > > > > > even though my NIC is correctly listed in devices for -net. > > > > > > > > > > > > Basic info: > > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > > Qubes 4.01, sigs checked good. > > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > > described below. Re-installed by DVD thinking I'd muffed > > > > > > something (think I read on reddit that USB installs made from > > > > > > windows had issues) and the behavior is exactly the same. > > > > > > > > > > > > Behavior observed: > > > > > > (anything in [xxx] is me telling you the variation, as I get > > > > > > this for 2 VM's, 2 error codes, etc.) > > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > > * When I attempt to manually start either, I get this error > > > > > > message: "ERROR: Start failed: internal error: libxenlight > > > > > > failed to create new domain 'sys-net' [or sys-firewall], > > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > > timestamps ranging from date of install to today: 1: > > > > > > "[date:time]: libxl: > > > > > > libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: > > > > > > -3" Those errors and nothing else. > > > > > > > > > > > > I've tried to update dom0 by command as found in docs, as > > > > > > well as through GUI without success. I found a page elsewhere > > > > > > that described temporarily putting NIC in firewall or another > > > > > > VM to see if it worked, but I must be doing it wrong as I > > > > > > always get loopback errors when trying to save. It always > > > > > > tells me failed, regardless. No wonder if network isn't > > > > > > working. > > > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, > > > > > > but I can't seem to figure out how to see if the NIC is > > > > > > operational since sys-net isn't working (new to qubes > > > > > > sorry!), however I verified my router is not showing an IP > > > > > > assigned, though link LED is on. > > > > > > > > > > > > If anyone can help me try to figure this out, I'd really > > > > > > appreciate it. I'm still a bit green on linux but I learn > > > > > > fast, I recently gave up on Windows (I hate 10 so much I > > > > > > could scream) so I'm trying to dive in with qubes (deep end > > > > > > of the pool I think) as it best suits my needs with the VM > > > > > > implementation. > > > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how > > > > > > to make USB copy work yet since I've been beating my head on > > > > > > the networking issue. > > > > > > > > > > > > Thanks, and sorry in advance if this duplicated another > > > > > > thread. > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > > > It might give you some pointers. > > > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain > > > > > creation fail: Operation not supported" in google.) > > > > > > > > > > Mike. > > > > > > > > > > > Test whether issue is with NIC by removing the card from sys-net > > > and confirming that sys-firewall starts (after sys-net). > > > Shutdown both. > > > Re-attach NIC to sys-net. > > > Report back. > > > > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > > device to the
[qubes-users] Re: APC UPS daemon
On 1/18/19 12:48 PM, Achim Patzner wrote:> On 20190118 at 16:18 +0100 Bill Wether wrote: >> I installed apcupsd to Dom0 > > Is there any good reason to do that? Simplicity. It would take me a long time to do what you describe below. > I handed over my UPS' USB connection to a separate VM which in turn > notifies dom0 using RPC. My next step was moving that to an old > Pi and asking it across the network. > > And please don't forget to restrict access appropriately if you use > a separate server. Someone turned off my workplace's power bar (and > thus the UPS) and it shut down my notebook across the VPN link. > Cheers BillW -- 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/trinity-9afcf1fc-7f89-4400-8057-f58bf73df189-1547837972120%403c-app-mailcom-lxa13. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] APC UPS daemon
On 20190118 at 16:18 +0100 Bill Wether wrote: > I installed apcupsd to Dom0 Is there any good reason to do that? I handed over my UPS' USB connection to a separate VM which in turn notifies dom0 using RPC. My next step was moving that to an old Pi and asking it across the network. And please don't forget to restrict access appropriately if you use a separate server. Someone turned off my workplace's power bar (and thus the UPS) and it shut down my notebook across the VPN link. Achim -- 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/d39831202def96786f6e9f9d01328f3e68d4556b.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
> That's odd. You say you are installing 4.01, yet the qubes manager > shows that fedora is only release 26. I thought that Qubes 4.01 had > Fedora 29 in it. > > Mike. Well Mike that could be it; you made me check when you said that, the image I used was "Qubes-R4.0-x86_64.iso" from 11/27/18. I checked the about in qubes itself is 4.0 (R4.0). Looks like I screwed up on which version I created the image from, I wrote down 4.01 but that's not what I used- too much spiked eggnog maybe. Since it doesn't seem to be possible for me to update with the VM's not starting for USB or Net, I will get the latest image and and reinstall to see if there's any issue. Thanks for pointing out my goof, I'll try that today and see if the results are any different! -- 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/4393d381-be6d-4de0-bb4c-57ec26998804%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Fri, 18 Jan 2019 08:14:43 -0800 (PST) Bryce wrote: > On Friday, January 18, 2019 at 11:11:00 AM UTC-5, Mike Keehan wrote: > > Ah, afraid I've run out of ideas now. > > > > I was hoping it was just the iommu not being enabled, but not > > starting any vm at all is not something I've seen before, as long > > as there is enough memory. 16Gb is fine. > > > > Sorry, out of inspiration now, > > > > Mike. > > Thanks anyways Mike. I did manage to attach the pics of memory and > qubes manager at least, in case they're useful for anyone. > That's odd. You say you are installing 4.01, yet the qubes manager shows that fedora is only release 26. I thought that Qubes 4.01 had Fedora 29 in it. Mike. -- 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/20190118163306.3c097104.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
Ah, afraid I've run out of ideas now. I was hoping it was just the iommu not being enabled, but not starting any vm at all is not something I've seen before, as long as there is enough memory. 16Gb is fine. Sorry, out of inspiration now, Mike. -- 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/20190118161056.613bd9e3.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Fwd: Re: [qubes-users] Mirage-Firewall - Trusted in Dom0?
Original Message From: goldsm...@riseup.net Sent: January 18, 2019 3:45:06 PM UTC To: unman Subject: Re: [qubes-users] Mirage-Firewall - Trusted in Dom0? On 2019-01-18 13:52, unman wrote: > On Fri, Jan 18, 2019 at 04:38:56AM -0800, goldsm...@riseup.net wrote: >> On 2019-01-15 15:19, Goldi wrote: >> > I've been happily using Qubes for several years and noticed that >> > several prominent members of the Qubes Team have in the past suggested >> > installing Mirage-Firewall as an alternative to Sys-Firewall. However, >> > I cannot find any reference to MF in the Qubes Docs. >> > I'd like to install Mirage-Firewall, but I have a nagging doubt about >> > whether the code can be trusted. Particularly as it has to been >> > installed in Dom0 >> > What do you guys recommend? Can the MF developer be trusted? >> > >> > https://groups.google.com/d/msgid/qubes-users/21F0DB51-AF5A-4729-8708-14C54BB4C29A%40riseup.net?utm_medium=email_source=footer >> In Nov 2018 a prominent member of the Qubes team; Unman suggested using >> Mirage-Firewall. >> I'd appreciate very much a reply to my earlier query about the integrity >> and reliability of the code/developer of Mirage Firewall >> > > There is a reference in the docs to GSOC potential work: otherwise > you'll find discussions here and in qubes-devel, and there's an open > issue in qubes-issues. > I have no view on the integrity of Thomas - don't know him. His > contributions have been good and he's always seemed helpful and to know > what he's talking about. > You can look at the code yourself and come to view on that: it's > pretty straightforward. > https://github.com/talex5/qubes-mirage-firewall > > I've done some testing, and the firewall works as expected, with no > strange effects I could see. Thank you for responding. I think I'll pass on installing Mirage-Firewall. I'm a user and regretfully not competent to review MF code. I had hoped that any recommendation to install anything in Dom0 would have been first thoroughly assessed by the qubes team. After all, if Dom0 is compromised its as Joanna used to say "game over" -- 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/A088F0AD-EB03-4B4E-AF08-BAE7BC9E8BC9%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote: > On Fri, 18 Jan 2019 07:17:00 -0800 (PST) > scott wrote: > > > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > > Thanks but unfortunately I don't know that issue helps, as those > > > > who were able to resolve it did so by updating which I cannot do > > > > since sys-net fails to start. > > > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , > > > > seems to cover that problem but nothing's mentioned about net & > > > > firewall failing to start. > > > > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > > scott wrote: > > > > > > > > > > > Hello, I apologize in advance if this has already been > > > > > > addressed but searching for "sys-net" & "libxl" give many > > > > > > confusing results, I don't see any that match both not > > > > > > working, and I'm completely new to Qubes. My problem is that > > > > > > after 2 different installs of the same version, 4.01, I keep > > > > > > getting the same problems: When I get into Qubes I cannot > > > > > > update dom0, and sys-net & sys-firewall both fail to start > > > > > > even though my NIC is correctly listed in devices for -net. > > > > > > > > > > > > Basic info: > > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > > Qubes 4.01, sigs checked good. > > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > > described below. Re-installed by DVD thinking I'd muffed > > > > > > something (think I read on reddit that USB installs made from > > > > > > windows had issues) and the behavior is exactly the same. > > > > > > > > > > > > Behavior observed: > > > > > > (anything in [xxx] is me telling you the variation, as I get > > > > > > this for 2 VM's, 2 error codes, etc.) > > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > > * When I attempt to manually start either, I get this error > > > > > > message: "ERROR: Start failed: internal error: libxenlight > > > > > > failed to create new domain 'sys-net' [or sys-firewall], > > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > > timestamps ranging from date of install to today: 1: > > > > > > "[date:time]: libxl: > > > > > > libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: > > > > > > -3" Those errors and nothing else. > > > > > > > > > > > > I've tried to update dom0 by command as found in docs, as > > > > > > well as through GUI without success. I found a page elsewhere > > > > > > that described temporarily putting NIC in firewall or another > > > > > > VM to see if it worked, but I must be doing it wrong as I > > > > > > always get loopback errors when trying to save. It always > > > > > > tells me failed, regardless. No wonder if network isn't > > > > > > working. > > > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, > > > > > > but I can't seem to figure out how to see if the NIC is > > > > > > operational since sys-net isn't working (new to qubes > > > > > > sorry!), however I verified my router is not showing an IP > > > > > > assigned, though link LED is on. > > > > > > > > > > > > If anyone can help me try to figure this out, I'd really > > > > > > appreciate it. I'm still a bit green on linux but I learn > > > > > > fast, I recently gave up on Windows (I hate 10 so much I > > > > > > could scream) so I'm trying to dive in with qubes (deep end > > > > > > of the pool I think) as it best suits my needs with the VM > > > > > > implementation. > > > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how > > > > > > to make USB copy work yet since I've been beating my head on > > > > > > the networking issue. > > > > > > > > > > > > Thanks, and sorry in advance if this duplicated another > > > > > > thread. > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > > > It might give you some pointers. > > > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain > > > > > creation fail: Operation not supported" in google.) > > > > > > > > > > Mike. > > > > > > > > > > > Test whether issue is with NIC by removing the card from sys-net > > > and confirming that sys-firewall starts (after sys-net). > > > Shutdown both. > > > Re-attach NIC to sys-net. > > > Report back. > > > > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > > device to the
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Fri, 18 Jan 2019 07:17:00 -0800 (PST) scott.lewis.engin...@gmail.com wrote: > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > Thanks but unfortunately I don't know that issue helps, as those > > > who were able to resolve it did so by updating which I cannot do > > > since sys-net fails to start. > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , > > > seems to cover that problem but nothing's mentioned about net & > > > firewall failing to start. > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > scott wrote: > > > > > > > > > Hello, I apologize in advance if this has already been > > > > > addressed but searching for "sys-net" & "libxl" give many > > > > > confusing results, I don't see any that match both not > > > > > working, and I'm completely new to Qubes. My problem is that > > > > > after 2 different installs of the same version, 4.01, I keep > > > > > getting the same problems: When I get into Qubes I cannot > > > > > update dom0, and sys-net & sys-firewall both fail to start > > > > > even though my NIC is correctly listed in devices for -net. > > > > > > > > > > Basic info: > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > Qubes 4.01, sigs checked good. > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > described below. Re-installed by DVD thinking I'd muffed > > > > > something (think I read on reddit that USB installs made from > > > > > windows had issues) and the behavior is exactly the same. > > > > > > > > > > Behavior observed: > > > > > (anything in [xxx] is me telling you the variation, as I get > > > > > this for 2 VM's, 2 error codes, etc.) > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > * When I attempt to manually start either, I get this error > > > > > message: "ERROR: Start failed: internal error: libxenlight > > > > > failed to create new domain 'sys-net' [or sys-firewall], > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > timestamps ranging from date of install to today: 1: > > > > > "[date:time]: libxl: > > > > > libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: > > > > > -3" Those errors and nothing else. > > > > > > > > > > I've tried to update dom0 by command as found in docs, as > > > > > well as through GUI without success. I found a page elsewhere > > > > > that described temporarily putting NIC in firewall or another > > > > > VM to see if it worked, but I must be doing it wrong as I > > > > > always get loopback errors when trying to save. It always > > > > > tells me failed, regardless. No wonder if network isn't > > > > > working. > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, > > > > > but I can't seem to figure out how to see if the NIC is > > > > > operational since sys-net isn't working (new to qubes > > > > > sorry!), however I verified my router is not showing an IP > > > > > assigned, though link LED is on. > > > > > > > > > > If anyone can help me try to figure this out, I'd really > > > > > appreciate it. I'm still a bit green on linux but I learn > > > > > fast, I recently gave up on Windows (I hate 10 so much I > > > > > could scream) so I'm trying to dive in with qubes (deep end > > > > > of the pool I think) as it best suits my needs with the VM > > > > > implementation. > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how > > > > > to make USB copy work yet since I've been beating my head on > > > > > the networking issue. > > > > > > > > > > Thanks, and sorry in advance if this duplicated another > > > > > thread. > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > It might give you some pointers. > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain > > > > creation fail: Operation not supported" in google.) > > > > > > > > Mike. > > > > > > > > Test whether issue is with NIC by removing the card from sys-net > > and confirming that sys-firewall starts (after sys-net). > > Shutdown both. > > Re-attach NIC to sys-net. > > Report back. > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > device to the qube (using devices widget) and copy log off system. > > Thanks Mike, here's the results: > * Trying to start the USB VM results in error: ERROR: Start failed: > internal error: libxenlight failed to create new domain 'USBlogs', > see
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 10:17:01 AM UTC-5, scott.lewi...@gmail.com wrote: > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > Thanks but unfortunately I don't know that issue helps, as those who were > > > able to resolve it did so by updating which I cannot do since sys-net > > > fails > > > to start. > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to > > > cover that problem but nothing's mentioned about net & firewall failing to > > > start. > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > scott wrote: > > > > > > > > > Hello, I apologize in advance if this has already been addressed but > > > > > searching for "sys-net" & "libxl" give many confusing results, I > > > > > don't see any that match both not working, and I'm completely new to > > > > > Qubes. My problem is that after 2 different installs of the same > > > > > version, 4.01, I keep getting the same problems: When I get into > > > > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > > > > start even though my NIC is correctly listed in devices for -net. > > > > > > > > > > Basic info: > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > Qubes 4.01, sigs checked good. > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > described below. Re-installed by DVD thinking I'd muffed something > > > > > (think I read on reddit that USB installs made from windows had > > > > > issues) and the behavior is exactly the same. > > > > > > > > > > Behavior observed: > > > > > (anything in [xxx] is me telling you the variation, as I get this for > > > > > 2 VM's, 2 error codes, etc.) > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > * When I attempt to manually start either, I get this error message: > > > > > "ERROR: Start failed: internal error: libxenlight failed to create > > > > > new domain 'sys-net' [or sys-firewall], > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > timestamps ranging from date of install to today: 1: "[date:time]: > > > > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > > > > Those errors and nothing else. > > > > > > > > > > I've tried to update dom0 by command as found in docs, as well as > > > > > through GUI without success. I found a page elsewhere that described > > > > > temporarily putting NIC in firewall or another VM to see if it > > > > > worked, but I must be doing it wrong as I always get loopback errors > > > > > when trying to save. It always tells me failed, regardless. No wonder > > > > > if network isn't working. > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, but I > > > > > can't seem to figure out how to see if the NIC is operational since > > > > > sys-net isn't working (new to qubes sorry!), however I verified my > > > > > router is not showing an IP assigned, though link LED is on. > > > > > > > > > > If anyone can help me try to figure this out, I'd really appreciate > > > > > it. I'm still a bit green on linux but I learn fast, I recently gave > > > > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > > > > dive in with qubes (deep end of the pool I think) as it best suits my > > > > > needs with the VM implementation. > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how to make > > > > > USB copy work yet since I've been beating my head on the networking > > > > > issue. > > > > > > > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > It might give you some pointers. > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain creation > > > > fail: Operation not supported" in google.) > > > > > > > > Mike. > > > > > > > > Test whether issue is with NIC by removing the card from sys-net and > > confirming that > > sys-firewall starts (after sys-net). > > Shutdown both. > > Re-attach NIC to sys-net. > > Report back. > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > device to the qube (using devices widget) and copy log off system. > > Thanks Mike, here's the results: > * Trying to start the USB VM results in error: ERROR: Start failed: internal > error: libxenlight failed to create new domain 'USBlogs', see > /var/log/libvirt/libxl/libxl-driver.log for details (at least
[qubes-users] APC UPS daemon
Hi, all, I'm running R4 on one of my Supermicro AMD boxes, which is plugged into an APC SmartUPS. I installed apcupsd to Dom0 (it's in the Dom0 repos) but the box doesn't seem to see the UPS. It works okay on the same hardware running CentOS 6.5 and KDE--it shows up in the power applet automatically, like a laptop battery. I expect it needs its own dedicated USB controller or something so that it can talk to Dom0, but I can't find anything on it in the docs or on the list archives. Since it's in the repo, I assume that it works--would someone please enlighten me? Thanks BillW -- 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/trinity-fdf6f5b2-a5be-4780-9590-440e32400715-1547824709004%403c-app-mailcom-lxa13. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > Thanks but unfortunately I don't know that issue helps, as those who were > > able to resolve it did so by updating which I cannot do since sys-net fails > > to start. > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to > > cover that problem but nothing's mentioned about net & firewall failing to > > start. > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > scott wrote: > > > > > > > Hello, I apologize in advance if this has already been addressed but > > > > searching for "sys-net" & "libxl" give many confusing results, I > > > > don't see any that match both not working, and I'm completely new to > > > > Qubes. My problem is that after 2 different installs of the same > > > > version, 4.01, I keep getting the same problems: When I get into > > > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > > > start even though my NIC is correctly listed in devices for -net. > > > > > > > > Basic info: > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > Qubes 4.01, sigs checked good. > > > > Install 1 done by USB, created in windows, had same issues as > > > > described below. Re-installed by DVD thinking I'd muffed something > > > > (think I read on reddit that USB installs made from windows had > > > > issues) and the behavior is exactly the same. > > > > > > > > Behavior observed: > > > > (anything in [xxx] is me telling you the variation, as I get this for > > > > 2 VM's, 2 error codes, etc.) > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > * When I attempt to manually start either, I get this error message: > > > > "ERROR: Start failed: internal error: libxenlight failed to create > > > > new domain 'sys-net' [or sys-firewall], > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > When I less the log, I get these errors dozens of time with > > > > timestamps ranging from date of install to today: 1: "[date:time]: > > > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > Operation not supported" 2: "[date:time]: libxl: > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > > > Those errors and nothing else. > > > > > > > > I've tried to update dom0 by command as found in docs, as well as > > > > through GUI without success. I found a page elsewhere that described > > > > temporarily putting NIC in firewall or another VM to see if it > > > > worked, but I must be doing it wrong as I always get loopback errors > > > > when trying to save. It always tells me failed, regardless. No wonder > > > > if network isn't working. > > > > > > > > Under sys-net, I see the correct name and model of my NIC, but I > > > > can't seem to figure out how to see if the NIC is operational since > > > > sys-net isn't working (new to qubes sorry!), however I verified my > > > > router is not showing an IP assigned, though link LED is on. > > > > > > > > If anyone can help me try to figure this out, I'd really appreciate > > > > it. I'm still a bit green on linux but I learn fast, I recently gave > > > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > > > dive in with qubes (deep end of the pool I think) as it best suits my > > > > needs with the VM implementation. > > > > > > > > I'd post the log itself, but I can't seem to figure out how to make > > > > USB copy work yet since I've been beating my head on the networking > > > > issue. > > > > > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > It might give you some pointers. > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain creation > > > fail: Operation not supported" in google.) > > > > > > Mike. > > > > > Test whether issue is with NIC by removing the card from sys-net and > confirming that > sys-firewall starts (after sys-net). > Shutdown both. > Re-attach NIC to sys-net. > Report back. > > > You can extract logs from dom0 by creating a qube with NO netvm, and > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > device to the qube (using devices widget) and copy log off system. Thanks Mike, here's the results: * Trying to start the USB VM results in error: ERROR: Start failed: internal error: libxenlight failed to create new domain 'USBlogs', see /var/log/libvirt/libxl/libxl-driver.log for details (at least I know why I couldn't get it to work the 1 time I tried before OP). * Trying to start -net resulted in the same error, with the NIC removed. * Trying to start -firewall resulted in the error saying -net couldn't start, pointing to libxenlight's log also. Other things I observed again
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott Lewis wrote: > Thanks but unfortunately I don't know that issue helps, as those who were > able to resolve it did so by updating which I cannot do since sys-net fails > to start. > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to > cover that problem but nothing's mentioned about net & firewall failing to > start. > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > scott.lewis.engin...@gmail.com wrote: > > > > > Hello, I apologize in advance if this has already been addressed but > > > searching for "sys-net" & "libxl" give many confusing results, I > > > don't see any that match both not working, and I'm completely new to > > > Qubes. My problem is that after 2 different installs of the same > > > version, 4.01, I keep getting the same problems: When I get into > > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > > start even though my NIC is correctly listed in devices for -net. > > > > > > Basic info: > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > Qubes 4.01, sigs checked good. > > > Install 1 done by USB, created in windows, had same issues as > > > described below. Re-installed by DVD thinking I'd muffed something > > > (think I read on reddit that USB installs made from windows had > > > issues) and the behavior is exactly the same. > > > > > > Behavior observed: > > > (anything in [xxx] is me telling you the variation, as I get this for > > > 2 VM's, 2 error codes, etc.) > > > * Dom0 starts and runs, but -net & -firewall will not. > > > * When I attempt to manually start either, I get this error message: > > > "ERROR: Start failed: internal error: libxenlight failed to create > > > new domain 'sys-net' [or sys-firewall], > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > When I less the log, I get these errors dozens of time with > > > timestamps ranging from date of install to today: 1: "[date:time]: > > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > > Operation not supported" 2: "[date:time]: libxl: > > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > > Those errors and nothing else. > > > > > > I've tried to update dom0 by command as found in docs, as well as > > > through GUI without success. I found a page elsewhere that described > > > temporarily putting NIC in firewall or another VM to see if it > > > worked, but I must be doing it wrong as I always get loopback errors > > > when trying to save. It always tells me failed, regardless. No wonder > > > if network isn't working. > > > > > > Under sys-net, I see the correct name and model of my NIC, but I > > > can't seem to figure out how to see if the NIC is operational since > > > sys-net isn't working (new to qubes sorry!), however I verified my > > > router is not showing an IP assigned, though link LED is on. > > > > > > If anyone can help me try to figure this out, I'd really appreciate > > > it. I'm still a bit green on linux but I learn fast, I recently gave > > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > > dive in with qubes (deep end of the pool I think) as it best suits my > > > needs with the VM implementation. > > > > > > I'd post the log itself, but I can't seem to figure out how to make > > > USB copy work yet since I've been beating my head on the networking > > > issue. > > > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > > > > Similar issues in the past were raised in this bug report - > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > It might give you some pointers. > > > > (I found it by searching for "Qubes libxl_domain_make:domain creation > > fail: Operation not supported" in google.) > > > > Mike. > > Test whether issue is with NIC by removing the card from sys-net and confirming that sys-firewall starts (after sys-net). Shutdown both. Re-attach NIC to sys-net. Report back. You can extract logs from dom0 by creating a qube with NO netvm, and using qvm-copy-to-vm to transfer the log to that qube. Attach USB device to the qube (using devices widget) and copy log off system. -- 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/20190118141657.4bdsdejxhwezeers%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Mirage-Firewall - Trusted in Dom0?
On Fri, Jan 18, 2019 at 04:38:56AM -0800, goldsm...@riseup.net wrote: > On 2019-01-15 15:19, Goldi wrote: > > I've been happily using Qubes for several years and noticed that > > several prominent members of the Qubes Team have in the past suggested > > installing Mirage-Firewall as an alternative to Sys-Firewall. However, > > I cannot find any reference to MF in the Qubes Docs. > > I'd like to install Mirage-Firewall, but I have a nagging doubt about > > whether the code can be trusted. Particularly as it has to been > > installed in Dom0 > > What do you guys recommend? Can the MF developer be trusted? > > > > https://groups.google.com/d/msgid/qubes-users/21F0DB51-AF5A-4729-8708-14C54BB4C29A%40riseup.net?utm_medium=email_source=footer > In Nov 2018 a prominent member of the Qubes team; Unman suggested using > Mirage-Firewall. > I'd appreciate very much a reply to my earlier query about the integrity > and reliability of the code/developer of Mirage Firewall > There is a reference in the docs to GSOC potential work: otherwise you'll find discussions here and in qubes-devel, and there's an open issue in qubes-issues. I have no view on the integrity of Thomas - don't know him. His contributions have been good and he's always seemed helpful and to know what he's talking about. You can look at the code yourself and come to view on that: it's pretty straightforward. https://github.com/talex5/qubes-mirage-firewall I've done some testing, and the firewall works as expected, with no strange effects I could see. -- 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/20190118135237.aoc5mdezlhtvjvt7%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
what procedures did you have to follow to get qubes installed with UEFI? I have the same laptop lenovo thinkpad X1 Carbon gen 6 and after using rufus with 'DD' it installs fine but after it restarts, it seams to load up the system files but goes to a black screen right after. just before you type in your disk password. I have flashed to the most recent bios 1.34. I have USB UEFI BIOS Support Enabled. VT-d is enabled. secure boot is disabled. I am booting UEFI Only with CSM Support disabled. -- 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/5346c1f3-f540-4fa1-8a2a-a0c0b405e284%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
Thanks but unfortunately I don't know that issue helps, as those who were able to resolve it did so by updating which I cannot do since sys-net fails to start. This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to cover that problem but nothing's mentioned about net & firewall failing to start. On Fri, Jan 18, 2019, 07:22 Mike Keehan On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > scott.lewis.engin...@gmail.com wrote: > > > Hello, I apologize in advance if this has already been addressed but > > searching for "sys-net" & "libxl" give many confusing results, I > > don't see any that match both not working, and I'm completely new to > > Qubes. My problem is that after 2 different installs of the same > > version, 4.01, I keep getting the same problems: When I get into > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > start even though my NIC is correctly listed in devices for -net. > > > > Basic info: > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > Qubes 4.01, sigs checked good. > > Install 1 done by USB, created in windows, had same issues as > > described below. Re-installed by DVD thinking I'd muffed something > > (think I read on reddit that USB installs made from windows had > > issues) and the behavior is exactly the same. > > > > Behavior observed: > > (anything in [xxx] is me telling you the variation, as I get this for > > 2 VM's, 2 error codes, etc.) > > * Dom0 starts and runs, but -net & -firewall will not. > > * When I attempt to manually start either, I get this error message: > > "ERROR: Start failed: internal error: libxenlight failed to create > > new domain 'sys-net' [or sys-firewall], > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > When I less the log, I get these errors dozens of time with > > timestamps ranging from date of install to today: 1: "[date:time]: > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > Operation not supported" 2: "[date:time]: libxl: > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > Those errors and nothing else. > > > > I've tried to update dom0 by command as found in docs, as well as > > through GUI without success. I found a page elsewhere that described > > temporarily putting NIC in firewall or another VM to see if it > > worked, but I must be doing it wrong as I always get loopback errors > > when trying to save. It always tells me failed, regardless. No wonder > > if network isn't working. > > > > Under sys-net, I see the correct name and model of my NIC, but I > > can't seem to figure out how to see if the NIC is operational since > > sys-net isn't working (new to qubes sorry!), however I verified my > > router is not showing an IP assigned, though link LED is on. > > > > If anyone can help me try to figure this out, I'd really appreciate > > it. I'm still a bit green on linux but I learn fast, I recently gave > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > dive in with qubes (deep end of the pool I think) as it best suits my > > needs with the VM implementation. > > > > I'd post the log itself, but I can't seem to figure out how to make > > USB copy work yet since I've been beating my head on the networking > > issue. > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > Similar issues in the past were raised in this bug report - > > https://github.com/QubesOS/qubes-issues/issues/3125 > > It might give you some pointers. > > (I found it by searching for "Qubes libxl_domain_make:domain creation > fail: Operation not supported" in google.) > > Mike. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/mGvt8QW2mBQ/unsubscribe. > To unsubscribe from this group and all its topics, 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/20190118122156.4973a340.mike%40keehan.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2B4dudfOdZL6RMom8P3JRTz76xakMiexidUmHFWE0k_HoD8F9w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Mirage-Firewall - Trusted in Dom0?
On 2019-01-15 15:19, Goldi wrote: > I've been happily using Qubes for several years and noticed that > several prominent members of the Qubes Team have in the past suggested > installing Mirage-Firewall as an alternative to Sys-Firewall. However, > I cannot find any reference to MF in the Qubes Docs. > I'd like to install Mirage-Firewall, but I have a nagging doubt about > whether the code can be trusted. Particularly as it has to been > installed in Dom0 > What do you guys recommend? Can the MF developer be trusted? > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > 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/21F0DB51-AF5A-4729-8708-14C54BB4C29A%40riseup.net > [1]. > For more options, visit https://groups.google.com/d/optout. > > > Links: > -- > [1] > https://groups.google.com/d/msgid/qubes-users/21F0DB51-AF5A-4729-8708-14C54BB4C29A%40riseup.net?utm_medium=email_source=footer In Nov 2018 a prominent member of the Qubes team; Unman suggested using Mirage-Firewall. I'd appreciate very much a reply to my earlier query about the integrity and reliability of the code/developer of Mirage Firewall -- 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/a229074dcf38cbaf69477a209e0e58b1%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Physical network adapter vlan
Le vendredi 18 janvier 2019 13:11:05 UTC+1, unman a écrit : > On Fri, Jan 18, 2019 at 02:00:44AM -0800, scarp...@gmail.com wrote: > > Hi, > > After checking the google group and documentation at cannot find any > > information regarding the add of vlan on the public ip of the qubes os. > > In my case i need to add 2 ip address on my physical interface of my > > computer and one if them need to be in vlan. > > > > Any idea or post i miss? > > > > Best regards > > > There have been questions about use of VLANs in the past: you should be > able to search the archive. > Configuring the external interface is no different from using > Network Manager in whatever distribution you are using for sys-net > template. > The Qubes specific part will be connecting your qubes to the relevant IP > addresses. Simple way would be to have two firewall qubes, each > dedicated to one IP, and enforcing separation there. Then allocate your > qubes to the firewalls as appropriate. > If you think that you need to have a qube using *both* IP addresses, > then you might want to think a little more about the security domains > that you have defined, and how you have broken down your work. Not > saying that cant be done (it can), but in almost every case I've seen > it's proved to be unnecessary. > > there should be enough here to get you done. If you need more help > give a little more detail on what you are trying to achieve. Ok, yes having 2 firewall mapping the same ethernet port is a solution, i have to try it. anyway this is to use one LAN for the game and all the rest passing throught another network. I will try asap. 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/d2e33503-86e0-4cae-be02-673d06ecc6c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Thu, 17 Jan 2019 16:42:28 -0800 (PST) scott.lewis.engin...@gmail.com wrote: > Hello, I apologize in advance if this has already been addressed but > searching for "sys-net" & "libxl" give many confusing results, I > don't see any that match both not working, and I'm completely new to > Qubes. My problem is that after 2 different installs of the same > version, 4.01, I keep getting the same problems: When I get into > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > start even though my NIC is correctly listed in devices for -net. > > Basic info: > Dell Optiplex 780, bios= A15 as recommended in HCL. > Qubes 4.01, sigs checked good. > Install 1 done by USB, created in windows, had same issues as > described below. Re-installed by DVD thinking I'd muffed something > (think I read on reddit that USB installs made from windows had > issues) and the behavior is exactly the same. > > Behavior observed: > (anything in [xxx] is me telling you the variation, as I get this for > 2 VM's, 2 error codes, etc.) > * Dom0 starts and runs, but -net & -firewall will not. > * When I attempt to manually start either, I get this error message: > "ERROR: Start failed: internal error: libxenlight failed to create > new domain 'sys-net' [or sys-firewall], > see /var/log/libvirt/libxl/libxl-driver.log for details". > > When I less the log, I get these errors dozens of time with > timestamps ranging from date of install to today: 1: "[date:time]: > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > Operation not supported" 2: "[date:time]: libxl: > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > Those errors and nothing else. > > I've tried to update dom0 by command as found in docs, as well as > through GUI without success. I found a page elsewhere that described > temporarily putting NIC in firewall or another VM to see if it > worked, but I must be doing it wrong as I always get loopback errors > when trying to save. It always tells me failed, regardless. No wonder > if network isn't working. > > Under sys-net, I see the correct name and model of my NIC, but I > can't seem to figure out how to see if the NIC is operational since > sys-net isn't working (new to qubes sorry!), however I verified my > router is not showing an IP assigned, though link LED is on. > > If anyone can help me try to figure this out, I'd really appreciate > it. I'm still a bit green on linux but I learn fast, I recently gave > up on Windows (I hate 10 so much I could scream) so I'm trying to > dive in with qubes (deep end of the pool I think) as it best suits my > needs with the VM implementation. > > I'd post the log itself, but I can't seem to figure out how to make > USB copy work yet since I've been beating my head on the networking > issue. > > Thanks, and sorry in advance if this duplicated another thread. > Similar issues in the past were raised in this bug report - https://github.com/QubesOS/qubes-issues/issues/3125 It might give you some pointers. (I found it by searching for "Qubes libxl_domain_make:domain creation fail: Operation not supported" in google.) Mike. -- 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/20190118122156.4973a340.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Physical network adapter vlan
On Fri, Jan 18, 2019 at 02:00:44AM -0800, scarp...@gmail.com wrote: > Hi, > After checking the google group and documentation at cannot find any > information regarding the add of vlan on the public ip of the qubes os. > In my case i need to add 2 ip address on my physical interface of my computer > and one if them need to be in vlan. > > Any idea or post i miss? > > Best regards > There have been questions about use of VLANs in the past: you should be able to search the archive. Configuring the external interface is no different from using Network Manager in whatever distribution you are using for sys-net template. The Qubes specific part will be connecting your qubes to the relevant IP addresses. Simple way would be to have two firewall qubes, each dedicated to one IP, and enforcing separation there. Then allocate your qubes to the firewalls as appropriate. If you think that you need to have a qube using *both* IP addresses, then you might want to think a little more about the security domains that you have defined, and how you have broken down your work. Not saying that cant be done (it can), but in almost every case I've seen it's proved to be unnecessary. there should be enough here to get you done. If you need more help give a little more detail on what you are trying to achieve. -- 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/20190118121102.zsiwrjbamlawjzoh%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Physical network adapter vlan
Hi, After checking the google group and documentation at cannot find any information regarding the add of vlan on the public ip of the qubes os. In my case i need to add 2 ip address on my physical interface of my computer and one if them need to be in vlan. Any idea or post i miss? Best regards -- 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/4d66b818-aa65-49d4-9be1-f00c7c3dc5cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
