Highlighted
Absent Member.
Absent Member.
3486 views

What's bloke to do?

Unless I'm missing something, I've been waiting for this capability for a long time.
We have a medium size SLES XEN based infrastructure (40 virtuals) with No VMWARE in sight! (We use VBOX for experimentation)

Does this mean I can't run filr unless I break our model and introduce VMWARE? Or will I be able to install and run filr on a SLES 11 infrastructure?
Thanks
Eric.
Tags (1)
14 Replies
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: What's bloke to do?

I have no expirience with VBOX.
I use KVM to rum the FiLR. Convert the image with:
# qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
copy the qcow2-Image file to the storage location and start it with the virtual Maschine Manager.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: What's bloke to do?

ucba;2261180 wrote:
Unless I'm missing something, I've been waiting for this capability for a long time.
We have a medium size SLES XEN based infrastructure (40 virtuals) with No VMWARE in sight! (We use VBOX for experimentation)

Does this mean I can't run filr unless I break our model and introduce VMWARE? Or will I be able to install and run filr on a SLES 11 infrastructure?
Thanks
Eric.


Along with Thomas's reply:

Filr can run on Xen, to run it optimally you will need to "tinker" with the appliance to get the correct Xen kernel packages installed.

From what I've heard, you should be able to import the ova into VirtualBox without to much hassle... that would seem the easiest route to get things running.

Any idea how large this deployment will be (users & content you are looking to service)?

-Willem
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: What's bloke to do?

On 01/05/2013 09:46, magic31 wrote:

> Along with Thomas's reply:
>
> Filr can run on Xen, to run it optimally you will need to "tinker" with
> the appliance to get the correct Xen kernel packages installed.
>
> From what I've heard, you should be able to import the ova into
> VirtualBox without to much hassle... that would seem the easiest route
> to get things running.


Please note that running the Filr Appliance on anything other than
VMware ESXi/ESX is currently unsupported. That doesn't mean that it
doesn't work though.

HTH.
--
Simon
Novell Knowledge Partner

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Technology Transfer
Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: What's bloke to do?

Simon Flood wrote:

> Please note that running the Filr Appliance on anything other than
> VMware ESXi/ESX is currently unsupported. That doesn't mean that it
> doesn't work though.


Correct, all good points throughout the thread so far. While it's only
supported under VMware, there were multiple beta/tech preview customers
who successfully ran filr under both Xen and Hyper-V so it appears to
work under other hypervisors.

More long term, adding support for additional hypervisors is being
investigated.

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: What's bloke to do?

ThomasHopp;2261200 wrote:
I have no expirience with VBOX.
I use KVM to rum the FiLR. Convert the image with:
# qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
copy the qcow2-Image file to the storage location and start it with the virtual Maschine Manager.


We ran the beta on Xen, seemed to work fine. Used VirtualBox to open (import) the ovf file. Then used qemu-img to convert it to a raw file:
# qemu-img convert -p -f vmdk Filr...vmdk -O raw filename.raw
When we created the Xen vm, pointed it to this raw file for the hard disk, and if you are using a secondary hard disk pointed that to another empty raw file, then just ran it as a fully virtualized machine. Magic31 mentioned tinkering with the appliance to get it to work I assume he means making it para-virtualized, haven't figured out how to do that successfully yet.
0 Likes
Highlighted
Absent Member.
Absent Member.

Antw: Re: What's bloke to do?



>>>


> ThomasHopp;2261200 Wrote:
>> I have no expirience with VBOX.
>> I use KVM to rum the FiLR. Convert the image with:
>> # qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
>> copy the qcow2-Image file to the storage location and start it with the
>> virtual Maschine Manager.

>
> We ran the beta on Xen, seemed to work fine. Used VirtualBox to open
> (import) the ovf file. Then used qemu-img to convert it to a raw file:
> # qemu-img convert -p -f vmdk Filr...vmdk -O raw filename.raw
> When we created the Xen vm, pointed it to this raw file for the hard
> disk, and if you are using a secondary hard disk pointed that to another
> empty raw file, then just ran it as a fully virtualized machine. Magic31
> mentioned tinkering with the appliance to get it to work I assume he
> means making it para-virtualized, haven't figured out how to do that
> successfully yet.


For running it in XEN with PV I just had to install the kernel-xen and
modify fstab in the domU and obviously modify the domU config..
(not supported - but seems to work)
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Antw: Re: What's bloke to do?

