[ANNOUNCE] kvm-52 release

[ANNOUNCE] kvm-52 release

[Avi Kivity]

Small fixes and updates.

Changes from kvm-51:
- fix efer reload host crash on T2600 and similar processors
- revert sleepy interrupt injection
   - fixes "Fault when IDT_Vectoring"
- atomically inject real-mode interrupts
- wbinvd exiting on newer Intel processors (Eddie Dong)
   - fixes real-time issues
- fix call/jmp instruction emulation (Izik Eidus)
   - fixes Vista x64 installation
- fix save/restore/migrate with multiple nics
- fix build on i386 uniprocessor w/ no ioapic hosts
- fix smp_call_function_single() emulation on older hosts
   - fixes smp guests not booting on RHEL 5 hosts
- make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
   - fixes issues with large memory guests
- libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)

Notes:
      If you use the modules bundled with kvm-52, you can use any version
of Linux from 2.6.9 upwards.
      If you use the modules bundled with Linux 2.6.20, you need to use
kvm-12.
      If you use the modules bundled with Linux 2.6.21, you need to use
kvm-17.
      Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22.  Some features may only be available in newer releases.
      For best performance, use Linux 2.6.23-rc2 or later as the host.

http://kvm.qumranet.com


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

Avi Kivity wrote:
> Small fixes and updates.
> 
> Changes from kvm-51:
> - fix efer reload host crash on T2600 and similar processors
> - revert sleepy interrupt injection
>    - fixes "Fault when IDT_Vectoring"
> - atomically inject real-mode interrupts
> - wbinvd exiting on newer Intel processors (Eddie Dong)
>    - fixes real-time issues
> - fix call/jmp instruction emulation (Izik Eidus)
>    - fixes Vista x64 installation
> - fix save/restore/migrate with multiple nics
> - fix build on i386 uniprocessor w/ no ioapic hosts
> - fix smp_call_function_single() emulation on older hosts
>    - fixes smp guests not booting on RHEL 5 hosts
> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>    - fixes issues with large memory guests
> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)

still not working for us, there is even a small regression.

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).
- centos 64bit guest boot but crash (or at least dump stack strace on
console) the other screenshot.
- winxp guest are hang during boot.
- mandrake 32bit guest are not able to start the kernel.

with single cpu:
- mandrake 32bit guest are hang during boot after a 3th shutdown,
restart finally it's able to boot and run.

setup:
- host:
  - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
  - Intel S3000AHV
  - 8GB RAM
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
  - Mandrake-9
  - kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
  - Windows XP Professional 32bit


-- 
  Levente                               "Si vis pacem para bellum!"

