Re: Does a Xen Dom0 require X to function - WORKS NOW
> # 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 > [...] > Paul: I made a temporary change to the FreeBSD default 'csh' shell for the root account and captured the 'xl create' file: Parsing config from freebsd.cfg libxl: debug: libxl_create.c:1504:do_domain_create: ao 0x802849060: create: how=0x0 callback=0x0 poller=0x802824060 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 libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=unknown libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=hdc, using backend phy libxl: debug: libxl_create.c:907:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:323:libxl__bootloader_run: not a PV domain, skipping bootloader libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x802858770: deregister unregistered xc: detail: elf_parse_binary: phdr: paddr=0x10 memsz=0x59b0c xc: detail: elf_parse_binary: memory: 0x10 -> 0x159b0c xc: detail: VIRTUAL MEMORY ARRANGEMENT: xc: detail: Loader: 0010->00159b0c xc: detail: Modules: -> xc: detail: TOTAL:->1f80 xc: detail: ENTRY:0010 xc: detail: PHYSICAL MEMORY ALLOCATION: xc: detail: 4KB PAGES: 0x0200 xc: detail: 2MB PAGES: 0x00fb xc: detail: 1GB PAGES: 0x xc: detail: elf_load_binary: phdr 0 at 0x80067a000 -> 0x8006caab1 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=phy libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x802b9e208 wpath=/local/domain/0/backend/vbd/2/768/state token=3/0: register slotnum=3 libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=phy libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=phy libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x802b9e3c8 wpath=/local/domain/0/backend/vbd/2/5632/state token=2/1: register slotnum=2 libxl: debug: libxl_create.c:1520:do_domain_create: ao 0x802849060: inprogress: poller=0x802824060, flags=i libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802b9e208 wpath=/local/domain/0/backend/vbd/2/768/state token=3/0: event epath=/local/domain/0/backend/vbd/2/768/state libxl: debug: libxl_event.c:830:devstate_watch_callback: backend /local/domain/0/backend/vbd/2/768/state wanted state 2 ok libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x802b9e208 wpath=/local/domain/0/backend/vbd/2/768/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x802b9e208: deregister unregistered libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x802b9e290: deregister unregistered libxl: debug: libxl_event.c:483:watchfd_callback: watch epath=/local/domain/0/backend/vbd/2/768/state token=3/0: empty slot libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802b9e3c8 wpath=/local/domain/0/backend/vbd/2/5632/state token=2/1: event epath=/local/domain/0/backend/vbd/2/5632/state libxl: debug: libxl_event.c:834:devstate_watch_callback: backend /local/domain/0/backend/vbd/2/5632/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802b9e3c8 wpath=/local/domain/0/backend/vbd/2/5632/state token=2/1: event epath=/local/domain/0/backend/vbd/2/5632/state libxl: debug: libxl_event.c:830:devstate_watch_callback: backend /local/domain/0/backend/vbd/2/5632/state wanted state 2 ok libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x802b9e3c8 wpath=/local/domain/0/backend/vbd/2/5632/state token=2/1: deregister slotnum=2 libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x802b9e3c8: deregister unregistered libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x802b9e450: deregister unregistered libxl: debug: libxl_dm.c:1435:libxl__spawn_local_dm: Spawning device-model /usr/local/lib/xen/bin/qemu-system-i386 with arguments: libxl: debug: libxl_dm.c:1437:libxl__spawn_local_dm: /usr/local/lib/xen/bin/qemu-system-i386 libxl: debug: libxl_dm.c:1437:libxl__spawn_local_dm: -xen-domid libxl: debug: libxl_dm.c:1437:libxl__spawn_local_dm: 2 libxl: debug: libxl_dm.c:
Re: Does a Xen Dom0 require X to function
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) - 0009d000 (usable) > (XEN) 0009d000 - 000a (reserved) > (XEN) 000e - 0010 (reserved) > (XEN) 0010 - 6a39b000 (usable) > (XEN) 6a39b000 - 7cd2f000 (reserved) > (XEN) 7cd2f000 - 7ce7f000 (ACPI NVS) > (XEN) 7ce7f000 - 7ceff000 (ACPI data) > (XEN) 7ceff000 - 7fa0 (reserved) > (XEN) b800 - fc00 (reserved) > (XEN) fec0 - fec01000 (reserved) > (XEN) fed08000 - fed09000 (reserved) > (XEN) fed1 - fed1a000 (reserved) > (XEN) fed1c000 - fed2 (reserved) > (XEN) fee0 - fee01000 (reserved) > (XEN) ffc0 - 0001 (reserved) > (XEN) 0001 - 00027e60 (usable) > (XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO) > (XEN) ACPI: XSDT 7CEFE170, 00EC (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: FACP 7CEF8000, 010C (r5 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: DSDT 7CEE, 120D4 (r1 LENOVO TP-GN2100 INTL 20120711) > (XEN) ACPI: FACS 7CE42000, 0040 > (XEN) ACPI: SLIC 7CEFD000, 0176 (r1 LENOVO TP-GN2100 PTEC1) > (XEN) ACPI: DBGP 7CEFB000, 0034 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: ECDT 7CEFA000, 0052 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: HPET 7CEF7000, 0038 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: APIC 7CEF6000, 0098 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: MCFG 7CEF5000, 003C (r1 LENOVO TP-GN2100 PTEC2) > (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 LENOVOCpuPm 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-GN2100 PTEC2) > (XEN) ACPI: SSDT 7CED8000, 0AC4 (r1 LENOVO Cpc_Tabl 1000 INTL 20120711) > (XEN) ACPI: TCPA 7CED7000, 0032 (r2PTL LENOVO 604 LNVO1) > (XEN) ACPI: UEFI 7CED6000, 0042 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: MSDM 7CDAA000, 0055 (r3 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: ASF! 7CEFC000, 00A5 (r32 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: BATB 7CED5000, 0046 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: FPDT 7CED4000, 0064 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: UEFI 7CED3000, 02E2 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) ACPI: SSDT 7CED2000, 047F (r1 LENOVO IsctTabl 1000 INTL 20120711) > (XEN) ACPI: DMAR 7CED1000, 00B8 (r1 LENOVO TP-GN2100 PTEC2) > (XEN) System RAM: 7817MB (8004832kB) > (XEN) No NUMA configuration found > (XEN) Faking a node at -00027e60 > (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) ACP
Re: Does a Xen Dom0 require X to function
> 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: (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) - 0009d000 (usable) (XEN) 0009d000 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 6a39b000 (usable) (XEN) 6a39b000 - 7cd2f000 (reserved) (XEN) 7cd2f000 - 7ce7f000 (ACPI NVS) (XEN) 7ce7f000 - 7ceff000 (ACPI data) (XEN) 7ceff000 - 7fa0 (reserved) (XEN) b800 - fc00 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fed08000 - fed09000 (reserved) (XEN) fed1 - fed1a000 (reserved) (XEN) fed1c000 - fed2 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ffc0 - 0001 (reserved) (XEN) 0001 - 00027e60 (usable) (XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO) (XEN) ACPI: XSDT 7CEFE170, 00EC (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: FACP 7CEF8000, 010C (r5 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: DSDT 7CEE, 120D4 (r1 LENOVO TP-GN2100 INTL 20120711) (XEN) ACPI: FACS 7CE42000, 0040 (XEN) ACPI: SLIC 7CEFD000, 0176 (r1 LENOVO TP-GN2100 PTEC1) (XEN) ACPI: DBGP 7CEFB000, 0034 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: ECDT 7CEFA000, 0052 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: HPET 7CEF7000, 0038 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: APIC 7CEF6000, 0098 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: MCFG 7CEF5000, 003C (r1 LENOVO TP-GN2100 PTEC2) (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 LENOVOCpuPm 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-GN2100 PTEC2) (XEN) ACPI: SSDT 7CED8000, 0AC4 (r1 LENOVO Cpc_Tabl 1000 INTL 20120711) (XEN) ACPI: TCPA 7CED7000, 0032 (r2PTL LENOVO 604 LNVO1) (XEN) ACPI: UEFI 7CED6000, 0042 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: MSDM 7CDAA000, 0055 (r3 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: ASF! 7CEFC000, 00A5 (r32 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: BATB 7CED5000, 0046 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: FPDT 7CED4000, 0064 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: UEFI 7CED3000, 02E2 (r1 LENOVO TP-GN2100 PTEC2) (XEN) ACPI: SSDT 7CED2000, 047F (r1 LENOVO IsctTabl 1000 INTL 20120711) (XEN) ACPI: DMAR 7CED1000, 00B8 (r1 LENOVO TP-GN2100 PTEC2) (XEN) System RAM: 7817MB (8004832kB) (XEN) No NUMA configuration found (XEN) Faking a node at -00027e60 (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/, using 32 (XEN) ACPI: wakeup_vec[7ce4200c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee0 (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
Re: Does a Xen Dom0 require X to function
El 05/11/15 a les 21.37, Thomas Laus ha escrit: >> Is there anything else in the Qemu logs? >> >> Also, can you post the output of `xl -vvv create ` and `xl >> list` while the domain is running? >> > I can't capture the 'xl -vvv create freebsd.cfg output to a file. This > computer doesn't have a functioning 'X' installation. The redirect to a file > '>' does not capture anything. 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 ;). > > The output of 'xl list': > > Name ID Mem VCPUs Stat Time(s) > Domain-0 0 20484 r- 23.5 > FreeBSD 1 512 1 -- 0.0 It looks like the guest called FreeBSD is not running at all. Can you paste the configuration file of your domain also? Can you also paste the output of `xl dmesg` after trying to launch the guest? Which revision of FreeBSD are you running in the Dom0? 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"
Re: Does a Xen Dom0 require X to function
> Is there anything else in the Qemu logs? > > Also, can you post the output of `xl -vvv create ` and `xl > list` while the domain is running? > I can't capture the 'xl -vvv create freebsd.cfg output to a file. This computer doesn't have a functioning 'X' installation. The redirect to a file '>' does not capture anything. The output of 'xl list': Name ID Mem VCPUsStat Time(s) Domain-0 0 20484 r- 23.5 FreeBSD 1 512 1 -- 0.0 The qemu-dm-FreeBSD.log: xen be core: can't open gnttab device qemu: terminating on signal 1 from pid 727 The xl-FreeBSD.log: Waiting for domain FreeBSD (domid 1) to die [pid 708] libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x8028193f8 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: register slotnum=2 libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x8028193f8 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1187:domain_death_xswatch_callback: [evg=0x802842a80:1] nentries=1 rc=1 1..1 libxl: debug: libxl.c:1198:domain_death_xswatch_callback: [evg=0x802842a80:1] got=domaininfos[0] got->domain=1 libxl: debug: libxl.c:1225:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=0002 libxl: debug: libxl.c:1191:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1254:domain_death_xswatch_callback: domain death search done libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: event epath=/local/domain/1/device/vbd/5632/eject libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: event epath=/local/domain/1/device/vbd/5632/eject libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: event epath=/local/domain/1/device/vbd/5632/eject libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: event epath=/local/domain/1/device/vbd/5632/eject libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x8028193f8 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1187:domain_death_xswatch_callback: [evg=0x802842a80:1] nentries=1 rc=1 1..1 libxl: debug: libxl.c:1198:domain_death_xswatch_callback: [evg=0x802842a80:1] got=domaininfos[0] got->domain=1 libxl: debug: libxl.c:1225:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=000b libxl: debug: libxl.c:1143:domain_death_occurred: dying libxl: debug: libxl.c:1191:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1254:domain_death_xswatch_callback: domain death search done Domain 1 has been destroyed. libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x8028193f8 wpath=@releaseDomain token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x802818440 wpath=/local/domain/1/device/vbd/5632/eject token=2/1: deregister slotnum=2 xc: debug: hypercall buffer: total allocations:4 total releases:4 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:2 misses:2 toobig:0 I hope that this information is helpful. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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"
Re: Does a Xen Dom0 require X to function
Hello, El 05/11/15 a les 15.09, Thomas Laus ha escrit: >> So the VNC client attaches successfully to the server, but the output is >> just a black screen? IMHO, that looks more like a guest or VNC issue >> rather than a Xen/Qemu one. Have you tried different guest OSes and >> different VNC clients? (TigerVNC Viewer has always worked fine for me). >> >> But regarding your question: no, Xen Dom0 doesn't require X at all in >> order to run. >> > I tried other guest OS's and VNC clients with the same result and came to the > conclusion that all of my guest OS's were not booting. All of my VNC clients > displayed the name of the guest OS in the margin, but had a black screen. I > looked at the 'xl list' billboard and the guest OS did not have a 'r' in the > column. The startup log for all of the guests had this line: > > 'xen be core: can't open gnttab device' Is there anything else in the Qemu logs? Also, can you post the output of `xl -vvv create ` and `xl list` while the domain is running? > My guess is that the 'gnttab' device is critical to a guest startup. I could > not find any reference to this item. What am I missing? No, gnttab is not critical, Qemu should work without it. 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"
Re: Does a Xen Dom0 require X to function
> So the VNC client attaches successfully to the server, but the output is > just a black screen? IMHO, that looks more like a guest or VNC issue > rather than a Xen/Qemu one. Have you tried different guest OSes and > different VNC clients? (TigerVNC Viewer has always worked fine for me). > > But regarding your question: no, Xen Dom0 doesn't require X at all in > order to run. > I tried other guest OS's and VNC clients with the same result and came to the conclusion that all of my guest OS's were not booting. All of my VNC clients displayed the name of the guest OS in the margin, but had a black screen. I looked at the 'xl list' billboard and the guest OS did not have a 'r' in the column. The startup log for all of the guests had this line: 'xen be core: can't open gnttab device' My guess is that the 'gnttab' device is critical to a guest startup. I could not find any reference to this item. What am I missing? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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"
Re: Does a Xen Dom0 require X to function
El 30/10/15 a les 18.02, Thomas Laus ha escrit: > List: > > I finally found a PC that had all of the necessary CPU instructions. It is > my company issued i7 laptop. I loaded FreeBSD Current on a spare hard drive > and Xen is able to start and the 'xl list' shows that my DomU is loaded and > running. I just get a black screen when attempting a vncviewer connection to > the Dom0 address from another computer. So the VNC client attaches successfully to the server, but the output is just a black screen? IMHO, that looks more like a guest or VNC issue rather than a Xen/Qemu one. Have you tried different guest OSes and different VNC clients? (TigerVNC Viewer has always worked fine for me). But regarding your question: no, Xen Dom0 doesn't require X at all in order to run. 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"
Does a Xen Dom0 require X to function
List: I finally found a PC that had all of the necessary CPU instructions. It is my company issued i7 laptop. I loaded FreeBSD Current on a spare hard drive and Xen is able to start and the 'xl list' shows that my DomU is loaded and running. I just get a black screen when attempting a vncviewer connection to the Dom0 address from another computer. I have not been able to get X to start on this Lenovo W540 laptop because of known Xorg problems separating the Intel 4600 primary display and the Nvidia graphic chip for the docking station. I wanted to test the functionality of Xen on FreeBSD before commiting to purchase a new motherboard and CPU that supports VT-d and EPT. I also got a xenserver syntax error when following the example configuration shown on the FreeBSD Wiki writeup. The 'vnclisten = 0.0.0.0' should have quotes around it. It should read vnclisten = "0.0.0.0" Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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"
