PetiteCloud 0.2.5 released
What's new: * Ability to use physical disks as backing stores * Multiple NIC's * Multiple backing stores (1 primary and upto 5 secondary) * Advanced settings -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ 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: Detect of BHyve VM was powered off or rebooted?
On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu neeln...@gmail.com wrote: One question, if bhyve exits, do I have to call bhyveload again before calling bhyve? Yes, that is correct. You will also need to destroy the VM after bhyve exits. Why can't bhyve clean up after itself as the bhyve process exits and destroy the VM? It seems pointless to me for the user to have to explictly destroy the VM. Once the bhyve process exits, I doesn't seem that I can use the VM again anyways. To run the VM again, I seem to need to call: - bhyvectl to destroy the VM - bhyveload to load - bhyve to run the VM Aryeh has pointed out to me that it is the responsibility of the user to explictly destroy and tap and bridge devices used by the bhyve process after it exits. Is this right? What if I have a single bridge0 device, and 10 tap devices, one per VM? If one VM exits and needs to be restarted, do I need to tear down all the taps and bridge? -- Craig ___ 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: Detect of BHyve VM was powered off or rebooted?
On Wed, Feb 12, 2014 at 4:28 AM, Craig Rodrigues rodr...@freebsd.orgwrote: On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu neeln...@gmail.com wrote: One question, if bhyve exits, do I have to call bhyveload again before calling bhyve? Yes, that is correct. You will also need to destroy the VM after bhyve exits. Why can't bhyve clean up after itself as the bhyve process exits and destroy the VM? It seems pointless to me for the user to have to explictly destroy the VM. Once the bhyve process exits, I doesn't seem that I can use the VM again anyways. To run the VM again, I seem to need to call: - bhyvectl to destroy the VM - bhyveload to load - bhyve to run the VM Aryeh has pointed out to me that it is the responsibility of the user to explictly destroy and tap and bridge devices used by the bhyve process after it exits. Is this right? What if I have a single bridge0 device, and 10 tap devices, one per VM? If one VM exits and needs to be restarted, do I need to tear down all the taps and bridge? Yes you do. It gets really harry when you have multple vm's and taps per instance that need to start and stop at arbitrary times. We are currently disccusing this issue on the petitecloud mailing list it might be off topic here to get into too much detail. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ 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: Fwd: CFT: bhyve AMD snapshot
On Tue, Feb 11, 2014 at 7:08 PM, Peter Grehan gre...@freebsd.org wrote: Hi Aryeh, root@:/home/aryeh # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01 EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 This isn't the revision of the bhyve_svm branch - did you possibly do a sync before building this ? svn switch Would you be able to retry with a fresh checkout of the branch e.g. svn co svn://svn.freebsd.org/base/projects/bhyve_svm/ . later, kernel panic during boot -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ 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: Detect of BHyve VM was powered off or rebooted?
Hi Craig, It seems pointless to me for the user to have to explictly destroy the VM. We're working on fixing it. What it gave during the development process (and still gives) is the ability to get post-mortem information when the bhyve process exits. Once the bhyve process exits, I doesn't seem that I can use the VM again anyways. To run the VM again, I seem to need to call: - bhyvectl to destroy the VM - bhyveload to load - bhyve to run the VM Yes, that's correct. The future version will be: /usr/sbin/bhyve to load/run/reboot the VM in a single process. Aryeh has pointed out to me that it is the responsibility of the user to explictly destroy and tap and bridge devices used by the bhyve process after it exits. Is this right? Only if you won't be using them anymore. What if I have a single bridge0 device, and 10 tap devices, one per VM? If one VM exits and needs to be restarted, do I need to tear down all the taps and bridge? No - leave them there. Think of the tap interfaces as ports on a switch, and the bhyve processes as being plugged/unplugged from the ports. 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: Fwd: CFT: bhyve AMD snapshot
Hi Aryeh, kernel panic during boot Can you post a verbose boot log with the panic (i.e. boot -v from the loader prompt) ? 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: Detect of BHyve VM was powered off or rebooted?
On Wed, Feb 12, 2014 at 10:28 AM, Peter Grehan gre...@freebsd.org wrote: No - leave them there. Think of the tap interfaces as ports on a switch, and the bhyve processes as being plugged/unplugged from the ports. Every time I have tried this it has lead to bricking the bridge if done in the wrong order and/or there was a packet in transit on the bridge while you have open end points -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ 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
best branch for bhyve on AMD?
Greetings, I am running FreeBSD 10.0-STABLE r261733 amd64 on a system with an AMD Brisbane CPU: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2835.16-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Family = 0xf Model = 0x6b Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch kldload vmm gives these kernel messages: amd_iommu_init: not implemented amdv_init: not implemented amdv_cleanup: not implemented module_register_init: MOD_LOAD (vmm, 0x80f5abf0, 0) error 6 and # bhyveload -m 256 -d /dev/zvol/bigz/bhyvetest bhyvetest gives: vm_create: Device not configured Am I right in thinking that bhyve support for AMD processors is not yet in -STABLE? If so, is there working code for bhyve under AMD anywhere? Where? -HEAD, projects/bhyve_svm or somewhere else? Is it considered experimental, stable, or something in between? Should it work with the above processor? Looking forward to trying bhyve on this hardware. Thanks! JN ___ 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: best branch for bhyve on AMD?
On Wed, Feb 12, 2014 at 12:14 PM, John Nielsen li...@jnielsen.net wrote: Greetings, I am running FreeBSD 10.0-STABLE r261733 amd64 on a system with an AMD Brisbane CPU: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2835.16-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Family = 0xf Model = 0x6b Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch kldload vmm gives these kernel messages: amd_iommu_init: not implemented amdv_init: not implemented amdv_cleanup: not implemented module_register_init: MOD_LOAD (vmm, 0x80f5abf0, 0) error 6 and # bhyveload -m 256 -d /dev/zvol/bigz/bhyvetest bhyvetest gives: vm_create: Device not configured Am I right in thinking that bhyve support for AMD processors is not yet in -STABLE? If so, is there working code for bhyve under AMD anywhere? Where? -HEAD, projects/bhyve_svm or somewhere else? Is it considered experimental, stable, or something in between? Should it work with the above processor? Looking forward to trying bhyve on this hardware. Thanks! JN This might answer some of your questions: http://bhyve.org/faq/ ___ 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: best branch for bhyve on AMD?
Hi John, Am I right in thinking that bhyve support for AMD processors is not yet in -STABLE? Yes, that's correct. If so, is there working code for bhyve under AMD anywhere? Where? -HEAD, projects/bhyve_svm or somewhere else? projects/bhyve_svm Is it considered experimental, stable, or something in between? I'd home somewhere on the stable side of experimental. I've had good success with it on a Phenom II, but looks like at least 1 user has had issues. Should it work with the above processor? I think your model may be predate the h/w nested paging support that bhyve relies on (EPT, or RVI in early AMD terminology). The list of AMD CPUs with RVI is at: http://support.amd.com/en-us/kb-articles/Pages/GPU120AMDRVICPUsHyperVWin8.aspx ... and the Athlon 64 X2 isn't on that list :( 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
