On Saturday, May 20, 2017 at 11:02:52 PM UTC-7, David Seaward wrote:
> Hi,
>
> Previously I've used type II VMs like VirtualBox for application
> testing: install application on the base OS, test features (including
> GUI features, shell integration and system integration), discard
> changes.
On Mon, 2017-05-22 at 05:48 -0700, Matty South wrote:
> > Previously I've used type II VMs like VirtualBox for application
> > testing: install application on the base OS, test features
> > (including
> > GUI features, shell integration and system integration), discard
> > changes. Additional
VirtualBox inside a VM is not going to work, at least not with x64. It might
work with x86 (32b).
Virtualization for x64 generally requires virtualization extensions (VT-x or
so), but they aren't available inside a Qubes VM. Maybe some patches can add
support for it (look for “nested HVM” or
On Sunday, May 21, 2017 at 1:02:52 AM UTC-5, David Seaward wrote:
> Hi,
>
> Previously I've used type II VMs like VirtualBox for application
> testing: install application on the base OS, test features (including
> GUI features, shell integration and system integration), discard
> changes.
On 05/21/2017 02:22 AM, Vít Šesták wrote:
> Getting rid of seamless mode: HVM is one approach, loopback VNC or Xvfb is
> another one.
>
> On pausing VMs: Actually, even if you just suspend and resume the whole
> system, all VMs get unpaused.
>
> Xen actually has some restore capability, at least
Getting rid of seamless mode: HVM is one approach, loopback VNC or Xvfb is
another one.
On pausing VMs: Actually, even if you just suspend and resume the whole system,
all VMs get unpaused.
Xen actually has some restore capability, at least for PVs and maybe also for
HVMs. This one is
On 05/21/2017 12:02 AM, David Seaward wrote:
> Hi,
>
> Previously I've used type II VMs like VirtualBox for application
> testing: install application on the base OS, test features (including
> GUI features, shell integration and system integration), discard
> changes. Additional steps might
