SLES 10 (SP3) on Hyper-V 2012 R2

I do realize that is unsupported (only SP4 supposedly is)
But I have SLES 10 (SP3) image that got converted from vSphere
Once I can boot the IDE disk (by editing menu.lst to /hda1 & uninstall Vmware Tools, I would need to get network connectivity, so logical step would be to use Intergration Services 2.1 (one that supports SLES 10 SP3)
But it is a no go. On make install during load of vmbus the whole VM just hangs & dies
http://imageshack.com/a/img545/7339/16u1.jpg
The initrd never even gets created as it dies & reset is the only option
If I rem-out vmbus start in Makefile then I can get new kernel installed, but restulting kernel will panic on VM boot
Anybody has any clever idea how to get it working (if at all possible)
Seb

Getting this to work is going to be difficult. The older LIS 2.1 does not work with Hyper-V 2012 and 2012 R2 due to changes in Hyper-V itself. But you could probably get SLES 10 SP3 with LIS 2.1 working if you went back to the older Hyper-V
2008 R2.
You are correct that the LIS 3.4 package is created only for the Red Hat (and CentOS) distros. It will not work with SLES releases.
We've gotten occasional requests to get SLES 10 working on Hyper-V 2012 and 2012 R2, and we're in conversations with SUSE about creating a combination that works. But we don't have anything to announce about a timeline. When/if we get something
working, it will most likely be SLES 10 SP4, since that's the most up-to-date version from the SLES 10 series.
Michael Kelley, Lead Program Manager, Open Source Technology Center

Similar Messages

Windows 2008 R2: SLES 11 Sp3 Guest converted from Vmware OVA to VHD, does not boot on Hyper-V: could not find /dev/sda4

Hi
I have a VMWare OVA file with Guest OS as SLES 11 Sp3. I have converted this file from OVA to VHD using Microsoft Virtual Machine Converter Solution accelerator. On first boot of this VHD on Windows Server 2008 R2 - Microsoft Hyper-V I get an error that
"Waiting for device /dev/sda4 to appear..
Cannot find /dev/sda4"
I have not even booted this VM once on Hyper-V, and hence not installed any Linux integration Services yet.
What could be the possible reason for this failure? Any suggested solution?
Thanks
Ashwini

Easiest way (and also applies to Hyper-V 2012 R2):
Ok, following properly (originally missed the step to mount the root directory of the converted VM as "/mnt" )
http://nwrickert2.wordpress.com/2011/10/24/rescuing-susie/
Then once chrooted
mkinitrd -d /dev/sda2
generated initrd from kdump WITH Hyper-V drivers & VM is usable!
http://forums.opensuse.org/showthread.php/476780-boot-failure-mkinitrd-does-not-understand-that-dev-sda-has-become-dev-sde
Can't believe that it was so painful to find the right info easily
Just to finish it off, after converted machine boots fine, there is a small
matter of removing tools & fixing networking as per links below:
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-6F7BE33A-3B8A-4C57-9C35-656CE05BE22D.html
http://www.vcritical.com/2010/10/getting-eth0-back-in-a-sles-for-vmware-clone/
All done!!!
Also (unsupported), but works fine is SLES 11 SP1

Unable to monitor SLES 10 SP4,SLES 11 SP3 and SLES 11 SP2 via SCOM 2012 R2

Hi ,
I am unable to get SLES 10 SP4, SLES 11 SP3 and SLES 11 SP2 under SCOM 2012 R2 monitoring. The PAM ,glibc and openssl are at the right versions.
Per the documentation SCOM MP for unix/Linux provides monitoring of SUSE Linux Enterprise
Server 9, SUSE Linux Enterprise Server 10 SP1, and SUSE Linux Enterprise Server 11 operating systems. Does this mean it cannot monitor SP2, SP3 and SP4 for the same Operating systems?
Plat form not supported is the error which I get.
Thank you much,

There should not be any problems with monitoring SLES 10 SP4 or SLES 11 SP2/SP3. If you are getting a "platform not supported" error, it may be that the right management packs have not successfully imported. Can you give more details on when
you get the error, and the management pack versions that you have installed? And what Update Rollup (UR) for OpsMgr do you have installed? The latest is UR4, and the Linux/UNIX management packs for UR4 are here:
http://www.microsoft.com/en-hk/download/details.aspx?id=29696 . Be sure to download the version for "R2".
Michael Kelley, Lead Program Manager, Open Source Technology Center

SLES 11 SP3 - VSS Problem

Hi all,
I've just installed a fresh SLES 11 SP3 vm. Once rebooted, i noticed this error in hyper-v log:
- Hyper-V Volume Shadow Copy Requestor failed to connecto to virtual machine "nameofvm" because the version does not match the version expected by hyper-v (virtual machine ID xyz..) Framework version: Negotiated (0.0) Expected (3.0) Message
version: Negotiated (0.0) Expected (4.0) To fix this problem you must upgrate the integration services. To upgrade connect to the virtual machine and select insert ....
Now, obviously the installer disc doesn't work and all integration services are embedded in the linux OS. I'm concerning about two major factor: first, how can this problem impact the system once in production? And how can i address (or disable) this integration
service?
Thank you all

Hi Miralem, I believe there may be one other way to install updates. When you are installing SLES 11 SP3 for the first time, the installation manager GUI asks you if it should apply the updates. You might want to see if that works for you by creating
a new VM and closely monitoring the installation manager program.
If the VM is not going offline while taking the snapshot then this may be a false error. However, if the VM is going offline then probably the snapshot infrastructure is having some issues. Please let me know if you see that the VM is going offline while
taking the snapshot.
Also notice that backup for Linux VMs is only file-system consistent and it is not application consistent. This implies that db snapshots may not have the same level of application data consistency that you have come to expect through use of VSS on Windows.
This is because Linux does not have VSS style infrastructure to coordinate with user mode while a snapshot or a backup operation is in progress.
Please keep me posted on your progress.
Thanks,
Abhishek

How do I turn off Hyper-V 2012 server sleep mode?

Just installed Hyper-V 2012 server on a HP ML360 G8. Also installed Corefig 1.1.1. It seems after about 10 minutes if idle time the monitor goes black and the unit goes into sleep or hibernation. I have used powercfg to set it to the High Performance
power scheme and set screensaver to none in Corefig.
When the monitor goes black, if I move the mouse the sconfig screen, corefig, etc windows do not show until I run the mouse over them. Even then the windows do not 'repaint' until I run the mouse over the whole window or make some kind of key stroke in each
window.
Worried what this will do to my VMs once I start building them and would like to see the screen at all times. This is the first 2012 box and I have never had this issue with any of the Core 2008 products.
Thanks

Hi,
“I can't locate the GUI you show, it's Hyper-V 2012 Server,so i can't edit the settings.
Sems like it may be the monitor itself is going to sleep”
The other possible is you don’t have the administrator rights, or your server has got the Power Management, after you configuration the power option, the GPO refresh then
the old configuration be covered. Please refer the following article to confirm that:
Power Policy Configuration and Deployment in Windows
http://msdn.microsoft.com/en-us/windows/hardware/gg463243.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can I assign several physical storage locations for each virtual machine when using the replication-feature from Hyper-V 2012 R2?

Hi everyone,
I have 2x physical servers running Hyper-V 2012 R2. Each hosts several virtual machines. The VHDs of the VMs are stored on several dedicated physical disks to have a performance boost. For exampe if VM A has two VHDs attached I made sure that the VHDs are
on different physical disks to have them not slow-down each other in case of intensive disk accesses.
So far so good. I was looking forward to the replication-feature. The idea is to have the two physical servers have their primary running VMs being replicated to the other physical server and vice-versa. I was hoping to have the chance to choose for each
individual VM where the replicated VHD will be stored. But instead I can only see the one location/path which is configured in Hyper-V Manager when I activate the replication-feature on the server.
Is there by any chance a way how to select the storage location for each VHD/VM if using the replication-feature of Hyper-V 2012 R2?
Thanks in advance.
Cheers,
Sebastian

Secondly, you could replicate different VMs to different storage locations to perform some of the disk balancing you are trying to perform. Lastly, you could copy the vhd file to a different location
before starting the VM.
.:|:.:|:. tim
Hi Tim,
thanks for the reply. Sorry, but I had some other tasks to take care of, so I wasn't paying enough attention to this thread.
The part I quoted from your reply sounds exactly like the action I'd like to perform, but as you pointed out before this should not be possible.
How can I perform the action (replicating each VM to a storage location) as you mentioned secondly? To sum it up again:
2x physical machines carrying severel HDDs
8+ VMs spread to run on the 2x servers
when setting up replication I can only set the storage-location from server A on B and vice versa B on A
Thanks again for your reply.
Cheers,
Sebastian

SLES 10 SP3 Crash and reboot

I'm using SLES 10 SP3 for all my transaction servers and database servers. This Morning (7.40 West Indonesian Time) I found my database server just restarted (from /var/log/messages).
I'm confused, because kernel crash message in /var/log/messages related to NFS and Samba.
Here is sample of my syslog message :
Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47258
Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47259
Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47260
Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47257
Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
Oct 22 07:07:12 cygnus kernel: martian source 255.255.255.255 from 10.100.249.2, on dev vlan50
Oct 22 07:07:12 cygnus kernel: ll header: ff:ff:ff:ff:ff:ff:00:0c:42:ea:50:a2:08:00
Oct 22 07:07:15 cygnus kernel: CIFS VFS: No response for cmd 162 mid 47256
Oct 22 07:07:15 cygnus kernel: scheduling while atomic: cmahostd/0xffff8001/5937
Oct 22 07:07:15 cygnus kernel:
Oct 22 07:07:15 cygnus kernel: Call Trace: <ffffffff802eea75>{__sched_text_start+125}
Oct 22 07:07:15 cygnus kernel: <ffffffff884c6dad>{:cifs:wait_for_response+182} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884c76a9>{:cifs:SendReceive2+1237} <ffffffff884cd9b2>{:cifs:CIFS_SessSetup+1405}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b923e>{:cifs:cifs_setup_session+300} <ffffffff8013d754>{del_timer_sync+12}
Oct 22 07:07:15 cygnus kernel: <ffffffff801db45c>{find_nls+41} <ffffffff884aec3e>{:cifs:smb_init+457}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}<1 >Unable to handle kernel paging request at 00000000bd022aa0 RIP:
Oct 22 07:07:15 cygnus kernel: <ffffffff8012cb5b>{try_to_wake_up+53}
Oct 22 07:07:15 cygnus kernel: PGD 0
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+460} <0>Oops: 0000 [1] SMP
Oct 22 07:07:15 cygnus kernel:
Oct 22 07:07:15 cygnus kernel: <0>last sysfs file: /devices/pci0000:00/0000:00:1c.2/0000:04:00.1/irq
Oct 22 07:07:15 cygnus kernel: CPU 2
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563}Modules linked in: ipt_MASQUERADE nls_cp850 smbfs<ffffffff8014892e>{autoremove_wake_function+0 } ip6t_REJECT ipt_REJECT ipt_LOG xt_limit xt_state ip6table_mangle
Oct 22 07:07:15 cygnus kernel: iptable_mangle ip6table_filter ip6_tables binfmt_misc st sr_mod ide_disk ide_cd cdrom joydev xt_tcpudp<ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnix Info+96} ipt_multiport iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables fuse ntfs<ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+45 8} usb_storage ide_core af_packet nls_utf8 cifs
Oct 22 07:07:15 cygnus kernel: softdog mptctl mptbase sg vboxpci vboxnetadp vboxnetflt hpilo vboxdrv bnx2i scsi_transport_iscsi cnic 8021q<ffffffff884baa90>{:cifs:reset_cifs_unix_caps +460} bonding ipv6 dock button battery ac apparmor loop usbhid uhci_hcd ehci_hcd usbcore bnx2 ext3 jbd scsi_dh_alua scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc dm_round_robin dm_multipath scsi_dh dm_snapshot edd dm_mod fan thermal processor cciss sd_mod scsi_mod
Oct 22 07:07:15 cygnus kernel: Pid: 9619, comm: cifsd Tainted: GF U 2.6.16.60-0.54.5-smp #1
Oct 22 07:07:15 cygnus kernel: RIP: 0010:[<ffffffff8012cb5b>] <ffffffff8012cb5b>{try_to_wake_up+53}
Oct 22 07:07:15 cygnus kernel: RSP: 0018:ffff810536e7ddd8 EFLAGS: 00010096
Oct 22 07:07:15 cygnus kernel: RAX: 0000000027986310 RBX: ffffffff8042f700 RCX: 0000000000000092
Oct 22 07:07:15 cygnus kernel: RDX: 0000000000000000 RSI: 000000000000000f RDI: ffff8108ab48e7d0
Oct 22 07:07:15 cygnus kernel: RBP: ffff810536e7de58 R08: 0000000000001ae0 R09: 000000000000fa53
Oct 22 07:07:15 cygnus kernel: R10: 0000000000007d29 R11: ffff81080ac8fdc0 R12: ffff8108ab48e7d0
Oct 22 07:07:15 cygnus kernel: R13: ffffffff8042f700 R14: 000000000000000f R15: ffff8106759f6000
Oct 22 07:07:15 cygnus kernel: FS: 0000000000000000(0000) GS:ffff8108ff57eec0(0000) knlGS:0000000000000000
Oct 22 07:07:15 cygnus kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0 CR3: 0000000077d95000 CR4: 00000000000006e0
Oct 22 07:07:15 cygnus kernel: Process cifsd (pid: 9619, threadinfo ffff810536e7c000, task ffff810138cf5080)
Oct 22 07:07:15 cygnus kernel: Stack: 00000000000000d0 000000004959e140 0000000000000061 ffffffff80164839
Oct 22 07:07:15 cygnus kernel: 0000000000000002 000000028012c2eb ffff8106759f613e 0000000000000000
Oct 22 07:07:15 cygnus kernel: 0000000000000004 0000000000000296
Oct 22 07:07:15 cygnus kernel: Call Trace: <ffffffff80164839>{mempool_alloc+49}<ffffffff884ae ca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0}<fff fffff884bdaa4>{:cifs:cifs_demultiplex_thread+2137}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884bd24b>{:cifs:cifs_demultiplex_thread+0 }<ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff80148525>{keventd_create_kthread+0} <ffffffff801487ed>{kthread+236}<ffffffff884baa90>{ :cifs:reset_cifs_unix_caps+460}
Oct 22 07:07:15 cygnus kernel: <ffffffff8010bea6>{child_rip+8} <ffffffff80148525>{keventd_create_kthread+0}
Oct 22 07:07:15 cygnus kernel:
Oct 22 07:07:15 cygnus kernel: <ffffffff80148701>{kthread+0} <ffffffff8010be9e>{child_rip+0}<ffffffff884aeca8>{ :cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: Code: 48 8b 04 c5 20
Oct 22 07:07:15 cygnus kernel: 12 3f 80 4c 03 68 08 4c 89 ef e8 54 43 1c 00
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96}< 1>RIP
Oct 22 07:07:15 cygnus kernel: <ffffffff8012cb5b>{try_to_wake_up+53} RSP <ffff810536e7ddd8>
Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
Oct 22 07:07:15 cygnus kernel: <ffffffff884b00eb>{:cifs:CIFSSMBQFSPosixInfo+96} <ffffffff884ae48a>{:cifs:cifs_statfs+155}
Oct 22 07:07:15 cygnus kernel: <ffffffff80186044>{vfs_statfs+108} <ffffffff801afc98>{compat_sys_statfs+63}
Oct 22 07:07:15 cygnus kernel: <ffffffff801fbc97>{_atomic_dec_and_lock+51} <ffffffff8019d4cc>{dput+64}
Oct 22 07:07:15 cygnus kernel: <ffffffff801865ec>{sys_close+143} <ffffffff80122d2c>{sysenter_do_call+27}
Oct 22 07:07:15 cygnus kernel: <1>Unable to handle kernel paging request at 00000000bd022aa0 RIP:
Oct 22 07:07:15 cygnus kernel: <ffffffff802ef4c9>{__sched_text_start+2769}
Oct 22 07:07:15 cygnus kernel: PGD 77268f067 PUD 0
Oct 22 07:07:15 cygnus kernel: Oops: 0000 [2] SMP
Oct 22 07:07:15 cygnus kernel: last sysfs file: /devices/pci0000:00/0000:00:1c.2/0000:04:00.1/irq
Oct 22 07:07:15 cygnus kernel: CPU 6
Oct 22 07:07:15 cygnus kernel: Modules linked in: ipt_MASQUERADE nls_cp850 smbfs ip6t_REJECT ipt_REJECT ipt_LOG xt_limit xt_state ip6table_mangle iptable_mangle ip6table_filter ip6_tables binfmt_misc st sr_mod ide_disk ide_cd cdrom joydev xt_tcpudp ipt_multiport iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables fuse ntfs usb_storage ide_core af_packet nls_utf8 cifs softdog mptctl mptbase sg vboxpci vboxnetadp vboxnetflt hpilo vboxdrv bnx2i scsi_transport_iscsi cnic 8021q bonding ipv6 dock button battery ac apparmor loop usbhid uhci_hcd ehci_hcd usbcore bnx2 ext3 jbd scsi_dh_alua scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc dm_round_robin dm_multipath scsi_dh dm_snapshot edd dm_mod fan thermal processor cciss sd_mod scsi_mod
Oct 22 07:07:15 cygnus kernel: Pid: 5937, comm: cmahostd Tainted: GF U 2.6.16.60-0.54.5-smp #1
Oct 22 07:07:15 cygnus kernel: RIP: 0010:[<ffffffff802ef4c9>] <ffffffff802ef4c9>{__sched_text_start+2769}
Oct 22 07:07:15 cygnus kernel: RSP: 0018:ffff8107726ac4d8 EFLAGS: 00210083
Oct 22 07:07:15 cygnus kernel: RAX: ffff8107726ac000 RBX: ffff8108ab48e7d0 RCX: ffff8108ab48e7d0
Oct 22 07:07:15 cygnus kernel: RDX: 0000000027986310 RSI: 0000000000000000 RDI: ffff81000107d800
Oct 22 07:07:15 cygnus kernel: RBP: ffff8107726ac598 R08: ffff8108aebc8000 R09: 0000000000000001
Oct 22 07:07:15 cygnus kernel: R10: 0000000000200286 R11: 0000000000000000 R12: ffff8108ab48e7d0
Oct 22 07:07:15 cygnus kernel: R13: 00000000000009c4 R14: ffff8108ab48e808 R15: 0000000000000000
Oct 22 07:07:15 cygnus kernel: FS: 0000000000000000(0000) GS:ffff8108ff62dbc0(0063) knlGS:00000000f7d838c0
Oct 22 07:07:15 cygnus kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0 CR3: 000000077268d000 CR4: 00000000000006e0
Oct 22 07:40:15 cygnus syslog-ng[5044]: syslog-ng version 1.6.8 starting
Oct 22 07:40:15 cygnus auditd[5194]: Init complete, auditd 1.2.9 listening for events
Oct 22 07:40:15 cygnus bnx2i-daemon[5264]: bnx2id daemon started.
Oct 22 07:40:15 cygnus rcpowersaved: CPU frequency scaling is not supported by your processor.
Oct 22 07:40:15 cygnus rcpowersaved: enter 'CPUFREQ_ENABLED=no' in /etc/powersave/cpufreq to avoid this warning.
Oct 22 07:40:15 cygnus rcpowersaved: Cannot load cpufreq governors - No cpufreq driver available
Oct 22 07:40:16 cygnus sshd[5389]: Server listening on 0.0.0.0 port 22.
Oct 22 07:40:16 cygnus rcpowersaved: s2ram does not know your machine. See 's2ram -i' for details. (127)
Oct 22 07:40:16 cygnus rcpowersaved: Use SUSPEND2RAM_FORCE=yes to override this detection.
Oct 22 07:40:16 cygnus [powersave-set_disk_settings][5454]: WARNING: could not retrieve list of disks from HAL:
Oct 22 07:40:16 cygnus vcagentd: Type: 4 - Event ID: 1073741884
Oct 22 07:40:18 cygnus modprobe: FATAL: Error running install command for binfmt_misc
Oct 22 07:40:18 cygnus ntpd[5527]: ntpd [email protected] Sat Sep 5 11:15:41 UTC 2009 (1)
Oct 22 07:40:18 cygnus ntpd[5539]: precision = 1.000 usec
Oct 22 07:40:18 cygnus ntpd[5539]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #2 lo, 127.0.0.2#123 Enabled
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #3 bond0, 192.168.5.73#123 Disabled
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #4 vlan40, 192.168.3.2#123 Disabled
Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #5 vlan50, 172.0.0.5#123 Disabled
Oct 22 07:40:18 cygnus ntpd[5539]: kernel time sync status 0040
Oct 22 07:40:18 cygnus ntpd[5539]: frequency initialized 12.181 PPM from /var/lib/ntp/drift/ntp.drift
Oct 22 07:40:18 cygnus /usr/sbin/cron[5564]: (CRON) STARTUP (V5.0)
Oct 22 07:40:20 cygnus kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 22 07:40:20 cygnus syslog-ng[5044]: Changing permissions on special file /dev/xconsole
Oct 22 07:40:20 cygnus syslog-ng[5044]: Changing permissions on special file /dev/tty10
Oct 22 07:40:20 cygnus kernel: JBD: barrier-based sync failed on dm-3 - disabling barriers
Oct 22 07:40:20 cygnus kernel: AppArmor: AppArmor initialized
Oct 22 07:40:20 cygnus kernel: audit(1413938407.210:2): info="AppArmor initialized" pid=3465
Oct 22 07:40:20 cygnus kernel: IA-32 Microcode Update Driver: v1.14 <[email protected]>
Oct 22 07:40:20 cygnus kernel: ACPI: Power Button (FF) [PWRF]
Oct 22 07:40:20 cygnus kernel: IA-32 Microcode Update Driver v1.14 unregistered
Oct 22 07:40:20 cygnus kernel: No dock devices found.
Oct 22 07:40:20 cygnus kernel: floppy0: no floppy controllers found
Oct 22 07:40:20 cygnus kernel: Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008)
Oct 22 07:40:20 cygnus kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
Oct 22 07:40:20 cygnus kernel: bonding: bond0: setting mode to active-backup (1).
Oct 22 07:40:20 cygnus kernel: bonding: bond0: Setting MII monitoring interval to 100.
Oct 22 07:40:20 cygnus kernel: bnx2: eth0: using MSI
Oct 22 07:40:20 cygnus kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link.
Oct 22 07:40:20 cygnus kernel: bnx2: eth2: using MSI
Oct 22 07:40:20 cygnus kernel: bonding: bond0: enslaving eth2 as a backup interface with a down link.
Oct 22 07:40:20 cygnus kernel: bonding: bond1 is being created...
Oct 22 07:40:20 cygnus kernel: bonding: bond1: setting mode to balance-tlb (5).
Oct 22 07:40:20 cygnus kernel: bonding: bond1: Setting MII monitoring interval to 100.
Oct 22 07:40:20 cygnus kernel: bnx2: eth1: using MSI
Oct 22 07:40:20 cygnus kernel: bonding: bond1: enslaving eth1 as an active interface with a down link.
Oct 22 07:40:20 cygnus kernel: bnx2: eth3: using MSI
Oct 22 07:40:20 cygnus kernel: bonding: bond1: enslaving eth3 as an active interface with a down link.
Oct 22 07:40:20 cygnus kernel: 802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
Oct 22 07:40:20 cygnus kernel: All bugs added by David S. Miller <[email protected]>
Oct 22 07:40:20 cygnus kernel: vlan40: add 01:00:5e:00:00:01 mcast address to master interface
Oct 22 07:40:20 cygnus kernel: vlan50: add 01:00:5e:00:00:01 mcast address to master interface
Oct 22 07:40:20 cygnus kernel: cnic: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: Broadcom NetXtreme II CNIC Driver cnic v1.9.13b (Dec 16, 2009)
Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth0
Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth1
Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth2
Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth3
Oct 22 07:40:20 cygnus kernel: Loading iSCSI transport class v2.0-724.
Oct 22 07:40:20 cygnus kernel: bnx2i: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: bnx2i: no version for "cnic_register_driver" found: kernel tainted.
Oct 22 07:40:20 cygnus kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v1.8.12g (Apr 12, 2010)
Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-040001)
Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth3, iscsi=bcm570x-040001
Oct 22 07:40:20 cygnus kernel: bnx2i [04:00.01]: ISCSI_INIT passed
Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-040000)
Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth2, iscsi=bcm570x-040000
Oct 22 07:40:20 cygnus kernel: bnx2i [04:00.00]: ISCSI_INIT passed
Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-030001)
Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth1, iscsi=bcm570x-030001
Oct 22 07:40:20 cygnus kernel: bnx2i [03:00.01]: ISCSI_INIT passed
Oct 22 07:40:20 cygnus kernel: audit(1413938415.718:3): audit_pid=5194 old=0 by auid=4294967295
Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-030000)
Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth0, iscsi=bcm570x-030000
Oct 22 07:40:20 cygnus kernel: bnx2i [03:00.00]: ISCSI_INIT passed
Oct 22 07:40:20 cygnus kernel: vboxdrv: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: vboxdrv: Found 8 processor cores.
Oct 22 07:40:20 cygnus kernel: VBoxDrv: dbg - g_abExecMemory=ffffffff88256380
Oct 22 07:40:20 cygnus kernel: vboxdrv: fAsync=0 offMin=0x8f6 offMax=0x10ce8
Oct 22 07:40:20 cygnus kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Oct 22 07:40:20 cygnus kernel: vboxdrv: Successfully loaded version 4.1.8 (interface 0x00190000).
Oct 22 07:40:20 cygnus kernel: hpilo: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: ACPI: PCI Interrupt 0000:02:00.2[B] -> GSI 17 (level, low) -> IRQ 138
Oct 22 07:40:20 cygnus kernel: PCI: Setting latency timer of device 0000:02:00.2 to 64
Oct 22 07:40:20 cygnus kernel: vboxnetflt: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: vboxnetadp: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: vboxpci: module not supported by Novell, setting U taint flag.
Oct 22 07:40:20 cygnus kernel: vboxpci: pci-stub module not available, cannot detach PCI devices
Oct 22 07:40:20 cygnus kernel: vboxpci: IOMMU not found (not compiled)
Oct 22 07:40:20 cygnus kernel: bnx2: eth3 NIC Copper Link is Up, 1000 Mbps full duplex
Oct 22 07:40:20 cygnus kernel: bonding: bond1: link status definitely up for interface eth3.
Oct 22 07:40:20 cygnus kernel: bonding: bond1: making interface eth3 the new active one.
Oct 22 07:40:20 cygnus kernel: bonding: bond1: first active interface up!
Oct 22 07:40:27 cygnus kernel: bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:27 cygnus kernel: bonding: bond0: link status definitely up for interface eth0.
Oct 22 07:40:27 cygnus kernel: bonding: bond0: making interface eth0 the new active one.
Oct 22 07:40:27 cygnus kernel: bonding: bond0: first active interface up!
Oct 22 07:40:30 cygnus kernel: bnx2: eth1 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:30 cygnus kernel: bonding: bond1: link status definitely up for interface eth1.
Oct 22 07:40:32 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:32 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Oct 22 07:40:32 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
Oct 22 07:40:32 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 22 07:40:34 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:34 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Oct 22 07:40:35 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
Oct 22 07:40:35 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 22 07:40:35 cygnus hpasmlited[5722]: hpDeferSPDThread: Starting thread to collect DIMM SPD Data.
Oct 22 07:40:36 cygnus kernel: Fusion MPT base driver 3.04.07_suse
Oct 22 07:40:36 cygnus kernel: Copyright (c) 1999-2008 LSI Corporation
Oct 22 07:40:36 cygnus kernel: Fusion MPT misc device (ioctl) driver 3.04.07_suse
Oct 22 07:40:36 cygnus kernel: mptctl: Registered with Fusion MPT base driver
Oct 22 07:40:36 cygnus kernel: mptctl: /dev/mptctl @ (major,minor=10,220)
Oct 22 07:40:36 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:36 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Oct 22 07:40:37 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
Oct 22 07:40:37 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 22 07:40:39 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:39 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Oct 22 07:40:39 cygnus kernel: ipmi message handler version 38.2
Oct 22 07:40:39 cygnus kernel: IPMI Watchdog: driver initialized
Oct 22 07:40:39 cygnus hpasrd[7367]: Starting with poll 1 and timeout 600.
Oct 22 07:40:39 cygnus hpasrd[7367]: Setting the watchdog timer.
Oct 22 07:40:39 cygnus kernel: Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0)
Oct 22 07:40:39 cygnus hpasrd[7367]: Preferred watchdog driver not found.
Oct 22 07:40:39 cygnus hpasrd[7367]: Found iLO memory at 0xf1ff0000.
Oct 22 07:40:39 cygnus hpasrd[7367]: Successfully mapped device.
Oct 22 07:40:39 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
Oct 22 07:40:39 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 22 07:40:41 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
Oct 22 07:40:41 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Oct 22 07:40:42 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
Oct 22 07:40:42 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 22 07:40:43 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 10 Mbps full duplex
Oct 22 07:40:43 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
Please help me to find root cause off this problem. Is there another log that i should be checking?
Regards

On 22/10/2014 04:56, syahrianto wrote:
> I'm using SLES 10 SP3 for all my transaction servers and database
> servers.
These forums are for Novell's Open Enterprise Server (OES) product which
is an add-on for SUSE Linux Enterprise Server.
If you are using "regular" SLES then you should repost in one of SUSE's
Forums for SLES @
https://forums.suse.com/forumdisplay...erprise-Server
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Hyper-v 2012 r2 slow throughputs on network / live migrations

Hi, maybe someone can point me in the right direction, I have 10 servers 5 Dell r210s and 5 Dell R320's, I have basically converted these servers to standalone hyper-v 2012 servers, so there is no clustering on any at the moment.
Each server is configured with 2 1Gb nics teamed via a virtual switch, now when I copt files between server 1 and 2 for example I see 100MBs throughput, but if I copy a file to server 3 at the same time the file copy load splits the 100MBs throughput between
the 2 copy processes. I was under the impression if I copied 2 files to 2 totally different servers the load would basically be split across the 2 nics effectively giving me 2Gbs throughput but this does not seem to be the case. I have played around with tcpip
large send offloads, jumbo packets, disabled vmq on the cards, they are broadcoms. :-( but it doesn't really seem to make a difference with all of these settings.
The other issue is If I live migrate a 12Gb vm machine running only 2gb ram, effectively just an o/s it takes between 15 to 20 minutes to migrate, I have played around with the advanced settings, smb, compression, tcpip not real game changers, BUT if I shut
town the vm and migrate it, it takes, just under 3 and a half minutes to move across.
I am really stumped here, I am busy in a test phase of hyper-v but cant find any definitive documents relating to this stuff.

Hi Mark,
The servers (hyper-v 2012 r2) are all basically configured with ssvmm2012R2 where they all have teamed 1Gb pNics, into a virtual switch, then there are vNics for the Vmcloud, live migration etc. The physical network is 2 Netgear Gs724T switches which
are interlinked and each servers 1st nic is plugged into the switch1 and the second nic is plugged into the switch2.See Below Image) The hyper-v port is set to independent Hyper-v load balancing.
The R320 servers are running raid 5 sas drives, the R210s have 1Tb drives mirrored. The servers all are using DAS storage, we have not moved to looking at using iscsi and san is out the question at the moment.
I am currently testing between 2x 320s and 2x R210s, I am not copying data to the vm's yets, I am basically testing the transfer between the actual hosts at the moment by copying a 4Gb file manually, After testing the live migrations I decided to test to
see the transfer rates between the servers first, I have been playing around with the offload settings and rss, what I don't understand is yesterday, the copy between the servers was running up to 228Mbs ie (using both nics) when copying
the file between the servers, and then a few hours later it only was copying at 50/60Mbs, but its now back at 113Mbs seemingly to be only using one nic.
I was under the impression if you copy a file between 2 servers the nicks could use the 2gb bandwidth, but after reading many posts they say only one nic, so how did the copies get up to 2Gb yesterday. Then again if you copy files between 3 servers, then
each copy would use one nic, basically giving you 2Gbs, but this is again not being seen.
Regards Keith

