I'm trying to do a macos vm with gpu passthrough with virt-manager, but everytime I run my vm with my GPU, libvirtd totally freeze.
If anyone got an idea about this topic, that could be nice :)
I followed this tutorial : https://www.youtube.com/watch?v=eTX10QlFJ6c
I cannot restart libvirtd service, access to qemu/kvm connection etc...
I set in virt-manager my gpu via pci passthrough, my bios rom, set my keyboard and mouse
When I start my vm, nothing happen except in logs
sudo tail -f /var/log/libvirt/libvirtd.log
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6697 : Create domain masterKey
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6701 : Setting up storage
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6705 : Setting up host devices
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6709 : Prepare chardev source backends
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6713 : Prepare device secrets
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6717 : Prepare bios/uefi paths
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6723 : Preparing external devices
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6728 : Aligning guest memory
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6742 : Preparing monitor state
2022-12-13 21:24:09.901+0000: 616: debug : qemuProcessPrepareDomain:6751 : Updating guest CPU definition
2022-12-13 21:24:09.923+0000: 616: debug : qemuProcessPrepareHost:7184 : Preparing network devices
2022-12-13 21:24:09.923+0000: 616: debug : qemuProcessPrepareHost:7189 : Preparing host devices
And then get stuck here, nothing else happen
Related
I know this isn't the right place to ask this but this site has the most users on it. I recently bought a Kemp LoadMaster LM-2600 Load Balancer for my webservers. However, this unit didn't include an SSD because the previous owner decided to erase it. So, I downloaded the VirtualBox version of free VLM from kemp's website. Then, I used VBoxManage clonehd LMOS.vmdk LMOS.img --format RAW to turn the disk into a raw img file. Then, I used dd if=LMOS.img of=/dev/sdb to flash a USB with the os. Then, I booted my loadmaster with the USB.
The boot process went like normal until it finished booting and then the machine switched to runlevel 0 (Shutdown)
This is the logs I got when I plugged the USB into my computer (The log file was so big that stack overflow won't allow me to paste it here):
https://pastebin.com/5PbKzRi6
I noticed that it said something about eth0 being down so I plugged in an ethernet cable and booted it again. The same thing happened but I got a different error (The log was shorter so I labeled it):
-- BOOT --
2022-08-07T19:50:06+00:00 lb100 syslog-ng: syslog-ng starting up; version='3.25.1'
-- ERROR --
2022-08-07T19:50:07+00:00 lb100 raid_events_handler: RAID controller not detected yet (check # 0)
-- LOGIN --
2022-08-07T19:50:11+00:00 lb100 login: pam_unix(login:session): session opened for user bal by LOGIN(uid=0)
-- ERROR --
2022-08-07T19:50:14+00:00 lb100 raid_events_handler: RAID controller not detected yet (check # 1)
-- SHUTDOWN --
2022-08-07T19:50:15+00:00 lb100 init: Switching to runlevel: 0
2022-08-07T19:50:15+00:00 lb100 kernel: S99final (938): drop_caches: 1
2022-08-07T19:50:17+00:00 lb100 syslog-ng: syslog-ng shutting down; version='3.25.1'
2022-08-07T19:50:17+00:00 lb100 kernel: Kernel logging (proc) stopped.
2022-08-07T19:50:17+00:00 lb100 kernel: Kernel log daemon terminating.
2022-08-07T19:50:17+00:00 lb100 sslproxy: (815) caught signal 15
2022-08-07T19:50:17+00:00 lb100 raid_events_handler: stop
I have no idea what to do right now. I already tried everything I knew. What should I do?
Any help would be great,
Thanks!
i am trying to create high-level app based on IntercoreComms samples from azsure-sphere-samples, the high level sample code itself it's working w/o issue on my mt3620 dev board, but when i try to add my code on top of it and run it, there is error message as below from high-level app.
ERROR: Unable to create socket: 13 (Permission denied)
and, the error message from RTApp is as below.
TargetName Type Endian TapName State
0* io0 cortex_m little mt3620.cpu unknown
Info : Listening on port 6666 for tcl connections
Info : Listening on port 23 for telnet connections
Info : clock speed 4800 kHz
Info : SWD DPIDR 0x3ba02477
Info : io0: hardware has 6 breakpoints, 4 watchpoints
Info : io0: external reset detected
Info : Listening on port 4444 for gdb connections
Info : accepting 'gdb' connection on tcp/4444
target halted due to debug-request, current mode: Thread
xPSR: 0x61000000 pc: 0x001008ea msp: 0x0012fb90
Warn : target io0 is not halted (gdb fileio)
Polling target io0 failed, trying to reexamine
Info : SWD DPIDR 0x3ba02477
Info : SWD DPIDR 0x3ba02477
Info : SWD DPIDR 0x3ba02477
Info : SWD DPIDR 0x3ba02477
Info : SWD DPIDR 0x3ba02477
To give permission for your high-level app to talk to your real-time app, and vice versa, the "AllowedApplicationConnections" field of the app_manifest.json for each app must contain the component ID of the other app. See here for details. The "ComponentId" is itself a field in the app manfiest: your new app(s) likely have different IDs to the sample apps.
Also, if you are deploying through Visual Studio (Code), you need to declare each app as a 'partner' of the other so one is not deleted when the other is deployed. See here for details of that. The RT app error that you see may come from it being deleted when the high-level app is deployed.
Using Bluez 5.37 bluetoothd. I compile my with flag --disable-systemd.
Using bluetoothctl to connect to my local bluetooth server.
After connecting it does not show any services on dbus.
I can see the following error in bluetoothd log:
bluetoothd[22098]: src/device.c:gatt_debug() start: 0x0001, end: 0x0004, uuid: 00001801-0000-1000-8000-00805f9b34fb
bluetoothd[22098]: src/device.c:gatt_debug() start: 0x0010, end: 0x0015, uuid: 00001827-0000-1000-8000-00805f9b34fb
bluetoothd[22098]: src/device.c:gatt_client_ready_cb() status: success, error: 10
bluetoothd[22098]: src/device.c:device_svc_resolved() /org/bluez/hci0/dev_XX_XX_XX_XX_BA_8F err 0
bluetoothd[22098]: src/gatt-client.c:btd_gatt_client_ready() GATT client ready
bluetoothd[22098]: src/gatt-client.c:create_services() Exporting objects for GATT services: XX:XX:XX:XX:BA:8F
bluetoothd[22098]: Unable to register GATT service with handle 0x0001 for device XX:XX:XX:XX:BA:8F
bluetoothd[22098]: Unable to register GATT service with handle 0x0010 for device XX:XX:XX:XX:BA:8F
On dbus I cannot see any service or characteristics populated. I need to use bluez 5.37, is there any fix for this?
Note: I have masked bd address as XX:XX:XX:XX:BA:8F
This was basically unable to register the objects on dbus interface.
Resolved this by running bluetoothd in "experimental" mode using "E" flag.
like:
./bluetoothd -ndE
I have a EAR which after deploying into WAS 8.5 looks fine. But after accessing for few minutes, the server restarts automatically. The exception captured captured in native_stdout shows the log as below:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0xa) at pc=0x001ffffeff3e6ea0, pid=15451, tid=239
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# C [libc.so.1+0xe6ea0]# [ timer expired, abort... ]
[7/13/17 18:32:28:111 SGT] 00000001 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
[7/13/17 18:32:28:520 SGT] 00000001 ManagerAdmin A TRAS0007I: Logging to the service log is disabled
[7/13/17 18:32:28:731 SGT] 00000001 ProviderTrack I com.ibm.ffdc.osgi.ProviderTracker AddingService FFDC1007I: FFDC Provider Installed:
The same application works fine in other environment. Thanks in advance for any help on identifying the problem.
I'm trying to boot VxWorks 6.3 on a Wind River SBC83XX PowerQUICC II Pro. I'm using Wind River Workbench as my IDE. I configured the kernel, built it, and attempted to run it, but it hangs on Starting at 0x100000 with no further output.
Here is the output of the terminal after typing # at the prompt:
boot device : mottsec
unit number : 0
processor number : 0
host name : XXXXXXXXXXX
file name : C:\WindRiver\workspace\vxworks-dev\default\vxWorks
inet on ethernet (e) : 69.88.163.22:ffffff00
host inet (h) : 69.88.163.21
gateway inet (g) : 69.88.163.1
user (u) : XXXXXXXXX
ftp password (pw) : XXXXXXXX
flags (f) : 0x0
Attaching interface lo0... done
Attached IPv4 interface to mottsec unit 0
Loading... 1838288
Starting at 0x100000...
Any suggestions would be greatly appreciated; I need this working for a college class on a tight schedule.
Many things could be wrong.
The first thing I would do is check the RAM size. If it exceed the amount on the board, this might happen.
Is the serial port & shell configured? I would suggest adding the standalone shell bundle.
If the symbol table is compiled as standalone, this can sometimes occur based on other configurations.
Compile the symbol table into the image.
In Work Bench:
Kernel Configuration -> CTRL+F, search "built-in symbol table", -> include it.