Проблемы с виртуализацией на 11.2

VirtualBox, QEMU, ESX/ESXi и прочия
Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
teejay
проходил мимо
Сообщения: 7
Зарегистрирован: 2013-09-18 20:56:55

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение teejay » 2018-12-30 11:31:10

Всем првет. Такой вопрос, точнее даже не вопрос, а нужен совет:
есть домашний сервер на котором постоянно крутятся samba, transmission, netatalk, minidlna и несколько других сервисов. Также на нём установлен VirtualBox. В VirtualBox'e работала Win7 64-bit долгое время, пока не пришлось обновиться сначала до 10.4 потом до 11.2. После обновления указанная вм начала вести крейне нестабильно: простоянно происходили bsod'ы. Иногда она не стартовала и т.д.. Я решил создать новую ВМ с аналогичными характеристиками, но это не помогло, она была также не стабильна. Тогда я решил, что проблема может быть с VirtualBox'ом. Перешёл на bhyve и ситуация оказалась такой же: вм перезагружалась, только чуть реже чем на VirtualBox. Пробовал сменить образ, с которого устанавливал систему, тоже не помогло (всегда использовал чистый образ без доп. софта, без активатора и т.д.).
Тогда предположил, что проблема с железом. Но хост работает 24/7, перезагружается только при необходимости обновления, никах проблем, запускал stress для создания нагрузки тоже без проблем. SMARTом контролирую состояние жёстких дисков. ВМ располагаются на одном жёстком диске с системой, в отдельном разделе с zfs. На всякий случай создан SWAP файл на 4 Гб.

dmesg