Hyper-V 2012 R2 Remote Management with Windows 8.1 using Microsoft Account (Workgroup)

Hello,
I've set up a Hyper-V 2012 R2 Server and tried to manage it from a Windows 8.1 with a Microsoft Account. Everything is in the same workgroup. After many searches, the only way is set up the server for remote access, install RSAT and log on with an Administrator
account from the server in Server Manager console.
So, this situation generates a question: since it's impossible to set up a Microsoft Account in Hyper-V server as a local user, it's impossible to use "the same account and password" way to establish a link between server and desktop? I must use
a remote account for connection? Why Windows 8.1 local account and online account can't be merged as a single account?
By the way, there are some consoles that cmdkey doesn't work, so it's not an option.
Best regards.
Herleson Pontes MCT | MCITP | MCSA | MCTS | MCP | MOS http://www.herlesonpontes.com.br – [email protected]

I have not fully tried this myself but I know this:
A microsoft account can only be added to Server as a User, and only after Desktop Experience has been added. This is also how you enable the MSFT Store on Server.
This also requires a Full install of Server and is not possible on the free Hyper-V Server SKU.
But, the legacy Server Manager console that Hyper-V Manager is built on has no concept of this new user account type. And neither does Kerberos (the default security mechanism).
So, my guess is that the best you can do is treat it the same as any workgroup machines.
If you use Azure AD and sync your domain credentials, you have the password equivalent. But you still require some AD in the middle. This is simply the current state of affairs.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

