Xen in Hardy
On Wed, Apr 2, 2008 at 11:43 PM, Leandro Pereira de Lima e Silva
<leandro@limaesilva.com.br> wrote: > Sander, > > That's what I did: > - I was trying to create a virtual machine with hardy on it (hardy on the > host too) using xen-create-image. > - xen-tools isn't coming with hooks for installing hardy (I've already > filled a bug report about that), so I tried symlinking hardy.d to edgy.d > just like the symlinks from feisty.d and gutsy.d. > - Runned: xen-create-image --force --fs ext3 --image-dev > /dev/group/volume_root --memory 512 --passwd --swap-dev > /dev/group/volume_swap --dist hardy --mirror > http://br.archive.ubuntu.com/ubuntu --gateway gateway_ip_addr --ip ip_addr > --netmask netmask_addr --hostname hostname_addr, where "group/volume_root", > "group/volume_swap", "gateway_ip_addr", "ip_addr", "netmask_addr", > "hostname_addr" are actually other things that I've changed to get some > privacy. > - Tried to boot, but initramfs can't find the root. > - Fixed a few things on the configuration file generated by xen-create-image > (tried different combinations, this is how it ended): > - Add "root = '/dev/sda2 ro'" after the memory line. > - Fixed the disk section that just contained "',sda1,w'," inside of it, > at the end it became: > disk = [ 'phy:group/volume_swap,sda1,w', > 'phy:group/volume_root,sda2,w' ] > - Add "xenblk" to /etc/initramfs-tools/modules and recreated the initrd > file. (the same as the above item, what seemd to work after a few > tentatives) > - Runned xm create -c hostname_addr > - Machine starts to boot and hangs at: > * Running local boot scripts (/etc/rc.local) [ > OK ] > > - Switched to gutsy (in xen-create-image), thinking that maybe it hangs > because of some new hook needed for hardy. > - Got the same problem that I had with hardy. Your guest probably doesn't hang, it just doesn't show the login prompt. You will get one by adding the following to your /etx/xen/guest-name.cfg: extra = "console=tty" Incidently, I have been playing just yesterday with xen in hardy and encountered the same problems. The next one for me is that the guest can't connect to the net, even if an eth0 shows up. The problem seems to be related to the new kernel in hardy as the very same host using gutsy kernel works just fine. More info on https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010 I would like to take the occasion to ask about the future of xen in ubuntu. A while ago a switch to kvm was announced. I would like to know if xen will still be supported or if it will be deprecated at some point. The nice thing with kvm is its simplicity when running unmodified guests, but it is much slower than xen when running "xen-enabled" guests. Xen has a number of other advantages: - the xen-create-image scripts make building new guests with xen much easier and faster than with kvm! - xen can use real devices easilly, I'm not even sure that kvm can (it requires full disk image, doesn't it ?) as a result, xen is so much easier to use and efficient for my use case (always running a few systems, without graphical interface). I see few options for xen in hardy * fully supported, which requires to fix the bugs discussed in this thread (missing hardy hooks, missing xenblk in initramfs/kernel and broken xennet in the latest kernel) * supported, which requires a bit less work (i.e. reverting to gutsy kernel to fix the xennet bug) * deprecated, which would be a bad regression if kvm doesn't get a LOT of attention (which is probably not doable in time) is the plan one of these options or an alternate one ? And then what is the plan in the long run ? The fedora guys seem to be working toward integrating as much of the huge and dirty xen patch in the vanilla kernel. If they succed the state of xen in every distrtib would be greatly improved IMHO. Is canonical able/willing to help this effort ? Sorry for the long worries/ranting, I hope it doesn't feel harsh for the people working on xen in ubuntu as it really doesn't intend to: thanks for your work so far, I just would like to get more hints about the future and didn't find any recent "official" discussion about this. Regards. -- Aurélien Naldi -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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@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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
Aurélien,
I forgot to comment your questions on my last e-mail. I'm worried about that too. My main concern is that I can run Xen almost on any machine I have, but KVM will only run on that that the processor has virtualization extensions (isn't it?). If KVM prove to be better supported that Xen I think I can consider using it, but right now it only limits my options. Cheers, Leandro. 2008/4/3, Aurélien Naldi <aurelien.naldi@gmail.com>: On Wed, Apr 2, 2008 at 11:43 PM, Leandro Pereira de Lima e Silva <leandro@limaesilva.com.br> wrote: > Sander, > > That's what I did: > - I was trying to create a virtual machine with hardy on it (hardy on the > host too) using xen-create-image. > - xen-tools isn't coming with hooks for installing hardy (I've already > filled a bug report about that), so I tried symlinking hardy.d to edgy.d > just like the symlinks from feisty.d and gutsy.d. >**- Runned: xen-create-image --force --fs ext3 --image-dev > /dev/group/volume_root --memory 512 --passwd --swap-dev > /dev/group/volume_swap --dist hardy --mirror > http://br.archive.ubuntu.com/ubuntu --gateway gateway_ip_addr --ip ip_addr > --netmask netmask_addr --hostname hostname_addr, where "group/volume_root", > "group/volume_swap", "gateway_ip_addr", "ip_addr", "netmask_addr", > "hostname_addr" are actually other things that I've changed to get some > privacy. >**- Tried to boot, but initramfs can't find the root. > - Fixed a few things on the configuration file generated by xen-create-image > (tried different combinations, this is how it ended): >** - Add "root********= '/dev/sda2 ro'" after the memory line. >****- Fixed the disk section that just contained "',sda1,w'," inside of it, > at the end it became: >****** disk********= [ 'phy:group/volume_swap,sda1,w', > 'phy:group/volume_root,sda2,w' ] >**- Add "xenblk" to /etc/initramfs-tools/modules and recreated the initrd > file. (the same as the above item, what seemd to work after a few > tentatives) > - Runned xm create -c hostname_addr > - Machine starts to boot and hangs at: >** * Running local boot scripts (/etc/rc.local)****************************[ > OK ] > > - Switched to gutsy (in xen-create-image), thinking that maybe it hangs > because of some new hook needed for hardy. > - Got the same problem that I had with hardy. Your guest probably doesn't hang, it just doesn't show the login prompt. You will get one by adding the following to your /etx/xen/guest-name.cfg: extra = "console=tty" Incidently, I have been playing just yesterday with xen in hardy and encountered the same problems. The next one for me is that the guest can't connect to the net, even if an eth0 shows up. The problem seems to be related to the new kernel in hardy as the very same host using gutsy kernel works just fine. More info on https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010 I would like to take the occasion to ask about the future of xen in ubuntu. A while ago a switch to kvm was announced. I would like to know if xen will still be supported or if it will be deprecated at some point. The nice thing with kvm is its simplicity when running unmodified guests, but it is much slower than xen when running "xen-enabled" guests. Xen has a number of other advantages: - the xen-create-image scripts make building new guests with xen much easier and faster than with kvm! - xen can use real devices easilly, I'm not even sure that kvm can (it requires full disk image, doesn't it ?) as a result, xen is so much easier to use and efficient for my use case (always running a few systems, without graphical interface). **I see few options for xen in hardy * fully supported, which requires to fix the bugs discussed in this thread (missing hardy hooks, missing xenblk in initramfs/kernel and broken xennet in the latest kernel) * supported, which requires a bit less work (i.e. reverting to gutsy kernel to fix the xennet bug) * deprecated, which would be a bad regression if kvm doesn't get a LOT of attention (which is probably not doable in time) is the plan one of these options or an alternate one ? And then what is the plan in the long run ? The fedora guys seem to be working toward integrating as much of the huge and dirty xen patch in the vanilla kernel. If they succed the state of xen in every distrtib would be greatly improved IMHO. Is canonical able/willing to help this effort ? Sorry for the long worries/ranting, I hope it doesn't feel harsh for the people working on xen in ubuntu as it really doesn't intend to: thanks for your work so far, I just would like to get more hints about the future and didn't find any recent**"official" discussion about this. Regards. -- Aurélien Naldi -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam -- Leandro Pereira de Lima e Silva -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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 On Thu, Apr 3, 2008 at 8:34 PM, Leandro Pereira de Lima e Silva <leandro@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@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@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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@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 On Thu, Apr 3, 2008 at 8:34 PM, Leandro Pereira de Lima e Silva <leandro@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@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@lists.ubuntu.com >**https://lists.ubuntu.com/mailman/listinfo/ubuntu-server >**More info: https://wiki.ubuntu.com/ServerTeam > -- Leandro Pereira de Lima e Silva -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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@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@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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
Let's attach the file this time for the nice peoples...
Andrew. -- Andrew Shugg <andrew@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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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@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@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@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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
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@gmail.com <mailto:deshantm@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@limaesilva.com.br <mailto:leandro@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@g.org.nz <mailto:g@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@lists.ubuntu.com > <mailto:ubuntu-server@lists.ubuntu.com> > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > > More info: https://wiki.ubuntu.com/ServerTeam > > > > > > > -- > Leandro Pereira de Lima e Silva -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
Xen in Hardy
Todd,
I think that Canonical's choice for KVM have already made it clear that they won't support Xen at least for a while. Cheers, Leandro. 2008/4/11, Todd Deshane <deshantm@gmail.com>: 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@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@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@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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam -- Leandro Pereira de Lima e Silva -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam |
| All times are GMT. The time now is 07:30 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.