Re: [Xen-API] XCP 1.1 and the DVD CPU Usage Bug in XenServer 5.6

[Dave Scott <Dave.Scott@xxxxxxxxxxxxx>]

Hi,

A simpler solution might be to disable the cdrommon service ('service cdrommon 
stop' and then 'chkconfig --del cdrommon' - I'm not totally sure about the 
command line, it's worth checking the man page)

IIRC cdrommon monitors the states (tray empty, tray full) of the physical CDROM 
drives of the host, passing through state changes to any interested VMs. If you 
aren't using physical CDs from guests then it doesn't perform any useful 
function. If you take a look at the file 'cdrommon.ml' in the github repo, 
you'll see how simple it is.

Cheers,
-- 
Dave Scott

On Jan 21, 2012, at 6:28 PM, "brooks@xxxxxxxxxxx" <brooks@xxxxxxxxxxx> wrote:

> 
> We're seeing the same issue as described in the following post:
> 
>     http://forums.citrix.com/thread.jspa?threadID=266744&start=30&tstart=0
> 
> Basically the CPU load on the servers is extremely high and the cause is 
> the cdrommon proc.
> 
> Citrix released a fix to this problem for XenServer 5.6 here:
> 
>     http://support.citrix.com/article/CTX126919
> 
> But that won't work under XCP 1.1 for obvious reasons (kernel 
> version mismatch).  A couple of questions for any of those of you that may 
> be knowledgeable concerning building kernel drivers under XCP.
> 
> 1. Is there a way to verify that the patch didn't make it into XCP 1.1?
>    The ata_generic module reports that it is version 2.15
> 
> # modinfo ata_generic
> filename:
> /lib/modules/2.6.32.12-0.7.1.xs1.1.0.327.170596xen/kernel/drivers/ata/ata_generic.ko
> version:        0.2.15
> 
> In theory that's the same version that was released as the patched 
> driver.  I definitely have the TEAC CD/DVD drives and I'm definitely 
> hitting the bug so it doesn't look like the patch made it into XCP 1.1.
> 
> # cat /proc/ide/hda/model
> DV-28E-V
> 
> 2. How difficult would it be to recompile the patched driver under XCP?
>    Citrix released the src, including a spec file and a Makefile, to the
>    patch along with the binary.
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api