FreeBSD › freebsd-xen

Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Classic

List

Threaded

17 messages Options

R0me0 ***

Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Guys,

I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC amd64

When booting systemrescuecd-6.0.3.iso ( http://www.system-rescue-cd.org )
, my system just hangs and reboot.

Just tried an older version and it's ok.

I don't have any log to help. If you guys want and some help, I can provide
more information.

Bests,

Packages installed:

# pkg info
argp-standalone-1.3_3 Standalone version of arguments parsing
functions from GLIBC
bareos17-client-17.2.7_3 Backup archiving recovery open sourced
(client)
ca_root_nss-3.44.1 Root certificate bundle from the Mozilla
Project
curl-7.65.1 Command line tool and library for
transferring data with URLs
doas-6.0p3 Simple sudo alternative to run commands as
another user
gettext-runtime-0.20.1 GNU gettext runtime libraries and programs
glib-2.56.3_5,1 Some useful routines of C programming
(current stable version)
indexinfo-0.3.1 Utility to regenerate the GNU info page index
jansson-2.12 C library for encoding, decoding, and
manipulating JSON data
libffi-3.2.1_3 Foreign Function Interface
libiconv-1.14_11 Character set conversion library
libnghttp2-1.39.1 HTTP/2.0 C Library
libxml2-2.9.9 XML parser library for GNOME
lzo2-2.10_1 Portable speedy, lossless data compression
library
mtr-nox11-0.92_1 Traceroute and ping in a single network
diagnostic tool
p5-Path-Tiny-0.108 File path utility
pcre-8.43_1 Perl Compatible Regular Expressions library
perl5-5.28.2 Practical Extraction and Report Language
pixman-0.34.0_1 Low-level pixel manipulation library
pkg-1.11.1 Package manager
python27-2.7.16_1 Interpreted object-oriented programming
language
python36-3.6.8_2 Interpreted object-oriented programming
language
qemu-utils-3.0.1_1 QEMU userland utilities
readline-8.0.0 Library for editing command lines as they
are typed
seabios-1.11.0_2 Open source implementation of a 16bit X86
BIOS
strongswan-5.8.0 Open Source IKEv2 IPsec-based VPN solution
vim-console-8.1.1439 Improved version of the vi editor (console
only)
xen-kernel-4.12.0_2 Hypervisor using a microkernel design
xen-tools-4.12.0_1 Xen management tools
yajl-2.1.0 Portable JSON parsing and serialization
library in ANSI C

And here the relevant dmesg:

---<<BOOT>>---
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 12.0-RELEASE-p6 GENERIC amd64
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
VT(vga): text 80x25
XEN: Hypervisor version 4.12 detected.
CPU: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz (3500.03-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x306e4 Family=0x6 Model=0x3e Stepping=4

Features=0x1fc3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT>

Features2=0xffba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV>
AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
AMD Features2=0x1<LAHF>
Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS>
Structured Extended Features3=0x9c000000<IBPB,STIBP,L1DFL,SSBD>
XSAVE Features=0x1<XSAVEOPT>
AMD Extended Feature Extensions ID EBX=0x1000
TSC: P-state invariant
Hypervisor: Origin = "XenVMMXenVMM"
real memory = 21522096128 (20525 MB)
avail memory = 18692644864 (17826 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table: < >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
random: unblocking device.
ioapic0 <Version 1.1> irqs 0-23 on motherboard
ioapic1 <Version 1.1> irqs 24-47 on motherboard
Launching APs: 1
random: entropy device external interface
netmap: loaded module
[ath_hal] loaded
module_register_init: MOD_LOAD (vesa, 0xffffffff810f9a00, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
kbd1 at kbdmux0
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
acpi0: <SUPERM SMCI--MB> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
hpet0: HPET never increments, disabling
device_attach: hpet0 attach returned 6
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 27 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 27 at device 1.1 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 33 at device 2.0 on pci0
pci3: <ACPI PCI bus> on pcib3
mfi0: <LSI MegaSAS Gen2> port 0xe000-0xe0ff mem
0xfba60000-0xfba63fff,0xfba00000-0xfba3ffff irq 32 at device 0.0 on pci3
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23
mfi0: FW MaxCmds = 1008, limiting to 128
mfi0: 20431 (614968582s/0x0020/info) - Shutdown command received from host
mfi0: 20432 (614968582s/0x0002/info) - Unexpected sense: PD 05(e0xfc/s0)
Path 4433221103000000, CDB: 2a 00 16 40 fd 02 00 01 00 00, Sense: 2/04/02
mfi0: 20433 (614968582s/0x0002/info) - Power state change on PD
05(e0xfc/s0) from POWERSAVE(1) to TRANSITION(ff)
mfi0: 20434 (614968582s/0x0002/info) - Unexpected sense: PD 05(e0xfc/s0)
Path 4433221103000000, CDB: 2a 00 16 40 fe 02 00 01 00 00, Sense: 2/04/02
mfi0: 20435 (boot + 3s/0x0020/info) - Firmware initialization started (PCI
ID 0079/1000/9260/1000)
mfi0: 20436 (boot + 3s/0x0020/info) - Firmware version 2.130.403-4660
mfi0: 20437 (boot + 5s/0x0020/info) - Package version 12.15.0-0239
mfi0: 20438 (boot + 5s/0x0020/info) - Board Revision 86C
mfi0: 20439 (boot + 24s/0x0002/info) - Inserted: PD 04(e0xff/s1)
mfi0: 20440 (boot + 24s/0x0002/info) - Inserted: PD 04(e0xff/s1) Info:
enclPd=ffff, scsiType=0, portMap=02,
sasAddr=4433221102000000,0000000000000000
mfi0: 20441 (boot + 24s/0x0002/info) - Inserted: PD 05(e0xff/s0)
mfi0: 20442 (boot + 24s/0x0002/info) - Inserted: PD 05(e0xff/s0) Info:
enclPd=ffff, scsiType=0, portMap=01,
sasAddr=4433221103000000,0000000000000000
mfi0: 20443 (boot + 24s/0x0002/info) - Inserted: PD 06(e0xff/s3)
mfi0: 20444 (boot + 24s/0x0002/info) - Inserted: PD 06(e0xff/s3) Info:
enclPd=ffff, scsiType=0, portMap=00,
sasAddr=4433221100000000,0000000000000000
mfi0: 20445 (boot + 24s/0x0002/info) - Inserted: PD 07(e0xff/s2)
mfi0: 20446 (boot + 24s/0x0002/info) - Inserted: PD 07(e0xff/s2) Info:
enclPd=ffff, scsiType=0, portMap=03,
sasAddr=4433221101000000,0000000000000000
mfi0: 20447 (boot + 25s/0x0001/info) - Policy change on VD 00/0 to
[ID=00,dcp=21,ccp=20,ap=0,dc=0] from [ID=00,dcp=21,ccp=21,ap=0,dc=0]
mfi0: 20448 (boot + 25s/0x0001/info) - Policy change on VD 01/1 to
[ID=01,dcp=21,ccp=20,ap=0,dc=0] from [ID=01,dcp=21,ccp=21,ap=0,dcpcib4: =0]
mfi0: 20449 (boot + 25s/0x0001/info) - Policy change on VD 02/2 to
[ID=02,dcp=21,ccp=20,ap=0,dc=0] from [ID=02,dcp=21,ccp=21,ap=0,dc=0]
mfi0: 20450 (614968626s/0x0020/info) - Time established as 06/27/19
16:37:06; (35 seconds since power on)
mfi0: 20451 (614968723s/0x0020/info) - Host driver is loaded and operational
<ACPI PCI-PCI bridge> irq 41 at device 3.0 on pci0
pci4: <ACPI PCI bus> on pcib4
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem
0xfb900000-0xfb91ffff,0xfb920000-0xfb923fff irq 40 at device 0.0 on pci4
igb0: attach_pre capping queues at 8
igb0: using 1024 tx descriptors and 1024 rx descriptors
igb0: msix_init qsets capped at 8
igb0: pxm cpus: 2 queue msgs: 9 admincnt: 1
igb0: using 2 rx queues 2 tx queues
igb0: Using MSIX interrupts with 3 vectors
igb0: allocated for 2 tx_queues
igb0: allocated for 2 rx_queues
igb0: Ethernet address: 0c:c4:7a:4d:bc:a8
igb0: netmap queues/slots: TX 2/1024, RX 2/1024
pcib5: <ACPI PCI-PCI bridge> irq 41 at device 3.2 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 17.0 on pci0
pci6: <ACPI PCI bus> on pcib6
pci0: <simple comms> at device 22.0 (no driver attached)
pci0: <simple comms> at device 22.1 (no driver attached)
ehci0: <Intel Patsburg USB 2.0 controller> mem 0xfbb23000-0xfbb233ff irq 16
at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
usbus0: 480Mbps High Speed USB v2.0
ehci1: <Intel Patsburg USB 2.0 controller> mem 0xfbb22000-0xfbb223ff irq 23
at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci1
usbus1: 480Mbps High Speed USB v2.0
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci7: <ACPI PCI bus> on pcib7
vgapci0: <VGA-compatible display> mem
0xfa000000-0xfaffffff,0xfb800000-0xfb803fff,0xfb000000-0xfb7fffff irq 16 at
device 4.0 on pci7
vgapci0: Boot video device
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Patsburg AHCI SATA controller> port
0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem
0xfbb21000-0xfbb217ff irq 18 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
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
ahciem0: <AHCI enclosure management bridge> on ahci0
pcib8: <ACPI Host-PCI bridge> on acpi0
pci8: <ACPI PCI bus> on pcib8
pci8: <dasp, performance counters> at device 14.1 (no driver attached)
pci8: <dasp, performance counters> at device 19.1 (no driver attached)
pci8: <dasp, performance counters> at device 19.5 (no driver attached)
acpi_button0: <Power Button> on acpi0
acpi_syscontainer0: <System Container> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
xenpv0: <Xen PV bus> on motherboard
granttable0: <Xen Grant-table Device> on xenpv0
gntdev0: <Xen grant-table user-space device> on xenpv0
debug0: <Xen debug handler> on xenpv0
xc0: <Xen Console> on xenpv0
xen_et0: <Xen PV Clock> on xenpv0
Event timer "XENTIMER" frequency 1000000000 Hz quality 950
Timecounter "XENTIMER" frequency 1000000000 Hz quality 950
xen_et0: registered as a time-of-day clock, resolution 0.000001s
xenstore0: <XenStore> on xenpv0
xsd_dev0: <Xenstored user-space device> on xenpv0
evtchn0: <Xen event channel user-space device> on xenpv0
privcmd0: <Xen privileged interface user-space device> on xenpv0
orm0: <ISA Option ROMs> at iomem
0xc0000-0xc7fff,0xc8000-0xce7ff,0xce800-0xcf7ff pnpid ORM0000 on isa0
vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff pnpid
PNP0900 on isa0
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 10.000 msec
Timecounters tick every 10.000 msec
mfid0 on mfi0
mfid0: 3814912MB (7812939776 sectors) RAID volume (no label) is optimal
mfid1 on mfi0
mfid1: 228416MB (467795968 sectors) RAID volume (no label) is optimal
mfid2 on mfi0
mfid2: 228416MB (467795968 sectors) RAID volume (no label) is optimal
ugen1.1: <Intel EHCI root HUB> at usbus1
ugen0.1: <Intel EHCI root HUB> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
Trying to mount root from zfs:fbroot/ROOT/default []...
Root mount waiting for: usbus1 usbus0
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen1.2: <vendor 0x8087 product 0x0024> at usbus1
uhub2 on uhub0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus1
ugen0.2: <vendor 0x8087 product 0x0024> at usbus0
uhub3 on uhub1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus0
Root mount waiting for: usbus1 usbus0
uhub3: 6 ports with 6 removable, self powered
uhub2: 8 ports with 8 removable, self powered
ugen0.3: <Winbond Electronics Corp Hermon USB hidmouse Device> at usbus0
ukbd0 on uhub3
ukbd0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev
1.10/0.01, addr 3> on usbus0
kbd2 at ukbd0
ioat0: <IVB IOAT Ch0> mem 0xfbb1c000-0xfbb1ffff irq 31 at device 4.0 on pci0
ioat0: Capabilities:
2f7<PQ,Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat1: <IVB IOAT Ch1> mem 0xfbb18000-0xfbb1bfff irq 39 at device 4.1 on pci0
ioat1: Capabilities:
2f7<PQ,Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat2: <IVB IOAT Ch2> mem 0xfbb14000-0xfbb17fff irq 31 at device 4.2 on pci0
ioat2: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat3: <IVB IOAT Ch3> mem 0xfbb10000-0xfbb13fff irq 39 at device 4.3 on pci0
ioat3: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat4: <IVB IOAT Ch4> mem 0xfbb0c000-0xfbb0ffff irq 31 at device 4.4 on pci0
ioat4: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat5: <IVB IOAT Ch5> mem 0xfbb08000-0xfbb0bfff irq 39 at device 4.5 on pci0
ioat5: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat6: <IVB IOAT Ch6> mem 0xfbb04000-0xfbb07fff irq 31 at device 4.6 on pci0
ioat6: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ioat7: <IVB IOAT Ch7> mem 0xfbb00000-0xfbb03fff irq 39 at device 4.7 on pci0
ioat7: Capabilities:
f7<Extended_APIC_ID,Block_Fill,Move_CRC,DCA,Marker_Skipping,CRC,Page_Break>
ums0 on uhub3
ums0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev
1.10/0.01, addr 3> on usbus0
ums0: 3 buttons and [Z] coordinates ID=0
pflog0: promiscuous mode enabled
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbusb_back0: <Xen Backend Devices> on xenstore0
xenballoon0: <Xen Balloon Device> on xenstore0
xctrl0: <Xen Control Device> on xenstore0
xs_dev0: <Xenstore user-space device> on xenstore0
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

Roger Pau Monné

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

On Fri, Jun 28, 2019 at 12:02:37PM +0000, R0me0 *** wrote:
> Guys,
>
> I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC amd64

I guess this is on the host?

> When booting systemrescuecd-6.0.3.iso ( http://www.system-rescue-cd.org )
> , my system just hangs and reboot.

So you are trying to boot systemrescuecd as a guest on the Xen host?

Can you paste your guest config file?

> Just tried an older version and it's ok.
>
> I don't have any log to help. If you guys want and some help, I can provide
> more information.

Could you get a serial hooked up to that box so we can get the trace?

Without some kind of trace it's going to be hard to debug this.

Thanks, Roger.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Hello Roger,

>So you are trying to boot systemrescuecd as a guest on the Xen host?
Yes.

Here is the config I have used:

# cat livecd.cfg

builder = "hvm"
name = "livecd"
memory = 2048
cpus="all,^0-1"
vcpus = 2
vif = [ 'type=vif,bridge=sandbox' ]
disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,
'/home/iso/systemrescuecd-6.0.3.iso,raw,xvdb:cdrom,r' ]
boot = 'd'
vnc = 1
vnclisten = '127.0.0.1'
serial = 'pty'

Regarding this:

> Could you get a serial hooked up to that box so we can get the trace?

Could you help me to provide the information you asked.

Thank you .

Kind regards,

Em qui, 4 de jul de 2019 às 07:26, Roger Pau Monné <[hidden email]>
escreveu:

> On Fri, Jun 28, 2019 at 12:02:37PM +0000, R0me0 *** wrote:
> > Guys,
> >
> > I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC amd64
>
> I guess this is on the host?
>
> > When booting systemrescuecd-6.0.3.iso ( http://www.system-rescue-cd.org
> )
> > , my system just hangs and reboot.
>
> So you are trying to boot systemrescuecd as a guest on the Xen host?
>
> Can you paste your guest config file?
>
> > Just tried an older version and it's ok.
> >
> > I don't have any log to help. If you guys want and some help, I can
> provide
> > more information.
>
> Could you get a serial hooked up to that box so we can get the trace?
>
> Without some kind of trace it's going to be hard to debug this.
>
> Thanks, Roger.
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

I tried to boot kali linux (
https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as guest.

The machine freezes on the same way I am using the latest xen 4.12 on
freebsd

here is the screenshot of console:

[image: 2019-07-23-084718_853x193_scrot.png]

and here is the xl dmesg

(d12) Detected Xen v4.12.0
(d12) xen: copy BIOS tables...
(d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60
(d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40
(d12) Copying PIR from 0x00010040 to 0x000f5cc0
(d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90
(d12) Using pmtimer, ioport 0xb008
(d12) Scan for VGA option rom
(d12) Running option rom at c000:0003
(d12) pmm call arg1=0
(d12) Turning on vga text mode console
(d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06)
(d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8
(d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(d12) ATA controller 2 at 170/374/0 (irq 15 dev 9)
(d12) Found 0 lpt ports
(d12) Found 1 serial ports
(d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes)
(d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(d12) PS2 keyboard initialized
(d12) All threads complete.
(d12) Scan for option roms
(d12) Running option rom at c980:0003
(d12) pmm call arg1=1
(d12) pmm call arg1=0
(d12) pmm call arg1=1
(d12) pmm call arg1=0
(d12) Searching bootorder for: /pci@i0cf8/*@4
(d12)
(d12) Press ESC for boot menu.
(d12)
(d12) Searching bootorder for: HALT
(d12) drive 0x000f5c20: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
s=167772160
(d12) Space available for UMB: ca800-eb000, f5680-f5bc0
(d12) Returned 258048 bytes of ZoneHigh
(d12) e820 map has 7 items:
(d12) 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(d12) 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(d12) 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(d12) 3: 0000000000100000 - 00000000effff000 = 1 RAM
(d12) 4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
(d12) 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(d12) 6: 0000000100000000 - 000000010f800000 = 1 RAM
(d12) enter handle_19:
(d12) NULL
(d12) Booting from Hard Disk...
(d12) Boot failed: not a bootable disk
(d12)
(d12) enter handle_18:
(d12) NULL
(d12) Booting from DVD/CD...
(d12) Booting from 0000:7c00

Em qui, 11 de jul de 2019 às 21:02, R0me0 *** <[hidden email]>
escreveu:

> Hello Roger,
>
> >So you are trying to boot systemrescuecd as a guest on the Xen host?
> Yes.
>
> Here is the config I have used:
>
> # cat livecd.cfg
>
> builder = "hvm"
> name = "livecd"
> memory = 2048
> cpus="all,^0-1"
> vcpus = 2
> vif = [ 'type=vif,bridge=sandbox' ]
> disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,
> '/home/iso/systemrescuecd-6.0.3.iso,raw,xvdb:cdrom,r' ]
> boot = 'd'
> vnc = 1
> vnclisten = '127.0.0.1'
> serial = 'pty'
>
> Regarding this:
>
> > Could you get a serial hooked up to that box so we can get the trace?
>
> Could you help me to provide the information you asked.
>
> Thank you .
>
> Kind regards,
>
>
>
>
> Em qui, 4 de jul de 2019 às 07:26, Roger Pau Monné <[hidden email]>
> escreveu:
>
>> On Fri, Jun 28, 2019 at 12:02:37PM +0000, R0me0 *** wrote:
>> > Guys,
>> >
>> > I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC
>> amd64
>>
>> I guess this is on the host?
>>
>> > When booting systemrescuecd-6.0.3.iso ( http://www.system-rescue-cd.org
>> )
>> > , my system just hangs and reboot.
>>
>> So you are trying to boot systemrescuecd as a guest on the Xen host?
>>
>> Can you paste your guest config file?
>>
>> > Just tried an older version and it's ok.
>> >
>> > I don't have any log to help. If you guys want and some help, I can
>> provide
>> > more information.
>>
>> Could you get a serial hooked up to that box so we can get the trace?
>>
>> Without some kind of trace it's going to be hard to debug this.
>>
>> Thanks, Roger.
>>
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Just boot Debian 10 e Machine freezes completely.

Seems to be related to Linux Kernel 4.X

Em ter, 23 de jul de 2019 às 11:51, R0me0 *** <[hidden email]>
escreveu:

> I tried to boot kali linux (
> https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as
> guest.
>
> The machine freezes on the same way I am using the latest xen 4.12 on
> freebsd
>
> here is the screenshot of console:
>
> [image: 2019-07-23-084718_853x193_scrot.png]
>
> and here is the xl dmesg
>
> (d12) Detected Xen v4.12.0
> (d12) xen: copy BIOS tables...
> (d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60
> (d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40
> (d12) Copying PIR from 0x00010040 to 0x000f5cc0
> (d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90
> (d12) Using pmtimer, ioport 0xb008
> (d12) Scan for VGA option rom
> (d12) Running option rom at c000:0003
> (d12) pmm call arg1=0
> (d12) Turning on vga text mode console
> (d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06)
> (d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8
> (d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
> (d12) ATA controller 2 at 170/374/0 (irq 15 dev 9)
> (d12) Found 0 lpt ports
> (d12) Found 1 serial ports
> (d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes)
> (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
> (d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
> (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
> (d12) PS2 keyboard initialized
> (d12) All threads complete.
> (d12) Scan for option roms
> (d12) Running option rom at c980:0003
> (d12) pmm call arg1=1
> (d12) pmm call arg1=0
> (d12) pmm call arg1=1
> (d12) pmm call arg1=0
> (d12) Searching bootorder for: /pci@i0cf8/*@4
> (d12)
> (d12) Press ESC for boot menu.
> (d12)
> (d12) Searching bootorder for: HALT
> (d12) drive 0x000f5c20: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> s=167772160
> (d12) Space available for UMB: ca800-eb000, f5680-f5bc0
> (d12) Returned 258048 bytes of ZoneHigh
> (d12) e820 map has 7 items:
> (d12) 0: 0000000000000000 - 000000000009fc00 = 1 RAM
> (d12) 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
> (d12) 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
> (d12) 3: 0000000000100000 - 00000000effff000 = 1 RAM
> (d12) 4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
> (d12) 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
> (d12) 6: 0000000100000000 - 000000010f800000 = 1 RAM
> (d12) enter handle_19:
> (d12) NULL
> (d12) Booting from Hard Disk...
> (d12) Boot failed: not a bootable disk
> (d12)
> (d12) enter handle_18:
> (d12) NULL
> (d12) Booting from DVD/CD...
> (d12) Booting from 0000:7c00
>
>
>
> Em qui, 11 de jul de 2019 às 21:02, R0me0 *** <[hidden email]>
> escreveu:
>
>> Hello Roger,
>>
>> >So you are trying to boot systemrescuecd as a guest on the Xen host?
>> Yes.
>>
>> Here is the config I have used:
>>
>> # cat livecd.cfg
>>
>> builder = "hvm"
>> name = "livecd"
>> memory = 2048
>> cpus="all,^0-1"
>> vcpus = 2
>> vif = [ 'type=vif,bridge=sandbox' ]
>> disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,
>> '/home/iso/systemrescuecd-6.0.3.iso,raw,xvdb:cdrom,r' ]
>> boot = 'd'
>> vnc = 1
>> vnclisten = '127.0.0.1'
>> serial = 'pty'
>>
>> Regarding this:
>>
>> > Could you get a serial hooked up to that box so we can get the trace?
>>
>> Could you help me to provide the information you asked.
>>
>> Thank you .
>>
>> Kind regards,
>>
>>
>>
>>
>> Em qui, 4 de jul de 2019 às 07:26, Roger Pau Monné <[hidden email]>
>> escreveu:
>>
>>> On Fri, Jun 28, 2019 at 12:02:37PM +0000, R0me0 *** wrote:
>>> > Guys,
>>> >
>>> > I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC
>>> amd64
>>>
>>> I guess this is on the host?
>>>
>>> > When booting systemrescuecd-6.0.3.iso (
>>> http://www.system-rescue-cd.org )
>>> > , my system just hangs and reboot.
>>>
>>> So you are trying to boot systemrescuecd as a guest on the Xen host?
>>>
>>> Can you paste your guest config file?
>>>
>>> > Just tried an older version and it's ok.
>>> >
>>> > I don't have any log to help. If you guys want and some help, I can
>>> provide
>>> > more information.
>>>
>>> Could you get a serial hooked up to that box so we can get the trace?
>>>
>>> Without some kind of trace it's going to be hard to debug this.
>>>
>>> Thanks, Roger.
>>>
>>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

Roger Pau Monné

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

In reply to this post by R0me0 ***

On Tue, Jul 23, 2019 at 11:51:51AM +0000, R0me0 *** wrote:
> I tried to boot kali linux (
> https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as guest.
>
> The machine freezes on the same way I am using the latest xen 4.12 on
> freebsd

I think I'm confused by this sentence. When you write the machine
freezes, I assume you mean that the guest freezes, but the host is
responsive?

> here is the screenshot of console:
>
> [image: 2019-07-23-084718_853x193_scrot.png]
>
> and here is the xl dmesg
>
> (d12) Detected Xen v4.12.0
> (d12) xen: copy BIOS tables...
> (d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60
> (d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40
> (d12) Copying PIR from 0x00010040 to 0x000f5cc0
> (d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90
> (d12) Using pmtimer, ioport 0xb008
> (d12) Scan for VGA option rom
> (d12) Running option rom at c000:0003
> (d12) pmm call arg1=0
> (d12) Turning on vga text mode console
> (d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06)
> (d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8
> (d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
> (d12) ATA controller 2 at 170/374/0 (irq 15 dev 9)
> (d12) Found 0 lpt ports
> (d12) Found 1 serial ports
> (d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes)
> (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
> (d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
> (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
> (d12) PS2 keyboard initialized
> (d12) All threads complete.
> (d12) Scan for option roms
> (d12) Running option rom at c980:0003
> (d12) pmm call arg1=1
> (d12) pmm call arg1=0
> (d12) pmm call arg1=1
> (d12) pmm call arg1=0
> (d12) Searching bootorder for: /pci@i0cf8/*@4
> (d12)
> (d12) Press ESC for boot menu.
> (d12)
> (d12) Searching bootorder for: HALT
> (d12) drive 0x000f5c20: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> s=167772160
> (d12) Space available for UMB: ca800-eb000, f5680-f5bc0
> (d12) Returned 258048 bytes of ZoneHigh
> (d12) e820 map has 7 items:
> (d12) 0: 0000000000000000 - 000000000009fc00 = 1 RAM
> (d12) 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
> (d12) 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
> (d12) 3: 0000000000100000 - 00000000effff000 = 1 RAM
> (d12) 4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
> (d12) 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
> (d12) 6: 0000000100000000 - 000000010f800000 = 1 RAM
> (d12) enter handle_19:
> (d12) NULL
> (d12) Booting from Hard Disk...
> (d12) Boot failed: not a bootable disk
> (d12)
> (d12) enter handle_18:
> (d12) NULL
> (d12) Booting from DVD/CD...
> (d12) Booting from 0000:7c00
>
>
>
> Em qui, 11 de jul de 2019 às 21:02, R0me0 *** <[hidden email]>
> escreveu:
>
> > Hello Roger,
> >
> > >So you are trying to boot systemrescuecd as a guest on the Xen host?
> > Yes.
> >
> > Here is the config I have used:
> >
> > # cat livecd.cfg
> >
> > builder = "hvm"
> > name = "livecd"
> > memory = 2048
> > cpus="all,^0-1"
> > vcpus = 2
> > vif = [ 'type=vif,bridge=sandbox' ]
> > disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,

Can you try with:

'format=raw, vdev=hda, access=rw, backendtype=qdisk, target=/dev/zvol/fbroot/SAND/disk'

Which version of FreeBSD are you running?

Can you also paste the output of `dmesg` when this happens?

Thanks, Roger.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Yes DOM0, the XEN hypervisor completely hangs and the host automatically
reboots.

It seems related with Linux guests using kernel 4.x

I'am using FreeBSD 12.0-RELEASE-p7 FreeBSD 12.0-RELEASE-p6 GENERIC amd64

# pkg info
argp-standalone-1.3_3 Standalone version of arguments parsing
functions from GLIBC
bareos17-client-17.2.7_3 Backup archiving recovery open sourced
(client)
ca_root_nss-3.45 Root certificate bundle from the Mozilla
Project
curl-7.65.2 Command line tool and library for
transferring data with URLs
doas-6.0p3 Simple sudo alternative to run commands as
another user
gettext-runtime-0.20.1 GNU gettext runtime libraries and programs
glib-2.56.3_5,1 Some useful routines of C programming
(current stable version)
indexinfo-0.3.1 Utility to regenerate the GNU info page index
jansson-2.12 C library for encoding, decoding, and
manipulating JSON data
libffi-3.2.1_3 Foreign Function Interface
libiconv-1.14_11 Character set conversion library
libnghttp2-1.39.1 HTTP/2.0 C Library
libxml2-2.9.9 XML parser library for GNOME
lzo2-2.10_1 Portable speedy, lossless data compression
library
mtr-nox11-0.92_1 Traceroute and ping in a single network
diagnostic tool
p5-Path-Tiny-0.108 File path utility
pcre-8.43_1 Perl Compatible Regular Expressions library
perl5-5.28.2 Practical Extraction and Report Language
pixman-0.38.4 Low-level pixel manipulation library
pkg-1.11.1 Package manager
python27-2.7.16_1 Interpreted object-oriented programming
language
python36-3.6.9 Interpreted object-oriented programming
language
qemu-utils-3.0.1_2 QEMU userland utilities
readline-8.0.0 Library for editing command lines as they
are typed
seabios-1.11.0_2 Open source implementation of a 16bit X86
BIOS
strongswan-5.8.0 Open Source IKEv2 IPsec-based VPN solution
vim-console-8.1.1439 Improved version of the vi editor (console
only)
xen-kernel-4.12.0_3 Hypervisor using a microkernel design
xen-tools-4.12.0_2 Xen management tools
yajl-2.1.0 Portable JSON parsing and serialization
library in ANSI C

Em ter, 23 de jul de 2019 às 13:13, Roger Pau Monné <[hidden email]>
escreveu:

> On Tue, Jul 23, 2019 at 11:51:51AM +0000, R0me0 *** wrote:
> > I tried to boot kali linux (
> > https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as
> guest.
> >
> > The machine freezes on the same way I am using the latest xen 4.12 on
> > freebsd
>
> I think I'm confused by this sentence. When you write the machine
> freezes, I assume you mean that the guest freezes, but the host is
> responsive?
>
> > here is the screenshot of console:
> >
> > [image: 2019-07-23-084718_853x193_scrot.png]
> >
> > and here is the xl dmesg
> >
> > (d12) Detected Xen v4.12.0
> > (d12) xen: copy BIOS tables...
> > (d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60
> > (d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40
> > (d12) Copying PIR from 0x00010040 to 0x000f5cc0
> > (d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90
> > (d12) Using pmtimer, ioport 0xb008
> > (d12) Scan for VGA option rom
> > (d12) Running option rom at c000:0003
> > (d12) pmm call arg1=0
> > (d12) Turning on vga text mode console
> > (d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06)
> > (d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8
> > (d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
> > (d12) ATA controller 2 at 170/374/0 (irq 15 dev 9)
> > (d12) Found 0 lpt ports
> > (d12) Found 1 serial ports
> > (d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes)
> > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
> > (d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
> > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
> > (d12) PS2 keyboard initialized
> > (d12) All threads complete.
> > (d12) Scan for option roms
> > (d12) Running option rom at c980:0003
> > (d12) pmm call arg1=1
> > (d12) pmm call arg1=0
> > (d12) pmm call arg1=1
> > (d12) pmm call arg1=0
> > (d12) Searching bootorder for: /pci@i0cf8/*@4
> > (d12)
> > (d12) Press ESC for boot menu.
> > (d12)
> > (d12) Searching bootorder for: HALT
> > (d12) drive 0x000f5c20: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> > s=167772160
> > (d12) Space available for UMB: ca800-eb000, f5680-f5bc0
> > (d12) Returned 258048 bytes of ZoneHigh
> > (d12) e820 map has 7 items:
> > (d12) 0: 0000000000000000 - 000000000009fc00 = 1 RAM
> > (d12) 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
> > (d12) 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
> > (d12) 3: 0000000000100000 - 00000000effff000 = 1 RAM
> > (d12) 4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
> > (d12) 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
> > (d12) 6: 0000000100000000 - 000000010f800000 = 1 RAM
> > (d12) enter handle_19:
> > (d12) NULL
> > (d12) Booting from Hard Disk...
> > (d12) Boot failed: not a bootable disk
> > (d12)
> > (d12) enter handle_18:
> > (d12) NULL
> > (d12) Booting from DVD/CD...
> > (d12) Booting from 0000:7c00
> >
> >
> >
> > Em qui, 11 de jul de 2019 às 21:02, R0me0 *** <[hidden email]>
> > escreveu:
> >
> > > Hello Roger,
> > >
> > > >So you are trying to boot systemrescuecd as a guest on the Xen host?
> > > Yes.
> > >
> > > Here is the config I have used:
> > >
> > > # cat livecd.cfg
> > >
> > > builder = "hvm"
> > > name = "livecd"
> > > memory = 2048
> > > cpus="all,^0-1"
> > > vcpus = 2
> > > vif = [ 'type=vif,bridge=sandbox' ]
> > > disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,
>
> Can you try with:
>
> 'format=raw, vdev=hda, access=rw, backendtype=qdisk,
> target=/dev/zvol/fbroot/SAND/disk'
>
> Which version of FreeBSD are you running?
>
> Can you also paste the output of `dmesg` when this happens?
>
> Thanks, Roger.
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

In reply to this post by Roger Pau Monné

Yes the DOM0, the XEN hypervisor completely hangs and the host
automatically reboots.

It seems related with Linux guests using kernel 4.x

I'am using FreeBSD 12.0-RELEASE-p7 FreeBSD 12.0-RELEASE-p6 GENERIC amd64

# pkg info | cut -f1 -d' '
argp-standalone-1.3_3
bareos17-client-17.2.7_3
ca_root_nss-3.45
curl-7.65.2
doas-6.0p3
gettext-runtime-0.20.1
glib-2.56.3_5,1
indexinfo-0.3.1
jansson-2.12
libffi-3.2.1_3
libiconv-1.14_11
libnghttp2-1.39.1
libxml2-2.9.9
lzo2-2.10_1
mtr-nox11-0.92_1
p5-Path-Tiny-0.108
pcre-8.43_1
perl5-5.28.2
pixman-0.38.4
pkg-1.11.1
python27-2.7.16_1
python36-3.6.9
qemu-utils-3.0.1_2
readline-8.0.0
seabios-1.11.0_2
strongswan-5.8.0
vim-console-8.1.1439
xen-kernel-4.12.0_3
xen-tools-4.12.0_2
yajl-2.1.0

Em ter, 23 de jul de 2019 às 13:13, Roger Pau Monné <[hidden email]>
escreveu:

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

>Can you try with:

> 'format=raw, vdev=hda, access=rw, backendtype=qdisk,
target=/dev/zvol/fbroot/SAND/disk'

I need to test on another time, because I have some services running on
this box and this bug bring me some headache on my job

Thank you for your patience and attention,

Kind regards,

Em ter, 23 de jul de 2019 às 15:45, R0me0 *** <[hidden email]>
escreveu:

> Yes the DOM0, the XEN hypervisor completely hangs and the host
> automatically reboots.
>
> It seems related with Linux guests using kernel 4.x
>
> I'am using FreeBSD 12.0-RELEASE-p7 FreeBSD 12.0-RELEASE-p6 GENERIC amd64
>
> # pkg info | cut -f1 -d' '
> argp-standalone-1.3_3
> bareos17-client-17.2.7_3
> ca_root_nss-3.45
> curl-7.65.2
> doas-6.0p3
> gettext-runtime-0.20.1
> glib-2.56.3_5,1
> indexinfo-0.3.1
> jansson-2.12
> libffi-3.2.1_3
> libiconv-1.14_11
> libnghttp2-1.39.1
> libxml2-2.9.9
> lzo2-2.10_1
> mtr-nox11-0.92_1
> p5-Path-Tiny-0.108
> pcre-8.43_1
> perl5-5.28.2
> pixman-0.38.4
> pkg-1.11.1
> python27-2.7.16_1
> python36-3.6.9
> qemu-utils-3.0.1_2
> readline-8.0.0
> seabios-1.11.0_2
> strongswan-5.8.0
> vim-console-8.1.1439
> xen-kernel-4.12.0_3
> xen-tools-4.12.0_2
> yajl-2.1.0
>
> Em ter, 23 de jul de 2019 às 13:13, Roger Pau Monné <[hidden email]>
> escreveu:
>
>> On Tue, Jul 23, 2019 at 11:51:51AM +0000, R0me0 *** wrote:
>> > I tried to boot kali linux (
>> > https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as
>> guest.
>> >
>> > The machine freezes on the same way I am using the latest xen 4.12 on
>> > freebsd
>>
>> I think I'm confused by this sentence. When you write the machine
>> freezes, I assume you mean that the guest freezes, but the host is
>> responsive?
>>
>> > here is the screenshot of console:
>> >
>> > [image: 2019-07-23-084718_853x193_scrot.png]
>> >
>> > and here is the xl dmesg
>> >
>> > (d12) Detected Xen v4.12.0
>> > (d12) xen: copy BIOS tables...
>> > (d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60
>> > (d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40
>> > (d12) Copying PIR from 0x00010040 to 0x000f5cc0
>> > (d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90
>> > (d12) Using pmtimer, ioport 0xb008
>> > (d12) Scan for VGA option rom
>> > (d12) Running option rom at c000:0003
>> > (d12) pmm call arg1=0
>> > (d12) Turning on vga text mode console
>> > (d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06)
>> > (d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8
>> > (d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
>> > (d12) ATA controller 2 at 170/374/0 (irq 15 dev 9)
>> > (d12) Found 0 lpt ports
>> > (d12) Found 1 serial ports
>> > (d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes)
>> > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
>> > (d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
>> > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
>> > (d12) PS2 keyboard initialized
>> > (d12) All threads complete.
>> > (d12) Scan for option roms
>> > (d12) Running option rom at c980:0003
>> > (d12) pmm call arg1=1
>> > (d12) pmm call arg1=0
>> > (d12) pmm call arg1=1
>> > (d12) pmm call arg1=0
>> > (d12) Searching bootorder for: /pci@i0cf8/*@4
>> > (d12)
>> > (d12) Press ESC for boot menu.
>> > (d12)
>> > (d12) Searching bootorder for: HALT
>> > (d12) drive 0x000f5c20: PCHS=16383/16/63 translation=lba
>> LCHS=1024/255/63
>> > s=167772160
>> > (d12) Space available for UMB: ca800-eb000, f5680-f5bc0
>> > (d12) Returned 258048 bytes of ZoneHigh
>> > (d12) e820 map has 7 items:
>> > (d12) 0: 0000000000000000 - 000000000009fc00 = 1 RAM
>> > (d12) 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
>> > (d12) 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
>> > (d12) 3: 0000000000100000 - 00000000effff000 = 1 RAM
>> > (d12) 4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
>> > (d12) 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
>> > (d12) 6: 0000000100000000 - 000000010f800000 = 1 RAM
>> > (d12) enter handle_19:
>> > (d12) NULL
>> > (d12) Booting from Hard Disk...
>> > (d12) Boot failed: not a bootable disk
>> > (d12)
>> > (d12) enter handle_18:
>> > (d12) NULL
>> > (d12) Booting from DVD/CD...
>> > (d12) Booting from 0000:7c00
>> >
>> >
>> >
>> > Em qui, 11 de jul de 2019 às 21:02, R0me0 *** <[hidden email]>
>> > escreveu:
>> >
>> > > Hello Roger,
>> > >
>> > > >So you are trying to boot systemrescuecd as a guest on the Xen host?
>> > > Yes.
>> > >
>> > > Here is the config I have used:
>> > >
>> > > # cat livecd.cfg
>> > >
>> > > builder = "hvm"
>> > > name = "livecd"
>> > > memory = 2048
>> > > cpus="all,^0-1"
>> > > vcpus = 2
>> > > vif = [ 'type=vif,bridge=sandbox' ]
>> > > disk = [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' ,
>>
>> Can you try with:
>>
>> 'format=raw, vdev=hda, access=rw, backendtype=qdisk,
>> target=/dev/zvol/fbroot/SAND/disk'
>>
>> Which version of FreeBSD are you running?
>>
>> Can you also paste the output of `dmesg` when this happens?
>>
>> Thanks, Roger.
>>
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

Roger Pau Monné

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

In reply to this post by R0me0 ***

On Tue, Jul 23, 2019 at 03:45:49PM +0000, R0me0 *** wrote:
> Yes the DOM0, the XEN hypervisor completely hangs and the host
> automatically reboots.

You will have to setup a serial console in order to debug then. You
need to find the serial port of your box and hook a null modem [0] to it,
and then plug the other side into another computer and use cu, minicom
or some other program in order to get the serial output.

There's a section on the handbook about how to use the serial console:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html

You will need to add something like:

console=com1,vga com1=115200,8n1

to your xen_cmdline if you don't have it yet in order to get the
output.

> It seems related with Linux guests using kernel 4.x

Does then same happen if you use a disk line like:

'format=raw, vdev=hda, access=rw, backendtype=qdisk, target=/dev/zvol/fbroot/SAND/disk'

Note the 'backendtype' option is set to qdisk.

Roger.

[0] https://en.wikipedia.org/wiki/Null_modem
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Sorry, but this host is hosted on another country which I do not have
access to. ( Hetzner )

So, I think I can't help.

Em ter, 23 de jul de 2019 às 15:54, Roger Pau Monné <[hidden email]>
escreveu:

> On Tue, Jul 23, 2019 at 03:45:49PM +0000, R0me0 *** wrote:
> > Yes the DOM0, the XEN hypervisor completely hangs and the host
> > automatically reboots.
>
> You will have to setup a serial console in order to debug then. You
> need to find the serial port of your box and hook a null modem [0] to it,
> and then plug the other side into another computer and use cu, minicom
> or some other program in order to get the serial output.
>
> There's a section on the handbook about how to use the serial console:
>
>
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
>
> You will need to add something like:
>
> console=com1,vga com1=115200,8n1
>
> to your xen_cmdline if you don't have it yet in order to get the
> output.
>
> > It seems related with Linux guests using kernel 4.x
>
> Does then same happen if you use a disk line like:
>
> 'format=raw, vdev=hda, access=rw, backendtype=qdisk,
> target=/dev/zvol/fbroot/SAND/disk'
>
> Note the 'backendtype' option is set to qdisk.
>
> Roger.
>
> [0] https://en.wikipedia.org/wiki/Null_modem
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

Roger Pau Monné

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Hello,

Could you please try to avoid top-posting.

On Tue, Jul 23, 2019 at 04:07:31PM +0000, R0me0 *** wrote:
> Sorry, but this host is hosted on another country which I do not have
> access to. ( Hetzner )
>
> So, I think I can't help.

Can you ask them to provide a serial console for you?

This is quite common practice for servers, since it's the most
reliable way to get backtraces and debug info when something goes
wrong. I'm sure your hosting provider should be able to help you.

Roger.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

I will ask. Count on me

Em ter, 23 de jul de 2019 às 16:12, Roger Pau Monné <[hidden email]>
escreveu:

> Hello,
>
> Could you please try to avoid top-posting.
>
> On Tue, Jul 23, 2019 at 04:07:31PM +0000, R0me0 *** wrote:
> > Sorry, but this host is hosted on another country which I do not have
> > access to. ( Hetzner )
> >
> > So, I think I can't help.
>
> Can you ask them to provide a serial console for you?
>
> This is quite common practice for servers, since it's the most
> reliable way to get backtraces and debug info when something goes
> wrong. I'm sure your hosting provider should be able to help you.
>
> Roger.
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Roger, I got a machine, I will perform a fresh install and try to
reproduce the bug. If possible I will send you

One more time, thank you very much

Kind regards,

Em ter, 23 de jul de 2019 às 16:13, R0me0 *** <[hidden email]>
escreveu:

> I will ask. Count on me
>
> Em ter, 23 de jul de 2019 às 16:12, Roger Pau Monné <[hidden email]>
> escreveu:
>
>> Hello,
>>
>> Could you please try to avoid top-posting.
>>
>> On Tue, Jul 23, 2019 at 04:07:31PM +0000, R0me0 *** wrote:
>> > Sorry, but this host is hosted on another country which I do not have
>> > access to. ( Hetzner )
>> >
>> > So, I think I can't help.
>>
>> Can you ask them to provide a serial console for you?
>>
>> This is quite common practice for servers, since it's the most
>> reliable way to get backtraces and debug info when something goes
>> wrong. I'm sure your hosting provider should be able to help you.
>>
>> Roger.
>>
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

Roger Pau Monné

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

On Wed, Jul 24, 2019 at 06:49:28PM +0000, R0me0 *** wrote:
> Roger, I got a machine, I will perform a fresh install and try to
> reproduce the bug. If possible I will send you

I've just committed a fix to xen-kernel yesterday which I think could
solve your issue. Can you update to xen-kernel 4.12.0_4?

Note you will likely need to build this from the ports tree, since
it's quite likely pkg hasn't got a binary package for this yet.

Roger.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Hello Roger,

Thank you very much, I will update it and reboot the server in a couple of
hours.

Thank you !

Em ter, 30 de jul de 2019 às 17:25, Roger Pau Monné <[hidden email]>
escreveu:

> On Wed, Jul 24, 2019 at 06:49:28PM +0000, R0me0 *** wrote:
> > Roger, I got a machine, I will perform a fresh install and try to
> > reproduce the bug. If possible I will send you
>
> I've just committed a fix to xen-kernel yesterday which I think could
> solve your issue. Can you update to xen-kernel 4.12.0_4?
>
> Note you will likely need to build this from the ports tree, since
> it's quite likely pkg hasn't got a binary package for this yet.
>
> Roger.
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"

R0me0 ***

Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots

Hello Roger,

First of all thank you very much. xen-kernel 4.12.0_4 had the issue fixed,
At least I was able to boot for example a debian 10 without any issue.

I am going to deploy some machines. You r0x as always :)

One more time. Thank you for everything.

Kind regards,

Em ter, 30 de jul de 2019 às 19:12, R0me0 *** <[hidden email]>
escreveu:

> Hello Roger,
>
> Thank you very much, I will update it and reboot the server in a couple of
> hours.
>
>
> Thank you !
>
> Em ter, 30 de jul de 2019 às 17:25, Roger Pau Monné <[hidden email]>
> escreveu:
>
>> On Wed, Jul 24, 2019 at 06:49:28PM +0000, R0me0 *** wrote:
>> > Roger, I got a machine, I will perform a fresh install and try to
>> > reproduce the bug. If possible I will send you
>>
>> I've just committed a fix to xen-kernel yesterday which I think could
>> solve your issue. Can you update to xen-kernel 4.12.0_4?
>>
>> Note you will likely need to build this from the ports tree, since
>> it's quite likely pkg hasn't got a binary package for this yet.
>>
>> Roger.
>>
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"