search for: xc_dom_control

Hi All, I''ve been looking through the code and list archives but haven''t found this yet... From dom0, how do you cause a virtual domain to gracefully shutdown? It seems like the machinery is there somewhere, because the hypervisor can do it to dom0... For reference, in UML you do this by putting this in /etc/inittab: ca:12345:ctrlaltdel:/sbin/shutdown -h now ...and then

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

...t; Parsing config file ''/etc/xc/test'' > VM IP address(es) : "169.254.1.1" > VM cmdline : "ip=169.254.1.1:169.254.1.0:169.254.1.0:255.255.0.0::eth0:off root=/dev/xvda ro 4 VMID=1" > VM started in domain 1 > > Then I add the address: > xc_dom_control.py vif_addip 1 0 192.168.250.60 > But no address is added. You''ve told Xen about the domain''s new IP address, but you still need to tell the domain itself in the normal way. i.e. either log into the domain and "ifconfig eth0:1 192.168.250.60", or put the configura...

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your