| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Debian etch Xen: No display window.
> -----Original Message-----
> From: Didier Trosset [mailto:didier_trosset@xxxxxxxxxxx]
> Sent: 14 May 2007 11:40
> To: Xen-users@xxxxxxxxxxxxxxxxxxx
> Cc: Petersson, Mats
> Subject: Re: [Xen-users] Debian etch Xen: No display window.
>
> Petersson, Mats wrote:
> >
> >> -----Original Message-----
> >> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> >> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >> Didier Trosset
> >> Sent: 14 May 2007 09:52
> >> To: Xen-users@xxxxxxxxxxxxxxxxxxx
> >> Subject: [Xen-users] Debian etch Xen: No display window.
> >>
> >>
> >> I am trying to setup Xen virtual servers using a Debian etch
> >> with the xen
> >> 3.0.3 provided in 32 bits mode. I am using full virtualization.
> >>
> >> I managed to get things started using the configuration
> >> provided below. I
> >> was able to run the install (with boot="d"). I even managed
> >> to start the
> >> system afterwards, and it runs correctly.
> >>
> >> But now I encounter a problem I already hit when running 64
> >> bits kernels (I
> >> am running now 32 bits, as I was told xen support for 64 bits
> >> was much
> >> better since 3.0.4).
> >>
> >> The xen domU starts, but it does not display the SDL
> window anymore.
> >>
> >> It did it a few times, for installing the system for
> instance, with
> >> everything runnig perfectly OK, connecting to a network
> >> mirror for the
> >> install. It runs really well!
> >>
> >> The only way for me to make it appear again is to remove the
> >> type=ioemu from
> >> the vif. But then the system does not recognize anymore the
> >> net card, which
> >> seems reasonable.
> >
> > I think (but I'm guessing) that you can't specify an IP-address to a
> > IOEMU network card. This probably confuses QEMU, which is
> responsible
> > for getting the SDL/VNC window to appear. You may want to check the
> > /var/log/qemu.<pid>.log for the QEMU that is runnning the
> guest (doing
> > "ls -ltr /var/log/qemu*" will show the last one at the end
> of the list -
> > if you get a HUGE list, you may want to delete the older ones!)
> >
>
> If I don't specify the IP address in the vif line, the device
> vifN.0 is
> assigned an address 10.X.X.X, which is not what I want. But
> can I specify it the way I do?
The reason you can't use the vif-line in the configuration to specify
the IP-address is that the IP-address isn't part of the hardware
specification. Since the fully-virtualizaed domains are given only
information available at the hardware level, there is no way to forward
the IP-address to the guest. [If you have a real hardware network card,
you don't give it an IP-address, right? You either set it up to use dhcp
(or similar), or you give it an IP-address via some configuration within
the OS that controls the network card].
The reason it WORKS to give an IP-address to the guest in a para-virtual
setup, is that the guest is AWARE that we're playing god with the
hardware it deals with, and the controls within the virtual network
"frontend" can fetch this information itself.
This is not the case for fully-virtual domains.
Unfortunately, I don't know enough about network setup to advice you on
your further questions. Perhaps someone else can do that.
--
Mats
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home