On Sat, Jun 26, 2010 at 2:46 AM, Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx> wrote:
>>> vif = [ 'bridge=br2' ]
> I added the extra line with the UUID and such and was able to boot the domu.
> However it had no networking other than just localhost. So I also couldn't
> install any other software.
Do you have a "br2" on your domU? Is it the correct bridge?
Usually it's easier to just start with using virb0, whicih provides
NAT Network with DHCP. It should just work.
Another alternative is to run "ifconfig -a" on domU and see if there's
an ethernet device showing. If not, try "lsmod" and "modprobe
xen_netfront". If you already have an ethernet device on domU, it's
simply a matter of configuring it as usual.
>
>>> Is there an easier way to do this than with the "kernel" and
>>> "ramdisk" options? I don't want to deal with the pygrub issue with grub2
>>> unless I just absolutely have to.
>>>
>>
>> - install grub on domU. makes your life easier. The "extra" line above
>> should be whatever that comes after "vmlinuz-2.6.32-22-server" on
>> menu.lst, with the most important ones being "root" and "console"
>> - use pygrub/pv-grub
>>
>>
>
> If I use pygrub and a dedicated /boot as ext3 should I be ok?
If you use dedicated /boot as ext3, AND use grub don domU, AND use
pygrub/pv-grub, it should be OK.
> Or is the
> grub2 being installed on the domu going to rear it's ugly head again?
There was a post Xen 4.0 patch that fixes bug related to grub2-Lucid
combination. Try
http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
As for ext3 vs ext4, AFAIK whether pygrub/pv-grub supports ext4
depends on whether the compiling environment's e2fslib supports ext4
or not. RHEL/Centos by default does not. Since I like to have "/" on
ext4, I compromise by having "/boot" separated as ext3.
> Also,
> how can I install grub on the domu if it won't boot?
for PV domU, you don't REALLY need grub installed. You could just
start with empty /boot (on ext3), and create a file
/boot/grub/menu.lst.
OR, since you can already get domU running using kernel on dom0, you
could just get networking up and install grub the normal way.
>
> When doing the install this way (http) it takes HOURS to complete due to
> some slow internet lines somewhere.
Yeah. And the silly thing is that Ubuntu's installation does not allow
you to specify your own mirror (at least I don't know how) :P
I get around that by:
- locating the closest mirror from me
- add an entry to dom0's /etc/hosts. Something like
IP_OF_MY_MIRROR us.archive.ubuntu.com
- do a "pkill -HUP dnsmasq" on dom0, so the running dnsmasq will pick
up the entry
- set up domU to use virbr0 bridge (whose DNS provided by dnsmasq)
- during domU installation, select "us.archive.ubuntu.com"
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|