Description of problem: after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd file (as base image), os can not startup. I found data error in C:\Windows\System32 : ?--------- ? ? ? ? ? pnpts.dll ?--------- ? ? ? ? ? pnpui.dll ?--------- ? ? ? ? ? PnPUnattend.exe ?--------- ? ? ? ? ? PnPutil.exe How reproducible: I tested 10 times, it appear 10 times that os can not startup. Steps to Reproduce: 1. vhd-util create -n test.vhd -s 20480 2. xm create test.hvm 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\ 15G, D:\ 5G ) 4. can not startup 5. xm des test.vhd 6. tapdisk2 -n vhd:/mnt/img/test.vhd 7. mount -o offset=105906176 -t ntfs /dev/xen/blktap-2/tapdev0 /mnt/vhd 8. ll /mnt/vhd/Windows/System32 | grep ? ?--------- ? ? ? ? ? pnpts.dll ?--------- ? ? ? ? ? pnpui.dll ?--------- ? ? ? ? ? PnPUnattend.exe ?--------- ? ? ? ? ? PnPutil.exe Additional info: I install Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd file, the problem disappear. Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the problem disappear. Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on vhd file, the problem disappear. Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, D:\10G) on vhdfile, the problem disappear. Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on rawfile, the problem disappear. Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd file, the problem appear. Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, D:\85G) on vhdfile, the problem appear. ps: windows 2003 need 3G disk space. redhat 5.4 need 4G disk space. windows 2008 need 8G disk space. the problem disappear means that os can startup and no data error. compile env and filesystem : Redhat AS 5.4 xm info: host : vm01 release : 2.6.31.13 version : #1 SMP Wed Apr 21 12:30:21 CST 2010 machine : x86_64 nr_cpus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24539 free_memory : 1668 node_to_cpu : node0:0-15 node_to_memory : node0:1668 node_to_dma32_mem : node0:82 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_domain : dev.sd.test.com cc_compile_date : Mon Apr 26 10:17:37 CST 2010 xend_config_format : 4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt
2010-May-08 10:04 UTC
RE: [Xen-devel] VHD BUG in xen4.0 when install windows2008
> Description of problem: > after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, > D:\ 5G) on vhd file (as base image), os can not startup.Which dom0 kernel is this with? I''m guessing one of Jeremy''s pvops trees? It might be worth reducing the number of dom0 VCPUs to 1 and repeating the experiment to see if that makes a difference. Thanks, Ian> I found data error in C:\Windows\System32 : > ?--------- ? ? ? ? ? pnpts.dll > ?--------- ? ? ? ? ? pnpui.dll > ?--------- ? ? ? ? ? PnPUnattend.exe > ?--------- ? ? ? ? ? PnPutil.exe > > How reproducible: > I tested 10 times, it appear 10 times that os can not startup. > > Steps to Reproduce: > 1. vhd-util create -n test.vhd -s 20480 > 2. xm create test.hvm > 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\ 15G, > D:\ 5G ) 4. can not startup 5. xm des test.vhd 6. tapdisk2 -n > vhd:/mnt/img/test.vhd 7. mount -o offset=105906176 -t ntfs > /dev/xen/blktap-2/tapdev0 /mnt/vhd 8. ll /mnt/vhd/Windows/System32 | grep > ? > ?--------- ? ? ? ? ? pnpts.dll > ?--------- ? ? ? ? ? pnpui.dll > ?--------- ? ? ? ? ? PnPUnattend.exe > ?--------- ? ? ? ? ? PnPutil.exe > > Additional info: > I install > Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd file, > the problem disappear. > Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the > problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on vhd > file, the problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, D:\10G) on > vhd file, the problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > raw file, the problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > vhd file, the problem appear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, D:\85G) on > vhd file, the problem appear. > > ps: > windows 2003 need 3G disk space. > redhat 5.4 need 4G disk space. > windows 2008 need 8G disk space. > the problem disappear means that os can startup and no data error. > > compile env and filesystem : > Redhat AS 5.4 > > xm info: > host : vm01 > release : 2.6.31.13 > version : #1 SMP Wed Apr 21 12:30:21 CST 2010 > machine : x86_64 > nr_cpus : 16 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 2 > cpu_mhz : 2400 > hw_caps : > bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 24539 > free_memory : 1668 > node_to_cpu : node0:0-15 > node_to_memory : node0:1668 > node_to_dma32_mem : node0:82 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .0 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) > cc_compile_by : root > cc_compile_domain : dev.sd.test.com > cc_compile_date : Mon Apr 26 10:17:37 CST 2010 > xend_config_format : 4 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
yingbin wang
2010-May-08 12:46 UTC
Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008
thank you for your reply.
as you guest, dom0 kernel: pvops 2.6.31.13
I try what you say.
menu.lst:
title Xen 4.0 kernel 2.6.31.13
root (hd0,0)
kernel /xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin
module /vmlinuz-2.6.31.13 ro root=LABEL=/ nomodeset
module /initrd-2.6.31.13.img
but the problem also appear, os can''t startup.
Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G)
on vhdfile, the problem
appear.
when I install windows 2008, I meet another problem :
the dom0 hang up, I reboot the physical machine and found some info from
/var/log/message:
May 8 20:02:47 SS01 tapdisk2[21997]: Assertion
''list_empty(&vreq->next)'' failed, line 1822, file
tapdisk-vbd.c
May 8 20:02:47 SS01 kernel: tapdisk2[21997]: segfault at 0 ip
000000000040a24f sp 00007fff162b2d90 error 6 in tapdisk2[400000+39000]
May 8 20:02:47 SS01 kernel: blktap_device_fail_pending_requests:
252:2: failing pending write of 11 pages
May 8 20:02:47 SS01 kernel: end_request: I/O error, dev tapdevc,
sector 10485752
May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc,
logical block 1310719
May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc
May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc,
logical block 1310720
May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc
May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc,
logical block 1310721
May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc
I don''t know the relation between two problems.I hope it give you more
info
to help me solve the problem.
I think it may be a bug of the pvops 2.6.31.13. I hope there is a way to
solve it. could you give some advise?
I will try xenlinux 2.6.18.8 and report the result.
Cheers,
wyb
2010/5/8 Ian Pratt <Ian.Pratt@eu.citrix.com>
> > Description of problem:
> > after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\
> 15G,
> > D:\ 5G) on vhd file (as base image), os can not startup.
>
> Which dom0 kernel is this with? I''m guessing one of
Jeremy''s pvops trees?
>
> It might be worth reducing the number of dom0 VCPUs to 1 and repeating the
> experiment to see if that makes a difference.
>
> Thanks,
> Ian
>
>
> > I found data error in C:\Windows\System32 :
> > ?--------- ? ? ? ? ? pnpts.dll
> > ?--------- ? ? ? ? ? pnpui.dll
> > ?--------- ? ? ? ? ? PnPUnattend.exe
> > ?--------- ? ? ? ? ? PnPutil.exe
> >
> > How reproducible:
> > I tested 10 times, it appear 10 times that os can not startup.
> >
> > Steps to Reproduce:
> > 1. vhd-util create -n test.vhd -s 20480
> > 2. xm create test.hvm
> > 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\
15G,
> > D:\ 5G ) 4. can not startup 5. xm des test.vhd 6. tapdisk2 -n
> > vhd:/mnt/img/test.vhd 7. mount -o offset=105906176 -t ntfs
> > /dev/xen/blktap-2/tapdev0 /mnt/vhd 8. ll /mnt/vhd/Windows/System32 |
grep
> > ?
> > ?--------- ? ? ? ? ? pnpts.dll
> > ?--------- ? ? ? ? ? pnpui.dll
> > ?--------- ? ? ? ? ? PnPUnattend.exe
> > ?--------- ? ? ? ? ? PnPutil.exe
> >
> > Additional info:
> > I install
> > Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd
file,
> > the problem disappear.
> > Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the
> > problem disappear.
> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on vhd
> > file, the problem disappear.
> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, D:\10G)
on
> > vhd file, the problem disappear.
> > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G)
on
> > raw file, the problem disappear.
> > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G)
on
> > vhd file, the problem appear.
> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, D:\85G)
on
> > vhd file, the problem appear.
> >
> > ps:
> > windows 2003 need 3G disk space.
> > redhat 5.4 need 4G disk space.
> > windows 2008 need 8G disk space.
> > the problem disappear means that os can startup and no data error.
> >
> > compile env and filesystem :
> > Redhat AS 5.4
> >
> > xm info:
> > host : vm01
> > release : 2.6.31.13
> > version : #1 SMP Wed Apr 21 12:30:21 CST 2010
> > machine : x86_64
> > nr_cpus : 16
> > nr_nodes : 1
> > cores_per_socket : 4
> > threads_per_core : 2
> > cpu_mhz : 2400
> > hw_caps :
> >
bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000
> > virt_caps : hvm
> > total_memory : 24539
> > free_memory : 1668
> > node_to_cpu : node0:0-15
> > node_to_memory : node0:1668
> > node_to_dma32_mem : node0:82
> > max_node_id : 0
> > xen_major : 4
> > xen_minor : 0
> > xen_extra : .0
> > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> > hvm-3.0-x86_32p hvm-3.0-x86_64
> > xen_scheduler : credit
> > xen_pagesize : 4096
> > platform_params : virt_start=0xffff800000000000
> > xen_changeset : unavailable
> > xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin
> > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)
> > cc_compile_by : root
> > cc_compile_domain : dev.sd.test.com
> > cc_compile_date : Mon Apr 26 10:17:37 CST 2010
> > xend_config_format : 4
> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
yingbin wang
2010-May-08 17:02 UTC
Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008
I have try xenlinux 2.6.18.8. the problem also appear. os can not startup. Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhdfile, the problem appear. does anyone successfully install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd file?? env : (xen4.0, kernel2.6.31.13) or (xen4.0, kernel2.6.18.8) Cheers, wyb 在 2010年5月8日 下午8:46，yingbin wang <yingbin.wangyb@gmail.com>写道：> thank you for your reply. > > as you guest, dom0 kernel: pvops 2.6.31.13 > > I try what you say. > menu.lst: > title Xen 4.0 kernel 2.6.31.13 > root (hd0,0) > kernel /xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > module /vmlinuz-2.6.31.13 ro root=LABEL=/ nomodeset > module /initrd-2.6.31.13.img > > but the problem also appear, os can''t startup. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > vhd file, the problem appear. > > when I install windows 2008, I meet another problem : > the dom0 hang up, I reboot the physical machine and found some info from > /var/log/message: > > May 8 20:02:47 SS01 tapdisk2[21997]: Assertion ''list_empty(&vreq->next)'' failed, line 1822, file tapdisk-vbd.c > > May 8 20:02:47 SS01 kernel: tapdisk2[21997]: segfault at 0 ip 000000000040a24f sp 00007fff162b2d90 error 6 in tapdisk2[400000+39000] > > May 8 20:02:47 SS01 kernel: blktap_device_fail_pending_requests: 252:2: failing pending write of 11 pages > > May 8 20:02:47 SS01 kernel: end_request: I/O error, dev tapdevc, sector 10485752 > > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310719 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310720 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310721 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > > I don''t know the relation between two problems.I hope it give you more > info to help me solve the problem. > I think it may be a bug of the pvops 2.6.31.13. I hope there is a way to > solve it. could you give some advise? > I will try xenlinux 2.6.18.8 and report the result. > > Cheers, > wyb > 2010/5/8 Ian Pratt <Ian.Pratt@eu.citrix.com> > > > Description of problem: >> > after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ >> 15G, >> > D:\ 5G) on vhd file (as base image), os can not startup. >> >> Which dom0 kernel is this with? I''m guessing one of Jeremy''s pvops trees? >> >> It might be worth reducing the number of dom0 VCPUs to 1 and repeating the >> experiment to see if that makes a difference. >> >> Thanks, >> Ian >> >> >> > I found data error in C:\Windows\System32 : >> > ?--------- ? ? ? ? ? pnpts.dll >> > ?--------- ? ? ? ? ? pnpui.dll >> > ?--------- ? ? ? ? ? PnPUnattend.exe >> > ?--------- ? ? ? ? ? PnPutil.exe >> > >> > How reproducible: >> > I tested 10 times, it appear 10 times that os can not startup. >> > >> > Steps to Reproduce: >> > 1. vhd-util create -n test.vhd -s 20480 >> > 2. xm create test.hvm >> > 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\ >> 15G, >> > D:\ 5G ) 4. can not startup 5. xm des test.vhd 6. tapdisk2 -n >> > vhd:/mnt/img/test.vhd 7. mount -o offset=105906176 -t ntfs >> > /dev/xen/blktap-2/tapdev0 /mnt/vhd 8. ll /mnt/vhd/Windows/System32 | >> grep >> > ? >> > ?--------- ? ? ? ? ? pnpts.dll >> > ?--------- ? ? ? ? ? pnpui.dll >> > ?--------- ? ? ? ? ? PnPUnattend.exe >> > ?--------- ? ? ? ? ? PnPutil.exe >> > >> > Additional info: >> > I install >> > Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd >> file, >> > the problem disappear. >> > Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the >> > problem disappear. >> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on vhd >> > file, the problem disappear. >> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, D:\10G) on >> > vhd file, the problem disappear. >> > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on >> > raw file, the problem disappear. >> > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on >> > vhd file, the problem appear. >> > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, D:\85G) on >> > vhd file, the problem appear. >> > >> > ps: >> > windows 2003 need 3G disk space. >> > redhat 5.4 need 4G disk space. >> > windows 2008 need 8G disk space. >> > the problem disappear means that os can startup and no data error. >> > >> > compile env and filesystem : >> > Redhat AS 5.4 >> > >> > xm info: >> > host : vm01 >> > release : 2.6.31.13 >> > version : #1 SMP Wed Apr 21 12:30:21 CST 2010 >> > machine : x86_64 >> > nr_cpus : 16 >> > nr_nodes : 1 >> > cores_per_socket : 4 >> > threads_per_core : 2 >> > cpu_mhz : 2400 >> > hw_caps : >> > bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 >> > virt_caps : hvm >> > total_memory : 24539 >> > free_memory : 1668 >> > node_to_cpu : node0:0-15 >> > node_to_memory : node0:1668 >> > node_to_dma32_mem : node0:82 >> > max_node_id : 0 >> > xen_major : 4 >> > xen_minor : 0 >> > xen_extra : .0 >> > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> > hvm-3.0-x86_32p hvm-3.0-x86_64 >> > xen_scheduler : credit >> > xen_pagesize : 4096 >> > platform_params : virt_start=0xffff800000000000 >> > xen_changeset : unavailable >> > xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin >> > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) >> > cc_compile_by : root >> > cc_compile_domain : dev.sd.test.com >> > cc_compile_date : Mon Apr 26 10:17:37 CST 2010 >> > xend_config_format : 4 >> > >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-May-08 19:52 UTC
Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sun, May 09, 2010 at 01:02:42AM +0800, yingbin wang wrote:> I have try xenlinux 2.6.18.8. the problem also appear. os can not startup. > > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > vhd file, the problem appear. > does anyone successfully install Windows 2008 R2 Standard Edition 64(disk > size: 20G, C:\ 15G, D:\ 5G) on vhd file?? > env : (xen4.0, kernel2.6.31.13) or (xen4.0, kernel2.6.18.8) >Looking at the log (below) it seems the ''tapdisk2'' process segfaults (crashes). Sounds like a bug in it.. -- Pasi> Cheers, > wyb > ÔÚ 2010Äê5ÔÂ8ÈÕ ÏÂÎç8:46£¬yingbin wang <[1]yingbin.wangyb@gmail.com>ÐŽµÀ£º > > thank you for your reply. > > as you guest, dom0 kernel: pvops 2.6.31.13 > > I try what you say. > menu.lst: > title Xen 4.0 kernel 2.6.31.13 > root (hd0,0) > kernel /xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > module /vmlinuz-2.6.31.13 ro root=LABEL=/ nomodeset > module /initrd-2.6.31.13.img > > but the problem also appear, os can''t startup. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > vhd file, the problem appear. > > when I install windows 2008, I meet another problem : > the dom0 hang up, I reboot the physical machine and found some info from > /var/log/message: > May 8 20:02:47 SS01 tapdisk2[21997]: Assertion ''list_empty(&vreq->next)'' failed, line 1822, file tapdisk-vbd.c > May 8 20:02:47 SS01 kernel: tapdisk2[21997]: segfault at 0 ip 000000000040a24f sp 00007fff162b2d90 error 6 in tapdisk2[400000+39000] > May 8 20:02:47 SS01 kernel: blktap_device_fail_pending_requests: 252:2: failing pending write of 11 pages > May 8 20:02:47 SS01 kernel: end_request: I/O error, dev tapdevc, sector 10485752 > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310719 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310720 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > May 8 20:02:47 SS01 kernel: Buffer I/O error on device tapdevc, logical block 1310721 > May 8 20:02:47 SS01 kernel: lost page write due to I/O error on tapdevc > > I don''t know the relation between two problems.I hope it give you more > info to help me solve the problem. > I think it may be a bug of the pvops 2.6.31.13. I hope there is a way to > solve it. could you give some advise? > I will try xenlinux 2.6.18.8 and report the result. > > Cheers, > wyb > 2010/5/8 Ian Pratt <[2]Ian.Pratt@eu.citrix.com> > > > Description of problem: > > after install Windows 2008 R2 Standard Edition 64(disk size: 20G, > C:\ 15G, > > D:\ 5G) on vhd file (as base image), os can not startup. > > Which dom0 kernel is this with? I''m guessing one of Jeremy''s pvops > trees? > > It might be worth reducing the number of dom0 VCPUs to 1 and repeating > the experiment to see if that makes a difference. > > Thanks, > Ian > > > I found data error in C:\Windows\System32 : > > ?--------- ? ? ? ? ? pnpts.dll > > ?--------- ? ? ? ? ? pnpui.dll > > ?--------- ? ? ? ? ? PnPUnattend.exe > > ?--------- ? ? ? ? ? PnPutil.exe > > > > How reproducible: > > I tested 10 times, it appear 10 times that os can not startup. > > > > Steps to Reproduce: > > 1. vhd-util create -n test.vhd -s 20480 > > 2. xm create test.hvm > > 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\ > 15G, > > D:\ 5G ) 4. can not startup 5. xm des test.vhd 6. tapdisk2 -n > > vhd:/mnt/img/test.vhd 7. mount -o offset=105906176 -t ntfs > > /dev/xen/blktap-2/tapdev0 /mnt/vhd 8. ll /mnt/vhd/Windows/System32 | > grep > > ? > > ?--------- ? ? ? ? ? pnpts.dll > > ?--------- ? ? ? ? ? pnpui.dll > > ?--------- ? ? ? ? ? PnPUnattend.exe > > ?--------- ? ? ? ? ? PnPutil.exe > > > > Additional info: > > I install > > Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd > file, > > the problem disappear. > > Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the > > problem disappear. > > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on > vhd > > file, the problem disappear. > > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, > D:\10G) on > > vhd file, the problem disappear. > > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) > on > > raw file, the problem disappear. > > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) > on > > vhd file, the problem appear. > > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, > D:\85G) on > > vhd file, the problem appear. > > > > ps: > > windows 2003 need 3G disk space. > > redhat 5.4 need 4G disk space. > > windows 2008 need 8G disk space. > > the problem disappear means that os can startup and no data error. > > > > compile env and filesystem : > > Redhat AS 5.4 > > > > xm info: > > host : vm01 > > release : 2.6.31.13 > > version : #1 SMP Wed Apr 21 12:30:21 CST 2010 > > machine : x86_64 > > nr_cpus : 16 > > nr_nodes : 1 > > cores_per_socket : 4 > > threads_per_core : 2 > > cpu_mhz : 2400 > > hw_caps : > > > bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 > > virt_caps : hvm > > total_memory : 24539 > > free_memory : 1668 > > node_to_cpu : node0:0-15 > > node_to_memory : node0:1668 > > node_to_dma32_mem : node0:82 > > max_node_id : 0 > > xen_major : 4 > > xen_minor : 0 > > xen_extra : .0 > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p > hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : unavailable > > xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat > 4.1.2-46) > > cc_compile_by : root > > cc_compile_domain : [3]dev.sd.test.com > > cc_compile_date : Mon Apr 26 10:17:37 CST 2010 > > xend_config_format : 4 > > > > References > > Visible links > 1. mailto:yingbin.wangyb@gmail.com > 2. mailto:Ian.Pratt@eu.citrix.com > 3. http://dev.sd.test.com/> _______________________________________________ > 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
Daniel Stodden
2010-May-09 18:40 UTC
Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sat, 2010-05-08 at 15:52 -0400, Pasi Kärkkäinen wrote:> On Sun, May 09, 2010 at 01:02:42AM +0800, yingbin wang wrote: > > I have try xenlinux 2.6.18.8. the problem also appear. os can not startup. > > > > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > > vhd file, the problem appear. > > does anyone successfully install Windows 2008 R2 Standard Edition 64(disk > > size: 20G, C:\ 15G, D:\ 5G) on vhd file?? > > env : (xen4.0, kernel2.6.31.13) or (xen4.0, kernel2.6.18.8) > > > > Looking at the log (below) it seems the ''tapdisk2'' process segfaults (crashes). > Sounds like a bug in it..This is the loop pulling requests from the userspace I/O ring. Missing a sanity check on the message content, hence the crash. I would have bet it''s smp-related, but sounds as if not. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Heiko Wundram
2010-May-09 19:03 UTC
AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
As I''m seeing a similar behavior of tapdisk2 (see my recent posts to xen-users, especially "blktap2, also broken in current pv_ops stable-2.6.32.x?"), I can confirm that at least in my testing (I''ve done some more over the weekend, re. that message), this is indeed an "SMP-related" problem, but only for HVM-64bit domains. What I can basically say is that: 1) Uni/Multi/32-bit/64-bit PV domains run properly. 1) Uni-VCPU, 32-bit HVM domains run properly. 2) Multi-VCPU, 32-bit HVM domains run properly. 3) Uni-VCPU, 64-bit HVM domains run properly. 4) Multi-VCPU, 64-bit HVM domains cause tapdisk2 to segfault, sometimes, under heavy I/O, and if that happens, causes the Dom0-kernel to freeze/lock up, Bug, and/or all other kinds of undefined behavior, where I really haven''t made out a pattern yet. Interestingly, these errors do not happen when using the "normal" blkback-driver, and I''m very positive (at least that''s what happened during my testing) that it''s specific to Multi-VCPU, 64-bit HVM domains that the crash occurs, independent of the number of VCPUs bound to Dom0. --- Heiko. -----Ursprüngliche Nachricht----- Von: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] Im Auftrag von Daniel Stodden Gesendet: Sonntag, 9. Mai 2010 20:41 An: Pasi Kärkkäinen Cc: Ian Pratt; yingbin wang; xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008 On Sat, 2010-05-08 at 15:52 -0400, Pasi Kärkkäinen wrote:> On Sun, May 09, 2010 at 01:02:42AM +0800, yingbin wang wrote: > > I have try xenlinux 2.6.18.8. the problem also appear. os can not startup. > > > > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > > vhd file, the problem appear. > > does anyone successfully install Windows 2008 R2 Standard Edition 64(disk > > size: 20G, C:\ 15G, D:\ 5G) on vhd file?? > > env : (xen4.0, kernel2.6.31.13) or (xen4.0, kernel2.6.18.8) > > > > Looking at the log (below) it seems the ''tapdisk2'' process segfaults (crashes). > Sounds like a bug in it..This is the loop pulling requests from the userspace I/O ring. Missing a sanity check on the message content, hence the crash. I would have bet it''s smp-related, but sounds as if not. Daniel _______________________________________________ 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
Daniel Stodden
2010-May-10 07:48 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sun, 2010-05-09 at 15:03 -0400, Heiko Wundram wrote:> As I''m seeing a similar behavior of tapdisk2 (see my recent posts to xen-users, especially "blktap2, also broken in current pv_ops stable-2.6.32.x?"), I can confirm that at least in my testing (I''ve done some more over the weekend, re. that message), this is indeed an "SMP-related" problem, but only for HVM-64bit domains. > > What I can basically say is that: > > 1) Uni/Multi/32-bit/64-bit PV domains run properly. > 1) Uni-VCPU, 32-bit HVM domains run properly. > 2) Multi-VCPU, 32-bit HVM domains run properly. > 3) Uni-VCPU, 64-bit HVM domains run properly. > 4) Multi-VCPU, 64-bit HVM domains cause tapdisk2 to segfault, sometimes, under heavy I/O, and if that happens, causes the Dom0-kernel to freeze/lock up, Bug, and/or all other kinds of undefined behavior, where I really haven''t made out a pattern yet. > > Interestingly, these errors do not happen when using the "normal" blkback-driver, and I''m very positive (at least that''s what happened during my testing) that it''s specific to Multi-VCPU, 64-bit HVM domains that the crash occurs, independent of the number of VCPUs bound to Dom0.Okay, one thing which was going to happen soon is a patch to make tapdisk run the device queue synchronously. From your description I''m just not very convinced that this resolves such issues as well. Looks like it needs some 64 bit testing beforehand. Thanks for the hints. Does HVM up there mean it''s rather triggered by qemu alone? Were you running pv drivers? Cheers, Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Heiko Wundram
2010-May-10 08:17 UTC
AW: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
The 64-bit HVM domain I''ve tested was a Windows (2008 R2 Web Server) domain, without PV drivers, so yeah, it was triggered by qemu alone in my specific test case. Looking back at my testing, I''m not 100% certain that the bug doesn''t occur on 64-bit Multi-VCPU PV-domains (I thought I tested those "properly", but I just did one test case with Ubuntu 10.04 running "fully" PV, and after the system booted successfully, I didn''t test whether bonnie++-I/O or any such would trigger the behavior; installation was done in a Dom0 chroot anyway for that, so I can''t actually say whether there''d also be a bug here), but I''m positive that Multi-VCPU 32-bit HVM and PV domains do not exhibit the errant behavior, just as Uni-VCPU 64-bit HVM and PV domains don''t. If you have a patch to test (regarding the synchronous queuing of tapdisk2), I''d be happy to give it a shot with my specific setup. --- Heiko. PS: again, sorry for topposting; I currently don''t have access to a "functioning" email client... Which begs the question: anybody know of a way to make Outlook behave sanely concerning quoting of mails? ;-) -----Ursprüngliche Nachricht----- Von: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] Im Auftrag von Daniel Stodden Gesendet: Montag, 10. Mai 2010 09:49 An: Heiko Wundram Cc: xen-devel@lists.xensource.com Betreff: Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008 On Sun, 2010-05-09 at 15:03 -0400, Heiko Wundram wrote:> As I''m seeing a similar behavior of tapdisk2 (see my recent posts to xen-users, especially "blktap2, also broken in current pv_ops stable-2.6.32.x?"), I can confirm that at least in my testing (I''ve done some more over the weekend, re. that message), this is indeed an "SMP-related" problem, but only for HVM-64bit domains. > > What I can basically say is that: > > 1) Uni/Multi/32-bit/64-bit PV domains run properly. > 1) Uni-VCPU, 32-bit HVM domains run properly. > 2) Multi-VCPU, 32-bit HVM domains run properly. > 3) Uni-VCPU, 64-bit HVM domains run properly. > 4) Multi-VCPU, 64-bit HVM domains cause tapdisk2 to segfault, sometimes, under heavy I/O, and if that happens, causes the Dom0-kernel to freeze/lock up, Bug, and/or all other kinds of undefined behavior, where I really haven''t made out a pattern yet. > > Interestingly, these errors do not happen when using the "normal" blkback-driver, and I''m very positive (at least that''s what happened during my testing) that it''s specific to Multi-VCPU, 64-bit HVM domains that the crash occurs, independent of the number of VCPUs bound to Dom0.Okay, one thing which was going to happen soon is a patch to make tapdisk run the device queue synchronously. From your description I''m just not very convinced that this resolves such issues as well. Looks like it needs some 64 bit testing beforehand. Thanks for the hints. Does HVM up there mean it''s rather triggered by qemu alone? Were you running pv drivers? Cheers, Daniel _______________________________________________ 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
Daniel Stodden
2010-May-10 21:41 UTC
Re: AW: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Mon, 2010-05-10 at 04:17 -0400, Heiko Wundram wrote:> The 64-bit HVM domain I''ve tested was a Windows (2008 R2 Web Server) domain, without PV drivers, so yeah, it was triggered by qemu alone in my specific test case. > > Looking back at my testing, I''m not 100% certain that the bug doesn''t occur on 64-bit Multi-VCPU PV-domains (I thought I tested those "properly", but I just did one test case with Ubuntu 10.04 running "fully" PV, and after the system booted successfully, I didn''t test whether bonnie++-I/O or any such would trigger the behavior; installation was done in a Dom0 chroot anyway for that, so I can''t actually say whether there''d also be a bug here), but I''m positive that Multi-VCPU 32-bit HVM and PV domains do not exhibit the errant behavior, just as Uni-VCPU 64-bit HVM and PV domains don''t.Thanks. I''m mainly looking for the cheapest way to come across a repro.> If you have a patch to test (regarding the synchronous queuing of tapdisk2), I''d be happy to give it a shot with my specific setup.I''ll cc you when posting them. Any additional testing before Jeremy gets to pick them up is welcome.> --- Heiko. > > PS: again, sorry for topposting; I currently don''t have access to a "functioning" email client... > Which begs the question: anybody know of a way to make Outlook behave sanely concerning quoting of mails? ;-)I gave up on Outlook for basically that reason. But I don''t think people mind. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
yingbin wang
2010-May-15 16:02 UTC
[Xen-devel] Re: VHD BUG in xen4.0 when install windows2008
the install problem is solved. after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd file (as base image), os reboot. I use command( ps aux | grep tapdisk2 ) to see the status and found that after new tapdisk2 process create, old tapdisk2 process didn''t close. I found something from xend source. when xend destroy tap2 device, xend create a thread to write remove to /sys/class/blktap2/blktap0/remove and then continue to create new tap2 device, but old tapdisk2 process didn''t immediately close. so I add some code before xend exec cmd ( [ TAPDISK_BINARY, ''-n'', ''%s:%s'' % (params, file) ] ). it just wait old tapdisk2 process. when it know the old process is closed, it will create new tapdisk2 process. after update /usr/lib64/python2.4/site-packages/xen/xend/server/BlktapController.py and restart xend, I install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd file (as base image). the problem disappear. I tested 5 times, the problem didn''t appear. I will do more test case later. the attachment is the new code of BlktapController.py ( base on xen 4.0 ). you can copy it to /usr/lib64/python2.4/site-packages/xen/xend/server/ and restart xend. this is a tentative plan, I will track the real reason later. Cheers, wyb 2010/5/8 yingbin wang <yingbin.wangyb@gmail.com>> Description of problem: > after install Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, > D:\ 5G) on vhd file (as base image), os can not startup. > I found data error in C:\Windows\System32 : > ?--------- ? ? ? ? ? pnpts.dll > ?--------- ? ? ? ? ? pnpui.dll > ?--------- ? ? ? ? ? PnPUnattend.exe > ?--------- ? ? ? ? ? PnPutil.exe > > How reproducible: > I tested 10 times, it appear 10 times that os can not startup. > > Steps to Reproduce: > 1. vhd-util create -n test.vhd -s 20480 > 2. xm create test.hvm > 3. install Windows 2008 R2 Standard Edition 64 ( disk size: 20G, C:\ 15G, > D:\ 5G ) > 4. can not startup > 5. xm des test.vhd > 6. tapdisk2 -n vhd:/mnt/img/test.vhd > 7. mount -o offset=105906176 -t ntfs /dev/xen/blktap-2/tapdev0 /mnt/vhd > 8. ll /mnt/vhd/Windows/System32 | grep ? > ?--------- ? ? ? ? ? pnpts.dll > ?--------- ? ? ? ? ? pnpui.dll > ?--------- ? ? ? ? ? PnPUnattend.exe > ?--------- ? ? ? ? ? PnPutil.exe > > Additional info: > I install > Windows 2003 Standard Edition SP1 32(disk size: 50G, C:\50G) on vhd file, > the problem disappear. > Redhat 5.4 AS 64(disk size:60G, /: 50G, swap: 10G) on vhd file, the > problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 100G) on vhdfile, the problem > disappear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 90G, D:\10G) on > vhd file, the problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on > raw file, the problem disappear. > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on vhd > file, the problem appear. > Windows 2008 R2 Standard Edition 64(disk size: 100G, C:\ 15G, D:\85G) on > vhd file, the problem appear. > > ps: > windows 2003 need 3G disk space. > redhat 5.4 need 4G disk space. > windows 2008 need 8G disk space. > the problem disappear means that os can startup and no data error. > > compile env and filesystem : > Redhat AS 5.4 > > xm info: > host : vm01 > release : 2.6.31.13 > version : #1 SMP Wed Apr 21 12:30:21 CST 2010 > machine : x86_64 > nr_cpus : 16 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 2 > cpu_mhz : 2400 > hw_caps : > bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 24539 > free_memory : 1668 > node_to_cpu : node0:0-15 > node_to_memory : node0:1668 > node_to_dma32_mem : node0:82 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .0 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : dom0_max_vcpus=2 dom0_vcpus_pin > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) > cc_compile_by : root > cc_compile_domain : dev.sd.test.com > cc_compile_date : Mon Apr 26 10:17:37 CST 2010 > xend_config_format : 4 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
yingbin wang
2010-Jun-12 05:04 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
hi, had you created the patch to make tapdisk run the device queue synchronously? if yes, could you tell me how to get it? thanks wyb 2010/5/10 Daniel Stodden <daniel.stodden@citrix.com>:> On Sun, 2010-05-09 at 15:03 -0400, Heiko Wundram wrote: >> As I''m seeing a similar behavior of tapdisk2 (see my recent posts to xen-users, especially "blktap2, also broken in current pv_ops stable-2.6.32.x?"), I can confirm that at least in my testing (I''ve done some more over the weekend, re. that message), this is indeed an "SMP-related" problem, but only for HVM-64bit domains. >> >> What I can basically say is that: >> >> 1) Uni/Multi/32-bit/64-bit PV domains run properly. >> 1) Uni-VCPU, 32-bit HVM domains run properly. >> 2) Multi-VCPU, 32-bit HVM domains run properly. >> 3) Uni-VCPU, 64-bit HVM domains run properly. >> 4) Multi-VCPU, 64-bit HVM domains cause tapdisk2 to segfault, sometimes, under heavy I/O, and if that happens, causes the Dom0-kernel to freeze/lock up, Bug, and/or all other kinds of undefined behavior, where I really haven''t made out a pattern yet. >> >> Interestingly, these errors do not happen when using the "normal" blkback-driver, and I''m very positive (at least that''s what happened during my testing) that it''s specific to Multi-VCPU, 64-bit HVM domains that the crash occurs, independent of the number of VCPUs bound to Dom0. > > Okay, one thing which was going to happen soon is a patch to make > tapdisk run the device queue synchronously. From your description I''m > just not very convinced that this resolves such issues as well. Looks > like it needs some 64 bit testing beforehand. > > Thanks for the hints. Does HVM up there mean it''s rather triggered by > qemu alone? Were you running pv drivers? > > Cheers, > Daniel > > > _______________________________________________ > 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
Daniel Stodden
2010-Jun-12 08:19 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sat, 2010-06-12 at 01:04 -0400, yingbin wang wrote:> hi, > had you created the patch to make tapdisk run the device queue synchronously? > if yes, could you tell me how to get it?Right. These were landed. Present xen-unstable.hg should be not as unstable as it says it is. Can you or Heiko build that and see if anything improved? I''m a bit short on time right now. If that doesn''t work for you, I''ll look into it myself. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
yingbin wang
2010-Jun-12 10:47 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
could you give me the exact changlog about the patch? 2010/6/12 Daniel Stodden <daniel.stodden@citrix.com>:> On Sat, 2010-06-12 at 01:04 -0400, yingbin wang wrote: >> hi, >> had you created the patch to make tapdisk run the device queue synchronously? >> if yes, could you tell me how to get it? > > Right. These were landed. Present xen-unstable.hg should be not as > unstable as it says it is. > > Can you or Heiko build that and see if anything improved? I''m a bit > short on time right now. > > If that doesn''t work for you, I''ll look into it myself. > > Daniel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2010-Jun-13 00:06 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sat, 2010-06-12 at 06:47 -0400, yingbin wang wrote:> could you give me the exact changlog about the patch?You want to get to the tip of these: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/dom0/backend/blktap2 Which ones you''re missing depends on what kernel you already got. What are you running? Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
yingbin wang
2010-Jun-13 03:01 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
I know what you mean. now I know the patchs are in /heads/xen/dom0/backend/blktap2. do I need to get patchs from other places? or only in /heads/xen/dom0/backend/blktap2? ps: you say present xen-unstable.hg should be not as unstable as it says it is. I don''t know there is a head about blktap2 in xen.git before, so it makes me think the patch is in xen-unstable.hg. 2010/6/13 Daniel Stodden <daniel.stodden@citrix.com>:> On Sat, 2010-06-12 at 06:47 -0400, yingbin wang wrote: >> could you give me the exact changlog about the patch? > > You want to get to the tip of these: > > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/dom0/backend/blktap2 > > Which ones you''re missing depends on what kernel you already got. > What are you running? > > Daniel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2010-Jun-13 09:23 UTC
Re: AW: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sat, 2010-06-12 at 23:01 -0400, yingbin wang wrote:> I know what you mean. now I know the patchs are in > /heads/xen/dom0/backend/blktap2. > do I need to get patchs from other places? or only in > /heads/xen/dom0/backend/blktap2?Try those first. *Should* work okay [, but didn''t get a lot of testing.] There are a couple more kernel updates coming, which should further improve interfacing with older installations.> ps: > you say present xen-unstable.hg should be not as unstable as it says it is. > I don''t know there is a head about blktap2 in xen.git before, so it > makes me think the patch is in xen-unstable.hg.No, the changes you were after are only in the kernel. The userspace part, including tapdisk, didn''t change much since then. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel