On Sunday, December 4, 2016 at 10:27:19 PM UTC+1, Marek Marczykowski-Górecki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sun, Dec 04, 2016 at 07:49:13AM -0800, Lorenzo Lamas wrote:
> > Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails
> > to start
On Wednesday, December 7, 2016 at 9:01:30 PM UTC+1, eldo...@riseup.net wrote:
> I have exactly the same problem with booting using AEM
> Look at this :
> https://groups.google.com/forum/#!topic/qubes-users/Vs2QDsU1zJQ
You don't mention AEM there. Everything works fine on my machine if I boot
On 2016-12-04 15:49, Lorenzo Lamas wrote:
Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM
fails to start serviceVM's(netVM, usbVM, firewallVM). When the boot
process finally completes, trying to manually launch the VMs through
VM Manager doesn't work either. When I choose to
> > This sounds familiar. Try removing the network devices from sys-net to
> > see if it will start then. Next, re-add the network devices and try
> > starting sys-net again.
> >
> > Chris
> Yes, removing network devices from sys-net makes it possible to start it,
> forgot to re-add them and
On Sunday, December 4, 2016 at 10:27:19 PM UTC+1, Marek Marczykowski-Górecki
wrote:
> What exactly you get when starting sys-net manually? Also, take a look
> at /var/log/libvirt/libxl/libxl-driver.log and
> /var/log/xen/console/hypervisor.log for any related messages. For
> example you can use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Dec 04, 2016 at 07:49:13AM -0800, Lorenzo Lamas wrote:
> Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to
> start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally
> completes, trying to
On 12/04/2016 10:49 AM, Lorenzo Lamas wrote:
Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to
start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally
completes, trying to manually launch the VMs through VM Manager doesn't work
either. When I
Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to
start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally
completes, trying to manually launch the VMs through VM Manager doesn't work
either. When I choose to boot without AEM, everything works as
