As I mentioned to Peter, I've been tricky enough to have four
Xen-capable distros on one disk. Each boots and is theoretically capable
of being host or guest.
I've had problems with S* hosts, so I copied my configuration and edited
it to this to see whether RHEL5 Server performs better:
[EMAIL PROTECTED] ~]# egrep '^[a-z ]' /etc/xen/thesecond
memory = 128
name = "SUSE101"
cpus = "" # leave to Xen to pick
vcpus = 1
vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0, vifname=eth0' ]
disk = [ 'phy:hda5,hda5,w' ]
kernel = "/var/lib/xen/boot/vmlinuz-xenpae"
ramdisk = "/var/lib/xen/boot/initrd-xenpae"
dhcp="dhcp"
hostname='syse101'
root = "/dev/hda5"
extra = "vga=6 3"
[EMAIL PROTECTED] ~]#
It boots and I can login etc, but the network does not come up.
Of possible relevance is the fact I'm using DHCP to configure the
network on the host.
Exploration shows that, when the guest comes up, the host's network goes
down: no wonder the guest network does not work.
Worse, when the guest goes down the network does not come up, and no
amount of unplugging & replugging wires, use of ifdown/ifup, fiddling
with dhclient or ifconfig works.
Using rmmod to remove the network driver does work though; after that I
can configure the host network as usual.
I've not tried Client.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Please do not reply off-list
_______________________________________________
rhelv5-beta-list mailing list
rhelv5-beta-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
