[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [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@xxxxxxxxx>
Attachment:
BlktapController.py _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |