virt

virt@lists.centos.org

2 participants
1612 discussions

Tips for installing Fedora 10 32bit Xen PV domU/guest on CentOS 5.3 dom0/host
by Pasi Kärkkäinen 24 Mar '09

24 Mar '09

Hello! Xen and related packages (libvirt, virt-install, virt-manager etc) in Upcoming CentOS 5.3 support running and installing Fedora 10 (and Fedora 11) paravirtual domU guest virtual machines. These upstream fixes (new features) make it possible: "RHEL5.3 xen: include support for booting Fedora 10 DomU (i.e. bzImage support)" https://bugzilla.redhat.com/show_bug.cgi?id=457199 "update virtinst to install f10 xen guests" https://bugzilla.redhat.com/show_bug.cgi?id=460585 But beware there's a bug in 32bit x86 Fedora 10 installer (anaconda). It installs wrong kernel to the domU (it should install kernel-PAE but it installs normal kernel), and that will prevent the domU from starting after installation. Xen only supports PAE kernels for 32bit PV guests. It's this bug: "anaconda installs the wrong kernel for i686 xen guests" https://bugzilla.redhat.com/show_bug.cgi?id=470905 It can be "fixed" by using a kickstart file for installation, which forces installation of kernel-PAE instead of normal kernel. Example of such kickstart: http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg Fedora 11 (current rawhide of 2009-03-24) does not have that bug anymore, so paravirtual F11 Xen PV domU installation should work out-of-the-box. I've tested and verified all the above works. Hopefully that helps someone :) -- Pasi

1 0

Re: [CentOS-virt] ConVirt 1.0 released
by jd 23 Mar '09

23 Mar '09

Yes. /Jd --- On Sun, 3/22/09, Hristo Benev <foxb(a)abv.bg> wrote: > From: Hristo Benev <foxb(a)abv.bg> > Subject: Re: [CentOS-virt] ConVirt 1.0 released > To: centos-virt(a)centos.org > Date: Sunday, March 22, 2009, 5:20 AM > > > >Message: 1 > >Date: Fri, 20 Mar 2009 11:04:39 -0700 (PDT) > >From: jd > >Subject: [CentOS-virt] ConVirt 1.0 released. > >To: centos-virt(a)centos.org > >Message-ID: > >Content-Type: text/plain; charset=us-ascii > > > > > >hi > > Just wanted to bring to your > attention the release of ConVirt 1.0. > > http://www.convirture.com/blog/2009/announcements/convirt-goes-10/ > > > >/Jd > > > > > > > > Is that an open source tool? > > >From first look on the site i have the impression that > it is paid tool?! > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-virt >

1 0

Re: [CentOS-virt] ConVirt 1.0 released
by Hristo Benev 22 Mar '09

22 Mar '09

> >Message: 1 >Date: Fri, 20 Mar 2009 11:04:39 -0700 (PDT) >From: jd >Subject: [CentOS-virt] ConVirt 1.0 released. >To: centos-virt(a)centos.org >Message-ID: >Content-Type: text/plain; charset=us-ascii > > >hi > Just wanted to bring to your attention the release of ConVirt 1.0. > http://www.convirture.com/blog/2009/announcements/convirt-goes-10/ > >/Jd > > > Is that an open source tool? >From first look on the site i have the impression that it is paid tool?!

1 0

ConVirt 1.0 released.
by jd 20 Mar '09

20 Mar '09

hi Just wanted to bring to your attention the release of ConVirt 1.0. http://www.convirture.com/blog/2009/announcements/convirt-goes-10/ /Jd

1 0

Windows Server 2008 with the KVM --no-acpi option
by Julez 19 Mar '09

19 Mar '09

