Xen in Hardy

[Todd Deshane]

Leandro see this bug:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010

I have been trying bridging, but we think that the problem is with the
driver, not the configuration.

Andrew: Kernel Freeze for hardy is already hit, so if the problem is with
the kernel then it is probably too late.Maybe the freeze will come off
before after 8.04 releases and before the 8.04.1 release? In any case, let's
do our best to keep the traffic on this list more productive and keep the
bug traffic on the proper launchpad bugs.

Xen is not yet offically supported by Canonical, so as such we need to do
the best we can with the community effort. Let's see what we can do to make
it functional, and then as Red Hat gets better support for Xen in mainline
Linux, I am sure Canonical will revisit being able to support it.

Best Regards,
Todd

On Fri, Apr 11, 2008 at 10:36 AM, Andrew Shugg <andrew at neep.com.au> wrote:

> Leandro Pereira de Lima e Silva said:
> > 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>:
> > >
> > > 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 to try to get some advice.
> > >
> > > I would like to see a working system before hardy releases too :)
> > >
> > > Todd
>
> Hi,
>
> I've been arguing in private with Xen on Ubuntu for some months now and
> am close to having a working domU on hardy.  The fact that hardy's
> release date is so close has me worried, but anyway...
>
> Recently with xen 3.2 I've been able to create a bootable domU again
> rather than something that just sat and spun its wheels.  Various
> package updates have corrected issues with block devices, etc, and now
> I'm stuck on networking.
>
> Using today's packages[1] I have created a new gutsy domU.  When I start
> it I get:
>
> Device 0 (vif) could not be connected. Hotplug scripts not working.
>
> A bzip2-compressed 'script' file is attached[2], showing:
>
> xm dmesg
> xm info
> dpkg -l *xen*
> xm log
> cat /var/log/xen-tools/gutsy.log
> cat /etc/xen/gutsy.cfg
> sudo strace xm create /etc/xen/gutsy.cfg
>
>
> Any suggestions?  I've tried Todd's ethtool suggestion but unfortunately
> that made no difference that I could see ...
>
> It is not the same problem reported in launchpad[3] where the vif is up,
> and packets come in, but don't go out (204010).
>
> Andrew.
>
>
> [1]
>
> xen-hypervisor-3.2              3.2.0-0ubuntu10
> xen-utils-3.2                   3.2.0-0ubuntu10
> python-xen-3.2                  3.2.0-0ubuntu10
> xen-tools                       3.8-4ubuntu4
> linux-image-2.6.24-15-xen       2.6.24-15.27
>
>
> [2]  'bzless' is one way to read it
>
>
> [3]  For the curious:
>
> https://bugs.launchpad.net/ubuntu/+source/xen-3.2
> https://bugs.launchpad.net/ubuntu/+source/xen-tools
>
>
> --
> Andrew Shugg <andrew at neep.com.au>
> http://www.neep.com.au/
>
> "Just remember, Mr Fawlty, there's always someone worse off than
> yourself."
> "Is there?  Well I'd like to meet him.  I could do with a good laugh."
>
> --
> ubuntu-server mailing list
> ubuntu-server at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20080411/be797a3c/attachment.html>