Xen users - Dec 2007 - Information Request - domU configuration variables

Hi all, I''m new to Xen but with trial and error (and a lot of googling)
I have a debian host server (dom0) working with a debian guest server
(domU).  My big thing I struggled with was trying to get the domU to
boot from an .iso or a cd-rom so I can setup different OS''s.  Like I
said, I managed to get things working but know I''m trying to understand
what I did and what changed.  

 

In my searching I found some people listed their config files with:

kernel = ''/path/vmlinuz-2.6.18-5-xen-686

builder = ''linux''

 

and others with:

                kernel = ''/path/hvmloader

builder = ''hvm''

                device_model = ''/path/qemu-dm''

 

My searching only seems to bring up hits of posted configurations.  Does
anyone have any links to information explaining the different between
these two values and when/why you would use them?  Sorry for the amateur
questions.  I''m just trying to get a better handle on everything.

 

Thanks,  

Jerry Norton

 



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Jerry,

I don''t have any links to more information but I can give you a quick
answer
on your question. You use the /path/hvmloader when you want your domU to run
an operating system  that is not Xen aware, such as Windows XP, Windows
Server 2003 or a non-paravirtualized linux distro. Pretty much it using the
HVMLoader should allow you to install any OS on your computer that you would
normally be able to on the bare metal. Your CPU must have virtualization
extensions in order for this to work.

The other example you listed "kernel =
''/path/vmlinuz-2.6.18-5-xen-686" is
for booting a domU that is Xen aware using a linux Kernel or other that was
compiled as a Xen guest domain. These types of domUs don''t require the
virtualization extensions in the CPU as the Kernel can talk to Xen.

At least, this is how I understand it. I am still learning...

I hope this helps.

Regards,

Dan

On Dec 11, 2007 4:56 PM, Norton, Jerry <jnorton@odindev.com> wrote:
>  Hi all, I''m new to Xen but with trial and error (and a lot of
googling) I
> have a debian host server (dom0) working with a debian guest server (domU).
> My big thing I struggled with was trying to get the domU to boot from an
> .iso or a cd-rom so I can setup different OS''s.  Like I said, I
managed to
> get things working but know I''m trying to understand what I did
and what
> changed.
>
>
>
> In my searching I found some people listed their config files with:
>
> kernel = ''/path/vmlinuz-2.6.18-5-xen-686
>
> builder = ''linux''
>
>
>
> and others with:
>
>                 kernel = ''/path/hvmloader
>
> builder = ''hvm''
>
>                 device_model = ''/path/qemu-dm''
>
>
>
> My searching only seems to bring up hits of posted configurations.  Does
> anyone have any links to information explaining the different between these
> two values and when/why you would use them?  Sorry for the amateur
> questions.  I''m just trying to get a better handle on everything.
>
>
>
> Thanks,
>
> *Jerry Norton*
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Folks,

I need some help on running a fully virtualised domU.

I have as host OS/dom0 a Fedora Core 7 with xen-3.1.0-0.rc7.1.fc7; the 
CPU is a Core2 Duo CPU  T7500. This lives on *sdb*. I boot from sdb.

I have a Linux HDD visible as *sda* which boots OK on its own on real 
hardware (kernel 2.6.10).

I want to run it under Xen fully virtualised -- I have it running as 
paravirtualised with a Linux 2.6.9 kernel but it is not what I need.

My config file is "c20-vt". I want my SATA disk (sdb) to show up as 
*sda* (SATA) in the VM (is PATA the only thing supported?)
(I tried mapped sda as hda but I got nowhere.)

I start the VM with "xm create c20-vt", I see no VNC console (my X11
is
fine), I see no serial output in the file and xm list reports
    Name                                      ID   Mem VCPUs      
State   Time(s)
    C20-VT                                     1  1024     1     
------      0.0
    Domain-0                                   0    64     2     
r-----     30.3

How can I get this to work? I attached a few log files and xen outputs.

Thanks,
Vlad

<cid:part1.02060402.03030907@ulianov.ca>








_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users