[elbe-devel] elbe v12.3 issue: unable to connect to the SOAP server

Yegor Yefremov yegorslists at googlemail.com
Thu Mar 12 14:38:30 CET 2020


On Thu, Mar 12, 2020 at 10:07 AM Yegor Yefremov
<yegorslists at googlemail.com> wrote:
>
> On Wed, Mar 11, 2020 at 5:25 PM Torben Hohn <torben.hohn at linutronix.de> wrote:
> >
> > On Wed, Mar 11, 2020 at 03:43:36PM +0100, Yegor Yefremov wrote:
> > > I have created a new initvm from git master. So both host elbe and
> > > initvm elbe show version v12.3.
> > >
> > > Netstat shows that someone is listening on 7587:
> > >
> > > netstat -apn | grep 7587
> > > (Not all processes could be identified, non-owned process info
> > >  will not be shown, you would have to be root to see it all.)
> > > tcp        0      0 0.0.0.0:7587            0.0.0.0:*
> > > LISTEN      -
> > >
> > > But issuing a submit produces the following output:
> > >
> > >  ./elbe initvm --skip-build-bin  submit --directory=initvm my-system.xml
> > > elbe control create_project failed.
> > > Failed to connect to Soap server localhost:7587
> > >
> > >
> > > Check, wether the Soap Server is running inside the initvm
> > > try 'elbe initvm attach'
> > >
> > > Giving up
> > >
> > > Any idea?
> >
> > Moin Yegor,
> >
> > attach into the initvm using ./elbe initvm attach
> >
> > then login: root/root
> >
> > the output from "systemctl status elbe-daemon"
> > and "journalctl _SYSTEMD_UNIT=elbe-daemon.service"
> >
> > should be helpful.
>
> Mar 12 08:35:50 elbe-daemon systemd[665]: elbe-daemon.service: Failed
> to executee
>  command: No such file or directory
> Mar 12 08:35:50 elbe-daemon systemd[665]: elbe-daemon.service: Failed
> at step EXX
> EC spawning /var/cache/elbe/devel/elbe: No such file or directory
>
> A trouble shooting guide would be helpful :-)

Now, trying to rebuild initvm I get the following message:

echo /usr/bin/kvm
/usr/bin/kvm
/usr/bin/kvm -M pc \
 -device virtio-rng-pci \
 -drive file=buildenv.img,if=virtio,bus=1,unit=0 \
 -kernel .elbe-in/vmlinuz \
 -initrd .elbe-gen/initrd-preseeded.gz \
 -append 'root=/dev/vda1 debconf_priority=critical
console=ttyS0,115200n1 DEBIAN_FRONTEND=text' \
 -no-reboot \
 -nographic \
 -device virtio-net-pci,netdev=user.0,mac="fa:6c:bd:72:70:56" \
 -netdev user,id=user.0 \
 -m 1024 \
 -smp $((`nproc` > 8 ? 8 : `nproc`)) \
 -usb \
 || ( echo; \
      echo "------------------------------------------------------------------";
\
      echo "kvm failed to start"; \
      echo "This is most likely the case, because /dev/kvm is not available."; \
      echo "To use KVM inside a VMWARE or other VM instance,"; \
      echo "nested KVM needs to be supported"; \
      echo "------------------------------------------------------------------";
\
      echo; \
      false \
 )
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.80000001H:ECX.svm [bit 2]
qemu: error reading initrd .elbe-gen/initrd-preseeded.gz: No such file
or directory

But

 l .elbe-gen/initrd-preseeded.gz
-rw-r--r-- 1 user users 2.1G Mar 12 12:42 .elbe-gen/initrd-preseeded.gz



More information about the elbe-devel mailing list