[-- Attachment #2: Screenshot-devel-i386VirtualMachineConsole.png --]
[-- Type: image/png, Size: 27362 bytes --]

[-- Attachment #3: Screenshot-devel-x86-64VirtualMachineConsole.png --]
[-- Type: image/png, Size: 28244 bytes --]

[-- Attachment #4: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #5: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [ANNOUNCE] kvm-52 release

[Alexey Eremenko]

[-- Attachment #1.1: Type: text/plain, Size: 248 bytes --]

Hi Levente !

The only idea that I have for you is to: Try to run KVM on newer kernel. (2.6.21+)

I did all of what you said on Fedora 7/x64 host (2.6.21 default kernel) and it all worked ! (except Mandrake 9.0, which I don't have)

-Alexey

[-- Attachment #1.2: Type: text/html, Size: 654 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [ANNOUNCE] kvm-52 release

[Izik Eidus]

On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
> Avi Kivity wrote:
> > Small fixes and updates.
> > 
> > Changes from kvm-51:
> > - fix efer reload host crash on T2600 and similar processors
> > - revert sleepy interrupt injection
> >    - fixes "Fault when IDT_Vectoring"
> > - atomically inject real-mode interrupts
> > - wbinvd exiting on newer Intel processors (Eddie Dong)
> >    - fixes real-time issues
> > - fix call/jmp instruction emulation (Izik Eidus)
> >    - fixes Vista x64 installation
> > - fix save/restore/migrate with multiple nics
> > - fix build on i386 uniprocessor w/ no ioapic hosts
> > - fix smp_call_function_single() emulation on older hosts
> >    - fixes smp guests not booting on RHEL 5 hosts
> > - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
> >    - fixes issues with large memory guests
> > - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
> 
> still not working for us, there is even a small regression.

wow, what host kernel are you using?
> 
> with smp:
> - centos 32bit guest hang during boot at different places (see screenshot).
work for me (2.6.23.1)

> - centos 64bit guest boot but crash (or at least dump stack strace on
work for me
> console) the other screenshot.
> - winxp guest are hang during boot.
work for me
> 
> setup:
> - host:
>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>   - Intel S3000AHV
>   - 8GB RAM
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
> - guest-1:
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 i386 32bit
> - guest-2:
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
> - guest-3:
>   - Mandrake-9
>   - kernel-2.4.19.16mdk-1-1mdk 32bit
> - guest-4:
>   - Windows XP Professional 32bit
> _


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Alexey Eremenko wrote:
> Hi Levente !
> 
> The only idea that I have for you is to: Try to run KVM on newer kernel.
> (2.6.21+)
> 
> I did all of what you said on Fedora 7/x64 host (2.6.21 default kernel)
> and it all worked ! (except Mandrake 9.0, which I don't have)

that's exactly which i'm not really want!
i really like to keep at a standard distributed upstream patched kernel.
we never would like to use non redhat/centos kernel on servers. we all
have fedora on our workstations, but (probably that's way) we all knows
the stability of these kernels. ok currently kvm also bring the hosts
and the guest to the same level or even worse, but i hope it'd change in
the near feature (the only thing i want a stable smp guest kvm and
probably won't update it for a while).
i can try a fedora kernel just for test but wouldn't like to switch the
whole host os and it's not so trivial to change only the kernel under
redhat/centos (there are udev and other dependencies).

-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[Izik Eidus]

On Mon, 2007-11-12 at 16:48 +0100, Farkas Levente wrote:
> Alexey Eremenko wrote:
> > Hi Levente !
> > 
> > The only idea that I have for you is to: Try to run KVM on newer kernel.
> > (2.6.21+)
> > 
> > I did all of what you said on Fedora 7/x64 host (2.6.21 default kernel)
> > and it all worked ! (except Mandrake 9.0, which I don't have)
> 
> that's exactly which i'm not really want!
> i really like to keep at a standard distributed upstream patched kernel.
> we never would like to use non redhat/centos kernel on servers. we all
> have fedora on our workstations, but (probably that's way) we all knows
> the stability of these kernels. ok currently kvm also bring the hosts
> and the guest to the same level or even worse, but i hope it'd change in
> the near feature (the only thing i want a stable smp guest kvm and
> probably won't update it for a while).
> i can try a fedora kernel just for test but wouldn't like to switch the
> whole host os and it's not so trivial to change only the kernel under
> redhat/centos (there are udev and other dependencies).
> 
you are 100% right!
it should work the same (just little slower) on older kernels
it is a bug that it dont work to you, i just asked you to see if it
related to be beacuse you run on a diffrent kernel than i do,
anyway i will try to check it out on centos 2.6.18 kernel
and we will try to fix it.


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Izik Eidus wrote:
> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>> Avi Kivity wrote:
>>> Small fixes and updates.
>>>
>>> Changes from kvm-51:
>>> - fix efer reload host crash on T2600 and similar processors
>>> - revert sleepy interrupt injection
>>>    - fixes "Fault when IDT_Vectoring"
>>> - atomically inject real-mode interrupts
>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>    - fixes real-time issues
>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>    - fixes Vista x64 installation
>>> - fix save/restore/migrate with multiple nics
>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>> - fix smp_call_function_single() emulation on older hosts
>>>    - fixes smp guests not booting on RHEL 5 hosts
>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>    - fixes issues with large memory guests
>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>> still not working for us, there is even a small regression.
> 
> wow, what host kernel are you using?

see bellow:-)
are you think i manually create the screenshots?:-)?

>> with smp:
>> - centos 32bit guest hang during boot at different places (see screenshot).
> work for me (2.6.23.1)

there is no such kernel for redhat/centos! we use a clean upstream fully
updated centos (ie. the kernel actually 2.6.18-8.1.15:-)

>> - centos 64bit guest boot but crash (or at least dump stack strace on
> work for me
>> console) the other screenshot.
>> - winxp guest are hang during boot.
> work for me
>> setup:
>> - host:
>>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>>   - Intel S3000AHV
>>   - 8GB RAM
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>> - guest-1:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 i386 32bit
>> - guest-2:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>> - guest-3:
>>   - Mandrake-9
>>   - kernel-2.4.19.16mdk-1-1mdk 32bit
>> - guest-4:
>>   - Windows XP Professional 32bit
>> _
> 


-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[Izik Eidus]

On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
> Izik Eidus wrote:
> > On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
> >> Avi Kivity wrote:
> >>> Small fixes and updates.
> >>>
> >>> Changes from kvm-51:
> >>> - fix efer reload host crash on T2600 and similar processors
> >>> - revert sleepy interrupt injection
> >>>    - fixes "Fault when IDT_Vectoring"
> >>> - atomically inject real-mode interrupts
> >>> - wbinvd exiting on newer Intel processors (Eddie Dong)
> >>>    - fixes real-time issues
> >>> - fix call/jmp instruction emulation (Izik Eidus)
> >>>    - fixes Vista x64 installation
> >>> - fix save/restore/migrate with multiple nics
> >>> - fix build on i386 uniprocessor w/ no ioapic hosts
> >>> - fix smp_call_function_single() emulation on older hosts
> >>>    - fixes smp guests not booting on RHEL 5 hosts
> >>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
> >>>    - fixes issues with large memory guests
> >>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
> >> still not working for us, there is even a small regression.
> > 
> > wow, what host kernel are you using?
> 
> see bellow:-)
> are you think i manually create the screenshots?:-)?
> 
> >> with smp:
> >> - centos 32bit guest hang during boot at different places (see screenshot).
> > work for me (2.6.23.1)
> 
> there is no such kernel for redhat/centos! we use a clean upstream fully
> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
> 

ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5 
and ran smp guest, (centos5 64 and winxp32) and it worked for me
you have any idea what i can do to make my system look more like your?
what could be diffrent?


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Izik Eidus wrote:
> On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
>> Izik Eidus wrote:
>>> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>>>> Avi Kivity wrote:
>>>>> Small fixes and updates.
>>>>>
>>>>> Changes from kvm-51:
>>>>> - fix efer reload host crash on T2600 and similar processors
>>>>> - revert sleepy interrupt injection
>>>>>    - fixes "Fault when IDT_Vectoring"
>>>>> - atomically inject real-mode interrupts
>>>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>>>    - fixes real-time issues
>>>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>>>    - fixes Vista x64 installation
>>>>> - fix save/restore/migrate with multiple nics
>>>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>>>> - fix smp_call_function_single() emulation on older hosts
>>>>>    - fixes smp guests not booting on RHEL 5 hosts
>>>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>>>    - fixes issues with large memory guests
>>>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>>>> still not working for us, there is even a small regression.
>>> wow, what host kernel are you using?
>> see bellow:-)
>> are you think i manually create the screenshots?:-)?
>>
>>>> with smp:
>>>> - centos 32bit guest hang during boot at different places (see screenshot).
>>> work for me (2.6.23.1)
>> there is no such kernel for redhat/centos! we use a clean upstream fully
>> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
>>
> 
> ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5 
> and ran smp guest, (centos5 64 and winxp32) and it worked for me
> you have any idea what i can do to make my system look more like your?
> what could be diffrent?

first of all fully update your centos (a bit newer kernel), then i use
these packages:
http://www.lfarkas.org/linux/packages/centos/5/x86_64/
use libvirtd and virt-manager too and start the guests from there. and
start them manually paralell (i used to reboot the host when i update
kvm, the start virt-manager and start each guests). anyway may be a
newer processor generate the same result as ours.
or if you can send me any kind of debug kvm version i can run it which
can print any additional debug messages etc...

i can just repeat my setup:
- host:
  - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
  - Intel S3000AHV
  - 8GB RAM
  - CentOS-5
  - kernel-2.6.18-8.1.15.el5 x86_64 64bit
- guest-1:
  - CentOS-5
  - kernel-2.6.18-8.1.15.el5 i386 32bit
- guest-2:
  - CentOS-5
  - kernel-2.6.18-8.1.15.el5 x86_64 64bit

packages on the host:
# rpm -qa|egrep "virt|vnc|kvm"|sort
gtk-vnc-0.2.0-4
gtk-vnc-python-0.2.0-4
kmod-kvm-52-1.2.6.18_8.1.15.el5
kvm-52-1
libvirt-0.3.3-2
libvirt-python-0.3.3-2
python-virtinst-0.300.1-3
virt-manager-0.5.2-2
virt-top-0.3.2.8-1
virt-viewer-0.0.2-2
vnc-4.1.2-9.el5

the two guest config in libvirtd are the following:
devel-i386.xml:
-------------------------------------------------------------
<domain type='kvm'>
  <name>devel-i386</name>
  <uuid>dee4ab98-363c-649f-4a02-fef25b17756b</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-i386-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-i386-swap'/>
      <target dev='hdb'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/md2'/>
      <target dev='hdc'/>
    </disk>
<!--
    <disk type='block' device='cdrom'>
      <source dev='/dev/hda'/>
      <target dev='hdcd?'/>
      <readonly/>
    </disk>
-->
    <interface type='bridge'>
      <mac address='00:16:3e:58:66:7b'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='127.0.0.1'/>
  </devices>
</domain>
-------------------------------------------------------------
devel-x86-64.xml:
-------------------------------------------------------------
<domain type='kvm'>
  <name>devel-x86-64</name>
  <uuid>9436bef1-aef9-2f5c-21cf-123e300fcd27</uuid>
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-x86_64-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
      <target dev='hdb'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:2e:99:e2'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='127.0.0.1'/>
  </devices>
</domain>
-------------------------------------------------------------


-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[david ahern]

Can you post the full qemu command that gets launched in each case?

david


Farkas Levente wrote:
> Izik Eidus wrote:
>> On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
>>> Izik Eidus wrote:
>>>> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>>>>> Avi Kivity wrote:
>>>>>> Small fixes and updates.
>>>>>>
>>>>>> Changes from kvm-51:
>>>>>> - fix efer reload host crash on T2600 and similar processors
>>>>>> - revert sleepy interrupt injection
>>>>>>    - fixes "Fault when IDT_Vectoring"
>>>>>> - atomically inject real-mode interrupts
>>>>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>>>>    - fixes real-time issues
>>>>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>>>>    - fixes Vista x64 installation
>>>>>> - fix save/restore/migrate with multiple nics
>>>>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>>>>> - fix smp_call_function_single() emulation on older hosts
>>>>>>    - fixes smp guests not booting on RHEL 5 hosts
>>>>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>>>>    - fixes issues with large memory guests
>>>>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>>>>> still not working for us, there is even a small regression.
>>>> wow, what host kernel are you using?
>>> see bellow:-)
>>> are you think i manually create the screenshots?:-)?
>>>
>>>>> with smp:
>>>>> - centos 32bit guest hang during boot at different places (see screenshot).
>>>> work for me (2.6.23.1)
>>> there is no such kernel for redhat/centos! we use a clean upstream fully
>>> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
>>>
>> ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5 
>> and ran smp guest, (centos5 64 and winxp32) and it worked for me
>> you have any idea what i can do to make my system look more like your?
>> what could be diffrent?
> 
> first of all fully update your centos (a bit newer kernel), then i use
> these packages:
> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
> use libvirtd and virt-manager too and start the guests from there. and
> start them manually paralell (i used to reboot the host when i update
> kvm, the start virt-manager and start each guests). anyway may be a
> newer processor generate the same result as ours.
> or if you can send me any kind of debug kvm version i can run it which
> can print any additional debug messages etc...
> 
> i can just repeat my setup:
> - host:
>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>   - Intel S3000AHV
>   - 8GB RAM
>   - CentOS-5
>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
> - guest-1:
>   - CentOS-5
>   - kernel-2.6.18-8.1.15.el5 i386 32bit
> - guest-2:
>   - CentOS-5
>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
> 
> packages on the host:
> # rpm -qa|egrep "virt|vnc|kvm"|sort
> gtk-vnc-0.2.0-4
> gtk-vnc-python-0.2.0-4
> kmod-kvm-52-1.2.6.18_8.1.15.el5
> kvm-52-1
> libvirt-0.3.3-2
> libvirt-python-0.3.3-2
> python-virtinst-0.300.1-3
> virt-manager-0.5.2-2
> virt-top-0.3.2.8-1
> virt-viewer-0.0.2-2
> vnc-4.1.2-9.el5
> 
> the two guest config in libvirtd are the following:
> devel-i386.xml:
> -------------------------------------------------------------
> <domain type='kvm'>
>   <name>devel-i386</name>
>   <uuid>dee4ab98-363c-649f-4a02-fef25b17756b</uuid>
>   <memory>2097152</memory>
>   <currentMemory>2097152</currentMemory>
>   <vcpu>1</vcpu>
>   <os>
>     <type>hvm</type>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>   </features>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>destroy</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-kvm</emulator>
>     <disk type='block' device='disk'>
>       <source dev='/dev/VolGroup00/centos-i386-root'/>
>       <target dev='hda'/>
>     </disk>
>     <disk type='block' device='disk'>
>       <source dev='/dev/VolGroup00/centos-i386-swap'/>
>       <target dev='hdb'/>
>     </disk>
>     <disk type='block' device='disk'>
>       <source dev='/dev/md2'/>
>       <target dev='hdc'/>
>     </disk>
> <!--
>     <disk type='block' device='cdrom'>
>       <source dev='/dev/hda'/>
>       <target dev='hdcd?'/>
>       <readonly/>
>     </disk>
> -->
>     <interface type='bridge'>
>       <mac address='00:16:3e:58:66:7b'/>
>       <source bridge='eth0'/>
>     </interface>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>   </devices>
> </domain>
> -------------------------------------------------------------
> devel-x86-64.xml:
> -------------------------------------------------------------
> <domain type='kvm'>
>   <name>devel-x86-64</name>
>   <uuid>9436bef1-aef9-2f5c-21cf-123e300fcd27</uuid>
>   <memory>524288</memory>
>   <currentMemory>524288</currentMemory>
>   <vcpu>1</vcpu>
>   <os>
>     <type>hvm</type>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>   </features>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>destroy</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-kvm</emulator>
>     <disk type='block' device='disk'>
>       <source dev='/dev/VolGroup00/centos-x86_64-root'/>
>       <target dev='hda'/>
>     </disk>
>     <disk type='block' device='disk'>
>       <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
>       <target dev='hdb'/>
>     </disk>
>     <interface type='bridge'>
>       <mac address='00:16:3e:2e:99:e2'/>
>       <source bridge='eth0'/>
>     </interface>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>   </devices>
> </domain>
> -------------------------------------------------------------
> 
> 

-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Avi Kivity]

Farkas Levente wrote:
> first of all fully update your centos (a bit newer kernel), then i use
> these packages:
> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
> use libvirtd and virt-manager too and start the guests from there. and
> start them manually paralell (i used to reboot the host when i update
> kvm, the start virt-manager and start each guests). 

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is 
running the old userspace.  Can you ensure that you are using the new 
userspace and new kernel modules at all times?

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

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


> david
> 
> 
> Farkas Levente wrote:
>> Izik Eidus wrote:
>>> On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
>>>> Izik Eidus wrote:
>>>>> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>>>>>> Avi Kivity wrote:
>>>>>>> Small fixes and updates.
>>>>>>>
>>>>>>> Changes from kvm-51:
>>>>>>> - fix efer reload host crash on T2600 and similar processors
>>>>>>> - revert sleepy interrupt injection
>>>>>>>    - fixes "Fault when IDT_Vectoring"
>>>>>>> - atomically inject real-mode interrupts
>>>>>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>>>>>    - fixes real-time issues
>>>>>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>>>>>    - fixes Vista x64 installation
>>>>>>> - fix save/restore/migrate with multiple nics
>>>>>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>>>>>> - fix smp_call_function_single() emulation on older hosts
>>>>>>>    - fixes smp guests not booting on RHEL 5 hosts
>>>>>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>>>>>    - fixes issues with large memory guests
>>>>>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>>>>>> still not working for us, there is even a small regression.
>>>>> wow, what host kernel are you using?
>>>> see bellow:-)
>>>> are you think i manually create the screenshots?:-)?
>>>>
>>>>>> with smp:
>>>>>> - centos 32bit guest hang during boot at different places (see screenshot).
>>>>> work for me (2.6.23.1)
>>>> there is no such kernel for redhat/centos! we use a clean upstream fully
>>>> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
>>>>
>>> ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5 
>>> and ran smp guest, (centos5 64 and winxp32) and it worked for me
>>> you have any idea what i can do to make my system look more like your?
>>> what could be diffrent?
>> first of all fully update your centos (a bit newer kernel), then i use
>> these packages:
>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>> use libvirtd and virt-manager too and start the guests from there. and
>> start them manually paralell (i used to reboot the host when i update
>> kvm, the start virt-manager and start each guests). anyway may be a
>> newer processor generate the same result as ours.
>> or if you can send me any kind of debug kvm version i can run it which
>> can print any additional debug messages etc...
>>
>> i can just repeat my setup:
>> - host:
>>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>>   - Intel S3000AHV
>>   - 8GB RAM
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
>> - guest-1:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.15.el5 i386 32bit
>> - guest-2:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
>>
>> packages on the host:
>> # rpm -qa|egrep "virt|vnc|kvm"|sort
>> gtk-vnc-0.2.0-4
>> gtk-vnc-python-0.2.0-4
>> kmod-kvm-52-1.2.6.18_8.1.15.el5
>> kvm-52-1
>> libvirt-0.3.3-2
>> libvirt-python-0.3.3-2
>> python-virtinst-0.300.1-3
>> virt-manager-0.5.2-2
>> virt-top-0.3.2.8-1
>> virt-viewer-0.0.2-2
>> vnc-4.1.2-9.el5
>>
>> the two guest config in libvirtd are the following:
>> devel-i386.xml:
>> -------------------------------------------------------------
>> <domain type='kvm'>
>>   <name>devel-i386</name>
>>   <uuid>dee4ab98-363c-649f-4a02-fef25b17756b</uuid>
>>   <memory>2097152</memory>
>>   <currentMemory>2097152</currentMemory>
>>   <vcpu>1</vcpu>
>>   <os>
>>     <type>hvm</type>
>>     <boot dev='hd'/>
>>   </os>
>>   <features>
>>     <acpi/>
>>   </features>
>>   <clock offset='utc'/>
>>   <on_poweroff>destroy</on_poweroff>
>>   <on_reboot>restart</on_reboot>
>>   <on_crash>destroy</on_crash>
>>   <devices>
>>     <emulator>/usr/bin/qemu-kvm</emulator>
>>     <disk type='block' device='disk'>
>>       <source dev='/dev/VolGroup00/centos-i386-root'/>
>>       <target dev='hda'/>
>>     </disk>
>>     <disk type='block' device='disk'>
>>       <source dev='/dev/VolGroup00/centos-i386-swap'/>
>>       <target dev='hdb'/>
>>     </disk>
>>     <disk type='block' device='disk'>
>>       <source dev='/dev/md2'/>
>>       <target dev='hdc'/>
>>     </disk>
>> <!--
>>     <disk type='block' device='cdrom'>
>>       <source dev='/dev/hda'/>
>>       <target dev='hdcd?'/>
>>       <readonly/>
>>     </disk>
>> -->
>>     <interface type='bridge'>
>>       <mac address='00:16:3e:58:66:7b'/>
>>       <source bridge='eth0'/>
>>     </interface>
>>     <input type='mouse' bus='ps2'/>
>>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>>   </devices>
>> </domain>
>> -------------------------------------------------------------
>> devel-x86-64.xml:
>> -------------------------------------------------------------
>> <domain type='kvm'>
>>   <name>devel-x86-64</name>
>>   <uuid>9436bef1-aef9-2f5c-21cf-123e300fcd27</uuid>
>>   <memory>524288</memory>
>>   <currentMemory>524288</currentMemory>
>>   <vcpu>1</vcpu>
>>   <os>
>>     <type>hvm</type>
>>     <boot dev='hd'/>
>>   </os>
>>   <features>
>>     <acpi/>
>>   </features>
>>   <clock offset='utc'/>
>>   <on_poweroff>destroy</on_poweroff>
>>   <on_reboot>restart</on_reboot>
>>   <on_crash>destroy</on_crash>
>>   <devices>
>>     <emulator>/usr/bin/qemu-kvm</emulator>
>>     <disk type='block' device='disk'>
>>       <source dev='/dev/VolGroup00/centos-x86_64-root'/>
>>       <target dev='hda'/>
>>     </disk>
>>     <disk type='block' device='disk'>
>>       <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
>>       <target dev='hdb'/>
>>     </disk>
>>     <interface type='bridge'>
>>       <mac address='00:16:3e:2e:99:e2'/>
>>       <source bridge='eth0'/>
>>     </interface>
>>     <input type='mouse' bus='ps2'/>
>>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>>   </devices>
>> </domain>
>> -------------------------------------------------------------
>>
>>


-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
>> first of all fully update your centos (a bit newer kernel), then i use
>> these packages:
>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>> use libvirtd and virt-manager too and start the guests from there. and
>> start them manually paralell (i used to reboot the host when i update
>> kvm, the start virt-manager and start each guests). 
> 
> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
> running the old userspace.  Can you ensure that you are using the new
> userspace and new kernel modules at all times?

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
the host (just to be sure).

-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[david ahern]

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

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'. 

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.

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
> 
> 
>> david
>>
>>
>> Farkas Levente wrote:
>>> Izik Eidus wrote:
>>>> On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
>>>>> Izik Eidus wrote:
>>>>>> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>>>>>>> Avi Kivity wrote:
>>>>>>>> Small fixes and updates.
>>>>>>>>
>>>>>>>> Changes from kvm-51:
>>>>>>>> - fix efer reload host crash on T2600 and similar processors
>>>>>>>> - revert sleepy interrupt injection
>>>>>>>>    - fixes "Fault when IDT_Vectoring"
>>>>>>>> - atomically inject real-mode interrupts
>>>>>>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>>>>>>    - fixes real-time issues
>>>>>>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>>>>>>    - fixes Vista x64 installation
>>>>>>>> - fix save/restore/migrate with multiple nics
>>>>>>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>>>>>>> - fix smp_call_function_single() emulation on older hosts
>>>>>>>>    - fixes smp guests not booting on RHEL 5 hosts
>>>>>>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>>>>>>    - fixes issues with large memory guests
>>>>>>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>>>>>>> still not working for us, there is even a small regression.
>>>>>> wow, what host kernel are you using?
>>>>> see bellow:-)
>>>>> are you think i manually create the screenshots?:-)?
>>>>>
>>>>>>> with smp:
>>>>>>> - centos 32bit guest hang during boot at different places (see screenshot).
>>>>>> work for me (2.6.23.1)
>>>>> there is no such kernel for redhat/centos! we use a clean upstream fully
>>>>> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
>>>>>
>>>> ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5 
>>>> and ran smp guest, (centos5 64 and winxp32) and it worked for me
>>>> you have any idea what i can do to make my system look more like your?
>>>> what could be diffrent?
>>> first of all fully update your centos (a bit newer kernel), then i use
>>> these packages:
>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>>> use libvirtd and virt-manager too and start the guests from there. and
>>> start them manually paralell (i used to reboot the host when i update
>>> kvm, the start virt-manager and start each guests). anyway may be a
>>> newer processor generate the same result as ours.
>>> or if you can send me any kind of debug kvm version i can run it which
>>> can print any additional debug messages etc...
>>>
>>> i can just repeat my setup:
>>> - host:
>>>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>>>   - Intel S3000AHV
>>>   - 8GB RAM
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
>>> - guest-1:
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.15.el5 i386 32bit
>>> - guest-2:
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.15.el5 x86_64 64bit
>>>
>>> packages on the host:
>>> # rpm -qa|egrep "virt|vnc|kvm"|sort
>>> gtk-vnc-0.2.0-4
>>> gtk-vnc-python-0.2.0-4
>>> kmod-kvm-52-1.2.6.18_8.1.15.el5
>>> kvm-52-1
>>> libvirt-0.3.3-2
>>> libvirt-python-0.3.3-2
>>> python-virtinst-0.300.1-3
>>> virt-manager-0.5.2-2
>>> virt-top-0.3.2.8-1
>>> virt-viewer-0.0.2-2
>>> vnc-4.1.2-9.el5
>>>
>>> the two guest config in libvirtd are the following:
>>> devel-i386.xml:
>>> -------------------------------------------------------------
>>> <domain type='kvm'>
>>>   <name>devel-i386</name>
>>>   <uuid>dee4ab98-363c-649f-4a02-fef25b17756b</uuid>
>>>   <memory>2097152</memory>
>>>   <currentMemory>2097152</currentMemory>
>>>   <vcpu>1</vcpu>
>>>   <os>
>>>     <type>hvm</type>
>>>     <boot dev='hd'/>
>>>   </os>
>>>   <features>
>>>     <acpi/>
>>>   </features>
>>>   <clock offset='utc'/>
>>>   <on_poweroff>destroy</on_poweroff>
>>>   <on_reboot>restart</on_reboot>
>>>   <on_crash>destroy</on_crash>
>>>   <devices>
>>>     <emulator>/usr/bin/qemu-kvm</emulator>
>>>     <disk type='block' device='disk'>
>>>       <source dev='/dev/VolGroup00/centos-i386-root'/>
>>>       <target dev='hda'/>
>>>     </disk>
>>>     <disk type='block' device='disk'>
>>>       <source dev='/dev/VolGroup00/centos-i386-swap'/>
>>>       <target dev='hdb'/>
>>>     </disk>
>>>     <disk type='block' device='disk'>
>>>       <source dev='/dev/md2'/>
>>>       <target dev='hdc'/>
>>>     </disk>
>>> <!--
>>>     <disk type='block' device='cdrom'>
>>>       <source dev='/dev/hda'/>
>>>       <target dev='hdcd?'/>
>>>       <readonly/>
>>>     </disk>
>>> -->
>>>     <interface type='bridge'>
>>>       <mac address='00:16:3e:58:66:7b'/>
>>>       <source bridge='eth0'/>
>>>     </interface>
>>>     <input type='mouse' bus='ps2'/>
>>>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>>>   </devices>
>>> </domain>
>>> -------------------------------------------------------------
>>> devel-x86-64.xml:
>>> -------------------------------------------------------------
>>> <domain type='kvm'>
>>>   <name>devel-x86-64</name>
>>>   <uuid>9436bef1-aef9-2f5c-21cf-123e300fcd27</uuid>
>>>   <memory>524288</memory>
>>>   <currentMemory>524288</currentMemory>
>>>   <vcpu>1</vcpu>
>>>   <os>
>>>     <type>hvm</type>
>>>     <boot dev='hd'/>
>>>   </os>
>>>   <features>
>>>     <acpi/>
>>>   </features>
>>>   <clock offset='utc'/>
>>>   <on_poweroff>destroy</on_poweroff>
>>>   <on_reboot>restart</on_reboot>
>>>   <on_crash>destroy</on_crash>
>>>   <devices>
>>>     <emulator>/usr/bin/qemu-kvm</emulator>
>>>     <disk type='block' device='disk'>
>>>       <source dev='/dev/VolGroup00/centos-x86_64-root'/>
>>>       <target dev='hda'/>
>>>     </disk>
>>>     <disk type='block' device='disk'>
>>>       <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
>>>       <target dev='hdb'/>
>>>     </disk>
>>>     <interface type='bridge'>
>>>       <mac address='00:16:3e:2e:99:e2'/>
>>>       <source bridge='eth0'/>
>>>     </interface>
>>>     <input type='mouse' bus='ps2'/>
>>>     <graphics type='vnc' port='-1' listen='127.0.0.1'/>
>>>   </devices>
>>> </domain>
>>> -------------------------------------------------------------
>>>
>>>
> 
> 

-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

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/

Re: [ANNOUNCE] kvm-52 release

[Avi Kivity]

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
>
>   

Well, you're not running kvm-52 userspace then.  You're running Fedora's
kvm package (unless you renamed /usr/local/bin/qemu-system-x86_64 to
/usr/bin/qemu-kvm).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Farkas Levente wrote:
>>     
>>> first of all fully update your centos (a bit newer kernel), then i use
>>> these packages:
>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>>> use libvirtd and virt-manager too and start the guests from there. and
>>> start them manually paralell (i used to reboot the host when i update
>>> kvm, the start virt-manager and start each guests). 
>>>       
>> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
>> running the old userspace.  Can you ensure that you are using the new
>> userspace and new kernel modules at all times?
>>     
>
> yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
> the host (just to be sure).
>
>   

Installing the files means nothing.  You also need to make sure all your
tools use the right binaries (or use the command line directly).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Avi Kivity wrote:
> 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
>>
>>   
> 
> Well, you're not running kvm-52 userspace then.  You're running Fedora's
> kvm package (unless you renamed /usr/local/bin/qemu-system-x86_64 to
> /usr/bin/qemu-kvm).

i running kvm-52 userspace. i build the rpm based on centos and fedora
spec file (which eventually rename it to  qemu-kvm). belive me these rpm
are the latest compiled by myself from the latest kvm-52.tar.gz on a
fully updated centos x86_64.
is there any way how can i prove it? may be a command line option for
qemu -version would be useful.

