| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Release 0.9.5 of GPL PV Drivers for Windows
Hi James;
>All your examples above say 'domain0' instead of 'domain/0'. Could that
be the problem or did you just make a typo in copying it into the email?
You are right, my bad - I was typing the command wrong - it should be
domain/0. The output you want is:
domain = "qcow"
frontend = "/local/domain/75/device/vbd/768"
uuid = "b01d6f19-e818-f976-a284-ed9a3097d857"
dev = "hda"
state = "2"
params = "qcow:/xenimages/w2k3/w2k3.qcow"
mode = "w"
online = "1"
frontend-id = "75"
type = "tap"
hotplug-status = "connected"
I will have a look at debugview next.
Cheers
G
-----Original Message-----
From: James Harper [mailto:james.harper@xxxxxxxxxxxxxxxx]
Sent: 02 June 2008 11:18 AM
To: Geoff Wiener; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Release 0.9.5 of GPL PV Drivers for Windows
> > Yes please to the screen shot, or at least give me the BSoD numbers.
>
> Screen shot attached.
As you say below, 0x7B is a 'can't find boot device' error.
> > a copy of the 'disk=' lines in your config
>
> For the machine that BSODs
> disk = [ 'tap:qcow:/xenimages/w2k3/w2k3.cow,hda,w' ]
> or
> disk = [ 'tap:qcow:/xenimages/w2k3/w2k3.cow,hda,w',
> 'file:/isorep/disc1.iso,hdc:cdrom,r' ]
>
> > output of xenstore-ls /local/domain/<id>/device/vbd
>
> 768= ""
> backend-id = "0"
> virtual-device = "768"
> device-type = "disk"
> state = "1
> backend = "/local/domain/0/backend/tap/52/768"
>
> >In that output there will be a 'backend=' line, I'd like to see the
> output of xenstore-ls on that too.
>
> Unfortunately I can't get any output from that.. for example..
>
> xenstore-ls /local/domain0/backend/tap/52/768
> or
> xenstore-ls /local/domain0/backend/tap/52/768/
> or
> xenstore-ls /local/domain0/backend/tap/52/
All your examples above say 'domain0' instead of 'domain/0'. Could that
be the problem or did you just make a typo in copying it into the email?
If that doesn't work, just do xenstore-ls /local/domain/0 and tell me
what the domain number is and I'll figure it out from there.
Another thing you could do is to boot with a file: block device, fire up
debugview, and then do a 'xm block-attach' to add the tap device at
runtime and see what debugview says.
I might have a go at using tap too to test it.
> With debugview running I selected "capture kernel, capture win32 &
> passthrough" and ran the iometer test on the machine with the 0.9.5
> drivers (RAW). The log is attached.
Hmmm... no evidence of unaligned buffer access. The queue only seems to
get to a maximum of 8 requests though during the tests which is a bit
strange.
> Lastly - what is the etiquette on cross posting to both user and devel
> lists like this? I do not subscribe to the devel list? Perhaps I
> should if I am going to post to it? I just hit reply all... Thanks.
Not sure... maybe we'll stick to -users for now just to be safe.
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home