Код: Выделить всё

Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.2-RELEASE-p7 #0: Tue Dec 18 08:29:33 UTC 2018
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
VT(vga): resolution 640x480
CPU: AMD FX(tm)-8320 Eight-Core Processor            (3515.62-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x600f20  Family=0x15  Model=0x2  Stepping=0
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x3e98320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x1ebbfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,TCE,NodeId,TBM,Topology,PCXC,PNXC>
  Structured Extended Features=0x8<BMI1>
  SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=65536
  TSC: P-state invariant, performance statistics
real memory  = 12884901888 (12288 MB)
avail memory = 11874603008 (11324 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <GBT    GBTUACPI>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 8 core(s)
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.1> irqs 0-23 on motherboard
SMP: AP CPU #4 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC-low" frequency 1757809590 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4580, 0) error 19
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <GBT GBTUACPI> on motherboard
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKA (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKB (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKC (20171214/dspkginit-517)
ACPI Error: Could not find/resolve named package element: LNKD (20171214/dspkginit-517)
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdee0000-0xfdeeffff,0xfdd00000-0xfddfffff irq 18 at device 5.0 on pci1
vgapci0: Boot video device
hdac0: <ATI RS780 HDA Controller> mem 0xfdefc000-0xfdefffff irq 19 at device 5.1 on pci1
pcib2: <ACPI PCI-PCI bridge> irq 18 at device 6.0 on pci0
pci2: <ACPI PCI bus> on pcib2
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xde00-0xdeff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 18 at device 0.0 on pci2
re0: Using 1 MSI-X message
re0: turning off MSI enable bit.
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: 94:de:80:bf:f9:2d
re0: netmap queues/slots: TX 1/256, RX 1/256
ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0
ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x22000<ATI_PMP_BUG,1MSI>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe02e000-0xfe02efff irq 16 at device 18.0 on pci0
usbus0 on ohci0
usbus0: 12Mbps Full Speed USB v1.0
ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe02d000-0xfe02dfff irq 16 at device 18.1 on pci0
usbus1 on ohci1
usbus1: 12Mbps Full Speed USB v1.0
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe02c000-0xfe02c0ff irq 17 at device 18.2 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
usbus2: 480Mbps High Speed USB v2.0
ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe02b000-0xfe02bfff irq 18 at device 19.0 on pci0
usbus3 on ohci2
usbus3: 12Mbps Full Speed USB v1.0
ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe02a000-0xfe02afff irq 18 at device 19.1 on pci0
usbus4 on ohci3
usbus4: 12Mbps Full Speed USB v1.0
ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe029000-0xfe0290ff irq 19 at device 19.2 on pci0
usbus5: EHCI version 1.0
usbus5 on ehci1
usbus5: 480Mbps High Speed USB v2.0
atapci0: <ATI IXP700/800 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0
ata0: <ATA channel> at channel 0 on atapci0
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci3: <ACPI PCI bus> on pcib3
ohci4: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe028000-0xfe028fff irq 18 at device 20.5 on pci0
usbus6 on ohci4
usbus6: 12Mbps Full Speed USB v1.0
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb4
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
Timecounters tick every 1.000 msec
ugen1.1: <ATI OHCI root HUB> at usbus1
ugen6.1: <ATI OHCI root HUB> at usbus6
uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
hdacc0: <ATI RS690/780 HDA CODEC> at cad 0 on hdac0
hdaa0: <ATI RS690/780 Audio Function Group> at nid 1 on hdacc0
pcm0: <ATI RS690/780 (HDMI)> at nid 3 on hdaa0
ugen3.1: <ATI OHCI root HUB> at usbus3
ugen0.1: <ATI OHCI root HUB> at usbus0
ugen5.1: <ATI EHCI root HUB> at usbus5
ugen2.1: <ATI EHCI root HUB> at usbus2
ugen4.1: <ATI OHCI root HUB> at usbus4
uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
uhub3: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub5: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
uhub6: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5
uhub1: 2 ports with 2 removable, self powered
uhub0: 3 ports with 3 removable, self powered
uhub2: 3 ports with 3 removable, self powered
uhub4: 3 ports with 3 removable, self powered
uhub5: 3 ports with 3 removable, self powered
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD2500BEKT-00PVMT0 01.01A01> ATA8-ACS SATA 2.x device
ada0: Serial Number WD-WX11A21M8305
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 238475MB (488397168 512 byte sectors)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <WDC WD10EZEX-08M2NA0 01.01A01> ACS-2 ATA SATA 3.x device
ada1: Serial Number WD-WCC3F1998252
ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors)
ada2 at ahcich3 bus 0 scbus3 target 0 lun 0
ada2: <WDC WD5000LPVX-55V0TT0 01.01A01> ACS-2 ATA SATA 3.x device
ada2: Serial Number WD-WX71A1380191
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 476940MB (976773168 512 byte sectors)
ada3 at ahcich4 bus 0 scbus4 target 0 lun 0
ada3: <ST9500325AS D005DEM1> ATA8-ACS SATA 2.x device
ada3: Serial Number 5VEN6100
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 476940MB (976773168 512 byte sectors)
ada4 at ahcich5 bus 0 scbus5 target 0 lun 0
ada4: <WDC WD5000LPVT-22G33T0 01.01A01> ATA8-ACS SATA 2.x device
ada4: Serial Number WD-WX51A1386753
ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 476940MB (976773168 512 byte sectors)
ada4: quirks=0x1<4K>
Trying to mount root from ufs:/dev/ada0p2 [rw]...
GEOM: ada1: the primary GPT table is corrupt or invalid.
GEOM: ada1: using the secondary instead -- recovery strongly advised.
GEOM: ada4: the primary GPT table is corrupt or invalid.
GEOM: ada4: using the secondary instead -- recovery strongly advised.
GEOM: diskid/DISK-WD-WCC3F1998252: the primary GPT table is corrupt or invalid.
GEOM: diskid/DISK-WD-WCC3F1998252: using the secondary instead -- recovery strongly advised.
uhub3: 6 ports with 6 removable, self powered
uhub6: 6 ports with 6 removable, self powered
GEOM: diskid/DISK-WD-WX51A1386753: the primary GPT table is corrupt or invalid.
GEOM: diskid/DISK-WD-WX51A1386753: using the secondary instead -- recovery strongly advised.
random: unblocking device.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
re0: link state changed to DOWN
re0: link state changed to UP
pflog0: promiscuous mode enabled
bridge0: Ethernet address: 02:90:60:23:9c:00
bridge0: changing name to 'vm-public'
re0: promiscuous mode enabled
vm-public: link state changed to UP
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1335, size: 65536
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1233, size: 53248
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1108, size: 8192
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 304929, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1379, size: 65536
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 37417, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262871, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 311324, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1847, size: 20480
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 90042, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 296970, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 311379, size: 16384
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 36448, size: 8192
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 382027, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 635985, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 640096, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 52972, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 639369, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 635002, size: 16384
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1379, size: 65536
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 637625, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 640006, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 640041, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 36448, size: 8192
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 382027, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 635985, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 640096, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 52972, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 639369, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 635002, size: 16384
pid 2220 (VBoxHeadless), uid 0 inumber 21 on /: filesystem full
Failed to write core file for process VBoxHeadless (error 28)
pid 2220 (VBoxHeadless), uid 0: exited on signal 8
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1379, size: 65536
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4639, size: 8192
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 637625, size: 4096
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
pid 92563 (VBoxHeadless), uid 0 inumber 21 on /: filesystem full
Failed to write core file for process VBoxHeadless (error 28)
pid 92563 (VBoxHeadless), uid 0: exited on signal 11
tap0: Ethernet address: 00:bd:98:da:80:00
tap0: promiscuous mode enabled
re0: link state changed to DOWN
vm-public: link state changed to DOWN
tap0: link state changed to UP
vm-public: link state changed to UP
re0: link state changed to UP
pid 24875 (bhyve), uid 0: exited on signal 11
tap0: link state changed to DOWN
re0: link state changed to DOWN
vm-public: link state changed to DOWN
re0: link state changed to UP
vm-public: link state changed to UP
tap0: Ethernet address: 00:bd:09:7a:81:00
tap0: promiscuous mode enabled
re0: link state changed to DOWN
vm-public: link state changed to DOWN
tap0: link state changed to UP
vm-public: link state changed to UP
re0: link state changed to UP
tap0: link state changed to DOWN
re0: link state changed to DOWN
vm-public: link state changed to DOWN
re0: link state changed to UP
vm-public: link state changed to UP
Лог ошибок из VirtualBox (ошибка похоже на 01:48:38.919903)

Код: Выделить всё

01:47:27.991822 AsyncCompletion: Task 0x00000807f10b40 completed after 16 seconds
01:47:28.221321 AsyncCompletion: Task 0x00000814e43ac0 completed after 16 seconds
01:47:28.558167 AsyncCompletion: Task 0x00000807efe700 completed after 16 seconds
01:47:29.041012 AsyncCompletion: Task 0x00000807f101c0 completed after 17 seconds
01:47:29.139520 AsyncCompletion: Task 0x00000807f10700 completed after 17 seconds
01:47:29.401329 AsyncCompletion: Task 0x00000814e43a00 completed after 17 seconds
01:47:29.527555 AsyncCompletion: Task 0x00000807efe5c0 completed after 17 seconds
01:47:29.939533 AsyncCompletion: Task 0x00000807efef80 completed after 17 seconds
01:47:30.755086 AsyncCompletion: Task 0x00000807efe7c0 completed after 18 seconds
01:47:37.901309 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 7 seconds ago
01:47:38.604554 VMMDev: GuestHeartBeat: Guest is alive (gone 8 231 021 719 ns)
01:48:30.378569 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 6 seconds ago
01:48:32.098549 VMMDev: GuestHeartBeat: Guest is alive (gone 12 147 066 186 ns)
01:48:38.919903 PIIX3 IDE: guest issued command 0xa0 while controller busy
01:48:47.111236 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:48:47.397738 VMMDev: GuestHeartBeat: Guest is alive (gone 4 618 423 467 ns)
01:49:57.586271 AsyncCompletion: Task 0x00000807efedc0 completed after 10 seconds
01:49:57.701769 AsyncCompletion: Task 0x00000807efea00 completed after 10 seconds
01:49:57.719908 AsyncCompletion: Task 0x00000807f105c0 completed after 10 seconds
01:49:57.925021 AsyncCompletion: Task 0x00000807efeac0 completed after 10 seconds
01:49:58.020105 AsyncCompletion: Task 0x00000807f102c0 completed after 10 seconds
01:50:11.574640 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:50:12.953477 VMMDev: GuestHeartBeat: Guest is alive (gone 5 516 971 033 ns)
01:52:06.935883 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:52:07.497176 VMMDev: GuestHeartBeat: Guest is alive (gone 4 842 943 634 ns)
01:52:35.027387 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 5 seconds ago
01:52:35.430469 VMMDev: GuestHeartBeat: Guest is alive (gone 7 712 978 104 ns)
01:52:44.818660 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:52:45.569496 VMMDev: GuestHeartBeat: Guest is alive (gone 5 523 217 340 ns)
01:54:46.644717 AsyncCompletion: Task 0x00000807efe080 completed after 10 seconds
01:54:46.732799 AsyncCompletion: Task 0x00000814f67a40 completed after 10 seconds
01:54:46.930323 AsyncCompletion: Task 0x00000807efe700 completed after 10 seconds
01:54:47.117312 AsyncCompletion: Task 0x00000807f10fc0 completed after 10 seconds
01:54:47.507889 AsyncCompletion: Task 0x00000814f67940 completed after 10 seconds
01:54:47.646297 AsyncCompletion: Task 0x00000807efe900 completed after 11 seconds
01:54:47.848767 AsyncCompletion: Task 0x00000807efe880 completed after 11 seconds
01:54:47.928946 AsyncCompletion: Task 0x00000807f10e40 completed after 11 seconds
01:54:48.103425 AsyncCompletion: Task 0x00000814f671c0 completed after 11 seconds
01:54:48.259413 AsyncCompletion: Task 0x00000814f67c00 completed after 11 seconds
01:54:48.387359 AsyncCompletion: Task 0x00000807f10780 completed after 11 seconds
01:54:49.391892 AsyncCompletion: Task 0x00000814e43900 completed after 12 seconds
01:54:49.392016 AsyncCompletion: Task 0x00000814f670c0 completed after 12 seconds
01:54:49.392156 AsyncCompletion: Task 0x00000807efe180 completed after 11 seconds
01:54:51.701090 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 6 seconds ago
01:54:52.391547 VMMDev: GuestHeartBeat: Guest is alive (gone 7 096 212 216 ns)
01:55:20.807957 AsyncCompletion: Task 0x00000814e43b40 completed after 10 seconds
01:55:21.329406 AsyncCompletion: Task 0x00000814f67a80 completed after 11 seconds
01:55:23.177023 AsyncCompletion: Task 0x00000807efed80 completed after 13 seconds
Лог bhyve не очень информативен, однако изучения дампа ошибки в Win7 показывает, что виновник, как правило ntoskrnl.exe +7fd00 или ошибка 0x00000101 или что-то аналогичное.

Код: Выделить всё

дек. 18 22:57:27:  [bhyve iso device: -s 3:0,ahci-cd,/usr/local/vm/.config/null.iso]
дек. 18 22:57:27: starting bhyve (run 3)
дек. 19 03:19:18: bhyve exited with status 0
дек. 19 03:19:18: restarting
дек. 19 03:19:18:  [bhyve options: -c 4 -m 4G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 0e72be1d-fa50-11e8-9a71-94de80bff92d -u]
дек. 19 03:19:18:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/usr/local/vm/winguest/disk0.img,sectorsize=512 -s 5:0,ahci-cd,/mnt/share/downloads/virtio.iso -s 6:0,virtio-net,tap0,mac=58:9c:fc:02:04:cb -s 7:0,fbuf,tcp=0.0.0.0:3388,w=1600,h=900]
дек. 19 03:19:18:  [bhyve console: -l com1,/dev/nmdm-winguest.1A]
дек. 19 03:19:18:  [bhyve iso device: -s 3:0,ahci-cd,/usr/local/vm/.config/null.iso]
дек. 19 03:19:18: starting bhyve (run 4)
дек. 22 03:05:27: bhyve exited with status 0
дек. 22 03:05:27: restarting
дек. 22 03:05:27:  [bhyve options: -c 4 -m 4G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 0e72be1d-fa50-11e8-9a71-94de80bff92d -u]
дек. 22 03:05:27:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/usr/local/vm/winguest/disk0.img,sectorsize=512 -s 5:0,ahci-cd,/mnt/share/downloads/virtio.iso -s 6:0,virtio-net,tap0,mac=58:9c:fc:02:04:cb -s 7:0,fbuf,tcp=0.0.0.0:3388,w=1600,h=900]
дек. 22 03:05:27:  [bhyve console: -l com1,/dev/nmdm-winguest.1A]
дек. 22 03:05:28:  [bhyve iso device: -s 3:0,ahci-cd,/usr/local/vm/.config/null.iso]
дек. 22 03:05:28: starting bhyve (run 5)
дек. 22 23:09:36: bhyve exited with status 0
дек. 22 23:09:36: restarting
В каком направлении копать? Куда смотреть?
Может необходимо более детально изучть состояние железа? Какими интсрументами?
Систему переустанавливать нет особого желания.

Хостинговая компания Host-Food.ru
Хостинг HostFood.ru
 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

snorlov
подполковник
Сообщения: 3684
Зарегистрирован: 2008-09-04 11:51:25
Откуда: Санкт-Петербург

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение snorlov » 2018-12-31 21:15:29

Вы знаете у вас все как то странно обновилось, vboxdrv стартует толи 2-а толи 3-и раза, при старте вм пишется, что дисковая система заполнена...
Вы после перехода на bhyve загрузку модулей vbox'а удалили?
У меня в свое время вм в vbox'е работала тоже не совсем стабильно пока я не привязал ее процесс к конкретному ядру через cpuset

teejay
проходил мимо
Сообщения: 7
Зарегистрирован: 2013-09-18 20:56:55

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение teejay » 2019-01-01 0:09:04

Дисковая подсистемы была заполнена из-за того, что Vbox записал дамп в /. Модули сейчас загружаю те, которые мне нужны. Если хочу запустить virtualbox то выгружаю vmm.ko и наоборот.
Про cpuset не знал. Надо будет почитать.

snorlov
подполковник
Сообщения: 3684
Зарегистрирован: 2008-09-04 11:51:25
Откуда: Санкт-Петербург

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение snorlov » 2019-01-02 12:54:54

Да кстати в bhyve винду рекомендуют грузить через effi...

guest
проходил мимо

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение guest » 2019-01-02 22:50:59

swap_pager: indefinite wait buffer: bufobj:
- означает высокую нагрузку на дисковую подсистему с которой последняя
не справляется, при работе со swap запросы вылетают по таймауту

teejay
проходил мимо
Сообщения: 7
Зарегистрирован: 2013-09-18 20:56:55

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение teejay » 2019-01-03 11:49:44

guest писал(а):
2019-01-02 22:50:59
- означает высокую нагрузку на дисковую подсистему с которой последняя
не справляется, при работе со swap запросы вылетают по таймауту
Вернуться к началу
Да, но это на этапе загрузки системы, пока вм не запущена.

Аватара пользователя
damir_madaga
старшина
Сообщения: 447
Зарегистрирован: 2007-10-01 8:13:38
Откуда: Красноярск
Контактная информация:

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение damir_madaga » 2019-02-13 5:49:28

У меня похожие проблемы с 11,2 только в Virtualbox крутится линукс, видимо версия виртуалки не важна. Куда капать не знаю, раза два в сутки падает.

Код: Выделить всё

vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
em0: promiscuous mode enabled
em1: promiscuous mode enabled
em2: promiscuous mode enabled
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed to DOWN
em0: link state changed to UP
em1: link state changed to DOWN
em1: link state changed to UP
em1: link state changed to DOWN
em1: link state changed to UP
em1: link state changed to DOWN
em1: link state changed to UP
em1: link state changed to DOWN
em1: link state changed to UP
pid 98500 (VBoxHeadless), uid 0: exited on signal 11 (core dumped)
em2: promiscuous mode disabled
em1: promiscuous mode disabled
em0: promiscuous mode disabled
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
em0: promiscuous mode enabled
em1: promiscuous mode enabled
em2: promiscuous mode enabled
root@srv-jail:/home/damir # uname -a
FreeBSD srv-jail 11.2-RELEASE-p5 FreeBSD 11.2-RELEASE-p5 #0: Tue Nov 27 09:33:52 UTC 2018     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
root@srv-jail:/home/damir # 
Женщины и софт - должны быть бесплатными!

teejay
проходил мимо
Сообщения: 7
Зарегистрирован: 2013-09-18 20:56:55

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение teejay » 2019-02-23 9:46:29

Нужно проверять свободную оперативную память, у меня была проблема с тем, что zfs съдал всю совободную ОЗУ и ВМ вываливалась, после того как я ограничил объём памяти, который может использовать ZFS, то все проблемы ушли.

Аватара пользователя
damir_madaga
старшина
Сообщения: 447
Зарегистрирован: 2007-10-01 8:13:38
Откуда: Красноярск
Контактная информация:

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение damir_madaga » 2019-03-25 10:30:11

Я решил изменением настроек машины сменил с 32 битной системы на 64 и все стабилизировалось.
Женщины и софт - должны быть бесплатными!


buzzukin
рядовой
Сообщения: 37
Зарегистрирован: 2011-08-26 7:35:30

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение buzzukin » 2019-04-15 16:23:18

teejay, расскажи как ограничивал ZFS

Аватара пользователя
Neus
капитан
Сообщения: 1772
Зарегистрирован: 2008-09-08 21:59:56

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение Neus » 2019-04-15 19:29:41

sysctl vfs.zfs.arc_max=
«Вы никогда не сумеете решить возникшую проблему,
если сохраните то же мышление и тот же подход,
который привёл вас к этой проблеме.»
© Альберт Эйнштейн


Sailbine
проходил мимо
Сообщения: 2
Зарегистрирован: 2019-04-25 15:53:39

Проблемы с виртуализацией на 11.2

Непрочитанное сообщение Sailbine » 2019-04-25 16:01:48

Спасибо всем за ответы. Сам сталкивался с похожей проблемой.