[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A light VM for testing Xen.


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Wed, 30 Dec 2020 12:39:24 +0000
  • Delivery-date: Wed, 30 Dec 2020 12:40:12 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

Hi,

On Wed, Dec 30, 2020 at 11:49:54AM +0000, Jason Long wrote:
> $ cat /etc/fstab 
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a device; this 
> may
> # be used with UUID= as a more robust way to name devices that works even if
> # disks are added and removed. See fstab(5).
> #
> # <file system>             <mount point>  <type>  <options>  <dump>  <pass>
> UUID=4d7a5a50-9288-424d-a383-2f6888b908a1 /              ext4    defaults   0 
> 1

>From the previous log you posted, the kernel had booted so I think
that pygrub was able to correctly find the guest's kernel and
initramfs.

The guest's kernel also did find its root filesystem (note how it
configured a bunch of things that it would have needed access to
/etc for) but then bailed out at the end saying "errors were found
while checking the disk drive for /." I think that message comes
from the init system.

So I *think* your guest config file is okay (I'd give it a bit more
RAM though), it's finding its root filesystem okay, but maybe your
/etc/fstab above is wrong.

If if I were you I'd check that the filesystem with UUID
4d7a5a50-9288-424d-a383-2f6888b908a1 is actually there, i.e. that
that is its UUID.

For an easier life and to prove the theory I might ensure that
/dev/xvda2 is used for the root in your /etc/fstab. If that worked
then I would try to find out why the UUID was wrong.

I'm not familiar with Lubuntu but it looks like possibly you could
also press "I" to ignore and it might just carry on booting.

Cheers,
Andy



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.