RDS - Issue using Windows 10 build 9926 as Virtual Desktop Infrastructure on Hyper-V 2012 R2

We currently have a production Windows 8.1 as a VDI/RDS on Hyper-V 2012 R2. On testing the last build of Windows 10 (98??) we had no issues deploying this in same RDS as pooled desktops.
The latest build 9926, although correctly sysprep-ed (either by removing AppX modern apps that have been updated, or not connecting the template to the internet), the build is only ever partially successful. Some VMs build others do not, and the ones that
build cannot be managed via RDS/Server Manager, functions such as logging a user off with server manager, result in an error. (WTS API failed)
Build Error on connection Broker - Microsoft-Windows-TerminalServices-SessionBroker
VM host [HOSTSERVER05] failed to execute VM Provisioning operation [Task: To perform post processing actions at VMHostAgent:] for virtual machine [VDI-W10-57] in pool [VDI_Advanced_Te], Error: [Error code: 0x88130221.]
Any guidance on how to troubleshoot this would be greatly appreciated, although I suspect something regarding the auto-deployment/unattend and management systems though RDS no longer works with the latest Windows 10 build.
Already posted this in the
Windows Insider Program site, but was asked to re-post here. Thanks

OK, I've carried out some more testing on the client site and have been able to move a couple of existing VMs from their 2008 R2 Hyper-V server to the new 2012 R2 server.
Both VMs are Windows 7 SP1 with the RDP 8.0 update installed and I can connect to them from a Thin Client running RDP 7.1 and a laptop running RDP 8.0.
When I add the RemoteFX vGPU to them both I can still connect from both devices but, as suggested, when connecting from the laptop with RDP 8.0 I don't get the vGPU performance (but the vGPU is still shown in the device manager).
It all looks good at the moment but I'm still concerned as to why I was unable to connect to the first VM I moved over (it was complaining about a error in the License network communication or similar).
I'll keep testing and post anything else that might be useful.
Cheers for now
Russell

