-
OK folks so here is the skinny on this.
UPDATE TO POWER KEYS..
In order to remove confusion of what TV supports what power keys.
I have decided to alter the Samsung handling of keys. The way Sams…
-
## Describe the bug
I encounter this error while I try to list the backup page
`error listing backup volume names: timeout executing: /var/lib/longhorn/engine-binaries/longhornio-longhorn-engin…
-
## Question
source node backup one VM machine to target node, NFS error
my test like this
source 10.64.9.41
target 10.64.41.10
nfs storge: 10.64.50.254
first ,i backup one VM machine on the …
-
## Describe the bug
Adding s3 backup target and the secret, still give an error message in the backup tab in the UI
## To Reproduce
1. Install k3s on a single node, with longhorn
2. Create a…
-
## Expected Behavior
When downloading a test file (https://nbg1-speed.hetzner.com/10GB.bin), both WAN connections, DSL (100 Mbps) and STARLINK (50-200 Mbps) should be used.
## Current Behavior
Op…
-
### System information
Type | Version/Name
--- | ---
Distribution Name | Arch
Distribution Version | Current
Linux Kernel | 5.4.84
Architecture | x64
ZFS Version | 2.0
### Descr…
-
ISSUE TYPE
BUG
Component Name
Volume,
CLOUDSTACK VERSION
Cloudstack version 4.18, 4.19
SUMMARY
Unable to attach a raw format volume to an instance running on KVM
Ste…
-
## Describe the bug
Run test case `test_recurring_job_restored_from_backup_target[nfs]`. It's possible to encounter backup creation failed with error message:
```
error: 'proxyServer=10.42.2.10…
-
Docs: https://bisq.wiki/Support_Agent
Team: @bisq-network/l1-support-agents
-
## Steps
1. Create a VM in namespace `default`.
2. Create some test data and it's checksum.
3. Backup VM as `default-vm-backup`.
4. Create a new namepsace `new-ns`.
5. Restore `default-vm-backup`…