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 <m...@keehan.net wrote: > > > > > > > > > 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 but not sure I detailed enough before: > > * Sys-net won't save with any setting but none for networking, but > > firewall gives me the error that networking is disabled and must be > > enabled, isn't that normal though since that's the network VM? The > > other 4 options give me the same "loops in network are unsupported" > > error for any of 'default (sys-firewall), sys-firewall, sys-net, > > sys-whonix'. > > * Sys-firewall gives me config error that it's connected to sys-net > > which doesn't support firewall (I assume due to above). > > > > Actually, it was unman who suggested looking at the logs:) > > If you set sys-firewall's networking to none, can you start it > successfully? > Do you have enough memory? Use xentop to see how much is free. > Does your bios have vtx and iommu enabled OK? > What VMs startup when you boot apart from dom0? > > Mike.
Weirdly, I replied but it said msg was deleted, perhaps because I posted a link to images of xentop and errors; must not be allowed. * Yes, xentop shows the correct amount of physical memory I think; 15623796k (I have 16g (4x4) installed to this desktop). * With -firewall @ none, it fails to start giving me the libxenlight error for failed to start. * Vt-x & -d are enabled in bios. During install one of the 2 times (by date I think the 1st time via USB install), the installer complained about IOMMU remapping missing, but it installed and boots fine now, not sure if that's cuz I reinstalled via DVD or not. * No VM's other than dom0 will run unfortunately :( -- 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/5f025921-292e-4700-8e16-0f482dc04171%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
