xen.org
2011-Apr-13 00:06 UTC
[Xen-devel] [xen-unstable test] 6825: tolerable FAIL - PUSHED
flight 6825 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6825/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-credit2 9 guest-start fail like 6820
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-win 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
version targeted for testing:
xen 56a3b9c7367f
baseline version:
xen 697ac895c11c
------------------------------------------------------------
People who touched revisions under test:
Ian Campbell <ian.campbell@citrix.com>
Jan Beulich <jbeulich@novell.com>
Keir Fraser <keir@xen.org>
Shriram Rajagopalan <rshriram@cs.ubc.ca>
Stephen Smalley <sds@tycho.nsa.gov>
Wei Wang <wei.wang2@amd.com>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-xcpkern-i386-xl pass
test-i386-xcpkern-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-xcpkern-i386-xl-credit2 pass
test-amd64-i386-rhel6hvm-intel fail
test-amd64-xcpkern-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-xcpkern-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-xcpkern-i386-pair pass
test-i386-xcpkern-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-xcpkern-i386-pv pass
test-i386-xcpkern-i386-pv pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-xcpkern-i386-win fail
test-i386-xcpkern-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-xcpkern-i386-xl-win fail
------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Pushing revision :
+ branch=xen-unstable
+ revision=56a3b9c7367f
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e ''
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
''
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ ''['' x ''!=''
x/export/home/osstest/repos/lock '']''
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push xen-unstable
56a3b9c7367f
+ branch=xen-unstable
+ revision=56a3b9c7367f
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e ''
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
''
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ ''['' x/export/home/osstest/repos/lock ''!=''
x/export/home/osstest/repos/lock '']''
+ : xen@xenbits.xensource.com
+ : xen@xenbits.xensource.com:git/linux-pvops
+ : master
+ case "$branch" in
+ cd /export/home/osstest/repos/xen-unstable.hg
+ hg push -r 56a3b9c7367f ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
pushing to ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 22 changesets with 64 changes to 26 files
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
hi all,
I have just ported the pvovhvm drivers to ubuntu 10.10 ,the domU can boot
successfully, but when the domU running, intermittence， the system will give me
such warnings:
INFO: task login:1073 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
INFO: task flush-202:0:457 blocked for more than 120seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
INFO: task jbd2/sda1-8:422 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
what's wrong with the domU? is it means there are some errors in
xen-blkfront? how should I debug this error???
Thanks a lot.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Apr-14 12:56 UTC
Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
On Wed, Apr 13, 2011 at 10:46:10AM +0800, topperxin wrote:> hi all, > I have just ported the pvovhvm drivers to ubuntu 10.10 ,the domU can boot successfully, but when the domU running, intermittence， the system will give me such warnings: > INFO: task login:1073 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > INFO: task flush-202:0:457 blocked for more than 120seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > INFO: task jbd2/sda1-8:422 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > what''s wrong with the domU? is it means there are some errors in > xen-blkfront? how should I debug this error???Enable the verbose output (DPRINTK) and see what the data stream has. What kernel version is 10.10? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
thanks for your time
the version of ubuntu 10.10 is 2.6.35.
the domU can boot successfully, but when I operate some commands such
as :ls ,touch , it'll be blocked, just like I stated before.
I have another question:
when I debug the xen-blkfront, I found the most difficult thing
is debug it. I want to know can I use xen-blkfront substitute a slave
disk, not the boot disk(primary disk), thus I can boot the system on qemu
emulated disk, and then mount the xen-blkfront disk, then to debug it. Can I do
this???
waiting...
At 2011-04-14 20:56:31，"Konrad Rzeszutek Wilk"
<konrad.wilk@oracle.com> wrote:
>On Wed, Apr 13, 2011 at 10:46:10AM +0800, topperxin wrote:
>> hi all,
>> I have just ported the pvovhvm drivers to ubuntu 10.10 ,the domU
can boot successfully, but when the domU running, intermittence， the system
will give me such warnings:
>> INFO: task login:1073 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
>> INFO: task flush-202:0:457 blocked for more than 120seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
>> INFO: task jbd2/sda1-8:422 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
>>
>> what's wrong with the domU? is it means there are some errors
in
>> xen-blkfront? how should I debug this error???
>
>Enable the verbose output (DPRINTK) and see what the data stream has. What
kernel
>version is 10.10?
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Apr-18 14:05 UTC
Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
On Mon, 18 Apr 2011, topperxin wrote:> thanks for your timethe version of ubuntu 10.10 is 2.6.35. > > the domU can boot successfully, but when I operate some commands such > as :ls ,touch , it''ll be blocked, just like I stated before. > > I have another question: > when I debug the xen-blkfront, I found the most difficult thing > is debug it. I want to know can I use xen-blkfront substitute a slave > disk, not the boot disk(primary disk), thus I can boot the system on qemu emulated disk, and then mount the xen-blkfront > disk, then to debug it. Can I do this??? > waiting...You can add xen_emul_unplug=aux-ide-disks to the linux command line options, so that the kernel will not unplug the emulated primary disk. Then you can use root=/dev/hda to make sure that the kernel uses the emulated interface to access the primary disk. Afterwards you should be able to debug blkfront accessing the secondary disk that should appear as /dev/xvdb for example. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
topperxin
2011-Apr-19 06:06 UTC
Re:Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
hi Stefano
thanks for your time
As your method, I modified my /boo/grub/grub.cfg of ubuntu10.10 like this:
=================================================== menuentry 'Ubuntu,
with Linux 2.6.35.4.pvonhvm' --class ubuntu --class gnu-linux --class gnu
--class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 3336889c-576e-4088-a6ff-89e869289766
linux /boot/vmlinuz-2.6.35.4
root=UUID=3336889c-576e-4088-a6ff-89e869289766 ro xen_emul_unplug=aux-ide-disks
initrd /boot/initrd.img-2.6.35.4.pvonhvm.0415
}
======================================================
then I reboot the Guest OS , I found the boot disk is still the xen-blkfront,
not the qemu emulate.
I reviewed the source of ./arch/x86/xen/platform-pci-unplug.c. there are several
parameters, such as:
==================================================================
if (!strncmp(p, "all", l))
xen_emul_unplug |= XEN_UNPLUG_ALL;
else if (!strncmp(p, "ide-disks", l))
xen_emul_unplug |= XEN_UNPLUG_ALL_IDE_DISKS;
else if (!strncmp(p, "aux-ide-disks", l))
xen_emul_unplug |= XEN_UNPLUG_AUX_IDE_DISKS;
else if (!strncmp(p, "nics", l))
xen_emul_unplug |= XEN_UNPLUG_ALL_NICS;
else if (!strncmp(p, "unnecessary", l))
xen_emul_unplug |= XEN_UNPLUG_UNNECESSARY;
else if (!strncmp(p, "never", l))
xen_emul_unplug |= XEN_UNPLUG_NEVER;
========================================================In my opinion , If I
want to use the emulated disk , I should set
xen_emul_unplug = XEN_UNPLUG_UNNECESSARY or
xen_emul_unplug = XEN_NEVER
right? I try these two ways, but I still failed.
Could you please tell me where can I get the source of
kernel 2.6.35 with pvonhvm???
Thank you very much.
At 2011-04-18 22:05:43，"Stefano Stabellini"
<stefano.stabellini@eu.citrix.com> wrote:
>On Mon, 18 Apr 2011, topperxin wrote:
>> thanks for your timethe version of ubuntu 10.10 is 2.6.35.
>>
>> the domU can boot successfully, but when I operate some commands such
>> as :ls ,touch , it'll be blocked, just like I stated before.
>>
>> I have another question:
>> when I debug the xen-blkfront, I found the most difficult thing
>> is debug it. I want to know can I use xen-blkfront substitute a slave
>> disk, not the boot disk(primary disk), thus I can boot the system on
qemu emulated disk, and then mount the xen-blkfront
>> disk, then to debug it. Can I do this???
>> waiting...
>
>You can add xen_emul_unplug=aux-ide-disks to the linux command line
>options, so that the kernel will not unplug the emulated primary disk.
>Then you can use root=/dev/hda to make sure that the kernel uses the
>emulated interface to access the primary disk.
>Afterwards you should be able to debug blkfront accessing the secondary
>disk that should appear as /dev/xvdb for example.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Apr-20 17:24 UTC
Re:Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
On Tue, 19 Apr 2011, topperxin wrote:> hi Stefano > thanks for your time > As your method, I modified my /boo/grub/grub.cfg of ubuntu10.10 like this: > ===================================================> menuentry ''Ubuntu, with Linux 2.6.35.4.pvonhvm'' --class ubuntu --class gnu-linux --class gnu --class os { > recordfail > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set 3336889c-576e-4088-a6ff-89e869289766 > linux /boot/vmlinuz-2.6.35.4 root=UUID=3336889c-576e-4088-a6ff-89e869289766 ro xen_emul_unplug=aux-ide-disks > initrd /boot/initrd.img-2.6.35.4.pvonhvm.0415 > } > ======================================================> > then I reboot the Guest OS , I found the boot disk is still the xen-blkfront, not the qemu emulate.aux-ide-disks means "do not unplug secondary emulated disks".> I reviewed the source of ./arch/x86/xen/platform-pci-unplug.c. there are several parameters, such as: > > ==================================================================> if (!strncmp(p, "all", l)) > xen_emul_unplug |= XEN_UNPLUG_ALL; > else if (!strncmp(p, "ide-disks", l)) > xen_emul_unplug |= XEN_UNPLUG_ALL_IDE_DISKS; > else if (!strncmp(p, "aux-ide-disks", l)) > xen_emul_unplug |= XEN_UNPLUG_AUX_IDE_DISKS; > else if (!strncmp(p, "nics", l)) > xen_emul_unplug |= XEN_UNPLUG_ALL_NICS; > else if (!strncmp(p, "unnecessary", l)) > xen_emul_unplug |= XEN_UNPLUG_UNNECESSARY; > else if (!strncmp(p, "never", l)) xen_emul_unplug |= XEN_UNPLUG_NEVER; > ========================================================> In my opinion , If I want to use the emulated disk , I should set > > xen_emul_unplug = XEN_UNPLUG_UNNECESSARY or > > xen_emul_unplug = XEN_NEVER > > right? I try these two ways, but I still failed.If you specify xen_emul_unplug=XEN_UNPLUG_UNNECESSARY you prevent blkfront from hooking PV disks corresponding to emulated disks. Of course you have to make sure your root device is not /dev/xvda because that wouldn''t work anymore, try root=/dev/sda if you want to make sure that you are using the emulated path. Also you need to specify hd* devices in your disk line in the VM config file, like this: disk = [ ''file:/root/images/debian_lenny_i386_small.raw,hda,w'']> > Could you please tell me where can I get the source of > > kernel 2.6.35 with pvonhvm???The first Linux kernel to have PV on HVM support was Linux 2.6.36, so I don''t have any 2.6.35 Linux tree with PV on HVM support. However a vanilla 2.6.36 (or 2.6.37 or 2.6.38) kernel should just work as PV on HVM kernel. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
topperxin
2011-Apr-25 03:15 UTC
Re:Re:Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
Thank you, Stefano
I have known that the first linux kernel version which include the PVONHVM
feature is 2.6.36. But now, the question I have to face is our clients always
required us to support other linux version, which not 2.6.36, perhaps 2.6.35,
2.6.34, 2.6.32... so I have to porting the PV drivers to these kernel version.
At first, if the target kernel version is
2.6.2X, I ported the pv-drivers based on 2.6.18,
these work not very hard, and I successfully. such ubuntu 8.04(2.6.24),
debian5.05(2.6.26)
But, if the target kernel version is 2.6.3X, these work seems very difficult, I
couldn't complete it, the biggest trouble is can't debug the
xen-blkfront.
Since I known that the pv-drivers will be included in linux kernel 2.6.36,
I studied the changes of it, and I try to port them to ubuntu10.10(2.6.35),
based on 2.6.36, the result is system can boot successfully with xen-blkfront
disk, but when I execute some commands such as:
ls, mkdir...
the system will be blocked, the phenomena just like before I have stated in this
mail.
What should I do next? Is this method ok?
Could you please tell me, when you write the xen-blkfront disk drivers for linux
kernel 2.6.36, how do you debug it when you meet errors?
Thank you very much.
At 2011-04-21 01:24:25，"Stefano Stabellini"
<stefano.stabellini@eu.citrix.com> wrote:
>On Tue, 19 Apr 2011, topperxin wrote:
>> hi Stefano
>> thanks for your time
>> As your method, I modified my /boo/grub/grub.cfg of ubuntu10.10 like
this:
>> ===================================================>>
menuentry 'Ubuntu, with Linux 2.6.35.4.pvonhvm' --class ubuntu --class
gnu-linux --class gnu --class os {
>> recordfail
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos1)'
>> search --no-floppy --fs-uuid --set
3336889c-576e-4088-a6ff-89e869289766
>> linux /boot/vmlinuz-2.6.35.4
root=UUID=3336889c-576e-4088-a6ff-89e869289766 ro xen_emul_unplug=aux-ide-disks
>> initrd /boot/initrd.img-2.6.35.4.pvonhvm.0415
>> }
>> ======================================================>>
>> then I reboot the Guest OS , I found the boot disk is still the
xen-blkfront, not the qemu emulate.
>
>aux-ide-disks means "do not unplug secondary emulated disks".
>
>
>> I reviewed the source of ./arch/x86/xen/platform-pci-unplug.c. there
are several parameters, such as:
>>
>>
==================================================================>>
if (!strncmp(p, "all", l))
>> xen_emul_unplug |= XEN_UNPLUG_ALL;
>> else if (!strncmp(p, "ide-disks", l))
>> xen_emul_unplug |= XEN_UNPLUG_ALL_IDE_DISKS;
>> else if (!strncmp(p, "aux-ide-disks", l))
>> xen_emul_unplug |= XEN_UNPLUG_AUX_IDE_DISKS;
>> else if (!strncmp(p, "nics", l))
>> xen_emul_unplug |= XEN_UNPLUG_ALL_NICS;
>> else if (!strncmp(p, "unnecessary", l))
>> xen_emul_unplug |= XEN_UNPLUG_UNNECESSARY;
>> else if (!strncmp(p, "never", l))
xen_emul_unplug |= XEN_UNPLUG_NEVER;
>> ========================================================>> In my
opinion , If I want to use the emulated disk , I should set
>>
>> xen_emul_unplug = XEN_UNPLUG_UNNECESSARY or
>>
>> xen_emul_unplug = XEN_NEVER
>>
>> right? I try these two ways, but I still failed.
>
>If you specify xen_emul_unplug=XEN_UNPLUG_UNNECESSARY you prevent
>blkfront from hooking PV disks corresponding to emulated disks.
>Of course you have to make sure your root device is not /dev/xvda
>because that wouldn't work anymore, try root=/dev/sda if you want to
>make sure that you are using the emulated path.
>Also you need to specify hd* devices in your disk line in the VM config
>file, like this:
>
>disk = [ 'file:/root/images/debian_lenny_i386_small.raw,hda,w']
>
>
>>
>> Could you please tell me where can I get the source of
>>
>> kernel 2.6.35 with pvonhvm???
>
>The first Linux kernel to have PV on HVM support was Linux 2.6.36, so I
>don't have any 2.6.35 Linux tree with PV on HVM support. However a
>vanilla 2.6.36 (or 2.6.37 or 2.6.38) kernel should just work as PV on
>HVM kernel.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Apr-26 08:45 UTC
Re: Re:Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
On Mon, Apr 25, 2011 at 11:15:45AM +0800, topperxin wrote:> Thank you, Stefano > I have known that the first linux kernel version which include the > PVONHVM feature is 2.6.36. But now, the question I have to face is our > clients always required us to support other linux version, which not > 2.6.36, perhaps 2.6.35, > 2.6.34, 2.6.32... so I have to porting the PV drivers to these kernel > version. > At first, if the target kernel version is > 2.6.2X, I ported the pv-drivers based on 2.6.18, > these work not very hard, and I successfully. such ubuntu 8.04(2.6.24), > debian5.05(2.6.26) > But, if the target kernel version is 2.6.3X, these work seems very > difficult, I couldn''t complete it, the biggest trouble is can''t debug the > xen-blkfront.Novell SLES/OpenSuse has a forward-port of the 2.6.18 based PVHVM drivers to 2.6.2x and 2.6.3x. But I think it''s better to use the new upstream-included PVHVM drivers these days. -- Pasi> Since I known that the pv-drivers will be included in linux kernel > 2.6.36, I studied the changes of it, and I try to port them to > ubuntu10.10(2.6.35), based on 2.6.36, the result is system can boot > successfully with xen-blkfront > disk, but when I execute some commands such as: > ls, mkdir... > the system will be blocked, the phenomena just like before I have stated > in this mail. > What should I do next? Is this method ok? > Could you please tell me, when you write the xen-blkfront disk drivers for > linux kernel 2.6.36, how do you debug it when you meet errors? > Thank you very much. > > > At 2011-04-21 01:24:25£¬"Stefano Stabellini" <stefano.stabellini@eu.citrix.com> wrote: > > >On Tue, 19 Apr 2011, topperxin wrote: > >> hi Stefano > >> thanks for your time > >> As your method, I modified my /boo/grub/grub.cfg of ubuntu10.10 like this: > >> ===================================================> >> menuentry ''Ubuntu, with Linux 2.6.35.4.pvonhvm'' --class ubuntu --class gnu-linux --class gnu --class os { > >> recordfail > >> insmod part_msdos > >> insmod ext2 > >> set root=''(hd0,msdos1)'' > >> search --no-floppy --fs-uuid --set 3336889c-576e-4088-a6ff-89e869289766 > >> linux /boot/vmlinuz-2.6.35.4 root=UUID=3336889c-576e-4088-a6ff-89e869289766 ro xen_emul_unplug=aux-ide-disks > >> initrd /boot/initrd.img-2.6.35.4.pvonhvm.0415 > >> } > >> ======================================================> >> > >> then I reboot the Guest OS , I found the boot disk is still the xen-blkfront, not the qemu emulate. > > > >aux-ide-disks means "do not unplug secondary emulated disks". > > > > > >> I reviewed the source of ./arch/x86/xen/platform-pci-unplug.c. there are several parameters, such as: > >> > >> ==================================================================> >> if (!strncmp(p, "all", l)) > >> xen_emul_unplug |= XEN_UNPLUG_ALL; > >> else if (!strncmp(p, "ide-disks", l)) > >> xen_emul_unplug |= XEN_UNPLUG_ALL_IDE_DISKS; > >> else if (!strncmp(p, "aux-ide-disks", l)) > >> xen_emul_unplug |= XEN_UNPLUG_AUX_IDE_DISKS; > >> else if (!strncmp(p, "nics", l)) > >> xen_emul_unplug |= XEN_UNPLUG_ALL_NICS; > >> else if (!strncmp(p, "unnecessary", l)) > >> xen_emul_unplug |= XEN_UNPLUG_UNNECESSARY; > >> else if (!strncmp(p, "never", l)) xen_emul_unplug |= XEN_UNPLUG_NEVER; > >> ========================================================> >> In my opinion , If I want to use the emulated disk , I should set > >> > >> xen_emul_unplug = XEN_UNPLUG_UNNECESSARY or > >> > >> xen_emul_unplug = XEN_NEVER > >> > >> right? I try these two ways, but I still failed. > > > >If you specify xen_emul_unplug=XEN_UNPLUG_UNNECESSARY you prevent > >blkfront from hooking PV disks corresponding to emulated disks. > >Of course you have to make sure your root device is not /dev/xvda > >because that wouldn''t work anymore, try root=/dev/sda if you want to > >make sure that you are using the emulated path. > >Also you need to specify hd* devices in your disk line in the VM config > >file, like this: > > > >disk = [ ''file:/root/images/debian_lenny_i386_small.raw,hda,w''] > > > > > >> > >> Could you please tell me where can I get the source of > >> > >> kernel 2.6.35 with pvonhvm??? > > > >The first Linux kernel to have PV on HVM support was Linux 2.6.36, so I > >don''t have any 2.6.35 Linux tree with PV on HVM support. However a > >vanilla 2.6.36 (or 2.6.37 or 2.6.38) kernel should just work as PV on > >HVM kernel. > > -------------------------------------------------------------------------- > > [1]ÌåÑéÍøÒ×ÓÊÏä2G³¬ŽóžœŒþ£¬ÇáËÉ·¢ÓÅÖÊŽóµçÓ°¡¢ŽóÕÕƬ£¬ÌáËÙ3±¶! > > References > > Visible links > 1. http://mail.163.com/html/110414_attachment/att1.htm> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-May-03 14:21 UTC
Re:Re:Re:Re: [Xen-devel] some errors of pvonhvm : xen-blkfront
On Mon, 25 Apr 2011, topperxin wrote:> Thank you, Stefano I have known that the first linux kernel version which include the PVONHVM feature is 2.6.36. But > now, the question I have to face is our clients always required us to support other linux version, which not 2.6.36, > perhaps 2.6.35, > 2.6.34, 2.6.32... so I have to porting the PV drivers to these kernel version. > At first, if the target kernel version is > 2.6.2X, I ported the pv-drivers based on 2.6.18, > these work not very hard, and I successfully. such ubuntu 8.04(2.6.24), debian5.05(2.6.26) > But, if the target kernel version is 2.6.3X, these work seems very difficult, I couldn''t complete it, the biggest trouble > is can''t debug the xen-blkfront. > Since I known that the pv-drivers will be included in linux kernel 2.6.36, I studied the changes of it, and I try to > port them to ubuntu10.10(2.6.35), based on 2.6.36, the result is system can boot successfully with xen-blkfront > disk, but when I execute some commands such as: > ls, mkdir... > the system will be blocked, the phenomena just like before I have stated in this mail. > What should I do next? Is this method ok? > Could you please tell me, when you write the xen-blkfront disk drivers for linux kernel 2.6.36, how do you debug it when > you meet errors?I don''t have a silver bullet, just add more printk''s until you understand what is going on :-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel