Re: FreeBSD PVHVM call for testing
Hi, On 22 Jul 2013, at 10:40, Jeroen van der Ham 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 22 Jul 2013, at 10:29, Roger Pau Monné 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 20 Jun 2013, at 11:33, Roger Pau Monné 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, I have this running for a day or so now, but I'm noticing that the load averages seem a bit off: $ uptime 11:17AM up 17:14, 1 user, load averages: 0.31, 0.27, 0.21 This is for a clean install, with just enough installed to compile this kernel. In top I'm seeing that the machine is idling >98% of the time. But this does not correlate to the load displayed above. Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 19 Jun 2013, at 18:52, Justin T. Gibbs wrote: >> I guess the kernel-toolchain takes a long time to build…and from what I can >> see it does a clean before rebuilding also. >> >> I'm doing the kernel-toolchain step only now and will report how long it >> took. This seems to be it, that took roughly 2 hours to build. The actual kernel is probably pretty fast in building. > Oh. Without any parallelism (-j X), the build will take a really long time. > Even with only one core, you'll get a large speedup by performing a parallel > build since many steps of the build are I/O bound. Neither of the systems actually had parallelism defined, either as flag or in /etc/make.conf Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 19 Jun 2013, at 18:15, Justin T. Gibbs wrote: > > I've never seen a kernel build take 2 hours, much less 2 hours *longer*. Are > you talking about buildworld? It would be interesting to know your results > building stable/9 sources in your 10 environment to see if this is just due > to "build bloat" or a true performance regression. > I copy/pasted the command from the wiki: > # make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make > installkernel KERNCONF=XENHVM On the stable/9 I only did > make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM I guess the kernel-toolchain takes a long time to build…and from what I can see it does a clean before rebuilding also. I'm doing the kernel-toolchain step only now and will report how long it took. Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 19 Jun 2013, at 14:44, Roger Pau Monné wrote: > On 19/06/13 14:33, Jeroen van der Ham wrote: >> >> On 19 Jun 2013, at 14:20, Roger Pau Monné wrote: >>> That's because Justin recently pushed a commit that changed the ad >>> translation to ada, you should change your /etc/fstab to ada0p2. It's >>> commit 526f3ad11acb296481215d7c2915b3f30f1844f6. >> >> >> Ah, you may want to update the wiki page also to warn for that. :) > > D'oh, I've completely forgot about the wiki page, it's updated now, > thanks for the pointer. Okay, everything works again now. Additionally, I've applied the patches from FreeBSD-SA-13:06.mmap, rebuilt the kernel and rebooted, and the system now works fine. I did note however that rebuilding the kernel takes an awful lot more time than on a FreeBSD9 system. As in it took about 2 hours longer. Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
On 19 Jun 2013, at 14:20, Roger Pau Monné wrote: > That's because Justin recently pushed a commit that changed the ad > translation to ada, you should change your /etc/fstab to ada0p2. It's > commit 526f3ad11acb296481215d7c2915b3f30f1844f6. Ah, you may want to update the wiki page also to warn for that. :) Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
On 19 Jun 2013, at 13:34, Roger Pau Monné wrote: > > Could you provide the boot log of the DomU, backtrace, Xen version and > Dom0 kernel version? I did not have a console attached when it rebooted, so I did not have a log of the initial boot. Now that I did, I see that it fails to mount its root volume. It had been running previously on pvhvm_v10 for about two weeks without problems. I updated my local git, and recompiled the kernel and rebooted. Then this happened. In order: Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 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 10.0-CURRENT #2 r+6ff8d00-dirty: Tue Jun 18 12:55:16 CEST 2013 root@image01:/usr/obj/root/freebsd/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.0 detected. CPU: Quad-Core AMD Opteron(tm) Processor 2374 HE (2200.07-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f42 Family = 0x10 Model = 0x4 Stepping = 2 Features=0x1781fbff Features2=0x80802001 AMD Features=0xe2500800 AMD Features2=0x1f3 real memory = 536870912 (512 MB) avail memory = 472260608 (450 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 random device not loaded; using insecure entropy ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-47 on motherboard kbd1 at kbdmux0 xen_et0: on motherboard Event timer "XENTIMER" frequency 10 Hz quality 950 Timecounter "XENTIMER" frequency 10 Hz quality 950 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a (3) failed cpu0: on acpi0 cpu1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: 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: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 1.3 (no driver attached) vgapci0: mem 0xf000-0xf1ff,0xf300-0xf3000fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem 0xf200-0xf2ff irq 28 at device 3.0 on pci0 xenstore0: on xenpci0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc9000-0xc97ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fdc0: No FDOUT register! Timecounters tick every 10.000 msec xenbusb_front0: on xenstore0 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [360385 x 2048 byte records] xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:2f:b7:22 xn1: at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:3e:64:c5 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xn1: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd0: disk supports cache flush using: barriers xbd1: 703MB at device/vbd/5632 on xenbusb_front0 xbd1: attaching as ada2 xbd1: disk supports cache flush using: barriers SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0p2 [rw]... mountroot: waiting for device /dev/ad0p2 ... Mounting from ufs:/dev/ad0p2 failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ad0p2 vfs.root.mountfrom.options=rw Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg
Re: FreeBSD PVHVM call for testing
Hi, I've just built a new kernel based on pvhvm_v17, but it panicked on boot. I still have a xen console attached, so I can provide additional information if someone gives me the right commands. Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 30 May 2013, at 16:56, Outback Dingo wrote: > first is this a public vm ? and if so who is?? > May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from > 150.165.15.175: 11: Bye Bye [preauth] > > because it is after this potential ssh login attempt, so is this you, has > there been a breach ? only thing i noticed, but it might be nothing. This VM is on a public IP indeed, and SSH connectivity is enabled. As with any publicly accessible host this then becomes the target of ssh scans. I included the message just to show that between it and the reboot nothing had been logged. AFAICT there has not been a breach, and I have not seen any indications at all that there may be one. Jeroen. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 30 May 2013, at 11:04, Roger Pau Monné 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 23 May 2013, at 19:41, Roger Pau Monné 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-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 wrote: > On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné wrote: > >> On 23/05/13 18:30, Outback Dingo wrote: >>> >>> >>> >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné >> <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é >><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: 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
On 13 May 2013, at 20:32, Roger Pau Monné 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-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD PVHVM call for testing
Hi, On 13 May 2013, at 20:32, Roger Pau Monné 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. 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 ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
