[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Debian/Xen usage summary


I just setup a few virtual systems, and I came into some limitations using XEN. I'd like to share these, just to know if the limitations are in the system or in the user :)

I am using a standard Debian 4.0 (etch) GNU/Linux distribiution. The system is an Intel Core 2 duo with virtualization inside. I use the amd64 flavour. Thus my kernel is '2.6.18-4-xen-amd64'. Xen is version 3.0.3.

Using paravirtualization, I can start only other 64 bits guests.
  Either the standard linux-image-2.6.18-4-xen-amd64,
  Or a specially compiled one, with IDE included not-as-module
  I cannot manage to start the ubuntu 7.04 kernels for amd64.

Using full virtualization (hvm), I can start only 32 bits guests.
  Starting on an ISO of a Debian amd64 or Fedora x86_64 install fails.
  But starting on a i386 ISO of these allows the install to run OK.

Using hvm, I have to use ioemu for the network card to be recognized.
  vif = [ "type=ioemu, ip=..." ] without it, the card is not detected.
  BTW, I am using NAT for networking.

Then, starting to use all of these is a bit of a nightmare. Indeed hvm systems do start but does not show the SDL display. xm list reports the system as running, but I have no access to it (and network not yet configured) although it was present during install. Don't know what happends here. I'd be glad for some hints?

One more question, how to mount inside dom0 a logical volume that is given as a whole disk to a hvm (which had it partitionned).

Thanks in advance

Didier Trosset-Moreau
Agilent Technologies
Geneva, Switzerland

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.