Hi Thomas, I just got a bundle of new hardware, so now I free to make tests.
> Well, sure that doesn't look a correct UUID. But by what mechanism has > these been created? I install Debian Squeeze (via PXE+preseed, if this matters) and install packages "ntp bridge-utils xen-qemu-dm-4.0 xen-linux-system openssh-server rcs screen" (this is from my preseed.cfg). Next I configure network, NTP, sources.list, enable "xend-unix-server" is xend-config.sxp, edit strings XENDOMAINS_RESTORE and XENDOMAINS_SAVE in /etc/default/xendomains (as described in http://wiki.debian.org/Xen), make symlink from /usr/lib64/xen-4.0 to /usr/lib64/xen and increase loop devices limit. Now I reboot host couple of times and look on xenstored via script from http://wiki.xensource.com/xenwiki/XenStore: root@sl03500008177:~# ./viewstore.sh /vm/00000000-0000-0000-0000-000000000000/on_xend_stop=ignore /vm/00000000-0000-0000-0000-000000000000/shadow_memory=0 /vm/00000000-0000-0000-0000-000000000000/uuid=00000000-0000-0000-0000-000000000000 /vm/00000000-0000-0000-0000-000000000000/on_reboot=restart /vm/00000000-0000-0000-0000-000000000000/image/ostype=linux /vm/00000000-0000-0000-0000-000000000000/image/kernel= /vm/00000000-0000-0000-0000-000000000000/image/cmdline= /vm/00000000-0000-0000-0000-000000000000/image/ramdisk= /vm/00000000-0000-0000-0000-000000000000/on_poweroff=destroy /vm/00000000-0000-0000-0000-000000000000/bootloader_args= /vm/00000000-0000-0000-0000-000000000000/on_xend_start=ignore /vm/00000000-0000-0000-0000-000000000000/on_crash=restart /vm/00000000-0000-0000-0000-000000000000/xend/restart_count=0 /vm/00000000-0000-0000-0000-000000000000/vcpus=16 /vm/00000000-0000-0000-0000-000000000000/vcpu_avail=65535 /vm/00000000-0000-0000-0000-000000000000/bootloader= /vm/00000000-0000-0000-0000-000000000000/name=Domain-0 /vm/00000000-0000-0000-0000-000000000000-1/on_xend_stop=ignore /vm/00000000-0000-0000-0000-000000000000-1/shadow_memory=0 /vm/00000000-0000-0000-0000-000000000000-1/uuid=00000000-0000-0000-0000-000000000000 /vm/00000000-0000-0000-0000-000000000000-1/on_reboot=restart /vm/00000000-0000-0000-0000-000000000000-1/image/ostype=linux /vm/00000000-0000-0000-0000-000000000000-1/image/kernel= /vm/00000000-0000-0000-0000-000000000000-1/image/cmdline= /vm/00000000-0000-0000-0000-000000000000-1/image/ramdisk= /vm/00000000-0000-0000-0000-000000000000-1/on_poweroff=destroy /vm/00000000-0000-0000-0000-000000000000-1/bootloader_args= /vm/00000000-0000-0000-0000-000000000000-1/on_xend_start=ignore /vm/00000000-0000-0000-0000-000000000000-1/on_crash=restart /vm/00000000-0000-0000-0000-000000000000-1/xend/restart_count=0 /vm/00000000-0000-0000-0000-000000000000-1/vcpus=16 /vm/00000000-0000-0000-0000-000000000000-1/vcpu_avail=65535 /vm/00000000-0000-0000-0000-000000000000-1/bootloader= /vm/00000000-0000-0000-0000-000000000000-1/name=Domain-0 /vm/00000000-0000-0000-0000-000000000000-2/on_xend_stop=ignore /vm/00000000-0000-0000-0000-000000000000-2/shadow_memory=0 /vm/00000000-0000-0000-0000-000000000000-2/uuid=00000000-0000-0000-0000-000000000000 /vm/00000000-0000-0000-0000-000000000000-2/on_reboot=restart /vm/00000000-0000-0000-0000-000000000000-2/image/ostype=linux /vm/00000000-0000-0000-0000-000000000000-2/image/kernel= /vm/00000000-0000-0000-0000-000000000000-2/image/cmdline= /vm/00000000-0000-0000-0000-000000000000-2/image/ramdisk= /vm/00000000-0000-0000-0000-000000000000-2/on_poweroff=destroy /vm/00000000-0000-0000-0000-000000000000-2/bootloader_args= /vm/00000000-0000-0000-0000-000000000000-2/on_xend_start=ignore /vm/00000000-0000-0000-0000-000000000000-2/on_crash=restart /vm/00000000-0000-0000-0000-000000000000-2/xend/restart_count=0 /vm/00000000-0000-0000-0000-000000000000-2/vcpus=16 /vm/00000000-0000-0000-0000-000000000000-2/vcpu_avail=65535 /vm/00000000-0000-0000-0000-000000000000-2/bootloader= /vm/00000000-0000-0000-0000-000000000000-2/name=Domain-0 /local/domain/0/vm=/vm/00000000-0000-0000-0000-000000000000-2 /local/domain/0/device= /local/domain/0/control/platform-feature-multiprocessor-suspend=1 /local/domain/0/error= /local/domain/0/memory/target=32242160 /local/domain/0/guest= /local/domain/0/hvmpv= /local/domain/0/data= /local/domain/0/cpu/15/availability=online /local/domain/0/cpu/3/availability=online /local/domain/0/cpu/8/availability=online /local/domain/0/cpu/9/availability=online /local/domain/0/cpu/5/availability=online /local/domain/0/cpu/13/availability=online /local/domain/0/cpu/0/availability=online /local/domain/0/cpu/6/availability=online /local/domain/0/cpu/12/availability=online /local/domain/0/cpu/14/availability=online /local/domain/0/cpu/2/availability=online /local/domain/0/cpu/11/availability=online /local/domain/0/cpu/1/availability=online /local/domain/0/cpu/7/availability=online /local/domain/0/cpu/4/availability=online /local/domain/0/cpu/10/availability=online /local/domain/0/description= /local/domain/0/console/limit=1048576 /local/domain/0/console/type=xenconsoled /local/domain/0/name=Domain-0 /local/domain/0/domid=0 /tool/xenstored= root@sl03500008177:~# That's all. >> How can I remove it permanently, any useful idea? > > Have you tried xenstore-rm? Yes, I have, but it doesn't have constant effect. Every reboot adds a new entry. Regards, Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
