Here is my setup on this server: Debian Wheezy (testing) with kernel 3.0.1 and xen 4.1.1 installed via apt-get DomU storage is lvm-based over iscsi Everything else works fine as far as i can tell however when i do an xm save and then try to xm restore the domain does not come back fully, it gets added to the xm list but the cpu time used sits at 0.0 and when i console to it it does not respond to any keystrokes (except to escape out of the console) I don''t see any error messages in the /var/log/xend.log and xen-debug.log and i have logging turned way up. Here is the procedure i follow: gibson:~# xm create zetas Using config file "/etc/xen/zetas". Started domain zetas (id=6) gibson:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2048 4 r----- 932.5 zetas 6 512 4 -b---- 2.1 gibson:~# gibson:~# xm save zetas zetas.xmsave2 gibson:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2048 4 r----- 922.6 gibson:~# xm restore zetas.xmsave2 gibson:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2048 4 r----- 929.3 zetas 7 512 4 -b---- 0.0 gibson:~# Here is the DomU config file as generated by xen-tools: # # Configuration file for the Xen instance zetas.darkholdings.com, created # by xen-tools 4.2.1 on Fri Oct 21 01:15:30 2011. # # # Kernel + memory size # kernel = ''/usr/lib/xen-4.1/boot/pv-grub-x86_64.gz'' extra = ''(hd0)/boot/grub/menu.lst'' vcpus = ''4'' memory = ''512'' cpu_weight = ''512'' # # Disk device(s). # disk = [ ''phy:/dev/vg_san/zetas.darkholdings.com-disk,xvda1,w'',''phy:/dev/vg_san/zetas.darkholdings.com-swap,xvdb1,w'' ] # # Physical volumes # # # Hostname # name = ''zetas'' hostname = ''zetas.darkholdings.com'' # # Networking # vif = [ ''ip=173.244.165.28,mac=00:16:3E:74:A2:F6,vifname=zetas,bridge=eth0'' ] # # Behaviour # on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' xen_shell = ''zetas'' ################################################ Anyone have any ideas? Thanks, David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
As an update, i attempted the same thing with a domU with file-backed storage on the localhost instead of iscsi lvm and got the same results. I''ve downloaded xen 4.1.2 and im wondering if i should attempt to build this from scratch and install it. -DDV On Fri, Oct 21, 2011 at 5:10 PM, David Della Vecchia < davidoftheold@gmail.com> wrote:> Yup, I''ve tried resume, unpause, start. Each command returns with "the > domain is not suspended/paused/shutdown. " > > -ddv > > Sent from my iPhone > > On Oct 21, 2011, at 4:40 PM, Shane Johnson <sdj@rasmussenequipment.com> > wrote: > > David, > My first thought (Untested) is even though it''s restored it is paused. > Have you tried doing a resume? > > Shane > > > On Fri, Oct 21, 2011 at 2:30 PM, David Della Vecchia <ddv@darkholdings.com > > wrote: > >> Here is my setup on this server: >> Debian Wheezy (testing) with kernel 3.0.1 and xen 4.1.1 installed via >> apt-get >> DomU storage is lvm-based over iscsi >> >> Everything else works fine as far as i can tell however when i do an xm >> save and then try to xm restore the domain does not come back fully, it gets >> added to the xm list but the cpu time used sits at 0.0 and when i console to >> it it does not respond to any keystrokes (except to escape out of the >> console) >> >> I don''t see any error messages in the /var/log/xend.log and xen-debug.log >> and i have logging turned way up. >> >> Here is the procedure i follow: >> gibson:~# xm create zetas >> Using config file "/etc/xen/zetas". >> Started domain zetas (id=6) >> gibson:~# xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 2048 4 r----- >> 932.5 >> zetas 6 512 4 -b---- >> 2.1 >> gibson:~# >> gibson:~# xm save zetas zetas.xmsave2 >> gibson:~# xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 2048 4 r----- >> 922.6 >> gibson:~# xm restore zetas.xmsave2 >> gibson:~# xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 2048 4 r----- >> 929.3 >> zetas 7 512 4 -b---- >> 0.0 >> gibson:~# >> >> Here is the DomU config file as generated by xen-tools: >> >> # >> # Configuration file for the Xen instance zetas.darkholdings.com, created >> # by xen-tools 4.2.1 on Fri Oct 21 01:15:30 2011. >> # >> >> # >> # Kernel + memory size >> # >> kernel = ''/usr/lib/xen-4.1/boot/pv-grub-x86_64.gz'' >> >> extra = ''(hd0)/boot/grub/menu.lst'' >> >> vcpus = ''4'' >> memory = ''512'' >> cpu_weight = ''512'' >> # >> # Disk device(s). >> # >> disk = [ >> ''phy:/dev/vg_san/zetas.darkholdings.com-disk,xvda1,w'',''phy:/dev/vg_san/zetas.darkholdings.com-swap,xvdb1,w'' >> ] >> >> >> # >> # Physical volumes >> # >> >> >> # >> # Hostname >> # >> name = ''zetas'' >> hostname = ''zetas.darkholdings.com'' >> >> # >> # Networking >> # >> vif = [ ''ip=173.244.165.28,mac=00:16:3E:74:A2:F6,vifname=zetas,bridge=eth0'' >> ] >> >> # >> # Behaviour >> # >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> xen_shell = ''zetas'' >> ################################################ >> >> Anyone have any ideas? >> >> Thanks, >> David >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > > -- > Shane D. Johnson > IT Administrator > Rasmussen Equipment > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
So it looks like i wasn''t the only one to have this issue. I hope i''m able to get a fixed kernel version here soon. Looks like the guy put the proposed fix into the proposed-updates section of the repo but it doesn''t appear to be available as a full binary download just yet. The holy grail of my suffering over the last week: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644604 -DDV On Fri, Oct 21, 2011 at 9:29 PM, David Della Vecchia < davidoftheold@gmail.com> wrote:> As an update, i attempted the same thing with a domU with file-backed > storage on the localhost instead of iscsi lvm and got the same results. > > I''ve downloaded xen 4.1.2 and im wondering if i should attempt to build > this from scratch and install it. > > -DDV > > > On Fri, Oct 21, 2011 at 5:10 PM, David Della Vecchia < > davidoftheold@gmail.com> wrote: > >> Yup, I''ve tried resume, unpause, start. Each command returns with "the >> domain is not suspended/paused/shutdown. " >> >> -ddv >> >> Sent from my iPhone >> >> On Oct 21, 2011, at 4:40 PM, Shane Johnson <sdj@rasmussenequipment.com> >> wrote: >> >> David, >> My first thought (Untested) is even though it''s restored it is paused. >> Have you tried doing a resume? >> >> Shane >> >> >> On Fri, Oct 21, 2011 at 2:30 PM, David Della Vecchia < >> ddv@darkholdings.com> wrote: >> >>> Here is my setup on this server: >>> Debian Wheezy (testing) with kernel 3.0.1 and xen 4.1.1 installed via >>> apt-get >>> DomU storage is lvm-based over iscsi >>> >>> Everything else works fine as far as i can tell however when i do an xm >>> save and then try to xm restore the domain does not come back fully, it gets >>> added to the xm list but the cpu time used sits at 0.0 and when i console to >>> it it does not respond to any keystrokes (except to escape out of the >>> console) >>> >>> I don''t see any error messages in the /var/log/xend.log and xen-debug.log >>> and i have logging turned way up. >>> >>> Here is the procedure i follow: >>> gibson:~# xm create zetas >>> Using config file "/etc/xen/zetas". >>> Started domain zetas (id=6) >>> gibson:~# xm list >>> Name ID Mem VCPUs State >>> Time(s) >>> Domain-0 0 2048 4 r----- >>> 932.5 >>> zetas 6 512 4 -b---- >>> 2.1 >>> gibson:~# >>> gibson:~# xm save zetas zetas.xmsave2 >>> gibson:~# xm list >>> Name ID Mem VCPUs State >>> Time(s) >>> Domain-0 0 2048 4 r----- >>> 922.6 >>> gibson:~# xm restore zetas.xmsave2 >>> gibson:~# xm list >>> Name ID Mem VCPUs State >>> Time(s) >>> Domain-0 0 2048 4 r----- >>> 929.3 >>> zetas 7 512 4 -b---- >>> 0.0 >>> gibson:~# >>> >>> Here is the DomU config file as generated by xen-tools: >>> >>> # >>> # Configuration file for the Xen instance zetas.darkholdings.com, >>> created >>> # by xen-tools 4.2.1 on Fri Oct 21 01:15:30 2011. >>> # >>> >>> # >>> # Kernel + memory size >>> # >>> kernel = ''/usr/lib/xen-4.1/boot/pv-grub-x86_64.gz'' >>> >>> extra = ''(hd0)/boot/grub/menu.lst'' >>> >>> vcpus = ''4'' >>> memory = ''512'' >>> cpu_weight = ''512'' >>> # >>> # Disk device(s). >>> # >>> disk = [ >>> ''phy:/dev/vg_san/zetas.darkholdings.com-disk,xvda1,w'',''phy:/dev/vg_san/zetas.darkholdings.com-swap,xvdb1,w'' >>> ] >>> >>> >>> # >>> # Physical volumes >>> # >>> >>> >>> # >>> # Hostname >>> # >>> name = ''zetas'' >>> hostname = ''zetas.darkholdings.com'' >>> >>> # >>> # Networking >>> # >>> vif = [ ''ip=173.244.165.28,mac=00:16:3E:74:A2:F6,vifname=zetas,bridge=eth0'' >>> ] >>> >>> # >>> # Behaviour >>> # >>> on_poweroff = ''destroy'' >>> on_reboot = ''restart'' >>> on_crash = ''restart'' >>> >>> xen_shell = ''zetas'' >>> ################################################ >>> >>> Anyone have any ideas? >>> >>> Thanks, >>> David >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> >> >> >> -- >> Shane D. Johnson >> IT Administrator >> Rasmussen Equipment >> >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users