From mboxrd@z Thu Jan 1 00:00:00 1970 From: Farkas Levente Subject: Re: [ANNOUNCE] kvm-52 release Date: Mon, 12 Nov 2007 22:05:50 +0100 Message-ID: <4738C02E.6060708@bppiac.hu> References: <47384377.70004@qumranet.com> <47387146.706@bppiac.hu> <1194882388.3983.4.camel@localhost.localdomain> <47387A44.3090604@bppiac.hu> <1194884867.3161.12.camel@localhost.localdomain> <473883C4.8040405@bppiac.hu> <473888D5.20603@cisco.com> <4738B51C.1080606@bppiac.hu> <4738BA52.1010603@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Avi Kivity To: david ahern Return-path: In-Reply-To: <4738BA52.1010603-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org david ahern wrote: > One of my hosts is a DL380 G5 (Intel(R) Xeon(R) CPU 5140 @ 2.33GHz) with 4GB of RAM. At this time it is running the stock i386 version of RHEL5.1. I am building kvm from the tar balls, currently using kvm-52. > > I have a stock RHEL5 guest (2.6.18-8.el5 kernel) and no added kernel boot options. The qemu command is: > > /usr/local/bin/qemu-system-x86_64 -boot c -localtime -hda images/rhel5.img -m 1536 -smp 4 -net nic,macaddr=00:1a:4b:34:74:52,model=rtl8139 -net tap,ifname=tap0,script=/bin/true -monitor stdio -vnc :2 strange as you state above rhel5.1 i386 how can you run qemu-system-x86_64? 64bit guest are not run on 32bit host (afaik). > Starting with the Avi's patch over the weekend, all of my SMP guests (running stock RHEL 3.8, RHEL 4.4, and RHEL 5.0) now boot just fine. > > > Are you adding any kernel options to the guest boot? If not, try adding 'noapic'. i don't have any kernel option (what's more as you can see from the xml and the command line acpi is enabled for kvm). i'll check 'noapic' on wednesday:-( > While debugging this issue, you might try downloading the kvm tar balls and building/installing from it -- removing the rpms first of course to make sure there are not conflicts -- and running qemu directly rather than through virtmanager. as i build myself the kvm rpm i download and compile them to one the same machine in the x86_64 centos-5 guest. ps. please break lines around 75-80 chars otherwise it's almost unreadable in this case. > david > > > Farkas Levente wrote: >> david ahern wrote: >>> Can you post the full qemu command that gets launched in each case? >> this is the current running one, the only difference when smp set is -smp 4: >> >> root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35 >> /usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda >> /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap >> -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net >> tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0 >> >> root 3299 0.7 6.6 636024 540116 ? Sl 16:20 2:19 >> /usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda >> /dev/VolGroup00/centos-x86_64-root -hdb >> /dev/VolGroup00/centos-x86_64-swap -net >> nic,macaddr=00:16:3e:2e:99:e2,vlan=0 -net tap,fd=14,script=,vlan=0 -usb >> -vnc 127.0.0.1:1 >> >> root 3459 0.4 5.0 639940 410684 ? Sl 16:21 1:23 >> /usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda >> /dev/VolGroup00/mandrake-root -hdb /dev/VolGroup00/mandrake-swap -net >> nic,macaddr=00:16:3e:37:68:fd,vlan=0 -net tap,fd=18,script=,vlan=0 -usb >> -vnc 127.0.0.1:2 -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/