Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] runv runtime start container failed #1464

Closed
fanux opened this issue Jun 4, 2018 · 5 comments
Closed

[bug] runv runtime start container failed #1464

fanux opened this issue Jun 4, 2018 · 5 comments
Assignees
Labels
areas/runv kind/bug This is bug report for project

Comments

@fanux
Copy link
Contributor

fanux commented Jun 4, 2018

Using runv runtime failed, error log:

[root@compute065 hyperstart]# pouch create --name hypervisor --runtime runv busybox:latest
6ee94d8ccc9ce4dfebd71e07eef5b9edfb33d960cf9481f015712e0a1990740d

[root@compute065 hyperstart]# pouch start hypervisor -i
E0604 17:05:24.734887 1834727 qemu_process.go:155]
                                                   (process:1834737): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
                        qemu-system-x86_64: -machine pc-i440fx-2.1,accel=kvm,usb=off: Unsupported machine type
                                                                                                              Use -machine help to list supported machines!
                                   E0604 17:05:24.735481 1834727 qemu_process.go:159] exit status 1
                                                                                                   E0604 17:05:34.679930 1834727 qmp_handler.go:371] QMP initialize timeout
                                                   E0604 17:05:34.738242 1834727 vm_states.go:242] SB[vm-BDUKvvRUeh] Start POD failed: rpc error: code = Internal desc = grpc: the client connection is closing
                                                                                       E0604 17:05:34.738390 1834727 sandbox.go:100] StartPod fail, response: &api.ResultBase{Id:"vm-BDUKvvRUeh", Success:false, ResultMessage:"got failed event when wait init message"}
                         Error: failed to start container hypervisor: {"message":"failed to create task, container id: 6ee94d8ccc9ce4dfebd71e07eef5b9edfb33d960cf9481f015712e0a1990740d: failed to retrieve OCI runtime container pid: open /var/lib/pouch/containerd/state/io.containerd.runtime.v1.linux/default/6ee94d8ccc9ce4dfebd71e07eef5b9edfb33d960cf9481f015712e0a1990740d/init.pid: no such file or directory: unknown"}
  • pouch version (use pouch version):
    [root@compute065 hyperstart]# pouch version
    GoVersion: go1.9.1
    KernelVersion: 4.16.13-1.el7.elrepo.x86_64
    Os: linux
    Version: 0.5.0
    APIVersion: 1.24
    Arch: amd64
    BuildTime: 2018-05-24T11:20:02+00:00
    GitCommit: 0.4.0-297-g17d62f9
  • OS (e.g. from /etc/os-release):
    CentOS Linux release 7.5.1804 (Core)
  • Kernel (e.g. uname -a):
    Linux compute065.sha.openstack 4.16.13-1.el7.elrepo.x86_64 add travis.yml for CI #1 SMP Wed May 30 14:31:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Others:
    qemu-x86_64 -version
    qemu-x86_64 version 2.0.0, Copyright (c) 2003-2008 Fabrice Bellard
  • runv version:
    runv version 1.0.0, commit: v1.0.0
@allencloud
Copy link
Collaborator

Please help to take a look at this. @Ace-Tang

In addition, I thing we need to add more CI test case for runV part, although it will use nested virtualization which leads to some difficulties. @chuanchang

@Ace-Tang
Copy link
Contributor

Ace-Tang commented Jun 5, 2018

@fanux , it seems you must upgrade your qemu version >= 2.9

@allencloud
Copy link
Collaborator

it seems you must upgrade your qemu version >= 2.9

If this is an essential part, I think we need to update the runv related doc https://github.com/alibaba/pouch/blob/master/docs/features/pouch_with_runV.md .
@Ace-Tang

@allencloud allencloud changed the title runv runtime start container failed [bug] runv runtime start container failed Jun 5, 2018
@pouchrobot pouchrobot added the kind/bug This is bug report for project label Jun 5, 2018
@allencloud
Copy link
Collaborator

allencloud commented Jun 5, 2018

Have you tried qemu version >= 2.9, we are looking forward to seeing the result. @fanux
In addition, we are planning to use azure which could use nested virtualization to integrate CI for runv part testing. @chuanchang
After that, we could have more specific experiment data then.

@fanux
Copy link
Contributor Author

fanux commented Jun 6, 2018

Build qemu from source, and solved this issue.

wget https://download.qemu.org/qemu-2.12.0.tar.xz
tar xvJf qemu-2.12.0.tar.xz
cd qemu-2.12.0
./configure
make

git clone git://git.qemu.org/qemu.git
cd qemu
git submodule init
git submodule update --recursive
./configure
make

@fanux fanux closed this as completed Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
areas/runv kind/bug This is bug report for project
Projects
None yet
Development

No branches or pull requests

5 participants