I''m trying to mount an additional unformatted drive for a windows
Server
instances but the instance doesnt'' seem to see it.
The xml looks like:
<disk type=''file'' device=''disk''>
<driver name=''file''/>
<source file=''/files/vdsk/win2k3Server-1.img''/>
<target dev=''hda''/>
</disk>
<disk type=''file'' device=''cdrom''>
<driver name=''file''/>
<source
file=''/files/images/windows/win2k3_r2_std_d2.iso''/>
<target dev=''hdc''/>
<readonly/>
</disk>
<disk type=''file'' device=''disk''>
<driver name=''file''/>
<source file=''/files/vdsk/magic.img''/>
<target dev=''hdb''/>
</disk>
While both hda and hdc are present, hdb is not detected. Is this a known
problem or have a cocked something up? magic.img is a raw and unformatted.
2nd Question, I note from the Win PV driver doc that using Fat32 as the
boot partition results in a blue screen (CR 6746380). If I were to
mount this 2nd disk as a FAT32 would I see the same behavior? I.e. is
there a general problem with fat32 or is it only related to having to
boot from it?
TIA!
=Ron=
Hi Ron, How did you add the disk? Did you use virsh to modify the existing domain, or did you tinker with the XML directly? What happens if you put the hdb device before hdc, so the list is sorted? [shouldn''t matter, but there could be a bug there] - R Ronald J Mann wrote:> I''m trying to mount an additional unformatted drive for a windows Server > instances but the instance doesnt'' seem to see it. > > The xml looks like: > <disk type=''file'' device=''disk''> > <driver name=''file''/> > <source file=''/files/vdsk/win2k3Server-1.img''/> > <target dev=''hda''/> > </disk> > <disk type=''file'' device=''cdrom''> > <driver name=''file''/> > <source file=''/files/images/windows/win2k3_r2_std_d2.iso''/> > <target dev=''hdc''/> > <readonly/> > </disk> > <disk type=''file'' device=''disk''> > <driver name=''file''/> > <source file=''/files/vdsk/magic.img''/> > <target dev=''hdb''/> > </disk> > > > While both hda and hdc are present, hdb is not detected. Is this a known > problem or have a cocked something up? magic.img is a raw and unformatted. > > 2nd Question, I note from the Win PV driver doc that using Fat32 as the > boot partition results in a blue screen (CR 6746380). If I were to > mount this 2nd disk as a FAT32 would I see the same behavior? I.e. is > there a general problem with fat32 or is it only related to having to > boot from it? > > TIA! > > =Ron> > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- ----------------------------------------------------- Russ Blaine | Solaris Kernel | russell.blaine@sun.com
Hi Russ, I actually tried both using the attach-disk command as well as dumpxml and editing. When I edited, the list was ordered, using attach-disk, the entry was appended to the end of the list. This morning I tried removing the cdrom entry to see if that had any effect. While the cdrom did indeed disappear, unfortunately the second hd definition still dod not show up. I should probably mention that this is b99 and that I have installed the PV drivers as well. Any other windows experimenters out there gotten this to work -or- should I file a bug? =Ron Russ Blaine wrote:> Hi Ron, > > How did you add the disk? Did you use virsh to modify the existing > domain, or did you tinker with the XML directly? What happens if you > put the hdb device before hdc, so the list is sorted? [shouldn''t > matter, but there could be a bug there] > > - R > > Ronald J Mann wrote: >> I''m trying to mount an additional unformatted drive for a windows >> Server instances but the instance doesnt'' seem to see it. >> >> The xml looks like: >> <disk type=''file'' device=''disk''> >> <driver name=''file''/> >> <source file=''/files/vdsk/win2k3Server-1.img''/> >> <target dev=''hda''/> >> </disk> >> <disk type=''file'' device=''cdrom''> >> <driver name=''file''/> >> <source file=''/files/images/windows/win2k3_r2_std_d2.iso''/> >> <target dev=''hdc''/> >> <readonly/> >> </disk> >> <disk type=''file'' device=''disk''> >> <driver name=''file''/> >> <source file=''/files/vdsk/magic.img''/> >> <target dev=''hdb''/> >> </disk> >> >> >> While both hda and hdc are present, hdb is not detected. Is this a >> known problem or have a cocked something up? magic.img is a raw and >> unformatted. >> >> 2nd Question, I note from the Win PV driver doc that using Fat32 as >> the boot partition results in a blue screen (CR 6746380). If I were >> to mount this 2nd disk as a FAT32 would I see the same behavior? I.e. >> is there a general problem with fat32 or is it only related to having >> to boot from it? >> >> TIA! >> >> =Ron>> >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >
Mea culpa. I suspect a lack of familiarity with some of the management aspects of Windows Server on my part is the rub. After this mornings doodling, I can now see a second hard disk under the disk drives portion of the device manager. Thanks for your help! =Ron Ronald J Mann wrote:> Hi Russ, > > I actually tried both using the attach-disk command as well as dumpxml > and editing. When I edited, the list was ordered, using attach-disk, the > entry was appended to the end of the list. This morning I tried removing > the cdrom entry to see if that had any effect. While the cdrom did > indeed disappear, unfortunately the second hd definition still dod not > show up. I should probably mention that this is b99 and that I have > installed the PV drivers as well. Any other windows experimenters out > there gotten this to work -or- should I file a bug? > > =Ron> > Russ Blaine wrote: > >> Hi Ron, >> >> How did you add the disk? Did you use virsh to modify the existing >> domain, or did you tinker with the XML directly? What happens if you >> put the hdb device before hdc, so the list is sorted? [shouldn''t >> matter, but there could be a bug there] >> >> - R >> >> Ronald J Mann wrote: >> >>> I''m trying to mount an additional unformatted drive for a windows >>> Server instances but the instance doesnt'' seem to see it. >>> >>> The xml looks like: >>> <disk type=''file'' device=''disk''> >>> <driver name=''file''/> >>> <source file=''/files/vdsk/win2k3Server-1.img''/> >>> <target dev=''hda''/> >>> </disk> >>> <disk type=''file'' device=''cdrom''> >>> <driver name=''file''/> >>> <source file=''/files/images/windows/win2k3_r2_std_d2.iso''/> >>> <target dev=''hdc''/> >>> <readonly/> >>> </disk> >>> <disk type=''file'' device=''disk''> >>> <driver name=''file''/> >>> <source file=''/files/vdsk/magic.img''/> >>> <target dev=''hdb''/> >>> </disk> >>> >>> >>> While both hda and hdc are present, hdb is not detected. Is this a >>> known problem or have a cocked something up? magic.img is a raw and >>> unformatted. >>> >>> 2nd Question, I note from the Win PV driver doc that using Fat32 as >>> the boot partition results in a blue screen (CR 6746380). If I were >>> to mount this 2nd disk as a FAT32 would I see the same behavior? I.e. >>> is there a general problem with fat32 or is it only related to having >>> to boot from it? >>> >>> TIA! >>> >>> =Ron>>> >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
And by way of atonement... I have formatted and accessed a FAT32 volume successfully, hopefully answering my original question #2. Is there some convenient way I can verify that in fact the PV drivers are in use? =Ron Ronald J Mann wrote:> Mea culpa. I suspect a lack of familiarity with some of the management > aspects of Windows Server on my part is the rub. After this mornings > doodling, I can now see a second hard disk under the disk drives portion > of the device manager. Thanks for your help! > > =Ron> > Ronald J Mann wrote: > >> Hi Russ, >> >> I actually tried both using the attach-disk command as well as dumpxml >> and editing. When I edited, the list was ordered, using attach-disk, the >> entry was appended to the end of the list. This morning I tried removing >> the cdrom entry to see if that had any effect. While the cdrom did >> indeed disappear, unfortunately the second hd definition still dod not >> show up. I should probably mention that this is b99 and that I have >> installed the PV drivers as well. Any other windows experimenters out >> there gotten this to work -or- should I file a bug? >> >> =Ron>> >> Russ Blaine wrote: >> >> >>> Hi Ron, >>> >>> How did you add the disk? Did you use virsh to modify the existing >>> domain, or did you tinker with the XML directly? What happens if you >>> put the hdb device before hdc, so the list is sorted? [shouldn''t >>> matter, but there could be a bug there] >>> >>> - R >>> >>> Ronald J Mann wrote: >>> >>> >>>> I''m trying to mount an additional unformatted drive for a windows >>>> Server instances but the instance doesnt'' seem to see it. >>>> >>>> The xml looks like: >>>> <disk type=''file'' device=''disk''> >>>> <driver name=''file''/> >>>> <source file=''/files/vdsk/win2k3Server-1.img''/> >>>> <target dev=''hda''/> >>>> </disk> >>>> <disk type=''file'' device=''cdrom''> >>>> <driver name=''file''/> >>>> <source file=''/files/images/windows/win2k3_r2_std_d2.iso''/> >>>> <target dev=''hdc''/> >>>> <readonly/> >>>> </disk> >>>> <disk type=''file'' device=''disk''> >>>> <driver name=''file''/> >>>> <source file=''/files/vdsk/magic.img''/> >>>> <target dev=''hdb''/> >>>> </disk> >>>> >>>> >>>> While both hda and hdc are present, hdb is not detected. Is this a >>>> known problem or have a cocked something up? magic.img is a raw and >>>> unformatted. >>>> >>>> 2nd Question, I note from the Win PV driver doc that using Fat32 as >>>> the boot partition results in a blue screen (CR 6746380). If I were >>>> to mount this 2nd disk as a FAT32 would I see the same behavior? I.e. >>>> is there a general problem with fat32 or is it only related to having >>>> to boot from it? >>>> >>>> TIA! >>>> >>>> =Ron>>>> >>>> >>>> _______________________________________________ >>>> xen-discuss mailing list >>>> xen-discuss@opensolaris.org >>>> >>>> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >> >> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
Answering my own question again, I can see that Device manager shows a driver list which includes xVMStorFlt.sys, so cool, it appears you can access a Fat32 file system with PV drivers installed. =Ron Ronald J Mann wrote:> And by way of atonement... I have formatted and accessed a FAT32 volume > successfully, hopefully answering my original question #2. Is there some > convenient way I can verify that in fact the PV drivers are in use? > > =Ron> >