On Tuesday, 1 November 2016 21:37:41 UTC+11, Chris Laprise wrote:
>
> On 10/30/2016 12:12 AM, Eric Shelton wrote:
> >
> > Outback Dingo:
> >
> > I am going to repeat a suggestion I made back when I tried helping you
> > out, as it seems like you never tried it and it is a fairly
> > inexpensive, simple, and effective solution.
> >
> > Get rid of the Realtek network adapter.
>
> I agree. Realtek is second-tier and can be a real pain even on Windows,
> depending on the product and version.
>
> Receiving a stamp of "Windows compatible" doesn't make a piece of
> hardware a good example of being "PC compatible" and playing well with
> other OSes. PC compatible doesn't really exist, so it is better to focus
> on brands that are 1) known for quality and 2) have good
> relations/popularity with the FOSS community.
>
>
> @Drew,
>
> Are you still using the Dell T5500? I noticed that Dell certifies it
> (only) for RHEL, which is a server OS. Ubuntu certified a number of Dell
> T-series workstations according to their HCL, but they skipped over the
> T5500 for some reason?
>
>
> https://certification.ubuntu.com/desktop/models/?query=precision&category=Desktop&category=Laptop&level=Any&vendors=Dell
>
>
> One thing you should consider is running with Intel or AMD graphics.
> Nvidia have a bad compatibility record and I wonder if that is the main
> factor in your screensaver lockups.
>
> As for systemd, its not as big or complex as you seem to think. And it
> makes Linux run /much/ better on PCs. I can imagine a future where a
> dom0 Linux has many fewer systemd modules, but not going back to init.
>
> Chris
>
Yes, I still use the T5500. And I'm not changing any time soon.
RHEL = After Fedora / Before CentOS
I don't know why they skipped over it. Maybe they couldn't get one?
It's a great PC... 24 threads, 36 Gb RAM... Can't really go wrong.
I can get more RAM into it too..
I think I can't get any more threads though. But I might be wrong.
Why it locks up, who knows?
The whole PC locks up...
It's something to do with XEN and the Guests.
I have 1 VM that I use to access the forum here, and if I have this one
running over night, sometimes even locks the PC up when I'm just running it
and working.
The VHD and HDD and SSD (s) are not getting full.. I have my script running
on every virtual every 5 minutes to tell me how much space is available,
what VMs are running, the processes that are running and everything else I
can find out. All up, about 15-20 MB worth of logs a day. Compressed, less
than 300kB.
I can't find anything that is out of the ordinary.
I'm thinking of increasing the amount up to every 60 seconds, then if I
can't find anything in that, then every 30 seconds.
But I'm trying different things at the moment.
All I can conclude is it's something in XEN itself that is overloading or
dying or just can't keep up.
I'm not pushing it hard. I only have 5 Guests running all the time, and I
start and stop 10 others at times.
Mostly they use 2 or 4 GB RAM. I don't like balancing, so I have static
since Fedora runs at 4 GB as soon as it starts (when balanced and it has
min of 300 MB and max of 4 GB)
Mostly I have things set at 2 GB, and Windows at 4 GB. If they need more
than 2, I give them 3.. but all depends how hard I'm pushing it...
If 2 threads, then 2 GB RAM. if 4 threads then 4 GB RAM. If 2 threads and
high memory usage applications, then 4 GB.
So I'm not really pushing the Workstation hard.
The lockups, they happen. I don't know why, and I can't find anything in
the logs because the PC does and can't log anything because it's dead.
(Dead as in locked up/ not responding)
Noone here is having this issue. I have 2 of these. 1 isn't having the
issue, 1 is. Mine is having issues, the other one isn't.
They are both almost identicle.
I run my own admin app for Qubes these days, since the qubes-manager is so
ram-heavy and is always consuming more.
At one point I thought it was qubes-manager that was causing the lockups...
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2697 root 20 0 569052 153648 41432 S 0.0 2.0 50:13.29
/usr/bin/X -background none :0 -seat seat0 -auth /var/run/lightdm/root/:0
-nolisten tcp vt1 -novtswitch
1330 root 20 0 1259916 144800 7692 S 0.0 1.9 223:57.19
/usr/sbin/libvirtd
2828 {user} 20 0 1172800 131268 39352 S 0.0 1.7 168:24.17
/usr/bin/python2 /usr/bin/qubes-manager
8113 {user} 20 0 284380 20064 13840 S 0.0 0.3 0:07.70 qtasker
That's the current RAM usage for those things.
qtasker is mine. It does most of the things that qubes-manager does, and
many things that it doesn't.
That top one though...
"usr/bin/X -background none" ... What is that, and why is it so high in
RAM usage?
qubes-manager is almost as high as it..
I use Realtek adaptor because Linux doesn't have the BroadCom drivers, nor
does it know how to use it, nor does XEN pass the device to the guest
properly.
I tried attaching it to a Windows HVM, and I installed the drivers and all,
but the device could not be started.
Yes, it's all plugged in and should work fine. But I want to use it on a
NetVM, Linux.
Realtek works fine and well though. And is completely compatible.
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/c6f3e222-2c30-435a-b2ec-c5b8dd894f78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
