Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Peter Grehan wrote: Hi Roman, When I was seing this 'Failed to emulate instruction at 0x80594f3a', it happened right after boot loader menu (the one with the ascii-art). At that time I had 'hw.physmem=0x18000' in my host's loader.conf. Also the problem wasn't 100% reproducible, it started to show up after creating/destroying several VMs. OK - I'm now wondering if this is a guest phys memory leak in the hypervisor, and it's not reporting the error correctly. How many times do you have to create/destroy vm's for this to occurr ? I'm writing some sort of automation scripts so I created and destroy vms quite often, I guess maybe 20 times or so... BTW, any ideas why I stared loosing a console after: GDB: debug ports: bvm GDB: current port: bvm KDB: debugger backends: ddb gdb KDB: current backend: ddb ? Roman Bogorodskiy pgpUjmUjfkc0d.pgp Description: PGP signature
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Peter Grehan wrote: Hi Roman, I start a VM like that: sudo /usr/sbin/bhyveload -m 256 -M 0 -h /var/run/bhyve/test1/vm1 test1 sudo /usr/bin/cpuset -l 0-3 /usr/sbin/bhyve -m 256 -M 0 -s 1,virtio-net,tap0 test1 The last commands give me: Failed to emulate instruction at 0x80594f3a What could be wrong with that? Was this during boot or later ? Do you have a console log up to where it occurred ? Hm, I see strange things happening. When I was seing this 'Failed to emulate instruction at 0x80594f3a', it happened right after boot loader menu (the one with the ascii-art). At that time I had 'hw.physmem=0x18000' in my host's loader.conf. Also the problem wasn't 100% reproducible, it started to show up after creating/destroying several VMs. I replaced the physmem value with hw.physmem=0x1. Now I have 100% reproducibility and it fails here: GDB: debug ports: bvm GDB: current port: bvm KDB: debugger backends: ddb gdb KDB: current backend: ddb (20:06) novel@kloomba:~/bhyve/vm1 % I can still see this VM in /dev/vmm though. Roman Bogorodskiy pgpAO7U4jmgnB.pgp Description: PGP signature
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Hi Roman, When I was seing this 'Failed to emulate instruction at 0x80594f3a', it happened right after boot loader menu (the one with the ascii-art). At that time I had 'hw.physmem=0x18000' in my host's loader.conf. Also the problem wasn't 100% reproducible, it started to show up after creating/destroying several VMs. OK - I'm now wondering if this is a guest phys memory leak in the hypervisor, and it's not reporting the error correctly. How many times do you have to create/destroy vm's for this to occurr ? later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Hi Roman, I start a VM like that: sudo /usr/sbin/bhyveload -m 256 -M 0 -h /var/run/bhyve/test1/vm1 test1 sudo /usr/bin/cpuset -l 0-3 /usr/sbin/bhyve -m 256 -M 0 -s 1,virtio-net,tap0 test1 The last commands give me: Failed to emulate instruction at 0x80594f3a What could be wrong with that? Was this during boot or later ? Do you have a console log up to where it occurred ? later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Andreas Nilsson wrote: On Sun, Sep 2, 2012 at 6:56 PM, Roman Bogorodskiy no...@freebsd.org wrote: Roman Bogorodskiy wrote: Peter Grehan wrote: Hi Roman, Yeah, but I'd like to leave more memory for the host system, so I specified 6GB. I have 8GB at all, so 2GB left for VMs. Should it cause any problems? No, that should be fine. BTW, I encountered a problem with the tap0 device. I create a tap device and assign an address to it, using 'ifconfig tap0 192.168.1.1 up'. I boot a VM and everything goes fine. When I do 'reboot' in the guest, it reboots, but tap0 on the host goes down and its address is dropped. Is that an expected behaviour? Yes - we probably need to fix the tap device to not do that :( Yeah, it would be great to get this fixed. And one question: is there a way to get a list of all running VMs on the host? Doesn't seem like vmmctl being able to do that. Oh, I've started reading the code and figured out that I can just do `ls /dev/vmm`! Roman Bogorodskiy IMHO: Please don't introduce reading stuff in /dev as a standard way to get info ( at least not for end user). sysctl is so much nicer to work with. Yes, reading from /dev is not very convenient, but appears that sysctl is not supported. I didn't read the code though, but I don't see anything looking like that in sysctl -a. Probably the most handy way of doing that is via 'vmmctl' or a tool like that. Anyways, I started spotting one more problem: I start a VM like that: sudo /usr/sbin/bhyveload -m 256 -M 0 -h /var/run/bhyve/test1/vm1 test1 sudo /usr/bin/cpuset -l 0-3 /usr/sbin/bhyve -m 256 -M 0 -s 1,virtio-net,tap0 test1 The last commands give me: Failed to emulate instruction at 0x80594f3a What could be wrong with that? Roman Bogorodskiy pgpfM2RxGRdE6.pgp Description: PGP signature
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Peter Grehan wrote: Hi Roman, Yeah, but I'd like to leave more memory for the host system, so I specified 6GB. I have 8GB at all, so 2GB left for VMs. Should it cause any problems? No, that should be fine. BTW, I encountered a problem with the tap0 device. I create a tap device and assign an address to it, using 'ifconfig tap0 192.168.1.1 up'. I boot a VM and everything goes fine. When I do 'reboot' in the guest, it reboots, but tap0 on the host goes down and its address is dropped. Is that an expected behaviour? Yes - we probably need to fix the tap device to not do that :( Yeah, it would be great to get this fixed. And one question: is there a way to get a list of all running VMs on the host? Doesn't seem like vmmctl being able to do that. Thanks, Roman Bogorodskiy pgpkXhR9oLPFb.pgp Description: PGP signature
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
On Sun, Sep 2, 2012 at 6:56 PM, Roman Bogorodskiy no...@freebsd.org wrote: Roman Bogorodskiy wrote: Peter Grehan wrote: Hi Roman, Yeah, but I'd like to leave more memory for the host system, so I specified 6GB. I have 8GB at all, so 2GB left for VMs. Should it cause any problems? No, that should be fine. BTW, I encountered a problem with the tap0 device. I create a tap device and assign an address to it, using 'ifconfig tap0 192.168.1.1 up'. I boot a VM and everything goes fine. When I do 'reboot' in the guest, it reboots, but tap0 on the host goes down and its address is dropped. Is that an expected behaviour? Yes - we probably need to fix the tap device to not do that :( Yeah, it would be great to get this fixed. And one question: is there a way to get a list of all running VMs on the host? Doesn't seem like vmmctl being able to do that. Oh, I've started reading the code and figured out that I can just do `ls /dev/vmm`! Roman Bogorodskiy IMHO: Please don't introduce reading stuff in /dev as a standard way to get info ( at least not for end user). sysctl is so much nicer to work with. Regards Andreas ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Hi Roman, Yeah, but I'd like to leave more memory for the host system, so I specified 6GB. I have 8GB at all, so 2GB left for VMs. Should it cause any problems? No, that should be fine. BTW, I encountered a problem with the tap0 device. I create a tap device and assign an address to it, using 'ifconfig tap0 192.168.1.1 up'. I boot a VM and everything goes fine. When I do 'reboot' in the guest, it reboots, but tap0 on the host goes down and its address is dropped. Is that an expected behaviour? Yes - we probably need to fix the tap device to not do that :( later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
