Xen in Hardy

[Leandro Pereira de Lima e Silva]

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>:
>
>  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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20080403/8e3bf43c/attachment.html>