anyway how should i've test noapic? qemu command line -noapic or guest
kernel param noapic or both?

-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> 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
>>>
>>>   
>>>       
>> Well, you're not running kvm-52 userspace then.  You're running Fedora's
>> kvm package (unless you renamed /usr/local/bin/qemu-system-x86_64 to
>> /usr/bin/qemu-kvm).
>>     
>
> i running kvm-52 userspace. i build the rpm based on centos and fedora
> spec file (which eventually rename it to  qemu-kvm). belive me these rpm
> are the latest compiled by myself from the latest kvm-52.tar.gz on a
> fully updated centos x86_64.
>   

Ah, okay.

> is there any way how can i prove it? may be a command line option for
> qemu -version would be useful.
>
>   

Checking the file date should be enough.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>   
>>> Farkas Levente wrote:
>>>     
>>>> first of all fully update your centos (a bit newer kernel), then i use
>>>> these packages:
>>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>>>> use libvirtd and virt-manager too and start the guests from there. and
>>>> start them manually paralell (i used to reboot the host when i update
>>>> kvm, the start virt-manager and start each guests). 
>>>>       
>>> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
>>> running the old userspace.  Can you ensure that you are using the new
>>> userspace and new kernel modules at all times?
>>>     
>> yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
>> the host (just to be sure).
>>
>>   
> 
> Installing the files means nothing.  You also need to make sure all your
> tools use the right binaries (or use the command line directly).

ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0
(not rhel3) i do know how to install and use packages and which files
are called. there is no any other kvm in the given machine. ok i
understand that you try to find some kind of reason why it's works for
you and not for me but that's not the reason.
anyway it'd be useful to if i can see which version of the userspace
running ie. give a short message into the stslog on the host about the
userspace version may be even a warning in case of the kmod and the
userspace version are different, but currently that's all:
------------------------------------
[root@kvm ~]# rpm -qa|grep kvm
kmod-kvm-52-1.2.6.18_8.1.15.el5
kvm-52-1
[root@kvm ~]# rpm -qf /usr/bin/qemu-kvm
kvm-52-1
[root@kvm ~]# rpm -V kvm-52-1
[root@kvm ~]# modinfo kvm_intel
filename:       /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
license:        GPL
author:         Qumranet
version:        kvm-52
srcversion:     F7E80D6C3124584F75EDAAF
depends:        kvm
vermagic:       2.6.18-8.1.15.el5 SMP mod_unload gcc-4.1
parm:           bypass_guest_pf:bool
------------------------------------
what the above means?
- there is only these two packages installed which has the kmv in it's name.
- the files /usr/bin/qemu-kvm is owned by kvm-52-1.
- all files in the kvm-52-1 package is verified so the file
/usr/bin/qemu-kvm also has the right checksum so it's really from kvm-52-1.
- the kernel module can show it's version too.
anyway if you don't believe me just grab src.rpm look into it or
recompile it:
http://www.lfarkas.org/linux/packages/centos/5/SRPMS/

