On Tue, Jul 28, 2009 at 02:03:10AM -0300, Lucas Meneghel Rodrigues wrote: > On Thu, Jul 23, 2009 at 4:18 AM, Yolkfull Chow<yzhou@xxxxxxxxxx> wrote: > >>> Hi Yaniv, following is the output from Windows guest: > >>> > >>> --- > >>> Microsoft DiskPart version 6.0.6001 > >>> Copyright (C) 1999-2007 Microsoft Corporation. > >>> On computer: WIN-Q18A9GP5ECI > >>> > >>> Disk 1 is now the selected disk. > >>> > >>> DiskPart has encountered an error: The media is write protected. > >>> See the System Event Log for more information. > >>> > >>> Have you ever seen this error during format newly added SCSI block > >>> device? > >>> > >>> The contents of my diskpart script file: > >>> --- > >>> select disk 1 > >>> > >> > >> online > >> > >>> create partition primary > >>> exit > >>> --- > >>> > >>> > >> I didn't use a script - nor have I ever hot-plugged a disk, but it does > >> seem to happen to me as well now - the 2nd disk (the first is IDE) is > >> indeed seems to be R/O. > >> I'll look into it. > > > > Hi Lucas, did you notice this problem happened on Windows guest? What's > > your opinion about the patch pci_hotplug,send or wait? > > Hi Yolkfull, sorry for the delay answering. Yes, I did see the problem > on windows guests. About the test itself, it looks good and I am > making more tests before integrating it. Interestingly I tried it with > older fedora versions and lspci doesn't seem to be able to recognize > the newly added devices. High time we add step files and data for F10 > and F11 on the default config file. > > > I think I can still send the patch for now, and just use 'detail disk' which doesn't format the newly added > > disk in diskpart script. As soon as we have a solution, I can submit a > > patch to fix it. Moreover, nic_virtio and block_virtio for Windows section will be > > disabled in config file as well since both drivers don't work well now. > > Ok, if you have an updated patch, please send it. Let's try to get all > the problems addressed as soon as possible. > > Thanks for your work on this! Ok, I will post it here soon after I finish current case. Thanks, Lucas. :-) Regards, -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
