RDS over PXE?
Here is the setup:
I currently am Running a 2012 R2 Domain which includes Remote Desktop Services. I have a pool of stateless VM's that I currently have users connect to for their VDI solution. Issue is I want to remove the HDD from the users desktops which are essentially
Thick clients at this time. There are a bunch of reasons why I would want to do this but let's just say it is for security. The Stateless Desktop Pool is literally locked in a Data Center. I want to boot these machines directly to the stateless VM's is this
possible at all or will I need to buy thin or zero-clients first?
Brendan Quinn
I don't know if they still have it, but Microsoft used to have a thin client product that allowed you to install that on the desktop PCs in order to do exactly what you are describing. The idea was for customers to redeploy older desktops to use
as thin clients. I don't remember the details, but I think it allowed the desktops to PXE boot into this thin client.
.:|:.:|:. tim
Similar Messages
-
Having issues with Surface Pro 3 downloading boot image over PXE
Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also? -
Installing Windows 7, 8 and 8.1 using ISOs, Answer Files and Driver files over PXE boot
I have a validation lab that uses Windows 7, 8 and 8.1 on several completely different systems. I am looking for an easy way for the techs to PXE boot from a 2012 Server, select the OS to install and have the OS installed with drivers so when they come back
to the system it has the OS installed with no Bangs in Device Manager.
I have done this in the past (7-8 years ago) and it was fairly easy. Now from what I read it appears I have to create "Image" files for each system type? I hope I am misreading this because that method is counter-productive to create 10 different
images for 10 different systems.
I thought I used WDS and AIK on a 2K3 Server but I don't remember.
Is there a method/tool to install the operating systems as I described above using original OS ISOs, unattended answer files and driver files? WDS or SCCM? AM I misreading how it works?Consider using newer Windows ADK
http://www.microsoft.com/en-us/download/details.aspx?id=39982 -
Installing arch on an eeepc with pxe
I have no flash drive at the moment, and I need to learn how to install over pxe, so I opened up all the proper documentation and followed it. But I can't start my dhcp server. I'm illiterate when it comes to networking.
I'm following this guide:
http://wiki.archlinux.org/index.php/PXE
which says to put this in /etc/dhcpd.conf:
# /etc/dhcpd.conf
option domain-name-servers 208.67.222.222, 208.67.220.220;
default-lease-time 86400;
max-lease-time 604800;
authoritative;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.10 192.168.0.49;
filename "pxelinux.0"; # the PXELinux boot agent
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
It specifically says to replace the default .conf with this one. So I open up dhcpd.conf and paste it in and nothing happens.
Here is the output of ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1A:92:6C:4B:5B
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21a:92ff:fe6c:4b5b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:670271 errors:0 dropped:0 overruns:0 frame:0
TX packets:469131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:910906738 (868.7 Mb) TX bytes:57291644 (54.6 Mb)
Interrupt:30 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:596 errors:0 dropped:0 overruns:0 frame:0
TX packets:596 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:35800 (34.9 Kb) TX bytes:35800 (34.9 Kb)
Here is the dhcpd.conf in its entirety, where is the 'default' that I'm suppose to replace? :
# dhcpd.conf
# Sample configuration file for ISC dhcpd
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# Use this to enble / disable dynamic dns updates globally.
#ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
subnet 10.152.187.0 netmask 255.255.255.0 {
# This is a very basic subnet declaration.
subnet 10.254.239.0 netmask 255.255.255.224 {
range 10.254.239.10 10.254.239.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
subnet 10.254.239.32 netmask 255.255.255.224 {
range dynamic-bootp 10.254.239.40 10.254.239.60;
option broadcast-address 10.254.239.31;
option routers rtr-239-32-1.example.org;
A slightly different configuration for an internal subnet.
subnet 10.5.5.0 netmask 255.255.255.224 {
range 10.5.5.26 10.5.5.30;
option domain-name-servers ns1.internal.example.org;
option domain-name "internal.example.org";
option routers 10.5.5.1;
option broadcast-address 10.5.5.31;
default-lease-time 600;
# max-lease-time 7200;
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
host passacaglia {
hardware ethernet 0:0:c0:5d:bd:95;
filename "vmunix.passacaglia";
server-name "toccata.fugue.com";
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
host fantasia {
hardware ethernet 08:00:07:26:c0:a5;
fixed-address fantasia.fugue.com;
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
class "foo" {
match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
shared-network 224-29 {
subnet 10.17.224.0 netmask 255.255.255.0 {
option routers rtr-224.example.org;
subnet 10.0.29.0 netmask 255.255.255.0 {
option routers rtr-29.example.org;
pool {
allow members of "foo";
range 10.17.224.10 10.17.224.250;
pool {
deny members of "foo";
range 10.0.29.10 10.0.29.230;
Guidance please?Just to be clear:-
i) you've a separate machine being configured for dhcp?
ii) how is that machine connected to your network?
iii) does the server have multiple interfaces?
Multiple dhcp servers operating on the same LAN will cause problems.
Let's assume the dhcp server was working:-
i) how are you testing this?
ii) how is your machine "without a flash drive" connected to the server?
iii) what's the server logs saying; syslog / dmesg / kern.log
Last edited by n1md4 (2010-03-01 17:38:07) -
[self-fixed] PXE booting w/ NFS
I'm having trouble getting an image I created using larch (I know not part of the standard arch packages).
I've figured out that I need to use a combination of DHCP/TFTP/NFS to get it to work. So far I've gotten pretty close to getting this working (it boots the kernel and initrd but it seems to fail on the nfs?) I get up to the point where it loads the hooks [net] and [larch], and it stops with a
: Looking for /dev/nfs
!! Sorry, couldn't find boot medium ...
I'm not familiar with a dev/nfs device, it certainly isn't here on the pxe server. dhcp/tftp/nfs-server daemons are all started (and I am able to mount the nfsshare on the server itself)
dhcp.conf looks like
subnet 192.168.0.0 netmask 255.255.0.0 {
option subnet-mask 255.255.0.0;
option time-offset -18000; # Eastern Standard Time
next-server 192.168.0.2;
filename "pxelinux.0";
allow booting;
allow bootp;
range 192.168.0.10 192.168.0.200;
authoritative;
exports looks like
/var/nfsshare *(rw,subtree_check,no_root_squash)
hosts.allow looks like
tftpd: ALL
in.tftpd: ALL
nfsd: ALL
rpcbind: ALL
mountd:ALL
conf.d/tftpd looks like
TFTPD_ARGS="-l -s /var/tftpboot"
and finally pxelinux default config
default pxelinux
label pxelinux
kernel vmlinuz26
append initrd=larch.img rootfstype=nfs root=/larch nfsroot=192.168.0.2:/var/nfsshare,v3,rsize=16384,wsize=16384 ip=::::::dhcp
the squashfs files in /var/nfsshare are r/w permissions to all (666). I do realized that I don't have the most secure setup in theese files, but I'm trying to get this working first before I tighten it down. (The entire network is within arms reach of me and not connected to anything else, so I'm not worried).
I'm a bit stuck, the creator of larch sent me a howto on pxebooting and I tried to follow it the best I could, if perhaps anyone saw an obvious problem
Last edited by valid (2011-04-06 15:45:25)ok I tried doing this without using larch instead using the guide here:
https://wiki.archlinux.org/index.php/Di … t_NFS_root
I was able to get into arch (a bit slow, but speed issue can be worked on later)...the weird thing is......it never ran my rc.local command on startup (it looks like rc.multi is fine and calls rc.local if it exists, which it does at least by the time I login)........is there a different file I need to use to have a startup script when booting over pxe?
Last edited by valid (2011-04-06 15:25:03) -
W520 - BIOS update (8buj19uc.iso) hangs after PXE booting
After PXE booting the latest 1.40 BIOS bootable CD,
the system hangs after pressing "2. Update system program"
Here my setup:
LABEL w520bios
MENU LABEL ^w. BIOS V1.40 W520 - 32bit - Normal - ISO - (EN)
TEXT HELP
* Boot the W520 BIOS ISO image over PXE
ENDTEXT
LINUX memdisk
INITRD ../isos/bios/w520/8buj19uc.iso
APPEND iso raw
I need this feature, because we have several thinkpads to update!
Any help regard this topic is greatly appreciatedI had no clue what PXE is, so I looked it up:
The Preboot eXecution Environment (PXE, also known as Pre-Execution Environment; sometimes pronounced "pixie") is an environment to bootcomputers using a network interface independently of data storage devices (like hard disks) or installed operating systems.
http://en.wikipedia.org/wiki/Preboot_Execution_Environment
W520 4270CTO i7-2820QM Quadro2000M 1920x1080 Display 16GB RAM 2x240GB Intel 510 SSDs (RAID 0) - BIOS 1.42 - PCMark7:4,568
Samsung Series 9 15-inch NP900X4C-A03US - PCMark7: 4674 -
Hi All,
can anyone please confirm if pxe boot works with gen 2 vms in hyperv? I have wds installed in standalone mode. When ever I create new gen 2 vm, it takes ip, downloads some file and it says
Station
IP address is x.x.x.x
Server
IP address is x.x.x.x
NBP filename is boot\x64\wdsmgfw.efi
NBP
filesize is 1459552 Bytes
Downloading
NBP file...
PXE-E18: Server response timeout.
Boot
Failed. EFI SCSI Device
Boot
Failed. EFI Network.
No
Operating System was Loaded. Press a key to retry the boot sequence
I have tried with and without enabling secure boot option. I have wds(standalone mode), MDT and gen 2 vms. Can anyone please guide me how to make gen 2 vms boot over pxe?
Chaitanya.
Chaitanya.Hi,
You might need to set DHCP options 60, 66, 67 and 4011:
60: set the identifier to "PXEClient" (without the quotes) - pop it in all the active (I put it in the inactive scopes as well, for over-zealous safety) DHCP scopes, just in case the request is picked up by another zone/scope (ensure there are
sufficient IP addresses within the scope[s] - bit of daft point, but it wouldn't be the first time I have seen a PXE boot fail because there aren't any available IPv4 addresses)
66: set the Boot Server Host Name "<boot_server_name>.<...>.<CN>.<CN>" or by IPv4 address
67: set the Boot File Name; stop WDS from listening on UDP Port 67 - it will be used by DHCP:: ensure the full path is listed (verify this before running the PXEboot) - Just as side note, I tend to make the folder containing the file read/write - not sure
it actually does anything, but it frequently makes things a bit "smoother".
4011: ensure that PXE broadcasts from the clients are routed by WDS properly i.e.: the traffic should go to the appropriate server (DHCP, WDS and possibly BootTP if configured)
Also, and don't take this wrong way, but check, check and check again that the boot order settings are set in the Hyper-V Manager correctly. Time and time again I have come up against this one. Sometimes, for whatever reason, Hyper-v will put
the defaults back in, so you think you are booting off the network, and will be told as such, but will actually be booting off DVD/CD...
Create a VM, open the settings and then start the VM; watch the settings in the left hand pane. If all is well, there will no change, if all is not well, there may be a slight "jump" as the VM starts up.
Could be an idea to start DHCP from the command line - if you have access to it and there are no impediments, there isn't (shouldn't be) any problem with ensuring it has started.
Hope this helps
- quick note, I'm not available for a couple of days but hopefully one of the other kind and generous souls on this site will assist you if you run into any problems.
have a good one! :D
Cheers
Andrew
Oh, just had thought, check that you are utilizing only one IP address per network adapter on the client, DHCP and WDS servers. There's a conflict between DHCP and RIS - or at least used to be, not sure if it has been fixed/sorted.
Cheers! Andrew -
Does Arch have a PXE Net Installation?
As the topic reads, I'm trying to install Arch on a few computers using PXE. I've found a few topics that show how to BOOT Arch Live using PXE, but that's not what I'm looking for. I'm looking to install arch on a computer using PXE.
Debian makes the process really simple with their network boot package. http://www.debian.org/distrib/netinst
Does Arch something similar?
Many Thanks!foolishrobot wrote:Debian makes the process really simple with their network boot package. http://www.debian.org/distrib/netinst
Does Arch something similar?
i know what you mean, i'm currently searching for something like that, but didn't succeed yet. I use the debian netinstall (over pxe) alot and it works like a charm.
to be honest, i want this for archlinux to... no need setup NFS or NBD. I just want to boot a simple little environment which gives me the ability to install archlinux by getting all the things i need from the internet, keeping everything in ram until it is installed.
I thought the page mentioned in this topic (regarding pxe boot) would do exactly this, but after reading this topic, i think i might have been missing something.
Due to the reason i still haven't found a solution to this, i assume such an netinstall image does not exist for arch linux... but what about creating one.
Archlinux already removed the AIF from the installation media (which is great) i think it wouldn't be so hard to support a basic netinstall image.
Debian does support it, and it helps a lot.
About the size, just for the people who don't know about the debian netinstall: on my tftp server (which is used for pxe) i keep 2 setups (one for x86 and one for x64) each setup has a kernel and an initramdisk. all together, they only measure about 16MB in size.
This might be possible for arch linux as well, don't you think? -
Hi
I just wanted to create a windows live cd/dvd and some how convert it to a boot wim file and then put it on a wds server so clients can boot to windows over pxe.
Any Idea?!? :)
**************** Sincerely Yours Ziyaei Ali *****************Thank you for your reply
I'm not going to use this live windows as a whole day use computer, its going to be used for few hours and nothing more.
I'm completely familiar with vdi infra and ...
Imagine a scenario of advanced MDT windows deployment scenario, everything is fine and working great.
Now some body calls from a branch office and claim his system does not boot any more and he has some critical data on C drive which he needs.
MDT can help deploy windows but it formats the C drive. I need to boot the system temporarily so the normal user can copy his files and then restart again and install windows by pressing F12 and so on...
So no I need a live CD or something like this which is compatible with WDS.
There are a lots of live cds who can be booted from network but non of them are compatible with WDS.
Any idea or help would be kindly appreciated.
**************** Sincerely Yours Ziyaei Ali ***************** -
Node crashes when enabling RDS for private interconnect.
OS: oel6.3 - 2.6.39-300.17.2.el6uek.x86_64
Grid and DB: 11.2.0.3.4
This is a two node Standard Edition cluster.
The node crashes upon restart of clusterware after following the instructions from note:751343.1 (RAC Support for RDS Over Infiniband) to enable RDS.
The cluster is running fine using ipoib for the cluster_interconnect.
1) As the ORACLE_HOME/GI_HOME owner, stop all resources (database, listener, ASM etc) that's running from the home. When stopping database, use NORMAL or IMMEDIATE option.
2) As root, if relinking 11gR2 Grid Infrastructure (GI) home, unlock GI home: GI_HOME/crs/install/rootcrs.pl -unlock
3) As the ORACLE_HOME/GI_HOME owner, go to ORACLE_HOME/GI_HOME and cd to rdbms/lib
4) As the ORACLE_HOME/GI_HOME owner, issue "make -f ins_rdbms.mk ipc_rds ioracle"
5) As root, if relinking 11gR2 Grid Infrastructure (GI) home, lock GI home: GI_HOME/crs/install/rootcrs.pl -patch
Looks to abend when asm tries to start with the message below on the console.
I have a service request open for this issue but, I am hoping someone may have seen this and has
some way around it.
Thanks
Alan
kernel BUG at net/rds/ib_send.c:547!
invalid opcode: 0000 [#1] SMP
CPU 2
Modules linked in: 8021q garp stp llc iptable_filter ip_tables nfs lockd
fscache auth_rpcgss nfs_acl sunrpc cpufreq_ondemand powernow_k8
freq_table mperf rds_rdma rds_tcp rds ib_ipoib rdma_ucm ib_ucm ib_uverbs
ib_umad rdma_cm ib_cm iw_cm ib_addr ipv6 ib_sa sr_mod cdrom microcode
serio_raw pcspkr ghes hed k10temp hwmon amd64_edac_mod edac_core
edac_mce_amd i2c_piix4 i2c_core sg igb dca mlx4_ib ib_mad ib_core
mlx4_en mlx4_core ext4 mbcache jbd2 usb_storage sd_mod crc_t10dif ahci
libahci dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
scsi_wait_scan]
Pid: 4140, comm: kworker/u:1 Not tainted 2.6.39-300.17.2.el6uek.x86_64
#1 Supermicro BHDGT/BHDGT
RIP: 0010:[<ffffffffa02db829>] [<ffffffffa02db829>]
rds_ib_xmit+0xa69/0xaf0 [rds_rdma]
RSP: 0018:ffff880fb84a3c50 EFLAGS: 00010202
RAX: ffff880fbb694000 RBX: ffff880fb3e4e600 RCX: 0000000000000000
RDX: 0000000000000030 RSI: ffff880fbb6c3a00 RDI: ffff880fb058a048
RBP: ffff880fb84a3d30 R08: 0000000000000fd0 R09: ffff880fbb6c3b90
R10: 0000000000000000 R11: 000000000000001a R12: ffff880fbb6c3a00
R13: ffff880fbb6c3a00 R14: 0000000000000000 R15: ffff880fb84a3d90
FS: 00007fd0a3a56700(0000) GS:ffff88101e240000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000002158ca2 CR3: 0000000001783000 CR4: 00000000000406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kworker/u:1 (pid: 4140, threadinfo ffff880fb84a2000, task
ffff880fae970180)
Stack:
0000000000012200 0000000000012200 ffff880f00000000 0000000000000000
000000000000e5b0 ffffffff8115af81 ffffffff81b8d6c0 ffffffffa02b2e12
00000001bf272240 ffffffff81267020 ffff880fbb6c3a00 0000003000000002
Call Trace:
[<ffffffff8115af81>] ? __kmalloc+0x1f1/0x200
[<ffffffffa02b2e12>] ? rds_message_alloc+0x22/0x90 [rds]
[<ffffffff81267020>] ? sg_init_table+0x30/0x50
[<ffffffffa02b2db2>] ? rds_message_alloc_sgs+0x62/0xa0 [rds]
[<ffffffffa02b31e4>] ? rds_message_map_pages+0xa4/0x110 [rds]
[<ffffffffa02b4f3b>] rds_send_xmit+0x38b/0x6e0 [rds]
[<ffffffff81089d53>] ? cwq_activate_first_delayed+0x53/0x100
[<ffffffffa02b6040>] ? rds_recv_worker+0xc0/0xc0 [rds]
[<ffffffffa02b6075>] rds_send_worker+0x35/0xc0 [rds]
[<ffffffff81089fd6>] process_one_work+0x136/0x450
[<ffffffff8108bbe0>] worker_thread+0x170/0x3c0
[<ffffffff8108ba70>] ? manage_workers+0x120/0x120
[<ffffffff810907e6>] kthread+0x96/0xa0
[<ffffffff81515544>] kernel_thread_helper+0x4/0x10
[<ffffffff81090750>] ? kthread_worker_fn+0x1a0/0x1a0
[<ffffffff81515540>] ? gs_change+0x13/0x13
Code: ff ff e9 b1 fe ff ff 48 8b 0d b4 54 4b e1 48 89 8d 70 ff ff ff e9
71 ff ff ff 83 bd 7c ff ff ff 00 0f 84 f4 f5 ff ff 0f 0b eb fe <0f> 0b
eb fe 44 8b 8d 48 ff ff ff 41 b7 01 e9 51 f6 ff ff 0f 0b
RIP [<ffffffffa02db829>] rds_ib_xmit+0xa69/0xaf0 [rds_rdma]
RSP <ffff880fb84a3c50>
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.39-300.17.2.el6uek.x86_64
([email protected]) (gcc version 4.4.6 20110731 (Red
Hat 4.4.6-3) (GCC) ) #1 SMP Wed Nov 7 17:48:36 PST 2012
Command line: ro root=UUID=5ad1a268-b813-40da-bb76-d04895215677
rd_DM_UUID=ddf1_stor rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us numa=off
console=ttyS1,115200n8 irqpoll maxcpus=1 nr_cpus=1 reset_devices
cgroup_disable=memory mce=off memmap=exactmap memmap=538K@64K
memmap=130508K@770048K elfcorehdr=900556K memmap=72K#3668608K
memmap=184K#3668680K
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000100 - 0000000000096800 (usable)
BIOS-e820: 0000000000096800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000dfe90000 (usable)
BIOS-e820: 00000000dfe9e000 - 00000000dfea0000 (reserved)
BIOS-e820: 00000000dfea0000 - 00000000dfeb2000 (ACPI data)
BIOS-e820: 00000000dfeb2000 - 00000000dfee0000 (ACPI NVS)
BIOS-e820: 00000000dfee0000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)I believe OFED version is 1.5.3.3 but I am not sure if this is correct.
We have not added any third parry drivers. All that has been done to add infiniband to our build is
a yum groupinstall iInfiniband support.
I have not tries rds-stress but rds-ping works fine and rds-info seems fine.
A service request has been opened but so far I have had better response here.
oracle@blade1-6:~> rds-info
RDS IB Connections:
LocalAddr RemoteAddr LocalDev RemoteDev
10.10.0.116 10.10.0.119 fe80::25:90ff:ff07:df1d fe80::25:90ff:ff07:e0e5
TCP Connections:
LocalAddr LPort RemoteAddr RPort HdrRemain DataRemain SentNxt ExpectUna SeenUna
Counters:
CounterName Value
conn_reset 5
recv_drop_bad_checksum 0
recv_drop_old_seq 0
recv_drop_no_sock 1
recv_drop_dead_sock 0
recv_deliver_raced 0
recv_delivered 18
recv_queued 18
recv_immediate_retry 0
recv_delayed_retry 0
recv_ack_required 4
recv_rdma_bytes 0
recv_ping 14
send_queue_empty 18
send_queue_full 0
send_lock_contention 0
send_lock_queue_raced 0
send_immediate_retry 0
send_delayed_retry 0
send_drop_acked 0
send_ack_required 3
send_queued 32
send_rdma 0
send_rdma_bytes 0
send_pong 14
page_remainder_hit 0
page_remainder_miss 0
copy_to_user 0
copy_from_user 0
cong_update_queued 0
cong_update_received 1
cong_send_error 0
cong_send_blocked 0
ib_connect_raced 4
ib_listen_closed_stale 0
ib_tx_cq_call 6
ib_tx_cq_event 6
ib_tx_ring_full 0
ib_tx_throttle 0
ib_tx_sg_mapping_failure 0
ib_tx_stalled 16
ib_tx_credit_updates 0
ib_rx_cq_call 33
ib_rx_cq_event 38
ib_rx_ring_empty 0
ib_rx_refill_from_cq 0
ib_rx_refill_from_thread 0
ib_rx_alloc_limit 0
ib_rx_credit_updates 0
ib_ack_sent 4
ib_ack_send_failure 0
ib_ack_send_delayed 0
ib_ack_send_piggybacked 0
ib_ack_received 3
ib_rdma_mr_alloc 0
ib_rdma_mr_free 0
ib_rdma_mr_used 0
ib_rdma_mr_pool_flush 8
ib_rdma_mr_pool_wait 0
ib_rdma_mr_pool_depleted 0
ib_atomic_cswp 0
ib_atomic_fadd 0
iw_connect_raced 0
iw_listen_closed_stale 0
iw_tx_cq_call 0
iw_tx_cq_event 0
iw_tx_ring_full 0
iw_tx_throttle 0
iw_tx_sg_mapping_failure 0
iw_tx_stalled 0
iw_tx_credit_updates 0
iw_rx_cq_call 0
iw_rx_cq_event 0
iw_rx_ring_empty 0
iw_rx_refill_from_cq 0
iw_rx_refill_from_thread 0
iw_rx_alloc_limit 0
iw_rx_credit_updates 0
iw_ack_sent 0
iw_ack_send_failure 0
iw_ack_send_delayed 0
iw_ack_send_piggybacked 0
iw_ack_received 0
iw_rdma_mr_alloc 0
iw_rdma_mr_free 0
iw_rdma_mr_used 0
iw_rdma_mr_pool_flush 0
iw_rdma_mr_pool_wait 0
iw_rdma_mr_pool_depleted 0
tcp_data_ready_calls 0
tcp_write_space_calls 0
tcp_sndbuf_full 0
tcp_connect_raced 0
tcp_listen_closed_stale 0
RDS Sockets:
BoundAddr BPort ConnAddr CPort SndBuf RcvBuf Inode
0.0.0.0 0 0.0.0.0 0 131072 131072 340441
RDS Connections:
LocalAddr RemoteAddr NextTX NextRX Flg
10.10.0.116 10.10.0.119 33 38 --C
Receive Message Queue:
LocalAddr LPort RemoteAddr RPort Seq Bytes
Send Message Queue:
LocalAddr LPort RemoteAddr RPort Seq Bytes
Retransmit Message Queue:
LocalAddr LPort RemoteAddr RPort Seq Bytes
10.10.0.116 0 10.10.0.119 40549 32 0
oracle@blade1-6:~> cat /etc/rdma/rdma.conf
# Load IPoIB
IPOIB_LOAD=yes
# Load SRP module
SRP_LOAD=no
# Load iSER module
ISER_LOAD=no
# Load RDS network protocol
RDS_LOAD=yes
# Should we modify the system mtrr registers? We may need to do this if you
# get messages from the ib_ipath driver saying that it couldn't enable
# write combining for the PIO buffs on the card.
# Note: recent kernels should do this for us, but in case they don't, we'll
# leave this option
FIXUP_MTRR_REGS=no
# Should we enable the NFSoRDMA service?
NFSoRDMA_LOAD=yes
NFSoRDMA_PORT=2050
oracle@blade1-6:~> /etc/init.d/rdma status
Low level hardware support loaded:
mlx4_ib
Upper layer protocol modules:
rds_rdma ib_ipoib
User space access modules:
rdma_ucm ib_ucm ib_uverbs ib_umad
Connection management modules:
rdma_cm ib_cm iw_cm
Configured IPoIB interfaces: none
Currently active IPoIB interfaces: ib0 -
How To: Debug missing Drivers in MDT
The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
○ Open the Device Manager (devmgmt.msc).
○ Find the network device in the list (ensure this is the wired device, not the wireless device)
○ Right click on "Properties" and click on the "Details" tab.
○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
PCI\VEN_8086&DEV_1502&CC_020000
PCI\VEN_8086&DEV_1502&CC_0200
○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
○ You should get a confirmation that the driver package was installed.
○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
○ Try connecting to the Deployment Share:
c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
○ Try pinging the Deployment Server:
c:\> Ping.exe MDT.Corp.contoso.com
○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
○ From within the MDT console, right click on the root of your Deployment Share and select properties.
○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
○ Open up the MDT console.
○ Download and run the DbgView.exe tool.
○ Update the deployment share in question.
○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
○ PnpEnum.xml (from Client)
○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
○ c:\windows\inf\SetupAPI.*.log (from client)
○ %DeployRoot%\control\Driver*.xml
○ %DeployRoot%\control\SelectionProfile*.xml
○ %DeployRoot%\control\settings.xml (if problems in WinPE)
○ x:\windows\System32\WpeInit.log (if problems in WinPE)
○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.comOK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ -
Infiniband support in Standard Edition RAC
Hi,
This document states that there is no InfiniBand support in Standard Edition:
http://docs.oracle.com/cd/E11882_01/license.112/e47877/editions.htm#DBLIC116
But I'm able to start Standard Edition RAC 11.2.0.4 with either UDP over IB or RDS over IB as private interconnect.
So, what exactly does it mean that Standard Edition does not support IB?ArtemD wrote:
But I'm able to start Standard Edition RAC 11.2.0.4 with either UDP over IB or RDS over IB as private interconnect.
So, what exactly does it mean that Standard Edition does not support IB?
You can run IPoIB (IP over Infiniband) for supporting a standard IP stack. You can also configure it for connected mode (7000 byte MTU recommended). From a TCP/UDP/IP application perspective (such as Oracle), it is just another standard IP stack being used.
Oracle may argue that relinking the rdbms executable for using RDS as oppose to UDP is a violation of the SE license. But I seriously doubt that they will claim SE prevents you from using IB all together and that using IPoIB is a license violation - as that would just be plain silly.
But then from an IB perspective - a SE RAC is a really a small minor cluster. Where the performance and scalability provided by IB is pretty much unused and wasted.
So SE not supporting IB is more a support statement I think from Oracle (not supporting high-end Interconnect with low-end cluster), and not a statement of incompatibility of SE with IB. -
[solved] No sound and AMD-Vi: Event logged
Hello,
Today I started to migrate my HTPC from openElec to Arch Linux since several things started to annoy me.
For now, I have made a fresh install and installed XBMC but I can't get audio. It is a AMD setup and has an Asus Xonar XD PCIe card installed. Integrated HD Audio is disabled.
The user xbmc is in the audio group and when I ssh into the HTPC and try to play a file with aplay I get tons of these on the TV:
[ 46.215678] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x0000000000100000 flags=0x0050]
Channels are unmuted and I priorized the output with the following alsa-base.conf:
options snd slots=snd_virtuoso
options snd_virtuoso index=0
Alsamixer shows the desired sound card as default.
xbmc@xbmc ~ % LANG= aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: DX [Xonar DX], device 0: Multichannel [Multichannel]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: DX [Xonar DX], device 1: Digital [Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
xbmc@xbmc ~ % aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=DX
Xonar DX, Multichannel
Default Audio Device
sysdefault:CARD=DX
Xonar DX, Multichannel
Default Audio Device
front:CARD=DX,DEV=0
Xonar DX, Multichannel
Front speakers
surround40:CARD=DX,DEV=0
Xonar DX, Multichannel
4.0 Surround output to Front and Rear speakers
surround41:CARD=DX,DEV=0
Xonar DX, Multichannel
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=DX,DEV=0
Xonar DX, Multichannel
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=DX,DEV=0
Xonar DX, Multichannel
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=DX,DEV=0
Xonar DX, Multichannel
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=DX,DEV=0
Xonar DX, Multichannel
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=HDMI,DEV=0
HDA ATI HDMI, HDMI 0
HDMI Audio Output
Setting iommu=pt as suggested here did not do any trick...
Does anyone here have a hint of what can be wrong?
Maybe this is interesting, too. The device, the AMD-Vi-Event refers to, is the mentioned sound card.
xbmc@xbmc ~ % lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 03)
00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 03)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 14)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 5
01:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)
02:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
Last edited by And1G (2013-08-20 13:43:11)Can't anyone help on this one? I just checked with a Fedora 19 Live image (Kernel 3.9.5) and I get the same error messages in dmesg as in this Arch installation, also no audio.
I believe the problem here might not be directly audio related, but where could I search for the cause?
Also, I don't really think it's a hardware failure since audio is working nice with openElec (using Kernel 3.10, if I remember that right)...
Edit: So I've set up openELEC to boot (over PXE, so I don't have to reinstall everything) and sound is working out of the box. Here is some data for comparison to the above statements from the Arch system:
xbmc:~ # cat /proc/cmdline
root=/dev/ram0 rdinit=/init BOOT_IMAGE=openelec/KERNEL ip=dhcp boot=NFS=192.168.178.20:/srv/nfs/openelec disk=NFS=192.168.178.20:/srv/nfs/openelec overlay
xbmc:~ # uname -r
3.10.5
xbmc:~ # lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Device 9993
00:01.1 Audio device: Advanced Micro Devices [AMD] nee ATI Device 9902
00:02.0 PCI bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Port
00:04.0 PCI bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Port
00:10.0 USB controller: Advanced Micro Devices [AMD] Hudson USB XHCI Controller (rev 03)
00:10.1 USB controller: Advanced Micro Devices [AMD] Hudson USB XHCI Controller (rev 03)
00:11.0 SATA controller: Advanced Micro Devices [AMD] Hudson SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices [AMD] Hudson USB OHCI Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices [AMD] Hudson USB EHCI Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices [AMD] Hudson USB OHCI Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices [AMD] Hudson USB EHCI Controller (rev 11)
00:14.0 SMBus: Advanced Micro Devices [AMD] Hudson SMBus Controller (rev 14)
00:14.2 Audio device: Advanced Micro Devices [AMD] Hudson Azalia Controller (rev 01)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] Hudson LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices [AMD] Hudson PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices [AMD] Hudson USB OHCI Controller (rev 11)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 5
01:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)
02:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
xbmc:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: DX [Xonar DX], device 0: Multichannel [Multichannel]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: DX [Xonar DX], device 1: Digital [Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
xbmc:~ # aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=DX
Xonar DX, Multichannel
Default Audio Device
sysdefault:CARD=DX
Xonar DX, Multichannel
Default Audio Device
front:CARD=DX,DEV=0
Xonar DX, Multichannel
Front speakers
surround40:CARD=DX,DEV=0
Xonar DX, Multichannel
4.0 Surround output to Front and Rear speakers
surround41:CARD=DX,DEV=0
Xonar DX, Multichannel
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=DX,DEV=0
Xonar DX, Multichannel
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=DX,DEV=0
Xonar DX, Multichannel
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=DX,DEV=0
Xonar DX, Multichannel
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=DX,DEV=0
Xonar DX, Multichannel
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=HDMI,DEV=0
HDA ATI HDMI, HDMI 0
HDMI Audio Output
default:CARD=Generic
HD-Audio Generic, ALC887-VD Analog
Default Audio Device
sysdefault:CARD=Generic
HD-Audio Generic, ALC887-VD Analog
Default Audio Device
front:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
Front speakers
surround40:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Generic,DEV=0
HD-Audio Generic, ALC887-VD Digital
IEC958 (S/PDIF) Digital Audio Output
Not a single one of these AMD-Vi Events is in the dmesg output.
Does anyone have a clue on how I could figure out if they installed uncommon patches or use weird parameters to get all this running?
Edit #2:
So I've searched through some of these odd IOMMU options and found this: https://www.kernel.org/doc/Documentatio … ptions.txt
I tried iommu=soft as a kernel parameter and I get audio output and the AMD-Vi Events are no longer present. But can anyone explain to me what exactly I have done here? Using a "software bounce buffering" seems weird to me if I have some hardware present, that can do such things (The IOMMU, I assume)...
Since this really does not look like only audio-related problem, can someone perhaps move the thread to the right place. Although I'm not quite sure which this will be.
Last edited by And1G (2013-08-19 22:12:20) -
Occasional Task Sequence fail (1 out of 5) with Error 615 Your Password is too short
We have a task sequence that fails to install software and updates with an error liek this: Operation System Error 615: The password you provided was too short for the computers password policy. Please provide a longer password.
With all software installations I always tick the continue on failure. Consequently in a task sequence you see the entire list of installation requirements fail with this error. This includes Applications, Packages and Software Updates. Without any amendment,
the next time it is run, it runs successfully. Add to this the issue that the task sequence no longer displays the progress bar after rebooting into windows (x64) and it all points to the OSD process being a bit flaky.
By the way, we are installing Win7 x64 (No x86 anymore) over PXE.
So any pointers with this would be very gratefully received.
Anthony Sheehy - MCP, MCITPHere is the status message sent to Configuration Manager:
The task sequence execution engine failed executing the action (Freefall Sensor) in the group (Install) with the error code 2278559764
Action output: 7"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)
0, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\WGS00137
reference count 1 for the source C:\_SMSTaskSequence\Packages\WGS00137 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\WGS00137
Released the resolved source C:\_SMSTaskSequence\Packages\WGS00137
pInstall->Install(sPackageID, sProgramName), HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Failed to invoke Execution Manager to Install Software for PackageID='WGS00137' ProgramID='Silent Installation' AdvertID='WES20013' hr=0x87d01014
InstallSoftware failed, hr=0x87d01014
Install Software failed, hr=0x87d01014. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
And here's the group policy that is applied to that OU:
Enforce password history
0 passwords remembered
Maximum password age
0 days
Minimum password age
0 days
Minimum password length
0 characters
Password must meet complexity requirements
Disabled
Of course, the password complexity issue is a non-starter: How come SCCM 2007 task sequences did not have the same problem? Why does the Task Sequence work
sometimes and not others. All passwords I provide to Configuration Manager all conform to complexity rules anyway.
The relevant SMSTS.log portion is below:
<![LOG[Variable name: _SMSSWDProgramName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsswd.exe /pkg:WGS00137 /install /basevar: /continueOnError:]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 90]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Applications]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_382fdd99-2228-452d-a6f0-63e543ce628d /basevar: /continueOnError:True]LOG]!><time="18:06:06.660-60"
date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 91]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Language Packs]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_9df3ec9a-e691-4106-b274-46c4c6c319b9,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_42e28566-b339-4773-92cf-05b8e748d996,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_305b4a34-0b5a-46fe-82dd-c57a5897e063,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_379afca3-f48e-486b-8848-296223481edd,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_502bf2db-e1c8-42ac-a499-61320d661cc3,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_455a6de9-fe98-47ed-8dab-e860dd4681ed,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_1707c97e-b4bb-4827-9117-02e79435213e,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_a17f2337-ad2e-42cb-9813-c9e167a85050
/basevar: /continueOnError:True]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 92]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[Processed all elements]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:333">
<![LOG[Adding end group instruction at 93]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:402">
<![LOG[The next instruction after group will be at 94]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:408">
<![LOG[
Parsing step node: Opt In to CEIP and WER]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
Anthony Sheehy - MCP, MCITP -
I'm trying to deploy Windows 8 over PXE within a Hyper-V VM.
I used the Assessment and Deployment Kit to create a PE environment that is served through my (Linux) TFTP server. But I have problems with getting the keyboard / mouse / network to work within Hyper-V.
The environment was created with the following command:
copype amd64 C:\tmp\pe
The boot.wim created in c:\tmp\pe\sources I have mounted with the following command:
dism.exe /mount-wim /wimfile:c:\tmp\pe\sources\boot.wim /index:1 /mountdir:c:\tmp\mount
For injecting the Hyper-V drivers I used the Windows6.2-HyperVIntegrationServices-x86.cab file within c:\windows\system32\vmguest.iso.
After extracting this cab file I have inserted every driver within it with the following command:
forfiles /p c:\tmp\drivers /s /m *inf /c "cmd /c dism /image:c:\tmp\mount /add-driver /driver:@path /forceunsigned"
Which returns it successfully added the drivers.
The Hyper-V VM is created as Gen 2 without the Secure Boot option. The Windows PE environment starts perfectly, but at the end, when the command prompt is opened and after wpeinit is executed, the keyboard / mouse, or network for that matter, is not working.
Can someone point me out which step I have forgotten to make this work?
Thanks in advance !Sorry, wrong account. please see below
Hello,
im trying set up a test environment, specifically trying to image a VM using SCCM2012 R2 and a local installation of hyper v on my workstation
I created a new virtual hard disk with my PE media inside, but when I boot off of it from my VM I receive an error from the PE environment immediately.
"Unable to read task sequence configuration disk. for more information contact your system administrator or helpdesk operator."
when I hit F8 I see that there is no network information assigned via IPCONFIG. do I need to inject some sort of driver into my boot image for this to work? I am using a GEN 2 VM so the legacy NIC situation shouldn't apply here.
I would very much appreciate any assistance.
Maybe you are looking for
-
Can I use my creative cloud membership on a second computer?
Can anyone tell me if I am permitted to use my adobe creative cloud membership on a second computer and if so, how do I download the apps?
-
How to retrieve data from IN OUT VARCHAR2 variable of PL/SQL
Hi, everyone, OCCI : OCCI10gR2 Here is a sample PL/SQL code. SQL> CREATE PROCEDURE test4_proc( str IN OUT VARCHAR2 ) IS 2 BEGIN 3 str := str || ':' || str; 4 END; And here is a C++ sample code using OCCI. std::string sql4 = "BEGIN test4_proc(:1); END
-
Hey guys, I recently downloaded Cs4, and whenever I open up a file, it always messes up, here's a screenshot. http://i680.photobucket.com/albums/vv169/ayociscobro/needhelp.jpg No idea what the problem is, I downloaded the trial acouple of months ago
-
BPEL - using JAR libraries, compile OK, but error while deploying
Hi All, i have a BPEL process with a JAVA program inside. It uses 3 JAR files as libraries, so they are included in the project properties CLASSPATH. When i compile and deploy directly to the domain, i dont have problems. But I am using an ANT xml ,
-
InitInstance() of AXComponent not getting called
Hi, I have derived a class from AXComponent and overriden the initInstance() method but some how during execution time its not getting called. The njawin documentation says it shold get called automatically from native code. So my ActiveX component(w