Hi,
booting /gplpv the emulated realtek nic's and the ide driver are marked
with a yellow sign, but I assume this can be silently ignored.
If I try to activate/deactivate a nic, a bluescreen occurs. This happens
for both - the realtek and the xennet.
*** STOP: 0x0000007E (0xC0000005,0x808925CF,0xF78DA4B8,0xF78DA1B4)
(for xennet)
System is a plain W2K3 Server Standard Edition / German.
Xen: 3.2 x86_64.
cheers,
Stephan
James Harper schrieb:
Another update. This one should fix the problems people were having with
chkdsk on boot failing. Chkdsk never aligns its buffers to a 512 byte
boundary, so I've put in some code which will handle this case when the
transfer size is > PAGE_SIZE. This might fix some other random crashes
too.
A word of warning though, on my system a windows bug check (eg BSoD)
will hang my Dom0 hard for upwards of 5 minutes, and when it finally
comes back it reports:
"
BUG: soft lockup detected on CPU#0!
Call Trace:
<IRQ> [<ffffffff8029fb2c>] softlockup_tick+0xdb/0xed
[<ffffffff80267dba>] timer_interrupt+0x38d/0x3db
[<ffffffff80211154>] handle_IRQ_event+0x2d/0x60
[<ffffffff8029fe6b>] __do_IRQ+0xa4/0x105
[<ffffffff8028364e>] _local_bh_enable+0x59/0xb3
[<ffffffff802665a8>] do_IRQ+0x65/0x73
[<ffffffff80360feb>] evtchn_do_upcall+0x86/0xe0
[<ffffffff8025c616>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff8020622a>] hypercall_page+0x22a/0x1000
[<ffffffff8020622a>] hypercall_page+0x22a/0x1000
[<ffffffff803607c4>] force_evtchn_callback+0xa/0xb
[<ffffffff8036a7a3>] make_response+0xeb/0x131
[<ffffffff8036b020>] blkif_schedule+0x24f/0x328
[<ffffffff8028fa70>] autoremove_wake_function+0x0/0x2e
[<ffffffff8028f8ad>] keventd_create_kthread+0x0/0x61
[<ffffffff8036add1>] blkif_schedule+0x0/0x328
[<ffffffff8028f8ad>] keventd_create_kthread+0x0/0x61
[<ffffffff8023352b>] kthread+0xd4/0x107
[<ffffffff8025c86c>] child_rip+0xa/0x12
[<ffffffff8028f8ad>] keventd_create_kthread+0x0/0x61
[<ffffffff80233457>] kthread+0x0/0x107
[<ffffffff8025c862>] child_rip+0x0/0x12
"
Dom0 just plods along fine again after that though. Not sure what to
make of it at this point. This probably also happened on 0.9.1 too, and
maybe 0.9.0. It's to do with a crash in xenvbd when Windows calls it in
'dump mode'.
You can trigger this behaviour manually on 0.9.2 with a 'xm sysrq
<domain> B' if you want to see it for yourself, and maybe give me a clue
as to why it's happening :)
Have a look at the wiki page for more details:
http://wiki.xensource.com/xenwiki/XenWindowsGplPv
Download from:
http://www.meadowcourt.org/downloads/
(there is a link to the download site from the wiki entry).
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
--
Stephan Seitz
Senior System Administrator
*netz-haut* e.K.
multimediale kommunikation
zweierweg 22
97074 würzburg
fon: +49 931 2876247
fax: +49 931 2876248
web: www.netz-haut.de <http://www.netz-haut.de/>
registriergericht: amtsgericht würzburg, hra 5054
s_seitz.vcf
Description: Vcard
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
| 
Home