Martin Weiss wrote:

>
>
>>>>

>
>> ThomasHopp;2261200 Wrote:
>>> I have no expirience with VBOX.
>>> I use KVM to rum the FiLR. Convert the image with:
>>> # qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
>>> copy the qcow2-Image file to the storage location and start it with the
>>> virtual Maschine Manager.

>>
>> We ran the beta on Xen, seemed to work fine. Used VirtualBox to open
>> (import) the ovf file. Then used qemu-img to convert it to a raw file:
>> # qemu-img convert -p -f vmdk Filr...vmdk -O raw filename.raw
>> When we created the Xen vm, pointed it to this raw file for the hard
>> disk, and if you are using a secondary hard disk pointed that to another
>> empty raw file, then just ran it as a fully virtualized machine. Magic31
>> mentioned tinkering with the appliance to get it to work I assume he
>> means making it para-virtualized, haven't figured out how to do that
>> successfully yet.

>
> For running it in XEN with PV I just had to install the kernel-xen and
> modify fstab in the domU and obviously modify the domU config..
> (not supported - but seems to work)


So did you add repositories and sles updating for this to work? That is the
only way I can see to get the proper kernel installed.


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Antw: Re: What's bloke to do?



>>>

> Martin Weiss wrote:
>
>>
>>
>>>>>

>>
>>> ThomasHopp;2261200 Wrote:
>>>> I have no expirience with VBOX.
>>>> I use KVM to rum the FiLR. Convert the image with:
>>>> # qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
>>>> copy the qcow2-Image file to the storage location and start it with

the
>>>> virtual Maschine Manager.
>>>
>>> We ran the beta on Xen, seemed to work fine. Used VirtualBox to open
>>> (import) the ovf file. Then used qemu-img to convert it to a raw file:
>>> # qemu-img convert -p -f vmdk Filr...vmdk -O raw filename.raw
>>> When we created the Xen vm, pointed it to this raw file for the hard
>>> disk, and if you are using a secondary hard disk pointed that to

another
>>> empty raw file, then just ran it as a fully virtualized machine.

Magic31
>>> mentioned tinkering with the appliance to get it to work I assume he
>>> means making it para-virtualized, haven't figured out how to do that
>>> successfully yet.

>>
>> For running it in XEN with PV I just had to install the kernel-xen and
>> modify fstab in the domU and obviously modify the domU config..
>> (not supported - but seems to work)

>
> So did you add repositories and sles updating for this to work? That is
> the
> only way I can see to get the proper kernel installed.


Yes - I just copied /etc/zypp/repos.d/* and /etc/zypp/services.d/*
from an other SLES 11 SP2 box to the filr appliance,
and then did a "zypper ref && zypper in kernel-xen".

In fstab I modified /vastorage and / like this (before rebooting as PV):

/dev/xvda1 / ext3 defaults 1 1
/dev/xvdb1 /vastorage ext3 rw 0 0

The PV version of the XEN domU config file looks like this:

name="filr01"
description="None"
uuid="f47da102-da2a-1cd9-9d5f-f7fbfbe6f269"
memory=4096
maxmem=4096
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
builder="linux"
bootloader="/usr/bin/pygrub"
bootargs=""
disk=[ 'file:/var/lib/xen/images/filr01/filr01.raw,xvda,w',
'file:/var/lib/xen/images/filr01/data01.raw,xvdb,w',]
vif=[ 'mac=00:16:3e:28:93:ff,bridge=br0', ]
vfb=['type=vnc,vncunused=1']
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
extra = "root=/dev/xvda1 "

The full virtualized domU config looks like this:

name="filr01"
description="None"
uuid="f47da102-da2a-1cd9-9d5f-f7fbfbe6f269"
memory=4096
maxmem=4096
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
builder="hvm"
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ 'file:/var/lib/xen/images/filr01/filr01.raw,hda,w',
'file:/var/lib/xen/images/filr01/data01.raw,hdb,w',]
vif=[ 'mac=00:16:3e:28:93:ff,bridge=br0,model=rtl8139', ]
stdvga=0
vnc=1
vncunused=1
viridian=0
acpi=1
pae=1
serial="pty"


0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: What's bloke to do?

We would like a native Xen based VM here as well, please.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: What's bloke to do?

ucba;2261180 wrote:
Unless I'm missing something, I've been waiting for this capability for a long time.
We have a medium size SLES XEN based infrastructure (40 virtuals) with No VMWARE in sight! (We use VBOX for experimentation)

Does this mean I can't run filr unless I break our model and introduce VMWARE? Or will I be able to install and run filr on a SLES 11 infrastructure?
Thanks
Eric.


Thank you all for your posts. I have to say converting the image didn't occur to me. It's been several years since I've done any converting of images. I will give it ago in the next couple of weeks and I'll post any information not found here already. It would be good to know if and when filr will be supported on XEN. We can probably manage to run unsupported given our in-house capability, but it also alters the risk profile.
I'll see if filr does actually solve our one last issue. Enterprise file access anywhere!

Thanks again
Eric.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Antw: Re: What's bloke to do?

mweiss2;2261567 wrote:

>>>

> Martin Weiss wrote:
>
>>
>>
>>>>>

>>
>>> ThomasHopp;2261200 Wrote:
>>>> I have no expirience with VBOX.
>>>> I use KVM to rum the FiLR. Convert the image with:
>>>> # qemu-img convert -O qcow2 FiLR...vmdk FiLR...qcow2
>>>> copy the qcow2-Image file to the storage location and start it with

the
>>>> virtual Maschine Manager.
>>>
>>> We ran the beta on Xen, seemed to work fine. Used VirtualBox to open
>>> (import) the ovf file. Then used qemu-img to convert it to a raw file:
>>> # qemu-img convert -p -f vmdk Filr...vmdk -O raw filename.raw
>>> When we created the Xen vm, pointed it to this raw file for the hard
>>> disk, and if you are using a secondary hard disk pointed that to

another
>>> empty raw file, then just ran it as a fully virtualized machine.

Magic31
>>> mentioned tinkering with the appliance to get it to work I assume he
>>> means making it para-virtualized, haven't figured out how to do that
>>> successfully yet.

>>
>> For running it in XEN with PV I just had to install the kernel-xen and
>> modify fstab in the domU and obviously modify the domU config..
>> (not supported - but seems to work)

>
> So did you add repositories and sles updating for this to work? That is
> the
> only way I can see to get the proper kernel installed.


Yes - I just copied /etc/zypp/repos.d/* and /etc/zypp/services.d/*
from an other SLES 11 SP2 box to the filr appliance,
and then did a "zypper ref && zypper in kernel-xen".

In fstab I modified /vastorage and / like this (before rebooting as PV):

/dev/xvda1 / ext3 defaults 1 1
/dev/xvdb1 /vastorage ext3 rw 0 0

The PV version of the XEN domU config file looks like this:

name="filr01"
description="None"
uuid="f47da102-da2a-1cd9-9d5f-f7fbfbe6f269"
memory=4096
maxmem=4096
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
builder="linux"
bootloader="/usr/bin/pygrub"
bootargs=""
disk=[ 'file:/var/lib/xen/images/filr01/filr01.raw,xvda,w',
'file:/var/lib/xen/images/filr01/data01.raw,xvdb,w',]
vif=[ 'mac=00:16:3e:28:93:ff,bridge=br0', ]
vfb=['type=vnc,vncunused=1']
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
extra = "root=/dev/xvda1 "

The full virtualized domU config looks like this:

name="filr01"
description="None"
uuid="f47da102-da2a-1cd9-9d5f-f7fbfbe6f269"
memory=4096
maxmem=4096
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
builder="hvm"
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ 'file:/var/lib/xen/images/filr01/filr01.raw,hda,w',
'file:/var/lib/xen/images/filr01/data01.raw,hdb,w',]
vif=[ 'mac=00:16:3e:28:93:ff,bridge=br0,model=rtl8139', ]
stdvga=0
vnc=1
vncunused=1
viridian=0
acpi=1
pae=1
serial="pty"


Ah thank you, this worked for me, however I had to edit my /boot/grub/menu.lst file, the section relating to Xen, I had to remove the kernel line it created and change the two "modules" to be kernel and initrd to look like this:

title Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.58-0.6.6
root (hd0,0)
kernel /boot/vmlinuz-3.0.58-0.6.6-xen root=/dev/xvda1
initrd /boot/initrd-3.0.58-0.6.6-xen

Also I just found it easier to use the create VM wizard to make the config file for me but of course either way works.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.