Current problem reports assigned to freebsd-xen@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/171873 xen[xen] xn network device floods warning in dmesg o kern/171138 xen[xen] [panic] Deactivating network interface produces o kern/171118 xen[xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen[xen] Problems ROOT MOUNT ERROR freebsd 8.3 o kern/165418 xen[xen] Problems mounting root filesystem from XENHVM o kern/164630 xen[xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen[xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen[xen] FreeBSD not compatible with Current Stable Xen o kern/161318 xen[xen] sysinstall crashes with floating point exception o kern/155468 xen[xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen[xen] [patch] put nudging TOD message under boot_ver o kern/154833 xen[xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen[xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen[xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen[xen] xn0 network interface and PF - Massive performan o kern/153674 xen[xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen[xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen[xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen[xen] XEN pmap code abuses vm page queue lock o kern/153150 xen[xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen[xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen[xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xenufs filesystem corruption on XEN DomU system f kern/135421 xen[xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen[xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen[xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen[xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen[xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 31 problems total. ___ 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
xenbusb_nop_confighook_cb timeout and cd issue
Good morning,
After doing some checks and debugs about this problem, I can conclude that :
under Xen 4.1.3 on Debian Wheezy it works properly although in XCP1.6 if you
remove the cd drive from the vm works too. I'm going to describe the two test
environments have used for debugging this :
ENV 1.- XCP 1.6 XEN 4.1.3 + FREEBSD 9.1-RC3 :
As you can see with an iso image mounted and without it, the boot process gets
stuck there….. (I paste here both screenshot location).
http://postfixquotareject.ramattack.net/PastedGraphic-8.tiff
http://postfixquotareject.ramattack.net/PastedGraphic-11.tiff
I have placed here two examples, with an empty (but existing) cd drive and with
a iso mounted in the drive.
BUT If I do a in the XCP shell :
xe vm-cd-remove uuid=08aec342-9572-8690-5e58-91d1b1f0aab2 cd-name=xs-tools.iso
The drive is being removed from the vm and it boots normally. This is the
workaround I'm using for the moment.
Another debugging check I have done too is to apply this patch (although it's
just for testing purposes and for checking if cd drive works) to see how the
drive behaves after booting but without stopping in that loop of the FreeBSD
kernel source code.
--- /usr/src/sys/kern/subr_autoconf.c-defecto 2012-10-10 13:51:27.0
+0200
+++ /usr/src/sys/kern/subr_autoconf.c 2012-10-10 18:21:51.0 +0200
@@ -133,16 +133,17 @@
/* Block boot processing until all hooks are disestablished. */
mtx_lock(intr_config_hook_lock);
warned = 0;
- while (!TAILQ_EMPTY(intr_config_hook_list)) {
+ /* while (!TAILQ_EMPTY(intr_config_hook_list)) { */
if (msleep(intr_config_hook_list, intr_config_hook_lock,
0, conifhk, WARNING_INTERVAL_SECS * hz) ==
EWOULDBLOCK) {
mtx_unlock(intr_config_hook_lock);
warned++;
run_interrupt_driven_config_hooks_warning(warned);
mtx_lock(intr_config_hook_lock);
}
- }
+ /* } */
mtx_unlock(intr_config_hook_lock);
}
After applying this patch, kernel boots under XCP 1.6Beta and cd can be mounted
in the shell (should say I have not noticed about IRQ problems after this). It
seems like FreeBSD domU is not able to continue the boot process because it's
not able to finish up some test related to THIS (the cd drive) device setup
(IRQ assigning tests I assume concretely) that should succeed before being
able to continue the boot process.
ENV 2.- Debian Wheezy (testing) XEN 4.1.3 + FreeBSD 9.1-RC3 :
Here is the concrete environment and config :
root@pruebas-xen-egoitz:~# uname -ar
Linux pruebas-xen-egoitz 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
root@pruebas-xen-egoitz:~# cat /etc/issue
Debian GNU/Linux wheezy/sid \n \l
root@pruebas-xen-egoitz:~# dpkg -l | grep -i xen
ii libxen-4.1 4.1.3-4 amd64
Public libs for Xen
ii libxenstore3.0 4.1.3-4 amd64
Xenstore communications library for Xen
ri linux-image-2.6.32-5-xen-amd64 2.6.32-46 amd64
Linux 2.6.32 for 64-bit PCs, Xen dom0 support
rc xen-hypervisor-4.0-amd64 4.0.1-5.4 amd64
The Xen Hypervisor on AMD64
ii xen-hypervisor-4.1-amd64 4.1.3-4 amd64
Xen Hypervisor on AMD64
ii xen-linux-system-3.2.0-4-amd64 3.2.32-1 amd64
Xen system with Linux 3.2 on 64-bit PCs (meta-package)
ii xen-linux-system-amd64 3.2+46amd64
Xen system with Linux for 64-bit PCs (meta-package)
ii xen-system-amd64 4.1.3-4 amd64
Xen System on AMD64 (meta-package)
ii xen-tools 4.3.1-1 all
Tools to manage Xen virtual servers
ii xen-utils-4.1 4.1.3-4 amd64
XEN administrative tools
ii xen-utils-common 4.1.3-4 all
Xen administrative tools - common files
ii xenstore-utils 4.1.3-4 amd64
Xenstore utilities for Xen
root@pruebas-xen-egoitz:~# xm list
NameID Mem VCPUs State Time(s)
Domain-0 0 6908 8 r- 1526.2
freebsd90js.ramattack.net 24 512 2 -b 59.9
I normally create the life cycle with a xm new, later xm start……. the config
file is :
root@pruebas-xen-egoitz:~# cat /etc/xen/freebsd90rjs.ramattack.net.cfg
kernel = '/usr/lib/xen-4.1/boot/hvmloader'
builder = 'hvm'
vcpus = 2
memory = 512
name = 'freebsd90js.ramattack.net'
vif = [ 'bridge=eth0, mac=00:13:3E:19:88:22, type=ioemu' ]
disk = [
Nova CPE Krazer Sky Station 5GHz N - CPE Antena Integrada de 18dBi e Com Saída para Antena Externa
Lançamento CPE Krazer Sky Station 5GHz N Você cliente pediu que a Krazer fizesse uma nova CPE num formato mais estiloso, pequena, de menor tamanho e que tivesse novas funcionabilidade, mais especificamente acesso fácil ao botão de reset, proteção contra queima e a tão desejada SAÍDA PARA ANTENA EXTERNA!!! R$ 179.90 Antena Integrada de 18dBi 60º Duas Portas de Rede Lan e Wan PA Real de 630mW e LNA Ultra Ganho PoE Passivo com Proteção Dupla de 12 a 24V Fonte Chaveada 12V Full Range 110 a 220V Exclusiva Saída para Antena Externa Homologação Anatel 0269-11-5280 Instalação Rápida e Simples. Software Amigavel e em Português! Suporte a PPPoE Wisp Cliente! Controle de Banda! Excelente sinal de recepção! Longa Distância! Faça um teste em sua rede e compare com os concorrentes, muito mais sinal que UBNT, muito mais dados, transmissão de quase 90Mbps TCP/IP continuamente! Latência de rede de 1 a 5 ms com carga completa! Contate-nos Val Campos // Carla Maria // Eder Roberto Email / MSN: ven...@allearth.com.br Vendas / SAC (19) 3256-5557 (19) 3245-0708 www.krazer.com.br Envio de Email não autorizado é crime, não seja o vilão da história! Email é protegido sobre sigilo fiscal e federal. Lei Federal Brasil. ___ 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: xenbusb_nop_confighook_cb timeout and cd issue
On Mon, 2012-12-03 at 19:04 +0100, Egoitz Aurrekoetxea Aurre wrote:
Good morning,
After doing some checks and debugs about this problem, I can conclude that :
under Xen 4.1.3 on Debian Wheezy it works properly although in XCP1.6 if you
remove the cd drive from the vm works too. I'm going to describe the two test
environments have used for debugging this :
ENV 1.- XCP 1.6 XEN 4.1.3 + FREEBSD 9.1-RC3 :
As you can see with an iso image mounted and without it, the boot process
gets stuck there….. (I paste here both screenshot location).
http://postfixquotareject.ramattack.net/PastedGraphic-8.tiff
http://postfixquotareject.ramattack.net/PastedGraphic-11.tiff
I have placed here two examples, with an empty (but existing) cd drive and
with a iso mounted in the drive.
BUT If I do a in the XCP shell :
xe vm-cd-remove uuid=08aec342-9572-8690-5e58-91d1b1f0aab2 cd-name=xs-tools.iso
The drive is being removed from the vm and it boots normally. This is the
workaround I'm using for the moment.
Another debugging check I have done too is to apply this patch (although it's
just for testing purposes and for checking if cd drive works) to see how the
drive behaves after booting but without stopping in that loop of the FreeBSD
kernel source code.
--- /usr/src/sys/kern/subr_autoconf.c-defecto 2012-10-10 13:51:27.0
+0200
+++ /usr/src/sys/kern/subr_autoconf.c 2012-10-10 18:21:51.0 +0200
@@ -133,16 +133,17 @@
/* Block boot processing until all hooks are disestablished. */
mtx_lock(intr_config_hook_lock);
warned = 0;
- while (!TAILQ_EMPTY(intr_config_hook_list)) {
+ /* while (!TAILQ_EMPTY(intr_config_hook_list)) { */
if (msleep(intr_config_hook_list, intr_config_hook_lock,
0, conifhk, WARNING_INTERVAL_SECS * hz) ==
EWOULDBLOCK) {
mtx_unlock(intr_config_hook_lock);
warned++;
run_interrupt_driven_config_hooks_warning(warned);
mtx_lock(intr_config_hook_lock);
}
- }
+ /* } */
mtx_unlock(intr_config_hook_lock);
}
After applying this patch, kernel boots under XCP 1.6Beta and cd can be
mounted in the shell (should say I have not noticed about IRQ problems after
this). It seems like FreeBSD domU is not able to continue the boot process
because it's not able to finish up some test related to THIS (the cd drive)
device setup (IRQ assigning tests I assume concretely) that should succeed
before being able to continue the boot process.
ENV 2.- Debian Wheezy (testing) XEN 4.1.3 + FreeBSD 9.1-RC3 :
Here is the concrete environment and config :
root@pruebas-xen-egoitz:~# uname -ar
Linux pruebas-xen-egoitz 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
root@pruebas-xen-egoitz:~# cat /etc/issue
Debian GNU/Linux wheezy/sid \n \l
root@pruebas-xen-egoitz:~# dpkg -l | grep -i xen
ii libxen-4.1 4.1.3-4 amd64
Public libs for Xen
ii libxenstore3.0 4.1.3-4 amd64
Xenstore communications library for Xen
ri linux-image-2.6.32-5-xen-amd64 2.6.32-46 amd64
Linux 2.6.32 for 64-bit PCs, Xen dom0 support
rc xen-hypervisor-4.0-amd64 4.0.1-5.4 amd64
The Xen Hypervisor on AMD64
ii xen-hypervisor-4.1-amd64 4.1.3-4 amd64
Xen Hypervisor on AMD64
ii xen-linux-system-3.2.0-4-amd64 3.2.32-1 amd64
Xen system with Linux 3.2 on 64-bit PCs (meta-package)
ii xen-linux-system-amd64 3.2+46amd64
Xen system with Linux for 64-bit PCs (meta-package)
ii xen-system-amd64 4.1.3-4 amd64
Xen System on AMD64 (meta-package)
ii xen-tools 4.3.1-1 all
Tools to manage Xen virtual servers
ii xen-utils-4.1 4.1.3-4 amd64
XEN administrative tools
ii xen-utils-common 4.1.3-4 all
Xen administrative tools - common files
ii xenstore-utils 4.1.3-4 amd64
Xenstore utilities for Xen
root@pruebas-xen-egoitz:~# xm list
NameID Mem VCPUs State
Time(s)
Domain-0 0 6908 8 r- 1526.2
freebsd90js.ramattack.net 24 512 2 -b 59.9
I normally create the life cycle with a xm new, later xm start……. the config
file is :
root@pruebas-xen-egoitz:~# cat /etc/xen/freebsd90rjs.ramattack.net.cfg
kernel = '/usr/lib/xen-4.1/boot/hvmloader'
builder = 'hvm'
vcpus = 2
memory
