Re: [qubes-users] bind-dirs qubes 4.0.1
> Hi, > > with the current 4.0.1 even the "How does it work?" section as mentioned > here > https://groups.google.com/d/msg/qubes-users/m0qWwToAi8w/phdwx1hSCQAJ > cannot be applied. > > Maybe because the file `bind-dirs.sh` is not available at the described > location anymore? > > A file with the same name would be here `/usr/lib/qubes/init/bind-dirs.sh`. > > Created a template clone from `fedora-29` and installed `Docker CE` into it. > > ``` > curl -fsSL https://get.docker.com -o get-docker.sh > CHANNEL=stable sh get-docker.sh > sudo usermod -aG docker user > sudo systemctl enable docker > ``` > > Shutdown that template and created an appvm from it. > > I added the bind-dir files as described. But it will not create symlinks > or copy existing files. > > In which state the `bind-dir.sh` is running. Maybe docker daemon already > created the files and no initial symlinks can be mounted by the script? > > > Thanks for some hints. > I inovked the script manually ``` sudo /usr/lib/qubes/init/bind-dirs.sh ``` after that it seems to work. -- 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/bf558d91-56f5-9ff0-9649-806f90a3fdf8%40rettig.bayern. For more options, visit https://groups.google.com/d/optout.
[qubes-users] bind-dirs qubes 4.0.1
Hi, with the current 4.0.1 even the "How does it work?" section as mentioned here https://groups.google.com/d/msg/qubes-users/m0qWwToAi8w/phdwx1hSCQAJ cannot be applied. Maybe because the file `bind-dirs.sh` is not available at the described location anymore? A file with the same name would be here `/usr/lib/qubes/init/bind-dirs.sh`. Created a template clone from `fedora-29` and installed `Docker CE` into it. ``` curl -fsSL https://get.docker.com -o get-docker.sh CHANNEL=stable sh get-docker.sh sudo usermod -aG docker user sudo systemctl enable docker ``` Shutdown that template and created an appvm from it. I added the bind-dir files as described. But it will not create symlinks or copy existing files. In which state the `bind-dir.sh` is running. Maybe docker daemon already created the files and no initial symlinks can be mounted by the script? Thanks for some hints. -- 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/c1c001b6-624f-0372-de9f-ec066558f38e%40rettig.bayern. For more options, visit https://groups.google.com/d/optout.
[qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt
Solved with the help of: https://www.qubes-os.org/doc/uefi-troubleshooting/ ``` mapbs=1 noexitboot=1 ``` From: qubes-users@googlegroups.com On Behalf Of Robert Rettig Sent: Wednesday, 9 January 2019 14:38 To: qubes-users@googlegroups.com Subject: [qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt Maybe I should add some options to XEN.CFG? Current File: ``` [global] default=4.14.74-1.pvops.qubes.x86_64 [4.14.74-1.pvops.qubes.x86_64] options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx ucode=scan smt=off kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb quiet ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img ``` Maybe console=vga … ? https://wiki.xen.org/wiki/Xen_EFI From: mailto:qubes-users@googlegroups.com <mailto:qubes-users@googlegroups.com> On Behalf Of Robert Rettig Sent: Wednesday, 9 January 2019 14:31 To: mailto:qubes-users@googlegroups.com Subject: [qubes-users] Qubes OS 4.0.1 fresh install reboot halt Hello, just used the new release https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ For reproduction I always use wipefs to cleanup the target disk before installation. I tested 2 times, because I have another disk in the system. 1. enabled 2. disabled the second disk from BIOS. The target disk is always /dev/sda in both cases. The installation media is transferred to an usb flash storage. The installation proceeds without errors. After clicking on reboot the machine reboots as expected. There is a short info about the Xen Kernel, than screen is blank. The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( “Ctrl Alt PrintScr rseinub” is not working too ). Is it possible to boot the usb flash storage as a rescue media? Otherwise I have some additional rescue media like knoppix … I do not have any hints because the screen is blank. Thanks Robert -- 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 mailto:qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to mailto:qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer. 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 mailto:qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to mailto:qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/AM0PR04MB590637CF500680A13C4FF115D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer. 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/AM0PR04MB5906E25E4DFF44EE108450D7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt
Maybe I should add some options to XEN.CFG? Current File: ``` [global] default=4.14.74-1.pvops.qubes.x86_64 [4.14.74-1.pvops.qubes.x86_64] options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx ucode=scan smt=off kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb quiet ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img ``` Maybe console=vga … ? https://wiki.xen.org/wiki/Xen_EFI From: qubes-users@googlegroups.com On Behalf Of Robert Rettig Sent: Wednesday, 9 January 2019 14:31 To: qubes-users@googlegroups.com Subject: [qubes-users] Qubes OS 4.0.1 fresh install reboot halt Hello, just used the new release https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ For reproduction I always use wipefs to cleanup the target disk before installation. I tested 2 times, because I have another disk in the system. 1. enabled 2. disabled the second disk from BIOS. The target disk is always /dev/sda in both cases. The installation media is transferred to an usb flash storage. The installation proceeds without errors. After clicking on reboot the machine reboots as expected. There is a short info about the Xen Kernel, than screen is blank. The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( “Ctrl Alt PrintScr rseinub” is not working too ). Is it possible to boot the usb flash storage as a rescue media? Otherwise I have some additional rescue media like knoppix … I do not have any hints because the screen is blank. Thanks Robert -- 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<mailto:qubes-users+unsubscr...@googlegroups.com>. To post to this group, send email to qubes-users@googlegroups.com<mailto:qubes-users@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com<https://groups.google.com/d/msgid/qubes-users/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer>. 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/AM0PR04MB590637CF500680A13C4FF115D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes OS 4.0.1 fresh install reboot halt
Hello, just used the new release https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ For reproduction I always use wipefs to cleanup the target disk before installation. I tested 2 times, because I have another disk in the system. 1. enabled 2. disabled the second disk from BIOS. The target disk is always /dev/sda in both cases. The installation media is transferred to an usb flash storage. The installation proceeds without errors. After clicking on reboot the machine reboots as expected. There is a short info about the Xen Kernel, than screen is blank. The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( "Ctrl Alt PrintScr rseinub" is not working too ). Is it possible to boot the usb flash storage as a rescue media? Otherwise I have some additional rescue media like knoppix ... I do not have any hints because the screen is blank. Thanks Robert -- 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/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
RE: [qubes-users] Re: Which parts of qubes-builder are guaranteed to work/supported?
> > > Right now I'm not even getting to centos-7: > > > > > > make get-sources get-sources-extra qubes-vm is stopping at > > > > > > -> Installing core RPM packages... > > > error: Failed dependencies: > > > glibc = 2.28-9.fc29 is needed by > > > glibc-all-langpacks-2.28-9.fc29.x86_64 > > > glibc-common = 2.28-9.fc29 is needed by > > > glibc-all-langpacks-2.28-9.fc29.x86_64 > > > make[1]: *** > > > [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:35: > > > > > > /home/user/qubes-builder/chroot-fc29/home/user/.prepared_base] Error > > > 1 > > > make: *** [Makefile:217: vmm-xen-vm] Error 1 > > > > Different environment. Started with a generic/fedora29 box (see > > https://app.vagrantup.com/generic/boxes/fedora29 ) > > > > Got same error but different reason > > https://pastebin.com/raw/Efi5JQKU > > > > ``` > > E: Failed to fetch > > https://deb.debian.org/debian/pool/main/r/reprepro/reprepro_4.16.0-1_amd64.deb > > GnuTLS recv error (-54): Error in the pull > function. > > > > E: Unable to fetch some archives, maybe run apt-get update or try with > > --fix-missing? > > make[1]: *** > > [/home/vagrant/qubes-builder/qubes-src/builder-debian/Makefile.debian: > > 176: > > /home/vagrant/qubes-builder/chroot-jessie/home/user/.prepared_base] > > Error 100 ``` > > > > How can I resume the broken build? > > > > Obviously you have had some network issue, so downloads have failed for > jessie.(Why Jessie? Latest Whonix is based on stretch.) It doesnt look as if > you > built much (anything) so you should be able to just start the build again. > I recommend breaking the build down to separate distros, rather than building > all at once. Also, you can use make qubes-vm and make template as > separate step. > > If you use a caching proxy upstream from the build device then this helps to > mitigate the pain, and also dramatically speeds up template updates. Since > you are downloading to update templates anyway, why download again to build > (vice versa) The build especially the gcc takes a lot of time. The network issue happened somehow at night. Therefore I asked how to resume and retry the build without building gcc again ... . Normally I would assume if a component like gcc is build upfront that it will be used from later components. To make it more clear what I did. Essentially I followed the rabbit in the documentation from https://www.qubes-os.org/faq/#how-do-i-build-qubes-from-sources to https://www.qubes-os.org/doc/qubes-builder/ to https://www.qubes-os.org/doc/qubes-r3-building/ . Maybe that needs some cleanup and pick up your recommendation "breaking the build down to separate distros"? I choose `qubes` meta target as it should "build all required components in correct order". "List of components is configured in builder.conf. You can also check the current value at the end of make help, or using make build-info." For me that shows up 'gcc vmm-xen core-libvirt core-vchan-xen core-qubesdb linux-utils python-cffi python-xcffib python-sphinx python-pillow python-quamash python-objgraph python-hid python-u2flib-host core-admin core-admin-client core-admin-addon-whonix core-admin-linux core-agent-linux intel-microcode linux-firmware linux-kernel artwork gui-common gui-daemon gui-agent-linux gui-agent-xen-hvm-stubdom vmm-xen-stubdom-linux app-linux-split-gpg app-linux-tor app-thunderbird app-linux-pdf-converter app-linux-img-converter app-linux-input-proxy app-linux-usb-proxy app-linux-snapd-helper app-shutdown-idle app-yubikey app-u2f mgmt-salt mgmt-salt-base mgmt-salt-base-topd mgmt-salt-base-config mgmt-salt-base-overrides mgmt-salt-dom0-qvm mgmt-salt-dom0-virtual-machines mgmt-salt-dom0-update infrastructure meta-packages dbus manager desktop-linux-common desktop-linux-kde desktop-linux-xfce4 desktop-linux-i3 desktop-linux-awesome desktop-linux-manager linux-dom0-updates linux-pvgrub2 linux-gbulb linux-scrypt linux-template-builder installer-qubes-os linux-yum linux-deb antievilmaid xscreensaver builder builder-rpm builder-debian template-whonix' As I wrote https://groups.google.com/d/msgid/qubes-users/AM0PR04MB590621E2E36C66F18DBBB4B8D2B30%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer I would like to rebuild a component which includes my BIOS SLIC information. The changes should be part of `vmm-xen` component. And yes I would like to create the whole ISO with just those changes ... if possible. Currently a fresh install with the original Qubes ISO is not possible for me. I have some trouble to install from USB device (dd'ed the ISO to flash) and I even with external USB DVD. Installer works as expected without errors but after reboot the pc, it show black screen no errors and is haltet (only power switch holding down >=4s is working). -- 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,
[qubes-users] Re: Which parts of qubes-builder are guaranteed to work/supported?
> Right now I'm not even getting to centos-7: > > make get-sources get-sources-extra qubes-vm is stopping at > > -> Installing core RPM packages... > error: Failed dependencies: > glibc = 2.28-9.fc29 is needed by > glibc-all-langpacks-2.28-9.fc29.x86_64 > glibc-common = 2.28-9.fc29 is needed by > glibc-all-langpacks-2.28-9.fc29.x86_64 > make[1]: *** > [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:35: > > /home/user/qubes-builder/chroot-fc29/home/user/.prepared_base] Error 1 > make: *** [Makefile:217: vmm-xen-vm] Error 1 Different environment. Started with a generic/fedora29 box (see https://app.vagrantup.com/generic/boxes/fedora29 ) Got same error but different reason https://pastebin.com/raw/Efi5JQKU ``` E: Failed to fetch https://deb.debian.org/debian/pool/main/r/reprepro/reprepro_4.16.0-1_amd64.deb GnuTLS recv error (-54): Error in the pull function. E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? make[1]: *** [/home/vagrant/qubes-builder/qubes-src/builder-debian/Makefile.debian:176: /home/vagrant/qubes-builder/chroot-jessie/home/user/.prepared_base] Error 100 ``` How can I resume the broken build? -- 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/AM0PR04MB5906AC57B50FAD66EBBC17E5D2880%40AM0PR04MB5906.eurprd04.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes HCL FUJITSU CELSIUS H730
Qubes 4.0 running on the attached machine. Currently I am using some sort of dual boot. Trying to integrate the OEM Windows as a HVM. A qubes-user was already doing this: https://mbrasile.com/cms/index.php/windows-7-oem-on-qubes.html Information seems to be valid for Qubes 3.2 but some essential points are missing which can be updated from https://forums.mydigitallife.net/threads/working-bios-mod-for-ws2008-in-xen-hvm.4437/#post-350284 -- 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/AM0PR04MB590621E2E36C66F18DBBB4B8D2B30%40AM0PR04MB5906.eurprd04.prod.outlook.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-FUJITSU-CELSIUS_H730-20190101-225313.yml Description: Qubes-HCL-FUJITSU-CELSIUS_H730-20190101-225313.yml
