Re: Xen console on 10.1 DomU
Hi, On 20 Jul 2015, at 18:04, Roger Pau Monné roger@citrix.com wrote: El 17/07/15 a les 21.02, Jeroen van der Ham ha escrit: Hi, What is the current way of getting a xen console on a FreeBSD 10.1 DomU? I’ve been searching on: * https://wiki.freebsd.org/FreeBSD/Xen (reasonably up to date, but has no info on console) * http://wiki.xen.org (completely outdated, “official” documentation points to installation of FreeBSD 7.2(!)) I found instructions to add a line to /boot/loader.conf (console=comconsole”) or a line to /etc/ttys (xc0 /usr/libexec/getty Pc vt100 on secure) You shouldn't need to modify /etc/ttys at all unless you are using a FreeBSD PVH guest or Dom0. But in either case I am getting an error on the Linux Dom0: xenconsole: Could not read tty from store: No such file or directory Is it still possible to get a console from a Linux Dom0? How? What would be the best place to publish instructions for that? Which kind of guest are you trying to get the console from? If it's a HVM guest (I'm only guessing here), you need to add serial='pty' to your xl configuration file and then follow https://www.freebsd.org/doc/handbook/serialconsole-setup.html. Thanks, that did the trick. Now the question remains where to document this properly so that others will not be mislead by all the other advice out there? Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Xen console on 10.1 DomU
Hi, What is the current way of getting a xen console on a FreeBSD 10.1 DomU? I’ve been searching on: * https://wiki.freebsd.org/FreeBSD/Xen (reasonably up to date, but has no info on console) * http://wiki.xen.org (completely outdated, “official” documentation points to installation of FreeBSD 7.2(!)) I found instructions to add a line to /boot/loader.conf (console=comconsole”) or a line to /etc/ttys (xc0 /usr/libexec/getty Pc vt100 on secure) But in either case I am getting an error on the Linux Dom0: xenconsole: Could not read tty from store: No such file or directory Is it still possible to get a console from a Linux Dom0? How? What would be the best place to publish instructions for that? Thanks, Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, After some more testing I thought it would be good to put this into production for my personal server. I've used pvhvm_v19 and built it without debugging options and installed it on a FreeBSD 9.1 system. I've run into some hiccups with 9.1 user land and a 10-CURRENT kernel, but that's all solvable[0]. My VPS has some very limited memory (256M), but I've compensated with swap space (1G) Now anytime I'm putting the system under stress, by building ports or by running a git clone on the kernel repository here, I'm seeing a lot of messages about swap_pager: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 132545, size: 4096 The system also becomes very sluggish and sometimes unresponsive. The weird thing was that one of these messages happened right after a reboot when I rebuilt an outdated port and on the main console was checking the swap memory: jeroen:~/ $ swapinfo [8:13:29] Device 1K-blocks UsedAvail Capacity /dev/ada0p2524288 2484 521804 0% /dev/md0 1048576 2364 1046212 0% Total 1572864 4848 1568016 0% swap_pager: indefinite wait buffer: bufobj: 0, blkno: 131424, size: 4096 Is anyone else seeing something similar? I certainly did not experience something like this on 9.0 with a XENHVM kernel. If necessary I can rebuild a kernel with debugging support and do some more recording of what is actually going on. Jeroen. [0]: I have edited bsd.port.mk to always apply the FBSD10_FIX, and for version checking I am running pkg version with UNAME_r=9.1-RELEASE. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, On 22 Jul 2013, at 10:29, Roger Pau Monné roger@citrix.com wrote: Is your guest running a 32bit or a 64bit kernel? $ uname -a FreeBSD positron.dckd.nl 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+a09eac7-dirty: Wed Jul 17 17:51:10 CEST 2013 root@image01:/usr/obj/usr/home/jeroen/freebsd/sys/XENHVM amd64 Could you also provide the config file used to launch your guest and the Xen and Dom0 kernel versions? Guest config: kernel = '/usr/lib/xen-4.0/boot/hvmloader' device_model = '/usr/lib/xen-4.0/bin/qemu-dm' builder = 'hvm' shadow_memory = 8 memory = 512 name = positron vcpus = 2 cpus = 2-7 maxvcpus = 4 xen_shell = 'root, jeroen' vif = [ 'type=vifname=positron.wan,bridge=br-wan,mac=00:16:3E:2F:AD:99,ip=94.142.246.99' , 'type=vifname=positron.lan,bridge=br-lan,mac=00:16:3E:0D:96:5C,ip=10.20.0.99' ] disk = ['phy:/xen/domains/positron/positron-disk1,hda,w'] xen_platform_pci=1 boot = 'c' sdl=0 stdvga=0 serial='pty' Xen info: host : soleus01.soleus.nu release: 2.6.32-5-xen-amd64 version: #1 SMP Mon Oct 3 07:53:54 UTC 2011 machine: x86_64 nr_cpus: 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2200 hw_caps: 178bf3ff:efd3fbff::1310:00802001::37ff: virt_caps : hvm total_memory : 65534 free_memory: 6865 node_to_cpu: node0:0-3 node1:4-7 node_to_memory : node0:3128 node1:3737 node_to_dma32_mem : node0:3128 node1:0 max_node_id: 1 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: placeholder dom0_mem=1852M cc_compiler: gcc version 4.4.5 (Debian 4.4.5-10) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Wed Jan 12 14:04:06 UTC 2011 xend_config_format : 4 Could you also try a HEAD XENHVM kernel (without my patches), to see if the issue is related to my changes or to some bug already present in HEAD? Will do. Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, On 22 Jul 2013, at 10:40, Jeroen van der Ham jer...@dckd.nl wrote: Could you also try a HEAD XENHVM kernel (without my patches), to see if the issue is related to my changes or to some bug already present in HEAD? It seems I was worrying too soon. I have been putting the system through the wringer some more, and I now believe that it has been caused by adding a new swap file. Just before I rebooted my system I created a larger swap file to be used by /etc/rc.d/add_swap. Right after I rebooted I started compiling and doing other things. And I am getting the feeling that the system was still initialising that swap file and was unable to provide swap space at that time. I've rebooted my system again with the PVHVM system, abused it even more than I did before and I'm not seeing the same messages again, nor getting any exaggerated sluggishness. So my apologies for the false alarm. Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: KERNCONF=XENHVM FAILED to build
Hi, I've been trying to build kernel on FreeBSD 9.0 also, and it fails for me as well: clang -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/home/jeroen/freebsd/sys -I/usr/home/jeroen/freebsd/sys/contrib/altq -I/usr/home/jeroen/freebsd/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/home/jeroen/freebsd/sys/kern/vfs_mountroot.c /usr/home/jeroen/freebsd/sys/kern/vfs_mountroot.c:270:2: error: expression result unused [-Werror,-Wunused-value] VFS_ROOT(mporoot, LK_EXCLUSIVE, vporoot); ^ /usr/home/jeroen/freebsd/sys/sys/mount.h:668:2: note: expanded from: _rc; }) ^~~ 1 error generated. *** Error code 1 Stop in /usr/obj/usr/home/jeroen/freebsd/sys/GENERIC. *** Error code 1 Stop in /usr/home/jeroen/freebsd. *** Error code 1 Stop in /usr/home/jeroen/freebsd. Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, On 20 Jun 2013, at 11:33, Roger Pau Monné roger@citrix.com wrote: This is probably due to the fact that we are not properly accounting for blocked/runnable/offline time. Did you see the same when running the XENHVM kernel without my patches? I have a different system on the same platform running FreeBSD9 with XENHVM. This server is running (web)mail, smokeping and irssi. That gives: 11:35AM up 20:07, 1 user, load averages: 0.06, 0.06, 0.07 Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, On 23 May 2013, at 19:41, Roger Pau Monné roger@citrix.com wrote: Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: I've been running a VM with this kernel for about a week now. It ran fine, until about 3:30 in the morning. The only thing I can see is the following cryptic messages in /var/log/messages, followed by a reboot of the system. May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] May 30 03:30:57 image01 kernel: . May 30 03:30:57 image01 ntpd[4436]: ntpd exiting on signal 15 May 30 03:30:57 image01 kernel: . May 30 03:30:58 image01 kernel: . May 30 03:31:00 image01 syslogd: exiting on signal 15 May 30 03:32:52 image01 syslogd: kernel boot file is /boot/kernel/kernel May 30 03:32:52 image01 kernel: Copyright (c) 1992-2013 The FreeBSD Project. May 30 03:32:52 image01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 30 03:32:52 image01 kernel: The Regents of the University of California. All rights reserved. May 30 03:32:52 image01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. I'm happy to help to gather more information, just tell me what you need. Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, On 30 May 2013, at 11:04, Roger Pau Monné roger@citrix.com wrote: So it looks like the system rebooted (but it was not a crash or a sporadic reboot? the kernel seems to be aware of the reboot request). It would be interesting if you could provide the output of the serial console when this happens, that might be helpful. Did you enable xenconsoled logging? Unfortunately I did not. Also, could you provide more info about your system, Xen version, what workload was the DomU running, Dom0 kernel version? There was no one logged in at the time of the reboot according to the last log. I did do some sysbench tests during the day, but that was way before it rebooted. The only thing that could be running during that time was daily periodic. $ sudo xm info host : soleus01.soleus.nu release: 2.6.32-5-xen-amd64 version: #1 SMP Mon Oct 3 07:53:54 UTC 2011 machine: x86_64 nr_cpus: 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2200 hw_caps: 178bf3ff:efd3fbff::1310:00802001::37ff: virt_caps : hvm total_memory : 65534 free_memory: 6866 node_to_cpu: node0:0-3 node1:4-7 node_to_memory : node0:3128 node1:3737 node_to_dma32_mem : node0:3128 node1:0 max_node_id: 1 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: placeholder dom0_mem=1852M cc_compiler: gcc version 4.4.5 (Debian 4.4.5-10) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Wed Jan 12 14:04:06 UTC 2011 xend_config_format : 4 $ uname -a Linux soleus01.soleus.nu 2.6.32-5-xen-amd64 #1 SMP Mon Oct 3 07:53:54 UTC 2011 x86_64 GNU/Linux Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
On 13 May 2013, at 20:32, Roger Pau Monné roger@citrix.com wrote: Also, I've created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM You mention on that page that it is easier to install on 10.0-CURRENT snapshots. What are the issues with installing this on 9.1? Is it possible? Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD PVHVM call for testing
Hi, Just remove this line (or pointing to a similar file from the template: (It's part of the disks definition: 'file:/root/freebsd-10.iso,hdc:cdrom,r', Jeroen. On 23 May 2013, at 19:02, Outback Dingo outbackdi...@gmail.com wrote: On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné roger@citrix.comwrote: On 23/05/13 18:30, Outback Dingo wrote: On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné roger@citrix.com mailto:roger@citrix.com wrote: On 23/05/13 14:57, Jeroen van der Ham wrote: Hi, On 13 May 2013, at 20:32, Roger Pau Monné roger@citrix.com mailto:roger@citrix.com wrote: Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. I've just been able to install it on a VPS using the latest pvhvm_v9 branch. The branch pvhvm_v9 contains an initial implementation of PV IPIs for amd64. I've now finished it and I'm going to port it to i386 also, and push a new branch to the repository. This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. I'm going to leave this running for a while and do some more tests on it. Jeroen. [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 I built the rev_9 branch on a XCP host and rebooted, however I am seeing on boot after ugen0.2: QEMU 0.10.2 at usbus0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_nop_confighook_cb panic: run_interrupt_driven_confighooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) db From what I've read on the list, it seems like you cannot boot the PVHVM kernel if you have a cdrom attached to the guest, could you try disabling the cdrom and booting again? great how does one go about disabling the cdrom, i get some disk parameters needs to be removed from the vm template before boot ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: kern/175822: [xen] FreeBSD 9.1 does not work with Xen 4.0
Hi, As I wrote before: This boots, and then goes into a loop printing pudna: fpcurthread == curthread xx times when it tries to mount the filesystem. I have tried the exact same setup with the similar 9.0 DVD, and this boots just fine. The system is then not respsonsive, with just the message scrolling by with the number increasing. Jeroen. On 5 Feb 2013, at 10:59, Egoitz Aurrekoetxea ego...@sarenet.es wrote: Why not?? What's the exact problem you are perceiving?? On 04/02/13 21:55, lini...@freebsd.org wrote: Old Synopsis: FreeBSD 9.1 does not work with Xen 4.0 New Synopsis: [xen] FreeBSD 9.1 does not work with Xen 4.0 Responsible-Changed-From-To: freebsd-bugs-freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 4 20:55:05 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org -- *Egoitz Aurrekoetxea* Departamento de sistemas Email: ego...@sarenet.es mailto:ego...@sarenet.es Phone: 94 - 420 94 00 SARENET ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
FreeBSD 9.1 and Xen 4.0?
Hi, I've been trying various things in my current setup with FreeBSD 9.1, but to no avail currently. I have tried the following setup on an AMD Opteron system, with kernel 2.6.32 on Dom0, using 4.0.1-2: kernel = '/usr/lib/xen-4.0/boot/hvmloader' device_model = '/usr/lib/xen-4.0/bin/qemu-dm' builder = 'hvm' memory = 512 shadow_memory = 8 vcpus = 4 cpus = 2-7 name = image01 #FreeBSD HVM disk = [ 'file:/xen/staging/FreeBSD-9.1-RELEASE-amd64-bootonly.iso,hdc:cdrom,r', 'phy:/dev/xendata/image,hda,w', ] boot = 'd' sdl=0 stdvga=0 serial='pty' This boots, and then goes into a loop printing pudna: fpcurthread == curthread xx times when it tries to mount the filesystem. Has anyone been succesful in installing FreeBSD 9.1 using Xen-4.0 ? Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Upgrading XENHVM 9.0 to 9.1
Hi, I've been playing around with an extra VPS on the same host. I used the same base image as my original VPS, this was FreeBSD 9.0-RELEASE-p4. For installation I first installed a bare minimum install, booted it, and using portsnap and freebsd-update installed additional components. I succesfully compiled a XENHVM kernel on that image, which boots just fine, on both of my VPSes. I can succesfully perform a freebsd-update to 9.1-RELEASE. If I then try to compile and install a new kernel, things go awry, both with GENERIC and XENHVM. I am fairly certain now that it has to do with the filesystem driver. I can succesfull boot into single user mode, get the prompt about bin/sh, and the moment I press enter it goes into the loop printing fpudna: fpcurthread == curthread 444 times Attached is the boot output. Let me know if there is anything I can do to help track down the problem. Jeroen. __ _ _ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | |||| | | | |_| |_| \___|\___||/|_/|_/```` s` `.---...--.``` -/ ?Welcome to FreeBSD +o .--` /y:` +. ? ? yo`:.:o `+- ? 1. Boot [Enter]? y/ -/` -o/ ? 2. [Esc]ape to loader prompt ? .- ::/sy+:. ? 3. Reboot ? / `-- / ? ? `: :` ? Options: ? `: :` ? 4. [A]CPI Support On ? / / ? 5. Safe [M]ode... off ? .--. ? 6. [S]ingle User. off ? -- -. ? 7. [V]erbose. off ?`:` `:` ? ? .-- `--. ? ? .---.. ??? Copyright (c) 1992-2012 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 9.1-RELEASE #0: Fri Feb 1 20:13:55 CET 2013 root@:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Quad-Core AMD Opteron(tm) Processor 2374 HE (2200.08-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x100f42 Family = 10 Model = 4 Stepping = 2 Features=0x1781fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX,FXSR,SSE,SSE2,HTT Features2=0x80802001SSE3,CX16,POPCNT,HV AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x1f3LAHF,CMP,CR8,ABM,SSE4A,MAS,Prefetch real memory = 536870912 (512 MB) avail memory = 492613632 (469 MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-47 on motherboard kbd1 at kbdmux0 acpi0: Xen on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a (3) failed 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 Event timer RTC frequency 32768 Hz quality 0 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 32-bit timer at 3.579545MHz port 0x1f48-0x1f4b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 WDMA2 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: ATA channel at channel 0 on atapci0 ata1: ATA channel at channel 1 on atapci0 pci0: bridge at device 1.3 (no driver attached) vgapci0: VGA-compatible display mem 0xf000-0xf1ff,0xf300-0xf3000fff at device 2.0 on pci0 pci0: unknown at device 3.0 (no driver attached) re0: RealTek 8139C+ 10/100BaseTX port 0xc100-0xc1ff mem 0xf3001000-0xf30010ff irq 32 at device 4.0 on pci0 re0: Chip rev. 0x7480 re0: MAC rev. 0x miibus0: MII bus on re0 rlphy0: RealTek internal media interface PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow re0: Ethernet address: 00:16:3e:2f:b7:22 re1: RealTek 8139C+ 10/100BaseTX port 0xc200-0xc2ff mem 0xf3001100-0xf30011ff irq 36 at device 5.0 on pci0 re1: Chip rev. 0x7480 re1:
Re: Upgrading XENHVM 9.0 to 9.1
Hi, On 24 Jan 2013, at 14:41, Mark Felder f...@feld.me wrote: - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting from that results in a rootmount mismatch (ada0 vs ad0). Just renaming it in /etc/fstab does not seem to be enough, what else would I need to do? Yes, the GENERIC kernel uses adaX and the XENHVM kernel uses adX. It shouldn't be a problem to just change it in the fstab though. I've not yet had problems running 9.1 with XENHVM yet. I tried this both using the mountroot prompt when booting with an old fstab and a corrected fstab. In both cases the kernel is not able to mount the UFS volume. - I manually built a new 9.1 XENHVM kernel. Booting from that results in the message: pudna: fpcurthread == curthread xx times scrolling by. What can I do to fix that? I've not seen this message yet either. I've seen this message also previously when I was toying around with my 9.0 system. I forget what exactly I did though. There are some references to it in earlier cases, dating back to 2005: http://marc.info/?l=freebsd-amd64m=112231842214570 Another in 2010: http://forums.freebsd.org/showthread.php?t=17979 (I did not try those options yet though) Can you provide more details of the Xen environment you're hosted on? AMD Opteron system, with kernel 2.6.32 on Dom0, using 4.0.1-2. My VPS is run using Xen qemu. Is there a problem in continuing to run the 9.0 XENHVM kernel with the 9.1 system? This would not be advised. It *may* work, but be warned that you may run into strange issues. I noticed that freebsd-update started complaining during its cron-job. I've since performed a freebsd-update rollback. Jeroen. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Upgrading XENHVM 9.0 to 9.1
Hi, Today I started with an upgrade process of my VPS which has been running 9.0 XENHVM almost a full year. I followed the process as outlined on the Handbook[1]. I may have made a mistake in placing back the right old kernel, but a new GENERIC kernel did not get installed. I was able to boot into the 9.1 system using my old 9.0 XENHVM kernel. I have been trying to fix this, but I keep running into problems: - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting from that results in a rootmount mismatch (ada0 vs ad0). Just renaming it in /etc/fstab does not seem to be enough, what else would I need to do? - I manually built a new 9.1 XENHVM kernel. Booting from that results in the message: pudna: fpcurthread == curthread xx times scrolling by. What can I do to fix that? Is there a problem in continuing to run the 9.0 XENHVM kernel with the 9.1 system? Thanks for any help, Jeroen. [1]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
fpudna: fpcurthread == curthread XXXX times
Hello, I've been trying to compile a kernel for my FreeBSD9 XEN guest system using the provided XENHVM config. I found that that configuration works fine, unless you use a specific make.conf file. When I used that make.conf file, booting from that kernel it spams the console with consecutive messages of: fpudna: fpcurthread == curthread times The make.conf file that I used is an adapted version of /usr/share/examples/etc/make.conf: % diff /etc/make.conf /usr/share/examples/etc/make.conf 47c47 CPUTYPE=opteron --- #CPUTYPE?=pentium3 61c61 CFLAGS= -O2 -fno-strict-aliasing -pipe --- #CFLAGS= -O2 -fno-strict-aliasing -pipe 68c68 CXXFLAGS+= -fconserve-space --- #CXXFLAGS+= -fconserve-space 185,190c185,190 SUP=/usr/bin/csup SUPFLAGS= -L 2 SUPHOST=cvsup.uk.FreeBSD.org SUPFILE=/usr/share/examples/cvsup/standard-supfile PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile --- #SUP=/usr/bin/csup #SUPFLAGS= -L 2 #SUPHOST=cvsup.uk.FreeBSD.org #SUPFILE=/usr/share/examples/cvsup/standard-supfile #PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile #DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile 287,289d286 # added by use.perl 2012-01-16 21:35:36 PERL_VERSION=5.12.4 WITHOUT_X11=YES Does anyone know what might cause this problem, and why it would not be caught earlier? Jeroen.___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
