John Danielson wrote:
.
Patrick Petit wrote:
David Edmondson wrote:
On 4 Aug 2006, at 1:22pm, Patrick Petit wrote:
When you're talking to Xen (using three control-A's) you should
hit 'q', which causes the dom0 to drop into kmdb (three control-
A's to get back to the dom0 and hence kmdb). Does this not work?
I'll try this. Note that I am seeing similar problems on vanilla
Nevada snv-44 that is not related to Xen at all. For instance, the
launching of build-workspace (build Xen from source) hangs very
badly in 'gld -m elf_i386 -r -o built_in.o amd.o centaur.o cyrix.o
generic.o main.o state.o'. You can't kill any of the gmake or gld
processes launched by the build! Even a reboot would not complete!
To get out of this, you need to cycle the platform! So, there seem
to be a more general hanging problem on this build that dom0 may
inherit. Wouldn't a similar hanging situation of the xend process
produce the same effects as those described earlier? The fact that
it happens when ZFS is involved is perhaps just the result of a side
effect.
Ahh, this sounds like something that was mentioned internally
recently. See CR 6425723 and perhaps try:
the work around for this is to manually diable vpm_enable
on a console of the machine, or direct monitor and keyboard
as root :
# mdb -kw
# vpm_enable/D (to disaply what it is set at)
# vpm_enable/W 0 (to set it to 0)
reboot machine and check if it has been set to 0
I have tried this and echo "set vpm_cache_enable=0" >> /etc/system.
What you did:
# echo "set vpm_cache_enable=0" >> /etc/system
Is the correct workaround for the build problem.. It's a generic
opensolaris bug.
Doesn't work. But is has solved the build process hang described above.
That's better than nothing.
Thanks for the suggestion anyway.
I know John D and Max had done some testing with zfs. I'll ping them
and see if they can add some comments...
We've tested the use of zvol's as device-backed VBD's but not extensively.
A couple of things to point out.
When creating the zvol, set the blocksize to 512
e.g. zfs create -b 512 -V 5g zpool/myzdev
You might also try increasing the amount of memory given to dom0 when
using zfs for backend devices. I've experienced very slow response times
when using zfs with the default Solaris dom0 memory settings.
Hi John
I have tried this and increased dom0's memory to 1GB as well.
Still hangs during domU's boot process at the moment the virtual disk
(mapped by zvol) is registered in the kernel. I filled CR 6458021
yesterday.
Best regards,
- Patrick
- john
|
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