-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 2769 bytes --]

Hi Levente,

Le mardi 13 novembre 2007 à 10:07 +0100, Farkas Levente a écrit :
> Avi Kivity wrote:
> > Farkas Levente wrote:
> >> Avi Kivity wrote:
> >>   
> >>> Farkas Levente wrote:
> >>>     
> >>>> first of all fully update your centos (a bit newer kernel), then i use
> >>>> these packages:
> >>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
> >>>> use libvirtd and virt-manager too and start the guests from there. and
> >>>> start them manually paralell (i used to reboot the host when i update
> >>>> kvm, the start virt-manager and start each guests). 
> >>>>       
> >>> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
> >>> running the old userspace.  Can you ensure that you are using the new
> >>> userspace and new kernel modules at all times?
> >>>     
> >> yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
> >> the host (just to be sure).
> >>
> >>   
> > 
> > Installing the files means nothing.  You also need to make sure all your
> > tools use the right binaries (or use the command line directly).
> 
> ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0
> (not rhel3) i do know how to install and use packages and which files
> are called. there is no any other kvm in the given machine. ok i
> understand that you try to find some kind of reason why it's works for
> you and not for me but that's not the reason.
> anyway it'd be useful to if i can see which version of the userspace
> running ie. give a short message into the stslog on the host about the
> userspace version may be even a warning in case of the kmod and the
> userspace version are different, but currently that's all:
> ------------------------------------
> [root@kvm ~]# rpm -qa|grep kvm
> kmod-kvm-52-1.2.6.18_8.1.15.el5
> kvm-52-1
> [root@kvm ~]# rpm -qf /usr/bin/qemu-kvm
> kvm-52-1
> [root@kvm ~]# rpm -V kvm-52-1
> [root@kvm ~]# modinfo kvm_intel
> filename:       /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
> license:        GPL
> author:         Qumranet
> version:        kvm-52
> srcversion:     F7E80D6C3124584F75EDAAF
> depends:        kvm
> vermagic:       2.6.18-8.1.15.el5 SMP mod_unload gcc-4.1
> parm:           bypass_guest_pf:bool
[snip]

