Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2017-01-09 Thread Lorenzo Lamas
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 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 
> > expected. Problem remains with the latest Xen 4.6.3-24.
> > It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2
> > 
> > I'm not very familiar with Linux, so if you want logs, please tell me where 
> > to find them.
> 
> 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 `tail -f` while starting sys-net manually, to see
> what messages will show up there:
> 
> sudo tail -f /var/log/libvirt/libxl/libxl-driver.log
> /var/log/xen/console/hypervisor.log
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab

Not trying to be impatient or rude, but do the logs give any useful information?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1bccfe92-d284-4099-ab72-27b0953631a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-07 Thread Lorenzo Lamas
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 
without AEM. Does booting without AEM change things for you?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a30cb05e-17e0-4f08-8dcb-1fd7c67d00ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-07 Thread eldorado

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 boot without AEM,
everything works as expected. Problem remains with the latest Xen
4.6.3-24.
It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2

I'm not very familiar with Linux, so if you want logs, please tell me
where to find them.

In case it may not be related to the new Xen version but some other
update installed at the same time, here is the update history:

Transaction ID : 13
Begin time : Tue Nov 22 19:56:34 2016
Begin rpmdb: 934:24862fb1256d9f648273fa8d88ac172b1a06d3d9
End time   :19:58:15 2016 (101 seconds)
End rpmdb  : 939:d785b8e09d66f2d440768eaa6b01d1e77e21ac7c
User   :  
Return-Code: Success
Command Line   :
--exclude=qubes-template-fedora-23,qubes-template-fedora-24,qubes-template-whonix-ws,qubes-template-whonix-gw,qubes-template-debian-8,
upgrade
Transaction performed with:
Installed dnf-1.1.10-1.fc23.noarch@anaconda/rawhide
Installed rpm-4.13.0-0.rc1.13.fc23.x86_64 @anaconda/rawhide
Packages Altered:
Upgraded glusterfs-3.7.16-1.fc23.x86_64
@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64
@qubes-dom0-cached
Upgraded glusterfs-api-3.7.16-1.fc23.x86_64
@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64
@qubes-dom0-cached
Upgraded glusterfs-client-xlators-3.7.16-1.fc23.x86_64 
@qubes-dom0-cached
Upgrade   3.7.17-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded glusterfs-libs-3.7.16-1.fc23.x86_64   
@qubes-dom0-cached
Upgrade 3.7.17-1.fc23.x86_64   
@qubes-dom0-cached
Upgraded libraw1394-2.1.0-6.fc23.x86_64
@anaconda/rawhide
Upgrade 2.1.2-1.fc23.x86_64
@qubes-dom0-cached
Upgraded qubes-core-dom0-3.2.11-1.fc23.x86_64  
@qubes-dom0-cached
Upgrade  3.2.12-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded qubes-core-dom0-doc-3.2.11-1.noarch   
@qubes-dom0-cached
Upgrade  3.2.12-1.noarch   
@qubes-dom0-cached
Upgraded qubes-db-3.2.1-1.fc23.x86_64  
@anaconda/rawhide
Upgrade   3.2.3-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded qubes-db-dom0-3.2.1-1.fc23.x86_64 
@anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded qubes-db-libs-3.2.1-1.fc23.x86_64 
@anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-datetime-plugin-0.6.2-6.fc23.x86_64 
@anaconda/rawhide
Upgrade0.7.0-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-diskperf-plugin-2.5.5-2.fc23.x86_64 
@anaconda/rawhide
Upgrade2.6.0-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-fsguard-plugin-1.0.2-2.fc23.x86_64  
@anaconda/rawhide
Upgrade   1.1.0-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded xfce4-systemload-plugin-1.1.2-3.fc23.x86_64   
@anaconda/rawhide
Upgrade  1.2.0-1.fc23.x86_64   
@qubes-dom0-cached
Upgraded quota-1:4.02-5.fc23.x86_64
@anaconda/rawhide
Upgrade1:4.02-6.fc23.x86_64
@qubes-dom0-cached
Upgraded quota-nls-1:4.02-5.fc23.noarch
@anaconda/rawhide
Upgrade1:4.02-6.fc23.noarch
@qubes-dom0-cached
Upgraded libpng-2:1.6.23-1.fc23.x86_64 
@anaconda/rawhide
Upgrade 2:1.6.26-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-hvm-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-hypervisor-2001:4.6.1-20.fc23.x86_64  
@anaconda/rawhide
Upgrade 2001:4.6.3-21.fc23.x86_64  
@qubes-dom0-cached
Upgraded xen-libs-2001:4.6.1-20.fc23.x86_64
@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64
@qubes-dom0-cached
Upgraded xen-licenses-2001:4.6.1-20.fc23.x86_64
@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64
@qubes-dom0-cached
Upgraded xen-runtime-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached

Scriptlet output:
   1 sed: can't read /etc/sysconfig/prelink: No such file 

Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-07 Thread Lorenzo Lamas
> > 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 try again, I'll do that later.

If I re-add them, it is again unable to start.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/78a3dc83-1ac5-41cf-a230-074d09bb1fcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-05 Thread Lorenzo Lamas
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 `tail -f` while starting sys-net manually, to see
> what messages will show up there:
> 
> sudo tail -f /var/log/libvirt/libxl/libxl-driver.log

