virt September 2007

virt@lists.centos.org

14 participants
20 discussions

virt-factory investigation
by Hristo Benev 07 Sep '07

07 Sep '07

Version 0.0.4 is out, but unfortunately unly for F7 According to: https://www.redhat.com/archives/et-mgmt-tools/2007-September/msg00040.html EL5 will be soon available. All depends on busrpc(AMQP) package - available only in f7 for now. So we need to wait even more.... ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG

2 1

virt-factory investigation (Server setup)
by Hristo Benev 07 Sep '07

07 Sep '07

Hi, I was trying to get virt-factory on my CentOS 5. First I set up virt-factory repo (with fc6 packages). Then following installation documentation I've typed: ------------------------------------------ yum install virt-factory-server ------------------------------------------- Wich returned: ----------------------------------------------------------- Error: Missing Dependency: puppet-server >= 0.23 is needed by package virt-factory-server ----------------------------------------------------------- Searching arround: -------------------------------------------------------- yum list puppet-server Loading "priorities" plugin Loading "fastestmirror" plugin Loading "installonlyn" plugin Setting up repositories Loading mirror speeds from cached hostfile Reading repository metadata in from local files 0 packages excluded due to repository priority protections Available Packages puppet-server.i386 0.22.4-1.el5.rf rpmforge Appropriate version was found in FC6 extras Need to install first puppet: http://fedora.mirror.iweb.ca/extras/6/i386/puppet-0.23.2-1.fc6.noarch.rpm Wich required: ------------------------------------- Adding for dependencies: facter-1.3.7-1.el5.rf ruby-1.8.5-5.el5 ruby-libs-1.8.5-5.el5 -------------------------------------- And installed: http://fedora.mirror.iweb.ca/extras/6/i386/puppet-server-0.23.2-1.fc6.noarc… after Finally: ------------------------------------------- Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: virt-factory-server noarch 0.0.3-3 virt-factory-fedora 164 k Installing for dependencies: cobbler noarch 0.5.0-1.el5.rf rpmforge 330 k createrepo noarch 0.4.8-1.el5.rf rpmforge 55 k koan noarch 0.5.0-1.el5.rf rpmforge 50 k mod_python i386 3.2.8-3.1 base 257 k postgresql i386 8.1.9-1.el5 updates 2.8 M postgresql-server i386 8.1.9-1.el5 updates 4.0 M python-cheetah i386 2.0-0.1.rc8.el5.rf rpmforge 423 k python-migrate noarch 0.2.2-1 virt-factory-fedora 85 k python-psycopg2 i386 2.0.4-1.el5.rf rpmforge 259 k python-sqlalchemy noarch 0.3.4-1.el5.rf rpmforge 1.0 M python-sqlite2 i386 2.3.3-1.el5.rf rpmforge 119 k tftp-server i386 0.42-3.1.el5.centos base 27 k xinetd i386 2:2.3.14-10.el5 base 124 k yum-metadata-parser i386 1.0-8.fc6 base 22 k Transaction Summary ============================================================================= Install 15 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 9.7 M ------------------------------------------------------------------------ Note that currently only posgeqsl is supproted as database I do not use PGrs so I ran: -------------------------- vf_fix_db_auth ------------------------- To initialize DB. This finalizes Server installation. ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG

2 1

Re: virt-factory investigation (Server settings)
by Hristo Benev 04 Sep '07

04 Sep '07

Just followup on the problem. I asked in IRC channel and they told me that next version 0.0.4 will be released in a week and it will be better to wait. ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG

1 0

Re: virt-factory investigation (Server settings)
by Hristo Benev 04 Sep '07

04 Sep '07

I assume that I also need to configure server In /etc/virt-factory/settings ----------------------- databases: primary: "postgres://virtfactory:%(password)s@localhost/virtfactory" -------------------------- I do not know PG is this line correct? ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG

1 0

virt-factory investigation (Server settings)
by Hristo Benev 04 Sep '07

04 Sep '07