Delegate permission on Hyper-V 2012 R2

Hi
I'm having problem to delegate permission on Hyper-V 2012R2,
Error - " you do not have the required permission to complete this task contact the administrator of the authorization policy for the computer 'localhost' "
Everything is working great on Hyper-V 2012 (NOT R2).
The steps that i'm doing are:
1)Using the AzMan.msc i'm opening the 'InitialStore.xml'.
2)in the Role Definition i'm creating new Role Definition.
3)After creating the Role Definition i'm adding the following tasks :
a. Allow Input to Virtual Machine.
b.Allow Output from virtual Machine.
c.Pause and Restart VM
d.Read Service Configuration
e.Start VM
f.Stop VM
g.View VM Configuration
4)In the Role Assignments I'm creating new group.
5)Adding the user from the AD.
6)Adding the user to Remote Desktop Users in the server management.
As i mentioned in server 2012 (NOT R2) it working great, since i started to install 2012R2 it's stopped working.
Any idea?

When searching this forum, you will find that issues with AzMan have been previously reported. The reason is that AzMan for Hyper-V has been deprecated and no longer supports what you are attempting to accomplish. This is now handled via
System Center Virtual Machine Manager.
.:|:.:|:. tim

VMs on Hyper-V 2012 R2 are shutting down automatically

