fqiao

Joined 7 months ago

Karma

27

Submissions

22

Member since

Apr 4

View on Hacker News

Recent submissions

RestockAlerts: The easiest way to score coveted Hermes handbags restockalerts.com

1 fqiao 4 months ago 0 comments

Comment · 6 months ago

So we originally just wanted the vm to be light-weight and can start fast, so we removed docker. @binsquare has a change later to add docker back.

Comment · 6 months ago

Let us know your thoughts! Thanks

Comment · 6 months ago

yah, i guess everybody share the experience of "i messed up with my dev env" right? We want this "machine" to be shippable, meaning that once it is configured correctly, it can be shared to anyone and use right away.

Comment · 6 months ago

No worry at all! Thanks!

Comment · 6 months ago

Thanks so much! Feel free to try it out if you have a chance, and let's us know your thoughts. Thanks!

Comment · 6 months ago

Hey thanks so much for the feedback. Yah try it and let us know. We have a discord if you want to join, but either github or discord feel free to report any issues you find to us.

Cheers!

Comment · 6 months ago

Thanks so much for the feedbacks. Yes these are valid concerns around libkrun security, We are planning and developing features around them actually, and hopefully that could alleviate the conerns.

for virtio-fs, yes the risk of exposing the host fs struture exists, and we plan to:

1. creating staging directory for each vm and bind-mount the host dir onto them

2. having private mount namespaces for vms

they are both tracked in our github issues:

https://github.com/smol-machines/smolvm/issues/152 https://github.com/smol-machines/smolvm/issues/151

2 may need much more efforts than we imagine, but we will ensure to call this out in our doc.

For the concern around TSI, we are developing virtio-net in-parallel, it is also tracked in our github and will be released soon: https://github.com/smol-machines/smolvm/issues/91

Would like to collect mroe suggestions on how to make this safer. Thanks!

Comment · 6 months ago

I came across SmolBSD before too. Cool project!

Comment · 6 months ago

I see. so right now smolvm can be stopped, and then "packed" (think of it as compressed), and restart on a different host. files in the disks are preserved, but memory snapshotting is still hard tbh

Comment · 6 months ago

we will evaluate. I created this issue to track this: https://github.com/smol-machines/smolvm/issues/150

Really appreciate the feedback!

Comment · 6 months ago

Cannot thank you more for this! Lets' work together to see how we can make this easier for cave!

Comment · 6 months ago

Really appreciate it! Would love to work together to make this easier to use.

Comment · 6 months ago

Really appreciate the suggestion! By "live migration", do you mean keeping the existing files and migrate them elsewhere with the vm?

Thanks

Comment · 6 months ago

Hey, thanks so much! yah we will definitely add windows support later. We are exploring how to get this work with WSL and will release it asap. Stay tuned and thanks!