Hi,
The default boot parameters of our Vagrant images activate a serial console. The problem is that VirtualBox doesn't enable a serial port by default, and our boxes hang if they really need to use the console, e.g. during relabeling[1] or during the initial configuration required for sealed VM templates (what I'm currently trying for Hyper-V support).
Is anyone using the serial console we provide? If not, I can just remove the console=ttyS0 parameter from the kernel command line. Otherwise, a patch for Image Factory is trivial - I can just the set the port to enabled in the XML file, without the cable connected, and probably move console=tty0 on the last position, so it becomes the active console.
Libvirt and VMware don't cause this problem, because they either have a serial port by default, or pretend it's there if the guest tries to use it. No idea if Hyper-V or Xen default to having a serial port.
I would like to fix this for version 1704, which should be released in the following days.
Regards, Laurențiu
On Wed, May 3, 2017 at 4:58 AM, Laurentiu Pancescu lpancescu@gmail.com wrote:
Is anyone using the serial console we provide?
Not here...
-Jeff
It isn't enabled by default in Hyper-V. It would be easy for me to add though in Vagrant if needed. Let me know.
Sent from a tiny keyboard
On May 3, 2017, at 4:58 AM, Laurentiu Pancescu lpancescu@gmail.com wrote:
Hi,
The default boot parameters of our Vagrant images activate a serial console. The problem is that VirtualBox doesn't enable a serial port by default, and our boxes hang if they really need to use the console, e.g. during relabeling[1] or during the initial configuration required for sealed VM templates (what I'm currently trying for Hyper-V support).
Is anyone using the serial console we provide? If not, I can just remove the console=ttyS0 parameter from the kernel command line. Otherwise, a patch for Image Factory is trivial - I can just the set the port to enabled in the XML file, without the cable connected, and probably move console=tty0 on the last position, so it becomes the active console.
Libvirt and VMware don't cause this problem, because they either have a serial port by default, or pretend it's there if the guest tries to use it. No idea if Hyper-V or Xen default to having a serial port.
I would like to fix this for version 1704, which should be released in the following days.
Regards, Laurențiu
[1] https://bugs.centos.org/view.php?id=13213 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 03/05/17 17:08, Patrick Lang wrote:
It isn't enabled by default in Hyper-V. It would be easy for me to add though in Vagrant if needed. Let me know.
Sent from a tiny keyboard
If there's no guarantee there's a serial port in all Vagrant providers, we should probably not default to activating a serial console - especially since the guests are usually headless and they can hang indefinitely during boot because of this. The images I sent you today don't use the serial console any more.
The Vagrant images v1704 are already released (the build I did this weekend), they are available on cloud.centos.org along with the gpg-signed checksums. Hopefully Atlas will also be updated soon. If we find a solution for Hyper-V, we can probably add it as another provider in this release. It's actually just CentOS Linux 6 holding us back, I hope the latest images fix the NIC renaming problem.
Status update: Patrick confirmed yesterday evening that the experimental sealed images work correctly with Hyper-V. I updated PR #98 on GitHub to produce sealed images without a serial console, and the cico tests with libvirt and VirtualBox passed.
Patrick, many thanks for the help and testing!
On 03/05/17 17:52, Laurentiu Pancescu wrote:
If there's no guarantee there's a serial port in all Vagrant providers, we should probably not default to activating a serial console - especially since the guests are usually headless and they can hang indefinitely during boot because of this. The images I sent you today don't use the serial console any more.
The Vagrant images v1704 are already released (the build I did this weekend), they are available on cloud.centos.org along with the gpg-signed checksums. Hopefully Atlas will also be updated soon. If we find a solution for Hyper-V, we can probably add it as another provider in this release. It's actually just CentOS Linux 6 holding us back, I hope the latest images fix the NIC renaming problem.
On 03/05/17 12:58, Laurentiu Pancescu wrote:
Hi,
The default boot parameters of our Vagrant images activate a serial console. The problem is that VirtualBox doesn't enable a serial port by default, and our boxes hang if they really need to use the console, e.g. during relabeling[1] or during the initial configuration required for sealed VM templates (what I'm currently trying for Hyper-V support).
Is anyone using the serial console we provide? If not, I can just remove the console=ttyS0 parameter from the kernel command line. Otherwise, a patch for Image Factory is trivial - I can just the set the port to enabled in the XML file, without the cable connected, and probably move console=tty0 on the last position, so it becomes the active console.
Libvirt and VMware don't cause this problem, because they either have a serial port by default, or pretend it's there if the guest tries to use it. No idea if Hyper-V or Xen default to having a serial port.
I would like to fix this for version 1704, which should be released in the following days.
the serial console setup is used by various virt stacks to deliver -any- console interface. Its certainly used in the libvirt/kvm world quite a bit.
On 18/05/17 00:50, Karanbir Singh wrote:
the serial console setup is used by various virt stacks to deliver -any- console interface. Its certainly used in the libvirt/kvm world quite a bit.
I had pushed further commits to PR #98 8 days ago, restoring the serial console, but setting tty0 as the default. It works well with VirtualBox on macOS: I can even login on the serial console when networking is broken (only on 7, since 6 doesn't start getty by default - I can add it, if there's interest in that). [2]
I was hoping to release a Hyper-V image in 1704, this is the only thing holding us back - I would appreciate further feedback on PR #98 (or merging into master).
Thanks, Laurențiu
[1] https://github.com/CentOS/sig-cloud-instance-build/pull/98 [2] https://www.laurentiupancescu.com/blog/5913767b/
-
Jeff Sheltren -
Karanbir Singh -
Laurentiu Pancescu -
Patrick Lang