| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Has anyone installed from an XP Pro "upgrade" disk
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jim Lynch
> Sent: 18 January 2007 13:59
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Has anyone installed from an XP Pro
> "upgrade" disk
>
> Petersson, Mats wrote:
> >> -----Original Message-----
> >> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> >> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> Of Jim Lynch
> >> Sent: 17 January 2007 11:34
> >> To: xen-users@xxxxxxxxxxxxxxxxxxx
> >> Subject: [Xen-users] Has anyone installed from an XP Pro
> >> "upgrade" disk
> >>
> >> I don't have a full install, just the upgrade. I tried to
> insert the
> >> windows 98 disk but it didn't find that, I tried to dd a
> working win98
> >> partition to an image and use it as the image file,
> thinking XP might
> >> read that file, but that didn't work. I also tried to install
> >> Win98 but
> >> it failed because it tried to load a driver to read the cdrom and
> >> couldn't.
> >>
> >
> > I definitely haven't tried this, but I don't see why it
> shouldn't work
> > (except perhaps Win98 is too similar to Win 3.1 and uses
> based segments
> > rather more than WinXP/NT type OS's).
> >
> > A driver to read the CDROM should work just fine.
> >
> > --
> > Mats
> >
> When the 98 cd boots, it starts in a dos window and attempts to load a
> generic cdrom driver, but eventually fails with a message
> suggesting it
> can't find a drive. I don't know enough about how a disk is
> "virtualized" to know if this generic driver will find
> anything. Win98
> came about before it was common to have BIOSs that knew about CDROM
> drives, if I recall correctly.
BIOS may not know about CDROM drive in ancient times, but the CDROM
driver (assuming it's an IDE one) should be able to identify the
emulated CDROM device [Do you add the ":cdrom" to your cdrom device in
the config file? - Otherwise it may not work].
The HVM domain just passes the device accesses to qemu, and it's
forwarding that to the Dom0 device itself after some translation, but
any identification should work just fine [unless of course the driver is
looking for something very particular in the device profile which isn't
satisfied by the emulated device, but I doubt it].
It may of course be that the driver doesn't play clean with regards to
how it accesses the device, or it may be that the driver is doing stuff
that the real-mode emulator (on Intel) doesn't like, for example.
--
Mats
>
> Jim.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home