From: Yolkfull Chow <yzhou@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: autotest@test.kernel.org, Vadim Rozenfeld <vrozenfe@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [Autotest] [PATCH] Add a kvm subtest -- pci_hotplug, which supports both Windows OS and Linux OS.
Date: Tue, 28 Jul 2009 17:01:59 +0800 [thread overview]
Message-ID: <20090728090159.GA5751@aFu.nay.redhat.com> (raw)
In-Reply-To: <6ac58f4f0907272203n8ee1a4aue2add1fd31163583@mail.gmail.com>
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@redhat.com> 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,
prev parent reply other threads:[~2009-07-28 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1283926593.702711248067671557.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
[not found] ` <4A64032A.8090804@redhat.com>
[not found] ` <20090720070110.GA17650@aFu.nay.redhat.com>
[not found] ` <4A641AD4.2030502@redhat.com>
[not found] ` <20090721061121.GA5975@dhcp-66-70-57.nay.redhat.com>
2009-07-21 7:45 ` [PATCH] Add a kvm subtest -- pci_hotplug, which supports both Windows OS and Linux OS Yaniv Kaul
2009-07-21 8:29 ` Yolkfull Chow
2009-07-21 9:01 ` Yolkfull Chow
2009-07-23 7:18 ` Yolkfull Chow
2009-07-28 5:03 ` [Autotest] " Lucas Meneghel Rodrigues
2009-07-28 9:01 ` Yolkfull Chow [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090728090159.GA5751@aFu.nay.redhat.com \
--to=yzhou@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=vrozenfe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox