On Sun, Oct 13, 2013 at 10:58 AM, Mark Felder <f...@freebsd.org> wrote:
> > > On Sat, Oct 12, 2013, at 21:48, Justin T. Gibbs wrote: > > On Oct 10, 2013, at 3:09 AM, Shanker Balan <m...@shankerbalan.net> > wrote: > > > > > > > > On 10-Oct-2013, at 1:37 PM, Shanker Balan <m...@shankerbalan.net> > wrote: > > > > > >> On 09-Oct-2013, at 8:06 PM, Mark Felder <f...@freebsd.org> wrote: > > >> > > >>> On Wed, Oct 9, 2013, at 8:53, Roger Pau Monné wrote: > > >>>> On 09/10/13 13:49, Mark Felder wrote: > > >>>>> On Wed, Oct 9, 2013, at 2:46, Roger Pau Monné wrote: > > >>>>>> On 09/10/13 08:18, Shanker Balan wrote: > > >>>>>>> On 08-Oct-2013, at 9:19 PM, Mark Felder <f...@freebsd.org> > wrote: > > >>>>>>> > > >>>>>>>> On Tue, Oct 8, 2013, at 9:45, Josias L.G wrote: > > >>>>>>>>> Problem with Citrix Xen 6.2 and install from ISO. The > "solution" was > > >>>>>>>>> remove cd-rom drive from virtual machine. Not possible now > with xen > > >>>>>>>>> default in GENERIC kernel. > > >>>>>>>>> Message error: > > >>>>>>>>> run_interrupt_driven_hooks - still waiting after 300 seconds > for > > >>>>>>>>> xenbusb_nop_confighook_cb > > >>>>>>>>> panic: run_interrupt_driven_config_hooks: waited too long > > >>>>>>>>> > > >>>>>>>> > > >>>>>>>> I was going to test this soon... but you're right -- you > probably can't > > >>>>>>>> install FreeBSD 10 from ISO on Citrix XenServer because of this > bug. > > >>>>>>>> > > >>>>>>>> Can someone working on the xen bits test and maybe find a > workaround? > > >>>>>>> > > >>>>>>> The "xenbusb_nop_confighook_cb" issue is the only issue which I > am aware > > >>>>>>> of that prevents CloudStack/XenServer IaaS private clouds from > offering > > >>>>>>> FreeBSD 10 as a supported OS template. The "vbd-destroy" > workaround is not > > >>>>>>> possible as the ISO is attached to the VM instance during the > installation. > > >>>>>>> > > >>>>>>> A "please pretty please" request to @citrix R&D for the > hopefully last fix > > >>>>>>> to get FreeBSD 10 running on XenServer+CloudStack. > > >>>>>>> > > >>>>>>> The earlier HyperV related panic on XenServer has been fixed in > ALPHA5. > > >>>>>> > > >>>>>> Hello, > > >>>>>> > > >>>>>> I've taken a look into this and I'm afraid there's no easy way to > > >>>>>> workaround it from FreeBSD. When Xen is detected all IDE devices > are > > >>>>>> disconnected, and there's no fine grained way to only disable IDE > disks > > >>>>>> and not cdrom devices. > > >>>>>> > > >>>>>> Could you please contact your XenServer representative, and/or > submit > > >>>>>> this bug to xs-devel (xs-de...@lists.xenserver.org) mailing > lists in > > >>>>>> order to get this fixed on XenServer. > > >>>>>> > > >>>>> > > >>>>> Citrix is aware of this as I've contacted several people there and > this > > >>>>> has been discussed both here and on the xs-devel list. There has > to be > > >>>>> something FreeBSD can do to work around this issue since Linux and > > >>>>> NetBSD have no issues. > > >>>> > > >>>> Linux and NetBSD have no issues because you probably only tried > them on > > >>>> PV mode, which doesn't exhibit this issue (also NetBSD doesn't have > > >>>> PVHVM support, so it's quite clear it won't have this issue). > > >>>> > > >>>>> As far as I'm aware the issue has been tracked > > >>>>> down to badly behaving qemu in XenServer -- they don't use > upstream qemu > > >>>>> in XenServer (yet), and instead have their own fork. A future > release is > > >>>>> supposed to merge with upstream qemu. > > >>>> > > >>>> The main problem here is that XenServer announces a PV block device > on > > >>>> xenstore (the cdrom), but then it seems like there's no backend to > > >>>> handle it, so it hangs on the connection phase. IMHO the problem is > not > > >>>> with the device model (Qemu), but with the backend that should > handle > > >>>> this PV device. > > >>>> > > >>>> Xen only allows you to either disable all IDE devices or none, so > the > > >>>> only possible solution I can think of is to not disable anything at > all > > >>>> and use the emulated devices, which will leave us with very poor > > >>>> performance (unless I'm missing something, there's no way to only > > >>>> disable disks but not cdroms). > > >>>> > > >>>>> But the fact remains that this is a non-issue on Linux and NetBSD > who > > >>>>> handle this buggy virtual CDROM without any problems. There has to > be > > >>>>> some way we can add a quirk on our side so this device doesn't > stop the > > >>>>> entire boot process. If FreeBSD 10 is released without > out-of-the-box > > >>>>> support on the premier commercial Xen platform we'll be shooting > > >>>>> ourselves in the foot and all of this work will be for naught. > Amazon > > >>>>> isn't the only Xen platform people use. > > >>>> > > >>>> You can always use the pre-build VM images I guess (I have not > tested > > >>>> those, but I expect they should work fine under Xen). > > >>>> > > >>>> > ftp://ftp.nl.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/20131007/10.0-ALPHA5/amd64/ > > >>>> > > >> > > >> This is way better. Having ready to import Xen images beats ISO > installation > > >> any day. Will try on my cloudstack setup later today. > > > > > > I converted the QCOV image to VHD and have imported it into > CloudStack. Instance > > > created from the template also have the "xenbusb" issue at bootup. > > > > > > Oh well. > > > > > > Thanks for all the help. > > > > > > Regards. > > > @shankerbalan > > > > The CDROM issue should be resolved in FreeBSD/head. These fixes will be > > include > > in 10.0-BETA2 as well as the first 11-CURRENT snapshot that should pop up > > in > > the next day or two. The snapshots are announced on the > > freebsd-snapshots > > mailing list. > > > > Can you please backport to 9-STABLE? This issue is what is preventing me > from upgrading my Xen infrastructure at work. > > Thanks so much! > confirmed to also work on Ubuntu/XEN/virt-manager on my laptop even :P with cd attached as before it would fail dmesg 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 11.0-CURRENT #0 c8b87aa(master): Sun Oct 13 10:53:25 EDT 2013 di...@devel.xxxxxxx.com:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.3 detected. CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a Stepping = 9 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0xffb82203<SSE3,PCLMULQDQ,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> Standard Extended Features=0x200<ENHMOVSB> real memory = 2147483648 (2048 MB) avail memory = 2047053824 (1952 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> 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 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 random: <Software, Yarrow> initialized kbd1 at kbdmux0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: <Xen> on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: <ACPI CPU> on acpi0 cpu1: <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 0xb008-0xb00b 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,0xc260-0xc26f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 uhci0: <Intel 82371SB (PIIX3) USB controller> port 0xc240-0xc25f irq 23 at device 1.2 on pci0 usbus0: controller did not stop usbus0 on uhci0 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3020000-0xf3020fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: <XenStore> on xenpci0 pcm0: <AudioPCI ES1370> port 0xc100-0xc1ff irq 36 at device 5.0 on pci0 pcm0: <Playback: DAC1,DAC2 / Record: ADC> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: <floppy drive controller> 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 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! ppc0: cannot reserve I/O port range ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 xenbusb_front0: <Xen Frontend Devices> on xenstore0 ugen0.1: <Intel> at usbus0 uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: <QEMU QEMU DVD-ROM 0.10> Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:d2:55:c7 xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 65536MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd0: features: flush, write_barrier xbd0: synchronize cache commands enabled. random: unblocking device. xbd1: 65536MB <Virtual Block Device> at device/vbd/832 on xenbusb_front0 xbd1: attaching as ada1 xbd1: features: flush, write_barrier xbd1: synchronize cache commands enabled. Netvsc initializing... SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered Trying to mount root from zfs:zroot/bootenv/default []... xn0: 2 link states coalesced xm info host : M14xR2 release : 3.11.0-12-generic version : #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 2494 hw_caps : bfebfbff:28100800:00000000:00007f00:77bae3bf:00000000:00000001:00000281 virt_caps : hvm total_memory : 8074 free_memory : 6 free_cpus : 0 xen_major : 4 xen_minor : 3 xen_extra : .0 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=0xffff800000000000 xen_changeset : xen_commandline : placeholder cc_compiler : gcc (Ubuntu/Linaro 4.8.1-10ubuntu5) 4.8.1 cc_compile_by : stefan.bader cc_compile_domain : canonical.com cc_compile_date : Wed Oct 2 11:17:12 UTC 2013 xend_config_format : 4 > _______________________________________________ > 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"