nevermind. I just got it working. Mods, if you''re reading, you
don''t have
to allow this one through :)
I just created a link from feisty.d to edgy.d in the /usr/lib/xen-tools
directory, recreated the system, and it worked perfectly. Odd.
On 9/1/07, Richard Pickler <rpickler@gmail.com>
wrote:>
> I''m trying to run Xen on Ubuntu Feisty AMD64, but I''m
running into some
> serious walls, and they''re giving me a headache.
>
> * I started off with a clean install of feisty server and installed
> ubuntu-xen-desktop-amd64 (why is the regular xen-server package not
> available on amd64?)
> * I created a ubuntu edgy image as instructed by some howto I read with an
> lvm partition. (some people get the feisty config, I did not, is there no
> way to debrootstrap feisty?)
> * I boot it up and get no login. I''m guessing my connection to
the
> console is getting messed up somewhere.
> * In the console it appears the network and the ssh server have started,
> but it does not appear the domU''s network is actually getting an
ip (My
> router confirms this).
>
> So, it boots, but I have no way of actually interacting with it.
I''ve
> found all sorts of information on trying to get the console right, but no
> luck. Should I move to the i386 version? Are things better supported
> there?
>
> There is one little trick I thought might help my problem. The ethernet
> connection on my system is actually on eth1. eth0 is disconnected because
> it is 1) on the motherboard and 2) 100bt, eth1 is a gig ether card. I
> changed the network-bridge command to read:
> (network-script network-bridge netdev=eth1)
> and ''btctl show'' lists out the interfaces as I expect
them to be. Alas,
> still no luck in getting an ip for the domU
>
> I''m a little frazzled at this point, but I was hoping someone
could help
> me answer my questions. If there are any config files you need, I can send
> them out.
>
>
> Rich
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users