Existing vagrant box stop working.

[Didip Kerabat]

Hi all,

I have this strange issue that I could use a second opinion on.

I have a base OEL Linux vagrant box that has been working for many months that suddenly stopped working this week.

I have tried a few things and nothing works.

The symptom: When I launch vagrant with gui=true, the display went blank right after grub menu is selected. And then Vagrant have a hard time trying to SSH and run provisioning.

Tailing the VBox.log shows that it hangs at this line:
00:00:07.189788 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x1

See:
00:00:00.183823 VMEmt: Halt method global1 (5)
00:00:00.183842 VMEmt: HaltedGlobal1 config: cNsSpinBlockThresholdCfg=2000
00:00:00.183848 Changing the VM state from 'CREATING' to 'CREATED'
00:00:00.190048 SharedFolders host service: Adding host mapping
00:00:00.190071     Host path '/path/to/vm-test', map name 'vagrant', writable, automount=false, create_symlinks=true, missing=false
00:00:00.190235 Changing the VM state from 'CREATED' to 'POWERING_ON'
00:00:00.190269 NAT: set redirect TCP host 127.0.0.1:2213 => guest 10.0.2.15:22
00:00:00.190328 AIOMgr: Endpoints without assigned bandwidth groups:
00:00:00.190333 AIOMgr:     /root/VirtualBox VMs/vm-test_default_1462279970355_15532/box-disk1.vmdk
00:00:00.190567 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:00.190576 Console: Machine state changed to 'Running'
00:00:00.192375 VMMDev: Guest Log: BIOS: VirtualBox 5.0.10
00:00:00.194486 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:00.209289 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:00.209365 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:00.216838 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x1
00:00:00.216948 AHCI#0: Reset the HBA
00:00:00.216999 AHCI#0: Port 0 reset
00:00:00.217490 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 41943040 sectors
00:00:00.217543 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:00.236890 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f303a11d000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x1
00:00:01.014598 NAT: old socket rcv size: 128KB
00:00:01.014626 NAT: old socket snd size: 128KB
00:00:02.705660 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:02.705885 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0023
00:00:02.706463 VMMDev: Guest Log: BIOS: CDROM boot failure code : 0003
00:00:02.706619 VMMDev: Guest Log: BIOS: Boot from CD-ROM failed
00:00:02.706805 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0002
00:00:02.706852 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x1
00:00:02.707653 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:02.710262 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=81
00:00:02.710560 VMMDev: Guest Log: int13_harddisk: function 08, unmapped device for ELDL=81
00:00:02.739104 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f303a11d000 w=640 h=480 bpp=0 cbLine=0x140 flags=0x1
00:00:07.189788 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x1

virtualbox version: 5.0.10r104061

vboxmanage list extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.0.10
Revision:     104061
Edition:     
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption.
VRDE Module:  VBoxVRDP
Usable:       true

vagrant plugin list
vagrant-share (1.1.5, system)
vagrant-vbguest (0.11.0)

Guest OS:
Linux oracle.vagrantup.com 3.8.13-118.4.2.el6uek.x86_64 #2 SMP Tue Mar 22 20:47:10 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux

Guest /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/linux-root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle Linux Server Red Hat Compatible Kernel (2.6.32-573.22.1.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-573.22.1.el6.x86_64 root=/dev/mapper/linux-root ro rd_NO_LUKS rd_LVM_LV=linux/root LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=linux/swap SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet crashkernel=auto
    initrd /initramfs-2.6.32-573.22.1.el6.x86_64.img
title Oracle Linux Server Unbreakable Enterprise Kernel (3.8.13-118.4.2.el6uek.x86_64)
    root (hd0,0)
    kernel /vmlinuz-3.8.13-118.4.2.el6uek.x86_64 root=/dev/mapper/linux-root ro rd_NO_LUKS rd_LVM_LV=linux/root LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=linux/swap SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
    initrd /initramfs-3.8.13-118.4.2.el6uek.x86_64.img
title Oracle Linux Server Unbreakable Enterprise Kernel (3.8.13-98.el6uek.x86_64)
    root (hd0,0)
    kernel /vmlinuz-3.8.13-98.el6uek.x86_64 root=/dev/mapper/linux-root ro rd_NO_LUKS rd_LVM_LV=linux/root LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=linux/swap SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
    initrd /initramfs-3.8.13-98.el6uek.x86_64.img
title Oracle Linux Server Red Hat Compatible Kernel (2.6.32-573.1.1.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-573.1.1.el6.x86_64 root=/dev/mapper/linux-root ro rd_NO_LUKS rd_LVM_LV=linux/root LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=linux/swap SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet crashkernel=auto
    initrd /initramfs-2.6.32-573.1.1.el6.x86_64.img


Both vagrant and virtualbox haven't changed for a while.

The grub of guest OS also has not changed for a while (except that UEK version went up).

The vagrant box itself is versioned, and this particular version has not changed for a while.

I don't see any other errors. vagrant --debug is quite verbose and I don't see anything that stick out as a problem.

Thank you before hand for looking at this problem.

[Alvaro Miranda Aguilera]

Hello,

In a vagrant managed environment, the boxes shouldn't be important, and you are always a vagrant destroy / vagrant up away to recreate a working one.

so I can understand something inside the box is important for you.

What you could do is using virtualbox create a copy of disk, then on a new vm attach this new copy, moutned, and extract the important data.

will be faster than troubleshoot what may have gone wrong

hope this helps

alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/3c018b20-3367-4d75-b692-51d38029c26c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dragon788]

I'm guessing that when the kernel upgraded it went to a version that doesn't work with the tools properly. You should attempt to get an alternate tty by using Ctrl + Alt + F1 (or any of F1-F6) and login as your user. Then using systemctl see if the virtualbox tools are working properly. It could be they removed some of the built in open-vm-tools code or they've enabled something else that is causing issues.

I'd suggest copying your Vagrantfile to another directory and try bringing it up as Alvaro suggested, and if it works then attempting to update and see what might have caused the issue so you can attempt to downgrade the package that is causing issues on your "broken" box.