Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/ Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
Kyle Hall <kyle.m.hall@...> writes:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle, great Job on building these! I have been running 3.0.1 on VMWARE myself and the speed is better than one would think as long as Zebra is the search engine. Very nice to see the VirtualBox worked out. I am hoping to switch to VBox once more OS admin. tools are released to manage the VMs. Do you like VBox better at this point? I have not checked out the latest version yet. -Darrell Ulm
I prefer to use VirtualBox for running vm's on my office pc ( such as a Windows VM for non-Linux software ). It supports seamless mode which VMWare does not ( except for Fusion on Mac ). For our 'real' vm's that are running services ( webservers, squid, etc. ) we use Xen. Xen beats every other free vm hands down for this, with the exception that snapshotting in Xen is literally stopping the vm and using dd to copy the image, quite a pain. We use XenServer, which is Citrix's Xen package. It's fantastic. I should mention that VirtualBox supports vmdk files, so you could try it with your existing vm's. Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Thu, May 28, 2009 at 4:19 PM, Darrell Ulm <darrellulm@smfpl.org> wrote:
Kyle Hall <kyle.m.hall@...> writes:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle, great Job on building these! I have been running 3.0.1 on VMWARE myself and the speed is better than one would think as long as Zebra is the search engine.
Very nice to see the VirtualBox worked out. I am hoping to switch to VBox once more OS admin. tools are released to manage the VMs.
Do you like VBox better at this point? I have not checked out the latest version yet.
-Darrell Ulm
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this? Paul Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
You can log in as the use account koha and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default. Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Try it with eth1, and eth2 as well. It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason. Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Try 'dmesg | grep eth' and see if any network devices are present. Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message? Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
If you run 'cat /etc/networking/interfaces' what does the output look like? Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Jun 1, 2009 at 10:38 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
Ignoring unknown interface eth1=eth1.
Paul
Kyle Hall wrote:
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Try 'cat /etc/network/interfaces' Paul Yachnes wrote:
cat: /etc/networking/interfaces: No such file or directory
Kyle Hall wrote:
If you run 'cat /etc/networking/interfaces' what does the output look like?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:38 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
Ignoring unknown interface eth1=eth1.
Paul
Kyle Hall wrote:
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tim McMahon Technical Services West Liberty Public Library
Now I get the following: #The loopback network interface auto lo iface lo inet loopback #The primary network interface allow-hotplug eth0 iface eth0 inet dhcp Tim McMahon wrote:
Try 'cat /etc/network/interfaces'
Paul Yachnes wrote:
cat: /etc/networking/interfaces: No such file or directory
Kyle Hall wrote:
If you run 'cat /etc/networking/interfaces' what does the output look like?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:38 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
Ignoring unknown interface eth1=eth1.
Paul
Kyle Hall wrote:
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
go to virtualbox and select the VM image. then go to "Network" and make sure the "enable network adapter" box is ticked Suchetha On Mon, Jun 1, 2009 at 9:14 PM, Paul Yachnes <yach@cox.net> wrote:
Now I get the following:
#The loopback network interface auto lo iface lo inet loopback
#The primary network interface allow-hotplug eth0 iface eth0 inet dhcp
Tim McMahon wrote:
Try 'cat /etc/network/interfaces'
Paul Yachnes wrote:
cat: /etc/networking/interfaces: No such file or directory
Kyle Hall wrote:
If you run 'cat /etc/networking/interfaces' what does the output look like?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:38 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
Ignoring unknown interface eth1=eth1.
Paul
Kyle Hall wrote:
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Check my photo album: http://picasaweb.google.com/suchetha Rants Raves and Miscellaneous Musings: http://raramimu.blogspot.com Why do I smell brimstone? And what am I doing in this hand-basket?
fwiw- I've run into exactly this problem before with VirtualBox (which I do like otherwise) and never found a fix -- always found it easier to reinstall to guest OS -- not a useful solution here I've suspected it might be related to the fake Ethernet addresses getting duplicated. You might try reassigning the interfaces and/or maybe turning off one and enabling another. -reed
I don't think I installed the guest additions in the vm. That may help. I've actually run into this problem with VMWare server as well, but it probably has a different cause there. This notice used to be on the vm page on my site: There is an issue involving the copying of a Debian-based VMware image in which the appliance appears to have no network interface, that is eth0 does not appear and attempts to bring it up result in errors. The fix this edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file to update the HWADDR line to match the MAC address found in the image’s VMX file (the MAC address can be found on the line ethernet0.address=XX:XX:XX:XX:XX:XX). Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Jun 2, 2009 at 12:29 AM, Reed Wade <reedwade@gmail.com> wrote:
fwiw- I've run into exactly this problem before with VirtualBox (which I do like otherwise) and never found a fix -- always found it easier to reinstall to guest OS -- not a useful solution here
I've suspected it might be related to the fake Ethernet addresses getting duplicated. You might try reassigning the interfaces and/or maybe turning off one and enabling another.
-reed _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
it should be cat /etc/network/interfaces not networking Suchetha 2009/6/1 Paul Yachnes <yach@cox.net>:
cat: /etc/networking/interfaces: No such file or directory
Kyle Hall wrote:
If you run 'cat /etc/networking/interfaces' what does the output look like?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:38 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
Ignoring unknown interface eth1=eth1.
Paul
Kyle Hall wrote:
So does executing 'sudo ifup eth1' say that the device does not exist, or does it give a different error message?
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Mon, Jun 1, 2009 at 10:07 AM, Paul Yachnes <yach@cox.net> wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 6:01 PM, Paul Yachnes <yach@cox.net> wrote:
Kyle Hall wrote:
Try it with eth1, and eth2 as well.
Neither are recognized.
It sounds like you should check the networking for the vm you created to use the vdi file with. It may not have been assigned a networking device for some reason.
That's not the problem either. I have assigned a host-only ethernet adapter.
Paul
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:46 PM, Paul Yachnes <yach@cox.net> wrote:
I am getting:
SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socet to interface: No such device Failed to bring up eth0
Paul
and run 'sudo ifconfig' to see if if is picking up any ip address. If not, I would try 'sudo /etc/init.d/networking restart && sudo ifup eth0'. Do you have the machine set up with bridged networking? The appliance is set up for DHCP by default.
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )
On Sun, May 31, 2009 at 2:01 PM, Paul Yachnes <yach@cox.net> wrote:
I have tried installing your virtual appliance on Sun VirtualBox. When I log in to the Koha Management Console, I see "IP Address: Error Finding IP Address". It is not picking up an IP Address. I have another installation of Koha 3 running under Ubuntu on VirtualBox and don't have a problem. How do I troubleshoot this?
Paul
Kyle Hall wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Check my photo album: http://picasaweb.google.com/suchetha Rants Raves and Miscellaneous Musings: http://raramimu.blogspot.com Why do I smell brimstone? And what am I doing in this hand-basket?
Paul Yachnes wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
I never use Virtual Appliances but it seems that in this linux system eth0 is renamed to eth1. If this is a Debian system, this is probably due to the fact that an eth0 interface is already 'registrered' by udev so udev register this interface with the next number (eth1). Interface are registered according to their MAC address. I do not know at all how the MAC address of the interface is created. Registered interfaces are listed (with MAC address and name) in /etc/udev/rules.d/70-persistent-net.rules To fix this, I see several solutions : - use eth1 everywhere instead of eth0 (not easy if you do not know what to modify exactly. /etc/network/interfaces would be one of such places) - remove /etc/udev/rules.d/70-persistent-net.rules (at least the line with the wrong eth0 AND the line with eth1 if it has been created) => next boot udev will pick the first number (eth0) for the interface - wait a new image where /etc/udev/rules.d/70-persistent-net.rules has been removed - modify your configuration so that the interface gets the MAC address written in /etc/udev/rules.d/70-persistent-net.rules for eth0 Regards, Vincent
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
-- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann Email: Vincent.Danjean@imag.fr 38330 Montbonnot Saint Martin
I'll have to test the vdi's on some other machines. I prepare them using the clonehd tool, which avoids problems with duplicate vm id's. I guess that might not be enough. Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Jun 2, 2009 at 9:21 AM, Vincent Danjean <vdanjean.ml@free.fr> wrote:
Paul Yachnes wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
I never use Virtual Appliances but it seems that in this linux system eth0 is renamed to eth1. If this is a Debian system, this is probably due to the fact that an eth0 interface is already 'registrered' by udev so udev register this interface with the next number (eth1). Interface are registered according to their MAC address. I do not know at all how the MAC address of the interface is created. Registered interfaces are listed (with MAC address and name) in /etc/udev/rules.d/70-persistent-net.rules
To fix this, I see several solutions : - use eth1 everywhere instead of eth0 (not easy if you do not know what to modify exactly. /etc/network/interfaces would be one of such places) - remove /etc/udev/rules.d/70-persistent-net.rules (at least the line with the wrong eth0 AND the line with eth1 if it has been created) => next boot udev will pick the first number (eth0) for the interface - wait a new image where /etc/udev/rules.d/70-persistent-net.rules has been removed - modify your configuration so that the interface gets the MAC address written in /etc/udev/rules.d/70-persistent-net.rules for eth0
Regards, Vincent
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
-- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann Email: Vincent.Danjean@imag.fr 38330 Montbonnot Saint Martin
Ok, There is an easy fix to glean from this. I did it with Koha_3.01-Release_Unconfigured-VirtualBox file. type this after logging in as koha: sudo pico /etc/udev/rules.d/70-persistent-net.rules delete all the rules! re-boot, and enjoy! Vincent Danjean-3 wrote:
Paul Yachnes wrote:
I get:
[ 5.983780] eth0: registered as PCnet/FAST III 79C973 [ 9.614702] udev: renamed network interface eth0 to eth1
Then, sudo ifconfig:
I still don't get an network ip address, just a local address.
Paul
I never use Virtual Appliances but it seems that in this linux system eth0 is renamed to eth1. If this is a Debian system, this is probably due to the fact that an eth0 interface is already 'registrered' by udev so udev register this interface with the next number (eth1). Interface are registered according to their MAC address. I do not know at all how the MAC address of the interface is created. Registered interfaces are listed (with MAC address and name) in /etc/udev/rules.d/70-persistent-net.rules
To fix this, I see several solutions : - use eth1 everywhere instead of eth0 (not easy if you do not know what to modify exactly. /etc/network/interfaces would be one of such places) - remove /etc/udev/rules.d/70-persistent-net.rules (at least the line with the wrong eth0 AND the line with eth1 if it has been created) => next boot udev will pick the first number (eth0) for the interface - wait a new image where /etc/udev/rules.d/70-persistent-net.rules has been removed - modify your configuration so that the interface gets the MAC address written in /etc/udev/rules.d/70-persistent-net.rules for eth0
Regards, Vincent
Kyle Hall wrote:
Try 'dmesg | grep eth' and see if any network devices are present.
Kyle
-- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann Email: Vincent.Danjean@imag.fr 38330 Montbonnot Saint Martin _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- View this message in context: http://www.nabble.com/New-Koha-Virtual-Appliances-Available-tp23760760p24184... Sent from the Koha - Discuss mailing list archive at Nabble.com.
This has been added to the official Koha download page: http://koha.org/download --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce@liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, May 28, 2009 at 8:28 AM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Looks good, but I would change: Kyle Hall maintains VMWARE Virtual Machines for Koha, you can download them from: to: Kyle Hall maintains Koha Virtual Appliances for VMWare, VirtualBox and others. You can download them from: Thanks, Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Wed, Jun 3, 2009 at 8:23 AM, Nicole Engard <nicole.engard@liblime.com> wrote:
This has been added to the official Koha download page: http://koha.org/download
---
Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce@liblime.com AIM/Y!/Skype: nengard
http://liblime.com http://blogs.liblime.com/open-sesame/
On Thu, May 28, 2009 at 8:28 AM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
On Wed, Jun 3, 2009 at 8:43 AM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
Looks good, but I would change: Kyle Hall maintains VMWARE Virtual Machines for Koha, you can download them from: to: Kyle Hall maintains Koha Virtual Appliances for VMWare, VirtualBox and others. You can download them from: Done.
Cheers, Josh -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
We have downloaded the Koha 3. VMware release image, and we need two user names and passwords: one to log in to the Linux OS and the other to administrate from the web management side of the KOHA. Thanks Sally Montserin --- On Wed, 6/3/09, Nicole Engard <nicole.engard@liblime.com> wrote: From: Nicole Engard <nicole.engard@liblime.com> Subject: Re: [Koha] New Koha Virtual Appliances Available To: "Kyle Hall" <kyle.m.hall@gmail.com> Cc: "koha" <koha@lists.katipo.co.nz> Date: Wednesday, June 3, 2009, 1:23 PM This has been added to the official Koha download page: http://koha.org/download --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce@liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, May 28, 2009 at 8:28 AM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
Hey all, I have finished uploading a new set of Koha virtual appliances. Each version is available in VirtualBox or VMWare formats, and in configured and unconfigured states. At the moment, there are versions for the 3.01 official release, and versions for 3.01.00.032, which was the latest from git.koha.org at the time it was created. URL: http://kylehall.info/index.php/projects/koha/koha-virtual-appliance/
Kyle
http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Sally, 2009/7/15 Sally Anne Montserin <samontserin@yahoo.com>:
We have downloaded the Koha 3. VMware release image, and we need two user names and passwords: one to log in to the Linux OS and the other to administrate from the web management side of the KOHA.
Check the directory into which you extracted the image - I believe there's a README file that contains the passwords. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
If not, the logins are as follows: Linux: koha mysql: kohaadmin koha: kohaadmin All passwords are 'katikoan' Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) On Thu, Jul 16, 2009 at 8:04 AM, Galen Charlton<galen.charlton@liblime.com> wrote:
Hi Sally,
2009/7/15 Sally Anne Montserin <samontserin@yahoo.com>:
We have downloaded the Koha 3. VMware release image, and we need two user names and passwords: one to log in to the Linux OS and the other to administrate from the web management side of the KOHA.
Check the directory into which you extracted the image - I believe there's a README file that contains the passwords.
Regards,
Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
participants (12)
-
Darrell Ulm -
Galen Charlton -
Joshua Ferraro -
Kyle Hall -
Nicole Engard -
Paul Yachnes -
Privateer -
Reed Wade -
Sally Anne Montserin -
Suchetha Wijenayake -
Tim McMahon -
Vincent Danjean