Hi, Next step is setting up mirrors fo virtual guest deployment This requires editing: ---------------------------- /etc/virt-factory/settings ---------------------------- This time I'll use FC6 mirrors to test product functionality. When editing this file setup local IP (not localhost) of the server. Next step is to start management server: -------------------------------------------- /etc/init.d/puppetmaster start Starting puppetmaster: [ OK ] -------------------------------------------- puppetmaster, apache, and virt-factory services could be set-up to start with the machine Then start the service: vf_server import Unfortunately I've recived error ----------------------------------------- vf_server import ***** CONFIG RELOAD ***** Traceback (most recent call last): File "/usr/bin/vf_server", line 12, in ? server.main(sys.argv) File "/usr/lib/python2.4/site-packages/virt-factory/server/server.py", line 185, in main websvc = XmlRpcInterface() File "/usr/lib/python2.4/site-packages/virt-factory/server/server.py", line 72, in __init__ Database(url) File "/usr/lib/python2.4/site-packages/virt-factory/server/db.py", line 346, in __init__ global_connect(interpolate_url_password(url), echo=False) File "/usr/lib/python2.4/site-packages/virt-factory/server/db.py", line 317, in interpolate_url_password pwfile = open("/etc/virt-factory/db/dbaccess") IOError: [Errno 2] No such file or directory: '/etc/virt-factory/db/dbaccess' ------------------------------------------------------ Any ideas what it could be? ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG

1 0

Virtual Box: br0 not resolving: No DHCPOFFERS
by Todd and Margo Chester 04 Sep '07

04 Sep '07

