|
21)
Message boards :
News :
VM applications broken by the Windows 10 update KB3206632
(Message 28446)
Posted 11 Jan 2017 by Jesse Viviano Post: Now that the cumulative patch KB3213986 is out and supersedes both KB3213522 and KB3206632, I would recommend that we install the latest Windows Update patch from now on. |
|
22)
Message boards :
Number crunching :
Microsoft KB3206632 from 16/12/15
(Message 28396)
Posted 8 Jan 2017 by Jesse Viviano Post: KB3206632 was applied as a routine Windows Update patch after I reformatted my computer. I had errors after that patch. Applying KB3213522 fixed the fault and allowed the work unit to start processing normally. I think that this fix should be put up on the news section so that others with Windows 10 faults like this one will be able to find the fix. |
|
23)
Message boards :
Number crunching :
Microsoft KB3206632 from 16/12/15
(Message 28393)
Posted 8 Jan 2017 by Jesse Viviano Post: That update is running on my system already, and Theory Simulation is not working on my machine. I am wondering if this update broke Theory Simulation because my computer was able to handle the Theory Simulation before that update. It fixed a DHCP bug, but might have broken the ability of VirtualBox to be able to perform twice NAT on DNS requests originating from VirtualBox guests when it is set to use what it calls its DNS proxy mode. Are you saying that uninstalling this update allowed Theory Simulation to work? |
|
24)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28385)
Posted 7 Jan 2017 by Jesse Viviano Post: Since the test CernVM virtual machines with the ISO that I set up that worked on my machine were not set up to use a DNS proxy, disabling NAT proxy could be a good short term fix. However, that could cause problems if the machine's DNS server changes due to an expired DHCP lease and the replacement DHCP lease containing other DNS servers that need to be used for some reason like maintenance for the DNS servers in the old DHCP lease; or the user switching internet connections because the other internet connection failed. There are three ways the DNS could be set up in VirtualBox according to what I read in the manual at https://www.virtualbox.org/manual/ch09.html: the default method where VirtualBox passes the computer's configured DNS server addresses to the virtual machine; the original NAT proxy method where VirtualBox passes a private DNS server IP address to the virtual machine to intercept the DNS traffic and performs twice NAT on that traffic (where twice NAT is Cisco's terminology for translating both the source and destination IP addresses in one transaction); and the alternate NAT proxy method in which VirtualBox passes a private DNS server IP address to the virtual machine to intercept the DNS traffic and then VirtualBox has to reconstruct the DNS request in the host OS's DNS API to go through the OS's DNS resolver as a proxy. The last method is the most work for VirtualBox, but it will cut down on network traffic because the host OS's DNS cache will resolve DNS requests from multiple virtual machines looking for the same server and could improve firewall compatibility because some host-based firewalls would expect DNS traffic to come only from the OS's resolver and might block alternate programs trying to do DNS themselves as attempts to get around the firewall. It is possible that the twice NAT DNS traffic could be misrouted into the Windows DNS cache instead of the process doing the twice NAT. It is also possible that VirtualBox has a bug with the twice NAT DNS proxy method that only is exposed with Windows 10. EDIT: Fix wrong URL |
|
25)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28380)
Posted 7 Jan 2017 by Jesse Viviano Post: I compared the DNS settings in the .vbox file you linked to in the message I am replying to and the .vbox files in the failing BOINC tasks, and noticed that the build .vbox file is set to not use a DNS proxy, but the BOINC tasks do use a DNS proxy. Could this be causing problems? EDIT: I just came up with a possible wild guess of a hypothesis of what could be going wrong. After I read https://www.virtualbox.org/manual/ch09.html#nat_host_resolver_proxy, I thought that Windows 10's networking stack could be intercepting all DNS replies and dumping them into Windows's DNS cache. If that is the case, then the DNS reply never gets back to the VM. The way to solve that is to use the host's DNS resolver as a DNS proxy as seen in the link I just wrote. I know that this is a wild guess, but it could not hurt to try using the host's DNS resolver as a DNS proxy. Using the host's DNS resolver as a DNS proxy would also cut down on DNS traffic from multiple virtual machines running at the same time because the host's DNS cache would catch DNS requests to the same domain names which would be redundant to the same real machine but not to each VM. If this change succeeds, I would recommend this to other VirtualBox projects like ATLAS@home to enhance software firewall compatibility because they might expect DNS queries from the host OS's DNS resolver and nowhere else, and to cut DNS traffic that would be redundant coming from the same machine because the host DNS resolver could have the requested information in its cache that could be reused by multiple virtual machines. |
|
26)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28378)
Posted 7 Jan 2017 by Jesse Viviano Post: I have tried that. Adding cable="true" did not allow the VM to work. I have even gave it a hard power down, edited the .vbox file, and manually restarted the VM. That did not allow the VM to work. Have you tried using a utility like diff or WinMerge on some of the .vbox files for the VMs that do work and the VMs that do not work? I also noticed that ATLAS@home uses the same network configuration in its .vbox files, and they still work. |
|
27)
Message boards :
Number crunching :
Max # CPUs vs projects?
(Message 28342)
Posted 4 Jan 2017 by Jesse Viviano Post: ATLAS@home at https://lhcathome.cern.ch/ATLAS/ provides up to 8-core tasks. |
|
28)
Message boards :
Number crunching :
Weird error message.
(Message 28338)
Posted 4 Jan 2017 by Jesse Viviano Post: The only work units that are properly self-contained in LHC@home are part of the the SixTrack and the sixtracktest subprojects. The rest require a network connection to even run. |
|
29)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28328)
Posted 3 Jan 2017 by Jesse Viviano Post: I just ran these tests as well, and it looks like the job successfully starts. It works, but not in BOINC. |
|
30)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28314)
Posted 2 Jan 2017 by Jesse Viviano Post: It goes to the screen with the following text requesting a login, not a command prompt: Welcome to CERN Virtual Machine, version 3.6.5.15 In short, it looks just like the screen that displays when an ATLAS@home task is properly functioning. |
|
31)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28305)
Posted 2 Jan 2017 by Jesse Viviano Post: I have set up Wireshark, and have made sure to install Npcap beforehand in WinPcap compatibility mode so that Wireshark can use it. (Npcap is essentially WinPcap reworked to use NDIS 6 because Windows 10 deprecates NDIS 5 and might remove NDIS 5 at any time like it did in the Windows 10 beta which caused compatibility problems, and is also faster and more efficient. NDIS is a networking stack interface in Windows.) If a developer is ready for a PCAP, I will provide it. |
|
32)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28304)
Posted 1 Jan 2017 by Jesse Viviano Post: I am thinking of setting up Wireshark so I can capture the traffic from my Gigabit Ethernet port to allow the developer try to debug what is going on. Is any one of the developers able to accept the resulting PCAP file for debugging? |
|
33)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28302)
Posted 31 Dec 2016 by Jesse Viviano Post: I have tried a VirtualBox downgrade to version 5.1.10 which previously worked, and that did not work. |
|
34)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28300)
Posted 31 Dec 2016 by Jesse Viviano Post: I just did a complete wipe and rebuild of my computer, and I am getting the same errors as before. I just did a complete wipe and rebuild of the computer, and it did not solve my CVMFS errors. I have to conclude that there is a server problem, a VirtualBox version problem, a client software problem, or a problem with AT&T Fiber. |
|
35)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28286)
Posted 28 Dec 2016 by Jesse Viviano Post: An example that gets a file from CERN: I have repeated these experiments from my machine and have replicated the results (the first experiment gets a file while the second experiment gets an HTTP 404 Not Found error). Could someone please check the CVMFS to fix the HTTP 404 error I am getting for the file my work units are trying to retrieve? |
|
36)
Message boards :
Number crunching :
Project Working?
(Message 28274)
Posted 28 Dec 2016 by Jesse Viviano Post: This project does not use GPUs. |
|
37)
Message boards :
Number crunching :
What version of VBox to use
(Message 28256)
Posted 26 Dec 2016 by Jesse Viviano Post: Instructions for Linux are found at https://www.virtualbox.org/wiki/Linux_Downloads. Ubuntu is a Debian-based distribution, by the way. |
|
38)
Message boards :
Number crunching :
Only 1 of 40 simulation jobs finished and gave results 1
(Message 28251)
Posted 26 Dec 2016 by Jesse Viviano Post: This project uses VirtualBox and not VMware. Download VirtualBox from https://www.virtualbox.org/. |
|
39)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28240)
Posted 24 Dec 2016 by Jesse Viviano Post: I have one more possible hypothesis based on the message I am replying to. Could there be something wrong with the replication between the CERN CVMFS repository and the FNAL CVMFS repository? |
|
40)
Message boards :
Number crunching :
Missing heartbeat file errors
(Message 28239)
Posted 23 Dec 2016 by Jesse Viviano Post: I found nothing regarding inconsistent version numbers between my installation of VirtualBox and the VirtualBox Extension Pack like that. |
Previous 20 · Next 20
©2024 CERN