I''m not able to start, destroy, or delete a DomU:> xen1:~ # xm start test4 > Error: Domain is already running > Usage: xm start <DomainName> > > Start a Xend managed domain > -p, --paused Do not unpause domain after starting it > -c, --console_autoconnect Connect to the console after the domain > is created > --vncviewer Connect to display via VNC after the > domain is created > --vncviewer-autopass Pass VNC password to viewer via stdin and > -autopass > > xen1:~ # xm console test4 > Error: Domain ''test4'' is not started > Usage: xm console [-q|--quiet] <Domain> > > Attach to <Domain>''s console. > -q, --quiet Do not print an error message if the > domain does not exist > > xen1:~ # xm list -l test4 | grep status > (status 3) > xen1:~ # xm destroy test4 >> xen1:~ # xm list -l test4 | grep status > (status 3)None of these commands caused an entry in /var/log/xen/xend.log. Ideas? Suggestions? Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hello. El 22/12/12 22:47, Eric escribió:> I''m not able to start, destroy, or delete a DomUStart by "xm list". "xentop" is also helpful. "xm list -l" might be a overkill at this stage, too much details. The rest of "xm" commands which require a <DomainName>, normally can use a "name" or the numeric ID, as displayed by "xm list". "xm start" does not take a <DomainName> as argument, it takes a filename instead. Usually it''s good idea to put the same name to the config file and the DomU''s "name =" directive, otherwise it will likely cause confusions. Greetings.
Hi, 2012/12/23 Alexandre Kouznetsov <alk@ondore.com>:> Hello. > > El 22/12/12 22:47, Eric escribió: > >> I''m not able to start, destroy, or delete a DomUyou could debug that with xenstore-ls maybe; usually I go about solving it in two steps. 1. xenconsoled restart (if it shows no valid state this will probably not help) 2. xend restart (plus wait for 20 seconds or so) After this the vm should be gone and the xenstore for this domid should also be empty. Florian p.s.: Note this also works for VMs than hung on reboot, but they''ll be lost, not rebooted as result (so manual restart of the vm is needed)
Florian Heigl wrote> you could debug that with xenstore-ls maybe; usually I go about > solving it in two steps. > 1. xenconsoled restart (if it shows no valid state this will probably not > help) > 2. xend restart (plus wait for 20 seconds or so) > > After this the vm should be gone and the xenstore for this domid > should also be empty. > > FlorianThanks, Florian: Neither command had an effect. The DomU test4 still appears in the output of xm list (but not in the output of xenstore-ls) and will not start; can not be destroyed, and; can not be deleted.> xen1:~ # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 502 2 r----- > 680.4 > test1 3 768 1 -b---- > 15.7 > test3 768 1 > 179.4 > test4 768 1 > 0.0 > > xen1:~ # xm list -l | grep ''(name'' > (name Domain-0) > (name test1) > (name test3) > (name test4) > > xen1:~ # xenstore-ls | grep ''name = '' > name = "Domain-0" > name = "test1" > name = "Pool-0" > pool_name = "Pool-0" > name = "Domain-0" > pool_name = "Pool-0" > name = "test1"The DomU test1 functions correctly, however. (The DomU test3 is experiencing the same symptoms as test4.) Ideas? Suggestions? Eric Pretorious Truckee, CA -- View this message in context: http://xen.1045712.n5.nabble.com/Unsticking-a-DomU-tp5713191p5713207.html Sent from the Xen - User mailing list archive at Nabble.com.
Florian Heigl wrote you could debug that with xenstore-ls maybe; usually I go about solving it in two steps. 1. xenconsoled restart (if it shows no valid state this will probably not help) 2. xend restart (plus wait for 20 seconds or so) After this the vm should be gone and the xenstore for this domid should also be empty. Florian Thanks, Florian: Neither command had an effect. The DomU test4 still appears in the output of xm list (but not in the output of xenstore-ls) and will not start; can not be destroyed, and; can not be deleted.> xen1:~ # xm list > Name ID Mem VCPUs State Time(s) > Domain-0 0 502 2 r----- 680.4 > test1 3 768 1 -b---- 15.7 > test3 768 1 179.4 > test4 768 1 0.0 > > xen1:~ # xm list -l | grep ''(name'' > (name Domain-0) > (name test1) > (name test3) > (name test4) > > xen1:~ # xenstore-ls | grep ''name = '' > name = "Domain-0" > name = "test1" > name = "Pool-0" > pool_name = "Pool-0" > name = "Domain-0" > pool_name = "Pool-0" > name = "test1"The DomU test1 functions correctly, however. (The DomU test3 is experiencing the same symptoms as test4.) Ideas? Suggestions? Eric Pretorious Truckee, CA>________________________________ > From: Eric <epretorious@yahoo.com> >To: "xen-users@lists.xen.org" <xen-users@lists.xen.org> >Sent: Saturday, December 22, 2012 8:47 PM >Subject: Unsticking a DomU > > >I''m not able to start, destroy, or delete a DomU: > > >> xen1:~ # xm start test4 >> Error: Domain is already running >> Usage: xm start <DomainName> >> >> Start a Xend managed domain >> -p, --paused Do not unpause domain after starting it >> -c, --console_autoconnect Connect to the console after the domain >> is created >> --vncviewer Connect to display via VNC after the >> domain is created >> --vncviewer-autopass Pass VNC password to viewer via stdin and >> -autopass >> >> xen1:~ # xm console test4 >> Error: Domain ''test4'' is not started >> Usage: xm console [-q|--quiet] <Domain> >> >> Attach to <Domain>''s console. >> -q, --quiet Do not print an error message if the >> domain does not exist >> >> xen1:~ # xm list -l test4 | grep status >> (status 3) >>xen1:~ # xm destroy test4>> > >> xen1:~ # xm list -l test4 | grep status >> (status 3) > > >None of these commands caused an entry in /var/log/xen/xend.log. > > >Ideas? Suggestions? > > >Eric Pretorious >Truckee, CA > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hello. El 25/12/12 02:39, epretorious escribió:>> xen1:~ # xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 502 2 r----- >> 680.4 >> test1 3 768 1 -b---- >> 15.7 >> test3 768 1 >> 179.4 >> test4 768 1 >> 0.0The output you quote lacks "ID" and "State" columns, seems like xend is seriously confused. I would expect it to complain via /var/log/xend.log. A good debugging would be to start manually test1, see how it is reflected in xend.log, then start test3 and see how different is the log. -- Alexandre Kouznetsov
Could you post the configurations for test1, test3 and test4, please ? Additionally, can you verify the misbehaviour of test3 if you didn''t start test1 before? Cheers, - Stephan Am Samstag, den 22.12.2012, 20:47 -0800 schrieb Eric:> I''m not able to start, destroy, or delete a DomU: >> > None of these commands caused an entry in /var/log/xen/xend.log. >There''s also a debug log and corresponding qemu-dm logs if the configured device_model is qemu-dm.> Ideas? Suggestions?_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sorry for the long absence, Stephan: The DomU''s are still stuck (i.e., they can''t be started, destroyed, or deleted) and I''ve pasted the configuration below: ================================xen1:~ # for x in 1 3 4 ; do xm list -l test${x} ; done (domain (cpu_weight 256) (cpu_cap 0) (pool_name Pool-0) (bootloader /usr/bin/pygrub) (vcpus 1) (cpus (())) (on_poweroff destroy) (description '''') (on_crash restart) (uuid 20f6dd78-b8e8-2a9e-e069-af6fe6502308) (bootloader_args '''') (name test1) (on_reboot restart) (maxmem 768) (memory 768) (shadow_memory 0) (features '''') (on_xend_start ignore) (on_xend_stop ignore) (start_time 1356423042.6) (cpu_time 51.882692825) (image (linux (kernel '''') (superpages 0) (pci ()) (nomigrate 0) (tsc_mode 0) (notes (HV_START_LOW 18446603336221196288) (FEATURES ''!writable_page_tables|pae_pgdir_above_4gb'') (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071578849280) (LOADER generic) (SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 18446744071591563776) (XEN_VERSION xen-3.0) ) ) ) (status 0) (device (vif (bridge br0) (mac 00:16:3e:bd:93:e3) (backend 0) (uuid 587a0aec-e8e5-5e4e-a784-100f89c0f9ae) (script /etc/xen/scripts/vif-bridge) ) ) (device (console (protocol vt100) (location 2) (uuid 812f1f65-6044-cdea-a9c3-5b874d42fa71) ) ) (device (vbd (protocol x86_64-abi) (uuid 28e98599-62d9-6ddc-6b0e-a4eecbd5a213) (bootable 1) (driver paravirtualised) (dev xvda:disk) (uname phy:/dev/disk/by-id/scsi-1494554000000000044524244370000000000000000000000 ) (mode w) (VDI '''') (backend 0) ) ) ) (domain (cpu_weight 256) (cpu_cap 0) (pool_name Pool-0) (bootloader /usr/bin/pygrub) (vcpus 1) (cpus (())) (on_poweroff destroy) (description sles11-sp2) (on_crash destroy) (uuid 5fc2e89e-f5d0-99fe-4166-9896c580eddd) (bootloader_args -q) (name test3) (on_reboot restart) (maxmem 768) (memory 768) (shadow_memory 0) (features '''') (on_xend_start ignore) (on_xend_stop ignore) (start_time 1356236502.62) (cpu_time 179.430691855) (image (linux (kernel '''') (args ''xencons=tty '') (superpages 0) (videoram 4) (pci ()) (nomigrate 0) (tsc_mode 0) (notes (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel'' ) (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071562080256) (LOADER generic) (INIT_P2M 18446719884453740544) (SUSPEND_CANCEL 1) (ENTRY 18446744071562076160) (XEN_VERSION xen-3.0) (MOD_START_PFN 1) (SUPPORTED_FEATURES 2063) ) ) ) (status 0) (device (vif (bridge br0) (mac 00:16:3e:38:6a:6d) (backend 0) (uuid f51b57d5-4e89-973b-80c0-35c56ddfbbda) (script /etc/xen/scripts/vif-bridge) ) ) (device (console (protocol vt100) (location 2) (uuid 5e16219a-0c20-541e-dd17-c689e0789b7d) ) ) (device (vbd (protocol x86_64-abi) (uuid 7aaaef51-7292-1d08-5dfb-6d72ca0c451c) (bootable 1) (driver paravirtualised) (dev xvda:disk) (uname phy:/dev/disk/by-id/scsi-1494554000000000044524244313000000000000000000000 ) (mode w) (VDI '''') (backend 0) ) ) ) (domain (cpu_weight 256) (cpu_cap 0) (pool_name Pool-0) (bootloader /usr/bin/pygrub) (vcpus 1) (cpus (())) (on_poweroff destroy) (description SLES11-SP2) (on_crash destroy) (uuid 080fcd1b-40a6-9b8f-ad38-f5d4684c2ed4) (bootloader_args -q) (name test4) (on_reboot restart) (maxmem 768) (memory 768) (shadow_memory 0) (features '''') (on_xend_start ignore) (on_xend_stop ignore) (start_time 1355615292.4) (image (linux (kernel '''') (args '' '') (superpages 0) (videoram 4) (pci ()) (nomigrate 0) (tsc_mode 0) (device_model /usr/lib/xen/bin/qemu-dm) (notes (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel'' ) (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071562080256) (LOADER generic) (INIT_P2M 18446719884453740544) (SUSPEND_CANCEL 1) (ENTRY 18446744071562076160) (XEN_VERSION xen-3.0) (MOD_START_PFN 1) (SUPPORTED_FEATURES 2063) ) ) ) (status 0) (device (vif (bridge br0) (mac 00:16:3e:4d:d1:83) (backend 0) (uuid 731b1ce8-4220-1df0-54a1-b4c863e5b105) (script /etc/xen/scripts/vif-bridge) ) ) (device (vkbd (uuid ec7a311f-3ed0-3070-e9cf-dc24be170cb5) (backend 0))) (device (vbd (protocol x86_64-abi) (uuid 2f42af46-992a-d210-6ee5-582f0d77c5a0) (bootable 1) (driver paravirtualised) (dev xvda:disk) (uname phy:/dev/disk/by-id/scsi-1494554000000000044524244390000000000000000000000 ) (mode w) (VDI '''') (backend 0) ) ) (device (vfb (vncunused 1) (vnc 1) (xauthority /root/.Xauthority) (keymap en-us) (uuid 3e4365b7-bfc7-7a71-b596-203d19748e51) ) ) ) ================================ I just want to delete these stubborn DomU''s and start over. Ideas? Suggestions? Eric Pretorious Truckee, CA>________________________________ > From: Stephan Seitz <s.seitz@secretresearchfacility.com> >To: xen-users@lists.xen.org >Sent: Wednesday, December 26, 2012 11:45 PM >Subject: Re: [Xen-users] Unsticking a DomU > >Could you post the configurations for test1, test3 and test4, please ? > >Additionally, can you verify the misbehaviour of test3 if you didn''t >start test1 before? > >Cheers, > >- Stephan > >Am Samstag, den 22.12.2012, 20:47 -0800 schrieb Eric: >> I''m not able to start, destroy, or delete a DomU: >> > >> >> None of these commands caused an entry in /var/log/xen/xend.log. >> > >There''s also a debug log and corresponding qemu-dm logs if the >configured device_model is qemu-dm. > > > > >> Ideas? Suggestions? > > > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xen.org >http://lists.xen.org/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users