Re: [Xen-devel] blktap2 problem with pvops kernel 2.6.32.13 and xen 4.0-rc1

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Fri, May 28, 2010 at 04:27:33AM -0700, Fantu wrote:
> 
> thanks for reply
> 
> About blktap i not uderstand, always this error:
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:790: blktapctrl:
> v1.0.0
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [raw image (aio)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [raw image (sync)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [vmware image (vmdk)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [ramdisk image (ram)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [qcow disk (qcow)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:792: Found driver:
> [qcow2 disk (qcow2)]
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl_linux.c:92: couldn't
> find device number for 'blktap0'
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:859: couldn't open
> blktap interface
> May 28 12:05:56 cpmcOR01AV BLKTAPCTRL[2775]: blktapctrl.c:922: Unable to
> start blktapctrl
> 
> But module there is in kernel and is load (see lsmod) i have try also xen
> 3.4.3, kernel 2.6.31 and 2.6.32 with some different config, always with
> blktap option, also with =y and also try with sysfs deprecated option but
> always nothing
> 

Hmm.. are you really running Xen 4.0.0-rc1 ? If yes, then you should definitely 
upgrade to Xen 4.0.0 final, or even better, to Xen 4.0.1-rc1.

There was some dom0 memory corruption bug fixed around Xen 4.0.0-rc6.

About your blktap2 problems.. dunno really. I'll try it myself some day and
let's see how it goes.

-- Pasi

> I found also 1 problem on save of 1 domU and some of this line in log:
> May 28 12:55:35 cpmcOR01AV kernel: [ 3000.882349] hrtimer: interrupt took
> 4279522 ns
> 
> Here the syslog and kern.log if can help: 
> http://old.nabble.com/file/p28705622/kern.log kern.log  
> http://old.nabble.com/file/p28705622/syslog syslog 
> And xend.log when stop some minute for problem on one domU save: 
> http://old.nabble.com/file/p28705622/xend.log xend.log 
> 
> 
> Pasi Kärkkäinen wrote:
> > 
> > On Fri, May 28, 2010 at 02:45:04AM -0700, Fantu wrote:
> >> 
> >> Server is Dell T610 with last bios (2.0.13)
> >> Dom0: Lenny 64 bit, kernel 2.6.32.13, xen 4.0-rc1
> >> Kernel is last commit of jeremy git xen/stable-2.6.32.x with this config: 
> >> http://old.nabble.com/file/p28704783/config-2.6.32.13 config-2.6.32.13 
> >> lspci -vvv:  http://old.nabble.com/file/p28704783/lspcivvv.log
> >> lspcivvv.log 
> >> dmidecode:  http://old.nabble.com/file/p28704783/dmidecode.log
> >> dmidecode.log 
> >> dmesg:  http://old.nabble.com/file/p28704783/dmesg dmesg 
> >> lsmod:  http://old.nabble.com/file/p28704783/lsmod.log lsmod.log 
> >> xend log:  http://old.nabble.com/file/p28704783/xend.log xend.log 
> >> menu.lst:
> >> title           Xen 4 / Debian GNU/Linux, kernel 2.6.32.13
> >> root            (hd0,0)
> >> kernel          /boot/xen.gz dom0_mem=2560M
> >> module          /boot/vmlinuz-2.6.32.13 root=LABEL=root-backup2 ro
> >> nomodeset
> >> module          /boot/initrd.img-2.6.32.13
> >> 
> >> The server run 12 domU windows xp with gplpv 0.11.0.213, all work
> >> On dom0 blktap not work (write about in other topic) and i must chage
> >> domU
> >> disk from tap:aio to file, is one or the problem about performance?
> >> With not set of dom0 memory and dom0 balloning have "freeze" with last
> >> msg
> >> calltrace about out of memory, i set dom0 memory in menu.lst and disable
> >> dom0 balloning, is necessary more ram that 2.5gb for dom0?
> >>
> > 
> > You really don't need 2,5 GB for dom0.
> > Start with 1024 MB. You might be able to go down to 512 MB or so.
> > 
> > It really depends what kind of tools you run in dom0.
> > 
> > Also remember that file: driver for guest disks uses dom0 page cache,
> > so it may appear that a lot of dom0 memory is used when using file: driver
> > since dom0 page cache will use *all* the free memory.. so increasing 
> > dom0 memory just makes you use more of the memory as cache.
> > 
> > You really should get tap:aio: working instead. But I guess you open
> > another
> > thread about it.
> > 
> >> There are some option in .config of kernel wrong or not good?
> >> with c state option in bios enable system is inusable, now i disable it
> >> but
> >> this is kernel, xen or bios problem?
> >> 
> >> I hope this information helps improve the kernel and xen, tell me if need
> >> another information
> >> 
> >> Thanks for any reply about my questions
> >> 
> > 
> > -- Pasi
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context: 
> http://old.nabble.com/Low-performance-and-some-problem-with-kernel-2.6.32.13-and-xen-4.0-rc1-tp28704783p28705622.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel