[qubes-devel] Memory balancing issue resurfaced

[Elias Mårtenson]

I'm on Qubes 4, latest updated from testing as of today.

This is about this bug: https://github.com/QubesOS/qubes-issues/issues/3265

The issue is that memory balancing randomly stops working, and I haven't seen 
this issue for a long time (months?) and I though it had been fixed.

That was until just now when then issue happened again. I look at the “Q” menu, 
and every running VM had their memory allocation set to whatever was their 
minimum allowed.

If this happens again, are there any logs or anything like that that I can 
collect in order to make it easier to debug this issue?

-- 
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 qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/a6c5b01e-a47b-4123-860b-442cbc0c60b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] An Admin-API based Vagrant provider: possible/advisable?

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, Mar 19, 2018 at 12:44:31PM -0700, chris.rede...@gmail.com wrote:
> I just discovered Qubes OS--thanks for the great work!  In reading through 
> the docs, I found Qubes OS's upcoming Admin API:
> 
> https://www.qubes-os.org/news/2017/06/27/qubes-admin-api/
> 
> I wonder, does the new Admin API provide the functionality required to 
> implement a Vagrant provider?  Does anyone know, off-hand, if v1.0 of Qubes 
> OS's Admin API is/will be missing any features that a provider implementer 
> would need?
> 
> https://www.vagrantup.com/docs/plugins/providers.html

I don't see there details what really provider needs to provide, besides
vague description of "actions": "It is the secret sauce that makes
providers do the magic they do.". There is also "The full list of
actions requested is listed in the comments of that method on the
superclass.", but I haven't found it anywhere.

Anyway, I'd expect this is a perfect fit for Admin API, purpose of both
mechanisms is very similar and it should be possible to translate from
one to another.

> More, though, I'm still wrapping my head around Qubes OS's 
> compartmentalization model and wonder, do I correctly understand the intent 
> of the API?  Does the Admin API offer a good/advisable path to using Vagrant 
> in Qubes OS?
> 
> Finally, if this is a workable idea, I wonder if a Vagrant driver is already 
> in progress?

I'm not aware of any. But if there is some IMO we should promote it!

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqpoOQACgkQ24/THMrX
1yygFAf+O2Zh64uzvkPt9cYZUs9M3M7fxYrBG4CLhIospPR5KhTWRftJUWo9YNc5
zOVmEglX1JOpVTnv1vnQNShWRY7d+OcEnbGOCjtbOjn8Nn+f3/BSv/BnzY0e+UUD
1ghhuKj3hybqO+o92PJCKDumDBq6MQlP8Q7rHtfTwxW7a3mGFscmk8IpB3FkKSLJ
RlA91B4r5IQUmM2UVALVveH+/XqBGg+bgzdxfQWt8viSwa8YYFCFnsbMKv+TnvZc
sbhoKtJTzDJDBUPvxUmZX4982mECbokqx4DdEGSiKvo3nTmY2V08ssovONMcfOPw
suFy73rwgE0/cXDI84icNUx+nA53tQ==
=cSLd
-END PGP SIGNATURE-

-- 
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 qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20180319201247.GG7364%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-devel] An Admin-API based Vagrant provider: possible/advisable?

[chris . redekop]

I just discovered Qubes OS--thanks for the great work!  In reading through the 
docs, I found Qubes OS's upcoming Admin API:

https://www.qubes-os.org/news/2017/06/27/qubes-admin-api/

I wonder, does the new Admin API provide the functionality required to 
implement a Vagrant provider?  Does anyone know, off-hand, if v1.0 of Qubes 
OS's Admin API is/will be missing any features that a provider implementer 
would need?

https://www.vagrantup.com/docs/plugins/providers.html

More, though, I'm still wrapping my head around Qubes OS's compartmentalization 
model and wonder, do I correctly understand the intent of the API?  Does the 
Admin API offer a good/advisable path to using Vagrant in Qubes OS?

Finally, if this is a workable idea, I wonder if a Vagrant driver is already in 
progress?

Thanks in advance.


-- 
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 qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/535299ca-d16a-4a70-8223-a4ac6be4be41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.