Tiny Core Extensions > TCE Corepure64

QEMU for 64bit?

<< < (6/10) > >>

flyingfishfinger:
Progress!
You're right, I shouldn't have zipped up the /home directory in the extension. I followed the directions for making one, and there was a QEMU-related file in the directory so I left it in.
Removed it, fixed permissions (755) and voila, no longer hangs on boot! I'm writing this from inside the VM, as it happens!

Always more questions though  ::) :
- Is there a spice client for TC? The graphics performance is kind of terrible, and I'd like to be able to start the VM on boot so I can just connect to it once the desktop shows up. I wrote this whole sentence before it appeared in the box, for example.
- There doesn't seem to be a cpufreq-util in the 64-bit category. Is that correct?
- I'm having trouble with my screen resolution, but that's probably a better question for a new thread.


R

Rich:
Hi flyingfishfinger

--- Quote --- ... I'd like to be able to start the VM on boot so I can just connect to it once the desktop shows up.
--- End quote ---
Create a file under  /home/tc/.X.d  containing the command to start QEMU. Something like:

--- Code: ---qemu-x86_64 options &
--- End code ---

Juanito:

--- Quote from: flyingfishfinger on February 08, 2016, 11:01:54 PM ---There doesn't seem to be a cpufreq-util in the 64-bit category.

--- End quote ---

That's true, but an element of cpufreq functionality is built into the base - Curaga can probably provide more details.

flyingfishfinger:
Rich: What's the difference between doing that and putting it bootsync?

Also, I found that this doesn't seem to work if you're using SDL. The machine will start before X, but I don't know how to connect to an SDL session after that.
What kind of VNC clients are there for corepure64? I didn't see any in the list.
In trying to build the spice client, spice-protocol, cyrus-sasl and vala-tools don't seem to exist. Will look into it further.

R

Juanito:

--- Quote from: flyingfishfinger on February 09, 2016, 12:17:35 AM ---What's the difference between doing that and putting it bootsync?

--- End quote ---

In ~/.X.d it will not start until after X has started.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version