similar to: How to enable vmx (virtual machine extensions) in virt-manager

Finished installing CentOS 5.5 x86_64 on a new Dell tower workstation that has a quad core Intel processor and 8 GB of ram. BIOS has hardware virtualization support enabled. /proc/cpuinfo shows that all four cores have the vmx flag present. I applied a lot of the National Security Agency guide for securing Red Hat Linux 5, testing the key applications I need as I went. At the end of the process

I’m confused. You’re asking if I’m able to connect with VNC in response to my comment that I’m unable to connect with VNC? What I see when I open the viewer on the port is a window titled “<username> X desktop”, with a grey background, an “X” cursor, and an error dialog (with an “okay” prompt) saying what I described before. Ctrl-Alt-F1 and similar keys do nothing. From: Jeff Tchang

This is offtopic, but related to what you’ve told me so far. I’m having some trouble getting the VNC connection to work. Technically, the “connection” is working fine, but the Windows TightVNC Viewer comes up with an error dialog saying this: Xsession: unable to start X session --- no "/home/.../.xsession" file, no "/home/.../.Xsession" file, no session managers, no window

Try some of these combinations: http://www.howtogeek.com/119293/4-ways-to-recover-from-a-crashed-or-frozen-x-server-on-linux/ The good thing is your vm is up and running. You should try SSHing into it if that works. On Fri, Jul 10, 2015 at 1:37 PM, KARR, DAVID <dk068x@att.com> wrote: > I’m confused. You’re asking if I’m able to connect with VNC in response > to my comment that

Thanks for replying. Good info so far. After I start the VM, I’m going to need to see the boot console, and I’ll need to ssh into it with a hostname or IP. What are some required steps for those needs? This VM is going to need to access a few associated networks. I can see that the “—networks” option is part of the interface for configuring this. What are some things I’ll have to do for

That's kind of weird. I don't think VNC has anything to do with X really. Are you able to connect with VNC? If you are able to establish a connection the first thing you should see is a login prompt on most distributions (unless the distribution is configure to start X windows). Maybe there is some key you can press to get a console window. Like CTRL-ALT-F1 or F2 or F3. On Fri, Jul 10,

Dear list, Something has been perplexing me lately. I have a bunch of Windows 7 virtual machines running on top of Fedora 20 in KVM using virt-manager. One of the big problems is that users who need the Windows VM's don't know how to user virt-manager and when they accidentally reboot a machine I have to manually setup the virt-manager session for them and make it full-screen. That

To see the boot console you need to have a VNC client and connect to it once it is up. For Mac OS I use the "Screen Sharing" application which can connect to VNC natively. For Windows you can use something like tightvnc. For SSH you need to make sure it is listening on the port. --network is used to specify a libvirt network I believe. On my example box it is in

I'm a beginner to libvirt and creating VMs, for that matter. I have a set of specifications for VMs I need to create and log into, but I have to create them on an Ubuntu box that I only have ssh access to. I won't have desktop GUI access, although I do have dynamic port forwarding, so I can access a browser GUI from my desktop. Reading through the libvirt info, I see numerous mentions

Passthrough the LBR stack to the guest, and auto switch the stack MSRs upon VMEntry and VMExit. Signed-off-by: Wei Wang <wei.w.wang at intel.com> --- arch/x86/kvm/vmx.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index 5f5c2f1..35e02a7 100644 --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c

On 09/25/2017 10:57 PM, Andi Kleen wrote: >> +static void auto_switch_lbr_msrs(struct vcpu_vmx *vmx) >> +{ >> + int i; >> + struct perf_lbr_stack lbr_stack; >> + >> + perf_get_lbr_stack(&lbr_stack); >> + >> + add_atomic_switch_msr(vmx, MSR_LBR_SELECT, 0, 0); >> + add_atomic_switch_msr(vmx, lbr_stack.lbr_tos, 0, 0); >> + >> + for

On 25/09/2017 06:44, Wei Wang wrote: > Passthrough the LBR stack to the guest, and auto switch the stack MSRs > upon VMEntry and VMExit. > > Signed-off-by: Wei Wang <wei.w.wang at intel.com> This has to be enabled separately for each guest, because it may prevent live migration to hosts with a different family/model. Paolo > --- > arch/x86/kvm/vmx.c | 50

On 25/09/2017 06:44, Wei Wang wrote: > Passthrough the LBR stack to the guest, and auto switch the stack MSRs > upon VMEntry and VMExit. > > Signed-off-by: Wei Wang <wei.w.wang at intel.com> This has to be enabled separately for each guest, because it may prevent live migration to hosts with a different family/model. Paolo > --- > arch/x86/kvm/vmx.c | 50

On Mon, Mar 19, 2018 at 02:21:24PM +0000, Зиновик Игорь Анатольевич wrote: > > -----Original Message----- > > From: Richard W.M. Jones [mailto:rjones@redhat.com] > > Sent: Monday, March 19, 2018 3:27 PM > > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > > Cc: libguestfs@redhat.com > > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM:

On Tue, Mar 06, 2018 at 08:40:51AM +0000, Зиновик Игорь Анатольевич wrote: > > What happens if you run these commands (which should be safe to run > > because they only operate on a throw-away overlay): > > > > qemu-img create -f qcow2 throwaway.qcow2 /mnt/knp1-vm-otp02/knp1-vm- > > otp02.vmdk I missed out the -b flag: qemu-img create -f qcow2 throwaway.qcow2 -b

On Mon, Mar 05, 2018 at 02:03:17PM +0000, Зиновик Игорь Анатольевич wrote: > Hello. > > I'm trying to convert VMware based virtual machines (CentOS 7.2) and output them into oVirt. > virt-v2v fails with following error: > setfiles: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /.*. > > File `file_contexts' looks same

On Mon, Mar 12, 2018 at 08:25:58AM +0000, Зиновик Игорь Анатольевич wrote: > Hello, Richard. > > Did you managed to find root cause of the problem that I reported last week? I didn't have a chance to look at this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora

> +static void auto_switch_lbr_msrs(struct vcpu_vmx *vmx) > +{ > + int i; > + struct perf_lbr_stack lbr_stack; > + > + perf_get_lbr_stack(&lbr_stack); > + > + add_atomic_switch_msr(vmx, MSR_LBR_SELECT, 0, 0); > + add_atomic_switch_msr(vmx, lbr_stack.lbr_tos, 0, 0); > + > + for (i = 0; i < lbr_stack.lbr_nr; i++) { > + add_atomic_switch_msr(vmx,

> +static void auto_switch_lbr_msrs(struct vcpu_vmx *vmx) > +{ > + int i; > + struct perf_lbr_stack lbr_stack; > + > + perf_get_lbr_stack(&lbr_stack); > + > + add_atomic_switch_msr(vmx, MSR_LBR_SELECT, 0, 0); > + add_atomic_switch_msr(vmx, lbr_stack.lbr_tos, 0, 0); > + > + for (i = 0; i < lbr_stack.lbr_nr; i++) { > + add_atomic_switch_msr(vmx,

Image.py should send 2 new arguments to qemu-dm for setting QEMU window Title. 1 is const string "-domain-name", the other is the string of domain name. At present imagy.py combines these two strings to 1. So Qemu will fail to recognize it and fail to start. Signed-off-by: Yongkang You <yongkang.you@intel.com> --- a/tools/python/xen/xend/image.py 2005-12-04 14:32:04.956602836