Hello Guys!
I'm having a huge problem in my Hyper-V 2012 R2 environment. Yesterday, 9 of 40 VMs were shutdown automatically, and so, caused a downtime problem to my customers in the business hours.
I checked in the Event Viewer (Application / System / Microsoft - Windows - Hyper) of the Host and VM but I couldn't locate any log related to this unexpected shutdown.
It occurred twice yesterday, the first in the morning and the second in the afternoon. I'm afraid that this issue can happen again. I've tried to locate some logs to identify this problem, but no luck here.
My question: Is there any other place where it can help me in this troubleshooting to find the root cause?
Obs: All the VMs are licensed / activated.
Obs2: The VMs are Win 2008 R2 Std
Leandro Soares - MCP/MCSA/MCTS

Hello Brian!
The customers doesn't have access using the RDP / ICA. The role machines is web servers.
In the VMs I can find only the following log:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 24/06/2014 11:09:04
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: xxx
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
But on the Host Hyper-V I cannot find any error related to this failure as I described in this thread.
Leandro Soares - MCP/MCSA/MCTS

Virtual Machine Manager to manage Hyper-V 2012 R2 Servers

Hi,
I am trying to create an environment wherein I have few Hyper-V 2012 R2 hosts, Windows Server 2012 hosts, and Windows Server 2008 hosts. All are registered to a AD server.
On Windows Server 2012 host, I have created a virtual machine on which System Center Virtual Machine Manager 2012 SP1 is running. This Virtual Machine Manager is perfectly able to manage Windows Server 2008 hosts.
However when tried to add Windows Server 2012 hosts and Hyper-V 2012 R2 hosts, it gives the following error:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Checked:
> WS-Management service is running
> VMM agent got installed
Questions:
1. Whether System Center 2012 SP1 - Virtual Machine Manager is compatible to manage Hyper-V Sever 2012 and Windows 2012 R2 Server.
2. What is the latest version of VMM to manage Hyper-V Sever 2012 and Windows 2012 R2 Server.

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Move VMs from Hyper-V 2008 R1 to Hyper-V 2012 R2