Dear Centos-Virt: Help! Guest=XP Pro, SP2 Host=CentOS5; # uname -r; 2.6.18-8.1.8.el5 VirtualBox-1.4.0_21864_rhel5-1.i586 http://www.virtualbox.org/download/1.5.0/VirtualBox-1.5.0_24069_rhel5-1.i58… I have two nic: eth0 is the internal network; eth1 connects to a DSL modem. I also have a fully functioning DHCP server on eth0 (works perfectly with Parallels for Linux). The directions (from hell): http://www.virtualbox.org/download/UserManual.pdf I am trying to set up a "host interface" network between my XP guest and my Linux host. Three problems: 1) "br0" does not resolve with my DHCP server: "No DHCPOFFERS received" 2) Virtual Box will not start, unless I switch to no network or NAT network 3) eth1 will not communicate with the Internet after restarting the network daemon to try to bet an address for br0 Following the directions on page 62 for Fedora Core in the users manual do not work (or I am doing them wrong): 1) # chmod 0666 /dev/net/tun 2) /etc/sysconfig/network-scripts/ifcfg-br0: DEVICE=br0 TYPE=Bridge BOOTPROTO=dhcp ONBOOT=yes 3) /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=Ethernet BOOTPROTO=static BROADCAST=192.168.255.255 IPADDR=192.168.255.10 NETMASK=255.255.255.0 NETWORK=192.168.255.0 GATEWAY=192.168.255.10 IPV6ADDR= IPV6PREFIX= ONBOOT=yes USERCTL=yes IPV6INIT=no PEERDNS=no BRIDGE=br0 4)# sudo /sbin/service network restart br0 failed: FAILED, unable to resolve IP address. From my /var/log/messages: dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER from 00:30:48:78:8e:92 via eth0 dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 dhclient: No DHCPOFFERS received. 5) #sudo VBoxAddIF vbox0 todd br0 Note: also tried it with user=root (did a VBoxDeleteIF first): no symptom change 6) In VirtualBox settings, set "network adaptors" to "Host Interface" and set “Interface name” to “vbox0” 7) started VB and got the same fail DHCP offcer as in step 4. VB refused to start. 8) at this point eth1 STOPS communicating with the DSL modem and the Internet (I have to comment out the "br" in eth0's config, restart the network daemon, and restart the firewall to get the Internet back.) Help! Many thanks, -T p.s. This is this is my full messages log when I restart networking (note the message at the end): #/etc/rc.d/init.d/network restart Aug 31 21:14:40 rn1 avahi-daemon[3207]: Withdrawing address record for fe80::230:48ff:fe78:8e92 on br0. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::230:48ff:fe78:8e92. Aug 31 21:14:40 rn1 avahi-daemon[3207]: iface.c: interface_mdns_mcast_join() called but no local address available. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Interface br0.IPv6 no longer relevant for mDNS. Aug 31 21:14:40 rn1 kernel: br0: port 1(eth0) entering disabled state Aug 31 21:14:40 rn1 kernel: br0: port 2(vbox0) entering disabled state Aug 31 21:14:40 rn1 avahi-daemon[3207]: Interface eth0.IPv6 no longer relevant for mDNS. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fe78:8e92. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Interface eth0.IPv4 no longer relevant for mDNS. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.255.10. Aug 31 21:14:40 rn1 dhcpd: receive_packet failed on eth0: Network is down Aug 31 21:14:40 rn1 avahi-daemon[3207]: Withdrawing address record for fe80::230:48ff:fe78:8e92 on eth0. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Withdrawing address record for 192.168.255.10 on eth0. Aug 31 21:14:40 rn1 kernel: device eth0 left promiscuous mode Aug 31 21:14:40 rn1 kernel: br0: port 1(eth0) entering disabled state Aug 31 21:14:40 rn1 avahi-daemon[3207]: Withdrawing address record for 192.168.1.47 on eth1. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.47. Aug 31 21:14:40 rn1 avahi-daemon[3207]: iface.c: interface_mdns_mcast_join() called but no local address available. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Interface eth1.IPv4 no longer relevant for mDNS. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Withdrawing address record for fe80::230:48ff:fe78:8e93 on eth1. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::230:48ff:fe78:8e93. Aug 31 21:14:40 rn1 avahi-daemon[3207]: iface.c: interface_mdns_mcast_join() called but no local address available. Aug 31 21:14:40 rn1 avahi-daemon[3207]: Interface eth1.IPv6 no longer relevant for mDNS. Aug 31 21:14:40 rn1 dhcpd: receive_packet failed on eth1: Network is down Aug 31 21:14:41 rn1 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Aug 31 21:14:41 rn1 kernel: device eth0 entered promiscuous mode Aug 31 21:14:41 rn1 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Aug 31 21:14:42 rn1 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex Aug 31 21:14:42 rn1 kernel: e1000: eth1: e1000_watchdog_task: 10/100 speed: disabling TSO Aug 31 21:14:42 rn1 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Aug 31 21:14:42 rn1 kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex Aug 31 21:14:42 rn1 kernel: e1000: eth0: e1000_watchdog_task: 10/100 speed: disabling TSO Aug 31 21:14:42 rn1 dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Aug 31 21:14:42 rn1 dhcpd: DHCPREQUEST for 192.168.1.47 from 00:30:48:78:8e:93 via eth1: unknown lease 192.168.1.47. Aug 31 21:14:42 rn1 dhclient: DHCPACK from 192.168.1.1 Aug 31 21:14:42 rn1 avahi-daemon[3207]: New relevant interface eth1.IPv4 for mDNS. Aug 31 21:14:42 rn1 avahi-daemon[3207]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.47. Aug 31 21:14:42 rn1 kernel: dsl-out Everything Else IN= OUT=eth1 SRC=192.168.1.47 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Aug 31 21:14:42 rn1 avahi-daemon[3207]: Registering new address record for 192.168.1.47 on eth1. Aug 31 21:14:42 rn1 avahi-daemon[3207]: Withdrawing address record for 192.168.1.47 on eth1. Aug 31 21:14:42 rn1 avahi-daemon[3207]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.47. Aug 31 21:14:42 rn1 kernel: dsl-out Everything Else IN= OUT=eth1 SRC=192.168.1.47 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Aug 31 21:14:42 rn1 avahi-daemon[3207]: iface.c: interface_mdns_mcast_join() called but no local address available. Aug 31 21:14:42 rn1 avahi-daemon[3207]: Interface eth1.IPv4 no longer relevant for mDNS. Aug 31 21:14:42 rn1 avahi-daemon[3207]: New relevant interface eth1.IPv4 for mDNS. Aug 31 21:14:42 rn1 avahi-daemon[3207]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.47. Aug 31 21:14:42 rn1 kernel: dsl-out Everything Else IN= OUT=eth1 SRC=192.168.1.47 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Aug 31 21:14:42 rn1 avahi-daemon[3207]: Registering new address record for 192.168.1.47 on eth1. Aug 31 21:14:42 rn1 dhclient: bound to 192.168.1.47 -- renewal in 38661 seconds. Aug 31 21:14:42 rn1 kernel: br0: port 1(eth0) entering learning state Aug 31 21:14:42 rn1 kernel: br0: port 2(vbox0) entering learning state Aug 31 21:14:43 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 4 Aug 31 21:14:43 rn1 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 31 21:14:44 rn1 avahi-daemon[3207]: New relevant interface eth1.IPv6 for mDNS. Aug 31 21:14:44 rn1 avahi-daemon[3207]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::230:48ff:fe78:8e93. Aug 31 21:14:44 rn1 avahi-daemon[3207]: Registering new address record for fe80::230:48ff:fe78:8e93 on eth1. Aug 31 21:14:44 rn1 avahi-daemon[3207]: New relevant interface br0.IPv6 for mDNS. Aug 31 21:14:44 rn1 avahi-daemon[3207]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::230:48ff:fe78:8e92. Aug 31 21:14:44 rn1 avahi-daemon[3207]: Registering new address record for fe80::230:48ff:fe78:8e92 on br0. Aug 31 21:14:45 rn1 avahi-daemon[3207]: New relevant interface eth0.IPv6 for mDNS. Aug 31 21:14:45 rn1 avahi-daemon[3207]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fe78:8e92. Aug 31 21:14:45 rn1 avahi-daemon[3207]: Registering new address record for fe80::230:48ff:fe78:8e92 on eth0. Aug 31 21:14:47 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 8 Aug 31 21:14:50 rn1 kernel: dsl-out Everything Else IN= OUT=eth1 SRC=192.168.1.47 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Aug 31 21:14:55 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 14 Aug 31 21:14:57 rn1 kernel: br0: topology change detected, propagating Aug 31 21:14:57 rn1 kernel: br0: port 1(eth0) entering forwarding state Aug 31 21:14:57 rn1 kernel: br0: topology change detected, propagating Aug 31 21:14:57 rn1 kernel: br0: port 2(vbox0) entering forwarding state Aug 31 21:15:09 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 15 Aug 31 21:15:09 rn1 dhcpd: DHCPDISCOVER from 00:30:48:78:8e:92 via eth0 Aug 31 21:15:10 rn1 dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 Aug 31 21:15:24 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 8 Aug 31 21:15:24 rn1 dhcpd: DHCPDISCOVER from 00:30:48:78:8e:92 via eth0 Aug 31 21:15:24 rn1 dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 Aug 31 21:15:32 rn1 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 12 Aug 31 21:15:32 rn1 dhcpd: DHCPDISCOVER from 00:30:48:78:8e:92 via eth0 Aug 31 21:15:32 rn1 dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 Aug 31 21:15:44 rn1 dhclient: No DHCPOFFERS received.

