On Mon, 2008-07-14 at 09:59 -0700, Tom Haddon wrote:
> On Thu, 2008-07-10 at 22:41 +0100, Tom Haddon wrote:
> > Hi Folks,
> >
> > I'm trying to switch a guest from using a -xen guest kernel to using an
> > unmodified guest kernel.
>
> > As I understand it, there are a few things that I'd need to do to be
> > able to do this.
> >
> > 1) Install the kernel on the guest itself, and configure grub on the
> > guest itself to boot that kernel
> > 2) Because I need to install grub, I need to switch from using
> > file-based partitions (/dev/hda1) to file-based disks (/dev/hda
> > with /dev/hda1 and /dev/hda2 as a partition within that).
> >
> > I think that what I may need to do is build the whole /dev/hda disk
> > image from scratch, and then mount it as a loopback device, and create
> > the partition layout I want and format the partitions as ext3 and swap
> > respectively. Then I should also mount the current /dev/hda1 image as
> > loopback devices, and then copy everything into the first partition.
> >
> > Then I should be able to change my disk config to:
> >
> > disk = [ 'tap:aio:/srv/xen/domains/dapper/new_disk.img,hda,w' ]
> >
> > I'd then boot into it and install grub, shut it down, change the config
> > to use hvmloader, and then boot again. Does this sound sane?
>
> I was successfully able to do this, and can now boot into the new guest
> with the unmodified kernel. However, networking doesn't work. (I figured
> out how to connect via vnc through an ssh tunnel). In other words, the
> network setup works fine with the -xen kernel, but not with the
> unmodified kernel. Anyone have any ideas why that might be?
I was missing "type:ioemu" and "bridge=xenbr0" from my networking config
section. Seems to be all working now.
Thanks, Tom
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home