--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 20 2007 - 14:25, Manuel Bouyer wrote:
> On Fri, Oct 19, 2007 at 10:46:54PM +0200, Joel CARNAT wrote:
> > Hello,
> >=20
> > I finally got a VT enabled BIOS on my Xen3 server so I'm trying to
> > install Windows XP on it. The thing is the Xen3 dom0 server is headless.
> >=20
> > How can I get the "console" for the Windows install ?
> >=20
> > If my config file contains:
> > sdl =3D 0
> > vnc =3D 1
> > vncdisplay =3D 1
> > vncunused =3D 0
> > vncpasswd =3D ''
> >=20
> > The domain is started OK (I can see it with `xm list`) but `netstat -a |
> > egrep 'localhost|LISTEN'` does not indicate the VNC port.
>=20
> This usually works for me.
> I have:
> vnc =3D 1
> vncdisplay =3D 0
> vncunused =3D 0
> vncpasswd=3D""
> vnclisten=3D'127.0.0.1'
>=20
> I'm not sure if the space around the '=3D' is significant or not.
>=20

It does not seem to work better.

In /var/log/xenbackendd.log, I can see:
xenstore-read: couldn't read path /local/domain/0/backend/vfb/26/0/type
Failed to read /local/domain/0/backend/console/26/0/script (No such file or=
 directory)


> >=20
> > If my config file contains:
> > sdl =3D 1
> > vnc =3D 0
> >=20
> > I create the VM from an X11 forwarding enabled session (`ssh -X luuna
> > "sudo /usr/pkg/sbin/xm create /home/xen/windows.conf"`) and the VM
> > starts but I don't see the console (I did `xhost +` on my workstation):
> > Warning: No xauth data; using fake authentication data for X11
> > forwarding.
> > Using config file "/home/xen/windows.conf".
> > Started domain windows
>=20
> Can you start a simple X client, like xclock ?
> Try it both from your shell, and from sudo ...
>=20

I've installed xbase.tgz and I can start an xterm.
Both as a normal user and with a sudo.
Running "xm create ..." from "ssh -X" or from the xterm launched using
"ssh -X" acts the same way.

If I start the domU with VNC=3D1, I can't see the port on netstat.
If I start the domU without any VNC parameters and run `xm create
/home/xen/windows.conf`, I get :
#####################
Using config file "/home/xen/windows.conf".
Started domain windows
#####################
but nothing pops up and no VNC port is LISTENing.
If I run `xm create -c /home/xen/windows.conf`, I get :
#####################
Using config file "/home/xen/windows.conf".
Started domain windows
xenconsole: Could not read tty from store: No such file or directory
#####################

In both case, the domU appears in `xm list`.

The only thing I didn't notice before is a log file in /var/log/xen :
# cat qemu-dm.25749.log=20
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'

I checked my installed xen packages (xenkernel3-3.1.0nb2=20
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).

In case it helps, here's the full windows config file:
name =3D "windows"
kernel =3D "/usr/pkg/lib/xen/boot/hvmloader"
builder =3D 'hvm'
memory =3D 512
#disk =3D [ 'file:/home/xen/windows/disk,ioemu:hda,w' ]
disk =3D [ 'file:/home/xen/windows/disk,ioemu:hda,w',
'file:/home/xen/windows/cd.iso,ioemu:hdc:cdrom,r' ]
vif =3D [ 'bridge=3Dbridge0, type=3Dioemu' ]
device_model =3D '/usr/pkg/libexec/qemu-dm'
boot=3D'd'
vnc =3D 1
vncdisplay =3D 0
vncunused =3D 0
vncpasswd=3D""
vnclisten=3D'127.0.0.1'
usb=3D1
usbdevice=3D'tablet'
#root =3D "/dev/wd0d"

Any (other) thoughts ?

TIA,
	Jo


--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFHGjNG0/VH7L7F7Y4RAoFZAJ9czO8fWIhk3jxxW2wAw3LlM+69TACgiTM9
d1fp0qnmFNjY8f3Vi4O7x0A=
=dtfO
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--