[one-users] Template for Windows XP

[Nikola Milutinovic]

Javier Fontan wrote:
> Hello,
>
> You should better try to run windows in xen manually, without
> OpenNebula. After you have your desired configuration ready you can
> start automating VM management with OpenNebula. Do not start with
> OpenNebula as it adds another complexity layer and will only mislead
> you. This advice is not only for windows machines in xen. You first
> need an already running VM infrastructure before installing and
> configuring OpenNebula. Maybe this article is a good start:
>
> http://www.planetjoel.com/viewarticle/568/HOWTO:+Windows+XP+running+under+Xen+3.0+on+Ubuntu+Dapper+Drake
>   

Hi Javier.

Thank you for sound advice. Actually, we have a running infrastructure, 
or should I say, we had it. Our original setup was with 2xVMWare + 
1xONE. That worked fine, but we needed live migration feature, so we 
turned to Xen.

We have converted VMDK to RAW and we think we're ready to start playing 
with Xen. One problem that we have, though is the IP. If the IP address 
of the VM is assigned via DHCP and MAC is also randomly assigned, I 
guess there is no way to learn the IP address of the VM, right?

With VMWare we had a way of querying the VMWare server for IP of a 
particular VM, if that VM had VMWare Tools installed.

Now, the link you posted here is something I have visited before. And it 
is the cause of my confusion. In OpenNebula I am supposed to supply 
something like this:

(example from Ubuntu site)

NAME   = Ubuntu
    CPU    = 0.5
    MEMORY = 128
    OS     = [
       kernel   = "/boot/vmlinuz-2.6.18-4-xen-amd64",
       initrd   = "/boot/initrd.img-2.6.18-4-xen-amd64",
       root     = "sda1" ]
    DISK   = [
       source   = "/opt/nebula/images/disk.img",
       target   = "sda1",
       readonly = "no" ]

This would translate in Xen to:

kernel = "/usr/lib/xen/boot/hvmloader"
builder = 'hvm'
memory = 128
name = "Ubuntu"
vcpus = 1
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'tap:aio:/home/xen/domains/Ubuntu/Ubuntu.img,ioemu:hda,w', 
'phy:/dev/scd0,ioemu:hdc:cdrom,r' ]
device_model = '/usr/lib/xen/bin/qemu-dm'
ne2000=0
boot='c'
vnc=0
vncviewer=1
sdl=1

And this confuses me. In Xen I can see what I would expect - just the 
path to the DISK to boot from and nothing more. The kernel is 
"hvmloader", just as I would expect.. In OpenNebula there are references 
to "kernel" being a normal Linux kernel and "initrd". These look more 
like boot parameters for GRUB or LILO, then something passed to the Xen 
loader.

And then I have to ask what should be in there for Windows?

Nix.
-- 
Met vriendelijke groet / Kind regards,
Nikola Milutinovic
Sr Java Developer
Levi9 Global Sourcing
------------------------------------------------------------------------
.  Jan van Goyenkade 8, 1075 HP Amsterdam, The Netherlands
(    +31 (0) 20 7547900 ext 2056
(    +381 (0) 21 4895800 ext 2056
È    +381 (0) 64 2202824
*    n.milutinovic at Levi9.com <mailto:n.milutinovic at Levi9.com>
^    Skype: nikola.milutinovic
ü    www.levi9.com <http://www.levi9.com/>

Chamber of commerce Levi9 Global Sourcing BV: 34221951
Chamber of commerce Levi9 Global Sourcing Benelux BV: 34224746
------------------------------------------------------------------------
This e-mail may contain confidential or privileged information. If you 
are not (one of) the intended recipient(s), please notify the sender 
immediately by reply e-mail and delete this message and any attachments 
permanently without retaining a copy. Any review, disclosure, copying, 
distribution or taking any action in reliance on the contents of this 
e-mail by persons or entities other than the intended recipient(s) is 
strictly prohibited and may be unlawful.

The services of Levi9 are exclusively subject to its general terms and 
conditions. These general terms and conditions can be found on 
www.levi9.com <http://www.levi9.com/> and a copy will be promptly 
submitted to you on your request and free of charge.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20091210/bb5e0a70/attachment-0002.htm>