Xen users - Dec 2009 - can Xen coexist/cooperate with a windows/linux dual-boot system?

I have a dual-boot setup, using grub, that I''m attempting to convert to
a dual-boot plus xen setup. I''m running openSuSE 11.2 with the
2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is partitioned as:
sda1 - xp (ntfs)
sda2 - extended partition
sda5 - /windows/D (fat32)
sda6 - swap
sda7 - / (ext4)
sda8 - /home (ext4)

I''ve configured the windows xp vm as:
name="windowsxp"
uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
memory=512
maxmem=512
vcpus=2
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=1
keymap="en-us"

builder="hvm"
extid=0
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ ''phy:/dev/sda1,hda1,w'', ]
vif=[ ''bridge=br0,model=rtl8139'', ]

stdvga=0
vnc=1
vncunused=1
apic=1
acpi=1
pae=1

usb=1
usbdevice=''tablet''

serial="pty"

When I attempt to run the windows xp vm the console shows "booting from
hard disk...", the cpu usage goes to 100%, and that''s as far as it
gets.
(I''ve tried multiple different "disk=..." combinations, this
is just the
latest, but I get the same results from all of them.)

Any ideas on how I might fix this? (it would seem that however xen tries
to boot windows xp, it''s not as effective as grub''s
chainloader.)


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

The challenge in this sort of setup is that the hardware configuration that
Windows was installed onto and the hardware configuration that Xen presents to
HVM-based domUs is different - in some cases very different.  For example, if
you''re running modern hardware, you probably have a SATA disk, which is
usually seen by O/Ss as a SCSI-type controller with SCSI disks.  However, HVM
domUs use IDE-based controllers and disks, which means booting is going to have
issues seeing the change.  There are also differences in the chipset, network
controllers, etc., that need to be seen correctly by Windows before it boots.

One of the basic things is to try converting the SCSI-based disk setup to IDE -
there are instructions on Microsoft''s support site for doing this.  The
downside to this is that you probably won''t be able to boot Windows
back on the original hardware outside of the VM after this change - Windows is
not very flexible in terms of differing hardware configurations outside of your
basic docked and undocked laptop modes.

Note that this also may pose licensing issues - usually machines that come with
Windows are installed using an OEM license, which licenses Windows to run on the
original hardware only.  Using this same copy of Windows to run in a domU is
likely a violation of the OEM license - you need another, full retail or volume
license for Windows to run as a VM.

-Nick
>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com> wrote:
> I have a dual-boot setup, using grub, that I''m attempting to
convert to
> a dual-boot plus xen setup. I''m running openSuSE 11.2 with the
> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is partitioned as:
> sda1 - xp (ntfs)
> sda2 - extended partition
> sda5 - /windows/D (fat32)
> sda6 - swap
> sda7 - / (ext4)
> sda8 - /home (ext4)
> 
> I''ve configured the windows xp vm as:
> name="windowsxp"
> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
> memory=512
> maxmem=512
> vcpus=2
> on_poweroff="destroy"
> on_reboot="restart"
> on_crash="destroy"
> localtime=1
> keymap="en-us"
> 
> builder="hvm"
> extid=0
> device_model="/usr/lib/xen/bin/qemu-dm"
> kernel="/usr/lib/xen/boot/hvmloader"
> boot="c"
> disk=[ ''phy:/dev/sda1,hda1,w'', ]
> vif=[ ''bridge=br0,model=rtl8139'', ]
> 
> stdvga=0
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> 
> usb=1
> usbdevice=''tablet''
> 
> serial="pty"
> 
> When I attempt to run the windows xp vm the console shows "booting
from
> hard disk...", the cpu usage goes to 100%, and that''s as far
as it gets.
> (I''ve tried multiple different "disk=..." combinations,
this is just the
> latest, but I get the same results from all of them.)
> 
> Any ideas on how I might fix this? (it would seem that however xen tries
> to boot windows xp, it''s not as effective as grub''s
chainloader.)


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

thanks for the response, but it leaves me wondering what''s the point of
full virtualization.  I can install the tweaked  OS for
paravirtualization, or I can tweak the hardware configuration for an
already installed OS for full virtualization.  Either way I can''t go
back to the original OS when I, as occasionally happens, get my linux
system hosed up.


Nick Couchman wrote:
> The challenge in this sort of setup is that the hardware configuration that
Windows was installed onto and the hardware configuration that Xen presents to
HVM-based domUs is different - in some cases very different.  For example, if
you''re running modern hardware, you probably have a SATA disk, which is
usually seen by O/Ss as a SCSI-type controller with SCSI disks.  However, HVM
domUs use IDE-based controllers and disks, which means booting is going to have
issues seeing the change.  There are also differences in the chipset, network
controllers, etc., that need to be seen correctly by Windows before it boots.
>
> One of the basic things is to try converting the SCSI-based disk setup to
IDE - there are instructions on Microsoft''s support site for doing
this.  The downside to this is that you probably won''t be able to boot
Windows back on the original hardware outside of the VM after this change -
Windows is not very flexible in terms of differing hardware configurations
outside of your basic docked and undocked laptop modes.
>
> Note that this also may pose licensing issues - usually machines that come
with Windows are installed using an OEM license, which licenses Windows to run
on the original hardware only.  Using this same copy of Windows to run in a domU
is likely a violation of the OEM license - you need another, full retail or
volume license for Windows to run as a VM.
>
> -Nick
>
>   
>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com> wrote:
>>>>         
>> I have a dual-boot setup, using grub, that I''m attempting to
convert to
>> a dual-boot plus xen setup. I''m running openSuSE 11.2 with the
>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is partitioned
as:
>> sda1 - xp (ntfs)
>> sda2 - extended partition
>> sda5 - /windows/D (fat32)
>> sda6 - swap
>> sda7 - / (ext4)
>> sda8 - /home (ext4)
>>
>> I''ve configured the windows xp vm as:
>> name="windowsxp"
>> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>> memory=512
>> maxmem=512
>> vcpus=2
>> on_poweroff="destroy"
>> on_reboot="restart"
>> on_crash="destroy"
>> localtime=1
>> keymap="en-us"
>>
>> builder="hvm"
>> extid=0
>> device_model="/usr/lib/xen/bin/qemu-dm"
>> kernel="/usr/lib/xen/boot/hvmloader"
>> boot="c"
>> disk=[ ''phy:/dev/sda1,hda1,w'', ]
>> vif=[ ''bridge=br0,model=rtl8139'', ]
>>
>> stdvga=0
>> vnc=1
>> vncunused=1
>> apic=1
>> acpi=1
>> pae=1
>>
>> usb=1
>> usbdevice=''tablet''
>>
>> serial="pty"
>>
>> When I attempt to run the windows xp vm the console shows "booting
from
>> hard disk...", the cpu usage goes to 100%, and that''s as
far as it gets.
>> (I''ve tried multiple different "disk=..."
combinations, this is just the
>> latest, but I get the same results from all of them.)
>>
>> Any ideas on how I might fix this? (it would seem that however xen
tries
>> to boot windows xp, it''s not as effective as grub''s
chainloader.)
>>     
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
use of the intended recipient.  If this email is not intended for you, or you
are not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
>
>   

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

The point of full virtualization is that there are certain operating systems
that cannot run as paravirtualized VMs.  Windows, for example, must run in a
full virtualization environment - Microsoft has not provided (and is not likely
to provide) a paravirtual kernel for Windows.  Windows Server 2008 has an
"enlightened" mode that switches drivers from full emulation to
paravirtual mode when it detects a hypervisor like VMware or Xen; however, even
this "enlightened" version of Windows still requires a full virtual
machine.

-Nick
>>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com> wrote:
> thanks for the response, but it leaves me wondering what''s the
point of
> full virtualization.  I can install the tweaked  OS for
> paravirtualization, or I can tweak the hardware configuration for an
> already installed OS for full virtualization.  Either way I can''t
go
> back to the original OS when I, as occasionally happens, get my linux
> system hosed up.
> 
> 
> Nick Couchman wrote:
>> The challenge in this sort of setup is that the hardware configuration
that
> Windows was installed onto and the hardware configuration that Xen presents
> to HVM-based domUs is different - in some cases very different.  For
example,
> if you''re running modern hardware, you probably have a SATA disk,
which is
> usually seen by O/Ss as a SCSI-type controller with SCSI disks.  However,
HVM
> domUs use IDE-based controllers and disks, which means booting is going to 
> have issues seeing the change.  There are also differences in the chipset, 
> network controllers, etc., that need to be seen correctly by Windows before
> it boots.
>>
>> One of the basic things is to try converting the SCSI-based disk setup
to IDE
> - there are instructions on Microsoft''s support site for doing
this.  The
> downside to this is that you probably won''t be able to boot
Windows back on
> the original hardware outside of the VM after this change - Windows is not 
> very flexible in terms of differing hardware configurations outside of your
> basic docked and undocked laptop modes.
>>
>> Note that this also may pose licensing issues - usually machines that
come
> with Windows are installed using an OEM license, which licenses Windows to 
> run on the original hardware only.  Using this same copy of Windows to run
in
> a domU is likely a violation of the OEM license - you need another, full 
> retail or volume license for Windows to run as a VM.
>>
>> -Nick
>>
>>   
>>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com> wrote:
>>>>>         
>>> I have a dual-boot setup, using grub, that I''m attempting
to convert to
>>> a dual-boot plus xen setup. I''m running openSuSE 11.2 with
the
>>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is
partitioned as:
>>> sda1 - xp (ntfs)
>>> sda2 - extended partition
>>> sda5 - /windows/D (fat32)
>>> sda6 - swap
>>> sda7 - / (ext4)
>>> sda8 - /home (ext4)
>>>
>>> I''ve configured the windows xp vm as:
>>> name="windowsxp"
>>> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>>> memory=512
>>> maxmem=512
>>> vcpus=2
>>> on_poweroff="destroy"
>>> on_reboot="restart"
>>> on_crash="destroy"
>>> localtime=1
>>> keymap="en-us"
>>>
>>> builder="hvm"
>>> extid=0
>>> device_model="/usr/lib/xen/bin/qemu-dm"
>>> kernel="/usr/lib/xen/boot/hvmloader"
>>> boot="c"
>>> disk=[ ''phy:/dev/sda1,hda1,w'', ]
>>> vif=[ ''bridge=br0,model=rtl8139'', ]
>>>
>>> stdvga=0
>>> vnc=1
>>> vncunused=1
>>> apic=1
>>> acpi=1
>>> pae=1
>>>
>>> usb=1
>>> usbdevice=''tablet''
>>>
>>> serial="pty"
>>>
>>> When I attempt to run the windows xp vm the console shows
"booting from
>>> hard disk...", the cpu usage goes to 100%, and that''s
as far as it gets.
>>> (I''ve tried multiple different "disk=..."
combinations, this is just the
>>> latest, but I get the same results from all of them.)
>>>
>>> Any ideas on how I might fix this? (it would seem that however xen
tries
>>> to boot windows xp, it''s not as effective as
grub''s chainloader.)
>>>     
>>
>>
>>
>> --------
>> This e-mail may contain confidential and privileged material for the
sole use
> of the intended recipient.  If this email is not intended for you, or you
are
> not responsible for the delivery of this message to the intended recipient,
> please note that this message may contain SEAKR Engineering (SEAKR) 
> Privileged/Proprietary Information.  In such a case, you are strictly 
> prohibited from downloading, photocopying, distributing or otherwise using 
> this message, its contents or attachments in any way.  If you have received
> this message in error, please notify us immediately by replying to this
e-mail
> and delete the message from your mailbox.  Information contained in this 
> message that does not relate to the business of SEAKR is neither endorsed
by
> nor attributable to SEAKR.
>>
>>   