KVM version 84 Host OS: Centos version: 2.6.18-92.el5 Guest OS: Windows Server 2008 Web Processor: Intel Xeon L5420 Quad-Core I have installed kvm version 84 from .rpm's on lfarkas.org. Without the --no-acpi option, Windows 2008 boots fine. With the --no-acpi option, the VM displays the following: Windows Boot Manager Windows failed to start... Status 0xc0000225 Info: Windows failed to load because the firmware (BIOS) is not ACPI compatible I heard that for best performance, the -no-acpi option is recommended. Maybe that's only an issue with other versions of Windows/KVM. Can anyone confirm? Assuming -no-acpi is worth persuing, is there a solution? Is it a known issue? I couldn't find many references on the web. I downloaded & compiled the latest kernel version 2.6.28.7 from kernel.org and I think the -no-acpi option worked but I've wiped the machine now so can't confirm. Do I need to install a kernel patch and if so which one? This is the kvm command-line... /usr/bin/qemu-kvm -no-acpi -k en-gb -m 1024 -monitor stdio -usb -usbdevice tablet -net nic,macaddr=52:54:00:12:34:58 -net tap,script=/etc/incharge/qemu-ifup -vnc :1 -hda /media/vm01/vm01-hda.raw -hdb /media/archive/vm01-hdb.raw ...although any variant with -no-acpi fails, including the installing from the .iso... /usr/bin/qemu-kvm -no-acpi -m 1024 -vnc :1 -cdrom "/media/archive/win2008web-trial.iso" -boot d /media/vm01/vm01-hda.raw For anyone else wanting to know how to install KVM version 84, this worked for me: yum remove kvm yum install zlib-devel alsa-lib-devel SDL-devel gnutls-devel dev86 texi2html glibc-devel.i386 rpm -i -v http://www.lfarkas.org/linux/packages/centos/5/x86_64/etherboot-roms-kvm-5.… rpm -i -v http://www.lfarkas.org/linux/packages/centos/5/x86_64/kmod-kvm-84-1.x86_64.… rpm -i -v http://www.lfarkas.org/linux/packages/centos/5/x86_64/kvm-84-1.x86_64.rpm reboot Before I post this solution under my original forum post... http://www.centos.org/modules/newbb/viewtopic.php?topic_id=19034&forum=38 ...is this the recommended method for running KVM 72+? According to this... http://www.linux-kvm.org/page/Guest_Support_Status ...KVM version 72 is required for Windows Server 2008. CentOS ships with KVM 36 and the testing repositories have version 66 - and that's only provided as source: http://dev.centos.org/centos/5/testing/SRPMS/. Maybe the KVM HowTo could be updated for anyone with the misfortune to require Windows Server 2008: http://wiki.centos.org/HowTos/KVM Thanks, Julez

3 2

xen-3.0.3-80.el5
by Shane Goulden 18 Mar '09

18 Mar '09

When will Xen-3.0.3-80.el5 be available for CentOS 5.2? https://rhn.redhat.com/errata/RHBA-2009-0118.html

2 2

VMWare Server 2 USB permissions
by Ted Miller 17 Mar '09

17 Mar '09

I have experienced the problems with trying to use USB in VMWare Server 2.0. I have read in various places that it involves the settings of some permissions in the /proc file system, but most of the information has been of the "check your permissions on /proc/bus/usb", but nothing to tell what they should be, or what the ownership of the "file" should be, or how to keep them set correctly (I believe that Centos "forgets" those permissions every time it is rebooted). Can anyone tell me: What the permission needs to be? Who has to have it? How can I set it automatically? I would prefer to create a group and assign ownership of the "file" to a group (like usbbus), and then assign users to that group as needed. The applications I am needed USB access to are running under desktop OS installs, not servers. Thanks for any help, Ted Miller Indiana, USA

1 0

Xen 3.3.1 on CentOS 5.2 - networking problem with bond
by Chris Brown 13 Mar '09

13 Mar '09

Hi, I'm new to the list and new to Xen, so please be gentle with me! ;-) I've got a CentOS 5.2 x86_64 machine with two interfaces (eth0 and eth1 unsurprisingly) bonded into bond0 in mode 4, and a Cisco switch set up with LACP to suit. I didn't select Xen at install time as I wanted to install Xen 3.3.1 from the gitco repo. After installing and yum updating, I added the gitco repo and gid a groupinstall Virtualization. No problem, Xen 3.3.1 installed on CentOS 5.2 and rebooted OK. I disabled Xen networking, and manually added my own bridge device, br0 and moved my IP address off bond0 and onto br0. I applied the patch from Bugzilla which changes the network startup order so that bond interfaces will join bridges properly. I enabled ip routing. Rebooted again to test, and all works - I can ssh the dom0 on the br0 IP address. I used virt-install to try and install a domu direct from the mirrorservice repo for CentOS 5.2 and the domu is created, console attches and the initrd downloads and runs. Anaconda starts and asks me for language, and IP details. I select manual ipv4 config, no ipv6, enter the ipv4 address I want the domu to have, subnet mask and gateway, and a DNS server address, and select Ok. Anaconda says "Determining host name and domain..." and after a couple of minutes or so, tells me I can ping the address I gave the domu from the dom0 and from the next hop (the default gateway for dom0 and domu - another Linux host acting as a firewall) and I get replies to both. Both see the same MAC address for the dom0 ip address - starting with 00:16:36:xx:xx:xx. On my dom0, if I tcpdump on bond0 for host <domuaddress>, all I see is arp entries - dom0 address asking who has domu address and domu address asking who has gateway address and arp replies. No traffic, even though I can ping the domu from the default gateway (ie outside the physical dom0 host). Any pointers to where I'm going wrong? It's pretty obvious to me that it is a network issue of some kind, I just don't know what... I guess I could try a HVM domu booted from cd-rom with a Knoppix or similar Live CD so I can test networking? Thanks, Chris

1 0

virtualizaton install and xen source compile on CentOS5.2
by mica fang 06 Mar '09

06 Mar '09

*Jerry Amundson* wrote on *Thu Mar 5 19:27:34 UTC 2009* >Otherwise, if you do not need Xen 3.2, just "yum groupinstall Virtualization". Thanks for your advice,i do "yum groupinstall Virtualization". Unfortuanately,when reboot,the system also halted at: ///////////////////////////////////////////////////////////////////////////// Red Hat nash version 5.1.19.6 usb 1-5: device not accepting address 4 ,error -110 usb 1-5: device not accepting address 5, error -110 usb 1-5: device not accepting address 6,error -110 usb 1-5: device not accepting address 7,error -110 ////////////////////////////////////////////////////////////////////////////////

2 1

virtualizaton install and xen source compile on CentOS5.2
by mica fang 06 Mar '09

06 Mar '09

Hi ,Guys I installed CentOS5.2-x86_64 on my Dell PowerEndger 1950 with virtualization component ,when reboot the system halted at: /////////////////////////////////////////////////////////// Red Hat nash version 5.1.19.6 usb 1-5: device not accepting address 4 ,error -110 usb 1-5: device not accepting address 5, error -110 usb 1-5: device not accepting address 6,error -110 usb 1-5: device not accepting address 7,error -110 ///////////////////////////////////////////////////////// I also installed CentOS5.2-x86_64 on the same Dell PowerEndger 1950 without virtualization component,everything work properly. I download the xen-3.3-testing.hg using "hg clone * http://xenbits.xensource.com/xen-3.3-testing.hg"*<http://xenbits.xensource.com/xen-3.3-testing.hg%22>command,then i followed its README : make world make install depmod 2.6.18.8-xen mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod /boot/initrd-2.6.18.8-xen.img 2.6.18.8-xen modify the grub,so that i can boot with xen-dom0 when I reboot with xen-dom0,the system also halted at: /////////////////////////////////////////////////////////// Red Hat nash version 5.1.19.6 usb 1-5: device not accepting address 4 ,error -110 usb 1-5: device not accepting address 5, error -110 usb 1-5: device not accepting address 6,error -110 usb 1-5: device not accepting address 7,error -110 ///////////////////////////////////////////////////////// the following infomation is the out of lspci on my Dell PowerEndger 1950: ////////////////////////////////////////////////////////////////////////////////////////////////// 00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 12) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 12) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 12) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 12) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 12) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12) 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) 00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04) 02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 04:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 04:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 05:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 0e:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Is anybody know why ?

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt