Install hurdle, OpenSUSE on virtualbox
Dear all, I've been repeatedly working through install steps at http://wiki.koha-community.org/wiki/Koha_3.0.0_on_openSUSE_11.3, and keep getting stuck. Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox. With ifconfig I can see eth0 inet addr 192.168.1.16 Bcast 192.168.1.255 Mask 255.255.255.0. When I ping from the Windows side, I get request timed out. As indicated in the steps, I have a minimum install with no gui. Using yast to configure network. As an added step I changed from NAT to Bridged adapter in the VirtualBox config, but this didn't help. Any suggestions would be much appreciated. My current goal w/ Koha is to "simply" install the software, including Zebra. Nelson (nfred - irc)
Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox.
This is not a problem with Koha installation, this is a problem with VirtualBox. I would recommend asking your question in their forum: http://forums.virtualbox.org/ Why not work on your Koha installation problems at the same time? Ask here about those while you're waiting to figure out your VirtualBox problems. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
is getting slightly off the Koha topic but-- I tend to set up 2 network devices. One set for NAT and the other for Host-Only. The NAT interface normally gets a 10.x.x.x address (assigned via dhcp)and allows the guest OS to reach out to the outside world and get software updates and for other outgoing things. The Host-Only device normally gets a 192.x.x.x address assigned via dhcp and is used to connect inbound from the host machine. -reed On Tue, Feb 8, 2011 at 4:06 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox.
This is not a problem with Koha installation, this is a problem with VirtualBox. I would recommend asking your question in their forum:
Why not work on your Koha installation problems at the same time? Ask here about those while you're waiting to figure out your VirtualBox problems.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hie, We also have problems with Win7 and VirtualBox (3.3 and 4). The most working mode for network is "bridge" : the network is used on guest like a new machine (new IP in DHCP). The problem is only when pc is not connected to a network. For your developers, we use Linux installed laptops. Best regards, On Mon, Feb 7, 2011 at 7:06 PM, Reed Wade <reedwade@gmail.com> wrote:
is getting slightly off the Koha topic but--
I tend to set up 2 network devices. One set for NAT and the other for Host-Only. The NAT interface normally gets a 10.x.x.x address (assigned via dhcp)and allows the guest OS to reach out to the outside world and get software updates and for other outgoing things. The Host-Only device normally gets a 192.x.x.x address assigned via dhcp and is used to connect inbound from the host machine.
-reed
On Tue, Feb 8, 2011 at 4:06 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox.
This is not a problem with Koha installation, this is a problem with VirtualBox. I would recommend asking your question in their forum:
Why not work on your Koha installation problems at the same time? Ask here about those while you're waiting to figure out your VirtualBox problems.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers@gmail.com
In bridge mode the virtual machine will be looking your machine for address assignment via DHCP so -- I would expect taking it off the network to cause trouble. -reed On Wed, Feb 16, 2011 at 1:25 AM, Fridolyn SOMERS <fridolyn.somers@gmail.com> wrote:
Hie,
We also have problems with Win7 and VirtualBox (3.3 and 4). The most working mode for network is "bridge" : the network is used on guest like a new machine (new IP in DHCP). The problem is only when pc is not connected to a network.
For your developers, we use Linux installed laptops.
Best regards,
On Mon, Feb 7, 2011 at 7:06 PM, Reed Wade <reedwade@gmail.com> wrote:
is getting slightly off the Koha topic but--
I tend to set up 2 network devices. One set for NAT and the other for Host-Only. The NAT interface normally gets a 10.x.x.x address (assigned via dhcp)and allows the guest OS to reach out to the outside world and get software updates and for other outgoing things. The Host-Only device normally gets a 192.x.x.x address assigned via dhcp and is used to connect inbound from the host machine.
-reed
On Tue, Feb 8, 2011 at 4:06 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox.
This is not a problem with Koha installation, this is a problem with VirtualBox. I would recommend asking your question in their forum:
Why not work on your Koha installation problems at the same time? Ask here about those while you're waiting to figure out your VirtualBox problems.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers@gmail.com
sorry-- "...looking beyond your machine..." On Wed, Feb 16, 2011 at 8:39 AM, Reed Wade <reedwade@gmail.com> wrote:
In bridge mode the virtual machine will be looking your machine for address assignment via DHCP so -- I would expect taking it off the network to cause trouble.
-reed
On Wed, Feb 16, 2011 at 1:25 AM, Fridolyn SOMERS <fridolyn.somers@gmail.com> wrote:
Hie,
We also have problems with Win7 and VirtualBox (3.3 and 4). The most working mode for network is "bridge" : the network is used on guest like a new machine (new IP in DHCP). The problem is only when pc is not connected to a network.
For your developers, we use Linux installed laptops.
Best regards,
On Mon, Feb 7, 2011 at 7:06 PM, Reed Wade <reedwade@gmail.com> wrote:
is getting slightly off the Koha topic but--
I tend to set up 2 network devices. One set for NAT and the other for Host-Only. The NAT interface normally gets a 10.x.x.x address (assigned via dhcp)and allows the guest OS to reach out to the outside world and get software updates and for other outgoing things. The Host-Only device normally gets a 192.x.x.x address assigned via dhcp and is used to connect inbound from the host machine.
-reed
On Tue, Feb 8, 2011 at 4:06 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox.
This is not a problem with Koha installation, this is a problem with VirtualBox. I would recommend asking your question in their forum:
Why not work on your Koha installation problems at the same time? Ask here about those while you're waiting to figure out your VirtualBox problems.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers@gmail.com
participants (4)
-
Fridolyn SOMERS -
Nelson Fredsell -
Owen Leonard -
Reed Wade