similar to: Convert CentOS-8 UEFI img to hyper-V

Displaying 20 results from an estimated 20000 matches similar to: "Convert CentOS-8 UEFI img to hyper-V"

2020 Apr 29
4
INITRD_MODULES
I am trying to take a CentOS 7 img and get hyperv to boot. First step. qemu-img convert "CentOS7.img" -O vhdx -o subformat=dynamic "CentOS7.vhdx" after adding new hyper-v I get dracut-timeout... So doing some searching it says add hv_vmbus hv_netvsc hv_storvsc to INITRD_MODULES. which doesnt really exist any more in CentOS 7. I did find /etc/dracut.conf and add_drivers... I
2015 Oct 09
0
[PATCH 2/2] kvm/x86: Hyper-V kvm exit
From: Andrey Smetanin <asmetanin at virtuozzo.com> A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V synic configuraion triggered by guest writing to the corresponding MSRs. Signed-off-by: Andrey Smetanin <asmetanin at virtuozzo.com> Reviewed-by: Roman Kagan <rkagan at virtiozzo.com> Signed-off-by: Denis V. Lunev <den at openvz.org> CC:
2015 Oct 16
0
[PATCH 9/9] kvm/x86: Hyper-V kvm exit
From: Andrey Smetanin <asmetanin at virtuozzo.com> A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V SynIC configuration triggered by guest writing to the corresponding MSRs. Signed-off-by: Andrey Smetanin <asmetanin at virtuozzo.com> Reviewed-by: Roman Kagan <rkagan at virtiozzo.com> Signed-off-by: Denis V. Lunev <den at openvz.org> CC:
2015 Jul 20
0
Migrate KVM linux based VM to microsoft Hyper-v
Hi, I am searching around this topic but didn't get any suitable link, can you guys please help with this. i have my linux based VM as .img which is built on top of VirtIO protocol and runs fine on KVM or qemu. i am trying to port the same on the Microsoft Hyper-V but it is not working. I get blank screen with no other actions, tried the same on virtual box also but result is same. i have
2015 Apr 07
0
Re: [Libvirt] [virsh] Transport Error during enumeration while connecting libvirt to Hyper-V Server
2015-04-02 12:04 GMT+02:00 <Dhaval_Shah1@dell.com>: > Hi all, > > > > I am using libvirt 1.1.1. I can successfully able to connect with Qemu > driver but when I am trying to connect to the windows Hyper-V using virsh, I > am getting failure. > > > > [root@localhost hyperv]# virsh version > > Compiled against library: libvirt 1.1.1 > > Using
2017 Mar 18
0
kerberos issue (SPN not found) with windows Hyper-V ( samba 4.5.3 AD)
After reviewing logs I found that my previous assumption was wrong. Situation: - i'm trying to start live migration from hyper-v host A (BMSRV4-HYPERV) to hyper-v host B (BM-SRV-5) from host B (logged in as user from DOMAIN ADMINS group). Kerberos constrained delegation is set in accordnance to microsoft instructions with proper SPN's set (well, proper as in with the workaround I
2018 Aug 02
2
ODP: Re: SAMBA 4 as Active Direcotry and Hyper-V
I have a suspicion that it is related to the specific SPNs that hyperv uses. Hyper-v tries to register 3 spn (typing from memory so I might be a bit off): Microsoft hyper-v console/HOST.FQDN Hyper-V Replication Servive/HOST.FQDN Microsoft Hyper-V Live Migration Service/HOST.FQDN. This fails because of the spaces, that is samba being on linux, not seeing escape characters, messes up the request it
2018 Aug 02
0
ODP: Re: SAMBA 4 as Active Direcotry and Hyper-V
On Thu, 2018-08-02 at 17:32 +0200, Kacper Wirski via samba wrote: > I have a suspicion that it is related to the specific SPNs that hyperv uses. Hyper-v tries to register 3 spn (typing from memory so I might be a bit off): > Microsoft hyper-v console/HOST.FQDN > Hyper-V Replication Servive/HOST.FQDN > Microsoft Hyper-V Live Migration Service/HOST.FQDN. > > This fails because of
2018 Aug 02
1
ODP: Re: SAMBA 4 as Active Direcotry and Hyper-V
I actually posted about this here on samba list about it last year, but nobody caught interest. I used to have logs from samba and wireshark, which very nicely showed what's wrong (kerberos request was for SPNĀ  eg. "Hyper-V Replication Service/Servername.mydomain.com" and in samba log there was an error with something like "Hyper-V\ Replication \Service.. not found".
2016 Mar 23
0
libvirt 1.3.3 and Hyper-V 2012
Hello I installed libvirt 1.3.3 for managing a Hyper-V 2012 R2 Server. On the hyper-v server I entered the two commands: winrm set winrm/config/service/auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} After connecting, I receive the following error: user@ubuntu-serv-kvm:~/libvirt-hyperv-r2-2012$ virsh -c hyperv://192.168.33.140/?transport=http
2015 Oct 12
0
[Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit
On 10/12/2015 04:42 PM, Eric Blake wrote: > On 10/09/2015 07:39 AM, Denis V. Lunev wrote: >> From: Andrey Smetanin <asmetanin at virtuozzo.com> >> >> A new vcpu exit is introduced to notify the userspace of the >> changes in Hyper-V synic configuraion triggered by guest writing to the > s/configuraion/configuration/ > Is 'synic' intended? Is it short
2017 Mar 19
1
kerberos issue (SPN not found) with windows Hyper-V ( samba 4.5.3 AD)
Hello, This won't be a very helpful reply, but I can confirm I've had the exact same issue. I ran into this a few years ago and could not get HyperV migrations to work with a Samba DC. I even went so far as to install a Windows DC just to prove to myself that it is supposed to work, and it does, perfectly (with ADDC it even creates all the SPNs for you auto-magically). Unfortunately at
2013 Aug 09
0
Hyper-V driver API version support
Hello The "version" function is not supported by the hyperv driver: $ virsh --connect=hyperv://hypervhost version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: Hyper-V 1.1.1 error: failed to get the hypervisor version error: this function is not supported by the connection driver: virConnectGetVersion But we need this funtion for the
2015 Apr 02
3
[Libvirt] [virsh] Transport Error during enumeration while connecting libvirt to Hyper-V Server
Hi all, I am using libvirt 1.1.1. I can successfully able to connect with Qemu driver but when I am trying to connect to the windows Hyper-V using virsh, I am getting failure. [root@localhost hyperv]# virsh version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: QEMU 1.1.1 Running hypervisor: QEMU 1.5.3 When I am doing virsh to connect to hype-V I am getting
2014 Nov 24
2
pxelinux efi64 boot woes on hyper-v gen 2
http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of TFTP server makes hyper-v happy. Virtualbox, VmWare seem to have the same EFI boot code & output
2015 Oct 09
0
[PATCH 1/2] kvm/x86: Hyper-V synthetic interrupt controller
From: Andrey Smetanin <asmetanin at virtuozzo.com> Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event
2014 Nov 27
0
pxelinux efi64 boot woes on hyper-v gen 2
On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ > > P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of
2012 Jan 10
1
Communication with Hyper-V
Hi, I'm interested in using libvirt to communicate with Microsoft's Hyper-V. I'm trying to use virsh, but with no success. I have a machine that runs Windows Server Developer Preview with Hyper-V on it, ip x.x.x.x I set the service Basic and AlloUnencrypted properties on this machine to true, as required I also have a Linux machine x.x.y.y, with libvirt installed. This is what I get:
2015 Nov 02
0
[kvm-unit-tests PATCH] x86: hyperv_synic: Hyper-V SynIC test
On 26/10/2015 10:56, Andrey Smetanin wrote: > Hyper-V SynIC is a Hyper-V synthetic interrupt controller. > > The test runs on every vCPU and performs the following steps: > * read from all Hyper-V SynIC MSR's > * setup Hyper-V SynIC evt/msg pages > * setup SINT's routing > * inject SINT's into destination vCPU by 'hyperv-synic-test-device' > * wait for
2018 Aug 02
0
SAMBA 4 as Active Direcotry and Hyper-V
Unfortunately i don't have any logs. Even from samba. I installed Samba from source (with option ads). After that, i used something like wizard to configure Samba as Active Direcotry Domain Controller. 2018-08-02 16:24 GMT+02:00 L.P.H. van Belle via samba <samba at lists.samba.org >: > Ok, what you use is your choice. It's what you preffer. > > Few other questions then.