Xen in Hardy

[Sander van Vugt]

Leandro,

for what it's worth, in my opinion only the network bridge code is 
stable. Haven't had much succes with the routing either.

Cheers,
Sander


Leandro Pereira de Lima e Silva schreef:
> Todd,
>
> What kind of networking are you using? I'm trying to use vif-route and 
> network-route without much success even using the ethtool command.
>
> Cheers, Leandro.
>
> 2008/4/3, Todd Deshane <deshantm at gmail.com <mailto:deshantm at gmail.com>>:
>
>     For the network problem can you give the following command a shot:
>
>     ethtool -K eth0 tx off
>
>     I plan to spend as much time as I can in ##xen on freenode and also
>     #xen on irc.oftc.net <http://irc.oftc.net> to try to get some advice.
>
>     I would like to see a working system before hardy releases too :)
>
>     Todd
>
>
>     On Thu, Apr 3, 2008 at 8:34 PM, Leandro Pereira de Lima e Silva
>
>     <leandro at limaesilva.com.br <mailto:leandro at limaesilva.com.br>> wrote:
>
>     > Mark & Aurélien, changing console= removed even more output.
>     Adding "extra =
>     > 'xencons=tty'" solved the problem. It gives me a terminal now.
>     >
>     > Todd, after loading xenblk driver the disk was recognized, I've
>     read about
>     > the sda/hda problem, but I didn't have to change it this time.
>     >
>     > I still get no network, I'll see what I can do about that.
>     >
>     > Cheers, Leandro.
>     >
>     > 2008/4/2, Mark Goldfinch <g at g.org.nz <mailto:g at g.org.nz>>:
>     > >
>     > > Hi Leandro,
>     > >
>     > >
>     > >
>     > >
>     > > Does the machine actually hang or are you missing just missing
>     your login
>     > prompt?
>     > >
>     > > If its the latter then it could be that Xen is running its
>     /dev/console on
>     > a device which there isn't a getty running for.
>     > >
>     > > Have a look at the configuration file for your Xen image, does
>     it contain
>     > a like like either:
>     > >
>     > > extra = "console=hvc0"
>     > >
>     > > or
>     > >
>     > > extra = "xencons=xvc console=xvc0"
>     > >
>     > > If so, then you need to update upstart by creating a new file
>     within
>     > /etc/event.d with the following contents:
>     > >
>     > > ========
>     > > # xvc0 - getty
>     > > #
>     > > # This service maintains a getty on xvc0 from the point the
>     system is
>     > > # started until it is shut down again.
>     > >
>     > > start on runlevel 2
>     > > start on runlevel 3
>     > > start on runlevel 4
>     > > start on runlevel 5
>     > >
>     > > stop on runlevel 0
>     > > stop on runlevel 1
>     > > stop on runlevel 6
>     > >
>     > > respawn
>     > > script
>     > >         if [ ! -c /dev/xvc0 ]; then
>     > >                 mknod --mode=600 /dev/xvc0 c 204 191;
>     > >         fi
>     > >
>     > >         exec /sbin/getty 38400 xvc0
>     > > end script
>     > > ========
>     > >
>     > > Then you can run "sudo start xvc0" to start your system
>     console, or just
>     > reboot. If you feel like doing so you can remove all your
>     tty[1-6] files
>     > from /etc/event.d as there's no virtual consoles on DomU hosts.
>     > >
>     > > Hopefully this should then get you a working system console..
>     > >
>     > > Thanks,
>     > > Mark.
>     > >
>     >
>     >
>     >
>     > --
>     >
>     > Leandro Pereira de Lima e Silva
>
>     > --
>     >  ubuntu-server mailing list
>     >  ubuntu-server at lists.ubuntu.com
>     <mailto:ubuntu-server at lists.ubuntu.com>
>     >  https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
>     >  More info: https://wiki.ubuntu.com/ServerTeam
>     >
>
>
>
>
> -- 
> Leandro Pereira de Lima e Silva