HN user

bstx

100 karma
Posts0
Comments39
View on HN
No posts found.

If you happen to be in SF, the Vallejo/Mare Island ferry should be a relatively convenient (and scenic) public transit option.

ARM architectural licensees develop their own microarchitectures that implement the ARM ISA spec, they do not license any particular microarchitecture from ARM (e.g. Cortex-A? IP cores). That includes Apple, Samsung, Nvidia and others.

No. It has become significantly easier for Europeans to immigrate since 2005. Labor certification alone now takes less than a year rather than multiple years pre-PERM. EB2 and EB3 priority dates are current. Europeans can expect to get a green card within a couple years (even accounting for the new mandatory Adjustment of Staus interviews for employment based applicants). It has become significantly harder for Indians where the green card backlog approaches a century (!) for EB2/EB3. The only thing that has become harder is getting an H-1B visa due to oversubscription.

Well, it's not just the userland. The XNU kernel is a hybrid of Mach (tasks, threads, IPC, VM), BSD (processes, users, devices, networking, system calls, VFS) and IOKit (driver framework)

QEMU 2.0.0 Released 12 years ago

You seem to be laboring under some serious misapprehensions here. QEMU is very much a virtualization solution. It calls itself an emulator because it's older than the name 'virtualization.'

QEMU is an emulator, it isn't by itself capable of doing virtualization. It can allow a hypervisor to do CPU (and some I/O) virtualization in lieu of QEMU doing binary translation/emulation. In that case QEMUs purpose is mainly I/O emulation. 'Virtualization' as a name and concept predates QEMU by several decades.

KVM is merely the kernel infrastructure that enables ring-0 access for faster hardware access. For many years it was called qemu-kmod; to this day the actual process that you run is called 'kvm-qemu.'

kqemu and KVM are technologically unrelated.

You are overstating the difference between 'virtualization' and 'emulation.' There really isn't one. What used to be called 'emulation' is nowadays called 'full-virtualization' as opposed to 'paravirtualization.' QEMU, KVM, and XenKVM are full-virt, while traditional Xen is paravirt.

Para-Virtualization is the concept where the guest OS is aware that it is being run on a hypervisor. For example using hypervisor hypercalls to create new address spaces rather than setting up hardware page tables. "Full" or hardware level virtualization happens when the guest OS does not need to be aware of this fact. Neither is related to emulation.

KVM is not a hypervisor;

It is.

libvirt is.

This one isn't.

Xen blurs the line between virtualization platform and hypervisor because both pieces ship within the same project. Either libvirt or Xen can act as hypervisor for QEMU or KVM.

"hypervisor":"virtualization platform" ~ "kernel":"operating system". KVM and Xen can act as hypervisor for Qemu managed by libvirt.

If you don't mind trailing whitespace block select might be an option (option + select on OS X / ctrl + alt + select on Linux). Or just use copy mode and yank the selection to the system clipboard.

> Ok so one of the coolest things in this game is that you can have multiple flights occurring at once. Has anyone been able to intercept another flight they have put into space?

Well, yes. That's how you assemble space stations :)

> but my little X121e is the best laptop I've ever used.

What do you compare it with? I have one too (but currently dead due to infamous reset loop bug) and I think it is the worst ThinkPad I have owned. The screen is horrible, lackluster build quality and fit'n'finish, so so Linux support and the underside of the keyboard needed to be stuffed with cardboard to type properly. Given the budget price point I don't think it should carry a ThinkPad label at all, it tarnishes the brand.

Edit: I have the AMD Fusion, not the Intel variant.

> Every time the operating system decides that it’s time to run a different process, all caches are invalidated (on account of the virtual memory system).

Unless you have a virtually indexed cache I don't see why an OS would want to do that.

That looks more like an issue with your machine. Does your CPU support VT extensions? Or they might not be enabled in the firmware. You can also fall back to traditional trap-n-emulate virtualization by disabling VT and nested paging in the VirtualBox preferences.

Always panics on boot in VMware. Sad :(

Edit: Seems to work in Parallels.

Edit 2: Boots in Parallels but is not very usable. Hangs very often, Parallels Tools do not work. Now trying in VirtualBox.

Edit 3: VirtualBox works as good or bad as Parallels. Native install seems to be the best option. Did someone try to install onto an external drive?

> What this means is that the kernel can no longer see if a user is writing to a read-only location, which is a major part of memory protection.

No, disabling WP in CR0 is only relevant for privileged code. Writes to write protected pages in user mode will still trap. It might mess up some in-kernel COW stuff though.

[dead] 15 years ago

He attempted to enter the US on a Visa Waiver (citizens of some western countries are eligible). A Visa Waiver doesn't require you to apply for a visa beforehand, you just hop on a plane when you feel like it. The terms and and conditions however state that you have to show sufficient funds for your stay when entering the country. He probably will be ineligible for VW in the future :/

My starting salary in the bay area right out of college is higher than what I would have conceivably made my entire career in Germany. I understand that small companies that do business locally operate with different economics, but what's the excuse for multinational corporations?

My decision to work in the US wasn't based in any way on expected compensation but rather on the excitingness of the job. Still, it's nice to be treated well as an employee.