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
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
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)?
>
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 Int
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 bec
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
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.
[...
[1]
The system is FreeBSD 11.0-CURRENT r282694 installed from
ftp.freebsd.org iso.
But dom0 fails to boot at this hardware with "iommu must be enabled for
PVH hardware domain" [2]. VT-d support is indeed not detected at kernel
level. Here is dmesg with VT-d enabled in BIOS [3] and dmesg
:
>>> Intel(R) Xeon(R) CPU E5504 [1]
>>>
>>> The system is FreeBSD 11.0-CURRENT r282694 installed from
>>> ftp.freebsd.org iso.
>>>
>>> But dom0 fails to boot at this hardware with "iommu must be enabled for
>>> PVH hardware domain"
at this hardware with "iommu must be enabled for
PVH hardware domain" [2]. VT-d support is indeed not detected at kernel
level. Here is dmesg with VT-d enabled in BIOS [3] and dmesg with VT-d
disabled in BIOS [4]. It's look like there is no difference on both
outputs. Here is the p
at this hardware with "iommu must be enabled for
PVH hardware domain" [2]. VT-d support is indeed not detected at kernel
level. Here is dmesg with VT-d enabled in BIOS [3] and dmesg with VT-d
disabled in BIOS [4]. It's look like there is no difference on both
outputs. Here is the p
boot at this hardware with "iommu must be enabled for
> PVH hardware domain" [2]. VT-d support is indeed not detected at kernel
> level. Here is dmesg with VT-d enabled in BIOS [3] and dmesg with VT-d
> disabled in BIOS [4]. It's look like there is no difference on both
> ou
Hello,
we have machine with VT-d and EPT-capable CPU:
Intel(R) Xeon(R) CPU E5504 [1]
The system is FreeBSD 11.0-CURRENT r282694 installed from
ftp.freebsd.org iso.
But dom0 fails to boot at this hardware with "iommu must be enabled for
PVH hardware domain" [2]. VT-d support is
13 matches
Mail list logo
