kernel panic when starting the virtual machine

[Anish Gupta]

Can you try cleaning old VM before restarting VM with same name?

bhyveload …testvm
bhyve……….testvm

<bhyvectl —destroy —vm=testvm >

bhyveload …testvm
bhyve……….testvm

-Anish
On Sep 26, 2014, at 10:36 AM, Denis Menshikov <dassi at inbox.ru> wrote:

> Hello,
> 
> for greater clarity, will present at once the order of my actions:
> 
> sudo bhyload -m 256 -d FreeBSD-10.0-RELEASE-amd64-dvd1.iso testvm
> 
> sudohyve -c 2 -a -A -H -P -I -m 256 -s 0,amd_hostbridge -s 1,lpc -s 2,ahci-cd,FreeBSD-10.0-RELEASE-amd64-dvd1.iso -s 3,virtio-blk,test.img -l com1,/dev/nmdm1A testvm
> 
> then runs a successful installation, and as written in the manual, I add in /etc/ttys line ttyu0 "/usr/libexec/getty 3wire" xterm on secure. Then it should restart. In the letter to contain messages when loading during installation and at its completion. Document 1 and 2, respectively.
> 
> then...
> 
> sudo bhyveload -m 256 -d test.img testvm
> 
> sudo bhyve -c 2 -a -A -H -P -m 256 -s 0,amd_hostbridge -s 1,lpc -s 2,virtio-blk,test.img -l com1,/dev/nmdm1A testvm
> dassi at 20:58:~ % sudo cu -l /dev/nmdm1B -s 9600
> Connected
> panic: AP #1 (PHY# 1) failed!
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff808e7dd0 at kdb_backtrace+0x60
> #1 0xffffffff808af8b5 at panic+0x155
> #2 0xffffffff80c7e4c5 at cpu_mp_start+0x625
> #3 0xffffffff808f4e8d at mp_start+0x3d
> #4 0xffffffff80861238 at mi_startup+0x118
> #5 0xffffffff802d3e0c at btext+0x2c
> Uptime: 1s It seems to me that I'm doing something wrong.
> 
> uname -a
> FreeBSD vmserver 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
> 
> -- 
> Denis Menshikov<1><2>_______________________________________________
> freebsd-virtualization at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at freebsd.org"