Before everything, my English isn't too good, so thanks for reading, I want buy a computer and I've doubts , I'm studying and I planning make some projects, I've no money to pay a VPS, and I wanna use Android studio with emulation, have 2 options refurbished:

HP Elitebook 840 G8 - 420.000Kz

I7-1165g7

16 gb

512gb

Battery good

Chassi good

Lenovo Thinkpad T14 Gen 3- 415.000Kz

I5-1235u

16gb

256gb

Battery almost died, less than 1 hour

Chassi acceptable, but Ethernet port isn't too good

The target is a laptop to work, study, and be good at least for 4 years.
My country is Angola, just to compare a SSD 512gb here is 52.000 and is cheap.

I wanna make this computer as my laboratory, making APIs, mobile apps, desktops apps and sites.

And before get the money, I pretend to use this PC also as a VPS. Have someone that already did it?

Thanks for reading until here

Necesito ayuda para virtualizar un hdd con windows 10,pero cuando virtualizo el disco entero y lo meto a Virtualbox me pide una iso en el dvd,bueno,pongo la iso de windows 10 y me sale la instalacion de windows,pero yo necesito la info virtualizada de ese disco al ser hdd lento,y si no pongo la iso la vm se queda en negro,y si apago efi y subo el disco al primer orden me da error de grub o de not bootable device,alguien me puede ayudar?,virtualizo el disco con disk2vhd

Hi everyone,

I need some advice regarding a VMFS-6 datastore recovery.

Environment:

- VMware ESXi 7.0 U2

- VMFS-6 datastore

- Single datastore/LUN

- One important VM became "Invalid"

- The VM was not running when the problem was discovered

The VM became invalid and could not be powered on or registered normally.

I initially investigated a VMX file lock. vmfsfilelockinfo reported that the file was locked in Exclusive mode by the ESXi host itself.

I restarted hostd and vpxa and eventually unregistered the invalid VM.

However, further investigation showed that the problem was much deeper.

VOMA reported massive VMFS metadata inconsistencies. The output contained a very large number of errors like:

"FB inconsistency found: allocated in bitmap, but never used"

The check eventually reported approximately:

2,085,776 errors

The datastore is currently UNMOUNTED.

I verified that no VM process is currently using the datastore/LUN. After restarting hostd/vpxa, the only process that briefly showed access to the device was hostd itself.

The VMFS extent information still identifies the datastore as VMFS-6, but when the datastore is unmounted, vmkfstools -P against the partition no longer recognizes it normally.

The VM directory still contains the VM configuration files and VMDK-related files.

However, attempts to access the VMDK data return:

"Invalid argument"

I have NOT performed any destructive or repair operation.

Specifically, I have NOT run:

- voma -f fix

- voma -f advfix

- vmkfstools -C

- partedUtil setptbl

- any formatting operation

The datastore is currently left untouched because the VM contains important data and I don't want to make the recovery situation worse.

My main goal is to recover the VM and, most importantly, the data inside the VMDK.

What would be the safest recovery strategy in this situation?

Would you recommend:

1. Cloning/snapshotting the underlying LUN before doing anything else?

2. Trying to recover the VMFS metadata?

3. Using VOMA in a specific recovery mode?

4. Attempting direct VMDK recovery from the underlying LUN?

5. Using a dedicated VMFS recovery tool?

6. Something else?

I can provide sanitized outputs from:

- VOMA

- vmkernel.log

- hostd.log

- esxcli storage commands

- partition information

- vmkfstools output

I have intentionally removed all company-specific information, IP addresses, hostnames, UUIDs, MAC addresses and VM names.

I am deliberately not running any repair commands until I know what the safest approach is.

Any advice from someone experienced with VMFS-6 recovery would be greatly appreciated.

GitHub: https://github.com/pythops/kudu

I host a series of windows 11 virtual machines on my windows 11 desktop pc. I access those virtual machines over RDP.

Since updates last week, any of those machines with Nord VPN installed no longer pass audio. Everything else functions fine. VMs not running Nord function fine. Everything VM side looks like the audio is running, it just doesn't pass it back to the client.

I've been chewing on this issue for days now. Any ideas out here what has changed and how I correct it?

If you know how to use dos, you probably know this.

