El 06/11/15 a les 16.22, Thomas Laus ha escrit:
>> xl debug messages go to stderr, not stdout, so you have to use "2>"
>> instead of ">" in order to do the redirection. Setting up a ssh server
>> on the Dom0 and using it remotely will also help ;).
>>
> Still nothing was sent to a file for 2>.  Here is my xl dmesg:

Then you will have to check how to redirect stderr to a file with the
shell you are using. It works fine for me when using bash.

# xl -vvv create freebsd_nodm.cfg 2> test.out
# cat test.out
Parsing config from freebsd_nodm.cfg
libxl: debug: libxl_create.c:1575:do_domain_create: ao 0x1c7a8e0:
create: how=(nil) callback=(nil) poller=0x1c6fb20
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
vdev=hda, using backend phy
[...]

> (XEN) ERROR: 16550-compatible serial UART not present
>  Xen 4.5.1
> (XEN) Xen version 4.5.1 (root@) (gcc48 (FreeBSD Ports Collection) 4.8.5) 
> debug=n Sat Oct 24 18:29:18 UTC 2015
> (XEN) Latest ChangeSet: 
> (XEN) Bootloader: FreeBSD Loader
> (XEN) Command line: dom0_mem=2048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 
> guest_loglvl=all loglvl=all
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009d000 (usable)
> (XEN)  000000000009d000 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000006a39b000 (usable)
> (XEN)  000000006a39b000 - 000000007cd2f000 (reserved)
> (XEN)  000000007cd2f000 - 000000007ce7f000 (ACPI NVS)
> (XEN)  000000007ce7f000 - 000000007ceff000 (ACPI data)
> (XEN)  000000007ceff000 - 000000007fa00000 (reserved)
> (XEN)  00000000b8000000 - 00000000fc000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
> (XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 000000027e600000 (usable)
> (XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO)
> (XEN) ACPI: XSDT 7CEFE170, 00EC (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: FACP 7CEF8000, 010C (r5 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: DSDT 7CEE0000, 120D4 (r1 LENOVO TP-GN        2100 INTL 20120711)
> (XEN) ACPI: FACS 7CE42000, 0040
> (XEN) ACPI: SLIC 7CEFD000, 0176 (r1 LENOVO TP-GN        2100 PTEC        1)
> (XEN) ACPI: DBGP 7CEFB000, 0034 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: ECDT 7CEFA000, 0052 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: HPET 7CEF7000, 0038 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: APIC 7CEF6000, 0098 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: MCFG 7CEF5000, 003C (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: SSDT 7CEF4000, 0033 (r1 LENOVO TP-SSDT1      100 INTL 20120711)
> (XEN) ACPI: SSDT 7CEF3000, 044F (r1 LENOVO TP-SSDT2      200 INTL 20120711)
> (XEN) ACPI: SSDT 7CEDF000, 0B78 (r1 LENOVO SataAhci     1000 INTL 20120711)
> (XEN) ACPI: SSDT 7CEDE000, 07E7 (r1 LENOVO  Cpu0Ist     3000 INTL 20120711)
> (XEN) ACPI: SSDT 7CEDD000, 0AD8 (r1 LENOVO    CpuPm     3000 INTL 20120711)
> (XEN) ACPI: SSDT 7CEDB000, 1215 (r1 LENOVO  SaSsdt      3000 INTL 20120711)
> (XEN) ACPI: SSDT 7CEDA000, 0379 (r1 LENOVO CppcTabl     1000 INTL 20120711)
> (XEN) ACPI: PCCT 7CED9000, 006E (r5 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: SSDT 7CED8000, 0AC4 (r1 LENOVO Cpc_Tabl     1000 INTL 20120711)
> (XEN) ACPI: TCPA 7CED7000, 0032 (r2    PTL   LENOVO  6040000 LNVO        1)
> (XEN) ACPI: UEFI 7CED6000, 0042 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: MSDM 7CDAA000, 0055 (r3 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: ASF! 7CEFC000, 00A5 (r32 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: BATB 7CED5000, 0046 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: FPDT 7CED4000, 0064 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: UEFI 7CED3000, 02E2 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) ACPI: SSDT 7CED2000, 047F (r1 LENOVO IsctTabl     1000 INTL 20120711)
> (XEN) ACPI: DMAR 7CED1000, 00B8 (r1 LENOVO TP-GN        2100 PTEC        2)
> (XEN) System RAM: 7817MB (8004832kB)
> (XEN) No NUMA configuration found
> (XEN) Faking a node at 0000000000000000-000000027e600000
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000f0100
> (XEN) DMI 2.7 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0x1808
> (XEN) ACPI: v5 SLEEP INFO: control[1:0], status[1:0]
> (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0]
> (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7ce42000/0000000000000000, 
> using 32
> (XEN) ACPI:             wakeup_vec[7ce4200c], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
> (XEN) Processor #2 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
> (XEN) Processor #3 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
> (XEN) Processor #4 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
> (XEN) Processor #5 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
> (XEN) Processor #6 7:12 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
> (XEN) Processor #7 7:12 APIC version 21
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
> (XEN) ERST table was not found
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs)
> (XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
> (XEN) Switched to APIC driver x2apic_cluster.
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2693.807 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
> (XEN) mce_intel.c:719: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 
> extended MCE MSR 0
> (XEN) Intel machine check reporting enabled
> (XEN) alt table ffff82d0802b6cf0 -> ffff82d0802b7e60
> (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
> (XEN) PCI: MCFG area at f8000000 reserved in E820
> (XEN) PCI: Using MCFG for segment 0000 bus 00-3f
> (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
> (XEN) Intel VT-d iommu 1 supported page sizes: 4kB.
> (XEN) Intel VT-d Snoop Control not enabled.
> (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
> (XEN) Intel VT-d Queued Invalidation enabled.
> (XEN) Intel VT-d Interrupt Remapping enabled.
> (XEN) Intel VT-d Shared EPT tables not enabled.
> (XEN) I/O virtualisation enabled
> (XEN)  - Dom0 mode: Relaxed
> (XEN) Interrupt remapping enabled
> (XEN) Enabled directed EOI with ioapic_ack_old on!
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using old ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) TSC deadline timer enabled
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Allocated console ring of 64 KiB.
> (XEN) mwait-idle: MWAIT substates: 0x42120
> (XEN) mwait-idle: v0.4 model 0x3c
> (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN)  - Unrestricted Guest
> (XEN)  - VMCS shadowing
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging (HAP) detected
> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
> (XEN) Brought up 8 CPUs
> (XEN) ACPI sleep modes: S3
> (XEN) mcheck_poll: Machine check polling timer started.
> (XEN) Dom0 has maximum 792 PIRQs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x200000 -> 0x1da6878
> (XEN)  Dom0 symbol map 0x1da6878 -> 0x20d6830
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000270000000->0000000274000000 (507901 pages to be 
> allocated)
> (XEN)  Init. ramdisk: 000000027e5fd000->000000027e600000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80200000->ffffffff820d6830
> (XEN)  Init. ramdisk: ffffffff820d7000->ffffffff820da000
> (XEN)  Phys-Mach map: ffffffff820da000->ffffffff824da000
> (XEN)  Start info:    ffffffff824da000->ffffffff824db4b4
> (XEN)  Page tables:   ffffffff824dc000->ffffffff824f3000
> (XEN)  Boot stack:    ffffffff824f3000->ffffffff824f4000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff82800000
> (XEN)  ENTRY ADDRESS: ffffffff80f09000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Masked UR signaling on 0000:00:00.0
> (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:1d.0] fault addr 
> 7af37000, iommu reg = ffff82c000203000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) ....................done.
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
> Xen)
> (XEN) Freed 304kB init memory.
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:14.0] fault addr 
> 7aec4000, iommu reg = ffff82c000203000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) irq.c:380: Dom0 callback via changed to Direct Vector 0x93
> (XEN) Masked UR signaling on 0000:00:00.0
> (XEN) PCI add device 0000:00:00.0
> (XEN) PCI add device 0000:00:01.0
> (XEN) PCI add device 0000:00:02.0
> (XEN) PCI add device 0000:00:03.0
> (XEN) PCI add device 0000:00:14.0
> (XEN) PCI add device 0000:00:16.0
> (XEN) PCI add device 0000:00:16.3
> (XEN) PCI add device 0000:00:19.0
> (XEN) PCI add device 0000:00:1a.0
> (XEN) PCI add device 0000:00:1b.0
> (XEN) PCI add device 0000:00:1c.0
> (XEN) PCI add device 0000:00:1c.1
> (XEN) PCI add device 0000:00:1c.2
> (XEN) PCI add device 0000:00:1c.4
> (XEN) PCI add device 0000:00:1d.0
> (XEN) PCI add device 0000:00:1f.0
> (XEN) PCI add device 0000:00:1f.2
> (XEN) PCI add device 0000:00:1f.3
> (XEN) PCI add device 0000:01:00.0
> (XEN) PCI add device 0000:02:00.0
> (XEN) PCI add device 0000:03:00.0
> (d1) HVM Loader
> (d1) Detected Xen v4.5.1
> (d1) Xenbus rings @0xfeffc000, event channel 1
> (d1) System requested SeaBIOS
> (d1) CPU speed is 2694 MHz
> (d1) Relocating guest memory for lowmem MMIO space disabled

That's weird, you should generally see more output here, this is what I
typically see:

(d451) HVM Loader
(d451) Detected Xen v4.7-unstable
(d451) Xenbus rings @0xfeffc000, event channel 1
(d451) System requested SeaBIOS
(d451) CPU speed is 2095 MHz
(d451) Relocating guest memory for lowmem MMIO space disabled
(XEN) irq.c:275: Dom451 PCI link 0 changed 0 -> 5
(d451) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:275: Dom451 PCI link 1 changed 0 -> 10
(d451) PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:275: Dom451 PCI link 2 changed 0 -> 11
(d451) PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:275: Dom451 PCI link 3 changed 0 -> 5
(d451) PCI-ISA link 3 routed to IRQ5
(d451) pci dev 01:3 INTA->IRQ10
(d451) pci dev 02:0 INTA->IRQ11
(d451) pci dev 04:0 INTA->IRQ5
(d451) RAM in high memory; setting high_mem resource base to 186800000
(d451) pci dev 03:0 bar 10 size 002000000: 0f0000008
(d451) pci dev 02:0 bar 14 size 001000000: 0f2000008
(d451) pci dev 04:0 bar 30 size 000040000: 0f3000000
(d451) pci dev 03:0 bar 30 size 000010000: 0f3040000
(d451) pci dev 03:0 bar 14 size 000001000: 0f3050000
(d451) pci dev 02:0 bar 10 size 000000100: 00000c001
(d451) pci dev 04:0 bar 10 size 000000100: 00000c101
(d451) pci dev 04:0 bar 14 size 000000100: 0f3051000
(d451) pci dev 01:1 bar 20 size 000000010: 00000c201
[...]

> I see the error about the UART here is the section of my device probes during 
> the boot:

Yes, if you want to get rid of that just change the Xen command line to:

"dom0_mem=2048M dom0_max_vcpus=4 dom0pvh=1 guest_loglvl=all loglvl=all"

> Nov  6 09:12:40 xenserver kernel: Copyright (c) 1992-2015 The FreeBSD 
> Project.
> Nov  6 09:12:40 xenserver kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 
> 1989, 1991, 1992, 1993, 1994
> Nov  6 09:12:40 xenserver kernel: The Regents of the University of 
> California. All rights reserved.
> Nov  6 09:12:40 xenserver kernel: FreeBSD is a registered trademark of The 
> FreeBSD Foundation.
> Nov  6 09:12:40 xenserver kernel: FreeBSD 11.0-CURRENT #0: Wed Nov  4 
> 14:39:53 EST 2015
> Nov  6 09:12:40 xenserver kernel: 
> root@xenserver:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64
> Nov  6 09:12:40 xenserver kernel: FreeBSD clang version 3.7.0 
> (tags/RELEASE_370/final 246257) 20150906
> Nov  6 09:12:40 xenserver kernel: VT(vga): resolution 640x480
> Nov  6 09:12:40 xenserver kernel: CPU: Intel(R) Core(TM) i7-4800MQ CPU @ 
> 2.70GHz (2693.76-MHz K8-class CPU)
> Nov  6 09:12:40 xenserver kernel: Origin="GenuineIntel"  Id=0x306c3  
> Family=0x6  Model=0x3c  Stepping=3
> Nov  6 09:12:40 xenserver kernel: 
> Features=0x1fc3ebff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,PGE,MCA,CMOV,P
> AT,PSE36,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT>
> Nov  6 09:12:40 xenserver kernel: 
> Features2=0xfff83a83<SSE3,PCLMULQDQ,EST,SSSE3,SDBG,FMA,CX16,SSE4.1,SSE4.2,x2AP
> IC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV>
> Nov  6 09:12:40 xenserver kernel: AMD Features=0x20100800<SYSCALL,NX,LM>
> Nov  6 09:12:40 xenserver kernel: AMD Features2=0x21<LAHF,ABM>
> Nov  6 09:12:40 xenserver kernel: Structured Extended 
> Features=0xb38<BMI1,HLE,AVX2,BMI2,ERMS,RTM>
> Nov  6 09:12:40 xenserver kernel: XSAVE Features=0x1<XSAVEOPT>
> Nov  6 09:12:40 xenserver kernel: TSC: P-state invariant, performance 
> statistics
> Nov  6 09:12:40 xenserver kernel: Hypervisor: Origin = "XenVMMXenVMM"
> Nov  6 09:12:40 xenserver kernel: real memory  = 4660690944 (4444 MB)
> Nov  6 09:12:40 xenserver kernel: avail memory = 1970360320 (1879 MB)
> Nov  6 09:12:40 xenserver kernel: FreeBSD/SMP: Multiprocessor System 
> Detected: 4 CPUs
> Nov  6 09:12:40 xenserver kernel: FreeBSD/SMP: 1 package(s) x 4 core(s)
> Nov  6 09:12:40 xenserver kernel: cpu0 (BSP): APIC ID:  0
> Nov  6 09:12:40 xenserver kernel: cpu1 (AP): APIC ID:  2
> Nov  6 09:12:40 xenserver kernel: cpu2 (AP): APIC ID:  4
> Nov  6 09:12:40 xenserver kernel: cpu3 (AP): APIC ID:  6
> Nov  6 09:12:40 xenserver kernel: uart2: <Intel Lynx Point KT Controller> 
> port 0x50b0-0x50b7 mem 0xb2a40000-0xb2a40fff irq 17 at device 22.3 on pci0
> 
>> Can you also paste the output of `xl dmesg` after trying to launch the
>> guest?
>>
> My FreeBSD guest file:
> 
> builder = "hvm"
> memory = 512
> vcpus = 1
> name = "FreeBSD"
> disk = [
>       '/root/xen/freebsd.img,raw,hda,rw',
>       '/root/bhyve/freebsd11.iso,raw,hdc:cdrom,r'
>       ]
> #boot = "c" #boot to hard drive image
> boot = "d" #boot to ISO image
> vnc = 1
> vnclisten = "0.0.0.0"

Config file looks fine (you don't have any nic added, but I guess that's
on purpose).

>> Which revision of FreeBSD are you running in the Dom0?
>>
> FreeBSD current that was built yesterday from source.

Can you make sure you are using a version of FreeBSD equal or greater
than r290392? This is a fix for a bug that could cause guests to stop
booting.

> I am a contract programmer working on an off-shore natural gas platform 
> project.  I have 5 computers running at home in my office and was thinking 
> about making all of them guests on a single hypervisor as a winter project.  
> I brought along a small ITX sized PC for to help me get acquaited with 
> hypervisors.  It's CPU is missing Intel VT-d instructions, so I went to the 
> local Best Buy store and bought a SSD upgrade kit for this company laptop.  
> The laptop has VT-d features and is an i7.  It is running on a spare 
> partition but I will need to go back to the original hard drive soon because 
> the Windows OS is complaining about needing re-activation.  I just work on my 
> hypervisor upgrade in my hotel room in the evenings and on the days that the 
> helicopter doesn't fly because of weather.  There isn't any way to grant 
> remote SSH access until I get back home in January.

FWIW, I also tent to do development on a small box when possible (I
don't like to waste power). What I use is a NUC5i3MYHE which has room
for a serial bracket (that's the only suitable small x86 box I've found
that comes with a serial bracket option). With 8GB of memory and a hard
drive it's price should be around 400-450€.

Roger.
_______________________________________________
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to