From rjones at redhat.com Wed Aug 1 13:07:44 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 01 Aug 2007 14:07:44 +0100 Subject: [Fedora-xen] AMD Opteron Quad Core CPU Availability In-Reply-To: <46A24776.3070102@speakeasy.net> References: <46A24776.3070102@speakeasy.net> Message-ID: <46B085A0.2000602@redhat.com> Robert L Cochran wrote: > Can anyone suggest a good retail source of AMD Opteron CPUs when the > quad core versions become available? Also what would be a good > motherboard for these CPUs. I assume the quad core units (all versions > and price levels of them) support full virtualization. I'm pretty sure Barcelona chips are unavailable except as engineering samples. Last I heard availability was tentatively scheduled for August[1]. Barcelona has full virtualisation -- not sure about "all versions and price levels", but certainly any version which you'd want to buy should support it. Should also supported nested page tables (boot the Xen hypervisor with hap=1 option to enable it). Rich. [1]http://www.amd.com/us-en/Corporate/VirtualPressRoom/0,,51_104_543~118193,00.html -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From s.jahangir at qut.edu.au Thu Aug 2 05:21:45 2007 From: s.jahangir at qut.edu.au (Selim Jahangir) Date: Thu, 2 Aug 2007 15:21:45 +1000 Subject: [Fedora-xen] AMD Opteron Quad Core CPU Availability In-Reply-To: <46B085A0.2000602@redhat.com> References: <46A24776.3070102@speakeasy.net> <46B085A0.2000602@redhat.com> Message-ID: <03DD0A35305B7045B436D107CDE9391A84888A@beeex03.qut.edu.au> Hi guys Have you anyone worked on tomcat and RHEL5 ? Please hints me on how to configure tomcat on RHEl5. I don't see the tomcat packages in RHEl5. Regards Muhammad Selim Jahangir Computer Systems Officer (UNIX/Linux Administrator) Faculty of Built Environment & Engineering Queensland University of Technology 2 George Street [GP Campus = S Block ? S913] Brisbane? QLD 4000 Email: s.jahangir at qut.edu.au Telephone: +61 7 3138 5018 Facsimile:? +61 7 3138 9022 Mobile: +61 422 639 965 QUT Institution Code: CRICOS No. 00213J -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Richard W.M. Jones Sent: Wednesday, August 01, 2007 11:08 PM To: Robert L Cochran Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] AMD Opteron Quad Core CPU Availability Robert L Cochran wrote: > Can anyone suggest a good retail source of AMD Opteron CPUs when the > quad core versions become available? Also what would be a good > motherboard for these CPUs. I assume the quad core units (all versions > and price levels of them) support full virtualization. I'm pretty sure Barcelona chips are unavailable except as engineering samples. Last I heard availability was tentatively scheduled for August[1]. Barcelona has full virtualisation -- not sure about "all versions and price levels", but certainly any version which you'd want to buy should support it. Should also supported nested page tables (boot the Xen hypervisor with hap=1 option to enable it). Rich. [1]http://www.amd.com/us-en/Corporate/VirtualPressRoom/0,,51_104_543~118193,00.html -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 From ukhanlists at hotmail.com Thu Aug 2 16:18:56 2007 From: ukhanlists at hotmail.com (Ubaidul Khan) Date: Thu, 02 Aug 2007 12:18:56 -0400 Subject: [Fedora-xen] AMD Opteron Quad Core CPU Availability In-Reply-To: <03DD0A35305B7045B436D107CDE9391A84888A@beeex03.qut.edu.au> Message-ID: The package name has changed. It's now called tomcat5. You should be able to install it via yum. Following is a list of associated packages: tomcat5.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5 Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. Tomcat is developed in an open and participatory environment and released under the Apache Software License. Tomcat is intended to be a collaboration of the best-of-breed developers from around the world. We invite you to participate in this open development project. To learn more about getting involved, click here. http://tomcat.apache.org/ tomcat5-servlet-2.4-api.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-servlet-2.4-api Jakarta Tomcat Servlet implementation classes Contains the implementation classes of the Jakarta Tomcat Servlet API (packages javax.servlet). http://tomcat.apache.org/ tomcat5-webapps.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-webapps Web applications for Jakarta Tomcat Web applications for Jakarta Tomcat http://tomcat.apache.org/ tomcat5-jsp-2.0-api-javadoc.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-jsp-2.0-api-javadoc Javadoc generated documentation for tomcat5-jsp-2.0-api Contains the javadoc generated documentation for the implementation classes of the Jakarta Tomcat JSP API (packages javax.servlet.jsp). http://tomcat.apache.org/ tomcat5-jsp-2.0-api.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-jsp-2.0-api Jakarta Tomcat Servlet and JSP implementation classes Contains the implementation classes of the Jakarta Tomcat JSP API (packages javax.servlet.jsp). http://tomcat.apache.org/ tomcat5-server-lib.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-server-lib Libraries needed to run the Tomcat Web container (part) Libraries needed to run the Tomcat Web container (part) http://tomcat.apache.org/ tomcat5-common-lib.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-common-lib Libraries needed to run the Tomcat Web container (part) Libraries needed to run the Tomcat Web container (part) http://tomcat.apache.org/ struts-webapps-tomcat5.x86_64 1.2.9-4jpp.5 GMU-RHEL5 Matched from: struts-webapps-tomcat5 Sample struts webapps for tomcat5 Sample struts webapps for tomcat5. tomcat5-servlet-2.4-api-javadoc.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-servlet-2.4-api-javadoc Javadoc generated documentation for tomcat5-servlet-2.4-api Contains the javadoc generated documentation for the implementation classes of the Jakarta Tomcat Servlet and JSP APIs (packages javax.servlet). http://tomcat.apache.org/ tomcat5-admin-webapps.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-admin-webapps The administrative web applications for Jakarta Tomcat The administrative web applications (admin and manager) for Jakarta Tomcat http://tomcat.apache.org/ tomcat5-jasper.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-jasper Compiler JARs and associated scripts for tomcat5 Compiler JARs and associated scripts for tomcat5 http://tomcat.apache.org/ tomcat5-jasper-javadoc.x86_64 5.5.17-8jpp.2 GMU-RHEL5 Matched from: tomcat5-jasper-javadoc Javadoc generated documentation for tomcat5-jasper Javadoc for generated documentation tomcat5-jasper http://tomcat.apache.org/ tomcat5-debuginfo.x86_64 5.5.17-8jpp.2 rhel-debuginfo Matched from: tomcat5-debuginfo Debug information for package tomcat5 This package provides debug information for package tomcat5. Debug information is useful when developing applications that use this package or when debugging this package. http://tomcat.apache.org/ tomcat5-debuginfo.x86_64 5.5.23-0jpp.1.0.3.el5 rhel-debuginfo Matched from: tomcat5-debuginfo Debug information for package tomcat5 This package provides debug information for package tomcat5. Debug information is useful when developing applications that use this package or when debugging this package. http://tomcat.apache.org/ tomcat5-debuginfo.x86_64 5.5.23-0jpp.1.0.4.el5 rhel-debuginfo Matched from: tomcat5-debuginfo Debug information for package tomcat5 This package provides debug information for package tomcat5. Debug information is useful when developing applications that use this package or when debugging this package. http://tomcat.apache.org/ >From: "Selim Jahangir" >To: "Richard W.M. Jones" ,"Robert L Cochran" > >CC: fedora-xen at redhat.com >Subject: RE: [Fedora-xen] AMD Opteron Quad Core CPU Availability >Date: Thu, 2 Aug 2007 15:21:45 +1000 > >Hi guys >Have you anyone worked on tomcat and RHEL5 ? Please hints me on how to >configure tomcat on RHEl5. I don't see the tomcat packages in RHEl5. > > > >Regards > >Muhammad Selim Jahangir >Computer Systems Officer >(UNIX/Linux Administrator) >Faculty of Built Environment & Engineering >Queensland University of Technology >2 George Street [GP Campus = S Block ?€“ S913] >Brisbane?? QLD 4000 >Email: s.jahangir at qut.edu.au >Telephone: +61 7 3138 5018 >Facsimile:?? +61 7 3138 9022 >Mobile: +61 422 639 965 >QUT Institution Code: CRICOS No. 00213J > > >-----Original Message----- >From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] >On Behalf Of Richard W.M. Jones >Sent: Wednesday, August 01, 2007 11:08 PM >To: Robert L Cochran >Cc: fedora-xen at redhat.com >Subject: Re: [Fedora-xen] AMD Opteron Quad Core CPU Availability > >Robert L Cochran wrote: > > Can anyone suggest a good retail source of AMD Opteron CPUs when the > > quad core versions become available? Also what would be a good > > motherboard for these CPUs. I assume the quad core units (all versions > > and price levels of them) support full virtualization. > >I'm pretty sure Barcelona chips are unavailable except as engineering >samples. Last I heard availability was tentatively scheduled for >August[1]. > >Barcelona has full virtualisation -- not sure about "all versions and price >levels", but certainly any version which you'd want to buy should support >it. Should also supported nested page tables (boot the Xen hypervisor with >hap=1 option to enable it). > >Rich. > >[1]http://www.amd.com/us-en/Corporate/VirtualPressRoom/0,,51_104_543~118193,00.html > >-- >Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered >Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, >Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under >Company Registration No. 03798903 > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen _________________________________________________________________ Booking a flight? Know when to buy with airfare predictions on MSN Travel. http://travel.msn.com/Articles/aboutfarecast.aspx&ocid=T001MSN25A07001 From ukhanlists at hotmail.com Thu Aug 2 16:24:00 2007 From: ukhanlists at hotmail.com (Ubaidul Khan) Date: Thu, 02 Aug 2007 12:24:00 -0400 Subject: [Fedora-xen] Hiding PCI devices from the hypervisor (dom0) Message-ID: Hi, I am trying to hide a PCI network card from the hypervisor. So I updated grub.conf with the following: title Red Hat Enterprise Linux Server (2.6.18-8.1.1.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-8.1.1.el5 physdev_dom0_hide=(01:01.1) module /vmlinuz-2.6.18-8.1.1.el5xen ro root=LABEL=/ rhgb quiet module /initrd-2.6.18-8.1.1.el5xen.img But the device still shows up on dom0. The version of Xen I'm running is: xen-3.0.3-25.0.3.el5 Any help is appreciated. _________________________________________________________________ Booking a flight? Know when to buy with airfare predictions on MSN Travel. http://travel.msn.com/Articles/aboutfarecast.aspx&ocid=T001MSN25A07001 From per at actius.com Mon Aug 6 06:07:54 2007 From: per at actius.com (Per Hjartoy) Date: Sun, 5 Aug 2007 23:07:54 -0700 Subject: [Fedora-xen] Installation trouble with CD-RW? Message-ID: <008c01c7d7f0$21197d70$20111bac@actius.com> All, I'm bringing up a new Fedora 7 server (quad core, about 1TByte Raid 5 disk). Fedora installed without any problem and the upgrade to the Xen kernel went without incident. I ran into problems after installing Windows 2003. The copying went fine, but when I got to the step to manually restart the virtual image I get the following error message: virDomainCreate() failed POST operation failed: (xend.err 'Device 5632 (vbd) could not be connected.\nDevice /dev/ is mounted read-write in the privileged domain,\nand so cannot be mounted read-only by a guest.') I'm inclined to point the blame at the factory installed CD-RW/DVD since I put the NTFS in a file during Xen setup. The questions for the group are: Is this expected behavior? If yes, can I disable the write option on the CD-RW so it become a read-only block device? Or am I mistaken about the CD-RW? My server configuration is simple: Dell 2900 Quad Core Raid 5 3x500GB WD disks Built in Broadcom 2x Ethernet Clean installation of Fedora 7 without anything extra added. -- Per -------------- next part -------------- An HTML attachment was scrubbed... URL: From zimmermann at ccrl-nece.de Fri Aug 3 15:17:18 2007 From: zimmermann at ccrl-nece.de (Falk Zimmermann) Date: Fri, 03 Aug 2007 17:17:18 +0200 Subject: [Fedora-xen] Problem with virt-manager Message-ID: <46B346FE.9080806@ccrl-nece.de> I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and using virt-manager to configure an F7 guest domain. Immediately after starting the installation process I receive the following error message: Unable to complete install: 'virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (tap) could not be connected.\n/home/falk/images/f6u1_img does not exist.')' Details: Unable to complete install ' virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (tap) could not be connected.\n/home/falk/images/f6u1_img does not exist.') Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 681, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 480, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (tap) could not be connected.\n/home/falk/images/f6u1_img does not exist.') ' I receive the message independent of the file I choose. The systems always considers it as non-existing. Has anyone experienced and solved this problem? Thanks, Falk -------------- next part -------------- A non-text attachment was scrubbed... Name: zimmermann.vcf Type: text/x-vcard Size: 787 bytes Desc: not available URL: From armbru at redhat.com Mon Aug 6 08:27:52 2007 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 06 Aug 2007 10:27:52 +0200 Subject: [Fedora-xen] Problem with virt-manager In-Reply-To: <46B346FE.9080806@ccrl-nece.de> (Falk Zimmermann's message of "Fri\, 03 Aug 2007 17\:17\:18 +0200") References: <46B346FE.9080806@ccrl-nece.de> Message-ID: <87vebtawzb.fsf@pike.pond.sub.org> Falk Zimmermann writes: > I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and > using virt-manager to configure an F7 guest domain. > Immediately after starting the installation process I receive the > following error message: > > Unable to complete install: 'virDomainCreateLinux() failed POST > operation failed: (xend.err 'Device 51712 (tap) could not be > connected.\n/home/falk/images/f6u1_img does not exist.')' > > Details: > Unable to complete install ' > virDomainCreateLinux() failed POST operation failed: (xend.err 'Device > 51712 (tap) could not be connected.\n/home/falk/images/f6u1_img does > not exist.') > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/create.py", line 681, in > do_install > dom = guest.start_install(False, meter = meter) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 710, > in start_install > return self._do_install(consolecb, meter) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, > in _do_install > self.domain = self.conn.createLinux(install_xml, 0) > File "/usr/lib64/python2.5/site-packages/libvirt.py", line 480, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed', > conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: > (xend.err 'Device 51712 (tap) could not be > connected.\n/home/falk/images/f6u1_img does not exist.') > ' > I receive the message independent of the file I choose. The systems > always considers it as non-existing. > > Has anyone experienced and solved this problem? > > Thanks, > Falk SELinux? Does it work when you put your image in /var/lib/xen/images/ ? From kraxel at redhat.com Mon Aug 6 09:04:30 2007 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 06 Aug 2007 11:04:30 +0200 Subject: [Fedora-xen] Running SLES 10 as pv guest in Fedora 7 In-Reply-To: <46A8DA8F.8050102@web.de> References: <46A8DA8F.8050102@web.de> Message-ID: <46B6E41E.3090904@redhat.com> Felix Schwarz wrote: > Hi, > > I tried to run a SLES 10 installation as (pv) guest in Fedora 7 but the > guest does not start. > I found Gerd Hoffmann's very helpful page > http://et.redhat.com/~kraxel/xen/suse-guest.html and tried to > incorporate his suggestions regarding the domUloader. Hmm, looks like the page needs some updating ... Some patches by the solaris guys for pygrub made booting sles (and opensuse) easier in xen 3.1 (I think 3.0.4 too). You can simply put these lines into your config file ... kernel=/boot/vmlinux-xen ramdisk=/boot/initrd-xen bootloader=/usr/bin/pygrub ... and pygrub will go and pull kernel+ramdisk from the guest disk without looking for a config file on the guest disk. No need for domUloader any more. HTH, Gerd PS: all IIRC, havn't actually tried that for some time. From zimmermann at ccrl-nece.de Mon Aug 6 09:08:10 2007 From: zimmermann at ccrl-nece.de (Falk Zimmermann) Date: Mon, 06 Aug 2007 11:08:10 +0200 Subject: [Fedora-xen] Problem with virt-manager In-Reply-To: <87vebtawzb.fsf@pike.pond.sub.org> References: <46B346FE.9080806@ccrl-nece.de> <87vebtawzb.fsf@pike.pond.sub.org> Message-ID: <46B6E4FA.2070303@ccrl-nece.de> >> I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and >> using virt-manager to configure an F7 guest domain. >> Immediately after starting the installation process I receive the >> following error message: >> >> Unable to complete install: 'virDomainCreateLinux() failed POST >> operation failed: (xend.err 'Device 51712 (tap) could not be >> connected.\n/home/falk/images/f6u1_img does not exist.')' >> >> Details: >> Unable to complete install ' >> virDomainCreateLinux() failed POST operation failed: (xend.err 'Device >> 51712 (tap) could not be connected.\n/home/falk/images/f6u1_img does >> not exist.') >> Traceback (most recent call last): >> File "/usr/share/virt-manager/virtManager/create.py", line 681, in >> do_install >> dom = guest.start_install(False, meter = meter) >> File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 710, >> in start_install >> return self._do_install(consolecb, meter) >> File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, >> in _do_install >> self.domain = self.conn.createLinux(install_xml, 0) >> File "/usr/lib64/python2.5/site-packages/libvirt.py", line 480, in >> createLinux >> if ret is None:raise libvirtError('virDomainCreateLinux() failed', >> conn=self) >> libvirtError: virDomainCreateLinux() failed POST operation failed: >> (xend.err 'Device 51712 (tap) could not be >> connected.\n/home/falk/images/f6u1_img does not exist.') >> ' >> I receive the message independent of the file I choose. The systems >> always considers it as non-existing. >> >> Has anyone experienced and solved this problem? >> >> Thanks, >> Falk >> > > SELinux? Does it work when you put your image in > /var/lib/xen/images/ ? > > That was the problem. Many thanks, Falk From acathrow at redhat.com Mon Aug 6 11:37:11 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 06 Aug 2007 07:37:11 -0400 Subject: [Fedora-xen] Running SLES 10 as pv guest in Fedora 7 In-Reply-To: <46B6E41E.3090904@redhat.com> References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> Message-ID: <1186400231.17484.28.camel@aic-f7.cathrow.org> On Mon, 2007-08-06 at 11:04 +0200, Gerd Hoffmann wrote: > Felix Schwarz wrote: > > Hi, > > > > I tried to run a SLES 10 installation as (pv) guest in Fedora 7 but the > > guest does not start. > > > I found Gerd Hoffmann's very helpful page > > http://et.redhat.com/~kraxel/xen/suse-guest.html and tried to > > incorporate his suggestions regarding the domUloader. > > Hmm, looks like the page needs some updating ... > > Some patches by the solaris guys for pygrub made booting sles (and > opensuse) easier in xen 3.1 (I think 3.0.4 too). You can simply put > these lines into your config file ... > > kernel=/boot/vmlinux-xen > ramdisk=/boot/initrd-xen > bootloader=/usr/bin/pygrub > > ... and pygrub will go and pull kernel+ramdisk from the guest disk > without looking for a config file on the guest disk. No need for > domUloader any more. I know that SLES10SP1 will run on RHEL5.1beta - I'm running a PV guest. I ended up copying the vmlinux-xenpae and initrd-xenpae outside of the guest - on the dom0 filesystem. I didn't debug too deeply but using reiserfs was probably by first mistake ,,,,,,, > > HTH, > Gerd > > PS: all IIRC, havn't actually tried that for some time. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.schwarz at web.de Mon Aug 6 14:00:35 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Mon, 06 Aug 2007 16:00:35 +0200 Subject: [Fedora-xen] Re: Running SLES 10 as pv guest in Fedora 7 In-Reply-To: <1186400231.17484.28.camel@aic-f7.cathrow.org> References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> <1186400231.17484.28.camel@aic-f7.cathrow.org> Message-ID: <46B72983.5070703@web.de> Andrew Cathrow schrieb: > I ended up copying the vmlinux-xenpae and initrd-xenpae outside of the > guest - on the dom0 filesystem. I think, I do not need vmlinux-xenpae etc. if I use 64 Bit Dom0/DomU, correct? > I didn't debug too deeply but using reiserfs was probably by first > mistake ,,,,,,, At least that is no problem to me: I never chose reiserfs as I don't trust this fs. .-) fs From acathrow at redhat.com Mon Aug 6 15:17:30 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 06 Aug 2007 11:17:30 -0400 Subject: [Fedora-xen] Re: Running SLES 10 as pv guest in Fedora 7 In-Reply-To: <46B72983.5070703@web.de> References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> <1186400231.17484.28.camel@aic-f7.cathrow.org> <46B72983.5070703@web.de> Message-ID: <1186413450.18972.4.camel@aic-f7.cathrow.org> On Mon, 2007-08-06 at 16:00 +0200, Felix Schwarz wrote: > Andrew Cathrow schrieb: > > I ended up copying the vmlinux-xenpae and initrd-xenpae outside of the > > guest - on the dom0 filesystem. > > I think, I do not need vmlinux-xenpae etc. if I use 64 Bit Dom0/DomU, correct? Correct > > > I didn't debug too deeply but using reiserfs was probably by first > > mistake ,,,,,,, > > At least that is no problem to me: I never chose reiserfs as I don't trust this > fs. .-) Yeah - comes from be hitting next, next, next > > fs > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From mnielsen at redhat.com Mon Aug 6 15:25:37 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Mon, 06 Aug 2007 11:25:37 -0400 Subject: [Fedora-xen] xen networking Message-ID: <46B73D71.1040709@redhat.com> Since I have not yet been able to resolve my complex networking issues in RHEL 5, I decided to upgrade 1 of my cluster nodes to 5.1 beta and take this new libvirt networking for a spin. I'm not sure if this is going to make my issue easier to resolve, or add to the complexity so I'm writing this e-mail to hopefully get some suggestions as how to proceed. My network looks like this: eth2 & eth3 comprise bond1 bond1 has bond1.48 - my public VLAN interface with an IP for dom0 bond1 has bond1.20 - my VLAN for some domU systems, dom0 has no IP on this VLAN bond1 has bond1.21 - my VLAN for some domU systems, dom0 has no IP on this VLAN I want to bridge to bond1.20 from some domU systems, and bond1.21 from other domU systems. dom0 should not have an IP on these VLANs. 1) do I need to define a network interface in /etc/libvirt/qemu/networks/ for each VLAN? (bond1.20 and bond1.21) 1a) If yes, do I need to have an IP address for the bond1.20 and bond1.21 interface defined in /etc/sysconfig/network-scripts/ifcfg-bond1.20 and bond1.21? 1b) Do I also need to define an IP address on that VLAN in the .xml file for that network? or 2) Can I just have 1 default.xml network and then use iptables to forward to a specific VLAN based on bond1.20 and bond1.21 configured in /etc/sysconfig/network-scripts/ ?? #2 would be best, if possible. Unfortunately there's not a lot of documentation out on the new networking methods. I've read http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt but that doesn't get in to all the VLANs and bonds. Any help is greatly appreciated! -------------- next part -------------- A non-text attachment was scrubbed... Name: mnielsen.vcf Type: text/x-vcard Size: 177 bytes Desc: not available URL: From bkearney at redhat.com Mon Aug 6 15:34:35 2007 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 06 Aug 2007 11:34:35 -0400 Subject: [Fedora-xen] F7 guest install failing on stage2.img Message-ID: <46B73F8B.7020404@redhat.com> I am attempting to install a paravitualized F7 guest (from this location http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/) onto an FC7 Domu (kernel 2925). It goes through the download process, but continues to fail on the following line from the debug console (Alt-F3): INFO: 519444 kB are available INFO: transferring http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/disc1/images/stage2.img to a fd This occurs whether I install to a file system (in /var/lib/xen/images) or to a raw partition. Is there a simple config issue which I am not selecting? -- bk From berrange at redhat.com Mon Aug 6 15:41:31 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 6 Aug 2007 16:41:31 +0100 Subject: [Fedora-xen] F7 guest install failing on stage2.img In-Reply-To: <46B73F8B.7020404@redhat.com> References: <46B73F8B.7020404@redhat.com> Message-ID: <20070806154131.GD14393@redhat.com> On Mon, Aug 06, 2007 at 11:34:35AM -0400, Bryan Kearney wrote: > I am attempting to install a paravitualized F7 guest (from this location > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/) > onto an FC7 Domu (kernel 2925). It goes through the download process, but > continues to fail on the following line from the debug console (Alt-F3): > > INFO: 519444 kB are available > INFO: transferring > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/disc1/images/stage2.img > to a fd > > This occurs whether I install to a file system (in /var/lib/xen/images) > or to a raw partition. Is there a simple config issue which I am not > selecting? The 'Everything' location is not an installable tree - it has no 'images' directory with install images - its merely a YUM repo. For initial install use http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/ Once installed you can still access all Fedora RPMs. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From admin at dougware.net Mon Aug 6 15:28:55 2007 From: admin at dougware.net (Doug Eubanks) Date: Mon, 06 Aug 2007 11:28:55 -0400 Subject: =?iso-8859-1?Q?Re=3A_=5BFedora-xen=5D_Any_workaround_available_for?= =?iso-8859-1?Q?_my_SCSI_problem=3F?= In-Reply-To: 20070726161247.57a026e3@mail.dougware.net Message-ID: <20070806152855.93feeae0@mail.dougware.net> So I did some experimenting this weekend.... Using the latest development xen kernel (2.6.21-2925.14-fc8) I get the same SCSI errors, unless I remove the acpi=off and noapic. Then it complains very little and boots up. However, I can not create a guest, the kernel crashes completely when I go to create the guest. I am thinking about going back to the latest stable xen kernel and remove the acpi=off and noapic and see if it boots and allows me to create a guest. The problem is that under the standard kernel, without acpi=off and noapic, my system randomly freezes. Any insight or opinions on this matter would be awesome! Doug _____ From: Doug Eubanks [mailto:admin at dougware.net] To: fedora-xen at redhat.com Sent: Thu, 26 Jul 2007 12:12:47 -0400 Subject: [Fedora-xen] Any workaround available for my SCSI problem? Has there been any word or workaround to the SCSI problem I reported with the xen kernel earlier this month? Thanks, Doug Eubanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkearney at redhat.com Mon Aug 6 17:23:13 2007 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 06 Aug 2007 13:23:13 -0400 Subject: [Fedora-xen] F7 guest install failing on stage2.img In-Reply-To: <20070806154131.GD14393@redhat.com> References: <46B73F8B.7020404@redhat.com> <20070806154131.GD14393@redhat.com> Message-ID: <46B75901.3090101@redhat.com> Thanks... same issue tho: 519444 kB are available http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os//images/stage2.img to a fd http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os//disc1/images/stage2.img to a fd I am using the virt-manager GUI with no kickstart file. Is that a bad config? -- bk Daniel P. Berrange wrote: > On Mon, Aug 06, 2007 at 11:34:35AM -0400, Bryan Kearney wrote: > >> I am attempting to install a paravitualized F7 guest (from this location >> http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/) >> onto an FC7 Domu (kernel 2925). It goes through the download process, but >> continues to fail on the following line from the debug console (Alt-F3): >> >> INFO: 519444 kB are available >> INFO: transferring >> http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/disc1/images/stage2.img >> to a fd >> >> This occurs whether I install to a file system (in /var/lib/xen/images) >> or to a raw partition. Is there a simple config issue which I am not >> selecting? >> > > The 'Everything' location is not an installable tree - it has no 'images' > directory with install images - its merely a YUM repo. For initial install > use > > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/ > > Once installed you can still access all Fedora RPMs. > > Regards, > Dan. > From berrange at redhat.com Mon Aug 6 21:31:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 6 Aug 2007 22:31:24 +0100 Subject: [Fedora-xen] Re: [Libvir] ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats In-Reply-To: <46B78F84.10309@redhat.com> References: <46B78F84.10309@redhat.com> Message-ID: <20070806213124.GG30665@redhat.com> On Mon, Aug 06, 2007 at 10:15:48PM +0100, Richard W.M. Jones wrote: > There are a few data collection artifacts which need to be investigated. > In particular, %CPU sometimes goes over 100%. Obviously accurate data > collection is an important goal for this tool. AFAICT it is impossible to stop it going over 100% - we have same issue in virt-manager when calculating CPU usage. To caculate the % usage you are looking at the differential between CPU time from two calls to virDomainGetInfo vs the time period between two gettimeofday() calls. If the time delta between your gettimeofday() calls does not exactly match the time delta between your virDomainGetInfo() calls, and the domain you're measuring is very active then you can end up calcuating > 100% occassionally. Not by much - typically < 1% over, but I don't really see any way around it. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From rjones at redhat.com Mon Aug 6 21:15:48 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 06 Aug 2007 22:15:48 +0100 Subject: [Fedora-xen] ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats Message-ID: <46B78F84.10309@redhat.com> I'm pleased to announce the first release of virt-top, which is a top-like utility for displaying virtualization stats. It aims to look and feel very much like regular 'top', so as to be as familiar as possible for systems administrators. You can also use it as a pleasant replacement for xentop. It uses libvirt, so can display stats across a variety of different hypervisors and virtualization systems (not just Xen, although that is where the testing has gone so far). http://et.redhat.com/~rjones/virt-top/ The license is a combination of LGPL (for the library) and GPL (for the virt-top program). Current status -------------- You can view domains and use familiar keys like 'P'/'M'/... to sort by processor/memory/..., and 'd'/'s' to set the delay between updates. Also some common top command-line options are implemented. The man page is here: http://et.redhat.com/~rjones/virt-top/virt-top.txt There are a variety of source and binary RPMs available for Fedora users. I don't yet have a working Debian/Ubuntu package, but will have a go at making one tomorrow. The next thing I'll be working on is showing virtual and physical CPU usage of guests. After that I'm hoping to discuss extensions to libvirt to make other interesting statistics available to virt-top, in particular disk and network I/O stats. There are a few data collection artifacts which need to be investigated. In particular, %CPU sometimes goes over 100%. Obviously accurate data collection is an important goal for this tool. Memory usage is good: typical 'RES' (in regular top) for virt-top is just under 2.5 MB, and I've had it running for hours at a time without memory usage increasing, which seems to indicate that there aren't any major memory leaks. Development ----------- The program is currently very small: exactly 500 lines of code! If you want to dive in and send me patches they are most welcome, but remember that I'm trying to make this utility act as much like 'top' as possible, so if 'top' does it in a particular way, then I'd prefer virt-top to do the same thing. (May not apply to obscure top functionality, if top does something silly). If you're a systems administrator, not a programmer, and you'd like virt-top to have some particular feature, then please let me know, and I will be happy to review it and code it for you. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: virt-top.png Type: image/png Size: 38338 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From tom.horsley at att.net Mon Aug 6 23:18:35 2007 From: tom.horsley at att.net (Tom Horsley) Date: Mon, 6 Aug 2007 19:18:35 -0400 Subject: [Fedora-xen] Re: [Libvir] ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats In-Reply-To: <20070806213124.GG30665@redhat.com> References: <46B78F84.10309@redhat.com> <20070806213124.GG30665@redhat.com> Message-ID: <20070806191835.38086472@zooty> On Mon, 6 Aug 2007 22:31:24 +0100 "Daniel P. Berrange" wrote: > If the time delta between your gettimeofday() calls does not exactly > match the time delta between your virDomainGetInfo() calls, and the > domain you're measuring is very active then you can end up calcuating > > 100% occassionally. Not by much - typically < 1% over, but I don't > really see any way around it. Shucks, it is easy to work around: if (percentcpu > 100) percentcpu = 100; :-). From berrange at redhat.com Tue Aug 7 03:33:07 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 7 Aug 2007 04:33:07 +0100 Subject: [Fedora-xen] Re: [Libvir] ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats In-Reply-To: <20070806191835.38086472@zooty> References: <46B78F84.10309@redhat.com> <20070806213124.GG30665@redhat.com> <20070806191835.38086472@zooty> Message-ID: <20070807033307.GA25531@redhat.com> On Mon, Aug 06, 2007 at 07:18:35PM -0400, Tom Horsley wrote: > On Mon, 6 Aug 2007 22:31:24 +0100 > "Daniel P. Berrange" wrote: > > > If the time delta between your gettimeofday() calls does not exactly > > match the time delta between your virDomainGetInfo() calls, and the > > domain you're measuring is very active then you can end up calcuating > > > 100% occassionally. Not by much - typically < 1% over, but I don't > > really see any way around it. > > Shucks, it is easy to work around: > > if (percentcpu > 100) percentcpu = 100; When I said "i don't see any way around it" I meant a way which would be calculating correct/accurate figures. Clamping to 100% is just pretending the problem doesn't exist - though it is the hack I am already using in virt-manager. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From suyashjape at gmail.com Tue Aug 7 07:37:16 2007 From: suyashjape at gmail.com (suyash jape) Date: Tue, 7 Aug 2007 13:07:16 +0530 Subject: [Fedora-xen] Problem installing Windows2003 Server on Xen Server 30 day trial Message-ID: <16314edc0708070037t496fde27j8deb27cd150ec274@mail.gmail.com> Hi all, I am using Xen Server ( 30 day trial ) on Intel VT Clovertown server with 8 cpus and 16gb RAM. I am trying to install Windows2003 Enterprise Edition on this setup. The Windows setup starts up fine , but at the time of copying files from CD , it is not able to copy a number of DLLs, .aspx,.exe, .js and so many other files from the i386 folder of the windows cd. When i skip the copying of these numerous files, finally windows is installed but without most of its features.(obviously) The installation cd is working absolutely fine when i install Windows 2003 on some other desktop machines and fully functional windows can be installed on the desktops. So i think the problem maybe with paravirtualization/VT hardware. The VT flag is enabled in BIOS.I am able to install FC4 ,FC6, SuSE 10.1, Debian. Does anyone have an idea about why this may be happening?? (Setup unable to copy files from i386 folder of installation cd ) This is my machine configuration. root at xenserver1 ~]# uname -a Linux xenserver1 2.6.16.38-xs3.2.0.531.3960xen #1 SMP Sat Mar 24 17:19:06 EDT 2007 i686 i686 i386 GNU/Linux [root at xenserver1 ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Genuine Intel(R) CPU @ 2.40GHz stepping : 5 cpu MHz : 2399.994 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips : 4801.57 Also let me know if there an appropriate forum/list to post problems about Xen Server Thanks Suyash -------------- next part -------------- An HTML attachment was scrubbed... URL: From ask at develooper.com Tue Aug 7 10:18:03 2007 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Tue, 7 Aug 2007 03:18:03 -0700 Subject: [Fedora-xen] i386 domU on x86_64 dom0 Message-ID: <408B9F9F-AF22-4EE6-B38F-02417E811BF4@develooper.com> Hi everyone, Most of our virtual machines could happily be i386 (and save a bit of memory). I prefer the dom0s to be x86_64 for some added flexibility for applications that do need 64bit (MySQL, memcached, varnish). I upgraded one of our boxes to F7 to get Xen 3.1 since it's supposed to be possible there. But it crashes pretty fast every time. I am running the latest kernel and xen in the dom0 and just the release tree in the domU. Any ideas? - ask Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Oops: 0000 [#1] SMP last sysfs file: /class/graphics/fb0/name Modules linked in: xenblk xennet iscsi_tcp libiscsi scsi_transport_iscsi sr_mod sd_mod scsi_mod cdrom ipv6 ext2 ext3 mbcache jbd squashfs pcspkr loop nfs nfs_acl lockd sunrpc vfat fat cramfs CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010097 (2.6.20-2925.9.fc7xen #1) EIP is at blkif_int+0x105/0x18c [xenblk] eax: 00000000 ebx: c252e000 ecx: c02d1550 edx: 00000000 esi: 00000001 edi: ed6b40ac ebp: c135ffc8 esp: c135ff9c ds: 007b es: 007b ss: 0069 Process init (pid: 243, ti=c135f000 task=c02d1550 task.ti=c1cb0000) Stack: 00000000 c135ffc8 00000000 00000001 00000002 00000001 ca000100 da537c5c ed78f580 00000000 00000000 c135ffe0 c1048ee9 0000010e c12fdb00 0000010e ed78f580 c135fff8 c104a2e4 c12fdb28 c1cb0e84 0000010e c104a24a c1cb0ea0 Call Trace: [] show_trace_log_lvl+0x1a/0x2f [] show_stack_log_lvl+0x9b/0xa3 [] show_registers+0x194/0x26a [] die+0x131/0x246 [] do_page_fault+0xafc/0xc80 [] error_code+0x35/0x3c [] handle_IRQ_event+0x1a/0x4a [] handle_level_irq+0x9a/0xea [] do_IRQ+0xc6/0xee [] evtchn_do_upcall+0x62/0x9b [] hypervisor_callback+0x46/0x50 [] raw_local_irq_enable+0x20/0x22 [] _spin_unlock_irq+0x27/0x2a [] do_syslog+0x122/0x30e [] kmsg_read+0x34/0x3c [] vfs_read+0xad/0x161 [] sys_read+0x3d/0x61 [] syscall_call+0x7/0xb ======================= Code: ff c7 04 24 58 e5 33 ee 83 c0 0c 89 44 24 04 e8 5c 20 ce d2 89 d8 c7 83 e0 13 00 00 00 00 00 00 e8 87 05 00 00 8b 55 dc 8b 45 dc <8b> 4a 30 89 f2 e8 98 02 d9 d2 85 c0 74 04 0f 0b eb fe 8b 45 dc EIP: [] blkif_int+0x105/0x18c [xenblk] SS:ESP 0069:c135ff9c <0>Kernel panic - not syncing: Fatal exception in interrupt BUG: at arch/i386/kernel/smp-xen.c:530 smp_call_function() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x16/0x18 [] smp_call_function+0x60/0xfb [] smp_send_stop+0x1e/0x34 [] panic+0x54/0x188 [] die+0x211/0x246 [] do_page_fault+0xafc/0xc80 [] error_code+0x35/0x3c [] handle_IRQ_event+0x1a/0x4a [] handle_level_irq+0x9a/0xea [] do_IRQ+0xc6/0xee [] evtchn_do_upcall+0x62/0x9b [] hypervisor_callback+0x46/0x50 [] raw_local_irq_enable+0x20/0x22 [] _spin_unlock_irq+0x27/0x2a [] do_syslog+0x122/0x30e [] kmsg_read+0x34/0x3c [] vfs_read+0xad/0x161 [] sys_read+0x3d/0x61 [] syscall_call+0x7/0xb ======================= [....] drivers/usb/input/hid-core.c: v2.6:USB HID core driver BUG: at kernel/fork.c:994 copy_process() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x16/0x18 [] copy_process+0x195/0x1245 [] do_fork+0x50/0x117 [] kernel_thread+0x8e/0x96 [] __call_usermodehelper+0x2d/0x46 [] run_workqueue+0x89/0x145 [] worker_thread+0xd5/0x102 [] kthread+0xb3/0xdc [] kernel_thread_helper+0x7/0x10 ======================= PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Oops: 0000 [#1] SMP last sysfs file: /class/graphics/fb0/name Modules linked in: xenblk xennet iscsi_tcp libiscsi scsi_transport_iscsi sr_mod sd_mod scsi_mod cdrom ipv6 ext2 ext3 mbcache jbd squashfs pcspkr loop nfs nfs_acl lockd sunrpc vfat fat cramfs CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010097 (2.6.20-2925.9.fc7xen #1) EIP is at blkif_int+0x105/0x18c [xenblk] eax: 00000000 ebx: c252e000 ecx: 00000000 edx: 00000000 esi: 00000001 edi: ed6e20ac ebp: c135ffc8 esp: c135ff9c ds: 007b es: 007b ss: 0069 Process init (pid: 243, ti=c135f000 task=c02ce030 task.ti=c1cb0000) Stack: 00000000 c135ffc8 00000000 00000001 00000002 00000001 ca000100 da537c5c c1cd84a0 00000000 00000000 c135ffe0 c1048ee9 0000010e c12fdb00 0000010e c1cd84a0 c135fff8 c104a2e4 c12fdb28 c1cb0e84 0000010e c104a24a c1cb0ea0 Call Trace: [] show_trace_log_lvl+0x1a/0x2f [] show_stack_log_lvl+0x9b/0xa3 [] show_registers+0x194/0x26a [] die+0x131/0x246 [] do_page_fault+0xafc/0xc80 [] error_code+0x35/0x3c [] handle_IRQ_event+0x1a/0x4a [] handle_level_irq+0x9a/0xea [] do_IRQ+0xc6/0xee [] evtchn_do_upcall+0x62/0x9b [] hypervisor_callback+0x46/0x50 [] raw_local_irq_enable+0x20/0x22 [] _spin_unlock_irq+0x27/0x2a [] do_syslog+0x122/0x30e [] kmsg_read+0x34/0x3c [] vfs_read+0xad/0x161 [] sys_read+0x3d/0x61 [] syscall_call+0x7/0xb ======================= Code: ff c7 04 24 58 e5 33 ee 83 c0 0c 89 44 24 04 e8 5c 20 ce d2 89 d8 c7 83 e0 13 00 00 00 00 00 00 e8 87 05 00 00 8b 55 dc 8b 45 dc <8b> 4a 30 89 f2 e8 98 02 d9 d2 85 c0 74 04 0f 0b eb fe 8b 45 dc EIP: [] blkif_int+0x105/0x18c [xenblk] SS:ESP 0069:c135ff9c <0>Kernel panic - not syncing: Fatal exception in interrupt BUG: at arch/i386/kernel/smp-xen.c:530 smp_call_function() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x16/0x18 [] smp_call_function+0x60/0xfb [] smp_send_stop+0x1e/0x34 [] panic+0x54/0x188 [] die+0x211/0x246 [] do_page_fault+0xafc/0xc80 [] error_code+0x35/0x3c [] handle_IRQ_event+0x1a/0x4a [] handle_level_irq+0x9a/0xea [] do_IRQ+0xc6/0xee [] evtchn_do_upcall+0x62/0x9b [] hypervisor_callback+0x46/0x50 [] raw_local_irq_enable+0x20/0x22 [] _spin_unlock_irq+0x27/0x2a [] do_syslog+0x122/0x30e [] kmsg_read+0x34/0x3c [] vfs_read+0xad/0x161 [] sys_read+0x3d/0x61 [] syscall_call+0x7/0xb ======================= -- http://develooper.com/ - http://askask.com/ From songtao.liu at mytum.de Tue Aug 7 13:38:49 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Tue, 07 Aug 2007 15:38:49 +0200 Subject: [Fedora-xen] how to get kernel-xen-debuginfo-2.6.19-1.2911.6.5.fc6xen??? Message-ID: Hello, I want to use oprofile to profile the xen. But only if the debuginfo is available,then I can get source file annotations. As the following kernel is the most stable version, so I dont want to update in the near future. # uname -r 2.6.19-1.2911.6.5.fc6xen The problem is previously I used yum --enablerepo=core-debuginfo --enable=updates-debuginfo install\ kernel-debuginfo and then # rpm -q --list kernel-xen-debuginfo | grep vmlinux /usr/lib/debug/lib/modules/2.6.20-1.2948.fc6xen/vmlinux I will get the 2.6.20-1.2948.fc6xen vmlinux, which doesn't match my kernel-xen 2.6.19-1.2911.6.5.fc6xen. How can I get the "kernel-xen-debuginfo-2.6.19-1.2911.6.5.fc6xen" just like the one lives here /usr/lib/debug/lib/modules/2.6.20-1.2948.fc6xen/vmlinux Thanks a lot. Songtao From AL.LINUX at bcpraha.com Tue Aug 7 09:59:50 2007 From: AL.LINUX at bcpraha.com (Artur Linhart - Linux communication) Date: Tue, 7 Aug 2007 11:59:50 +0200 Subject: [Fedora-xen] RE: [Xen-users] Problem installing Windows2003 Server on Xen Server 30day trial In-Reply-To: <16314edc0708070037t496fde27j8deb27cd150ec274@mail.gmail.com> References: <16314edc0708070037t496fde27j8deb27cd150ec274@mail.gmail.com> Message-ID: <012701c7d8d9$b1af5870$6d58a8c0@private.praha.bcpraha.com> Hello, Unfortunately there are no PV drivers available to the community... So, I think You should contact the conference dedicated to the Xen commercial products, they should know more about the PV drivers... With best regards, Artur _____ From: xen-users-bounces at lists.xensource.com [mailto:xen-users-bounces at lists.xensource.com] On Behalf Of suyash jape Sent: Tuesday, August 07, 2007 9:37 AM To: xen-users at lists.xensource.com Cc: fedora-xen at redhat.com Subject: [Xen-users] Problem installing Windows2003 Server on Xen Server 30day trial Hi all, I am using Xen Server ( 30 day trial ) on Intel VT Clovertown server with 8 cpus and 16gb RAM. I am trying to install Windows2003 Enterprise Edition on this setup. The Windows setup starts up fine , but at the time of copying files from CD , it is not able to copy a number of DLLs, .aspx,.exe, .js and so many other files from the i386 folder of the windows cd. When i skip the copying of these numerous files, finally windows is installed but without most of its features.(obviously) The installation cd is working absolutely fine when i install Windows 2003 on some other desktop machines and fully functional windows can be installed on the desktops. So i think the problem maybe with paravirtualization/VT hardware. The VT flag is enabled in BIOS.I am able to install FC4 ,FC6, SuSE 10.1, Debian. Does anyone have an idea about why this may be happening?? (Setup unable to copy files from i386 folder of installation cd ) This is my machine configuration. root at xenserver1 ~]# uname -a Linux xenserver1 2.6.16.38-xs3.2.0.531.3960xen #1 SMP Sat Mar 24 17:19:06 EDT 2007 i686 i686 i386 GNU/Linux [root at xenserver1 ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Genuine Intel(R) CPU @ 2.40GHz stepping : 5 cpu MHz : 2399.994 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips : 4801.57 Also let me know if there an appropriate forum/list to post problems about Xen Server Thanks Suyash -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.schwarz at web.de Wed Aug 8 12:15:09 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Wed, 08 Aug 2007 14:15:09 +0200 Subject: [Fedora-xen] Re: Running SLES 10 as pv guest in Fedora 7 In-Reply-To: <46B6E41E.3090904@redhat.com> References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> Message-ID: <46B9B3CD.4020306@web.de> Hi, Gerd Hoffmann schrieb: > Hmm, looks like the page needs some updating ... > > Some patches by the solaris guys for pygrub made booting sles (and > opensuse) easier in xen 3.1 (I think 3.0.4 too). You can simply put > these lines into your config file ... > > kernel=/boot/vmlinux-xen > ramdisk=/boot/initrd-xen > bootloader=/usr/bin/pygrub > > ... and pygrub will go and pull kernel+ramdisk from the guest disk > without looking for a config file on the guest disk. No need for > domUloader any more. Thanks for your help. I finally got it working, so maybe this may interest some people: ------------------------------------------------------------------------ name = "sles10_64_test" memory = "512" disk = [ 'tap:aio:/var/lib/xen/images/sles10_64_test,hda,w', ] vif = [ 'mac=00:16:3e:4a:f5:f0, bridge=eth0', ] vfb = [ 'type=vnc,vncunused=1' ] uuid = "b1fd65e84128ced2dc435bb9d2e1861e" bootloader = "/usr/bin/pygrub" kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" vcpus=1 on_reboot = 'restart' on_crash = 'restart' ------------------------------------------------------------------------ The only thing which is missing is the VNC console. Does SLES 10 not support it? fs From Travis.Formoso at blueslate.net Wed Aug 8 12:55:32 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Wed, 8 Aug 2007 08:55:32 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: <47302.189.15.123.33.1185307420.squirrel@webmail.ispbrasil.com.br> Message-ID: OK I am back from vacation and have started up this project again. I am taking old xen images from Fedora Core 4 and upgrading them to 7 on a new server. Here is what I have done so far and have run into a problem. I installed Fedora Core 7 on the new server and has new xen and kernel. I transferred the old images and files from the old server to the new one. I then went in to the old config file - and changed the kernel from FC4 to the new vmlinuz FC7. I then created a new initrd with xenblk with the following command: mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.20-2925.13.fc7xen.img 2.6.20-2925.13.fc7-1xen. I put that in the config file under ramdisk. Now when I run the command xm create -c xmconfig I get this: Using config file "./xmconfig". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I looked at the archives and tried many suggestions, however none of them have worked - Anything else I could do to get by this error? > yes, > you also need to create a new initrd for domU's with xenblk module. > OK I am going to install Fedora Core 7 on the new server (it has 6 now). > > I will install the latest Xen 3.1 and the *13* kernel. > > After that I will transfer all the stuff from the older server to the new > one. > > Then do I go into the xmconfig and change the kernel name? So here is the > xmconfig for the sec-int-dns vm. > > # Kernel image file. > kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" > > Do I go and switch that line to kernel = (new xen kernel)? > > I am trying to understand that part - thanks for all your help! This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From rstory-l at 2006.revelstone.com Wed Aug 8 12:14:43 2007 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Wed, 8 Aug 2007 08:14:43 -0400 Subject: [Fedora-xen] Hiding PCI devices from the hypervisor (dom0) In-Reply-To: References: Message-ID: <200708081317.l78DHbx0014735@mx1.redhat.com> On Thu, 02 Aug 2007 12:24:00 -0400 Ubaidul wrote: UK> I am trying to hide a PCI network card from the hypervisor. So I updated UK> grub.conf with the following: UK> UK> title Red Hat Enterprise Linux Server (2.6.18-8.1.1.el5xen) UK> root (hd0,0) UK> kernel /xen.gz-2.6.18-8.1.1.el5 physdev_dom0_hide=(01:01.1) UK> module /vmlinuz-2.6.18-8.1.1.el5xen ro root=LABEL=/ rhgb quiet UK> module /initrd-2.6.18-8.1.1.el5xen.img try using pciback.hide, and putting it on the module line: module /vmlinuz-2.6.18-8.1.1.el5xen ro root=LABEL=/ rhgb quiet pciback.hide=hide=(01:01.1) From rstory-l at 2006.revelstone.com Wed Aug 8 12:17:44 2007 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Wed, 8 Aug 2007 08:17:44 -0400 Subject: [Fedora-xen] Possible to delegate hardware to domU? In-Reply-To: References: Message-ID: <200708081317.l78DHdMH002295@mx2.redhat.com> On Wed, 18 Jul 2007 17:44:40 +0200 Arik wrote: ARF> is it possible to hide hardware from dom0 and delegate it to a domU with ARF> the out-of-the-box Fedora xen? I.e. with pciback. I would like to ARF> delegate a network interface to one of my domU's. Can anybody confirm ARF> either that it is or that it is not possible? I'm not sure about Fedora XEN (I'm only using fedora on guests), but with RHEL/Centos 5 as dom0, this works for me to hide a USB interface: title CentOS (2.6.18-8.1.6.el5xen) root (hd0,1) kernel /xen.gz-2.6.18-8.1.6.el5 dom0_mem=512M module /vmlinuz-2.6.18-8.1.6.el5xen ro root=/dev/k/root pciback.hide=(00:09.0)(00:09.1)(00:09.2) noirqdebug module /initrd-2.6.18-8.1.6.el5xen.img From Travis.Formoso at blueslate.net Wed Aug 8 14:08:56 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Wed, 8 Aug 2007 10:08:56 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: I looked at the config file again and it stated under vif: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ] vif = [ 'mac=aa:00:00:00:01:04' ] I changed it to: vif = [' '] I then did the xm create and got this error: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Here is the entire log file: #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" # Optional ramdisk. ramdisk = "/boot/initrd-2.6.20-2925.13.fc7xen.img" # The domain build function. Default is 'linux'. #builder='linux' # Initial memory allocation (in megabytes) for the new domain. memory = 32 # A name for your domain. All domains must have different names. name = "sec-int-dns" # Which CPU to start domain on? #cpu = -1 # leave to Xen to pick #---------------------------------------------------------------------------- # Define network interfaces. # Number of network interfaces. Default is 1. #nics=1 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ] #vif = [ 'mac=aa:00:00:00:01:04' ] vif = [' '] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ 'file:/xen/sec-int-dns/root.img,sda1,w', 'file:/xen/sec-int-dns/swap.img,sda2,w' ] #---------------------------------------------------------------------------- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. dhcp="dhcp" #ip="172.20.1.88" # Set netmask. netmask="255.255.255.0" # Set default gateway. gateway="172.20.1.1" # Set the hostname. hostname= "sec-int-dns" # Set root device. root = "/dev/sda1 ro" # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = '169.254.1.0' # Root directory on the nfs server. #nfs_root = '/full/path/to/root/directory' # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- # Set according to whether you want the domain restarted when it exits. # The default is 'onreboot', which restarts the domain when it shuts down # with exit code reboot. # Other values are 'always', and 'never'. #restart = 'onreboot' #============================================================================ Here is the xen log file: [2007-08-08 04:53:01 25349] DEBUG (XendDomainInfo:957) XendDomainInfo.handleShutdownWatch [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vif. [2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 0. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/16/0/hotplug-status. [2007-08-08 04:53:02 25349] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices usb. [2007-08-08 04:53:02 25349] DEBUG (DevController:148) Waiting for devices vbd. [2007-08-08 04:53:02 25349] DEBUG (DevController:153) Waiting for 2049. [2007-08-08 04:53:02 25349] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/16/2049/hotplug-status. [2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1709) XendDomainInfo.destroy: domid=16 [2007-08-08 04:54:42 25349] DEBUG (XendDomainInfo:1726) XendDomainInfo.destroyDomain(16) Log file for hotplug: Nothing to flush. xenstore-read: couldn't read path backend/vbd/16/2049/node xenstore-read: couldn't read path backend/vbd/16/2050/node Hope this helps to determine the problem. Thanks > OK I am back from vacation and have started up this project again. I am > > taking old xen images from Fedora Core 4 and upgrading them to 7 on a new > server. Here is what I have done so far and have run into a problem. > I installed Fedora Core 7 on the new server and has new xen and kernel. I > transferred the old images and files from the old server to the new one. > I then went in to the old config file - and changed the kernel from FC4 to > the new vmlinuz FC7. I then created a new initrd with xenblk with the > following command: mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd- > 2.6.20-2925.13.fc7xen.img 2.6.20-2925.13.fc7-1xen. I put that in the config file under ramdisk. > Now when I run the command xm create -c xmconfig I get this: > Using config file "./xmconfig". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > I looked at the archives and tried many suggestions, however none of them > have worked - > Anything else I could do to get by this error? > yes, > you also need to create a new initrd for domU's with xenblk module. > OK I am going to install Fedora Core 7 on the new server (it has 6 now). > > I will install the latest Xen 3.1 and the *13* kernel. > > After that I will transfer all the stuff from the older server to the new > one. > > Then do I go into the xmconfig and change the kernel name? So here is the > xmconfig for the sec-int-dns vm. > > # Kernel image file. > kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" > > Do I go and switch that line to kernel = (new xen kernel)? > > I am trying to understand that part - thanks for all your help! This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From Travis.Formoso at blueslate.net Wed Aug 8 15:31:58 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Wed, 8 Aug 2007 11:31:58 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: Update: I disabled my firewall and selinux and now get it to start to boot, but then this comes up: XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 759k USB Universal Host Controller Interface driver v3.0 SCSI subsystem initialized Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel at redhat.com Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can't get major 8 with name sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/9/2049 Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can't get major 8 with name sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/9/2050 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) XENBUS: Timeout connecting to device: device/vbd/2050 (state 6) Kernel panic - not syncing: Attempted to kill init! Thanks > I looked at the config file again and it stated under vif: > # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > #vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ] > vif = [ 'mac=aa:00:00:00:01:04' ] > I changed it to: > vif = [' '] > I then did the xm create and got this error: > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > working. > snip This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From Tameika.Reed at nortelgov.com Wed Aug 8 21:25:49 2007 From: Tameika.Reed at nortelgov.com (Reed, Tameika N) Date: Wed, 8 Aug 2007 17:25:49 -0400 Subject: [Fedora-xen] LUN to VM References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> <46B9B3CD.4020306@web.de> Message-ID: Hi All, I have some questions about presenting LUNS to a virtual machine. My configuration is as follows: 1 HP EVA 8000 that is being presented to a blade bl 456c running Rhel 5. The kernel is basic 2.6.18 xen kernel. I can see the LUNS on the blade, by using multipath. Below is a snippet of mulitpath. mpath10 (3600508b4001069430001d000017d0000) dm-17 HP,HSV200 [size=100G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=0][active] \_ 0:0:0:11 sdk 8:160 [active][undef] mpath3 (3600508b4001069430001d00001960000) dm-5 HP,HSV200 [size=250G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=0][active] \_ 0:0:0:4 sdd 8:48 [active][undef] Now as you can see the devices are showing up under /dev/sd* and /dev/mapper/mpath*. I can mount the LUNS to blade without any problems. I now want these devices to be seen by the virtual machine created on the san. Below is a my configuration that I have set up for one of my VM's. VM Config file: # Automatically generated xen config file name = "REDDISK" builder = "hvm" memory = "2000" disk = [ 'file:/opt/reddiskd0,hda,w','phy:/dev/mapper/mpath0,sda1,w', ] vif = [ 'type=ioemu, mac=00:16:3e:4d:d2:ea, bridge=xenbr0', ] uuid = "57ad8f41-cd50-5e89-985f-6462aa5a5f9b" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' ************************************************************** I can also run the following command from cli and see the output in my configuration file once I enter this command: command 1: xm block-attach TXWD_COURT /block/sda sda w command 2: xm list REDDISK --long | less results from command 2 domain (domid 20) (uuid 57ad8f41-cd50-5e89-985f-6462aa5a5f9b) (vcpus 1) (cpu_weight 1.0) (memory 2000) (shadow_memory 9) (maxmem 2000) (features ) (name REDDISK) (on_poweroff destroy) (on_reboot restart) (on_crash restart) (image (hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib64/xen/bin/qemu-dm) (pae 1) (vcpus 1) (boot c) (serial pty) (vnc 1) (vncunused 1) (display localhost:1003.0) (xauthority /root/.xauthJl2aRE) (acpi 1) (apic 1) (vncpasswd 'None') ) ) (device (vif (backend 0) (script vif-bridge) (bridge xenbr0) (mac 00:16:3e:4d:d2:ea) (type ioemu) ) ) (device (vbd (backend 0) (dev hda:disk) (uname file:/opt/reddiskd0) (mode w)) ) (device (vbd (backend 0) (dev sda:disk) (mode w))) (device (vkbd (backend 0))) (device (vfb (backend 0) (type vnc) (vncunused 1) (display localhost:1003.0) (xauthority /root/.xauthJl2aRE) ) ) (state -b----) (shutdown_reason poweroff) (cpu_time 116.031996341) (online_vcpus 1) (up_time 3220.21273112) (start_time 1186604696.56) (store_mfn 61791) ) This tells me that the command was ok an that it should be see as sda on my virtual machine ( i think)? ************************************************************************* So sum up all my questions: 1. Is my configuration file correct to present LUNS to the VM's ? disk = [ 'file:/opt/reddiskd0,hda,w','phy:/dev/mapper/mpath0,sda1,w', ] 2. Do I need to create a scsi block device in order for this work? ie mknod or MAKEDEV. Reason being none of the scsi partitions show up at all I checked cat /proc/partitions and /dev 3.Am I presenting this information wrong to the VM? 4. I have also explored setting up WWID inside the VM but if it can't see the SAN then it does me no good for right now. I know that this may see confusing but if you need me to clarify then I can do that. ANY IDEAS OR SUGGESTIONS ? Thanks in advance, Tameika -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Thu Aug 9 14:31:24 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 09 Aug 2007 15:31:24 +0100 Subject: [Fedora-xen] ANNOUNCE: Virt-top 0.3.1.5 - a top-like utility for displaying virtualization stats In-Reply-To: <46B78F84.10309@redhat.com> References: <46B78F84.10309@redhat.com> Message-ID: <46BB253C.5010204@redhat.com> There is a significantly updated version of virt-top now available. On systems which support it, you can show the mapping of domains to physical CPUs and the amount of each physical CPU being used. Screenshots: http://et.redhat.com/~rjones/virt-top/screenshots.html There are also binaries available to download for i386 and x86-64. (The binaries are just self-contained Linux executables, no extra files or dependencies are needed, except for libvirt.so). Downloads: http://et.redhat.com/~rjones/virt-top/download.html If you are a systems administrator, what do you think could be improved about virt-top? Try it out and let me have your suggestions ... Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From bkearney at redhat.com Thu Aug 9 15:00:23 2007 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 09 Aug 2007 11:00:23 -0400 Subject: [Fedora-xen] xm create on fedora 7 Message-ID: <46BB2C07.4060003@redhat.com> I am trying to load an exisinting xen image, and I get the following error: [root at localhost ~]# xm create --config=/home/bkearney/rhel5.cfg Error: memory_dynamic_max must be greater than zero I have not found a way to set this either in the config file, or in the xend configuration. [root at localhost ~]# cat /home/bkearney/rhel5.cfg memory="500" name="rhel5" disk=['file://var/lib/xen/images,xvda,rw'] [root at localhost ~]# how does this max setting get set? -- bk From mmacdonald at symcor.com Thu Aug 9 23:23:45 2007 From: mmacdonald at symcor.com (mmacdonald at symcor.com) Date: Thu, 9 Aug 2007 19:23:45 -0400 Subject: [Fedora-xen] Fw: XEN Guest Install problem Message-ID: Hey I am trying to install a new XEN guest up and running on Fedora 7 x86_64 and it hangs everytime: I am using the following command: virt-install --paravirt -b virbr0 --nographics --debug -n foafdz01 -r 1024 -lnfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7 -f /dev/vg01/dblv01 -x ks=http://10.229.70.234/ks/foafdz01.cfg and I get the following: Thu, 09 Aug 2007 11:55:02 DEBUG Path is block file: Assuming Block disk type. Starting install... libvir: Xen Daemon error : GET operation failed: Thu, 09 Aug 2007 11:55:02 DEBUG Preparing mount at /var/lib/xen/virtinstmnt.S6wuva Thu, 09 Aug 2007 11:55:02 DEBUG Acquiring file from /var/lib/xen/virtinstmnt.S6wuva/Fedora Thu, 09 Aug 2007 11:55:02 DEBUG Found a directory Thu, 09 Aug 2007 11:55:02 DEBUG Detected a Fedora distro Thu, 09 Aug 2007 11:55:02 DEBUG Acquiring file from /var/lib/xen/virtinstmnt.S6wuva/images/xen/vmlinuz Thu, 09 Aug 2007 11:55:02 DEBUG Saved file to /var/lib/xen/virtinst-vmlinuz.kVhm-B Thu, 09 Aug 2007 11:55:02 DEBUG Acquiring file from /var/lib/xen/virtinstmnt.S6wuva/images/xen/initrd.img Thu, 09 Aug 2007 11:55:03 DEBUG Saved file to /var/lib/xen/virtinst-initrd.img.GVqMWE Thu, 09 Aug 2007 11:55:03 DEBUG Cleaning up mount at /var/lib/xen/virtinstmnt.S6wuva libvir: Xen Daemon error : GET operation failed: Thu, 09 Aug 2007 11:55:03 DEBUG Creating guest from ' foafdz01 1048576 1048576 80291afd-cbef-a8b1-d868-730c0d316efc linux /var/lib/xen/virtinst-vmlinuz.kVhm-B /var/lib/xen/virtinst-initrd.img.GVqMWE ks=http://10.229.70.234/ks/foafdz01.cfg method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7 destroy destroy destroy 1 ' Creating domain... 0 B 00:00 Thu, 09 Aug 2007 11:55:04 DEBUG Created guest, looking to see if it is running Thu, 09 Aug 2007 11:55:04 DEBUG Launching console callback Thu, 09 Aug 2007 11:55:04 DEBUG Saving XML boot config ' foafdz01 1048576 1048576 80291afd-cbef-a8b1-d868-730c0d316efc /usr/bin/pygrub destroy restart restart 1 ' Linux version 2.6.20-2925.9.fc7xen (kojibuilder at xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007 Command line: ks=http://10.229.70.234/ks/foafdz01.cfg method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000040800000 (usable) end_pfn_map = 264192 Zone PFN ranges: DMA 0 -> 264192 DMA32 264192 -> 264192 Normal 264192 -> 264192 early_node_map[1] active PFN ranges 0: 0 -> 264192 No mptable found. PERCPU: Allocating 26368 bytes of per cpu data Built 1 zonelists. Total pages: 259481 Kernel command line: ks=http://10.229.70.234/ks/foafdz01.cfg method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2194.496 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 1015932k/1056768k available (2207k kernel code, 32024k reserved, 1347k data, 192k init) Calibrating delay using timer specific routine.. 5488.99 BogoMIPS (lpj=10977983) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7236k freed IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1186674904.434:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 938k ------------------------ I have tried some other options and I just can't seem to get past this stage. Any thoughts would be great -------------- next part -------------- An HTML attachment was scrubbed... URL: From anakonieczny.fedora-xen at e-list.pingwin.eu.org Sat Aug 11 17:29:30 2007 From: anakonieczny.fedora-xen at e-list.pingwin.eu.org (Andrzej Nakonieczny) Date: Sat, 11 Aug 2007 19:29:30 +0200 Subject: [Fedora-xen] Xen on FC7 and bridge not on eth0 Message-ID: <46BDF1FA.10708@e-list.pingwin.eu.org> Hi I'm looking for informations about networking in Xen on FC7. I'm trying to change default bridge device from eth0 to another one. On RHEL5 Beta2 I did change only one line in xend-config.sxp to: (network-script 'network-bridge netdev=dummy0') and it worked fine. But on FC7 it doesn't work. So what is the right way to bridge all Xen domains to dummy0? I tried to add my own script instead of network-bridge and vif-bridge but after some changes virt-manager stops with segmentation fault. So is there any way to change default settings? Regards, Andrzej From joe_hesse at actcx.com Sat Aug 11 19:48:32 2007 From: joe_hesse at actcx.com (Joseph Hesse) Date: Sat, 11 Aug 2007 14:48:32 -0500 Subject: [Fedora-xen] Install location for FC7 as a guest Message-ID: <000001c7dc50$997c40e0$6500a8c0@nan> Hi, I am using 'virt-manager', paravirtualization, to install FC7 as a guest under FC7. I can't seem to find a network install location that works. The Fedora site list many ftp and http mirror sites for installing. I can ping them and verify they are alive. My problem is I don't know how deep to go into the directory tree to get something that anaconda likes. I tried 'http://download.fedora.redhat.com/pub/fedora/linux' The error message I get is "Unable to complete install: Invalid URL given." Can I take the FC7 DVD, mount it and then ftp to it? Thank you, Joe Hesse From berrange at redhat.com Sat Aug 11 20:47:35 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 11 Aug 2007 21:47:35 +0100 Subject: [Fedora-xen] Install location for FC7 as a guest In-Reply-To: <000001c7dc50$997c40e0$6500a8c0@nan> References: <000001c7dc50$997c40e0$6500a8c0@nan> Message-ID: <20070811204734.GA13242@redhat.com> On Sat, Aug 11, 2007 at 02:48:32PM -0500, Joseph Hesse wrote: > Hi, > > I am using 'virt-manager', paravirtualization, to install FC7 as a guest > under FC7. I can't seem to find a network install location that works. > > The Fedora site list many ftp and http mirror sites for installing. I can > ping them and verify they are alive. My problem is I don't know how deep to > go into the directory tree to get something that anaconda likes. > > I tried 'http://download.fedora.redhat.com/pub/fedora/linux' The error > message I get is "Unable to complete install: Invalid URL given." You need to specify the path to the specific distro release+arch tree. For example for Fedora 7 on x86_64 http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/ > Can I take the FC7 DVD, mount it and then ftp to it? Yes, you can export the DVD using a FTP/NFS/HTTP from your Dom0 host. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From ask at develooper.com Mon Aug 13 12:33:34 2007 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Mon, 13 Aug 2007 05:33:34 -0700 Subject: [Fedora-xen] i386 domU on x86_64 dom0 In-Reply-To: <408B9F9F-AF22-4EE6-B38F-02417E811BF4@develooper.com> References: <408B9F9F-AF22-4EE6-B38F-02417E811BF4@develooper.com> Message-ID: <97BB6769-B7E7-45C8-AE86-5DC50F7FF0AF@develooper.com> On Aug 7, 2007, at 3:18 AM, Ask Bj?rn Hansen wrote: > Most of our virtual machines could happily be i386 (and save a bit > of memory). I prefer the dom0s to be x86_64 for some added > flexibility for applications that do need 64bit (MySQL, memcached, > varnish). > > I upgraded one of our boxes to F7 to get Xen 3.1 since it's > supposed to be possible there. But it crashes pretty fast every > time. I am running the latest kernel and xen in the dom0 and just > the release tree in the domU. I take it nobody has an obvious solution. :-) Is it supposed to work at all? - ask > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762k > Oops: 0000 [#1] > SMP > last sysfs file: /class/graphics/fb0/name > Modules linked in: xenblk xennet iscsi_tcp libiscsi > scsi_transport_iscsi sr_mod sd_mod scsi_mod cdrom ipv6 ext2 ext3 > mbcache jbd squashfs pcspkr loop nfs nfs_acl lockd sunrpc vfat fat > cramfs > CPU: 0 > EIP: 0061:[] Not tainted VLI > EFLAGS: 00010097 (2.6.20-2925.9.fc7xen #1) [snip] -- http://develooper.com/ - http://askask.com/ From tthtlc at singnet.com.sg Thu Aug 9 16:15:30 2007 From: tthtlc at singnet.com.sg (Peter Teoh) Date: Fri, 10 Aug 2007 00:15:30 +0800 Subject: [Fedora-xen] Upgrading to 2.6.20-1.2999 Fedora Core 6 Message-ID: <46BB3DA2.9040109@singnet.com.sg> After updating my system, the kernel change from 2.6.20-1.2962.fc6 to 2.6.20-1.2999xen.fc6, and my original Xen installation now cannot have xend started, giving rise to the following errors instead. Why and please help. Thank you very much!!!! Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17, in ? import xen.lowlevel.xc ImportError: /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so: undefined symbol: xc_domain_set_memmap_limit From dlbewley at lib.ucdavis.edu Mon Aug 13 18:26:01 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 13 Aug 2007 11:26:01 -0700 (PDT) Subject: [Fedora-xen] xen networking In-Reply-To: <46B73D71.1040709@redhat.com> Message-ID: <266606063.400531187029561559.JavaMail.root@zebra.lib.ucdavis.edu> Wow, I didn't even know that /etc/libvirt/qemu/networks/ existed. Now I know how to remove that annoying 192.168 network. Thanks :) I'm on F7 and not doing any bonding, but I am using bridges on VLANs and I setup all my interfaces and do my filtering the old fashioned way in /etc/sysconfig. Sorry if I'm stating the obvious below... [root at helix sysconfig]# grep forward /etc/sysctl.conf # Controls IP packet forwarding net.ipv4.ip_forward = 1 [root at helix sysconfig]# grep phys iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT [root at helix network-scripts]# cat ifcfg-eth0 DEVICE=eth0 MTU=1504 BOOTPROTO=none ONBOOT=yes BRIDGE=br101 [root at helix network-scripts]# cat ifcfg-vlan6 DEVICE=eth0.6 BRIDGE=br6 VLAN=yes MTU=1500 ONBOOT=yes BOOTPROTO=none [root at helix network-scripts]# cat ifcfg-br6 DEVICE=br6 TYPE=Bridge BOOTPROTO=static ONBOOT=yes MTU=1500 IPADDR=1.1.1.1 NETMASK=255.255.255.0 NETWORK=1.1.1.0 BROADCAST=1.1.1.255 And set (network-script /bin/true) in xend-config.sxp. Change your domU bridge like so: # virsh shutdown # virsh dumpxml | sed s/br101/br6/ > .xml # virsh define .xml # virsh startup -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 ----- "Mark Nielsen" wrote: > Since I have not yet been able to resolve my complex networking issues > > in RHEL 5, I decided to upgrade 1 of my cluster nodes to 5.1 beta and > > take this new libvirt networking for a spin. I'm not sure if this is > going to make my issue easier to resolve, or add to the complexity so > > I'm writing this e-mail to hopefully get some suggestions as how to > proceed. > > My network looks like this: > eth2 & eth3 comprise bond1 > bond1 has bond1.48 - my public VLAN interface with an IP for dom0 > bond1 has bond1.20 - my VLAN for some domU systems, dom0 has no IP on > > this VLAN > bond1 has bond1.21 - my VLAN for some domU systems, dom0 has no IP on > > this VLAN > > I want to bridge to bond1.20 from some domU systems, and bond1.21 from > > other domU systems. dom0 should not have an IP on these VLANs. > > 1) do I need to define a network interface in > /etc/libvirt/qemu/networks/ for each VLAN? (bond1.20 and bond1.21) > 1a) If yes, do I need to have an IP address for the bond1.20 and > bond1.21 interface defined in > /etc/sysconfig/network-scripts/ifcfg-bond1.20 and bond1.21? > 1b) Do I also need to define an IP address on that VLAN in the .xml > file for that network? > > or > > 2) Can I just have 1 default.xml network and then use iptables to > forward to a specific VLAN based on bond1.20 and bond1.21 configured > in > /etc/sysconfig/network-scripts/ ?? > > #2 would be best, if possible. Unfortunately there's not a lot of > documentation out on the new networking methods. I've read > http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt > > but that doesn't get in to all the VLANs and bonds. > > Any help is greatly appreciated! From mnielsen at redhat.com Mon Aug 13 19:26:07 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Mon, 13 Aug 2007 15:26:07 -0400 Subject: [Fedora-xen] xen networking In-Reply-To: <266606063.400531187029561559.JavaMail.root@zebra.lib.ucdavis.edu> References: <266606063.400531187029561559.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <46C0B04F.1040006@redhat.com> Dale Bewley wrote: > Wow, I didn't even know that /etc/libvirt/qemu/networks/ existed. Now I know how to remove that annoying 192.168 network. Thanks :) > > I'm on F7 and not doing any bonding, but I am using bridges on VLANs and I setup all my interfaces and do my filtering the old fashioned way in /etc/sysconfig. > > Sorry if I'm stating the obvious below... > > > Thanks for the help :) I had some issue with the BRIDGE= lines, the kernel was saying that it didn't support bridging. Rather than try to deviate any farther from the supported enterprise installation in place here, I just went back to RHEL 5 on the node I had upgrade to 5.1 and made all the bonded VLANs work with the Xen bridges. It's pretty complex, but I've developed a how-to that I'm hoping to get out soon. (if you need help before then, feel free to e-mail me). Mark -------------- next part -------------- A non-text attachment was scrubbed... Name: mnielsen.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From Tameika.Reed at nortelgov.com Tue Aug 14 17:51:42 2007 From: Tameika.Reed at nortelgov.com (Reed, Tameika N) Date: Tue, 14 Aug 2007 13:51:42 -0400 Subject: [Fedora-xen] LUN to VM References: <46A8DA8F.8050102@web.de> <46B6E41E.3090904@redhat.com> <46B9B3CD.4020306@web.de> Message-ID: Hi All, So sum up all my answers to questions 1. This line is correct! disk = [ 'file:/opt/reddiskd0,hda,w', 'phy:/dev/mapper/mpath0,hdb,w', 'phy:/dev/mapper/mpath4,hdc,w', ] 2. SCSCi device create is not needed futhermore once you create it, it will not be there upon rebooting the server. 3.The way this works is as long as the LUN is not mounted on the blade in which the guest vm is running on. Then the VM can mount the LUN. The VM can mount the LUN even if it is presented and mounted to a different blade. The one key point here is as long as the LUN is not mounted to blade where the virtual machine is running from, it should be able to mount it. 4. WWID is only necessary if I want to use multipath inside VM. For the most part I rebooted the blades and the VM's serveral time and they come back with the same WWID. so far... I will continue to look at this post back if any significant changes. Thanks Tameika -------------- next part -------------- An HTML attachment was scrubbed... URL: From cjm at ecollege.com Wed Aug 15 16:42:54 2007 From: cjm at ecollege.com (Christopher Miller) Date: Wed, 15 Aug 2007 10:42:54 -0600 Subject: [Fedora-xen] win2k3 server standard edition hangs on "Starting Windows" Message-ID: Hello list! I'm having a heck of a time getting Windows 2003 Server Standard Edition to install. I've tried using both virt-install and virt-manager, however it would seem that virt-manager gets further. On the command line, I used this to provision the machine: # virt-install \ --name=system1 \ --ram=2048 \ --file=/home/luser/virtuals/system1/system1.img \ --file-size=80 \ --nonsparse \ --network=bridge:xenbr0 \ --sdl \ --hvm \ --os-type=windows \ --os-variant=win2k3 \ --cdrom=/media/EN_OS_XP_2003_2428.4/english/win2003/standard/setup.exe this command failed until I "touch"ed /home/luser/virtuals/system1/system1.img, and then said it was provisioning, and I should reconnect to the domain to see the machine, when I tried this, it was unavailable. As I've indicated, my experience with virt-manager gets me "further" but what this further is, isn't usable either. I select the same options as above in the gui, and when I click "finish" it allocates the file I've selected, and the new domain shows up in the virt-manager window. I can right-click on the new virtual and connect to the console, select which version of windows I'm installing, and the startup even runs up to the point where it says "Windows Setup: Setup is starting Windows" (this is the last blue dos type screen before being switched into the windows install gui, for those familiar) and freezes there. I've posted a couple screen shots here: http://63.231.71.205/~cj/xen/AllWindows.png http://63.231.71.205/~cj/xen/Console.png I'm running Fedora Core 6, all updates, on a AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, kernel 2.6.20-1.2999.fc6xen, 3GB RAM. I'm installing from an MSDN disk in my cdrom drive. Please let me know if there's any more information I can provide. Thanks in advance! Christopher Jon Miller Programmer, Research and Development -------------------------------------------------------www.eCollege.com eCollege Supporting your Success cjm at eCollege.com phone 303.873.7400x3233 cell 303.552.7666 fax 303.632.1719 eCollege Building 4900 S Monaco St Denver, CO 80237 From Travis.Formoso at blueslate.net Wed Aug 15 19:30:52 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Wed, 15 Aug 2007 15:30:52 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: Update on this issue and need some help. I am trying to get an old FC4 image booted up on my new FC7 xen box so that I can upgrade the old FC4 machine to FC7 - however I am having trouble booting it up. I will place the config file after explanation. The situation is as follows: I have 2 old P3 boxes with xen images on them. We now have a new Power Edge server and I installed Fedora Core 7 on it. I then transferred over all the files from the old boxes to the new FC7 box and have the same directory structures. (All the files were in the /xen directory and a bunch of sub-directories with the xen images.) I am trying to get one of the old FC4 xen images to boot with an xm create -c (config file name) - however when I do that - it will not boot and giving me errors. I did a few things listed below: (Itamar on the mailing list guided me in this direction) I created a new initrd with this command: mkinitrd --preload=xenblk --preload=xennet -f -v /boot/initrd-2.6.20-2925.13.fc7xen.guest.img 2.6.20-2925.13.fc7xen I then had my new initrd img with xenblk and xennet. Now in the config file I had to change the kernel from: #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" So that I can get the old machine to boot up in the FC7 environment. When I go to boot the machine I get this: xm create -c xmconfig 4gb seg fixup, process S28autofs (pid 825), cs:ip 73:0092914b printk: 197950 messages suppressed. 4gb seg fixup, process egrep (pid 973), cs:ip 73:008e8149 printk: 116932 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f printk: 15 messages suppressed. 4gb seg fixup, process dhcpd (pid 941), cs:ip 73:00d20d7f printk: 108 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f printk: 15 messages suppressed. 4gb seg fixup, process named (pid 752), cs:ip 73:002f775f This just keeps repeating and going and never stops and I can not do anything with the machine except kill it. I googled for these errors and tried just about everything I could find and nothing worked. It all comes back to this repeating. I really would like to get this FC4 image up and running so I can go in and then update it to FC7 as I have to do this with 4 of our old images. Here is the full config file. If you guys have any ideas of what I could do please let me know. # -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/boot/vmlinuz-2.6.12-1.1398_FC4xenU" kernel = "/boot/vmlinuz-2.6.20-2925.13.fc7xen" # Optional ramdisk. #ramdisk = "/boot/initrd.gz" ramdisk = "/boot/initrd-2.6.20-2925.13.fc7xen.guest.img" # The domain build function. Default is 'linux'. #builder='linux' # Initial memory allocation (in megabytes) for the new domain. memory = 128 # A name for your domain. All domains must have different names. name = "sec-int-dns" # Which CPU to start domain on? #cpu = -1 # leave to Xen to pick #---------------------------------------------------------------------------- # Define network interfaces. # Number of network interfaces. Default is 1. #nics=1 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ] vif = [ 'mac=aa:00:00:00:01:04' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ 'file:/xen/sec-int-dns/root.img,sda1,w', 'file:/xen/sec-int-dns/swap.img,sda2,w' ] #---------------------------------------------------------------------------- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. dhcp="dhcp" #ip="17x.2x.x.xx" # Set netmask. #netmask="255.255.255.0" # Set default gateway. #gateway="17x.xx.x.x" # Set the hostname. hostname= "sec-int-dns" # Set root device. root = "/dev/sda1 ro" # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = 'xxx.xxx.x.0' # Root directory on the nfs server. #nfs_root = '/full/path/to/root/directory' # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- # Set according to whether you want the domain restarted when it exits. # The default is 'onreboot', which restarts the domain when it shuts down # with exit code reboot. # Other values are 'always', and 'never'. #restart = 'onreboot' #============================================================================ This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From cjm at ecollege.com Wed Aug 15 23:09:00 2007 From: cjm at ecollege.com (Christopher Miller) Date: Wed, 15 Aug 2007 17:09:00 -0600 Subject: [Fedora-xen] win2k3 server standard edition hangs on "StartingWindows" In-Reply-To: Message-ID: Okay, I found a couple months back where a fella pushed F5 during the initial setup phase, I did that and got as far as rebooting the machine into the installation. I see now I have to add the CDROM device back in the conf file. I've yet to find the instructions on this, but I'm sure they're in the archives somewhere. I'll keep posted on my progress. peace, cj -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]On Behalf Of Christopher Miller Sent: Wednesday, August 15, 2007 10:43 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] win2k3 server standard edition hangs on "StartingWindows" Hello list! I'm having a heck of a time getting Windows 2003 Server Standard Edition to install. I've tried using both virt-install and virt-manager, however it would seem that virt-manager gets further. On the command line, I used this to provision the machine: # virt-install \ --name=system1 \ --ram=2048 \ --file=/home/luser/virtuals/system1/system1.img \ --file-size=80 \ --nonsparse \ --network=bridge:xenbr0 \ --sdl \ --hvm \ --os-type=windows \ --os-variant=win2k3 \ --cdrom=/media/EN_OS_XP_2003_2428.4/english/win2003/standard/setup.exe this command failed until I "touch"ed /home/luser/virtuals/system1/system1.img, and then said it was provisioning, and I should reconnect to the domain to see the machine, when I tried this, it was unavailable. As I've indicated, my experience with virt-manager gets me "further" but what this further is, isn't usable either. I select the same options as above in the gui, and when I click "finish" it allocates the file I've selected, and the new domain shows up in the virt-manager window. I can right-click on the new virtual and connect to the console, select which version of windows I'm installing, and the startup even runs up to the point where it says "Windows Setup: Setup is starting Windows" (this is the last blue dos type screen before being switched into the windows install gui, for those familiar) and freezes there. I've posted a couple screen shots here: http://63.231.71.205/~cj/xen/AllWindows.png http://63.231.71.205/~cj/xen/Console.png I'm running Fedora Core 6, all updates, on a AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, kernel 2.6.20-1.2999.fc6xen, 3GB RAM. I'm installing from an MSDN disk in my cdrom drive. Please let me know if there's any more information I can provide. Thanks in advance! Christopher Jon Miller Programmer, Research and Development -------------------------------------------------------www.eCollege.com eCollege Supporting your Success cjm at eCollege.com phone 303.873.7400x3233 cell 303.552.7666 fax 303.632.1719 eCollege Building 4900 S Monaco St Denver, CO 80237 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From per at actius.com Wed Aug 15 23:30:24 2007 From: per at actius.com (Per Hjartoy) Date: Wed, 15 Aug 2007 16:30:24 -0700 Subject: [Fedora-xen] win2k3 server standard edition hangs on"StartingWindows" In-Reply-To: References: Message-ID: <000f01c7df94$417a0ca0$3b354b0a@actius.com> Hi Chris, I'm trying to install win2k3 standard on Fedora 7. The configuration system is different, but I'm running into the same issues that you have. I've been able to solve the CD problem with the help of Andy (RedHat). (I met him at Linux World last week) No documentation exists about this matter as we could find. However, there are still issues and any reboot of the win2k3 server requires a "fake" reinstall to get it up and running again. If we could connect off list, maybe we could compare notes and report back about our progress. It would also be nice to get someone from the distro team to join us as well. I have suspicion that virtualization of win2k3 wasn't given much attention and that we jointly can provide some good feedback. You can contact me a per-at-actius-dot-com. -- Per -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Christopher Miller Sent: Wednesday, August 15, 2007 4:09 PM To: fedora-xen at redhat.com Subject: RE: [Fedora-xen] win2k3 server standard edition hangs on"StartingWindows" Okay, I found a couple months back where a fella pushed F5 during the initial setup phase, I did that and got as far as rebooting the machine into the installation. I see now I have to add the CDROM device back in the conf file. I've yet to find the instructions on this, but I'm sure they're in the archives somewhere. I'll keep posted on my progress. peace, cj -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]On Behalf Of Christopher Miller Sent: Wednesday, August 15, 2007 10:43 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] win2k3 server standard edition hangs on "StartingWindows" Hello list! I'm having a heck of a time getting Windows 2003 Server Standard Edition to install. I've tried using both virt-install and virt-manager, however it would seem that virt-manager gets further. On the command line, I used this to provision the machine: # virt-install \ --name=system1 \ --ram=2048 \ --file=/home/luser/virtuals/system1/system1.img \ --file-size=80 \ --nonsparse \ --network=bridge:xenbr0 \ --sdl \ --hvm \ --os-type=windows \ --os-variant=win2k3 \ --cdrom=/media/EN_OS_XP_2003_2428.4/english/win2003/standard/setup.exe this command failed until I "touch"ed /home/luser/virtuals/system1/system1.img, and then said it was provisioning, and I should reconnect to the domain to see the machine, when I tried this, it was unavailable. As I've indicated, my experience with virt-manager gets me "further" but what this further is, isn't usable either. I select the same options as above in the gui, and when I click "finish" it allocates the file I've selected, and the new domain shows up in the virt-manager window. I can right-click on the new virtual and connect to the console, select which version of windows I'm installing, and the startup even runs up to the point where it says "Windows Setup: Setup is starting Windows" (this is the last blue dos type screen before being switched into the windows install gui, for those familiar) and freezes there. I've posted a couple screen shots here: http://63.231.71.205/~cj/xen/AllWindows.png http://63.231.71.205/~cj/xen/Console.png I'm running Fedora Core 6, all updates, on a AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, kernel 2.6.20-1.2999.fc6xen, 3GB RAM. I'm installing from an MSDN disk in my cdrom drive. Please let me know if there's any more information I can provide. Thanks in advance! Christopher Jon Miller Programmer, Research and Development -------------------------------------------------------www.eCollege.com eCollege Supporting your Success cjm at eCollege.com phone 303.873.7400x3233 cell 303.552.7666 fax 303.632.1719 eCollege Building 4900 S Monaco St Denver, CO 80237 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From berrange at redhat.com Wed Aug 15 23:35:10 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 16 Aug 2007 00:35:10 +0100 Subject: [Fedora-xen] win2k3 server standard edition hangs on "Starting Windows" In-Reply-To: References: Message-ID: <20070815233510.GA20369@redhat.com> On Wed, Aug 15, 2007 at 10:42:54AM -0600, Christopher Miller wrote: > Hello list! I'm having a heck of a time getting Windows 2003 Server Standard Edition to install. I've tried using both virt-install and virt-manager, however it would seem that virt-manager gets further. > On the command line, I used this to provision the machine: > > # virt-install \ > --name=system1 \ > --ram=2048 \ > --file=/home/luser/virtuals/system1/system1.img \ Disk images have to be in /var/lib/xen/images > --file-size=80 \ > --nonsparse \ > --network=bridge:xenbr0 \ > --sdl \ > --hvm \ > --os-type=windows \ > --os-variant=win2k3 \ > --cdrom=/media/EN_OS_XP_2003_2428.4/english/win2003/standard/setup.exe You need to point it at the CDROM device, rather than a file on the CDROM. Unmount /media/EN_OS_XP_2003_2428.4, and use /dev/cdrom as your path. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Travis.Formoso at blueslate.net Thu Aug 16 12:41:00 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 16 Aug 2007 08:41:00 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: Here is the complete boot up process with the 4gb seg fixup problem if that helps to diagnose the problem. Thank you! Started domain sec-int-dns Linux version 2.6.20-2925.13.fc7xen (kojibuilder at xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue Jul 17 10:38:27 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1 Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/sda1 ro ip=:1.2.3.4:::sec-int-dns:eth0:dhcp 4 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c135d000 soft=c133d000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 3000.104 MHz processor. Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1064 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 114332k/139264k available (2023k kernel code, 16588k reserved, 1077k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc130c000 - 0xc1339000 ( 180 kB) .data : 0xc11f9fe5 - 0xc1307714 (1077 kB) .text : 0xc1000000 - 0xc11f9fe5 (2023 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 7504.32 BogoMIPS (lpj=15008654) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 6, 262144 bytes) TCP bind hash table entries: 4096 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 8752k freed IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1187228011.247:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 759k Registering block device major 8 blkfront: sda1: barriers enabled blkfront: sda2: barriers enabled netfront: Initialising virtual ethernet driver. netfront: device eth0 has copying receive path. USB Universal Host Controller Interface driver v3.0 SCSI subsystem initialized register_blkdev: cannot get major 8 for sd device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel at redhat.com EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. 4gb seg fixup, process init (pid 1), cs:ip 73:0092da56 4gb seg fixup, process init (pid 1), cs:ip 73:0099e2ee 4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f 4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d 4gb seg fixup, process init (pid 1), cs:ip 73:008e8b6b 4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f 4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d 4gb seg fixup, process init (pid 1), cs:ip 73:00901d7f 4gb seg fixup, process init (pid 1), cs:ip 73:0092c75f 4gb seg fixup, process init (pid 1), cs:ip 73:0092c76d SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1187228019.543:2): selinux=0 auid=4294967295 audit(1187228073.382:3): audit_backlog_limit=256 old=64 by auid=4294967295 audit(1187228073.774:4): audit_pid=778 old=0 by auid=4294967295 4gb seg fixup, process S28autofs (pid 804), cs:ip 73:0092914b printk: 129366 messages suppressed. 4gb seg fixup, process newaliases (pid 954), cs:ip 73:00217ce7 printk: 191711 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f printk: 18 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f printk: 41 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f printk: 15 messages suppressed. 4gb seg fixup, process sendmail (pid 962), cs:ip 73:0020d75f (Right here it keeps repeating the 4gb seg fixup.) > snip > When I go to boot the machine I get this: xm create -c xmconfig > 4gb seg fixup, process S28autofs (pid 825), cs:ip 73:0092914b > printk: 197950 messages suppressed. > 4gb seg fixup, process egrep (pid 973), cs:ip 73:008e8149 > printk: 116932 messages suppressed. > 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f > printk: 15 messages suppressed. > 4gb seg fixup, process dhcpd (pid 941), cs:ip 73:00d20d7f > printk: 108 messages suppressed. > 4gb seg fixup, process sendmail (pid 962), cs:ip 73:004d675f > printk: 15 messages suppressed. > 4gb seg fixup, process named (pid 752), cs:ip 73:002f775f > snip This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From schwier at rvs.uni-hannover.de Thu Aug 16 12:39:44 2007 From: schwier at rvs.uni-hannover.de (Harald Schwier) Date: Thu, 16 Aug 2007 14:39:44 +0200 Subject: [Fedora-xen] Fedora7 / Bridge instead of NAT Message-ID: <46C44590.3040400@rvs.uni-hannover.de> Hallo, My xen 3.1 dom-0 host uses a public IPv4 address and i want to configure the virtual machines with public addresses to. By default, the Fedora 7 network Interface virbr0 is configured with a private IPv4 address (192.168.122.1). How can i switch from NAT to bridged networking? Configuration in /etc/xen/xend-config.sxp : ... (network-script network-bridge) ... Thanks in advance, Harald From itamar at ispbrasil.com.br Fri Aug 17 02:59:15 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Thu, 16 Aug 2007 23:59:15 -0300 Subject: [Fedora-xen] Citrix acquires XenSource for desktop and server virtualization Message-ID: <00a901c7e07a$9b1c17d0$fe01a8c0@ispbrasil> this is good for xen ? now the xen team have alot of money to get a big beer http://www.networkworld.com/news/2007/081507-citrix-xensource-desktop-server-virtualization.html -------------------- Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 -------------- next part -------------- An HTML attachment was scrubbed... URL: From songtao.liu at mytum.de Fri Aug 17 15:24:08 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Fri, 17 Aug 2007 17:24:08 +0200 Subject: [Fedora-xen] PV network driver Message-ID: Hi, as now i want to insert PV driver in my HVM guest to get better network performance, so i should run the following steps as from the README in file: xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/ --------------------------------------------------------------------- To build, run ./mkbuildtree and then make -C /path/to/kernel/source M=$PWD modules You get four modules, xen-evtchn-pci.ko, xenbus.ko, xen-vbd.ko, and xen-vnif.ko. Load xen-evtchn-pci first, then xenbus, and then whichever of xen-vbd and xen-vnif you happen to need. ---------------------------------------------------------------------- after ./mkbuildtree the 'make' will bring following errors. where could be the problem? [root at localhost linux-2.6]# make -C /usr/src/kernels/2.6.19-1.2911.6.5.fc6xen-i686/ M=$PWD modules make: Entering directory `/usr/src/kernels/2.6.19-1.2911.6.5.fc6xen-i686' CC [M] /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.o :1:1: warning: "__XEN_INTERFACE_VERSION__" redefined :1:1: warning: this is the location of the previous definition In file included from /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c:39: /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/block.h:38:26: error: linux/config.h: No such file or directory /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/block.h:50:35: error: linux/devfs_fs_kernel.h: No such file or directory /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c: In function ???setup_blkring???: /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c:232: warning: passing argument 2 of ???bind_evtchn_to_irqhandler??? from incompatible pointer type /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c: In function ???backend_changed???: /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c:275: error: ???struct block_device??? has no member named ???bd_sem??? /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c:281: error: ???struct block_device??? has no member named ???bd_sem??? /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c: In function ???do_blkif_request???: /home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.c:617: warning: format ???%lx??? expects type ???long unsigned int???, but argument 4 has type ???sector_t??? make[2]: *** [/home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront/blkfront.o] Error 1 make[1]: *** [/home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6/blkfront] Error 2 make: *** [_module_/home/songtao/Desktop/rpm/xen-3.0.3-8.fc6.src.rpm_FILES/xen-3.0.3_0-src/unmodified_drivers/linux-2.6] Error 2 make: Leaving directory `/usr/src/kernels/2.6.19-1.2911.6.5.fc6xen-i686' [root at localhost linux-2.6]# ls /usr/src/kernels/2.6.19-1.2911.6.5.fc6xen-i686/ arch crypto fs init kabi_whitelist lib mm net security symsets-2.6.19-1.2911.6.5.fc6xen.tar.gz block drivers include ipc kernel Makefile Module.symvers scripts sound usr [root at localhost linux-2.6]# uname -a Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux [root at localhost linux-2.6]# rpm -qa | grep xen xen-libs-3.0.3-8.fc6 kernel-xen-debuginfo-2.6.19-1.2911.6.5.fc6 kernel-xen-2.6.19-1.2911.6.5.fc6 xen-debuginfo-3.0.3-8.fc6 xen-3.0.3-8.fc6 Any hint will be highly appreciated. Thanks Songtao From jsteer at bitscout.com Sun Aug 19 04:37:43 2007 From: jsteer at bitscout.com (Jon Steer) Date: Sun, 19 Aug 2007 00:37:43 -0400 Subject: [Fedora-xen] Cannot boot F7 LiveCD as Xen Guest Message-ID: <74e6f65d0708182137o271716afta9eca12aa73ea330@mail.gmail.com> Hello, I am trying to boot a F7 LiveCD with the following command line virt-install --hvm --name=mytestvm --ram=1280 \ --nodisks --livecd --cdrom=livecd-20070818-2122.iso \ --os-type=linux --vcpus=1 --vnc However, I cannot connect to the console. All that I get is a black screen. The liveCD is built with the default livecd-tools kickstart which produces a simple, no-X based console system. I have read through the list and noticed that there was a thread about having to have inittab setup so that the console is pointed at xvc0? and also so the kernel had a command line of "console=tty console=xvc0,9600n8" is this the case, or is there something else I'm missing? thanks, jon From rjones at redhat.com Mon Aug 20 12:38:53 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 20 Aug 2007 13:38:53 +0100 Subject: [Fedora-xen] ANNOUNCE: Virt-top 0.3.1.5 - a top-like utility for displaying virtualization stats In-Reply-To: References: <46B78F84.10309@redhat.com> <46BB253C.5010204@redhat.com> Message-ID: <46C98B5D.5000401@redhat.com> Andy Burns wrote: > On 09/08/07, Richard W.M. Jones wrote: > >> There is a significantly updated version of virt-top now available. On >> systems which support it, you can show the mapping of domains to >> physical CPUs and the amount of each physical CPU being used. > > I downloaded the binary 64bit version and ran it on a fedora 7 xen > host without any problems, the host is a dual-core xeon andnoticed > the CPU% reporting works differently compared to xentop, I assume this > is deliberate? Thanks for trying this! I was on holiday last week, hence the late reply. > virt-top seems to report each domain's usage as a percentage of all > the sum of all CPUs, where xentop seems to report the percentages in > terms of a single CPU. > > e.g. on xentop may show dom0 taking 102% and my domU taking 24%, while > virt-top will shows this as 51% and 12% respectively, which seems more > logical. Yes, this is deliberate. We wanted to make it work like virt-manager and plain top. Notice that xentop is the exception in this regard. Rich. PS: I will be making available proper binaries for RHEL, Fedora, CentOS and Debian, i386 & x86-64, this week. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From justin.conover at gmail.com Mon Aug 20 19:17:46 2007 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 20 Aug 2007 14:17:46 -0500 Subject: [Fedora-xen] freeing up memory back to Domain-0 Message-ID: How can you free up memory when you shut a guest down? Give back to Domain-0 so you can start another one up? Also, were are the profiles for xen stored? For example I create all of them under /vm/xen/blah if I decide to delete blah1 and create a new one named blah1 it says it is already there, even though I removed it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Tue Aug 21 11:28:25 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 21 Aug 2007 12:28:25 +0100 Subject: [Fedora-xen] freeing up memory back to Domain-0 In-Reply-To: References: Message-ID: <46CACC59.7040003@redhat.com> Justin Conover wrote: [These are a couple of frequently asked questions ... do we have an FAQ?] > How can you free up memory when you shut a guest down? Give back to > Domain-0 so you can start another one up? Domain-0 doesn't recover the memory when a domain shuts down. The assumption (within Xen) is that another domain will be starting up shortly, so there is no point wasting time returning the memory to Domain-0. However the memory hasn't just gone away, as your question implies. The hypervisor is still managing that free memory, and will give it to the next guest which starts up. If you really want to give the free memory back to Domain-0, then I think you can do it by: virsh setmem Domain-0 where is the total number of kilobytes that you want Domain-0 to have (ie. current size + size of freed guest -- you have to calculate this for yourself). > Also, were are the profiles for xen stored? For example I create all of > them under /vm/xen/blah if I decide to delete blah1 and create a new one > named blah1 it says it is already there, even though I removed it. Since Xen 3.0.3 or 3.0.4, I forget exactly which, Xen manages the profiles in its own private place. So there are no configuration files. I agree that this is very annoying, but that's the way Xen forces us to do it. To view or edit a configuration file, you now have to do: virsh dumpxml domain > domain.xml edit domain.xml virsh define domain.xml ('virsh define' only works if the domain has been shutdown, so if it is still running then shut it down first using 'virsh shutdown'). If you want to make a change to a running domain, there are some changes which you are allowed to do, basically adding and removing block and network devices, and adding and removing memory. The commands to use are: virsh attach-device virsh attach-disk virsh attach-interface virsh detach-device virsh detach-disk virsh detach-interface virsh setmem virsh setmaxmem (Just do 'virsh help command' to get help on each of those commands). Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Tue Aug 21 11:38:40 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 21 Aug 2007 12:38:40 +0100 Subject: [Fedora-xen] freeing up memory back to Domain-0 In-Reply-To: <46CACC59.7040003@redhat.com> References: <46CACC59.7040003@redhat.com> Message-ID: <46CACEC0.60206@redhat.com> Richard W.M. Jones wrote: > Justin Conover wrote: >> Also, were are the profiles for xen stored? For example I create all >> of them under /vm/xen/blah if I decide to delete blah1 and create a >> new one named blah1 it says it is already there, even though I removed >> it. I should add that if you want Xen to completely forget about a domain, you must: (1) shut it down, if not already (virsh shutdown) (2) undefine it (virsh undefine) (3) delete any disk image file or disk partition It's step (3) which actually gets rid of the data stored in the domain. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From justin.conover at gmail.com Tue Aug 21 11:58:08 2007 From: justin.conover at gmail.com (Justin Conover) Date: Tue, 21 Aug 2007 06:58:08 -0500 Subject: [Fedora-xen] freeing up memory back to Domain-0 In-Reply-To: <46CACC59.7040003@redhat.com> References: <46CACC59.7040003@redhat.com> Message-ID: On 8/21/07, Richard W.M. Jones wrote: > > Justin Conover wrote: > > [These are a couple of frequently asked questions ... do we have an FAQ?] > > > How can you free up memory when you shut a guest down? Give back to > > Domain-0 so you can start another one up? > > Domain-0 doesn't recover the memory when a domain shuts down. The > assumption (within Xen) is that another domain will be starting up > shortly, so there is no point wasting time returning the memory to > Domain-0. > > However the memory hasn't just gone away, as your question implies. The > hypervisor is still managing that free memory, and will give it to the > next guest which starts up. > > If you really want to give the free memory back to Domain-0, then I > think you can do it by: > > virsh setmem Domain-0 > > where is the total number of kilobytes that you want Domain-0 to > have (ie. current size + size of freed guest -- you have to calculate > this for yourself). > > > Also, were are the profiles for xen stored? For example I create all of > > them under /vm/xen/blah if I decide to delete blah1 and create a new one > > named blah1 it says it is already there, even though I removed it. > > Since Xen 3.0.3 or 3.0.4, I forget exactly which, Xen manages the > profiles in its own private place. So there are no configuration files. > I agree that this is very annoying, but that's the way Xen forces us > to do it. > > To view or edit a configuration file, you now have to do: > > virsh dumpxml domain > domain.xml > edit domain.xml > virsh define domain.xml > > ('virsh define' only works if the domain has been shutdown, so if it is > still running then shut it down first using 'virsh shutdown'). > > If you want to make a change to a running domain, there are some changes > which you are allowed to do, basically adding and removing block and > network devices, and adding and removing memory. The commands to use are: > > virsh attach-device > virsh attach-disk > virsh attach-interface > virsh detach-device > virsh detach-disk > virsh detach-interface > virsh setmem > virsh setmaxmem > > (Just do 'virsh help command' to get help on each of those commands). > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 > > Very nice, thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From per at actius.com Tue Aug 21 15:39:49 2007 From: per at actius.com (Per Hjartoy) Date: Tue, 21 Aug 2007 08:39:49 -0700 Subject: [Fedora-xen] win2k3 server standard edition hangson"StartingWindows" In-Reply-To: <000f01c7df94$417a0ca0$3b354b0a@actius.com> References: <000f01c7df94$417a0ca0$3b354b0a@actius.com> Message-ID: <020401c7e409$8287b980$20111bac@actius.com> All, We have made some progress with the Win2k3 server install, but need help on how to mount a CD in a running guest. The initial problem Chris and I had was to have the CD Rom correctly recognized. The best way seems to be to use the definition of the CD Rom drive in /etc/sysconfig/hwconf which was /dev/scd0. Using this in the guest configuration file, I got the following xml (where '/dev/scdo' is from hwconf) (Also note the that is sparsely documented): If I have a CD Rom in the drive when I start the Win2K3 Guest, it is usable both from Fedora as well as Win2K3! The catch is that I have found no way to access a CD that is inserted after the Guest has started. It is interesting that the only way to make this definition is with the following sequence: # virsh dumpxml > foo.xml # vi foo.xml (and then edit according to instructions above) # virsh define foo.xml The visual tools are not able to create this, and it appears that the only way to set up Win2k3 is by making an .iso of the installation CD first (use dd command). I don't have my images in /var/lib/xen/images. It appears not to matter under F7. Do you have any ideas to how to mount the cd for a running guest? -- Per -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Per Hjartoy Sent: Wednesday, August 15, 2007 4:30 PM To: fedora-xen at redhat.com Subject: RE: [Fedora-xen] win2k3 server standard edition hangson"StartingWindows" Hi Chris, I'm trying to install win2k3 standard on Fedora 7. The configuration system is different, but I'm running into the same issues that you have. I've been able to solve the CD problem with the help of Andy (RedHat). (I met him at Linux World last week) No documentation exists about this matter as we could find. However, there are still issues and any reboot of the win2k3 server requires a "fake" reinstall to get it up and running again. If we could connect off list, maybe we could compare notes and report back about our progress. It would also be nice to get someone from the distro team to join us as well. I have suspicion that virtualization of win2k3 wasn't given much attention and that we jointly can provide some good feedback. You can contact me a per-at-actius-dot-com. -- Per -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Christopher Miller Sent: Wednesday, August 15, 2007 4:09 PM To: fedora-xen at redhat.com Subject: RE: [Fedora-xen] win2k3 server standard edition hangs on"StartingWindows" Okay, I found a couple months back where a fella pushed F5 during the initial setup phase, I did that and got as far as rebooting the machine into the installation. I see now I have to add the CDROM device back in the conf file. I've yet to find the instructions on this, but I'm sure they're in the archives somewhere. I'll keep posted on my progress. peace, cj -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]On Behalf Of Christopher Miller Sent: Wednesday, August 15, 2007 10:43 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] win2k3 server standard edition hangs on "StartingWindows" Hello list! I'm having a heck of a time getting Windows 2003 Server Standard Edition to install. I've tried using both virt-install and virt-manager, however it would seem that virt-manager gets further. On the command line, I used this to provision the machine: # virt-install \ --name=system1 \ --ram=2048 \ --file=/home/luser/virtuals/system1/system1.img \ --file-size=80 \ --nonsparse \ --network=bridge:xenbr0 \ --sdl \ --hvm \ --os-type=windows \ --os-variant=win2k3 \ --cdrom=/media/EN_OS_XP_2003_2428.4/english/win2003/standard/setup.exe this command failed until I "touch"ed /home/luser/virtuals/system1/system1.img, and then said it was provisioning, and I should reconnect to the domain to see the machine, when I tried this, it was unavailable. As I've indicated, my experience with virt-manager gets me "further" but what this further is, isn't usable either. I select the same options as above in the gui, and when I click "finish" it allocates the file I've selected, and the new domain shows up in the virt-manager window. I can right-click on the new virtual and connect to the console, select which version of windows I'm installing, and the startup even runs up to the point where it says "Windows Setup: Setup is starting Windows" (this is the last blue dos type screen before being switched into the windows install gui, for those familiar) and freezes there. I've posted a couple screen shots here: http://63.231.71.205/~cj/xen/AllWindows.png http://63.231.71.205/~cj/xen/Console.png I'm running Fedora Core 6, all updates, on a AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, kernel 2.6.20-1.2999.fc6xen, 3GB RAM. I'm installing from an MSDN disk in my cdrom drive. Please let me know if there's any more information I can provide. Thanks in advance! Christopher Jon Miller Programmer, Research and Development -------------------------------------------------------www.eCollege.com eCollege Supporting your Success cjm at eCollege.com phone 303.873.7400x3233 cell 303.552.7666 fax 303.632.1719 eCollege Building 4900 S Monaco St Denver, CO 80237 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From dsm717 at gmail.com Tue Aug 21 17:06:44 2007 From: dsm717 at gmail.com (David Mueller) Date: Tue, 21 Aug 2007 10:06:44 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces Message-ID: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> I'm trying to move from Fedora Core 5 to Fedora 7. I've run into an issue where the xen guests, which need several bridged interfaces bound to dummy devices so they can communicate with each other (similar to host-only networking with VMWare), won't boot. I think I've traced the problem to a lack of the dummy1, dummy2, and dummy3 devices, and I'm not sure how to fix it. What I'll describe below is the setup that worked in Fedora Core 5: I used the following custom network-bridge script: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1 "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2 "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3 And the following line was used in the .xen files passed to xm create: vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1', 'mac=2E:22:22:22:22:21,bridge=xenbr2', 'mac=2E:22:22:22:22:22,bridge=xenbr3'] Running the script resulted in the following: Using config file "./guest1.xen". Error: Device 0 (vif) could not be connected. Could not find bridge device xenbr1 If I try to run the custom network-bridge script manually passing the "start" command I get several errors: Device "dummy1" does not exist. usage: ifdown Device "dummy1" does not exist. Cannot find device "dummy1" SIOCGIFFLAGS: No such device Device "dummy2" does not exist. usage: ifdown Device "dummy2" does not exist. Cannot find device "dummy2" SIOCGIFFLAGS: No such device Device "dummy3" does not exist. usage: ifdown Device "dummy3" does not exist. Cannot find device "dummy3" SIOCGIFFLAGS: No such device Any ideas on how to get this working would be greatly appreciated. - David From per at actius.com Wed Aug 22 18:37:27 2007 From: per at actius.com (Per Hjartoy) Date: Wed, 22 Aug 2007 11:37:27 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> Message-ID: <001001c7e4eb$7d3b8a50$06000100@actius.com> David, The configuration has changed quite a bit between F5 and F7. I've found that there is not much you can do unless you go "virsh dumpxml ...". In my experimentation, I made the most progress when I defined the device with dummy data in the GUI version. I could then dump the result out and make changes in the xml template I got. Finally I would reload by "virsh define ...". Hope this helps. -- Per -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Mueller Sent: Tuesday, August 21, 2007 10:07 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces I'm trying to move from Fedora Core 5 to Fedora 7. I've run into an issue where the xen guests, which need several bridged interfaces bound to dummy devices so they can communicate with each other (similar to host-only networking with VMWare), won't boot. I think I've traced the problem to a lack of the dummy1, dummy2, and dummy3 devices, and I'm not sure how to fix it. What I'll describe below is the setup that worked in Fedora Core 5: I used the following custom network-bridge script: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1 "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2 "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3 And the following line was used in the .xen files passed to xm create: vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1', 'mac=2E:22:22:22:22:21,bridge=xenbr2', 'mac=2E:22:22:22:22:22,bridge=xenbr3'] Running the script resulted in the following: Using config file "./guest1.xen". Error: Device 0 (vif) could not be connected. Could not find bridge device xenbr1 If I try to run the custom network-bridge script manually passing the "start" command I get several errors: Device "dummy1" does not exist. usage: ifdown Device "dummy1" does not exist. Cannot find device "dummy1" SIOCGIFFLAGS: No such device Device "dummy2" does not exist. usage: ifdown Device "dummy2" does not exist. Cannot find device "dummy2" SIOCGIFFLAGS: No such device Device "dummy3" does not exist. usage: ifdown Device "dummy3" does not exist. Cannot find device "dummy3" SIOCGIFFLAGS: No such device Any ideas on how to get this working would be greatly appreciated. - David -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From jlagrue at gmail.com Wed Aug 22 21:35:30 2007 From: jlagrue at gmail.com (John Lagrue) Date: Wed, 22 Aug 2007 22:35:30 +0100 Subject: [Fedora-xen] Xen, QEMU/KVM or Vmware ? Message-ID: Being quite keen on the concept of virtualisation, I find myself in a bit of a quandary with F7. Being one who needs an uptodate kernel (my laptop power does funny things with older ones) I can't run Xen because the kernels are too old. Therefore I have QEMU/KVM or Vmware. Though the F7 documents talk lightly about QEMU being all part of the Virtual Machine Manager, it isn't really; the resulting systems are slow, refuse to boot off valid ISO images and have no configuration options for networking. They don't even use the system CDROM until you specifically add it after the virtual machine is built. So I use qemu-kvm on the command line; not that the Fedora documents mention that option - thank heaven for Google! But I also see that others are choosing Vmware server to virtualise guests, and I wonder why. qemu-kvm is pretty good and fairly fast, so I'm really asking why people choose to use a 3rd party system instead; is it faster? Coupled with that: is the virtual machine manager going to work properly with QEMU/KVM one day, or are the developers all assuming we'll go for Xen? And if the latter, when might we get an Xen kernel that's uptodate? Enquiring minds want to know. JDL From per at actius.com Wed Aug 22 21:44:56 2007 From: per at actius.com (Per Hjartoy) Date: Wed, 22 Aug 2007 14:44:56 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> Message-ID: <004a01c7e505$ae721de0$06000100@actius.com> Is "test_vm" your guest? If not, that is what you need to use as an argument to virsh and not the Domain-0 (vm container). -- Per -----Original Message----- From: David Mueller [mailto:dsm717 at gmail.com] Sent: Wednesday, August 22, 2007 2:03 PM To: Per Hjartoy Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Fedora 7 - missing dummy interfaces Per, Ok. I was hoping there was something realatively straightforward to change. I've also been working on a new approach to use KVM with Fedora 7. I've been able to use Revisor to create a custom Install CD image and used that with virt-manager to create a virtual machine. However, I've run into a wall with virt-manager's insistance on using only private IP address space. Your suggestion to dump the result to xml and modify that seems like it might work, except I can't get virsh to work: # virsh dumpxml test_vm error: failed to connect to the hypervisor error: no valid connection Where test_vm is the name of my virtual machine in the Name column of the virt-manager GUI. It doesn't make a difference whether or not the virtual machine is running at the time. - David On 8/22/07, Per Hjartoy wrote: > David, The configuration has changed quite a bit between F5 and F7. I've > found that there is not much you can do unless you go "virsh dumpxml ...". > In my experimentation, I made the most progress when I defined the device > with dummy data in the GUI version. I could then dump the result out and > make changes in the xml template I got. Finally I would reload by "virsh > define ...". Hope this helps. -- Per > > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of David Mueller > Sent: Tuesday, August 21, 2007 10:07 AM > To: fedora-xen at redhat.com > Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces > > I'm trying to move from Fedora Core 5 to Fedora 7. I've run into an > issue where the xen guests, which need several bridged interfaces > bound to dummy devices so they can communicate with each other > (similar to host-only networking with VMWare), won't boot. I think > I've traced the problem to a lack of the dummy1, dummy2, and dummy3 > devices, and I'm not sure how to fix it. What I'll describe below is > the setup that worked in Fedora Core 5: > > I used the following custom network-bridge script: > > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 > "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1 > "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2 > "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3 > > And the following line was used in the .xen files passed to xm create: > > vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1', > 'mac=2E:22:22:22:22:21,bridge=xenbr2', > 'mac=2E:22:22:22:22:22,bridge=xenbr3'] > > Running the script resulted in the following: > > Using config file "./guest1.xen". > Error: Device 0 (vif) could not be connected. Could not find bridge > device xenbr1 > > If I try to run the custom network-bridge script manually passing the > "start" command I get several errors: > > Device "dummy1" does not exist. > usage: ifdown > Device "dummy1" does not exist. > Cannot find device "dummy1" > SIOCGIFFLAGS: No such device > Device "dummy2" does not exist. > usage: ifdown > Device "dummy2" does not exist. > Cannot find device "dummy2" > SIOCGIFFLAGS: No such device > Device "dummy3" does not exist. > usage: ifdown > Device "dummy3" does not exist. > Cannot find device "dummy3" > SIOCGIFFLAGS: No such device > > Any ideas on how to get this working would be greatly appreciated. > > - David > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > From dsm717 at gmail.com Wed Aug 22 21:02:48 2007 From: dsm717 at gmail.com (David Mueller) Date: Wed, 22 Aug 2007 14:02:48 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <001001c7e4eb$7d3b8a50$06000100@actius.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> Message-ID: <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> Per, Ok. I was hoping there was something realatively straightforward to change. I've also been working on a new approach to use KVM with Fedora 7. I've been able to use Revisor to create a custom Install CD image and used that with virt-manager to create a virtual machine. However, I've run into a wall with virt-manager's insistance on using only private IP address space. Your suggestion to dump the result to xml and modify that seems like it might work, except I can't get virsh to work: # virsh dumpxml test_vm error: failed to connect to the hypervisor error: no valid connection Where test_vm is the name of my virtual machine in the Name column of the virt-manager GUI. It doesn't make a difference whether or not the virtual machine is running at the time. - David On 8/22/07, Per Hjartoy wrote: > David, The configuration has changed quite a bit between F5 and F7. I've > found that there is not much you can do unless you go "virsh dumpxml ...". > In my experimentation, I made the most progress when I defined the device > with dummy data in the GUI version. I could then dump the result out and > make changes in the xml template I got. Finally I would reload by "virsh > define ...". Hope this helps. -- Per > > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of David Mueller > Sent: Tuesday, August 21, 2007 10:07 AM > To: fedora-xen at redhat.com > Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces > > I'm trying to move from Fedora Core 5 to Fedora 7. I've run into an > issue where the xen guests, which need several bridged interfaces > bound to dummy devices so they can communicate with each other > (similar to host-only networking with VMWare), won't boot. I think > I've traced the problem to a lack of the dummy1, dummy2, and dummy3 > devices, and I'm not sure how to fix it. What I'll describe below is > the setup that worked in Fedora Core 5: > > I used the following custom network-bridge script: > > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 > "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1 > "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2 > "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3 > > And the following line was used in the .xen files passed to xm create: > > vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1', > 'mac=2E:22:22:22:22:21,bridge=xenbr2', > 'mac=2E:22:22:22:22:22,bridge=xenbr3'] > > Running the script resulted in the following: > > Using config file "./guest1.xen". > Error: Device 0 (vif) could not be connected. Could not find bridge > device xenbr1 > > If I try to run the custom network-bridge script manually passing the > "start" command I get several errors: > > Device "dummy1" does not exist. > usage: ifdown > Device "dummy1" does not exist. > Cannot find device "dummy1" > SIOCGIFFLAGS: No such device > Device "dummy2" does not exist. > usage: ifdown > Device "dummy2" does not exist. > Cannot find device "dummy2" > SIOCGIFFLAGS: No such device > Device "dummy3" does not exist. > usage: ifdown > Device "dummy3" does not exist. > Cannot find device "dummy3" > SIOCGIFFLAGS: No such device > > Any ideas on how to get this working would be greatly appreciated. > > - David > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > From dsm717 at gmail.com Wed Aug 22 22:04:54 2007 From: dsm717 at gmail.com (David Mueller) Date: Wed, 22 Aug 2007 15:04:54 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <004a01c7e505$ae721de0$06000100@actius.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <004a01c7e505$ae721de0$06000100@actius.com> Message-ID: <137a61500708221504g228a3882j397d3a6eee2b266b@mail.gmail.com> Yes, test_vm is the name of the virtual machine in the second column of the list in virt-manager. If I just try to launch virsh I get an error too: # virsh error: failed to connect to the hypervisor Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # Note that I am using the standard kernel 2.6.22.1-41.fc7 and not a xen0 kernel, so it should be using KVM rather than xen. The computer has an Intel Core Duo processor with the Virtualization instructions enabled in BIOS -- the guest VM runs just fine. - David On 8/22/07, Per Hjartoy wrote: > Is "test_vm" your guest? If not, that is what you need to use as an > argument to virsh and not the Domain-0 (vm container). -- Per > > -----Original Message----- > From: David Mueller [mailto:dsm717 at gmail.com] > Sent: Wednesday, August 22, 2007 2:03 PM > To: Per Hjartoy > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Fedora 7 - missing dummy interfaces > > Per, > > Ok. I was hoping there was something realatively straightforward to change. > > I've also been working on a new approach to use KVM with Fedora 7. > I've been able to use Revisor to create a custom Install CD image and > used that with virt-manager to create a virtual machine. However, > I've run into a wall with virt-manager's insistance on using only > private IP address space. Your suggestion to dump the result to xml > and modify that seems like it might work, except I can't get virsh to > work: > > # virsh dumpxml test_vm > error: failed to connect to the hypervisor > error: no valid connection > > Where test_vm is the name of my virtual machine in the Name column of > the virt-manager GUI. It doesn't make a difference whether or not the > virtual machine is running at the time. > > - David > > On 8/22/07, Per Hjartoy wrote: > > David, The configuration has changed quite a bit between F5 and F7. I've > > found that there is not much you can do unless you go "virsh dumpxml ...". > > In my experimentation, I made the most progress when I defined the device > > with dummy data in the GUI version. I could then dump the result out and > > make changes in the xml template I got. Finally I would reload by "virsh > > define ...". Hope this helps. -- Per > > > > -----Original Message----- > > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > > On Behalf Of David Mueller > > Sent: Tuesday, August 21, 2007 10:07 AM > > To: fedora-xen at redhat.com > > Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces > > > > I'm trying to move from Fedora Core 5 to Fedora 7. I've run into an > > issue where the xen guests, which need several bridged interfaces > > bound to dummy devices so they can communicate with each other > > (similar to host-only networking with VMWare), won't boot. I think > > I've traced the problem to a lack of the dummy1, dummy2, and dummy3 > > devices, and I'm not sure how to fix it. What I'll describe below is > > the setup that worked in Fedora Core 5: > > > > I used the following custom network-bridge script: > > > > #!/bin/sh > > dir=$(dirname "$0") > > "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 > > "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1 > > "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2 > > "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3 > > > > And the following line was used in the .xen files passed to xm create: > > > > vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1', > > 'mac=2E:22:22:22:22:21,bridge=xenbr2', > > 'mac=2E:22:22:22:22:22,bridge=xenbr3'] > > > > Running the script resulted in the following: > > > > Using config file "./guest1.xen". > > Error: Device 0 (vif) could not be connected. Could not find bridge > > device xenbr1 > > > > If I try to run the custom network-bridge script manually passing the > > "start" command I get several errors: > > > > Device "dummy1" does not exist. > > usage: ifdown > > Device "dummy1" does not exist. > > Cannot find device "dummy1" > > SIOCGIFFLAGS: No such device > > Device "dummy2" does not exist. > > usage: ifdown > > Device "dummy2" does not exist. > > Cannot find device "dummy2" > > SIOCGIFFLAGS: No such device > > Device "dummy3" does not exist. > > usage: ifdown > > Device "dummy3" does not exist. > > Cannot find device "dummy3" > > SIOCGIFFLAGS: No such device > > > > Any ideas on how to get this working would be greatly appreciated. > > > > - David > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > From berrange at redhat.com Wed Aug 22 22:09:27 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Aug 2007 23:09:27 +0100 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> Message-ID: <20070822220927.GQ18061@redhat.com> On Wed, Aug 22, 2007 at 02:02:48PM -0700, David Mueller wrote: > Per, > > Ok. I was hoping there was something realatively straightforward to change. > > I've also been working on a new approach to use KVM with Fedora 7. > I've been able to use Revisor to create a custom Install CD image and > used that with virt-manager to create a virtual machine. However, > I've run into a wall with virt-manager's insistance on using only > private IP address space. Your suggestion to dump the result to xml > and modify that seems like it might work, except I can't get virsh to > work: virt-manager will happily use bridging for KVM guests if you setup your host so that its physical interfaces are part of a bridge. There's a guide here: http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt Basically we recommend bridging (configured in /etc/sysconfig/network-scripts) for machines with permanent wired ethernet connections. We recommend the NAT based virtual networking for machines with dynamic connections (eg Networkmanager) or using wireless / VPN / dialup. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Aug 23 02:16:00 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 23 Aug 2007 03:16:00 +0100 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708221504g228a3882j397d3a6eee2b266b@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <004a01c7e505$ae721de0$06000100@actius.com> <137a61500708221504g228a3882j397d3a6eee2b266b@mail.gmail.com> Message-ID: <20070823021600.GG18061@redhat.com> On Wed, Aug 22, 2007 at 03:04:54PM -0700, David Mueller wrote: > Yes, test_vm is the name of the virtual machine in the second column > of the list in virt-manager. If I just try to launch virsh I get an > error too: > > # virsh > error: failed to connect to the hypervisor > Welcome to virsh, the virtualization interactive terminal. > > Type: 'help' for help with commands > 'quit' to quit > > virsh # > > Note that I am using the standard kernel 2.6.22.1-41.fc7 and not a > xen0 kernel, so it should be using KVM rather than xen. When connecting with virsh, you need to provide a URI to override the default use of Xen. For QEMU/KVM use 'virsh --connect qemu:///system' Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dsm717 at gmail.com Thu Aug 23 02:24:45 2007 From: dsm717 at gmail.com (David Mueller) Date: Wed, 22 Aug 2007 19:24:45 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <20070823021600.GG18061@redhat.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <004a01c7e505$ae721de0$06000100@actius.com> <137a61500708221504g228a3882j397d3a6eee2b266b@mail.gmail.com> <20070823021600.GG18061@redhat.com> Message-ID: <46CCEFED.4040401@gmail.com> Daniel P. Berrange wrote: > When connecting with virsh, you need to provide a URI to override the > default use of Xen. For QEMU/KVM use 'virsh --connect qemu:///system' Thanks, that fixed the issue. I'll look at the rest tomorrow and see If I can get something working. Perhaps a future feature could attempt to detect whether or not a xen kernel is running and if not, connect to QEMU/KVM instead? - David From Wiwat.Tharateeraparb at reuters.com Thu Aug 23 05:09:56 2007 From: Wiwat.Tharateeraparb at reuters.com (Wiwat Tharateeraparb) Date: Thu, 23 Aug 2007 12:09:56 +0700 Subject: [Fedora-xen] Install guest os from cd/dvd media Message-ID: <9E303D777B7A3B4391787454AA05334702CF82DD@BKKSMSXM01.apac.ime.reuters.com> can virt-manager and libvirt are now able to install a guest os from cd/dvd/iso directly? -- Wiwat Tharateeraparb This email was sent to you by Reuters, the global news and information company. To find out more about Reuters visit www.about.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Limited. Reuters Limited is part of the Reuters Group of companies, of which Reuters Group PLC is the ultimate parent company. Reuters Group PLC - Registered office address: The Reuters Building, South Colonnade, Canary Wharf, London E14 5EP, United Kingdom Registered No: 3296375 Registered in England and Wales -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsteer at bitscout.com Thu Aug 23 05:15:55 2007 From: jsteer at bitscout.com (Jon Steer) Date: Thu, 23 Aug 2007 00:15:55 -0500 Subject: [Fedora-xen] Install guest os from cd/dvd media In-Reply-To: <9E303D777B7A3B4391787454AA05334702CF82DD@BKKSMSXM01.apac.ime.reuters.com> References: <9E303D777B7A3B4391787454AA05334702CF82DD@BKKSMSXM01.apac.ime.reuters.com> Message-ID: <74e6f65d0708222215n4e1d71cbr8df73e2b54ce4944@mail.gmail.com> I have not been able to install an F7 liveCD as a guest on an F7 host. Various drivers in xen appear to old.. jon On 8/23/07, Wiwat Tharateeraparb wrote: > > can virt-manager and libvirt are now able to install a guest os from > cd/dvd/iso directly? > > > -- > Wiwat Tharateeraparb > > This email was sent to you by Reuters, the global news and information > company. > To find out more about Reuters visit www.about.reuters.com > > Any views expressed in this message are those of the individual sender, > except where the sender specifically states them to be the views of Reuters > Limited. > > Reuters Limited is part of the Reuters Group of companies, of which Reuters > Group PLC is the ultimate parent company. Reuters Group PLC - Registered > office address: The Reuters Building, South Colonnade, Canary Wharf, London > E14 5EP, United Kingdom > Registered No: 3296375 > Registered in England and Wales > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- "Whereever you go, there you are" From kraxel at redhat.com Thu Aug 23 08:37:58 2007 From: kraxel at redhat.com (Gerd Hoffmann) Date: Thu, 23 Aug 2007 10:37:58 +0200 Subject: [Fedora-xen] Xen, QEMU/KVM or Vmware ? In-Reply-To: References: Message-ID: <46CD4766.6000506@redhat.com> Hi, > Coupled with that: is the virtual machine manager going to work > properly with QEMU/KVM one day, or are the developers all assuming > we'll go for Xen? And if the latter, when might we get an Xen kernel > that's uptodate? I'm using qemu/kvm all day long on my laptop, works fine for me. There are a few shortcomings tough. You can't configure virtual serial and parallel ports yet via libvirt for example. Also not all options are available in the virt-manager GUI, so you'll have to hand-edit the xml config files from time to time. One very useful thing not visible in the gui is the emulator binary path. You can have that point to qemu for one and to kvm for another VM and have them both run libvirt-managed side-by-side. You can also point it to some wrapper script to sneak in some parameters into the qemu command line for options not (yet) supported by libvirt. So it isn't (yet) as comforable as vmware, but works well enougth for my needs. cheers, Gerd From zimmermann at it.neclab.eu Thu Aug 23 12:14:34 2007 From: zimmermann at it.neclab.eu (Falk Zimmermann) Date: Thu, 23 Aug 2007 14:14:34 +0200 Subject: [Fedora-xen] Problems running xp guest Message-ID: <46CD7A2A.3010806@it.neclab.eu> Hi, I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and used virt-manager to configure an F7 and xp guest domain. Whereas I can correctly run the F7 guest, I receive the following message after trying to run the xp guest: (xend.err 'Disk image does not exist: ') Both images reside in the same directory (/var/lib/xen/images) and I have selinux disabled. Any ideas? Thanks, Falk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3249 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Thu Aug 23 13:28:35 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 23 Aug 2007 14:28:35 +0100 Subject: [Fedora-xen] Xen, QEMU/KVM or Vmware ? In-Reply-To: References: Message-ID: <46CD8B83.8030902@redhat.com> John Lagrue wrote: > But I also see that others are choosing Vmware server to virtualise > guests, and I wonder why. qemu-kvm is pretty good and fairly fast, so > I'm really asking why people choose to use a 3rd party system instead; > is it faster? VMWare is a mature piece of software, and it's mature because it's been around for 10 years or so. KVM is only about 1/5th as old :-) KVM also requires that your processor supports virtualisation features, and at the moment these types of processors are not very widespread, although in a few years time they will definitely be very common. Because VMWare (and Xen) run on more common hardware, you'll find more of them about. > Coupled with that: is the virtual machine manager going to work > properly with QEMU/KVM one day, or are the developers all assuming > we'll go for Xen? And if the latter, when might we get an Xen kernel > that's uptodate? Yes definitely we want virt-manager to work well with QEMU and KVM. If you have found specific problems, please check out the bug database (https://bugzilla.redhat.com/). Feel free also to join in contributing fixes if you are able. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Thu Aug 23 13:29:40 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 23 Aug 2007 14:29:40 +0100 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CD7A2A.3010806@it.neclab.eu> References: <46CD7A2A.3010806@it.neclab.eu> Message-ID: <46CD8BC4.1000904@redhat.com> Falk Zimmermann wrote: > Hi, > I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and > used virt-manager to configure an F7 and xp guest domain. Whereas I can > correctly run the F7 guest, I receive the following message after trying > to run the xp guest: > > (xend.err 'Disk image does not exist: ') > > Both images reside in the same directory (/var/lib/xen/images) and I > have selinux disabled. > Any ideas? Can you try: virsh dumpxml (where is the name of the XP guest domain). Then check that the disk device shown has the right path. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From zimmermann at it.neclab.eu Thu Aug 23 13:42:57 2007 From: zimmermann at it.neclab.eu (Falk Zimmermann) Date: Thu, 23 Aug 2007 15:42:57 +0200 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CD8BC4.1000904@redhat.com> References: <46CD7A2A.3010806@it.neclab.eu> <46CD8BC4.1000904@redhat.com> Message-ID: <46CD8EE1.4010402@it.neclab.eu> Richard W.M. Jones schrieb: > Falk Zimmermann wrote: >> Hi, >> I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and >> used virt-manager to configure an F7 and xp guest domain. Whereas I can >> correctly run the F7 guest, I receive the following message after trying >> to run the xp guest: >> >> (xend.err 'Disk image does not exist: ') >> >> Both images reside in the same directory (/var/lib/xen/images) and I >> have selinux disabled. >> Any ideas? > > Can you try: > > virsh dumpxml > > (where is the name of the XP guest domain). Then check that the > disk device shown has the right path. > > Rich. > Hi Richard, the entry in the xml file looks fine (at least to me) and the image file exists: xp4 1e9860a0e244a2645b0a321a0fe649ec hvm /usr/lib/xen/boot/hvmloader 512000 1 destroy restart restart /usr/lib64/xen/bin/qemu-dm Cheers, Falk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3249 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Thu Aug 23 13:48:18 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 23 Aug 2007 14:48:18 +0100 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CD8EE1.4010402@it.neclab.eu> References: <46CD7A2A.3010806@it.neclab.eu> <46CD8BC4.1000904@redhat.com> <46CD8EE1.4010402@it.neclab.eu> Message-ID: <46CD9022.2070708@redhat.com> Falk Zimmermann wrote: > Richard W.M. Jones schrieb: >> Falk Zimmermann wrote: >>> Hi, >>> I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and >>> used virt-manager to configure an F7 and xp guest domain. Whereas I can >>> correctly run the F7 guest, I receive the following message after trying >>> to run the xp guest: >>> >>> (xend.err 'Disk image does not exist: ') >>> >>> Both images reside in the same directory (/var/lib/xen/images) and I >>> have selinux disabled. >>> Any ideas? >> >> Can you try: >> >> virsh dumpxml >> >> (where is the name of the XP guest domain). Then check that the >> disk device shown has the right path. >> >> Rich. >> > Hi Richard, > the entry in the xml file looks fine (at least to me) and the image file > exists: Looks like a bug. Can you post also /var/log/xen/xend.log and /var/log/xen/xend-debug.log. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From zimmermann at it.neclab.eu Thu Aug 23 14:04:20 2007 From: zimmermann at it.neclab.eu (Falk Zimmermann) Date: Thu, 23 Aug 2007 16:04:20 +0200 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CD9022.2070708@redhat.com> References: <46CD7A2A.3010806@it.neclab.eu> <46CD8BC4.1000904@redhat.com> <46CD8EE1.4010402@it.neclab.eu> <46CD9022.2070708@redhat.com> Message-ID: <46CD93E4.7080604@it.neclab.eu> Richard W.M. Jones schrieb: > Falk Zimmermann wrote: >> Richard W.M. Jones schrieb: >>> Falk Zimmermann wrote: >>>> Hi, >>>> I'm running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and >>>> used virt-manager to configure an F7 and xp guest domain. Whereas I >>>> can >>>> correctly run the F7 guest, I receive the following message after >>>> trying >>>> to run the xp guest: >>>> >>>> (xend.err 'Disk image does not exist: ') >>>> >>>> Both images reside in the same directory (/var/lib/xen/images) and I >>>> have selinux disabled. >>>> Any ideas? >>> >>> Can you try: >>> >>> virsh dumpxml >>> >>> (where is the name of the XP guest domain). Then check that >>> the disk device shown has the right path. >>> >>> Rich. >>> >> Hi Richard, >> the entry in the xml file looks fine (at least to me) and the image >> file exists: > > Looks like a bug. Can you post also /var/log/xen/xend.log and > /var/log/xen/xend-debug.log. > > Rich. > Ok, here they come: Xend started at Tue Aug 21 08:57:05 2007. device eth0 already exists; can't create bridge with the same name set hello timer failed: No such file or directory set forward delay failed: No such file or directory set stp status failed: No such file or directory Nothing to flush. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: Running with no password 23/08/2007 11:09:34 Autoprobing TCP port 23/08/2007 11:09:34 Autoprobing selected port 5900 23/08/2007 11:09:35 other clients: 23/08/2007 11:09:35 Client Protocol Version 3.8 23/08/2007 11:09:35 Protocol version sent 3.8, using 3.8 23/08/2007 11:09:35 rfbProcessClientSecurityType: executing handler for type 1 23/08/2007 11:09:35 rfbProcessClientSecurityType: returning securityResult for client rfb versin >= 3. 8 23/08/2007 11:09:35 Pixel format for client 127.0.0.1: 23/08/2007 11:09:35 32 bpp, depth 8, big endian 23/08/2007 11:09:35 true colour: max r 255 g 255 b 255, shift r 24 g 16 b 8 23/08/2007 11:09:35 Enabling NewFBSize protocol extension for client 127.0.0.1 23/08/2007 11:09:35 Using raw encoding for client 127.0.0.1 23/08/2007 11:10:50 Client 127.0.0.1 gone 23/08/2007 11:10:50 Statistics events Transmit/ RawEquiv ( saved) 23/08/2007 11:10:50 FramebufferUpdate : 568 | 0/ 0 ( 0.0%) 23/08/2007 11:10:50 raw : 568 | 175169312/175169312 ( 0.0%) 23/08/2007 11:10:50 TOTALS : 1136 | 175169312/175169312 ( 0.0%) 23/08/2007 11:10:50 Statistics events Received/ RawEquiv ( saved) 23/08/2007 11:10:50 PointerEvent : 22 | 132/ 132 ( 0.0%) 23/08/2007 11:10:50 FramebufferUpdate : 569 | 5690/ 5690 ( 0.0%) 23/08/2007 11:10:50 SetEncodings : 1 | 12/ 12 ( 0.0%) 23/08/2007 11:10:50 SetPixelFormat : 1 | 20/ 20 ( 0.0%) 23/08/2007 11:10:50 TOTALS : 593 | 5854/ 5854 ( 0.0%) Xend started at Thu Aug 23 12:33:50 2007. device eth0 already exists; can't create bridge with the same name set hello timer failed: No such file or directory set forward delay failed: No such file or directory set stp status failed: No such file or directory Nothing to flush. Xend started at Thu Aug 23 13:10:24 2007. device eth0 already exists; can't create bridge with the same name set hello timer failed: No such file or directory set forward delay failed: No such file or directory set stp status failed: No such file or directory Nothing to flush. Running with no password 23/08/2007 13:26:58 Autoprobing TCP port 23/08/2007 13:26:58 Autoprobing selected port 5900 23/08/2007 13:27:00 other clients: 23/08/2007 13:27:00 Client Protocol Version 3.8 23/08/2007 13:27:00 Protocol version sent 3.8, using 3.8 23/08/2007 13:27:00 rfbProcessClientSecurityType: executing handler for type 1 23/08/2007 13:27:00 rfbProcessClientSecurityType: returning securityResult for client rfb versin >= 3. 8 23/08/2007 13:27:00 Pixel format for client 127.0.0.1: 23/08/2007 13:27:00 32 bpp, depth 8, big endian 23/08/2007 13:27:00 true colour: max r 255 g 255 b 255, shift r 24 g 16 b 8 23/08/2007 13:27:00 Enabling NewFBSize protocol extension for client 127.0.0.1 23/08/2007 13:27:00 Using raw encoding for client 127.0.0.1 ==== [2007-08-23 15:37:31 2776] DEBUG (SrvDomain:76) Starting domain xp4 False [2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1463) XendDomainInfo.constructDomain [2007-08-23 15:37:31 2776] DEBUG (balloon:113) Balloon: 7100988 KiB free; need 2048; done. [2007-08-23 15:37:31 2776] DEBUG (XendDomain:443) Adding Domain: 5 [2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1517) XendDomainInfo.initDomain: 5 256 [2007-08-23 15:37:31 2776] DEBUG (image:330) args: boot, val: c [2007-08-23 15:37:31 2776] DEBUG (image:330) args: fda, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: fdb, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: soundhw, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: localtime, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: serial, val: pty [2007-08-23 15:37:31 2776] DEBUG (image:330) args: std-vga, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: isa, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: acpi, val: 1 [2007-08-23 15:37:31 2776] DEBUG (image:330) args: usb, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: usbdevice, val: None [2007-08-23 15:37:31 2776] DEBUG (image:330) args: k, val: None [2007-08-23 15:37:31 2776] ERROR (XendDomainInfo:1584) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1522, in _initDomain self.image = image.create(self, self.info) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 44, in create return findImageHandlerClass(vmConfig)(vm, vmConfig) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 236, in __init__ ImageHandler.__init__(self, vm, vmConfig) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 75, in __init__ self.configure(vmConfig) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 250, in configure self.dmargs = self.parseDeviceModelArgs(vmConfig) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 344, in parseDeviceModelArgs vbdparam) VmError: Disk image does not exist: [2007-08-23 15:37:31 2776] ERROR (XendDomainInfo:416) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 396, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1587, in _initDomain raise exn VmError: Disk image does not exist: [2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1709) XendDomainInfo.destroy: domid=5 [2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1726) XendDomainInfo.destroyDomain(5) [2007-08-23 15:37:31 2776] ERROR (SrvBase:88) Request start failed. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start return self.xd.domain_start(self.dom.getName(), paused) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 994, in domain_start dominfo.start(is_managed = True) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 396, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1587, in _initDomain raise exn VmError: Disk image does not exist: Cheers, Falk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3249 bytes Desc: S/MIME Cryptographic Signature URL: From acathrow at redhat.com Thu Aug 23 15:07:57 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Thu, 23 Aug 2007 11:07:57 -0400 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <46CCEFED.4040401@gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <004a01c7e505$ae721de0$06000100@actius.com> <137a61500708221504g228a3882j397d3a6eee2b266b@mail.gmail.com> <20070823021600.GG18061@redhat.com> <46CCEFED.4040401@gmail.com> Message-ID: <1187881677.3854.1.camel@aic-macbook-fc7> On Wed, 2007-08-22 at 19:24 -0700, David Mueller wrote: > Daniel P. Berrange wrote: > > When connecting with virsh, you need to provide a URI to override the > > default use of Xen. For QEMU/KVM use 'virsh --connect qemu:///system' > > Thanks, that fixed the issue. I'll look at the rest tomorrow and see If > I can get something working. Perhaps a future feature could attempt to > detect whether or not a xen kernel is running and if not, connect to > QEMU/KVM instead? > You could always set the VIRSH_DEFAULT_CONNECT_URI environmental variable. VIRSH_DEFAULT_CONNECT_URI=qemu:///system > - David > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From sonny.sarai at digitaloceanmarketing.com Thu Aug 23 17:06:10 2007 From: sonny.sarai at digitaloceanmarketing.com (Sonny Sarai) Date: Thu, 23 Aug 2007 10:06:10 -0700 Subject: [Fedora-xen] Assistance with Xen 3.1 Message-ID: <46CDBE82.9010406@digitaloceanmarketing.com> Hello, I have Xen server 3.1 running. We installed this into our network before I was hired. We also had a Nat'd IP. The ip address of the base system was the public IP. Due to changing business requirements we needed more IPs. Our ISP gave us a block. I had to change the IP structure for the whole company. I had to change the IP's of the guest VM's (virtual machine) on Xen. The challenge is this. I cannot change the IP of the Xen base system so I can use the xenserver-client to create new vm and add new ones. It seems it is bridged. How can I change the ip address so I can then use the client to do some updates and add new VM. Or..how can I increase the virtual hard drive space on one of my virtual machines. This is just a short term workaround. The challenge of changing the IP address of the base system which is XEN is proving to be difficult. Any help is greatly appreciated. Long live Xen Thank you, Sonny From crobinso at redhat.com Thu Aug 23 17:40:28 2007 From: crobinso at redhat.com (Cole Robinson) Date: Thu, 23 Aug 2007 13:40:28 -0400 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CD8EE1.4010402@it.neclab.eu> References: <46CD7A2A.3010806@it.neclab.eu> <46CD8BC4.1000904@redhat.com> <46CD8EE1.4010402@it.neclab.eu> Message-ID: <46CDC68C.3020107@redhat.com> Falk Zimmermann wrote: > > > > > > This section is what is causing the error. With windows guests, the tools try to do some funky stuff so that windows can still have access to the install cd for the second stage of the install (after the first reboot.) It probably shouldn't be erroring like that so there is a bug somewhere, just not sure where in the chain it is. In the interim, you can get your guest to work with access to your iso image with: - virsh dumpxml > somefile.xml - replace with in the above block in somefile.xml - virsh undefine - virsh define somefile.xml If you don't need access to the iso in the guest, you can go to the details section of the domain in virt-manager and remove hdc, which will get rid of the block of xml without needing to undefine/define. - Cole -- Cole Robinson crobinso at redhat.com From asraikhn at gmail.com Thu Aug 23 19:25:39 2007 From: asraikhn at gmail.com (Asrai khn) Date: Fri, 24 Aug 2007 00:25:39 +0500 Subject: [Fedora-xen] Re: domUs become unaccessible running 2.6.20-1.2962.fc6xen on host In-Reply-To: <5f0f8dba0707120447vee80e29u8a5b007e840c26d9@mail.gmail.com> References: <5f0f8dba0707120447vee80e29u8a5b007e840c26d9@mail.gmail.com> Message-ID: <5f0f8dba0708231225w52157003lafe4477a5babd984@mail.gmail.com> On 7/12/07, Asrai khn wrote: > > Hi, > > We have recently update kernel-xen on all of our hosts (3) and its vms all > running fc6. kernel-xen 2.6.20-1.2962.fc6xen is doing good on two hosts > and all its vms (10), however its giving lot of problem on third host. > > when i reboots the host into latest kernel-xen the domUs become > unaccessible in a while hardly run for 10 minutes, 'xm list' still shows > there status but i can't access it from outside. > > We are using loop back files for domUs File system, for testing i rebooted > host into last working kernel 2.6.20-1.2952.fc6xen and domUs into latest > kernel-xen and its doing pretty good, which mean latest kernel-xen is only > giving problem at host side. > > when running 2.6.20-1.2962 on host it giving this in /var/log/messages > > Jul 12 10:42:45 xxxx kernel: xen_net: Memory squeeze in netback driver. > Jul 12 10:42:50 xxxx kernel: printk: 4 messages suppressed. > Jul 12 10:42:50 xxxx kernel: xen_net: Memory squeeze in netback driver. > Jul 12 10:42:55 xxxx kernel: printk: 4 messages suppressed. (...) Same thing happen again when today i updated host kernel-xen from 2.6.20- 1.2952.fc6xen To 2.6.20-1.2999.fc6xen. It working fine at domUs but when I reboot the domO into 2.6.20-1.2999.fc6xen it start giving these errors in Aug 23 18:41:52 xxxx kernel: printk: 4 messages suppressed. Aug 23 18:41:52 xxxx kernel: xen_net: Memory squeeze in netback driver. Aug 23 18:41:57 xxxxl kernel: printk: 4 messages suppressed. Aug 23 18:41:57 xxxx kernel: xen_net: Memory squeeze in netback driver. Aug 23 18:42:02 xxxxxl kernel: printk: 4 messages suppressed. Aug 23 18:42:02 xxx kernel: xen_net: Memory squeeze in netback driver. and all domUs become unaccessible, in end I have to revert back to 2.6.20- 1.2952.fc6xen at domO (host) :-s Any help in this regard will be highly appreciated. Regards. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsm717 at gmail.com Thu Aug 23 23:17:55 2007 From: dsm717 at gmail.com (David Mueller) Date: Thu, 23 Aug 2007 16:17:55 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <20070823021359.GF18061@redhat.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <20070822220927.GQ18061@redhat.com> <46CCEB47.5060702@gmail.com> <20070823021359.GF18061@redhat.com> Message-ID: <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> I'm making progress, but I've run into a couple issues. I've created the following three xml files for the three networks (I'm only worrying about one of the virtual machines now; once I get it working I should be able to replicate it for the other): emu0 8d18febd-e295-4e67-9373-a8b2a5855e60 emu2 8d18febd-e295-4e67-9373-a8b2a5855e62 emu3 8d18febd-e295-4e67-9373-a8b2a5855e63 emu2 and emu3 networks I didn't assign an IP address to since the host doesn't need one; they will be exclusively for VM to VM communcation. emu0 (and in the future emu1) will be used for communication between host and VM -- each will be a different subnet. And here is the xml dump of the VM, taken while its running: emu0 9b517b2c-b315-62fc-626b-2525e2576217 262144 262144 1 hvm destroy restart destroy /usr/bin/qemu-kvm The first problem is that I can't get the guest VM to communicate with the host. I assign an address to the interface with this command: # /sbin/ifconfig eth0 128.10.0.1/24 up Then I attempt to ping the host, but get an error message Destinamtion Host Unreachable. The same happens if I try to ping the guest from the host. I did notice an additional oddity. While the three interfaces all show their correct MAC addresses in the Hardware tab of the Virtual Machine Details tab, if I run ifconfig within the guest, all three show the same address, 1E:11:11:11:11:12 (which should be eth2's MAC address). - David On 8/22/07, Daniel P. Berrange wrote: > On Wed, Aug 22, 2007 at 07:04:55PM -0700, David Mueller wrote: > > On 8/22/07 Daniel P. Berrange wrote: > > >virt-manager will happily use bridging for KVM guests if you setup > > >your host so that its physical interfaces are part of a bridge. > > > > Actually, that's not quite what I need. The final setup will have two > > guest machines, each with an eth0 to communicate with the Domain 0 host. > > Each also will have a virtual eth1 and and eth2 that is used for > > communication between the two VMs. The virtual machines need to > > commuincate only with each other and the host; they don't actually need > > to connect to the network. Because this will run in an isolated network > > not connected to the Internet, we're not restricted to private address > > space and it would be much more work to remap all the addresses we use > > to be only in private address space. > > Ok, that makes sense. virt-manager restricts you to only allow private > address spaces - we could relax that to a warning. In the mean time you > could use 'virsh net-define' to setup a virtual network using a public > IP address range, and virsh doesn't enforce addresing policy. Use the > take a look at /usr/share/libvirt for an example XML file you can tweak. > For an isolated network, simply remove the tag. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > -=| > From berrange at redhat.com Thu Aug 23 23:22:23 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 24 Aug 2007 00:22:23 +0100 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <20070822220927.GQ18061@redhat.com> <46CCEB47.5060702@gmail.com> <20070823021359.GF18061@redhat.com> <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> Message-ID: <20070823232223.GA12777@redhat.com> On Thu, Aug 23, 2007 at 04:17:55PM -0700, David Mueller wrote: > I'm making progress, but I've run into a couple issues. I've created > the following three xml files for the three networks (I'm only > worrying about one of the virtual machines now; once I get it working > I should be able to replicate it for the other): > > > emu0 > 8d18febd-e295-4e67-9373-a8b2a5855e60 > > > > > > emu2 > 8d18febd-e295-4e67-9373-a8b2a5855e62 > > > > > emu3 > 8d18febd-e295-4e67-9373-a8b2a5855e63 > > > > emu2 and emu3 networks I didn't assign an IP address to since the host > doesn't need one; they will be exclusively for VM to VM communcation. > emu0 (and in the future emu1) will be used for communication between > host and VM -- each will be a different subnet. > > > The first problem is that I can't get the guest VM to communicate with > the host. I assign an address to the interface with this command: > > # /sbin/ifconfig eth0 128.10.0.1/24 up > > Then I attempt to ping the host, but get an error message Destinamtion > Host Unreachable. The same happens if I try to ping the guest from > the host. I suspect this is due to the next problem you mention... > I did notice an additional oddity. While the three interfaces all > show their correct MAC addresses in the Hardware tab of the Virtual > Machine Details tab, if I run ifconfig within the guest, all three > show the same address, 1E:11:11:11:11:12 (which should be eth2's MAC > address). Is this with QEMU, or KVM ? Ie is it running /usr/bin/qemu-kvm, or the regular qemu binary. There was a bug where all NICs got the same MAC address https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247641 IIRC we've only fixed KVM so far. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dsm717 at gmail.com Fri Aug 24 00:30:57 2007 From: dsm717 at gmail.com (David Mueller) Date: Thu, 23 Aug 2007 17:30:57 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <20070823232223.GA12777@redhat.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <20070822220927.GQ18061@redhat.com> <46CCEB47.5060702@gmail.com> <20070823021359.GF18061@redhat.com> <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> <20070823232223.GA12777@redhat.com> Message-ID: <137a61500708231730j5689537dra1a616686425ff17@mail.gmail.com> /usr/bin/qemu-kvm While I'm at it, anyone know how to keep Fedora 7 from trying to do DHCP? It's slowing down the guest VM boot time considerably as it has to wait for DHCP timeout to proceed. Three times since there are three interfaces. The interfaces will have their proper IP addresses assigned later. - David On 8/23/07, Daniel P. Berrange wrote: > On Thu, Aug 23, 2007 at 04:17:55PM -0700, David Mueller wrote: > > I'm making progress, but I've run into a couple issues. I've created > > the following three xml files for the three networks (I'm only > > worrying about one of the virtual machines now; once I get it working > > I should be able to replicate it for the other): > > > > > > emu0 > > 8d18febd-e295-4e67-9373-a8b2a5855e60 > > > > > > > > > > > > emu2 > > 8d18febd-e295-4e67-9373-a8b2a5855e62 > > > > > > > > > > emu3 > > 8d18febd-e295-4e67-9373-a8b2a5855e63 > > > > > > > > emu2 and emu3 networks I didn't assign an IP address to since the host > > doesn't need one; they will be exclusively for VM to VM communcation. > > emu0 (and in the future emu1) will be used for communication between > > host and VM -- each will be a different subnet. > > > > > > The first problem is that I can't get the guest VM to communicate with > > the host. I assign an address to the interface with this command: > > > > # /sbin/ifconfig eth0 128.10.0.1/24 up > > > > Then I attempt to ping the host, but get an error message Destinamtion > > Host Unreachable. The same happens if I try to ping the guest from > > the host. > > I suspect this is due to the next problem you mention... > > > I did notice an additional oddity. While the three interfaces all > > show their correct MAC addresses in the Hardware tab of the Virtual > > Machine Details tab, if I run ifconfig within the guest, all three > > show the same address, 1E:11:11:11:11:12 (which should be eth2's MAC > > address). > > Is this with QEMU, or KVM ? Ie is it running /usr/bin/qemu-kvm, or the > regular qemu binary. There was a bug where all NICs got the same MAC > address > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247641 > > IIRC we've only fixed KVM so far. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > -=| > From zimmermann at it.neclab.eu Fri Aug 24 09:53:43 2007 From: zimmermann at it.neclab.eu (Falk Zimmermann) Date: Fri, 24 Aug 2007 11:53:43 +0200 Subject: [Fedora-xen] Problems running xp guest In-Reply-To: <46CDAA0C.40502@redhat.com> References: <46CD7A2A.3010806@it.neclab.eu> <46CD8BC4.1000904@redhat.com> <46CD8EE1.4010402@it.neclab.eu> <46CDAA0C.40502@redhat.com> Message-ID: <46CEAAA7.4010904@it.neclab.eu> Thanks a lot, this fixed the problem. Cheers, Falk Cole Robinson schrieb: > Falk Zimmermann wrote: > > >> >> >> >> >> >> >> > > This section is what is causing the error. With windows guests, the > tools try to do some funky stuff so that windows can still have access > to the install cd for the second stage of the install (after the first > reboot.) It probably shouldn't be erroring like that so there is a bug > somewhere, just not sure where in the chain it is. > > In the interim, you can get your guest to work with access to your iso > image with: > > - virsh dumpxml > somefile.xml > - replace with in > the above block in somefile.xml > - virsh undefine > - virsh define somefile.xml > > If you don't need access to the iso in the guest, you can go to the > details section of the domain in virt-manager and remove hdc, which will > get rid of the block of xml without needing to undefine/define. > > - Cole > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3249 bytes Desc: S/MIME Cryptographic Signature URL: From fedora.lists at burns.me.uk Sat Aug 25 07:38:24 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 25 Aug 2007 08:38:24 +0100 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: <137a61500708231730j5689537dra1a616686425ff17@mail.gmail.com> References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <20070822220927.GQ18061@redhat.com> <46CCEB47.5060702@gmail.com> <20070823021359.GF18061@redhat.com> <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> <20070823232223.GA12777@redhat.com> <137a61500708231730j5689537dra1a616686425ff17@mail.gmail.com> Message-ID: On 24/08/07, David Mueller wrote: > /usr/bin/qemu-kvm > > While I'm at it, anyone know how to keep Fedora 7 from trying to do > DHCP? It's slowing down the guest VM boot time considerably as it has > to wait for DHCP timeout to proceed. Three times since there are > three interfaces. The interfaces will have their proper IP addresses > assigned later. /etc/sysconfig/networking/devices/ifcfg-eth[012] BOOTPROTO=NONE ? From dsm717 at gmail.com Sat Aug 25 17:36:56 2007 From: dsm717 at gmail.com (David Mueller) Date: Sat, 25 Aug 2007 10:36:56 -0700 Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces In-Reply-To: References: <137a61500708211006q5a8f47f2g44d8f5a00695c1f6@mail.gmail.com> <001001c7e4eb$7d3b8a50$06000100@actius.com> <137a61500708221402r6184f23eh81577f4289779a0c@mail.gmail.com> <20070822220927.GQ18061@redhat.com> <46CCEB47.5060702@gmail.com> <20070823021359.GF18061@redhat.com> <137a61500708231617s14f6e01l37bda2bc8b85e81@mail.gmail.com> <20070823232223.GA12777@redhat.com> <137a61500708231730j5689537dra1a616686425ff17@mail.gmail.com> Message-ID: <46D068B8.9050603@gmail.com> On 8/25/07 Andy Burns wrote: > /etc/sysconfig/networking/devices/ifcfg-eth[012] > BOOTPROTO=NONE Thanks, that seemed to fix it. - David From paul at actionlans.com Sun Aug 26 11:12:49 2007 From: paul at actionlans.com (paul) Date: Sun, 26 Aug 2007 20:42:49 +0930 Subject: [Fedora-xen] fedora4 guest iso Message-ID: <1188126770.4871.3.camel@paul> can you please give me an address where a fedora core 4 xen guest installation iso is. I have a bootable dvd but it does not seem to work properly! From berrange at redhat.com Sun Aug 26 16:23:43 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 26 Aug 2007 17:23:43 +0100 Subject: [Fedora-xen] fedora4 guest iso In-Reply-To: <1188126770.4871.3.camel@paul> References: <1188126770.4871.3.camel@paul> Message-ID: <20070826162343.GB31217@redhat.com> On Sun, Aug 26, 2007 at 08:42:49PM +0930, paul wrote: > can you please give me an address where a fedora core 4 xen guest > installation iso is. I have a bootable dvd but it does not seem to work > properly! Fedora Core 4 did not support Xen as an installation target. We merely provided some add-on packages for a Xen kernel, but these are long since discontinued and won't work with current Xen anyway. Fedora Core 4 has been unsupported for a long time even on bare metal, upgrade to something more recent if you want Xen support, or run FC4 fully-virtualized instead. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From robin-lists at robinbowes.com Wed Aug 29 13:37:29 2007 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 29 Aug 2007 14:37:29 +0100 Subject: [Fedora-xen] FC7 as guest on FC6 dom0? Message-ID: Hi, I have a FC6 machine: Linux wast.sitepen.com 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 18:37:05 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux I have several guests running, including FC6, Windows Server 2003, and CentOS5. I want to install a FC7 guest but when I run the following virt-install command the installation freezes: virt-install --nographics --name=skeggles --file=/dev/vg_guests/lv_skeggles --ram=512 --location=http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ --extra-args="ip=172.29.172.50 netmask=255.255.255.0 gateway=172.29.172.1 dns=192.168.2.203,192.168.2.204 ks=http://dev.robinbowes.com/kickstart/sitepen/skeggles-FC7.cfg" It boots into the FC7 install but only gets as far as: Write protecting the kernel read-only data: 938k Then it hangs. Any idea what's up? R. From berrange at redhat.com Wed Aug 29 14:30:27 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 29 Aug 2007 15:30:27 +0100 Subject: [Fedora-xen] FC7 as guest on FC6 dom0? In-Reply-To: References: Message-ID: <20070829143027.GC4330@redhat.com> On Wed, Aug 29, 2007 at 02:37:29PM +0100, Robin Bowes wrote: > Hi, > > I have a FC6 machine: > > Linux wast.sitepen.com 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 18:37:05 > EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > I have several guests running, including FC6, Windows Server 2003, and > CentOS5. > > I want to install a FC7 guest but when I run the following virt-install > command the installation freezes: > > virt-install --nographics --name=skeggles > --file=/dev/vg_guests/lv_skeggles --ram=512 > --location=http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ > --extra-args="ip=172.29.172.50 netmask=255.255.255.0 > gateway=172.29.172.1 dns=192.168.2.203,192.168.2.204 > ks=http://dev.robinbowes.com/kickstart/sitepen/skeggles-FC7.cfg" > > It boots into the FC7 install but only gets as far as: > > Write protecting the kernel read-only data: 938k > > Then it hangs. It hasn't hung - its merely sending console output somewhere you can't see it. Basically its supposed to send it to both text console (xvc) and the grpahical console, but only sends it to the latter. Since you used --nographics, you thus see nothing. IIRC, you can add this arg to virt-install to workaround it: -x "console=xvc0" Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From robin-lists at robinbowes.com Wed Aug 29 15:12:08 2007 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 29 Aug 2007 16:12:08 +0100 Subject: [Fedora-xen] Re: FC7 as guest on FC6 dom0? In-Reply-To: <20070829143027.GC4330@redhat.com> References: <20070829143027.GC4330@redhat.com> Message-ID: Daniel P. Berrange wrote: > On Wed, Aug 29, 2007 at 02:37:29PM +0100, Robin Bowes wrote: >> It boots into the FC7 install but only gets as far as: >> >> Write protecting the kernel read-only data: 938k >> >> Then it hangs. > > It hasn't hung - its merely sending console output somewhere you can't > see it. Basically its supposed to send it to both text console (xvc) > and the grpahical console, but only sends it to the latter. Since you > used --nographics, you thus see nothing. > > IIRC, you can add this arg to virt-install to workaround it: > > -x "console=xvc0" Ah, OK. Thanks. I'll give that a go. R. From robin-lists at robinbowes.com Wed Aug 29 15:30:10 2007 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 29 Aug 2007 16:30:10 +0100 Subject: [Fedora-xen] Re: FC7 as guest on FC6 dom0? In-Reply-To: <20070829143027.GC4330@redhat.com> References: <20070829143027.GC4330@redhat.com> Message-ID: Daniel P. Berrange wrote: > On Wed, Aug 29, 2007 at 02:37:29PM +0100, Robin Bowes wrote: >> It boots into the FC7 install but only gets as far as: >> >> Write protecting the kernel read-only data: 938k >> >> Then it hangs. > > It hasn't hung - its merely sending console output somewhere you can't > see it. Basically its supposed to send it to both text console (xvc) > and the grpahical console, but only sends it to the latter. Since you > used --nographics, you thus see nothing. > > IIRC, you can add this arg to virt-install to workaround it: > > -x "console=xvc0" OK, I'm now trying the same install on a different FC6 box: Linux slippy.robinbowes.com 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 19:19:04 EDT 2007 i686 i686 i386 GNU/Linux i.e. this is i386 not x86_64 I've used this command to start the install: virt-install --nographics --name=test --file=/dev/vg_host/lv_test --ram=512 --location=http://mirrors.kernel.org/fedora/releases/7/Fedora/i386/os/ --extra-args="ip=192.168.1.110 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.60 ks=http://dev.robinbowes.com/kickstart/misc/test-FC7.cfg console=xvc0" I now get this output: ========================================================= [ INFO: possible irq lock inversion dependency detected ] 2.6.20-2925.9.fc7xen #1 --------------------------------------------------------- loader/206 just changed the state of lock: (&np->rx_lock){-...}, at: [] network_open+0x28/0x83 [xennet] but this lock was taken by another, hard-irq-safe lock in the past: (&np->tx_lock){+...} ... plus a load of further memory information. Installation seems to continue, but then stops. The last output seems to be: eth0: no IPv6 routers present I don't see anything in the logs. Any more ideas? R. From rjones at redhat.com Wed Aug 29 17:03:35 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 29 Aug 2007 18:03:35 +0100 Subject: [Fedora-xen] ANNOUNCE: virt-top 0.3.2.5 released Message-ID: <46D5A6E7.2070608@redhat.com> I'm pleased to announce a new release of virt-top, which is a utility like 'top' that works for virtual machines. Many keys and command line options are the same as for ordinary top. Thanks to all the people who have been playing with it and sending me feedback. This version adds block device and network statistics (if supported by the hypervisor and libvirt). This version also fixes a bug where it would fail silently if unable to contact the hypervisor. Main page: http://et.redhat.com/~rjones/virt-top/ Source and binaries for several architectures available from: http://et.redhat.com/~rjones/virt-top/download.html If you have Fedora 7, this will probably work: yum --enablerepo=development install virt-top Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From achan at jonathan360.com Thu Aug 30 14:57:10 2007 From: achan at jonathan360.com (achan at jonathan360.com) Date: Thu, 30 Aug 2007 10:57:10 -0400 Subject: [Fedora-xen] libvir: Xen error on Guest install - Fedora 6 64-bit Message-ID: <46D6DAC6.7020601@jonathan360.com> I'm having difficulties getting Xen to run on Fedora 6 64-bit. The host system is a dual core opteron server with 1gb of ram. This server does not have X installed and is only reachable via ssh, so any graphical tools can't be used. I have the following installed xen-3.0.3-9 libvirt-0.3.1-1 kernel-xen-2.6.20-1.3001 The xen kernel loads fine: Linux removed.removed.com 2.6.20-1.3001.fc6xen #1 SMP Thu Aug 9 16:18:42 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux and domU is up and running: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 723 2 r----- 30.9 When i use virt-install i get the following virt-install --nographic Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. yes What is the name of your virtual machine? ostrich How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /usr/virtualServers/ostrich.iso How large would you like the disk (/usr/virtualServers/ostrich.iso) to be (in gigabytes)? 4 What is the virtual CD image, CD device or install location? http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID Retrieving file Fedora... 286 kB 00:01 Retrieving file boot.iso. 100% |=========================| 7.8 MB 00:17 libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Creating storage file... 100% |=========================| 4.0 GB 00:00 Creating domain... 0 B 00:01 Domain installation still in progress. You can reconnect to the console to complete the installation process. At this point I get dumped back to a command prompt. If i try to reconnect to the console, I get: xenconsole: Could not read tty from store: No such file or directory I have no idea what to do from this point. I have checked log files however I can't find what's wrong. xend.log shows [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vbd/3/768/hotplug-status. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices irq. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vkbd. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vfb. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices pci. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices ioports. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices tap. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vtpm. [2007-08-30 10:48:31 xend 3449] INFO (XendDomain:370) Domain ostrich (3) unpaused. and the qemu-dm log says domid: 1 qemu: the number of cpus is 1 shared page at pfn:ffff, mfn: 8cef buffered io page at pfn:fffd, mfn: 8cf1 xs_read(): vncpasswd get error. /vm/6416a433-45ac-af5d-5a04-6f23be199dc4/vncpasswd. Could not initialize SDL - exiting I've spent three days with this and I haven't been able to find any help. I've found a lot of hints but nothing has worked. If someone can offer some assistance I'd greatly appreciate it! From achan at jonathan360.com Thu Aug 30 19:07:26 2007 From: achan at jonathan360.com (achan at jonathan360.com) Date: Thu, 30 Aug 2007 15:07:26 -0400 Subject: [Fedora-xen] libvir: Xen error on Guest install - Fedora 6 64-bit In-Reply-To: <46D6DAC6.7020601@jonathan360.com> References: <46D6DAC6.7020601@jonathan360.com> Message-ID: <46D7156E.9030905@jonathan360.com> It appears that HVM does NOT support console. I haven't been able to verifty that though, just from a few obscure posts I've read. achan at jonathan360.com wrote: > I'm having difficulties getting Xen to run on Fedora 6 64-bit. The > host system is a dual core opteron server with 1gb of ram. This > server does not have X installed and is only reachable via ssh, so any > graphical tools can't be used. > > I have the following installed > > xen-3.0.3-9 > libvirt-0.3.1-1 > kernel-xen-2.6.20-1.3001 > > The xen kernel loads fine: > > Linux removed.removed.com 2.6.20-1.3001.fc6xen #1 SMP Thu Aug 9 > 16:18:42 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > and domU is up and running: > > Name ID Mem(MiB) VCPUs State > Time(s) > Domain-0 0 723 2 r----- > 30.9 > > When i use virt-install i get the following > > virt-install --nographic > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes > What is the name of your virtual machine? ostrich > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? > /usr/virtualServers/ostrich.iso > How large would you like the disk (/usr/virtualServers/ostrich.iso) to > be (in gigabytes)? 4 > What is the virtual CD image, CD device or install location? > http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ > > Starting install... > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID > Retrieving file Fedora... 286 kB > 00:01 > Retrieving file boot.iso. 100% |=========================| 7.8 MB > 00:17 > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > Creating storage file... 100% |=========================| 4.0 GB > 00:00 > Creating domain... 0 B > 00:01 > Domain installation still in progress. You can reconnect to > the console to complete the installation process. > > At this point I get dumped back to a command prompt. If i try to > reconnect to the console, I get: > > xenconsole: Could not read tty from store: No such file or directory > > I have no idea what to do from this point. I have checked log files > however I can't find what's wrong. xend.log shows > > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:472) > hotplugStatusCallback /local/domain/0/backend/vbd/3/768/hotplug-status. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:486) > hotplugStatusCallback 1. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices irq. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices vkbd. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices vfb. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices pci. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices ioports. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices tap. > [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for > devices vtpm. > [2007-08-30 10:48:31 xend 3449] INFO (XendDomain:370) Domain ostrich > (3) unpaused. > > and the qemu-dm log says > > domid: 1 > qemu: the number of cpus is 1 > shared page at pfn:ffff, mfn: 8cef > buffered io page at pfn:fffd, mfn: 8cf1 > xs_read(): vncpasswd get error. > /vm/6416a433-45ac-af5d-5a04-6f23be199dc4/vncpasswd. > Could not initialize SDL - exiting > > I've spent three days with this and I haven't been able to find any > help. I've found a lot of hints but nothing has worked. If someone > can offer some assistance I'd greatly appreciate it! > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From dsm717 at gmail.com Thu Aug 30 20:19:34 2007 From: dsm717 at gmail.com (David Mueller) Date: Thu, 30 Aug 2007 13:19:34 -0700 Subject: [Fedora-xen] Possible to skip reboot with virt-install? Message-ID: <137a61500708301319v1fbfc0b5gdb6e86394283df8a@mail.gmail.com> Is it possible to tell virt-install to skip the reboot it does after completing the OS install to a guest? I'm writing some shell scripts to automate creating and running of virtual machines, and the reboot after the install is just slowing things down as I have to wait for it to boot up, then shut it down before I can continue. I'm using a customized Fedora 7 installer creating using Revisor and a kickstart file, so if it's a change I need to do there (thinking perhaps that the command to restart rather than shut down is coming from the guest) I can. I noticed that using virt-manager, when the install finished and I hit restart, the guest simply shut down. - David From berrange at redhat.com Fri Aug 31 16:19:29 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 31 Aug 2007 17:19:29 +0100 Subject: [Fedora-xen] Possible to skip reboot with virt-install? In-Reply-To: <137a61500708301319v1fbfc0b5gdb6e86394283df8a@mail.gmail.com> References: <137a61500708301319v1fbfc0b5gdb6e86394283df8a@mail.gmail.com> Message-ID: <20070831161929.GD14463@redhat.com> On Thu, Aug 30, 2007 at 01:19:34PM -0700, David Mueller wrote: > Is it possible to tell virt-install to skip the reboot it does after > completing the OS install to a guest? I'm writing some shell scripts > to automate creating and running of virtual machines, and the reboot > after the install is just slowing things down as I have to wait for it > to boot up, then shut it down before I can continue. > > I'm using a customized Fedora 7 installer creating using Revisor and a > kickstart file, so if it's a change I need to do there (thinking > perhaps that the command to restart rather than shut down is coming > from the guest) I can. I noticed that using virt-manager, when the > install finished and I hit restart, the guest simply shut down. This capability was supposed to be included in the 0.300.0 release, adding a --noreboot flag. But we screwed up and forgot to push the changeset in question to the upstream repo. I'll add it as a patch to the next Fedora RPM we release. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|