-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, Sep 06, 2016 at 03:49:49PM +0200, 'Olivier Médoc' via qubes-devel wrote:
> On 09/06/2016 03:07 PM, 'Olivier Médoc' via qubes-devel wrote:
> > On 09/06/2016 11:50 AM, Marek Marczykowski-Górecki wrote:
> >> On Tue, Sep 06, 2016 at 08:01:26AM +0200, 'Olivier Médoc' via
> >> qubes-devel wrote:
> >>> Hello,
> >>> I'm trying to improve the pvgrub2 support for archlinux, but after
> >>> updating my system and the kernel, I cannot successfully boot with
> >>> pvgrub2 anymore.
> >>> The system boot successfully, but all qubes related components are
> >>> failing starting with the error message:
> >>> [ 1.177436] qubesdb-daemon[306]: Cannot get own domid
> >> Looks like it can't talk to xenstore. You can check this manually:
> >>
> >> xenstore-read domid
> > Thanks xenstore apparently is broken, but I wonder why.
>
> Could it be that I use the git HEAD of vmm-xen in Qubes 3.1 ?
Shouldn't matter.
> > Strace shows that it somehow fails when writing the domid on xenbus (The
> > exact same bytes are written on working vms.):
> >
> > rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
> > getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
> > stat("/var/run/xenstored/socket", 0x7ffe5f761770) = -1 ENOENT (No such
> > file or directory)
> > access("/dev/xen/xenbus", F_OK) = 0
> > stat("/dev/xen/xenbus", {st_mode=S_IFCHR|0660, st_rdev=makedev(10, 62),
> > ...}) = 0
> > open("/dev/xen/xenbus", O_RDWR) = 3
> > brk(NULL) = 0x2396000
> > brk(0x23b7000) = 0x23b7000
> > rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f868f37e0b0},
> > {SIG_DFL, [], 0}, 8) = 0
> > write(3, "\2\0\0\0\0\0\0\0\0\0\0\0\6\0\0\0", 16) = 16
> > write(3, "domid\0", 6) = -1 ESRCH (No such process)
> > rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f868f37e0b0}, NULL,
> > 8) = 0
> > close(3) = 0
> > write(2, "xenstore-read: ", 15xenstore-read: ) = 15
> > write(2, "couldn't read path domid", 24couldn't read path domid) = 24
> > write(2, "\n", 1
> > ) = 1
> > close(-1) = -1 EBADF (Bad file descriptor)
> > exit_group(1) = ?
> > +++ exited with 1 +++
> >
> However, xenstore-exists works successfully. And when running strace
> xenstore-exists, I can even see that xenstore-exists reads to domid
> successfully.
>
> So it is apparently a bug in xenstore-read. xenstore-exists seems to use
> transaction ID. Could it be linked to the bug ?
>
> I also found this reference of a kernel bug on the internet:
> https://lkml.org/lkml/2016/8/21/308
Yes, exactly - see my other mail.
- --
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
iQEcBAEBCAAGBQJXzssAAAoJENuP0xzK19csbt4IAIKc+ZNRVNOK19K5iJB0UH+z
c8aWiB1Xq4+JaIBDHWWmEuxfKiNKOzFPms9sRb9SAVTkcR59jOm2Ri66yx6h+lq6
Q/pEFldIQ554Jnd3qZrpcIqyoFn/GUo9YDJb9K1QlDs55Iv0oF8XtZxmS46G9vj+
7cJXgBH5B6eWJOmGKu6ZmQ3eevu2q5JYmtBLvbjQLIpHYi/H3BFO50TLEngBC7mg
WJzfIwOegZhGFY7Jm+1ubcHunxMwLVk6HyT0v0tG4cn0pYYw0PqlG+RqQb53R5pV
THX0iKoh5ivU9GXxMP/fKu7lme53+9U0YHKepm7B0Zok6ld3kcvRVGo6gbfZXgY=
=vHFw
-----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/20160906135615.GV13909%40mail-itl.
For more options, visit https://groups.google.com/d/optout.
