Re: [solved] iommu must be enabled for PVH hardware domain
Roger Pau Monné wrote on 05/13/15 14:21: El 13/05/15 a les 13.12, Ruslan Makhmatkhanov ha escrit: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? Can you paste the DomU configuration file (debian.cfg)? Here it is: https://dpaste.de/wneF/raw This is weird, I don't see anything obviously wrong. Could you try to increase the DomU memory to 512Mb and boot again? Yes, it is helped. So 512Mb is the minimal RAM quantity? This is FreeBSD HVM attempt: Can you run the same command with xl -vvv instead (it will print more http://dpaste.com/2AGRN13 verbose debug info)? Also, can you paste the contents of /var/log/xen/qemu-dm-freebsd.log? Roger. This log-file contains only one line: VNC support is disabled I think this is fixed in the last version of the xen-tools package, can you make sure you are using xen-tools-4.5.0_4? Roger. You are right. It's xen-tools-4.5.0_3 installed from packages. Will build own package later and response back. Thank you much for all your help! -- Regards, Ruslan T.O.S. Of Reality ___ 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: [solved] iommu must be enabled for PVH hardware domain
El 13/05/15 a les 13.12, Ruslan Makhmatkhanov ha escrit: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? Can you paste the DomU configuration file (debian.cfg)? Here it is: https://dpaste.de/wneF/raw This is weird, I don't see anything obviously wrong. Could you try to increase the DomU memory to 512Mb and boot again? This is FreeBSD HVM attempt: Can you run the same command with xl -vvv instead (it will print more http://dpaste.com/2AGRN13 verbose debug info)? Also, can you paste the contents of /var/log/xen/qemu-dm-freebsd.log? Roger. This log-file contains only one line: VNC support is disabled I think this is fixed in the last version of the xen-tools package, can you make sure you are using xen-tools-4.5.0_4? Roger. ___ 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: [solved] iommu must be enabled for PVH hardware domain
El 13/05/15 a les 12.34, Ruslan Makhmatkhanov ha escrit: My bad. `ulimit -l unlimited` doesn't worked for me, but changing the limit via /etc/login.conf did. Now it works flawlessly. Thank you! Is there any resource where these cases covered (Cannot allocate memory and disabling IOMMU because of erratas)? Just want to know bloody details. I don't thinks there's any generic resource about this issues, your best bet is to google for them, this is for example the patch related to that hw errata: http://lists.xen.org/archives/html/xen-devel/2013-01/msg01016.html It contains a link to the Intel SDM that has more info about the erratas. And one more question, am I right that PV-guests are no more supported in FreeBSD? We tried to run Debian guest in PV mode like described here: http://wiki.xen.org/wiki/FreeBSD_Dom0#Creating_your_first_PV_guest but guest's kernel panicking like that: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? Can you paste the DomU configuration file (debian.cfg)? This is FreeBSD HVM attempt: libxl: error: libxl_dm.c:1482:device_model_spawn_outcome: domain 5 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1319:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1586:kill_device_model: Device Model already exited Can you run the same command with xl -vvv instead (it will print more verbose debug info)? Also, can you paste the contents of /var/log/xen/qemu-dm-freebsd.log? Roger. ___ 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: [solved] iommu must be enabled for PVH hardware domain
Roger Pau Monné wrote on 05/13/15 11:51: Hello, El 13/05/15 a les 10.46, Ruslan Makhmatkhanov ha escrit: Yes, the system is now booted successfully! But `xl list` doesn't work with: root@:~ # xl list libxl: error: libxl.c:669:libxl_list_domain: getting domain info list: Cannot allocate memory libxl_list_domain failed. [...] Shell memory values are unlimited too: root@:~ # ulimit -a cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 33554432 stack size (kbytes, -s) 524288 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) 64 Shell memory is not unlimited, as the output above shows. `ulimit -l unlimited` should fix that. Roger. My bad. `ulimit -l unlimited` doesn't worked for me, but changing the limit via /etc/login.conf did. Now it works flawlessly. Thank you! Is there any resource where these cases covered (Cannot allocate memory and disabling IOMMU because of erratas)? Just want to know bloody details. And one more question, am I right that PV-guests are no more supported in FreeBSD? We tried to run Debian guest in PV mode like described here: http://wiki.xen.org/wiki/FreeBSD_Dom0#Creating_your_first_PV_guest but guest's kernel panicking like that: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? This is FreeBSD HVM attempt: libxl: error: libxl_dm.c:1482:device_model_spawn_outcome: domain 5 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1319:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1586:kill_device_model: Device Model already exited Full log: http://dpaste.com/0499WH8 -- Regards, Ruslan T.O.S. Of Reality ___ 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: [solved] iommu must be enabled for PVH hardware domain
Roger Pau Monné wrote on 05/13/15 13:44: I don't thinks there's any generic resource about this issues, your best bet is to google for them, this is for example the patch related to that hw errata: http://lists.xen.org/archives/html/xen-devel/2013-01/msg01016.html It contains a link to the Intel SDM that has more info about the erratas. Thanks! Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? Can you paste the DomU configuration file (debian.cfg)? Here it is: https://dpaste.de/wneF/raw This is FreeBSD HVM attempt: Can you run the same command with xl -vvv instead (it will print more http://dpaste.com/2AGRN13 verbose debug info)? Also, can you paste the contents of /var/log/xen/qemu-dm-freebsd.log? Roger. This log-file contains only one line: VNC support is disabled -- Regards, Ruslan T.O.S. Of Reality ___ 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: [solved] iommu must be enabled for PVH hardware domain
El 13/05/15 a les 13.40, Ruslan Makhmatkhanov ha escrit: Roger Pau Monné wrote on 05/13/15 14:21: El 13/05/15 a les 13.12, Ruslan Makhmatkhanov ha escrit: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Full log: http://dpaste.com/2GZTJMH Or it's some bad zfs setup on dom0 system? Can you paste the DomU configuration file (debian.cfg)? Here it is: https://dpaste.de/wneF/raw This is weird, I don't see anything obviously wrong. Could you try to increase the DomU memory to 512Mb and boot again? Yes, it is helped. So 512Mb is the minimal RAM quantity? No idea, you can try with 256 also, maybe that's enough? It looks like 128 isn't, but that's a debian issue unrelated to FreeBSD. Roger. ___ 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
