LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud
User Name
Password
Linux - Virtualization and Cloud This forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.

Notices


Reply
  Search this Thread
Old 12-10-2009, 04:16 AM   #1
jonaskellens
Member
 
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 694

Rep: Reputation: 34
Xen: trying to install from cdrom or iso but failing


Trying to install Endian firewall on my Xen-system but failing.

Code:
[root@xen vm]# virt-install --name endian --ram 512 --file /var/vm/endian/endian.img --file-size 8 --vnc --cdrom /dev/cdrom --network bridge:eth0 --network bridge:eth1
ERROR    Paravirtualized guests cannot install off cdrom media.
So I copy the endian cd-rom :

Code:
[root@xen vm]# dd if=/dev/cdrom of=/tmp/endian/endian.iso
But :
Code:
[root@xen vm]# virt-install --name endian --ram 512 --file /var/vm/endian/endian.img --file-size 8 --vnc --cdrom /tmp/endian/endian.iso --network bridge:eth0 --network bridge:eth1
ERROR    Paravirtualized guests cannot install off cdrom media.
Code:
[root@xen vm]# virt-install --name endian --ram 512 --file /var/vm/endian/endian.img --file-size 8 --vnc --location /tmp/endian/endian.iso --network bridge:eth0 --network bridge:eth1
Starting install...
Could not find an installable distribution at '/tmp/endian/endian.iso'
ERROR    Could not find an installable distribution at '/tmp/endian/endian.iso'
How can I install from a cdrom-image ?? Or do I really need to setup nfs (which will have the same effect I think) ?
 
Old 12-10-2009, 08:11 AM   #2
jonaskellens
Member
 
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 694

Original Poster
Rep: Reputation: 34
Forget the above, I haver worked around it by manually creating a disk-image and a configuration file.

However, I've come across another vehicle : network configuration !

This is my configuration file :

Code:
[root@xen ~]# cat /etc/xen/endian.cfg
import os, re
arch = os.uname()[4]

kernel = "/boot/vmlinuz-2.6.18-164.6.1.el5xen"

memory = 512
shadow_memory = 8
name = "endian"
vif = [ 'type=ioemu, bridge=eth0' ]
disk = [ 'file:/var/vm/endian/endian.img,hda,w', 'file:/tmp/endian/endian.iso,hdc:cdrom,r' ]
device_model = '/usr/lib/xen-default/bin/qemu-dm'
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"

sdl=0
vnc=1
vnclisten="0.0.0.0"
vncconsole=1
vncpasswd='endian'
stdvga=0
serial='pty'
usbdevice='tablet'

on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
When I start my vm, I get the following error :
Code:
[root@xen ~]# xm create endian.cfg
Using config file "/etc/xen/endian.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
These are my network interfaces :

Code:
[root@xen ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:22:B0:68:73:B9  
          inet6 addr: fe80::222:b0ff:fe68:73b9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13151 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1558 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1507358 (1.4 MiB)  TX bytes:156621 (152.9 KiB)

eth1      Link encap:Ethernet  HWaddr 00:24:21:54:70:22  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::224:21ff:fe54:7022/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8300 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5475 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:819918 (800.7 KiB)  TX bytes:1188729 (1.1 MiB)
          Interrupt:253 Base address:0xc000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1463 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2405572 (2.2 MiB)  TX bytes:2405572 (2.2 MiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:13151 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1558 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1559962 (1.4 MiB)  TX bytes:172357 (168.3 KiB)
          Interrupt:17 

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1558 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:156621 (152.9 KiB)  TX bytes:1507358 (1.4 MiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:11001 (10.7 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:12538 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1220739 (1.1 MiB)  TX bytes:0 (0.0 b)
eth0 is connected to the internet, and I want the interface of my xen vm to be directly connected to the internet.
So I state :
Code:
vif = [ 'type=ioemu, bridge=eth0' ]
which should mean that the virtual network interface of my endian-vm is connected with the 'real' network interface eth0 of dom0 and traffic flowing into eth0 is passed to my endian-vm.

I don't specify an IP-address because I get one through dhcp (of my isp).

Can someone advise on these network-troubles ??
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can I convert a xen .iso for use with qemu (kvm .iso)? aimGuy Linux - Virtualization and Cloud 2 10-16-2009 05:15 AM
XEN installation failing with hg command not found priyophan Linux - Server 1 04-25-2009 01:59 PM
install from iso cdrom is bad mahmoud Linux - Hardware 2 02-15-2008 07:13 AM
Xen in RHEL5: Unable to finish install of virtual domains (cannot access cdrom) Swakoo Red Hat 11 01-22-2008 09:48 PM
LILO install failing, Boot failing, but Installation fine. sramelyk Slackware 9 08-23-2003 02:37 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud

All times are GMT -5. The time now is 05:10 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration