Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what's wrong?

[Mauro <mrsanna1@xxxxxxxxx>]

On 11 February 2011 20:08, Matt Richardson <shortpath@xxxxxxxxx> wrote:
> On Fri, Feb 11, 2011 at 3:38 AM, Mauro <mrsanna1@xxxxxxxxx> wrote:
>> On 11 February 2011 11:12, Henrik Langos <hlangos-xen@xxxxxxxxxxxxxx> wrote:
>>> On Fri, Feb 11, 2011 at 10:04:44AM +0000, Mauro wrote:
> <snip>
>>>> >
>>>> >
>>>> >> I've solved using pygrub.
>>>> >> So it seems that without pygrub I can't run DomUs?
>>>> >
>>>> > You shouldn't have to use pygrub for something that simple.
>>>> >
>>>> > My guess is that there was a lack of communication between the
>>>> > maintainers of xen and xen-tools in regard to the default devices.
>>>> >
>>>>
>>>> mail1.cfg:
>>>>
>>>> bootloader = '/usr/lib/xen-default/bin/pygrub'
>>>>
>>>> vcpus    = '4'
>>>> memory   Â= '2048'
>>>>
>>>> #
>>>> # ÂDisk device(s).
>>>> #
>>>> root    Â= '/dev/xvda2 ro'
>>>> disk    Â= [
>>>> Â Â Â Â Â Â Â Â Â 'phy:/dev/vg00/mail1-disk,xvda2,w',
>>>> Â Â Â Â Â Â Â Â Â 'phy:/dev/vg00/mail1-swap,xvda1,w',
>>>> Â Â Â Â Â Â Â ]
>>>>
>>>>
>>>> #
>>>> # ÂPhysical volumes
>>>> #
>>>>
>>>>
>>>> #
>>>> # ÂHostname
>>>> #
>>>> name    Â= 'mail1'
>>>>
>>>> #
>>>> # ÂNetworking
>>>> #
>>>> vif     = [ 'ip=172.16.10.154,mac=00:16:3E:01:D7:24' ]
>>>>
>>>> #
>>>> # ÂBehaviour
>>>> #
>>>> on_poweroff = 'destroy'
>>>> on_reboot  = 'restart'
>>>> on_crash  Â= 'restart
>>>>
>>>> It's exactly as another DomU that runs with xen 3.2 on a debian lenny 
>>>> machine.
>>>> The only difference is the bootloader = '/usr/lib/xen-default/bin/pygrub'.
>>>
>
> <snip>
>>
>> Ok, you convinced me to use pygrub.
>> I have many doubts on using DomU in a SAN system, but for this I open
>> a new thread.
>>
>
>
> I just got my back up xen machine updated to squeeze and started a new
> guest on it to test the upgrade procedure for the production machine.
> I'm using Dom0's kernel (no pygrub), installed the base system via
> debootstrap and I don't have linux-image-2.6.32-5-xen-amd64 installed
> on the DomU:
>
> rocket.cfg
>
> #-*- mode: python; -*-
> kernel = "/boot/vmlinuz-2.6.32-5-xen-amd64"
> ramdisk = "/boot/initrd.img-2.6.32-5-xen-amd64"
> memory = 2048
> name = "rocket"
> vif = ['bridge=xenbr0']
> disk = ['phy:/dev/debian1/rocket-root,xvda1,w',
> 'phy:/dev/debian1/rocket-home,xvda2,w',
> 'phy:/dev/debian1/rocket-tmp,xvda3,w',
> 'phy:/dev/debian1/rocket-usr,xvda4,w',
> 'phy:/dev/debian1/rocket-var,xvda5,w',
> 'phy:/dev/debian1/rocket-swap,xvda6,w']
> ip = "192.168.1.7"
> netmask = "255.255.0.0"
> gateway = "192.168.1.1"
> hostname = "rocket"
> root = "/dev/xvda1 ro"
> extra = "console=hvc0 xencons=tty clocksource=jiffies"
>
>
> So the short of it is that I can confirm that the set up works without
> pygrub. ÂHowever, I noticed that you specified ext4 in the
> xen-tools.cfg and I have seen elsewhere that people have had trouble
> with the defaults being wrong when file systems other than ext3 are
> specified.
>
I've tried with ext3 too.
I've upgraded only Dom0 from lenny to squeeze while DomUs are all
fresh installations.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users