Hello,
I have downloaded, built, and begun testing Sculpt EA, following the instructions linked to in the 18.02 release notes. Everything went well during the build process.
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible. It booted fine from a virtual CD, the system came up using the VESA framebuffer driver, the mouse worked, and I was able to follow the instructions until I got to the part about storage. Unfortunately, there are no "<device>" nodes under "<block_devices>" in "/report/drivers/block_devices".
I have the VM set up with a "SATA" controller and a single virtual drive. Has anyone tried this? Do you have any hints on how to diagnose what is going wrong?
Also, I modified the config to use wired networking (using a virtual Intel-based NIC), but I couldn't think of a way to easily test whether it is working or not. (I'm sure I'm missing something obvious here, but I appreciate any hints.)
If I can get those two items working, it looks like I'll be in good shape!
Thanks,
Actually, while the problems at SourceForge were delaying the mailing list, I solved part of my problem. Details below...
On 03/01/2018 11:14 PM, John J. Karcher wrote:
Hello,
I have downloaded, built, and begun testing Sculpt EA, following the instructions linked to in the 18.02 release notes. Everything went well during the build process.
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible. It booted fine from a virtual CD, the system came up using the VESA framebuffer driver, the mouse worked, and I was able to follow the instructions until I got to the part about storage. Unfortunately, there are no "<device>" nodes under "<block_devices>" in "/report/drivers/block_devices".
I have the VM set up with a "SATA" controller and a single virtual drive. Has anyone tried this? Do you have any hints on how to diagnose what is going wrong?
Once I switched the "Chipset" setting to "ICH9", it found the drive, and I was able to continue.
Also, I modified the config to use wired networking (using a virtual Intel-based NIC), but I couldn't think of a way to easily test whether it is working or not. (I'm sure I'm missing something obvious here, but I appreciate any hints.)
Unfortunately, I am not having luck with the network card. I have tried all of the available Adapter Types, but none of them work. I get messages in "/report/log" like these:
For Intel 82540EM:
[runtimne -> nic -> nic] Found 00:3.0 8086:100e (rev 02) IRQ 09 [runtimne -> nic -> nic] using driver 82540em [runtimne -> nic -> nic] PCI BIOS has not enabled device 00:3.0! Updating PCI command 0003->0007 [drivers -> platform_drv] Error: runtimne -> nic -> nic: assignment of PCI device 0:3.0 failed phys=0xdc018000 virt=0x1000 [runtimne -> nic -> nic] PCI device 00:3.0 latency timer is unreasonably low at 0. Setting to 32. [runtimne -> nic -> nic] bus_addr = e2000000 len = 20000 ... [runtimne -> nic -> nic] snprintf not implemented [drivers -> platform_drv] IRQ override 9->9 trigger mode: LEVEL, polarity: LOW [drivers -> platform_drv] 0:3.0 uses IRQ, vector 0x9, non-maskable
For Intel 82543GC (all the same, except):
[runtimne -> nic -> nic] Found 00:3.0 8086:100e (rev 02) IRQ 09 [runtimne -> nic -> nic] using driver 82543gc
For Intel 82545EM (all the same, except):
[runtimne -> nic -> nic] Found 00:11.0 8086:100f (rev 02) IRQ 0b [runtimne -> nic -> nic] using driver 82545em [runtimne -> nic -> nic] PCI BIOS has not enabled device 00:11.0! Updating PCI command 0003->0007 [drivers -> platform_drv] Error: runtimne -> nic -> nic: assignment of PCI device 0:11.0 failed phys=0xdc088000 virt=0x1000 ... [runtimne -> nic -> nic] bus_addr = e2420000 len = 20000 ... [drivers -> platform_drv] 0:11.0 uses IRQ, vector 0xb, non-maskable
FWIW, VirtualBox doesn't seem to give any way of tweaking things at the IRQ level.
This is closer to the hardware than I usually get these days. Is there anything I can try?
Thanks!
Hi,
On 04.03.2018 08:22, John J. Karcher wrote:
Actually, while the problems at SourceForge were delaying the mailing list, I solved part of my problem. Details below...
On 03/01/2018 11:14 PM, John J. Karcher wrote:
Hello,
I have downloaded, built, and begun testing Sculpt EA, following the instructions linked to in the 18.02 release notes. Everything went well during the build process.
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible.
It will work until the point where you try to start a VM in Sculpt, which will not run because VirtualBox don't support nested virtualization.
[drivers -> platform_drv] Error: runtimne -> nic -> nic: assignment of PCI device 0:11.0 failed phys=0xdc088000 virt=0x1000
This is a normal message if you have no IOMMU support, which virtualbox doesn't provide to guests. You may just ignore (and we have to silence the output in the future.)
... [runtimne -> nic -> nic] bus_addr = e2420000 len = 20000 ... [drivers -> platform_drv] 0:11.0 uses IRQ, vector 0xb, non-maskable
This is closer to the hardware than I usually get these days. Is there anything I can try?
It sounds like the issue reported in https://github.com/genodelabs/genode/issues/1044 - unfortunately there has been no solution for ICH9 and network, but a quirk for PCIIX3 and network exists. Maybe you can report there your findings, if you have some news.
Cheers,
On 03/05/2018 08:05 AM, Alexander Boettcher wrote:
Hi,
On 04.03.2018 08:22, John J. Karcher wrote:
Actually, while the problems at SourceForge were delaying the mailing list, I solved part of my problem. Details below...
On 03/01/2018 11:14 PM, John J. Karcher wrote:
Hello,
I have downloaded, built, and begun testing Sculpt EA, following the instructions linked to in the 18.02 release notes. Everything went well during the build process.
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible.
It will work until the point where you try to start a VM in Sculpt, which will not run because VirtualBox don't support nested virtualization.
That's all I need! Could you send me the configuration for a working VM? My virtual SATA drive is not recognized if using PIIX3. ("VBoxManage showvminfo" is verbose, but we don't have to worry about missing anytihng.)
[drivers -> platform_drv] Error: runtimne -> nic -> nic: assignment of PCI device 0:11.0 failed phys=0xdc088000 virt=0x1000
This is a normal message if you have no IOMMU support, which virtualbox doesn't provide to guests. You may just ignore (and we have to silence the output in the future.)
That's good to know.
... [runtimne -> nic -> nic] bus_addr = e2420000 len = 20000 ... [drivers -> platform_drv] 0:11.0 uses IRQ, vector 0xb, non-maskable
This is closer to the hardware than I usually get these days. Is there anything I can try?
It sounds like the issue reported in https://github.com/genodelabs/genode/issues/1044 - unfortunately there has been no solution for ICH9 and network, but a quirk for PCIIX3 and network exists. Maybe you can report there your findings, if you have some news.
Interesting. The log output of "download.config" doesn't contain the network-related errors when using PIIX3 - hopefully that's a good sign. (Without storage, I can't tell if it actually works, of course.)
Thanks!
On 05.03.2018 17:07, John J. Karcher wrote:
On 03/05/2018 08:05 AM, Alexander Boettcher wrote:
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible.
It will work until the point where you try to start a VM in Sculpt, which will not run because VirtualBox don't support nested virtualization.
That's all I need! Could you send me the configuration for a working VM?Â
Sorry, you got me wrong, I haven't a working configuration. I just noted that even if you get Sculpt running in a VM, it will be limited in use.
On 03/05/2018 02:48 PM, Alexander Boettcher wrote:
On 05.03.2018 17:07, John J. Karcher wrote:
On 03/05/2018 08:05 AM, Alexander Boettcher wrote:
Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible.
It will work until the point where you try to start a VM in Sculpt, which will not run because VirtualBox don't support nested virtualization.
That's all I need! Could you send me the configuration for a working VM?
Sorry, you got me wrong, I haven't a working configuration. I just noted that even if you get Sculpt running in a VM, it will be limited in use.
Sorry about that.
Is there anything I can try to get this running (either networking with ICH9, or storage with PIIX3)?
I don't mind trying hard-coded values in drivers, or something like that.
-
Alexander Boettcher -
John J. Karcher