search for: blockfront

hi, has anyone attempted to add grant tables, blockfront or netfront support to mini-os recently? Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ring a bell with a member of the Xen developer community. The setup is Xen 4.0.0-RC2 (OpenSUSE 11.2 package) on a Nehalem system. The sole guest instance is 64bit FreeBSD running in HVM mode, a single vcpu, and a PCI passed-through LSI Logic 1068e SAS controller. FreeBSD is running netfront and blockfront PV drivers. After a few hours of operation, FreeBSD''s entire grant table (3 pages) is spammed with the pattern 0x5a5a5a5a. This problem has been replicated on multiple machines. The first assumption was a bug in the FreeBSD PV drivers or other Xen support. To rule this out, we modified...

Hello, as some might have read in my previous postings, I have a Mini-OS dom0 that constructs a Mini-OS domU on x86 xen-3.0.4-testing. As the memory layout my Dom0 builds does not guarantee, that pages the DomU Mini-OS tries to use as page tables are mapped to existing memory, I changed new_pt_frame in arch/x86/mm.c in the following way: The pt_pfn is mapped R/W, then it is zeroed by a

Some question. Can I install Xen-3.2.1 with 2.6.18-xen kernel... to my Dom0 and without HVM, starting a debian(DomU) with kernel 2.6.25 from kernel src and compiled with all XEN port / features ? or i need to use the vmlinuz-2.6.18-xen to all my DomU ?? Thanks Crazy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

...s at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices needed to make it work (netfront, blockfront, console). It also has xen-pvfb support, which means you can run the standard X server without needing to set up Xvnc. I don't know of any bugs in 2.6.26, so I'd recommend you try it out for all your 32-bit domU needs. It has had fairly wide exposure in Fedora kernels, so I'd rank it...

...uld I make an .iso image file accassable to a domU? If a use tap:/var/lib/libvirt/images/some.iso tapdisk2 claims the image and passes phy:/dev/xen/blktapX to qemu-dm, which I can access fine, but eject does not work, since qemu only sees the phy: device and can''t open another file. xen-blockfront in PVonHVM and Windows-GPLPV driver both reject CDROM-devices, so the CDROM remains IDE emulated. With GPLPV /local/domain/0/backend/vbd/18/768/state changes from "1" → "4", while with Linux it changes to "6" as soon as the Xen modules probe the XenBus. After that...

...d appreciate it if people could grab the patch queue from http://ozlabs.org/~rusty/paravirt/ - or from the posting I'm about to make - and tell me if it works for you. This is a limited Xen implementation for now, so bear in mind that it's: * domU only * UP only * netfront and blockfront only * not particularly performance tuned But it should support both PAE and non-PAE. Oh, and the console will be hvc0, since its using the hvc console infrastructure rather than the traditional xen-console. Thanks, J

...d appreciate it if people could grab the patch queue from http://ozlabs.org/~rusty/paravirt/ - or from the posting I'm about to make - and tell me if it works for you. This is a limited Xen implementation for now, so bear in mind that it's: * domU only * UP only * netfront and blockfront only * not particularly performance tuned But it should support both PAE and non-PAE. Oh, and the console will be hvc0, since its using the hvc console infrastructure rather than the traditional xen-console. Thanks, J

...d appreciate it if people could grab the patch queue from http://ozlabs.org/~rusty/paravirt/ - or from the posting I'm about to make - and tell me if it works for you. This is a limited Xen implementation for now, so bear in mind that it's: * domU only * UP only * netfront and blockfront only * not particularly performance tuned But it should support both PAE and non-PAE. Oh, and the console will be hvc0, since its using the hvc console infrastructure rather than the traditional xen-console. Thanks, J

...s at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices needed to make it work (netfront, blockfront, console). It also has xen-pvfb support, which means you can run the standard X server without needing to set up Xvnc. I don't know of any bugs in 2.6.26, so I'd recommend you try it out for all your 32-bit domU needs. It has had fairly wide exposure in Fedora kernels, so I'd rank it...

...s at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices needed to make it work (netfront, blockfront, console). It also has xen-pvfb support, which means you can run the standard X server without needing to set up Xvnc. I don't know of any bugs in 2.6.26, so I'd recommend you try it out for all your 32-bit domU needs. It has had fairly wide exposure in Fedora kernels, so I'd rank it...

...s at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices needed to make it work (netfront, blockfront, console). It also has xen-pvfb support, which means you can run the standard X server without needing to set up Xvnc. I don't know of any bugs in 2.6.26, so I'd recommend you try it out for all your 32-bit domU needs. It has had fairly wide exposure in Fedora kernels, so I'd rank it...

...s at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices needed to make it work (netfront, blockfront, console). It also has xen-pvfb support, which means you can run the standard X server without needing to set up Xvnc. I don't know of any bugs in 2.6.26, so I'd recommend you try it out for all your 32-bit domU needs. It has had fairly wide exposure in Fedora kernels, so I'd rank it...

I have seen the following kernel panic 5 times today on three different machines, two of which had been stable for months and one of which is a brand new install. We are running the x86_64 xen kernel and userland tools that came in the Xen 3.1.0 tarball from xen.org, on top of scientific linux (redhat clone) 5.1 or 5.2. <Aug/28 12:21 pm>Unable to handle kernel NULL pointer dereference at

...& misc & submit xen for scanning by Coverity tool; investigate warnings flagged \\ 3/4 & misc & tools support for doing auto CPU/memory resource allocation across VMs \\ 3/4 & misc & support to checkpoint/rollback guests \\ 4 & misc & port Grub2 bootloader to net/blockfront devices \\ 4 & misc & investigate ''pluggable driver architecture'' \\ 4 & misc & xenfs filesystem-level virtualization; shared buffer cache \\ 4 & misc & do we need support for ISA/PCMCIA DMA (below 16MB)? \\ \hline \end{tabular} \end{document}...

...n implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The...

...n implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The...

...n implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The...

...iles - Core Xen implementation - Efficient late-pinning/early-unpinning pagetable handling - Virtualized time, including stolen time - SMP support - Preemption support - Batched pagetable updates - Xen console, based on hvc console - Xenbus - Netfront, the paravirtualized network device - Blockfront, the paravirtualized block device Thanks, J --

...iles - Core Xen implementation - Efficient late-pinning/early-unpinning pagetable handling - Virtualized time, including stolen time - SMP support - Preemption support - Batched pagetable updates - Xen console, based on hvc console - Xenbus - Netfront, the paravirtualized network device - Blockfront, the paravirtualized block device Thanks, J --