2 3

Re: [kvm-devel] kvm guests are not able to restart
by Farkas Levente 03 Sep '07

03 Sep '07

Luca wrote: > On 9/3/07, Farkas Levente <lfarkas(a)bppiac.hu> wrote: >> hi, >> i've got a centos-5 x86_64 kvm-35 host system with one centos-5 i386 and >> one x86_64 guests. but none of the guest are able to restart. ie. i >> login to the guests and restart it. it start's as normal reboot, but >> after the last command (shuting down md device) it's do nothing, but in >> virt-manager i see 50% load on the guest. the biggest problem currently >> i can't find any way to restart any guest's other then shutdown and use >> virt-manager and restart them:-( >> what can be a problem? is it a known bug or it's just not working for me? > > It's known, but ATM there's no fix available. For more details see: > http://thread.gmane.org/gmane.comp.emulators.kvm.devel/5651/focus=6003 > and following mails. is this really true? this means kvm are not usable any real environment since imho the feature to be able to reboot a server is essential! -- Levente "Si vis pacem para bellum!"

1 0

kvm guests are not able to restart
by Farkas Levente 03 Sep '07

03 Sep '07

hi, i've got a centos-5 x86_64 kvm-35 host system with one centos-5 i386 and one x86_64 guests. but none of the guest are able to restart. ie. i login to the guests and restart it. it start's as normal reboot, but after the last command (shuting down md device) it's do nothing, but in virt-manager i see 50% load on the guest. the biggest problem currently i can't find any way to restart any guest's other then shutdown and use virt-manager and restart them:-( what can be a problem? is it a known bug or it's just not working for me? thanks in advance. my system: kernel-2.6.18-8.1.8.el5 kernel-headers-2.6.18-8.1.8.el5 kmod-kvm-35-1.2.6.18_8.1.8.el5 kvm-35-1 libvirt-0.3.2-2 libvirt-python-0.3.2-2 python-virtinst-0.300.0-1 virt-manager-0.5.0-1 virt-top-0.3.2.5-1 virt-viewer-0.0.2-1 -- Levente "Si vis pacem para bellum!"

1 0

Proper use of this group?
by Todd and Margo Chester 02 Sep '07

02 Sep '07

Hi All, I am having a problem creating a tap device with Virtual Box. Is this the proper group to post such a problem to? (I have tons of error messages and documentation.) -T

2 2

Xen Minimal images for CentOS 4 and 5 x86_64
by Karanbir Singh 02 Sep '07

02 Sep '07

Hi, A while back I had created some minimal Xen images for centos-4 and centos-5 on x86_64 paravirt under a c5 x86_64 install. The images are at : http://www.karan.org/mock/Xen/ root account password for these images is : p4s5w0rd Feel free to look and use/abuse as you like, yum is completely functional within the images and its recommended you do a 'yum update' as soon as possible. If we can standardise on a packageset, these images can be built at the time we do a distro update. And can be done for all Arch and Versions that support Xen. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt September 2007