Re: Panic booting with FreeBSD 10 r259073 under XenServer 6.2
On 29-Dec-2013, at 4:44 pm, Karl Pielorz kpielorz_...@tdx.co.uk wrote: --On 28 December 2013 23:55:06 +0530 Shanker Balan m...@shankerbalan.net wrote: FreeBSD 10 RC3 r259778 is what I am running under XenServer 6.2 here which seems to work fine. root@gw1-1:~ # uname -a FreeBSD gw1-1 10.0-RC3 FreeBSD 10.0-RC3 #0 r259778: Tue Dec 24 04:35:46 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 Ok, having fixed up my svn mirror - I switched to base/releng/10.0 - which got me r260027. A kernel built from that doesn't boot either (same panic). I've also just noticed you're running i386 - I'm running amd64. Do you have any 10.x amd64 systems running under XenServer 6.2? -Karl Yep, I have 64bit also running just fine. Not updated to RC3 yet though. $ uname -a FreeBSD fb10-xen64 10.0-RC2 FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 08:18:20 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Regards. @shankerbalan ___ 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 Alpha5 amd64 - Citrix Xen 6.2 problem
On 13-Oct-2013, at 8:18 AM, Justin T. Gibbs gi...@scsiguy.com 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 RD 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. I just saw the commit myself. Really looking forward to FreeBSD 10 on XenServers. Thank you very much much. Regards. @shankerbalan ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd
Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem
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 RD 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 ___ 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 Alpha5 amd64 - Citrix Xen 6.2 problem
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 RD 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. Regards. @shankerbalan ___ 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: Latest current -CURRENT (rev 255904) panics with device hyperv on XenServer 6.2
On 04-Oct-2013, at 5:35 PM, Sergey Nasonov snaso...@bcc.ru wrote: Hi Sergey, Thank you very much for suggesting the workaround. My use case is for users uploading the ISO to CloudStack private cloud and not being able to install FreeBSD 10. As an end user of cloudstack, I don't have access to the hypervisor (XenServer) to make the required param changes. End user's only have the ability to upload ISOs and create VMs and they will hit the panic. Ок, in that case you need to change properties of template, based on which your users created their VMs. The only user modifiable template setting is the Operating System type. I think it is possible with CloudStack. As of now, its not possible to modify any param-set options via template settings in CloudStack. Regards. @shankerbalan ___ 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: Latest current -CURRENT (rev 255904) panics with device hyperv on XenServer 6.2
On 27-Sep-2013, at 9:59 PM, Shanker Balan m...@shankerbalan.net wrote: (Doing a proper reply all now) On 27-Sep-2013, at 8:34 PM, Roger Pau Monné roger@citrix.com wrote: On 27/09/13 16:59, Shanker Balan wrote: Roger, Thank you very much for looking into the issue. Can I have a SVN version of the patch? patch does not seem to like the diff (or maybe I am using it incorrectly) root@fxen1:/usr/src # patch -n ~/xen_hyperv.patch Hmm... I can't seem to find a patch in there anywhere. $ patch -p1 /path/to/patch should work AFAIK, this is a git generated diff. If it still doesn't work applying it by hand shouldn't be that hard. Patch works for me on XenServer 6.2. root@fxen1:~ # uname -a FreeBSD fxen1.lab 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #1 r255912M: Fri Sep 27 15:27:19 IST 2013 r...@fxen1.lab:/usr/obj/usr/src/sys/MYKERNEL amd64 root@fxen1:~ # root@fxen1:~ # sysctl -a | grep ^device | grep xen\|hyper devicehyperv devicexenpci Thank you very much. I just tried FreeBSD 10 ALPHA4 ISO. The ISO fails to boot on XenServer 6.2 resulting with the same HyperV panic Regards. @shankerbalan ___ 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
Latest current -CURRENT (rev 255904) panics with device hyperv on XenServer 6.2
Helo, Now that XENHVM has been merged into the GENERIC kernel, I recompiled todays -CURRENT (rev 255904) and hit the following panic. It seeems to be HyperV related. GENERIC without device hyperv works properly. The hypervisor is XenServer 6.2. # HyperV drivers device hyperv # HyperV drivers Panic screenshots with backtrace at http://imgur.com/cZsDsKEVCkh4VS Regards. @shankerbalan ___ 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: Latest current -CURRENT (rev 255904) panics with device hyperv on XenServer 6.2
On 27-Sep-2013, at 8:20 PM, Roger Pau Monné roger@citrix.com wrote: On 27/09/13 08:16, Shanker Balan wrote: Helo, Now that XENHVM has been merged into the GENERIC kernel, I recompiled todays -CURRENT (rev 255904) and hit the following panic. It seeems to be HyperV related. GENERIC without device hyperv works properly. The hypervisor is XenServer 6.2. # HyperV drivers device hyperv # HyperV drivers Panic screenshots with backtrace at http://imgur.com/cZsDsKEVCkh4VS Hello, This is because XenServer enables viridian by default when running HVM guests. That makes Xen also announce itself as HyperV for compatibility reasons, as a workaround you can try to disable viridian support (not sure if this is possible on XenServer). I'm attaching a patch that should solve the problem, Ccing the virt mailing list and the persons that I think are involved in the HyperV support for FreeBSD. Hi Roger, Thank you very much for looking into the issue. Can I have a SVN version of the patch? patch does not seem to like the diff (or maybe I am using it incorrectly) root@fxen1:/usr/src # patch -n ~/xen_hyperv.patch Hmm... I can't seem to find a patch in there anywhere. root@fxen1:/usr/src # Regards. @shankerbalan ___ 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: Latest current -CURRENT (rev 255904) panics with device hyperv on XenServer 6.2
(Doing a proper reply all now) On 27-Sep-2013, at 8:34 PM, Roger Pau Monné roger@citrix.com wrote: On 27/09/13 16:59, Shanker Balan wrote: Roger, Thank you very much for looking into the issue. Can I have a SVN version of the patch? patch does not seem to like the diff (or maybe I am using it incorrectly) root@fxen1:/usr/src # patch -n ~/xen_hyperv.patch Hmm... I can't seem to find a patch in there anywhere. $ patch -p1 /path/to/patch should work AFAIK, this is a git generated diff. If it still doesn't work applying it by hand shouldn't be that hard. Patch works for me on XenServer 6.2. root@fxen1:~ # uname -a FreeBSD fxen1.lab 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #1 r255912M: Fri Sep 27 15:27:19 IST 2013 r...@fxen1.lab:/usr/obj/usr/src/sys/MYKERNEL amd64 root@fxen1:~ # root@fxen1:~ # sysctl -a | grep ^device | grep xen\|hyper device hyperv device xenpci Thank you very much. Regards. @shankerbalan ___ 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
