Success! Fixed! It was EFI problem and efibootmgr help to fix it (from
UEFI troubleshooting)
On 2020-02-19 20:22, evas...@firemail.cc wrote:
Hello,
After I changed some BIOS settings to boot from flash card on my Qubes
system. Qubes never boot again even though I changed all back.
Strange
Hello,
After I changed some BIOS settings to boot from flash card on my Qubes
system. Qubes never boot again even though I changed all back.
Strange this that I do at bios is visiting "boot options" bios menu. It
give access to navidate to qubes xen.efi file, but not edit. Anyway, not
New version of my Qubes Screenshot Tool
https://github.com/evadogstar/qvm-screenshot-tool/
New features:
- Full log of all uploaded screenshot urls and urls to remove them at dom0 !
- Possible to erase this log from the tool
- Bug fix. No screenshots deleted from dom0 by default.
--
You
Previously have the same problem with 4.19 kernel: cpu freeze at some
point, now the same issue with new 4.19 kernel. I'm already checked the
group and found that other users reported the same behavior. But I think
it will not be superfluous to report this again, because this kernel
update
> Did you notice any other errors around the soft lockup? Try searching
> for them; it would be good to figure out what's causing the lockup, but
> it can be hard to do.
Only one error: all system very unresponsive, :) And as I'm already note 100%
cpu usage by some processes. Also I saw strange
By the way, I got the idea and switched to other tty before login to the
system where Qubes Manager and other tasks start. It give me some time
to use the system. And I found the bug at std error output:
!
wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325]
kernel
Maybe it's possible to return to this emergency mode? System freeze
until Qubes Manager start. It can freeze at 45% or at 91% or at any
point. I see high cpu usage. It freeze because of this. I shutdown it
before at this point and filesystem corrupt. Need the way to access
/boot/efi without
Filesystem corruption is a different issue. In the emergency console,
"fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks,
then "reboot". If that lets you get back into Qubes, DO NOT DO
ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as
previously described.
On 2019-05-26 15:57, 'awokd' via qubes-users wrote:
Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg
it request to run fsch or e2fsck. What I must run first and how?
Then if filesystem will be fixed, how to mount boot to change it? I
guess this emergency console can help me, because dom0
On 2019-05-26 16:32, 'awokd' via qubes-users wrote:
Yes, but be aware that it may mount the boot directory you're looking
to edit underneath a different location, so watch the messages when
you do.
What is correct "mount" command to do this?
And to fix filesystem then...
--
You received
On 2019-05-26 15:57, awokd wrote:
First thing to try is to rollback the dom0 kernel update. If you're
using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change
the default kernel line at the top to point to the previous version
number. Save and reboot. If you're not sure how to do
Okey... keep calm...
Time to time I can use dom0 console without troubles (sudo
qubes-dom0-update also still work by no fix still come :( )
I guess now need to somehow change new kernel to old one?
How to do this? I guess I'm at UEFI mode (new notebook)
1) boot from some qubes installed usb
Hello,
Oh no... :(
After last update (kernel) system almost dead!
It can boot and I have access to dom0 console, but mouse not work and
there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes
eating to much cpu
How to remove last update? How to recover now?
Data is urgent. I
https://i.imgur.com/qnH5JNh.png
Some updates show as always skipped after each qubes-dom0-update run.
How to fix this?
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
Some updates show as always skipped after each qubes-dom0-update run.
How to fix this? i.imgur [DOTCOM] / qnH5JNh [dot] png
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,
> FWIW, I'm not sure when Qubes started enabling ipv6 by default. I > thought
> R4.0 was going to support ipv6 but leave it disabled by default? > Thanks for
> fix. I found it! BTW, I have the same question! I never enable ipv6 and it's
> my old vpn vm! Maybe I'm compromised? All work like a
Hello,
Seems after last whonix update my old VPN VM begin leaking traffic. After
investigation I found that it's because ipv6 primary connection to whonix-gw. I
guess that whonix-gw now supporting ipv6. It leak traffic through ipv6
connection to whonix and ignore my default old ipv4 setup.
Hello,
How to setup networking (internet access) at Android / Qubes 4? Thanks!
2Qubes Devs: thanks for new Qubes Manager :)
--
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
And 2th question:
Do you know how to restore all connections after proxyvm reboot. Yes, it's not
possible to reboot it from qubes manager, but I can reboot it with terminal.
Then, maybe, some simple steps exists to reconnect all AppVMs? This would help
me a lot. It's my simpler to reboot
> If the vif interfaces are going down, that suggests a bug either in
Today it happens again and now I open terminal at ethervpn and write "route".
It freeze, not totally freeze, but it print line by line output of this command
and every line took ~10 seconds to print. Maybe it's because I
> Posting back to qubes-users...
Sorry for direct message. Now, I use web-based mail it set direct answer by
default :(
A little more information. When it goes to "no network state" then I seeing at
my ethervpn with "ip route list" (as I remember) that all vif+ interfaces show
as "down". It
misspelling. Qubes 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
Hello,
I still have issues with my proxy/vpn-vms. Something happens, maybe my vpn lose
connection or not (I don't know). I only know that at some point from timee to
time all my AppVms lose network and it's not possible to restore networking
without restarting VPN-VM and all connected VMs. Any
Hello,
Thanks for new updates!
I got some error with last dom0 update
https://i.imgur.com/yWQD1lp.png
After ~10 minutes of waiting ( I through that update freeze) this:
https://i.imgur.com/diAOG8V.png
How to fix? What to do next?
Thanks
--
You received this message because you are subscribed
Subj. Move windows to workspace N(2) default shortcut Ctrl+alt+2 does not works.
--
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
https://github.com/evadogstar/qvm-screenshot-tool
:-)
--
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
Laszlo Zrubecz, yes, 4.14.18-1 kernel. Seems it's effect me not only one way
(switching networking on the fly), but also affect me in other way...
Or is there some planed networking tasks at proxyvm or AppVM by time?
Laszlo Zrubecz, Thanks, but I do not think that it's keep alive, because I
I do another research. After clean reboot I tried to change "networking"-vm to
another one for my AppVM-client from Qube Manager. Without success. After I do
this I loss my network at App-client and I do not know how to fix it, because
if I manually change "networking"-vm again to the first one
I have trouble with my ProxyVM setup. It's the same VPN Qube (ProxyVM, now
AppVM) from Qubes 3.2. At the previous Q3.2 version it works like a charm for
all day long. With Q4 I noticed that my workground loss connection at all
AppVMs connected to this ProxyVM.
Connection lost after 30/60
Can this be included at Qubes Q4 or at some Qubes repo with tools for quick
installation?
--
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
After restore from Q3.2 buckup I have all network VM doubled with "disp-"
prefix? Why? Is it safe to remove them all? All of them have 0.0 MiB size
reported at Qube manager.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Sorry, I tried other usd drive with NTFS and ExFAT and no results! It does not
mound automatically and I do not know how to mount all this drives. The problem
not only with usb drive, but also with HDD. Maybe my template lack some driver
that support NTFS? Hot to check his? I guess it's
Sorry, send to Unman private. I use web interface now, because all my previous
emails close IMAP support :
Repost to group:
Qubes Reinstalled. I can confirm that at the first step user always lose access
to mouse in case of sys-usb created, but not running.
About not syncing template &
Something strange is going on. I can not run fedora-26 template terminal.
Template is clean 4.0 template, before I only install nano on it. Start/resume
also does not work. I get message about "halted". It's also harder to get the
real state of app vms& templates, because Qubes Manager is
New error:
I guess that I must update template fedora-26 and maybe error will be fixed. At
the end of the process:
Cleanup: . some files and lines ... disk I/O error... Read-only file
system.. Packages: write failed for page 1 etc :(
--
You received this message because you are
I tried to attach (and mount) other usb flash drive (first one was hdd). It
give me the same results:
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the
2all: thanks fro help and answers
Unman, About 5. I attach the disk without any errors from plugin and from
console with qvm-block. After attached I see new device at /dev/xvdi.
"mount /dev/xvdi" and got this:
1) Unclean file system (0, 1)
the file system wasn't safety closed on Windows.
Because I do not have access to Windows disk after I attach it to any Qube it's
impossible for me to migrate, because I can not restore my backup :(
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Hello, Thanks for this great update! I found at the issue tracker that Qubes
Manager from 3.2 was ported to Q4.0 and because of this I thought it is the
time to migrate or try to migrate to new Qubes version.
Issues:
1) After installation done, "usb-qube" does not run. Because of this(?) I
Hello,
Maybe somebody can help me with python3 on fedora 25 template?
There is not google.protobuf package at fedora 25
It's possible to install it with sudo pip3 install protobuf
But it does not load when script call it "import google.protobuf"
Also it can not be loaded with included
> I want to also add that the current address publicly displayed will work
> just fine on Bitcoin Cash, which may be useful to know.
POSSIBLE: NOT
I'm not sure that it's possible to use current Qubes address with the same
private keys at Bitcoin Cash (BCH) network. I guess that this 700 is
3.2 affected? When patch will be 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,
Happy New Year Qubes Community!
Due to high fees and heavy losses to donator at Bitcoin Core (BTC) network I
suggest to at Bitcoin Cash (BCH) donation address as alternative.
Nobody want to donate 50$ and lose 40$ as fees.
Also it's not possible with current Core address to donate low amount
43 matches
Mail list logo
