From: Yaniv Kaul <ykaul@redhat.com>
To: Yolkfull Chow <yzhou@redhat.com>
Cc: kvm@vger.kernel.org, lmr@redhat.com, autotest@test.kernel.org,
Vadim Rozenfeld <vrozenfe@redhat.com>
Subject: Re: [PATCH] Add a kvm subtest -- pci_hotplug, which supports both Windows OS and Linux OS.
Date: Tue, 21 Jul 2009 10:45:31 +0300 [thread overview]
Message-ID: <4A65721B.9070002@redhat.com> (raw)
In-Reply-To: <20090721061121.GA5975@dhcp-66-70-57.nay.redhat.com>
On 7/21/2009 9:11 AM, Yolkfull Chow wrote:
<SNIP>
>
>>>
>>>
>>>>> Previously, I used 'create partition primary' to verify whether the disk could be formatted but always got an error:
>>>>> ---
>>>>> diskpart has encountered an error...
>>>>> ---
>>>>> And then I found the SCSI disk was added to Windows guest was read-only. So I changed the format command to be 'detail disk' temporarily.
>>>>>
>>>>>
>>>>>
>>>> Interesting - how did that happen? Lets see your command line, and
>>>> probably 'info block' from the monitor. Are you saying that hot-plugged
>>>> drives are added as r/o?
>>>>
>>>>
>>> I am afraid yes. After pci_add (monitor command: pci_add pci_addr=auto storage
>>> file=/tmp/stg.qcow2,if=scsi) the SCSI block device, 'info block' will
>>> show the scsi0-hd0 device is 'ro=0' whereas when I 'create partition
>>> primary' on this selected disk in diskpart tool, error message will be raised that the disk is
>>> write protected.
>>>
>>>
>> Well, that doesn't sound like the desired behavior. Work with the KVM
>> developers on this.
>>
> 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.
>>
>>>
>>>
>>>> Also, you can always add an already formatted drive. Just create a qcow
>>>> drive in another instance, format it properly and use it.
>>>>
>>>>
>>>>
Any result with an already formatted drive?
Y.
next parent reply other threads:[~2009-07-21 7:45 UTC|newest]
Thread overview: 8+ 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 ` Yaniv Kaul [this message]
2009-07-21 8:29 ` [PATCH] Add a kvm subtest -- pci_hotplug, which supports both Windows OS and Linux OS 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
2009-07-15 3:49 Yolkfull Chow
2009-07-15 9:46 ` Yaniv Kaul
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=4A65721B.9070002@redhat.com \
--to=ykaul@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=vrozenfe@redhat.com \
--cc=yzhou@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