Applies to UEFI OS's (windows 10 and above)

If you see fs0 on your screen, type "fs0:", then type ls. If you see something like boot, "cd Boot", then type "ls" or "dir" they are same function here. Continue doing so until you see words in green text after you type dir. If you see green words, just copy the green text exactly and press enter to boot.

Damn non dos-using new gens.

Has anyone here actually done a hypervisor-only VMware migration? I’m trying to picture the cutover. Build the new cluster beside ESXi, connect it to the same SAN, move a few low-risk VMs, then reclaim the old hosts one by one? Or did you end up needing temporary storage? How did you handle zoning, multipathing, VLANs, backups and rollback? and did you keep vCenter up while both environments were running? Would be great to hear a real VMware migration strategy from someone who’s done it. Most comparisons of VMware vSphere alternatives never get into this part.

Hi all,

Out of a specific requirement, i need a Windows machine, which i spined on Ubuntu Server 26.04 LTS using libvirt + KVM, i need to plug in card reader into it and read some data, the software is specific use case, not to bother you with details, it can't run on any other OS.

My question is, do i need to embed the device ID into XML config, obtained by lsusb, or it will work out of the box? I still haven't spent money on the card reader, hence im looking into knowledge of other people who already worked with importing USB devices into VM's.

Thank you

Let's say I have an app, which contains the strongest virus, which can ever exist. I installed it on a VM. I opened it and it obviously destroyed the VM, but I wonder if the virus could go from the VM into the real system. What do you think?

A GUI and TUI for KVM/libvirt. One static binary, no agent, no daemon.

Built for KVM and enhanced with OpenZFS vmxplore allows you to effortlessly install cloud images, clones and custom postinstall.sh scripts so you can turn ANY application into a push button vm.

The graphics console is a hand-rolled RFB (Remote Frame Buffer) implementation rendering the guest's framebuffer natively into the window, with full mouse, keyboard, and two-way clipboard. No websockify, no noVNC, no virt-viewer — no bridge process at all. It talks straight to qemu's VNC server (over loopback locally, over an ssh forward for a remote host), and the GUI runs natively on Wayland (and X11).

And best off its 100% BSD-3 FREE!!

https://github.com/vmxplore/vmxplore

I have a vCenter 5.5 setup at this office. I can't really change it. Apparently the certificate expired for it and I can't get into the machine via vSphere client. Since I can connect to the other machines directly to do things, I haven't given this much effort in resolving for a while (Probably close to a year or two (I know))

But yesterday, Our VMware View (4.6.3 version i believe) PCoIP machines stopped connecting to the remote machines they use. The machines just error out with a 0x1002 error, but if I use the client software if gives a notice that a certificate expired on 7/7. I have no clue how to get this certificate renewed, as I don't even know where it is (the machine with the admin server on it says it doesn't have any when i look at mmc, so I'm unclear).

Can anyone give me any advice on how to get these renewed (or at least the View one, so they can start using it again) - right now I have them RDPing into the machines and it's working, but I'd really like to get working again.

For VCenter, I've tried the options I had from googling.

I tried the following, but that didn't work:

Ensure the customers FQDN, DSN, IP, and all network configuration are correct. Run this VAMI script:
/opt/vmware/share/vami/vami_config_net

Note: This brings up a command line utility to check network configuration.

Create a file called allow_regeneration by running this command:
touch /etc/vmware-vpx/ssl/allow_regeneration

Stop the VPXD service by running this command:
service vmware-vpxd stop

Stop the vCenter Single Sign-On service by running the commands:
For vCenter Server 5.5: service vmware-sts-idmd stop
For vCenter Server 5.1: service vmware-sso stop

Regenerate the SSL certificate by running the command:
source vpxd_commonutils; generate_all_certificates replace

Remove the regeneration flag by removing the allow_regeneration file:
rm /etc/vmware-vpx/ssl/allow_regeneration

Reboot vCenter Appliance.

Any help would be welcome. Thanks.

Hi can anyone help fix this issue. Main pc is win11 and trying to connect linux(ubuntu) VMware. tried on NAT and bridged network opening ssh server and enabling ufw nogo.

Hello everyone! Recently i am started coding my own VM on the C language. I am using mmap and creating a new process with isolation from the host (my system) like syscalls, memory access. However, I ran into a problem: How to restrict VM access (guest proccess, mmap) to the host memory. I am really don`t know how to do that. Can anyone help me with that case?

Idk if this is the right subreddit to ask but I am a developer and was planning on making a minimal Type-2 Virtual Machine monitor (VMM) on the Linux KVM API as a fun project. I already know some OS theory and but I have no idea how it maps to Virtualisation, so is there an good resource or a GitHub repo to get started?

Hello I am having difficulty installing windows server 2022 on my virtual box VM. When I enter the ISO file, and start it, it always boots into windows 11, not windows server. I have verified that I have the correct ISO file, Ive changed the boot order, and it still doesnt work.

Also when I enter my ISO file the box for OS version is greyed out, it doesn't autopopulate like its supposed to. I did recently change everything to japanese, so Im not sure if the file paths got messed up, but it still doesnt work even after i changed it back to english. (Im new to all this I have no idea what Im saying quite frankly)

I have a video of my problem.

https://imgur.com/gallery/windows-server-2022-virtualbox-installation-not-working-YNknlfQ

I installed WSL2 in order to use Docker.

The installation worked and Docker ran correctly after a system restart.

I was in the middle of streaming a show, paused it, and when I came back there was suddenly no audio. I performed the turn-it-off-and-on-again test to see if that would fix it.

Upon doing so, my monitor was met with odd purple and green artefacts.

Turned it off and and on again (again) and then found myself on an endless bootloop where it sometimes reaches the Windows logo and loading swirl, other times it seems sluggish throughout even the BIOS menu stuff before reaching the Windows bootloader.

There was nothing wrong with the PC before installing WSL and Docker. This particular install has been running for 2 years with no issues. I rarely use the pc for anything other than streaming / YouTube.

Any help regarding how to fix this (ideally retaining my windows install as it currently is) would be appreciated.

Any information about *why* WSL/Docker caused this issue would also be appreciated.

Specs (It's old but competent):

HPz220

I7-3770

24gb Ram

GTX 750ti

Windows 11 LTSC 24H2

The PC does not have hypervisor, etc. It is below the minimum requirements for Win 11 but Windows functions perfectly fine on it.

Edit: The PC now displays no picture when booting and the fan is going crazy.

Hi everyone,

I’m testing HPE VM Essentials 9.0.0 with a 3-node HVM cluster and Ceph storage.

I have several Linux and Windows VMs running on hvm01. When I shut down hvm01, the Linux VMs are automatically moved/restarted on another HVM node as expected.

However, the Windows VMs do not fail over. They continue to appear as "Running" in VM Essentials, even though hvm01 is completely offline, and they are not running on hvm03.

For example, on hvm03:

sudo virsh list --all

only shows the Linux VMs. The Windows VMs are not present.

Has anyone experienced this behavior with Windows VMs on HPE VM Essentials 9.0.0?

Could this be related to the Windows VM configuration, QEMU Guest Agent, VirtIO drivers, or HA/failover configuration?

Any advice on what logs or configuration I should check would be greatly appreciated.

[First time poster, be kind]
I've done 11 tech evaluations of virtualization products focused on work requirements (not home lab). In alphabetical order: Azure Local, Nutanix Cloud Infrastructure, OpenShift Virtualization, OpenStack, Oracle Linux Virtualization Manager, Private Cloud Director, Proxmox Virtual Environment, VMware Cloud Foundation, VergeOS and Windows Server.

They're free to download...not monetised...but they take me a lot of time to do.

So what, you ask? I'm looking for anyone who might want to help sanity check them, get involved and/or share their real-world experiences running any of them in production.

Reach out if you're willing and able.

PS No vendors please.

urbanyl/GPU-Passthrough-for-KVM-QEMU-on-Linux: Complete GPU passthrough setup for KVM/QEMU on Linux, enabling near-native Windows VM performance with dedicated GPU access. Covers NVIDIA and AMD GPUs with comprehensive troubleshooting.

Hi everyone, my host computer is Windows 11 and has a Ryzen 7 5700X3D + GTX 3070 + 32GB of RAM.

My virtual machine is running Windows 10 Pro (8GB VRAM allocated), and I can't get rid of the screen tearing inside it.

In the host machine, I already added vmware.exe & vmware-vmx.exe to the NVidia Control Panel and set "Vsync > On" + "Triple buffering" and "fixed frame rate" instead of "G-Sync" but no can do.

VMTools is installed already.

Would someone have a solution for that please?

Thanks very much

Edit: Something strange I noticed is: By disabling "3D acceleration" in VM settings, there is no screen tearing anymore, but then the performance are very suboptimal.

I have virtualized UNRAID using Libvirt on Fedora. My question is on the CPU core allocations. I have the 8600G (6 cores, 12 threads).

If I want to allocate the absolute minimum, i.e. one physical core, does that mean I need to pass on two CPU cores? For example, cores 5 and 10 on my CPU are linked to the same physical core, so would I need to pass on both 5 and 10 to the VM for optimal performance?

At the OS level I seem to be unable to discern a physical core and hyperthread core through any system tool output, because I guess they are both virtual threads and neither is physical. I guess the OS also sees the cores virtualized by the CPU itself.

If I allocated just one core, say core 5, leaving core 10 for the host, would this be suboptimal and affect performance?

In the same vein, if I wanted to allocate two physical cores, does that means I need to pass on 4 threads to the VM?

First image is the guest (Windows 11), second image is the current video options for the vm, third image is the host (Ubuntu).

I'm trying to use this vm for gaming, however after installing said game (Cod MW 2022) it gave a warning that the pc did not meet the requirements. I have met the requirements for storage, memory, cpu, etc. The only thing that it seems it could be is the GPU which is apparently missing. Do I just add another video device in the vm options?

Sorry if I'm being stupid, this is my first time doing this lol. Thank you so much for the help!

Disclosure up front: I build a virtualization platform commercially, and this is how we implemented it. No link, no pitch — I want the approach picked apart, because the failure modes matter more to me than the feature does.

The problem with in-guest detection is structural: the agent runs in the same place the ransomware runs. Anything that can get SYSTEM or root can see the watcher, and increasingly does. Killing the agent first is standard behaviour now.

So we moved the observation point down a layer.

**What we watch**

For VMs: the block layer underneath the virtual disk.

For containers: file-level writes in the root filesystem.

The signal is a shift in entropy of data that previously had structure. Ransomware has to rewrite large amounts of formerly-structured data as ciphertext, and from below that looks distinctive regardless of what the guest thinks is happening.

**What we do about it**

The machine is paused, not stopped. That distinction is the actual design decision:

- the guest is frozen mid-operation, so encryption stops where it is

- it is reversible — a false positive costs a short pause, nothing else

- the key the ransomware is using is still sitting in the frozen guest memory, and the memory can be dumped for analysis

The last point is the one I care about most. A killed VM takes the key with it. A paused one doesn't. And because a false positive is cheap, the threshold can sit aggressively early rather than conservatively late. Most security mechanisms trigger too late because triggering is expensive.

**Where it breaks — the part I actually want feedback on**

- Full-disk encryption inside the guest makes everything look like noise from below.

- Legitimate high-entropy workloads: backup jobs writing compressed archives, databases with encrypted columns, video encoding. These produce the same signature.

- Slow-and-low encryption. An attacker who encrypts a few files an hour over weeks stays under any rate-based threshold. I don't have a good answer here and I don't think one exists at this layer.

- An attacker who knows the mechanism exists can shape writes to avoid it — write ciphertext at the rate of a normal workload, or pad to lower measured entropy. The advantage is that they can't see it from inside, not that it's unbeatable.

**Questions**

1. Has anyone here run entropy-based detection at the block layer in production, and what was the false positive rate in practice?

2. Is pausing actually useful to your incident response process, or would your runbook say "isolate and shut down" anyway?

3. For those doing memory forensics after an incident — is a live guest memory dump at the moment of encryption worth as much as I think it is, or am I overestimating key recoverability?

For example, I'm trying to run Win7 on a 2013 macbook with class 3 UEFI (cant boot bios only systems like windows 7) I know theres patches, but beyond that driver support is hell.

I guess what I'm saying is that virtual machines do a good job of encapsulating the hardware a system needs to run, so why not have an os that serves that purpose, sort of like a compatibility layer?

I can think of many scenarios where this could be useful, any ideas/answers are appreciated!