VM complain /dev/vda1 not found

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

VM complain /dev/vda1 not found

Mac Lin
Hi,

We are using vagrant(1.9.1) with qemu on ARM64, therefore we have to rebuilt the vagrant to use it. It have been working for a long time until recently.  Several dependency issues have been fixed, but recently we run into the following issue, and we have no clue. Anyway to get more debug message? Any help is welcome.

We are using same script, same Vagrantfile. Vagrant of older server works fine, but newly installed server doesn't. The VM is up and running, commandline console showing "Waiting for domain to get an IP address...". But the virsh console stuck at initramfs shell, for no /dev/vda1 found. And the image file in is not increased to what it should be:
~$ ls /var/lib/libvirt/images -hal
-rw-------  1 root root 193K Aug 14 22:53 build_prod.img
-rwxr--r--  1 root root 194K Aug 14 22:53 build_prod-vdb.qcow2
-rwxr--r--  1 root root 193K Aug 14 12:24 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

This is the normal case, VM could boot to Ubuntu without issue:
# ls /var/lib/libvirt/images -hal
-rw-------  1 root root  19G Aug 14 23:01 build_prod.img
-rwxr--r--  1 root root  29G Aug 14 23:01 build_prod-vdb.qcow2
-rwxr--r--  1 root root 2.1G Mar 17 11:42 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

qemu command line:
/usr/bin/qemu-system-aarch64 -name build_prod -S -machine virt,gic_version=3,accel=kvm,usb=off -cpu host -m 24576 -realtime mlock=off -smp 32,sockets=32,cores=1,threads=1 -uuid d113a0b5-5582-4936-81c8-28a3748af02c -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-build_prod/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /cord/vmlinuz-4.4.0-57-generic -initrd /cord/initrd.img-4.4.0-57-generic -append root=/dev/vda1 console=ttyAMA0 earlyprintk -usb -drive file=/var/lib/libvirt/images/build_prod.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/build_prod-vdb.qcow2,if=none,id=drive-virtio-disk1,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1 -net nic,macaddr=52:54:00:4d:7b:1f,vlan=0,model=virtio,name=net0 -net tap,fd=20,vlan=0,name=hostnet0 -net nic,macaddr=52:54:00:6c:f3:6f,vlan=1,model=virtio,name=net1 -net tap,fd=22,vlan=1,name=hostnet1 -net nic,macaddr=52:54:00:62:17:40,vlan=2,model=virtio,name=net2 -net tap,fd=23,vlan=2,name=hostnet2 -net nic,macaddr=52:54:00:83:0e:fa,vlan=3,model=virtio,name=net3 -net tap,fd=24,vlan=3,name=hostnet3 -serial pty -msg timestamp=on

Please let me know if you need any other information.
Thanks,
Mac Lin

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/72c43b59-ce7a-48f6-b11b-e8830c3db410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: VM complain /dev/vda1 not found

Alvaro Miranda Aguilera
Hello

Are you using some plugin for that?

Alvaro

On Tue, Aug 15, 2017 at 8:29 AM, Mac Lin <[hidden email]> wrote:
Hi,

We are using vagrant(1.9.1) with qemu on ARM64, therefore we have to rebuilt the vagrant to use it. It have been working for a long time until recently.  Several dependency issues have been fixed, but recently we run into the following issue, and we have no clue. Anyway to get more debug message? Any help is welcome.

We are using same script, same Vagrantfile. Vagrant of older server works fine, but newly installed server doesn't. The VM is up and running, commandline console showing "Waiting for domain to get an IP address...". But the virsh console stuck at initramfs shell, for no /dev/vda1 found. And the image file in is not increased to what it should be:
~$ ls /var/lib/libvirt/images -hal
-rw-------  1 root root 193K Aug 14 22:53 build_prod.img
-rwxr--r--  1 root root 194K Aug 14 22:53 build_prod-vdb.qcow2
-rwxr--r--  1 root root 193K Aug 14 12:24 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

This is the normal case, VM could boot to Ubuntu without issue:
# ls /var/lib/libvirt/images -hal
-rw-------  1 root root  19G Aug 14 23:01 build_prod.img
-rwxr--r--  1 root root  29G Aug 14 23:01 build_prod-vdb.qcow2
-rwxr--r--  1 root root 2.1G Mar 17 11:42 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

