Re: [Xen-users] Xen 4.2 + XP x64 + PVGPL 2K3 x64 = BSOD (UNMOUNTABLE_BOOT_VOLUME)

[Andrew Bobulsky <rulerof@xxxxxxxxx>]

On May 19, 2013, at 10:18 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote:

> On 05/19/2013 06:14 PM, Andrew Bobulsky wrote:
>> On May 19, 2013, at 5:10 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote:
>>
>>> The subject says it all, really.
>>>
>>> I couldn't find any XP x64 specific drivers, but in all other cases 2K3 x64 
>>> drivers have worked for me on XP x64, so since the kernels and driver 
>>> models are the same, I am guessing this should work.
>>>
>>> Thankfully I took a snapshot of the block device before installing the 
>>> drivers.
>>>
>>> Is there a better driver to use on XP x64?
>>>
>>> The HVM disk performance is really quite attrocious. From dom0, I get about 
>>> 60MB/s on unbuffered reads with dd iflag=direct and hdparm -t. From domU I 
>>> get 5MB/s and qemu-dm hits 100% CPU usage.
>>>
>>> Is there a way to make this work
>>
>> Always!  I'm just not sure how :P
>>
>>> establish why it doesn't work?
>>
>> If you could get the system booted from a completely different storage
>> device, and then try to get GPLPV working on a volume that's not the
>> boot volume, that might be a good place to start.  Personally, due to
>> either my brand of weirdness or perhaps tunnel vision, I would boot
>> from an iSCSI volume and then attempt to interact with the "local"
>> disks that way.
>
> Funny you should mention iSCSI. My setup is an iSCSI volume exposed to the 
> domU "raw" as a physical IDE disk. But domU seems to be alergic to it. If I 
> leave the disk spec in the domU config as hda, it BSODs with the mentioned 
> error. If I change it in the config to xvda, the domU starts to burn through 
> 100% of CPU on all cores given to it and never finishes booting.

Ooooo..... Well, you can try it if you like.  Download the Microsoft
iSCSI boot-capable initiator, install it, then download and install
sanbootconf from the iPXE web site.

Once you're done, reboot the domain and boot from the built-in iPXE.
Use Ctrl-B to enter the command line and run the following:

dhcp net0
sanboot iscsi:your.iscsi.server::::name.of.target

That's assuming you're not using chap auth or something, and that your
LUN is also LUN 0 on the target.  I can dig up the doc if you need
help on that, though :)

>> Alternatively, the only other method is probably to hook up the kernel
>> debugger and interrogate things from there.  :P
>
> Nothing ever "just works", does it...
>
> Gordan

Nope!  I've got a pile of dead MacBooks to prove it!  Muahahahah ;)

-Andrew

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users