Memory and network problems

[Chris Willard]

Hello All,

I have installed Qubes 3.2 and am having problems with memory and
networking.

Firstly, Qubes only sees 4GB RAM but I actually have 32GB RAM!

Secondly, networking keeps stopping. I can initially ping (e.g.
4.2.2.1) but then I just get "Destination Host Unreachable" from
the DHCP IP given by my router.

I am installing on a Dell PowerEdge T710 and have added "--
efi=attr=uc" to the boot command.

Any help with these problems would be much appreciated as I would like
to use Qubes as my main operating system.

--
Best regards,
Chris

[Aneer Qadri]

Chris Willard:

>
> Firstly, Qubes only sees 4GB RAM but I actually have 32GB RAM!

What does 'xl info' print next to total_memory and free_memory?

[Aneer Qadri]

Chris Willard:

> Firstly, Qubes only sees 4GB RAM but I actually have 32GB RAM!

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2017-01-30 11:28, Chris Willard wrote:
> Hello All,
>
> I have installed Qubes 3.2 and am having problems with memory
> and networking.
>
> Firstly, Qubes only sees 4GB RAM but I actually have 32GB RAM!
>

If you're basing this conclusion on the dom0 RAM indicator in Qubes VM
Manager, then there's no need to worry. That shows only the amount of
RAM that is allocated to dom0, not the total amount of RAM that Qubes
sees and uses. Qubes automatically and dynamically reallocates your
total RAM to all running VMs (including dom0).

> Secondly, networking keeps stopping. I can initially ping
> (e.g. 4.2.2.1) but then I just get "Destination Host Unreachable"
> from the DHCP IP given by my router.
>

- From which VM are you issuing these pings?

Also, are you sure that it's not a problem with your router?

> I am installing on a Dell PowerEdge T710 and have added
> "-- efi=attr=uc" to the boot command.
>
> Any help with these problems would be much appreciated as I would
> like to use Qubes as my main operating system.
>

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYkVYjAAoJENtN07w5UDAwCcAP/0wc/UdxnB5sBNNCn7z3MFic
banf6CK7xI7RtKWt74H7ho2T7NlzPaK0WU5lMkfuNo8M4e/3WLC290TZqZU5PVR/
AksMIbl23X1YzfPxiW6D2Sbe8PSfxeMkiRkMFxJb5+cvz33Zr3cXqWscEovgZBg6
v2fAJXkowR1ndYCqx2+ffm1lCTUf0fXUt6a/4FFTOdlj1+RjNHUn2AtYqzDScNqQ
Rm0sQRrWLnA2EwQRU948kL4UKT6c//Ucp502KpSgxrTZBOSisO5A1xDOnAFyTItM
e3ZVoWaTfi1LJuL+p3IrFfpzaj+RrmY15vyYlkjYxto2huby/oOIjRqmHapOkXNh
oqXJ4nNG0r3x+a6ysvXHK0LYgAGg6jydZxMVhkXMitsS2hmw3ddueNpEaV61Gb2H
ytX1wkPGIhuDLhMFDY9NNSprW6Nb3KDvcl3oA39IMywucJC3qJsLfux+bRiYu3cx
O96VSNdTqhaoaUBP6EB1BAXOaCn7YNgFnpSY9E40lGUCahBlJADmmrwhBC74w6Gu
DydIUCzrr+GrAUGrgE+CMHjE0Nc9K1Hg0xBu041SjMCt+DoQ4mbBZsC6YshOVmSF
edxUMN0xCN8DvG0+oH/CUwKOX8Rcgdj9NM+xLSw64Zds8K0PL4IEOwhw8ijlO1kt
Rk1Am6TwgToV7WkClZxh
=kHbL
-----END PGP SIGNATURE-----

[Chris Willard]

Hello Andrew,

Wednesday, February 1, 2017, 3:29:46 AM, you wrote:

> - From which VM are you issuing these pings?

I'm pinging from the Untrusted domain as I believe that dom0 has no
networking.

I have other PCs that can access the internet so I know it's working
OK.

I have done a traceroute to 4.2.2.1 which gets to the IP assigned by
my router but no further, I can't ping the router either!

Also there was a "failed to start Load Kernel Modules" when booting.

Hope this makes sense!


--
Best regards,
Chris mailto:ch...@thewillards.co.uk

[raah...@gmail.com]

dom0 has no network by design. A major point of qubes security.

The failed to start load kernel modules message is safe to ignore.

[Aneer Qadri]

Chris Willard:

> Hello Andrew,
>
> Wednesday, February 1, 2017, 3:29:46 AM, you wrote:
>
>> - From which VM are you issuing these pings?
>
> I'm pinging from the Untrusted domain as I believe that dom0 has no
> networking.
>
> I have other PCs that can access the internet so I know it's working
> OK.
>
> I have done a traceroute to 4.2.2.1 which gets to the IP assigned by
> my router but no further, I can't ping the router either!
>
> Also there was a "failed to start Load Kernel Modules" when booting.
>
> Hope this makes sense!
>
>

dom0 has no networking. Other appVMs don't have their own networking
system either unless they're a netVM. You would have to make sure that
the NetVM is propertly detecting your internet connection and then
connect those NetVMs to individual appVMs to connect to the internet in
them.