On Sun, Oct 12, 2008 at 09:35:54PM -0700, Russ Blaine wrote:
> This is:
>
> 6740122 win2k8 with --vcpus > 1 blue screen 0x101
>
> I'm working on the fix. BTW, for server 2008, use --os-variant=vista.
Ahhh - ok - thanx a lot!
To find a workaround I installed win2008 with 1 CPU, than added
all recent WinUpdates and after snapshot that installed SunxVMWin32PV.
Than I 'virsh setvcpus 2 domain' and restartet win2k8 and it seems to
be working - no blue screen for alomost a day now....
[BTW: www.hdtune.com pro eval comes up with max. speed ~ 120 MB/s r/w
for 64MB files in 512 K chunks - mkfile 2g on dom0 gives ~ 70 MB/s
on the 2way SATA mirror]
2)
Got a kind of workaround for slowness wrt. win2k3: After 1st reboot
I interrupt the setup (at this point it is possible) and installed
the SunxVMWin32PV. After reboot continued the setup, which gaves me
~ same install time as reported for VirtualBox on 2.4 GHz Mac.
Unfortunately, I can't install win updates - the vm consumes 200% CPU
(2 vcpus) but is completely unresponsible (even Ctrl+Alt+Del via
vncviewer doesn't trigger the "taskman menu" - to be able to kill the
process).
xentop - 19:22:51 Xen 3.1.4-xvm
2 domains: 2 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0
shutdown
Mem: 16776416k total, 16766580k used, 9836k free CPUs: 8 @ 2992MHz
NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%)
VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID
Domain-0 -----r 254 2.3 12818432 76.4 no limit n/a 8 0
0 0 0 0 0 0 0
win2003sbs -----r 1756 200.0 3678076 21.9 3686400 22.0 2 1
0 0 1 0 0 0 0
Also 'virsh shutdown win2003sbs' doesn't work - domain keeps running.
'virsh reboot' doesn't work either. The only thing I can do seems
to be to 'init 6' - to solve the problem :(((
So any hints, how one can force to tear down/reboot a domain without
'virsh destroy'ing it?
Regards,
jel.
--
Otto-von-Guericke University http://www.cs.uni-magdeburg.de/
Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2
39106 Magdeburg, Germany Tel: +49 391 67 12768
_______________________________________________
xen-discuss mailing list
[email protected]