Hi, > -----Original Message----- > From: Andreas Färber [mailto:afaer...@suse.de] > Sent: Monday, May 12, 2014 3:09 PM > To: Gonglei (Arei) > Cc: qemu-devel@nongnu.org > Subject: Re: [Qemu-devel] [Crucial bug] Qemu-2.0.0 do not support virtio-net > hot plug/unplug exceed two times > > Am 06.05.2014 17:02, schrieb Andreas Färber: > > Am 06.05.2014 16:08, schrieb Gonglei (Arei): > >>> -----Original Message----- > >>> From: Andreas Färber [mailto:afaer...@suse.de] > >>> Sent: Tuesday, May 06, 2014 9:58 PM > >>> To: Gonglei (Arei) > >>> Cc: Markus Armbruster; Hani Benhabiles; Peter Maydell; Paolo Bonzini; > >>> Michael S. Tsirkin; qemu-devel@nongnu.org > >>> Subject: Re: [Qemu-devel] [Crucial bug] Qemu-2.0.0 do not support > virtio-net > >>> hot plug/unplug exceed two times > >>> > >>>>> Sounds like the acpiphp kernel module is not loaded inside the guest? > >>>>> > >>>> OMG, thank you so much. Good catch. > >>> > >>> In that case check your /etc/modprobe.conf file in the SLES guest. From > >>> at least SLES 11 SP2 on you should have an entry like this (here SP3): > >>> > >>> alias dmi:bvnQEMU:bvrQEMU:* acpiphp > >>> > >>> The exact values changed between SeaBIOS versions at some point. > >>> > >> Yes, I find the entry in /etc/modprobe.conf file. But I don't understand > >> it: > >> > >> # QEMU/KVM can handle ACPI Hotplugging > >> alias dmi:bvnQEMU:bvrQEMU:* acpiphp > >> > >> Why not the SLSE OS auto load the acpiphp module when it's booting? > > > > This entry is what's supposed to trigger the auto-load on our KVM. :) > > > > Like I said above, it depends on the (Sea)BIOS, and you can verify your > > values by running > > > > udevadm monitor --property > > > > and while it's monitoring, running > > > > udevadm trigger > > > > On a recent QEMU I then see > > > > KERNEL[761.415335] change /devices/virtual/dmi/id (dmi) > > ACTION=change > > DEVPATH=/devices/virtual/dmi/id > > > MODALIAS=dmi:bvnBochs:bvrBochs;bd01/01/2011:svnQEMU:pnStandardPC(i4 > 40FX+PIIX,1996):pvrpc-i440fx-2.0:cvnBochs:ct1:cvr: > > SEQNUM=2896 > > SUBSYSTEM=dmi > > > > So with the SeaBIOS blob from qemu.git, > > > > alias dmi:bvnBochs:bvrBochs:* acpiphp > > > > would be needed. Once you add it to modprobe.conf I would expect the > > next `udevadm trigger` (or reboot) to auto-load the module again. > > SLES 11 SP2 kernels since 2012 > (https://bugzilla.novell.com/show_bug.cgi?id=754391) and SP3 should not > need the modprobe.conf entry for "Bochs", since the DMI match was added > to the module itself. So it sounds as if the kernel package is not > up-to-date? > > If you do see this problem with a fully-updated SLES guest (kernel-* and > module-init-tools packages), please let us know. > My guest os configuration is:
linux-b2ij:~ # rpm -qa|grep kernel kernel-source-3.0.76-0.11.1 linux-kernel-headers-2.6.32-1.13.5 kernel-default-devel-3.0.76-0.11.1 kernel-default-base-3.0.76-0.11.1 kernel-default-3.0.76-0.11.1 kernel-firmware-20110923-0.42.49 linux-b2ij:~ # rpm -qa|grep module libgmodule-2_0-0-2.22.5-0.8.8.1 pam-modules-11-1.22.1 pulseaudio-module-x11-0.9.23-0.7.128 libgmodule-2_0-0-32bit-2.22.5-0.8.8.1 module-init-tools-3.11.1-1.28.5 pam-modules-32bit-11-1.22.1 linux-b2ij:~ # uname -a Linux linux-b2ij 3.0.76-0.11-default #1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990) x86_64 x86_64 x86_64 GNU/Linux linux-b2ij:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 Best regards, -Gonglei
