On Sat, Oct 20 2007 - 19:22, Manuel Bouyer wrote:
> >
> > The only thing I didn't notice before is a log file in /var/log/xen :
> > # cat qemu-dm.25749.log
> > domid: 34
> > qemu: the number of cpus is 1
> > Watching /local/domain/34/logdirty/next-active
> > /usr/pkg/etc/xen/scripts/qemu-ifup: could not launch network script
> > Could not initialize device 'tap'
>
> that could be the issue: the domain is running but qemu isn't. qemu is
> doing the interface between the HVM domain and dom0, if it's not there
> you don't have a console.
>
> >
> > I checked my installed xen packages (xenkernel3-3.1.0nb2
> > xentools3-3.1.0 xentools3-hvm-3.1.0) and indeed, the script is not present.
> > I do not have such logs when starting NetBSD domU (netbsd-4 for both
> > dom0 and domU).
>
> I though I had added this in the xentools3-hvm-3.1.0 package. The script is
> present in pkgsrc/sysutils/xentools3-hvm/files but doesn't seem to
> be installed :(
>
> this script is just:
> #!/bin/sh
> ifconfig $1 up
> exec /sbin/brconfig $2 add $1
>
YEAH !
Now I can get the console.
VNC has a really slow rendering.
But "ssh -X" looks nice.
Thanks a lot.
Jo
Attachment:
pgpNphtqOoP1e.pgp
Description: PGP signature