I have a Server with Windows Server 2008 (NOT R2) running with the Hyper-V role installed and 8 VMs.
I want to move them to our new server running Hyper-V 2012 R2.
I tried to copy the original files to the 2012 Server and Import them as described in a similar article on this site (not allowed to post a link) but I get following error message (translated from German):
Error while importing.
The VM-Version of the virtual Maschine xxx could not be updated: unknown error 0x80004005
The VM-Version 1.0 of the virtual Maschine is not supported.
Any suggestons / ideas on how to fix this Problem?

Hi Ralf,
>>I am afraid that there might occur a Problem with a double SID now?
There is no "double SID" if the SID that you mentioned is Virtual Machine SID , because you have created a new VM with new SID .
But if you mean operation system SID (I assume that OS is windows OS) then "double SID" might arise when they are online at the same time (but I think the original VM should be offline after you create that new VM ).
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Moving VMs From One Hyper-v 2012 R2 to Another Hyper-v 2012 R2

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks
It all depends on your environment and your current Hyper-V configuration.
I asume both servers are domain-member of the same domain and don't use SCVMM. If so, then make sure you do the following:
First enable the "Live Migration" feature in the Hyper-V settings on both Hyper-V Servers.
Make sure both Hyper-V Servers have a vSwitch configured with the same display name and connectivity. They must be somewhat identical, but not everything. As long as the connectivity is the same.
Make sure you have a location to store the VM files on SERVER2.
Then do a Live Migration from SERVER1 to SERVER2, follow the wizard. By using the Hyper-V Manager console on SERVER1.
NOTE1: Without computer certificates and Kerberos configuration on your Live Migration settings you cannot initiate a Live Migration from the Hyper-V Manager cconsole on SERVER2. With the default configuration, you have to login on (or connect
to) SERVER1 en then initiate the Live Migration.
NOTE2: If you can't configure the vSwitches the same. Then you have to shut down the VMs and do a Quick Migration. Then re-configure the VM network properties and power on the VMs.
I hope this information will help you goin on. If you need more detailed information use the following link:
Configure Live Migration and Migrating Virtual Machines without Failover Clustering
http://technet.microsoft.com/nl-nl/library/jj134199.aspx
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

SLES 10 (SP3) on Hyper-V 2012 R2

Similar Messages

Maybe you are looking for