Re: [qubes-users] Cannot start qubes-guid
> -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sat, Dec 03, 2016 at 05:22:05PM -, ferd...@sigaint.org wrote: >> Hi >> Each time that I create a new appVM based on whonix-ws, the appVM shows >> a >> message "Error starting VM: Cannot start qubes-guid!", after 30 seconds >> the message leaves and all works normally. This doesn't appear with new >> appVM based on fedora or debian. >> Is it anything that can be considered normal? > > Do applications in such Whonix AppVMs work anyway? How do you start the > VM - from the menu, or "start" button from Qubes Manager? > Is it fresh install, or upgraded from previous Qubes release? > > Also, take a look at guid log - it's in /var/log/qubes/guid.VMNAME.log > (replace VMNAME with actual VM name) - also accessible from Qubes > Manager - right click on the VM). > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYQxXwAAoJENuP0xzK19csdf4H/Aw5RrEHoiKQdqRbIhvCdj0x > ZI180Lwt3OS31EjzNAePrjuhAEmF3cSaoPxgLK+5FnZ+ah2mN6M+YPolN2Q70JYl > Kvp8oplQWdN9FQqe4n0oC/BL5gUFoJJjZ/U8LpD9eAfUrq1urODLj/xWW8tZilg4 > G8sG2dU7QpprAWHAbXil4kpsYVrSgyfXjdVLbts7wafBCIgMtnfAPQhzeKm36yZ7 > fSjoLP9ICGjXBaR0QfU8eTLlltAKcx2ewQgszbk46bIgy8vnoeKtFiAbUyc8YwN2 > nbuS0jCR2rII3tbEY2y8rybenka11gmG0DhmDnrNWdUbFo2NGxoDmxAeONl12Uw= > =jb4m > -END PGP SIGNATURE- > Hi Application in VM works anyway, this message appears only from the first start of the appVM created Start VM from Qubes Manager I reinstalled whonix-ws -- 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/1e34560d88e196684e107028f2e1cae4.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot start qubes-guid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Dec 03, 2016 at 05:22:05PM -, ferd...@sigaint.org wrote: > Hi > Each time that I create a new appVM based on whonix-ws, the appVM shows a > message "Error starting VM: Cannot start qubes-guid!", after 30 seconds > the message leaves and all works normally. This doesn't appear with new > appVM based on fedora or debian. > Is it anything that can be considered normal? Do applications in such Whonix AppVMs work anyway? How do you start the VM - from the menu, or "start" button from Qubes Manager? Is it fresh install, or upgraded from previous Qubes release? Also, take a look at guid log - it's in /var/log/qubes/guid.VMNAME.log (replace VMNAME with actual VM name) - also accessible from Qubes Manager - right click on the VM). - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYQxXwAAoJENuP0xzK19csdf4H/Aw5RrEHoiKQdqRbIhvCdj0x ZI180Lwt3OS31EjzNAePrjuhAEmF3cSaoPxgLK+5FnZ+ah2mN6M+YPolN2Q70JYl Kvp8oplQWdN9FQqe4n0oC/BL5gUFoJJjZ/U8LpD9eAfUrq1urODLj/xWW8tZilg4 G8sG2dU7QpprAWHAbXil4kpsYVrSgyfXjdVLbts7wafBCIgMtnfAPQhzeKm36yZ7 fSjoLP9ICGjXBaR0QfU8eTLlltAKcx2ewQgszbk46bIgy8vnoeKtFiAbUyc8YwN2 nbuS0jCR2rII3tbEY2y8rybenka11gmG0DhmDnrNWdUbFo2NGxoDmxAeONl12Uw= =jb4m -END PGP SIGNATURE- -- 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/20161203185856.GE1145%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot start qubes-guid
Hi Each time that I create a new appVM based on whonix-ws, the appVM shows a message "Error starting VM: Cannot start qubes-guid!", after 30 seconds the message leaves and all works normally. This doesn't appear with new appVM based on fedora or debian. Is it anything that can be considered normal? Thank you -- 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/fe39cce66d08fe93ecb8be0afe338f4e.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot start qubes-guid!
The first thing that I have done On 10/7/2016 at 7:53 PM, "Andrew David Wong" wrote:On 2016-10-07 04:12, illix...@hushmail.com wrote: > Hello > I was updating my whonix-ws but maybe it was reboot and I closed it. > Now I can't start more it and shows up this message > > "Error starting vm: cannot start qubes-guid!" > > Reading some post I run this command > > qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i > -E "error|fail|qubes-gui" > > The result is: > > .host kernel: Could not initialize VPMU for cpu 0, error -95 > .host kernel: dmi: Firmware registration failed. > .host systemd[1]: Failed to insert module 'kdbus" : Function not > implemented > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host kernel: Error: Driver 'pcspkr' is already registered > aborting.. > > Any help is appreciated > Have you tried restarting the host? -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -- 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/20161007200601.C07CFE072B%40smtp.hushmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot start qubes-guid!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-07 04:12, illix...@hushmail.com wrote: > Hello > I was updating my whonix-ws but maybe it was reboot and I closed it. > Now I can't start more it and shows up this message > > "Error starting vm: cannot start qubes-guid!" > > Reading some post I run this command > > qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i > -E "error|fail|qubes-gui" > > The result is: > > .host kernel: Could not initialize VPMU for cpu 0, error -95 > .host kernel: dmi: Firmware registration failed. > .host systemd[1]: Failed to insert module 'kdbus" : Function not > implemented > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host kernel: Error: Driver 'pcspkr' is already registered > aborting.. > > Any help is appreciated > Have you tried restarting the host? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJX9+EkAAoJENtN07w5UDAwp/kP/Aj8FrTBE0JYaUBlG1ZbrUHK 0brEawqgxv/LWSbkruKM1eSPYJ6LD3Ii5mbu19mS15w7VlZKVQRCHaNQgc9gnUBs MQCP7zH/2tYD0FsGd4J+zyTYe7R+AAiKW4FCx+/QkUYQL6H5zCCAz/ZoIbLtHv/y 1EF8MbAL80GtDboL/qxYnv2qzefZ//zuQcIm0LpjBSQPxXUduJYczjusVQT2fz5X Ei0o4XnGhvZ9GWIBv/gNccChiu6Ocsx/Ur8GvZSfGLUMJl5NYVQNmc5jKxcf8KYw +3JFN1EUqN6guambVTQ4q2vulU2EqrmS0Z0Si8UBGTbXTOYXub1MK8yvRV1xBP0O wLN75ZH23dqYK4g4CBJ4+oJ7gbNQFuly1Rog7k1Xbir2eCG2+pfgxWreBaxjwi9C QtredkE/gN4TWVl3uB1XT4hrBQ4Woo+4WFMJzfJlOBoE7Y5gsAbWApkf+dLs5Gyh ez/As/kKWvSdtozaD0gZi2hX0ImCRxg3pQBaUGgwstrywcOv4enBTpiLRwTy/YD9 hwVhY6HMCfgvSAfyHh4PHINVDIt2BgiWKwqh7PHIxsFSGJWqoirZ4gn8d5yzG2iC CNUVTzbwJK7H+3l+dSwL7u7IZvlyzDfrBdE/ozzEnc4Gly3viLv1udIHhnhPE39h ciBg9gu43Nmj8NI/N7ND =fBkn -END PGP SIGNATURE- -- 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/7b67fcb1-4f48-6c64-eab6-cbc2aaf5565b%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot start qubes-guid!
Hello I was updating my whonix-ws but maybe it was reboot and I closed it. Now I can't start more it and shows up this message "Error starting vm: cannot start qubes-guid!" Reading some post I run this command qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i -E "error|fail|qubes-gui" The result is: .host kernel: Could not initialize VPMU for cpu 0, error -95 .host kernel: dmi: Firmware registration failed. .host systemd[1]: Failed to insert module 'kdbus" : Function not implemented .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32 .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32 .host kernel: Error: Driver 'pcspkr' is already registered aborting.. Any help is appreciated -- 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/20161007111253.2011DE06AE%40smtp.hushmail.com. For more options, visit https://groups.google.com/d/optout.