--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

On Mon, Dec 28, 2009 at 9:34 AM, richard heade <richard.heade@gmail.com>
wrote:
> thanks for the response, but it leaves me wondering what''s the
point of
> full virtualization.
Let''s see ... hardware consolidation? cloud computing? hosted vps?
> I can install the tweaked  OS for
> paravirtualization, or I can tweak the hardware configuration for an
> already installed OS for full virtualization.  Either way I can''t
go
> back to the original OS when I, as occasionally happens, get my linux
> system hosed up.
That''s because you use windows. Seriously.
You should ask MS if they provide a solution for what you''re trying to
achieve, but I doubt you''d get satisfactory response even with their
Hyper-V.

As a side note, you could try something like this

disk=[ ''phy:/dev/sda,hda,w'', ]
apic=1
acpi=1
pae=1

if your Windows already has support for IDE drives as Nick mentioned
(also see http://www.virtualbox.org/wiki/Migrate_Windows), you should
be able to get Windows to run. BE VERY CAREFUL though, as it should
initially invoke grub (just like when you boot normally), but you MUST
choose Windows entry. If you accidently let it boot Linux, you''ll be
mounting the Linux filesystem twice (one on your dom0, one on your
domU) which is a sure recipe for corruption.

A little extra note about dom0 recovery, if for whatever reason your
dom0 is hosed up, you can easily run your domU elsewhere provided that
you have backup or access to:
- domU''s disk storage (in your example it''s /dev/sda1)
- domU''s config file
- dom0 and domU''s networking setup (well, mostly it''s a matter
of
making sure domU is connected to the correct bridge)

-- 
Fajar

-- 
Fajar

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

>>> On 2009/12/27 at 20:22, "Fajar A. Nugraha"
<fajar@fajar.net> wrote:
> On Mon, Dec 28, 2009 at 9:34 AM, richard heade
<richard.heade@gmail.com> wrote:
>> thanks for the response, but it leaves me wondering what''s the
point of
>> full virtualization.
> 
> Let''s see ... hardware consolidation? cloud computing? hosted vps?
I think the question, more specifically, is why use full virutalization (HVM)
instead of paravirtualization?  The answers you gave apply to the question,
"Why use virtualization at all?"  However, as far as Full vs. Para,
the answer is that Paravirtualization is much more efficient in resource
utilization, but full virtualization allows for running operating systems that
are not "aware" of the fact that they are virtualized or are not
compatible with Xen''s idea of paravirtualization.
> 
>> I can install the tweaked  OS for
>> paravirtualization, or I can tweak the hardware configuration for an
>> already installed OS for full virtualization.  Either way I
can''t go
>> back to the original OS when I, as occasionally happens, get my linux
>> system hosed up.
> 
> That''s because you use windows. Seriously.
> You should ask MS if they provide a solution for what you''re
trying to
> achieve, but I doubt you''d get satisfactory response even with
their
> Hyper-V.
Ha!  I''d love to see Microsoft provide a Xen-compatible PV kernel, but
I''m not holding my breath - I can see them only doing this in a Hyper-V
world, but I think "enlightened" Windows essentially already does
this.  Unfortunately it isn''t a true PV kernel, which means you still
need HVM support for Xen.

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

I''ve read about the enlightened mode before but poking around in
windows I
wasn''t able to find it. Is it in all versions of server 2008 or just
certain
editions? What if anything needs to be done to activate this? How does it
compare to gplpv? I''d be curious to play around with it but
haven''t found
any specifics.

Chris

On Mon, Dec 28, 2009 at 1:17 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> >>> On 2009/12/27 at 20:22, "Fajar A. Nugraha"
<fajar@fajar.net> wrote:
> > On Mon, Dec 28, 2009 at 9:34 AM, richard heade
<richard.heade@gmail.com>
> wrote:
> >> thanks for the response, but it leaves me wondering
what''s the point of
> >> full virtualization.
> >
> > Let''s see ... hardware consolidation? cloud computing? hosted
vps?
>
> I think the question, more specifically, is why use full virutalization
> (HVM) instead of paravirtualization?  The answers you gave apply to the
> question, "Why use virtualization at all?"  However, as far as
Full vs.
> Para, the answer is that Paravirtualization is much more efficient in
> resource utilization, but full virtualization allows for running operating
> systems that are not "aware" of the fact that they are
virtualized or are
> not compatible with Xen''s idea of paravirtualization.
>
> >
> >> I can install the tweaked  OS for
> >> paravirtualization, or I can tweak the hardware configuration for
an
> >> already installed OS for full virtualization.  Either way I
can''t go
> >> back to the original OS when I, as occasionally happens, get my
linux
> >> system hosed up.
> >
> > That''s because you use windows. Seriously.
> > You should ask MS if they provide a solution for what you''re
trying to
> > achieve, but I doubt you''d get satisfactory response even
with their
> > Hyper-V.
>
> Ha!  I''d love to see Microsoft provide a Xen-compatible PV kernel,
but I''m
> not holding my breath - I can see them only doing this in a Hyper-V world,
> but I think "enlightened" Windows essentially already does this.
>  Unfortunately it isn''t a true PV kernel, which means you still
need HVM
> support for Xen.
>
> -Nick
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient.  If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way.  If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
>  Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Enlightened mode happens automatically in Server 2008 - all editions.  There
isn''t anything to change/set - the kernel detects at boot-time that it
is running on a Xen or Hyper-V platform and switches to Enlightened Mode.  I
don''t know if Windows 7 contains this or not - I hope so, but given
Microsoft''s attempts to lock down licensing for the client-side virtual
machine O/Ss (XP, Vista, and 7), I wouldn''t be surprised if it is only
included in the Server O/Ss 2008 and future.

-Nick
>>> On 2009/12/28 at 12:41, chris <tknchris@gmail.com> wrote:
> I''ve read about the enlightened mode before but poking around in
windows I
> wasn''t able to find it. Is it in all versions of server 2008 or
just certain
> editions? What if anything needs to be done to activate this? How does it
> compare to gplpv? I''d be curious to play around with it but
haven''t found
> any specifics.
> 
> Chris
> 
> On Mon, Dec 28, 2009 at 1:17 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> 
>> >>> On 2009/12/27 at 20:22, "Fajar A. Nugraha"
<fajar@fajar.net> wrote:
>> > On Mon, Dec 28, 2009 at 9:34 AM, richard heade
<richard.heade@gmail.com>
>> wrote:
>> >> thanks for the response, but it leaves me wondering
what''s the point of
>> >> full virtualization.
>> >
>> > Let''s see ... hardware consolidation? cloud computing?
hosted vps?
>>
>> I think the question, more specifically, is why use full virutalization
>> (HVM) instead of paravirtualization?  The answers you gave apply to the
>> question, "Why use virtualization at all?"  However, as far
as Full vs.
>> Para, the answer is that Paravirtualization is much more efficient in
>> resource utilization, but full virtualization allows for running
operating
>> systems that are not "aware" of the fact that they are
virtualized or are
>> not compatible with Xen''s idea of paravirtualization.
>>
>> >
>> >> I can install the tweaked  OS for
>> >> paravirtualization, or I can tweak the hardware configuration
for an
>> >> already installed OS for full virtualization.  Either way I
can''t go
>> >> back to the original OS when I, as occasionally happens, get
my linux
>> >> system hosed up.
>> >
>> > That''s because you use windows. Seriously.
>> > You should ask MS if they provide a solution for what
you''re trying to
>> > achieve, but I doubt you''d get satisfactory response even
with their
>> > Hyper-V.
>>
>> Ha!  I''d love to see Microsoft provide a Xen-compatible PV
kernel, but I''m
>> not holding my breath - I can see them only doing this in a Hyper-V
world,
>> but I think "enlightened" Windows essentially already does
this.
>>  Unfortunately it isn''t a true PV kernel, which means you
still need HVM
>> support for Xen.
>>
>> -Nick
>>
>>
>>
>> --------
>> This e-mail may contain confidential and privileged material for the
sole
>> use of the intended recipient.  If this email is not intended for you,
or
>> you are not responsible for the delivery of this message to the
intended
>> recipient, please note that this message may contain SEAKR Engineering
>> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
>> strictly prohibited from downloading, photocopying, distributing or
>> otherwise using this message, its contents or attachments in any way. 
If
>> you have received this message in error, please notify us immediately
by
>> replying to this e-mail and delete the message from your mailbox.
>>  Information contained in this message that does not relate to the
business
>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com 
>> http://lists.xensource.com/xen-users 
>>


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

okay, I accept that I''m not going to be able to use the same
"image" for
Xen, and to boot directly.  I''ve rebuilt my system, so that it now only
boots to linux or Xen.  The disk is partitioned somewhat similarly:
/dev/sda1 - windows xp
/dev/sda2 - extended
/dev/sda5 - /
/dev/sda6 - swap
/dev/sda7 - home

I created a new XP vm, winxp, with the following configuration, using Yast:
name="winxp"
uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
memory=512
maxmem=1024
vcpus=2
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=1
keymap="en-us"

builder="hvm"
extid=0
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="cd"
disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
vif=[ ''bridge=br0,model=rtl8139'', ]

stdvga=0
vnc=1
vncunused=1
apic=1
acpi=1
pae=1

usb=1
usbdevice=''tablet''

serial="pty"

the "create" went okay, the vm console/window opened, it brought up
the XP
install disk, and it did the XP install to /dev/sda1 (the files are there),
but when it came time to reboot and finish the installation I got "NTLDR is
missing".  Is this because I went with a physical partition
("phy:") instead
of an image ("file:")?  And how do I get this to work?



On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> The point of full virtualization is that there are certain operating
> systems that cannot run as paravirtualized VMs.  Windows, for example, must
> run in a full virtualization environment - Microsoft has not provided (and
> is not likely to provide) a paravirtual kernel for Windows.  Windows Server
> 2008 has an "enlightened" mode that switches drivers from full
emulation to
> paravirtual mode when it detects a hypervisor like VMware or Xen; however,
> even this "enlightened" version of Windows still requires a full
virtual
> machine.
>
> -Nick
>
> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com> wrote:
> > thanks for the response, but it leaves me wondering what''s
the point of
> > full virtualization.  I can install the tweaked  OS for
> > paravirtualization, or I can tweak the hardware configuration for an
> > already installed OS for full virtualization.  Either way I
can''t go
> > back to the original OS when I, as occasionally happens, get my linux
> > system hosed up.
> >
> >
> > Nick Couchman wrote:
> >> The challenge in this sort of setup is that the hardware
configuration
> that
> > Windows was installed onto and the hardware configuration that Xen
> presents
> > to HVM-based domUs is different - in some cases very different.  For
> example,
> > if you''re running modern hardware, you probably have a SATA
disk, which
> is
> > usually seen by O/Ss as a SCSI-type controller with SCSI disks. 
However,
> HVM
> > domUs use IDE-based controllers and disks, which means booting is
going
> to
> > have issues seeing the change.  There are also differences in the
> chipset,
> > network controllers, etc., that need to be seen correctly by Windows
> before
> > it boots.
> >>
> >> One of the basic things is to try converting the SCSI-based disk
setup
> to IDE
> > - there are instructions on Microsoft''s support site for
doing this.  The
> > downside to this is that you probably won''t be able to boot
Windows back
> on
> > the original hardware outside of the VM after this change - Windows is
> not
> > very flexible in terms of differing hardware configurations outside of
> your
> > basic docked and undocked laptop modes.
> >>
> >> Note that this also may pose licensing issues - usually machines
that
> come
> > with Windows are installed using an OEM license, which licenses
Windows
> to
> > run on the original hardware only.  Using this same copy of Windows to
> run in
> > a domU is likely a violation of the OEM license - you need another,
full
> > retail or volume license for Windows to run as a VM.
> >>
> >> -Nick
> >>
> >>
> >>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com>
> wrote:
> >>>>>
> >>> I have a dual-boot setup, using grub, that I''m
attempting to convert to
> >>> a dual-boot plus xen setup. I''m running openSuSE 11.2
with the
> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is
partitioned
> as:
> >>> sda1 - xp (ntfs)
> >>> sda2 - extended partition
> >>> sda5 - /windows/D (fat32)
> >>> sda6 - swap
> >>> sda7 - / (ext4)
> >>> sda8 - /home (ext4)
> >>>
> >>> I''ve configured the windows xp vm as:
> >>> name="windowsxp"
> >>> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
> >>> memory=512
> >>> maxmem=512
> >>> vcpus=2
> >>> on_poweroff="destroy"
> >>> on_reboot="restart"
> >>> on_crash="destroy"
> >>> localtime=1
> >>> keymap="en-us"
> >>>
> >>> builder="hvm"
> >>> extid=0
> >>> device_model="/usr/lib/xen/bin/qemu-dm"
> >>> kernel="/usr/lib/xen/boot/hvmloader"
> >>> boot="c"
> >>> disk=[ ''phy:/dev/sda1,hda1,w'', ]
> >>> vif=[ ''bridge=br0,model=rtl8139'', ]
> >>>
> >>> stdvga=0
> >>> vnc=1
> >>> vncunused=1
> >>> apic=1
> >>> acpi=1
> >>> pae=1
> >>>
> >>> usb=1
> >>> usbdevice=''tablet''
> >>>
> >>> serial="pty"
> >>>
> >>> When I attempt to run the windows xp vm the console shows
"booting from
> >>> hard disk...", the cpu usage goes to 100%, and
that''s as far as it
> gets.
> >>> (I''ve tried multiple different "disk=..."
combinations, this is just
> the
> >>> latest, but I get the same results from all of them.)
> >>>
> >>> Any ideas on how I might fix this? (it would seem that however
xen
> tries
> >>> to boot windows xp, it''s not as effective as
grub''s chainloader.)
> >>>
> >>
> >>
> >>
> >> --------
> >> This e-mail may contain confidential and privileged material for
the
> sole use
> > of the intended recipient.  If this email is not intended for you, or
you
> are
> > not responsible for the delivery of this message to the intended
> recipient,
> > please note that this message may contain SEAKR Engineering (SEAKR)
> > Privileged/Proprietary Information.  In such a case, you are strictly
> > prohibited from downloading, photocopying, distributing or otherwise
> using
> > this message, its contents or attachments in any way.  If you have
> received
> > this message in error, please notify us immediately by replying to
this
> e-mail
> > and delete the message from your mailbox.  Information contained in
this
> > message that does not relate to the business of SEAKR is neither
endorsed
> by
> > nor attributable to SEAKR.
> >>
> >>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient.  If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way.  If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
>  Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>

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

okay, figuring that maybe the problem was with the physical partition I
built another vm to a "file:", with the following configuration:
name="winxp2"
uuid="86764f24-88ae-a66e-44c4-45c10714efed"
memory=512
maxmem=1024
vcpus=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=1
keymap="en-us"

builder="hvm"
extid=0
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ ''file:/var/lib/xen/images/winxp2/disk0,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
vif=[ ''bridge=br0,model=rtl8139'', ]

stdvga=0
vnc=1
vncunused=1
apic=1
acpi=1
pae=1

usb=1
usbdevice=''tablet''

serial="pty"

Same experience as before, the "create" went okay, the vm
console/window
opened, it brought up the XP install disk, it did the XP install, but when
it came time to reboot and finish the installation I got "NTLDR is
missing".  If I do a "direct" (non-Xen) XP install, it boots
okay, and when
I had it set up for a dual-boot it boots okay.  What is the Xen XP
installation missing?  Is there an extra step, that everyone forgot to
mention, where you install NTLDR or some alternate boot loader (like grub)
to boot XP?


On Sat, Jan 2, 2010 at 8:38 AM, richard heade
<richard.heade@gmail.com>wrote:
> okay, I accept that I''m not going to be able to use the same
"image" for
> Xen, and to boot directly.  I''ve rebuilt my system, so that it now
only
> boots to linux or Xen.  The disk is partitioned somewhat similarly:
> /dev/sda1 - windows xp
> /dev/sda2 - extended
> /dev/sda5 - /
> /dev/sda6 - swap
> /dev/sda7 - home
>
> I created a new XP vm, winxp, with the following configuration, using Yast:
> name="winxp"
> uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
> memory=512
> maxmem=1024
>
> vcpus=2
> on_poweroff="destroy"
> on_reboot="restart"
> on_crash="destroy"
> localtime=1
> keymap="en-us"
>
> builder="hvm"
> extid=0
> device_model="/usr/lib/xen/bin/qemu-dm"
> kernel="/usr/lib/xen/boot/hvmloader"
> boot="cd"
> disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
>
> vif=[ ''bridge=br0,model=rtl8139'', ]
>
> stdvga=0
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
>
> usb=1
> usbdevice=''tablet''
>
> serial="pty"
>
> the "create" went okay, the vm console/window opened, it brought
up the XP
> install disk, and it did the XP install to /dev/sda1 (the files are there),
> but when it came time to reboot and finish the installation I got
"NTLDR is
> missing".  Is this because I went with a physical partition
("phy:") instead
> of an image ("file:")?  And how do I get this to work?
>
>
>
>
> On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
>
>> The point of full virtualization is that there are certain operating
>> systems that cannot run as paravirtualized VMs.  Windows, for example,
must
>> run in a full virtualization environment - Microsoft has not provided
(and
>> is not likely to provide) a paravirtual kernel for Windows.  Windows
Server
>> 2008 has an "enlightened" mode that switches drivers from
full emulation to
>> paravirtual mode when it detects a hypervisor like VMware or Xen;
however,
>> even this "enlightened" version of Windows still requires a
full virtual
>> machine.
>>
>> -Nick
>>
>> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com>
>> wrote:
>> > thanks for the response, but it leaves me wondering
what''s the point of
>> > full virtualization.  I can install the tweaked  OS for
>> > paravirtualization, or I can tweak the hardware configuration for
an
>> > already installed OS for full virtualization.  Either way I
can''t go
>> > back to the original OS when I, as occasionally happens, get my
linux
>> > system hosed up.
>> >
>> >
>> > Nick Couchman wrote:
>> >> The challenge in this sort of setup is that the hardware
configuration
>> that
>> > Windows was installed onto and the hardware configuration that Xen
>> presents
>> > to HVM-based domUs is different - in some cases very different. 
For
>> example,
>> > if you''re running modern hardware, you probably have a
SATA disk, which
>> is
>> > usually seen by O/Ss as a SCSI-type controller with SCSI disks.
>>  However, HVM
>> > domUs use IDE-based controllers and disks, which means booting is
going
>> to
>> > have issues seeing the change.  There are also differences in the
>> chipset,
>> > network controllers, etc., that need to be seen correctly by
Windows
>> before
>> > it boots.
>> >>
>> >> One of the basic things is to try converting the SCSI-based
disk setup
>> to IDE
>> > - there are instructions on Microsoft''s support site for
doing this.
>>  The
>> > downside to this is that you probably won''t be able to
boot Windows back
>> on
>> > the original hardware outside of the VM after this change -
Windows is
>> not
>> > very flexible in terms of differing hardware configurations
outside of
>> your
>> > basic docked and undocked laptop modes.
>> >>
>> >> Note that this also may pose licensing issues - usually
machines that
>> come
>> > with Windows are installed using an OEM license, which licenses
Windows
>> to
>> > run on the original hardware only.  Using this same copy of
Windows to
>> run in
>> > a domU is likely a violation of the OEM license - you need
another, full
>> > retail or volume license for Windows to run as a VM.
>> >>
>> >> -Nick
>> >>
>> >>
>> >>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com>
>> wrote:
>> >>>>>
>> >>> I have a dual-boot setup, using grub, that I''m
attempting to convert
>> to
>> >>> a dual-boot plus xen setup. I''m running openSuSE
11.2 with the
>> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive is
partitioned
>> as:
>> >>> sda1 - xp (ntfs)
>> >>> sda2 - extended partition
>> >>> sda5 - /windows/D (fat32)
>> >>> sda6 - swap
>> >>> sda7 - / (ext4)
>> >>> sda8 - /home (ext4)
>> >>>
>> >>> I''ve configured the windows xp vm as:
>> >>> name="windowsxp"
>> >>> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>> >>> memory=512
>> >>> maxmem=512
>> >>> vcpus=2
>> >>> on_poweroff="destroy"
>> >>> on_reboot="restart"
>> >>> on_crash="destroy"
>> >>> localtime=1
>> >>> keymap="en-us"
>> >>>
>> >>> builder="hvm"
>> >>> extid=0
>> >>> device_model="/usr/lib/xen/bin/qemu-dm"
>> >>> kernel="/usr/lib/xen/boot/hvmloader"
>> >>> boot="c"
>> >>> disk=[ ''phy:/dev/sda1,hda1,w'', ]
>> >>> vif=[ ''bridge=br0,model=rtl8139'', ]
>> >>>
>> >>> stdvga=0
>> >>> vnc=1
>> >>> vncunused=1
>> >>> apic=1
>> >>> acpi=1
>> >>> pae=1
>> >>>
>> >>> usb=1
>> >>> usbdevice=''tablet''
>> >>>
>> >>> serial="pty"
>> >>>
>> >>> When I attempt to run the windows xp vm the console shows
"booting
>> from
>> >>> hard disk...", the cpu usage goes to 100%, and
that''s as far as it
>> gets.
>> >>> (I''ve tried multiple different
"disk=..." combinations, this is just
>> the
>> >>> latest, but I get the same results from all of them.)
>> >>>
>> >>> Any ideas on how I might fix this? (it would seem that
however xen
>> tries
>> >>> to boot windows xp, it''s not as effective as
grub''s chainloader.)
>> >>>
>> >>
>> >>
>> >>
>> >> --------
>> >> This e-mail may contain confidential and privileged material
for the
>> sole use
>> > of the intended recipient.  If this email is not intended for you,
or
>> you are
>> > not responsible for the delivery of this message to the intended
>> recipient,
>> > please note that this message may contain SEAKR Engineering
(SEAKR)
>> > Privileged/Proprietary Information.  In such a case, you are
strictly
>> > prohibited from downloading, photocopying, distributing or
otherwise
>> using
>> > this message, its contents or attachments in any way.  If you have
>> received
>> > this message in error, please notify us immediately by replying to
this
>> e-mail
>> > and delete the message from your mailbox.  Information contained
in this
>> > message that does not relate to the business of SEAKR is neither
>> endorsed by
>> > nor attributable to SEAKR.
>> >>
>> >>
>>
>>
>> --------
>> This e-mail may contain confidential and privileged material for the
sole
>> use of the intended recipient.  If this email is not intended for you,
or
>> you are not responsible for the delivery of this message to the
intended
>> recipient, please note that this message may contain SEAKR Engineering
>> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
>> strictly prohibited from downloading, photocopying, distributing or
>> otherwise using this message, its contents or attachments in any way. 
If
>> you have received this message in error, please notify us immediately
by
>> replying to this e-mail and delete the message from your mailbox.
>>  Information contained in this message that does not relate to the
business
>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>
>
>

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

On Sun, Jan 3, 2010 at 10:21 PM, richard heade <richard.heade@gmail.com>
wrote:
> Same experience as before, the "create" went okay, the vm
console/window
> opened, it brought up the XP install disk, it did the XP install, but when
> it came time to reboot and finish the installation I got "NTLDR is
> missing".  If I do a "direct" (non-Xen) XP install, it boots
okay, and when
> I had it set up for a dual-boot it boots okay.
That''s odd.
> What is the Xen XP
> installation missing?  Is there an extra step, that everyone forgot to
> mention, where you install NTLDR or some alternate boot loader (like grub)
> to boot XP?
It should work with your config file.

At this point I should probably ask what your goal is, and how
proficient you are with Xen.
If your goal is simply to be able to use Windows on top of Linux, then
using VIrtualbox is MUCH easier. Especially for users new to
Virtualization. It has fullscreen and seamless mode too.

If you want to use Xen for production purposes (e.g. on datacenter
servers), then I highly recommend using RHEL/Centos5 x86_64. They''re
stable and easy to setup.

If you simply want to learn about Xen, or absolutely must use
Opensuse, then you might have some issues. There were some seriuos
problems with Opensuse Xen packages (although I''m not sure if your
problem is caused by one of them). Updating to latest packages would
probably help, as well as asking in opensuse list/forum. If that
doesn''t work, you might want to install xen from source. I can share
some instructions for that (or search xen-users list archive)

FWIW, here''s my Windows domU domU config file under RHEL5,

#=============================memory = 500

vif = [ ''mac=00:16:3E:48:DE:93, bridge=br62'' ]
disk = [ ''phy:/dev/rootVG/winlv,hda,w'',
''file:/data/iso/Win.iso,hdc:cdrom,r'' ]
boot="cd"

device_model = ''/usr/lib64/xen/bin/qemu-dm''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''

sdl=0
vnc=1
vnclisten="0.0.0.0"
vncpasswd=''''
stdvga=0
serial=''pty''
localtime=1

usbdevice=''tablet''
apic=0
acpi=1
pae=1

vcpus=1
cpus="1-7"
#=============================
-- 
Fajar

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

Well, I can see why the previous attempts didn''t work, with the
partition being pushed through, but this one puzzles me - your config looks
fine, and I''ve certainly had a lot of success running Windows using
file-backed (and LVM-backed) disk images.  Doesn''t look like
you''re doing anything wrong.  Can you try booting into the XP Recovery
Console and using "fixmbr" to rewrite the MBR once you''ve
done the install?  This shouldn''t be necessary, but I''m
stumped.  You can install grub on the MBR in the domU, but you still need NTLDR
active on the XP Install - Grub just chain loads NTLDR, so I don''t
think that''s going to help much.

-Nick
>>> On 2010/01/03 at 08:21, richard heade
<richard.heade@gmail.com> wrote:
> okay, figuring that maybe the problem was with the physical partition I
> built another vm to a "file:", with the following configuration:
> name="winxp2"
> uuid="86764f24-88ae-a66e-44c4-45c10714efed"
> memory=512
> maxmem=1024
> vcpus=1
> on_poweroff="destroy"
> on_reboot="restart"
> on_crash="destroy"
> localtime=1
> keymap="en-us"
> 
> builder="hvm"
> extid=0
> device_model="/usr/lib/xen/bin/qemu-dm"
> kernel="/usr/lib/xen/boot/hvmloader"
> boot="c"
> disk=[ ''file:/var/lib/xen/images/winxp2/disk0,hda,w'',
> ''phy:/dev/sr0,hdc:cdrom,r'', ]
> vif=[ ''bridge=br0,model=rtl8139'', ]
> 
> stdvga=0
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> 
> usb=1
> usbdevice=''tablet''
> 
> serial="pty"
> 
> Same experience as before, the "create" went okay, the vm
console/window
> opened, it brought up the XP install disk, it did the XP install, but when
> it came time to reboot and finish the installation I got "NTLDR is
> missing".  If I do a "direct" (non-Xen) XP install, it boots
okay, and when
> I had it set up for a dual-boot it boots okay.  What is the Xen XP
> installation missing?  Is there an extra step, that everyone forgot to
> mention, where you install NTLDR or some alternate boot loader (like grub)
> to boot XP?
> 
> 
> On Sat, Jan 2, 2010 at 8:38 AM, richard heade
<richard.heade@gmail.com>wrote:
> 
>> okay, I accept that I''m not going to be able to use the same
"image" for
>> Xen, and to boot directly.  I''ve rebuilt my system, so that it
now only
>> boots to linux or Xen.  The disk is partitioned somewhat similarly:
>> /dev/sda1 - windows xp
>> /dev/sda2 - extended
>> /dev/sda5 - /
>> /dev/sda6 - swap
>> /dev/sda7 - home
>>
>> I created a new XP vm, winxp, with the following configuration, using
Yast:
>> name="winxp"
>> uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
>> memory=512
>> maxmem=1024
>>
>> vcpus=2
>> on_poweroff="destroy"
>> on_reboot="restart"
>> on_crash="destroy"
>> localtime=1
>> keymap="en-us"
>>
>> builder="hvm"
>> extid=0
>> device_model="/usr/lib/xen/bin/qemu-dm"
>> kernel="/usr/lib/xen/boot/hvmloader"
>> boot="cd"
>> disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
>>
>> vif=[ ''bridge=br0,model=rtl8139'', ]
>>
>> stdvga=0
>> vnc=1
>> vncunused=1
>> apic=1
>> acpi=1
>> pae=1
>>
>> usb=1
>> usbdevice=''tablet''
>>
>> serial="pty"
>>
>> the "create" went okay, the vm console/window opened, it
brought up the XP
>> install disk, and it did the XP install to /dev/sda1 (the files are
there),
>> but when it came time to reboot and finish the installation I got
"NTLDR is
>> missing".  Is this because I went with a physical partition
("phy:") instead
>> of an image ("file:")?  And how do I get this to work?
>>
>>
>>
>>
>> On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
>>
>>> The point of full virtualization is that there are certain
operating
>>> systems that cannot run as paravirtualized VMs.  Windows, for
example, must
>>> run in a full virtualization environment - Microsoft has not
provided (and
>>> is not likely to provide) a paravirtual kernel for Windows. 
Windows Server
>>> 2008 has an "enlightened" mode that switches drivers from
full emulation to
>>> paravirtual mode when it detects a hypervisor like VMware or Xen;
however,
>>> even this "enlightened" version of Windows still requires
a full virtual
>>> machine.
>>>
>>> -Nick
>>>
>>> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com>
>>> wrote:
>>> > thanks for the response, but it leaves me wondering
what''s the point of
>>> > full virtualization.  I can install the tweaked  OS for
>>> > paravirtualization, or I can tweak the hardware configuration
for an
>>> > already installed OS for full virtualization.  Either way I
can''t go
>>> > back to the original OS when I, as occasionally happens, get
my linux
>>> > system hosed up.
>>> >
>>> >
>>> > Nick Couchman wrote:
>>> >> The challenge in this sort of setup is that the hardware
configuration
>>> that
>>> > Windows was installed onto and the hardware configuration that
Xen
>>> presents
>>> > to HVM-based domUs is different - in some cases very
different.  For
>>> example,
>>> > if you''re running modern hardware, you probably have
a SATA disk, which
>>> is
>>> > usually seen by O/Ss as a SCSI-type controller with SCSI
disks.
>>>  However, HVM
>>> > domUs use IDE-based controllers and disks, which means booting
is going
>>> to
>>> > have issues seeing the change.  There are also differences in
the
>>> chipset,
>>> > network controllers, etc., that need to be seen correctly by
Windows
>>> before
>>> > it boots.
>>> >>
>>> >> One of the basic things is to try converting the
SCSI-based disk setup
>>> to IDE
>>> > - there are instructions on Microsoft''s support site
for doing this.
>>>  The
>>> > downside to this is that you probably won''t be able
to boot Windows back
>>> on
>>> > the original hardware outside of the VM after this change -
Windows is
>>> not
>>> > very flexible in terms of differing hardware configurations
outside of
>>> your
>>> > basic docked and undocked laptop modes.
>>> >>
>>> >> Note that this also may pose licensing issues - usually
machines that
>>> come
>>> > with Windows are installed using an OEM license, which
licenses Windows
>>> to
>>> > run on the original hardware only.  Using this same copy of
Windows to
>>> run in
>>> > a domU is likely a violation of the OEM license - you need
another, full
>>> > retail or volume license for Windows to run as a VM.
>>> >>
>>> >> -Nick
>>> >>
>>> >>
>>> >>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>> I have a dual-boot setup, using grub, that
I''m attempting to convert
>>> to
>>> >>> a dual-boot plus xen setup. I''m running
openSuSE 11.2 with the
>>> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard drive
is partitioned
>>> as:
>>> >>> sda1 - xp (ntfs)
>>> >>> sda2 - extended partition
>>> >>> sda5 - /windows/D (fat32)
>>> >>> sda6 - swap
>>> >>> sda7 - / (ext4)
>>> >>> sda8 - /home (ext4)
>>> >>>
>>> >>> I''ve configured the windows xp vm as:
>>> >>> name="windowsxp"
>>> >>> uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>>> >>> memory=512
>>> >>> maxmem=512
>>> >>> vcpus=2
>>> >>> on_poweroff="destroy"
>>> >>> on_reboot="restart"
>>> >>> on_crash="destroy"
>>> >>> localtime=1
>>> >>> keymap="en-us"
>>> >>>
>>> >>> builder="hvm"
>>> >>> extid=0
>>> >>> device_model="/usr/lib/xen/bin/qemu-dm"
>>> >>> kernel="/usr/lib/xen/boot/hvmloader"
>>> >>> boot="c"
>>> >>> disk=[ ''phy:/dev/sda1,hda1,w'', ]
>>> >>> vif=[ ''bridge=br0,model=rtl8139'', ]
>>> >>>
>>> >>> stdvga=0
>>> >>> vnc=1
>>> >>> vncunused=1
>>> >>> apic=1
>>> >>> acpi=1
>>> >>> pae=1
>>> >>>
>>> >>> usb=1
>>> >>> usbdevice=''tablet''
>>> >>>
>>> >>> serial="pty"
>>> >>>
>>> >>> When I attempt to run the windows xp vm the console
shows "booting
>>> from
>>> >>> hard disk...", the cpu usage goes to 100%, and
that''s as far as it
>>> gets.
>>> >>> (I''ve tried multiple different
"disk=..." combinations, this is just
>>> the
>>> >>> latest, but I get the same results from all of them.)
>>> >>>
>>> >>> Any ideas on how I might fix this? (it would seem that
however xen
>>> tries
>>> >>> to boot windows xp, it''s not as effective as
grub''s chainloader.)
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --------
>>> >> This e-mail may contain confidential and privileged
material for the
>>> sole use
>>> > of the intended recipient.  If this email is not intended for
you, or
>>> you are
>>> > not responsible for the delivery of this message to the
intended
>>> recipient,
>>> > please note that this message may contain SEAKR Engineering
(SEAKR)
>>> > Privileged/Proprietary Information.  In such a case, you are
strictly
>>> > prohibited from downloading, photocopying, distributing or
otherwise
>>> using
>>> > this message, its contents or attachments in any way.  If you
have
>>> received
>>> > this message in error, please notify us immediately by
replying to this
>>> e-mail
>>> > and delete the message from your mailbox.  Information
contained in this
>>> > message that does not relate to the business of SEAKR is
neither
>>> endorsed by
>>> > nor attributable to SEAKR.
>>> >>
>>> >>
>>>
>>>
>>> --------
>>> This e-mail may contain confidential and privileged material for
the sole
>>> use of the intended recipient.  If this email is not intended for
you, or
>>> you are not responsible for the delivery of this message to the
intended
>>> recipient, please note that this message may contain SEAKR
Engineering
>>> (SEAKR) Privileged/Proprietary Information.  In such a case, you
are
>>> strictly prohibited from downloading, photocopying, distributing or
>>> otherwise using this message, its contents or attachments in any
way.  If
>>> you have received this message in error, please notify us
immediately by
>>> replying to this e-mail and delete the message from your mailbox.
>>>  Information contained in this message that does not relate to the
business
>>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>>
>>
>>


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

I booted into the xp recovery console and ran fixmbr.  I got a lot of text
about the "computer appears to have non-standard or invalid master boot
record", but what do I have to lose - so I did it.  didn''t make
any change,
still fails on boot with "NTLDR is missing".  I also tried fixboot, 
and
when that failed added another fixmbr - but boot still fails.  Would you
know where NTLDR is supposed to reside?


On Mon, Jan 4, 2010 at 12:06 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> Well, I can see why the previous attempts didn''t work, with the
partition
> being pushed through, but this one puzzles me - your config looks fine, and
> I''ve certainly had a lot of success running Windows using
file-backed (and
> LVM-backed) disk images.  Doesn''t look like you''re doing
anything wrong.
>  Can you try booting into the XP Recovery Console and using
"fixmbr" to
> rewrite the MBR once you''ve done the install?  This
shouldn''t be necessary,
> but I''m stumped.  You can install grub on the MBR in the domU, but
you still
> need NTLDR active on the XP Install - Grub just chain loads NTLDR, so I
> don''t think that''s going to help much.
>
> -Nick
>
> >>> On 2010/01/03 at 08:21, richard heade
<richard.heade@gmail.com> wrote:
> > okay, figuring that maybe the problem was with the physical partition
I
> > built another vm to a "file:", with the following
configuration:
> > name="winxp2"
> > uuid="86764f24-88ae-a66e-44c4-45c10714efed"
> > memory=512
> > maxmem=1024
> > vcpus=1
> > on_poweroff="destroy"
> > on_reboot="restart"
> > on_crash="destroy"
> > localtime=1
> > keymap="en-us"
> >
> > builder="hvm"
> > extid=0
> > device_model="/usr/lib/xen/bin/qemu-dm"
> > kernel="/usr/lib/xen/boot/hvmloader"
> > boot="c"
> > disk=[
''file:/var/lib/xen/images/winxp2/disk0,hda,w'',
> > ''phy:/dev/sr0,hdc:cdrom,r'', ]
> > vif=[ ''bridge=br0,model=rtl8139'', ]
> >
> > stdvga=0
> > vnc=1
> > vncunused=1
> > apic=1
> > acpi=1
> > pae=1
> >
> > usb=1
> > usbdevice=''tablet''
> >
> > serial="pty"
> >
> > Same experience as before, the "create" went okay, the vm
console/window
> > opened, it brought up the XP install disk, it did the XP install, but
> when
> > it came time to reboot and finish the installation I got "NTLDR
is
> > missing".  If I do a "direct" (non-Xen) XP install, it
boots okay, and
> when
> > I had it set up for a dual-boot it boots okay.  What is the Xen XP
> > installation missing?  Is there an extra step, that everyone forgot to
> > mention, where you install NTLDR or some alternate boot loader (like
> grub)
> > to boot XP?
> >
> >
> > On Sat, Jan 2, 2010 at 8:38 AM, richard heade
<richard.heade@gmail.com
> >wrote:
> >
> >> okay, I accept that I''m not going to be able to use the
same "image" for
> >> Xen, and to boot directly.  I''ve rebuilt my system, so
that it now only
> >> boots to linux or Xen.  The disk is partitioned somewhat
similarly:
> >> /dev/sda1 - windows xp
> >> /dev/sda2 - extended
> >> /dev/sda5 - /
> >> /dev/sda6 - swap
> >> /dev/sda7 - home
> >>
> >> I created a new XP vm, winxp, with the following configuration,
using
> Yast:
> >> name="winxp"
> >> uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
> >> memory=512
> >> maxmem=1024
> >>
> >> vcpus=2
> >> on_poweroff="destroy"
> >> on_reboot="restart"
> >> on_crash="destroy"
> >> localtime=1
> >> keymap="en-us"
> >>
> >> builder="hvm"
> >> extid=0
> >> device_model="/usr/lib/xen/bin/qemu-dm"
> >> kernel="/usr/lib/xen/boot/hvmloader"
> >> boot="cd"
> >> disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
> >>
> >> vif=[ ''bridge=br0,model=rtl8139'', ]
> >>
> >> stdvga=0
> >> vnc=1
> >> vncunused=1
> >> apic=1
> >> acpi=1
> >> pae=1
> >>
> >> usb=1
> >> usbdevice=''tablet''
> >>
> >> serial="pty"
> >>
> >> the "create" went okay, the vm console/window opened, it
brought up the
> XP
> >> install disk, and it did the XP install to /dev/sda1 (the files
are
> there),
> >> but when it came time to reboot and finish the installation I got
"NTLDR
> is
> >> missing".  Is this because I went with a physical partition
("phy:")
> instead
> >> of an image ("file:")?  And how do I get this to work?
> >>
> >>
> >>
> >>
> >> On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman
<Nick.Couchman@seakr.com
> >wrote:
> >>
> >>> The point of full virtualization is that there are certain
operating
> >>> systems that cannot run as paravirtualized VMs.  Windows, for
example,
> must
> >>> run in a full virtualization environment - Microsoft has not
provided
> (and
> >>> is not likely to provide) a paravirtual kernel for Windows. 
Windows
> Server
> >>> 2008 has an "enlightened" mode that switches drivers
from full
> emulation to
> >>> paravirtual mode when it detects a hypervisor like VMware or
Xen;
> however,
> >>> even this "enlightened" version of Windows still
requires a full
> virtual
> >>> machine.
> >>>
> >>> -Nick
> >>>
> >>> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com>
> >>> wrote:
> >>> > thanks for the response, but it leaves me wondering
what''s the point
> of
> >>> > full virtualization.  I can install the tweaked  OS for
> >>> > paravirtualization, or I can tweak the hardware
configuration for an
> >>> > already installed OS for full virtualization.  Either way
I can''t go
> >>> > back to the original OS when I, as occasionally happens,
get my linux
> >>> > system hosed up.
> >>> >
> >>> >
> >>> > Nick Couchman wrote:
> >>> >> The challenge in this sort of setup is that the
hardware
> configuration
> >>> that
> >>> > Windows was installed onto and the hardware configuration
that Xen
> >>> presents
> >>> > to HVM-based domUs is different - in some cases very
different.  For
> >>> example,
> >>> > if you''re running modern hardware, you probably
have a SATA disk,
> which
> >>> is
> >>> > usually seen by O/Ss as a SCSI-type controller with SCSI
disks.
> >>>  However, HVM
> >>> > domUs use IDE-based controllers and disks, which means
booting is
> going
> >>> to
> >>> > have issues seeing the change.  There are also
differences in the
> >>> chipset,
> >>> > network controllers, etc., that need to be seen correctly
by Windows
> >>> before
> >>> > it boots.
> >>> >>
> >>> >> One of the basic things is to try converting the
SCSI-based disk
> setup
> >>> to IDE
> >>> > - there are instructions on Microsoft''s support
site for doing this.
> >>>  The
> >>> > downside to this is that you probably won''t be
able to boot Windows
> back
> >>> on
> >>> > the original hardware outside of the VM after this change
- Windows
> is
> >>> not
> >>> > very flexible in terms of differing hardware
configurations outside
> of
> >>> your
> >>> > basic docked and undocked laptop modes.
> >>> >>
> >>> >> Note that this also may pose licensing issues -
usually machines
> that
> >>> come
> >>> > with Windows are installed using an OEM license, which
licenses
> Windows
> >>> to
> >>> > run on the original hardware only.  Using this same copy
of Windows
> to
> >>> run in
> >>> > a domU is likely a violation of the OEM license - you
need another,
> full
> >>> > retail or volume license for Windows to run as a VM.
> >>> >>
> >>> >> -Nick
> >>> >>
> >>> >>
> >>> >>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com>
> >>> wrote:
> >>> >>>>>
> >>> >>> I have a dual-boot setup, using grub, that
I''m attempting to
> convert
> >>> to
> >>> >>> a dual-boot plus xen setup. I''m running
openSuSE 11.2 with the
> >>> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The hard
drive is
> partitioned
> >>> as:
> >>> >>> sda1 - xp (ntfs)
> >>> >>> sda2 - extended partition
> >>> >>> sda5 - /windows/D (fat32)
> >>> >>> sda6 - swap
> >>> >>> sda7 - / (ext4)
> >>> >>> sda8 - /home (ext4)
> >>> >>>
> >>> >>> I''ve configured the windows xp vm as:
> >>> >>> name="windowsxp"
> >>> >>>
uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
> >>> >>> memory=512
> >>> >>> maxmem=512
> >>> >>> vcpus=2
> >>> >>> on_poweroff="destroy"
> >>> >>> on_reboot="restart"
> >>> >>> on_crash="destroy"
> >>> >>> localtime=1
> >>> >>> keymap="en-us"
> >>> >>>
> >>> >>> builder="hvm"
> >>> >>> extid=0
> >>> >>> device_model="/usr/lib/xen/bin/qemu-dm"
> >>> >>> kernel="/usr/lib/xen/boot/hvmloader"
> >>> >>> boot="c"
> >>> >>> disk=[ ''phy:/dev/sda1,hda1,w'',
]
> >>> >>> vif=[
''bridge=br0,model=rtl8139'', ]
> >>> >>>
> >>> >>> stdvga=0
> >>> >>> vnc=1
> >>> >>> vncunused=1
> >>> >>> apic=1
> >>> >>> acpi=1
> >>> >>> pae=1
> >>> >>>
> >>> >>> usb=1
> >>> >>> usbdevice=''tablet''
> >>> >>>
> >>> >>> serial="pty"
> >>> >>>
> >>> >>> When I attempt to run the windows xp vm the
console shows "booting
> >>> from
> >>> >>> hard disk...", the cpu usage goes to 100%,
and that''s as far as it
> >>> gets.
> >>> >>> (I''ve tried multiple different
"disk=..." combinations, this is
> just
> >>> the
> >>> >>> latest, but I get the same results from all of
them.)
> >>> >>>
> >>> >>> Any ideas on how I might fix this? (it would seem
that however xen
> >>> tries
> >>> >>> to boot windows xp, it''s not as
effective as grub''s chainloader.)
> >>> >>>
> >>> >>
> >>> >>
> >>> >>
> >>> >> --------
> >>> >> This e-mail may contain confidential and privileged
material for the
> >>> sole use
> >>> > of the intended recipient.  If this email is not intended
for you, or
> >>> you are
> >>> > not responsible for the delivery of this message to the
intended
> >>> recipient,
> >>> > please note that this message may contain SEAKR
Engineering (SEAKR)
> >>> > Privileged/Proprietary Information.  In such a case, you
are strictly
> >>> > prohibited from downloading, photocopying, distributing
or otherwise
> >>> using
> >>> > this message, its contents or attachments in any way.  If
you have
> >>> received
> >>> > this message in error, please notify us immediately by
replying to
> this
> >>> e-mail
> >>> > and delete the message from your mailbox.  Information
contained in
> this
> >>> > message that does not relate to the business of SEAKR is
neither
> >>> endorsed by
> >>> > nor attributable to SEAKR.
> >>> >>
> >>> >>
> >>>
> >>>
> >>> --------
> >>> This e-mail may contain confidential and privileged material
for the
> sole
> >>> use of the intended recipient.  If this email is not intended
for you,
> or
> >>> you are not responsible for the delivery of this message to
the
> intended
> >>> recipient, please note that this message may contain SEAKR
Engineering
> >>> (SEAKR) Privileged/Proprietary Information.  In such a case,
you are
> >>> strictly prohibited from downloading, photocopying,
distributing or
> >>> otherwise using this message, its contents or attachments in
any way.
>  If
> >>> you have received this message in error, please notify us
immediately
> by
> >>> replying to this e-mail and delete the message from your
mailbox.
> >>>  Information contained in this message that does not relate to
the
> business
> >>> of SEAKR is neither endorsed by nor attributable to SEAKR.
> >>>
> >>
> >>
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient.  If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way.  If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
>  Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>

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

the XP VM fails to boot because NTLDR really is missing.  I used the xp
recovery console to look at the xp installation, looking for NTLDR, and I
found that there are whole directories missing (including the
C:WINDOWS\ServicePackFiles\ directory that has the NTLDR one directory
lower).


On Mon, Jan 4, 2010 at 6:29 PM, richard heade
<richard.heade@gmail.com>wrote:
> I booted into the xp recovery console and ran fixmbr.  I got a lot of text
> about the "computer appears to have non-standard or invalid master
boot
> record", but what do I have to lose - so I did it.  didn''t
make any change,
> still fails on boot with "NTLDR is missing".  I also tried
fixboot,  and
> when that failed added another fixmbr - but boot still fails.  Would you
> know where NTLDR is supposed to reside?
>
>
> On Mon, Jan 4, 2010 at 12:06 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
>
>> Well, I can see why the previous attempts didn''t work, with
the partition
>> being pushed through, but this one puzzles me - your config looks fine,
and
>> I''ve certainly had a lot of success running Windows using
file-backed (and
>> LVM-backed) disk images.  Doesn''t look like you''re
doing anything wrong.
>>  Can you try booting into the XP Recovery Console and using
"fixmbr" to
>> rewrite the MBR once you''ve done the install?  This
shouldn''t be necessary,
>> but I''m stumped.  You can install grub on the MBR in the domU,
but you still
>> need NTLDR active on the XP Install - Grub just chain loads NTLDR, so I
>> don''t think that''s going to help much.
>>
>> -Nick
>>
>> >>> On 2010/01/03 at 08:21, richard heade
<richard.heade@gmail.com>
>> wrote:
>> > okay, figuring that maybe the problem was with the physical
partition I
>> > built another vm to a "file:", with the following
configuration:
>> > name="winxp2"
>> > uuid="86764f24-88ae-a66e-44c4-45c10714efed"
>> > memory=512
>> > maxmem=1024
>> > vcpus=1
>> > on_poweroff="destroy"
>> > on_reboot="restart"
>> > on_crash="destroy"
>> > localtime=1
>> > keymap="en-us"
>> >
>> > builder="hvm"
>> > extid=0
>> > device_model="/usr/lib/xen/bin/qemu-dm"
>> > kernel="/usr/lib/xen/boot/hvmloader"
>> > boot="c"
>> > disk=[
''file:/var/lib/xen/images/winxp2/disk0,hda,w'',
>> > ''phy:/dev/sr0,hdc:cdrom,r'', ]
>> > vif=[ ''bridge=br0,model=rtl8139'', ]
>> >
>> > stdvga=0
>> > vnc=1
>> > vncunused=1
>> > apic=1
>> > acpi=1
>> > pae=1
>> >
>> > usb=1
>> > usbdevice=''tablet''
>> >
>> > serial="pty"
>> >
>> > Same experience as before, the "create" went okay, the
vm console/window
>> > opened, it brought up the XP install disk, it did the XP install,
but
>> when
>> > it came time to reboot and finish the installation I got
"NTLDR is
>> > missing".  If I do a "direct" (non-Xen) XP install,
it boots okay, and
>> when
>> > I had it set up for a dual-boot it boots okay.  What is the Xen XP
>> > installation missing?  Is there an extra step, that everyone
forgot to
>> > mention, where you install NTLDR or some alternate boot loader
(like
>> grub)
>> > to boot XP?
>> >
>> >
>> > On Sat, Jan 2, 2010 at 8:38 AM, richard heade
<richard.heade@gmail.com
>> >wrote:
>> >
>> >> okay, I accept that I''m not going to be able to use
the same "image"
>> for
>> >> Xen, and to boot directly.  I''ve rebuilt my system,
so that it now only
>> >> boots to linux or Xen.  The disk is partitioned somewhat
similarly:
>> >> /dev/sda1 - windows xp
>> >> /dev/sda2 - extended
>> >> /dev/sda5 - /
>> >> /dev/sda6 - swap
>> >> /dev/sda7 - home
>> >>
>> >> I created a new XP vm, winxp, with the following
configuration, using
>> Yast:
>> >> name="winxp"
>> >> uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
>> >> memory=512
>> >> maxmem=1024
>> >>
>> >> vcpus=2
>> >> on_poweroff="destroy"
>> >> on_reboot="restart"
>> >> on_crash="destroy"
>> >> localtime=1
>> >> keymap="en-us"
>> >>
>> >> builder="hvm"
>> >> extid=0
>> >> device_model="/usr/lib/xen/bin/qemu-dm"
>> >> kernel="/usr/lib/xen/boot/hvmloader"
>> >> boot="cd"
>> >> disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
>> >>
>> >> vif=[ ''bridge=br0,model=rtl8139'', ]
>> >>
>> >> stdvga=0
>> >> vnc=1
>> >> vncunused=1
>> >> apic=1
>> >> acpi=1
>> >> pae=1
>> >>
>> >> usb=1
>> >> usbdevice=''tablet''
>> >>
>> >> serial="pty"
>> >>
>> >> the "create" went okay, the vm console/window
opened, it brought up the
>> XP
>> >> install disk, and it did the XP install to /dev/sda1 (the
files are
>> there),
>> >> but when it came time to reboot and finish the installation I
got
>> "NTLDR is
>> >> missing".  Is this because I went with a physical
partition ("phy:")
>> instead
>> >> of an image ("file:")?  And how do I get this to
work?
>> >>
>> >>
>> >>
>> >>
>> >> On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman <
>> Nick.Couchman@seakr.com>wrote:
>> >>
>> >>> The point of full virtualization is that there are certain
operating
>> >>> systems that cannot run as paravirtualized VMs.  Windows,
for example,
>> must
>> >>> run in a full virtualization environment - Microsoft has
not provided
>> (and
>> >>> is not likely to provide) a paravirtual kernel for
Windows.  Windows
>> Server
>> >>> 2008 has an "enlightened" mode that switches
drivers from full
>> emulation to
>> >>> paravirtual mode when it detects a hypervisor like VMware
or Xen;
>> however,
>> >>> even this "enlightened" version of Windows still
requires a full
>> virtual
>> >>> machine.
>> >>>
>> >>> -Nick
>> >>>
>> >>> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com>
>> >>> wrote:
>> >>> > thanks for the response, but it leaves me wondering
what''s the point
>> of
>> >>> > full virtualization.  I can install the tweaked  OS
for
>> >>> > paravirtualization, or I can tweak the hardware
configuration for an
>> >>> > already installed OS for full virtualization.  Either
way I can''t go
>> >>> > back to the original OS when I, as occasionally
happens, get my
>> linux
>> >>> > system hosed up.
>> >>> >
>> >>> >
>> >>> > Nick Couchman wrote:
>> >>> >> The challenge in this sort of setup is that the
hardware
>> configuration
>> >>> that
>> >>> > Windows was installed onto and the hardware
configuration that Xen
>> >>> presents
>> >>> > to HVM-based domUs is different - in some cases very
different.  For
>> >>> example,
>> >>> > if you''re running modern hardware, you
probably have a SATA disk,
>> which
>> >>> is
>> >>> > usually seen by O/Ss as a SCSI-type controller with
SCSI disks.
>> >>>  However, HVM
>> >>> > domUs use IDE-based controllers and disks, which
means booting is
>> going
>> >>> to
>> >>> > have issues seeing the change.  There are also
differences in the
>> >>> chipset,
>> >>> > network controllers, etc., that need to be seen
correctly by Windows
>> >>> before
>> >>> > it boots.
>> >>> >>
>> >>> >> One of the basic things is to try converting the
SCSI-based disk
>> setup
>> >>> to IDE
>> >>> > - there are instructions on Microsoft''s
support site for doing this.
>> >>>  The
>> >>> > downside to this is that you probably won''t
be able to boot Windows
>> back
>> >>> on
>> >>> > the original hardware outside of the VM after this
change - Windows
>> is
>> >>> not
>> >>> > very flexible in terms of differing hardware
configurations outside
>> of
>> >>> your
>> >>> > basic docked and undocked laptop modes.
>> >>> >>
>> >>> >> Note that this also may pose licensing issues -
usually machines
>> that
>> >>> come
>> >>> > with Windows are installed using an OEM license,
which licenses
>> Windows
>> >>> to
>> >>> > run on the original hardware only.  Using this same
copy of Windows
>> to
>> >>> run in
>> >>> > a domU is likely a violation of the OEM license - you
need another,
>> full
>> >>> > retail or volume license for Windows to run as a VM.
>> >>> >>
>> >>> >> -Nick
>> >>> >>
>> >>> >>
>> >>> >>>>> On 2009/12/27 at 07:52, richard heade
<richard.heade@gmail.com>
>> >>> wrote:
>> >>> >>>>>
>> >>> >>> I have a dual-boot setup, using grub, that
I''m attempting to
>> convert
>> >>> to
>> >>> >>> a dual-boot plus xen setup. I''m
running openSuSE 11.2 with the
>> >>> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1.  The
hard drive is
>> partitioned
>> >>> as:
>> >>> >>> sda1 - xp (ntfs)
>> >>> >>> sda2 - extended partition
>> >>> >>> sda5 - /windows/D (fat32)
>> >>> >>> sda6 - swap
>> >>> >>> sda7 - / (ext4)
>> >>> >>> sda8 - /home (ext4)
>> >>> >>>
>> >>> >>> I''ve configured the windows xp vm
as:
>> >>> >>> name="windowsxp"
>> >>> >>>
uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>> >>> >>> memory=512
>> >>> >>> maxmem=512
>> >>> >>> vcpus=2
>> >>> >>> on_poweroff="destroy"
>> >>> >>> on_reboot="restart"
>> >>> >>> on_crash="destroy"
>> >>> >>> localtime=1
>> >>> >>> keymap="en-us"
>> >>> >>>
>> >>> >>> builder="hvm"
>> >>> >>> extid=0
>> >>> >>>
device_model="/usr/lib/xen/bin/qemu-dm"
>> >>> >>>
kernel="/usr/lib/xen/boot/hvmloader"
>> >>> >>> boot="c"
>> >>> >>> disk=[
''phy:/dev/sda1,hda1,w'', ]
>> >>> >>> vif=[
''bridge=br0,model=rtl8139'', ]
>> >>> >>>
>> >>> >>> stdvga=0
>> >>> >>> vnc=1
>> >>> >>> vncunused=1
>> >>> >>> apic=1
>> >>> >>> acpi=1
>> >>> >>> pae=1
>> >>> >>>
>> >>> >>> usb=1
>> >>> >>> usbdevice=''tablet''
>> >>> >>>
>> >>> >>> serial="pty"
>> >>> >>>
>> >>> >>> When I attempt to run the windows xp vm the
console shows "booting
>> >>> from
>> >>> >>> hard disk...", the cpu usage goes to
100%, and that''s as far as it
>> >>> gets.
>> >>> >>> (I''ve tried multiple different
"disk=..." combinations, this is
>> just
>> >>> the
>> >>> >>> latest, but I get the same results from all
of them.)
>> >>> >>>
>> >>> >>> Any ideas on how I might fix this? (it would
seem that however xen
>> >>> tries
>> >>> >>> to boot windows xp, it''s not as
effective as grub''s chainloader.)
>> >>> >>>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --------
>> >>> >> This e-mail may contain confidential and
privileged material for
>> the
>> >>> sole use
>> >>> > of the intended recipient.  If this email is not
intended for you,
>> or
>> >>> you are
>> >>> > not responsible for the delivery of this message to
the intended
>> >>> recipient,
>> >>> > please note that this message may contain SEAKR
Engineering (SEAKR)
>> >>> > Privileged/Proprietary Information.  In such a case,
you are
>> strictly
>> >>> > prohibited from downloading, photocopying,
distributing or otherwise
>> >>> using
>> >>> > this message, its contents or attachments in any way.
If you have
>> >>> received
>> >>> > this message in error, please notify us immediately
by replying to
>> this
>> >>> e-mail
>> >>> > and delete the message from your mailbox. 
Information contained in
>> this
>> >>> > message that does not relate to the business of SEAKR
is neither
>> >>> endorsed by
>> >>> > nor attributable to SEAKR.
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>> >>> --------
>> >>> This e-mail may contain confidential and privileged
material for the
>> sole
>> >>> use of the intended recipient.  If this email is not
intended for you,
>> or
>> >>> you are not responsible for the delivery of this message
to the
>> intended
>> >>> recipient, please note that this message may contain SEAKR
Engineering
>> >>> (SEAKR) Privileged/Proprietary Information.  In such a
case, you are
>> >>> strictly prohibited from downloading, photocopying,
distributing or
>> >>> otherwise using this message, its contents or attachments
in any way.
>>  If
>> >>> you have received this message in error, please notify us
immediately
>> by
>> >>> replying to this e-mail and delete the message from your
mailbox.
>> >>>  Information contained in this message that does not
relate to the
>> business
>> >>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>> >>>
>> >>
>> >>
>>
>>
>>
>> --------
>> This e-mail may contain confidential and privileged material for the
sole
>> use of the intended recipient.  If this email is not intended for you,
or
>> you are not responsible for the delivery of this message to the
intended
>> recipient, please note that this message may contain SEAKR Engineering
>> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
>> strictly prohibited from downloading, photocopying, distributing or
>> otherwise using this message, its contents or attachments in any way. 
If
>> you have received this message in error, please notify us immediately
by
>> replying to this e-mail and delete the message from your mailbox.
>>  Information contained in this message that does not relate to the
business
>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>
>
>

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

Well, yes, but I think the larger question is why NTLDR ends up missing every
time you install into a Xen VM, but, from presumably the same installation
media, it succeeds without error when installing to a non-Xen environment. 
I''ve never run into this issue, so I''m kind of stumped as to
what would be causing that.

-Nick
>>> On 2010/01/06 at 11:12, richard heade
<richard.heade@gmail.com> wrote:
> the XP VM fails to boot because NTLDR really is missing.  I used the xp
> recovery console to look at the xp installation, looking for NTLDR, and I
> found that there are whole directories missing (including the
> C:WINDOWS\ServicePackFiles\ directory that has the NTLDR one directory
> lower).
> 
> 
> On Mon, Jan 4, 2010 at 6:29 PM, richard heade
<richard.heade@gmail.com>wrote:
> 
>> I booted into the xp recovery console and ran fixmbr.  I got a lot of
text
>> about the "computer appears to have non-standard or invalid master
boot
>> record", but what do I have to lose - so I did it. 
didn''t make any change,
>> still fails on boot with "NTLDR is missing".  I also tried
fixboot,  and
>> when that failed added another fixmbr - but boot still fails.  Would
you
>> know where NTLDR is supposed to reside?
>>
>>
>> On Mon, Jan 4, 2010 at 12:06 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
>>
>>> Well, I can see why the previous attempts didn''t work,
with the partition
>>> being pushed through, but this one puzzles me - your config looks
fine, and
>>> I''ve certainly had a lot of success running Windows using
file-backed (and
>>> LVM-backed) disk images.  Doesn''t look like
you''re doing anything wrong.
>>>  Can you try booting into the XP Recovery Console and using
"fixmbr" to
>>> rewrite the MBR once you''ve done the install?  This
shouldn''t be necessary,
>>> but I''m stumped.  You can install grub on the MBR in the
domU, but you still
>>> need NTLDR active on the XP Install - Grub just chain loads NTLDR,
so I
>>> don''t think that''s going to help much.
>>>
>>> -Nick
>>>
>>> >>> On 2010/01/03 at 08:21, richard heade
<richard.heade@gmail.com>
>>> wrote:
>>> > okay, figuring that maybe the problem was with the physical
partition I
>>> > built another vm to a "file:", with the following
configuration:
>>> > name="winxp2"
>>> > uuid="86764f24-88ae-a66e-44c4-45c10714efed"
>>> > memory=512
>>> > maxmem=1024
>>> > vcpus=1
>>> > on_poweroff="destroy"
>>> > on_reboot="restart"
>>> > on_crash="destroy"
>>> > localtime=1
>>> > keymap="en-us"
>>> >
>>> > builder="hvm"
>>> > extid=0
>>> > device_model="/usr/lib/xen/bin/qemu-dm"
>>> > kernel="/usr/lib/xen/boot/hvmloader"
>>> > boot="c"
>>> > disk=[
''file:/var/lib/xen/images/winxp2/disk0,hda,w'',
>>> > ''phy:/dev/sr0,hdc:cdrom,r'', ]
>>> > vif=[ ''bridge=br0,model=rtl8139'', ]
>>> >
>>> > stdvga=0
>>> > vnc=1
>>> > vncunused=1
>>> > apic=1
>>> > acpi=1
>>> > pae=1
>>> >
>>> > usb=1
>>> > usbdevice=''tablet''
>>> >
>>> > serial="pty"
>>> >
>>> > Same experience as before, the "create" went okay,
the vm console/window
>>> > opened, it brought up the XP install disk, it did the XP
install, but
>>> when
>>> > it came time to reboot and finish the installation I got
"NTLDR is
>>> > missing".  If I do a "direct" (non-Xen) XP
install, it boots okay, and
>>> when
>>> > I had it set up for a dual-boot it boots okay.  What is the
Xen XP
>>> > installation missing?  Is there an extra step, that everyone
forgot to
>>> > mention, where you install NTLDR or some alternate boot loader
(like
>>> grub)
>>> > to boot XP?
>>> >
>>> >
>>> > On Sat, Jan 2, 2010 at 8:38 AM, richard heade
<richard.heade@gmail.com
>>> >wrote:
>>> >
>>> >> okay, I accept that I''m not going to be able to
use the same "image"
>>> for
>>> >> Xen, and to boot directly.  I''ve rebuilt my
system, so that it now only
>>> >> boots to linux or Xen.  The disk is partitioned somewhat
similarly:
>>> >> /dev/sda1 - windows xp
>>> >> /dev/sda2 - extended
>>> >> /dev/sda5 - /
>>> >> /dev/sda6 - swap
>>> >> /dev/sda7 - home
>>> >>
>>> >> I created a new XP vm, winxp, with the following
configuration, using
>>> Yast:
>>> >> name="winxp"
>>> >> uuid="4c1c1e3d-dc7f-4c62-2467-688c64d77394"
>>> >> memory=512
>>> >> maxmem=1024
>>> >>
>>> >> vcpus=2
>>> >> on_poweroff="destroy"
>>> >> on_reboot="restart"
>>> >> on_crash="destroy"
>>> >> localtime=1
>>> >> keymap="en-us"
>>> >>
>>> >> builder="hvm"
>>> >> extid=0
>>> >> device_model="/usr/lib/xen/bin/qemu-dm"
>>> >> kernel="/usr/lib/xen/boot/hvmloader"
>>> >> boot="cd"
>>> >> disk=[ ''phy:/dev/sda1,hda,w'',
''phy:/dev/sr0,hdc:cdrom,r'', ]
>>> >>
>>> >> vif=[ ''bridge=br0,model=rtl8139'', ]
>>> >>
>>> >> stdvga=0
>>> >> vnc=1
>>> >> vncunused=1
>>> >> apic=1
>>> >> acpi=1
>>> >> pae=1
>>> >>
>>> >> usb=1
>>> >> usbdevice=''tablet''
>>> >>
>>> >> serial="pty"
>>> >>
>>> >> the "create" went okay, the vm console/window
opened, it brought up the
>>> XP
>>> >> install disk, and it did the XP install to /dev/sda1 (the
files are
>>> there),
>>> >> but when it came time to reboot and finish the
installation I got
>>> "NTLDR is
>>> >> missing".  Is this because I went with a physical
partition ("phy:")
>>> instead
>>> >> of an image ("file:")?  And how do I get this to
work?
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Sun, Dec 27, 2009 at 7:20 PM, Nick Couchman <
>>> Nick.Couchman@seakr.com>wrote:
>>> >>
>>> >>> The point of full virtualization is that there are
certain operating
>>> >>> systems that cannot run as paravirtualized VMs. 
Windows, for example,
>>> must
>>> >>> run in a full virtualization environment - Microsoft
has not provided
>>> (and
>>> >>> is not likely to provide) a paravirtual kernel for
Windows.  Windows
>>> Server
>>> >>> 2008 has an "enlightened" mode that switches
drivers from full
>>> emulation to
>>> >>> paravirtual mode when it detects a hypervisor like
VMware or Xen;
>>> however,
>>> >>> even this "enlightened" version of Windows
still requires a full
>>> virtual
>>> >>> machine.
>>> >>>
>>> >>> -Nick
>>> >>>
>>> >>> >>> On 2009/12/27 at 19:34, richard heade
<richard.heade@gmail.com>
>>> >>> wrote:
>>> >>> > thanks for the response, but it leaves me
wondering what''s the point
>>> of
>>> >>> > full virtualization.  I can install the tweaked 
OS for
>>> >>> > paravirtualization, or I can tweak the hardware
configuration for an
>>> >>> > already installed OS for full virtualization. 
Either way I can''t go
>>> >>> > back to the original OS when I, as occasionally
happens, get my
>>> linux
>>> >>> > system hosed up.
>>> >>> >
>>> >>> >
>>> >>> > Nick Couchman wrote:
>>> >>> >> The challenge in this sort of setup is that
the hardware
>>> configuration
>>> >>> that
>>> >>> > Windows was installed onto and the hardware
configuration that Xen
>>> >>> presents
>>> >>> > to HVM-based domUs is different - in some cases
very different.  For
>>> >>> example,
>>> >>> > if you''re running modern hardware, you
probably have a SATA disk,
>>> which
>>> >>> is
>>> >>> > usually seen by O/Ss as a SCSI-type controller
with SCSI disks.
>>> >>>  However, HVM
>>> >>> > domUs use IDE-based controllers and disks, which
means booting is
>>> going
>>> >>> to
>>> >>> > have issues seeing the change.  There are also
differences in the
>>> >>> chipset,
>>> >>> > network controllers, etc., that need to be seen
correctly by Windows
>>> >>> before
>>> >>> > it boots.
>>> >>> >>
>>> >>> >> One of the basic things is to try converting
the SCSI-based disk
>>> setup
>>> >>> to IDE
>>> >>> > - there are instructions on Microsoft''s
support site for doing this.
>>> >>>  The
>>> >>> > downside to this is that you probably
won''t be able to boot Windows
>>> back
>>> >>> on
>>> >>> > the original hardware outside of the VM after
this change - Windows
>>> is
>>> >>> not
>>> >>> > very flexible in terms of differing hardware
configurations outside
>>> of
>>> >>> your
>>> >>> > basic docked and undocked laptop modes.
>>> >>> >>
>>> >>> >> Note that this also may pose licensing issues
- usually machines
>>> that
>>> >>> come
>>> >>> > with Windows are installed using an OEM license,
which licenses
>>> Windows
>>> >>> to
>>> >>> > run on the original hardware only.  Using this
same copy of Windows
>>> to
>>> >>> run in
>>> >>> > a domU is likely a violation of the OEM license -
you need another,
>>> full
>>> >>> > retail or volume license for Windows to run as a
VM.
>>> >>> >>
>>> >>> >> -Nick
>>> >>> >>
>>> >>> >>
>>> >>> >>>>> On 2009/12/27 at 07:52, richard
heade <richard.heade@gmail.com>
>>> >>> wrote:
>>> >>> >>>>>
>>> >>> >>> I have a dual-boot setup, using grub,
that I''m attempting to
>>> convert
>>> >>> to
>>> >>> >>> a dual-boot plus xen setup. I''m
running openSuSE 11.2 with the
>>> >>> >>> 2.6.31.5-0.1-xen kernel and Xen 3.4.1. 
The hard drive is
>>> partitioned
>>> >>> as:
>>> >>> >>> sda1 - xp (ntfs)
>>> >>> >>> sda2 - extended partition
>>> >>> >>> sda5 - /windows/D (fat32)
>>> >>> >>> sda6 - swap
>>> >>> >>> sda7 - / (ext4)
>>> >>> >>> sda8 - /home (ext4)
>>> >>> >>>
>>> >>> >>> I''ve configured the windows xp
vm as:
>>> >>> >>> name="windowsxp"
>>> >>> >>>
uuid="b3a2c424-7df7-94f6-79a8-c641e412f68d"
>>> >>> >>> memory=512
>>> >>> >>> maxmem=512
>>> >>> >>> vcpus=2
>>> >>> >>> on_poweroff="destroy"
>>> >>> >>> on_reboot="restart"
>>> >>> >>> on_crash="destroy"
>>> >>> >>> localtime=1
>>> >>> >>> keymap="en-us"
>>> >>> >>>
>>> >>> >>> builder="hvm"
>>> >>> >>> extid=0
>>> >>> >>>
device_model="/usr/lib/xen/bin/qemu-dm"
>>> >>> >>>
kernel="/usr/lib/xen/boot/hvmloader"
>>> >>> >>> boot="c"
>>> >>> >>> disk=[
''phy:/dev/sda1,hda1,w'', ]
>>> >>> >>> vif=[
''bridge=br0,model=rtl8139'', ]
>>> >>> >>>
>>> >>> >>> stdvga=0
>>> >>> >>> vnc=1
>>> >>> >>> vncunused=1
>>> >>> >>> apic=1
>>> >>> >>> acpi=1
>>> >>> >>> pae=1
>>> >>> >>>
>>> >>> >>> usb=1
>>> >>> >>> usbdevice=''tablet''
>>> >>> >>>
>>> >>> >>> serial="pty"
>>> >>> >>>
>>> >>> >>> When I attempt to run the windows xp vm
the console shows "booting
>>> >>> from
>>> >>> >>> hard disk...", the cpu usage goes to
100%, and that''s as far as it
>>> >>> gets.
>>> >>> >>> (I''ve tried multiple different
"disk=..." combinations, this is
>>> just
>>> >>> the
>>> >>> >>> latest, but I get the same results from
all of them.)
>>> >>> >>>
>>> >>> >>> Any ideas on how I might fix this? (it
would seem that however xen
>>> >>> tries
>>> >>> >>> to boot windows xp, it''s not as
effective as grub''s chainloader.)
>>> >>> >>>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> --------
>>> >>> >> This e-mail may contain confidential and
privileged material for
>>> the
>>> >>> sole use
>>> >>> > of the intended recipient.  If this email is not
intended for you,
>>> or
>>> >>> you are
>>> >>> > not responsible for the delivery of this message
to the intended
>>> >>> recipient,
>>> >>> > please note that this message may contain SEAKR
Engineering (SEAKR)
>>> >>> > Privileged/Proprietary Information.  In such a
case, you are
>>> strictly
>>> >>> > prohibited from downloading, photocopying,
distributing or otherwise
>>> >>> using
>>> >>> > this message, its contents or attachments in any
way.  If you have
>>> >>> received
>>> >>> > this message in error, please notify us
immediately by replying to
>>> this
>>> >>> e-mail
>>> >>> > and delete the message from your mailbox. 
Information contained in
>>> this
>>> >>> > message that does not relate to the business of
SEAKR is neither
>>> >>> endorsed by
>>> >>> > nor attributable to SEAKR.
>>> >>> >>
>>> >>> >>
>>> >>>
>>> >>>
>>> >>> --------
>>> >>> This e-mail may contain confidential and privileged
material for the
>>> sole
>>> >>> use of the intended recipient.  If this email is not
intended for you,
>>> or
>>> >>> you are not responsible for the delivery of this
message to the
>>> intended
>>> >>> recipient, please note that this message may contain
SEAKR Engineering
>>> >>> (SEAKR) Privileged/Proprietary Information.  In such a
case, you are
>>> >>> strictly prohibited from downloading, photocopying,
distributing or
>>> >>> otherwise using this message, its contents or
attachments in any way.
>>>  If
>>> >>> you have received this message in error, please notify
us immediately
>>> by
>>> >>> replying to this e-mail and delete the message from
your mailbox.
>>> >>>  Information contained in this message that does not
relate to the
>>> business
>>> >>> of SEAKR is neither endorsed by nor attributable to
SEAKR.
>>> >>>
>>> >>
>>> >>
>>>
>>>
>>>
>>> --------
>>> This e-mail may contain confidential and privileged material for
the sole
>>> use of the intended recipient.  If this email is not intended for
you, or
>>> you are not responsible for the delivery of this message to the
intended
>>> recipient, please note that this message may contain SEAKR
Engineering
>>> (SEAKR) Privileged/Proprietary Information.  In such a case, you
are
>>> strictly prohibited from downloading, photocopying, distributing or
>>> otherwise using this message, its contents or attachments in any
way.  If
>>> you have received this message in error, please notify us
immediately by
>>> replying to this e-mail and delete the message from your mailbox.
>>>  Information contained in this message that does not relate to the
business
>>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>>
>>
>>


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

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

On Thu, Jan 7, 2010 at 1:12 AM, richard heade <richard.heade@gmail.com>
wrote:
> the XP VM fails to boot because NTLDR really is missing.  I used the xp
> recovery console to look at the xp installation, looking for NTLDR, and I
> found that there are whole directories missing (including the
> C:WINDOWS\ServicePackFiles\ directory that has the NTLDR one directory
> lower).
That should never happen. Since you now have an unused partition
(sda1), I suggest you install Centos 5.4 there, choose Virtualization
group during install. You should then be able to install Windows domU
using virt-install.

If that works, then there''s something wrong with your opensuse setup.
If that doesn''t work, then there''s something wrong with your
XP
install disc.

-- 
Fajar

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