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 > [email protected] -- ----------------------------------------------------- Russ Blaine | Solaris Kernel | [EMAIL PROTECTED] _______________________________________________ xen-discuss mailing list [email protected]