perhaps you can try:

- "rpm -ql kvm-52-1"
- "rpm -qf /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko"
- "find /lib/modules -name kvm.ko"
- "find /lib/modules -name kvm-intel.ko"
- "type qemu-kvm"

Just to be sure there is no garbage on your system...

Regards,
Laurent
-- 
------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  --------------
       "Any sufficiently advanced technology is
  indistinguishable from magic." - Arthur C. Clarke

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [ANNOUNCE] kvm-52 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Farkas Levente wrote:
>>     
>>> Avi Kivity wrote:
>>>   
>>>       
>>>> Farkas Levente wrote:
>>>>     
>>>>         
>>>>> first of all fully update your centos (a bit newer kernel), then i use
>>>>> these packages:
>>>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>>>>> use libvirtd and virt-manager too and start the guests from there. and
>>>>> start them manually paralell (i used to reboot the host when i update
>>>>> kvm, the start virt-manager and start each guests). 
>>>>>       
>>>>>           
>>>> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
>>>> running the old userspace.  Can you ensure that you are using the new
>>>> userspace and new kernel modules at all times?
>>>>     
>>>>         
>>> yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
>>> the host (just to be sure).
>>>
>>>   
>>>       
>> Installing the files means nothing.  You also need to make sure all your
>> tools use the right binaries (or use the command line directly).
>>     
>
> ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0
> (not rhel3) i do know how to install and use packages and which files
> are called. there is no any other kvm in the given machine. ok i
> understand that you try to find some kind of reason why it's works for
> you and not for me but that's not the reason.
>   

