WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Windows 2000 DomU

I'm coming into this thread a bit late, and I'm not sure I'm right on topic, but hopefully this fits. From the following blog post, I gleaned some info about HALs and such:
http://ian.blenke.com/vmware/vmdk/xen/hvm/qemu/vmware_to_xen_hvm.html

In the end when I was doing that migration, I didn't use his methods (HALs turned out to be the same on both), due to a persistent BSOD. The first part of my solution:
-----------
Prepare the VMWare VM:
In the running VMWare VM, uninstall VMWare Tools.
'Upgrade' the driver of the IDE Controller to "Standard Dual Channel PCI IDE Controller" (by manually selecting it) but don't reboot. Shut down the machine.
-----------

After that, I just get the virtual machine contents over to the xen server (with dd in my case), configure it and power it on.

HTH,
Greg.

Antoine Benkemoun wrote:
Thank you for your help.

I am going to look at system state backup... never heard of this but it sounds pretty good to me.

I'll have a look at the boot.ini to see if that could solve it.

Antoine

On Wed, Jul 23, 2008 at 4:42 PM, Dustin Henning <Dustin.Henning@xxxxxxxxxxx <mailto:Dustin.Henning@xxxxxxxxxxx>> wrote:

           Another possibility would be installing Windows 2000 on Xen
    instead of migrating it, then doing a backup on the real machine and
    restore on the xen machine, my understanding is that the system
    state portion of the backup will leave drivers alone so you can
    restore to another system.  I have seen this suggested as a way to
    migrate to other virtual scenarios, so I would think it would work
    here as well.  You might want to do a web search on migration and/or
    system state backups to find a good list of steps, and an install
    followed by a backup and restore might then be as fast as a making
    an image and then doing a repair (and perhaps cleaner to boot).
           It is also possible that you have Windows 2000 on SATA or
    SCSI with SCSI drivers, in which case you would need to change your
    boot.ini similar to the following:
    Before: scsi(0)disk(0)rdisk(0)partition(1)
    After: multi(0)disk(0)rdisk(0)partition(1)
    This change alone may not resolve your issue, though, because the
    drivers still might not match up, but it would be worth checking
    your boot.ini and if it has scsi, trying that before the more in
    depth suggestions from myself and others.
           Dustin


    -----Original Message-----
    From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
    <mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx>
    [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx
    <mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx>] On Behalf Of
    Fernando Jiménez Solano
    Sent: Tuesday, July 22, 2008 09:55
    To: James Dingwall; Antoine Benkemoun; xen-users@xxxxxxxxxxxxxxxxxxx
    <mailto:xen-users@xxxxxxxxxxxxxxxxxxx>
    Subject: Re: [Xen-users] Windows 2000 DomU

    I also had that problem. A workaround that fixed was repairing from the
    Windows 2000
    CD, then it went all just fine.



    On Tue, 22 Jul 2008 15:34:29 +0200, James Dingwall
    <james.dingwall@xxxxxxxxxx <mailto:james.dingwall@xxxxxxxxxx>> wrote:

     > I am doing tests to convert old rotting servers into a big shiny
    new Xen
     > platform. I have been able to migrate a Windows 2003 server without a
     > scratch. I am trying to do the same thing with Windows 2000
    Server but
     > things aren't so great...
     >
     > I made an image from the disk that worked in a machine. Then I
    boot on
     > this image using Xen. Windows 2000 starts to boot up then give me
    a BSOD
     > stating UNACESSIBLE_BOOT_DEVICE.
     >
     > Has anybody encountered this error before ?
     >
     > Thank you in advance for your help,
     >
     >
     >
     > Were you using an IDE disk on the original machine?  There is a
    problem
     > moving 2000/XP system disks between computers when the IDE
    devices are
     > different.  You can fix this by importing some additional
    registry keys
     > before moving the drive or taking the image:
     >
     > Windows 2000: http://support.microsoft.com/kb/822052/en-us
     > Windows XP: http://support.microsoft.com/kb/314082
     >
     > Alternatively I don't know if you can change the IDE device that Xen
     > will emulate to match the source hardware.
     >
     > James
     >
     > This message and the information contained herein is proprietary and
     > confidential and subject to the Amdocs policy statement,
     > you may review at http://www.amdocs.com/email_disclaimer.asp
     >
     > _______________________________________________
     > Xen-users mailing list
     > Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
     > http://lists.xensource.com/xen-users
     >



    --
    Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

    _______________________________________________
    Xen-users mailing list
    Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
    http://lists.xensource.com/xen-users





--
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


------------------------------------------------------------------------

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


--
   - ---- -----
     Gregory Orange             Phone: +61 8 9387 7955
    System Administrator            Fax: +61 8 9387 6686
   RPS MetOcean                        http://www.rpsmetocean.com.au
  System Administrators Guild of Australia  http://www.sage-au.org.au
- ---- -----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>