Pkg xen devel - Sep 2015 - Bug#794071: Bug#794071: "xenconsole: Could not open tty `': No such file or directory" during PV guest boot

Package: xen-utils-common
Version: 4.4.1-9+deb8u1
Severity: normal

Dear Maintainer,

When booting a PV guest (xl create -c /etc/xen/foo.conf), immediately
after pygrub has determined which kernel/initramfs it will use, the
following error messages are logged:

xenconsole: Could not open tty `': No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0]
exited with error status 2

The boot does however continue normally including all expected console
output from the guest. The resulting console is perfectly usable once
the guest's login prompt is reached.

Then, once the console is exited with ctrl-], the terminal settings are
messed up such that no text is echoed and pressing return does not
advance to the next line. Terminal usability can be restored by using
"stty sane" or "reset" at this point.

Searching the web for the above error messages only reveals people who
say that xenconsoled wasn't running, however in this case xenconsoled
*is* running (and the console does work, both continuing from the "xl
create -c ?" and also if connected to with "xl console ?").

Here is an example guest config:

name       = "debtest1"
memory     = 1024
vif        = [ "mac=00:16:5e:00:02:39, ip=192.168.82.225,
vifname=v-debtest1" ]
bootloader = "/usr/lib/xen-default/bin/pygrub"
disk       = [ "phy:/dev/vg/debtest1_xvda,xvda,w",
               "phy:/dev/vg/debtest1_xvdb,xvdb,w", ]

The kernel command line that pygrub will extract is:

linux (kernel <kernel:/boot/vmlinuz-3.16.0-4-amd64>)(ramdisk
<ramdisk:/boot/initrd.img-3.16.0-4-amd64>)(args
"root=UUID=bb7a41e3-67f4-436a-8a80-07ec26573360 ro console=hvc0")

however it happens with all my guests regardless of distribution or
version.

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xen-utils-common depends on:
ii  lsb-base        4.1+Debian13+nmu1
ii  python          2.7.9-1
ii  ucf             3.0030
ii  udev            215-17+deb8u1
ii  xenstore-utils  4.4.1-9+deb8u1

xen-utils-common recommends no packages.

xen-utils-common suggests no packages.

-- Configuration Files:
/etc/xen/scripts/vif-route changed [not included]
/etc/xen/xl.conf changed [not included]

-- no debconf information

On Thu, 2015-07-30 at 09:41 +0000, Andy Smith wrote:
> Package: xen-utils-common
> Version: 4.4.1-9+deb8u1
> Severity: normal
> 
> Dear Maintainer,
> 
> When booting a PV guest (xl create -c /etc/xen/foo.conf), immediately
> after pygrub has determined which kernel/initramfs it will use, the
> following error messages are logged:
> 
> xenconsole: Could not open tty `': No such file or directory
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console 
> child [0] exited with error status 2
This sounds a bit like the issue fixed by
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=39ba2989b10b6a1852e253b204eb010f8e7026f1

Are you able to run a new Xen (either 4.5.1~rc1-1 from experimental or an
upstream version would do) to confirm?

(I've also asked for that commit to be backported upstream, since it is
certainly a fix for something even if not this issue)

Thanks,
Ian.
> 
> The boot does however continue normally including all expected console
> output from the guest. The resulting console is perfectly usable once
> the guest's login prompt is reached.
> 
> Then, once the console is exited with ctrl-], the terminal settings are
> messed up such that no text is echoed and pressing return does not
> advance to the next line. Terminal usability can be restored by using
> "stty sane" or "reset" at this point.
> 
> Searching the web for the above error messages only reveals people who
> say that xenconsoled wasn't running, however in this case xenconsoled
> *is* running (and the console does work, both continuing from the "xl
> create -c ?" and also if connected to with "xl console ?").
> 
> Here is an example guest config:
> 
> name       = "debtest1"
> memory     = 1024
> vif        = [ "mac=00:16:5e:00:02:39, ip=192.168.82.225, vifname=v
> -debtest1" ]
> bootloader = "/usr/lib/xen-default/bin/pygrub"
> disk       = [ "phy:/dev/vg/debtest1_xvda,xvda,w",
>                "phy:/dev/vg/debtest1_xvdb,xvdb,w", ]
> 
> The kernel command line that pygrub will extract is:
> 
> linux (kernel <kernel:/boot/vmlinuz-3.16.0-4-amd64>)(ramdisk 
> <ramdisk:/boot/initrd.img-3.16.0-4-amd64>)(args
"root=UUID=bb7a41e3-67f4
> -436a-8a80-07ec26573360 ro console=hvc0")
> 
> however it happens with all my guests regardless of distribution or
> version.
> 
> -- System Information:
> Debian Release: 8.1
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages xen-utils-common depends on:
> ii  lsb-base        4.1+Debian13+nmu1
> ii  python          2.7.9-1
> ii  ucf             3.0030
> ii  udev            215-17+deb8u1
> ii  xenstore-utils  4.4.1-9+deb8u1
> 
> xen-utils-common recommends no packages.
> 
> xen-utils-common suggests no packages.
> 
> -- Configuration Files:
> /etc/xen/scripts/vif-route changed [not included]
> /etc/xen/xl.conf changed [not included]
> 
> -- no debconf information
> 
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel

Hi Ian,

On Fri, Sep 04, 2015 at 02:27:27PM +0100, Ian Campbell
wrote:
> This sounds a bit like the issue fixed by
>
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=39ba2989b10b6a1852e253b204eb010f8e7026f1
> 
> Are you able to run a new Xen (either 4.5.1~rc1-1 from experimental or an
> upstream version would do) to confirm?
Yes, that fixes the problem for me. I applied the patch to the
current Debian stable "xen" source package and it also fixed the
issue.

Thanks,
Andy

Your message dated Wed, 21 Oct 2015 10:25:55 +0100
with message-id <1445419555.9563.64.camel at debian.org>
and subject line Re: [Pkg-xen-devel] Bug#794071: Bug#794071: "xenconsole:
Could not open tty `': No such file or directory" during PV guest boot
has caused the Debian Bug report #794071,
regarding "xenconsole: Could not open tty `': No such file or
directory" during PV guest boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
794071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794071
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Andy Smith <andy at strugglers.net>
Subject: "xenconsole: Could not open tty `': No such file or
directory" during PV guest boot
Date: Thu, 30 Jul 2015 09:41:17 +0000
Size: 5053
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20151021/b601f139/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Ian Campbell <ijc at debian.org>
Subject: Re: [Pkg-xen-devel] Bug#794071: Bug#794071: "xenconsole: Could not
open tty `': No such file or directory" during PV guest boot
Date: Wed, 21 Oct 2015 10:25:55 +0100
Size: 3467
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20151021/b601f139/attachment-0001.mht>