It says cannot create qrexec-daemon.
During boot it says "Failed to start Qubes NetVM startup" and "Failed to start 
Start Qubes VM sys-net"(and some more for the other serviceVMs)

This is the log from libxl-driver.log:

[user@dom0 ~]$ sudo tail -f /var/log/libvirt/libxl/libxl-driver.log
2016-12-05 17:24:33 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :23:00.0
2016-12-05 17:24:33 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :23:00.2
2016-12-05 17:24:43 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:24:43 CET libxl: error: libxl_pci.c:1321:do_pci_remove: 
xc_physdev_unmap_pirq irq=16: Invalid argument
2016-12-05 17:24:54 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:24:54 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :23:00.0
2016-12-05 17:25:04 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:25:04 CET libxl: error: libxl_pci.c:1321:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2016-12-05 17:25:04 CET libxl: error: libxl_pci.c:1047:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :23:00.2
2016-12-05 17:25:14 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/4/0 not ready
2016-12-05 17:29:34 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/5/0 not ready
2016-12-05 17:29:45 CET libxl: error: 
libxl_device.c:1269:libxl__wait_for_backend: Backend 
/local/domain/0/backend/pci/5/0 not ready

and hypervisor.log:
[user@dom0 ~]$ sudo tail -f /var/log/xen/console/hypervisor.log
(XEN) 81c03f30 81d53c6a 3e55772b4f5cc499
(XEN) 81c03f60 81c03f5c 
(XEN) 81c03f40 81d53339 81c03ff8
(XEN)81d56b96 000206a7 000103100800 1f898b75
(XEN)   
(XEN)   
(XEN)   
(XEN)   
(XEN)   00010102464c457f
(XEN) 0001003e0003 09b0 0040
(XEN) d6v0 Unhandled invalid opcode fault/trap [#6, ec=]
(XEN) domain_crash_sync called from entry.S: fault at 82d08022c643 
create_bounce_frame+0x12b/0x13a
(XEN) Domain 6 (vcpu#0) crashed on cpu#3:
(XEN) [ Xen-4.6.3  x86_64  debug=n  Not tainted ]
(XEN) CPU:3
(XEN) RIP:e033:[]
(XEN) RFLAGS: 0292   EM: 1   CONTEXT: pv guest (d6v0)
(XEN) rax:    rbx: 00012c00   rcx: 
(XEN) rdx: 81a3f810   rsi: 003f   rdi: 
(XEN) rbp: 81c03e70   rsp: 81c03da8   r8:  0011
(XEN) r9:  0168   r10: 0001   r11: 
(XEN) r12: 000a9b00   r13: 8000   r14: 000111d0
(XEN) r15: 0011   cr0: 80050033   cr4: 000426e0
(XEN) cr3: 000333409000   cr2: 
(XEN) ds:    es:    fs:    gs:    ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=81c03da8:
(XEN)  81d57b3a 0001e030
(XEN)00010092 81c03de8 e02b 81d57b3a
(XEN)81df7920   81c03e10
(XEN)0001 00111d00 00012c00 12c0
(XEN)7ff081c03e88 0013 81dfc020 db3d2ed3ec447c09
(XEN)0100 81c03f00 81df7920 
(XEN) 81c03e88 81d5e406 0100
(XEN)81c03ef0 81d5bd08 0010 81c03f00
(XEN)81c03eb8 db3d2ed3ec447c09 697a696c61697469 db3d2ed3ec447c09
(XEN)  

Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-04 Thread Marek Marczykowski-Górecki
-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 manually launch the VMs through VM Manager doesn't work 
> either. When I choose to boot without AEM, everything works as expected. 
> Problem remains with the latest Xen 4.6.3-24.
> It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2
> 
> I'm not very familiar with Linux, so if you want logs, please tell me where 
> to find them.

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 `tail -f` while starting sys-net manually, to see
what messages will show up there:

sudo tail -f /var/log/libvirt/libxl/libxl-driver.log
/var/log/xen/console/hypervisor.log

- -- 
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYRIoyAAoJENuP0xzK19csBTEH/AtfVWEDUUToA/MLt2sLxbmc
wW2fhRsegzJNKNZhBDmXlZw1Oa+B7oFqVL5o1lFrCrvpwXhNatL3GV78XBK2hI/F
sWi6Yi/WkAz68I71dKWX9ixKY1/UZxXhf8Cl6pnFWmFBeyePL/U/vLtFG7mR2qNd
MTP/7jnKsKBJMsuwvX2Maa0EJe+apjetgmSyCybvFw/Sgvozc2NEDKyxJhMn82Ss
Na9MTNbN6CB5RA/5jPpU0ppS0EO3GH4TfN9AGBPWLimdvJkObgJmtCOHweSHn6h2
Dpm+eL78UTqHN7HNrAifi9rufEzz0yeAMXYfXRi1Nj/Oa9QD/IxUYBcY6ewsWAc=
=02Xd
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20161204212713.GS1145%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-04 Thread Chris Laprise

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 choose to boot without AEM, everything works as expected. 
Problem remains with the latest Xen 4.6.3-24.
It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2

I'm not very familiar with Linux, so if you want logs, please tell me where to 
find them.

In case it may not be related to the new Xen version but some other update 
installed at the same time, here is the update history:



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

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/aaf2e564-a506-9e4b-1ee7-e01c77192467%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.