Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008

[yingbin wang <yingbin.wangyb@xxxxxxxxx>]

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@xxxxxxxxxxxxx>

> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel