openSUSE Studio

On Sun, 16 Aug 2009 18:10:03 +0200
houghi <houghi RemoveThis @houghi.org.invalid> wrote:

>Vahis wrote:
>
>> They say VirtualBox can run VMWare machines but I haven't got
>> VirtualBox. I tried it a long time ago but couldn't make it work, so
>> I went to VMWare. It's been working fine.
>
>I can't get any of them to work. See my other post.
>

That's strange -- I just loaded VirtualBox a week ago from YaST
software and it works great. I also included the 'VirtualBox'
repository and upgraded to the latest version they had, also no
problems.


--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- (temporarily offline)

Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.25.20-0.4-pae
10:57am up 28 days 12:19, 34 users, load average: 0.74, 0.41, 0.46

On 2009-08-16, houghi <houghi RemoveThis @houghi.org.invalid> wrote:
> Vahis wrote:
>> I received my invitation and tried to create an appliance:
>> SLES 11 server.
>
> Neat.
>
>> Everything looks fine but when I try "testdrive" I get this:
>>
>> Connection timed out
>> Testdrive needs to access ports 843 and 5900 - 5908
>> (You may have an issue with a firewall or proxy)
>
> OK. I just did the same. Made a diskimage and all I did was change the
> wallpaper and added nmap and mc. Build it and done. Testdrive works
> perfectly.
>
>> Then I first disabled my own firewall, no change.
>>
>> Then I rebuilt the image with firewall disabled, no change.
>> Now what?
>
> Ask on the SUSE Studio mailinglist. I doubt that many people here have
> an account there, let alone know what is going on.
> I am guessing it is your firewall, not the firewall of the image.

Dunno. I don't think it can be mine if it's disabled?
>
> Also unclear to what you try to do. testdrive will NOT have access to
> the outside world,

Sure it does. You can ssh to it. The guy showed that on the screencast.

> so if you made something where you try to connect to
> your home machine, that won't work from the testdrive.

I haven't tried to connect from there. I couldn't even make it boot.

I made an appliance which I wanted to fire up via testdrive.
That failed. When I pushed "Testdrive" I got the error I quoted.

I'll try again.
>
>> Assuming I would get a SLES working I would need some further assistance
>> in finding instructions to configure.
>
> If specific on SUSE Studio, what you need to do is first build a disk
> image to do all the testing. Then run it as testdrive and do whatever
> you need to edit.

That's exactly what I'm trying to do.

> e.g. configure it in such a way that you don't need to
> accept the EULA each time, Apache starts and what not.
>
> Watch the second screencast at http://susestudio.com/screencast

Thanks for that. I watched it.

He did the same as I had done. But mine didn't boot. Or it didn't let me
boot it or whatever.

I'll try again, another appliance.

I like the idea of building and tweaking and rebuilding till everything
is fine. Then just download and run locally.
>
>> I have thought of running virtual machines on top of KVM.
>> Is this a good idea or would VirtualBox be better?
>
> I spoke to somebody who knows a lot more then I do and he favoured
> VirtualBox over XEN and VMware. He still prefers Parallels on his Mac.
> Unfortunatly still no 64bit for parallels. :-/
>
>> So far I've been running VMWareServer, byt I somehow like the idea of
>> having the virtualization built in kernel.
>
> Why? I would think the the less there is in the kernel the better. I
> would also think that I know nothing about kernels. I used to run
> parallels as that worked right out of the box for me. Now it does not
> anymore. :-/
>
> Can VirtualBox use either XEN or VMware images?

They say VirtualBox can run VMWare machines but I haven't got
VirtualBox. I tried it a long time ago but couldn't make it work, so I
went to VMWare. It's been working fine.

Vahis
--
"Sunrise 5:38am (EEST), sunset 9:09pm (EEST) at Espoo, Finland (15:31 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.4-default #1 SMP 2009-06-01 09:57:12 +0200 x86_64
5:42pm up 63 days 2:16, 14 users, load average: 1.10, 1.38, 1.26

This message is not archived

On 2009-08-16, houghi <houghi RemoveThis @houghi.org.invalid> wrote:
> Vahis wrote:
>>> Also unclear to what you try to do. testdrive will NOT have access to
>>> the outside world,
>>
>> Sure it does. You can ssh to it. The guy showed that on the screencast.
>
> You can have a connection to it. It can not have a connection to you.

I couldn't boot it. That's all I tried.
>
>> They say VirtualBox can run VMWare machines but I haven't got
>> VirtualBox. I tried it a long time ago but couldn't make it work, so I
>> went to VMWare. It's been working fine.
>
> I can't get any of them to work. See my other post.

http://waxborg.servepics.com/howto/install-vmware-server-in-opensuse


Vahis
--
"Sunrise 5:38am (EEST), sunset 9:09pm (EEST) at Espoo, Finland (15:31 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.4-default #1 SMP 2009-06-01 09:57:12 +0200 x86_64
7:17pm up 63 days 3:51, 14 users, load average: 1.10, 1.13, 1.26

On 2009-08-16, Vahis <waxborg.DeleteThis@gmail.com.invalid> wrote:
> I received my invitation and tried to create an appliance:
> SLES 11 server.
>
> Everything looks fine but when I try "testdrive" I get this:
>
> Connection timed out
> Testdrive needs to access ports 843 and 5900 - 5908
> (You may have an issue with a firewall or proxy)
>
> Then I first disabled my own firewall, no change.
>
> Then I rebuilt the image with firewall disabled, no change.
> Now what?

Don't know what happened. It just works now.
They say their servers are under quite some stress.
That could explain timeouts.

This is one great thing

Vahis
--
"Sunrise 5:38am (EEST), sunset 9:09pm (EEST) at Espoo, Finland (15:31 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.4-default #1 SMP 2009-06-01 09:57:12 +0200 x86_64
8:47pm up 63 days 5:21, 12 users, load average: 0.50, 0.69, 0.80

On Sun, 16 Aug 2009 10:59:35 -0700, Kevin Nathan <knathan RemoveThis @project54.com> wrote:

>On Sun, 16 Aug 2009 18:10:03 +0200
>houghi <houghi RemoveThis @houghi.org.invalid> wrote:
>
>>Vahis wrote:
>>
>>> They say VirtualBox can run VMWare machines but I haven't got
>>> VirtualBox. I tried it a long time ago but couldn't make it work, so
>>> I went to VMWare. It's been working fine.
>>
>>I can't get any of them to work. See my other post.
>>
>
>That's strange -- I just loaded VirtualBox a week ago from YaST
>software and it works great. I also included the 'VirtualBox'
>repository and upgraded to the latest version they had, also no
>problems.

No so very strange. Perhaps the kernel does not fit. I all the time have to pick
some extras until VMware works again.

Also, the automatic update of SuSE is insane as it

a) spoils GRUB and
b) destroys the kernel so that VMware does not run anymore.


--
**** WARNING **** The web-hoster Globat.com steals money from your
credit card account. If you are a customer of Globat.com, never give
them any credit card information. If you can't erase the information,
then do delete the old card and get a new one! **** WARNING ****

Happy Oyster wrote:
> a) spoils GRUB and
> b) destroys the kernel so that VMware does not run anymore.

If you got the (default as far as I know)
AOU_SKIP_INTERACTIVE_PATCHES="true"
option set (AOU is automatic online update, set-able in yast or by
hand in /etc/sysconfig/automatic_online_update
no kernel replacements and/or other "have to agree to" patches will be
automatic applied at all, you WILL have to do those by hand (e.g. with
a zypper up -y command). With no kernel replacement the menu.lst from
grub will also be untouched.
--
Eef Hartman, Delft University of Technology, dept. SSC/ICT

On Wed, 19 Aug 2009 11:28:31 +0200, Eef Hartman <E.J.M.Hartman RemoveThis @tudelft.nl>
wrote:

>Happy Oyster wrote:
>> a) spoils GRUB and
>> b) destroys the kernel so that VMware does not run anymore.
>
>If you got the (default as far as I know)
>AOU_SKIP_INTERACTIVE_PATCHES="true"
>option set (AOU is automatic online update, set-able in yast or by
>hand in /etc/sysconfig/automatic_online_update
>no kernel replacements and/or other "have to agree to" patches will be
>automatic applied at all, you WILL have to do those by hand (e.g. with
>a zypper up -y command). With no kernel replacement the menu.lst from
>grub will also be untouched.

Thanks. Ich will look for that parameter.

--
Vollalternative Schmerzbehandlung

http://www.ariplex.com/ama/amalanc1.htm