Sure, I'd rather find out it's a configuration problem before I spend 
time debugging it rather than after, especially after other users 
reported success.

> anyway it'd be useful to if i can see which version of the userspace
> running ie. give a short message into the stslog on the host about the
> userspace version may be even a warning in case of the kmod and the
> userspace version are different, but currently that's all:
>   

kvm is designed to support mismatched kernel/userspace versions, so 
that's inappropriate for production.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Laurent Vivier wrote:
> Hi Levente,
> 
> Le mardi 13 novembre 2007 à 10:07 +0100, Farkas Levente a écrit :
>> Avi Kivity wrote:
>>> Farkas Levente wrote:
>>>> Avi Kivity wrote:
>>>>   
>>>>> Farkas Levente wrote:
>>>>>     
>>>>>> first of all fully update your centos (a bit newer kernel), then i use
>>>>>> these packages:
>>>>>> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
>>>>>> use libvirtd and virt-manager too and start the guests from there. and
>>>>>> start them manually paralell (i used to reboot the host when i update
>>>>>> kvm, the start virt-manager and start each guests). 
>>>>>>       
>>>>> IIRC virt-manager uses /usr/bin/kvm as its qemu launcher.  Maybe it is
>>>>> running the old userspace.  Can you ensure that you are using the new
>>>>> userspace and new kernel modules at all times?
>>>>>     
>>>> yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot
>>>> the host (just to be sure).
>>>>
>>>>   
>>> Installing the files means nothing.  You also need to make sure all your
>>> tools use the right binaries (or use the command line directly).
>> ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0
>> (not rhel3) i do know how to install and use packages and which files
>> are called. there is no any other kvm in the given machine. ok i
>> understand that you try to find some kind of reason why it's works for
>> you and not for me but that's not the reason.
>> anyway it'd be useful to if i can see which version of the userspace
>> running ie. give a short message into the stslog on the host about the
>> userspace version may be even a warning in case of the kmod and the
>> userspace version are different, but currently that's all:
>> ------------------------------------
>> [root@kvm ~]# rpm -qa|grep kvm
>> kmod-kvm-52-1.2.6.18_8.1.15.el5
>> kvm-52-1
>> [root@kvm ~]# rpm -qf /usr/bin/qemu-kvm
>> kvm-52-1
>> [root@kvm ~]# rpm -V kvm-52-1
>> [root@kvm ~]# modinfo kvm_intel
>> filename:       /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
>> license:        GPL
>> author:         Qumranet
>> version:        kvm-52
>> srcversion:     F7E80D6C3124584F75EDAAF
>> depends:        kvm
>> vermagic:       2.6.18-8.1.15.el5 SMP mod_unload gcc-4.1
>> parm:           bypass_guest_pf:bool
> [snip]
> 
> perhaps you can try:
> 
> - "rpm -ql kvm-52-1"
> - "rpm -qf /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko"
> - "find /lib/modules -name kvm.ko"
> - "find /lib/modules -name kvm-intel.ko"
> - "type qemu-kvm"
> 
> Just to be sure there is no garbage on your system...

