search for: virtm

On Mon, Sep 1, 2014 at 10:39 AM, Andy Lutomirski <luto at amacapital.net> wrote: > This fixes virtio on Xen guests as well as on any other platform > that uses virtio_pci on which physical addresses don't match bus > addresses. > > This can be tested with: > > virtme-run --xen xen --kimg arch/x86/boot/bzImage --console > > using virtme from here: > > https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git > > Without these patches, the guest hangs forever. With these patches, > everything works. > Dusting off an ancient thread....

On Mon, Sep 1, 2014 at 10:39 AM, Andy Lutomirski <luto at amacapital.net> wrote: > This fixes virtio on Xen guests as well as on any other platform > that uses virtio_pci on which physical addresses don't match bus > addresses. > > This can be tested with: > > virtme-run --xen xen --kimg arch/x86/boot/bzImage --console > > using virtme from here: > > https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git > > Without these patches, the guest hangs forever. With these patches, > everything works. > Dusting off an ancient thread....

...off by default on everything except Xen PV on x86. >> > > What is your setup? My understanding is that virtio doesn't work on PV > guest as of now because a suitable transport is missing. I cheated and ran Xen under KVM with the virtio-pci device provided by QEMU. If you have virtme (https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git/), you can do: virtme-run --kdir=. --pwd --xen xen-4.5.2 --qemu-opts -smp 3 -m 1024 where xen-4.5.2 is the gunzipped Xen binary. (Other versions work, too.) --Andy

...off by default on everything except Xen PV on x86. >> > > What is your setup? My understanding is that virtio doesn't work on PV > guest as of now because a suitable transport is missing. I cheated and ran Xen under KVM with the virtio-pci device provided by QEMU. If you have virtme (https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git/), you can do: virtme-run --kdir=. --pwd --xen xen-4.5.2 --qemu-opts -smp 3 -m 1024 where xen-4.5.2 is the gunzipped Xen binary. (Other versions work, too.) --Andy

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init root...

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init root...

...0:39 AM, Andy Lutomirski <luto at amacapital.net> wrote: >> This fixes virtio on Xen guests as well as on any other platform >> that uses virtio_pci on which physical addresses don't match bus >> addresses. >> >> This can be tested with: >> >> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console >> >> using virtme from here: >> >> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git >> >> Without these patches, the guest hangs forever. With these patches, >> everything works. >>...

...2 soon, and please tell me whether my code makes sense on ARM. (My attempt to boot-test s390 failed because I have no clue what command-line options to pass to QEMU. If anyone wants to give me some pointers to get a working configuration with -kernel and some kind of console, I can add support to virtme. Alas, I think that no one ever bothered to implement 9p over virtio-ccw in QEMU. Why exactly does the virtio stuff in QEMU require that you instantiate virtio-9p-pci instead of just asking for an appropriate virtio dievice?) --Andy

...2 soon, and please tell me whether my code makes sense on ARM. (My attempt to boot-test s390 failed because I have no clue what command-line options to pass to QEMU. If anyone wants to give me some pointers to get a working configuration with -kernel and some kind of console, I can add support to virtme. Alas, I think that no one ever bothered to implement 9p over virtio-ccw in QEMU. Why exactly does the virtio stuff in QEMU require that you instantiate virtio-9p-pci instead of just asking for an appropriate virtio dievice?) --Andy

On 27/08/14 23:50, Andy Lutomirski wrote: > This fixes virtio on Xen guests as well as on any other platform > that uses virtio_pci on which physical addresses don't match bus > addresses. > > This can be tested with: > > virtme-run --xen xen --kimg arch/x86/boot/bzImage --console > > using virtme from here: > > https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git > > Without these patches, the guest hangs forever. With these patches, > everything works. > > This should be safe on...

...t amacapital.net> wrote: > >> This fixes virtio on Xen guests as well as on any other platform > >> that uses virtio_pci on which physical addresses don't match bus > >> addresses. > >> > >> This can be tested with: > >> > >> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console > >> > >> using virtme from here: > >> > >> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git > >> > >> Without these patches, the guest hangs forever. With these patches, >...

...t amacapital.net> wrote: > >> This fixes virtio on Xen guests as well as on any other platform > >> that uses virtio_pci on which physical addresses don't match bus > >> addresses. > >> > >> This can be tested with: > >> > >> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console > >> > >> using virtme from here: > >> > >> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git > >> > >> Without these patches, the guest hangs forever. With these patches, >...

This fixes virtio on Xen guests as well as on any other platform that uses virtio_pci on which physical addresses don't match bus addresses. This can be tested with: virtme-run --xen xen --kimg arch/x86/boot/bzImage --console using virtme from here: https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git Without these patches, the guest hangs forever. With these patches, everything works. This should be safe on all platforms that I'm aware of. That d...

This fixes virtio on Xen guests as well as on any other platform that uses virtio_pci on which physical addresses don't match bus addresses. This can be tested with: virtme-run --xen xen --kimg arch/x86/boot/bzImage --console using virtme from here: https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git Without these patches, the guest hangs forever. With these patches, everything works. This should be safe on all platforms that I'm aware of. That d...

....com> wrote: > On 27/08/14 23:50, Andy Lutomirski wrote: >> This fixes virtio on Xen guests as well as on any other platform >> that uses virtio_pci on which physical addresses don't match bus >> addresses. >> >> This can be tested with: >> >> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console >> >> using virtme from here: >> >> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git >> >> Without these patches, the guest hangs forever. With these patches, >> everything works. >>...

....com> wrote: > On 27/08/14 23:50, Andy Lutomirski wrote: >> This fixes virtio on Xen guests as well as on any other platform >> that uses virtio_pci on which physical addresses don't match bus >> addresses. >> >> This can be tested with: >> >> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console >> >> using virtme from here: >> >> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git >> >> Without these patches, the guest hangs forever. With these patches, >> everything works. >>...

I'm running a Fedora distro kernel (3.13.7-200.fc20.x86_64) in kvm with these options: -chardev null,id=hvc0,signal=off -device virtio-serial-pci -device virtconsole,chardev=hvc0,name=virtme_console -append console=hvc0 console=ttyS0 -nographic (There are more, but these are the interesting ones, I think.) Note that virtio_console is modular, which might be a problem. It blows up like this: [ 0.443591] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 0...

I'm running a Fedora distro kernel (3.13.7-200.fc20.x86_64) in kvm with these options: -chardev null,id=hvc0,signal=off -device virtio-serial-pci -device virtconsole,chardev=hvc0,name=virtme_console -append console=hvc0 console=ttyS0 -nographic (There are more, but these are the interesting ones, I think.) Note that virtio_console is modular, which might be a problem. It blows up like this: [ 0.443591] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 0...

This fixes virtio on Xen guests as well as on any other platform that uses virtio_pci on which physical addresses don't match bus addresses. This can be tested with: virtme-run --xen xen --kimg arch/x86/boot/bzImage --console using virtme from here: https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git Without these patches, the guest hangs forever. With these patches, everything works. This should be safe on all platforms that I'm aware of. That d...

This fixes virtio on Xen guests as well as on any other platform that uses virtio_pci on which physical addresses don't match bus addresses. This can be tested with: virtme-run --xen xen --kimg arch/x86/boot/bzImage --console using virtme from here: https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git Without these patches, the guest hangs forever. With these patches, everything works. This should be safe on all platforms that I'm aware of. That d...