Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ubuntu VM won't start

Featured Replies

Hi everyone,

 

I have an Ubuntu VM that's been working perfectly for over the last month without any need to touch it.  Yesterday I noticed Couch Potato wasn't working so I rebooted the VM.  Now it's not coming back up.

 

This is what I get when I try to start the VM:

 

root@TowerB:/mnt/cache/domains/ubuntu# xl create ubuntu.cfg -c
Parsing config from ubuntu.cfg
libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.10.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [3601] exited with error status 1
libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -3
libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10
Unable to attach console
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1
root@TowerB:/mnt/cache/domains/ubuntu#

 

 

This is the contents of the referenced bootloader log:

 

root@TowerB:/mnt/cache/domains/ubuntu# less /var/log/xen/bootloader.9.log
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive recordfail
WARNING:root:Unknown image directive load_video
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive knetbsd
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive linux16
WARNING:root:Unknown directive source
WARNING:root:Unknown directive elif
WARNING:root:Unknown directive source
ESC(BESC)0ESC[1;24rESC[m^OESC[?7hESC[?1hESC=ESC[HESC[JESC[?1hESC=ESC[?1lESC>ESC[24;1H^MESC[?1lESC>Traceback (most recent call last):
  File "/usr/lib64/xen/bin/pygrub", line 877, in <module>
    raise RuntimeError, "Unable to find partition containing kernel"
RuntimeError: Unable to find partition containing kernel

 

Here is my config:

 

name = "ubuntu"
bootloader = "pygrub"
#kernel = "/mnt/cache/domains/ubuntu/vmlinuz"
#ramdisk = "/mnt/cache/domains/ubuntu/initrd.gz"
memory = 2048
vcpus = '2'
disk = ['phy:/mnt/cache/domains/ubuntu/ubuntu.img,xvdb,w',]
vif = [ 'mac=00:16:3e:aa:bb:cc,bridge=br0' ]
#extra = "debian-installer/exit/always_halt=true -- console=hvc0"

 

I'm currently running 6.0 Beta 4.  I haven't changed anything for quite some time.  Any thoughts on what might be going on?

 

Any help would be greatly appreciated.

 

Doug

I sometimes see weird issues with VM's not wanting to restart.  Rebooting unRAID usually fixes any of these unexplainable issues.  not sure why, but whenever a VM won't start like I think it should, I reboot unRAID and try again.  Worth a shot.

  • Author

Yeah I had tried that and it didn't work unfortunately.  I was really hoping not to have to fully reconfigure everything, but oh well.  I gave up and deleted the VM, now I'm focusing on using Docker instead.

 

Thanks,

 

Doug

I gave up and deleted the VM, now I'm focusing on using Docker instead.

 

I wish I could install windows 7 in docker!

I gave up and deleted the VM, now I'm focusing on using Docker instead.

 

I wish I could install windows 7 in docker!

You and me both!  That's the only limitation of Linux container tech in general:  only supports Linux :-). That's also one of the reasons that VMs are still relevant.

Windows in KVM works ! :-)

 

not for me, not with GPU passthru :(

  • 3 weeks later...

best guess is that the vm kernel was updated and now xen can't find it - seems to have happened to me today after a vm reboot.

 

after a few searches it looks like it can be fixed by using xe-edit-bootloader (or editing the grub config inside the VM?) but it doesn't look like we have access to that under unraid.

does anyone know/have an alternative we can use from the xl toolset, or any way to mount/edit files in the VM's .img?

 

edit:

 

in case anyone else runs into this, here's what i did to fix it:

 

1) copied xen image file to an ubuntu machine

2) used kpartx to mount the image file as a loopback device

3) mounted the partition

4) edited the grub config file, removing the submenu {} section

5) started the fixed vm image

... any way to mount/edit files in the VM's .img?

 

When I did a silly which stopped an ArchVM booting I simply specified the .img as a second (non boot) disk on another VM.  Use that second VM to make the necessary changes and remove the .img from the second VM.  Bingo!

  • 2 weeks later...

Hi everyone,

 

I have an Ubuntu VM that's been working perfectly for over the last month without any need to touch it.  Yesterday I noticed Couch Potato wasn't working so I rebooted the VM.  Now it's not coming back up.

 

This is what I get when I try to start the VM:

 

root@TowerB:/mnt/cache/domains/ubuntu# xl create ubuntu.cfg -c
Parsing config from ubuntu.cfg
libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.10.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [3601] exited with error status 1
libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -3
libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10
Unable to attach console
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1
root@TowerB:/mnt/cache/domains/ubuntu#

 

 

This is the contents of the referenced bootloader log:

 

root@TowerB:/mnt/cache/domains/ubuntu# less /var/log/xen/bootloader.9.log
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive recordfail
WARNING:root:Unknown image directive load_video
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive knetbsd
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive linux16
WARNING:root:Unknown directive source
WARNING:root:Unknown directive elif
WARNING:root:Unknown directive source
ESC(BESC)0ESC[1;24rESC[m^OESC[?7hESC[?1hESC=ESC[HESC[JESC[?1hESC=ESC[?1lESC>ESC[24;1H^MESC[?1lESC>Traceback (most recent call last):
  File "/usr/lib64/xen/bin/pygrub", line 877, in <module>
    raise RuntimeError, "Unable to find partition containing kernel"
RuntimeError: Unable to find partition containing kernel

 

Here is my config:

 

name = "ubuntu"
bootloader = "pygrub"
#kernel = "/mnt/cache/domains/ubuntu/vmlinuz"
#ramdisk = "/mnt/cache/domains/ubuntu/initrd.gz"
memory = 2048
vcpus = '2'
disk = ['phy:/mnt/cache/domains/ubuntu/ubuntu.img,xvdb,w',]
vif = [ 'mac=00:16:3e:aa:bb:cc,bridge=br0' ]
#extra = "debian-installer/exit/always_halt=true -- console=hvc0"

 

I'm currently running 6.0 Beta 4.  I haven't changed anything for quite some time.  Any thoughts on what might be going on?

 

Any help would be greatly appreciated.

 

Doug

 

All those parse errors in the log file make it seem like it was parsing a shell script instead of a config file.  Are you sure the configuration file is correct?

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.