[root@kvm ~]# rpm -ql kvm-52-1
/etc/sysconfig/modules/kvm.modules
/usr/bin/qemu-kvm
/usr/share/man/man1/qemu-kvm.1.gz
/usr/share/qemu
/usr/share/qemu/bios.bin
/usr/share/qemu/keymaps
/usr/share/qemu/keymaps/ar
/usr/share/qemu/keymaps/common
/usr/share/qemu/keymaps/da
/usr/share/qemu/keymaps/de
/usr/share/qemu/keymaps/de-ch
/usr/share/qemu/keymaps/en-gb
/usr/share/qemu/keymaps/en-us
/usr/share/qemu/keymaps/es
/usr/share/qemu/keymaps/et
/usr/share/qemu/keymaps/fi
/usr/share/qemu/keymaps/fo
/usr/share/qemu/keymaps/fr
/usr/share/qemu/keymaps/fr-be
/usr/share/qemu/keymaps/fr-ca
/usr/share/qemu/keymaps/fr-ch
/usr/share/qemu/keymaps/hr
/usr/share/qemu/keymaps/hu
/usr/share/qemu/keymaps/is
/usr/share/qemu/keymaps/it
/usr/share/qemu/keymaps/ja
/usr/share/qemu/keymaps/lt
/usr/share/qemu/keymaps/lv
/usr/share/qemu/keymaps/mk
/usr/share/qemu/keymaps/modifiers
/usr/share/qemu/keymaps/nl
/usr/share/qemu/keymaps/nl-be
/usr/share/qemu/keymaps/no
/usr/share/qemu/keymaps/pl
/usr/share/qemu/keymaps/pt
/usr/share/qemu/keymaps/pt-br
/usr/share/qemu/keymaps/ru
/usr/share/qemu/keymaps/sl
/usr/share/qemu/keymaps/sv
/usr/share/qemu/keymaps/th
/usr/share/qemu/keymaps/tr
/usr/share/qemu/openbios-sparc32
/usr/share/qemu/ppc_rom.bin
/usr/share/qemu/pxe-ne2k_pci.bin
/usr/share/qemu/pxe-pcnet.bin
/usr/share/qemu/pxe-rtl8139.bin
/usr/share/qemu/vgabios-cirrus.bin
/usr/share/qemu/vgabios.bin
/usr/share/qemu/video.x
[root@kvm ~]# rpm -qf /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
kmod-kvm-52-1.2.6.18_8.1.15.el5
[root@kvm ~]# find /lib/modules -name kvm.ko
/lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm.ko
[root@kvm ~]# find /lib/modules -name kvm-intel.ko
/lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
[root@kvm ~]# type qemu-kvm
qemu-kvm is /usr/bin/qemu-kvm


-- 
  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/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

Avi Kivity wrote:
>> anyway it'd be useful to if i can see which version of the userspace
>> running ie. give a short message into the stslog on the host about the
>> userspace version may be even a warning in case of the kmod and the
>> userspace version are different, but currently that's all:
>>   
> 
> kvm is designed to support mismatched kernel/userspace versions, so
> that's inappropriate for production.

that's why is wrote just log it or write a warning messages to the syslog.


-- 
  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/

Re: [ANNOUNCE] kvm-52 release

[david ahern]

Farkas Levente wrote:
> anyway how should i've test noapic? qemu command line -noapic or guest
> kernel param noapic or both?
> 

Add 'noapic' to guest kernel boot options. I've been adding it for a while to workaround a networking issue (see kvm-Bugs-1802082).

david

-------------------------------------------------------------------------
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/

Re: [ANNOUNCE] kvm-52 release

[Farkas Levente]

david ahern wrote:
> Farkas Levente wrote:
>> anyway how should i've test noapic? qemu command line -noapic or guest
>> kernel param noapic or both?
>>
> 
> Add 'noapic' to guest kernel boot options. I've been adding it for a while to workaround a networking issue (see kvm-Bugs-1802082).

i know try with noapic kernel param (everything is a fully updated
centos-5). x86_64 guest on x86_64 boot and run, but i386 guest on x86_64
host hang during boot at the usual place udev. what's more mandrake-9
guest are not able to boot (hang during kernel load) with single cpu
about 5 times when finally able to boot.
there was no any kind of stack trace in any of the above case.

-- 
  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/