qemu command line:
/usr/bin/qemu-system-aarch64 -name build_prod -S -machine virt,gic_version=3,accel=kvm,usb=off -cpu host -m 24576 -realtime mlock=off -smp 32,sockets=32,cores=1,threads=1 -uuid d113a0b5-5582-4936-81c8-28a3748af02c -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-build_prod/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /cord/vmlinuz-4.4.0-57-generic -initrd /cord/initrd.img-4.4.0-57-generic -append root=/dev/vda1 console=ttyAMA0 earlyprintk -usb -drive file=/var/lib/libvirt/images/build_prod.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/build_prod-vdb.qcow2,if=none,id=drive-virtio-disk1,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1 -net nic,macaddr=52:54:00:4d:7b:1f,vlan=0,model=virtio,name=net0 -net tap,fd=20,vlan=0,name=hostnet0 -net nic,macaddr=52:54:00:6c:f3:6f,vlan=1,model=virtio,name=net1 -net tap,fd=22,vlan=1,name=hostnet1 -net nic,macaddr=52:54:00:62:17:40,vlan=2,model=virtio,name=net2 -net tap,fd=23,vlan=2,name=hostnet2 -net nic,macaddr=52:54:00:83:0e:fa,vlan=3,model=virtio,name=net3 -net tap,fd=24,vlan=3,name=hostnet3 -serial pty -msg timestamp=on

Please let me know if you need any other information.
Thanks,
Mac Lin

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/72c43b59-ce7a-48f6-b11b-e8830c3db410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exkRYwyAvNnnjdrAF_ZXQqpnbbmE8HqwujHaOHr9rDQ_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: VM complain /dev/vda1 not found

Mac Lin
Yes, but only vagrant-libvirt. And the image we used is the same between the good and bad one, verified by md5sum.

And VAGRANT_LOG does't work on the vagrant I built, so there isn't any additional log to debug. Is it possible to enable it?

On Wed, Aug 16, 2017 at 9:27 AM, Alvaro Miranda Aguilera <[hidden email]> wrote:
Hello

Are you using some plugin for that?

Alvaro

On Tue, Aug 15, 2017 at 8:29 AM, Mac Lin <[hidden email]> wrote:
Hi,

We are using vagrant(1.9.1) with qemu on ARM64, therefore we have to rebuilt the vagrant to use it. It have been working for a long time until recently.  Several dependency issues have been fixed, but recently we run into the following issue, and we have no clue. Anyway to get more debug message? Any help is welcome.

We are using same script, same Vagrantfile. Vagrant of older server works fine, but newly installed server doesn't. The VM is up and running, commandline console showing "Waiting for domain to get an IP address...". But the virsh console stuck at initramfs shell, for no /dev/vda1 found. And the image file in is not increased to what it should be:
~$ ls /var/lib/libvirt/images -hal
-rw-------  1 root root 193K Aug 14 22:53 build_prod.img
-rwxr--r--  1 root root 194K Aug 14 22:53 build_prod-vdb.qcow2
-rwxr--r--  1 root root 193K Aug 14 12:24 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

This is the normal case, VM could boot to Ubuntu without issue:
# ls /var/lib/libvirt/images -hal
-rw-------  1 root root  19G Aug 14 23:01 build_prod.img
-rwxr--r--  1 root root  29G Aug 14 23:01 build_prod-vdb.qcow2
-rwxr--r--  1 root root 2.1G Mar 17 11:42 ubuntu-VAGRANTSLASH-trusty64_vagrant_box_image_0.img

qemu command line:
/usr/bin/qemu-system-aarch64 -name build_prod -S -machine virt,gic_version=3,accel=kvm,usb=off -cpu host -m 24576 -realtime mlock=off -smp 32,sockets=32,cores=1,threads=1 -uuid d113a0b5-5582-4936-81c8-28a3748af02c -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-build_prod/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /cord/vmlinuz-4.4.0-57-generic -initrd /cord/initrd.img-4.4.0-57-generic -append root=/dev/vda1 console=ttyAMA0 earlyprintk -usb -drive file=/var/lib/libvirt/images/build_prod.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/build_prod-vdb.qcow2,if=none,id=drive-virtio-disk1,format=qcow2 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1 -net nic,macaddr=52:54:00:4d:7b:1f,vlan=0,model=virtio,name=net0 -net tap,fd=20,vlan=0,name=hostnet0 -net nic,macaddr=52:54:00:6c:f3:6f,vlan=1,model=virtio,name=net1 -net tap,fd=22,vlan=1,name=hostnet1 -net nic,macaddr=52:54:00:62:17:40,vlan=2,model=virtio,name=net2 -net tap,fd=23,vlan=2,name=hostnet2 -net nic,macaddr=52:54:00:83:0e:fa,vlan=3,model=virtio,name=net3 -net tap,fd=24,vlan=3,name=hostnet3 -serial pty -msg timestamp=on

Please let me know if you need any other information.
Thanks,
Mac Lin

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/72c43b59-ce7a-48f6-b11b-e8830c3db410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/hUzVMH1lARQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exkRYwyAvNnnjdrAF_ZXQqpnbbmE8HqwujHaOHr9rDQ_Q%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAK1hUK8ghjCZFShPHCKC_in%3DTkTGuB5NCZ_50xV4xwv%3D5GLOxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.