[Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225579 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free ||BSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225579 Rodney W. Grimes changed: What|Removed |Added CC||rgri...@freebsd.org --- Comment #1 from Rodney W. Grimes --- I can do some investigation here, but using an I/O intensive task and evaluating CPU load is probably not a good choice in benchmarks or testing. Are the FreeBSD guests using UFS, or ZFS or ??? for the file system that the dd operations are going to. Is the backing store in ESXi eager or lazy zero? What file system was used in the ubuntu case? What version of Ununtu? What are the I/O rates during this testing? This really is an I/O benchmark and not a CPU benchmark. Would be interesting to see this running a CPU intensive task. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225579 amvandem...@gmail.com changed: What|Removed |Added CC||amvandem...@gmail.com --- Comment #2 from amvandem...@gmail.com --- May be related to bug #173541 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve passthrough problems (update)
On Fri, 19 Jan 2018 17:52:57 -0300 Mario Lobo wrote: > On Thu, 18 Jan 2018 00:58:08 -0800 > Peter Grehan wrote: > > > Hi Mario, > > > > > I'm trying to passthrough a firewire pci card to a windows 7 64 > > > guest. > > > > First, you'll need to verify if that card supports MSI or MSI-x > > since that is required by bhyve for passthru support. This can be > > seen with 'pciconf -lbc' on the FreeBSD host. > > > > > VM exits with: > > > > > > Assertion failed: (mr->name == memp->name), function > > > unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265. > > > Abort trap > > > > This is bug in bhyve when running Windows with PCI devices that > > have more than 1 memory BAR (e.g. Intel igb ethernet devices), due > > to the order that Windows determines BAR sizes. I've been meaning > > to fix this for a long time so will try and get to it. > > > > later, > > > > Peter. > > Hi there: > > Well, now, even without setting up passthrough, the VM doesn't start > (which it did, before I svned up /usr/src). > > With vnc: > > bhyve -c 4 -s 0,amd_hostbridge > -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512 > -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso > -s 10,virtio-net,tap0 > -s 11,fbuf,tcp=0.0.0.0:5900,,w=1600,h=900,wait > -s 20,xhci,tablet > -s 31,lpc > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -m 4G -H -w WIN-764 > fbuf frame buffer base: 0x942e0 [sz 16777216] > > error: > Assertion failed: (error == 0), function modify_bar_registration, > file /usr/src/usr.sbin/bhyve/pci_emul.c, line 491. Abort trap > > > Without vnc: > > bhyve -c 4 -s 0,amd_hostbridge > -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512 > -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso > -s 10,virtio-net,tap0 > -s 20,xhci,tablet > -s 31,lpc > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -m 4G -H -w WIN-764 > > error: > Assertion failed: (mr->name == memp->name), function unregister_mem, > file /usr/src/usr.sbin/bhyve/mem.c, line 265. Abort trap > > > Revisions (/usr/src 11-STABLE): > > working: 321652 > not working (current): 328163 > > Any updates on this issue? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve passthrough problems (update)
Hi Mario, Well, now, even without setting up passthrough, the VM doesn't start (which it did, before I svned up /usr/src). ... working: 321652 not working (current): 328163 ... Any updates on this issue? Can you verify if the issue still occurrs if you destroy the guest before re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 ) later, Peter. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
