Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Wednesday, January 23, 2019 at 6:29:04 AM UTC-5, Mike Keehan wrote: > > Hi Bryce, > > Glad you got something working for you :) > > This is a good description of the changes in Qubes 4.0 :- >https://www.qubes-os.org/doc/releases/4.0/release-notes/ > > Mike. Thanks 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/f31a100e-afc2-4917-a2fe-1979b499d2cf%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 Saturday, January 19, 2019 at 6:37:47 AM UTC-5, Mike Keehan wrote: > > Ah, what a shame. It does seem as if your iommu is a problem. > > Without any other ideas, the only thing I can suggest is that you try > the latest Qubes 3.2 just to allow you to try out Qubes. It doesn't > require the vt-d stuff, so might work on your box. > > The other thing you can do is try googling for iommu and your cpu > together to see if others have had problems (not necessarily in > Qubes, just in general use). > > Mike. Well, just to put this out there, it seems as if my CPU doesn't support SLAT and maybe that's why (I thought from intel's page it did). Installing the latest 3 stable and I don't get any errors about IOMMU like I did with 4, but just like with 4 I do have to disable vt-d in bios in order to boot to the installer. Unfortunately as soon as I turn vt-d back on, the system goes thru post, I see qubes start to boot and then after a minute (about when I think I'd see the disk password prompt) I get a message from my monitor that the input timing is wrong, which I've never seen on several other operating systems! Wierldy, I was able to reproduce this behavior by turning off vt-d, booting up fully and then was able to update without issues unlike in 4. Rebooted twice without issues, then turned vt-d back on and got the exact same behavior. So I guess I just try out using 3.2 without vt-d. I'll take a look around the users' group, but I don't see any real details on the qubes site for what the key differences are between 3 & 4 are, can anyone point me to something that will tell me how worth it (secure) that it is to use 3.2 instead of replacing hardware to run 4? -- 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/5f726c70-f3cb-4473-8b2f-77fbb7f4e3fd%40googlegroups.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 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: Getting HVM to recognize a Windows 10 "Installation Media" bootable USB for installation
On Monday, March 13, 2017 at 4:26:18 PM UTC-6, Grzesiek Chodzicki wrote: > W dniu poniedziałek, 13 marca 2017 22:18:42 UTC+1 użytkownik > bryce.pa...@gmail.com napisał: > > Some additional information: > > > > vt-x is available and enabled in the BIOS > > vt-d is not available > > Are You sure You used the correct syntax? it's supposed to be > --drive=/dev/sdd (equals sign not a space) Grezesiek, Thanks for responding. I did use spaces. I just tried all the same commands(--cdrom and --hd and --hddisk) with the '=' sign separator as you suggested with the same results unfortunately. I also tried the --drive command with each prefix e.g. 'qvm-start --drive=hd:/dev/sdd win10' with the same results. I'm wondering if I need a custom xen config for this usb to boot. -- 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/489c7c61-2d3f-4c02-a8d3-a9719f30cda1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Getting HVM to recognize a Windows 10 "Installation Media" bootable USB for installation
Some additional information: vt-x is available and enabled in the BIOS vt-d is not available -- 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/765dc218-2b51-48ce-8f38-29cfedc418f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Getting HVM to recognize a Windows 10 "Installation Media" bootable USB for installation
Hi, I recently created a USB bootable installation media from my previous Windows 10 installation using a Microsoft media creation tool. In addition to the installation media, it contains info about my product key somehow. I've done this before moving from HDD to SSD. [dom0] mount /dev/sdd1 /mnt [dom0] ls /mnt Here's the file contents of the base directory of the only partition of the usb: autorun.inf bootmgr bootmgf.efi boot efi MediaMeta.xml setup.exe sources support Fdisk -l tell me that the first and only usb partition (/dev/sdd1) is marked as bootable. The partition type is W95 FAT32 (LBA). My bios also successfully boots into the device. Here's what I've tried so far: [dom0] qvm-create win10 --hvm --label green [dom0] qvm-start --cdrom /dev/sdd win10 [win10] Booting from CD-Rom... 7663MB medium detected CDROM boot failure code : 0005 Boot from CD-Rom failed: could not read the boot disk [dom0] qvm-start --cdrom /dev/sdd1 Same output [dom0] qvm-start --hd /dev/sdd CDROM boot failure code : 0002 .. Boot from Hard Disk failed: not a bootable disk [dom0] qvm-start --hd /dev/sdd1 Same output [dom0] dd if=/dev/sdd of=/windows.img (all the enumerations of trying windows.img) [dom0] dd if=/dev/sdd1 of=/windows_sdd1.img (all the enumerations of trying this image) I've run out of things to try. I cannot boot into the old Windows install to get the product key since I cloned it to a new drive, so I can't go the iso route easily. I'm running Qubes 3.2 with the latest dom0 updates. Can anyone help me get this USB to boot into an HVM? -- 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/31ada190-c075-4f1a-93ce-b71b47743633%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
