[xenpreview-dev] can't boot existing sles10 domu usingsles10 sp1

[Krysan, Susan]

Thank you very much.  That worked.  I had tried many things and I
thought I had tried that, but obviously I did not.

I definitely need the documentation for updating virtual machines to SP1
as soon as possible, specifically domUs.  I am actually going to attempt
it right now.

Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
 

-----Original Message-----
From: Charles Coffing [mailto:ccoffing at novell.com] 
Sent: Friday, July 27, 2007 1:38 PM
To: xenpreview-dev at forge.novell.com; Krysan, Susan
Cc: Steve Bearnson
Subject: Re: [xenpreview-dev] can't boot existing sles10 domu
usingsles10 sp1

On Fri, Jul 27, 2007 at 11:07 AM, "Krysan, Susan" <KRYSANS at unisys.com>
wrote: 
> On x86_86 machine, I have a sles10 domu that was created using sles10
> gmc and want to start it and then eventually upgrade it to sp1.  When
I
> start it using xm create, I get this warning and error:
> 
>  
> 
> Warning: The bootentry option is deprecated. Use bootargs and pass
> --entry= directly.

Indeed, this is just a warning; you can keep your "bootentry" line as it
is and it still will work.  (But note that the tools in SP1 have been
updated to use "bootargs").

The old "bootentry" line was deprecated because it assumed what
bootloader was being used and rewrote stuff based on that assumption;
"bootargs" assumes nothing and passes its string straight through to the
bootloader.

For reference, the old bootentry line is handled like this:
"<bootargs>" = "--entry=<bootentry>"



> Copy kernel /boot/vmlinuz-xen from hda2 to
> /var/lib/xen/tmp/kernel.j80EnN for booting
> 
> Error: Had a bootloader specified, but can't find disk

Your disks line below looks wrong.  The (virtual) name of your disk is
"sda", but your bootentry line is looking for files on "hda2".

Change "sda" to "hda" and retry.


_However_, even with all that said, be aware that some changes have
occurred regarding how video is done between SLES 10 and SLES 10 SP1.
Once you upgrade your domU to SP1, it will attempt to use the
paravirtual frame buffer instead of the text-only console.  To support
this, you'll need a line like this in your config file:

vfb=['type=vnc,vncunused=1']

(CC-ing Steve; he is preparing the doc that describes updating dom0s and
domUs from SLES 10 to SLES 10 SP1.  When it's ready, it would be good to
post a link on this list...)




> My config file is:
> 
> disk = [ 'file:/home/unisys/sles10-master.img,sda,w' ]
> 
> memory = 256
> 
> vcpus = 4
> 
> builder = 'linux'
> 
> name = 'testmaster'
> 
> vif = [ '' ]
> 
> ip = '10.0.75.100'
> 
> netmask = '255.254.0.0'
> 
> localtime = 0
> 
> on_poweroff = 'destroy'
> 
> on_reboot = 'restart'
> 
> on_crash = 'restart'
> 
> extra = ' TERM=xterm'
> 
> bootloader = '/usr/lib/xen/boot/domUloader.py'
> 
> bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'
> 
>  
> 
> I tried replacing the bootentry statement with:
> 
> bootargs -entry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'
> 
>  
> 
> But then get an error on that line indicating it is invalid.  What
> should the syntax of the bootargs statement be?  Since the deprecation
> message was only I warning I changed the bootargs statement back to
the
> bootentry statement and continued trying to get the domu to boot.
> 
>  
> 
> Any ideas why it can't find the disk?  
> 
> Df shows:
> 
> Filesystem           1K-blocks      Used Available Use% Mounted on
> 
> /dev/sda2            154138904  10644496 143494408   7% /
> 
> udev                   1952024       204   1951820   1% /dev
> 
> So I tried changing the hda2 on the bootentry statement to sda2 and
then
> the boot hangs waiting for device hda2.
> 
>  
> 
> Any help would be appreciated since I cannot get any further.
> 
>  
> 
> Thanks,
> 
> Sue Krysan
> 
> Linux Systems Group
> 
> Unisys Corporation
> 
>  
> 
>