Those were the most important questions, beside memory bought being best for your hardware, which I didn’t digged into yet and would prefer you to answer.
From your answer, you seem to say that the behavior was better with 16gb of ram, same Q4.1 defaults, same laptop, right?
Have you made sure your laptop requirements for maximum memory perf matched the ram modules you bought?
Other then that, I doubt this post will be useful to anybody else having to skim through. I would advise creating another one and flagging mods for suppression of this one, and creating a new one, better named, based on learned experience. What do you think?
You are right. I am senior in recognizing seniors in whining and expecting others to resolve their issues. Here’s my bet from the quote above: if you don’t stop whining and not putting personal effort to resolve your issue while showing that, you won’t resolve this issue and you will eventually blame it on someone/something else: me, @Insurgo, your hardware, and most probably on Qubes or all together, but not yourself.
They use the maximum memory because you have free memory available. If your system has memory to give, any qube you start will be given the maximum memory.
Once you don’t have any more free memory, you will start to see the memory being balanced between the qubes.
as far i understood it should be compatible. crucials website is saying that.
right!
i didnt told you a thing because my guess were nvme is overheating but this guess is now death.
because when my appvms freezed yesterday i rebooted and got the feeling it takes pretty long.
thought ok, nvmes getting slower if they are hot. but this cant be the case today because i got in my living room ~20°C and my laptop were shut down the whole time i were away ~8h
i would say my qubes needs to startup ~5 minutes? i watched the process and its hanging up in the “starting qubes” step
what i also watched is, my sys-usb is set up to start on startup but it doesnt.
is my qubes installation corrupt in some way? am i able to check this?
after the fresh installation (1. reboot ive done after updating qubes) everything were fine, qube started in a normal speed as we are all are used to it.
uh, idk what do you mean precisely but, i would say yes - i googled my cpu model and its saying my cpu is able to get up till 128gb ram.
guess this wouldnt make a difference… seems like enmus cant quit trolling here.
oh nice. why are you here then? my motto is always, treat other as you want to get treated.
if you expecting that other people would fix theyr own problems you are in the wrong forum because as i said - qubes vision is to make qubes usable for everyone.
not for only sys admins.
if you are searching a community like this, switch to arch or gentoo but dont waste our time please.
as insurgo already said - what are you doing doesnt move us forward, this is nonconstructive and doesnt “contribute” to anyone as you was telling it.
this should be a knowledge base for everyone, but got the feeling you arent getting it in any way.
got doubt in your intelligence.
if you cant answer to a post and you didnt got tagged to it, why are you writing here?
i never wrote @enmus please help me, you are the only person who could know that or something like that.
what you are doing is trolling here like a kiddo.
were it so complicated to give an answer like insurgo to explain how ballooning is working?
ok to be fair, renehoj answered it also without any problems. you are the only person who is makes a problem out of it.
hold on, this doesnt make any sense of what youve wrote.
im not whining and im putting in it personal effort. as you were able to see, im always answering you although i could ignore you.
i answered insurgo with all details because he was wanted to help me.
this answeres are also personal effort. i just dont know how to troubleshoot this at the best.
“you wont resolve the issue and you will eventually blame it on someone or something else”
yeah what would be the reason why i wont would fix my issue? i mean my first question about ballooning is “fixed” cause insurgo and renehoj answered it.
so why should i blame it on qubes or someone? seems like you didnt know that because, if you knew that your second post would be something different than, you should disable balancing.
answeres like this would people blame on qubes, because they are thinking memory balancing isnt working and qubes dev team is too dumb to fix it.
but thanks to insurgo that he correct the answer of yours.
and yep, i would blame it on you. because you are in the wrong community.
blaming on insurgo… do you read what you are writing? this wouldnt make sense, why should i ever blame it on someone who was helping me out and put so much effort?
i mean his first answer took him for sure ~10 minutes? maybe longer? maybe shorter?
if anyone doesnt want to help you he would give answers like you. this is gentoo community spirit.
never would blame it on my hardware for no reason, we are troubleshooting here, i cant exclude my hardware here.
insurgo also doesnt because maybe the ram is incompatible with my laptop.
uhm… “or all together”.
you know how that is happening? people who doesnt get good technical understanding, searching for help but dont receive it.
those people are the ones who would blame it on all together.
i know a person who is acting like that because of reasons like you. he searched the web, searched forums, asked in the forums but didnt got help…
but if we all helping those people, they would never blame it on someone.
to be fair, im blaming much on myself, i got anxiety and depression. tried to kill myself for several times.
i know that i be a dumb person who never reached anything in my life.
i just wanted to get some help, but you dont give me one.
was thinking to delete my account on that forum because i thought the community got changed.
but… now insurgo and renehoj answered me to my problems and its just a dumb person… why should i delete it because of 1 person?
if you dont want help, its fine, as you can see, there are more than enough people here who are willing.
so this would be my last answer to you because i hate this toxic behave as you are doing.
i dont need it
just always think: treat other as you want to get treated.
if you ever meet a person like you, you arent allowed to blame him because you treated others also like this.
but anyhow, you are treating everyone like this, i read the gitlab vs github topic and you also discussed with sven about this topic.
and i also didnt liked it how you treated newbie.
as he said, he is a newbie and just curious… anyhow… i got on myself too many problems.
but you know what? i searched also help for my depression and anxiety.
probably you should also search for some help because this behave isnt normal.
thanks, insurgo already told me this
but really, thanks. one thing less to troubleshoot lol
oh btw. you dont using graphene right? then you would also know why people are blaming something.
its because they got misinformation or dont know how it woks.
thats also the reason why we always answer other people. so they could getting smarter and then they would also maybe appreciate some things more.
thats how graphene is always getting blamed from calyx community.
yeah something like freezing, my appvms ui would be pretty unusable - but for all appvms if this happens.
didnt got this problem today…
as example: yesterday i was wanted to switch my tab from youtube to another tab and then it loaded for years
then i got a signal message, was wanted to answer but were unable to send it
thought ok, i would continue work on my browser which loaded for years and werent able to scroll
then i tried to use keepass and this one also hang up.
but as i said, didnt expect it today (till yet).
but boot process is still weird.
didnt start my sys usb qube automatically / boot process hang up shortly.
little update for people who are interested:
using now 55gb ram and didnt got any problems anymore. seems like only this boot problem is still remaining but i could life with it anyhow. maybe i would reinstall qubes one day and check if this would fix my problem but… i dont really care about it atm.
just happy that my qubes is running without any problems
maybe i could find anywhere in the forum a topic similiar to my boot problem / qube starting problem.
again a little update:
today i was wanted to boot qubes and it were unusable for me, wasnt able to open the wifi settings to connect to my wifi.
dom0 as usually still fine.
then i thought, ok, ill reinstall qubes now, maybe its really a corrupt installation.
this problem still exist further.
now i replaced nvme ssd and installed everything and setup everything almost to the state i were and tried to reboot and now the boot time is now like its immediately here.
sys-usb and sys-whonix is also now starting at startup.
would give my nvme back and get the same again, maybe i received a broken one?
but this would be really weird after its wd blue… i mean a company like wd shouldnt send out broken parts?
anyhow, would hold this thread up to date.
if my nvme is getting changed with a new one, hopefully this would be then my last time to setup qubes xD
Hey, it seems like your qubes are using the maximum amount of ram available as you have plenty left. As the available amount decreases, each vm with memory balancing enabled will receive a smaller amount of ram to allow ram for others.
Are you sure the allocated ram in your qubes is actually filing up? or are you just reading the allocated amount from dom0?
I also have qubes running on a 64gb system, a lot of performance depends on your cpu model. If you could report back with this information, I can assist you further.
it should be noted that i’ve also run qubes on a relatively weak i7-6200u setup with 16gb of ram, and frequently had vm crashes when loading far too many at once.
Sorry if this reply isnt that could, answering now via my phone
So no, it aint anymore about the memory
Its pretty sure the nvme
Stock nvme is working well with qubes (512gb).
Today i got into the shop again and let my nvme swap because i thought its broken
Now i build the new one in and… Voila, same issue
To boot qubes takes me ~10 minutes and cant start my sys-net because my qubes is trying to start sys-firewall while sys-net isnt really running (missing the button im the top to conmect with wifi)
I cant stop sys-net while sys-firewall is starting
Is there a known issue with a 2tb nvme on qubes? Maybe the system cant initalize it correctly?
It only could be this anymore
Maybe i would switch to fedora till im able to find a solution for it…
Idk what to do anymore
Oh btw. Tried to start qubes now and i cant type in my password into the login formular because its hanging so much…
With 512gb nvme everything is fine
So weird…
Btw. If im switching while its booting im not able to see something strange there (nothing is failing)
Either Qube Manager isn’t refreshing (close and open it), or qui-domains isn’t refreshing (terminate it, it will auto-restart and you won’t see sys-whonix there anymore).
didnt helped sadly, but it isnt only sys-whonix, it was just in this example, sometimes i also got some troubles with sys-firewall or sys-net which isnt able to start.
also as i said, the boot time is much much longer than with the stock nvme.
if i would replace the wd blue nvme with the stock one everything is “normal” again and pretty fast.
i dont unterstand the difference between those 2 “base” qubes install versions.
my best guess would be atm an initialize problem?
cant shutdown my laptop because it getting stuck at some steps, then i have to press the power button till it get shut downed.
anything is pretty buggy with 2tb nvme
wish i would have a 1tb nvme to see if its really the space.
oh and im getting sometimes qrexec errors if that would help?
but sometimes!!!
my boot duration is always slow and my shutdown duration!
my qubes are also not starting at boot - never
they hang up while starting up (like the whonix example here)
Ok, i saw in the thread QubesOS freeze, crash and reboots some people upgraded kernel with kernel-latest and it got better.
I also done this now.
After the reboot, it seems like all qubes started at boot but… Boot time were ~10 minutes, a pic of proof would follow.
Because i got the feeling nobody is believing me, because nobody were writing anything about it.
