At Thu, 18 Mar 2021 17:19:45 -0700, Brian Buhrow <buhrow%nfbcal.org@localhost> wrote:
Subject: Re: trouble running FreeBSD with Xen-4.11 (including weird performance issues)
>
> hello. Are you running these machines in hvm or pvh mode? If
> hvm mode, are you seeing a bunch of cpu taken up on dom0 by the qemu
> process supporting the hvm host?
The dom0 is running XEN3_DOM0.
The domU's are FreeBSD 12.2-p4 kernel (extracted from
/boot/kernel/kernel) with "type='pvh'" with Xen config as:
type = "pvh"
name = "fbsd-test"
memory = 2000
maxmem = 8000
vcpus = 4
vif = [ 'bridge=bridge0' ]
kernel = "/build/images/freebsd-12.2-kernel"
cmdline = 'vfs.root.mountfrom=cd9660:/dev/ada0,vfs.root.mountfrom.options=ro,boot_verbose=YES'
disk = [
'format=raw, vdev=hda, access=ro, target=/build/images/Repacked-FreeBSD-12.2-RELEASE-amd64-bootonly.iso',
'format=raw, vdev=hdb, access=rw, target=/dev/mapper/scratch-fbsd--test.0',
]
> Also, what is the xbd(4) problem you
> refer to?
That was in the opening of this thread, but here's more info.
Note these machines were running a much older (10 months) 8.99.xx kernel
with xen-4.8, and were booting and running FreeBSD 11 and 12 just fine,
with one of them having been in production use for well over a year.
Since upgrading to 9.99.81 and xen-4.11 the production VM was corrupted
and crashed an I now have trouble booting the original ISO or
memstick.img files as the FreeBSD kernel thinks the labels are corrupt.
Trying to mount root from cd9660:/dev/ada0 []...
GEOM_PART: integrity check failed (ada0, MBR)
Mounting from cd9660:/dev/ada0 failed with error 22; retrying for 3 more seconds
Mounting from cd9660:/dev/ada0 failed with error 22.
mountroot: invalid file system specification.
or (for the mini-memstick.img):
xbd0: 386MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0
xbd0: attaching as ada0
xbd0: features: flush
xbd0: synchronize cache commands enabled.
GEOM: new disk ada0
Trying to mount root from ufs:/dev/ada0p3 [ro]...
GEOM_PART: partition 2 has end offset beyond last LBA: 791120 > 790527
GEOM_PART: integrity check failed (ada0, MBR)
mountroot: waiting for device /dev/ada0p3...
Mounting from ufs:/dev/ada0p3 failed with error 19.
Rebuilding the ISO on NetBSD by unpacking it and re-making it with
mkisofs results in a workable image file, as shown below.
(I came across this because we had built a "headless" ISO first with a
serial console boot for an HVM domU, and that booted.)
Then when I try to use an LVM-backed device, e.g. here shown as ada1, I
cannot create a clean filesystem, and repeated fsck's never make it
clean either (and mounting an existing filesystem and writing to it will
eventually create corruption and crash the system):
xbd0: 345MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0
xbd0: attaching as ada0
xbd0: features: flush
xbd0: synchronize cache commands enabled.
GEOM: new disk ada0
xbd1: 40960MB <Virtual Block Device> at device/vbd/832 on xenbusb_front0
xbd1: attaching as ada1
xbd1: features: flush
xbd1: synchronize cache commands enabled.
# newfs ada1
/dev/ada1: 30720.0MB (62914560 sectors) block size 32768, fragment size 4096
using 50 cylinder groups of 626.09MB, 20035 blks, 80256 inodes.
super-block backups (for fsck_ffs -b #) at:
192, 1282432, 2564672, 3846912, 5129152, 6411392, 7693632, 8975872, 10258112,
11540352, 12822592, 14104832, 15387072, 16669312, 17951552, 19233792,
20516032, 21798272, 23080512, 24362752, 25644992, 26927232, 28209472,
29491712, 30773952, 32056192, 33338432, 34620672, 35902912, 37185152,
38467392, 39749632, 41031872, 42314112, 43596352, 44878592, 46160832,
47443072, 48725312, 50007552, 51289792, 52572032, 53854272, 55136512,
56418752, 57700992, 58983232, 60265472, 61547712, 62829952
# fsck -y ada1
** /dev/ada1
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
CG 0: BAD CHECK-HASH 0xd968324d vs 0xa74e812f
SUMMARY INFORMATION BAD
SALVAGE? yes
BLK(S) MISSING IN BIT MAPS
SALVAGE? yes
CG 1: BAD CHECK-HASH 0x340499e8 vs 0x6edad3cf
CG 2: BAD CHECK-HASH 0xca6d214f vs 0x4adbfbb7
CG 3: BAD CHECK-HASH 0x63119b7d vs 0x40980165
CG 4: BAD CHECK-HASH 0x335226f0 vs 0xc0b5d56b
CG 5: BAD CHECK-HASH 0x9a2e9cc2 vs 0xccd0285d
CG 6: BAD CHECK-HASH 0x64472465 vs 0x10d03d4c
CG 7: BAD CHECK-HASH 0xcd3b9e57 vs 0x6c7ed5c6
CG 8: BAD CHECK-HASH 0xc4c05f7f vs 0xb1dc02a5
CG 9: BAD CHECK-HASH 0x6dbce54d vs 0x6429ef41
CG 10: BAD CHECK-HASH 0x93d55dea vs 0x8c9dc519
CG 11: BAD CHECK-HASH 0x3aa9e7d8 vs 0xc3b4abd6
CG 12: BAD CHECK-HASH 0x6aea5a55 vs 0xad04678d
CG 13: BAD CHECK-HASH 0xc396e067 vs 0x605e20d7
CG 14: BAD CHECK-HASH 0x3dff58c0 vs 0x3f41df9a
CG 15: BAD CHECK-HASH 0x9483e2f2 vs 0x24c8b8e
CG 16: BAD CHECK-HASH 0x2e08da90 vs 0x5c622ba1
CG 17: BAD CHECK-HASH 0x877460a2 vs 0xc0cd37e1
CG 18: BAD CHECK-HASH 0x791dd805 vs 0x2cf22f75
CG 19: BAD CHECK-HASH 0xd0616237 vs 0xa660b07d
CG 20: BAD CHECK-HASH 0x8022dfba vs 0x24a42dff
CG 21: BAD CHECK-HASH 0x295e6588 vs 0x25854334
CG 22: BAD CHECK-HASH 0xd737dd2f vs 0xe13cd0c8
CG 23: BAD CHECK-HASH 0x7e4b671d vs 0x4d85fd1d
CG 24: BAD CHECK-HASH 0x77b0a635 vs 0x3f677758
CG 25: BAD CHECK-HASH 0xdecc1c07 vs 0x4f77db87
CG 26: BAD CHECK-HASH 0x20a5a4a0 vs 0xdaffcbe6
CG 27: BAD CHECK-HASH 0x89d91e92 vs 0x52b27914
CG 28: BAD CHECK-HASH 0xd99aa31f vs 0x52637503
CG 29: BAD CHECK-HASH 0x70e6192d vs 0x2d2a9c56
CG 30: BAD CHECK-HASH 0x8e8fa18a vs 0xcd3d934d
CG 31: BAD CHECK-HASH 0x27f31bb8 vs 0x262e150a
CG 32: BAD CHECK-HASH 0xfe75a7bf vs 0x25326f6b
CG 33: BAD CHECK-HASH 0x57091d8d vs 0x38d0ad6
CG 34: BAD CHECK-HASH 0xa960a52a vs 0xa37dd882
CG 35: BAD CHECK-HASH 0x1c1f18 vs 0xad14de25
CG 36: BAD CHECK-HASH 0x505fa295 vs 0x15e8d157
CG 37: BAD CHECK-HASH 0xf92318a7 vs 0xc9d5ff83
CG 38: BAD CHECK-HASH 0x74aa000 vs 0xde57fd7c
CG 39: BAD CHECK-HASH 0xae361a32 vs 0x3d90eebb
CG 40: BAD CHECK-HASH 0xa7cddb1a vs 0x69dba09
CG 41: BAD CHECK-HASH 0xeb16128 vs 0x483d04b2
CG 42: BAD CHECK-HASH 0xf0d8d98f vs 0xb0a5c246
CG 43: BAD CHECK-HASH 0x59a463bd vs 0x16727e2
CG 44: BAD CHECK-HASH 0x9e7de30 vs 0xd42581be
CG 45: BAD CHECK-HASH 0xa09b6402 vs 0x6734ec30
CG 46: BAD CHECK-HASH 0x5ef2dca5 vs 0xa6dd6eb7
CG 47: BAD CHECK-HASH 0xf78e6697 vs 0x90f940a8
CG 48: BAD CHECK-HASH 0x4d055ef5 vs 0x7eb540ba
CG 49: BAD CHECK-HASH 0x2ea1983f vs 0x6682d755
2 files, 2 used, 7612693 free (21 frags, 951584 blocks, 0.0% fragmentation)
***** FILE SYSTEM IS CLEAN *****
***** FILE SYSTEM WAS MODIFIED *****
My next step will probably be to try moving my test machine to xen-4.13.
--
Greg A. Woods <gwoods%acm.org@localhost>
Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost>
Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpqJoRVXrf5P.pgp
Description: OpenPGP Digital Signature