similar to: Virtualization Active Through Reboot?

How large would a hypervisor be if it were constructed as the smallest program supporting the virtualization of unmodified operating systems only (i.e. no linux-specific features, no para-virtualization)? Thanks, Dave Feustel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, a heave a share on a samba server 3.6.3 that is used as a DFS-Root. The DFS Links a working on Client with Windows 7 but not on Windows XP clients. Searching on the internet gives me a hint that it can be a problem with "security = ADS". The Samba server is member of a windows 2003 R2 Domain, and the Unix user info (uid, gid) are stored on the domain in der RFC 2302

Hi chaps, So my general problems with disks disappeared once I understood it was an SELinux problem. However I''m still finding in the DomU when I run through my kickstart that I''m getting an error which says: "Error processing drive: xen-vbd-51712 ........ this drive may need to be reinitialized" See: http://d.pr/i/YrH8 If I go ahead and reinitialize it, the

Fix reboot to work with the VMI. We must support fallback to the standard BIOS reboot mechanism. Turns out that this is required by kexec, and a good idea for native hardware. We simply insert the NOP VMI reboot hook before calling the BIOS reboot. While here, fix SMP reboot issues as well. The problem is the halt() macro in VMI has been defined to be equivalent to safe_halt(), which enables

Fix reboot to work with the VMI. We must support fallback to the standard BIOS reboot mechanism. Turns out that this is required by kexec, and a good idea for native hardware. We simply insert the NOP VMI reboot hook before calling the BIOS reboot. While here, fix SMP reboot issues as well. The problem is the halt() macro in VMI has been defined to be equivalent to safe_halt(), which enables

While trying to port kexec cleanly to klibc, came across this syscall usage for reboot(2). Calling reboot directly simplifies the code. Signed-off-by: maximilian attems <max at stro.at> --- kexec/kexec-syscall.h | 18 ------------------ kexec/kexec.c | 3 ++- 2 files changed, 2 insertions(+), 19 deletions(-) v2: keep LINUX_REBOOT_CMD_KEXEC defines, thus no need of

Whe have a Active Directory with the SFU2307 Unix extensions running. The user authentication is running fine against the Active Directorty, for this why are using the "ad" idmap backend. The only problem that are not running is, that "getent group" are only shows the local linux groups and no Actvie Directory Groups with a GID. "wbinfo -g" and "wbinfo -G"

Hi all, Is it possible to reload the dom0 / host node's kernel with a newer one, without rebooting the server? I know kexec can do something like this for security patches, but I don't know much about kexec, and I don't want to mess up a production server either. So, has anyone done something like this before? I need to load a new kernel for one of the domU's iptables to work, but

Avi, Hope this series is okay now. Thanks for the testing

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

R-help, I am tring to create a plot with two y-axis. I found an example which is fine but the problem is that the range of the second y-axes appears in the first y-axes causing confusion. The example I refer to is : ################################## dev.off() ## start with a new graphics device # X11() or postscript() plot(x<-rnorm(100),y<-rnorm(100)) z<-rnorm(100)*250 par(new=T)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone have any thoughts on why anaconda might be prompting me to reinitialize the disk during the kickstart of a Centos6.4 install on hyperV when a) the kickstart file contains "zerombr" as referred to in the installation guide[1] b) installation proceeds with no prompt on KVM hypervisors and succeeds? I have read the release notes[2]/tech

Hi Folks, GRUB claims to provide a feature that I want, but that doesn't really work. With GRUB you can presumably run GRUB from the command line of a shell and see the menu of boot options that would be presented if you were actually booting. You can select a stanza from the configfile and invoke it right then and there causing the machine to reboot as though you had selected this option

On 01/30/2017 08:06 PM, Greg Kurz wrote: >> Currently, under certain circumstances vhost_init_is_le does just a part >> of the initialization job, and depends on vhost_reset_is_le being called >> too. For this reason vhost_vq_init_access used to call vhost_reset_is_le >> when vq->private_data is NULL. This is not only counter intuitive, but >> also real a problem

On 01/30/2017 08:06 PM, Greg Kurz wrote: >> Currently, under certain circumstances vhost_init_is_le does just a part >> of the initialization job, and depends on vhost_reset_is_le being called >> too. For this reason vhost_vq_init_access used to call vhost_reset_is_le >> when vq->private_data is NULL. This is not only counter intuitive, but >> also real a problem

Hello guys, I have a problem when using my MSI R9 380 4G graphic card as GPU passthrough with KVM. At the first linux boot (Fedora 23) I am able to successfully start virtual machine and it works! However if i will shut down virtual machine and start it again - the screen will stay blank! So far I have been able to find on the internet that some graphic cards just can not reinitialize itself

Hi all, I'm using libvirt-go and I following code to listen for lifecycle events: func event_listen() { log.Printf("event_listen %s", conf.Libvirt.LocalUrl) hv, err := libvirt.NewConnect(conf.Libvirt.LocalUrl) lifecycleCallback := func(c *libvirt.Connect, d *libvirt.Domain, event *libvirt.DomainEventLifecycle) { event_message(c, d, "lifecycle", event)

Currently, under certain circumstances vhost_init_is_le does just a part of the initialization job, and depends on vhost_reset_is_le being called too. For this reason vhost_vq_init_access used to call vhost_reset_is_le when vq->private_data is NULL. This is not only counter intuitive, but also real a problem because it breaks vhost_net. The bug was introduced to vhost_net with commit